Method and system for detaching subscriber in a network

Abstract

The present disclosure relates to a method and a system for detaching a subscriber in a network The disclosure encompasses receiving a detachment command request at policy control function (PCF) [122]; receiving a subscription permanent identifier (SUPI) value for which subscriber detachment process is triggered; generating successful / unsuccessful validation result; triggering detachment command related to the subscriber detachment process at network node(s) [312]; triggering terminate request command for the network node(s) [312]; and sending an indication of successful detachment of a subscriber from the network.

Description

METHOD AND SYSTEM FOR DETACHING SUBSCRIBER IN A NETWORKFIELD OF THE DISCLOSURE

[0001] Embodiments of the present disclosure generally relate to the field of wireless communication. More particularly, embodiments of the present disclosure relate to detaching subscriber(s) in a network.BACKGROUND

[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on antilog 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.

[0004] A policy control function (PCF) in a 5G network is responsible for controlling the policy and charging aspects of user sessions. The PCF can define specific rules that dictate how a user's traffic should be treated based on their service level, subscription, or other criteria. However, for some reason, the PCF fails to send the desired PCC rule for a particular user, which could mean that the intended quality of service or other policies won't be applied to their session. In such cases, the sub scriber / sub scriber permanent identifier (SUPI) may be disconnected from the network.However, if the SUPI is not detached from the network, the freeing up of resources cannot be ensured. This may lead to inaccurate accounting for the user's session in many cases.

[0005] Hence, in view of these and other existing limitations, there exists an imperative need in the art to provide a method and a system for detaching subscriber permanent identifier in absence of policy and charging control rule, which the present disclosure aims to address.OBJECTS OF THE DISCLOSURE

[0006] This section is provided to introduce certain objects and aspects of the present invention in a simplified form that are further described below in the description. In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present invention is to substantially reduce the limitations and drawbacks of the prior arts as described hereinabove.

[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0008] It is an object of the present disclosure to provide a system and a method for detaching subscriber / subscriber permanent identifier (SUPI) in absence of policy and charging control rule.

[0009] It is another object of the present disclosure to provide a solution that facilitates release of network resources and terminate active sessions by properly disconnecting the user from the network.

[0010] It is yet another object of the present disclosure to provide a solution that facilitates accurate accounting for the user's session.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 may relate to a method for detaching a subscriber in a network. The method comprises receiving, by a transceiver unit, a detachment command request at a policy control function (PCF). The detachment command request is related to a subscriber detachment process at one or more network nodes. The method further comprises receiving, by the transceiver unit, a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. The method further comprises generating, by a generating unit, one of a successful validation result, and an unsuccessful validation result. The method further comprises triggering, by a triggering unit, a detachment command related to the subscriber detachment process at the one or more network nodes. The method further comprises triggering, by the triggering unit, a terminate request command for the one or more network nodes. The method further comprises sending, by the transceiver unit, an indication of successful detachment of the subscriber from the network.

[0013] In an exemplary aspect of the present disclosure, the method further comprises checking, by a processing unit, the appropriateness of permissions of a user.

[0014] In an exemplary aspect of the present disclosure, the successful validation result is an event when the permissions of the user are appropriate, and the unsuccessful validation result is an event when the permissions of the user are inappropriate.

[0015] In an comprise aspect of the present disclosure, the one or more network nodes comprise at least one of an access and mobility management function (AMF) and a session management function (SMF).

[0016] In an exemplary aspect of the present disclosure, prior to the triggering, by the triggering unit, the terminate request command for the one or more network nodes, the method comprises determining, by a determination unit, a state of the PCF. The state of the PCF is one of an active state, and an inactive state.

[0017] In an exemplary aspect of the present disclosure, the method further comprises triggering, by the triggering unit, the terminate request command for the one or more network nodes, in an event the state of the PCF is determined as the active state.

[0018] In an exemplary aspect of the present disclosure, the detachment command is utilised for detaching the SUPI of the one or more network nodes.

[0019] In an exemplary aspect of the present disclosure, wherein prior to receiving the detachment command request, by the transceiver unit, the method comprises facilitating, by the processing unit, a login at a user interface (UI) of the PCF, based on a user input by the user.

[0020] Another aspect of the present disclosure may relate to a system for detaching a subscriber in a network. The system comprises a transceiver unit configured to receive a detachment command request at a policy control function (PCF). The detachment command request is related to a subscriber detachment process at one or more network nodes. The transceiver unit is further configured to receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. The system further comprises a generation unit configured to generate one of a successful validation result, and an unsuccessful validation result. The system further comprises a triggering unit configured to trigger a detachment command related to the subscriber detachment process at the one or more network nodes. The triggering unit is further configured to trigger a terminate request command for the one or more network nodes. The transceiver unit is further configured to send an indication of successful detachment of the subscriber from the network.

[0021] Another aspect of the present disclosure may relate to a non-transitory computer readable storage medium, storing instructions for detaching a subscriber in a network, the storage medium comprising executable code which, when executed by one or more units of a system, causes a transceiver unit to receive a detachment command request at a policy control function (PCF). The detachment command request is related to a subscriber detachment process at one or more network nodes. Further, the executable code which, when executed causes the transceiver unit to receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. Further, the executable code which, when executed causes a generation unit to generate one of: a successful validation result, and an unsuccessful validation result. Further, the executable code which, when executed causes a triggering unit to trigger a detachment command related to the subscriber detachment process at the one or more network nodes. Further, the executable code which, when executed causes the triggering unit to trigger a terminate request command for the one or more network node. Further, the executable code which, when executed causes the transceiver unit to send an indication of successful detachment of a subscriber from the network.

[0022] Yet another aspect of the present disclosure may relate to a user equipment (UE) for detaching a subscriber in a network. The UE comprises a processing unit configured to facilitate alogin at a user interface (UI) of a policy control function (PCF), based on a user input by a user. The UE further comprises a transceiver unit configured to receive a detachment command request at the PCF. The detachment command request is related to a subscriber detachment process at one or more network nodes. The transceiver unit is further configured to receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. The UE further comprises a generation unit configured to generate one of a successful validation result, and an unsuccessful validation result. The UE further comprises a triggering unit configured to trigger a detachment command related to the subscriber detachment process at the one or more network nodes. The triggering unit is further configured to trigger a terminate request command for the one or more network nodes. The transceiver unit is further configured to send an indication of successful detachment of a subscriber from the network.DESCRIPTION OF DRAWINGS

[0023] 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.

[0024] FIG.l illustrates an exemplary block diagram representation of a 5th generation core (5GC) network architecture

[0100] ,

[0025] FIG.2 illustrates an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0026] FIG.3 illustrates an exemplary block diagram of a network environment having system

