Search

EP-4740637-A1 - METHOD AND SYSTEM FOR CONFIGURING AND MANAGING PROXY REGISTRATIONS IN A NETWORK

EP4740637A1EP 4740637 A1EP4740637 A1EP 4740637A1EP-4740637-A1

Abstract

The present disclosure relates to a method and a system for configuring and managing proxy registrations in a network The disclosure encompasses: receiving one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller over an interface, wherein the one or more proxy registration requests are received in one of a startup event and during an update event; defining a service instance identifier with each of the one or more proxy services during the registration; updating one or more service attributes associated with one or more proxy services, at the SCP controller [302], based at least on the one or more proxy registration requests of the one or more proxy services; and sending an update registration request to a Network Repository Function (NRF) comprising information of a set of network instances.

Inventors

  • BISHT, SANDEEP
  • BHATNAGAR, AAYUSH
  • BHATNAGAR, PRADEEP KUMAR
  • SINHA, ANURAG
  • Ansari, Ezaj
  • YADAV, RAVINDRA
  • PANDEY, PRASHANT
  • KUMAR, ANUJ

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240611

Claims (11)

  1. We Claim: 1. A method for configuring and managing proxy registrations in a network, comprising: ^ receiving, by a transceiver unit [202], one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event; ^ defining, by an identification unit [204], a service instance identifier with each of the one or more proxy services during the registration; ^ updating, by an updating unit [206], one or more service attributes associated with one or more proxy services, at the SCP controller [302], based at least on the one or more proxy registration requests of the one or more proxy services; and ^ sending, by the transceiver unit [202], an update registration request to a Network Repository Function (NRF) [120] comprising information of a set of network instances.
  2. 2. The method as claimed in claim 1, wherein the one or more proxy registration requests comprises the one or more service attributes, wherein the one or more service attributes comprises at least one of a supported network function (NF) type, a proxy type, a supported Public Land Mobile Network (PLMN), a load, a network slice, and a locality.
  3. 3. The method as claimed in claim 2, wherein the proxy type is at least one of an ingress proxy type and an egress proxy type.
  4. 4. The method as claimed in claim 3, wherein upon determining that the proxy type of the one or more proxy service is the ingress proxy type, transmitting, by the transceiver unit [202], an ingress profile information to one or more egress proxies associated with the one or more proxy services.
  5. 5. The method as claimed in claim 3 further comprising: ^ receiving, by the transceiver unit [202], a notification of NF profile update from the NRF [120]; and ^ forwarding, by the transceiver unit [202] upon receiving the notification of NF profile update, a configuration information to the ingress proxy type associated with a specific NF.
  6. 6. A system [200] for configuring and managing proxy registrations in a network, comprising: a transceiver unit [202], configured to receive one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event; an identification unit [204] connected at least to the transceiver unit [202], the identification unit [204] configured to define a service instance identifier with each of the one or more proxy services during the registration; an updating unit [206] connected at least to the identification unit [204], the updating unit [206] configured to update one or more service attributes at the SCP controller [302] based at least on the one or more proxy registration requests of the one or more proxy services; and the transceiver unit [202] further configured to send an update registration request to a Network Resource Function (NRF) [120] comprising information of a set of network instances.
  7. 7. The system [200] as claimed in claim 6, wherein the one or more proxy registration request comprises a set of attributes, wherein the set of attributes comprises at least one of a supported network function (NF) type, a proxy type, a supported Public Land Mobile Network (PLMN), a load, a slice, and a locality.
  8. 8. The system [200] as claimed in claim 7, wherein the proxy type is at least one of an ingress proxy type and an egress proxy type.
  9. 9. The system [200] as claimed in claim 8, wherein upon determining that the proxy type of the one or more proxy service is the ingress proxy type, the transceiver unit [202] is further configured to transmit an ingress profile information to one or more egress proxies associated with the one or more proxy services.
  10. 10. The system [200] as claimed in claim 8, wherein the transceiver unit [202] is configured to: receive a notification of NF profile update from the NRF [120]; and forward a configuration information to the ingress proxy type associated with a specific NF type upon receiving the notification of NF profile update.
  11. 11. A non-transitory computer-readable storage medium storing instructions for configuring and managing proxy registrations in a network, the storage medium comprising executable code which, when executed by one or more units of a system [200], causes: a transceiver unit [202] of the system [200] to receive one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event; an identification unit [204] of the system [200] to define a service instance identifier with each of the one or more proxy services during the registration; an updating unit [206] of the system [200] to update one or more service attributes at the SCP controller [302] based at least on the one or more proxy registration requests of the one or more proxy services; and the transceiver unit [202] of the system [200] to send an update registration request to a Network Resource Function (NRF) [120] comprising information of a set of network instances

Description

METHOD AND SYSTEM FOR CONFIGURING AND MANAGING PROXY REGISTRATIONS IN A NETWORK FIELD OF THE DISCLOSURE [0001] The present disclosure relates generally to the field of wireless communication systems, more particularly, the present disclosure relates to methods and systems for configuring and managing proxy registrations in a network, and may also relate to methods and systems for registering custom service for Service Communication Proxy (SCP). BACKGROUND [0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 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] 5G core networks are based on service-based architecture (SBA), which is centered around network function (NF) services, where each NF registers itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services. The Service communication Proxy (SCP) architecture contains different microservice components such as Egress SCP, Ingress SCP, and SCP Controller, where each egress SCP and Ingress SCP are associated with single or multiple NF and with single or Multiple Public Land Mobile Networks (PLMN) for better management. For Registering to NRF, all Egress SCP as well as Ingress SCP need to register separately to NRF which increases overhead at each SCP Proxy to support N27 Interface with NRF which increases compute resource requirement and thus overall cost of SCP Proxy. Also, as there can be multiple proxies, number of registration and their associated Heart Beat will increase load at NRF which ultimately increases cost of compute resources, power requirements etc. [0005] To attempt to solve the above problem, the SCP controller performs OAM (Operations Administration & Management) tasks for SCP Proxies to send a single registration to NRF containing details of all proxies. One way to achieve is to have multiple service instances corresponding to multiple SCP Proxies, however the existing solutions have not allowed any service for the SCP as it is just a Proxy, making single registration from the controller impossible. [0006] Thus, there exists an imperative need in the art to register custom service for service communication proxy, which the present disclosure aims to address. OBJECTS OF THE DISCLOSURE [0007] Some of the objects of the present disclosure, which at least one implementation disclosed herein satisfies are listed herein below. [0008] It is an object of the present disclosure to provide a system and a method for configuring and managing proxy registrations in a network. [0009] It is another object of the present disclosure to provide a solution that the SCP controller which performs OAM (Operations Administration & Management) tasks for SCP Proxies sends a single registration to NRF containing details of all proxies. SUMMARY OF THE DISCLOSURE [0010] 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. [0011] A first aspect of the present disclosure is related to a method for configuring and managing proxy registrations in a network. The method comprising receiving, by a transceiver unit, one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event. The method further comprises d