Method and system for managing session bindings in a network

Abstract

The present disclosure relates to a method and a system for managing session bindings in a network The present disclosure comprises transmitting, by a transceiver unit [302] at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session; receiving, by the transceiver unit [302] at the PCF, a response for the request from the BSF; identifying, by an identification unit [304] at the PCF, a binding failure in the response; implementing, by a processing unit [306], a retry mechanism to retry for the request of the binding session based on a set of retry parameters; and sending, by the transceiver unit [302] from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

Description

METHOD AND SYSTEM FOR MANAGING SESSION BINDINGS IN A NETWORK FIELD OF DISCLOSURE ϱ^

[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for managing session bindings in a network. BACKGROUND ϭϬ^

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

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice ϮϬ^ services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Ϯϱ^ Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. ϯϬ^

[0004] Moreover, the 5G core networks are based on service-based architecture (SBA) that is centered around network function (NF) services. In said Service-Based Architecture (SBA), a set of interconnected Network Functions (NFs) delivers the control plane functionality and common data repositories of the 5G network, where each NF is authorized to access services of other NFs. Particularly, each NF can register itself and its supported services to a Network Repository ϯϱ^ Function (NRF), which is used by other NFs for the discovery of NF instances and their services.The NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances. ϱ^

[0005] Also, Binding Support Function (BSF) is one of key 5G Core Network Function (NF) with key functionality including storing a binding information for protocol data unit (PDU) session / user equipment (UE), discovery of binding information, and lastly acting as proxy / redirect agent for Rx interface between Proxy Call Session Control Function / Diameter Routing Agent (P- ϭϬ^ CSCF / DRA) and policy control function (PCF). Furthermore, the Binding Support Function (BSF) allows the Policy Control Function (PCF) to register, update, and remove the binding information from it, and allows Network Function (NF) consumers to discover the selected Policy Control Function. For any application function (AF) using Rx, such as P-CSCF, the Binding Support Function determines the selected Policy Control Function address according to the information ϭϱ^ carried by the incoming Rx requests. Hence, the registration of the Policy Control Function (PCF) with the Binding Support Function (BSF) serves a crucial role in managing policy and charging aspects of user sessions.

[0006] The existing systems fail to efficiently and effectively deal with a scenario, when the PCF ϮϬ^ encounters a binding failure with BSF. This failure could be related to the BSF not responding within a specified time (timeout) or connection issues or request timeout, etc.

[0007] Thus, there exists an imperative need in the art to provide an efficient and effective system and method for managing session bindings in a network, which the present disclosure aims to Ϯϱ^ address. SUMMARY

[0008] This section is provided to introduce certain aspects of the present disclosure in a simplified ϯϬ^ form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0009] An aspect of the present disclosure may relate to a method for managing session bindings in a network. The method includes transmitting, by a transceiver unit at a policy control function ϯϱ^ (PCF), a request to a Binding Support Function (BSF) for a binding session. Next, the methodincludes receiving, by the transceiver unit at the PCF, a response for the request from the BSF. Next, the method includes identifying, by an identification unit at the PCF, a binding failure in the response. Next, the method includes implementing, by a processing unit, a retry mechanism to retry for the request of the binding session based on a set of retry parameters. Thereafter, the ϱ^ method includes sending, by the transceiver unit from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

[0010] In an exemplary aspect of the present disclosure, the set of retry parameters are received ϭϬ^ by a transceiver unit at the PCF from the BSF.

[0011] In an exemplary aspect of the present disclosure, the retry mechanism facilitates retry for transmitting the request by the transceiver unit for a configured number of times based on a Register / Update Retry Count parameter of the BSF. ϭϱ^

[0012] In an exemplary aspect of the present disclosure, the binding session is identified by a data network name (DNN).

[0013] In an exemplary aspect of the present disclosure, the set of retry parameters comprises at ϮϬ^ least one of a retry timer parameter and a register / update retry count parameter.

[0014] In an exemplary aspect of the present disclosure, the retry timer parameter specifies a time interval between a plurality of successive binding retry attempts. Ϯϱ^

[0015] In an exemplary aspect of the present disclosure, the register / update retry count parameter determines a maximum retry numbers of the request for the binding session that the PCF transmits prior to transmitting the terminate notify request to the SMF.

[0016] In an exemplary aspect of the present disclosure, the request is at least one of register ϯϬ^ request or update request.

