System and method for managing users within a network

Abstract

The present invention provides a system (108) for managing users within a network. The system (108) includes a processor (202), which receives requests via one or more computing devices (104), establishes a binding session with a primary control plane function based on a user session, receives an authorization authentication request (AAR) from an application function based on corruption of session data associated with the user session, sends the AAR to the control plane function to determine a specific control plane function associated with the primary control plane function that processes the user session based on the binding session, and also, based on receiving an error message from the specific control plane function, sends the AAR to a network function and is configured to process the user session via a secondary control plane function.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to wireless communication systems. More specifically, the present disclosure relates to systems and methods for managing users within a network.

Background Art

[0002] The following description of related art is intended to provide background information related to the field of the present disclosure. This section may include specific aspects of the technology that may be related to various features of the present disclosure. However, this section is only intended to deepen the reader's understanding of the present disclosure and does not admit prior art.

[0003] Generally, in a communication network, a service endpoint can be an address at a network node that uniquely identifies an entity that provides a service to a service consumer. A service endpoint can include an Internet Protocol (IP) address, or a combination of an IP address and a transport layer port number (which can also be referred to as an IP endpoint). Similarly, in a 5G communication network, a network node that provides a service can be called a producer network function (NF). A network node that consumes a service can be called a consumer NF. An NF can be both a producer NF and a consumer NF depending on whether it consumes or provides a service. There can be multiple service endpoints for a particular producer NF. A producer NF can register with a network function repository function (NRF). The NRF maintains NF profiles of available NF instances and the services they support. Further, a consumer NF can subscribe to receive information about producer NF instances registered with the NRF.

[0004] In addition to the consumer NF, another type of network node that can subscribe to receive information about NF service instances is the Service Communication Proxy (SCP). The SCP subscribes to the NRF and obtains reachability and service profile information about producer NF service instances. The consumer NF connects to the service communication proxy, and the service communication proxy distributes the traffic load among producer NF service instances that either provide the required services or directly route the traffic to the destination producer NF.

[0005] Furthermore, the process of creating a Packet Data Unit (PDU) session includes the process by which the Access and Mobility Management Function (AMF) selects a Session Management Function (SMF), and the process by which the SMF selects a User Plane Function (UPF). When selecting an SMF, the AMF may select an SMF that meets specific parameter requirements. For example, the AMF may send specific parameter requirements to the NRF, and the NRF may select an SMF that meets the parameter requirements and send the selection result to the AMF. Additionally, the Binding Support Function (BSF) enables other network functions (NFs), such as the Internet Protocol Multimedia Subsystem (IMS) Call Session Control Function (CSCF) and the Network Exposure Function (NEF), to identify the Policy Control Function (PCF) that holds the necessary policy and accounting information for each active User Equipment (UE) data session. Furthermore, the BSF may provide support management service operations such as registration, deregistration, and detection operations. In addition, the BSF also provides proxy support for the Receive (Rx) interface. As part of the proxy support for the Rx interface, the BSF may search for binding data saved during the registration operation, find the PCF currently processing the session, and forward an Authorization Authentication Request (AAR) message to the destination PCF.

[0006] Conventionally, there may be scenarios where the PCF returns an error code such as 5065 (indicating that the Internet Protocol Connectivity Access Network (IP-CAN) session is unavailable), or the PCF itself cannot be reached, or the BSF cannot find the binding data locally. In all these cases, the BSF returns an error to the Call Session Control Function (CSCF) / Application Function (AF) (CSCF / AF). In such cases, the subscriber session may not be released / re-established, and the subscriber may retry the call, resulting in the service to the subscriber being ultimately limited until the subscriber manually restarts each UE. When the PCF returns 5065 (or other error code, or unreachable), the BSF transparently passes the error to the AF / CSCF (via the Diameter Routing Agent (DRA)). Additionally, fourth generation (4G)-equivalent behavior where the DRA can release the Gx session may not be currently implemented.

