FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR CREATING A SESSION MANAGEMENT (SM) CONTEXT IN FIRST AND SECOND
NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

5 METHOD AND SYSTEM FOR CREATING A SESSION MANAGEMENT (SM)
CONTEXT IN FIRST AND SECOND NETWORK
TECHNICAL FIELD
10 [0001] Embodiments of the present disclosure generally relate to network performance
management systems. More particularly, embodiments of the present disclosure relate to a session management (SM) context in a first and a second network.
BACKGROUND
15
[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 be appreciated that this section is used only to enhance the understanding of the reader with
20 respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered
25 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. The third–generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and
30 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 generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
35 [0004] Nowadays, telecom operators are working hard to enhance network capabilities and to
efficiently handle a handover scenario or switching conditions from a low generation network (say 4G) to a high generation network (say 5G) or vice versa.
2

5 [0005] In particular, a Session Management (SM)-context is created in 4G and 5G network
during interworking scenarios and the SM-context is tracked to fetch a User Equipment’s (UE)
current network and perform operations on the UE. However, non-tracking of the SM context
leads to uncertainty at an Application Function (AF) and may also lead to uncertainty of one
or more operations such as “mobile terminated message”, “monitoring events”, “device
10 triggering” etc. may be executed in a network where UE is not latched. Thus, overall
performance of a Radio Access Network (RAN) gets affected due to non-tracking or inefficient tracking of the Session Management (SM) context at the first network and the second network.
[0006] Hence, in view of these and other existing limitations, there arises an imperative need
15 to provide an efficient solution to overcome the above-mentioned limitations and to provide a
method and system to allow efficient creation, tracking and management of session
management context in the Radio Access Network such as the 4G network and the 5G network.
SUMMARY
20 [0007] 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 not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for creating a session management (SM) context in a first network. A method for creating a session management (SM) context in a first network includes sending, by a first network node, a request to a second network node to obtain a first identifier. The method further encompasses receiving, at the first network node, a response to the request along with the obtained first identifier. Furthermore, the method includes sending, by the first network node, a request to a third network node for creation of the SM context. Further, the method includes receiving, at the first network node, a response from the third network node on the creation of the SM context, wherein the response comprises data associated with the SM context.
[0009] In an exemplary aspect of the present disclosure, the method further comprises
35 checking, by the third network node over Nesc interface, an existence of prestored SM context
for the UE at a fourth network node. The method further encompasses sending, by the third network node over the Nesc interface, a request to the fourth network node for deletion of the SM context based on a presence of the prestored SM context at the fourth network node,
3

5 wherein the fourth network node is a Service Capability Exposure Function (SCEF). Further,
the method includes receiving, at the third network node over the Nesc interface, a response to the request sent for the deletion of the prestored SM context.
[0010] In an exemplary aspect of the present disclosure, the method further comprises the first
10 network node is a Session Management Function (SMF) node, the second network node is a
Unified Data Management (UDM) node, and the third network node is a Network Exposure Function (NEF) node, wherein the first network is a 5th Generation network.
[0011] In an exemplary aspect of the present disclosure, the first identifier is a Network
15 Exposure Function ID (NEF-ID).
[0012] In another aspect of the present disclosure, the present disclosure may comprise a method for creating session management (SM) context in a second network. The method includes sending, by a fifth network node, a request to a sixth network node to obtain a second
20 identifier. The method further encompasses receiving, at the fifth network node, a response to
the request along with the obtained second identifier. Furthermore, the method includes sending, by the fifth network node, a request to a fourth network node for creation of the SM context. Further, the method includes receiving, at the fifth network node, a response from the fourth network node on the creation of the SM context, wherein the response comprises data
25 associated with the SM context.
[0013] In an aspect of the present disclosure, the method further comprises sending, by the
fourth network node over a Nesc interface, the SM context data to a third network node. The
method further includes receiving, at the fourth node over the Nesc interface, a response from
30 the third network node of successful reception of the SM context data.
[0014] In an aspect of the present disclosure, the third network node is a Network Exposure
Function (NEF) node, the fifth network node is a Mobility Management Entity (MME) node,
the sixth network node is a Home Subscriber Server (HSS) node, wherein the second network
35 is a 4th Generation network.
4

5 [0015] In an aspect of the present disclosure, sending, by the fourth network node over the
Nesc interface, the SM context data to the third network node, overwrites existing SM context data available at the third network node.
[0016] In an aspect of the present disclosure, the second identifier is a Service Capabilities
10 Exposure Function (SCEF-ID).
[0017] Another aspect of the present disclosure may relate to a system for creating a session management (SM) context in a first network. The system comprising a first network node, configured to send a request to a second network node to obtain a first identifier. The first
15 network node is further configured to receive a response to the request along with the obtained
first identifier. Further the first network node is configured to send a request to a third network node for creation of the SM context and the first network node is further configured to receive a response from the third network node on the creation of the SM context, wherein the response comprises data associated with the SM context.
20
[0018] Another aspect of the present disclosure may relate to a system for creating a session management (SM) context in a second network. The system comprising a fifth network node, configured to send a request to a sixth network node to obtain a second identifier. The fifth network node is further configured to receive a response to the request along with the obtained
25 second identifier. Furthermore, the fifth network node is configured to send a request to a fourth
network node for creation of the SM context. Further, the fifth network node is configured to receive a response from the fourth network node on the creation of the SM context, wherein the response comprises data associated with the SM context.
30 [0019] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instruction for creating a session management (SM) context in a first network, the instructions include executable code which, when executed by a one or more units of a system, causes a first network node to send a request to a second network node to obtain a first identifier, receive a response to the request along with the obtained first
35 identifier, sends a request to a third network node for creation of the SM context, and receives
a response from the third network node on the creation of the SM context, wherein the response comprises data associated with the SM context.
5

5 [0020] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instruction for creating a session management (SM) context
in a second network, when executed by one or more units of a system, causes a fifth network
node to send a request to a sixth network node to obtain a second identifier, receive a response
to the request along with the obtained second identifier, send a request to a fourth network node
10 for creation of the SM context, and receive a response from the fourth network node on the
creation of the SM context, wherein the response comprises data associated with the SM context.
OBJECTS OF THE INVENTION
15
[0021] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0022] It is an object of the present disclosure to provide a methods and systems for creation
20 of session management context.
[0023] It is another objection of the present disclosure to provide a single interface or common interface to serve SM (Session Management) context operations which increases the reliability.
25 [0024] It is yet another object of the present disclosure to handle SM-Context on a single node
or interface for both Radio Access Network i.e., 4G and 5G network.
[0025] It is yet another object of the present disclosure to provide a solution to track UE’s
current network with only one node i.e., converged NEF (common node or interface between
30 4G and 5G RAN) and the operations like sending “mobile terminated” messages can be
executed by Converged NEF after validating SM-Context source network.
DESCRIPTION OF THE DRAWINGS
35 [0026] 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. Components in the drawings are not necessarily to scale, emphasis instead being placed upon
6

