Search

EP-4740609-A1 - METHOD AND SYSTEM FOR MANAGING INCOMING NETWORK REQUESTS ON AN OVERLOADED PRODUCER NETWORK FUNCTION

EP4740609A1EP 4740609 A1EP4740609 A1EP 4740609A1EP-4740609-A1

Abstract

The present disclosure relates to a method [500] and a system [300] for managing incoming network requests on an overloaded producer network function (producer NF) [302] The present disclosure encompasses: a transceiver unit [306], at a producer NF [302], receives a network request from a consumer network function (consumer NF) [304], to establish a communication between the consumer NF [304] and the producer NF [302] to access one of a plurality of microservices running on the producer NF [302]. Further, a processing unit [308] at the producer NF [302], process the network request by parsing the received network request on a network protocol level. Further, a determination unit [310] at the producer NF [302], determines one of an acceptance and a rejection, of the network request, based on the processing of the network request and a status of the microservice.

Inventors

  • JHA, ADITYAKAR
  • BHATNAGAR, AAYUSH
  • REDDY, Boddireddy Ajith
  • KATHURIA, Deepak
  • CHAUHAN, Himanshu Singh
  • VERMA, NITIN
  • VASHISHTH, Yog

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240614

Claims (19)

  1. 1. A method [500] for managing incoming network requests on an overloaded producer network function (producer NF) [302], the method [500] comprising: receiving, by a transceiver unit [306], at a producer NF [302], a network request from a consumer network function (consumer NF) [304], wherein the network request is to establish a communication between the consumer NF [304] and the producer NF [302] to access one of a plurality of microservices running on the producer NF [302]; processing, by a processing unit [308], at the producer NF [302], the network request, wherein processing the network request comprises parsing the received network request on a network protocol level; and determining, by a determination unit [310], at the producer NF [302], one of an acceptance and a rejection, of the network request, based on the processing of the network request and a status of the microservice.
  2. 2. The method [500] as claimed in claim 1, wherein the parsing the received network request on the network protocol level comprises reading a header of the network request.
  3. 3. The method [500] as claimed in claim 1, further comprising: based on one of the acceptance and the rejection of the network request, transmitting, by the producer NF [302], an acknowledgement to the consumer NF [304],
  4. 4. The method [500] as claimed in claim 1, wherein the rejection, by the producer NF [302], of the network request, is based on an overloaded status of the microservice.
  5. 5. The method [500] as claimed in claim 4, wherein, in an event of the rejection of the network request, transmitting, by the producer NF [302], an internal error response as a response to the consumer NF [304],
  6. 6. The method [500] as claimed in claim 5, wherein the internal error response further comprises an excessive load error message.
  7. 7. The method [500] as claimed in claim 1, wherein the acceptance, by the producer NF [302], of the network request, is based on a non-overloaded status of the microservice.
  8. 8. The method [500] as claimed in claim 7, further comprising: in an event of the acceptance of the network request, transmitting, by the producer NF [302], an overload control information (OCI) header information and a load control information (LCI) header information as a response to the consumer NF [304],
  9. 9. The method [500] as claimed in claim 1, wherein the network request is a HTTP/2 network request message.
  10. 10. A system [300] for managing incoming network requests on an overloaded producer network function (producer NF) [302], the system [300] comprising: a transceiver unit [306], at a producer NF [302], the transceiver unit [306] configured to receive a network request from a consumer network function (consumer NF) [304], wherein the network request is to establish a communication between the consumer NF [304] and the producer NF [302] to access one of a plurality of microservices running on the producer NF [302]; a processing unit [308], at the producer NF [302], the processing unit [308] configured to process the network request, wherein processing the network request comprises parsing the received network request on a network protocol level; and a determination unit [310], at the producer NF [302], the determination unit [310] configured to determine one of an acceptance and a rejection, of the network request, based on the processing of the network request and a status of the microservice.
  11. 11. The system [300] as claimed in claim 10, wherein, the parsing the received network request on the network protocol level comprises reading a header of the network request.
  12. 12. The system [300] as claimed in claim 10, wherein the transceiver unit [306] is further configured to: transmit an acknowledgement to the consumer NF [304], based on one of the acceptance and the rejection of the network request.
  13. 13. The system [300] as claimed in claim 10, wherein the rej ection, by the producer NF [302] , of the network request, is based on an overloaded status of the microservice.
  14. 14. The system [300] as claimed in claim 13, wherein, in an event of rejection of the network request, the transceiver unit [306], is further configured to transmit an internal error response as a response to the consumer NF [304] .
  15. 15. The system [300] as claimed in claim 14, wherein the internal error response further comprises an excessive load error message.
  16. 16. The system [300] as claimed in claim 10, wherein, the acceptance, by the producer NF [302], of the network request, is based on a non-overloaded status of the microservice.
  17. 17. The system [300] as claimed in claim 16, wherein, in an event of acceptance of the network request, the transceiver unit [306], is further configured to transmit an overload control information (OCI) header information and a load control information (LCI) header information as a response to the consumer NF [304] .
  18. 18. The system [300] as claimed in claim 10, wherein the network request is a HTTP/2 network request message.
  19. 19. A non-transitory computer readable storage medium storing instruction for managing incoming network requests on an overloaded producer network function (producer NF) [302], the instructions include executable code which, when executed by a one or more units of a system, cause: a transceiver unit [306] to receive at a producer NF [302], a network request from a consumer network function (consumer NF) [304], wherein the network request is to establish a communication between the consumer NF [304] and the producer NF [302] to access one of a plurality of microservices running on the producer NF [302]; a processing unit [308] to process at the producer NF [302], the network request, wherein processing the network request comprises parsing the received network request on a network protocol level; and a determination unit [310] to determine at the producer NF [302], one of an acceptance and a rejection, of the network request, based on the processing of the network request and a status of the microservice.

