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 HANDLING PROTOCOL DATA UNIT RELEASE COMMAND INITIATED FROM SESSION MANAGEMENT
FUNCTION”
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 HANDLING PROTOCOL DATA UNIT RELEASE COMMAND INITIATED FROM SESSION MANAGEMENT
FUNCTION
FIELD OF THE DISCLOSURE
[001] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to methods and systems for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF).
BACKGROUND
[002] 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.
[003] 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. 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 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.

[004] In telecommunications, as a mobile device transitions between plurality of states such as a network connected state and a network idle state, it's crucial for a network to adapt accordingly. When a User Equipment (UE) is in an idle mode, it conserves resources by minimizing its interactions with the network. However, despite being idle, the UE may still need to be responsive to network commands or events.
[005] In scenarios where a Session Management Function (SMF) identifies the need to release certain Protocol Data Unit (PDU), such as in cases of errors or network optimization, it initiates the release process, which also involve releasing of one or more resources to alleviate a network congestion, resolving network errors, or adjusting network configurations. Further an Access and Mobility Management Function (AMF) assists in storing and managing a PDU-Release N1N2 (Non-access Stratum Signaling Connection Setup) message during the UE's idle state serves two primary purposes. Firstly, it ensures that critical network commands, such as PDU releases, are not lost or ignored while the UE is inactive. Secondly, by initiating paging towards the Radio Access Network (RAN) to wake up the UE, the network minimizes delays in executing essential commands, ensuring timely responsiveness.
[006] Upon the UE's transition back to a connected state in response to paging, the network swiftly resumes communication, delivering the pending PDU release message. This approach optimizes network efficiency by allowing the UE to seamlessly transition between states while maintaining responsiveness to network commands. However, the storing of the PDU-Release message by the AMF consumes memory space, thereby posing scalability challenges and potential resource strain, while also failing to entirely mitigate the need for additional signaling, as paging to awaken the UE still incurs signaling overhead. Also, the accumulation of stored messages over time may exacerbate memory management issues may impact network reliability and responsiveness.
[007] Thus, there exists an imperative need in the art to provide a solution that optimise handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF).
OBJECTS OF THE INVENTION

[008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[009] It is an object of the present disclosure to provide a system and a method for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF).
[010] It is another object of the present disclosure to provide a system and method to reduce a memory consumption within the Access and Mobility Management Function (AMF) by eliminating a need to store one or more release messages, thereby improving the scalability and efficiency of the network infrastructure.
[011] It is another object of the present disclosure to provide a system and method for ensuring seamless re-establishment of PDU sessions that were previously marked as out of sync by the AMF.
[012] It is another object of the present disclosure to provide a system and method to improve a network responsiveness by reducing a processing load on the AMF.
[013] It is yet another object of the present disclosure to provide a system and method to minimize signalling overhead by avoiding the necessity for additional signalling to deliver one or mor release commands, leading to more streamlined communication between network nodes and faster response times.
SUMMARY
[014] 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.
[015] An aspect of the present disclosure may relate to a method for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF).

The method comprising receiving, by a transceiver unit at an Access and Mobility Management Function (AMF) module from the SMF, the Protocol Data Unit (PDU) release command associated with a PDU, wherein the PDU release command comprises at least a PDU session id associated with the PDU. The method further comprises initiating, by a paging unit at the AMF to a radio access network (RAN) node, a paging message based on the PDU release command. The method comprising deleting, by a PDU session manager unit, at least a PDU context associated with the PDU session id based on the paging message. The method comprising detecting, by a detection unit at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response. The method comprising receiving, by the transceiver unit at the AMF from the UE, a target request based on the response. The method comprising transmitting, by the transceiver unit at the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE). The method comprising receiving, by the transceiver unit at the AMF from the UE, a PDU session establishment request based on the accept message. The method comprising establishing, by the PDU session manager unit at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
[016] In an exemplary aspect of the present disclosure, the method further comprising receiving, by the transceiver unit at the AMF from the Radio access network (RAN) node, a UE context release request associated with the user equipment (UE). The method further comprising configuring, by the PDU session manager unit at the AMF, a UE idle state associated with the UE based on the UE context release request. The method further comprising detecting, by the PDU session manager unit via the SMF, an error in the UE idle state associated with the at least one PDU.
[017] In an exemplary aspect of the present disclosure, wherein the target request associated with the network is at least one of a mobility request associated with the network, a periodic request associated with the network, a service request associated with the network.

[018] In an exemplary aspect of the present disclosure, wherein the positive response is detected by the detection unit in an event wherein the response associated with the paging message is successfully received from the UE at the AMF, and the negative response is detected by the detection unit in an event wherein the response associated with the paging message is unsuccessfully received from the UE at the AMF.
[019] In an exemplary aspect of the present disclosure, wherein the establishing by the PDU session manager unit the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises: synchronising the UE and at least a target PDU session ID associated with a target PDU session, and wherein synchronising the UE and the target PDU session ID is based on at least one of initiating a Mobile Originated (MO) trigger at the AMF, and receiving a Mobile Terminated (MT) date at the AMF.
[020] In an exemplary aspect of the present disclosure, wherein establishing by the PDU session manager unit the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises: receiving at the AMF from the SMF a Downlink Data Notification (DDN) associated with the target PDU session ID and initiating from the AMF to the UE the paging message based on receiving the DDN.
[021] Another aspect of the present disclosure relates to a system for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF). The system a transceiver unit at an Access and Mobility Management Function (AMF) configured to receive from the SMF, the PDU release command associated with a PDU, wherein the PDU release command comprises at least a PDU session ID associated with the PDU. The system further comprises paging unit connected to at least the transceiver unit, the paging unit configured to initiate to a radio access network (RAN) node, a paging message based on the PDU release command. The system comprises a PDU session manager unit connected to at least the paging unit; the PDU session manager unit configured to delete at least a PDU context associated with the PDU session ID based on the paging message. The system further comprises a detection unit connected to at least the PDU session manager unit, the detection unit is configured to detect, at the AMF from a