5 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
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
10 components.
[0027] FIG. 1A illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
15 [0028] FIG. 1B illustrates an exemplary block diagram representation of 4th generation
network architecture interworking with the 5th generation network.
[0029] 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
20 implementation of the present disclosure.
[0030] FIG. 3 illustrates a system diagram for creating a session management (SM) context in a first network and a second network, in accordance with exemplary implementations of the present disclosure. 25
[0031] FIG. 4A illustrates an exemplary signal flow diagram for creating a session management (SM) context in a first network, in accordance with exemplary implementations of the present disclosure.
30 [0032] FIG. 4B illustrates an exemplary signal flow diagram for creating session management
(SM) context in a second network, in accordance with exemplary implementations of the present disclosure.
[0033] FIG. 5A illustrates a method flow diagram for creating a session management (SM)
35 context in a first network, in accordance with exemplary implementations of the present
disclosure.
7

5 [0034] FIG. 5B illustrates a method flow diagram for creating session management (SM)
context in a second network, in accordance with exemplary implementations of the present disclosure.
[0035] The foregoing shall be more apparent from the following more detailed description of
10 the disclosure.
DETAILED DESCRIPTION
[0036] 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 details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0037] 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 skilled in the art with an enabling description
25 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.
[0038] Specific details are given in the following description to provide a thorough
30 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.
35 [0039] 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
8

5 operations may be re-arranged. A process is terminated when its operations are completed but
could have additional steps not included in a figure.
[0040] 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
10 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
15 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.
[0041] As used herein, a “processing unit” or “processor” or “operating processor” includes
20 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
microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array
25 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.
30 [0042] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-
device”, “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 the features of the present disclosure. The user equipment/device may include, but is not limited
35 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
9

5 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.
[0043] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a
10 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.
15
[0044] 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 or more modules or one or more units with each other, which also includes the methods,
20 functions, or procedures that may be called.
[0045] All modules, units, components used herein, unless explicitly excluded herein, may be
software modules or hardware processors, the processors being a general-purpose processor, a
special purpose processor, a conventional processor, a digital signal processor (DSP), a
25 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.
[0046] As used herein the transceiver unit include at least one receiver and at least one
30 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.
[0047] As discussed in the background section, the current known solutions have several
35 shortcomings. The present disclosure provides a solution for handling and tracking a session
management context at network where a User equipment (UE) moves from one Radio Access Network (say 4G network) to another Radio Access Network (say 5G network) or vice-versa. Further, the present solution provides a solution for tracking of the SM context to avoid
10

