Method and system for managing binding information of a session in a network

Abstract

The disclosure provides a method and a system for managing binding information of a session in a network (106) The method includes receiving request to create or update session from first network function. Further, the method includes extracting parameters from the received request. The method further includes determining whether binding information of the session exist with Binding Support Function (BSF) (212) based on the extracted parameters. Upon determining that the binding information of the session exist with BSF (212), the method includes determining overwriting of the binding information of the session that exist with BSF (212). The method includes transmitting register request to BSF (212) to create new binding information of the session based on determination. The register request includes binding identifiers (IDs) associated with each of the binding information of the session that exist with BSF (212). The method further includes overwriting binding information of the session with the new binding information of the session.

Description

METHOD AND SYSTEM FOR MANAGING BINDING INFORMATION OF A SESSION IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to JIO PLATFORMS LIMITED or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates to a field of telecommunications network. In particular, the present disclosure relates to a method and a system for managing one or more binding information of a session in a network.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term ‘Protocol Data Unit (PDU) Session’ as used herein in the specification refer to a logical connection established between a User Equipment (UE) and a Data Network (DN) in a fifth generation (5G) network system, which provides the user with Internet Protocol (IP) connectivity or Ethernet connectivity to external data networks.

[0005] The term ‘Binding Identifier (ID) as used herein in the specification refer to a unique identifier assigned by the BSF to each binding information of a session established between the PCF and the BSF. The binding ID uniquely represents a PCF for a UE or PDU session binding and is used for storage, retrieval, update, or deletion of binding information in the BSF database.

[0006] The term ‘Subscription Permanent Identifier (SUPI)’ used herein in the specification refers to a permanent, unique identifier assigned to a user in the 5G networks. The SUPI is used to identify the user across various network operations and services.

[0007] The term ‘Data Network Name (DNN)’, as used herein in the specification refers to an identifier of a data network that the UE connects to in the 5G network. The DNN specifies the data network that a user wishes to connect to within the 5G network. The DNN is equivalent to the Access Point Name (APN) in 4G systems. The DNN is crucial for directing user traffic to the appropriate external network, like the internet or an enterprise network.

[0008] The term ‘Policy Control Function (PCF)’, as used herein in the specification refers to a core network component of the 5G network architecture. The PCF in the 5G network is responsible for managing and enforcing policies that control network behaviour, such as Quality of Service (QoS), bandwidth allocation, and session management. The PCF communicates with other core network functions to ensure that user sessions are handled according to predefined rules.

[0009] The term ‘Session Management Function (SMF)’, as used herein in the specification refers to a core network component of the 5G network architecture. The SMF may handle session-related functions in 5G networks, such as session establishment, modification, and termination. The SMF also manages IP address allocation, the QoS, and interacts with the User Plane Function (UPF) for routing data.

[0010] The term ‘Session Management (SM) Policy Session’ as used herein in the specification refer to a policy control association established between the PCF and the SMF for managing the PDU session in a 5G network. The SM Policy Session governs session-specific rules and decisions such as Quality of Service (QoS) enforcement, charging, access control, and traffic steering.

[0011] The term ‘Access and Mobility Management Function (AMF)’ as used herein in the specification refers to a key control-plane function. The AMF manages mobility and connection states for UE and interfaces with both the core and radio access networks. Further, the AMF enables seamless mobility and session continuity, acting as a central controller for managing access and signalling between the UE and 5G core functions.

[0012] The term ‘Access and Mobility (AM) Policy Session’ as used herein in the specification refer to a policy control association established between the PCF and the AMF in a 5G network. The AM Policy Session governs mobility- and access- related policies for the UE, including registration management, mobility restrictions, access control rules, roaming behaviour, and network slice selection.

[0013] The term ‘Binding Support Function (BSF)’ as used herein in the specification refers to a key network function, responsible for managing and maintaining binding information of a session for network functions like the PCF. The BSF ensures that the correct bindings between the UE sessions and the network policies are maintained, allowing for efficient communication between different network functions.

[0014] The term ‘Information Element (IE)’ as used herein in the specification refers to a structured piece of data that is part of signalling messages exchanged between different network functions. The IES carry specific parameters such as session information, policy data, or user identifiers. For example, when the PCF communicates with the BSF, the PCF use IEs to include details like the binding identifier (ID), user identity, or network slice information.

[0015] The term ‘HTTP / 2’ as used herein in the specification refer to a version 2 of the Hypertext Transfer Protocol (HTTP) used for transferring data over the web. The HTTP / 2 allows multiple streams of data to be sent over a single connection, reducing latency. Further, the HTTP / 2 reduces the size of HTTP headers, improving load times and enables prioritization of requests, ensuring that more important resources are loaded first.

[0016] The term ‘HTTP / 3’ as used herein in the specification refer to a version 3 of the HTTP used for transferring data. The HTTP / 3 is built on top of Quick User Datagram Protocol (UDP) Internet Connections (QUIC), reducing latency, enhancing security and improving connection times. The HTTP / 3 allows seamless transfer of connections between networks (e.g., switching from Wireless-Fidelity (Wi-Fi) to mobile).

[0017] The term ‘Header’ as used herein in the specification refer to the metadata at the start of a message or packet, used in the HTTP / 2 or the HTTP / 3 communication protocols, which are part of a Service-Based Architecture (SBA). The headers contain information like the request type, target network function, or specific instructions for processing. For instance, the HTTP / 2 header might carry binding information or policy control data when the PCF interacts with other network functions like the BSF, enabling efficient routing and handling of messages without additional transactions.

[0018] The term ‘Counter’ as used herein in the specification refer to a measurable variable maintained by a network function such as the PCF or the BSF to record the number of occurrences of specific events, operations, or conditions during session or binding management.

[0019] These definitions are in addition to those expressed in the art.BACKGROUND

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

[0021] In a 5G communication system, a Policy Control Function (PCF) and a Binding Support Function (BSF) manage policy control and binding associations for User Equipments (UEs). During the establishment or modification of Access and Mobility (AM) Policy Sessions and Session Management (SM) Policy Sessions, the PCF communicates with the BSF to create and maintain binding information of a session. The binding information of the session map identifiers such as Subscription Permanent Identifier (SUPI), Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), and UE address information with the corresponding PCF instance. Each session is uniquely identified using a binding Identifier (ID) to ensure accurate session management and policy enforcement.

[0022] Conventionally, when a new SM Policy Session or AM Policy Session is created, the PCF may overwrite an existing session if certain conditions are met, for an example, when the number of concurrent sessions per subscriber exceeds operator-defined limits. In such overwrite scenarios, the PCF may send an explicit Deregister message to the BSF for the old binding and / or silently remove the old binding information at the PCF side without notifying the BSF. The conventional approach reduces signalling overhead and network transactions but introduces a significant drawback as old or unused bindings remain stored at the BSF. The persistence of stale binding information of the session at the BSF leads to inefficient resource utilization, increased database storage, and potential latency in binding lookups and message handling. Over time, the accumulation of obsolete binding information of the session can degrade BSF performance and negatively affect overall network efficiency.

[0023] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE

[0024] In an exemplary embodiment, a method for managing one or more binding information of a session in a network is described. The method includes receiving,by a Policy Control Function (PCF), a request to create or update a session from a first network function. Further, the method includes extracting, by the PCF, one or more parameters from the received request. The method further includes determining, by the PCF, whether one or more binding information of the session exist with a Binding Support Function (BSF) based on the one or more extracted parameters. Upon determining that the one or more binding information of the session exist with the BSF, the method includes determining, by the PCF, overwriting of the one or more binding information of the session that exist with the BSF. The method further includes transmitting, by the PCF, a register request to the BSF to create one or more new binding information of the session based on the determination. The register request includes one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF. Further, the method includes overwriting, by the PCF, the one or more binding information of the session with the one or more new binding information of the session.

[0025] In another exemplary embodiment, a method for managing one or more binding information of a session in the network is described. The method includes receiving, by the BSF, the register request from the PCF. Further, the method includes determining, by the BSF, whether the register request comprises the one or more binding IDs. Upon determining that the register request comprises the one or more binding IDs, the method further includes checking, by the BSF, whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. The method further includes removing, by the BSF, each of the one or more binding information of the session corresponding to the one or more binding IDs.

[0026] In an embodiment, the first network function is one of an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).

[0027] In another embodiment, upon determining that the one or more binding information of the session does not exist with the BSF, the method includes transmitting, by the PCF, the register request to the BSF to create the one or more new binding information of the session. Further, the method includes creating, by the BSF, the one or more new binding information of the session based on the register request.

[0028] In another embodiment, the method includes counting, by the BSF, instances of transmitting the register request to keep a record of removal of the one or more binding information of the session. Further, the method includes incrementing, by the BSF, a register request counter based on the counting of the instances of transmitting the register request that includes the one or more binding IDs, wherein the register request counter is configured at the PCF.

[0029] In another embodiment, the method includes counting, by the BSF, instances of transmitting the register request without the one or more binding IDs to keep a record of an absence of the one or more binding information of the session. Further, the method includes incrementing, by the BSF, an overwrite counter based on the counting of the instances of transmitting the register request without the one or more binding IDs. The overwrite counter is configured at the PCF.

