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 INITIATING A
DEREGISTRATION AT AN ACCESS AND MOBILITY
MANAGEMENT FUNCTION (AMF) UNIT”
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 INITIATING A DEREGISTRATION AT AN ACCESS AND MOBILITY MANAGEMENT FUNCTION (AMF) UNIT
CROSS-REFERENCE
[0001] The present disclosure takes priority from Indian Patent Application
No. 202321060033 filed on 6th September 2023, and Indian Patent Application No. 202321060042 filed on 6th September 2023.
TECHNICAL FIELD
[0002] Embodiments of the present disclosure generally relate to wireless
communication. More particularly, embodiments of the present disclosure relate to methods and systems for initiating a deregistration at an Access and Mobility Management Function (AMF).
BACKGROUND
[0003] The following description of the related art is intended to provide
background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0004] 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. 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.
[0005] In some cases, when an access and mobility management function
(AMF) is concurrently managing an ongoing emergency Packet Data Unit (PDU) session, a non-emergency registration, and a Unified Data Management (UDM) deregistration request marked with the reason of subscription withdrawal, a complex problem arises. The problem emerges in determining the appropriate course of action when these concurrent activities coincide. On one hand, releasing the emergency PDU session and deregistering the user from the network might be necessary, but this may conflict with the ongoing emergency session. Conversely, if the emergency PDU session is terminated and no subsequent requests are initiated by a User Equipment (UE), there is ambiguity regarding how to proceed with the network registration status of the user. Thus, there exists an imperative need in the art for managing registration of the UE at the AMF.
OBJECTS OF THE 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 a system and a method
for initiating a deregistration of a user equipment (UE) at an Access and Mobility Management Function (AMF).

[0008] It is another object of the present disclosure to provide a solution that
detects the UDM deregistration request comprises at least a deregistration request reason as a subscription withdrawn status associated with the network.
[0009] It is another object of the present disclosure to provide a solution that
detects that the UDM deregistration request comprises a re-registration request associated with the network.
[0010] It is yet another object of the present disclosure to provide a solution
that detects an emergency PDU release from the UE associated with the emergency PDU session, to free up the network resources.
SUMMARY
[0011] 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.
[0012] An aspect of the present disclosure relates to a method for initiating a
deregistration at an Access and Mobility Management Function (AMF) unit. The method comprises detecting, by a detection unit at the AMF unit, a target network session associated with a user equipment (UE). The target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non-emergency network registration at the user equipment (UE). Further, the method comprises receiving, by a transceiver unit at the AMF unit from a Unified Data Management (UDM) unit, a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE. Further, the method comprises configuring, by an arranging unit at the AMF unit, a session counter associated with the target network session based on the UDM deregistration request. Further, the method comprises detecting, by an analysis unit, an emergency

PDU release action associated with the ongoing emergency protocol data unit (PDU) session. Further, the method comprises initiating, by a processing unit at the AMF unit, the deregistration of the UE based on one of the emergency PDU release action and the session counter
[0013] In an exemplary aspect of the present disclosure, the re-registration
request indicates an inactive network session associated with the network of the UE.
[0014] In an exemplary aspect of the present disclosure, the session counter is
configured at the AMF unit based on the UDM deregistration request comprising a deregistration request reason in a predefined format.
[0015] In an exemplary aspect of the present disclosure, the method further
comprises transmitting, by the transceiver unit from the AMF unit to a UDM unit, a UDM deregistration response based on the UDM deregistration request.
[0016] In an exemplary aspect of the present disclosure, the method further
comprises initiating, by the processing unit at the AMF unit, a UE terminated deregistration based on the emergency PDU release action.
[0017] Another aspect of the present disclosure relates to a system for initiating
a deregistration at an Access and Mobility Management Function (AMF) unit. The system comprises a detection unit to detect, at the AMF unit, a target network session associated with a user equipment (UE). Further, the target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration at the user equipment (UE). Further, the system comprises a transceiver unit connected at least to the detection unit. The transceiver unit is further configured to receive, at the AMF unit from a Unified Data Management (UDM) unit, a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE. Further, the system

