FORM 2
THE PATENTS ACT, 1970 (39 of 1970) THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
SYSTEM AND METHOD FOR MANAGING MOBILE ORIGINATED MESSAGE IN NETWORK
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad -
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION OF RIGHTS
[001] A portion of the disclosure of this patent document contains material,
which is subject to intellectual property rights such as, but are not limited to,
copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade
5 dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates
(hereinafter referred as owner). The owner has no objection to the facsimile
reproduction by anyone of the patent document or the patent disclosure, as it
appears in the Patent and Trademark Office patent files or records, but otherwise
reserves all rights whatsoever. All rights to such intellectual property are fully
10 reserved by the owner.
FIELD OF INVENTION
[002] Embodiments of the present disclosure generally relate to wireless
communications technology. In particular, the present disclosure relates to a system
15 and a method for managing data transfer in a network to minimise failure during
transfer of data in the network.
BACKGROUND OF INVENTION
[003] The following description of related art may be intended to provide
20 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 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.
25 [004] In some cases, a cellular Internet of Things (CIoT) is a scenario
where a large number of devices may be served by a wireless network. The devices may range from stationary devices deep in basements to devices that have limited mobility speed. The devices may send and/or receive infrequent, small amounts of data. Examples of CIoT devices may include smart utility meters such as gas, water,
30 or electric meters that may autonomously report utility usage to the utility provider
via the wireless network. Another example of CIoT devices may include
2

environmental monitoring sensors that may be placed randomly in a geographical area to monitor air or water quality.
[005] In some cases, mobile originated (MO) short message service (SMS)
may be used for a device to send and/or receive a short message up to 140
5 bytes/octets in length. The infrequent and small amount of CIoT data may be
included in the short message and delivered to the network by SMS.
[006] The MO messages are generally exchanged based on 3GPP
protocols. 3GPP standards evolve with time and cover aspects of integration and features that a node of the network (such as 4G or 5G) supports.
10 [007] However, lack of explicit description of interaction between 4G
nodes like Service Capability Exposure Function (SCEF) and Network Exposure Function (NEF) may lead to designing flaws. While the 3GPP may indicate sparsely about interactions between Application Function (AF), NEF, and SCEF through the Common Application Programming Interface (API) Framework (CAPIF), the
15 description lacks how CAPIF selects between NEF and SCEF. Moreover, AF needs
to support N33 and T8 APIs.
[008] There is, therefore, a requirement in the art for a means to address
the issue of mitigating the complexity of transfer of data elements between network elements.
20 DEFINITION
[009] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context
in which they are used to indicate otherwise.
[0010] The term SMF as used herein, refers to a Session Management
25 Function. The SMF is responsible for establishing, maintaining, and terminating
user sessions in the 5G core network. The SMF is a functional module that is responsible for interacting with decoupled data plane, creating, updating, and removing Protocol Data Unit (PDU) sessions and managing session context with a User Plane Function (UPF).
30 [0011] The term AF as used herein, refers Application Function. The AF is
a control plane function within 5G core network, provides application services to
3

the subscriber. For example, it can be for video streaming service. If an AF is trusted, it may interact directly with 5GC network functions or if it is third party, then it may interact with an NEF.
[0012] The term NEF as used herein, refers to a Network Exposure
5 Function. The NEF is among the fundamental capabilities natively built-in in the
5G network. It allows carriers to securely handle valuable data coming from Application Functions (AF) and enables optimal allocation and utilization of resources. The NEF provides signaling scenarios to allow a controlled and secure way of exchanging information to and from an external application. The NEF
10 facilitates secure, robust, developer-friendly access to the exposed network services
and capabilities of 5G network, enabling third-party developers and enterprises to
create and tailor composite or specialized network services on-demand.
[0013] The term SCEF as used herein, refers to a Service Capability
Exposure Function. The SCEF is a new network element that securely exposes the
15 servers and capabilities provided by 3GPP network interfaces. Some functions
included with SCEF include non-IP data delivery (NIDD) for low power devices.
[0014] The term MME as used herein, refers to Mobile Management Entity.
The MME is a functional module which presents a key control node for the Long-Term Evolution (LTE) access network, manages UE access network and mobility,
20 as well as establishes the bearer path for UEs. The MME may also be concerned
with the bearer activation/deactivation process. In addition, the MME may be responsible for selecting the Serving-Gateway (S-GW) for a UE at the initial join and at time of intra-LTE handover. The MME is in charge of authenticating the user as well as the generation and allocation of temporary identities to UEs.
25 [0015] The term AMF as used herein, refers to an Access and Mobility
Management Function. The AMF may refer a functional module which terminates the control plane of different access networks onto the 5G Core Network (5GC) and control which user equipments (UEs) can access the 5GC to exchange traffic with Data Networks (DNs).
30
4

