Search

EP-4740626-A1 - METHOD AND SYSTEM FOR REAL-TIME SYNCHRONIZATION OF ONE OR MORE NETWORK ENTITIES

EP4740626A1EP 4740626 A1EP4740626 A1EP 4740626A1EP-4740626-A1

Abstract

The present disclosure relates to a method and a system for real-time synchronization of one or more network entities [301] for termination of an ongoing session The disclosure encompasses receiving a session abort request (SAR); transmitting the session abort request (SAR); initiating a session hold wait timer [305]; receiving session information; holding the session information based on the session hold wait timer [305]; receiving a session abort answer (SAA); and transmitting the session abort answer (SAA).

Inventors

  • Shetty, Mukta
  • BHATNAGAR, AAYUSH
  • BHASKAR, ALOK
  • KUMAR, SANJEEV
  • NARAYAN, Gaurav
  • KUMAWAT, SACHIN
  • Kumar, Pritam
  • Joshi, Yugandhara
  • Pareek, Puneet

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240611

Claims (20)

  1. 1. A method [400] for real-time synchronization of one or more network entities [301] for termination of an ongoing session, the method [400] comprising: receiving, by a transceiver unit [3021] of a Binding Support Function (BSF) [302], a session abort request (SAR) from a Policy Control Function (PCF) [303]; transmitting, by the transceiver unit [3021] of the BSF [302], the session abort request (SAR) to an Application Function (AF) [304]; initiating, by an initialization unit [3022] ofthe BSF [302], a session hold wait timer [305]; receiving, by the transceiver unit [3021] of the BSF [302], a session information from the AF [304]; holding, by a holding unit [3023] of the BSF [302], the session information based on the session hold wait timer [305]; receiving, by the transceiver unit [3021] of the BSF [302], a session abort answer (SAA) from the AF [304]; and transmitting, by the transceiver unit [3021] of the BSF [302], the session abort answer (SAA) to the PCF [303],
  2. 2. The method [400] as claimed in claim 1, wherein receiving the session abort request (SAR) is based on reception of a failure code at the PCF [303] from a session management function (SMF) [306],
  3. 3. The method [400] as claimed in claim 2, wherein the failure code corresponds to session management policy association termination request.
  4. 4. The method [400] as claimed in claim 1, wherein the session information comprises at least one of a session termination request (STR) and a session termination answer (STA).
  5. 5. The method [400] as claimed in claim 4, wherein the session information is held till the session termination answer (STA) is received from the PCF [303],
  6. 6. The method [400] as claimed in claim 4, wherein the session information is held by the holding unit [3023] of the BSF [302], in an event the session termination request (STR) is received before receiving the session abort answer (SAA), from the AF [304],
  7. 7. The method [400] as claimed in claim 4, wherein the session information is held by the holding unit [3023] of the BSF [302], in an event the session termination request (STR) is not received from the AF [304] .
  8. 8. The method [400] as claimed in claim 1, wherein the session hold wait timer [305] is initiated by the PCF [303] after transmitting the session abort request (SAR) to the BSF [302],
  9. 9. The method [400] as claimed in claim 4, wherein the PCF [303] awaits to release an ongoing session in an event the session termination request (STR) is received before receiving the session abort answer (SAA) from the AF [304],
  10. 10. The method [400] as claimed in claim 4, wherein the PCF [303] awaits to release the ongoing session in an event the session termination request (STR) is not received from the AF [304],
  11. 11. The method [400] as claimed in claim 1, the method [400] further comprising displaying, by the PCF [303], one or more key performance indicators (KPI) based on the received session abort answer (SAA).
  12. 12. A system [300] for real-time synchronization of one or more network entities [301] for termination of an ongoing session, the system [300] comprising: a Binding Support Function (BSF) [302] comprising: a transceiver unit [3021] configured to receive a session abort request (SAR) from a Policy Control Function (PCF) [303]; the transceiver unit [3021] further configured to transmit the session abort request (SAR) to an Application Function (AF) [304]; an initialization unit [3022] configured to initiate a session hold wait timer [305]; the transceiver unit [3021] further configured to receive session information from the AF [304]; a holding unit [3023] configured to hold the session information based on the session hold wait timer [305]; the transceiver unit [3021] further configured to receive a session abort answer (SAA) from the AF [304]; and the transceiver unit [3021] further configured to transmit the session abort answer (SAA) to the PCF [303],
  13. 13. The system [300] as claimed in claim 12, wherein the session abort request (SAR) is based on reception of a failure code at the PCF [303] from a session management function (SMF) [306],
  14. 14. The system [300] as claimed in claim 13, wherein the failure code corresponds to session management policy association termination request.
  15. 15. The system [300] as claimed in claim 12, wherein the session information comprises at least one of a session termination request (STR) and a session termination answer (STA).
  16. 16. The system [300] as claimed in claim 15, wherein the session information is held till the session termination answer (STA) is received from the PCF [303],
  17. 17. The system [300] as claimed in claim 15, wherein the holding unit [3023] of the BSF [302] held the session information, in an event the session termination request (STR) is received before receiving the session abort answer (SAA), from the Application Function (AF) [304],
  18. 18. The system [300] as claimed in claim 15, wherein the holding unit [3023] of the BSF [302] held the session information in an event the session termination request (STR) is not received from the Application Function (AF) [304],
  19. 19. The system [300] as claimed in claim 12, wherein the session hold wait timer [305] is initiated by the PCF [303] after transmitting the session abort request (SAR) to the BSF [302],
  20. 20. The system [300] as claimed in claim 15, wherein the PCF [303] awaits to release an ongoing session in an event the session termination request (STR) is received before receiving the session abort answer (SAA) from the Application Function (AF) [304],