[0300] for detaching a subscriber in a network, in accordance with exemplary implementations of the present disclosure.

[0027] FIG.4 illustrates an exemplary method

[0400] flow diagram for detaching the subscriber in the network, in accordance with the exemplary embodiments of the present disclosure.

[0028] FIG.5 illustrates an exemplary scenario of the present disclosure depicting a flow chart of a process

[0500] for detaching subscriber permanent identifier (SUPI) in absence of policy and charging control rule(s) in a network, in accordance with the exemplary embodiments of the present disclosure.

[0029] FIG.6 illustrates another exemplary scenario of the present disclosure showcasing a system

[0600] for detaching the SUPI in absence of the policy and charging control rule(s) in the network, in accordance with exemplary implementations of the present disclosure.

[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0032] 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.

[0033] 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 disclosure. These terms are not intended to limit the scope of the disclosure 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 disclosure 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 disclosure as defined herein.

[0034] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to 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.

[0035] 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 completed but could have additional steps that may not be included in any of the figures.

[0036] 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.

[0037] 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 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, 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.

[0038] Further, the user device and / or a system as described herein to implement technical features as disclosed in the present disclosure may also comprise a “processor” or “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 Digital Signal Processor (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 is a hardware processor.

[0039] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “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 at least one of a transceiver unit, a processingunit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0040] 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.

[0041] As used herein “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0042] 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.

[0043] 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.

[0044] As discussed in the background section, the current known solutions have several shortcomings for detaching a subscriber / subscriber permanent identifier (SUPI) in absence of policy and charging control rule, such as unavoidable consumption of network resources, inaccurate accounting for the user's session etc.

[0045] The present disclosure thus aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and a system for detaching a subscriber in a network.

[0046] The present disclosure provides an easy way to detach subscriber / subscription Permanent Identifier (SUPI) of a particular subscriber / user by terminating session management functions (SMF)

[0108] (as shown in FIG.l) and access and mobility management function (AMF)

[0106] (as shown in FIG.l). The present disclosure helps policy control function (PCF)

[0122] to release resources and terminate active sessions. The PCF

[0122] sends a ‘Detach Request’ to the appropriate network nodes / elements / functions, typically involving the AMF

[0106] and the SMF

[0108] , The AMF

[0106] and the SMF

[0108] start the process of terminating any active sessions and releasing resources associated with the subscriber. The present disclosure comprises adding application programming interfaces (APIs) inside the PCF

[0122] which can be triggered by an authorized user (preferably a network administrator) through a user interface (UI) (whether command line interface (CLI) or graphical user interface (GUI)) designed for the PCF

[0122] ,

[0047] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0048] 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

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] , 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.

[0049] The Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects the user equipment (UE)

[0102] to the core network (CN) and provides accessto different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0050] The Access and Mobility Management Function (AMF)

[0106] is the 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0051] The Session Management Function (SMF)

[0108] is the 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)

[0128] for data forwarding and handles IP address allocation and Quality of Service (QoS) enforcement. Further, the SMF

[0108] facilitates enforcement of session management related policy decisions from the PCF

[0122] ,

[0052] The Service Communication Proxy (SCP)

[0110] 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.

[0053] The Authentication Server Function (AUSF)

[0112] is the network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0054] The Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is the 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.

[0055] The Network Slice Selection Function (NSSF)

[0116] is the network function responsible for selecting the appropriate network slice for the UE based on factors such as subscription, requested services, and network policies.

[0056] The Network Exposure Function (NEF)