[0030] In another embodiment, the one or more binding information of the session is a User Equipment (UE) session binding associated with an Access Management (AM) policy session, and wherein a UE binding ID is transmitted towards the BSF to create the UE session binding.

[0031] In another embodiment, the one or more binding information of the session is a Protocol Data Unit (PDU) session binding associated with a Session Management (SM) policy session, and wherein a PDU binding ID is transmitted towards the BSF to create the PDU session binding.

[0032] In another exemplary embodiment, a system for managing one or more binding information of a session in a network is described. The system includes aPolicy Control Function (PCF). The PCF is configured to receive a request to create or update a session from a first network function. Further, the PCF is configured to extract one or more parameters from the received request. Further, the PCF is configured to determine whether one or more binding information of the session exist with a Binding Support Function (BSF) based on the one or more extracted parameters. Upon determining that the one or more binding information of the session exist with the BSF, the PCF is further configured to determine overwriting of the one or more binding information of the session that exist with the BSF. The PCF is configured to transmit a register request to the BSF to create one or more new binding information of the session based on the determination. The register request includes one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF. Further, the PCF is configured to overwrite the one or more binding information of the session with the one or more new binding information of the session.

[0033] In another exemplary embodiment, a system for managing one or more binding information of the session in a network is described. The system includes a Binding Support Function (BSF). The BSF is configured to receive the register request from the PCF. Further, the BSF is configured to determine whether the register request comprises the one or more binding IDs. Upon determining that the register request comprises the one or more binding IDs, the BSF is configured to check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. Further, the BSF is configured to remove each of the one or more binding information of the session corresponding to the one or more binding IDs.

[0034] In another embodiment, a non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Policy Control Function (PCF) in a network, cause the one or more processors to receive a request to create or update a session from a first network function. Further, the PCF cause the one or more processors to extract one or more parameters from the received request. The PCF cause the one or more processors to determinewhether one or more binding information of the session exist with a Binding Support Function (BSF) based on the one or more extracted parameters. Upon determining that the one or more binding information of the session exist with the BSF, the PCF cause the one or more processors to determine overwriting of the one or more binding information of the session that exist with the BSF. The PCF may further cause the one or more processors to transmit a register request to the BSF to create one or more new binding information of the session based on the determination, wherein the register request comprises one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF. Further, the PCF cause the one or more processors to overwrite the one or more binding information of the session with the one or more new binding information of the session.

[0035] In yet another embodiment, a non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Binding Support Function (BSF) in a network, cause the one or more processors to receive the register request from the PCF. The BSF cause the one or more processors to determine whether the register request comprises the one or more binding IDs. Upon determining that the register request comprises the one or more binding IDs, the BSF cause the one or more processors to check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. The BSF cause the one or more processors to remove each of the one or more binding information of the session corresponding to the one or more binding IDs.OBJECTIVES OF THE PRESENT DISCLOSURE

[0036] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0037] An objective of the present disclosure is to provide a method and a system that minimize the accumulation of existing User Equipment (UE) session andProtocol Data Unit (PDU) session at Binding Support Function (BSF), optimizing resource utilization.

[0038] Another objective of the present disclosure is to provide a method and a system that improves the efficiency of Access Management (AM) policy session and Session Management (SM) policy session handling at the BSF by enabling the silent removal of existing binding information of the session without additional deregistration messages.

[0039] Another objective of the present disclosure is to prevent the adverse impact of existing binding information of the session at the BSF, such as increased latency and reduced performance in inter-network function communications.

[0040] Another objective of the present disclosure is to provide a method and a system to include existing binding Identifiers (IDs) in new session requests of Policy Control Function (PCF), reducing the need for extra transactions between the PCF and the BSF.

[0041] Another objective of the present disclosure is to provide a method and a system that allows the BSF to dynamically delete existing binding information of the session using a custom information element (IE) or Hypertext Transfer Protocol version 2 (HTTP / 2) header, as specified by the PCF.

[0042] Another objective of the present disclosure is to provide a method and a system that support high volumes of session operations without overburdening network resources.

[0043] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0045] FIG. 1 illustrates an exemplary network architecture of a system for managing one or more binding information of a session in a network, in accordance with an embodiment of the present disclosure.

[0046] FIG. 2 illustrates an exemplary block diagram of the system for managing the one or more binding information of the session in the network, in accordance with an embodiment of the present disclosure.

[0047] FIG. 3 illustrates an exemplary process flow for managing the one or more binding information of the session in the network, in accordance with an embodiment of the present disclosure.

[0048] FIG. 4 illustrates another exemplary process flow for managing the one or more binding information of the session in the network, in accordance with an embodiment of the present disclosure.

[0049] FIG. 5 illustrates another exemplary process flow depicting a registration of a Policy Control Function (PCF) for binding information in the network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 6 illustrates a flow diagram of a method for managing the one or more binding information of the session in the network, in accordance with an embodiment of the present disclosure.

[0051] FIG. 7 illustrates another flow diagram of a method for managing the one or more binding information of the session in the network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 8 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0053] The foregoing shall be more apparent from the following detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Policy Control Function (PCF)210 - Database12 - Binding Support Function (BSF)300 - Process Flow302 - Access Mobility Function (AMF) 00 - Process Flow402 - Session Management Function (SMF)500 - Process Flow502 - Network Function (NF) service consumer600 - Flow diagram700 - Flow diagram800 - A computer system810 - External Storage Device820 - Bus830 - Main Memory840 - Read Only Memory850 - Mass Storage Device860 - Communication Port870 - ProcessorDETAILED DESCRIPTION

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

[0055] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0056] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0057] Also, it is noted that individual embodiment may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel orconcurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure . A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0058] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

[0059] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0060] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or“comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0061] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0062] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signalling Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0063] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0064] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. These advancements represent a significant leap forward from previous generations,enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way to connect and interact with technology.

[0065] In a 5th Generation (5G) network, a Policy Control Function (PCF) plays important role in enforcing policies related to network usage and managing sessions for users. The session refers to a specific communication instance between a user equipment (UE) and the 5G network, governed by certain policies such as Quality of service (QoS), resource allocation, and traffic steering. During session creation or updates, the PCF communicates with a Binding Support Function (BSF) to establish or modify the binding information of a session for the UE.

[0066] As per known standards, the PCF creates a UE session binding at the BSF during Access Mobility (AM) policy control create request / AM policy control update request. In an embodiment, the AM policy control create request may corresponds to “Npcf_AMPolicyControl_Create” service operation. The “Npcf_AMPolicyControl_Create” service operation is sent by the AMF to the PCF when the UE registers with the network or undergoes a mobility event such as a handover. The “Npcf_AMPolicyControl_Create” service operation creates an AM Policy association and provides corresponding policies to the AMF. The AMF selects the PCF and invokes the Npcf_AMPolicyControl_Create service operation by sending the HTTP POST request to the "AM Policy Associations" resource.

[0067] In another embodiment, the AM policy control update request may correspond to Npcf_AMPolicyControl_Update service operation. The AMF invokes the Npcf_AMPolicyControl_Update service operation to the (V-) PCF by sending the HTTP POST request to the "Individual AM Policy Association" resource with information on the conditions that have changed.

[0068] Further, the PCF creates PDU session binding at the BSF during Session Management (SM) policy control create request / SM policy control update request. In an embodiment, the SM policy control create request may correspond to “Npcf_SMPolicyControl_Create” service operation, configured to create a new session with the PCF at the BSF. The “Npcf_SMPolicyControl_Create” service operation is sent by the SMF to the PCF when the UE registers with the network or undergoes a mobility event such as a handover. The Npcf_SMPolicyControl_Create service operation creates an SM Policy Association with the PCF to receive the policy for the UE session or the PDU session. The PCF, based on the Npcf_SMPolicyControl_Create service operation creates the SM policy rules. The SMF receives a PDU session establishment request from the UE. The SMF selects the PCF and invokes the Npcf_SMPolicyControl_Create service operation by sending the HTTP POST request to the "SM Policies" resource. The request operation provides the needed information within the " SmPolicyContextData" .

[0069] In another embodiment, the SM policy control update request may correspond to Npcf_SMPolicyControl_Update service operation. The Npcf_SMPolicyControl_Update service operation requests to update the SM Policy association with the PCF to receive the updated policy when Policy Control Request Trigger condition is met.

[0070] When the PCF receives a request for creating or updating AM policy or SM policy, it is possible to limit the number of active sessions per Subscription Permanent Identifier (SUPI), based on at least one user-defined criteria. The user- defined criteria may include such as limiting the number of concurrent SM sessions per Data Network Name (DNN) and Network Slice, or the limiting the number of concurrent AM sessions per SUPI. When a new SM Policy Create and / or AM Policy Create is received at the PCF, and PCF need to take a decision to overwrite an existing session at the BSF. The PCF has options of either sending a deregister request for old binding or silent removal of old UE and / or PDU session bindings created with the BSF (i.e. without sending the deregister request for the old Bindingidentifier (ID) towards the BSF to save the number of transactions). During the silent removal of the old UE and / or PDU session bindings by the PCF created with the BSF, the existing binding information of the session is not explicitly deregistered with the BSF. In an embodiment, the deregister request may include “Nbsf_Management_Deregister” Service Operation. The service operation allows the NF service consumer to delete existing PCF for a PDU session binding information for a UE at the BSF. The service operation is executed by deleting the corresponding "Individual PCF for a PDU Session Binding" resource. The operation is invoked by issuing an HTTP DELETE request targeting the resource URI representing the specific PCF for a PDU session binding information that is to be deleted. This may reduce the number of network transactions between the PCF and the BSF. However, the existing binding information of the session at the BSF introduces several problems. The existing binding information of the session add to stale UE session binding / PDU session binding at the BSF. The addition of stale sessions at the BSF may increase resource utilization as the BSF since the BSF has to maintain records of both new binding information of the session and existing binding information of the session. The existing binding information of the session result in overutilization of BSF resources, leading to reduced network efficiency. Additionally, higher resource usage at the BSF can increase the latency of internetwork function communication, particularly in handling messages, degrading overall network performance. Finally, the accumulation of existing binding information of the session requires additional resources for managing these existing bindings.