[0007] However, since the BSF does not recognize the SMF (or PDU session ID), it may not be able to connect to the SMF to release the session. Furthermore, the BSF may store the binding data in the Supplementary Downlink (SDL). Therefore, if the BSF session management cannot reach the SDL (partially or completely), a scenario may occur where the BSF cannot find the binding data. In such a case, the BSF returns a 5065 error code to the AF / CSCF via the DRA. Furthermore, since the BSF may not recognize the SMF (or PDU session ID), it may not be able to connect to the SMF to release the session in some cases. In one scenario, if the BSF cannot find the binding data (note that in the case of a unique Subscription Permanent Identifier (SUPI) + Data Network Name (DNN) + slice, the BSF stores only a single binding), the BSF may return a 5065 error, and as a result, the BSF may not be able to connect to the SMF to release the session. Furthermore, in a conventional system using the Unified Data Manager function (UDM), the UDM / Home Subscriber Server (HSS) may initiate communication with the AMF / Mobility Management Entity (MME) via an external trigger (called via an Application Programming Interface (API)), and the subscriber's deregistration and re-registration may be performed. The BSF may be responsible for finding the case based on the response received from the PCF or the region. The UDM and the AMF / (HSS and MME) may need to interact according to the standard to ensure that the subscriber is first deregistered and then re-registered with the network. In the case of a 4G network, since the binding data for Gx and Rx exists in the DRA, all decisions including the Gx session release can be made by the DRA. In the case of 5G, the BSF does not have the Gx / N7 information for performing the subscriber's deregistration / re-registration.

[0008] Therefore, there is a need to provide a system and method for managing users within a network that can overcome the drawbacks of existing prior art. Purpose of the Disclosure

[0009] Some of the purposes of the present disclosure satisfied by at least one embodiment of this specification are listed below.

[0010] The purpose of the present disclosure is to provide a system and method for managing users within a network.

[0011] Another purpose of the present disclosure is to provide a system and method for unsubscribing / resubscribing subscribers by triggering an appropriate application programming interface (API) to the Unified Data Manager function (UDM).

[0012] Another purpose of the present disclosure is to overcome the overload of the Unified Data Manager function (UDM) by the Binding Support Function (BSF) in the case of a bulk session failure from the Policy Control Function (PCF) or BSF.

[0013] Another purpose of the present disclosure is to provide a system and method for deleting binding data (and / or diameter data) when it corresponds to a Subscription Permanent Identifier (SUPI) for which the UDM API has been triggered.

[0014] Yet another purpose of the present disclosure is to solve the problem of restarting a user equipment (UE) for Rx session establishment with network failures or errors, based on providing a network start action based on such a rare occurrence by initiating communication with the UDM and sending a "resubscribe" service operation to the UDM. Summary of the Invention

[0015] In this section, specific purposes and aspects of the present disclosure, which are detailed in subsequent sections, are briefly described. This summary is not intended to identify key features or delimit the scope of the claimed subject matter.

[0016] In a first aspect, the present disclosure provides a system for managing users within a network. The system includes a processor and a memory operably coupled to the memory. Instructions executable by the processor are stored in the memory. The processor is configured to receive requests via one or more computing devices. The computing devices are associated with one or more users. The requests are based on a user session requested by one or more users. The processor is further configured to establish a binding session with a primary control plane function based on the user session. The processor is further configured to receive an authentication authorization request (AAR) from an application function based on corruption of session data associated with the user session. The processor is further configured to send the AAR to a control plane function to determine a particular control plane function associated with the primary control plane function that processes the user session based on the binding session. The processor is further configured to send the AAR to a network function based on receiving an error message from the particular control plane function to process the user session via a secondary control plane function.

[0017] In one embodiment, the processor is further configured to re - establish the user session by receiving a protocol data unit (PDU) session from the secondary control plane function.

[0018] In one embodiment, the processor is further configured to end the user session by receiving a PDU session from the secondary control plane function.

[0019] In one embodiment, the secondary plane function is configured to process the user session via an access and mobility management function (AMF).

[0020] In one embodiment, the processor is further configured to terminate the binding session upon re - establishment of the user session and send an error message to the application function.

[0021] In one embodiment, the processor is further configured to automatically activate the secondary control plane function before sending the error message to the application function.

[0022] In one embodiment, the binding session includes any one or a combination of a subscription permanent identifier (SUPI), a data network name (DNN), and a network slice associated with the user session.

[0023] In one embodiment, the primary control plane function is a policy control function (PCF). The secondary control plane function is an integrated data manager function (UDM).

[0024] In a second aspect, the present disclosure provides a method for managing users within a network. The method includes receiving, by a processor associated with a system, a request via one or more computing devices. The request is based on a user session requested by one or more users. The method further includes establishing, by the processor, a binding session with a primary control plane function based on the user session. The method further includes receiving, by the processor, an authorization authentication request (AAR) from an application function based on corruption of session data associated with the user session. The method further includes transmitting, by the processor, the AAR to a control plane function to determine a specific control plane function associated with a primary control plane function that processes the user session based on the binding session. The method further includes transmitting, by the processor, the AAR to a network function based on receiving an error message from the specific control plane function to process the user session via a secondary control plane function.