OBJECTS OF THE DISCLOSURE
[0016] An object of the present disclosure is to provide a technique to
manage mobile originated (MO) messages in any of 4G or 5G networks.
[0017] Another object of the present disclosure is to reduce complexity of
5 transfer of data between various network elements in a network.
[0018] Another object of the present disclosure is to provide an interface
between NEF and SCEF.
[0019] Another object of the present disclosure is to save session
management (SM)-context in a database to be used.
10 [0020] Another object of the present disclosure is to enhance the nodes in
communication.
[0021] Yet another object of the present disclosure is to improvise the
network capabilities.
15 SUMMARY
[0022] In an exemplary embodiment, the present invention discloses a
method for managing a mobile originated (MO) message for a user equipment (UE) moving between a first network and a second network. The method comprising determining if the UE is connected to the first network or to the second network.
20 When it is determined that the UE is connected to the first network, then the method
comprising sending, by the UE, an MO message to a session management function (SMF). The method comprising forwarding, by the SMF, the received MO message to a network exposure function (NEF). The method comprising forwarding, by the NEF, the MO message to an application function (AF). The method comprising
25 sending, by the AF, an acknowledgement signal to the NEF after receiving the MO
message. The method comprising forwarding, by the NEF, the acknowledgement signal to the UE via the SMF. When it is determined that the UE is attached to the second network, then the method comprising sending, by the UE, an MO message to a mobility management entity (MME). The method comprising forwarding, by
30 the MME the received MO message to a service capability exposure function
(SCEF). The method comprising forwarding, by the SCEF, the MO message to the
5

NEF. The method comprising forwarding, by the NEF, the MO message to an
application function (AF). The method comprising sending, by the AF, an
acknowledgement signal to the NEF after receiving the MO message. The method
comprising forwarding, by the NEF, the acknowledgement signal to the SCEF and
5 delivering, by the SCEF, the acknowledgement signal to the UE via the MME.
[0023] In some embodiments, the first network and the second network are
provided with a reliable data services (RDS) support indication.
[0024] In some embodiments, the UE sends the MO message to the SMF
after performing a successful attach procedure with the first network.
10 [0025] In some embodiments, the method further comprising creating, by
the SMF, a session management (SM) context on the NEF during the attach procedure.
[0026] In some embodiments, the method further comprising searching, by
the NEF, an endpoint of the AF for forwarding the MO message to the AF.
15 [0027] In some embodiments, the NEF checks the SM context and a Non-
Internet Protocol Data Delivery (NIDD) configuration mapping for searching the endpoint of the AF.
[0028] In some embodiments, the NIDD configuration includes an address
of the AF for each UE available in the first network and the second network.
20 [0029] In some embodiments, the NEF forwards the acknowledgement
signal to the UE via the SMF as per the SM context.
[0030] In some embodiments, the NEF forwards the acknowledgement
signal to the UE after determining that the UE indicated support for the RDS during the attach procedure.
25 [0031] In some embodiments, the method further comprising creating, by
the MME, a session management (SM) context on the SCEF during the attach procedure.
[0032] In some embodiments, the SCEF forwards the MO message to the
NEF through a predefined interface.
30 [0033] In some embodiments, the NEF forwards the acknowledgement
signal to the SCEF as per the SM context over the predefined interface.
6

[0034] In some embodiments, the SCEF delivers the acknowledgement
signal to the UE via the MME after determining that the UE indicated support for the RDS during the attach procedure.
[0035] In some embodiments, the first network is a 5G network and the
5 second network is a 4G network.
[0036] In an exemplary embodiment, the present invention discloses a
system for managing a mobile originated (MO) message for a user equipment (UE) moving between a first network and a second network. The system is configured to determine if the UE is connected to the first network or to the second network.
10 When it is determined that the UE is connected to the first network, then the system
is configured to send, by the UE, an MO message to a session management function (SMF). The system is configured to forward, by the SMF, the received MO message to a network exposure function (NEF). The system is configured to forward, by the NEF, the MO message to an application function (AF). The system is configured to
15 send, by the AF, an acknowledgement signal to the NEF after receiving the MO
message. The system is configured to forward, by the NEF, the acknowledgement signal to the UE via the SMF. When it is determined that the UE is attached to the second network, then the system is configured to send, by the UE, an MO message to a mobility management entity (MME). The system is configured to forward, by
20 the MME the received MO message to a service capability exposure function
(SCEF). The system is configured to forward, by the SCEF, the MO message to the NEF. The system is configured to forward, by the NEF, the MO message to an application function AF. The system is configured to send, by the AF, an acknowledgement signal to the NEF after receiving the MO message. The system
25 is configured to forward, by the NEF, the acknowledgement signal to the SCEF and
deliver, by the SCEF, the acknowledgement signal to the UE via the MME.
[0037] In some embodiments, the first network and the second network are
provided with a reliable data services (RDS) support indication.
[0038] In some embodiments, the UE sends the MO message to the SMF
30 after performing a successful attach procedure with the first network.
7