comprises an arranging unit connected at least to the transceiver unit. Further, the arranging unit is configured to arrange, at the AMF unit, a session counter associated with the target network session based on the UDM deregistration request. Further, the system comprises an analysis unit connected at least with the arranging unit. Further, the analysis unit is configured to detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session. Further, the system comprises a processing unit connected at least with the analysis unit. The processing unit is configured to initiate, at the AMF unit, the deregistration of the UE based on one of the emergency PDU release action and the session counter.
[0018] Yet another aspect of the present disclosure relates to a user equipment
(UE) for initiating a deregistration at an Access and Mobility Management Function (AMF) unit. The UE comprises a processor, where the processor is configured to deregister the UE based on a target network session of the UE. Further, to deregister the UE, the processor is configured to detect the target network session as one of at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration. The processor may further receive, from a Unified Data Management (UDM) unit, a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE. The processor may further configure a session counter associated with the target network session based on the UDM deregistration request. The processor may detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session, and further the processor may initiate deregistration of the UE based on one of the emergency PDU release action and the session counter.
[0019] Yet another aspect of the present disclosure relates to a non-transitory
computer readable storage medium storing instructions for initiating a deregistration at an Access and Mobility Management Function (AMF) unit, the instructions including executable code which, when executed by one or more units of a system, causes: a detection unit to detect, at the AMF unit, a target network

session associated with a user equipment (UE), wherein the target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration at the user equipment (UE); a transceiver unit to receive, at the AMF unit from a Unified Data Management (UDM) unit, a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE; an arranging unit to arrange, at the AMF unit, a session counter associated with the target network session based on the UDM deregistration request; an analysis unit to detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session; and a processing unit to initiate, at the AMF unit, the deregistration of the UE based on one of the emergency PDU release action and the session counter.
DESCRIPTION OF THE DRAWINGS
[0020] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0021] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.

[0022] FIG. 2 illustrates an exemplary block diagram of a computing device
upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 3 illustrates an exemplary block diagram of a system for initiating
a deregistration at an Access and Mobility Management Function (AMF) unit, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 4 illustrates an exemplary flow diagram of a method for initiating
a deregistration at an Access and Mobility Management Function (AMF) unit, in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 5 illustrates an exemplary flow diagram for initiating an
administrative deregistration at an Access and Mobility Management Function
(AMF) unit, in accordance with exemplary implementations of the present
disclosure.
[0026] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
[0027] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0028] The ensuing description provides exemplary embodiments only, and is
not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description 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.
[0029] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0030] Also, it is noted that individual embodiments may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0031] 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 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 similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0032] As used herein, a “processing unit” or “processor” or “operating
processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0033] As used herein, “a user equipment”, “a user device”, “a smart-user-
device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
[0034] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a

form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0035] As used herein “interface” or “user interface” refers to a shared
boundary across which two or more separate components of a system exchange information or data. The interface may also refer to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0036] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0037] As used herein the transceiver unit includes at least one receiver and at
least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0038] As discussed in the background section, the current known solutions
have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and a system for initiating a deregistration at an Access and Mobility