user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response. The transceiver unit is further configured to receive, at the AMF from the UE, a target request associa t ed with the netwo rk based on the response. The transceiver unit is further configured to transmit, from the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE). The transceiver unit is further configured to receive, at the AMF from the UE, a PDU session establishment request based on the accept message. The PDU session manager unit is further configured to establish, at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
[022] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instruction for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF). The instructions include an executable code which, when executed by one or more units of the system, causes a transceiver unit to receive from the SMF, a PDU release command associated with a PDU, wherein the PDU release command comprises at least a PDU session ID associated with the PDU, a paging unit connected to at least the transceiver unit, the paging unit configured to initiate to a radio access network (RAN) node, a paging message based on the PDU release command, a PDU session manager unit to delete at least a PDU context associated with the PDU session ID based on the paging message, a detection unit to detect, at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response, the transceiver unit to receive, at the AMF from the UE, a target request associated with the network based on the response, the transceiver unit to transmit, from the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE), the transceiver unit to receive, at the AMF from the UE, a PDU session establishment request based on the accept message, the PDU session manager unit is further configured to establish, at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
BRIEF DESCRIPTION OF DRAWINGS

[023] 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 clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[024] FIG. 1 illustrates an exemplary block diagram [100] representation of 5th generation core (5GC) network architecture.
[025] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] upon which an embodiment of the present disclosure may be implemented.
[026] FIG.3 illustrates an exemplary block diagram of a system [300] for handling a protocol data unit (PDU) release command initiated from a Session Management Function (SMF), in accordance with exemplary embodiments of the present disclosure.
[027] FIG.4 illustrates an exemplary method [400] flow diagram indicating a process for handling a protocol data unit (PDU) release command initiated from a Session Management Function (SMF), in accordance with exemplary embodiments of the present disclosure.
[028] FIG.5 illustrates an exemplary scenario method [500] flow diagram indicating a process for handling a protocol data unit (PDU) release command upon receiving a positive response from a user equipment (UE), in accordance with exemplary embodiments of the present disclosure.
[029] FIG. 6 illustrates an exemplary method [600] flow diagram indicating a process for handling a protocol data unit (PDU) release command upon receiving a negative response from a user equipment (UE), in accordance with exemplary embodiments of the present disclosure.

[030] FIG.7 illustrates an exemplary scenario method [700] flow diagram indicating the process for handling a protocol data unit (PDU) release command upon receiving a negative response from a user equipment (UE), in accordance with exemplary embodiments of the 5 present disclosure.
[031] FIG.8 illustrates exemplary scenario signal flow [800] diagram indicating the method for handling a protocol data unit (PDU) release command initiated from a Session Management Function (SMF), in accordance with exemplary embodiments of the present 10 disclosure.
[032] The foregoing shall be more apparent from the following more detailed description of the disclosure.
15 DETAILED DESCRIPTION
[033] 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
20 may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address 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
25 the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[034] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the 30 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.
9

[035] 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
5 invention or imply any specific functionality or 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
[036] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as
15 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.
20 [037] 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. A process is terminated when its operations are
25 completed but could have additional steps not included in a figure.
[038] 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 30 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
10

words are used in either the 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.
5 [039] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers 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
10 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 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,
15 smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, 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.
20 [040] Further, the user device may also comprise a “processor” or “processing 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,
25 a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
30
[041] One or more modules, units, components (including but not limited to paging unit, PDU session manager unit, and processing unit) used herein may be software modules configured via hardware modules/processor, or hardware processors, the processors being
11

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, Field Programmable Gate Array circuits, any other type of integrated 5 circuits, etc.
[042] 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 10 communications, the dynamic advancement of various generations of cellular technology are also seen. The 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.
15 [043] Radio Access Technology (RAT) refers to the technology used by mobile 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
20 techniques, and other parameters used for 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
25 capabilities. 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.
[044] As discussed in the background section, in telecommunications, as a mobile device 30 transitions between connected and idle states, network adaptation is essential. While in idle mode, User Equipment (UE) conserves resources but remains responsive to network commands. When the Session Management Function (SMF) identifies the need to release certain Protocol Data Units (PDUs) for reasons like errors or network optimization, it
12

