Search

EP-4740633-A1 - METHOD AND SYSTEM FOR MANAGEMENT OF CONTAINERIZED NETWORK FUNCTION COMPONENTS (CNFC)

EP4740633A1EP 4740633 A1EP4740633 A1EP 4740633A1EP-4740633-A1

Abstract

The present disclosure relates to a method and a system for management of containerized network function components (CNFC) The disclosure encompasses: receiving, by a transceiver unit [102], a registration request from one or more CNFC nodes in a consecutive sequence; extracting, by an extraction unit [104], an information from the registration request for each of the one or more CNFC nodes; determining, by an analysis unit [106], a registration status of the one or more CNFC nodes,; determining, by the analysis unit [106], if the extracted information is required for registration of one or more target CNFC nodes, in an event the registration status is determined as the registered status, wherein the one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; facilitating, by a registration unit [108], registration of the one or more target CNFC.

Inventors

  • GAURAV, KUMAR
  • BHATNAGAR, AAYUSH
  • KUMAR, RAKESH

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240613

Claims (14)

  1. 1. A method for management of containerized network function components (CNFC), the method comprising: receiving, by a transceiver unit [ 102] , a registration request from one or more containerized network function component (CNFC) nodes in a consecutive sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances; extracting, by an extraction unit [104], an information from the registration request for each of the one or more CNFC nodes; determining, by an analysis unit [106], a registration status of the one or more CNFC nodes, wherein the registration status is one of a registered status and a non-registered status, and wherein at least one of: the registered status is determined in an event where all of the one or more CNFC instances associated with the one or more CNFC nodes are registered, and the non-registered status is determined in an event where at least one of the one or more CNFC instances associated with the one or more CNFC nodes is not registered; determining, by the analysis unit [106], if the extracted information is required for registration of one or more target CNFC nodes, in an event, the registration status is determined as the registered status, wherein the one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; facilitating, by a registration unit [108], registration of the one or more target CNFC nodes based on the determination if the extracted information is required by the one or more target CNFC nodes.
  2. 2. The method as claimed in claim 1, further comprising: determining, by a progress monitoring unit [112], an initialisation status of each of the one or more CNFC instances associated with the one or more target CNFC nodes, wherein the initialisation status can be one of an initialised status and a noninitialised status, and wherein the initialised status is determined in an event where all of the one or more CNFC instances associated with the one or more target CNFC nodes are initialised, and the non-initialised status is determined in an event where at least one of the one or more CNFC instances associated with the one or more target CNFC nodes is not initialised; and creating, by a clustering unit [312], a cluster of one or more final CNFC nodes, wherein the final CNFC nodes comprise the CNFC nodes for which the initialised status is determined.
  3. 3. The method as claimed in claim 1, wherein the information extracted for CNFC registration is stored, by a storage unit [114], in one or more cache units and a file system.
  4. 4. The method as claimed in claim 3, wherein prior to the facilitating, by the registration unit [108], the registration of the one or more target CNFC nodes based on the extracted information, the method comprises: fetching, by the registration unit [108], from the one or more of the cache units and the file system, the stored extracted information.
  5. 5. The method as claimed in claim 1, the method comprising: sending, by the transceiver unit [102], the extracted information, to the one or more target CNFC nodes, based on the determining, by the analysis unit, that extracted information is required for registration of the one or more target CNFC nodes.
  6. 6. The method as claimed in claim 1, the method further comprising: restarting, by the analysis unit [106], the method in an event of malfunctioning of the one or more CNFC instances.
  7. 7. A system for management of containerized network function components (CNFC), the system comprising: a transceiver unit [102] configured to receive a registration request from one or more containerized network function component (CNFC) nodes in a consecutive sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances. an extraction unit [104] connected to at least the transceiver unit [102], the extraction unit [104] configured to extract an information from the registration request for each of the one or more CNFC nodes; an analysis unit [106] connected to at least the extraction unit [104], the analysis unit [106] configured to o determine a registration status of the one or more CNFC nodes, wherein the registration status is one of a registered status and a nonregistered status, and wherein the registered status is determined in an event all of the one or more CNFC instances associated with the one or more CNFC nodes are registered, and the non-registered status is determined in an event at least one of the one or more CNFC instances associated with the one or more CNFC nodes is not registered; o determine if the extracted information is required for registration of one or more target CNFC nodes, in an event the registration status is determined as the registered status, wherein the one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; a registration unit [108] connected to at least the analysis unit [106], the registration unit [108] configured to facilitate registration of the one or more target CNFC nodes based on the determination if the extracted information is required by the one or more target CNFC nodes.
  8. 8. The system as claimed in claim 7, the system further comprising: a progress monitoring unit [112], connected to at least the registration unit [108], wherein the progress monitoring unit [112] is configured to determine an initialisation status of each of the one or more CNFC instances associated with the one or more target CNFC nodes, wherein the initialisation status can be one of an initialised status and a non-initialised status, and wherein the initialised status is determined in an event where all of the one or more CNFC instances associated with the one or more target CNFC nodes are initialised, and the non-initialised status is determined in an event where at least one of the one or more CNFC instances associated with the one or more target CNFC nodes is not initialised; and a clustering unit [312] connected to at least a progress monitoring unit [112], the clustering unit [312] configured to create a cluster of one or more final CNFC nodes, wherein the final CNFC nodes comprise the CNFC nodes for which the initialised status is determined.
  9. 9. The system as claimed in claim 7, further comprising a storage unit [114] configured to store the extracted information in one or more cache units and a file system.
  10. 10. The system as claimed in claim 9, wherein the registration unit [108], prior to the facilitating the registration of the one or more target CNFC nodes based on the extracted information, is configured to: fetch, from the one or more cache units and the file system, the stored extracted information.
  11. 11. The system as claimed in claim 7, wherein the transceiver unit [102] is further configured to: send, to the one or more target CNFC nodes, the extracted information, based on the determining, by the analysis unit, that the extracted information is required for registration of the one or more target CNFC nodes.
  12. 12. The system as claimed in claim 7, in an event of malfunctioning of the one or more CNFC instances, the analysis unit [106] is further configured to: reinitiate the system, wherein the system, after reinitiating, causes: - the transceiver unit [102] to receive a new registration request from one or more containerized network function component (CNFC) nodes in a consecutive sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances. - the extraction unit [104] to extract an information from the new registration request for each of the one or more CNFC nodes; - the analysis unit [106] connected to at least the extraction unit [104], to: o determine a registration status of the one or more CNFC nodes, wherein the registration status is one of a registered status and a nonregistered status, and wherein the registered status is determined in an event all of the one or more CNFC instances associated with the one or more CNFC nodes are registered, and the non-registered status is determined in an event at least one of the one or more CNFC instances associated with the one or more CNFC nodes is not registered; o determine if the extracted information is required for registration of one or more target CNFC nodes, in an event the registration status is determined as the registered status, wherein the one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; - the registration unit [108] connected to at least the analysis unit [106], to facilitate registration of the one or more target CNFC nodes based on the determination if the extracted information is required by the one or more target CNFC nodes.
  13. 13. A User Equipment (UE) for management of containerized network function components (CNFC), the UE comprising: a system, wherein the system comprises: a transceiver unit [102] configured to receive a registration request from one or more containerized network function component (CNFC) nodes in a consecutive sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances an extraction unit [104] connected to at least the transceiver unit [102], the extraction unit [104] configured to extract an information from the registration request for each of the one or more CNFC nodes; an analysis unit [106] connected to at least the extraction unit [104], the analysis unit [106] configured to o determine a registration status of the one or more CNFC nodes, wherein the registration status is one of a registered status and a nonregistered status, and wherein the registered status is determined in an event where all of the one or more CNFC instances associated with the one or more CNFC nodes are registered, and the non-registered status is determined in an event where at least one of the one or more CNFC instances associated with the one or more CNFC nodes is not registered; o determine if the extracted information is required for registration of one or more target CNFC nodes, in an event the registration status is determined as the registered status, wherein the one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; a registration unit [108] connected to at least the analysis unit [106], the registration unit [108] configured to facilitate registration of the one or more target CNFC nodes based on the determination if the extracted information is required by the one or more target CNFC nodes.
  14. 14. A non-transitory computer readable storage medium for management of containerized network function components (CNFC), the storage medium comprising executable code which, when executed by one or more units of a system, causes: a transceiver unit [102] to receive a registration request from one or more containerized network function component (CNFC) nodes in a consecutive sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances; an extraction unit [104] to extract an information from the registration request for each of the one or more CNFC nodes; an analysis unit [106] to determine a registration status of the one or more CNFC nodes, wherein the registration status is one of a registered status and a non-registered status, and wherein at least one of: the registered status is determined in an event where all of the one or more CNFC instances associated with the one or more CNFC nodes are registered, and the non-registered status is determined in an event where at least one of the one or more CNFC instances associated with the one or more CNFC nodes is not registered; - the analysis unit [106] to determine if the extracted information is required for registration of the one or more target CNFC nodes, in an event, the registration status is determined as the registered status, wherein the one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; and registration unit [108] to facilitate registration of the one or more target CNFC nodes based on the determination if the extracted information is required by the one or more target CNFC nodes.