Management Function (AMF). The present disclosure discloses a novel solution to address the intricate scenario where an ongoing emergency PDU session coincides with non-emergency registration at the AMF. Such as, when a UDM deregistration request is received by the AMF, marked with the deregistration reason of subscription withdrawal or a re-registration, and the UE subsequently releases the emergency PDU, a series of technical actions are initiated. The innovative approach involves the AMF efficiently triggering an administrative deregistration process. This process involves not only the seamless termination of the emergency PDU session but also the clearing of associated network resources. Furthermore, the AMF proactively communicates with the UE, transmitting a "UE terminated deregistration" signal. This solution ensures a synchronized response to the complex set of events, effectively managing emergency and non-emergency communications while maintaining network integrity. The technical effect of this approach is a streamlined and coordinated handling of diverse activities, facilitating optimized emergency communication and network resource utilization.
[0039] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) unit [108], a 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 (PCF) [122], a Unified Data Management (UDM) unit [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.

[0040] 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.
[0041] Access and Mobility Management Function (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.
[0042] Session Management Function (SMF) unit [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.
[0043] 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.
[0044] 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.
[0045] 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.

[0046] 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.
[0047] Network Exposure Function (NEF) [118] is a network function that
exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0048] 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.
[0049] 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.
[0050] Unified Data Management (UDM) unit [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0051] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network capabilities and services.
[0052] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0053] 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.

[0054] The 5GC network architecture also comprises a plurality of interfaces
for connecting the network functions with a network entity for performing the network functions. The NSSF [116] is connected with the network entity via the interface denoted as (Nnssf) interface in the figure. The NEF [118] is connected with the network entity via the interface denoted as (Nnef) interface in the figure. The NRF [120] is connected with the network entity via the interface denoted as (Nnrf) interface in the figure. The PCF [122] is connected with the network entity via the interface denoted as (Npcf) interface in the figure. The UDM unit [124] is connected with the network entity via the interface denoted as (Nudm) interface in the figure. The AF [126] is connected with the network entity via the interface denoted as (Naf) interface in the figure. The NSSAAF [114] is connected with the network entity via the interface denoted as (Nnssaaf) interface in the figure. The AUSF [112] is connected with the network entity via the interface denoted as (Nausf) interface in the figure. The AMF unit [106] is connected with the network entity via the interface denoted as (Namf) interface in the figure. The SMF unit [108] is connected with the network entity via the interface denoted as (Nsmf) interface in the figure. The SMF unit [108] is connected with the UPF [128] via the interface denoted as (N4) interface in the figure. The UPF [128] is connected with the RAN [104] via the interface denoted as (N3) interface in the figure. The UPF [128] is connected with the DN [130] via the interface denoted as (N6) interface in the figure. The RAN [104] is connected with the AMF unit [106] via the interface denoted as (N2). The AMF unit [106] is connected with the RAN [104] via the interface denoted as (N1). The UPF [128] is connected with other UPF [128] via the interface denoted as (N9). The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9, N6, N4, N3, N2, and N1 can be referred to as a communication channel between one or more functions or modules for enabling exchange of data or information between such functions or modules, and network entities.
[0055] FIG. 2 illustrates an exemplary block diagram of a computing device
[200] (herein, also referred to as a computer system [200]) upon which one or more

features of the present disclosure may be implemented, in accordance with an exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for initiating a deregistration at an Access and Mobility Management Function (AMF) [106], utilising a system, or one or more sub-systems, provided in the network. In another implementation, the computing device [200] itself implements the method for initiating a deregistration at an Access and Mobility Management Function (AMF) [106], using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0056] The computing device [200] may include a bus [202] or other
communication mechanism(s) for communicating information, and a hardware processor [204] coupled with bus [202] for processing said information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202], for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in a non-transitory storage media accessible to the processor [204], render the computing device [200] into a special purpose device that is customized to perform operations according to the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0057] A storage device [210], such as a magnetic disk, optical disk, or solid-
state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),

Light Emitting Diode (LED) display, Organic LED (OLED) display, etc., for displaying information to a user of the computing device [200]. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The cursor controller [216] typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the cursor controller [216] to specify positions in a plane.
[0058] The computing device [200] 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 [200], causes or programs the computing device [200] to be a special-purpose device. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. The one or more instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the one or more sequences of the one or more instructions contained in the main memory [206] causes the processor [204] 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.
[0059] The computing device [200] also may include a communication
interface [218] coupled to the bus [202]. The communication interface [218] provides two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] 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 telecommunication line. In another example, the communication interface [218] 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 [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing different types of information.
[0060] The computing device [200] can send and receive data, including
program code, messages, etc. through the network(s), the network link [220] and the communication interface [218]. In an example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], the host [224] and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
[0061] FIG. 3 illustrates an exemplary block diagram of a system [300] for
initiating a deregistration at an Access and Mobility Management Function (AMF) [106], is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one detection unit [302], at least one transceiver unit [304], at least one arranging unit [306], at least one analysis unit [308], and at least one processing unit [310]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment [102] to implement the features of the present disclosure. The system [300] may be a part of the user device [102]/ or may be independent of but in communication with the user device

