FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING SESSION
BINDINGS IN A NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr.
Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat,
India.
The following specification particularly describes the invention and the manner in
which it is to be performed.
2
METHOD AND SYSTEM FOR MANAGING SESSION BINDINGS IN A
NETWORK
FIELD OF DISCLOSURE
5
[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.
10
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
15 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.
20 [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
25 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
30 deployed, promising even faster data speeds, low latency, and the ability to connect
multiple devices simultaneously. With each generation, wireless communication
3
technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
[0004] Moreover, the 5G core networks are based on service-based architecture
(SBA) that is centered around network function 5 (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
10 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
15 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
20 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
25 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
30 and charging aspects of user sessions.
4
[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.
5
[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.
10 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
15 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
20 (BSF) for a binding session. Next, the method includes 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.
25 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.
30 [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.
5
[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.
5
[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
10 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.
15
[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.
20
[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
25 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
30 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
6
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 5 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.
10
[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
15 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
20 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
25 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
30 embodiment disclosed herein satisfies are listed herein below.
7
[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).
5
[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.
10 [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
15
[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,
20 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
25 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
30 implementations of the present disclosure.
8
[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 5 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
10 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
15 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.
20
[0031] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
25
[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
30 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
9
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, 5 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
10 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
15 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
20 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
25 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
30 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
10
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” 5 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
10 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
15 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.
20 [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
25 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
30 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.
11
[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 5 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.
10 [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
15 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,
20 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.
25 [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.
30 [0043] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above12
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 r 5 eference 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
10 architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
15 Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
User Plane Function (UPF) [128], a data network (DN) [130] a binding support
function (BSF) [132], wherein all the components are assumed to be connected to
20 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) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
25 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) [106] is a 5G core
30 network function responsible for managing access and mobility aspects, such as UE
13
registration, connection, and reachability. It also handles mobility management
procedures like handovers and paging.
[0048] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-5 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) [110] is a network function in the 5G
10 core network that facilitates communication between other network functions by
providing a secure and efficient messaging service. It acts as a mediator for servicebased
interfaces.
[0050] Authentication Server Function (AUSF) [112] is a network function in the
15 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) [114] is a network function that provides authentication and
20 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) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors
25 such as subscription, requested services, and network policies.
[0053] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling
integration with third-party services and applications.
14
[0054] Network Repository Function (NRF) [120] 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 5 (PCF) [122] 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) [124] is a network function that
10 centralizes the management of subscriber data, including authentication,
authorization, and subscription information.
[0057] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network
15 capabilities and services.
[0058] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
20
[0059] Data Network (DN) [130] refers to a network that provides data services to
user equipment (UE) in a telecommunications system. The data services may
include but are not limited to Internet services, private data network related services.
25 [0060] Binding support function (BSF) [132] 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.
30
15
[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 [116] is connected with the network entity via the interface
denoted as (Nbsf) interface in the figure. The NEF [118] is connected with the
network entity via the interface denoted as (Nnef) 5 interface in the figure. The NRF
[120] is connected with the network entity via the interface denoted as (Nnrf)
interface in the figure. The PCF [122] is connected with the network entity via the
interface denoted as (Npcf) interface in the figure. The UDM [124] is connected
with the network entity via the interface denoted as (Nudm) interface in the figure.
10 The AF [126] is connected with the network entity via the interface denoted as (Naf)
interface in the figure. The NSSAAF [114] is connected with the network entity via
the interface denoted as (Nnssaaf) interface in the figure. The AUSF [112] is
connected with the network entity via the interface denoted as (Nausf) interface in
the figure. The AMF [106] is connected with the network entity via the interface
15 denoted as (Namf) interface in the figure. The SMF [108] is connected with the
network entity via the interface denoted as (Nsmf) interface in the figure. The SMF
[108] is connected with the UPF [128] via the interface denoted as (N4) interface
in the figure. The UPF [128] is connected with the RAN [104] via the interface
denoted as (N3) interface in the figure. The UPF [128] is connected with the DN
20 [130] via the interface denoted as (N6) interface in the figure. The RAN [104] is
connected with the AMF [106] via the interface denoted as (N2). The AMF [106]
is connected with the RAN [104] via the interface denoted as (N1). The UPF [128]
is connected with other UPF [128] via the interface denoted as (N9). The interfaces
such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9,
25 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 [200]
30 (also referred herein as a computer system [200]) upon which the features of the
present disclosure may be implemented in accordance with exemplary
16
implementation of the present disclosure. In an implementation, the computing
device [200] may also implement a method for managing session bindings in a
network utilising the system. In another implementation, the computing device
[200] itself implements the method for managing session bindings in a network
using one or more units configured 5 within the computing device [200], wherein said
one or more units are capable of implementing the features as disclosed in the
present disclosure.
[0063] The computing device [200] may include a bus [202] or other
10 communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a randomaccess
memory (RAM), or other dynamic storage device, coupled to the bus [202]
15 for storing information and instructions to be executed by the processor [204]. The
main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special20
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
25 [0064] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
30 displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
17
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as
a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
cursor movement on the 5 display [212]. 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 [200] may implement the techniques described
10 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
15 sequences of one or more instructions contained in the main memory [206]. Such
instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
20 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0066] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two25
way data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [218] may be a
30 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
18
implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0067] The computing device [200] can 5 send messages and receive data, including
program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], host [224] and the communication interface
10 [218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0068] The computing device [200] encompasses a wide range of electronic
15 devices capable of processing data and performing computations. Examples of
computing device [200] 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 [200]
20 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 [300] for
25 managing session bindings in a network is shown, in accordance with the exemplary
implementations of the present disclosure. The system [300] comprises at least one
transceiver unit [302], at least one identification unit [304], and at least one
processing unit [306]. Also, all of the components/ units of the system [300] are
assumed to be connected to each other unless otherwise indicated below. Also, in
30 FIG. 3, only a few units are shown, however, the system [300] may comprise
multiple such units or the system [300] may comprise any such numbers of said
19
units, as required to implement the features of the present disclosure. Further, in an
implementation, the system [300] may be present in a user device to implement the
features of the present invention. The system [300] 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 5 another implementation, the system [300] may reside
in a server or a network entity. In yet another implementation, the system [300] may
reside partly in the server/ network entity and partly in the user device.
[0070] The system [300] is configured for managing session bindings in the
10 network, with the help of the interconnection between the components/units of the
system [300].
[0071] The system [300] comprises the transceiver unit [302]. The transceiver unit
[302] is configured to transmit, at a policy control function (PCF), a request to a
15 Binding Support Function (BSF) for a binding session. To create the binding
session in the network, the transceiver unit [302] at the PCF of the system [300] 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
20 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.
25 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
30 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
20
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, 5 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-uebindings/{
bindingId}.
10 [0073] The transceiver unit [302] 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 [302] at the PCF
15 of the system [300] 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 [300] further comprises the identification unit [304]. The
20 identification unit [304] is connected at least with the transceiver unit [302]. The
identification unit [304] 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 [302]
25 at the PCF, the identification unit [304] 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
30 request. In an exemplary aspect, the binding failure may be due to network
connectivity failure.
21
[0075] The system [300] further comprises the processing unit [306]. The
processing unit [306] is connected at least with the identification unit [304]. The
identification unit [304] is configured to send binding failure response to the
processing unit [306]. The processing unit 5 [306] 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 [302] 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
10 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 [306] facilitates retry for
transmitting the register/update request by the transceiver unit [302] for a
15 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 binding
session that the PCF may transmit. In one example, retry mechanism retry for
20 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.
25 Once the 30 seconds have passed, the retry mechanism retransmits the
registration/update request.
[0076] The transceiver unit [302] of the system [300] is further configured to send,
from the PCF, a terminate notify request to a Session Management Function (SMF)
30 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
22
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 [302] is configured to send the terminate notify request
to the SMF. The transceiver unit [302] at the PCF is configured to send an "SM
Terminate Notify" request to the SMF. 5 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
10 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
15 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
20 of the system [300] 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.
25 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.
[0079] Referring to FIG. 4, an exemplary method flow diagram [400] for managing
30 session bindings in the network, in accordance with exemplary implementations of
the present disclosure is shown. In an implementation, the method [400] is
23
performed by the system [300]. In an implementation, the system [300] may be
present in a server device to implement the features of the present disclosure. Also,
as shown in FIG. 4, the method [400] starts at step [402].
[0080] At step [404], the method 5 [400] comprises transmitting, by the transceiver
unit [302] 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 [302] at the PCF of the system [300] may send the
request to the BSF. The request is at least one of register request or update request.
10 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
15 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.
20
[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
25 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
30 information, the update request may comprise PATCH …/pcf-uebindings/{
bindingId}.
24
[0082] Next, at step [406], the method [400] comprises receiving, by the transceiver
unit [302] 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 5 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 [302] at the PCF of the system [300] 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.
10
[0083] Next, at step [408], the method [400] comprises identifying, by the
identification unit [304] 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
15 response from the BSF via the transceiver unit [302] at the PCF, the identification
unit [304] 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
20 response for the request. In an exemplary aspect, the binding failure may be due to
network connectivity failure.
[0084] Next, at step [410], the method [400] comprises implementing, by the
processing unit [306], the retry mechanism to retry for the request of the binding
25 session based on the set of retry parameters. The processing unit [306] 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 [302] 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
30 parameter. In an implementation, PCF may comprise a timer and counter. The
counter and timer measure the count parameter and timer parameter. In one
25
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
[306] facilitates retry for transmitting the register/update request by the transceiver
unit [302] for a configured number of times based on the register/update retry count
parameter of the BSF. The retry time parameter 5 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
10 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
15 registration/update request.
[0085] Next, at step [412], the method [400] comprises sending, by the transceiver
unit [302] from the PCF, the terminate notify request to the Session Management
Function (SMF) to terminate the binding session upon identification of the binding
20 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 [202] sends the terminate notify request to the SMF.
25 [0086] The transceiver unit [302] 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
30 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
26
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 5 to the SMF for representing the reason
of termination of the policy association.
[0087] Thereafter, the method [400] terminates at step [414].
10 [0088] Referring to FIG. 5 a process flow diagram [500] for managing session
bindings in the network, in accordance with exemplary implementations of the
present disclosure, is shown. The process [500] as depicted in the FIG. 5 starts at
step [502].
15 [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 [500] leads to step S510 from
20 the step S506.
[0091] In case the request failed, the process [500] goes to step S508 from step
S506. At step S508, the retry count is monitored for a configured retry count for
attempting to establish binding session. At step S508, the retry is performed till the
25 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
30 BSF is done.
27
[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 [600] for managing session
bindings in the network, in accordance 5 with exemplary implementations of the
present disclosure. As shown in FIG. 6, the sequence flow diagram [600] comprises
a NF service consumer [602], a binding support function (BSF) [132], and a session
management function (SMF) [108]. In an implementation, NF service consumer
[602] is policy control function (PCF) [122].
10
[0095] At step S1, NF service consumer [602] or the PCF [122] sends a service
request for registration or updation of a session binding information for a user
equipment (UE) to the BSF [132]. The register request for the binding session may
comprise, but not limited to, UE identity, data network name (DNN), UE
15 address(es), and PCF address for a packet data unit (PDU) session. In the
registration request, the PCF [122] may send at least one of POST .../pcfBindings,
and POST .../pcf-ue-bindings. The update request may allow the PCF [122] to
update an existing PCF for a PDU session binding information for the UE in the
BSF [132] by providing the information to be updated (e.g., the UE address(es)),
20 and the BSF [132] updates the PDU session binding information. In the update
request, the PCF [122] may send at least one of PATCH …/pcf-uebindings/{
bindingId}, and PATCH …/pcfindings/{bindingId}.
[0096] At step S2, in response to the request, the BSF [132] may send a response
25 such as at least one of ‘created’, ‘not created’, ‘ack’, ‘nack’, ‘success’, or ‘failed’.
[0097] At step S3, the PCF [122] may identify the received response from the BSF
[132], such as ‘success’ or ‘failed’.
30 [0098] At step S4, if the PCF [122] receives the failed response from the BSF [132],
the PCF [122] further applies a retry mechanism to resend the request. In an aspect,
28
the failed response may be received by the PCF [122] from the BSF [132] due to
request timeout, connection failure, and connection refused callback. The PCF
[122] 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) a 5 nd retry count (e.g., number of retry attempts, such as 2 to 10).
[0099] At step S5, the PCF [122] again receives a failure response after configured
number of re-attempts from the BSF [132].
10 [0100] At step S6, after receiving the failure response from the BSF [132], the PCF
[122] sends a termination notification request for the binding session to the SMF
[132]. The PCF [122] may trigger Npcf_SMPolicyControl_UpdateNotify Service
operation for triggering the deletion of context of SM related policies. The PCF
[122] may send POST {notificationUri}/terminate for terminate notify request for
15 terminating PDU session to the SMF [108].
[0101] At step S7, in response to the request (e.g., termination notification request)
the SMF [108] sends a response such as ‘No content’ to the PCF [122]. After the
successful processing of the HTTP POST request, the SMF [108] may invoke the
20 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
25 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 [300], causes: a transceiver unit [302] of the system [300] 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 [300] to receive, at
30 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
29
[304] of the system [300] 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 [300] 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 [300] to 5 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.
10 [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
15 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.
20
[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
25 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
30 uninterrupted service to users. The retry mechanism helps maintain session
continuity by attempting to establish the necessary connections even in the face of
30
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 5 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
10 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
15 and non-limiting.
31
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 t 5 o 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
10 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
15 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.
20 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
25 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).
30
32
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, 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
10 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
15 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.
20 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;
25 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
30 response;
a
processing unit [306] connected at least with the
identification unit [304], the processing unit [306] is
33
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 5 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.
10 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
15 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).
20
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.
25 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
30 parameter determines a maximum retry numbers of the request for the
34
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
5 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.