[0017] In an exemplary aspect of the present disclosure, the binding failure comprises one of request timeout or connection issue.

[0018] Another aspect of the present disclosure may relate to a system for managing session bindings in a network. The system comprises a transceiver unit configured to transmit, at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session. The transceiver unit is also configured to receive, at the PCF, a response for the request from the BSF. ϱ^ The system further comprises an identification unit connected at least with the transceiver unit. The identification unit is configured to identify, at the PCF, a binding failure in the response. Furthermore, the system comprises a processing unit connected at least with the identification unit. The processing unit is configured to implement a retry mechanism to retry for the request of the binding session based on a set of retry parameters. Next, the transceiver unit is configured to send, ϭϬ^ from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

[0019] Yet another aspect of the present disclosure may relate to a non-transitory computer ϭϱ^ readable storage medium storing instructions for managing session bindings in a network, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to transmit, at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session; the transceiver unit of the system to receive, at the PCF, a response for the request from the BSF; an identification unit connected at ϮϬ^ least with the transceiver unit, wherein the identification unit is configured to identify, at the PCF, a binding failure in the response; a processing unit connected at least with the identification unit, the processing unit is configured to implement a retry mechanism to retry for the request of the binding session based on a set of retry parameters; and the transceiver unit configured to send, from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate Ϯϱ^ the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism. OBJECTS OF THE DISCLOSURE ϯϬ^

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

[0021] It is an object of the present disclosure to provide a system and a method to provide automated resilience and graceful handling of persistent binding failures in events where Policy ϯϱ^ Control Function (PCF) tries binding with Binding Support Function (BSF).

[0022] It is another object of the present disclosure to provide a solution that provides a retry mechanism that allows the network to recover from temporary issues causing binding failures. ϱ^

[0023] It is yet another object of the present disclosure to provide a solution that can provide session continuity, reduced manual interventions in handling binding failures, and fault isolation. DESCRIPTION OF THE DRAWINGS ϭϬ^

[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be ϭϱ^ construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components. ϮϬ^

[0025] FIG.1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementations of the present disclosure.

[0026] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary Ϯϱ^ implementation of the present disclosure.

[0027] FIG. 3 illustrates an exemplary block diagram of a system for managing session bindings in a network, in accordance with exemplary implementations of the present disclosure. ϯϬ^

[0028] FIG. 4 illustrates a method flow diagram for managing session bindings in the network, in accordance with exemplary implementations of the present disclosure.

[0029] FIG. 5 illustrates a process flow diagram for managing session bindings in the network, in accordance with exemplary implementations of the present disclosure. ϯϱ^

[0030] FIG. 6 illustrates a sequence flow diagram for managing session bindings in the network, in accordance with exemplary implementations of the present disclosure.

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

[0032] In the following description, for the purposes of explanation, various specific details are ϭϬ^ set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. ϭϱ^

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

[0034] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the Ϯϱ^ embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0035] Also, it is noted that individual embodiments may be described as a process which is ϯϬ^ depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. ϯϱ^

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

[0037] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors ϭϱ^ in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor. ϮϬ^

[0038] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart- device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the Ϯϱ^ features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing ϯϬ^ unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0039] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or ϯϱ^ similar machine. For example, a computer-readable medium includes read-only memory(“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions. ϱ^

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

[0041] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality ϭϱ^ of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0042] As used herein the transceiver unit include at least one receiver and at least one transmitter ϮϬ^ configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0043] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing Ϯϱ^ problems in this field of technology by providing method and system for managing session bindings in a network.

[0044] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. ϯϬ^

[0045] FIG.1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

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

[0106] , a ϯϱ^ Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , anAuthentication Server Function (AUSF)

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

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

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function ϱ^ (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] a binding support function (BSF)

[0132] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. ϭϬ^

[0046] Radio Access Network (RAN)

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

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

[0047] Access and Mobility Management Function (AMF)

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

[0048] Session Management Function (SMF)

[0108] is a 5G core network function responsible for ϮϬ^ managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.

[0049] Service Communication Proxy (SCP)

[0110] is a network function in the 5G core network Ϯϱ^ that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0050] Authentication Server Function (AUSF)

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

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

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. ϯϱ^

[0052] Network Slice Selection Function (NSSF)

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

[0053] Network Exposure Function (NEF)

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

[0054] Network Repository Function (NRF)