[102] (may also referred herein as a UE). In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
[0062] The system [300] is configured for initiating a deregistration at an
Access and Mobility Management Function (AMF) unit [106], with the help of the interconnection between the components/units of the system [300].
[0063] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various 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 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.
[0064] The system [300] comprises the detection unit [302]. The detection unit
[302] mentioned herein may be configured to detect, at the AMF unit [106], a target network session associated with a user equipment (UE) [102]. The AMF unit [106] is the 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability, along with handling the mobility management procedures like handovers and paging. Further, the target network session mentioned herein refers to a specific set of connections or at least one activity which may involve the UE [102] within the network.
[0065] Further, the target network session comprises at least an ongoing
emergency protocol data unit (PDU) session and a non- emergency network

registration at the user equipment (UE) [102]. Herein, the emergency PDU session may belong to a category of PDU sessions which is reserved for transmitting/ receiving data packets during an event of emergency. The emergency PDU sessions may further be prioritized over other PDU sessions to facilitate an uninterrupted communication of entities during the event of emergency. Meanwhile, the non-emergency network registration may involve a scenario where the UE [102] may require registering within the network for availing regular communication services (such as voice call services, messaging services, data services, and similar).
[0066] Further, in an implementation of the present disclosure, the detection
unit [302] at the AMF unit [106] is configured to identify and prioritize the emergency PDU session over other non-emergency network registration to ensure an effective conversation during a time of emergency. The above-mentioned details are explained by an exemplary scenario: considering an event where a user is actively engaged in streaming a video on the UE, which is a non-emergency PDU session. Further, during the non-emergency PDU session, if the user needs to initiate an emergency call, (such as, dialling 101 for Fire and Rescue Department in India) the initiation of the emergency call is deemed an emergency PDU session, and the detection unit [302] may immediately identify the emergency call as the initiation of the emergency PDU session and may further prioritize the emergency call over the streaming of the video.
[0067] Further, in an aspect, the prioritizing of the emergency call may include
allocation of resources by the AMF unit [106], for example, if the network or the AMF may have 100 available resources, and out of 100, 10 resources may have been allocated to the video stream. Further, in case the detecting unit [302] may detect the emergency call, then the AMF may allocate a total of 40 or 50 out of the available network sessions to the emergency call. The allocation of a high number of resources may ensure that the emergency call may face no disruption.

[0068] It is to be noted that the above-mentioned scenario is just exemplary
and used for better explanation. The scenario in any order may not limit the scope of the present disclosure and the present disclosure may be utilized for other similar scenarios.
[0069] Further, the system [300] comprises the transceiver unit [304]
connected at least to the detection unit [302]. The transceiver unit [304] mentioned herein is configured to receive, at the AMF unit [106] from a Unified Data Management (UDM) [124], a Unified Data Management (UDM) deregistration request. The UDM unit [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0070] Further, during the emergency PDU session, the transceiver unit [304]
may receive the UDM deregistration request. Herein, in one aspect the UDM deregistration request may include a deregistration request reason, stating the one or more reasons for an inactive network session associated with the network of the UE [102]. The one or more reasons may arise due to at least one of a network disconnection state (due to weak signal strength or loss of signal coverage), an ideal state (such as the UE [102] may been inactive for a long time period), a restart state (such as if the UE [102] may be turned off and then back on) and a handover failure state (such as the UE [102] may lost connection with the network during the handover).
[0071] Further, the above-mentioned details is explained by the exemplary
scenario: considering the above mentioned event, post concluding the emergency call, the UDM unit [124] may detect that the subscription of the UE has been withdrawn. Thereafter, in such circumstances, the UDM unit [124] may send the deregistration request to the AMF unit [106] via the transceiver unit [304], wherein the deregistration request may contain the one or reasons for the withdrawing the

