Search

EP-4740628-A1 - METHOD AND SYSTEM FOR PROCESSING A REGISTRATION REQUEST IN A COMMUNICATION NETWORK

EP4740628A1EP 4740628 A1EP4740628 A1EP 4740628A1EP-4740628-A1

Abstract

The present disclosure relates to method and system for processing a registration request in a communication network The method comprises receiving dynamically, at a load balancer, the registration request from one or more user devices; determining continuously, by a counter unit [304], a number of registration request received at the load balancer; extracting, by a decision unit [306], a process identifier and a thread identifier from the received registration request, and performing, a first level throttling of the determined number of registration request; performing, by the decision unit [306], a second level throttling of the determined number of registration request; performing, by the decision unit [306], a third level throttling of the determined number of registration request; and processing, by the load balancer, the registration request based on the first level throttling, the second level throttling and the third level throttling of the determined number of registration request.

Inventors

  • BHATNAGAR, AAYUSH
  • Bisht, Birendra Singh
  • Singh, Harbinder Pal
  • Naskar, Suman
  • KUMAR, PRADEEP
  • ABHISHEK, R
  • MANDOWARA, Harshit
  • Eslavath, Mahendra Varma
  • CHANDRA, Shakshi

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240611

Claims (20)

  1. 1. A method [400] for processing a registration request in a communication network, the method comprising: receiving dynamically, at a load balancer [302] of an access and mobility management function (AMF) unit [106], the registration request from one or more user devices; determining continuously, by a counter unit [304] of the AMF unit [106], a number of registration request received at the load balancer [302]; extracting, by a decision unit [306] of the AMF unit [106], a process identifier and a thread identifier from the received registration request; performing, by the decision unit [306] of the AMF unit [ 106], a first level throttling of the determined number of registration request; performing, by the decision unit [306] of the AMF unit [106], a second level throttling of the determined number of registration request; performing, by the decision unit [306] of the AMF unit [ 106] , a third level throttling of the determined number of registration request; and processing, by the load balancer [302] of the AMF unit [106], the registration request based on the first level throttling, the second level throttling and the third level throttling of the determined number of registration request.
  2. 2. The method [400] as claimed in claim 1, wherein the counter unit [304] of the AMF unit [106] determines the number of registration request received at the load balancer [302] within a configurable predefined time period.
  3. 3. The method [400] as claimed in claim 1, wherein extracting the process identifier and the thread identifier from the received registration request further comprises hashing, by the decision unit [306] of the AMF unit [106], the received registration request.
  4. 4. The method [400] as claimed in claim 1, wherein performing the first level throttling comprises of analysing, by the decision unit [306] of the AMF unit [106], whether the number of registration request exceeds a first threshold count.
  5. 5. The method [400] as claimed in claim 4, wherein the processing the registration request based on the first level throttling comprises: determining, by the load balancer [302] of the AMF unit [106], the registration request as a first unsuccessful request in an event the number of the registration request exceeds the first threshold count; and rejecting, by the load balancer [302] of the AMF unit [106], the first unsuccessful request.
  6. 6. The method [400] as claimed in claim 4, wherein processing the registration request based on the first level throttling further comprises: determining, by the load balancer [302] of the AMF unit [106], the registration request as a first successful request in an event the number of the registration request is less than or equal to the first threshold count.
  7. 7. The method [400] as claimed in claim 6, wherein performing the second level throttling comprises of determining, by the decision unit [306] of the AMF unit [106], the first successful request as a second successful request based on the process identifier successfully matching with an allowed process identifier.
  8. 8. The method [400] as claimed in claim 7, wherein processing the registration request based on the second level throttling comprises: determining, by the load balancer [302] of the AMF unit [106], the first successful request as a second unsuccessful request based on a mismatch in the process identifier with an allowed process identifier; and rejecting, by the load balancer [302] of the AMF unit [106], the second unsuccessful request.
  9. 9. The method [400] as claimed in claim 8, wherein performing the third level throttling comprises of determining, by the decision unit [306] of the AMF unit [106], the second successful request as a third successful request based on the thread identifier successfully matching with an allowed thread identifier.
  10. 10. The method [400] as claimed in claim 9, wherein processing the registration request based on the third level throttling comprises: determining, by the load balancer [302] of the AMF unit [106], the second successful request as a third unsuccessful request based on a mismatch in the thread identifier with an allowed third identifier; and rejecting, by the load balancer [302] of the AMF unit [106], the third unsuccessful request.
  11. 11. A system [300] for processing a registration request in a communication network, the system [300] comprising: an access and mobility management function (AMF) unit [106] further comprising : o a load balancer [302] configured to dynamically receive the registration request from one or more user devices; o a counter unit [304] connected at least with the load balancer [302], the counter unit [304] configured to continuously determine a number of registration request received at the load balancer [302]; and o a decision unit [306] connected at least with the counter unit [304], the decision unit [306] configured to: ■ extract a process identifier and a thread identifier from the received registration request, ■ perform a first level throttling of the determined number of registration request, ■ perform a second level throttling of the determined number of registration request, and ■ perform a third level throttling of the determined number of registration request; and the load balancer [302] further configured to process the registration request based on the first level throttling, the second level throttling and the third level throttling of the determined number of registration request.
  12. 12. The system [300] as claimed in claim 11, wherein the counter unit [304] of the AMF unit [106] is further configured to determine the number of registration request received at the load balancer [302] within a configurable predefined time period.
  13. 13. The system [300] as claimed in claim 11, wherein the decision unit [306] is further configured to hash the received registration request to extract the process identifier and the thread identifier from the received registration request.
  14. 14. The system [300] as claimed in claim 11, wherein the decision unit [306] is further configured to analyse whether the number of registration request exceeds a first threshold count.
  15. 15. The system [300] as claimed in claim 14, wherein to process the registration request based on the first level throttling, the load balancer [302] is configured to: determine the registration request as a first unsuccessful request in an event the number of the registration request exceeds the first threshold count; and reject the first unsuccessful request.
  16. 16. The system [300] as claimed in claim 14, wherein to process the registration request based on the first level throttling, the load balancer [302] is further configured to: determine the registration request as a first successful request in an event the number of the registration request is less than or equal to the first threshold count.
  17. 17. The system [300] as claimed in claim 16, wherein to perform the second level throttling, the decision unit [306] is configured to determine the first successful request as a second successful request based on the process identifier successfully matching with an allowed process identifier.
  18. 18. The system [300] as claimed in claim 17, wherein to process the registration request based on the second level throttling, the load balancer [302] is configured to: determine the first successful request as a second unsuccessful request based on a mismatch in the process identifier with an allowed process identifier; and reject the second unsuccessful request.
  19. 19. The system [300] as claimed in claim 18, wherein to perform the third level throttling, the decision unit [306] is configured to determine the second successful request as a third successful request based on the thread identifier successfully matching with an allowed thread identifier.
  20. 20. The system [300] as claimed in claim 19, wherein to process the registration request based on the third level throttling, the load balancer [302] is configured to determine the second successful request as a third unsuccessful request based on a mismatch in the thread identifier with an allowed third identifier; and reject the third unsuccessful request.