5 uncertainty at Application Function (AF) and also the present discloses that one or more
operations such as “mobile terminated message”, “monitoring events”, “device triggering” etc.
may be executed in a network where UE is not latched. Thus, overall performance of the Radio
Access Network does not get affected due to non-tracking or inefficient tracking of the SM
context at the network, Therefore, the present disclosure aims to overcome the above-
10 mentioned and other existing problems in this field of technology by providing a solution of
creation and tracking of session management context considering the aspect related to
switching of a fifth-generation (5G) to a fourth-generation (4G) network by the UE or vice
versa, by a single proprietary interface, called as NeSc interface that is added to support SM
Context operations in the network in case where UE gets attached to 4G. The NeSc interface
15 supports Hypertext Transfer Protocol 2 (HTTP 2) and Hypertext transfer Protocol 1.1 (HTTP
1.1).
[0048] FIG. 1A and FIG. 1B illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture and 4th generation network architecture. FIG. 1B
20 is an illustration of the interworking of the 4th and 5th generation network through a Nesc
Interface. As shown in FIG. 1A, the 5GC network architecture [100A] 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 (SCP) [110], an Authentication Server Function (AUSF) [112], a
25 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 network (DN) [130], wherein all the components are assumed to be
30 connected to each other in a manner as obvious to the person skilled in the art for implementing
features of the present disclosure.
[0049] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system
that connects user equipment (UE) [102] to the core network (CN) and provides access to
35 different types of networks (e.g., 5G network). It consists of radio base stations and the radio
access technologies that enable wireless communication.
11

5 [0050] Access and Mobility Management Function (AMF) [106] is a 5G core network 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.
[0051] Session Management Function (SMF) [108] is a 5G core network function responsible
10 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.
[0052] Service Communication Proxy (SCP) [110] is a network function in the 5G core
15 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.
[0053] Authentication Server Function (AUSF) [112] is a network function in the 5G core
responsible for authenticating UEs during registration and providing security services. It
20 generates and verifies authentication vectors and tokens.
[0054] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. 25
[0055] 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.
30 [0056] 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.
[0057] Network Repository Function (NRF) [120] is a network function that acts as a central
35 repository for information about available network functions and services. It facilitates the
discovery and dynamic registration of network functions.
12

5 [0058] Policy Control Function (PCF) [122] is a network function responsible for policy
control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
[0059] Unified Data Management (UDM) [124] is a network function that centralizes the
10 management of subscriber data, including authentication, authorization, and subscription
information.
[0060] 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
[0061] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0062] Data Network (DN) [130] refers to a network that provides data services to user
20 equipment (UE) in a telecommunications system. The data services may include but are not
limited to Internet services, private data network related services.
[0063] As shown in FIG. 1B, the 4G network architecture [100B] is in an interworking
connection with the 5th Generation core network. The system [100B], in addition to the above-
25 mentioned components, further includes-
[0064] A Binding Support Function (BSF) [132] enables binding an application function
request to the PCF [122]. The BSF [132] tracks sessions taking place in the network.
30 [0065] A Short Message Service Function (SMSF) [134] supports transfer of Short Message
Service (SMS). The SMSF [134] checks the subscription and perform a relay function between the UE [102] and a Short Message Service Centre (SMSC).
[0066] A Security Edge Protection Proxy (SEPP) [136] is a network function that secures inter-
35 PLMN (Public Land Mobile Network) traffic. The SEPP [136] further ensures that signalling
traffic between operators is encrypted and authenticated.
13

5 [0067] A Gateway Mobile Location Centre (GMLC) [138] is a network function to support the
location services. The GMLC [138] may be integrated with a location-based service to locate the UE [102] connected to the network at a specific time.
[0068] A Home Subscriber Service (HSS) [140] is a network function which provides details
10 of the user to other network functions in the network. The HSS [140] is an inclusive
management database for user information.
[0069] A Mobile Management Entity (MME) [142] is a network function which handles the
security, connectivity, mobility, inter-network communication, and the like in a network. The
15 MME [142] ensures the users have a consistent, secure, and efficient communication
experience in the network.
[0070] A Policy and Charging Rules Function (PCRF) [144] is a network function which
makes policy and charging rules based on factors like a user equipment’s usage, location, status
20 roaming, and the like. The PCRF [144] implements flexible policy control for mobile, fixed-
line, and IMS (IP multimedia system).
[0071] A Short Message Service Centre (SMSC) [146] is a network function responsible for
delivery of short messages. The SMSC [146] stores the received short messages and sends back
25 acknowledgement on receiving the short messages. The SMSC [146] is responsible for finding
the destination from the short messages and deliver it to the destination.
[0072] An Operations, Administration, and Maintenance (OAM) [150] is a network function
which stores a set of functions and procedures which may be important for efficient
30 management of a network architecture. The OAM [150] ensures reliability, performance and
overall health of the network.
[0073] A Supplementary DownLink (SDL) [152] is a network function to improve the
utilization of network resources which may have been under-utilized in the communication
35 network.
[0074] An Elastic Load Balancer (ELB) [154] is a network function responsible to distribute the requests received to a service across several backend servers. The ELB [154] ensures that
14

