FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR HANDLING A RACE CONDITION IN A WIRELESS COMMUNICATION NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.
2
METHOD AND SYSTEM FOR HANDLING A RACE CONDITION IN A WIRELESS COMMUNICATION NETWORK
FIELD OF DISCLOSURE
5
[0001]
The present disclosure generally relates to network performance management systems. More particularly, embodiments of the present disclosure relate to a method and a system for handling a race condition in a wireless communication network.
10
BACKGROUND
[0002]
The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the 15 present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003]
Wireless communication technology has rapidly evolved over the past few 20 decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology 25 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 30 multiple devices simultaneously. With each generation, wireless communication
3
technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
[0004]
During the call flow in a 5G core communication network, the Policy Control Function (PCF) sends a Spending Limit Subscribe Request message to a 5 Charging Function (CHF) for every SM Policy Control Create message received from a Session Management Function (SMF). Further, in the production environment, it is often seen that Subsequent Delete and Attach of SMF sessions are close to each other in time thereby causing a race condition of SM Policy Create and Delete messages along with CHF Spending Limit Unsubscribe and subscribe 10 requests triggered by them respectively. This is due to the triggering of the Spending Limit Create and Delete messages at the CHF end. Additionally, this results in the deletion of subscription-info at the CHF which is not desired or favorable.
[0005]
Thus, there exists an imperative need to address and overcome the problem 15 of the above-mentioned race condition occurring due to SM Policy Control Delete and subsequent SM Policy Control Create Request and Spending Limit Subscribe and Unsubscribe requests triggered by them.
SUMMARY 20
[0006]
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. 25
[0007]
An aspect of the present disclosure may relate to a method for handling a race condition in a wireless communication network. The method includes receiving, by a transceiver unit of a Policy Control Function (PCF), a first create request from a Session Management Function (SMF). The method further includes 30 transmitting, by the transceiver unit of the PCF, a first subscribe request to a
4
Charging Function (CHF) in response to the first create request. The method further
includes receiving, by the transceiver unit of the PCF, a first delete request from the SMF. The method further includes receiving, by the transceiver unit of the PCF, a second create request from the SMF. The method further includes blocking, by a processing unit, a transmission of a first unsubscribe request in an event the second 5 create request is received within a predefined time interval after receiving the first delete request. The method further includes transmitting, by the transceiver unit of the PCF, a second subscribe request to the CHF in response to the second create request.
10
[0008]
In an exemplary aspect of the present disclosure, the method further comprises generating, by the processing unit of the PCF, the first subscribe request in response to receiving the first create request and the second subscribe request in response to receiving the second create request.
15
[0009]
In an exemplary aspect of the present disclosure, the method further comprises maintaining, by the processing unit of the PCF, a mapping of one or more create requests with one or more subscribe requests and one or more delete requests.
[0010]
In an exemplary aspect of the present disclosure, blocking the transmission 20 of the first unsubscribe request includes determining, by the processing unit from the mapping, whether the second create request is received within the predefined time interval after receiving the first delete request. Next, the method includes the step of blocking, by the processing unit, the transmission of the first unsubscribe request based on a confirmation, from the mapping, that the second create request 25 is received within the predefined time interval after the first delete request.
[0011]
In an exemplary aspect of the present disclosure, the first create request, the first delete request and the second create request contains a common subscriber identifier. 30
5
[0012]
Another aspect of the present disclosure may relate to a system for handling a race condition in a wireless communication network. The system comprises a transceiver unit configured to receive, at a Policy Control Function (PCF), a first create request from a Session Management Function (SMF). The transceiver unit is further configured to transmit, from the PCF, a first subscribe request to a Charging 5 Function (CHF) in response to the first create request. The transceiver unit is further configured to receive, at the PCF, a first delete request from the SMF. The transceiver unit is further configured to receive, at the PCF, a second create request from the SMF. The system comprises a processing unit. The processing unit is configured to block, at the PCF, a transmission of a first unsubscribe request in an 10 event the second create request is received within a predefined time interval after receiving the first delete request. The transceiver unit is further configured to transmit, from the PCF, a second subscribe request to the CHF in response to the second create request.
15
[0013]
Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for handling a race condition in a wireless communication network, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit to receive, at a Policy Control Function (PCF), a first create request from a 20 Session Management Function (SMF). The instructions when executed further cause the transceiver unit to transmit, from the PCF, a first subscribe request to a Charging Function (CHF) in response to the first create request. The instructions when executed further cause the transceiver unit to receive, at the PCF, a first delete request from the SMF. The instructions when executed further cause the transceiver 25 unit to receive, at the PCF, a second create request from the SMF. The instructions when executed further cause a processing unit to block, at the PCF, a transmission of a first unsubscribe request in an event the second create request is received within a predefined time interval after receiving the first delete request. The instructions when executed further cause the transceiver unit to transmit, from the PCF, a second 30 subscribe request to the CHF in response to the second create request.
6
OBJECTS OF THE DISCLOSURE
[0014]
Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. 5
[0015]
It is an object of the present disclosure to provide a system and a method for handling a race condition in a wireless communication network.
[0016]
It is another object of the present disclosure to provide a solution that 10 maintains mapped details of the corresponding requests of the SMF and CHF call flows at the PCF to handle race condition.
BRIEF DESCRIPTION OF THE DRAWINGS
15
[0017]
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 20 disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used 25 to implement such components.
[0018]
FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
30
7
[0019]
FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented, in accordance with exemplary implementation of the present disclosure.
[0020]
FIG. 3 illustrates an exemplary block diagram of a system for handling a 5 race condition in a wireless communication network, in accordance with exemplary implementations of the present disclosure.
[0021]
FIG. 4 illustrates a method flow diagram for handling a race condition in a wireless communication network, in accordance with exemplary implementations 10 of the present disclosure.
[0022]
FIG. 5 illustrates a process flow diagram for handling a race condition in a wireless communication network, in accordance with exemplary implementations of the present disclosure. 15
[0023]
The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION 20
[0024]
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 25 details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
30
8
[0025]
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 5 arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0026]
Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of 10 ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
15
[0027]
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process 20 is terminated when its operations are completed but could have additional steps not included in a figure.
[0028]
The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the 25 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 30 “includes,” “has,” “contains,” and other similar words are used in either the detailed
9
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.
[0029]
As used herein, a “processing unit” or “processor” or “operating processor” 5 includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific 10 Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor. 15
[0030]
As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device 20 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 25 contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
[0031]
As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a 30 form readable by a computer or similar machine. For example, a computer-readable
10
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. 5
[0032]
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 as a set of rules or protocols that define the communication or interaction of one or more modules or one or more units with 10 each other, which also includes the methods, functions, or procedures that may be called.
[0033]
All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a 15 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. 20
[0034]
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. 25
[0035]
As used herein, race condition refers to a situation that occurs when a device or system or a network function node attempt to perform two or more operations at the same time that result in affecting the overall task to be performed by the device or system or the network function node. Further, due to the nature of the device or 30
11
system
or the network function node, the operations are to be performed in the proper sequence to complete the task efficiently and reliably.
[0036]
As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-5 mentioned and other existing problems in this field of technology by providing a method and a system for handling a race condition in a wireless communication network.
[0037]
FIG. 1 illustrates an exemplary block diagram representation of 5th 10 generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in fig. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], 15 an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a 20 User Plane Function (UPF) [128], a data network (DN) [130], and a charging function (CHF) [132], 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.
25
[0038]
As used herein, a Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication. 30
12
[0039]
As used herein, an Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
5
[0040]
As used herein, a Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement. 10
[0041]
As used herein, a Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces. 15
[0042]
As used herein, an Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens. 20
[0043]
As used herein, a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. 25
[0044]
As used herein, a Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
30
13
[0045]
As used herein, a Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0046]
As used herein, a Network Repository Function (NRF) [120] is a network 5 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.
[0047]
As used herein, a Policy Control Function (PCF) [122] is a network function 10 responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
[0048]
As used herein, a Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including 15 authentication, authorization, and subscription information.
[0049]
As used herein, an Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 20
[0050]
As used herein, a User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
25
[0051]
As used herein, a Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, and private data network related services.
30
14
[0052]
As used herein, a Charging Function (CHF) [132] is a crucial component of the 5G core network responsible for accurately calculating and allocating charges for various services and resources used by subscribers.
[0053]
FIG. 2 illustrates an exemplary block diagram of a computing device [200] 5 upon which the features of the present disclosure may be implemented, in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for handling a race condition in a wireless communication network utilising the system [300]. In another implementation, the computing device [200] itself implements the 10 method for handling the race condition in a wireless communication network using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
15
[0054]
The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with the bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a 20 random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during the execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory 25 storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204]. 30
15
[0055]
A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for 5 displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction 10 information and command selections to the processor [204], and for controlling cursor movement on the display [212]. 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.
15
[0056]
The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware, and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the 20 computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the 25 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.
[0057]
The computing device [200] also may include a communication interface 30 [218] coupled to the bus [202]. The communication interface [218] provides a two-
16
way data communication coupling to a network link [
220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a 5 local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information. 10
[0058]
The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220], and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the 15 ISP [226], the local network [222], the host [224], and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
20
[0059]
Referring to FIG. 3, an exemplary block diagram of a system [300] for handling a race condition in a wireless communication network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302], and at least one processing unit [304]. Also, all of the components/ units of the system [300] are 25 assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units, or the system [300] may comprise any such numbers of said units, as required to implement the features of the present 30 disclosure. Further, in an implementation, the system [300] may be present in a user
17
device
/ user equipment [102] to implement the features of the present disclosure. The system [300] may be a part of the user device [102]/ or may be independent of but in communication with the user device [102] (may also referred to herein as a UE). In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly 5 in the server/ network entity and partly in the user device.
[0060]
The system [300] is configured for handling a race condition in a wireless communication network, with the help of the interconnection between the components/units of the system [300]. 10
[0061]
The system [300] includes a transceiver unit [302] configured to receive, at a Policy Control Function (PCF) [122], a first create request from a Session Management Function (SMF) [108].
15
[0062]
The transceiver unit [302] receives the first create request from a Session Management Function (SMF) [108] at the PCF [122]. In an exemplary aspect, the first create request includes a user or subscriber identifier such as but not limited to an International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Subscription Permanent Identifier (SUPI), etc. 20
[0063]
In an exemplary aspect, the first create request further includes session or policy creation, which indicates a spending limit to be set up with the CHF [132].
[0064]
In an exemplary aspect, the first create request includes a 25 Npcf_SMPolicyControl_Create service. In an exemplary aspect, the Npcf_SMPolicyControl_Create service operation provides a means for the SMF [108] to request the creation of a corresponding SM Policy Association with PCF [122]. Further, the Npcf_SMPolicyControl_Create is a request sent from the SMF to the PCF to create the SM policy associated with the PCF to receive the policy for 30 a PDU session. In a non-limiting embodiment, the Npcf_SMPolicyControl_Create
18
service operation includes a request for creation of a corresponding SM Policy
Association with PCF, provisioning of PCC rules, provisioning of policy control request triggers, and provisioning of charging-related information for PDU session.
[0065]
In an exemplary aspect, for the SM Policy Association establishment, the 5 SMF sends an HTTP POST request to the PCF [122] to create an "Individual SM Policy" resource. Further, the SMF also includes the SmPolicyContextData data structure in the payload body of the HTTP POST request in order to request the creation of a representation of the individual SM policy resource. Further, the SmPolicyContextData request includes but is not limited to the SUPI of the user 10 within the "supi" attribute; PDU Session Id within the "pduSessionId" attribute; and DNN within the "dnn" attribute.
[0066]
The transceiver unit [302] is further configured to transmit, from the PCF [122], a first subscribe request to a Charging Function (CHF) [132] in response to 15 the first create request. Upon receiving the first create request from the Session Management Function (SMF) [108], the transceiver unit [302] is configured to transmit, from the PCF [122] to the CHF [132], the first subscribe request.
[0067]
In an exemplary aspect, the first subscribe request includes 20 Nchf_SpendingLimitControl_Subscribe service operation. In an exemplary aspect, the Nchf_SpendingLimitControl_Subscribe service operation is used by the NF service consumer (e.g., PCF) to subscribe to the notification of changes in the status of the policy counters available and to retrieve the status of the policy counters for which the subscription is accepted. The subscribe service operation includes various 25 procedures such as initial spending limit retrieval, and intermediate spending limit report retrieval.
[0068]
In an exemplary aspect, the first subscribe request includes the SpendingLimitContext data structure that is provided in the request body which 30 further includes the subscription permanent identifier (SUPI) encoded in the "supi"
19
attribute; and the general public subscription identifier (GPSI) encoded in the "gpsi"
attribute.
[0069]
In an exemplary aspect, the SpendingLimitContext contains the information for the creation of a new individual spending limit retrieval subscription. 5
[0070]
The transceiver unit [302] is further configured to receive, at the PCF [122], a first delete request from the SMF [108].
[0071]
The transceiver unit [302] receives the first delete request from the SMF 10 [108] at the PCF [122] indicating that the subscription related to the previously created request should be removed. In an exemplary aspect, the first delete request is associated with the initially transmitted first create request.
[0072]
In an exemplary aspect, the first delete request includes 15 Npcf_SMPolicyControl_Delete Service Operation. In an exemplary aspect, the first delete request service operation provides a means for the NF service consumer (e.g., SMF) to delete the policy context associated with a PDU Session. More particularly, the Npcf_SMPolicyControl_Delete is a request from the SMF to delete the SM Policy Association and the associated resources. In an exemplary aspect, the 20 Npcf_SMPolicyControl_Delete service operation supports various procedures such as but not limited to deletion of the policy context associated with a PDU session, report accumulated usage, report access network information, report service data flow QoS monitoring, and network slice-related data rate policy control.
25
[0073]
In an exemplary aspect, the first delete request further includes SM Policy Association termination which occurs when an individual resource of the SM Policy Association collection is deleted, then the NF service consumer (e.g., SMF) shall invoke the Npcf_SMPolicyControl_Delete service operation towards the PCF [122] using an HTTP POST request. In an exemplary aspect, SmPolicyDeleteData refers 30
20
to parameters to be sent by the NF service consumer when the individual SM policy
is deleted.
[0074]
The transceiver unit [302] is further configured to receive, at the PCF [122], a second create request from the SMF [108]. The transceiver unit [302] is 5 configured to receive the second create request from the SMF [108], at the PCF [122].
[0075]
In an exemplary aspect, this second create request suggests the creation of a new session or policy creation, which indicates a new spending limit to be set up 10 with the CHF [132].
[0076]
In an exemplary aspect, the second create request further includes the Npcf_SMPolicyControl_Create service. In an exemplary aspect, the Npcf_SMPolicyControl_Create service operation provides a means for the SMF 15 [108] to request the creation of a corresponding SM Policy Association with the PCF [122].
[0077]
The system further includes a processing unit [304] connected at least with the transceiver unit [302]. The processing unit [304] is configured to block a 20 transmission of a first unsubscribe request in an event the second create request is received within a predefined time interval after receiving the first delete request. In an example, when the second create request is received within the predefined time interval after receiving the first delete request then the processing unit may discard the first unsubscribe request. 25
[0078]
The transceiver unit [302] is further configured to transmit, from the PCF [122], a second subscribe request to the CHF [132] in response to the second create request.
30
21
[0079]
Upon receiving the second create request from the Session Management Function (SMF) [108], the transceiver unit [302] is configured to transmit from the PCF [122] to the CHF [132], the second subscribe request.
[0080]
In an exemplary aspect, the second subscribe request includes 5 Nchf_SpendingLimitControl_Subscribe service operation. In an exemplary aspect,
the Nchf_SpendingLimitControl_Subscribe service operation is used by the NF service consumer to subscribe to notification of changes in the status of the policy counters available and to retrieve the status of the policy counters for which the subscription is accepted. The procedures related to the subscribe service operation 10 are initial spending limit retrieval and intermediate spending limit report retrieval.
[0081]
In an exemplary aspect, the second subscribe request includes the SpendingLimitContext data structure that is provided in the request body which further includes the subscription permanent identifier (SUPI) encoded in the "supi" 15 attribute; and the general public subscription identifier (GPSI) encoded in the "gpsi" attribute.
[0082]
In an exemplary aspect, SpendingLimitContext contains the information for the creation of a new individual spending limit retrieval subscription. 20
[0083]
In an exemplary aspect, the PCF transmits the second subscribe request with the CHF [132] so that the CHF may process the second subscribe request i.e. the newer subscription request before removing/deleting the existing subscription session. 25
[0084]
In an exemplary implementation, if the first unsubscribe request is received at the CHF after the second subscribe request, then the CHF session created by the second subscribe request will be removed based on the first unsubscribe request. To prevent removal of the CHF session, the PCF checks if the second create request 30 for the same SUPI that has been received at the PCF. In case the second create
22
request is received within a predefined time interval (e.g., 15 seconds), the PCF
then suppresses or blocks the transmission of the first unsubscribe request and sends the second subscribe request in response to the received second create request.
[0085]
In another embodiment of the present disclosure, the PCF may first send the 5 second subscribe request to the CHF and wait for an acknowledgment of the request from the CHF. If a positive response or the acknowledgment of the same is received at the PCF from the CHF, the PCF may transmit the first unsubscribe request for the same subscriber identifier to unsubscribe the previous session initiated because of the first subscribe request. To transmit the unsubscribe request post the reception 10 of a response from the CHF for the second subscribe request, the PCF uses a holding mechanism to hold the first unsubscribe request. As used herein, the holding mechanism may refer to the temporary storage of the first unsubscribe request in a repository by the PCF.
15
[0086]
The processing unit [304] is further configured to generate, at the PCF [122], the first subscribe request in response to receiving the first create request and the second subscribe request in response to receiving the second create request.
[0087]
In an exemplary aspect, the first create request, the first delete request and 20 the second create request contain a common subscriber identifier e.g., SUPI.
[0088]
In an exemplary aspect, the PCF [122] receives the first create request from the Session Management Function (SMF) [108], the processing unit [304] generates and sends the first subscribe request to the Charging Function (CHF) [132]. This 25 first subscribe request informs the CHF [122] about the new session or policy associated with the first create request, so the CHF [122] may apply the spending limits accordingly.
23
[0089]
In an exemplary aspect, upon receiving the second create request at the PCF [122], the processing unit [304] generates and sends a second subscribe request to the CHF [132]. This ensures that the CHF [132] updates its records to apply spending limits for the new session or policy associated with the second create request. 5
[0090]
The processing unit [304] is further configured to maintain, at the PCF [122], a mapping of one or more create requests with one or more subscribe requests and one or more delete requests.
10
[0091]
The processing unit [304] maps one or more create requests with one or more subscribe requests and one or more delete requests. In an exemplary aspect, the mapping keeps track of the relationships between the various requests and their statuses and specifically focuses on create, subscribe, and delete requests sent between the Session Management Function (SMF) [108] and the Charging Function 15 (CHF) [132]. In an exemplary aspect, the mapping of one or more create requests with one or more subscribe requests and one or more delete requests prevents race conditions where overlapping requests could lead to incorrect or inconsistent state changes in the CHF [122], thereby maintaining the integrity of session and subscription management in the network. In an example, the mapping of the one or 20 more create requests with one or more subscribe requests and the one or more delete requests may be stored in a tabular format so that the PCF may access the required information at the earliest to take a corresponding action such as blocking the transmission of the first unsubscribe request post the reception of a second create request within the predefined time interval of receiving the first delete request. 25
[0092]
In an implementation of the present disclosure, to block the transmission of the first unsubscribe request, the processing unit is configured to determine, from the mapping, whether the second create request is received within the predefined time interval after receiving the first delete request. Next, the processing unit is 30 configured to block the transmission of the first unsubscribe request based on a
24
confirmation, from the mapping, that the second create request is received within
the predefined time interval after the first delete request. The processing unit analyse the mapping to check whether the second create request has been received at the PCF or not. In case the second create request has been received at the PCF, then the PCF also checks the metadata associated with the second create request 5 and the first delete request. The metadata herein refers to details such as time, date, and location of receiving the first delete request and the second create request. Thereafter, the processing unit checks the difference between the time of receiving the first delete request and the second create request. After checking the difference (e.g., 10 seconds), the processing unit determines whether the second create request 10 is received within the predefined time interval or not. In case the second create request is received within the predefined time period interval (e.g., within 15 seconds), the processing unit blocks the first unsubscribe request and sends the second subscribe request to the CHF. In another embodiment, the PCF may not send any further requests to the CHF to continue the existing CHF session in case the 15 second create request is received for the same subscriber or user identifier.
[0093]
In an exemplary embodiment, the processing unit [304] blocks the first unsubscribe request if the second create request has already been received at the PCF within the predefined time interval. Thereafter, the processing unit [304] 20 prioritizes the second subscribe request over the first unsubscribe request for the transmission to the CHF. This blocking or suppressing of the first unsubscribe request ensures that the first subscription i.e., the old subscription is not removed untimely while the second subscription request i.e., the new subscription is still being processed, thereby avoiding race conditions. 25
[0094]
In an embodiment, the PCF may terminate or may not send the unsubscribe request to the CHF upon receiving a confirmation of the receipt of the first subscribe request at the CHF for the same subscriber identifier.
30
25
[0095]
Referring to FIG. 4, an exemplary method flow diagram [400] for handling a race condition in a wireless communication network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement 5 the features of the present disclosure. Also, as shown in Fig. 4, the method [400] starts at step [402].
[0096]
At step 404, the method [400] comprises receiving, by a transceiver unit of a Policy Control Function (PCF) [122], a first create request from a Session 10 Management Function (SMF) [108]. The transceiver unit [302] receives the first create request from the Session Management Function (SMF) [108] at the PCF [122]. In an exemplary aspect, the first create request includes user identifier such as but not limited to an International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Subscription Permanent Identifier 15 (SUPI) etc.
[0097]
In an exemplary aspect, the first create request further includes session or policy creation, which indicates a spending limit to be set up with the CHF [132]. In an exemplary aspect, the first create request further includes the 20 Npcf_SMPolicyControl_Create service.
[0098]
At step 406, the method [400] further comprises transmitting, by the transceiver unit of the PCF [122], a first subscribe request to a Charging Function (CHF) [132] in response to the first create request. Upon receiving the first create 25 request from the Session Management Function (SMF) [108], the transceiver unit [302] transmits from the PCF [122] to the CHF [132], the first subscribe request.
[0099]
In an exemplary aspect, the first subscribe request includes Nchf_SpendingLimitControl_Subscribe service operation. In an exemplary aspect, 30 the Nchf_SpendingLimitControl_Subscribe service operation is used by the NF
26
service consumer to subscribe to notification of changes in the status of the policy
counters available and to retrieve the status of the policy counters for which the subscription is accepted. The subscribe service operation includes various procedures such as initial spending limit retrieval, and intermediate spending limit report retrieval. 5
[0100]
At step 408, the method [400] further comprises receiving, by the transceiver unit [302] of the PCF [122], a first delete request from the SMF [108].
[0101]
The transceiver unit [302] receives the first delete request from the SMF 10 [108] at the PCF [122] indicating that the previously created request should be removed. In an exemplary aspect, the first delete request is associated with the initially transmitted first create request. In an exemplary aspect, the first delete request includes Npcf_SMPolicyControl_Delete Service Operation.
15
[0102]
At step 410, the method [400] further comprises receiving, by the transceiver unit [302] of the PCF [122], a second create request from the SMF [108]. The transceiver unit [302] receives the second create request from the SMF [108], at the PCF [122]. In an exemplary aspect, this second create request suggests creation of a new session or policy creation, which indicates a new spending limit 20 to be set up with the CHF [132].
[0103]
In an exemplary aspect, the second create request further includes the Npcf_SMPolicyControl_Create service.
25
[0104]
At step 412, the method [400] further comprises blocking, by a processing unit [304] of the PCF [122], a transmission of a first unsubscribe request in an event the second create request is received within a predefined time interval after receiving the first delete request. As used herein, blocking the transmission of the first unsubscribe request corresponds to discarding the first unsubscribe request. 30
27
[0105]
At step 414, the method [400] further comprises transmitting, by the transceiver unit of the PCF [122], a second subscribe request to the CHF [132] in response to the second create request.
[0106]
The method [400] further comprises generating, by the processing unit of 5 the PCF, the first subscribe request in response to receiving the first create request and the second subscribe request in response to receiving the second create request.
[0107]
Upon receiving the second create request from the Session Management Function (SMF) [108], the transceiver unit [302] transmits from the PCF [122] to 10 the CHF [132], the second subscribe request. In an exemplary aspect, the second create request is associated with the second subscribe request.
[0108]
In an exemplary aspect, the second subscribe request includes Nchf_SpendingLimitControl_Subscribe service operation. 15
[0109]
The Nchf_SpendingLimitControl_Subscribe service operation is used by the NF service consumer to subscribe to notification of changes in the status of the policy counters available and to retrieve the status of the policy counters for which the subscription is accepted. The procedures related to the subscribe service 20 operation are initial spending limit retrieval and intermediate spending limit report retrieval.
[0110]
In an exemplary aspect, when the PCF [122] receives the first create request from the Session Management Function (SMF) [108], then the processing unit 25 [304] generates and sends the first subscribe request to the Charging Function (CHF) [132]. This first subscribe request informs the CHF [122] about the new session or policy associated with the first create request, so the CHF [122] may apply the spending limits accordingly.
30
28
[0111]
In an exemplary aspect, upon receiving the second create request at the PCF [122], the processing unit [304] generates and sends a second subscribe request to the CHF [132]. This ensures that the CHF [132] updates its records to apply spending limits for the new session or policy associated with the second create request. 5
[0112]
In an exemplary aspect, the first create request, the first delete request and the second create request contain the same subscriber identifier e.g., SUPI. Thus, the subscriber identifier is same or common in the first create request, the first delete request and the second create request. 10
[0113]
The method [400] further comprises maintaining, by the processing unit [304] of the PCF [122], a mapping of one or more create requests with one or more subscribe requests and one or more delete requests. The processing unit [304] maps one or more create requests with one or more subscribe requests and one or more 15 delete requests. In an exemplary aspect, the mapping keeps track of the relationships between the various requests and their statuses and specifically focuses on create, subscribe, and delete requests sent between the Session Management Function (SMF) [108] and the Charging Function (CHF) [132]. In an exemplary aspect, the mapping one or more create requests with one or more 20 subscribe requests and one or more delete requests prevents race conditions where overlapping requests could lead to incorrect or inconsistent state changes in the CHF [122], thereby maintaining the integrity of session and subscription management in the network.
25
[0114]
In an exemplary aspect, blocking the transmission of the first unsubscribe request includes determining, by the processing unit from the mapping, whether the second create request is received within the predefined time interval after receiving the first delete request. Next, the method includes blocking, by the processing unit, the transmission of the first unsubscribe request based on a confirmation, from the 30 mapping, that the second create request is received within the predefined time
29
interval after the first delete request. Thus, after blocking the first unsubscribe
request, the processing unit only sends the second subscribe request in response to the second create request to ensure that the user experience does not degrade or affect due to the race conditions. Thereafter, at step [416], the method [400] is terminated. 5
[0115]
Referring to FIG. 5, an exemplary process flow diagram [500] for handling a race condition in a wireless communication network, in accordance with exemplary implementations of the present disclosure is shown.
10
[0116]
At step S1, the process [500] comprises transmitting, from the SMF [108], a first create request (also referred to as SMF create request 1) to the PCF [122]. In an exemplary aspect, PCF [122] receives the first create request from a Session Management Function (SMF) [108]. In an exemplary aspect, the first create request includes user identifier such as but not limited to an International Mobile Subscriber 15 Identity (IMSI), International Mobile Equipment Identity (IMEI), Subscription Permanent Identifier (SUPI), etc. In an exemplary aspect, the first create request further includes a session creation or policy creation, which indicates a spending limit to be set up with the CHF [132].
20
[0117]
At step S2, the process [500] comprises transmitting, from the PCF [122], the first subscribe request (also referred to herein as CHF subscribe 1) associated with the first created request to the CHF [132]. In an exemplary aspect, upon receiving the first create request from the Session Management Function (SMF) [108], the transceiver unit [302] transmits from the PCF [122] to the CHF [132], 25 the first subscribe request.
[0118]
At step S3, the process [500] comprises transmitting, from the SMF [108], the first delete request (also referred to herein as SMF delete request 1). In an exemplary aspect, the transceiver unit [302] receives the first delete request from 30 the SMF [108] at the PCF [122] indicating that the previously created request
30
should be removed. In an exemplary aspect, the first delete request is associated
with the initially transmitted first create request.
[0119]
At step S4, the process [500] comprises transmitting, from the SMF [108], the second create request (also referred to herein as SMF create request 2) to the 5 PCF [122]. In an exemplary aspect, the transceiver unit [302] receives the second create request from the SMF [108], at the PCF [122]. In an exemplary aspect, this second create request suggests the creation of a new session or policy creation, which indicates a new spending limit to be set up with the CHF [132].
10
[0120]
At step S5, the process [500] comprises blocking, by a processing unit [304], a transmission of a first unsubscribe request in an event the second create request is received within a predefined time interval after receiving the first delete request. Thus, the process comprises blocking or discarding, at the PCF, the first unsubscribe request in case the second create request is received within the predefined time 15 interval after receiving the first delete request.
[0121]
At step S6, the process [500] comprises transmitting, from the PCF [122], the second subscribe request (also referred to herein as CHF subscribe 2) to the CHF [122]. Upon receiving the second create request from the Session 20 Management Function (SMF) [108], the transceiver unit [302] transmits from the PCF [122] to the CHF [132], the second subscribe request. In an exemplary aspect, the second create request is associated with the second subscribe request.
[0122]
The present disclosure further discloses a non-transitory computer-readable 25 storage medium storing instructions for handling a race condition in a wireless communication network, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit to receive, at a Policy Control Function (PCF), a first create request from a Session Management Function (SMF). The instructions when executed further cause the transceiver unit 30 to transmit, from the PCF, a first subscribe request to a Charging Function (CHF)
31
in response to the first create request. The instructions when executed further cause
the transceiver unit to receive, at the PCF, a first delete request from the SMF. The instructions when executed further cause the transceiver unit to receive, at the PCF, a second create request from the SMF. The instructions when executed further cause a processing unit to block a transmission of a first unsubscribe request in an event 5 the second create request is received within a predefined time interval after receiving the first delete request. The instructions when executed further cause the transceiver unit to transmit, from the PCF, a second subscribe request to the CHF in response to the second create request.
10
[0123]
As is evident from the above, the present disclosure provides a technically advanced solution for handling a race condition in a wireless communication network. The present invention provides a solution for the race condition occurring due to the non-sequential flow of the SM Policy Control Delete and subsequent SM Policy Control Create Request, and Spending Limit Subscribe and Unsubscribe 15 requests. The present invention provides the solution by providing a mapping of the requests sent in the SMF and CHF call flows at PCF. With the help of this mapping, the PCF locks the sending of the CHF unsubscribe request if a new or second create request is received at the PCF within the predefined time interval. By this measure, the present disclosure efficiently handles the race condition in the wireless 20 communication network.
[0124]
It should be noted that the terms "first", "second", "primary", "secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another. 25
[0125]
Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various 30 configurations and combinations thereof are within the scope of the disclosure. The
32
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. 5
[0126]
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 10 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.
15
33
We Claim:
1.
A method for handling a race condition in a wireless communication network, the method comprising:
-
receiving, by a transceiver unit [302] of a Policy Control Function (PCF) 5 [122], a first create request from a Session Management Function (SMF) [108];
-
transmitting, by the transceiver unit [302] of the PCF [122], a first subscribe request to a Charging Function (CHF) [132] in response to the first create request; 10
-
receiving, by the transceiver unit [302] of the PCF [122], a first delete request from the SMF [108];
-
receiving, by the transceiver unit [302] of the PCF [122], a second create request from the SMF [108];
-
blocking, by a processing unit [304], a transmission of a first unsubscribe 15 request in an event the second create request is received within a predefined time interval after receiving the first delete request; and
-
transmitting, by the transceiver unit [302] of the PCF [122], a second subscribe request to the CHF [132] in response to the second create request.
-
20
2.
The method as claimed in claim 1 further comprises generating, by the processing unit [304] of the PCF [122], the first subscribe request in response to receiving the first create request and the second subscribe request in response to receiving the second create request.
25
3.
The method as claimed in claim 1, the method further comprises maintaining, by the processing unit [304] of the PCF [122], a mapping of one or more create requests with one or more subscribe requests and one or more delete requests.
4.
The method as claimed in claim 3 wherein blocking the transmission of the first 30 unsubscribe request comprises:
34
determining, by the processing unit [304] from the mapping, whether the second create request is received within the predefined time interval after receiving the first delete request;
blocking, by the processing unit [304], the transmission of the first unsubscribe request based on a confirmation, from the mapping, that the second 5 create request is received within the predefined time interval after the first delete request.
5.
The method as claimed in claim 1, wherein the first create request, the first delete request and the second create request contains a common subscriber 10 identifier.
6.
A system for handling a race condition in a wireless communication network, the system comprising:
a transceiver unit [302] configured to: 15
-
receive, at a Policy Control Function (PCF) [122], a first create request from a Session Management Function (SMF) [108];
-
transmit, from the PCF [122], a first subscribe request to a Charging Function (CHF) [132] in response to the first create request;
-
receive, at the PCF [122], a first delete request from the SMF [108]; 20
-
receive, at the PCF [122], a second create request from the SMF [108];
a processing unit [304] connected at least with the transceiver unit [302], the processing unit [304] is configured to:
-
block, at the PCF [122], a transmission of a first unsubscribe request in an event the second create request is received within a predefined time interval 25 after receiving the first delete request;
the transceiver unit [302] configured to:
-
transmit, from the PCF [122], a second subscribe request to the CHF [132] in response to the second create request.
30
35
7.
The system as claimed in claim 6, wherein the processing unit [304] is further configured to generate, at the PCF [122], the first subscribe request in response to receiving the first create request and the second subscribe request in response to receiving the second create request. 5
8.
The system as claimed in claim 6, wherein the processing unit [304] is further configured to maintain, at the PCF [122], a mapping of one or more create requests with one or more subscribe requests and one or more delete requests.
9.
The system as claimed in claim 8, wherein to block the transmission of the first 10 unsubscribe request, the processing unit is configured to:
determine, from the mapping, whether the second create request is received within the predefined time interval after receiving the first delete request; and
block the transmission of the first unsubscribe request based on a confirmation, from the mapping, that the second create request is received 15 within the predefined time interval after the first delete request.
10.
The system as claimed in claim 6, wherein the first create request, the first delete request and the second create request contains a common subscriber identifier.