subscription. Further, the transceiver unit [106] may further transfer the request to the AMF unit [106] for further action.
[0072] Further, in another aspect, the UDM deregistration request may include
a re-registration request from the UDM unit [124]. The re-registration request may include one or more commands to re-establish the network connections of UE after the emergency call. For ease of understanding, the above mentioned details are explained by the exemplary scenario: considering the above mentioned event, post ending the emergency PDU session (suppose 101), the user may pause the current streaming video for further assisting in the emergency. In such a case, the UDM unit [124] may detect an inactivity in the network session (that is associated with the pause video). In such cases, the UDM unit [124] may send the deregistration request to the AMF unit [106] which may further indicate the inactive session in video streaming. Thereafter, the transceiver unit [304] at the AMF unit [106] may again receive the re-registration request, allowing the AMF unit [106] to re¬establish the connection of the UE [102] and the network, enabling the user to resume the video stream or any other activity. The re-registration request may allow the AMF unit [106] to allocate a dedicated number of resources available in the network to smoothly continue the streaming of video or use any other non-emergency PDU session.
[0073] The system [300] may further comprise the arranging unit [306]
connected at least to the transceiver unit [304]. Further, the arranging unit [306] is configured to arrange, at the AMF unit [106], a session counter associated with the target network session based on the UDM deregistration request. In one aspect, the session counter may refer to a numeric value. In another aspect, the session counter may refer to an indicator. It is to be noted that the session counter may further be defined in any other definition that is known to a person skilled in the art and in any order may not impact the scope of the present disclosure.

[0074] Further, the session counter may be utilized for tracking or managing a
state of the network session. In one example, the session counter may assist the AMF unit [106] in monitoring a number of times the session of a specific UE [102] is registered, deregistered or re-registered. Such as in case the network session for a UE [102] is constantly inactive and may require frequent re-registration, the session counter may assist in finding potential issues that may be present within the network or the UE.
[0075] In another example, the session counter may assist the AMF unit [106]
in managing life cycles of the network sessions of the UE [102] for effectively allocating the number of resources for the network sessions, such that the network sessions are maintained or terminated as per the requirement.
[0076] Further, the session counter is configured at the AMF unit [106] based
on the UDM deregistration request comprising a deregistration request reason mapped at the AMF unit [106] in a predefined format. The UDM deregistration request mentioned herein may include at least one of a specific code or a message that may provide a context regarding one or more reasons behind the re-registration of the UE. The one or more reasons are preferably categorized into one or more categories. Further, the one or more reasons may include at least a reason for inactivity, such as the network session being idle for a pre-defined threshold period of time which may further deregister the network session. Further, the one or more reasons may include a user-initiated reason, implying that the user may desire to de-register the network session. Further, the one or more reasons may include a reason of network issue, implying that the network session is being de-registered due to network problems such as a signal loss. Further, the one or more reasons may include a reason for device shutdown which imply that the UE [102] is either powered off or is in restart mode which may automatically deregister the network session.

[0077] For ease in understanding, the above-mentioned details are explained
by the exemplary scenario: considering the above-mentioned event, when the user may pause the current streaming video, then the UDM unit [124] may detect the inactivity in a video session of the streaming video. Simultaneously, the UDM unit [124] may send the deregistration request to the AMF unit [106] with the UDM deregistration request reason as the reason for inactivity. Thereafter, post receiving the UDM deregistration request the arranging unit [306] at the AMF unit [106] may further update the session counter that may be associated with the video session. Further, the arranging unit [306] based on the results of the session counter may further track an inactivity status for a particular network session (such as the inactivity status of the video session).
[0078] Further, the system [300] comprises the analysis unit [308] connected
at least with the arranging unit [306]. Herein the analysis unit [308] is configured to detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session. In one aspect the emergency PDU release action mentioned herein dictates a process such as ‘network instructions’ to terminate the active emergency PDU session as the emergency PDU session may no longer be needed based on the one or more policies assigned to the network. In another aspect, the emergency PDU release action may indicate by a signal such as ‘Session timeout’, ‘End of the emergency PDU session’ or a ‘user action to disengage the emergency PDU session’ to terminate the active emergency PDU session. Further, the emergency PDU session release action may indicate that the emergency PDU session is conducted, and the number of resources allocated to the emergency PDU session may now be released. It is to be noted that the emergency PDU release action may further be presented in any other definition that is known to a person skilled in the art and in any order may impact the scope of the present disclosure.
[0079] For ease in understanding, the above mentioned details is explained by
the exemplary scenario: considering the above mentioned event, when in case the user may desire to disengage the emergency PDU session, then in such case the user