[0118] is the network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0057] The Network Repository Function (NRF)

[0120] is the 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.

[0058] The Policy Control Function (PCF)

[0122] enables efficient policy control and management, facilitating network behaviour control, network slicing, user equipment (UE) activities, and communication with other 5G core network functions. PCF is responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. The PCF is responsible for policy control decisions and flow-based charging control functionalities.

[0059] The Unified Data Management (UDM)

[0124] is the network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0060] The Application Function (AF)

[0126] is the network function that represents external applications interfacing with the 5G core network to access network capabilities and services. In an exemplary implementation, the application function (AF)

[0126] as shown in FIG. 1, resembles an application server that can interact with the other control-plane NFs. AF(s)

[0126] can exist for different application services and can be owned by the network operator or by trusted third parties. For instance, the AF

[0126] of an over-the-top application provider can influence routing, steering its traffic towards its external edge servers. For services considered to be trusted by the operator, the AF

[0126] can access Network Function(s) (NF) directly whereas untrusted or third-party AF(s)

[0126] would access the Network Functions through the NEF

[0118] ,

[0061] The User Plane Function (UPF)

[0128] is the network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0062] The Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE)

[0102] in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0063] 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 network is designed as an interconnected system of Network Functions (NFs) [also known as fifth generationcommunication network (5GCN) network function NF)] that communicate through the one or more interfaces (i.e., service-based interfaces or reference point interfaces). The Network Functions (NF(s)) within the 5G control plane will use service-based interfaces for their interactions. The user plane function (UPF)

[0128] , and radio interactions shall use the reference point interfaces. Each NF exposes specific functionality and provides services to other NFs. Therefore, any communication or routing between NFs or between the network nodes and NFs takes place through these interfaces. Interfaces are self-contained software modules that are reusable independently of each other and can be thought of as micro services. Further, as shown in the FIG. 1, the following service-based interfaces are defined:Namf: Service-based interface exhibited by AMF

[0106] ,Nsmf: Service-based interface exhibited by SMF

[0108] ,Nnef: Service-based interface exhibited by NEF

[0118] , Npcf: Service-based interface exhibited by PCF

[0122] , Nudm: Service-based interface exhibited by UDM

[0124] , Naf: Service-based interface exhibited by AF

[0126] , Nchf: Service-based interface exhibited by CHF

[0132] , Nnrf: Service-based interface exhibited by NRF

[0120] , Nnssf: Service-based interface exhibited by NSSF

[0116] , Nausf: Service-based interface exhibited by AUSF

[0112] , Nnssaaf: Service-based interface exhibited by NSSAAF

[0114] , Nlmf: Service-based interface exhibited by LMF

[0144] ,

[0064] Nscp: Service-based interface exhibited by SCP

[0110] , Further, the 5G System Architecture as shown in FIG. 1, contains the following reference points:N1 : Reference point between the UE

[0102] and the AMF

[0106] ,N2: Reference point between the RAN

[0104] and the AMF

[0106] ,N3: Reference point between the RAN

[0104] and the UPF

[0128] ,N4: Reference point between the SMF

[0108] and the UPF

[0128] , N6: Reference point between the UPF

[0128] and a Data Network.

[0065] The present disclosure can be implemented on a computing device

[0200] as shown in FIG. 2. The computing device

[0200] implements the present disclosure in accordance with the 5G communication network architecture (as shown in FIG. 1). FIG. 2 illustrates an exemplary block diagram of the computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In animplementation, the computing device

[0200] may also implement a method

[0400] for detaching a subscriber in a network utilising a system

[0300] (as shown in FIG.3). In another implementation, the computing device

[0200] itself implements the method

[0400] for detaching the subscriber in the network using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0066] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0067] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] , The 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.

[0068] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic whichin combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] 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.

[0069] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] 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

[0218] 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

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0070] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , the host

[0224] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0071] The present disclosure is implemented by the system

[0300] (as shown in FIG. 3). The system

[0300] may be implemented using the computing device

[0200] (as shown in FIG. 2). In an implementation, the computing device

[0200] may be connected to the system

[0300] to perform the present disclosure. Referring to FIG. 3, an exemplary block diagram of the system

[0300] for detaching a subscriber in a network, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one policy control function (PCF)

[0122] which further comprises at least one processing unit

[0302] ; at least one user interface (UI)[such as but not limited to a command line interface (CLI) or a graphical user interface (GUI)]

[0304] ; at least one transceiver unit

[0306] ; at least one generation unit

[0308] and at least one triggering unit

[0310] , The system

[0300] is connected to one or more network nodes / functions / units

[0312] comprising at least one session management function (SMF)

[0108] and at least one access and mobility management function (AMF)

[0106] , Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG.3, all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such number of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device / equipment (may also referred herein as a UE)

[0314] to implement the features of the present disclosure. The system

[0300] may be a part of the UE

[0314] or may be independent of but in communication with the user device. In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the UE

[0314] ,

[0072] The system

[0300] is configured for detaching a subscriber in a network, with the help of the interconnection between the components / units of the system

[0300] , In an exemplary aspect of the present disclosure, the system