[0039] In some embodiments, the system is configured to create, by the
SMF, a session management (SM) context on the NEF during the attach procedure.
[0040] In some embodiments, the system is configured to search, by the
NEF, an endpoint of the AF for forwarding the MO message to the AF.
5 [0041] In some embodiments, the NEF checks the SM context and a Non-
Internet Protocol Data Delivery (NIDD) configuration mapping for searching the endpoint of the AF.
[0042] In some embodiments, the NIDD configuration includes an address
of the AF for each UE available in the first network and the second network.
10 [0043] In some embodiments, the NEF forwards the acknowledgement
signal to the UE via the SMF as per the SM context.
[0044] In some embodiments, the NEF forwards the acknowledgement
signal to the UE after determining that the UE indicated support for the RDS during the attach procedure.
15 [0045] In some embodiments, the system is configured to create, by the
MME, a session management (SM) context on the SCEF during the attach procedure.
[0046] In some embodiments, the SCEF forwards the MO message to the
NEF through a predefined interface.
20 [0047] In some embodiments, the NEF forwards the acknowledgement
signal to the SCEF as per the SM context over the predefined interface.
[0048] In some embodiments, the SCEF delivers the acknowledgement
signal to the UE via the MME after determining that the UE indicated support for the RDS during the attach procedure.
25 [0049] In some embodiments, the first network is a 5G network and the
second network is a 4G network.
[0050] In an exemplary embodiment, the present invention discloses a user
equipment (UE) moving between a first network and a second network. The first network and the second network comprising one or more network elements for
30 managing a mobile originated (MO) message for the UE. The one or more network
elements configured for determining if the UE is connected to the first network or
8

the second network. When it is determined that the UE is connected to the first
network, receiving, from the UE, an MO message by a session management
function (SMF). The one or more network elements configured for forwarding, by
the SMF, the received MO message to a network exposure function (NEF) and
5 forwarding, by the NEF, the MO message to an application function (AF). The one
or more network elements configured for sending, by the AF, an acknowledgement signal to the NEF after receiving the MO message and forwarding, by the NEF, the acknowledgement signal to the UE via the SMF. When it is determined that the UE is attached to the second network, receiving, from the UE, an MO message by a
10 mobility management entity (MME). The one or more network elements configured
for forwarding, by the MME, the received MO message to a service capability exposure function (SCEF). The one or more network elements configured for forwarding, by the SCEF, the MO message to the NEF, and forwarding, by the NEF, the MO message to an application function AF. The one or more network
15 elements configured for sending, by the AF, an acknowledgement signal to the NEF
after receiving the MO message, forwarding, by the NEF, the acknowledgement
signal to the SCEF and delivering, by the SCEF, the acknowledgement signal to the
UE via the MME.
[0051] The foregoing general description of the illustrative embodiments
20 and the following detailed description thereof are merely exemplary aspects of the
teachings of this disclosure and are not restrictive.
BRIEF DESCRIPTION OF THE DRAWINGS
[0052] The accompanying drawings, which are incorporated herein, and
25 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. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components
30 using block diagrams and may not represent the internal circuitry of each
component. It will be appreciated by those skilled in the art that disclosure of such
9

drawings includes the disclosure of electrical components, electronic components
or circuitry commonly used to implement such components.
[0053] FIG. 1A illustrates an exemplary system architecture (100A) for
implementing a proposed system, in accordance with an embodiment of the present
5 disclosure.
[0054] FIG. 1B illustrates an exemplary sequence diagram (100B)
representing different call flows in a network, in accordance with an embodiment
of the present disclosure.
[0055] FIG. 2 illustrates an exemplary computer system in which or with
10 which the proposed system for the sequence drawing may be implemented, in
accordance with an embodiment of the present disclosure.
[0056] FIG. 3 illustrates an exemplary flow diagram (300) for a method for
managing a mobile originated (MO) message for a user equipment (UE) moving
between a first network and a second network, in accordance with an embodiment
15 of the present disclosure.
[0057] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
20 100A- System architecture
102- User equipment (UE)
104- Session management function (SMF)
106- Network exposure function (NEF)
108- Service capability exposure function (SCEF)
25 110- Mobility management entity (MME)
112- Application function (AF)
114-1, 114-2 – Internet of things (IoT) device
116- System
10

118 - Receiving unit
120 - Processing unit
122 - Database
124 - Interfacing unit
5 100B – Flow Diagram
200 - A computer system 210 - External storage device 220 - Bus
230 - Main memory
10 240 - Read only memory
250 - Mass storage device 260 - Communication port(s) 270 – Processor
300- Flow Diagram
15 DETAILED DESCRIPTION
[0058] 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 disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific
20 details. Several features described hereafter can each be used independently of one
another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
25 [0059] The ensuing description provides exemplary embodiments only, and
is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those
11

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.
5 [0060] 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, networks, processes, and other components may be shown as components in block diagram form in order not to
10 obscure the embodiments in unnecessary detail. In other instances, well-known
circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0061] 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
15 structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a
20 procedure, a subroutine, a subprogram, etc. When a process corresponds to a
function, its termination can correspond to a return of the function to the calling function or the main function.
[0062] The word “exemplary” and/or “demonstrative” is used herein to
mean serving as an example, instance, or illustration. For the avoidance of doubt,
25 the subject matter disclosed 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
30 “includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner
12

similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0063] Reference throughout this specification to “one embodiment” or “an
embodiment” or “an instance” or “one instance” means that a particular feature,
5 structure, or characteristic described in connection with the embodiment is included
in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined
10 in any suitable manner in one or more embodiments.
[0064] The terminology used herein is for the purpose of describing
particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further
15 understood that the terms “comprises” and/or “comprising,” when used in this
specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations
20 of one or more of the associated listed items.
[0065] Certain terms and phrases have been used throughout the disclosure
and will have the following meanings in the context of the ongoing disclosure.
[0066] The term “3GPP” is a 3rd Generation Partnership Project or 3GPP
and is a collaborative project between a group of telecommunications associations
25 with the initial goal of developing globally applicable specifications for Third
Generation (3G) mobile systems. 3GPP specifications cover cellular telecommunications technologies, including radio access, core network, and service capabilities, which provide a complete system description for mobile telecommunications. The 3GPP specifications also provide hooks for non-radio
30 access to the core network, and for networking with non-3GPP networks.
13

