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 TRANSMITTING PAGING MESSAGE”
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.

METHOD AND SYSTEM FOR TRANSMITTING PAGING
MESSAGE
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to methods and systems for transmitting paging message.
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that 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.
[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 only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security.

[0004] Existing solutions in the telecommunications industry often struggle to efficiently manage the handover process when a User Equipment (UE) moves from an Evolved Packet System (EPS) network to a 5th Generation System (5GS) network. This challenge is particularly evident in the context of paging, where the network needs to send a signal to the UE to notify it of incoming data or calls. In the current state of the art, when a UE undergoes a handover from EPS to 5GS, the Access and Mobility Management Function (AMF) in the 5GS network lacks the necessary information to execute differential paging strategies based on the Data Network Name (DNN). This is because the AMF does not have access to the DNN name after the user has moved from EPS to 5GS using the N26 interface. Existing systems are unable to distinguish between different types of data networks, such as IMS (IP Multimedia Subsystem) and regular data networks, when paging UEs. This limitation leads to a one-size-fits-all approach to paging, which can be inefficient and result in suboptimal use of network resources. For example, paging for IMS services, which are often time-sensitive, cannot be prioritized over regular data services. As a result, the call setup time for IMS services may be longer than necessary, and the overall paging success rate may be lower than desired. Furthermore, existing systems do not allow for the customization of paging strategies based on the type of data network. This means that the network cannot adjust its paging approach to reduce the load on the Radio Access Network (RAN) or to improve the response time for specific services. Consequently, the network may experience unnecessary congestion, and the quality of service for users may be compromised.
[0005] Thus, there exists an imperative need in the art to provide an efficient system and method for transmitting paging message.
OBJECTS OF THE PRESENT DISCLOSURE

[0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0007] It is an object of the present disclosure to provide system and method for transmitting paging message.
[0008] It is another object of the present disclosure to provide a system and method for retrieving Data Network Name (DNN) that enables the Access and Mobility Management Function (AMF) to execute differential paging strategies based on the DNN, improving the paging success rate and call setup time.
[0009] It is yet another object of the present disclosure to provide a system and method for retrieving Data Network Name (DNN) that allows for the efficient handover of User Equipment (UE) from an Evolved Packet System (EPS) to a 5th Generation System (5GS), ensuring seamless connectivity during the transition.
[0010] It is yet another object of the present disclosure to provide a system and method for retrieving Data Network Name (DNN) that facilitates the mapping of PDU Session IDs to their corresponding DNNs, enabling the AMF to have a clear understanding of the network resources being utilized by the UE.
[0011] It is yet another object of the present disclosure to provide a system and method for retrieving Data Network Name (DNN) that optimizes the use of network resources by allowing the AMF to tailor its paging strategy based on the type of data network, reducing unnecessary load on the Radio Access Network (RAN).
[0012] It is yet another object of the present disclosure to provide a system and method for retrieving Data Network Name (DNN) that enhances the quality of service for users by ensuring that time-sensitive services, such as those provided by the IP Multimedia Subsystem (IMS), receive priority in the paging process.

[0013] It is yet another object of the present disclosure to provide a system and method for retrieving Data Network Name (DNN) that improves the overall efficiency of the 5G Core network by enabling the AMF to make informed decisions about paging and resource allocation based on the specific needs of different data networks.
SUMMARY
[0014] 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.
[0015] An aspect of the present disclosure provides a method for transmitting paging message is disclosed. The method comprises receiving, at a first network node, a handover request message for handover of a user equipment (UE) from a first network system to a second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier. The method further comprises transmitting, by the first network node, a Session Management (SM) context create request to a second network node associated with the second network system. The method further comprises receiving, at the first network node, a SM context create response from the second network node, wherein the SM context create response comprises Packet Data Unit (PDU) Session ID. The method further comprises mapping, by the first network node, the network name identifier with the PDU session ID. The method further comprises storing, by the first network node in a repository, the mapping of the network name identifier with the PDU session ID. Thereafter, the method comprises transmitting, by the first network node,

differential paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs.
[0016] In an exemplary aspect of the present disclosure, the first network system is an Evolved Packet System (EPS), and the second network system is a 5th Generation System (5GS).
[0017] In an exemplary aspect of the present disclosure, the handover request message is received at the first network node from a Mobility Management Entity (MME) associated with the first network system.
[0018] In an exemplary aspect of the present disclosure, the first network node is an Access and Mobility Management Function (AMF) associated with the second network system.
[0019] In an exemplary aspect of the present disclosure, the second network node corresponds to Session Management Function and Packet Data Network Gateway-Control Plane (SMF-PGW-C).
[0020] In an exemplary aspect of the present disclosure, the handover request message is a forward relocation request message to perform a handover of the UE from the first network system to the second network system.
[0021] In an exemplary aspect of the present disclosure, the handover request message is a context response message to perform idle mode mobility handover procedure of the UE from the first network system to the second network system.
[0022] In an exemplary aspect of the present disclosure, transmitting the differential paging for different network name identifiers involve sending of paging messages to the User Equipment(s) via a Radio Access Network (RAN).

[0023] Another aspect of the present disclosure provides a system for transmitting paging messages. The system comprises a first network node of a second network system comprising a transceiver unit, configured to receive a handover request message for handover of a user equipment (UE) from a first network system to the second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier. The transceiver unit is further configured to transmit a Session Management (SM) context create request to a second network node associated with the second network system. The transceiver unit is further configured to receive a SM context create response from the second network node, wherein the SM context create response comprises Packet Data Unit (PDU) Session ID. The system comprises a mapping unit, configured to map the network name identifier with the PDU session ID. The system comprises a storing unit, configured to store, in a repository, the mapping of the network name identifier with the PDU session ID. The system comprises the transceiver unit, configured to transmit differential paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs.
[0024] Yet another aspect of the present disclosure relates to a user equipment (UE). The UE comprising: a processor configured to: receive differential paging for different network name identifiers based on a stored mapping between network name identifiers and PDU session IDs, wherein the differential message is generated based on a handover request message for handover of the UE [102] from a first network system to the second network system, and wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier.
[0025] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for transmitting paging

5 [0027] FIG. 1 illustrates an exemplary 5GC network architecture, in accordance
with exemplary embodiments of the present disclosure.
[0028] FIG. 2 illustrates an exemplary system for transmitting paging messages, in accordance with exemplary embodiments of the present disclosure. 10
[0029] FIG. 3A illustrates an exemplary sequence diagram illustrating transmitting paging messages, in accordance with exemplary embodiments of the present disclosure.
15 [0030] FIG. 3B illustrates an exemplary sequence diagram illustrating
transmitting paging messages, in accordance with exemplary embodiments of the present disclosure.
[0031] FIG. 4 illustrates an exemplary method flow diagram indicating the
20 process for transmitting paging messages, in accordance with exemplary
embodiments of the present disclosure.
[0032] FIG. 5 illustrates an exemplary block diagram of a computing device upon which an embodiment of the present disclosure may be implemented. 25
[0033] FIG. 6 illustrates an exemplary block diagram of a user equipment (UE) for transmitting paging messages, in accordance with exemplary embodiments of the present disclosure.
30 [0034] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
9

5 [0035] 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 can each be used independently of one
10 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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in
15 which like reference numerals refer to the same parts throughout the different
drawings.
[0036] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
20 the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
25
[0037] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or
30 limitations on the described embodiments. The use of these terms is solely for
convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
10

5
[0038] 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
10 components may be shown as components in block diagram form in order not to
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.
15 [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 can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged.
20 A process is terminated when its operations are completed but could have additional
steps not included in a figure.
[0040] In addition, each block may indicate some of modules, segments, or codes
including one or more executable instructions for executing a specific logical
25 function(s). Further, functions mentioned in the blocks occur regardless of a
sequence in some alternative embodiments. For example, two blocks that are contiguously illustrated may be simultaneously performed in fact or be performed in a reverse sequence depending on corresponding functions.
30 [0041] Herein, the term "unit" indicates software or hardware components, such
as a field-programmable gate array (FPGA) and an application-specific integrated circuit (ASIC). However, the meaning of the "unit" is not limited to software or hardware. For example, a "unit" may be configured to be in a storage medium that may be addressed and may also be configured to be reproduced one or more
11

5 processor. Accordingly, a "unit" may include components such as software
components, object oriented software components, class components, and task components and processors, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuit, data, database, data structures, tables, arrays, and variables. The functions provided in the
10 components and the "units" may be combined with a smaller number of
components, and the "units" or may be further separated into additional components and "units". In addition, the components and the "units" may also be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card.
15
[0042] 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 herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
20 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 detailed description or the claims, such terms are intended to be inclusive—in a manner
25 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0043] As used herein, an “electronic device”, or “portable electronic device”, or
“user device” or “communication device” or “user equipment” or “device” refers
30 to any electrical, electronic, electromechanical and computing device. The user
device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user
12

5 equipment may be capable of operating on any radio access technology including
but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low
Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For
instance, the user equipment may include, but not limited to, a mobile phone,
smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop,
10 a general-purpose computer, desktop, personal digital assistant, tablet computer,
mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0044] Further, the user device may also comprise a “processor” or “processing
15 unit” includes processing unit, wherein processor refers to any logic circuitry for
processing instructions. The 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
DSP core, a controller, a microcontroller, Application Specific Integrated Circuits,
20 Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
25 [0045] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The
30 development, in this respect, has been incremental in the order of second generation
(2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
13

5 [0046] Hereinafter, terms identifying an access node, terms indicating network
entities, terms indicating messages, terms indicating an interface between network
entities, and terms indicating various pieces of identification information, as used
in the following description, are exemplified for convenience of explanation.
Accordingly, the disclosure is not limited to terms to be described below, and other
10 terms indicating objects having equal technical meanings may be used.
[0047] Hereinafter, for convenience of explanation, the disclosure uses terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) standards or technical specifications. However, the disclosure is not limited
15 to the terms and names, and may also be applied to systems following other
standards. In an exemplary aspect of the present disclosure, a base station may be, such as evolved node B (eNB) for 4G network. In an exemplary aspect of the present disclosure, a base station may be, such as next-generation node B (gNB) for 5G network.
20
[0048] In the following descriptions, the term "base station" refers to an entity for allocating resources to a user equipment (UE) and may be used interchangeably with at least one of a gNode B, an eNode B, a node B, a base station (BS), a radio access unit, a radio access network (RAN), a base station controller (BSC), or a
25 node over a network. The term "terminal" may be used interchangeably with a user
equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. However, the disclosure is not limited to the aforementioned examples.
30 [0049] In particular, the disclosure is applicable to 3GPP new radio (NR) (or 5th
generation (5G)) mobile communication standards. The disclosure is applicable to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail trade, security, and safety services) based on 5G communication technologies and Internet of things (IoT)-
14