initiates the release process, involving resource freeing for congestion alleviation or error resolution. The Access and Mobility Management Function (AMF) assists by storing and managing PDU-Release N1N2 messages during UE idle states, ensuring critical commands are not lost and minimizing delays by paging the UE via the Radio Access Network (RAN)
5 for prompt responsiveness. Upon UE transition to a connected state, pending PDU release messages are swiftly delivered, optimizing network efficiency. However, storing PDU-Release messages consumes memory space, posing scalability challenges and failing to entirely eliminate the need for additional signalling, potentially impacting network reliability and responsiveness due to memory management issues over time.
10
[045] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by sending PSS (Protocol Data Unit (PDU) Session Status) IE in a registration and/or a service accept. Initially, a transceiver unit receives a Protocol Data Unit (PDU) release command from the Session Management Function
15 (SMF), containing crucial information such as a PDU session ID. Subsequently, a paging unit initiates a paging message to a Radio Access Network (RAN) node based on this command. Upon detecting a response from the User Equipment (UE), a PDU session manager unit proceeds to delete a relevant PDU context and receives a target request from a user equipment (UE). An accept message, containing an updated out-of-sync PDU
20 Session Status Information Element (PSS IE), is then transmitted to the UE. Upon receiving a PDU session establishment request from the UE, the PDU session manager unit establishes a PDU session based on this request and the updated PSS IE, thereby ensuring efficient PDU session management and synchronization between one or more network components.
25
[046] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[047] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core 30 (5GC) network architecture, in accordance with exemplary embodiment of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a
13

Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function 5 (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 connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
10 [048] The User Equipment (UE) [102] interfaces with the network via the Radio Access Network (RAN) [104]; the Access and Mobility Management Function (AMF) [106] manages connectivity and mobility, while the Session Management Function (SMF) [108] administers session control; the service communication proxy (SCP) [110] routes and manages communication between network services, enhancing efficiency and security, and
15 the Authentication Server Function (AUSF) [112] handles user authentication; the Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] for integrating the 5G core 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
20 customization, secure interfacing with external applications, and maintain network function registries respectively; the Policy Control Function (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
25 to external internet resources; collectively, these components are designed to enhance mobile broadband, ensure low-latency communication, and support massive machine-type communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
30 [049] 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 different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
14

[050] 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 5 handovers and paging.
[051] 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 10 and handles IP address allocation and QoS enforcement.
[052] 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
[053] 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 [054] 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 [055] 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.
[056] Network Exposure Function (NEF) [118] is a network function that exposes 30 capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
15

[057] 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.
5 [058] 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.
[059] Unified Data Management (UDM) [124] is a network function that centralizes 10 the management of subscriber data, including authentication, authorization, and subscription information.
[060] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and 15 services.
[061] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
20 [062] 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.
[063] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also 25 referred herein as computing system [1000]) upon which an embodiment of the present disclosure may be implemented. In an implementation, the computing device [1000] may also implement a method for handling a protocol data unit (PDU) release command initiated from a Session Management Function (SMF), utilising the system. In another implementation, the computing device [1000] itself implements the method for handling 30 the protocol data unit (PDU) release command initiated from the Session Management Function (SMF) using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
16

[064] The computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with the bus [1002] for processing information. The hardware processor [1004] may be, for
5 example, a general purpose microprocessor. The computing device 1000] may also include a main memory [1006], such as a random access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be
10 executed by the processor [1004]. Such instructions, when stored in non-transitory storage media accessible to the processor [1004], render the computing device [1000] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information
15 and instructions for the processor [1004].
[065] 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
20 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], 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
25 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]. 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.
30
[066] 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 which in combination with the computing device [1000] causes or programs
17