Description

METHOD AND SYSTEM FOR PROCESSING A REGISTRATION REQUEST IN A COMMUNICATION NETWORK TECHNICAE FIELD [001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for processing a registration request in a communication network. BACKGROUND [002] 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. [003] 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. 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. [004] In a 5G communication system include a user equipment (UE) that communicated with a network core over a radio access network (RAN). The network core comprises a plurality of network functions (NFs) such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), and others. The plurality of NFs communicate with each other using different interfaces like N 1/N2, Ni l, N26 and Si l. [005] For example, the AMF communicated with the UE/RAN via the N1/N2 interface using a Non-Access Stratum (NAS) protocol or Next Generation Application Protocol (NGAP). The AMF utilized various load balancers, such as Next Generation Application Protocol Load Balancer (NGAP LB), General Packet Radio Service (GPRS) Tunnelling Protocol (GTP LB), and a Hypertext Transfer Protocol Load Balancer (HTTP -LB), to handle the communication with the UE/RAN and other NFs. [006] Additionally, the AMF receives a high volume of transactions or requests on the load balancers, which is referred to as "traffic." The rate of this traffic may increase due to system failures or other unforeseen circumstances, potentially exceeding the transaction capacity threshold. To prevent system failure, the AMF's load balancers are equipped with a throttling module. The throttling module divides the incoming transactions into allowed and rejected sets. The allowed transactions are executed by the AMF's core application, while the rejected transactions are further divided into discarded and rejection-responded sets. The discarded transactions are completely discarded, and for the rejection-responded set, the AMF sends response rejection signals back to the UE/RAN. [007] “Throttling” technique is commonly known in the communication industry, wherein the number of transactions in a defined time period is limited to a defined level. Specifically, the throttling module is suitably functioned to divide the plurality of transactions between allowed set of transactions and a rejected set of transactions, as the number of the plurality of transactions reached beyond a first transaction capacity threshold level. [008] Even after throttling the overall transaction rate, there may still be instances where the number of transactions for a specific process function or thread in the AMF's core application exceeds their respective capacity thresholds, leading to system failures or interruptions. This type of scenario may occur and in said scenario a set of users face network failure conditions due to unforeseen reasons. [009] Thus, there exists an imperative need in the art to provide an efficient system and method for processing registration request in a communication network. SUMMARY [010] 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. [Oi l] An aspect of the present disclosure may relate to a method for processing a registration request in a communication network. The method comprise