[0067] Various embodiments of the present disclosure will be explained
with reference to FIGs. 1A, 1B and 2.
[0068] FIG. 1A illustrates an exemplary network architecture (100A) for
implementing a proposed system, in accordance with an embodiment of the present
5 disclosure.
[0069] In an aspect, the network architecture (100A) includes a user
equipment (UE) (102) connected to the network (a first network or a second network). The network may be a 4G network or a 5G network. The UE (102) initiates at least one request message towards the network and receives at least one
10 response message from the network. The network may include a plurality of
network elements. For example, the network may include SMF (104), NEF (106), SCEF (108), MME (110), and AF (112). The network may be further connected to a plurality of Internet of Things (IoT) devices such as IoT device-1 (114-1) and IoT device-2 (114-2). The UE (102) may communicate with a system (116), through a
15 network. The network enables the UE (102) to communicate with other devices in
the network architecture (100A) and/or with the system (116). The network may include a wireless card or some other transceiver connection to facilitate this communication. The system (116) includes a receiving unit (118), a processing unit (120), a database (122), and an interfacing unit (124). The receiving unit (118) is
20 configured to receive a connection request from the UE (102). The receiving unit
(118) is configured to communicate an acknowledgment of the connection request
to the UE (102) and is further configured to transmit a plurality of signals to one or
more network elements in response to the connection.
[0070] The processing unit (120) is coupled to the receiving unit (118). The
25 processing unit (120) may be implemented as one or more microprocessors,
microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the processing unit (120) may be configured to fetch and execute computer-readable instructions stored in a memory of the
30 system (116). The memory may be configured to store one or more computer-
readable instructions or routines in a non-transitory computer readable storage
14