[0071] The silent removal of existing binding information of the UE session and existing binding information of the PDU sessions at the PCF results in an increasing number of existing binding information of the session that are left at the BSF. The existing binding information of the session at the BSF results in leading to several issues such as resource utilization at the BSF increases, causing potential performance degradation in the form of higher network function (NF) latency and resource wastage. Further, the management of the existing binding information ofthe session increases overall resource consumption, creating inefficiencies in network operations and degrading system performance over time. The existing bindings may correspond to, but not limited to, outdated binding information of the session, binding information of the session corresponding to the UE session or the PDU session to be removed, inactive binding information of the session, and binding information of the session corresponding to unresponsive UE session or the PDU sessions.

[0072] There is, therefore, a need for a method and a system that manages the existing binding information of the UE session and existing binding information of the PDU sessions at the BSF. The present disclosure provides an improved method and a system that ends the existing binding information of the session at the BSF and results in optimizing the resource utilization. The system removes existing binding information of the session without additional deregister requests, maintaining transaction efficiency while optimizing resource utilization at the BSF. Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1 - FIG. 8.

[0073] FIG. 1 illustrates an exemplary network architecture 100 of a system 108 for managing a binding information of the session in a network 106, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the network architecture 100 may include one or more User Equipments (UEs) 104-1, 104- 2... 104-N associated with one or more users 102-1, 102-2... 102 -N in an environment. A person of ordinary skill in the art will understand that one or more users 102-1, 102-2... 102-N may be collectively referred to as the users 102. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104-2. . . 104-N may be collectively referred to as the UE 104 or the UEs 104. Although only three UE 104 are depicted in FIG. 1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0074] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE 104 may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users 102 and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 104 may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloudcomputing system or any other device that is network-connected.

[0075] Additionally, in some embodiments, the UE 104 may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), awearable computer device (e.g., aheadmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill inthe art will appreciate that the UE 104 may not be restricted to the mentioned devices and various other devices may be used.

[0076] In FIG. 1, the UE 104 may communicate with the system 108 through the network 106 for sending or receiving various types of data. In an embodiment, the network 106 may include at least one of the 5G network, the 6G network, or the like. The network 106 may enable the UE 104 to communicate with other devices in the network architecture 100 and / or with the system 108. The network 106 may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0077] In an embodiment, the network 106 may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, the PSTN, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0078] In an embodiment, the UE 104 is communicatively coupled with the network 106. The network 106 may receive a connection request from the UE 104. The network 106 may send an acknowledgment of the connection request to the UE 104. The UE 104 may transmit a plurality of signals in response to the connection request.

[0079] In an embodiment, the system 108 may include a Policy Control Function (PCF) and a Binding Support Function (BSF) which may enable the system 108 to manage one or more binding information of the session in the network 106. The system 108 may receive a request to create or update a session from a first network function. Further, the system 108 may extract one or more parameters from the received request. The system 108 may determine whether one or more binding information of the session exist with the BSF based on the one or more extracted parameters. Upon determining that the one or more binding information of the session exist with the BSF, the system 108 may determine overwriting of the one or more binding information of the session that exist with the BSF. Further, the system 108 may transmit a register request to the BSF to create one or more new binding information of the session based on the determination. The register request includes one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF. The system 108 may then overwrite the one or more binding information of the session with the one or more new binding information of the session.

[0080] In another embodiment, the system 108 may receive the register request from the PCF. Further, the system 108 may determine whether the register request comprises the one or more binding IDs. Upon determining that the register request comprises the one or more binding IDs, the system 108 may check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. Further, the system 108 may remove each of the one or more binding information of the session corresponding to the one or more binding IDs.

[0081] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture 100 may perform functionsdescribed as being performed by one or more other components of the network architecture 100.

[0082] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 for managing binding information of the session in the network 106, in accordance with an embodiment of the disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0083] In an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 108. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0084] In an embodiment, the one or more processor 202 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the one or more processor 202. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the one or more processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the one or more processor 202 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the one or more processor 202. Insuch examples, the system 108 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the one or more processor 202 may be implemented by electronic circuitry. In an embodiment, the system 108 may include a Policy Control Function (PCF) 208 and a Binding Support Function (BSF) 212. The PCF 208 and the BSF 212 may be configured to communicate with the one or more processor 202 and one or more Network Function (NF) service consumer such as the AMF and the SMF. The NF service consumer may be present within the one or more processor of another system that is in communication with the system 108. In some embodiments, the PCF 208, the BSF 212, and the NF service consumer may be present within the one or more processor 202 of the system 108.

[0085] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the PCF 208, the BSF 212, and a database 210.

[0086] In an embodiment, the PCF 208 is configured to receive a request to create or update a session from a first network function. The first network function is one of an Access and Mobility Management Function (AMF) and a Session Management Function (SMF). The PCF 208 operates as a central decision-making entity in the 5G core network that manages policy rules for both Access and Mobility (AM) Policy Sessions and Session Management (SM) Policy Sessions. The PCF 208 receives a signaling request to either establish a new session or update an existing one. When the request originates from the Access and Mobility Management Function (AMF), the request typically concerns mobility-related or access-related policies. Examples include registration management, roamingrestrictions, or slice selection updates for a particular UE 104. The AMF notifies the PCF 208 so that the PCF 208 may generate or adjust the AM policy rules and binding information of the session accordingly. Further, When the request originates from a Session Management Function (SMF), the request relates to session-specific policies for a PDU session. The requests may involve Quality of Service (QoS) enforcement, charging control, or traffic routing rules. The SMF interacts with the PCF 208 to ensure that the correct SM Policy Session is created or updated for the ongoing data session of the UE 104.

[0087] Further, the PCF 208 may be configured to extract one or more parameters from the received request. Upon receiving a create / update request from AMF for AM policy, or from SMF for SM policy, the PCF 208 may parse the message and extracts the parameters required to scope, select, and bind the session with the extracted parameters. The extracted parameters may include UE and session identifiers such as SUPI, GPSI, DNN, and S-NSSAI, which uniquely scope the policy association and any BSF binding derived from it, UE addressing / access type IP and / or Ethernet identity to characterize the session ipv4Addr, ipv6Prefix (and addIpv6Prefixes), or macAddr48 (including TSN / Ethemet DS-TT cases), PCF / NF addressing & feature negotiation such as pcfFqdn, pcflpEndPoints, pcfDiamHost / pcfDiamRealm, and suppFeat, enabling the PCF 208 to negotiate optional features and later populate BSF 212 registrations consistently, and Overwrite for stale bindings such as an oldBindingld, if conveyed such as for SM policy flows, which the PCF 208 associates to the new session so that any downstream BSF 212 register may silently clear stale bindings.