Description

METHOD AND SYSTEM FOR MANAGING INCOMING NETWORK REQUESTS ON AN OVERLOADED PRODUCER NETWORK FUNCTION TECHNICAL FIELD [0001] 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 managing incoming network requests on an overloaded producer network function (producer NF). 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 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. [0004] As per standard, an overloaded Network Function (producer microservice) can reject requests received from a consumer network function with a status code such as 503/429/307. It is emphasized that such an approach requires processing the complete request and thereafter rejecting with a suitable response code such as a response code 503/429/307 and response data, which adds to additional processing of application request-response to an already overloaded application. This further puts the application server in more overloaded condition. Such an approach, is therefore, counter-productive and only adds to the load of an already overloaded server. It is also noted here that communication between a consumer network function and producer network function happens through HTTP/2 stream even when the producer network function can reject requests received from the consumer network function, thus increasing the load even further on the overloaded producer network function. [0005] Thus, there exists an imperative need in the art to optimize signalling of requests when a Network Function (producer microservice) is overloaded, which the present disclosure aims to address. SUMMARY [0006] 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. [0007] An aspect of the present disclosure may relate to a method for managing incoming network requests on an overloaded producer network function (producer NF). The method comprising steps of receiving, by a transceiver unit, at a producer NF, a network request from a consumer network function (consumer NF), wherein the network request is to establish a communication between the consumer NF and the producer NF to access one of a plurality of microservices running on the producer NF. Further, the method comprises steps of processing, by a processing unit, at the producer NF, the network request, wherein processing the network request comprises parsing the received network request on a network protocol level. Further, the method comprises steps of determining, by a determination unit, at the producer NF, one of an acceptance and a rejection, of the network request, based on the processing of the network request and a status of the microservice. [0008] In an exemplary aspect of the present disclosure, the parsing the received network request on a network protocol level comprises reading a header of the network request. [0009] In an exemplary aspect of the present disclosure, the method further comprises based on one of the acceptance and the rejection of the network request, transmitting, by the producer NF, an acknowledgement to the consumer NF. [0010] In an exemplary aspect of the present disclosure, the rejection, by the producer NF, of the network request, is based on an overloaded status of the microservice. [0011] In an exemplary aspect of the present disclosure, in the event