medium, which may be fetched and executed to create or share data packets over a
network service. The memory may comprise any non-transitory storage device
including, for example, volatile memory such as random-access memory (RAM),
or non-volatile memory such as erasable programmable read-only memory
5 (EPROM), flash memory, and the like. The database (122) may store information
such as MO data, NIDD configurations, and the like.
[0071] In an embodiment, the interfacing unit (124) may comprise a variety
of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interfacing unit (124) may facilitate communication
10 through the system (116). The interfacing unit (124) may also provide a
communication pathway for one or more components of the system (116).
[0072] In an embodiment, the user device (UE) (102) may include, but not
be limited to, a mobile, a laptop, etc. Further, the user device (102) may include one or more in-built or externally coupled accessories including, but not limited to, a
15 visual aid device such as a camera, audio aid, microphone, or keyboard.
Furthermore, the user device (102) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, and a mainframe computer. Additionally, input devices for receiving input from the user
20 (102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be
used. In an embodiment, the network may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or
25 current levels, some combination thereof, or so forth. The network may also
include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable
30 network, a cellular network, a satellite network, a fiber optic network, or some
combination thereof.
15

[0073] FIG. 1B illustrates an exemplary sequence diagram (100B)
representing different call flows in a network, in accordance with an embodiment
of the present disclosure. Specifically, the sequence diagram (100B) represents a
management of mobile originated (MO) messages in a network.
5 [0074] A UE (102) is configured in the 5G network and is provided with
reliable data services (RDS) support indication. The reliable data services in a
telecommunication network refer to the ability of the network to consistently
deliver high-quality, low-latency, and uninterrupted data connectivity to the users.
[0075] At step 1, the UE (102) may send an MO data (message) to a SMF
10 (104) on successful attachment with the 5G network.
[0076] At step 2, the SMF (104) may receive the MO data from the UE
(102), and subsequently, forward the MO data towards an NEF (106) on which the SMF (104) created a session management (SM)-context during the attachment procedure. The SM context is created by SMF, or in V-SMF in home routed (HR)
15 roaming scenarios, for a Packet Data Unit (PDU) session. The SMF (104) may send
a Non-Internet Protocol (IP) Data Delivery (NIDD) data request to the NEF. The NIDD refers to a communication mechanism used in cellular networks to transmit non-IP (Internet Protocol) data. In traditional cellular networks, IP is the primary protocol used for data communication. However, there are cases where non-IP data
20 needs to be transmitted efficiently and securely, such as for specialized applications
or services. The NIDD provides an alternative method for delivering non-IP data over cellular networks. It allows the transmission of data using protocols other than IP, enabling efficient delivery of non-IP traffic. Further, The NEF (106) may be further configured to check the SM-context to Non-Internet Protocol (IP) Data
25 Delivery (NIDD) configuration mapping to search for an AF (112) endpoint.
[0077] At step 3, once the AF endpoint may be determined, the NEF (106)
may be configured to forward the MO message to the AF (112).
[0078] At step 4, the AF (112) may be further adapted to acknowledge
receipt of the MO message (MO delivery response). The NEF (106) may
30 subsequently receive the acknowledgement from the AF (112).
16

[0079] At step 5, the NEF (106) forwards the acknowledgement to the SMF
(104). The SMF (104) further forwards the acknowledgement to the UE (102) using the SM-context if the UE (102) may have indicated support for RDS.
[0080] At step 6, the SMF (104) sends a MO delivery response to the UE
5 (102) in case of RDS. In an aspect, the SMF (104) sends a RDS based response to
the UE (102). In some embodiments, the UE (102) may be configured in a 4G network and may be provided with RDS support.
[0081] At step 7, the UE (102) may send the MO data towards an MME
(110).
10 [0082] At step 8, the MME (110) may send a NIDD MO data request
towards the SCEF (108).
[0083] At step 9, the SCEF (108) may redirect the received NIDD MO data
request to the NEF (106).
[0084] In an embodiment the MME (110) may be configured to forward
15 the MO data (message) to an SCEF (108) instance on which it may have created the
SM-context during the attachment procedure. Further, the SCEF (108) may be configured to forward the MO message to the NEF (106) over an interface, while delivering the MO message to the AF (112). The NEF (106) may be further configured to check the SM-context to NIDD configuration mapping to search for
20 an AF (112) endpoint.
[0085] At step 10, once the AF (112) endpoint may be determined, the NEF
(106) may be configured to forward the MO message to the AF (112).
[0086] At step 11, the AF (112) may be further adapted to acknowledge
receipt of the MO message and forwards a MO delivery response towards the NEF.
25 The NEF (106) may subsequently receive the MO delivery response
(acknowledgement) from the AF (112).
[0087] At step 12, the NEF (106) may forward the MO delivery response
(acknowledgement) to the SCEF (108) over the predefined interface using the SM-context.
30 [0088] At step 13, the MO delivery response (acknowledgment) may be sent
from the SCEF (108) towards the MME (110). The MME (110) may further deliver
17

the MO delivery response (acknowledgement) to the UE (102)) if the UE (102) may have indicated support for RDS.
[0089] The NEF (106) may be configured to check SM-context to NIDD
configuration mapping and redirect NIDD MO data to the NEF (106). When the
5 UE (102) is attached to 5G, the SM-context may be created on the NEF (106) by
the SMF (104). Similarly, when the UE (102) is attached to 4G, the SM-context may be created by the MME (110) on the SCEF (108).
[0090] The SM-Context may be saved in a database. The NIDD
configuration may contain the address of the AF (112) for every UE (102). Thus,
10 whenever the NEF (106) may receive an MO message, it may check the destination
address of the AF (112), as per the NIDD configuration data and corresponding UE (102) network.
[0091] Further, whenever the SCEF (108) may receive the MO data, it may
not directly forward it to the AF (112); however, the MO message may be
15 forwarded to the NEF (106) over the predefined interface. Hence, data transfer
complexity is reduced for interworking scenarios.
[0092] In an aspect, the present system and method for managing mobile
originated (MO) message in a network is configured to be employed in a 5G telecommunication network. The present system and method provide management
20 of messages and communication between the network devices.
[0093] In an embodiment, the present disclosure provides a means to
manage mobile originated (MO) messages in any of 4G or 5G networks. The present disclosure provides a means to reduce complexity of transfer of data between various network elements in a network. The present disclosure provides a
25 means to save session management (SM)-context in a database to be used.
[0094] FIG. 2 illustrates an exemplary computer system (200) in which or
with which a proposed system for the sequence drawing (100B) may be
implemented, in accordance with an embodiment of the present disclosure.
[0095] As shown in FIG. 2, the computer system (200) may include an
30 external storage device (210), a bus (220), a main memory (230), a read-only
memory (240), a mass storage device (250), a communication port(s) (260), and a
18

processor (270). A person skilled in the art will appreciate that the computer system
(200) may include more than one processor and communication ports. The
processor (270) may include various modules associated with embodiments of the
present disclosure. The communication port(s) (260) may be any of an RS-232 port
5 for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit
or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (260) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (200) connects.
10 [0096] In an embodiment, the main memory (230) may be Random Access
Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (240) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input/output system (BIOS) instructions for the
15 processor (270). The mass storage device (250) may be any current or future mass
storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having
20 Universal Serial Bus (USB) and/or Firewire interfaces).
[0097] In an embodiment, the bus (220) may communicatively couple the
processor(s) (270) with the other memory, storage, and communication blocks. The bus (220) may be, e.g., a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus
25 (USB), or the like, for connecting expansion cards, drives, and other subsystems as
well as other buses, such a front side bus (FSB), which connects the processor (270) to the computer system (200).
[0098] In another embodiment, operator, and administrative interfaces, e.g.,
a display, keyboard, and cursor control device may also be coupled to the bus (220)
30 to support direct operator interaction with the computer system (200). Other
operator and administrative interfaces can be provided through network
19