5 the service maintains the same performance level at all times and prevents it from becoming
overloaded or unavailable.
[0075] A Common API Framework (CAPIF) [156] is a framework comprising common API
aspects that are required to support service APIs. The CAPIF [156] is places within PLMN
10 operator network.
[0076] A Network Exposure Function Manager (NEF Manager) [158] is a network function which manages the exposure of network capabilities to external applications and services. The NEF Manager [158] may act as intermediary between the network and the applications.
[0077] A Network Exposure Function Application (NEF Application) [160] refers to any external application or service that interacts with the network through the NEF. The NEF application [160] are developed to enhance the user equipment’s capabilities by leveraging the communication network.
[0078] An Element Management System (EMS) [168] is a network function responsible to manage one or more network elements in a communication system.
[0079] The 4th and the 5th Generation networks are working together through the Nesc
25 interface.
[0080] Fig. 2 illustrates an exemplary block diagram of a computing device [1000] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. The computing device [1000] may be implemented
30 by a system [300] as shown in FIG. 3 further mentioned. In an implementation, the computing
device [1000] may also implement a method for creating a session management (SM) context in a first network utilising the system. In another implementation, the computing device [1000] itself implements the method for creating the session management (SM) context in the first network using one or more units configured within the computing device [1000], wherein said
35 one or more units are capable of implementing the features as disclosed in the present
disclosure.
15

5 [0081] The computing device [1000] may include a bus [1002] or other communication
mechanism for communicating information, and a hardware processor [1004] coupled with bus [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,
10 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 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
15 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 coupled to the bus [1002] for storing static information and instructions for the processor [1004].
20 [0082] 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],
25 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].
30 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.
[0083] 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
35 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
16

5 memory [1006]. Such instructions may be read into the main memory [1006] from another
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.
10
[0084] 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
15 (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication
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,
20 electromagnetic or optical signals that carry digital data streams representing various types of
information.
[0085] 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].
25 In the Internet example, a server [1030] might transmit a requested code for an application
program through the Internet [1028], the ISP [1026], 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.
30
[0086] FIG. 3 illustrates an exemplary block diagram of a system for creating a session management (SM) context in a first network, in accordance with exemplary implementations of the present disclosure. The system [300] comprises at least one first network node [302], at least one second network node [304], at least one third network node [306], at least fourth
35 network node [308], at least one fifth network node [310], and at least one sixth network node
[312]. 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
17

5 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 implement the features of the present disclosure. In another implementation, the 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.
10
[0087] The first network node [302] of the system [300] is configured to send a request to the second network node [304] to obtain a first identifier. The first identifier is a Network Exposure Function ID (NEF-ID). The Network Exposure Function (NEF) provides interfaces that make it possible for a Network Application to interact with a network. Further, the NEF-ID is the
15 identifier related to a specific network configuration which makes it possible for the Network
Application to interact with the network.
[0088] The first network node [302] is further configured to receive a response to the request along with the obtained first identifier. Further the first network node [302] is configured to
20 send a request to the third network node [306] for creation of the Session Management (SM)
context. The SMF sends the SM-context request to the SCEF. The SM-context allows the NEF and the SCEF to interact with each other and keep a track of the UE’s serving network. The Service Capability Exposure Function (SCEF) is the key entity to securely expose the services and capabilities provided by the 3GPP network interfaces. The NEF (Network Exposure
25 Function) may expose unified Application Programming Interfaces (APIs) to other external
applications for interaction with the 5th Generation core network functions. The NEF may provide interfaces for monitoring, provisioning and policy/charging functionalities in the 5G network.
30 [0089] Thereafter, the first network node [302] receive a response from the third network node
[306] on the creation of the SM context, wherein the response comprises data associated with the SM context.
[0090] The first network node [302] is a Session Management Function (SMF) node, the
35 second network node [304] is a Unified Data Management (UDM) node, and the third network
node [306] is a Network Exposure Function (NEF) node, wherein the first network is a 5th Generation network.
18

5 [0091] In the system [300], the third network node [306] is configured to check, over a Nesc
interface, an existence of prestored SM context for the UE at the fourth network node [308]. The Nesc interface is a proprietary interface which is added to support SM Context operations in the network in cases where the UE attached in the 4G network. The Nesc interface facilitates NEF to manage the SM-context related operations on both networks.
10
[0092] The third network node [306] is further configured to send, over the Nesc interface, a request to the fourth network node [308] for deletion of the SM context based on a presence of the prestored SM context at the fourth network node [308], wherein the fourth network node [308] is a Service Capability Exposure Function (SCEF). The SCEF is used for the delivery of
15 non-IP data over the control plane and provides an interface for network services
(authentication and authorization, discovery and access network capabilities). The SCEF is the key entity within the 3GPP architecture for service capability exposure that provides a means to expose the services and capabilities provided by 3GPP network interfaces securely to external entities to support IoT applications.
20
[0093] The third network node [306] is further configured to receive, over the Nesc interface, a response to the request sent for the deletion of the prestored SM context.
[0094] Further, as disclosed by the present disclosure the system [300] is further configured
25 for creating a session management (SM) context in a second network, in accordance with
exemplary implementations of the present disclosure.
[0095] Further, the system [300] is configured for creating the session management (SM)
context in the second network, with the help of the interconnection between the
30 components/units of the system [300].
[0096] The fifth network node [310] of the system [300] is configured to send a request to the
sixth network node [312] to obtain a second identifier. The second identifier is a Service
Capabilities Exposure Function (SCEF-ID). The SCEF is used for the delivery of non-IP data
35 over the control plane and provides an interface for network services (authentication and
authorization, discovery and access network capabilities). The SCEF is the key entity within the 3GPP architecture for service capability exposure that provides a means to expose the
19