the computing device [1000] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the
5 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
[067] 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]. The local network [1022] is further connected to a host [1024]. For example, the
15 communication interface [1018] may be an integrated services digital network (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
20 implementation, the communication interface [1018] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.
[068] The computing device [1000] can send messages and receive data, including 25 program code, through the network(s), the network link [1020] and the communication interface [1018]. In the Internet example, a server [1030] might transmit a requested code for an application program through the Internet [1028], the ISP [1026], the local network [1022], the Host [1024] 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 30 [1010], or other non-volatile storage for later execution.
[069] Referring to FIG. 3, illustrates an exemplary block diagram of a system [300] for handling a protocol data unit (PDU) release command initiated from a Session Management
18

Function (SMF), in accordance with exemplary embodiments of the present disclosure. The system [300] comprises at least one transceiver unit [302], at least one paging unit [304], at least one PDU session manager unit [306] and a detection unit [308]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless
5 otherwise indicated below. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. For ease of reference, FIG. 3 depicts units/components of the system [300] by way of representation of blocks and FIG. 3 do not represent the internal circuitry or connections
10 of each component/unit of the system [300]. It will be appreciated by those skilled in the art that disclosure of such drawings/block diagrams includes disclosure of electrical components and connections between said electronic components, and electronic components or circuitry commonly used to implement such components.
15 [070] Additionally, the paging unit [304], the PDU session manager unit [306] and the detection unit [308] are processors. 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 (digital signal processor) core, a controller, a microcontroller, Application Specific Integrated Circuits,
20 Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
[071] The system [300] is configured to handle the PDU release command initiated from the Session Management Function (SMF), with the help of the interconnection between the components/units of the system [300].
25
[072] 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
30 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
19

the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[073] In order to handle the PDU release command initiated from the Session 5 Management Function (SMF), the transceiver unit [302] at an Access and Mobility Management Function (AMF) configured to receive from the SMF, the PDU release command associated with a PDU, wherein the PDU release command comprises at least a PDU session ID associated with the PDU.
10 [074] A PDU release command refers to a directive sent within a telecommunications network to release or terminate a Protocol Data Unit (PDU) session. The PDU release command is typically initiated by a network component, such as the Session Management Function (SMF), in response to various conditions such as errors, network optimization, or user actions. The PDU release command contains an essential information needed to
15 identify a specific PDU session that needs to be released, including a PDU session ID associated with a PDU. Once received, the network components involved in the PDU session release process take appropriate actions to terminate the PDU session, free up resources, and update relevant network states accordingly.
20 [075] The PDU session ID, or Protocol Data Unit session ID, is a unique identifier assigned to a specific PDU session within a telecommunications network.
[076] Further, upon receiving the PDU release command, the paging unit [304] at the AMF, which is connected at least with the transceiver unit [302] is configured to initiate to 25 a radio access network (RAN) RAN node, a paging message based on the PDU release command.
[077] For example, the paging message serves to awaken a user equipment (UE), prompting it to transition from an idle state to a connected state so that subsequent actions, 30 such as releasing the PDU session, may be executed. The RAN node plays a role in delivering the paging message to a target UE.
20

[078] Thereafter, the PDU session manager unit [306] at the AMF, which is connected to at least the paging unit [304], is configured to delete at least a PDU context associated with the PDU session ID based on the paging message.
5 [079] The PDU context refers to the set of parameters and information maintained by one or more network elements to manage the communication session associated with a Protocol Data Unit (PDU) session. The set of parameters includes various details such as the PDU session ID, a Quality of Service (QoS) requirements, a security association, and a ro u t i ng i nf or ma tio n nece ss ar y f or a p ro p e r tr a ns m i ssi o n a nd h a n dling of data packets within
10 a session.
[080] Further, the detection unit [308] at the AMF, which may be connected to at least with the PDU session manager unit [306], is configured to detect, at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is 15 one of a positive response and a negative response.
[081] The present disclosure encompasses that the positive response is detected by detection unit [308] in an event wherein the response associated with the paging message is successfully received from the UE at the AMF, and the negative response is detected by 20 the detection unit [308] in an event wherein the response associated with the paging message is unsuccessfully received from the UE at the AMF.
[082] Furthermore, the transceiver unit [302] is further configured to receive, at the AMF from the UE, a target request associated with the network based on the response. 25
[083] The present disclosure encompasses that the target request associated with the network is at least one of a mobility request associated with the network, a periodic request associated with the network, a service request associated with the network.
30 [084] For example, the target request refers to a request direct towards a specific requirement within a network infrastructure such as a mobility request, a periodic request, and a service request.
21

[085] The transceiver unit [302] is further configured to transmit, from the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE).
5 [086] The updated out of sync PDU session status IE (PSS IE) refers to an Information Element (IE) which indicates that the PSS IE has been adjusted to reflect the current status of the PDU session.
[087] The transceiver unit [302] is further configured to receive, at the AMF from the 10 UE, a PDU session establishment request based on the accept message.
[088] The PDU session manager unit [306] is further configured to establish, at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
15
[089] For instance, the PDU session establishment request may be a message sent by the User Equipment (UE) to the network to initiate the creation of a new data session. The message may include one or more essential details such as the type of service required and quality of service preferences.
20
[090] The present disclosure encompasses that the transceiver unit [302] is further configured to receive from the Radio access network (RAN) node, a UE context release request associated with the user equipment (UE). The PDU session manager unit [306] is further configured to configure a UE idle state associated with the UE based on the UE
25 context release request. The PDU session manager unit [306] is further configured to detect via the SMF, an error in the UE idle state associated with the at least one PDU.
[091] The present disclosure encompasses that the PDU session manager unit [306] configured to establish the PDU session based on the PDU session establishment request 30 and the updated out of sync PSS IE in an event the negative response is detected further comprises the PDU session manager unit [306] configured to synchronise the UE and at least a target PDU session ID associated with a target PDU session, and wherein the UE and the target PDU session IDis synchronised based on at least one of a Mobile Originated
22

(MO) trigger initiated at the AMF, and a Mobile Terminated (MT) date received at the AMF.
[092] The present disclosure encompasses that the MO is a message sent to from a user 5 device to another user device or a network operator that may be associated with the said user device. The MT is a message that originates from a network operator that may be associated with a user device and is transmitted at said user device.
[093] The present disclosure encompasses that the PDU session manager unit [306] is 10 configured to establish the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises at least the PDU session manager unit [306] configured to receive at the AMF from the SMF a Downlink Data Notification (DDN) associated with the target P DU s ession ID, and the paging unit [304] configured to initiate from the AMF to the UE the paging 15 message based on receiving the DDN.
[094] The DDN is a message sent from the network to the User Equipment (UE) to indicate that downlink data is available for delivery. In other words, it notifies the UE that there is data waiting to be received from the network. Moreover, the downlink data refers 20 to data sent from the network to the UE, such as web pages, videos, or messages. The DDN serves as a trigger for the UE to wake up from an idle state or to be prepared to receive data, ensuring efficient utilization of network resources and timely delivery of data to the UE.
25 [095] For instance, when the network has data to send to the UE, it sends a DDN to inform the UE that data is forthcoming. Upon receiving the DDN, the UE can then initiate the necessary actions to receive and process the data, such as waking up from a low-power mode or activating the appropriate communication protocols. This ensures that the UE promptly receive the data from the network, contributing to a seamless user experience and
30 efficient data delivery.
[096] Referring to FIG. 4, illustrates an exemplary method [400] flow diagram indicating a process for handling a protocol data unit (PDU) release command initiated from a Session
23