connections connected through the communication port(s) (260). Components
described above are meant only to exemplify various possibilities. In no way should
the aforementioned exemplary computer system (200) limit the scope of the present
disclosure.
5 [0099] FIG. 3 illustrates an exemplary flow diagram (300) for a method for
managing a mobile originated (MO) message for a user equipment (UE) moving
between a first network and a second network. The method comprising the
following steps:
[00100] At 302, the method comprising determining if the UE is connected
10 to the first network or to the second network.
[00101] At 304, when it is determined that the UE is connected to the first
network, then performing the following steps:
[00102] At 306 the method comprising sending, by the UE, an MO message
to a session management function (SMF).
15 [00103] At 308, the method comprising forwarding, by the SMF, the received
MO message to a network exposure function (NEF).
[00104] At 310, the method comprising forwarding, by the NEF, the MO
message to an application function (AF).
[00105] At 312, the method comprising sending, by the AF, an
20 acknowledgement signal to the NEF after receiving the MO message.
[00106] At 314, the method comprising forwarding, by the NEF, the
acknowledgement signal to the UE via the SMF.
[00107] At 316, When it is determined that the UE is attached to the second
network, then the method comprising
25 [00108] At 318, the method comprising sending, by the UE, an MO message
to a mobility management entity (MME).
[00109] At 320, the method comprising forwarding, by the MME the
received MO message to a service capability exposure function (SCEF).
[00110] At 322, the method comprising forwarding, by the SCEF, the MO
30 message to the NEF.
20

[00111] At 324, the method comprising forwarding, by the NEF, the MO
message to an application function AF.
[00112] At 326, the method comprising sending, by the AF, an
acknowledgement signal to the NEF after receiving the MO message.
5 [00113] At 328, the method comprising forwarding, by the NEF, the
acknowledgement signal to the SCEF,
[00114] At 330, the method comprising delivering, by the SCEF, the
acknowledgement signal to the UE via the MME.
[00115] In some embodiments, the first network and the second network are
10 provided with a reliable data services (RDS) support indication.
[00116] In some embodiments, the UE sends the MO message to the SMF
after performing a successful attach procedure with the first network.
[00117] In some embodiments, the method further comprising creating, by
the SMF, a session management (SM) context on the NEF during the attach
15 procedure.
[00118] In some embodiments, the method further comprising searching, by
the NEF, an endpoint of the AF for forwarding the MO message to the AF.
[00119] In some embodiments, the NEF checks the SM context and a Non-
Internet Protocol Data Delivery (NIDD) configuration mapping for searching the
20 endpoint of the AF.
[00120] In some embodiments, the NIDD configuration includes an address
of the AF for each UE available in the first network and the second network.
[00121] In some embodiments, the NEF forwards the acknowledgement
signal to the UE via the SMF as per the SM context.
25 [00122] In some embodiments, the NEF forwards the acknowledgement
signal to the UE after determining that the UE indicated support for the RDS during the attach procedure.
[00123] In some embodiments, the method further comprising creating, by
the MME, a session management (SM) context on the SCEF during the attach
30 procedure.
21

[00124] In some embodiments, the SCEF forwards the MO message to the
NEF through a predefined interface.
[00125] In some embodiments, the NEF forwards the acknowledgement
signal to the SCEF as per the SM context over the predefined interface.
5 [00126] In some embodiments, the SCEF delivers the acknowledgement
signal to the UE via the MME after determining that the UE indicated support for the RDS during the attach procedure.
[00127] In some embodiments, the first network is a 5G network and the
second network is a 4G network.
10 [00128] In an exemplary embodiment, the present invention discloses a
system for managing a mobile originated (MO) message for a user equipment (UE) moving between a first network and a second network. The system is configured to determine if the UE is connected to the first network or to the second network. When it is determined that the UE is connected to the first network, then the system
15 is configured to send, by the UE, an MO message to a session management function
(SMF). The system is configured to forward, by the SMF, the received MO message to a network exposure function (NEF). The system is configured to forward, by the NEF, the MO message to an application function (AF). The system is configured to send, by the AF, an acknowledgement signal to the NEF after receiving the MO
20 message. The system is configured to forward, by the NEF, the acknowledgement
signal to the UE via the SMF. When it is determined that the UE is attached to the second network, then the system is configured to send, by the UE, an MO message to a mobility management entity (MME). The system is configured to forward, by the MME the received MO message to a service capability exposure function
25 (SCEF). The system is configured to forward, by the SCEF, the MO message to the
NEF. The system is configured to forward, by the NEF, the MO message to an application function AF. The system is configured to send, by the AF, an acknowledgement signal to the NEF after receiving the MO message. The system is configured to forward, by the NEF, the acknowledgement signal to the SCEF and
30 deliver, by the SCEF, the acknowledgement signal to the UE via the MME.
22

