Sign In to Follow Application
View All Documents & Correspondence

Method And System For Sending An Alert Notification To A User Equipment (Ue) Subscriber

Abstract: METHOD AND SYSTEM FOR SENDING AN ALERT NOTIFICATION TO A USER EQUIPMENT (UE) SUBSCRIBER The present disclosure relates to a method and a system for sending an alert notification to a user equipment (UE) subscriber. The disclosure encompasses: identifying a service request for a service for the UE subscriber; cloning at least a request header and request data content into a cache; sending the service request to a producer Network Function (NF); receiving a service response comprising at least a response header and response data content from the producer NF, the service response is received in response to the service request; transmitting at least the response header and response data content to a consumer NF; merging at least the request header and at least the response header into a service request header, and the request data content and the response data content into a service data content; and sending the service request header and the service data content to an alert server. [FIG. 4]

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
04 July 2023
Publication Number
47/2024
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
Parent Application

Applicants

Jio Platforms Limited
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Inventors

1. Sandeep Bisht
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Specification

1
FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
&
THE PATENT RULES, 2003
5 COMPLETE SPECIFICATION
(See section 10 and rule 13)
10 “METHOD AND SYSTEM FOR SENDING AN ALERT NOTIFICATION TO A USER
EQUIPMENT (UE) SUBSCRIBER”
15
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5
Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
20
The following specification particularly describes the invention and the manner in which it is to be
performed.
25
2
5 METHOD AND SYSTEM FOR SENDING AN ALERT NOTIFICATION TO A USER
EQUIPMENT (UE) SUBSCRIBER
FIELD OF THE DISCLOSURE
10 [0001] Embodiments of the present disclosure generally relate to network performance
management systems. More particularly, embodiments of the present disclosure relate to
method and system for sending an alert notification to a user equipment (UE) subscriber in a
network.
15 BACKGROUND
[0002] The following description of the related art is intended to provide background
information pertaining to the field of the disclosure. This section may include certain aspects
of the art that may be related to various features of the present disclosure. However, it should
20 be appreciated that this section is used only to enhance the understanding of the reader with
respect to the present disclosure, and not as admissions of the prior art.
[0003] The following description of related art is intended to provide background information
pertaining to the field of the disclosure. This section may include certain aspects of the art that
25 may be related to various features of the present disclosure. However, it should be appreciated
that this section be used only to enhance the understanding of the reader with respect to the
present disclosure, and not as admissions of prior art.
[0004] Wireless communication technology has rapidly evolved over the past few decades,
30 with each generation bringing significant improvements and advancements. The first
generation of wireless communication technology was based on analog technology and offered
only voice services. However, with the advent of the second-generation (2G) technology,
digital communication and data services became possible, and text messaging was introduced.
3G technology marked the introduction of high-speed internet access, mobile video calling,
35 and location-based services. The fourth-generation (4G) technology revolutionized wireless
communication with faster data speeds, better network coverage, and improved security.
Currently, the fifth-generation (5G) technology is being deployed, promising even faster data
speeds, low latency, and the ability to connect multiple devices simultaneously. With each
3
5 generation, wireless communication technology has become more advanced, sophisticated, and
capable of delivering more services to its users.
[0005] A network runs by one operator in one area is known as a Public Land Mobile Network
(PLMN) and when a subscribed user uses his operator’s PLMN then it is called home PLMN
10 but when the user moves outside the home PLMN and uses the resources from other operator’s
network, then it is called visited PLMN. Roaming refers to the ability for a cellular customer
to automatically make and receive voice calls, send and receive data, or access other services,
including home data services, when the user travels outside the geographical coverage area of
the home network, by means of using the visited PLMN. The roaming charges are different for
15 when the UE subscriber moves to different visited PLMN’s. Whenever the UE subscriber
moves from one PLMN to other PLMN, there is a regulatory requirement to inform the
subscriber through SMS about the change in PLMN. This notification is called as target SMS
(example, welcome SMS).
20 [0006] However, when the UE subscriber moves out of the home PLMN, the existing
solutions failed to enable sending target SMS to the UE when the user changes PLMN in
roaming case in 5G network. Further, over the period of time various solutions have been
developed to improve the performance of communication devices and to notify the UE
subscriber about the change of the home PLMN. However, there are certain challenges with
25 existing solutions. The existing solutions failed to enable sending target SMS to the UE when
the UE subscriber changes PLMN in roaming case in 5G network.
[0007] Thus, there exists an imperative need in the art for sending an alert notification to a
user equipment (UE) subscriber in a network, which the present disclosure aims to address.
30
SUMMARY
[0008] This section is provided to introduce certain aspects of the present disclosure in a
simplified form that are further described below in the detailed description. This summary is
35 not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for sending an alert
notification to a user equipment (UE) subscriber in a network is disclosed. The method includes
4
5 identifying, by an identification unit of a service communication proxy (SCP), a service request
for a service for the UE subscriber. The method further includes cloning, by a cloning unit of
the SCP, at least a request header and request data content into a cache. The method further
includes sending, by a transceiver unit of the SCP, the service request to a producer Network
Function (NF). The method further includes receiving, by the transceiver unit of the SCP, a
10 service response comprising at least a response header and response data content from the
producer NF, the service response is received in response to the service request. The method
further includes transmitting, by the transceiver unit of the SCP, at least the response header
and response data content to a consumer NF. The method further includes merging, by a
processing unit of the SCP, at least the request header and at least the response header into a
15 service request header, and the request data content and the response data content into a service
data content. Thereafter, the method includes sending, by the transceiver unit of the SCP, the
service request header and the service data content to an alert server.
[0010] In an exemplary aspect of the present disclosure, the service request is identified based
20 at least on a predefined version of Hypertext Transfer Protocol (HTTP) pseudo-header.
[0011] In an exemplary aspect of the present disclosure, the cloning of at least the request
header and the request data is done into the cache upon successful comparison and matching
of a value of a path defined in the predefined version of HTTP pseudo header with at least
25 name of the service in the service request.
[0012] In an exemplary aspect of the present disclosure, the method comprises duplicating,
by the processing unit of the SCP, at least the response header and response data content into
the cache upon receipt of the service response from the producer NF.
30
[0013] In an exemplary aspect of the present disclosure, the method comprises sending, by
the transceiver unit of the SCP via the alert server, an alert notification to the UE subscriber in
the network based at least on determination of a change in Public Land Mobile Network
(PLMN) during roaming.
35
[0014] In an exemplary aspect of the present disclosure, the alert notification is sent to the
UE subscriber based at least on the service request header and the service data content.
5
5 [0015] In an exemplary aspect of the present disclosure, the alert notification is in Short
Message Service (SMS) format.
[0016] In an exemplary aspect of the present disclosure, merging at least the request header
and at least the response header into the service request header, and the request data content
10 and the response data content into the service data content comprises converting, by the
processing unit of the SCP, status pseudo-header from at least the response header to a
response-status; and converting, by the processing unit of the SCP, method pseudo-header from
at least the request header to a request-method, to send the service request header and the
service data content to the alert server.
15
[0017] Another aspect of the present disclosure may relate to a system for sending an alert
notification to a user equipment (UE) subscriber in a network is disclosed. The system
comprises a service communication proxy (SCP). The SCP further comprises: an identification
unit, configured to identify a service request for a service for the UE subscriber. The SCP
20 further comprises a cloning unit, configured to clone at least a request header and request data
content into a cache. The SCP further comprises a transceiver unit, configured to: send the
service request to a producer Network Function (NF). The transceiver unit is further configured
to receive a service response comprising at least a response header and response data content
from the producer NF, the service response is received in response to the service request;
25 transmit at least the response header and response data content to a consumer NF. The SCP
further comprises a processing unit, configured to merge at least the request header and at least
the response header into a service request header, and the request data content and the response
data content into a service data content. The SCP further comprises the transceiver unit is
configured to send the service request header and the service data content to an alert server.
30
[0018] Another aspect of the present disclosure may relate to a user equipment (UE),
comprising a processor configured to receive, via an alert server, an alert notification based on
the service request, wherein the alert notification is generated based on an identification of a
service request for a service for the UE subscriber.
35
[0019] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for sending an alert notification to a user
equipment (UE) subscriber in a network, the instructions include executable code which, when
6
5 executed by a one or more units of a system, causes: an identification unit to identify a service
request for a service for the UE subscriber; a cloning unit to clone at least a request header and
request data content into a cache; a transceiver unit, to send the service request to a producer
Network Function (NF); receive a service response comprising at least a response header and
response data content from the producer NF, the service response is received in response to the
10 service request; transmit at least the response header and response data content to a consumer
NF; a processing unit to merge at least the request header and at least the response header into
a service request header, and the request data content and the response data content into a
service data content; and the transceiver unit to send the service request header and the service
data content to an alert server.
15
OBJECTS OF THE INVENTION
[0020] Some of the objects of the present disclosure, which at least one embodiment disclosed
herein satisfies are listed herein below.
20
[0021] It is an object of the present disclosure to provide a system and method for enabling
the 5G network to provide the UE subscriber a target message.
[0022] It is another object of the present disclosure to provide a solution that notifies the UE
25 subscriber based on user PLMN change.
[0023] It is yet another object of the present disclosure to provide a solution to alert the UE
subscriber regarding the PLMN change.
30 DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute a part of
this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in
which like reference numerals refer to the same parts throughout the different drawings.
35 Components in the drawings are not necessarily to scale, emphasis instead being placed upon
clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the
figures are not to be construed as limiting the disclosure, but the possible variants of the method
and system according to the disclosure are illustrated herein to highlight the advantages of the
7
5 disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings
includes disclosure of electrical components or circuitry commonly used to implement such
components.
[0025] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
10 (5GC) network architecture.
[0026] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the
features of the present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure.
15
[0027] FIG. 3 illustrates an exemplary block diagram of a system for sending an alert
notification to a user equipment (UE) subscriber in a network, in accordance with exemplary
implementations of the present disclosure.
20 [0028] FIG. 4 illustrates a method flow diagram for sending an alert notification to a user
equipment (UE) subscriber in a network, in accordance with exemplary implementations of the
present disclosure.
[0029] FIG. 5 illustrates an exemplary block diagram of a system architecture for sending an
25 alert notification to a user equipment (UE) subscriber in a network, in accordance with
exemplary implementations of the present disclosure.
[0030] The foregoing shall be more apparent from the following more detailed description of
the disclosure.
30
DETAILED DESCRIPTION
[0031] In the following description, for the purposes of explanation, various specific details
are set forth in order to provide a thorough understanding of embodiments of the present
35 disclosure. It will be apparent, however, that embodiments of the present disclosure may be
practiced without these specific details. Several features described hereafter may each be used
independently of one another or with any combination of other features. An individual feature
8
5 may not address any of the problems discussed above or might address only some of the
problems discussed above.
[0032] The ensuing description provides exemplary embodiments only, and is not intended
to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing
10 description of the exemplary embodiments will provide those skilled in the art with an enabling
description for implementing an exemplary embodiment. It should be understood that various
changes may be made in the function and arrangement of elements without departing from the
spirit and scope of the disclosure as set forth.
15 [0033] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in
the art that the embodiments may be practiced without these specific details. For example,
circuits, systems, processes, and other components may be shown as components in block
diagram form in order not to obscure the embodiments in unnecessary detail.
20
[0034] Also, it is noted that individual embodiments may be described as a process which is
depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block
diagram. Although a flowchart may describe the operations as a sequential process, many of
the operations may be performed in parallel or concurrently. In addition, the order of the
25 operations may be re-arranged. A process is terminated when its operations are completed but
could have additional steps not included in a figure.
[0035] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an
example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed
30 herein is not limited by such examples. In addition, any aspect or design described herein as
“exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or
advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary
structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent
that the terms “includes,” “has,” “contains,” and other similar words are used in either the
35 detailed description or the claims, such terms are intended to be inclusive—in a manner similar
to the term “comprising” as an open transition word—without precluding any additional or
other elements.
9
5 [0036] As used herein, a “processing unit” or “processor” or “operating processor” includes
one or more processors, wherein processor refers to any logic circuitry for processing
instructions. A processor may be a general-purpose processor, a special purpose processor, a
conventional processor, a digital signal processor, a plurality of microprocessors, one or more
microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a
10 microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array
circuits, any other type of integrated circuits, etc. The processor may perform signal coding
data processing, input/output processing, and/or any other functionality that enables the
working of the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
15
[0037] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless
communication device”, “a mobile communication device”, “a communication device” may
be any electrical, electronic and/or computing device or equipment, capable of implementing
20 the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital
assistant, tablet computer, wearable device or any other computing device which is capable of
implementing the features of the present disclosure. Also, the user device may contain at least
one input means configured to receive an input from at least one of a transceiver unit, a
25 processing unit, a storage unit, a detection unit and any other such unit(s) which are required
to implement the features of the present disclosure.
[0038] As used herein, “storage unit” or “memory unit” refers to a machine or computerreadable medium including any mechanism for storing information in a form readable by a
30 computer or similar machine. For example, a computer-readable medium includes read-only
memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
storage media, flash memory devices or other types of machine-accessible storage media. The
storage unit stores at least the data that may be required by one or more units of the system to
perform their respective functions.
35
[0039] As used herein “interface” or “user interface refers to a shared boundary across which
two or more separate components of a system exchange information or data. The interface may
also be referred to a set of rules or protocols that define communication or interaction of one
10
5 or more modules or one or more units with each other, which also includes the methods,
functions, or procedures that may be called.
[0040] All modules, units, components used herein, unless explicitly excluded herein, may
be software modules or hardware processors, the processors being a general-purpose processor,
10 a special purpose processor, a conventional processor, a digital signal processor (DSP), a
plurality of microprocessors, one or more microprocessors in association with a DSP core, a
controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field
Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
15 [0041] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information or
a combination thereof between units/components within the system and/or connected with the
system.
20 [0042] As used herein, cache refers to a temporary storage area used to store copies of data
that are frequently accessed or used by a system to improve performance and efficiency. The
cache holds intermediate data, such as request headers and request data content, which can be
quickly retrieved and reused without the need to repeatedly access the original source.
25 [0043] As used herein, producer NF refers to a network function responsible for providing or
generating a specific service or resource in response to a service request from a user equipment
(UE) subscriber. The producer NF facilitates the delivery of requested services to the UE
subscriber.
30 [0044] As used herein, consumer NF refers to a network function within the
telecommunications network that receives and processes the response data from another
network function, known as the producer NF. The consumer NF acts as the end-point that
utilizes the service response to fulfil the service requested by the user equipment (UE)
subscriber.
35
[0045] As used herein, HTTP pseudo header refers to a set of predefined headers in the
HTTP/2 protocol that provide essential information about the HTTP message in a way that is
separate from the traditional HTTP headers. The pseudo headers are used for conveying the
HTTP request or response, such as the method (e.g., GET, POST), scheme (e.g., http, https),
11
5 authority (e.g., the domain name), and path (e.g., the specific resource being requested). Unlike
standard HTTP headers, pseudo headers are not included in the message body but are instead
used for framing the HTTP/2 communication, ensuring efficient and structured transmission of
the request and response metadata.
10 [0046] As used herein, an alert server refers to a dedicated network component responsible
for managing and distributing alert notifications to user equipment (UE) subscribers. The alert
server operates within the communication network to receive, process, and deliver various
types of alerts, such as welcome messages, roaming notifications, or emergency alerts, to
subscribers based on specific triggers or conditions. The alert server facilitates in maintaining
15 regulatory compliance and ensuring that subscribers are promptly informed of important
network events, changes, or emergencies through reliable and timely messaging systems like
SMS or other supported formats.
[0047] As used herein, alert notification refers to a message sent to a user equipment (UE)
20 subscriber to inform them of specific events or changes related to their network service. This
message is typically generated in response to predefined triggers, such as changes in the Public
Land Mobile Network (PLMN) during roaming, and is delivered to ensure the subscriber is
aware of important updates or actions required. The alert notification can be conveyed through
various communication formats, such as Short Message Service (SMS), and includes relevant
25 details extracted from both the service request and response, merged into a coherent and
informative message.
[0048] As used herein, Public Land Mobile Network (PLMN) refers to a network established
and operated by mobile network operators to provide wireless communication services to the
30 public. A PLMN includes various network components and infrastructure such as base stations,
switching systems, and backhaul networks that facilitate mobile telephony, data transmission,
and other wireless communication services. Each PLMN is identified by a unique combination
of a Mobile Country Code (MCC) and a Mobile Network Code (MNC), allowing it to be
distinctly recognized globally.
35
[0049] As used herein, roaming refers to the ability of a mobile device to automatically
connect to and use services from a different network operator when outside the coverage area
of its home network. The roaming allows users to make and receive calls, send texts, and access
data services while traveling beyond their home network's geographic boundaries. Roaming
12
5 ensures continuous connectivity and service availability by leveraging agreements between
network operators, enabling a seamless transition for the mobile device from one network to
another.
[0050] As discussed in the background section, the current known solutions, when the UE
10 subscriber moves out of the home PLMN, the existing solutions fail to enable sending target
SMS to the UE when the user changes PLMN in roaming case in 5G network. Further, over
the period of time various solutions have been developed to improve the performance of
communication devices and to notify the UE subscriber about the change of the home PLMN.
However, there are certain challenges with existing solutions. The existing solutions failed to
15 enable sending target SMS to the UE when the UE subscriber changes PLMN in roaming case
in 5G network.
[0051] The present disclosure aims to overcome the above-mentioned and other existing
problems in this field of technology by providing a method and system for sending an alert
20 notification to a user equipment (UE) subscriber in a network. The method includes identifying
a service request for the UE subscriber by an identification unit of a service communication
proxy (SCP). The request is then cloned, including at least the request header and request data
content, into a cache by a cloning unit of the SCP. The service request is subsequently sent to
a producer Network Function (NF) by a transceiver unit of the SCP. Upon receiving a service
25 response, which includes at least a response header and response data content from the producer
NF in response to the service request, the transceiver unit forwards these to a consumer NF.
The proposed method further involves merging, by a processing unit of the SCP, the request
header and the response header into a service request header, and the request data content and
the response data content into a service data content. This consolidated service request header
30 and service data content are then sent to an alert server by the transceiver unit. The service
request can be identified based on a predefined version of the Hypertext Transfer Protocol
(HTTP) pseudo-header. Cloning of the request header and data into the cache occurs upon
successful comparison and matching of a value defined in the HTTP pseudo-header with the
service name in the service request. Additionally, the processing unit of the SCP duplicates the
35 response header and data content into the cache upon receiving the service response from the
producer NF. An alert notification can then be sent to the UE subscriber via the alert server,
based on a determination of a change in the Public Land Mobile Network (PLMN) during
roaming. The alert notification is derived from the service request header and service data
13
5 content and can be sent in Short Message Service (SMS) format. The merging process involves
converting the status pseudo-header from the response header to a response-status and the
method pseudo-header from the request header to a request-method, allowing the transmission
of the service request header and data content to the alert server.
10 [0052] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
(5GC) network architecture, in accordance with exemplary implementation of the present
disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment
(UE) [102], a radio access network (RAN) [104], an access and mobility management function
(AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy
15 (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection
Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository
Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management
(UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data
20 network (DN) [130], wherein all the components are assumed to be connected to each other in
a manner as obvious to the person skilled in the art for implementing features of the present
disclosure.
[0053] Radio Access Network (RAN) [104] is the part of a mobile telecommunications
25 system that connects user equipment (UE) [102] to the core network (CN) and provides access
to different types of networks (e.g., 5G network). It consists of radio base stations and the radio
access technologies that enable wireless communication.
[0054] Access and Mobility Management Function (AMF) [106] is a 5G core network
30 function responsible for managing access and mobility aspects, such as UE registration,
connection, and reachability. It also handles mobility management procedures like handovers
and paging.
[0055] Session Management Function (SMF) [108] is a 5G core network function responsible
35 for managing session-related aspects, such as establishing, modifying, and releasing sessions.
It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address
allocation and QoS enforcement.
14
5 [0056] Service Communication Proxy (SCP) [110] is a network function in the 5G core
network that facilitates communication between other network functions by providing a secure
and efficient messaging service. It acts as a mediator for service-based interfaces.
[0057] Authentication Server Function (AUSF) [112] is a network function in the 5G core
10 responsible for authenticating UEs during registration and providing security services. It
generates and verifies authentication vectors and tokens.
[0058] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114]
is a network function that provides authentication and authorization services specific to
15 network slices. It ensures that UEs can access only the slices for which they are authorized.
[0059] Network Slice Selection Function (NSSF) [116] is a network function responsible for
selecting the appropriate network slice for a UE based on factors such as subscription,
requested services, and network policies.
20
[0060] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling integration with
third-party services and applications.
25 [0061] Network Repository Function (NRF) [120] is a network function that acts as a central
repository for information about available network functions and services. It facilitates the
discovery and dynamic registration of network functions.
[0062] Policy Control Function (PCF) [122] is a network function responsible for policy
30 control decisions, such as QoS, charging, and access control, based on subscriber information
and network policies.
[0063] Unified Data Management (UDM) [124] is a network function that centralizes the
management of subscriber data, including authentication, authorization, and subscription
35 information.
[0064] Application Function (AF) [126] is a network function that represents external
applications interfacing with the 5G core network to access network capabilities and services.
15
5
[0065] User Plane Function (UPF) [128] is a network function responsible for handling user
data traffic, including packet routing, forwarding, and QoS enforcement.
[0066] Data Network (DN) [130] refers to a network that provides data services to user
10 equipment (UE) in a telecommunications system. The data services may include but are not
limited to Internet services, private data network related services.
[0067] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also
referred to herein as a computer system [1000]) upon which the features of the present
15 disclosure may be implemented in accordance with exemplary implementation of the present
disclosure. In an implementation, the computing device [1000] may also implement a method
for sending an alert notification to a user equipment (UE) subscriber in a network utilising the
system. In another implementation, the computing device [1000] itself implements the method
for sending an alert notification to a user equipment (UE) subscriber in a network using one or
20 more units configured within the computing device [1000], wherein said one or more units are
capable of implementing the features as disclosed in the present disclosure.
[0068] The computing device [1000] may include a bus [1002] or other communication
mechanism for communicating information, and a hardware processor [1004] coupled with bus
25 [1002] for processing information. The hardware processor [1004] may be, for example, a
general purpose microprocessor. The computing device [1000] may also include a main
memory [1006], such as a random access memory (RAM), or other dynamic storage device,
coupled to the bus [1002] for storing information and instructions to be executed by the
processor [1004]. The main memory [1006] also may be used for storing temporary variables
30 or other intermediate information during execution of the instructions to be executed by the
processor [1004]. Such instructions, when stored in non-transitory storage media accessible to
the processor [1004], render the computing device [1000] into a special-purpose machine that
is customized to perform the operations specified in the instructions. The computing device
[1000] further includes a read only memory (ROM) [1008] or other static storage device
35 coupled to the bus [1002] for storing static information and instructions for the processor
[1004].
16
5 [0069] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is
provided and coupled to the bus [1002] for storing information and instructions. The computing
device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray
tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED
(OLED) display, etc. for displaying information to a computer user. An input device [1014],
10 including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [1002] for communicating information and command selections to the processor [1004].
Another type of user input device may be a cursor controller [1016], such as a mouse, a
trackball, or cursor direction keys, for communicating direction information and command
selections to the processor [1004], and for controlling cursor movement on the display [1012].
15 This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a
second axis (e.g., y), that allow the device to specify positions in a plane.
[0070] The computing device [1000] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic
20 which in combination with the computing device [1000] causes or programs the computing
device [1000] to be a special-purpose machine. According to one implementation, the
techniques herein are performed by the computing device [1000] in response to the processor
[1004] executing one or more sequences of one or more instructions contained in the main
memory [1006]. Such instructions may be read into the main memory [1006] from another
25 storage medium, such as the storage device [1010]. Execution of the sequences of instructions
contained in the main memory [1006] causes the processor [1004] to perform the process steps
described herein. In alternative implementations of the present disclosure, hard-wired circuitry
may be used in place of or in combination with software instructions.
30 [0071] The computing device [1000] also may include a communication interface [1018]
coupled to the bus [1002]. The communication interface [1018] provides a two-way data
communication coupling to a network link [1020] that is connected to a local network [1022].
For example, the communication interface [1018] may be an integrated services digital network
(ISDN) card, cable modem, satellite modem, or a modem to provide a data communication
35 connection to a corresponding type of telephone line. As another example, the communication
interface [1018] may be a local area network (LAN) card to provide a data communication
connection to a compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [1018] sends and receives electrical,
17
5 electromagnetic or optical signals that carry digital data streams representing various types of
information.
[0072] The computing device [1000] can send messages and receive data, including program
code, through the network(s), the network link [1020] and the communication interface [1018].
10 In the Internet example, a server [1030] might transmit a requested code for an application
program through the Internet [1028], the ISP [1026], the Host [1024], the local network [1022]
and the communication interface [1018]. The received code may be executed by the processor
[1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage
for later execution.
15
[0073] The computing device [1000] encompasses a wide range of electronic devices capable
of processing data and performing computations. Examples of computing device [1000]
include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers,
and embedded systems. The devices may operate independently or as part of a network and
20 can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally,
computing device [1000] may include peripheral devices, such as monitors, keyboards, and
printers, as well as integrated components within larger electronic systems, showcasing their
versatility in various technological applications.
25 [0074] Referring to FIG. 3, an exemplary block diagram of a system [300] for sending an
alert notification to a user equipment (UE) subscriber in a network, is shown, in accordance
with the exemplary implementations of the present disclosure. The system [300] comprises at
least one service communication proxy (SCP) [110]. The SCP [110] further comprises an
identification unit [302], at least one cloning unit [304] unit, at least one transceiver unit [306],
30 at least one a processing unit [308]. Also, all of the components/ units of the system [300] are
assumed to be connected to each other unless otherwise indicated below. As shown in the
figures all units shown within the system should also be assumed to be connected to each other.
Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple
such units or the system [300] may comprise any such numbers of said units, as required to
35 implement the features of the present disclosure. Further, in an implementation, the system
[300] may be present in a user device to implement the features of the present disclosure. The
system [300] may be a part of the user device / or may be independent of but in communication
with the user device (may also referred to herein as an UE). In another implementation, the
18
5 system [300] may reside in a server or a network entity. In yet another implementation, the
system [300] may reside partly in the server/ network entity and partly in the user device.
[0075] The system [300] is configured for sending an alert notification to a user equipment
(UE) subscriber in a network with the help of the interconnection between the
10 components/units of the system [300]. The system [300] may be incorporated within the SCP
[110], or the system [3400] may be associated with the SCP [110].
[0076] The system [300] comprises an identification unit [302]. The identification unit [302]
is configured to identify a service request for a service for the UE subscriber. For example, the
15 identification unit may analyse the metadata and request header of each request to ascertain
whether they pertain to services that the UE subscriber is entitled to or has requested. In an
exemplary aspect, the service request for the UE subscriber may correspond to the request for
preferred service such as voice service, data service, etc. Herein, the service can be any type of
service, such as a communication service (for e.g., a notification service or a callback service),
20 a context management (for e.g., user equipment context management (UECM)) service,
resource optimization service, network function management, registration, and the like. In an
example, the service request may comprise at least one of service name, service context,
nfType, and a response timeout.
25 [0077] The identification unit [302] is a part of service communication proxy (SCP) [110].
Service Communication Proxy (SCP) is a network function in the 5G core network that
facilitates communication between other network functions by providing a secure and efficient
messaging service. The SCP acts as a mediator for service-based interfaces. In an exemplary
aspect, the service request is identified based at least on a predefined version of Hypertext
30 Transfer Protocol (HTTP) pseudo-header. The identification unit [302] may identify the
predefined version of Hypertext Transfer Protocol (HTTP) pseudo-header. The predefined
version of HTTP pseudo-header includes, such as, but are not limited, to HTTP/1, HTTP/2,
and HTTP/3. As used herein, the Hypertext Transfer Protocol (HTTP) is the foundation of the
World Wide Web (WWW) and is used to load webpages using hypertext links.
35
[0078] The system [300] comprises a cloning unit [304] communicatively coupled to the
identification unit [302]. The cloning unit [304] is configured to clone at least a request header
and request data content into a cache. For example, if a service request involves streaming a
19
5 video, the request header might include details such as the type of request (e.g., GET or POST),
the URL of the video resource, and other control information like content type and encoding.
The request data content would include any parameters or data necessary for the video
streaming service to process the request. The cloning unit [304] duplicates both these parts and
stores them securely in the cache.
10
[0079] The caches are used to store temporary files, using hardware and software
components. An example of a hardware cache is a CPU cache that is used to store basic
instructions that are recently used or are frequently used.
15 [0080] In an exemplary aspect, the cloning unit [304] may communicatively attached with
the identification unit [302]. The cloning unit [304] is further configured to perform cloning of
at least the request header and the request data into the cache upon successful comparison and
matching of a value of a path defined in the predefined version of HTTP pseudo header with
at least name of the service in the service request. In case the path value defined in the
20 predefined version of HTTP pseudo header matches the desired service name, request header
and request data, content is copied in the cache. In case path value does not matches then
normal flow happens and no notification is sent to message copy server. Then, the request is
forwarded to a transceiver unit [306] for further processing.
25 [0081] The system [300] comprises a transceiver unit [306]. The transceiver unit [306] is
configured to send the service request to producer Network Function (NF). Once the cloning
unit [304] has duplicated the request header and request data content into the cache, the
transceiver unit [306] sends the service request to the producer NF. For example, a UE
subscriber initiating a cloud storage operation, such as uploading a file. The transceiver unit
30 [306] would send the service request, containing details like the file path and user credentials,
to the cloud storage server (the producer NF).
[0082] The transceiver unit [306] is further configured to receive a service response
comprising at least a response header and response data content from the producer NF, the
35 service response is received in response to the service request. After the transceiver unit [306]
sends the service request to the producer Network Function (NF), it receives the response
generated by the producer NF. For example, in a cloud storage operation where a UE subscriber
requests to upload a file, the service response received by the transceiver unit [306] would
include a header with status information about the upload request (e.g., success or failure,
20
5 storage location details) and the response data content might include metadata about the
uploaded file such as file ID, storage path, and access permissions.
[0083] Furthermore, the transceiver unit [306] is configured to transmit at least the response
header and response data content to a consumer NF. After receiving the service response from
10 the producer NF, the transceiver unit [306] transmits to the consumer NF, which is responsible
for utilizing the response data to deliver the requested service to the UE subscriber. For
instance, in a cloud storage service, after a file upload request, the transceiver unit [306]
transmits the upload confirmation response, including headers and metadata about the uploaded
file (e.g., file ID, storage path), to the consumer NF that manages the user’s cloud storage
15 account, ensuring that the user can access and verify the uploaded file.
[0084] In an exemplary aspect, the cloning unit [304] may be communicatively attached with
the transceiver unit [306]. After receiving the request from the cloning unit [304], the
transceiver unit [306] may send the service request to the producer Network Function (NF),
20 such as, but not limited to, AMF [106], SMF [108], UDM [124] and the like. After sending the
service request to the producer NF, the transceiver unit [306] may receive a service response
comprising at least a response header and response data content from the producer NF, the
service response is received in response to the service request. After receiving the response
from the producer NF, the transceiver unit [306] may transmit at least the response header and
25 response data content to a consumer NF, such as, but not limited to, AMF [106], SMF [108],
UDM [124] and the like.
[0085] The system [300] comprises a processing unit [308]. The processing unit [308] is
configured to merge at least the request header and at least the response header into a service
30 request header, and the request data content and the response data content into a service data
content. The merging facilitates in consolidating the information from the service request and
the service response into a coherent format that can be used for further processing or
transmission. In an exemplary aspect, the processing unit [308] may communicatively attached
with the transceiver unit [306]. The processing unit [308] may process the received request
35 header and response header by the transceiver unit [306]. The processing unit [308] is further
configured to duplicate at least the response header and response data content into the cache
upon receipt of the service response from the producer NF.
21
5 [0086] In an exemplary aspect, in order to merge at least the request header and at least the
response header into the service request header, and the request data content and the response
data content into the service data content, the processing unit [308] is configured to convert
status pseudo-header from at least the response header to a response-status and convert method
pseudo-header from at least the request header to a request-method, to send the service request
10 header and the service data content to the alert server. When the service request comes, the
processing unit [308] may check pseudo path header (also known as Uniform Resource
Identifier (URI) in HTTP/1). If this path header matches, then the processing unit [308] may
combine request headers and response headers also request data and response data. The
processing unit [308] may send via the transceiver unit [306] this combined resultant as a new
15 request to a welcome server or an alert server. In an exemplary aspect, the method pseudoheader in HTTP/2 is part of the request headers and specifies the type of action (e.g., GET,
POST, PUT, DELETE, PATCH) to be performed as per the request. As defined herein, the
status pseudo headers in HTTP/2, is used to send key information about the message. Most
notably, several pseudo-headers effectively replace the HTTP/1 request line and status line.
20 Further defined herein, GET is for fetching data, appending parameters in the URL, ideal for
searches. Furthermore, PATCH is defined as a method that applies partial modifications to a
resource, making it a lightweight option to PUT. Both methods are equivalent, but
semantically, they are different. PUT inserts or updates a resource, while PATCH applies a
partial update to the resource. As defined herein, PUT is a technique of altering resources when
25 the client transmits data that revamps the whole resource. Furthermore, POST creates new
resources, and DELETE for deleting resources.
[0087] It would be appreciated by the person skilled in the art that by merging the request
and response components, the processing unit [308] facilitates efficient processing and
30 transmission to the alert server or other network components for maintaining the integrity and
continuity of service transactions within the system [300], enabling accurate and timely
delivery of services and notifications to the UE subscriber.
[0088] The transceiver unit [306] is further configured to send a service request header and
35 service data content to an alert server. In an exemplary aspect, the transceiver unit [306] is
configured to send, via the alert server, an alert notification to the UE subscriber in the network
based at least on the determination of a change in Public Land Mobile Network (PLMN) during
roaming. As used herein, Public Land Mobile Network (PLMN) is the term used to describe all
22
5 mobile wireless networks that use earth-based stations rather than satellites. PLMN is the
mobile equivalent of the Public Switched Telephone Network (PSTN). Such a system can stand
alone, but often it is interconnected with a fixed system such as the public switched telephone
network (PSTN). The alert notification is sent to the UE subscriber based at least on the service
request header and the service data content. In an exemplary aspect, the alert notification is in
10 Short Message Service (SMS) format. The Service Request Header and Data contains
essentials UE subscriber information which is required to send notification to that particular
user equipment (UE) [102].
[0089] Referring to FIG. 4, an exemplary method flow diagram [400] for sending an alert
15 notification to a user equipment (UE) subscriber in a network in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the method [400] is
performed by the system [300]. Further, in an implementation, the system [300] may be present
in a server device to implement the features of the present disclosure. Also, as shown in FIG.
4, the method [400] starts at step [402].
20
[0090] At step 404, the method [400] as disclosed by the present disclosure comprises
identifying, by an identification unit [302] of a service communication proxy (SCP), a service
request for a service for the UE subscriber. The method [400] implemented by the identification
unit [302] of the SCP of the system [300] may identify the service request for a service for the
25 UE subscriber. For example, the identification unit may analyse the metadata and request
header of each request to ascertain whether they pertain to services that the UE subscriber is
entitled to or has requested. In an exemplary aspect, the service request for the UE subscriber
may correspond to the request for preferred service such as voice service, data service, etc.
Herein, the service can be any type of service, such as a communication service (for e.g., a
30 notification service or a callback service), a context management (for e.g., user equipment
context management (UECM)) service, resource optimization service, network function
management, registration, and the like. In an example, the service request may comprise at
least one of service name, service context, nfType, and a response timeout.
35 [0091] The identification unit [302] is a part of service communication proxy (SCP) [110].
Service Communication Proxy (SCP) is a network function in the 5G core network that
facilitates communication between other network functions by providing a secure and efficient
messaging service. The SCP acts as a mediator for service-based interfaces. In an exemplary
23
5 aspect, the service request is identified based at least on a predefined version of Hypertext
Transfer Protocol (HTTP) pseudo-header. The identification unit [302] may identify the
predefined version of Hypertext Transfer Protocol (HTTP) pseudo-header. The predefined
version of HTTP pseudo-header includes, such as, but are not limited, to HTTP/1, HTTP/2,
and HTTP/3. As used herein, the Hypertext Transfer Protocol (HTTP) is the foundation of the
10 World Wide Web (WWW) and is used to load webpages using hypertext links.
[0092] Next, at step 406, the method [400] as disclosed by the present disclosure comprises
cloning, by a cloning unit [304] of the SCP, at least a request header and request data content
into a cache. In an exemplary aspect, the cloning unit [304] may communicatively attached
15 with the identification unit [302]. For example, if a service request involves streaming a video,
the request header might include details such as the type of request (e.g., GET or POST), the
URL of the video resource, and other control information like content type and encoding. The
request data content would include any parameters or data necessary for the video streaming
service to process the request. The cloning unit [304] duplicates both these parts and stores
20 them securely in the cache.
[0093] The caches are used to store temporary files, using hardware and software
components. An example of a hardware cache is a CPU cache that is used to store basic
instructions that are recently used or are frequently used.
25
[0094] In an exemplary aspect, the cloning unit [304] may communicatively attached with
the identification unit [302]. The cloning unit [304] is further configured to perform cloning of
at least the request header and the request data into the cache upon successful comparison and
matching of a value of a path defined in the predefined version of HTTP pseudo header with
30 at least name of the service in the service request. In case the path value defined in the
predefined version of HTTP pseudo header matches the desired service name, request header
and request data, content is copied in the cache. In case path value does not matches then
normal flow happens and no notification is sent to message copy server. Then, the request is
forwarded to a transceiver unit [306] for further processing.
35
[0095] Next, at step 408, the method [400] as disclosed by the present disclosure comprises
sending, by a transceiver unit [306] of the SCP, the service request to a producer Network
Function (NF). Once the cloning unit [304] has duplicated the request header and request data
24
5 content into the cache, the transceiver unit [306] sends the service request to the producer NF.
For example, a UE subscriber initiating a cloud storage operation, such as uploading a file. The
transceiver unit [306] would send the service request, containing details like the file path and
user credentials, to the cloud storage server (the producer NF). After receiving the request from
the cloning unit [304], the transceiver unit [306] may send the service request to the producer
10 Network Function (NF), such as, but not limited to, AMF [106], SMF [108], UDM [124] and
the like.
[0096] Next, at step 410, the method [400] as disclosed by the present disclosure comprises
receiving, by the transceiver unit [306] of the SCP, a service response comprising at least a
15 response header and response data content from the producer NF, the service response is
received in response to the service request. After the transceiver unit [306] sends the service
request to the producer Network Function (NF), it receives the response generated by the
producer NF. For example, in a cloud storage operation where a UE subscriber requests to
upload a file, the service response received by the transceiver unit [306] would include a header
20 with status information about the upload request (e.g., success or failure, storage location
details) and the response data content might include metadata about the uploaded file such as
file ID, storage path, and access permissions.
[0097] Next, at step 412, the method [400] as disclosed by the present disclosure comprises
25 transmitting, by the transceiver unit [306] of the SCP, at least the response header and response
data content to a consumer NF. After receiving the service response from the producer NF, the
transceiver unit [306] transmits to the consumer NF, which is responsible for utilizing the
response data to deliver the requested service to the UE subscriber. For instance, in a cloud
storage service, after a file upload request, the transceiver unit [306] transmits the upload
30 confirmation response, including headers and metadata about the uploaded file (e.g., file ID,
storage path), to the consumer NF that manages the user’s cloud storage account, ensuring that
the user can access and verify the uploaded file.
[0098] Next, at step 414, the method [400] as disclosed by the present disclosure comprises
35 merging, by a processing unit [308] of the SCP, at least the request header and at least the
response header into a service request header, and the request data content and the response
data content into a service data content. In an exemplary aspect, the processing unit [308] may
communicatively attached with the transceiver unit [306]. The processing unit [308] may
25
5 process the received request header and response header by the transceiver unit [306]. The
processing unit [308] is further configured to duplicate at least the response header and
response data content into the cache upon receipt of the service response from the producer
NF.
10 [0099] In an exemplary aspect, in order to merge at least the request header and at least the
response header into the service request header, and the request data content and the response
data content into the service data content, the processing unit [308] is configured to convert
status pseudo-header from at least the response header to a response-status and convert method
pseudo-header from at least the request header to a request-method, to send the service request
15 header and the service data content to the alert server. When the service request comes, the
processing unit [308] may check pseudo path header (also known as Uniform Resource
Identifier (URI) in HTTP/1). If this path header matches, then the processing unit [308] may
combine request headers and response headers also request data and response data. The
processing unit [308] may send via the transceiver unit [306] this combine resultant as a new
20 request to a welcome server (not shown). In an exemplary aspect, the method pseudo-header
in HTTP/2 is part of the request headers and specifies the type of action (e.g., GET, POST,
PUT, DELETE, PATCH) to be performed as per the request. As defined herein, the status
pseudo headers in HTTP/2, is used to send key information about the message. Most notably,
several pseudo-headers effectively replace the HTTP/1 request line and status line. Further
25 defined herein, GET is for fetching data, appending parameters in the URL, ideal for
searches. Furthermore, PATCH is defined as a method that applies partial modifications to a
resource, making it a lightweight option to PUT. Both methods are equivalent, but
semantically, they are different. PUT inserts or updates a resource, while PATCH applies a
partial update to the resource. As defined herein, PUT is a technique of altering resources when
30 the client transmits data that revamps the whole resource. Furthermore, POST creates new
resources, and DELETE for deleting resources.
[0100] In an exemplary aspect, merging at least the request header and at least the response
header into the service request header, and the request data content and the response data
35 content into the service data content comprises converting, by the processing unit [308] of the
SCP, status pseudo-header from at least the response header to a response-status. Furthermore,
converting, by the processing unit [308] of the SCP, method pseudo-header from at least the
26
5 request header to a request-method, to send the service request header and the service data
content to the alert server.
[0101] It would be appreciated by the person skilled in the art that by merging the request
and response components, the processing unit [308] facilitates efficient processing and
10 transmission to the alert server or other network components for maintaining the integrity and
continuity of service transactions within the system [300], enabling accurate and timely
delivery of services and notifications to the UE subscriber.
[0102] At step 416, the method [400] as disclosed by the present disclosure comprises
15 sending, by the transceiver unit [306] of the SCP, the service request header and the service
data content to an alert server. In an exemplary aspect, the transceiver unit [306] is configured
to send, via the alert server, an alert notification to the UE subscriber in the network based at
least on determination of a change in Public Land Mobile Network (PLMN) during roaming.
As used herein, Public Land Mobile Network (PLMN) is the term used to describe all mobile
20 wireless networks that use earth-based stations rather than satellites. PLMN is the mobile
equivalent of the Public Switched Telephone Network (PSTN). Such a system can stand alone,
but often it is interconnected with a fixed system such as the public switched telephone network
(PSTN). The alert notification is sent to the UE subscriber based at least on the service request
header and the service data content. In an exemplary aspect, the alert notification is in Short
25 Message Service (SMS) format. The Service Request Header and Data contains essentials UE
subscriber information which is required to send notification to that particular user equipment
(UE) [102].
[0103] Thereafter, the method [400] terminates at step [418].
30
[0104] Referring to FIG. 5, an exemplary block diagram of a system architecture for sending
an alert notification to a user equipment (UE) subscriber in a network, is shown. As shown in
FIG. 5, the system [500] comprises at least one NF Consumer [502], at least one SCP [110], at
least one NF Producer [506], at least one Welcome Server [508], at least one 5G/IMS node
35 [510] and at least one user equipment (UE) [102].
27
5 [0105] The system [500] is configured to send an alert message or SMS to the UE [102],
when the UE [102] changes a PLMN. In order to sending an alert to the UE [102] after PLMN
change, the welcome server [508] may send an alert SMS to the UE [102].
[0106] The SCP [110] of the system [500] is configured to identify appropriate service
10 request through HTTP2 path pseudo header. In case path pseudo header value matches the
desired service name, the request header and request data content is copied in the cache. Then,
the SCP [110] forwards the request to NF producer [506]. Further, the SCP [110] may wait for
the response from the NF Producer [506]. On receipt of response from the NF Producer [506],
response headers and data content is copied in cache. Then, the SCP [110] forwards the
15 response to NF Consumer [502]. Furthermore, the SCP [110] merges the request headers and
response headers as well as request Data and response data content in single request header and
single request data and sends to the welcome server [508].
[0107] Therefore, the system [500] enables sending welcome SMS via welcome server [508]
20 to the UE [102], when UE [102] changes PLMN in roaming case in 5G/IMS network [510].
Here the SMS is sent to notify the UE [102] or user, when it sends registration request to PLMN
which is different from previous registrations in legacy networks.
[0108] The present disclosure further discloses a user equipment (UE), comprising a
25 processor configured to receive, via an alert server, an alert notification based on the service
request, wherein the alert notification is generated based on an identification of a service
request for a service for the UE subscriber.
[0109] The present disclosure further discloses a non-transitory computer readable storage
30 medium storing instructions for sending an alert notification to a user equipment (UE)
subscriber in a network the instructions include executable code which, when executed by a
one or more units of a system, causes: an identification unit [302] to identify a service request
for a service for the UE subscriber; a cloning unit [304] to clone at least a request header and
request data content into a cache; a transceiver unit [304] to send the service request to a
35 producer Network Function (NF); to receive a service response comprising at least a response
header and response data content from the producer NF, the service response is received in
response to the service request; to transmit at least the response header and response data
content to a consumer NF; a processing unit [308] to merge at least the request header and at
28
5 least the response header into a service request header, and the request data content and the
response data content into a service data content; and the transceiver unit [306] to send the
service request header and the service data content to an alert server.
[0110] As is evident from the above, the present disclosure provides a technically advanced
10 solution for sending a SMS alert to user equipment subscriber after user PLMN change. The
present disclosure alerts the UE subscriber when there is any change in user PLMN. Also, the
present disclosure tracks the user location and timely updates the UE subscriber if there is any
change in user PLMN. Further, the present disclosure also updates the user regarding
thunderstorm updates.
15
[0111] Further, in accordance with the present disclosure, it is to be acknowledged that the
functionality described for the various the components/units can be implemented
interchangeably. While specific embodiments may disclose a particular functionality of these
units for clarity, it is recognized that various configurations and combinations thereof are
20 within the scope of the disclosure. The functionality of specific units as disclosed in the
disclosure should not be construed as limiting the scope of the present disclosure.
Consequently, alternative arrangements and substitutions of units, provided they achieve the
intended functionality described herein, are considered to be encompassed within the scope of
the present disclosure.
25
[0112] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many
changes can be made to the implementations without departing from the principles of the
present disclosure. These and other changes in the implementations of the present disclosure
30 will be apparent to those skilled in the art, whereby it is to be understood that the foregoing
descriptive matter to be implemented is illustrative and non-limiting.
29
We Claim:
1. A method for sending an alert notification to a user equipment (UE) subscriber in a
network, comprising:
identifying, by an identification unit [302] of a service communication proxy
(SCP), a service request for a service for the UE subscriber;
cloning, by a cloning unit [304] of a SCP, at least a request header and request
data content into a cache;
sending, by a transceiver unit [306] of the SCP, the service request to a producer
Network Function (NF);
receiving, by the transceiver unit [306] of the SCP, a service response
comprising at least a response header and response data content from the producer
NF, the service response is received in response to the service request;
transmitting, by the transceiver unit [306] of the SCP, at least the response
header and response data content to a consumer NF;
merging, by a processing unit [308] of the SCP, at least the request header and
at least the response header into a service request header, and the request data
content and the response data content into a service data content; and
sending, by the transceiver unit [306] of the SCP, the service request header and
the service data content to an alert server.
2. The method as claimed in claim 1, wherein the service request is identified based at
least on a predefined version of Hypertext Transfer Protocol (HTTP) pseudo-header.
3. The method as claimed in claim 2, wherein the cloning of at least the request header
and the request data is done into the cache upon successful comparison and matching
of a value of a path defined in the predefined version of HTTP pseudo header with at
least name of the service in the service request.
4. The method as claimed in claim 1, further comprises duplicating, by the processing unit
[308] of the SCP, at least the response header and response data content into the cache
upon receipt of the service response from the producer NF.
30
5. The method as claimed in claim 1, further comprising sending, by the transceiver unit
[306] of the SCP via the alert server, an alert notification to the UE subscriber in the
network based at least on determination of a change in Public Land Mobile Network
(PLMN) during roaming.
6. The method as claimed in claim 1, wherein the alert notification is sent to the UE
subscriber based at least on the service request header and the service data content.
7. The method as claimed in claim 1, wherein the alert notification is in Short Message
Service (SMS) format.
8. The method as claimed in claim 2, wherein merging at least the request header and at
least the response header into the service request header, and the request data content
and the response data content into the service data content comprises:
converting, by the processing unit [308] of the SCP, status pseudo-header from
at least the response header to a response-status; and
converting, by the processing unit [308] of the SCP, method pseudo-header from
at least the request header to a request-method, to send the service request header and
the service data content to the alert server.
9. A system for sending an alert notification to a user equipment (UE) subscriber in a
network, comprising:
an identification unit [302], configured to identify a service request for a service for
the UE subscriber;
a cloning unit [304], configured to clone at least a request header and request data
content into a cache;
a transceiver unit [306], configured to:
send the service request to a producer Network Function (NF);
receive a service response comprising at least a response header and response
data content from the producer NF, the service response is received in response to
the service request;
transmit at least the response header and response data content to a consumer
NF;
31
a processing unit [308], configured to merge at least the request header and at
least the response header into a service request header, and the request data content
and the response data content into a service data content; and
the transceiver unit [306], configured to send the service request header and the
service data content to an alert server.
10. The system as claimed in claim 9, wherein the service request is identified based at least
on a predefined version of Hypertext Transfer Protocol (HTTP) pseudo-header.
11. The system as claimed in claim 10, wherein the cloning unit [304] is configured to
perform cloning of at least the request header and the request data into the cache upon
successful comparison and matching of a value of a path defined in the predefined
version of HTTP pseudo header with at least name of the service in the service request.
12. The system as claimed in claim 9, wherein the processing unit [308] is further
configured to duplicate at least the response header and response data content into the
cache upon receipt of the service response from the producer NF.
13. The system as claimed in claim 9, wherein the transceiver unit [306] is configured to
send, via the alert server, an alert notification to the UE subscriber in the network based
at least on determination of a change in Public Land Mobile Network (PLMN) during
roaming .
14. The system as claimed in claim 9, wherein the alert notification is sent to the UE
subscriber based at least on the service request header and the service data content.
15. The system as claimed in claim 9, wherein the alert notification is in Short Message
Service (SMS) format.
16. The system as claimed in claim 10, wherein to merge at least the request header and at
least the response header into the service request header, and the request data content
and the response data content into the service data content, the processing unit [308] is
configured to:
32
convert status pseudo-header from at least the response header to a responsestatus; and
convert method pseudo-header from at least the request header to a requestmethod, to send the service request header and the service data content to the alert
server.
17. A user equipment (UE) [102], comprising:
a processor configured to:
receive, via an alert server, an alert notification based on a service request,
wherein the alert notification is generated based on an identification of a service
request for a service for a UE subscriber.
18. The UE as claimed in claim 17, wherein the alert notification is generated based on the
method steps performed in method claim 1.

Documents

Application Documents

# Name Date
1 202321044636-STATEMENT OF UNDERTAKING (FORM 3) [04-07-2023(online)].pdf 2023-07-04
2 202321044636-PROVISIONAL SPECIFICATION [04-07-2023(online)].pdf 2023-07-04
3 202321044636-FORM 1 [04-07-2023(online)].pdf 2023-07-04
4 202321044636-FIGURE OF ABSTRACT [04-07-2023(online)].pdf 2023-07-04
5 202321044636-DRAWINGS [04-07-2023(online)].pdf 2023-07-04
6 202321044636-FORM-26 [06-09-2023(online)].pdf 2023-09-06
7 202321044636-Proof of Right [17-10-2023(online)].pdf 2023-10-17
8 202321044636-ORIGINAL UR 6(1A) FORM 1 & 26)-301123.pdf 2023-12-07
9 202321044636-ENDORSEMENT BY INVENTORS [12-06-2024(online)].pdf 2024-06-12
10 202321044636-DRAWING [12-06-2024(online)].pdf 2024-06-12
11 202321044636-CORRESPONDENCE-OTHERS [12-06-2024(online)].pdf 2024-06-12
12 202321044636-COMPLETE SPECIFICATION [12-06-2024(online)].pdf 2024-06-12
13 Abstract1.jpg 2024-07-12
14 202321044636-FORM 3 [31-07-2024(online)].pdf 2024-07-31
15 202321044636-Request Letter-Correspondence [13-08-2024(online)].pdf 2024-08-13
16 202321044636-Power of Attorney [13-08-2024(online)].pdf 2024-08-13
17 202321044636-Form 1 (Submitted on date of filing) [13-08-2024(online)].pdf 2024-08-13
18 202321044636-Covering Letter [13-08-2024(online)].pdf 2024-08-13
19 202321044636-CERTIFIED COPIES TRANSMISSION TO IB [13-08-2024(online)].pdf 2024-08-13
20 202321044636-FORM-9 [19-11-2024(online)].pdf 2024-11-19
21 202321044636-FORM 18A [19-11-2024(online)].pdf 2024-11-19
22 202321044636-FER.pdf 2025-05-19
23 202321044636-FORM 3 [03-08-2025(online)].pdf 2025-08-03
24 202321044636-FER_SER_REPLY [06-08-2025(online)].pdf 2025-08-06
25 202321044636-US(14)-HearingNotice-(HearingDate-28-10-2025).pdf 2025-10-08
26 202321044636-FORM-26 [17-10-2025(online)].pdf 2025-10-17
27 202321044636-Correspondence to notify the Controller [17-10-2025(online)].pdf 2025-10-17
28 202321044636-Written submissions and relevant documents [10-11-2025(online)].pdf 2025-11-10

Search Strategy

1 202321044636_SearchStrategyNew_E_searchstrategyE_19-05-2025.pdf