Management Function (SMF), in accordance with exemplary embodiments of the present disclosure. In an implementation the method [400] is performed by the system [300]. Also, as shown in FIG. 4, the method [400] starts at step [402].
5 [097] At step [404], the method [400] as disclosed by the present disclosure comprises receiving, by a transceiver unit [302] at an Access and Mobility Management Function (AMF) from the SMF, the Protocol Data Unit (PDU) release command associated with a PDU, wherein the PDU release command comprises at least a PDU session ID associated with the PDU.
10
[098] A PDU release command refers to a directive sent within a telecommunications network to release or terminate a Protocol Data Unit (PDU) session. The PDU release command is typically initiated by a network component, such as the Session Management Function (SMF), in response to various conditions such as errors, network optimization, or
15 user actions. The PDU release command contains an essential information needed to identify a specific PDU session that needs to be released, including a PDU session ID associated with a PDU. Once received, the network components involved in the PDU session release process take appropriate actions to terminate the PDU session, free up resources, and update relevant network states accordingly.
20
[099] The PDU session ID, or Protocol Data Unit session ID, is a unique identifier assigned to a specific PDU session within a telecommunication network.
[100] Next, at step [406], the method [400] as disclosed by the present disclosure 25 comprises initiating, by a paging unit [304] at the AMF to a radio access network (RAN) node, a paging message based on the PDU release command.
[101] At step [408], the method [400] as disclosed by the present disclosure comprises deleting, by a PDU session manager unit [306], at least a PDU context associated with the 30 PDU session ID based on the paging message.
[102] The PDU context refers to the set of parameters and information maintained by one or more network elements to manage the communication session associated with a
24

Protocol Data Unit (PDU) session. The set of parameters includes various details such as the PDU session ID, a Quality of Service (QoS) requirements, a security association, and a ro u t i ng i nf or ma tio n nece ss ar y f or a p ro p e r tr a ns m i ssi o n a nd h a n dling of data packets within a session.
5
[103] At step [410], the method [400] as disclosed by the present disclosure comprises detecting, by a detection unit [308] at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response.
10
[104] The present disclosure encompasses that the positive response is detected by the detection unit [308] in an event wherein the response associated with the paging message is successfully received from the UE at the AMF, and the negative response is detected by the detection unit [308] in an event wherein the response associated with the paging
15 message is unsuccessfully received from the UE at the AMF.
[105] At step [412], the method [400] as disclosed by the present disclosure comprises -receiving, by the transceiver unit [302] at the AMF from the UE, a target request based on the response. 20
[106] For example, the target request refers to a request direct towards a specific requirement within a network infrastructure such as a mobility request, a periodic request, and a service request.
25 [107] The present disclosure encompasses that the target request associated with the network is at least one of a mobility request associated with the network, a periodic request associated with the network, a service request associated with the network.
[108] At step [414], the method [400] as disclosed by the present disclosure comprises 30 transmitting, by the transceiver unit [302] at the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE);
25

[109] The updated out of sync PDU session status IE (PSS IE) refers to an Information Element (IE) which indicates that the PSS IE has been adjusted to reflect the current status of the PDU session.
5 [110] At step [416], the method [400] as disclosed by the present disclosure comprises receiving, by the transceiver unit [302] at the AMF from the UE, a PDU session establishment request based on the accept message.
[111] For instance, the PDU session establishment request may be a message sent by the 10 User Equipment (UE) to the network to initiate the creation of a new data session. The message may include one or more essential details such as the type of service required and quality of service preferences.
[112] At step [418], the method [400] as disclosed by the present disclosure comprises 15 establishing, by the PDU session manager unit [306] at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
[113] The present disclosure encompasses that the method further comprising establishing by the PDU session manager unit [306] the PDU session based on the PDU
20 session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises: synchronising the UE and at least a target PDU session ID associated with a target PDU session, and wherein synchronising the UE and the target PDU session ID is based on at least one of initiating a Mobile Originated (MO) trigger at the AMF, and receiving a Mobile Terminated (MT) date at the AMF.
25
[114] The present disclosure encompasses that the method further comprising establishing by the PDU session manager unit [306], the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises: receiving at the AMF from the SMF a Downlink
30 Data Notification (DDN) associated with the target PDU session ID, and initiating from the AMF to the UE the paging message based on receiving the DDN.
26