[0025] In one embodiment, the method further includes re - establishing the user session by receiving, by the processor, a protocol data unit (PDU) session from the secondary control plane function.

[0026] In one embodiment, the method further includes ending the user session by receiving, by the processor, a PDU session from the secondary control plane function.

[0027] In one embodiment, the method further includes ending the binding session by the processor upon re - establishing the user session and transmitting an error message to the application function.

[0028] In one embodiment, the method further includes automatically activating, by a processor, a secondary control plane function before sending an error message to an application function.

[0029] In one embodiment, the binding session includes any one or a combination of a subscription permanent identifier (SUPI), a data network name (DNN), and a network slice associated with a user session.

[0030] In one embodiment, the primary control plane function is a policy control function (PCF). The secondary control plane function is an integrated data manager function (UDM).

[0031] In a third aspect, the present disclosure provides a non-transitory computer-readable medium including a processor with executable instructions. The processor is configured to receive a request via one or more computing devices. The computing devices are associated with one or more users. The request is based on a user session requested by one or more users. The processor is further configured to establish a binding session with a primary control plane function based on the user session. The processor is further configured to receive an authorization authentication request (AAR) from an application function based on corruption of session data associated with the user session. The processor is further configured to send the AAR to a control plane function to determine a specific control plane function associated with the primary control plane function that processes the user session based on the binding session. The processor is further configured to send the AAR to a network function based on receiving an error message from the specific control plane function to process the user session via a secondary control plane function.

Brief Description of the Drawings