[00129] In an exemplary embodiment, the present invention discloses a user
equipment (UE) moving between a first network and a second network. The first
network and the second network comprising one or more network elements for
managing a mobile originated (MO) message for the UE. The one or more network
5 elements configured for determining if the UE is connected to the first network or
the second network. When it is determined that the UE is connected to the first network, receiving, from the UE, an MO message by a session management function (SMF). The one or more network elements configured for forwarding, by the SMF, the received MO message to a network exposure function (NEF) and
10 forwarding, by the NEF, the MO message to an application function (AF). The one
or more network elements configured for sending, by the AF, an acknowledgement signal to the NEF after receiving the MO message and forwarding, by the NEF, the acknowledgement signal to the UE via the SMF. When it is determined that the UE is attached to the second network, receiving, from the UE, an MO message by a
15 mobility management entity (MME). The one or more network elements configured
for forwarding, by the MME, the received MO message to a service capability exposure function (SCEF). The one or more network elements configured for forwarding, by the SCEF, the MO message to the NEF, and forwarding, by the NEF, the MO message to an application function AF. The one or more network
20 elements configured for sending, by the AF, an acknowledgement signal to the NEF
after receiving the MO message, forwarding, by the NEF, the acknowledgement
signal to the SCEF and delivering, by the SCEF, the acknowledgement signal to the
UE via the MME.
[00130] While considerable emphasis has been placed herein on the preferred
25 embodiments, it will be appreciated that many embodiments can be made and that
many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing
30 descriptive matter to be implemented merely as illustrative of the disclosure and not
as limitation.
23

ADVANTAGES OF THE DISCLOSURE
[00131] The present disclosure provides a means to manage mobile
originated (MO) messages in any of 4G or 5G networks.
5 [00132] The present disclosure provides a means to reduce complexity of
transfer of data between various network elements in a network.
[00133] The present disclosure provides an interface between Network
Exposure Function (NEF) and Service Capability Exposure Function (SCEF).
[00134] The present disclosure provides a means to save session
10 management (SM)-context in a database to be used.
[00135] The invention mitigates managing multiple protocols between
network elements.
[00136] The invention mitigates data transfer mechanisms between network
elements.
15 [00137] The invention mitigates data transfer mechanisms/ certificates/
security related protocols/ end point IP connection details and data connection
management between network elements.
24

WE CLAIM:
1. A method (300) for managing a mobile originated (MO) message for a user
equipment (UE) (102) moving between a first network and a second network, the
5 method (300) comprising:
determining (302) if the UE (102) is connected to the first network or to the second network;
when it is determined that the UE (102) is connected to the first
network, then performing (304) following steps:
10 sending (306), by the UE (102), an MO message to a session
management function (SMF) (104);
forwarding (308), by the SMF (104), the received MO message to a network exposure function (NEF) (106);
forwarding (310), by the NEF (106), the MO message to an
15 application function (AF) (112);
sending (312), by the AF (112), an acknowledgement signal to the NEF (106) after receiving the MO message;
forwarding (314), by the NEF (106), the acknowledgement
signal to the UE (102) via the SMF (104);
20 when it is determined that the UE (102) is attached to the second
network, then performing (316) following steps:
sending (318), by the UE (102), an MO message to a mobility management entity (MME) (110);
forwarding (320), by the MME (110), the received MO
25 message to a service capability exposure function (SCEF) (108);
forwarding (322), by the SCEF (108), the MO message to the NEF (106);
forwarding (324), by the NEF (106), the MO message to an application function AF (112);
25

sending (326), by the AF (112), an acknowledgement signal to the NEF (106) after receiving the MO message;
forwarding (328), by the NEF (106), the acknowledgement
signal to the SCEF (108); and
5 delivering (330), by the SCEF (108), the acknowledgement
signal to the UE (102) via the MME (110).
2. The method (300) as claimed in claim 1, wherein the first network and the second
network are provided with a reliable data services (RDS) support indication.
10
3. The method (300) as claimed in claim 1, wherein the UE (102) sends the MO
message to the SMF (104) after performing a successful attach procedure with the
first network.
15 4. The method (300) as claimed in claim 1, further comprising creating, by the SMF
(104), a session management (SM) context on the NEF (106) during the attach procedure.
5. The method (300) as claimed in claim 1, further comprising searching, by the
20 NEF (106), an endpoint of the AF (112) for forwarding the MO message to the AF
(112).
6. The method (300) as claimed in claim 5, wherein the NEF (106) checks the SM
context and a Non-Internet Protocol Data Delivery (NIDD) configuration mapping
25 for searching the endpoint of the AF (112).
7. The method (300) as claimed in claim 6, wherein the NIDD configuration
includes an address of the AF (112) for each UE (102) available in the first network
and the second network.
30
26

8. The method (300) as claimed in claim 1, wherein the NEF (106) forwards the
acknowledgement signal to the UE (102) via the SMF (104) as per the SM context.
9. The method (300) as claimed in claim 8, wherein the NEF (106) forwards the
5 acknowledgement signal to the UE (102) after determining that the UE (102)
indicated support for the RDS during the attach procedure.
10. The method (300) as claimed in claim 1, further comprising creating, by the
MME (110), a session management (SM) context on the SCEF (108) during the
10 attach procedure.
11. The method (300) as claimed in claim 1, wherein the SCEF (108) forwards the
MO message to the NEF (106) through a predefined interface.
15 12. The method (300) as claimed in claim 11, wherein the NEF (106) forwards the
acknowledgement signal to the SCEF (108) as per the SM context over the predefined interface.
13. The method (300) as claimed in claim 12, wherein the SCEF (108) delivers the
20 acknowledgement signal to the UE (102) via the MME (110) after determining that
the UE (102) indicated support for the RDS during the attach procedure.
14. The method (300) as claimed in claim 1, wherein the first network is a 5G
network and the second network is a 4G network.
25
15. A system (116) for managing a mobile originated (MO) message for a user
equipment (UE) (102) moving between a first network and a second network, the
system (116) comprising:
a receiving unit (118) configured to receive a connection setup
30 request from the UE (102) and send an acknowledgment of the connection
setup request to the UE (102);
27