[115] The DDN is a message sent from the network to the User Equipment (UE) to indicate that downlink data is available for delivery. In other words, it notifies the UE that there is data waiting to be received from the network. Moreover, the downlink data refers to data sent from the network to the UE, such as web pages, videos, or messages. The DDN 5 serves as a trigger for the UE to wake up from an idle state or to be prepared to receive data, ensuring efficient utilization of network resources and timely delivery of data to the UE.
[116] For instance, when the network has data to send to the UE, it sends a DDN to 10 inform the UE that data is forthcoming. Upon receiving the DDN, the UE can then initiate the necessary actions to receive and process the data, such as waking up from a low-power mode or activating the appropriate communication protocols. This ensures that the UE promptly receive the data from the network, contributing to a seamless user experience and efficient data delivery. 15
[117] The present disclosure encompasses receiving, by the transceiver unit [302] at the AMF from the Radio access network (RAN) node, a UE context release request associated with the user equipment (UE).
20 [118] The present disclosure encompasses configuring, by the PDU session manager unit [306] at the AMF, a UE idle state associated with the UE based on the UE context release request.
[119] The present disclosure encompasses detecting, by the PDU session manager unit 25 [306] via the SMF, an error in the UE idle state associated with the at least one PDU.
[120] Thereafter, the method [400] terminates at step [420].
[121] Referring to FIG. 5, illustrates an exemplary scenario method [500] flow diagram 30 indicating a process for handling a protocol data unit (PDU) release command upon receiving a positive response from a user equipment (UE), in accordance with exemplary embodiments of the present disclosure is shown. In an implementation the method [500] is performed by the system [300]. As shown in FIG. 5, the method [500] starts at step [502].
27

[122] At step [504], the method [500] as disclosed by the present disclosure comprises of detecting, by a detection unit [308], a UE idle associated with the UE based on UE context release request state of the UE.
5
[123] Next, at step [506], the method [500] as disclosed by the present disclosure comprises initiating, by a PDU session manager unit [306], a PDU Release session command wherein the PDU release session command comprises of at least a PDU session ID and a PDU Session context.
10
[124] Next, at step [508], the method [500] as disclosed by the present disclosure comprises deleting, by the PDU session manager unit [306], at least the PDU session context associated with the PDU session ID.
15 [125] Next, at step [510], the method [500] as disclosed by the present disclosure comprises initiating, by the paging unit [304], a paging message to the UE.
[126] Next, at step [512], the method [500] as disclosed by the present disclosure comprises initiating, by the PDU session manager unit [306], a connection at the UE,
20 wherein the connection is based on at least one of a Mobility Request (MR) and a Periodic Request (PR) and a Service Request (SR) procedure based on a positive response from the UE. In an implementation, the connection is initiated at the UE via an Access and Mobility Management Function (AMF) associated with the network, wherein the connection is based on at least one of the Mobility Request (MR) and the Periodic Request (PR) and the
25 Service Request (SR) procedure associated with the AMF that is network.
[127] Next, at step [514], the method [500] as disclosed by the present disclosure comprises detecting, by the detection unit [308], a response associated with the paging message wherein the response is one of a positive response or a negative response. 30
[128] Next, at step [516], the method [500] as disclosed by the present disclosure comprises generating by the PDU session manager unit [306] an updated PSS list wherein
28

the updated PSS list is based on the received Mobility Request (MR) and/or the Periodic Request (PR) and/or Service Request (SR) procedure response.
[129] Thereafter, the method [500] terminates at step [518].
5
[130] Referring to FIG. 6, illustrates an exemplary method [600] flow diagram indicating a process for handling a protocol data unit (PDU) release command upon receiving a negative response from a user equipment (UE), in accordance with exemplary embodiments of the present disclosure. The method [600] is implemented after step [510]
10 of the method [500] depicted in FIG. 5.
[131] The method [600] initiates at [602].
[132] At step [604], the method further comprises synchronization, by the PDU session 15 manager unit [306], of the UE for other PDU session ID, wherein the synchronization is based on initiating a Mo signal, that is triggered after receiving the negative response from the UE.
[133] At step [606], the method further comprises receiving, by the transceiver unit [302] 20 from the UE, at least one of a Mobility Request, a Periodic Request, and a Service Request, wherein the Mobility Request, the Periodic Request and the Service Request may be associated with pending signalling or data.
[134] At step [608], the method further comprises transmitting, by the transceiver unit 25 [302] to the UE, at least one of a registration accept and a service accept with the updated PSS (PDU session status). In an implementation of the present solution, the updated PSS is used since the AMF has already deleted the PDU session ID from the user context.
[135] At step [610], the method further comprises receiving, by the transceiver unit [302] 30 from UE, a PDU session establishment request after receiving an out of sync PSS (PDU Session Status) IE.
[136] The method [600] terminates at step [612].
29

[137] Referring to FIG. 7, illustrates an exemplary scenario method [700] flow diagram indicating the process for handling a protocol data unit (PDU) release command upon receiving a negative response from a user equipment (UE), in accordance with exemplary 5 embodiments of the present disclosure. The method [700] is implemented upon step [410] of the method [400] depicted in FIG. 4.
[138] The method [700] initiates at step [702].
10 [139] At step [704], the method comprising synchronizing, by the PDU session manager unit [306], of the UE for other PDU session ID, wherein the synchronization is based on receiving a Mt data and triggered upon receiving the negative response from UE.
[140] At step [706], the method comprising receiving, by the transceiver unit [302] from 15 SMF, a Downlink Data Notification (DDN) for other PDU session ID.
[141] At step [708], the method further comprising initiating, by the paging unit [304] to UE, a paging message. In an implementation of the present solution, the paging message is initiated towards ran to wake the UE. 20
[142] At step [710], the method further comprising receiving, by the transceiver unit [302] from UE, at least one of a Mobility Request, a Periodic Request, and a Service Request in response of the paging message.
25 [143] At step [712], the method further comprising transmitting, by the transceiver unit [302] to the UE, one of a registration accept and a service accept with the updated PSS (PDU session status). In an implementation of the present solution, the updated PSS is used since the AMF has already deleted the PDU session ID from the user context.
30 [144] At step [714], the method further comprising receiving, by the transceiver unit [302] from UE, a PDU session establishment request after receiving out of sync PSS (PDU Session Status) IE.
30