[0300] is configured for detaching subscriber permanent identifier (SUPI) in absence of policy and charging control rule(s). It is to be noted that a Policy and Charging Control (PCC) rules are a set of information elements enabling the detection of a service data flow and providing parameters for PCF

[0122] , The PCC rules enable policy control and proper charging for a service data flow. There are two different types of PCC rules: dynamic PCC rules and predefined PCC rules. The dynamic PCC rules are dynamically provisioned by the PCF

[0122] to the SMF

[0108] , These PCC rules may be either predefined or dynamically generated in the PCF

[0122] , The dynamic PCC rules can be installed, modified and removed at any time. While the predefined PCC rules are preconfigured in the SMF

[0108] , The predefined PCC rules can be activated or deactivated by the PCF

[0122] at any time. The predefined PCC rules within the PCF

[0122] may be grouped allowing the PCF

[0122] to dynamically activate a set of PCC rules.

[0073] The transceiver unit

[0306] is configured to receive a detachment command request at a policy control function (PCF)

[0122] , The detachment command request here relates to a subscriber detachment process at one or more network nodes

[0312] , The subscriber detachment process relates to release of the user / subscriber session from the network. The detachment request de-registers the subscriber and terminates active sessions of the subscriber thereby freeing up the network resources. Thereafter, the transceiver unit

[0306] receives a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. The SUPI is a unique permanent identifier assigned to a subscriber in a network (preferably a 5G network) for transmission.

[0074] Upon receiving the SUPI value, the generation unit

[0308] of the system

[0300] generates one of a successful validation result, and an unsuccessful validation result. The validation result here signifies whether the process of verifying the authenticity and integrity of the SUPI value by the network is verified. A successful validation result indicates that validation is successful as the SUPI belongs to a legitimate subscriber and no altercation has taken place in the SUPI value during transmission while the unsuccessful validation results indicate vice versa thereby often requiring reauthentication and reauthorization of the SUPI value with the subscriber’s details.

[0075] After generation of the validation result, the triggering unit

[0310] triggers a detachment command related to the subscriber detachment process at the one or more network nodes

[0312] , The triggering unit

[0310] then triggers a terminate request command for the one or more network nodes

[0312] , The terminate request command refers to a signalling message for ending or releasing the active session / connection. This is performed to free up network resources currently dedicated to ongoing network functions. It is to be noted that the event leading to trigger may include but not limited to a specific condition for prompting the update of policies for session management.

[0076] Post, the triggering of the terminate request command, the transceiver unit

[0306] sends an indication of successful detachment of the subscriber from the network.

[0077] In an exemplary aspect of the present disclosure, a processing unit

[0302] is configured to check the appropriateness of permissions of a user. In an embodiment, appropriateness herein refers to evaluation of whether a user has correct rights or privileges to perform a specific action within the system

[0300] , For example, before proceeding with the detachment command, the system

[0300] may check if the user has necessary permissions to perform that action. This may be done through a validation step that may verify the user’s credentials.

[0078] In an exemplary aspect of the present disclosure, the successful validation result is an event when the permissions of the user are appropriate, and the unsuccessful validation result is an event when the permissions of the user are inappropriate.

[0079] In an exemplary aspect of the present disclosure, the one or more network nodes

[0312] comprises at least one of: an access and mobility management function (AMF)

[0106] and a session management function (SMF)

[0108] ,

[0080] In an exemplary aspect of the present disclosure, wherein a determination unit

[0312] , prior to triggering by the triggering unit

[0310] , the terminate request command for the one or more network nodes

[0312] , is configured to determine a state of the PCF

[0122] , wherein the state of the PCF

[0122] is one of: an active state, and an inactive state. The active state of the PCF

[0122] is when the PCF

[0122] is actively managing and enforcing policies in the communication network for users and network resources. While the inactive state of the PCF

[0122] is when the PCF

[0122] is not indulged in policy management.

[0081] In an exemplary aspect of the present disclosure, the triggering unit

[0310] is configured to trigger the terminate request command for the one or more network nodes

[0312] in an event the state of the PCF

[0122] is determined as the active state.

[0082] In an exemplary aspect of the present disclosure, the detachment command is utilised for detaching the SUPI of the one or more network nodes

[0312] ,

[0083] In an exemplary aspect of the present disclosure, wherein the processing unit

[0302] , prior to receiving the detachment command request by the transceiver unit

[0306] , is configured to facilitate a login at a user interface (UI)

[0304] of the PCF

[0122] , based on a user input by the user.

[0084] Referring to FIG. 4, an exemplary method flow diagram

[0400] for detaching a subscriber in a network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the system

[0300] for detaching subscriber permanent identifier (SUPI) in absence of policy and charging control rule(s). It is to be noted that a Policy and Charging Control (PCC) rules are a set of information elements enabling the detection of a service data flow and providing parameters for PCF

[0122] , The PCC rules enable policy control and proper charging for a service data flow. There are two different types of PCC rules: dynamic PCC rules and predefined PCC rules. The dynamic PCC rules are dynamically provisioned by the PCF

[0122] to the SMF

[0108] , These PCC rules may be either predefined or dynamically generated in the PCF