may hung up the emergency call (such as the 101) as the user may have conveyed the necessary message to the Fire and Rescue Department (if suppose the User may have dialed 101). The hanging up of the emergency call may indicate a user action which may further be concluded as a signal to the analysis unit [308] as the emergency PDU release action and the further the analysis unit [308] may further assist in releasing the number of resources (such as 40 or 50 out of 100 as mentioned earlier) for other network sessions.
[0080] The system [300] further comprises the processing unit [310] connected
at least with the analysis unit [308]. Herein, the processing unit [310] is configured to initiate, at the AMF unit [106], the deregistration based on one of the emergency PDU release action and the session counter. In one aspect, post analysing the emergency PDU release action by the analysis unit [308], or the session counter at the AMF unit [106], the processing unit [310] may initiate the deregistration of the emergency PDU session.
[0081] For ease in understanding, the above-mentioned details is explained by
the exemplary scenario: considering the above mentioned event, the processing unit [310] may direct the AMF unit [106] to free up the number of resources (such as 40 or 50) allotted to the emergency PDU session, for allowing the freed number of resources to be utilized by other network sessions.
[0082] Further, the processing unit [310] is further configured to initiate, at the
AMF unit [106], a UE terminated deregistration based on the emergency PDU release action. In another aspect, the processing unit [310] may further initiate the deregistration of the emergency PDU session solely based on the emergency PDU release action if the emergency PDU release action is provided by the end-user operating the UE.
[0083] Further, the transceiver unit [304] is further configured to transmit,
from the AMF unit [106] to a UDM unit [124], a UDM deregistration response

based on the UDM deregistration request. The transceiver unit [304] may further send the UDM deregistration response from the AMF unit [106] to the UDM unit [124] to acknowledge and confirm the deregistration process based on the UDM deregistration request. The UDM deregistration response may vary based on the outcome of the deregistration process which may include but not limited to a success outcome, a partial success outcome, a failure outcome or any other outcome known to a person skilled in the art.
[0084] FIG. 4 illustrates an exemplary flow diagram of a method [400] for
initiating a deregistration at an Access and Mobility Management Function (AMF) [106], in accordance with exemplary implementations of the present disclosure. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0085] At step [404], the method [400] encompasses detecting, by a detection
unit [302] at the AMF unit [106], a target network session associated with a user equipment (UE) [102]. Further, the target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration at the user equipment (UE) [102].
[0086] At step [406], the method [400] encompasses receiving, by a transceiver
unit [304] at the AMF unit [106] from a Unified Data Management (UDM) [124], a Unified Data Management (UDM) deregistration request comprising a re-registration request. Further, the re-registration request indicates an inactive network session associated with the network of the UE.
[0087] At step [408], the method [400] further encompasses arranging, by an
arranging unit [306] at the AMF unit [106], a session counter associated with the target network session based on the UDM deregistration request. Furthermore, the

session counter is configured at the AMF unit [106] based on the UDM deregistration request comprising a deregistration request reason in a predefined format.
[0088] At step [410], the method [400] further encompasses detecting, by the
analysis unit [308], an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session.
[0089] At step [412], the method [400] further encompasses initiating, by a
processing unit [310] at the AMF unit [106], the deregistration based on one of the emergency PDU release action and the session counter.
[0090] The method [400] further encompasses initiating, by the processing unit
[310] at the AMF unit [106], a UE terminated deregistration based on the emergency PDU release action.
[0091] The method [400] further encompasses, transmitting, by the transceiver
unit [304] from the AMF unit [106] to a UDM unit [124], a UDM deregistration response based on the UDM deregistration request.
[0092] The method [400] herein terminates at step [414].
[0093] FIG. 5 illustrates an exemplary flow diagram [500] for initiating an
administrative deregistration at an Access and Mobility Management Function (AMF) [106]. Further, the system [300] may perform the flow diagram [500] as depicted in FIG. 5.
[0094] The flow diagram [500] may comprise a User Equipment (UE) [102]
that may refer to an equipment or devices such as the smartphones, tablets, or IoT devices which may be used by an end user to be connected to a network in a network infrastructure.