[145] The method [700] terminates at step [712].
[146] Referring to FIG. 8, exemplary scenario signal flow [800] diagram indicating the method for handling a protocol data unit (PDU) release command initiated from a Session 5 Management Function (SMF), in accordance with exemplary embodiments of the present disclosure is shown. Further, the signal flow [500] as indicated in figure 8 diagram may be implemented by the system [300] in accordance with the various embodiments of the present disclosure.
10 [147] At step S1, the SMF initiates a Protocol Data Unit (PDU) release command associated with a specific PDU.
[148] At step S2, a transceiver unit [302] receives the PDU release command from the SMF. The PDU release command includes a PDU session ID. 15
[149] At step S3, a paging unit [304] generates a paging message to a Radio Access Network (RAN) node based on the received PDU release command.
[150] At step S4, a PDU session manager unit [306] deletes a PDU context associated 20 with the PDU session ID based on the paging message.
[151] Also, a response associated with the paging message is detected via a detection unit [308] by the transceiver unit [302] at the AMF from the UE, wherein the response is one of a positive response and a negative response. Additionally, a target request based on the 25 response is received by the transceiver unit [302] at the AMF from the UE.
[152] At step S5, the transceiver unit [302] sends an accept message to the UE, including an updated out-of-sync PDU session status Information Element (IE).
30 [153] At step S6, the transceiver unit [302] receives a PDU session establishment request from the UE based on the accept message.
31

[154] At step S7, the PDU session manager unit [306] establishes a new PDU session based on the received PDU session establishment request and the updated out-of-sync PDU session status IE.
5 [155] The method and system for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF) of the present disclosure may be implemented in a telecommunication network. For instance, a mobile phone (i.e. a user equipment (UE) is connected to a 5G network, and a user of the mobile phone is streaming a video and the network encounters an issue that requires termination of a data session,
10 then the network's Session Management Function (SMF) detects the issue and sends a command (i.e. PDU release command) to the Access and Mobility Management Function (AMF), indicating the need to end the data session. This command includes one or more details like session ID. Thereafter, the paging unit [304] initiates a paging message to a nearby radio access network (RAN) node. Upon receiving the paging message, the PDU
15 session manager deletes the data session (i.e. PDU context) for addressing the network issue. Thereafter, a response is received by the mobile phone which may be a positive response or a negative response. In case the positive response is received that a request from the mobile device is received for re-connection. Thereafter a message to the mobile phone is transmitted for confirming the re-connection and in response the mobile phone
20 transmits a request to establish a new data session with the network. Further, the PDU session manager unit [306] sets up a new data session based on the request received from the mobile phone. Thereby, ensuring a seamless reconnection process.
[156] The present disclosure may relate to a non-transitory computer readable storage 25 medium storing instruction for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF). The instructions include an executable code which, when executed by one or more units of the system, causes a transceiver unit [302] of the system at an Access and Mobility Management Function (AMF) to receive from the SMF, the PDU release command associated with a PDU, 30 wherein the PDU release command comprises at least a PDU session ID associated with the PDU; a paging unit [304] of the system at the AMF, to initiate to a radio access network (RAN) node, a paging message based on the PDU release command ;a PDU session manager unit [306] of the system at the AMF, to delete at least a PDU context associated
32

with the PDU session ID based on the paging message; a detection unit [308] of the system at the AMF, to detect, at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response; the transceiver unit [302] to receive, at the AMF from the UE, a target request associated with the network based on the response, transmit, from the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE), receive, at the AMF from the UE, a PDU session establishment request based on the accept message; and the PDU session manager unit [306] to establish, at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
[157] As is evident from the above, the present disclosure provides a technically advanced solution for handling a Protocol Data Unit (PDU) release command initiated from a Session Management Function (SMF) which reduce memory consumption within the Access and Mobility Management Function (AMF) by eliminating a need to store one or more release messages, thereby improving the scalability and efficiency of the network infrastructure. Also, the method and system of the present disclosure ensures a seamless re-establishment of PDU sessions that were previously marked as out of sync by the AMF, which improve network responsiveness by reducing a processing load on the AMF. The present solution minimizes overhead signaling by avoiding the necessity for additional signaling to deliver one or mor release commands, leading to more streamlined communication between network nodes and faster response times.
[158] 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 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.