[0122] , The dynamic PCC rules can be installed, modified and removed at any time. While the predefined PCC rules are preconfigured in the SMF

[0108] , Thepredefined PCC rules can be activated or deactivated by the PCF

[0122] at any time. The predefined PCC rules within the PCF

[0122] may be grouped allowing the PCF

[0122] to dynamically activate a set of PCC rules. Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. In another implementation the method

[0400] is performed by a system

[0600] (as shown in FIG.6). Further, in an implementation, the system

[0600] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method

[0400] starts at step

[0402] ,

[0085] At step

[0404] , the method

[0400] comprises receiving, by a transceiver unit

[0306] , a detachment command request at a policy control function (PCF)

[0122] , The detachment command request is related to a subscriber detachment process at one or more network nodes

[0312] , The subscriber detachment process relates to release of the user / subscriber session from the network. The detachment request de-registers the subscriber and terminates active sessions of the subscriber thereby freeing up the network resources.

[0086] At step

[0406] , the method

[0400] comprises receiving, by the transceiver unit

[0306] , a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. The SUPI is a unique permanent identifier assigned to a subscriber in a network (preferably a 5G network) for transmission.

[0087] At step

[0408] , the method

[0400] comprises generating, by a generating unit

[0308] , one of a successful validation result, and an unsuccessful validation result. The validation result here signifies whether the process of verifying the authenticity and integrity of the SUPI value by the network is verified. A successful validation result indicates that validation is successful as the SUPI belongs to a legitimate subscriber and no altercation has taken place in the SUPI value during transmission while the unsuccessful validation result indicates vice versa thereby often requiring reauthentication and reauthorization of the SUPI value with the subscriber’s details.

[0088] At step

[0410] , the method

[0400] comprises triggering, by a triggering unit

[0310] , a detachment command related to the subscriber detachment process at the one or more network nodes

[0312] ,

[0089] At step

[0412] , the method

[0400] comprises triggering, by the triggering unit

[0310] , a terminate request command for the one or more network nodes

[0312] , The terminate request command refers to a signalling message for ending or releasing the active session / connection.This is performed to free up network resources currently dedicated to ongoing network functions. It is to be noted that the event leading to trigger may include but not limited to a specific condition for prompting the update of policies for session management.

[0090] At step

[0414] , the method

[0400] comprises sending, by the transceiver unit

[0306] , an indication of successful detachment of the subscriber from the network.

[0091] In an exemplary aspect of the present disclosure, the method

[0400] further comprises checking, by a processing unit

[0302] , the appropriateness of permissions of a user. In an embodiment, appropriateness herein refers to evaluation of whether a user has correct rights or privileges to perform a specific action within the system

[0300] , For example, before proceeding with the detachment command, the system

[0300] may check if the user has necessary permissions to perform that action. This may be done through a validation step that may verify the user’s credentials.

[0092] In an exemplary aspect of the present disclosure, the successful validation result is an event when the permissions of the user are appropriate, and the unsuccessful validation result is an event when the permissions of the user are inappropriate.

[0093] In an exemplary aspect of the present disclosure, the one or more network nodes

[0312] comprises at least one of an access and mobility management function (AMF)

[0106] and a session management function (SMF)

[0108] ,

[0094] In an exemplary aspect of the present disclosure, prior to the triggering, by the triggering unit

[0310] , the terminate request command for the one or more network nodes

[0312] , the method

[0400] comprises determining, by a determination unit

[0310] , a state of the PCF

[0122] , The state of the PCF

[0122] is one of an active state, and an inactive state. The active state of the PCF

[0122] is when the PCF

[0122] is actively managing and enforcing policies in the communication network for users and network resources. While the inactive state of the PCF

[0122] is when the PCF

[0122] is not indulged in policy management.

[0095] In an exemplary aspect of the present disclosure, the method

[0400] further comprises triggering, by the triggering unit

[0310] , the terminate request command for the one or more network nodes

[0312] , in an event the state of the PCF

[0122] is determined as the active state.

[0096] In an exemplary aspect of the present disclosure, the detachment command is utilised for detaching the SUPI of the one or more network nodes

[0312] ,

[0097] In an exemplary aspect of the present disclosure, wherein prior to receiving the detachment command request, by the transceiver unit

[0306] , the method

[0400] comprises facilitating, by the processing unit

[0302] , a login at a user interface (UI)

[0304] of the PCF

[0122] , based on a user input by the user.

[0098] Thereafter, the method

[0400] terminates at step

[0416] ,

[0099] Referring to FIG. 5, an exemplary scenario of the present disclosure depicting a flow chart of a process

[0500] for detaching subscriber permanent identifier (SUPI) in absence of policy and charging control rule(s) in a network is shown, in accordance with the present disclosure. It is to be noted that a Policy and Charging Control (PCC) rules are a set of information elements enabling the detection of a service data flow and providing parameters for PCF

[0122] , The PCC rules enable policy control and proper charging for a service data flow. There are two different types of PCC rules: dynamic PCC rules and predefined PCC rules. The dynamic PCC rules are dynamically provisioned by the PCF

[0122] to the SMF