[0095] The flow diagram [500] may further comprise a Next Generation
NodeB (gNB) [502] which may provide a radio access to the UE, allowing the UE [102] to connect to the network and further assisting in managing the communications between the UE [102] and the network.
[0096] The flow diagram [500] may further comprise an Access and Mobility
Management Function (AMF) [106] that manages the access and mobility aspects of the UE [102] such as a UE [102] registration, a UE [102] connection, or managing the mobility of the UE [102] within different network areas.
[0097] The flow diagram [500] may further comprise a Session Management
Function (SMF) [108] that is responsible for managing data sessions in 5G networks. Further, the SMF unit [108] may work with the AMF unit [106] to manage the user data flows based on the communication between the UE [102] and the network.
[0098] The flow diagram [500] may further comprise a Unified Data
Management (UDM) unit [124] that is responsible for managing user data, such as subscription information, and authentication.
[0099] At step 502, herein, the UE [102] has an active non-emergency
registration, and the UE [102] is also engaged in an emergency Protocol Data Unit (PDU) session. The network sessions are further managed by the AMF unit [106], with the assistance of the gNB [602] and the SMF unit [108]. Further, the flow diagram [500] suggests that the AMF unit [106] receives a deregistration request from the UDM unit [124]. In one aspect, the deregistration request may include a deregistration request reason such as a subscription withdrawn status associated with the UE [102]. In another aspect, the deregistration request may include a re-registration (RE-REG) flag which may indicate that the UE [102] is required to re¬register after completing the ongoing network sessions.

[0100] At step 504, the AMF unit [106] processes the deregistration request
and sends a deregistration response back to the UDM unit [124]. The deregistration response may define that the deregistration request is acknowledged, and the necessary actions are to be taken for the deregistration request. Further, the response may further indicate that whether the UE [102] is deregistered, re-registered or any other actions such as a session termination action is initiated. It is to be noted that the other actions may involve any other actions that may be known to a person skilled in the art.
[0101] At step 506, the UE [102] releases the emergency PDU session in the
form of an action such as an emergency PDU release action. The requirement of the emergency PDU release action is necessary as the ongoing emergency PDU session requires to be properly terminated prior de-registering or re-registering the UE. The flow diagram [500] further suggests that the AMF unit [106] initiates administrative deregistration (Admin Dereg) with the re-registration flag, ensuring that the UE [102] is properly re-registered for future sessions. The Admin Dereg action is thereafter communicated from the AMF unit [106] back to the UDM unit [124], which may indicate a successful deregistration process of the UE.
[0102] The flow diagram [500] showcases a process to ensure minimal
disruption caused to the user experience, especially in critical situations such as emergency calls, by proficiently managing the different types of network sessions.
[0103] The present disclosure further discloses a user equipment (UE) [102]
for initiating a deregistration at an Access and Mobility Management Function (AMF) unit [106], the UE [102] comprising a processor, where the processor is configured to deregister, the UE [102] based on a target network session of the UE. Further, to deregister the UE, the processor is configured to detect the target network session as one of at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration. The processor may further

receive, from a Unified Data Management (UDM) unit [124], a Unified Data Management (UDM) deregistration request comprising a re-registration request. The processor may further configure a session counter associated with the target network session based on the UDM deregistration request. The processor may detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session, and further the processor may initiate UE [102] deregistration of the UE based on one of the emergency PDU release action and the session counter.
[0104] Yet another aspect of the present disclosure relates to a non-transitory
computer readable storage medium storing instructions for initiating a deregistration at an Access and Mobility Management Function (AMF) unit, the instructions including executable code which, when executed by one or more units of a system, causes: a detection unit to detect, at the AMF unit, a target network session associated with a user equipment (UE), wherein the target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration at the user equipment (UE); a transceiver unit to receive, at the AMF unit from a Unified Data Management (UDM) unit, a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE; an arranging unit to arrange, at the AMF unit, a session counter associated with the target network session based on the UDM deregistration request; an analysis unit to detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session; and a processing unit to initiate, at the AMF unit, the deregistration of the UE based on one of the emergency PDU release action and the session counter.
[0105] As is evident from the above, the present disclosure provides a
technically advanced solution for initiating a deregistration at an Access and Mobility Management Function (AMF) unit. The present solution brings forth several distinct advantages and notable technical advancements. Firstly, by promptly deregistering the user immediately upon the release of an emergency PDU