5 related technologies. In the following description, the base station explained as a
gNB may also indicate an eNB. The term UE may also indicate a mobile phone, NB-IoT devices, sensors, and other wireless communication devices.
[0050] Radio Access Technology (RAT) refers to the technology used by mobile
10 devices/ user equipment (UE) to connect to a cellular network. It refers to the
specific protocol and standards that govern the way devices communicate with base
stations, which are responsible for providing the wireless connection. Further, each
RAT has its own set of protocols and standards for communication, which define
the frequency bands, modulation techniques, and other parameters used for
15 transmitting and receiving data. Examples of RATs include GSM (Global System
for Mobile Communications), CDMA (Code Division Multiple Access), UMTS
(Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
and 5G. The choice of RAT depends on a variety of factors, including the network
infrastructure, the available spectrum, and the mobile device's/device's capabilities.
20 Mobile devices often support multiple RATs, allowing them to connect to different
types of networks and provide optimal performance based on the available network
resources.
[0051] As discussed in the background section, existing solutions in the
25 telecommunications industry often struggle to efficiently manage the handover
process when a User Equipment (UE) moves from an Evolved Packet System (EPS)
network to a 5th Generation System (5GS) network. This challenge is particularly
evident in the context of paging, where the network needs to send a signal to the
UE to notify it of incoming data or calls. In the current state of the art, when a UE
30 undergoes a handover from EPS to 5GS, the Access and Mobility Management
Function (AMF) in the 5GS network lacks the necessary information to execute differential paging strategies based on the Data Network Name (DNN). This is because the AMF does not have access to the DNN name after the user has moved from EPS to 5GS using the N26 interface. Existing systems are unable to
15

5 distinguish between different types of data networks, such as IMS (IP Multimedia
Subsystem) and regular data networks, when paging UEs. This limitation leads to a one-size-fits-all approach for paging, which can be inefficient and result in suboptimal use of network resources. For example, paging for IMS services, which are often time-sensitive, cannot be prioritized over regular data services. As a result,
10 the call setup time for IMS services may be longer than necessary, and the overall
paging success rate may be lower than desired. Furthermore, existing systems do not allow for the customization of paging strategies based on the type of data network. This means that the network cannot adjust its paging approach to reduce the load on the Radio Access Network (RAN) or to improve the response time for
15 specific services. Consequently, the network may experience unnecessary
congestion, and the quality of service for users may be compromised.
[0052] To overcome these and other inherent problems in the art, the present disclosure proposes a solution of a method and system for transmitting paging
20 messages that involve receiving a handover request message for handover of a user
equipment (UE) from a first network system to a second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier. The first network node of the first network system then transmits a Session Management (SM)
25 context create request to a second network node associated with the second network
system. Upon receiving a SM context create response from the second network node, which includes a Packet Data Unit (PDU) Session ID, the first network node maps the network name identifier with the PDU session ID and stores this mapping in a repository. This stored mapping enables the first network node to transmit
30 differential paging for different network name identifiers based on the stored
mapping between network name identifiers and PDU session IDs. This method allows the Access and Mobility Management Function (AMF) in the 5GS network to have access to the DNN name even after the UE has moved from EPS to 5GS using the N26 interface, thereby enabling the AMF to execute differential paging
16

5 strategies based on the DNN name. This capability is particularly important for
efficiently managing paging in scenarios where UEs undergo handovers from EPS
to 5GS networks. By enabling the AMF to distinguish between different types of
data networks, such as IMS and regular data networks, the invention allows for the
customization of paging strategies based on the type of data network. This leads to
10 a more efficient use of network resources, improved paging success rates, and
enhanced quality of service for users, especially in terms of reduced call setup times for time-sensitive services like IMS.
[0053] Hereinafter, exemplary embodiments of the present disclosure will be
15 described with reference to the accompanying drawings.
[0054] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture [100], in accordance with exemplary embodiment of the present disclosure. As shown in FIG. 1, the 5GC network
20 architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104] or gNodeB, a plurality if network functions or network entities such as, an access and mobility management function (AMF) [106], a Session Management Function (SMF) unit [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
25 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
30 components are assumed to be connected to each other in a manner as obvious to
the person skilled in the art for implementing features of the present disclosure.
[0055] The User Equipment (UE) [102] interfaces with the network via the Radio Access Network (RAN) [104]; the Access and Mobility Management Function
17

5 (AMF) [106] manages connectivity and mobility, while the Session Management
Function (SMF) unit [108] administers session control; the service communication proxy (SCP) [110] routes and manages communication between network services, enhancing efficiency and security, and the Authentication Server Function (AUSF) [112] handles user authentication; the NSSAAF [114] for integrating the 5G core
10 network with existing 4G LTE networks i.e., to enable Non-Standalone (NSA) 5G
deployments, the Network Slice Selection Function (NSSF) [116], Network Exposure Function (NEF) [118], and Network Repository Function (NRF) [120] enable network customization, secure interfacing with external applications, and maintain network function registries respectively; the Policy Control Function
15 (PCF) [122] develops operational policies, and the Unified Data Management
(UDM) [124] manages subscriber data; the Application Function (AF) [126] enables application interaction, the User Plane Function (UPF) [128] processes and forwards user data, and the Data Network (DN) [130] connects to external internet resources; collectively, these components are designed to enhance mobile
20 broadband, ensure low-latency communication, and support massive machine-type
communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
[0056] Radio Access Network (RAN) [104] is the part of a mobile
25 telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
30 [0057] Access and Mobility Management Function (AMF) [106] (alternatively
referred to as AMF unit [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.
18

5
[0058] Session Management Function (SMF) [108] is a 5G core network function responsible 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.
10
[0059] Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
15
[0060] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
20 [0061] 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 [0062] 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.
[0063] Network Exposure Function (NEF) [118] is a network function that
30 exposes capabilities and services of the 5G network to external applications,
enabling integration with third-party services and applications.
19

5 [0064] Network Repository Function (NRF) [120] is a network function that acts
as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
[0065] Policy Control Function (PCF) [122] is a network function responsible for
10 policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0066] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication,
15 authorization, and subscription information.
[0067]
[0068] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 20
[0069] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
25 [0070] Data Network (DN) [130] refers to a network that provides data services
to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
[0071] FIG. 2 illustrates an exemplary block diagram of a system [200] for
30 transmitting paging message, in accordance with exemplary embodiments of the
present disclosure. As shown in FIG. 2, the system [200] includes a transceiver unit [202], a mapping unit [204], and a storing unit [206], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. Also, in FIG.
20

5 2 only a few units are shown, however, the system [200] may comprise multiple
such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. In an embodiment, the system [200] may be incorporated by a first network node such as the AMF [106].
10 [0072] The system [200] comprises a first network node of a second network
system. The first network node of a second network system further comprising a transceiver unit, configured to receive a handover request message for handover of a user equipment (UE) from a first network system to the second network system, wherein the handover request message comprises Packet Data Network (PDN)
15 connection Information Element (IE) comprising a network name identifier. In an
exemplary aspect, the first network system is an Evolved Packet System (EPS) and the second network system is a 5th Generation System (5GS). The first network node is an Access and Mobility Management Function (AMF) [106] associated with the second network system. The first network node (such as AMF [106]) comprises
20 the transceiver unit [202], which is configured to receive a handover request
message for handover of a user equipment (UE) [102] from a first network system (such as Evolved Packet System (EPS) to the second network system (such as 5th Generation System (5GS)). The handover request message comprises a Packet Data Network (PDN) connection Information Element (IE) comprising a network name
25 identifier. The handover request message is received at the first network node (such
as AMF [106]) from a Mobility Management Entity (MME) associated with the first network system (EPS system). In an exemplary aspect, when a UE [102] performs mobility procedure from the first network system to the second network system, a handover request message is sent from the MME to AMF [106] network
30 node. There may be, such as two types of mobility procedure may be possible
between the first network system (EPS system) and the second network system (5GS system): EPS to 5GS handover and EPS to 5GS idle mode mobility handover. The handover request message contains details about the UE's connection, including the PDN connection within forward relocation request IE, which holds
21

5 the network name identifier. The network name identifier allows the network node
to identify the specific network to which the UE [102] is attempting to connect. In
an embodiment, the handover request message is a forward relocation request
message to perform a handover of the UE [102] from the first network system to
the second network system. The MME sends handover request message to the AMF
10 over the N26 interface as part of the EPS to 5GS handover procedures. In an
exemplary aspect, the forward relocation request may comprise MME/SGSN (Serving GPRS Support Node)/AMF UE EPS PDN information.
[0073] In an embodiment, the AMF sends handover request message to the MME
15 over the N26 interface as part of the 5GS to EPS handover procedures.
[0074] In another embodiment, the handover request message is an information
element in a context response message to perform idle mode mobility handover
procedure of the UE [102] from the first network system to the second network
20 system. In an exemplary aspect, the context response message may sent as a
response to a previous context request message. The context response message may comprise information of MME/SGSN/AMF UE MM Context.
[0075] The transceiver unit [202] is further configured to transmit a Session
25 Management (SM) context create request to a second network node (such as
Session Management Function and Packet Data Network Gateway-Control Plane
(SMF-PGW-C)) associated with the second network system. Once the transceiver
unit [202] has received the handover request message and extracted the necessary
information, it initiates the establishment of a new session management context for
30 the UE [102] in the second network system.
[0076] The EPS to 5GS idle mode mobility using N26 interface.
[0077] The NF Service Consumer (e.g. AMF [106]) requests the session
management function (SMF) [108] to move a UE EPS PDN connection to 5GS
22

5 using N26 interface. The NF service consumer may send a POST request towards
the SMF (+PGW-C) of each UE EPS PDN connection, with the following one or more additional information: UE EPS PDN connection, including the EPS bearer contexts, received from the MME, representing the individual SM context resource to be created; the pduSessionsActivateList attribute, including the PDU Session ID
10 of all the PDU session(s) to be reactivated; the epsBearerCtxStatus attribute,
indicating the status of all the EPS bearer contexts in the UE, if corresponding information is received in the Registration Request from the UE; the dlDataWaitingInd attribute, indicating that DL data buffered in EPS needs to be forwarded to the UE, if such indication is present in the Context Response received
15 from the MME.
[0078] Then the SMF [108] may return a created response including the following information: PDU Session ID corresponding to the default EPS bearer ID of the EPS PDN connection.
20
[0079] EPS to 5GS Handover Preparation using N26 interface
[0080] The NF Service Consumer (e.g. AMF [106]) may request to the SMF [108]
to handover a UE EPS PDN connection to 5GS system using N26 interface, as
follows:
25 [0081] The NF Service Consumer s send a POST request, with the following
additional information: UE EPS PDN connection, including the EPS bearer contexts, representing the individual SM context resource to be created.
[0082] The SMF shall return a 201 Created response including the following
30 information: PDU Session ID corresponding to the default EPS bearer ID of the
EPS PDN connection.
[0083] The SM context create request includes details such as the network name identifier and other relevant information obtained from the handover request
23

5 message. The UE EPS PDN connection, includes the EPS bearer contexts, received
from the MME, representing the individual SM context resource to be created. The
second network node, upon receiving this request, processes it and creates a new
session management context for the UE, enabling it to access services in the second
network system for ensuring a seamless transition for the UE [102] as it moves from
10 one network system to another, maintaining continuity of service and connectivity.
[0084] The transceiver unit [202] is further configured to receive a SM context create response from the second network node, wherein the SM context create response comprises a Packet Data Unit (PDU) Session ID. In response to the
15 receiving SM context create request, the SMF shall return a 201 Created response
including the following information: PDU Session ID corresponding to the default EPS bearer ID of the EPS PDN connection. After the transceiver unit [202] has transmitted the SM context create request to the second network node, it awaits a response that confirms the creation of the new session management context and
20 provides the PDU Session ID, which is a unique identifier for the newly established
session. The receipt of the SM context create response with the PDU Session ID marks a significant step in the handover process, enabling the UE [102] to transition smoothly from the first network system to the second network system while maintaining continuous connectivity and service access.
25
[0085] The mapping unit [204] is communicatively coupled to the transceiver unit [202]. The mapping unit [204] is configured to map the network name identifier with the PDU session ID. After the transceiver unit [202] receives the SM context create response, which includes the PDU session ID, the mapping unit [204] takes
30 the network name identifier obtained from the handover request message and
associates with the corresponding PDU session ID. Based on a clear association between the network name identifier and the PDU session ID, the first network node (such as the AMF [106]) can efficiently manage paging messages, ensuring that they are directed appropriately based on the specific network (e.g., IMS or Data
24

5 DNN) to which the UE [102] is connected. This targeted approach to paging
enhances the overall efficiency of the network, improves paging success rates, and optimizes the use of network resources, especially in scenarios involving handovers between different network systems.
10 [0086] The storing unit [206] is communicatively coupled to the mapping unit
[204]. The storing unit [206] is configured to store, in a repository, the mapping of the network name identifier with the PDU session ID. The repository maintained by the storing unit [206] serves as a database or memory where the mappings of the network name identifier with the PDU session ID with user context are securely
15 stored for future reference. The storing unit [206] enables the first network node
(such as AMF [106]) to efficiently manage and access the session information for the UE [102]. The stored information allows the first network node (such as AMF [106]) to identify the appropriate PDU session ID based on the network name identifier and thereby send paging messages to the UE through the correct network
20 channel. The ability to retrieve this mapping information quickly and accurately
ensures that the network can provide timely and effective paging to the UE [102], enhancing the overall efficiency of the network and the quality of service provided to the user.
25 [0087] The transceiver unit [202] is further configured to transmit differential
paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs. The stored mapping, maintained in a repository by the storing unit [206], provides the necessary information for the transceiver unit [202] to determine the appropriate PDU session ID associated with
30 each network name identifier. When a paging message needs to be sent to the UE
[102], the transceiver unit [202] retrieves the mapping information from the repository and identifies the specific PDU session ID corresponding to the network name identifier for which the paging message is intended. This allows the transceiver unit [202] to send the paging message through the correct network
25

5 channel, ensuring that it reaches the UE [102] efficiently and accurately. The ability
to transmit differential paging based on the network name identifier facilitates in
optimizing network resources and enhancing the quality of service provided to the
user. It enables the network to prioritize paging for certain services, such as IMS
(IP Multimedia Subsystem), by sending paging messages more aggressively, while
10 using a more conservative paging strategy for other services, thereby reducing the
overall load on the Radio Access Network (RAN) [104]. Further, transmitting the differential paging for different network name identifiers involve sending of paging messages to User Equipment(s) [102] via a Radio Access Network (RAN) [104].
15 [0088] FIG. 3A illustrates an exemplary sequence diagram [300] illustrating for
transmitting paging message, in accordance with exemplary embodiments of the present disclosure. As shown in FIG. 3A comprises eNB [302], MME [304], AMF [106] and SMF+PGW-C [306].
20 [0089] At step S1, the process begins with the user equipment (UE) [102]
initiating a handover from the Evolved Packet System (EPS) to the 5th Generation System (5GS). The source eNodeB (eNB) [302] receives the handover necessary signal from the UE [102] and forwards the handover request to the Mobility Management Entity (MME) [304], including the PDN Connection IE which
25 contains the network name identifier.
[0090] Following this, at step S2, the MME [304] processes the handover request and sends a message to the Access and Mobility Management Function (AMF) [106] in the 5GS and the PDN Connection IE from the handover request. 30
[0091] At step S3, the AMF [106] then creates a Session Management (SM) context create request and sends it to the Session Management Function and Packet Data Network Gateway-Control Plane (SMF+PGW-C) [306]. The request includes
26

5 the network name identifier and is a critical step in establishing a new PDU session
for the UE [102] in the 5GS network.
[0092] Upon receipt of this request, at step S4, the SMF+PGW-C [306] generates
a PDU Session ID, which is necessary to manage the UE's session in the new
10 network, and sends a SM context create response back to the AMF [106]. The
response contains the newly created PDU Session ID.
[0093] Finally, at step S5, the AMF [106], with the received PDU Session ID,
maps it to the network name identifier initially obtained from the MME [304]. The
15 mapping is then stored with user context in a repository, which allows the AMF
[106] to later perform differential paging for different network name identifiers, enhancing the network's paging strategy and improving service for the UE [102].
[0094] FIG. 3B illustrates an exemplary sequence diagram [350] illustrating for
20 transmitting paging message, in accordance with exemplary embodiments of the
present disclosure. As shown in FIG. 3B comprises eNB [302], MME [304], AMF [106] and SMF+PGW-C [306].
[0095] At step S1, the Idle Mode Mobility Registration Request such as Tracking
25 Area Update (TAU) Request, is initiated by the User Equipment (UE) [102] from
enode B (eNB) [302] to AMF [106]. The UE [102] is in idle mode and updates its location with the network to maintain continuity of service and ensure that it can be paged correctly.
30 [0096] At step S2, a Context Request is sent by the AMF [106] to the Mobility
Management Entity (MME) [304], to acquire the necessary information for the handover. This includes the current state and session information of the UE [102], which is essential for establishing the UE's context in the new network.
27

5 [0097] Moving to step S3, the MME [304] responds with a Context Response
which contains the Packet Data Network (PDN) connection Information Element (IE). This element includes the Access Point Name (APN) which identifies the data network that the UE [102] wishes to connect to in the 5GS.
10 [0098] At step S4, the Access and Mobility Management Function (AMF) [106]
generates a Session Management Context Create Request towards the Session Management Function and Packet Data Network Gateway-Control Plane (SMF+PGW-C) [306]. This request carries the UE's EPS PDN connections information, signalling the intention to establish a new session management context
15 for the UE [102] in the 5GS.
[0099] At step S5, in response, the SMF+PGW-C [306] returns a Session
Management Context Create Response to the AMF [106]. The response includes
the newly assigned Packet Data Unit (PDU) Session ID, which will be used for
20 managing the data sessions in the 5GS.
[0100] Finally, at step S6, the AMF [106] maps the APN received from the MME
[304] with the PDU Session ID received from the SMF+PGW-C [306]. It then
stores the mapping of the DNN (Data Network Name) versus the PDU Session ID.
25 This mapping is essential for differential paging and session management in the
5GS network.
[0101] Referring to FIG. 4, an exemplary method flow diagram [400], for a
method to transmit paging message, in accordance with exemplary embodiments of
30 the present invention is shown. In an implementation the method [400] is performed
by one of the components of the system [200], or a first network node for example, an AMF [106]. As shown in FIG. 4, the method [400] starts at step [402].
28

5 [0102] According to an embodiment of the present disclosure, when a UE moves
or transitions from EPS to 5GS, the AMF may perform differential paging strategies when the AMF is able to retrieve DNN. Usually, there are two types of EPS to 5GS mobility, for example, EPS to 5GS handover procedure and 5GS to EPS Idle mode mobility procedure.
10
[0103] At step [404], the method [400] comprises receiving, at a first network node, a handover request message for handover of a user equipment (UE) [102] from a first network system to a second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information
15 Element (IE) comprising a network name identifier. In an exemplary aspect, the
first network system is an Evolved Packet System (EPS) and the second network system is a 5th Generation System (5GS). The first network node is an Access and Mobility Management Function (AMF) [106] associated with the second network system. The first network node (such as AMF [106]) comprises the transceiver unit
20 [202], which is configured to receive a handover request message for handover of
a user equipment (UE) [102] from a first network system (such as Evolved Packet System (EPS) to the second network system (such as 5th Generation System (5GS)). The handover request message comprises a Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier. The
25 handover request message is received at the first network node (such as AMF [106])
from a Mobility Management Entity (MME) associated with the first network system (EPS system). In an exemplary aspect, when a UE [102] performs mobility procedure from the first network system to the second network system, a handover request message is sent from the MME to AMF [106] network node. There may be,
30 such as two types of mobility procedure may be possible between the first network
system (EPS system) and the second network system (5GS system): EPS to 5GS handover and EPS to 5GS idle mode mobility handover. The handover request message contains details about the UE's connection, including the PDN connection within forward relocation request IE, which holds the network name identifier. The
29

5 network name identifier allows the network node to identify the specific network
to which the UE is attempting to connect. In an embodiment, the handover request
message is a forward relocation request message to perform a handover of the UE
[102] from the first network system to the second network system. The MME sends
handover request message to the AMF over the N26 interface as part of the EPS to
10 5GS handover procedures. In an exemplary aspect, the forward relocation request
may comprise MME/SGSN (Serving GPRS Support Node)/AMF UE EPS PDN information.
[0104] In an embodiment, the AMF sends handover request message to the MME
15 over the N26 interface as part of the 5GS to EPS handover procedures.
[0105] In another embodiment, the handover request message is an information
element in a context response message to perform idle mode mobility handover
procedure of the UE [102] from the first network system to the second network
20 system. In an exemplary aspect, the context response message may sent as a
response to a previous context request message. The context response message may comprise information of MME/SGSN/AMF UE MM Context.
[0106] At step [406], the method [400] comprises transmitting, by the first
25 network node, a Session Management (SM) context create request to a second
network node associated with the second network system. The transceiver unit
[202] is further configured to transmit a Session Management (SM) context create
request to a second network node (such as Session Management Function and
Packet Data Network Gateway-Control Plane (SMF-PGW-C)) associated with the
30 second network system. Once the transceiver unit [202] has received the handover
request message and extracted the necessary information, it initiates the establishment of a new session management context for the UE [102] in the second network system.
30

5 [0107] The EPS to 5GS idle mode mobility using N26 interface.
[0108] The NF Service Consumer (e.g. AMF [106]) requests the session management function (SMF) [108] to move a UE EPS PDN connection to 5GS using N26 interface. The NF service consumer may send a POST request towards the SMF (+PGW-C) of each UE EPS PDN connection, with the following one or
10 more additional information: UE EPS PDN connection, including the EPS bearer
contexts, received from the MME, representing the individual SM context resource to be created; the pduSessionsActivateList attribute, including the PDU Session ID of all the PDU session(s) to be reactivated; the epsBearerCtxStatus attribute, indicating the status of all the EPS bearer contexts in the UE, if corresponding
15 information is received in the Registration Request from the UE; the
dlDataWaitingInd attribute, indicating that DL data buffered in EPS needs to be forwarded to the UE, if such indication is present in the Context Response received from the MME.
20 [0109] Then the SMF [108] may return a created response including the following
information: PDU Session ID corresponding to the default EPS bearer ID of the EPS PDN connection.
[0110] EPS to 5GS Handover Preparation using N26 interface
25 [0111] The NF Service Consumer (e.g. AMF [106]) may request to the SMF [108]
to handover a UE EPS PDN connection to 5GS system using N26 interface, as
follows:
[0112] The NF Service Consumer s send a POST request, with the following
additional information: UE EPS PDN connection, including the EPS bearer
30 contexts, representing the individual SM context resource to be created.
[0113] The SMF shall return a 201 Created response including the following information: PDU Session ID corresponding to the default EPS bearer ID of the EPS PDN connection.
31

5
[0114] The SM context create request includes details such as the network name
identifier and other relevant information obtained from the handover request
message. The UE EPS PDN connection, includes the EPS bearer contexts, received
from the MME, representing the individual SM context resource to be created. The
10 second network node, upon receiving this request, processes it and creates a new
session management context for the UE, enabling it to access services in the second network system for ensuring a seamless transition for the UE [102] as it moves from one network system to another, maintaining continuity of service and connectivity.
15 [0115] At step [408], the method [400] comprises receiving, at the first network
node, a SM context create response from the second network node, wherein the SM context create response comprises Packet Data Unit (PDU) Session ID. In response to the receiving SM context create request, the SMF shall return a 201 Created response including the following information: PDU Session ID corresponding to
20 the default EPS bearer ID of the EPS PDN connection. After the transceiver unit
[202] has transmitted the SM context create request to the second network node, it awaits a response that confirms the creation of the new session management context and provides the PDU Session ID, which is a unique identifier for the newly established session. The receipt of the SM context create response with the PDU
25 Session ID marks a significant step in the handover process, enabling the UE [102]
to transition smoothly from the first network system to the second network system while maintaining continuous connectivity and service access.
[0116] At step [410], the method [400] comprises mapping, by the first network
30 node, the network name identifier with the PDU session ID. After the transceiver
unit [202] receives the SM context create response, which includes the PDU session ID, the mapping unit [204] takes the network name identifier obtained from the handover request message and associates with the corresponding PDU session ID. Based on a clear association between the network name identifier and the PDU
32

5 session ID, the first network node (such as the AMF [106]) can efficiently manage
paging messages, ensuring that they are directed appropriately based on the specific
network (e.g., IMS or Data DNN) to which the UE [102] is connected. This targeted
approach to paging enhances the overall efficiency of the network, improves paging
success rates, and optimizes the use of network resources, especially in scenarios
10 involving handovers between different network systems.
[0117] At step [412], the method [400] comprises storing, by the first network node in a repository, the mapping of the network name identifier with the PDU session ID. The repository maintained by the storing unit [206] serves as a database
15 or memory where the mappings of the network name identifier with the PDU
session ID with user context are securely stored for future reference. The storing unit [206] enables the first network node (such as AMF [106]) to efficiently manage and access the session information for the UE [102]. The stored information allows the first network node (such as AMF [106]) to identify the appropriate PDU session
20 ID based on the network name identifier and thereby send paging messages to the
UE through the correct network channel. The ability to retrieve this mapping information quickly and accurately ensures that the network can provide timely and effective paging to the UE [102], enhancing the overall efficiency of the network and the quality of service provided to the user.
25
[0118] At step [414], the method [400] comprises transmitting, by the first network node, differential paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs. The stored mapping, maintained in a repository by the storing unit [206], provides the
30 necessary information for the transceiver unit [202] to determine the appropriate
PDU session ID associated with each network name identifier. When a paging message needs to be sent to the UE [102], the transceiver unit [202] retrieves the mapping information from the repository and identifies the specific PDU session ID corresponding to the network name identifier for which the paging message is
33

5 intended. This allows the transceiver unit [202] to send the paging message through
the correct network channel, ensuring that it reaches the UE [102] efficiently and accurately. The ability to transmit differential paging based on the network name identifier facilitates in optimizing network resources and enhancing the quality of service provided to the user. It enables the network to prioritize paging for certain
10 services, such as IMS (IP Multimedia Subsystem), by sending paging messages
more aggressively, while using a more conservative paging strategy for other services, thereby reducing the overall load on the Radio Access Network (RAN) [104]. Further, transmitting the differential paging for different network name identifiers involve sending of paging messages to User Equipment(s) [102] via a
15 Radio Access Network (RAN) [104].
[0119] Thereafter, the method [400] terminates at step [416]
[0120] FIG. 5 illustrates an exemplary block diagram of a computing device [500]
20 (also referred to herein as a computer system [500]) upon which an embodiment of
the present disclosure may be implemented. In an implementation, the computing
device implements the method for transmitting paging message using the system
[200]. In another implementation, the computing device itself implements the
method for transmitting paging message by using one or more units configured
25 within the computing device, wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
[0121] The computing device [500] may include a bus [502] or other
communication mechanism for communicating information, and a processor [504]
30 coupled with bus [502] for processing information. The processor [504] may be, for
example, a general-purpose microprocessor. The computing device [500] may also include a main memory [506], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also
34

5 may be used for storing temporary variables or other intermediate information
during execution of the instructions to be executed by the processor [504]. Such
instructions, when stored in non-transitory storage media accessible to the processor
[504], render the computing device [500] into a special-purpose machine that is
customized to perform the operations specified in the instructions. The computing
10 device [500] further includes a read only memory (ROM) [508] or other static
storage device coupled to the bus [502] for storing static information and instructions for the processor [504].
[0122] A storage device [510], such as a magnetic disk, optical disk, or solid-
15 state drive is provided and coupled to the bus [502] for storing information and
instructions. The computing device [500] may be coupled via the bus [502] to a
display [512], such as a cathode ray tube (CRT), for displaying information to a
computer user. An input device [514], including alphanumeric and other keys, may
be coupled to the bus [502] for communicating information and command
20 selections to the processor [504]. Another type of user input device may be a cursor
controller [516], such as a mouse, a trackball, or cursor direction keys, for
communicating direction information and command selections to the processor
[504], and for controlling cursor movement on the display [512]. This input device
typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second
25 axis (e.g., y), that allow the device to specify positions in a plane.
[0123] The computing device [500] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [500] causes
30 or programs the computing device [500] to be a special-purpose machine.
According to one embodiment, the techniques herein are performed by the computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506]. Such instructions may be read into the main memory [506] from another storage medium,
35

5 such as the storage device [510]. Execution of the sequences of instructions
contained in the main memory [506] causes the processor [504] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
10 [0124] The computing device [500] also may include a communication interface
[518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
15 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [518] 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 [518] sends and receives electrical,
20 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0125] The computing device [500] can send messages and receive data, including program code, through the network(s), the network link [520] and the
25 communication interface [518]. In the Internet example, a server [530] might
transmit a requested code for an application program through the Internet [528], the Internet Service Provider (ISP) [526], the Host [524], the local network [522] attached with the Host [524] (e.g., computer, thin client and multi-functional device) and the communication interface [518]. The received code may be executed
30 by the processor [504] as it is received, and/or stored in the storage device [510], or
other non-volatile storage for later execution.
[0126] FIG. 6 illustrates an exemplary block diagram [600] of a user equipment (UE) [102] for receiving paging messages, in accordance with exemplary
36

5 embodiments of the present disclosure. In an embodiment, the UE [102] comprises
a processor [102A] and a memory [102B].
[0127] As illustrated, the processor [102A] is configured to receive differential paging for different network name identifiers based on the stored mapping between
10 network name identifiers and PDU session IDs, wherein the differential message is
generated based on a handover request message for handover of the UE [102] from a first network system to the second network system, and wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier.
15
[0128] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for transmitting paging message, the instructions include executable code which, when executed by a one or more units of a system, causes: a transceiver unit [202] of the system to receive a handover
20 request message for handover of a user equipment (UE) [102] from a first network
system to the second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier; the transceiver unit [202] of the system to transmit a Session Management (SM) context create request to a second network
25 node associated with the second network system; the transceiver unit [202] of the
system to receive a SM context create response from the second network node, wherein the SM context create response comprises Packet Data Unit (PDU) Session ID; a mapping unit [204] of the system to map the network name identifier with the PDU session ID; a storing unit [206] of the system to store, in a repository, the
30 mapping of the network name identifier with the PDU session ID; and the
transceiver unit [202] of the system to transmit differential paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs.
37

5 [0129] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The
10 functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
15
[0130] As is evident from the above, the present disclosure provides a technically advanced solution for transmitting paging message. With the present solution, even users moving from EPS to 5G can be paged based on DNN. AMF may execute different paging strategies based on DNN name. DNN wise paging is used to
20 improve paging success rate where paging for IMS DNN is done aggressively, as
compared to Data DNN. This aggressive paging strategy for IMS DNN ultimately results in faster call setup when the UE is idle mode. Similarly for Data DNN, AMF can opt to use slower paging strategy and paging messages load can be reduced at NG-RAN. The present solution allows the idle user to be reached and connected
25 quickly and hence call setup time can be reduced to minimum.
[0131] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that
many changes can be made to the embodiments without departing from the
30 principles of the present disclosure. These and other changes in the embodiments
of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
38

We Claim
1. A method to transmit paging message, the method comprising:
receiving, at a first network node, a handover request message for handover of a user equipment (UE) [102] from a first network system to a second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier;
transmitting, by the first network node, a Session Management (SM) context create request to a second network node associated with the second network system;
receiving, at the first network node, a SM context create response from the second network node, wherein the SM context create response comprises Packet Data Unit (PDU) Session ID;
mapping, by the first network node, the network name identifier with the PDU session ID;
storing, by the first network node in a repository, the mapping of the network name identifier with the PDU session ID; and
transmitting, by the first network node, differential paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs.
2. The method as claimed in claim 1, wherein the first network system is an Evolved Packet System (EPS), and the second network system is a 5th Generation System (5GS).
3. The method as claimed in claim 1, wherein the handover request message is received at the first network node from a Mobility Management Entity (MME) associated with the first network system.

4. The method as claimed in claim 1, wherein the first network node is an Access and Mobility Management Function (AMF) [106] associated with the second network system.
5. The method as claimed in claim 1, wherein the second network node corresponds to Session Management Function and Packet Data Network Gateway-Control Plane (SMF-PGW-C).
6. The method as claimed in claim 1, wherein the handover request message is a forward relocation request message to perform a handover of the UE [102] from the first network system to the second network system.
7. The method as claimed in claim 1, wherein the handover request message is a context response message to perform idle mode mobility handover procedure of the UE [102] from the first network system to the second network system.
8. The method as claimed in claim 1, wherein transmitting the differential paging for different network name identifiers involve sending of paging messages to the User Equipment(s) [102] via a Radio Access Network (RAN) [104].
9. A system to transmit paging message, the system comprising:
a first network node of a second network system comprising:
a transceiver unit [202], configured to receive a handover request message for handover of a user equipment (UE) [102] from a first network system to the second network system, wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier;

the transceiver unit [202], configured to transmit a Session Management (SM) context create request to a second network node associated with the second network system;
the transceiver unit [202], configured to receive a SM context create response from the second network node, wherein the SM context create response comprises Packet Data Unit (PDU) Session ID;
a mapping unit [204], configured to map the network name identifier with the PDU session ID;
a storing unit [206], configured to store, in a repository, the mapping of the network name identifier with the PDU session ID; and
the transceiver unit [202], configured to transmit differential paging for different network name identifiers based on the stored mapping between network name identifiers and PDU session IDs.
10. The system as claimed in claim 9, wherein the first network system is an Evolved Packet System (EPS) and the second network system is a 5th Generation System (5GS).
11. The system as claimed in claim 9, wherein the handover request message is received at the first network node from a Mobility Management Entity (MME) associated with the first network system.
12. The system as claimed in claim 9, wherein the first network node is an Access and Mobility Management Function (AMF) associated with the second network system.
13. The system as claimed in claim 9, wherein the second network node corresponds to Session Management Function and Packet Data Network Gateway-Control Plane (SMF-PGW-C).

14. The system as claimed in claim 9, wherein the handover request message is a forward relocation request message to perform a handover of the UE [102] from the first network system to the second network system.
15. The system as claimed in claim 9, wherein the handover request message is a context response message to perform idle mode mobility handover procedure of the UE [102] from the first network system to the second network system.
16. The system as claimed in claim 9, wherein transmitting the differential paging for different network name identifiers involve sending of paging messages to User Equipment(s) [102] via a Radio Access Network (RAN) [104].
17. A user equipment (UE) [102] comprising:
a processor [102A] configured to:
receive differential paging for different network name identifiers based on a stored mapping between network name identifiers and PDU session IDs, wherein
the differential paging message is generated based on a handover request message for handover of the UE [102] from a first network system to a second network system, and wherein the handover request message comprises Packet Data Network (PDN) connection Information Element (IE) comprising a network name identifier.
18. The UE [102] as claimed in claim 17, wherein the differential paging message
is generated based on method performed by claim 1.