[0120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the ϭϬ^ discovery and dynamic registration of network functions.

[0055] Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. ϭϱ^

[0056] Unified Data Management (UDM)

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

[0057] Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0058] User Plane Function (UPF)

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

[0059] Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services. ϯϬ^

[0060] Binding support function (BSF)

[0132] provides policy / charging (PCF / CHF) scaling of the 5G network while ensuring session correlation for HTTP / 2. BSF allows Policy Control Function (PCF) to register, update, and remove the binding information from it, and allows Network Function (NF) consumers to discover the selected PCF. ^

[0061] The 5GC network architecture also comprises a plurality of interfaces for connecting the network functions with a network entity for performing the network functions. The NSSF

[0116] is connected with the network entity via the interface denoted as (Nbsf) interface in the figure. The NEF

[0118] is connected with the network entity via the interface denoted as (Nnef) interface in the ϱ^ figure. The NRF

[0120] is connected with the network entity via the interface denoted as (Nnrf) interface in the figure. The PCF

[0122] is connected with the network entity via the interface denoted as (Npcf) interface in the figure. The UDM

[0124] is connected with the network entity via the interface denoted as (Nudm) interface in the figure. The AF

[0126] is connected with the network entity via the interface denoted as (Naf) interface in the figure. The NSSAAF

[0114] is ϭϬ^ connected with the network entity via the interface denoted as (Nnssaaf) interface in the figure. The AUSF

[0112] is connected with the network entity via the interface denoted as (Nausf) interface in the figure. The AMF

[0106] is connected with the network entity via the interface denoted as (Namf) interface in the figure. The SMF

[0108] is connected with the network entity via the interface denoted as (Nsmf) interface in the figure. The SMF

[0108] is connected with the UPF ϭϱ^

[0128] via the interface denoted as (N4) interface in the figure. The UPF

[0128] is connected with the RAN

[0104] via the interface denoted as (N3) interface in the figure. The UPF

[0128] is connected with the DN

[0130] via the interface denoted as (N6) interface in the figure. The RAN

[0104] is connected with the AMF

[0106] via the interface denoted as (N2). The AMF

[0106] is connected with the RAN

[0104] via the interface denoted as (N1). The UPF

[0128] is connected with other UPF ϮϬ^

[0128] via the interface denoted as (N9). The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9, N6, N4, N3, N2, and N1 can be referred to as a communication channel between one or more functions or modules for enabling exchange of data or information between such functions or modules, and network entities. Ϯϱ^

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

[0200] (also referred herein as a computer system

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

[0200] may also implement a method for managing session bindings in a network utilising the system. In another implementation, the computing device

[0200] ϯϬ^ itself implements the method for managing session bindings in a network using one or more units configured within the computing device

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

[0063] The computing device

[0200] may include a bus

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

[0204] coupled with bus

[0202] forprocessing information. The hardware processor

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

[0200] may also include a main memory

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

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

[0204] . The main memory ϱ^

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

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

[0204] , render the computing device

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

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

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

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

[0204] .

[0064] A storage device

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

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

[0200] may be coupled via the bus

[0202] to a display

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

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

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

[0204] . Another type of user ϮϬ^ input device may be a cursor controller

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

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

[0212] . This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane. Ϯϱ^

[0065] The computing device

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

[0200] causes or programs the computing device

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

[0200] in response to the processor

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

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

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

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

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations ofthe present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0066] The computing device

[0200] also may include a communication interface

[0218] coupled to ϱ^ the bus

[0202] . The communication interface

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

[0220] that is connected to a local network

[0222] . For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may ϭϬ^ be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

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

[0067] The computing device

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

[0220] and the communication interface

[0218] . In the Internet example, a server

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

[0228] , the ISP

[0226] , the local network

[0222] , host

[0224] and the communication interface

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

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

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

[0068] The computing device