session, the solution ensures swift and efficient handling of network resources. This eliminates any potential resource wastage that might occur if the deregistration process were delayed. Additionally, the approach offers a substantial improvement by removing the dependency on user equipment (UE) triggered messages. This results in a more reliable and automated process, reducing the need for specific UE actions to initiate deregistration. This advancement enhances the overall system's responsiveness and robustness, ensuring a seamless and streamlined user experience. In summary, this innovation's ability to expedite deregistration, optimize resource utilization, and eliminate dependency on UE-triggered actions marks a significant step forward in network management and emergency communication efficiency.
[0106] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to 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 [400] for initiating a deregistration at an Access and Mobility
Management Function (AMF) unit [106], the method [400] comprising:
detecting, by a detection unit [302] at the AMF unit [106], a target network session associated with a user equipment (UE) [102], wherein the target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration at the user equipment (UE) [102];
receiving, by a transceiver unit [304] at the AMF unit [106] from a Unified Data Management (UDM) unit [124], a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE [102];
arranging, by an arranging unit [306] at the AMF unit [106], a session counter associated with the target network session based on the UDM deregistration request;
detecting, by an analysis unit [308], an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session; and
initiating, by a processing unit [310] at the AMF unit [106], the deregistration of the UE [102] based on one of the emergency PDU release action and the session counter.
2. The method [400] as claimed in claim 1, wherein the re-registration request indicates an inactive network session associated with the network of the UE.
3. The method [400] as claimed in claim 1, wherein the session counter is configured at the AMF unit [106] based on the UDM deregistration request comprising a deregistration request reason in a predefined format.

4. The method [400] as claimed in claim 1, further comprises transmitting, by the transceiver unit [304] from the AMF unit [106] to a UDM unit [124], a UDM deregistration response based on the UDM deregistration request.
5. The method [400] as claimed in claim 1, further comprises initiating, by the processing unit [310] at the AMF unit [106], a UE terminated deregistration based on the emergency PDU release action.
6. A system [300] for initiating a deregistration at an Access and Mobility Management Function (AMF) unit [106], the system [300] comprises:
a detection unit [302] configured to:
detect, at the AMF unit [106], a target network session associated with a user equipment (UE) [102], wherein the target network session comprises at least an ongoing emergency protocol data unit (PDU) session and a non- emergency network registration at the user equipment (UE) [102];
a transceiver unit [304] connected at least to the detection unit [302],
wherein the transceiver unit [304] is configured to:
receive, at the AMF unit [106] from a Unified Data Management (UDM) unit [124], a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE [102];
an arranging unit [306] connected at least to the transceiver unit [304],
wherein the arranging unit [306] is configured to:
arrange, at the AMF unit [106], a session counter associated with the target network session based on the UDM deregistration request;
an analysis unit [308] connected at least with the arranging unit [306],
wherein the analysis unit [308] is configured to:
detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session; and

a processing unit [310] connected at least with the analysis unit [308], wherein the processing unit [310] is configured to:
initiate, at the AMF unit [106], the deregistration of the UE
[102] based on one of the emergency PDU release action and the
session counter.
7. The system [300] as claimed in claim 6, wherein the re-registration request indicates an inactive network session associated with the network of the UE.
8. The system [300] as claimed in claim 6, wherein the session counter is configured at the AMF unit [106] based on the UDM deregistration request comprising a deregistration request reason mapped at the AMF unit [106] in a predefined format.
9. The system [300] as claimed in claim 6, wherein the processing unit [310] is further configured to transmit, from the AMF unit [106] to a UDM unit [124], a UDM deregistration response based on the UDM deregistration request.

10. The system [300] as claimed in claim 6, wherein the processing unit [310] is further configured to initiate, at the AMF unit [106], a UE terminated deregistration based on the emergency PDU release action.
11. A user equipment (UE) [102] comprising:
a processor, wherein the processor is configured to:
deregister the UE [102] based on a target network session of
the UE, wherein to deregister the UE, the processor is configured to: detect the target network session as one of at least an ongoing
emergency protocol data unit (PDU) session and a non- emergency
network registration;

receive, from a Unified Data Management (UDM) unit [124], a Unified Data Management (UDM) deregistration request comprising a re-registration request for the UE [102];
configure a session counter associated with the target network session based on the UDM deregistration request;
detect an emergency PDU release action associated with the ongoing emergency protocol data unit (PDU) session; and
initiate deregistration of the UE [102] based on one of the emergency PDU release action and the session counter.