We claim:
1. A method [300] for handling a Protocol Data Unit (PDU) release command
initiated from a Session Management Function (SMF), the method comprising:
- receiving, by a transceiver unit [302] at an Access and Mobility Management Function (AMF) from the SMF, the Protocol Data Unit (PDU) release command associated with a PDU, wherein the PDU release command comprises at least a PDU session ID associated with the PDU;
- initiating, by a paging unit [304] at the AMF to a radio access network (RAN) node, a paging message based on the PDU release command;
- deleting, by a PDU session manager unit [306], at least a PDU context associated with the PDU session ID based on the paging message;
- detecting, by a detection unit [308] at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response;
- receiving, by the transceiver unit [302] at the AMF from the UE, a target request based on the response;
- transmitting, by the transceiver unit [302] at the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE);
- receiving, by the transceiver unit [302] at the AMF from the UE, a PDU session establishment request based on the accept message; and
- establishing, by the PDU session manager unit [306] at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
2. The method as claimed in claim 1, wherein the method further comprising:
- receiving, by the transceiver unit [302] at the AMF from the Radio access network (RAN) node, a UE context release request associated with the user equipment (UE);
- configuring, by the PDU session manager unit [306] at the AMF, a UE idle state associated with the UE based on the UE context release request; and

- detecting, by the PDU session manager unit [306] via the SMF, an error in the UE idle state associated with the at least one PDU.
3. The method as claimed in claim 1, wherein the target request associated with a network is at least one of a mobility request associated with the network, a periodic request associated with the network, a service request associated with the network.
4. The method as claimed in claim 1, wherein the positive response is detected by the detection unit [308] in an event wherein the response associated with the paging message is successfully received from the UE at the AMF, and the negative response is detected by the detection unit [308] in an event wherein the response associated with the paging message is unsuccessfully received from the UE at the AMF.
5. The method as claimed in claim 1, wherein the establishing by the PDU session manager unit [306], the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises:
. synchronising the UE and at least a target PDU session ID associated with a target PDU session, and wherein synchronising the UE and the target PDU session ID is based on at least one of initiating a Mobile Originated (MO) trigger at the AMF and receiving a Mobile Terminated (MT) date at the AMF.
6. The method as claimed in claim 5, wherein the establishing by the PDU session
manager unit [306], the PDU session based on the PDU session establishment
request and the updated out of sync PSS IE in an event the negative response is
detected further comprises:
. receiving at the AMF from the SMF a Downlink Data Notification (DDN) associated with the target PDU session ID, and initiating from the AMF to the UE the paging message based on receiving the DDN.
7. A system for handling a Protocol Data Unit (PDU) release command initiated from
a Session Management Function (SMF), the system comprises:
o a transceiver unit [302] at an Access and Mobility Management Function (AMF) configured to receive from the SMF, the PDU release

command associated with a PDU, wherein the PDU release command comprises at least a PDU session ID associated with the PDU;
o a paging unit [304] at the AMF, connected to at least the transceiver unit [302], the paging unit [304] configured to initiate to a radio access network (RAN) node, a paging message based on the PDU release command;
o a PDU session manager unit [306] at the AMF, connected to at least the paging unit [304], the PDU session manager unit [306] configured to delete at least a PDU context associated with the PDU session ID based on the paging message;
o a detection unit [308] at the AMF, connected to at least the PDU session manager unit [306], the detection unit [308] is configured to detect, at the AMF from a user equipment (UE), a response associated with the paging message, wherein the response is one of a positive response and a negative response;
wherein the transceiver unit [302] is further configured to:
. receive, at the AMF from the UE, a target request associated with the
network based on the response; . transmit, from the AMF to the UE, an accept message associated with the target request, wherein the accept message at least comprises an updated out of sync PDU session status IE (PSS IE); . receive, at the AMF from the UE, a PDU session establishment request based on the accept message; and wherein the PDU session manager unit [306] is further configured to:
. establish, at the AMF, a PDU session based on the PDU session establishment request and the updated out of sync PSS IE.
8. The system as claimed in claim 7 wherein the system further comprising:
- the transceiver unit [302] is further configured to receive from the Radio access network (RAN) node, a UE context release request associated with the user equipment (UE);

- the PDU session manager unit [306] is further configured to configure a UE idle state associated with the UE based on the UE context release request; and
- the PDU session manager unit [306] is further configured to detect via the SMF, an error in the UE idle state associated with the at least one PDU.

9. The system as claimed in claim 7, wherein the target request associated with the network is at least one of a mobility request associated with the network, a periodic request associated with the network, a service request associated with the network.
10. The system as claimed in claim 7, wherein the positive response is detected by detection unit [308] in an event wherein the response associated with the paging message is successfully received from the UE at the AMF, and the negative response is detected by the detection unit [308] in an event wherein the response associated with the paging message is unsuccessfully received from the UE at the AMF.
11. The system as claimed in claim 7, wherein the PDU session manager unit [306] configured to establish the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises the PDU session manager unit [306] configured to synchronise the UE and at least a target PDU session ID associated with a target PDU session, and wherein the UE and the target PDU session IDis synchronised based on at least one of a Mobile Originated (MO) trigger initiated at the AMF, and a Mobile Terminated (MT) date received at the AMF.
12. The system as claimed in claim 11, wherein the PDU session manager unit [306] is configured to establish the PDU session based on the PDU session establishment request and the updated out of sync PSS IE in an event the negative response is detected further comprises at least the PDU session manager unit [306] configured to receive at the AMF from the SMF a Downlink Data Notification (DDN) associated with the target PDU session ID, and the paging unit [304] configured to initiate from the AMF to the UE the paging message based on receiving the DDN.