[0088] In an embodiment, the PCF 208 may be configured to determine whether one or more binding information of the session exist with a Binding Support Function (BSF) 212 based on the one or more extracted parameters. The one or more binding information of the session is a UE session binding associated with a AM policy session, and a UE binding ID is transmitted towards the BSF 212 to create the UE session binding. Further, the one or more binding information of the session is a Protocol Data Unit (PDU) session binding associated with a SessionManagement (SM) policy session, and a PDU binding ID is transmitted towards the BSF 212 to create the PDU session binding. Once the PCF 208 extracts the relevant identifiers and attributes from the received request such as SUPI, GPSI, DNN, and S-NSSAI, the PCF 208 may evaluate whether an active binding information of the session already exists in the BSF 212 for the same subscriber or session context. The active binding information of the session may be a valid and currently stored association in the BSF 212 that links a subscriber or a session context (e.g., DNN, S-NSSAI, UE IP / MAC address to the PCF 208 managing the policy.

[0089] In some embodiments, when the extracted parameters indicate that the request concerns an Access and Mobility (AM) Policy Session, the PCF 208 check for a corresponding UE session binding in the BSF 212. In an embodiment, when the extracted parameters indicate that the request relates to the AM policy session, the PCF 208 uses the subscriber identity (e.g., SUPI) and session attributes (e.g., DNN, S-NSSAI, or AM Policy ID) to determine whether the UE binding already exists at the BSF 212. The PCF 208 queries the internal binding context table, where mapping between AM Policy Sessions and UE Binding IDs is maintained, and correlates this with the BSF’s binding registry. If no such binding exists, the PCF 208 transmits a Nbsf_Management_Register message towards the BSF 212 to create a new binding Identifier towards the BSF 212 using the Nbsf_Management_Register procedure, enabling the BSF 212 to create or update the UE binding entry that associates the SUPI with the serving PCF 208 instance responsible for AM policy decisions. When the extracted parameters indicate that the request relates to a Session Management (SM) Policy Session, the PCF 208 checks for an existing PDU session binding in the BSF 212. If absent, the PCF transmits a PDU Binding Identifier (PDU binding ID) to the BSF 212, also using the Nbsf_Management_Register procedure. The BSF 212 may use the identifier to create or update the PDU session binding, which links the subscriber’s session context such as DNN, S-NSSAI, IP / MAC address with the PCF 208 instance that governs SM policy rules.

[0090] Upon determining that the one or more binding information of the session exist with the BSF 212, the PCF 208 may be configured to determine overwriting of the one or more binding information of the session that exist with the BSF 212. Once the PCF 208 identifies that an active binding information of the session already exists within the BSF 212 for a given subscriber or session context, the PCF 208 evaluates whether the existing binding information should be overwritten by a newly created session.

[0091] In an embodiment, the PCF 208 may be configured to transmit a register request to the BSF to create one or more new binding information of the session based on the determination. The new binding information of the session may be a fresh association created by the PCF 208 when a new AM Policy or SM Policy session is established. During this process, the PCF 208 generates a new UE or PDU binding identifier and registers it with the BSF 212. The register request includes one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF 212. After the PCF 208 determines that new bindings are required due to overwrite or new policy association, the PCF 208 may invoke the BSF registration procedure to create the corresponding binding resource. For PDU session bindings such as SM policy context, the PCF 208 sends an HTTP POST to the BSF’s Nbsf_Management_Register endpoint with a PcfBinding body carrying session scope (SUPI / GPSI. DNN, S-NSSAI, UE addressing, and PCF addressing. The BSF 212, upon successful creation, allocates and returns a new bindingid and stores the binding. The register request may include one or more existing binding identifiers as references for example, an oldB indingid field within PcfBinding. Each such identifier corresponds to a binding information of the session that already exists at the BSF 212 and is being superseded. When present, the BSF 212 searches for the referenced binding and silently removes it according to local policy, consolidating the creation of the new binding and cleanup of the old binding into a single transaction.

[0092] Further, the PCF 208 may be configured to overwrite the one or more binding information of the session with the one or more new binding information of the session. Once the PCF 208 decides that replacement is required, the PCF 208 may perform an overwrite by creating the new binding information of the session and instructing the BSF 212 to retire the corresponding existing binding information of the session within the same control flow. In an embodiment, the PCF 208 issues an Nbsf_Management_Register request carrying a PCf Binding data for the new PDU session. The body may include an old Binding Id that points to the existing BSF binding. Upon receipt, the BSF 212 creates the new binding and, if old Binding Id is present, silently removes the referenced old binding, eliminating the need for a separate deregistration transaction. For AM policy, the PCF 208 registers the new UE binding and conveys the identifier of the to-be -replaced UE binding such as via a custom IE or HTTP / 2 header. The BSF 212 processes the registration and deletes the old UE binding referenced by that identifier, keeping only the newly created UE binding active.

[0093] Upon determining that the one or more binding information of the session do not exist with the BSF 212, the PCF 208 may be configured to transmit the register request to the BSF to create the one or more new binding information of the session. When the PCF 208 establishes that no existing binding information of the session is present in the BSF 212 for the current AM or SM policy context, the PCF 208 initiates a fresh registration. The PCF 208 may invoke the Nbsf Management Register operation via an HTTP POST to the PCF 208 for a PDU Session Bindings collection supplying a PCF Binding data that includes the session scope such as SUPI / GPSI, DNN, S-NSSAI and UE addressing along with PCF addressing, creating a new PDU session binding at the BSF 212. Upon success, the BSF 212 creates and stores the binding and returns 201c Created with the newly assigned binding Id (resource URI in Location header). For AM policy control, the PCF 208 similarly creates a new UE binding by posting to the PCF 208 for a UE Bindings collection which results in BSF 212 instantiating the individual PCF 208 for a UE Binding resource and returning the corresponding identifier upon creation.

[0094] In some embodiments, the BSF 212 may be configured to receive the register request from the PCF 208. The BSF 212 acts as the NF service producer for binding creation. The BSF 212 receives a registration request from the PCF 20 over the Nbsf_Management service.

[0095] Further, the BSF 212 may be configured to determine whether the register request comprises the one or more binding IDs. When the BSF 212 receives a registration request from the PCF 208, the BSF 212 performs a validation check to determine whether the request contains one or more Binding Identifiers (IDs). The determination is critical because the presence or absence of binding IDs dictates how the BSF 212 processes the request.

[0096] Upon determining that the register request comprises the one or more binding IDs, the BSF 212 may be configured to check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF 212. Once the BSF 212 detects that a registration request received from the PCF 208 contains one or more Binding Identifiers (IDs), the BSF 212 proceeds to validate whether each referenced binding information of the session is present in its internal database. The BSF 212 performs a lookup operation against its stored binding records using the received Binding IDs. Each Binding ID serves as a unique key that identifies a specific binding information, allowing the BSF to quickly determine if the session is active, stale, or already removed.

[0097] Further, the BSF 212 may be configured to remove each of the one or more binding information of the session corresponding to the one or more binding IDs. The PCF 208 transmits the old Binding ID along with the request to create a new binding. By executing the removal in line with the registration process, the BSF 212 performs a “silent deletion”, eliminating the stale binding without requiring a separate deregistration transaction, reducing signalling overhead. If multiple Binding IDs are provided, the BSF 212 systematically iterates through them, removing each associated binding information of the session from the database. During a session, the PCF 208 establishes and manages binding informationassociated with an AM / SM policy instance. When a new session is created or updated, the PCF 208 evaluates whether an existing binding information of the session is active for the same subscriber context. If so, the PCF 208 associates the old binding identifier with the new session and forwards both to the BSF 212. The BSF 212 then removes the stale binding while registering the new one, ensuring that the session remains consistent, resource-efficient, and compliant with service continuity requirements without introducing excess deregistration signalling.

[0098] In an embodiment, the BSF 212 may create the one or more new binding information of the session based on the register request. Upon reception of a register request from the PCF 208, the BSF 212 behaves as the NF service producer and instantiates new binding information of the session resources corresponding to the request context. For PDU-session (SM policy) bindings, the BSF 212 receives an request to the PCF 208 for a PDU Session Bindings collection carrying a Pcf Binding data. The request provides the scope and addressing needed to create the binding. For UE-level (AM policy) bindings, the BSF 212 accepts a request to the PCF 208 for a UE Bindings collection to create an individual PCF 208 for a UE Binding. On successful processing of the request, the BSF 212 creates new binding information, assigns a binding Id, stores the binding, and returns 201 created with the resource representation and a Location header pointing to the created binding.

[0099] In an embodiment, the BSF 212 may count instances of receiving the register request to keep a record of removal of the one or more binding information of the session. Further, the BSF 212 may increase a register request counter based on the counting of the instances of transmitting the register request that includes the one or more binding IDs. The register request counter is configured at the PCF 208. The counters are used to provide auditable evidence of silent removal during overwrite flows and to monitor feature efficacy. For each register request received from the PCF 208, the BSF 212 performs an intake check. If the request includes one or more binding identifiers, the BSF 212 increments a register counter. The counter reflects how many overwrite flows were attempted via inline cleanup, and it is separate from outcome counters such as “old binding removed,” “old bindingnot found,” or “DB error while removing” that the BSF 212 also maintains for observability. When the BSF 212 removes a binding referenced by the identifier, it increments a successful-removal counter. In an embodiment, the PCF 208 maintains a configured register counter, which increments whenever it sends a register request that embeds an old binding identifier.

[0100] In another embodiment, the BSF 212 may count instances of receiving the register request without the one or more binding IDs to keep a record of an absence of the one or more binding information of the session. Further, the BSF 212 may increase an overwrite counter based on the counting of the instances of receiving the register request without the one or more binding IDs. The overwrite counter is configured at the PCF 208. When the BSF 212 receives a register request without any binding IDs, the BSF 212 classifies the event as a pure create / no-overwrite flow and increments a overwrite counter, maintaining a record that the PCF 208 did not signal any existing binding to be replaced, consistent with the requirement that no old Binding ID shall be included when none exists. In one implementation, the PCF 208 maintains a register counter and a overwrite counter. The BSF’s 212 overwrite count may be compared with the PCF’s sender-side no-ID count to validate interface integrity and confirm absence of overwrite activity for those transactions.

[0101] In an embodiment, the system 108 may include a database 210 that includes data (e.g., the one or more parameters, the existing binding information of the session, flags, counter, etc.) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor 202.

[0102] FIG. 3 illustrates an exemplary process flow 300 for managing binding information of the session in the network 106, in accordance with an embodiment of the present disclosure. The process flow 300 may be implemented by the one or more processor 202 implemented within or with the PCF 208, the BSF 212, and an Access and Mobility Management Function (AMF) 302. FIG. 3 is explained inconjunction with FIGS. 1 and 2. In FIG. 3, a communication flow between the AMF 302, the PCF 208, and the BSF 212 is depicted.

[0103] At step 304, the PCF 208 may have an existing binding information of the session with the BSF 212 associated with the AMF 302. The existing binding information of the session is associated with the Access Mobility (AM) policy session at the PCF 208. The existing binding information of the session is created when the AMF 302 initiates an AM policy request (e.g., during UE registration or mobility event), and the PCF 208 registers the corresponding UE binding with the BSF 212. Further, the UE 104 binding information (Bind2) associated with the existing binding information of the session is present at the PCF 208 and the BSF 212.

[0104] In an embodiment, the AMF 302 is responsible for handling the initial connection setup between the UE 104 and the network 106, including registration, authentication, and authorization of the UE 104. The AMF 302 manages connection state of the UE 104, ensuring the UE 104 is properly connected, and coordinates reconnections when the UE 104 moves between network nodes. However, during reconnection, at 306 the AMF 302 may transmit an AM policy control create request towards the PCF 208 to create a new session with the PCF 208 at the BSF 212. In an embodiment, the AM policy control create request may corresponds to “Npcf_AMPolicyControl_Create” service operation. The “Npcf_AMPolicyControl_Create” service operation is sent by the AMF 302 to the PCF 208 when the UE 104 registers with the network 106 or undergoes a mobility event such as a handover.

[0105] At 308, upon receiving the AM policy control create request, the PCF 208 determines whether to overwrite the existing AM policy session including old (existing) UE binding Identifiers (IDs) (Bind2) associated with the existing binding information.

[0106] At 310, the PCF 208 may transmit a Binding Support (BS) management register request to the BSF 212. In an embodiment, the BS management registerrequest may correspond to a “Nbsf_management_register” service operation including IE / header=old binding IE (i.e., bind2). The Nbsf_management_register service operation manages the binding information associated with the UE 104 or Protocol data units (PDU) sessions. The Nbsf_management_register service operation registers or updates the binding information for the UE session in the BSF 212. The Nbsf_management_register service operation allows a NF service consumer (e.g. PCF for a PDU session) to register the binding information of the session for the UE 104 in the BSF 212 by providing the user identity, the DNN, the UE address(es) and the selected PCF 208 address for a certain PDU Session to the BSF 212, and the BSF 212 stores the binding information. The NF service consumer shall invoke the Nbsf_Management_Register service operation to register the PCF 208 for a UE binding information in the BSF 212. The NF service consumer shall send for this an HTTP POST request with "{apiRoot} / nbsf- management / <apiVersion> / pcf-ue-bindings" as Resource URI representing the "PCF for a UE Bindings", to create a binding information for an "Individual PCF for a UE Binding" according to the information in the message body.

[0107] In an embodiment, the PCF 208 may create an entry for the old (existing) UE binding ID corresponding to the UE session. The PCF 208 send the existing UE binding ID along with the BS management register request to the BSF 212. The existing UE binding ID are embedded into the BS management register request in custom Information Element (IE) such as user defined name or custom header such as user defined HTTP / 2 header. The custom IE and custom header are used by the BSF 212 for removing existing UE binding ID. In some embodiments, the PCF 208 may include a register counter that may store the existing UE binding ID for a predefined time.

[0108] At 312, the BSF 212 may create session corresponding to the AM policy control create request with the PCF 208. The BSF 212 creates binding information for new register request. For custom lE / header received session is deleted. Further, the BSF 212 may determine the existing binding information of the sessions corresponding to the custom IE or the custom header. The BSF 212 then delete theexisting binding information of the session and increment the overwrite counter by 1. The overwrite counter may record the overwriting of the binding information of the session.

[0109] At 314, the BSF 212 may transmit a response message to the PCF 208. In an embodiment, the response message may include a “201” response referring to an HTTP status code that indicates successful resource creation. The 201 responses may include a reference to the location of the newly created resource, and other relevant metadata such as the binding ID, and session information.

[0110] At 316, upon receiving the response, the PCF 208 may also send a response message towards the AMF 302. In an embodiment, the response may correspond to the 201 response.[oni] FIG. 4 illustrates another exemplary process flow 400 for managing the binding information of the session in the network 106, in accordance with an embodiment of the present disclosure. The process flow 400 may be implemented by the one or more processor 202 implemented within or with the PCF 208, the BSF 212, and a Session Management Function (SMF) 402. FIG. 4 is explained in conjunction with FIGS. 1, 2, and 3. In FIG. 4, a communication flow between the SMF 402, the PCF 208, and the BSF 212 is depicted.

[0112] At 404, the PCF 208 may have a binding information of the session with the BSF 212 associated with the SMF 402. The binding information of the session is associated with the Session Management (SM) policy session at the PCF 208. Further, the PDU binding information (Bindl) is present at the PCF 208 and the BSF 212.

[0113] In an embodiment, the SMF 402 interacts with other network functions, such as the User Plane Function (UPF) and the AMF, to facilitate seamless connectivity and mobility for users 102, ensuring adherence to policies and security measures. However, during reconnection, at 406, the SMF 402 may transmit an SM policy control create request corresponding to “Npcf_SMPolicyControl_Create”service operation to create a new session with the PCF 208 at the BSF 212. The “Npcf_SMPolicyControl_Create” service operation is sent by the SMF 402 to the PCF 208 when the UE 104 registers with the network 106 or undergoes a mobility event such as a handover. The Npcf_SMPolicyControl_Create service operation creates an SM Policy Association with the PCF 208 to receive the policy for the UE session or the PDU session. The PCF 208, based on the Npcf_SMPolicyControl_Create service operation creates the SM policy rules.

[0114] At 408, upon receiving the SM policy control create request, the PCF 208 determines to overwrite the existing SM policy session including existing PDU binding Identifiers (IDs) associated with the old (existing) binding information of the PDU session (Bindl).

[0115] At 410, the PCF 208 may transmit the BS management register request to the BSF 212. The BS management register request may correspond to a “Nbsf_management_register” service operation including IE / header=old binding ID (i.e., bindl). The BS management register request manages the binding information associated with the UE 104 or Protocol data units (PDU) sessions. The BS management register request register or update the binding information for the UE session in the BSF 212.

[0116] At 412, the BSF 212 may create binding information of the session corresponding to the SM policy control create request with the PCF 208. The BSF 212 create binding for new register request. For custom lE / header received binding information of the session is deleted. Further, the BSF 212 may determine the existing binding information of the session corresponding to the custom IE or the custom header. In some embodiments, the BSF 212 does not receive existing Binding ID from the PCF 208. The BSF 212 may check the existing Binding ID received from the PCF 208 and lookup the same in the database 210. If the Binding ID is found for same SUPI, then the existing Binding is removed silently. The BSF 212 may also increment the corresponding counter indicating that Register messageis received with existing binding id and another counter indicating that existing binding is successfully removed.

[0117] In another embodiment, the BSF 212 checks the existing Binding ID received from the PCF 208 and lookup the same in database 210. If the Binding ID is not found for same SUPI, then the existing Binding information may be ignored by the BSF 212. The BSF 212 may increment the corresponding counter indicating that Register message is received with existing binding id and another counter indicating that existing binding are not found.

[0118] In yet another embodiment, the BSF 212 checks the existing Binding ID received from the PCF 208 and lookups the same in database 210, but database error occurs such as database down or database timeout, etc. In this case, the BSF 212 may increment the corresponding counter indicating that Register message is received with existing binding id and another counter indicating that existing binding is not found due to database error. It should be noted that in this case, the BSF 212 may look at other options to keep the information in cache with limited time or threshold), so that once database 210 is restored, existing binding information of the session may be removed from database 210 as well.

[0119] At 414, the BSF 212 may transmit a response message to the PCF 208. In an embodiment, the response message may include a “201” response referring to an HTTP status code that indicates successful resource creation. The 201 responses may include a reference to the location of the newly created resource, and other relevant metadata such as the binding ID, and session information.

[0120] At 416, upon receiving the response, the PCF 208 may also send a response message towards the SMF 402. The response message may correspond to the 201 response message.

[0121] FIG. 5 illustrates another exemplary process flow 500 depicting a registration of the PCF 208 for binding information of the session in the network 106, in accordance with an embodiment of the present disclosure. The process flow500 may be implemented by the one or more processor 202 implemented within or with the PCF 208, the BSF 212, and a Network Function (NF) service consumer 502 such as the AMF 302 and the SMF 402. FIG. 5 is explained in conjunction with FIGS. 1, 2, 3, and 4.

[0122] As depicted in FIG. 5, the NF service consumer 502 may invoke the Nbsf_Management_Register service operation to register the PDU session binding information for a UE 104 in the BSF 212. At step 504, the NF service consumer 502 may send an HTTP POST request with "{apiRoot} / nbsf- management / <apiVersion> / pcfBindings" as Resource URI representing the "PCF for a PDU Session Bindings”, to create a binding information for an "Individual PCF for a PDU Session Binding" according to the information (e.g. UE address(es), SUPI, GPSI, DNN, S-NSSAI) in the message body. When the "ExtendedSamePcf ' feature is not supported, the "PcfBinding" data structure provided in the request body may include, if the "MultiUeAddr" feature is not supported or not yet known, address information of the served UE consisting of either IP address information consisting of the IPv4 address encoded as "ipv4Addr" attribute; and / or the / 128 IPv6 address, the IPv6 address prefix or an IPv6 prefix shorter than / 64 encoded as "ipv6Prefix" attribute. The MAC address encoded as "macAddr48" attribute Otherwise, address information of the served UE consisting of any IP address information consisting of the IPv4 address encoded as "ipv4Addr" attribute, the / 128 IPv6 address, the IPv6 address prefix or an IPv6 prefix shorter than / 64 encoded as "ipv6Prefix" attribute and / or the additional / 128 IPv6 addresses, the IPv6 address prefixes or IPv6 prefixes shorter than / 64 encoded as "addIpv6Prefixes" attribute.

[0123] Further, the MAC address encoded as "macAddr48" attribute and / or the additional MAC addresses encoded as "addMacAddrs" attribute, PCF address information consisting of if the PCF 208 supports the Npcf_PolicyAuthorization service, the FQDN of the PCF 208 encoded as "pcfFqdn" attribute and / or a description of IP endpoints at the PCF 208 hosting the Npcf Policy Authorization service encoded as "pcflpEndPoints" attribute. Further, if the PCF 208 supports theRx interface, the Diameter host id of the PCF 208 encoded as "pcfDiamHost" and the Diameter realm of the PCF 208 encoded as"pcfDiamRealm" attributes DNN encoded as "dnn" attribute, S-NSSAI encoded as "snssai" attribute; and if the "SamePcf feature is supported and the PCF 208 determines based on operator policies that the same PCF 208 may be selected for the SM Policy associations.

[0124] Further, PCF 208 address information for Npcf_SMPolicyControl service consisting of the FQDN of the PCF 208 encoded as "pcfSmFqdn" attribute or a description of IP endpoints at the PCF 208 hosting the Npcf SMPolicyControl service encoded as "pcfSmlpEndPoints" attribute and the parameters combination for selecting the same PCF 208 encoded within the "paraCom" attribute if the PCF 208 registers the binding information for the indicated parameter combination for the first time. When the "SamePcf feature is supported, the PCF 208 omits the "paraCom" attribute when creates the corresponding binding information related to the subsequent PDU sessions for the same parameter combination. In an embodiment, the request may consist of SUPI encoded as "supi" attribute, GPSI encoded as "gpsi" attribute, IPv4 address domain encoded as "ipDomain" attribute, and framed routes consisting of one or more framed routes within the "ipv4FrameRouteList" attribute for IPv4, one or more framed routes within the "ipv6FrameRouteList" attribute for IPv6, and / or Old PDU Session Binding Id encoded as “oldB indingid” attribute.

[0125] When the "TimeSensitiveNetworking" feature or the "TimeSensitiveCommunication" feature is supported by the PCF 208, and for Ethernet type of PDU sessions, the address information of the served UE 104 contains the MAC address of the DS-TT port encoded in the "macAddr48" attribute as received by the PCF 208 when the SMF 402 reports the bridge information of the detected TSC user plane node. For the integration with time sensitive communication networks using IP type of applications, the address information of the served UE contains the UE IP address of the corresponding PDU session. When the "ExtendedSamePcf ' feature is supported the address information of the served UE 104 may be provided if available, i.e., the "ipv4Addr", the "ipv6Prefix" and / or"addIpv6Prefixes" atributes or the "macAddr48" and / or "addMacAddrs" atributes may be provided if available. When the "ExtendedSamePcf ' feature is supported the PCF 208 address for the Npcf_Policy Authorization and / or Rx interface may be provided if available, i.e., the "pcfFqdn" and / or the "pcflpEndPoints" atributes, and / or the "pcfDiamHost" and / or the "pcfDiamReahn" atributes may be provided if available.

[0126] Before requesting the BSF 212 to check if there is an existing PCF 208 binding information for the same UE ID, S-NSSAI and DNN combination registered by other PCF(s) 208, the PCF 208 determines whether the BSF 212 supports the "SamePcf and / or "ExtendedSamePcf1features either via local configuration or by checking the BSF 212 profile retrieved from the NRF. Upon the reception of an HTTP POST request with: "{apiRoot} / nbsf- management / <apiVersion> / pcfBindings" as Resource URI and "PcfBinding" data structure as request body, the BSF 212 may create new binding information, assign a bindingid, and store the binding information.

[0127] In an embodiment, the PCF 208 as NF service consumer 502 may provide PCF Id in "pcfld" atribute and recovery timestamp in "recoveryTime" atribute. The BSF 212 may use the "pcfld" atribute to supervise the status of the PCF 208 and perform necessary clean up upon status change of the PCF 208 later, and / or both the "pcfld" atribute and the "recoveryTime" atribute in clean up procedure. The PCF 208 as a NF service consumer 502 may provide PCF Set Id within the "pcfSetld" attribute and "bindLevel" attribute set to NF SET or provide PCF Set Id within the "pcfSetld" atribute, PCF instance Id within the "pcfld" atribute and "bindLevel" atribute set to NF_INSTANCE. If PCF 208 has provided old PDU Session Binding ID within the “oldBindingld” atribute, then BSF 212 may check for existing PDU Session Binding ID for matching value and the same may be handled as per local BSF policy e.g. same shall be deleted silently.

[0128] If the BSF 212 created an "Individual PCF for a PDU Session Binding" resource, at step 506, the BSF 212 may respond with "201 Created" status code withthe message body containing a representation of the created binding information. The BSF 212 shall include a Location HTTP header field containing the URI of the created binding information, i.e. "{apiRoot} / nbsf- management / <apiVersion> / pcfBindings / {bindingId}". If errors occur when processing the HTTP POST request, the PCF 208 may apply error handling procedures. If the "SamePcf ' feature is supported and the "paraCom" attribute is included in the HTTP POST message, the BSF 212 may check the received "paraCom" attribute. If the BSF detects that there is an existing PCF 208 binding information including the same "dnn", "snssai" and "supi" attribute values as each of the corresponding attribute values within the "paraCom" attribute, the BSF shall reject the request with an HTTP "403 Forbidden" status code and may include in the response the "ExtProblemDetails" data structure including the FQDN of the existing PCF 208 hosting the Npcf_SMPolicyControl service within the "pcfSmFqdn" attribute or the description of IP endpoints at the existing PCF 208 hosting the Npcf_SMPolicyControl service within the "pcfSmlpEndPoints" attribute of "BindingResp" data structure, and the "cause" attribute of the "ProblemDetails" data structure set to "EXISTING BINDING INFO FOUND".

[0129] FIG. 6 illustrates a flow diagram of a method 600 for managing the one or more binding information of the session in the network 106, in accordance with an embodiment of the present disclosure. The process flow 600 may be implemented by the one or more processor 202 implemented within or with the PCF 208, the BSF 212, and the NF service consumer 502 such as the AMF 302 and the SMF 402. FIG. 6 is explained in conjunction with FIGS. 1, 2, 3, 4, and 5.

[0130] At step 602, the PCF 208 may receive a request to create or update a session from a first network function. The first network function is one of an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).