[0108] , These PCC rules may be either predefined or dynamically generated in the PCF

[0122] , The dynamic PCC rules can be installed, modified and removed at any time. While the predefined PCC rules are preconfigured in the SMF

[0108] , The predefined PCC rules can be activated or deactivated by the PCF

[0122] at any time. The predefined PCC rules within the PCF

[0122] may be grouped allowing the PCF

[0122] to dynamically activate a set of PCC rules. The process

[0500] is performed in the following steps:At step

[0502] , a user (preferably a network administrator) login through a user interface (UI)

[0304] (whether through a command line interface or graphical user interface) of a policy control function (PCF)

[0122] , The user desires to trigger a subscriber permanent identifier (SUPI) detachment process by issuing “detachSUPI” command. For example, the user triggers the SUPI detachment process at an AMF

[0106] , then the user logins at the PCF

[0122] command line interface using the user login credentials. In an exemplary implementation of the present disclosure, if the desired network function is AMF

[0106] , then the detachment command may be “detachSUPI -intf amf ’. In another implementation, if the desired network function is SMF

[0108] , then the detachment command may be “detachSUPI -intf smf’. In yet another implementation, if the desired network function is both AMF

[0106] and the SMF

[0108] , then the detachment command may be “detachSUPI -intf all”.At step

[0504] , after the “detachSUPI” command is received at the UI

[0304] of the PCF

[0122] , a state of the PCF

[0122] is checked for being active. If the state of the PCF

[0122] is active, then the process

[0500] proceeds to step

[0506] otherwise a message “PCF

[0122] not in active state, SUPI cannot be detached” is prompted as an error response may be received at the UI

[0304] ,At step

[0506] , the process

[0500] sends terminate request to AMF

[0106] / SMF

[0108] on receiving user input. This is done after checking whether permissions of the user are appropriate or not, and in case the user’s permissions are appropriate, the terminate request is triggered. For example, if case the desired network function is AMF

[0106] , then the terminate request command may be “AMFTerminateNotify” upon execution of step

[0508] , In another example, if case the desired network function is SMF

[0108] , then the terminate request command may be “SMFTerminateNotify” upon execution of step

[0510] , The AMF Terminate request may be sent against the SUPI value received and thus terminates all the AMF sessions attached to the SUPI. Similarly, the SMF Terminate request may be sent against the SUPI value received and thus the SMF terminate request command may terminate all the SMF sessions attached to the SUPI. In another example, in case the desired network function is both the AMF

[0106] and the SMF

[0108] , then the terminate request command may be a combination of both “AMFTerminateNotify” and “SMFTerminateNotify”.Thereafter, the process

[0500] as disclosed by the present disclosure comprises sending a successful response indicating successful detachment of SUPI from the network and the process of detaching a subscriber / SUPI in the network is thus concluded.

[0100] In an example, the terminate request command may be “Npcf_SMPolicyControl_UpdateNotify Service Operation”. In general, the Npcf_SMPolicyControl_UpdateNotify Service Operation” provides updated Session Management related policies to an NF service consumer (SMF) or triggers the deletion of context of SM related policies. The following procedures using the “Npcf_SMPolicyControl_UpdateNotify service operation” are supported:- PCF initiated deletion of SM Policy Association of a PDU session.

[0101] In another example, the terminate request command may be an “Npcf AMPolicyControl UpdateNotify Service Operation”. The PCF may decide to update policies or to request the termination of a policy association and shall then use the “Npcf_AMPolicyControl_UpdateNotify Service Operation”. The following procedures using the“Npcf_AMPolicyControl_UpdateNotify Service Operation” are supported: policy update notification; and request for termination of the policy association.

[0102] Referring to FIG. 6, another exemplary scenario of the present disclosure showcasing a system

[0600] for detaching the SUPI in absence of the policy and charging control rule(s) in the network is shown, in accordance with exemplary implementations of the present disclosure. The system

[0600] comprises at least one user interface (UI)

[0304] connected to at least one policy control function (PCF)

[0122] , The system

[0600] further comprises at least one session management function (SMF)

[0108] and an access and mobility management function (AMF)

[0106] , Also, all of the components / units of the system

[0600] are assumed to be connected to each other unless otherwise indicated below. Also, in Fig. 6 only a few units are shown, however, the system

[0600] may comprise multiple such units or the system

[0600] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0600] may be present in a user device / equipment (UE)

[0314] (as shown in FIG.3) to implement the features of the present disclosure. The system

[0600] may be a part of the UE

[0314] or may be independent of but in communication with the UE

[0314] , In another implementation, the system

[0314] may reside in a server or a network entity. In yet another implementation, the system

[0314] may reside partly in the server / network entity and partly in the UE

[0314] , The system

[0600] is configured for detaching the SUPI in absence of the policy and charging control rule(s) in the network, with the help of the interconnection between the components / units of the system

[0600] ,

[0103] To detach subscriber permanent identifier (SUPI) in absence of policy and charging control rule, a user logins on the user interface (UI)

[0304] of the PCF

[0122] when the user desires to trigger the SUPI detachment process. For example, the user desires to trigger the SUPI detachment process at the AMF