5 services and capabilities provided by the 3GPP network interfaces securely to external entities
to support Internet of Things (IoT) applications.
[0097] The fifth network node [310] is further configured to receive a response to the request along with the obtained second identifier. Further, the fifth network node [310] is configured
10 to send a request to the fourth network node [308] for creation of the SM context, where the
request includes a User Identity, a Packet data Unit (PDU) session ID, a Non Ip data Delivery (NIDD) information, a Single Network Slice Selection Assistance Information (S-NSSAI) and a data Network Name (DNN). Further, the fifth network node [310] receives a response from the fourth network node [308] on the creation of the SM context, wherein the response
15 comprises data associated with the SM context. The response includes comprises the data
associated with the SM context such as a User Identity, a Packet data Unit (PDU) session ID, a Non Ip data Delivery (NIDD) information, a Single Network Slice Selection Assistance Information (S-NSSAI) and a data Network Name (DNN). The SM-context is created to allow the NEF and the SCEF to interact with each other and keep a track of the UE’s serving network.
20
[0098] The fourth network node [308] sends the SM context data to the third network node [306] to overwrite existing SM context data available at the third network node [306]. The third network node [306] may perform the process to overwrite the existing SM context data based on the user identity, the PDU session ID, the NIDD information, the S-NSSAI and the DNN.
25 The process to overwrite may assist in sending the SM context data to the SCEF accurately.
[0099] The third network node [306] is a Network Exposure Function (NEF) node, the fifth
network node [310] is a Mobility Management Entity (MME) node, the sixth network node
[312] is a Home Subscriber Server (HSS) node, wherein the second network is a 4th Generation
30 network.
[0100] Mobility Management Entity (MME): MME exists in the core network. MME is responsible for core network control functionality. The control plane protocols terminate at the MME and MME manages the mobility contexts of the UEs. 35
[0101] Home Subscriber Server (HSS): It is the main subscriber database used in the IP Multimedia Subsystem (IMS) which is responsible to provide details of the subscribers to other entities within the network.
20

5
[0102] In the system [300], the fourth network node [308] is further configured to send, over a Nesc interface, the SM context data to the third network node [306] and receive, over the Nesc interface, a response from the third network node [306] of successful reception of the SM context data. 10
[0103] FIG. 4A illustrates an exemplary signal flow diagram for creating a session management (SM) context in a first network, in accordance with exemplary implementations of the present disclosure.
15 [0104] FIG. 4B illustrates an exemplary signal flow diagram for creating session management
(SM) context in a second network, in accordance with exemplary implementations of the present disclosure.
[0105] As depicted in FIG. 4A and FIG. 4B one or more units configured to implement the
20 solution of the present disclosure comprises is at least one User Equipment (UE) [402], at least
one Session Management Function (SMF) [404], at least one Mobile Management Entity (MME) [406], at least one Unified Data Management (UDM) [408], at least one Home Subscriber Server (HSS) [410], at least one Network Exposure Function (NEF/ converged NEF) [412] and at least one Service Capability Exposure Function (SCEF) [414]. 25
[0106] Mobility Management Entity (MME): MME is responsible for core network control functionality. The control plane protocols terminate at the MME and the MME manages the mobility contexts of the UEs.
30 [0107] Home Subscriber Server (HSS): It is the main subscriber database used in the IP
Multimedia Subsystem (IMS) which is responsible to provide details of the user to other entities within the network.
[0108] At S1, the UE [402] attaches in a 5G Core Network with PDU (Packet Data Unit)
35 session type as “UNSTRUCTURED” and NEF ID in subscription information of PDN request,
with the SMF [404].
21