[0131] At step 604, the PCF 208 may extract one or more parameters from the received request. The one or more parameters may include subscriber identity(SUPI), data network name (DNN), slice identifier (S-NSSAI), UE IP / MAC addressing, and serving network information. The one or more parameters determine the scope of the session and to identify or create corresponding binding information of the session at the BSF 212.

[0132] At step 606, the PCF 208 may be configured to determine whether one or more binding information of the session exist with a Binding Support Function (BSF) 212 based on the one or more extracted parameters. The one or more binding information of the session is a User Equipment (UE) session binding associated with an Access Management (AM) policy session, and a UE binding ID is transmitted towards the BSF 212 to create the UE session binding. Further, the one or more binding information of the session is a Protocol Data Unit (PDU) session binding associated with a Session Management (SM) policy session, and a PDU binding ID is transmitted towards the BSF 212 to create the PDU session binding.

[0133] Upon determining that the one or more binding information of the session exist with the BSF, at step 608, the PCF 208 may determine overwriting of the one or more binding information of the session that exist with the BSF 212. If existing bindings are detected, the PCF 208 evaluates whether they should be overwritten. Overwriting may be required if, for example, subscriber limits for concurrent sessions are reached or if operator policy mandates replacing an old binding with a new one.

[0134] At step 610, the PCF 208 may transmit a register request to the BSF to create one or more new binding information of the session based on the determination. The register request includes one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF 212. When overwrite is necessary, the PCF 208 transmits a register request to the BSF 212. The request contains the identifiers of the existing binding information of the session such as oldBindingld. The inclusion of the existing binding information IDs allows the BSF 212 to create new binding information of the sessions whilesimultaneously removing the referenced old ones, avoiding additional deregistration signalling.