Description

METHOD AND SYSTEM FOR MANAGEMENT OF CONTAINERIZED NETWORK FUNCTION COMPONENTS (CNFC) 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 management of containerized network function (CNF) and specifically containerized network function components (CNFC). 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. 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] Various service providers continue 5G journey by building out microservices-based, cloudnative infrastructure from the core to the edge of the network. This cloud-native deployment facilitates dynamic workload provisioning, enabling unprecedented levels of operational automation, flexibility, and adaptability. However, managing Containerized Network Function (CNF) components within cloud-native environment presents certain challenges. CNFs, which are integral to 5G networks, require meticulous handling and configuration, often consuming significant human resources and increasing the likelihood of errors. [0005] Thus, in order to efficiently handle the CNFC and for proper functioning of network including but not limited to radio access network, there is an imperative need in the art for a system and method that can reliably exchange data between CNFCs and can reduce chances of error during the configuration of the CNFC. OBJECTS OF THE INVENTION [0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. [0007] It is an object of the present disclosure to provide a method and system for management of containerized network function components. [0008] It is another object of the present disclosure to reduce time and configuration efforts made during the CNFC initialization. [0009] It is yet another object of the present disclosure to monitor the CNFC instance status and make the cluster healthy again once the CNFC instance reboots. 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] According to an aspect of the present disclosure, a method for management of containerized network function components (CNFC) is disclosed. The method includes receiving, by a transceiver unit, a registration request from one or more containerized network function component (CNFC) nodes in a consecutive sequence. Each of the one or more CNFC nodes is associated with one or more CNFC instances. Next, the method includes extracting, by an extraction unit, an information from the registration request for each of the one or more CNFC nodes. Next, the method includes determining, by an analysis unit, a registration status of the one or more CNFC nodes. The registration status is one of a registered status and a non-registered status, and at least one of: the registered status is determined in an event all of the one or more CNFC instances associated with the one or more CNFC nodes are registered, and the nonregistered status is determined in an event at least one of the one or more CNFC instances associated with the one or more CNFC nodes is not registered. Next, the method includes determining, by the analysis unit, if the extracted information is required for registration of one or more target CNFC nodes, in an event the registration status is determi