5 [0109] At S2, the SMF [404] send a NEF-ID Request to the UDM [408]. The NEF-ID request
may be ‘Nudm_UECM_Get service operation’. The NEF-ID request may include an NF ID
and a UE ID. NEF-ID is the identifier related to a specific network configuration which makes
it possible for the Network exposure function to interact with the network. Here, the NEF-ID
is the identifier for the 5G network exposure function. In an implementation of the present
10 disclosure, a converged NEF instance may be used. The converged NEF instance includes but
may not be limited to the NEF and the SCEF. In an embodiment, the NEF (third network node) and SCEF (fourth network node) may be used in combination.
[0110] At S3, if the UE [402] request contains the NEF-ID, the SMF (Session Management
15 Function) [404] initiates SMF [404]-NEF [412] connection establishment procedure to
corresponding the converged NEF [412] instance or else the SMF [404] fetches the NEF-ID response from the UDM [408].
[0111] At S4, the SMF [404] sends an “SM-Context create request” towards the Converged
20 NEF [412]. The request includes a User Identity, a Packet data Unit (PDU) session ID, a Non
Ip data Delivery (NIDD) information, a Single Network Slice Selection Assistance Information (S-NSSAI) and a data Network Name (DNN).
[0112] Next, at S5, the NEF [412] may optionally also share an “SM-Context Delete Request”
25 to the SCEF [414] and the SCEF [414] may at S6, share a response for the same to the NEF
[412]. The SCEF is the key entity within the 3GPP architecture for service capability exposure that provides a means to expose the services and capabilities provided by 3GPP network interfaces securely to external entities to support IoT applications.
30 [0113] Next at S7, the NEF [412] sends a “SM-Context Create Response”, where the where
the response includes a User Identity, a Packet data Unit (PDU) session ID, a Non Ip data Delivery (NIDD) information, a Single Network Slice Selection Assistance Information (S-NSSAI) and a data Network Name (DNN), and further creates a SM Context and associates it with User Identity and a PDU session ID and shares the information to the SMF [404]. The
35 SM-context allows the NEF [412] and the SCEF to interact with each other and keep a track of
the UE’s [402] serving network.
22

5 [0114] Further, in order to handle a 4G to a 5G handover scenario, the NEF [412] checks if
any previous SM context exists for the UE created by the SCEF.
[0115] NeSc interface is the medium between NEF and SCEF to communicate messages
related to SM-Context. If it exists, then NEF [412] initiates a delete SM-Context to SCEF over
10 the NeSc interface. The Nesc interface is an interface which is added to support SM Context
operations in the network in cases where UE attached in 4G. The Nesc interface facilitates NEF to manage SM-context related operations on both networks.
[0116] Now, referring to FIG. 4B illustrates-15
[0117] At S8, in case the UE [402] attaches in a 4G EPC, the UE [402] gets connected to the MME [406].
[0118] At S9, the MME [406] sends the NEF-ID request to the HSS [410]. NEF-ID is the
20 identifier related to a specific network configuration which makes it possible for the Network
Application to interact with the network. Here, the NEF-ID is the identifier related to the network configuration between the UE [402] and the 4G network.
[0119] Further at S10, the HSS [410] sends back the NEF-ID response to the MME [406].
25
[0120] Further at S11, the MME [406] send a SM- context create Request to the SCEF [414], wherein at step 12, the SCEF [414] sends back the SM-context create response to the MME [406]. The response includes a User Identity, a Packet data Unit (PDU) session ID, a Non Ip data Delivery (NIDD) information, a Single Network Slice Selection Assistance Information
30 (S-NSSAI) and a data Network Name (DNN).
[0121] Next at S13, the SCEF [414] will forward the SM-context create response to the NEF [412] internally over the NeSc interface.
35 [0122] At S14, the NEF [412] will overwrite the new SM-context in its database, then he SM-
context will help the NEF [412] to forward Mobile Terminated (MT) messages to correct the SCEF [414].
23

5
[0123] Referring to Figure 5A, an exemplary method flow diagram [500a] for creating a
session management (SM) context in a first network, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the method [500a]
is performed by the system [300]. Further, in an implementation, the system [300] may be
10 present in a server device to implement the features of the present disclosure. Also, as shown
in Figure 5A, the method [500a] starts at step [502a].
[0124] At [502a], the method includes sending, by a first network node [302], a request to a
second network node [304] to obtain a first identifier. The first identifier is a Network Exposure
15 Function ID (NEF-ID).
[0125] Further, at step [504a], the method encompasses receiving, at the first network node [302], a response to the request along with the obtained first identifier.
20 [0126] Further at step [506a], sending, by the first network node [302], a request to a third
network node [306] for creation of the SM context. The first network node [302] is a Session Management Function (SMF) node, the second network node [304] is a Unified Data Management (UDM) node, and the third network node [306] is a Network Exposure Function (NEF) node, wherein the first network is a 5th Generation network. 25
[0127] The method at step [508a] further encompasses receiving, at the first network node [302], a response from the third network node [306] on the creation of the SM context, wherein the response comprises data associated with the SM context. The SM-context allows the NEF and the SCEF to interact with each other and keep a track of the UE’s serving network. 30
[0128] The method further includes checking, by the third network node [306] over Nesc
interface, an existence of prestored SM context for the UE at a fourth network node [308]. Nesc
interface is a proprietary interface which is added to support SM Context operations in the
network in cases where UE attached in 4G. The Nesc interface facilitates NEF to manage SM-
35 context related operations on both networks.
[0129] The method further comprises sending, by the third network node [306] over the Nesc interface, a request to the fourth network node [308] for deletion of the SM context based on a
24