[0135] Upon determining that the one or more binding information of the session do not exist with the BSF 212, the PCF 208 may transmit the register request to the BSF to create the one or more new binding information of the session. If the PCF 208 determines that no binding information of the session exist at the BSF 212, the PCF 208 sends a register request without any old Binding IDs. The BSF 212, upon receiving the request, creates fresh binding information of the session for the new policy associations, ensuring correct linkage between UE / PDU sessions and the PCF 208.

[0136] At step 612, the PCF 208 may overwrite the one or more binding information of the session with the one or more new binding information of the session. The PCF 208 completes the overwrite operation by ensuring the newly created binding information of the session replace the old ones in the BSF database. The overwriting occurs by associating the newly created AM / SM policy session with the identifier of the previously active binding information. At the time of registering the new binding with the BSF 212, the PCF 208 transmits the new binding information along with the old binding identifier in a dedicated IE or custom header. Upon receipt, the BSF 212 checks for the existence of the old binding in its database and, if found, deletes it while registering the new binding in its place.

[0137] FIG. 7 illustrates another flow diagram of a method 700 for managing the one or more binding information of the session in the network 106, in accordance with an embodiment of the present disclosure. The process flow 700 may be implemented by the one or more processor 202 implemented within or with the PCF 208, the BSF 212, and the NF service consumer 502 such as the AMF 302 and the SMF 402. FIG. 7 is explained in conjunction with FIGS. 1, 2, 3, 4, 5, and 6.