Description

METHOD AND SYSTEM FOR REAL-TIME SYNCHRONIZATION OF ONE OR MORE NETWORK ENTITIES TECHNICAL FIELD [0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to realtime synchronization of one or more network entities for termination of an ongoing session. BACKGROUND [0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analogue 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. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized 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] In the 5G communication system, a plurality of network functions (NFs) are provided, for example an Access and Mobility Management Function (AMF), session management function (SMF), Policy control function (PCF), Network Exposure Function (NEF), Application Function (AF), Network Data Analytics Function (NWDAF), Network Repository Function (NRF), Binding Support Function (BSF) and the like. One or more of the aforementioned NFs communicate with each other, to implement multiple activities on the 5G communication system. For example, for data transfer, the AMF communicates with SMF, to initiate the communication. Binding Support Function (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 Policy Control Function (PCF). Accordingly, one or more connections are established between the two NFs, thereby allowing communication and enabling exchange of information and network activities. [0005] In the 5G communication system, the BSF stores the binding information for a certain PDU session and discovers the selected PCF according to the binding information. The BSF also acts as diameter proxy agent or diameter redirect agent to Rx requests targeting an IP address of a user equipment (UE) to the selected PCF. The BSF provides a PDU session binding functionality, which ensures that the Application Function (AF) request for a certain PDU session reaches the relevant PCF holding the PDU session information. [0006] Further, in the 5G communication system, when an ongoing call is discontinued or an Internet Protocol-Connectivity Access Network (IP-CAN) session is terminated, the PCF informs the AF about the IP-CAN session termination by sending an Abort Session Request (ASR) message to the AF on each active Rx Diameter session. When the AF receives the ASR message, it acknowledges the message by sending an Abort Session Answer (ASA) message to the PCF via BSF. After that the AF initiates an AF session termination procedure in which the AF sends a Session Termination Request (STR) message to the PCF via BSF. This message flow occurs in the ideal or normal situation. However, in a real network environment, this message flow sequence may not exist due to factors such as but not limited to network latency issues, traffic load etc. Further, in another case, some of these messages may timeout and impact the successful key performance indicators (KPI) of the network. For example, PCF sends an ASR message to AF via BSF. AF sends ASA and STR messages to BSF. Due to a delay on the network or network latency issues, the BSF receives STR first and sends it to PCF. Thus, the STR-Session Termination Answer (STA) message arrives at the BSF side, session information is removed from the database of BSF. In this case, the BSF is not able to forward the ASA messages to the PCF due to the race around condition being developed. Moreover, the ASR message of the PCF and the BSF is timed out and thus impacts the successful KPI on Rx interface. [0007] Thus, there