5 presence of the prestored SM context at the fourth network node [308], wherein the fourth
network node [308] is a Service Capability Exposure Function (SCEF). Thereafter, the method comprises receiving, at the third network node [306] over the Nesc interface, a response to the request sent for the deletion of the prestored SM context.
10 [0130] The method comes to an end at step [510a].
[0131] Referring to Figure 5B, an exemplary method flow diagram [500b] for creating a
session management (SM) context in a second network, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the method [500b]
15 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 Figure 5B, the method [500b] starts at step [502b].
[0132] At step [502b], the method includes sending, by a fifth network node [310], a request
20 to a sixth network [312] node to obtain a second identifier. The second identifier is a Service
Capabilities Exposure Function (SCEF-ID). The SCEF is used for the delivery of non-IP data
over the control plane and provides an interface for network services (authentication and
authorization, discovery and access network capabilities). The SCEF is the key entity within
the 3GPP architecture for service capability exposure that provides a means to expose the
25 services and capabilities provided by 3GPP network interfaces securely to external entities to
support IoT applications.
[0133] Next, at step [506b], the method includes receiving, at the fifth network node [310], a response to the request along with the obtained second identifier.
30
[0134] At step [508b], the method encompasses sending, by the fifth network node [310], a request to a fourth network node [308] for creation of the SM context. The request includes a User Identity, a Packet data Unit (PDU) session ID, a Non Ip data Delivery (NIDD) information, a Single Network Slice Selection Assistance Information (S-NSSAI) and a data
35 Network Name (DNN). The third network node [306] is a Network Exposure Function (NEF)
node, the fifth network node [310] is a Mobility Management Entity (MME) node, the sixth network node [312] is a Home Subscriber Server (HSS) node, wherein the second network is a 4th Generation network.
25

5 [0135] Mobility Management Entity (MME): MME is responsible for core network
control functionality. The control plane protocols terminate at the MME and MME manages the mobility contexts of the UEs.
[0136] Home Subscriber Server (HSS): It is the main subscriber database used in the IP
10 Multimedia Subsystem (IMS) which is responsible to provide details of the subscribers to other
entities within the network.
[0137] Further at step [510b], the method includes receiving, at the fifth network node [310], a response from the fourth network node [308] on the creation of the SM context, wherein the
15 response comprises data associated with the SM context. The method further encompasses
sending, by the fourth network node [308] over a Nesc interface, the SM context data to a third network node [306]. Further, the method may comprises receiving, at the fourth network node [308] over the Nesc interface, a response from the third network node [306] of successful reception of the SM context data. The method further includes sending, by the fourth network
20 node [308] over the Nesc interface, the SM context data to the third network node [306],
overwrites existing SM context data available at the third network node [306].
[0138] At step [512b], the method comes to an end.
25 [0139] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for creating a session management (SM) context in a first and second network, the instructions include executable code which, when executed by a one or more units of a system, causes: a first network node [302] of the system to send a request to a second network node [304] to obtain a first identifier, receive a response to the request along
30 with the obtained first identifier, send a request to a third network node [306] for creation of
the SM context and receive a response from the third network node [306] on the creation of the SM context, wherein the response comprises data associated with the SM context.
[0140] Yet another aspect of the present disclosure may relate to a non-transitory computer
35 readable storage medium storing instruction for creating a session management (SM) context
in a second network, when executed by one or more units of a system causes a fifth network node [310] of the system to send a request to a sixth network node [312] to obtain a second identifier, receive a response to the request along with the obtained second identifier, send a
26

5 request to a fourth network node [308] for creation of the SM context and receive a response
from the fourth network node [308] on the creation of the SM context, wherein the response comprises data associated with the SM context.
[0141] As is evident from the above, the present disclosure provides a technically advanced
10 solution for methods and systems for creating a session management (SM) context in a first
and second network. The present solution provides methods and systems for creation of session management context in a first and second network. The present disclosure provides a technically advanced solution by disclosing a single interface or common interface to serve SM (Session Management) context operations which increases the reliability. The solution further
15 handles SM-Context on a single node or interface for both Radio Access Network i.e., 4G and
5G network. The solution also provides a solution to track UE’s current network with only one node i.e., converged NEF (common node or interface between 4G and 5G RAN) and the operations like sending “mobile terminated” messages can be executed by Converged NEF after validating SM-Context source network.
20
[0142] 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 will be apparent to
25 those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to
be implemented is illustrative and non-limiting.
[0143] 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
30 interchangeably. While specific embodiments may disclose a particular functionality of these
units for clarity, it is recognized that various configurations and combinations thereof are 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
35 intended functionality described herein, are considered to be encompassed within the scope of
the present disclosure.