[0106] , then the user may login at the UI

[0304] using the user login credentials.

[0104] Further, the PCF

[0122] receives a detachment command at the UI

[0304] , For example, if the desired network function is AMF

[0106] , then the detachment command may be “detachSupi - intf amf’. In another example, if the desired network function is SMF

[0108] , then the detachment command may be “detachSupi -intf smf ’. In another example, if the desired network function is both the AMF

[0106] and the SMF

[0108] , then the detachment command may be “detachSupi -intf all”.

[0105] In an implementation, the UI

[0304] is configured to receive the detachment command through a manual input. In an implementation, the UI

[0304] prompts with a question if same user input can be proceeded for all instances. Upon receiving a SUPI value for detachment of the subscriber, the PCF

[0122] checks whether the permissions of the user are appropriate or not, and in case the user’s permissions are appropriate, the PCF

[0122] triggers the detachment command.

[0106] Pertinently, the PCF

[0122] should be in an active state for detaching the SUPI. If the PCF

[0122] is not active, an error response may be received at the UI

[0304] , Further, the PCF

[0122] triggers a terminate request command in an event the PCF

[0122] is in active state. For example, if case the desired network function is AMF

[0106] , then the terminate request command may be “AMFTerminateNotify”. In another example, if case the desired network function is SMF

[0108] , then the terminate request command may be “SMFTerminateNotify”. The AMF Terminate request may be sent against the SUPI value received at the PCF

[0122] , The AMF terminate request command may terminate all AMF sessions attached to the SUPI. Similarly, the SMF Terminate request may be sent against the SUPI value received at the PCF

[0122] , The SMF terminate request command may terminate all SMF sessions attached to the SUPI. In another example, in case the desired network function is both the AMF

[0106] and the SMF

[0108] , then the terminate request command may be a combination of both “AMFTerminateNotify” and “SMFTerminateNotify”. Further, the PCF

[0122] sends a response indicating successful detachment of SUPI from the network.

[0107] The present disclosure further discloses a non-transitory computer readable storage medium, storing instructions for detaching a subscriber in a network, the storage medium comprising executable code which, when executed by one or more units of a system

[0300] , causes a transceiver unit

[0306] to receive a detachment command request at a policy control function (PCF)

[0122] , The detachment command request is related to a subscriber detachment process at one or more network nodes

[0312] , Further, the executable code which, when executed causes the transceiver unit

[0306] to receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. Further, the executable code which, when executed causes a generation unit

[0308] to generate one of a successful validation result, and an unsuccessful validation result. Further, the executable code which, when executed causes a triggering unit

[0310] to trigger a detachment command related to the subscriber detachment process at the one or more network nodes

[0312] , Further, the executable code which, when executed causes the triggering unit

[0310] to trigger a terminate request command for the one or more network node

[0312] , Further, the executable code which, when executed causes thetransceiver unit

[0306] to send an indication of successful detachment of a subscriber from the network.

[0108] The present disclosure also discloses a user equipment (UE)

[0314] for detaching a subscriber in a network. The UE

[0314] comprises a processing unit

[0302] configured to facilitate a login at a user interface (UI)

[0304] of a policy control function (PCF)

[0122] , based on a user input by a user. The UE

[0314] further comprises a transceiver unit

[0306] configured to receive a detachment command request at the PCF

[0122] , The detachment command request is related to a subscriber detachment process at one or more network nodes

[0312] , The transceiver unit

[0306] is further configured to receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered. The UE

[0314] further comprises a generation unit

[0308] configured to generate one of a successful validation result, and an unsuccessful validation result. The UE

[0314] further comprises a triggering unit

[0310] configured to trigger a detachment command related to the subscriber detachment process at the one or more network nodes

[0312] , The triggering unit

[0310] is further configured to trigger a terminate request command for the one or more network nodes

[0312] , The transceiver unit

[0306] is further configured to send an indication of successful detachment of a subscriber from the network.

[0109] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The 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.

[0110] As is evident from the above, the present disclosure provides a technically advanced solution for detaching subscriber permanent identifier (SUPI) in absence of policy and charging control rule. The advantage of this approach is that it releases the network resources by ensuring that the user is properly disconnected from the network. Further, the solution also facilitates accurate accounting for the user's session. In cases of network congestion, detaching SUPIs of inactive or idle users may help manage network resources more efficiently. This way, resources are made available for active users who need them. Further, detaching a SUPI can be used tomanage Quality of Service levels. For example, if a user's session violates certain Quality of Service thresholds, detaching their SUPI could be a way to enforce service quality policies.[OHl] 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.

Claims

We Claim:

1. A method [400] for detaching a subscriber in a network, the method [400] comprising: receiving, by a transceiver unit [306], a detachment command request at a policy control function (PCF) [122], wherein the detachment command request is related to a subscriber detachment process at one or more network nodes [312]; receiving, by the transceiver unit [306], a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered; generating, by a generating unit [308], one of a successful validation result, and an unsuccessful validation result; triggering, by a triggering unit [310], the detachment command related to the subscriber detachment process at the one or more network nodes [312]; triggering, by the triggering unit [310], a terminate request command for the one or more network nodes [312]; and sending, by the transceiver unit [306], an indication of successful detachment of the subscriber from the network.