a processing unit (120) coupled to the receiving unit (118) and is configured to:
determine if the UE (102) is connected to the first network or to the
second network;
5 when it is determined that the UE (102) is connected to the first
network, then performing following steps:
send, by the UE (102), an MO message to a session management function (SMF) (104);
forward, by the SMF (104), the received MO message to a
10 network exposure function (NEF) (106);
forward, by the NEF (106), the MO message to an application function (AF) (112);
send, by the AF (112), an acknowledgement signal to the
NEF (106) after receiving the MO message;
15 forward, by the NEF (106), the acknowledgement signal to
the UE (102) via the SMF (104);
when it is determined that the UE (102) is attached to the second network, then performing following steps:
send, by the UE (102), an MO message to a mobility management
20 entity (MME) (110);
forward, by the MME (110), the received MO message to a service capability exposure function (SCEF) (108);
forward, by the SCEF (108), the MO message to the NEF (106);
forward, by the NEF (106), the MO message to an application
25 function AF (112);
send, by the AF (112), an acknowledgement signal to the NEF (106) after receiving the MO message;
forward, by the NEF (106), the acknowledgement signal to the SCEF
(108); and
30 deliver, by the SCEF (108), the acknowledgement signal to the UE
(102) via the MME (110).
28

16. The system (116) as claimed in claim 15, wherein the first network and the second network are provided with a reliable data services (RDS) support indication.
5 17. The system (116) as claimed in claim 15, wherein the UE (102) sends the MO
message to the SMF (104) after performing a successful attach procedure with the first network.
18. The system (116) as claimed in claim 15, further configured to create, by the
10 SMF (104), a session management (SM) context on the NEF (106) during the attach
procedure.
19. The system (116) as claimed in claim 15, further configured to search, by the
NEF (106), an endpoint of the AF (112) for forwarding the MO message to the AF
15 (112).
20. The system (116) as claimed in claim 19, wherein the NEF (106) checks the SM
context and a Non-Internet Protocol Data Delivery (NIDD) configuration mapping
for searching the endpoint of the AF (112).
20
21. The system (116) as claimed in claim 20, wherein the NIDD configuration
includes an address of the AF (112) for each UE (102) available in the first network
and the second network.
25 22. The system (116) as claimed in claim 15, wherein the NEF (106) forwards the
acknowledgement signal to the UE (102) via the SMF (104) as per the SM context.
23. The system (116) as claimed in claim 22, wherein the NEF (106) forwards the
acknowledgement signal to the UE (102) after determining that the UE (102)
30 indicated support for the RDS during the attach procedure.

24. The system (116) as claimed in claim 15, further configured to create, by the MME (110), a session management (SM) context on the SCEF (108) during the attach procedure.
5 25. The system (116) as claimed in claim 15, wherein the SCEF (108) forwards the
MO message to the NEF (106) through a predefined interface.
26. The system (116) as claimed in claim 25, wherein the NEF (106) forwards the
acknowledgement signal to the SCEF (108) as per the SM context over the
10 predefined interface.
27. The system (116) as claimed in claim 26, wherein the SCEF (108) delivers the
acknowledgement signal to the UE (102) via the MME (110) after determining that
the UE (102) indicated support for the RDS during the attach procedure.
15
28. The system (116) as claimed in claim 15, wherein the first network is a 5G
network and the second network is a 4G network.
29. A user equipment (UE) (102) moving between a first network and a second
20 network, wherein the first network and the second network comprising one or more
network elements for managing a mobile originated (MO) message for the UE (102), the one or more network elements configured for:
determining if the UE (102) is connected to the first network or to
the second network;
25 when it is determined that the UE (102) is connected to the first
network, the one or more network elements are configured for performing following steps:
receiving, from the UE (102), an MO message by a session
management function (SMF) (104);
30 forwarding, by the SMF (104), the received MO message to
a network exposure function (NEF) (106);
30

forwarding, by the NEF (106), the MO message to an application function (AF) (112);
sending, by the AF (112), an acknowledgement signal to the
NEF (106) after receiving the MO message;
5 forwarding, by the NEF (106), the acknowledgement signal
to the UE (102) via the SMF (104);
when it is determined that the UE (102) is attached to the second
network, the one or more network elements are configured for performing
following steps:
10 receiving, from the UE (102), an MO message by a mobility
management entity (MME) (110);
forwarding, by the MME (110), the received MO message to a service capability exposure function (SCEF) (108);
forwarding, by the SCEF (108), the MO message to the NEF
15 (106);
forwarding, by the NEF (106), the MO message to an application function AF (112);
sending, by the AF (112), an acknowledgement signal to the
NEF (106) after receiving the MO message;
20 forwarding, by the NEF (106), the acknowledgement signal
to the SCEF (108); and
delivering, by the SCEF (108), the acknowledgement signal to the UE (102) via the MME (110).
Dated this 08 day of May 2024
~Digitally signed~
25
Arindam Paul
REG.NO:IN/PA-174
of De Penning & De Penning
Agent for the Applicants