[0138] At step 702, the BSF 212 receive the register request from the PCF 208. The BSF 212 acts as the service producer for binding creation and receives an HTTP POST register request from the PCF.

[0139] At step 704, the BSF 212 may determine whether the register request comprises the one or more binding IDs. The BSF 212 inspects the payload to see whether it includes binding identifiers, e.g., an oldBindingld attribute that references an existing binding targeted for cleanup during a new registration.

[0140] Upon determining that the register request comprises the one or more binding IDs, at step 706, the BCF 212 may check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. The BSF 212 looks up each referenced binding in its database to confirm whether it exists (e.g., UE binding for AM policy or PDU binding for SM policy).

[0141] At step 708, the BSF 212 may remove each of the one or more binding information of the session corresponding to the one or more binding IDs. For each existing referenced binding, the BSF 212 deletes it silently as part of processing the same register transaction, avoiding a separate deregistration flow and preventing stale records.

[0142] In an embodiment, the BSF 212 may create the one or more new binding information of the session based on the register request. The BSF 212 creates and stores the new binding information, assigns a bindingid, and returns a 201 Created with the resource representation and location header.

[0143] In an embodiment, the BSF 212 may count instances of transmitting the register request to keep a record of removal of the one or more binding information of the session. Further, the BSF 212 may increment a register request counter based on the counting of the instances of transmitting the register request that includes the one or more binding IDs. The register request counter is configured at the PCF 208. For observability, events where the register request includes binding IDs are counted. The PCF 208 maintains a configured counter for “register-with-oldB indingid” so operators may reconcile sent vs. received and correlate with “removed / not-found / DB-error” outcomes.

[0144] In another embodiment, the BSF 212 may count instances of transmitting the register request without the one or more binding IDs to keep a record of an absence of the one or more binding information of the session. Further, the BSF 212 may increment an overwrite counter based on the counting of the instances of transmitting the register request without the one or more binding IDs. The overwrite counter is configured at the PCF 208. When a register request arrives without any binding IDs, the BSF 212 records that class of event (e.g., “register-without- oldB indingid (received)”). The PCF may maintain a configured ‘no-ID ’ / overwrite counter to confirm absence of overwrite activity.

[0145] FIG. 8 illustrates an exemplary computer system 800 in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 8, the computer system 800 may include an external storage device 810, a bus 820, a main memory 830, a read-only memory 840, a mass storage device 850, communication port(s) 860, and a processor 870. A person skilled in the art will appreciate that the computer system 800 may include more than one processor and communication ports. The processor 870 may include various modules associated with embodiments of the present disclosure. The communication port(s) 860 may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) 860 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 800 connects.

[0146] The main memory 830 may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 840 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor 870. The massstorage device 850 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device 850 includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

[0147] The bus 820 communicatively couples the processor 870 with the other memory, storage, and communication blocks. The bus 820 may be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 870 to the computer system 800.

[0148] Optionally, operator and administrative interfaces, e.g. a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus 820 to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 860. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 800 limit the scope of the present disclosure.

[0149] In an embodiment, the PCF 208 receives a policy create request from a network function. The at least one request may be, but not limited to, session management policy control request and access management policy control request. Further, the PCF 208 extracts one or more parameters from the received request. The one or more parameters may include access type, User Location Information (ULI), Subscription Information, Single Network Slice Selection Assistance Information (S-NSSAI), Data Network Name (DNN), Session Management Information, Quality of Service (QoS) Information, service Data Flow Descriptions (SDF), UE Identity, Internet protocol (IPv4 / IPv6) Addresses, etc. The PCF 208checks if at least one binding information of the session exists at a Binding Support Function (BSF) based on the one or more extracted parameters. Further, the PCF 208 transmits a register request along with the binding ID associated with the at least one existing session. Further, the PCF 208 creates at least one new session based on the register request. The register request is a message exchanged between the PCF 208 and the BSF 212. The PCF 208 further removes the binding ID from the at least one existing session corresponding to the register request.

[0150] In an embodiment, when the PCF makes a decision to overwrite the existing AM policy session or SM policy session, the PCF may check if existing UE session binding or PDU session binding is present for AM / SM Session to be overwritten. When existing UE session binding or PDU session binding is present for AM session / SM session to be overwritten, the PCF may create an entry for binding ID corresponding to UE session binding / PDU session binding to be silently discarded corresponding to newly created AM policy session / SM policy session.

[0151] In an embodiment, when the PCF decides to create the new UE session binding and / or PDU session binding towards the BSF, the PCF may include corresponding old silently deleted binding ID towards BSF in custom IE or custom header. In an embodiment, the custom IE may include a user defined name, and the custom header may include a user defined HTTP2 header. In an embodiment, the custom IE / custom header may be used by the BSF for deleting old silently deleted old binding ID. The PCF may ensure that if UE binding is created for overwrite (corresponding to AM policy session) then old UE binding ID is transmitted towards the BSF and similarly if PDU binding is created for overwrite (corresponding to SM policy session) then old PDU binding ID is transmitted towards the BSF.

[0152] In an embodiment, the UE session binding and / or PDU session binding towards the BSF is created based on AM policy control create request / AM policy control update request or SM policy control create request / SM policy control update request. In an embodiment, it may be possible that the even though overwritedecision may be taken when AM policy control create request / AM policy control create request is received at the PCF from the AMF and the SMF respectively, but the binding register request (BS management register request) is sent at the PCF at AM policy control update request or SM policy control update request. In an embodiment, the PCF must ensure that old binding ID is to be included irrespective of case if binding register message is sent for AM policy control create request / AM policy control update request or SM policy control create request / SM policy control update request.

[0153] In an embodiment, when the PCF determines that there is no existing binding ID which needs to be overwritten, then the PCF may not include old binding ID in the register request sent towards BSF.

[0154] In an embodiment, the PCF may include a counter for register request in which old binding ID information is sent towards the BSF. In an embodiment, the PCF may support a flag for performing runtime enable or disable of the above steps.

[0155] In an embodiment, the BSF may provide user defined custom IE name or custom header name in which PCF may send the old (existing) binding ID which the BSF may use for deleting old bindings which have been silently removed by PCF.

[0156] In an embodiment, when the BSF receives old binding information, the BSF may check to see if the old binding exists. When it is determined that the old binding exists, the BSF may remove the binding and increment the counter. When it is determined that the old binding does not exists, the BSF may increment the old binding not found for an overwrite counter. In both cases, the BSF may process the register message received from the PCF.

[0157] In an embodiment, the PCF may send the information for old binding ID that needs to be removed without need to send addition deregister request towards the BSF.

[0158] In an embodiment, the BSF may be able to delete old silently removed binding IDs at PCF without need to receive additional deregister request from the PCF.

[0159] In an embodiment, the disclosure provides a system for managing the one or more binding information of the session in the network. The system may include a Policy Control Function (PCF). The PCF may be configured to receive a request to create or update a session from a first network function. Further, the PCF is configured to extract one or more parameters from the received request. Further, the PCF is configured to determine whether one or more binding information of the session exist with a Binding Support Function (BSF) based on the one or more extracted parameters. Upon determining that the one or more binding information of the session exist with the BSF, the PCF is further configured to determine overwriting of the one or more binding information of the session that exist with the BSF. The PCF is configured to transmit a register request to the BSF to create one or more new binding information of the session based on the determination. The register request includes one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF. Further, the PCF is configured to overwrite the one or more binding information of the session with the one or more new binding information of the session.

[0160] In another embodiment, the disclosure provides a system for managing the one or more binding information of the session in the network. The system includes a Binding Support Function (BSF). The BSF is configured to receive the register request from the PCF. Further, the BSF is configured to determine whether the register request comprises the one or more binding IDs. Upon determining that the register request comprises the one or more binding IDs, the BSF is configured to check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. Further, the BSF is configured to remove each of the one or more binding information of the session corresponding to the one or more binding IDs.

[0161] In another embodiment, the disclosure provides a non-transitory computer- readable storage medium storing instructions that, when executed by one or more processors of a Policy Control Function (PCF) in a network, cause the one or more processors to receive a request to create or update a session from a first network function. Further, the PCF cause the one or more processors to extract one or more parameters from the received request. The PCF cause the one or more processors to determine whether one or more binding information of the session exist with a Binding Support Function (BSF) based on the one or more extracted parameters. Upon determining that the one or more binding information of the session exist with the BSF, the PCF cause the one or more processors to determine overwriting of the one or more binding information of the session that exist with the BSF. The PCF may further cause the one or more processors to transmit a register request to the BSF to create one or more new binding information of the session based on the determination, wherein the register request comprises one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF. Further, the PCF cause the one or more processors to overwrite the one or more binding information of the session with the one or more new binding information of the session.