[0200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device

[0200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded Ϯϱ^ systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device

[0200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications. ϯϬ^

[0069] Referring to FIG. 3, an exemplary block diagram of a system

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

[0300] comprises at least one transceiver unit

[0302] , at least one identification unit

[0304] , and at least one processing unit

[0306] . Also, all of the components / units ϯϱ^ of the system

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

[0300] may comprise multiple such units or the system

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

[0300] may be present in a user device to implement the features of the present invention. The system ϱ^

[0300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system

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

[0300] may reside partly in the server / network entity and partly in the user device. ϭϬ^

[0070] The system

[0300] is configured for managing session bindings in the network, with the help of the interconnection between the components / units of the system

[0300] .

[0071] The system

[0300] comprises the transceiver unit

[0302] . The transceiver unit

[0302] is configured to transmit, at a policy control function (PCF), a request to a Binding Support Function ϭϱ^ (BSF) for a binding session. To create the binding session in the network, the transceiver unit

[0302] at the PCF of the system

[0300] is configured to send the request to the BSF. The request is at least one of register request or update request. In an implementation, the network may be such as, but not limited to, 5G network. In an exemplary implementation, the PCF or network function (NF) service consumer may send the register request for the binding session for a user equipment (UE). ϮϬ^ The register request for the binding session may comprise such as, but not limited to, UE identity, data network name (DNN), UE address(es), and PCF address for a packet data unit (PDU) session. The register request may be implemented by Nbsf_Management_Register Service Operation. For registering the new PCF for a PDU session binding information, the register request may comprise POST ... / pcfBindings. For registering the new PCF for a UE binding information, the request may Ϯϱ^ comprise POST ... / pcf-ue-bindings.

[0072] In an exemplary implementation, the request may be associated with an update request for the binding session for a user equipment (UE). The update request allows the NF service consumer (e.g., PCF) to update an existing PCF for a PDU session binding information for the UE in the ϯϬ^ BSF by providing the information to be updated (e.g., the UE address(es)), and the BSF updates the PDU session binding information. The update request may be implemented by the Nbsf_Management_Update Service Operation. For updating an existing PCF for a PDU session binding information, the update request may comprise PATCH … / pcfBindings / {bindingId}. For updating an existing PCF for a UE binding information, the update request may comprise PATCH ϯϱ^ … / pcf-ue-bindings / {bindingId}.

[0073] The transceiver unit

[0302] is further configured to receive, at the PCF, a response for the request from the BSF. The BSF stores the request information (e.g., register request, update request) for the binding session in a database or server. In an implementation, the binding session ϱ^ is identified by a data network name (DNN). In response to the register or update request, the transceiver unit

[0302] at the PCF of the system

[0300] is configured to receive the response from the BSF. The response may comprise such as, but not limited to, created, not created, ack (acknowledge), nack (not acknowledge), success, or fail. ϭϬ^

[0074] The system

[0300] further comprises the identification unit

[0304] . The identification unit

[0304] is connected at least with the transceiver unit

[0302] . The identification unit

[0304] is configured to identify, at the PCF, a binding failure in the response. In an exemplary implementation, the binding failure comprises one of request timeout, connection issue, or connection refused callback. In the operation after receiving the response from the BSF via the ϭϱ^ transceiver unit

[0302] at the PCF, the identification unit

[0304] at the PCF is configured to identify the binding failure response. In an exemplary aspect, the binding failure response may be associated with such as fail, not created, and nack. The binding failure may be due to request timeout or connection issue. The request timeout herein may refer completing a predefined waiting time for receiving a successful response for the request. In an exemplary aspect, the binding failure ϮϬ^ may be due to network connectivity failure.

[0075] The system

[0300] further comprises the processing unit

[0306] . The processing unit

[0306] is connected at least with the identification unit

[0304] . The identification unit

[0304] is configured to send binding failure response to the processing unit

[0306] . The processing unit

[0306] is configured Ϯϱ^ to implement a retry mechanism to retry for the request of the binding session based on a set of retry parameters. The set of retry parameters are received by the transceiver unit

[0302] at the PCF from the BSF. The set of retry parameters may comprise at least one of a retry timer parameter and a register / update retry count parameter. In an implementation, PCF may comprise a timer and counter. The counter and timer measure the count parameter and timer parameter. In one example, ϯϬ^ the count parameter may be predefined such as 5 and timer parameter 10 seconds-60 seconds. The retry mechanism implemented by the processing unit

[0306] facilitates retry for transmitting the register / update request by the transceiver unit

[0302] for a configured number of times based on the register retry count parameter of the BSF. The retry timer parameter specifies a time interval between a plurality of successive binding retry attempts to the BSF. The register / update retry count ϯϱ^ parameter determines a maximum retry numbers of the register / update request for the bindingsession that the PCF may transmit. In one example, retry mechanism retry for transmitting the register / update request based on timer parameter and count parameter via the PCF. The BSF responds with a negative response indicating that the register / update request was not successful. Then upon receiving the negative response, if the pre-defined time interval associated with the ϱ^ timer parameter is set at the value of 30 seconds, the retry mechanism starts the timer set to 30 seconds. Once the 30 seconds have passed, the retry mechanism retransmits the registration / update request.

[0076] The transceiver unit

[0302] of the system

[0300] is further configured to send, from the PCF, ϭϬ^ a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism. In an implementation, if the binding failure persists even after the maximum retry numbers of the request (e.g., register request, update request) for the binding session, the transceiver unit

[0302] is configured to send the terminate notify request to the SMF. ϭϱ^ The transceiver unit

[0302] at the PCF is configured to send an "SM Terminate Notify" request to the SMF. This request serves as a notification to the SMF that the binding for the specified session, identified by the DNN (Data Network Name), should be terminated due to the persistent binding failures. ϮϬ^

[0077] In an implementation, the PCF may send POST {notificationUri} / terminate for terminate notify request for terminating PDU session, to the SMF. In response to this request (i.e., terminate notify request), the SMF may send response such as ‘No content’ to the PCF. After the successful processing of the HTTP POST request, the SMF may invoke the Npcf_SMPolicyControl_Delete service operation to terminate the policy association and initiate the procedure to terminate the Ϯϱ^ PDU session and / or binding session. In an implementation, the PCF may send SmPolicyAssociationReleaseCause message to the SMF for representing the cause of the termination of the policy association.

[0078] It is noted that the functionality described for the various components / units of the system ϯϬ^

[0300] can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve theintended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

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

[0400] for managing session ϱ^ bindings in the network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation, the method

[0400] is performed by the system

[0300] . In an implementation, the system

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

[0400] starts at step

[0402] . ϭϬ^

[0080] At step

[0404] , the method

[0400] comprises transmitting, by the transceiver unit

[0302] at the policy control function (PCF), the request to the Binding Support Function (BSF) for the binding session. In an operation for the binding session in the network, the transceiver unit

[0302] at the PCF of the system

[0300] may send the request to the BSF. The request is at least one of register request or update request. In an implementation, the network may include, but not limited to, 5G ϭϱ^ network or higher than 5G network. In an exemplary implementation, the PCF or network function (NF) service consumer may send the register request for the binding session for the user equipment (UE). The register request for the binding session may comprise, but not limited to, UE identity, data network name (DNN), UE address(es), and PCF address for the packet data unit (PDU) session. The register request may be implemented by Nbsf_Management_Register Service ϮϬ^ Operation. For registering the new PCF for a PDU session binding information, the register request may comprise POST ... / pcfBindings. For registering the new PCF for a UE binding information, the request may comprise POST ... / pcf-ue-bindings.

[0081] In an exemplary implementation, the request may be associated with an update request for Ϯϱ^ the binding session for the user equipment (UE). This update request allows the NF service consumer (e.g., PCF) to update an existing PCF for a PDU session binding information for the UE in the BSF by providing the information to be updated (e.g., the UE address(es)), and the BSF updates the PDU session binding information. The update request may be implemented by the Nbsf_Management_Update Service Operation. For updating an existing PCF for a PDU session ϯϬ^ binding information, the update request may comprise PATCH … / pcfBindings / {bindingId}. For updating an existing PCF for a UE binding information, the update request may comprise PATCH … / pcf-ue-bindings / {bindingId}.

[0082] Next, at step

[0406] , the method

[0400] comprises receiving, by the transceiver unit

[0302] at ϯϱ^ the PCF, the response for the request from the BSF. The BSF stores the request information (e.g.,register request, update request) for the binding session in the database or server. In an implementation, the binding session is identified by the data network name (DNN). In response to the register or update request, the transceiver unit

[0302] at the PCF of the system

[0300] may receive the response from the BSF. The response may comprise, but not limited to, created, not created, ϱ^ ack (acknowledge), nack (not acknowledge), success or fail.

[0083] Next, at step

[0408] , the method

[0400] comprises identifying, by the identification unit

[0304] at the PCF, the binding failure in the response. In an exemplary implementation, the binding failure comprises one of request timeout or connection issue or connection refused callback. In the ϭϬ^ operation after receiving the response from the BSF via the transceiver unit

[0302] at the PCF, the identification unit

[0304] at the PCF identifies the binding failure response. In an exemplary aspect, the binding failure response may be associated with fail, not created, and nack. The binding failure may be due to request timeout or connection issue. The request timeout may refer completing a predefined waiting time for receiving a successful response for the request. In an exemplary aspect, ϭϱ^ the binding failure may be due to network connectivity failure.

[0084] Next, at step

[0410] , the method

[0400] comprises implementing, by the processing unit

[0306] , the retry mechanism to retry for the request of the binding session based on the set of retry parameters. The processing unit

[0306] may implement the retry mechanism to retry for the request ϮϬ^ of the binding session based on the set of retry parameters. The set of retry parameters are received by the transceiver unit

[0302] at the PCF from the BSF. The set of retry parameters may comprise at least one of a retry timer parameter and a register / update retry count parameter. In an implementation, PCF may comprise a timer and counter. The counter and timer measure the count parameter and timer parameter. In one example, the count parameter may be predefined such as 5 Ϯϱ^ and timer parameter 10 seconds-60 seconds. The retry mechanism implemented by the processing unit

[0306] facilitates retry for transmitting the register / update request by the transceiver unit

[0302] for a configured number of times based on the register / update retry count parameter of the BSF. The retry time parameter specifies a time interval between the plurality of successive binding retry attempts. The register / update retry count parameter determines a maximum retry numbers of the ϯϬ^ register / update request for the binding session that the PCF may transmit. In one example, retry mechanism retry for transmitting the register / update request based on timer parameter and count parameter via the PCF. The BSF responds with a negative response indicating that the register / update request was not successful. Then upon receiving the negative response, if the pre- defined time interval associated with the timer parameter is set at the value of 30 seconds, the retrymechanism starts the timer set to 30 seconds. Once the 30 seconds have passed, the retry mechanism retransmits the registration / update request.

[0085] Next, at step

[0412] , the method

[0400] comprises sending, by the transceiver unit

[0302] from ϱ^ the PCF, the terminate notify request to the Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism. In an implementation, if the binding failures persist even after the maximum retry number of the requests (e.g., register request, update request) for the binding session, the transceiver unit

[0202] sends the terminate notify request to the SMF. ϭϬ^

[0086] The transceiver unit

[0302] at the PCF sends an "SM Terminate Notify" request to the SMF. This request serves as a notification to the SMF that the binding for the specified session, identified by the DNN, should be terminated due to the persistent binding failures. In an implementation, the PCF may send POST {notificationUri} / terminate for terminate notify request for terminating PDU ϭϱ^ session to the SMF. In response to this request (e.g., terminate notify request), the SMF may send response such as ‘No content’ to the PCF. After the successful processing of the HTTP POST request, the SMF may invoke the Npcf_SMPolicyControl_Delete service operation to terminate the policy association and initiate the procedure to terminate the PDU session and / or binding session. In an implementation, the PCF may send SmPolicyAssociationReleaseCause message to ϮϬ^ the SMF for representing the reason of termination of the policy association.

[0087] Thereafter, the method

[0400] terminates at step

[0414] .

[0088] Referring to FIG. 5 a process flow diagram

[0500] for managing session bindings in the Ϯϱ^ network, in accordance with exemplary implementations of the present disclosure, is shown. The process

[0500] as depicted in the FIG. 5 starts at step

[0502] . ^

[0089] Next, at step S504, PCF sends BSF Register / Update Request to BSF for establishing binding session.^ ϯϬ^

[0090] Next, at step S506, PCF identifies whether the request failed or timeout. If the request is not failed or not timeout, the process

[0500] leads to step S510 from the step S506. ^

[0091] In case the request failed, the process

[0500] goes to step S508 from step S506. At step ϯϱ^ S508, the retry count is monitored for a configured retry count for attempting to establish bindingsession. At step S508, the retry is performed till the configured retry count; and upon successful retry, the step S508 leads to step S510. In case of unsuccessful retry in the configured retry counts, the step S508 leads to step S512. ^ ϱ^

[0092] At step S510, if retry is successful, then successful registration / update to the BSF is done.^

[0093] At step S512, if the retry count exceeds, PCF sends the SMF terminate notification to the SMF.^ ϭϬ^

[0094] FIG. 6 illustrates a sequence flow diagram

[0600] for managing session bindings in the network, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 6, the sequence flow diagram

[0600] comprises a NF service consumer

[0602] , a binding support function (BSF)

[0132] , and a session management function (SMF)

[0108] . In an implementation, NF service consumer

[0602] is policy control function (PCF)

[0122] . ϭϱ^

[0095] At step S1, NF service consumer

[0602] or the PCF

[0122] sends a service request for registration or updation of a session binding information for a user equipment (UE) to the BSF

[0132] . The register request for the binding session may comprise, but not limited to, UE identity, data network name (DNN), UE address(es), and PCF address for a packet data unit (PDU) session. ϮϬ^ In the registration request, the PCF

[0122] may send at least one of POST ... / pcfBindings, and POST ... / pcf-ue-bindings. The update request may allow the PCF

[0122] to update an existing PCF for a PDU session binding information for the UE in the BSF

[0132] by providing the information to be updated (e.g., the UE address(es)), and the BSF

[0132] updates the PDU session binding information. In the update request, the PCF

[0122] may send at least one of PATCH … / pcf-ue-Ϯϱ^ bindings / {bindingId}, and PATCH … / pcfindings / {bindingId}.^

[0096] At step S2, in response to the request, the BSF

[0132] may send a response such as at least one of ‘created’, ‘not created’, ‘ack’, ‘nack’, ‘success’, or ‘failed’. ^ ϯϬ^

[0097] At step S3, the PCF

[0122] may identify the received response from the BSF

[0132] , such as ‘success’ or ‘failed’.^

[0098] At step S4, if the PCF

[0122] receives the failed response from the BSF

[0132] , the PCF

[0122] further applies a retry mechanism to resend the request. In an aspect, the failed response may be ϯϱ^ received by the PCF

[0122] from the BSF

[0132] due to request timeout, connection failure, andconnection refused callback. The PCF

[0122] may resend the request for the binding session for a configured retry timer value (e.g., duration of consecutive attempts, such as in seconds, lesser than seconds and in minutes) and retry count (e.g., number of retry attempts, such as 2 to 10). ^ ϱ^

[0099] At step S5, the PCF

[0122] again receives a failure response after configured number of re- attempts from the BSF

[0132] . ^

[0100] At step S6, after receiving the failure response from the BSF

[0132] , the PCF

[0122] sends a termination notification request for the binding session to the SMF

[0132] . The PCF

[0122] may ϭϬ^ trigger Npcf_SMPolicyControl_UpdateNotify Service operation for triggering the deletion of context of SM related policies. The PCF

[0122] may send POST {notificationUri} / terminate for terminate notify request for terminating PDU session to the SMF

[0108] .

[0101] At step S7, in response to the request (e.g., termination notification request) the SMF

[0108] ϭϱ^ sends a response such as ‘No content’ to the PCF

[0122] . After the successful processing of the HTTP POST request, the SMF

[0108] may invoke the Npcf_SMPolicyControl_Delete service operation to terminate the policy association and initiate the procedure to terminate the PDU session and / or binding session. ϮϬ^

[0102] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing session bindings in a network, the instructions include executable code which, when executed by one or more units of a system

[0300] , causes: a transceiver unit

[0302] of the system

[0300] to transmit, at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session; the transceiver unit

[0302] of the system Ϯϱ^

[0300] to receive, at the PCF, a response for the request from the BSF; an identification unit

[0304] connected at least with the transceiver unit

[0302] , wherein the identification unit

[0304] of the system

[0300] to identify, at the PCF, a binding failure in the response; a processing unit

[0306] connected at least with the identification unit

[0304] , the processing unit

[0306] of the system

[0300] to implement a retry mechanism to retry for the request of the binding session based on a set of ϯϬ^ retry parameters; and the transceiver unit

[0302] of the system

[0300] to send, from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

[0103] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the ϱ^ disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure. ^ ϭϬ^

[0104] As is evident from the above, the present disclosure provides a technically advanced solution for providing automated resilience and graceful handling of persistent binding failures in events where Policy Control Function (PCF) tries binding with Binding Support Function (BSF). The present disclosure provides a solution that has a retry mechanism, which allows the network to recover from temporary issues causing binding failures. By retrying the binding process, PCF ϭϱ^ increases its chances of successfully establishing the necessary connections when transient issues are resolved. The present disclosure provides a solution which ensures that session bindings are properly established and maintained for delivering uninterrupted service to users. The retry mechanism helps maintain session continuity by attempting to establish the necessary connections even in the face of initial failures. Further, the present disclosure provides a solution which ϮϬ^ automates the retry process and reduces the need for manual intervention by the PCF to handle binding failures. This helps to streamline network operations. The present disclosure provides a solution for fault isolation. If binding failures persist despite retries, the termination request helps isolate problematic sessions. This prevents unsuccessful sessions from consuming resources unnecessarily and allows PCF to focus on successful sessions. Ϯϱ^

[0105] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, ϯϬ^ whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

Claims

We Claim:

1. A method for managing session bindings in a network, the method comprising: - transmitting, by a transceiver unit [302] at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session; ϱ^ - receiving, by the transceiver unit [302] at the PCF, a response for the request from the BSF; - identifying, by an identification unit [304] at the PCF, a binding failure in the response; - implementing, by a processing unit [306], a retry mechanism to retry for the request of the binding session based on a set of retry parameters; and - sending, by the transceiver unit [302] from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

2. The method as claimed in claim 1, wherein the set of retry parameters are received by the transceiver unit [302] at the PCF from the BSF.

3. The method as claimed in claim 1, wherein the retry mechanism facilitates retry for the transmitting the request by the transceiver unit [302] for a configured number of times based on a Register / Update Retry Count parameter of the BSF.

4. The method as claimed in claim 1, wherein the binding session is identified by a data network name (DNN).

5. The method as claimed in claim 1, wherein the set of retry parameter comprises at least one of a retry timer parameter and a register / update retry count parameter.

6. The method as claimed in claim 5, wherein the retry timer parameter specifies a time interval between a plurality of successive binding retry attempts.

7. The method as claimed in claim 5, wherein the register / update retry count parameter determines a maximum retry numbers of the request for the binding session that the PCF transmits prior to transmit the terminate notify request to the SMF.

8. The method as claimed in claim 1, wherein the request is at least one of register request or update request.

9. The method as claimed in claim 1, wherein the binding failure comprises one of request ϱ^ timeout or connection issue.

10. A system for managing session bindings in a network, the system comprises of: - a transceiver unit [302] configured to transmit, at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session; - the transceiver unit [302] configured to receive, at the PCF, a response for the request from the BSF; - an identification unit [304] connected at least with the transceiver unit [302], wherein the identification unit is configured to identify, at the PCF, a binding failure in the response; - a processing unit [306] connected at least with the identification unit [304], the processing unit [306] is configured to implement a retry mechanism to retry for the request of the binding session based on a set of retry parameters; and - the transceiver unit [302] configured to send, from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

11. The system as claimed in claim 10, wherein the set of retry parameters are received by the transceiver unit [302] at the PCF from the BSF.

12. The system as claimed in claim 10, wherein the retry mechanism facilitates retry for the transmitting the request by the transceiver unit [302] for a configured number of times based on a Register / Update Retry Count parameter of the BSF.

13. The system as claimed in claim 10, wherein the binding session is identified by a data network name (DNN).

14. The system as claimed in claim 10, wherein the set of retry parameters comprises at least one of a retry timer parameter and a register / update retry count parameter.

15. The system as claimed in claim 14, wherein the retry timer parameter specifies a time interval between a plurality of successive binding retry attempts.

16. The system as claimed in claim 14, wherein the register / update retry count parameter ϱ^ determines a maximum retry numbers of the request for the binding session that the PCF transmits prior to transmit the terminate notify request to the SMF.

17. The system as claimed in claim 10, wherein the request is at least one of register request or update request.

18. The system as claimed in claim 10, wherein the binding failure comprises one of request timeout or connection issue.

19. A non-transitory computer readable storage medium storing instructions for managing session bindings in a network, the instructions include executable code which, when executed by one or more units of a system, causes: - a transceiver unit [302] of the system to transmit, at a policy control function (PCF), a request to a Binding Support Function (BSF) for a binding session; - the transceiver unit [302] of the system to receive, at the PCF, a response for the request from the BSF; - an identification unit [304] connected at least with the transceiver unit [302], wherein the identification unit [304] of the system to identify, at the PCF, a binding failure in the response; - a processing unit [306] connected at least with the identification unit [304], the processing unit [306] of the system to implement a retry mechanism to retry for the request of the binding session based on a set of retry parameters; and - the transceiver unit [302] of the system to send, from the PCF, a terminate notify request to a Session Management Function (SMF) to terminate the binding session upon identification of the binding failure in the response associated with the request after using the retry mechanism.

Images