[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the disclosed methods and systems, and like reference numerals refer to the same parts throughout the different drawings. The components in the drawings are not necessarily to scale, with emphasis instead being placed upon clearly illustrating the principles of the present disclosure. In some of the drawings, block diagrams are used to show components, which may not represent the internal circuitry of each component. Those skilled in the art will appreciate that the disclosure of such drawings includes the disclosure of the electrical, electronic, or circuit components generally used to implement such components.

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 4

Figure 5

DETAILED DESCRIPTION OF THE INVENTION

[0033] For the purposes of the following description, 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 the embodiments of the present disclosure may be practiced without these specific details. Some of the features described below can be used independently or in combination with other functions. By themselves, the individual features may or may not be able to solve all of the problems described above, or may only solve some of the problems described above. Some of the problems described above may not be completely solved by any of the features described below.

[0034] The following description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the purpose is to provide an effective description for those skilled in the art to implement the exemplary embodiments. It should be understood that various changes can be made to the functions and arrangements of the elements without departing from the spirit and scope of the described disclosure.

[0035] Various embodiments of the present disclosure provide systems and methods for managing users within a network. The present disclosure provides systems and methods for subscribing / unsubscribing subscribers by triggering an appropriate application programming interface (API) to an integrated data manager function (UDM). The present invention overcomes the overload of the integrated data manager function (UDM) by the binding support function (BSF) when a bulk session failure occurs from the policy control function (PCF) or BSF. The present disclosure provides systems and methods for deleting binding data (and / or diameter data) when the UDM API is triggered corresponding to a subscription permanent identifier (SUPI). The present invention solves the problem of restarting a user equipment (UE) for Rx session establishment with network failures or errors based on providing a network start action based on such a rare occurrence of a case by initiating communication with the UDM and sending a "reregistration" service operation to the UDM.

[0036] Referring to FIG. 1, an exemplary network architecture of a subscriber session release system (100) (also referred to as a network architecture (100)) is shown according to an embodiment of the present disclosure. In the subscriber session release system, or by the subscriber session release system, the system (110) of the present disclosure or simply the system (110) can be implemented. As shown, the exemplary architecture (100) can be equipped with a system (110) for managing users within a network for one or more subscribers, such as one or more users (102-1, 102-2, 102-3,..., 102-N) (individually referred to as user (102) and collectively as users (102)) associated with one or more first computing devices (104-1, 104-2,..., 104-N) (individually referred to as the first computing device (104) and collectively as the first computing device (104)).

[0037] The network can include, but is not limited to, the third generation (3G), the fourth generation (4G), the fifth generation (5G), the sixth generation (6G), New Radio (NR), Narrowband Internet of Things (NB-IoT), Open Radio Access Network (O-RAN), etc. The system (110) can further be operatively coupled to a second computing device (108) associated with an entity (114). The entity (114) can include a company, an organization, a university, a research facility, a business, a network operator, a vendor, a manufacturing unit, a network operator, a business, a defense facility, or other security-protected facilities. In some embodiments, the system (110) can also be associated with the second computing device (108). Further, the system (110) can also be communicatively coupled to one or more first computing devices (104) via a communication network (106).

[0038] System (110) can be coupled to a centralized server (112). The centralized server (112) can also be operatively coupled to one or more first computing devices (104) and second computing devices (108) via a communication network (106). In some embodiments, system (110) can also be associated with the centralized server (112).

[0039] In one embodiment, system (110) can be communicatively connected to a core network (not shown in FIG. 1), such as 3G, 4G, 5G, 6G, NR, NB-IoT, O-RAN, etc., to manage users within the network.

[0040] In one embodiment, system (110) can identify various cases where a subscriber needs to be deregistered and re-registered within the network by triggering an appropriate application programming interface (API) to the unified data manager function (UDM) through a binding support function (BSF) (not shown in FIG. 1). Additionally, even when a bulk session failure occurs from the policy control function (PCF) or BSF, the BSF may not overload the UDM. Furthermore, in the BSF, operations such as error codes, timeouts, connection status, etc. can be set by the user.

[0041] In one embodiment, the BSF may include a runtime configuration for supporting multiple Internet Protocol (IP) addresses (two local IPs and two GRIPs) as destinations for the UDM. The BSF also supports the user's ability to set an error code for retrying failed or timed-out transactions. Additionally, the local IP / port (on the BSF side) that can be used for communication with the UDM may be configured at runtime. Further, the maximum transactions per second (TPS) rate for API calls to the UDM may be configured at runtime. Additionally, the API used for the UDM may be user-configurable. This may include, but is not limited to, tokens, JSON bodies (including only the subscription permanent identifier (SUPI) as a variable in the JSON / header), flags, paths, etc. In one embodiment, the BSF may include a runtime flag to enable / disable the API used for the UDM.

[0042] In one embodiment, the BSF may support a manual command line for triggering the API for a specific SUPI. Additionally, the BSF may be able to delete binding data (and / or diameter data) if the UDM API was triggered for the corresponding SUPI. Further, the BSF may provide appropriate logs, alarms, and counters for deleting the binding data. Additionally, the UDM may also provide an API guide for implementation in the BSF. Also, the communication between the UDM and the Access Mobility Management Function (AMF) / Home Subscriber Server (HSS) and MME may be determined based on the API.

[0043] In one embodiment, when the system (110) receives an "Npcf_SMPolicyControl_Create" message, it may create a binding session via the PCF within the BSF by sending an "Nbsf_Management_Register" message to the BSF. Due to a database failure or network failure, the session for the SUPI in question may be deleted from the PCF, but not from the BSF or the Session Management Function (SMF).

[0044] In one embodiment, when a call is initiated, the system (110) may send an Authorization Authentication Request (AAR) message from a Call Session Control Function (CSCF) / Application Function (AF) (CSCF / AF) to the BSF.

[0045] In one embodiment, the system (110) may trigger the BSF to check the binding data of the problematic SUPI in the local DB and find an entry for the binding data. The BSF forwards the AAR to the appropriate PCF based on the entry. Since the PCF may not contain the session data of the SUPI, the PCF may respond to the BSF with a 5065 result code.

[0046] In one embodiment, when the system (110) receives an error code from the BSF, it may initiate communication with the UDM via the BSF and send a "reregistration" service operation to the UDM.

[0047] In one embodiment, when the system (110) receives a "reregistration" service operation from the UDM, it may internally interact with the AMF / SMF via the UDM and send a notification to the SMF to delete / re - establish the PDU session or determine whether to deregister and register the subscriber via the AMF.

[0048] In one embodiment, the system (110) may trigger the BSF to remove the binding data from itself and transfer a 5065 error code to the AF / CSCF.

[0049] In one embodiment, the system (110) can be, but is not limited to, a system-on-chip (SoC) system. In another embodiment, the capture, storage, matching, processing, decision-making, and actuation logic of on-site data can be coded using a microservices architecture (MSA), but is not limited thereto. To support portability, multiple microservices can be containerized and made event-based.

[0050] In one embodiment, the network architecture (100) can be modular and flexible to accommodate any kind of change to the system (110) because it can obtain proximity processing for managing users within the network. The details of the configuration of the system (110) can be changed on the spot.

[0051] In one embodiment, the system (110) can be remotely monitored, and the data, applications, and physical security of the system (110) can be fully ensured. In one embodiment, data can be densely collected, stored and processed in a cloud-based data lake, and practical insights can be extracted. Thus, aspects of predictive maintenance can be realized.

[0052] In one exemplary embodiment, the communication network (106) may include at least a portion of one or more networks, by way of example and not limitation, which have one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or combine one or more messages, packets, signals, waves, voltage or current levels, and combinations thereof. The network may include, but is not limited to, one or more of a wireless network, a wired network, the Internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad-hoc network, an infrastructure network, a public switched telephone network (PSTN), a cable network, a cellular network, a satellite network, an optical fiber network, and combinations thereof.

[0053] In another exemplary embodiment, the centralized server (112) may include or be composed of, but is not limited to, one or more of a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, cloud services or hardware that supports a portion of a system, a home server, hardware that runs a virtualized server, one or more processors that execute code that functions as a server, one or more machines that execute server-side functions described herein, at least a portion of any of the foregoing, and combinations thereof.

[0054] In one embodiment, the one or more first computing devices (104) and the one or more second computing devices (108) are Android (商標) , IOS (商標) , KaiOS (商標)It can communicate with the system (110) via a set of executable instructions that exist on any operating system including but not limited to these. In one embodiment, the one or more first computing devices (104) and the one or more second computing devices (108) can include any electrical, electronic, electromechanical, or device, or one or more combinations of the above devices, such as a mobile phone, smartphone, virtual reality (VR) device, augmented reality (AR) device, laptop, general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or other computing devices, but are not limited to these. Here, the computing device can include one or more built-in or externally coupled accessories including, but not limited to, input devices for receiving input from a user such as a camera, visual aids such as an audio assistant, microphone, keyboard, touchpad, touch-responsive screen, electronic pen, receiving devices for receiving any audio or visual signal in any frequency range, and transmitting devices capable of transmitting any audio or visual signal in any frequency range. It is understood that the one or more first computing devices (104) and the one or more second computing devices (108) are not limited to the aforementioned devices and various other devices can be used. A smart computing device is one type of system suitable for storing data and other personal or confidential information.

[0055] Figure 2 shows an exemplary block diagram representation of a system (110) for managing users within a network, proposed in accordance with an embodiment of the present disclosure. In one aspect, the system (110) may include one or more processors (202). The one or more processors (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuits, and / or any device that processes data based on operation instructions. Among other functions, the one or more processors (202) may be configured to obtain and execute computer-readable instructions stored in the memory (204) of the system (110). The memory (204) may be configured to store one or more computer-readable instructions or routines on a non-transitory computer-readable storage medium, and these instructions or routines may be obtained and executed to create or share data packets via a network service. The memory (204) may include any non-transitory storage device, including, for example, volatile memory such as random access memory (RAM), or non-volatile memory such as erasable programmable read-only memory (EPROM), flash memory, etc.

[0056] In one embodiment, the system (110) may include interfaces (206). The interfaces (206) may include various interfaces, such as, for example, data input / output (I / O) devices, interfaces for storage devices, etc. The interfaces (206) may facilitate the communication of the system (110). The interfaces (206) may also provide communication paths to one or more components of the system (110). Examples of such components may include, but are not limited to, processing units / engines (208), databases (210), etc.

[0057] The processing engine(s) (208) can be implemented as a combination of hardware and programming (e.g., programmable instructions) to implement one or more functions of the processing engine(s) (208). In the examples described herein, such a combination of hardware and programming can be implemented in several different ways. For example, the programming of the processing engine(s) (208) can be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware of the processing engine(s) (208) can include processing resources (e.g., one or more processors) for executing such instructions. In this embodiment, the machine-readable storage medium can store instructions that, when executed by the processing resources, implement the processing engine(s) (208). In such an embodiment, the system (110) can include a machine-readable storage medium that stores instructions and processing resources for executing the instructions, or the machine-readable storage medium can be separate but accessible to the system (110) and the processing resources. In other embodiments, the processing engine(s) (208) can be implemented by electronic circuitry.

[0058] The processing engine (208) can include one or more engines selected from any of a data acquisition engine (212), a subscriber session release engine (214), and other engines / units (216). The processing engine (208) can further perform, but is not limited to, edge-based microservice event processing.

[0059] In one embodiment, the data acquisition engine (212) can identify various cases where a subscriber needs to be deregistered and re-registered within the network by triggering an appropriate application programming interface (API) to the unified data manager function (UDM) via a binding support function (BSF) (not shown in FIG. 1). In one embodiment, upon receiving an "Npcf_SMPolicyControl_Create / Update" message, the subscriber session release engine (214) can create a binding session via the PCF within the BSF by sending an "Nbsf_Management_Register" message to the BSF. Due to a database failure or a network failure, the session of the SUPI in question can be deleted from the PCF, but not from the BSF or the session management function (SMF). In one embodiment, the subscriber session release engine (214) can trigger the BSF to remove binding data from itself and transfer a 5065 error code to the AF / CSCF.

[0060] FIG. 3A shows an exemplary block diagram representation of a system architecture (300) for managing users within a network, according to one embodiment of the present disclosure.

[0061] The system architecture (300) may include a Policy Control Function (PCF) (302), a Binding Support Function (BSF) (304), an Application Function (AF) / Call Session Control Function (CSCF) / (AF / CSCF) (306), and an Unified Data Manager function (UDM) (308). When the PCF (302) receives an "Npcf_SMPolicyControl_Create / Update" message, it may send an "Nbsf_Management_Register" message to the BSF (304) to create a binding session with the BSF (304) via the NBSF service-based interface (SBI) and the Receive (Rx) interface. The CSCF / AF (306) may send an Authorization Authentication Request (AAR) message to the BSF (304) at the start of a call. When the BSF (304) receives an error code from the BSF, it may initiate communication with the UDM (308) via a custom NUDM interface and send a "reregistration" service operation to the UDM (308). Exemplary Scenario 1

[0062] For example, in a scenario where the session has been removed from the PCF (302) or the BSF (304) but still exists in the SMF (not shown), a subscriber such as the user (102) may attempt to call another user (102). However, since the establishment of the Rx session may end in an error, the call may not be connected. This error may not affect the existing session in the SMF. Therefore, the user (102) may not be able to resolve the problem until the UE, such as the computing device (104), is restarted. Therefore, the UDM (308) may determine whether to send a notification to the SMF to delete / re-establish the PDU session or to deregister and then register the subscriber via the AMF. The function of deleting / re-establishing the PDU session or the function of deregistering and then registering the subscriber may be an extended function of the network-initiated action. Exemplary Scenario 2

[0063] If a network failure occurs, since there is no session information in the PCF (302) / BSF (304), the call from the user (102) may not be completed. As a result, the user experience may deteriorate, and the user (102) may not be able to solve the problem until the UE is restarted for re-registration. Releasing the subscriber session to automatically handle such a network failure may improve the user experience.

[0064] FIG. 3B shows an illustrative sequence diagram representation for managing users in a network according to an embodiment of the present disclosure.

[0065] In step (312), the SMF (310) may send an "Npcf_SMPolicyControl_Create / Update" message to the PSF (302). In step (314), the PSF (302) may send an "Nbsf_Management_Register" message to the BSF (304). In step (316), upon receiving the "Nbsf_Management_Register" message, the BSF (304) may create a binding session. When the binding session is created, a confirmation response "201 Created" may be sent to the SMF (310) via the PCF (302).

[0066] In step (318), due to a database failure or a network failure, the session of the problematic SUPI may be deleted from the PCF (302), but not from the BSF or the SMF (310). In step (320), the CSCF / AF (306) may send an authorization authentication request (AAR) message to the BSF (304) when a call is initiated.

[0067] In step (322), the BSF (304) checks the binding data of the problematic SUPI in the local database (DB) and may find an entry for the binding data. The BSF (304) transfers the AAR to the appropriate PCF (302) based on the entry. In step (324), the PCF (302) may not include the session data of the SUPI, and the PCF (302) may respond to the BSF (304) with a 5065 result code.

[0068] In step (326), upon receiving an error code, the BSF (304) may initiate communication with the UDM (308) and send a "re-registration" service operation to the UDM (308). In one embodiment, upon receiving the "re-registration" service operation, the UDM (308) may internally interact with the AMF / SMF (310). In step (318), the UDM (308) determines whether to send a notification to the SMF (310) to delete / re-establish the PDU session or to determine to unregister and re-register the subscriber via the AMF. In step (330), the BSF (304) may remove the binding data from itself and transfer a 5065 error code to the AF / CSCF (306).

[0069] Figure 4 shows an exemplary flowchart of a method (400) for managing users within a network, according to an embodiment of the present invention. In step (402), the method (400) includes receiving a request via one or more computing devices (104) by a processor (202) associated with a system (108). In step (404), the method (400) includes establishing a binding session with a primary control plane function based on a user session by the processor (202). In step (406), the method (400) includes receiving an AAR from an application function based on corruption of session data associated with the user session by the processor (202). In step (408), the method (400) includes transmitting the AAR to a control plane function and determining a specific control plane function associated with a primary control plane function that processes the user session based on the binding session by the processor (202). In step (410), the method (400) includes transmitting the AAR to a network function that processes the user session via a secondary control plane function by the processor (202) based on receiving an error message from the specific control plane function.

[0070] Figure 5 shows an exemplary computer system (500) in which embodiments of the present invention are utilized, or utilized with embodiments of the present invention, in accordance with embodiments of the present disclosure.

[0071] As shown in FIG. 5, a computer system (500) can include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port (560), and a processor (570). One of ordinary skill in the art will understand that a computer system may include multiple processors and communication ports. Examples of the processor (570) include, but are not limited to, Intel® Itanium® or Itanium 2 processor(s), AMD® Opteron® or Athlon MP® processor(s), Motorola® series processors, FortiSOC™ system-on-chip processors, or other future processors. The processor (570) may include various modules related to embodiments of the present disclosure. The communication port (560) can be any of an RS-232 port for use in a modem-based dial-up connection, a 10 / 100 Ethernet port, a gigabit or 10 gigabit port using copper wire or fiber optic, a serial port, a parallel port, or any other existing or future port. The communication port (560) can be selected according to the network, such as a local area network (LAN), a wide area network (WAN), or any network to which the computer system is connected. The memory (530) can be a random access memory (RAM) or any other dynamic storage device generally known in the art. The read-only memory (540) can be any static storage device(s), such as a programmable read-only memory (PROM) chip for storing static information such as startup or BIOS instructions of the processor (570), but is not limited thereto. The mass storage device (550) can be any current or future mass storage device solution capable of storing information and instructions.Exemplary high-capacity storage solutions include parallel advanced technology attachment (PATA) or serial advanced technology attachment (SATA) hard disk drives or solid state drives (internal or external, e.g., with a universal serial bus (USB) and / or Firewire interface), e.g., available from Seagate (e.g., Seagate Barracuda 782 family) or Hitachi (e.g., Hitachi Deskstar 13K800), one or more optical disks, redundant array of independent disks (RAID) storage, e.g., disk arrays (e.g., SATA arrays) available from various vendors such as Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc., and Enhance Technology, Inc., but are not limited thereto.

[0072] The bus (520) communicatively couples the processor(s) (570) to other memory, storage, and communication blocks. The bus (520) can be, for example, a peripheral component interconnect (PCI) / PCI extended (PCI-X) bus for connecting expansion cards, drives, and other subsystems, a small computer system interface (SCSI), a USB, etc., and can also be other buses such as a front side bus (FSB) that connects the processor (570) to a software system.

[0073] As an option, an operator and management interface (display, keyboard, cursor control device, etc.) is also connected to the bus (520), which can support direct interaction between the operator and the computer system. Other operator and management interfaces can be provided through a network connection connected via a communication port (560). External storage devices (510) can use all kinds of external hard drives, floppy drives, Iomega (registered trademark) Zip drives, compact disc-read only memory (CD-ROM), compact disc-rewritable (CD-RW), digital video disc-read only memory (DVD-ROM). The above components are only for the purpose of exemplifying various possibilities. The foregoing exemplary computer system is in no way intended to limit the scope of the present disclosure.

[0074] Although considerable emphasis has been placed on the preferred embodiments in the present disclosure, the present invention can take many embodiments without departing from the disclosed principles. It will be understood that many changes may be made to the preferred embodiments. These and other changes in the preferred embodiments of the present disclosure will be apparent to those skilled in the art from the disclosure herein. It should be clearly understood that the foregoing description is merely illustrative of the present disclosure and not limiting. Advantages of the Disclosure

[0075] The present invention provides a system and method for managing users within a network.

[0076] The present disclosure provides a system and method for unsubscribing / resubscribing subscribers by triggering an appropriate application programming interface (API) to an integrated data manager function (UDM).

[0077] The present invention overcomes the overload of the Unified Data Manager function (UDM) by the Binding Support Function (BSF) when a bulk session failure occurs from the Policy Control Function (PCF) or the BSF.

[0078] The present disclosure provides a system and method for deleting binding data (and / or diameter data) when the UDM API corresponds to a triggered Subscription Permanent Identifier (SUPI).

[0079] The present invention solves the problem of restarting a User Equipment (UE) for Rx session establishment with network failures or errors, based on providing a network start action based on such a rare occurrence, by initiating communication with the UDM and sending a "re-register" service operation to the UDM. Reservation of Rights Part of the disclosure of this patent document includes materials that are the subject of intellectual property rights owned by Jio Platforms Limited (JPL) or its related companies (hereinafter collectively referred to as the patent holders), such as (but not limited to) copyrights, designs, trademarks, integrated circuit (IC) layout designs, and / or trade dress protection. The patent holders do not object to the reproduction of the patent documents or patent disclosures described in the patent files or records of the Patent and Trademark Office by third parties, but reserve all other rights. All rights to such intellectual property are fully reserved by the patent holders. This disclosure complies with the technical specifications of the 3rd Generation Partnership Project (3GPP), such as 3GPP (registered trademark) TS 29.512, 3GPP TS 29.212, and 3GPP TS 29.521.

Claims

1. A system (108) for managing users within a network, the system (108) comprising: a processor (202); and a memory (204) operably coupled to the processor (202), the memory (204) storing instructions which, when executed by the processor (202), receive a request via one or more computing devices (104), the computing device (102) being associated with one or more users (102), the request being based on a user session requested by the one or more users (102); establish a binding session with a primary control plane function based on the user session; receive an authorization authentication request (AAR) from an application function based on corruption of session data associated with the user session. send the AAR to a control plane function to determine a specific control plane function associated with a primary control plane function that processes the user session based on the binding session; send the AAR to the network function based on receiving an error message from the specific control plane function to process the user session via the secondary control plane function.

2. The system (108) according to claim 1, wherein the processor (202) re - establishes the user session by receiving a protocol data unit (PDU) session from a secondary control plane function.

3. The system (108) according to claim 2, wherein the processor (202) terminates the user session by receiving a PDU session from the secondary control plane function.

4. The system (108) according to claim 2, wherein the secondary plane function processes the user session via an access mobility management function (AMF).

5. The system (108) according to claim 2, wherein the processor (202) terminates the binding session upon re - establishment of the user session and sends the error message to the application function.

6. The system (108) according to claim 1, wherein the processor (202) automatically activates the secondary control plane function before transmitting the error message to the application function.

7. The system (108) according to claim 1, wherein the binding session includes at least one of a subscription permanent identifier (SUPI), a data network name (DNN), and a network slice associated with the user session.

8. The system (108) according to claim 1, wherein the primary control plane function is a policy control function (PCF), and the secondary control plane function is an integrated data manager function (UDM).

9. A method for managing users in a network, comprising: receiving, by a processor (202) associated with a system (108), via one or more computing devices (104), a request based on a user session requested by one or more users (102); establishing, by the processor (202), a binding session with a primary control plane function based on the user session; receiving, by the processor (202), an authorization authentication request (AAR) from an application function based on session data corruption associated with the user session; transmitting, by the processor (202), the AAR to a control plane function to determine a specific control plane function associated with a primary control plane function that processes the user session based on the binding session; transmitting, by the processor (202), the AAR to a network function based on receiving an error message from the specific control plane function to process the user session via a secondary control plane function.

10. The method according to claim 9, further comprising re-establishing the user session by the processor (202) receiving a protocol data unit (PDU) session from the secondary control plane function.

11. The method according to claim 10, comprising the step of ending a user session by receiving a PDU session from the secondary control plane function by the processor (202).

12. The method according to claim 10, comprising the step of ending the binding session upon re - establishment of the user session by the processor (202) and transmitting the error message to the application function.

13. The method according to claim 10, comprising the step of automatically activating the secondary control plane function by the processor (202) before transmitting the error message to the application function.

14. The method according to claim 10, wherein the binding session includes at least one of a subscription permanent identifier (SUPI), a data network name (DNN), and a network slice associated with the user session.

15. The method according to claim 10, wherein the primary control plane function is a policy control function (PCF) and the secondary control plane function is a unified data manager function (UDM).

16. A non - transitory computer - readable medium comprising a processor with executable instructions, the instructions being: Receiving a request via one or more computing devices (104), wherein the computing device (102) is associated with one or more users (102) and the request is based on a user session requested by the one or more users (102), the step and Establishing a binding session with a primary control plane function based on the user session. Receiving an authorization authentication request (AAR) from an application function based on corruption of session data associated with the user session; and Transmitting the AAR to a control plane function to determine a specific control plane function associated with a primary control plane function that processes the user session based on the binding session. A non-transitory computer-readable medium that causes the processor to execute a step of transmitting the AAR to the network function based on receiving an error message from the specific control plane function and processing a user session via the secondary control plane function.

Images