[0162] In yet another embodiment, the disclosure provides a non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Binding Support Function (BSF) in a network, cause the one or more processors to receive the register request from the PCF. The BSF cause the one or more processors to determine whether the register request comprises the one or more binding IDs. Upon determining that the register request comprises the one or more binding IDs, the BSF cause the one or more processors to check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF. The BSF cause the one or more processors to remove each of the one or more binding information of the session corresponding to the one or more binding IDs.

[0163] While the foregoing description describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0164] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0165] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0166] The present disclosure provides significant technical advancements in managing binding information of the session between the Policy Control Function (PCF) and the Binding Support Function (BSF) in 5G core networks. Conventionalmechanisms require the PCF to either send explicit deregistration requests for stale bindings or silently discard them without BSF awareness. The former increases signalling load and network transaction overhead, while the latter results in accumulation of stale UE and PDU bindings at the BSF, leading to inefficient resource utilization, database bloat, and degraded message-handling latency. To overcome these limitations, the present disclosure introduces an optimized overwrite procedure wherein the PCF includes the identifier of the old binding (oldBindingld) within the register request for a new session, enabling the BSF to seamlessly remove outdated bindings while simultaneously creating new ones, eliminating the need for separate deregistration flows.

[0167] By incorporating runtime-configurable parameters at the PCF (e.g., enabling or disabling old Binding Id transmission, choosing between custom IE or HTTP / 2 header modes) and robust handling at the BSF (including success, not- found, and error counters), the present disclosure achieves streamlined signalling, reduced transaction overhead, and improved synchronization of binding state across network functions. The approach ensures that only valid bindings are maintained at the BSF, optimizing storage, reducing intra-NF latency, and enhancing system scalability. Furthermore, the counter mechanisms provide realtime observability into overwrite operations, supporting better performance monitoring, fault detection, and operational assurance in dense subscriber environments.TECHNICAL ADVANTAGES

[0168] Efficient Resource Management: The present disclosure provides a method and a system to prevent the accumulation of existing UE / PDU binding information of the session at the BSF, optimizing the usage of network resources.

[0169] Reduced Network Overhead: The present disclosure eliminates the need for separate deregistration messages for existing binding information of the session, leading to less signalling overhead.

[0170] Improved Binding information Accuracy: The present disclosure provides a method and a system to use custom Information Elements (IE) or HTTP2 headers, ensuring accurate deletion of outdated binding information of the session, maintaining a clean and efficient session database.

[0171] Enhanced Performance and Latency: The present disclosure provides a method and a system to reduce resource utilization at BSF, minimizing potential intra-network function latency, leading to faster message handling and overall improved network performance.

[0172] Scalable Solution: The present disclosure provides ability to handle high volume of binding information of the session without increasing resource strain, making the system scalable for large and complex 5G network environments.

[0173] Simplified Network Management: By automating the binding deletion process and integrating standard session creation flows, the present disclosure simplifies network management, reducing manual intervention and potential errors.

Claims

Claims1. A method (600) for managing one or more binding information of a session in a network (106), the method (600) comprising: receiving (602), by a Policy Control Function (PCF) (208), a request to create or update a session from a first network function; extracting (604), by the PCF (208), one or more parameters from the received request; determining (606), by the PCF (208), whether one or more binding information of the session exist with a Binding Support Function (BSF) (212) based on the one or more extracted parameters; upon determining that the one or more binding information of the session exist with the BSF (212), determining (608), by the PCF (208), overwriting of the one or more binding information of the session that exist with the BSF (212); transmitting (610), by the PCF (208), a register request to the BSF (212) to create one or more new binding information of the session based on the determination, wherein the register request comprises one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF (212); and overwriting (612), by the PCF (208), the one or more binding information of the session with the one or more new binding information of the session.

2. The method (600) as claimed in claim 1, wherein the first network function is one of an Access and Mobility Management Function (AMF) (302) and a Session Management Function (SMF) (402).

3. The method (600) as claimed in claim 1, comprising:upon determining that the one or more binding information of the session does not exist with the BSF (212), transmitting, by the PCF (208), the register request to the BSF (212) to create the one or more new binding information of the session ; and creating, by the BSF (212), the one or more new binding information of the session based on the register request.

4. The method (600) as claimed in claim 1, wherein the one or more binding information of the session is a User Equipment (UE) session binding associated with an Access Management (AM) policy session, and wherein a UE binding ID is transmitted towards the BSF (212) to create the UE session binding.

5. The method (600) as claimed in claim 1, wherein the one or more binding information of the session is a Protocol Data Unit (PDU) session binding associated with a Session Management (SM) policy session, and wherein a PDU binding ID is transmitted towards the BSF (212) to create the PDU session binding.

6. A method (700) for managing one or more binding information of a session in the network (106), the method (700) comprising: receiving (702), by the BSF (212), the register request from the PCF (208); determining (704), by the BSF (212), whether the register request comprises the one or more binding IDs; upon determining that the register request comprises the one or more binding IDs, checking (706), by the BSF (212), whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF (212); and removing (708), by the BSF (212), each of the one or more binding information of the session corresponding to the one or more binding IDs.

7. The method (700) as claimed in claim 6 comprising:counting, by the BSF (212), instances of receiving the register request to keep a record of removal of the one or more binding information of the session ; and incrementing, by the BSF (212), a register request counter based on the counting of the instances of receiving the register request that comprises the one or more binding IDs.

8. The method (700) as claimed in claim 6, comprising: counting, by the BSF (212), instances of receiving the register request without the one or more binding IDs to keep a record of an absence of the one or more binding information of the session ; and incrementing, by the BSF (212), an overwrite counter based on the counting of the instances of receiving the register request without the one or more binding IDs.

9. A system (108) for managing one or more binding information of the session in a network (106), the system (108) comprising: a Policy Control Function (PCF) (208) configured to: receive a request to create or update a session from a first network function; extract one or more parameters from the received request; determine whether one or more binding information of the session exist with a Binding Support Function (BSF) (212) based on the one or more extracted parameters; upon determining that the one or more binding information of the session exist with the BSF (212), determine overwriting of the one or more binding information of the session that exist with the BSF (212);transmit a register request to the BSF (212) to create one or more new binding information of the session based on the determination, wherein the register request comprises one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF (212); and overwrite the one or more binding information of the session with the one or more new binding information of the session.

10. The system (108) as claimed in claim 9, wherein the first network function is one of an Access and Mobility Management Function (AMF) (302) and a Session Management Function (SMF) (402).

11. The system (108) as claimed in claim 9, wherein upon determining that the one or more binding information of the session does not exist with the BSF (212), the PCF (208) is configured to transmit the register request to the BSF (212) to create the one or more new binding information of the session, and the BSF (212) is configured to create the one or more new binding information of the session based on the register request.

12. The system (108) as claimed in claim 9, wherein the one or more binding information of the session is a User Equipment (UE) session binding associated with an Access Management (AM) policy session, and wherein a UE binding ID is transmitted towards the BSF to create the UE session binding.

13. The system (108) as claimed in claim 9, wherein the one or more binding information of the session is a Protocol Data Unit (PDU) session binding associated with a Session Management (SM) policy session, and wherein a PDU binding ID is transmitted towards the BSF to create the PDU session binding.

14. A system (108) for managing one or more binding information of the session in a network (106), the system (108) comprising: a Binding Support Function (BSF) (212) configured to:receive the register request from the PCF (208); determine whether the register request comprises the one or more binding IDs; upon determining that the register request comprises the one or more binding IDs, check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF (212); and remove each of the one or more binding information of the session corresponding to the one or more binding IDs.

15. The system (108) as claimed in claim 14, wherein the BSF (212) is configured to: count instances of transmitting the register request to keep a record of removal of the one or more binding information of the session ; and increment a register request counter based on the counting of the instances of transmitting the register request that comprises the one or more binding IDs.

16. The system (108) as claimed in claim 14, wherein the BSF (208) is configured to: count instances of transmitting the register request without the one or more binding IDs to keep a record of an absence of the one or more binding information of the session ; increment an overwrite counter based on the counting of the instances of transmitting the register request without the one or more binding IDs.

17. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Policy Control Function (PCF) (208) in a network, cause the one or more processors to:receive a request to create or update a session from a first network function; extract one or more parameters from the received request; determine whether one or more binding information of the session exist with a Binding Support Function (BSF) (212) based on the one or more extracted parameters; upon determining that the one or more binding information of the session exist with the BSF (212), determine overwriting of the one or more binding information of the session that exist with the BSF (212); transmit a register request to the BSF (212) to create one or more new binding information of the session based on the determination, wherein the register request comprises one or more binding identifiers (IDs) associated with each of the one or more binding information of the session that exist with the BSF (212); and overwrite the one or more binding information of the session with the one or more new binding information of the session.

18. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Binding Support Function (BSF) (212) in a network, cause the one or more processors to: receive the register request from the PCF (208); determine whether the register request comprises the one or more binding IDs; upon determining that the register request comprises the one or more binding IDs, check whether the one or more binding information of the session corresponding to the one or more binding IDs exist at the BSF (212); and remove each of the one or more binding information of the session corresponding to the one or more binding IDs.

Images