2. The method [400] as claimed in claim 1, further comprising checking, by a processing unit [302], the appropriateness of permissions of a user.

3. The method [400] as claimed in claim 1, wherein the successful validation result is an event when the permissions of the user are appropriate, and the unsuccessful validation result is an event when the permissions of the user are inappropriate.

4. The method [400] as clamed in claim 1, wherein the one or more network nodes [312] comprises at least one of: an access and mobility management function (AMF) [106] and a session management function (SMF) [108],5. The method [400] as clamed in claim 1, wherein prior to the triggering, by the triggering unit [310], the terminate request command for the one or more network nodes [312], the method [400] comprises: determining, by a determination unit [310], a state of the PCF [122], wherein the state of the PCF [122] is one of: an active state, and an inactive state.

6. The method [400] as claimed in claim 1, wherein the method [400] further comprises triggering, by the triggering unit [310], the terminate request command for the one or more network nodes [312], in an event the state of the PCF [122] is determined as the active state.

7. The method [400] as claimed in claim 1, wherein the detachment command is utilised for detaching the SUPI of the one or more network nodes [312],8. The method [400] as claimed in claim 1, wherein prior to receiving the detachment command request, by the transceiver unit [306], the method [400] comprises: facilitating, by the processing unit [302], a login at a user interface (UI) [304] of the PCF [122], based on a user input by the user.

9. A system [300] for detaching a subscriber in a network, the system [300] comprising: a transceiver unit [306] configured to: o receive a detachment command request at a policy control function (PCF) [122], wherein the detachment command request is related to a subscriber detachment process at one or more network nodes [312]; o receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered; a generation unit [308] connected to at least the transceiver unit [306], the generation unit [308] configured to: o generate one of: a successful validation result, and an unsuccessful validation result; a triggering unit [310] connected to at least the generation unit [308], the triggering unit [310] configured to: o trigger the detachment command related to the subscriber detachment process at the one or more network nodes [312]; o trigger a terminate request command for the one or more network node [312]; and the transceiver unit [306] further configured to: o send an indication of successful detachment of the subscriber from the network.

10. The system [300] as claimed in claim 9, wherein a processing unit [302] is configured to check the appropriateness of permissions of a user.

11. The system [300] as claimed in claim 9, wherein the successful validation result is an event when the permissions of the user are appropriate, and the unsuccessful validation result is an event when the permissions of the user are inappropriate.

12. The system [300] as claimed in claim 9, wherein the one or more network nodes [312] comprises at least one of: an access and mobility management function (AMF) [106] and a session management function (SMF) [108],13. The system [300] as clamed in claim 9, wherein a determination unit [312] prior to triggering by the triggering unit [310], the terminate request command for the one or more network nodes [312], is configured to:determine a state of the PCF [122], wherein the state of the PCF [122] is one of: an active state, and an inactive state.

14. The system [300] as clamed in claim 9, wherein the triggering unit [310] is configured to trigger the terminate request command for the one or more network nodes [312] in an event the state of the PCF [122] is determined as the active state.

15. The system [300] as claimed in claim 9, wherein the detachment command is utilised for detaching the SUPI of the one or more network nodes [312],16. The system [300] as claimed in claim 9, wherein the processing unit [302], prior to receiving the detachment command request by the transceiver unit [306], is configured to: facilitate a login at a user interface (UI) [304] of the PCF [122], based on a user input by the user.

17. A user equipment (UE) [314] for detaching a subscriber in a network, the UE [314] comprising: a processing unit [302] configured to: o facilitate a login at a user interface (UI) [304] of a policy control function (PCF) [122], based on a user input by a user; a transceiver unit [306] connected to at least the processing unit [302], the transceiver unit [306] configured to: o receive a detachment command request at the PCF [122], wherein the detachment command request is related to a subscriber detachment process at one or more network nodes [312]; o receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered; a generation unit [308] connected to at least the transceiver unit [306], the generation unit [308] configured to: o generate one of a successful validation result, and an unsuccessful validation result; a triggering unit [310] connected to at least the generation unit [308], the triggering unit [310] configured to: o trigger a detachment command related to the subscriber detachment process at the one or more network nodes [312]; o trigger a terminate request command for the one or more network nodes [312]; and the transceiver unit [306] further configured to: o send an indication of successful detachment of the subscriber from the network.

18. A non-transitory computer-readable storage medium storing instruction for detaching a subscriber in a network, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [306] to: receive a detachment command request at a policy control function (PCF) [122], wherein the detachment command request is related to a subscriber detachment process at one or more network nodes [312]; receive a subscription permanent identifier (SUPI) value for which the subscriber detachment process is triggered; a generation unit [308] to: generate one of: a successful validation result, and an unsuccessful validation result; a triggering unit [310] to: trigger a detachment command related to the subscriber detachment process at the one or more network nodes [312]; trigger a terminate request command for the one or more network node [312]; and the transceiver unit [306] to: send an indication of successful detachment of the subscriber from the network.

Images