5 We Claim:
1. A method for creating a session management (SM) context in a first network, the
method comprising:
sending, by a first network node [302], a request to a second network node [304] to
10 obtain a first identifier;
receiving, at the first network node [302], a response to the request along with the obtained first identifier;
sending, by the first network node [302], a request to a third network node [306] for
creation of the SM context; and
15 receiving, at the first network node [302], a response from the third network node
[306] on the creation of the SM context, wherein the response comprises data associated with the SM context.
2. The method as claimed in claim 1, further comprises:
20 checking, by the third network node [306] over Nesc interface, an existence of
prestored SM context for a User Equipment (UE) at a fourth network node [308];
sending, by the third network node [306] over the Nesc interface, a request to
the fourth network node [308] for deletion of the SM context based on a presence of
the prestored SM context at the fourth network node [308], wherein the fourth network
25 node [308] is a Service Capability Exposure Function (SCEF); and
receiving, at the third network node [306] over the Nesc interface, a response to the request sent for the deletion of the prestored SM context.
3. The method as claimed in claim 1, wherein the first network node [302] is a Session
30 Management Function (SMF) node, the second network node [304] is a Unified Data
Management (UDM) node, and the third network node [306] is a Network Exposure Function (NEF) node, wherein the first network is a 5th Generation network.
4. The method as claimed in claim 1, wherein the first identifier is a Network Exposure
35 Function ID (NEF-ID).

5
5. A method for creating session management (SM) context in a second network, the
method comprising:
sending, by a fifth network node [310], a request to a sixth network [312] node to
obtain a second identifier;
10 receiving, at the fifth network node [310], a response to the request along with the
obtained second identifier;
sending, by the fifth network node [310], a request to a fourth network node [308] for creation of the SM context; and
receiving, at the fifth network node [310], a response from the fourth network node
15 [308] on the creation of the SM context, wherein the response comprises data associated
with the SM context.
6. The method as claimed in claim 5, further comprises:
sending, by the fourth network node [308] over a Nesc interface, the SM context
20 data to a third network node [306]; and
receiving, at the fourth network node [308] over the Nesc interface, a response from the third network node [306] of successful reception of the SM context data.
7. The method as claimed in claim 6, wherein the third network node [306] is a Network
25 Exposure Function (NEF) node, the fifth network node [310] is a Mobility Management
Entity (MME) node, the sixth network node [312] is a Home Subscriber Server (HSS) node, wherein the second network is a 4th Generation network.
8. The method as claimed in claim 6, wherein sending, by the fourth network node [308]
30 over the Nesc interface, the SM context data to the third network node [306], overwrites
existing SM context data available at the third network node [306].
9. The method as claimed in claim 5, wherein the second identifier is a Service
Capabilities Exposure Function (SCEF-ID).
35
10. A system [300] for creating a session management (SM) context in a first network, the
system [300] comprising:

5 a first network node [302] configured to:
send a request to a second network node [304] to obtain a first identifier;
receive a response to the request along with the obtained first identifier;
send a request to a third network node [306] for creation of the SM context; and
receive a response from the third network node [306] on the creation of the SM
10 context, wherein the response comprises data associated with the SM context.
11. The system [300] as claimed in claim 10, wherein the third network node [306] is
configured to:
check, over a Nesc interface, an existence of prestored SM context for a User
15 Equipment (UE) at a fourth network node [308];
send, over the Nesc interface, a request to the fourth network node [308] for
deletion of the SM context based on a presence of the prestored SM context at the fourth
network node [308], wherein the fourth network node [308] is a Service Capability
Exposure Function (SCEF);
20 receive, over the Nesc interface, a response to the request sent for the deletion
of the prestored SM context.
12. The system [300] as claimed in claim 10, wherein the first network node [302] is a
Session Management Function (SMF) node, the second network node [304] is a Unified
25 Data Management (UDM) node, and the third network node [306] is a Network
Exposure Function (NEF) node, wherein the first network is a 5th Generation network.
13. The system [300] as claimed in claim 10, wherein the first identifier is a Network
Exposure Function ID (NEF-ID).
30
14. A system [300] for creating a session management (SM) context in a second network,
the system comprising:
a fifth network node [310] configured to:
35 send a request to a sixth network node [312] to obtain a second identifier;
receive a response to the request along with the obtained second identifier; send a request to a fourth network node [308] for creation of the SM context; and
30

5 receive a response from the fourth network node [308] on the creation of the
SM context, wherein the response comprises data associated with the SM context.
15. The system [300] as claimed in claim 14, wherein the fourth network node [3006] is
further configured to:
10 send, over a Nesc interface, the SM context data to a third network node [306];
and
receive, over the Nesc interface, a response from the third network node [306] of successful reception of the SM context data.
15 16. The system [300] as claimed in claim 15, wherein the third network node [306] is a
Network Exposure Function (NEF) node, the fifth network node [310] is a Mobility Management Entity (MME) node, the sixth network node [312] is a Home Subscriber Server (HSS) node, wherein the second network is a 4th Generation network.
20 17. The system [300] as claimed in claim 15, wherein the fourth network node [308] sends
the SM context data to the third network node [306] to overwrite existing SM context data available at the third network node [306].
18. The system [300] as claimed in claim 14, wherein the second identifier is a Service
Capabilities Exposure Function (SCEF-ID).