FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGEMENT OF CONTAINERIZED NETWORK FUNCTION COMPONENTS
(CNFC)”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

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, cloud-native 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 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. 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 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. Next, the method includes facilitating, a registration unit, 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.
[0012] In an aspect of the present disclosure, the method further includes determining, by a progress monitoring unit, an initialisation status of each of the one or more CNFC instances associated with the one or more target CNFC nodes. 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 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 at least one of the one or more CNFC instances associated with the one or more target CNFC nodes is not initialised. Thereafter, the method includes creating, by a clustering unit, 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.
[0013] In an aspect of the present disclosure, the information extracted for CNFC registration is stored by a storage unit, in one or more cache units and a file system.

[0014] In an aspect of the present disclosure, prior to the facilitating the registration of the one or more target CNFC nodes based on the extracted information, the method comprises: fetching, by the registration unit from the one or more of the cache units and the file system, the stored extracted information.
[0015] In an aspect of the present disclosure, sending, by the transceiver unit, the extracted information, to 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.
[0016] In an aspect of the present disclosure, restarting, by the analysis unit, the method in an event of malfunctioning of one or more CNFC instances.
[0017] According to another aspect of the present disclosure, a system for management of containerized network function components (CNFC) is disclosed. The system comprises: a transceiver unit 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 connected to at least the transceiver unit, the extraction unit configured to extract an information from the registration request for each of the one or more CNFC nodes; an analysis unit connected to at least the extraction unit, the analysis unit configured to determine a registration status of the one or more CNFC nodes. The registration status is one of a registered status and a non-registered status. 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; 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. The one or more target CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are registered; a registration unit connected to at least the analysis unit, the registration unit 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.
[0018] In an aspect of the present disclosure, the system further comprises a progress monitoring unit, connected to at least the registration unit, wherein the progress monitoring unit 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. The initialisation status can be one of an initialised status and a non-initialised status. 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; a clustering unit connected to at least a progress monitoring unit the clustering unit configured to create a cluster of one or more final CNFC nodes. The final CNFC nodes comprise the CNFC nodes for which the initialised status is determined.
[0019] In an exemplary aspect of the present disclosure, the system further comprises a storage unit configured to store the extracted information in one or more cache units and a file system.
[0020] In an exemplary aspect of the present disclosure, the system further comprises the registration unit, that is configured to: fetch, from the one or more of the cache unit and the file system, the stored extracted information, prior to the facilitating the registration of the one or more target CNFC nodes based on the extracted information.
[0021] In an exemplary aspect of the present disclosure, the system further comprises the transceiver unit that 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.
[0022] In an exemplary aspect of the present disclosure, in an event of malfunctioning of the one or more CNFC instances, the analysis unit is further configured to reinitiate the system. The system after reinitiating, causes the transceiver unit 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. In addition, the system after reinitiating, causes the extraction unit to extract an information from the new registration request for each of the one or more CNFC nodes; the analysis unit connected to at least the extraction unit 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; 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. Further, the system causes the analysis unit to 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. Also, the system causes the registration unit connected to at least the analysis unit, 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.
[0023] According to another aspect of the present disclosure, a user equipment (UE) for management of containerized network function components (CNFC) is disclosed. The UE comprises a transceiver unit 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 connected to at least the transceiver unit, the extraction unit configured to extract an information from the registration request for each of the one or more CNFC nodes; an analysis unit connected to at least the extraction unit, the analysis unit configured 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 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; 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 connected to at least the analysis unit, the registration unit 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.
[0024] According to another aspect, the present disclosure may relate to 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 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 to extract, an information from the registration request for each of the one or more CNFC nodes; analysis unit 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 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; the analysis unit to 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; registration unit 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.
BRIEF DESCRIPTION OF DRAWINGS
[0025] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed

upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0026] FIG. 1A illustrates an exemplary block diagram of a system for management of containerized network function components (CNFC), in accordance with exemplary embodiments of the present disclosure.
[0027] FIG. 1B illustrates an exemplary block diagram of a system [100] architecture for management of containerized network function components, in accordance with exemplary embodiments of the present disclosure.
[0028] FIG. 2 illustrates an exemplary block diagram of a User Equipment (UE) for management of containerized network function components (CNFC), in accordance with exemplary embodiments of the present disclosure.
[0029] FIG. 3 illustrates an exemplary flow diagram depicting a method for management of containerized network function components, in accordance with exemplary embodiments of the present disclosure.
[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DESCRIPTION
[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address

only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0032] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0033] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0034] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0035] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process,

many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
5 [0036] The word “exemplary” and/or “demonstrative” is used herein to mean serving as
an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude
10 equivalent exemplary structures and techniques known to those of ordinary skill in the art.
Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word— without precluding any additional or other elements.
15
[0037] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating
20 with other user devices and transmitting data to the other user devices. The user equipment
may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi
25 direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone,
smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
30
[0038] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose
11

processor, a conventional processor, a digital signal processor, a plurality of
microprocessors, one or more microprocessors in association with a DSP core, a controller,
a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate
Array circuits, any other type of integrated circuits, etc. The processor may perform signal
5 coding data processing, input/output processing, and/or any other functionality that enables
the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0039] As used herein, the CNF refers to containerized network functions (CNFs) to
10 perform network duties. The CNF has a set of operational requirements: security,
compliance, resource management, scalability, availability, data persistence, networking, and monitoring.
[0040] As discussed in the background section, the current known solutions require
15 manual efforts in handling various task related to management of CNFCs such as
configuration, exchange of data between different components and the like. For large scale
deployment of the cluster instances, it is very difficult to manually manage each instance
as it requires a lot of hard work, consume time and increase the change of error. In addition,
even on choosing the cloud native deployment as per the conventional system, it is difficult
20 to send information to other instance present in the cluster which are required for their
successful inter connection/communication.
[0041] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and system that is efficient and
25 reliable to automatically manage the containerized network function components. The
present invention has the capability to store the information received during one or more CNFC instance registration as well as the provisioned information of one or more CNFCs configured on cluster manager’s end. From the registration information, the present system gets all the details required for instance inter-connection. From the provisioned
30 information, the present system gets the information such as assign ID’s to instance,
distribute range type of parameter between one or more CNFC (required for CNFC initialization) and the like. Thus, the present invention forms the cluster using the required information exchanged between the one or more CNFCs.
12

[0042] The present invention forms the cluster of instances to automate the data exchange
between one or more CNFCs for more reliability, ease and for less chances of error while
configuration. Further, by forming the cluster, the present system reduces the time and lot
5 of configuration work required for CNFC initialization. In addition, the present system
eases the task of assignment and distribution of one or more CNFC related parameters (e.g., Range-type, IDs) between instances. Moreover, the present system allows making of stand¬alone and mated pair cluster by using configuration change mode.
10 [0043] Hereinafter, exemplary embodiments of the present disclosure will be described
with reference to the accompanying drawings.
[0044] Referring to Figure 1A, an exemplary block diagram of a system [100] for management of containerized network function components (CNFC) is shown, in
15 accordance with the exemplary embodiments of the present invention. The system [100]
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. The one or more CNFC nodes are responsible for running and managing the various components that make up a network function such as a database. Each of the one or more
20 CNFC nodes is associated with one or more CNFC instances. The CNFC refer to individual
elements of network functions that are encapsulated within containers for deployment and management within a containerized environment. In addition, the one or more CNFC allows registering of a request on a central process, while dynamically directing network traffic to correct the one or more CNFC instances. Further, the one or more CNFC instances
25 refer to individual deployments or instances of Containerized Network Function
Components within a network function architecture. For example, multiple instances of CNFC node database (DB) can be deployed in Network Function architecture.
[0045] The system [100] further incudes an extraction unit [104] connected to at least the
30 transceiver unit [102]. The extraction unit [104] is configured to extract an information
from the registration request for each of the one or more CNFC nodes. The extracted information may be related to any configuration which CNFCs need to transfer in between like an IP address. For example, let a CNFC – A (behaving like a client) which requires
13

some other CNFC – B’s (say a Database, behaving like a server) IP addresses to communicate with CNFC – B. For this purpose, the central process need the IP address of the CNFC – B so that this IP address can be reported to the CNFC – A when it will first register or when it will ask for the information. 5
[0046] Also, the system [100] includes an analysis unit [106] connected to at least the extraction unit [104]. The analysis unit [106] is configured to determine a registration status of the one or more CNFC nodes. The registration status is one of: a registered status and a non-registered status. The registered status is determined in an event where all of the one
10 or more CNFC instances associated with the one or more CNFC nodes are registered on
the central process, 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 central process is a process of automating cluster formation of the network function. The one or more units of the system [100] interact with each other to
15 perform the central process.
[0047] The analysis unit [106] is further configured to determine if the extracted
information is required for registration of one or more target CNFC nodes, in an event
where the registration status is determined as the registered status. The one or more target
20 CNFC nodes comprise the CNFC nodes where all the associated CNFC instances are
registered.
[0048] The system [100] further comprises a registration unit [108] connected to at least
the analysis unit [106]. The registration unit [108] is configured to facilitate registration of
25 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.
[0049] The system [100] is configured for management of containerized network function
components (CNFC), with the help of the interconnection between the components/units
30 of the system [100].
[0050] In an exemplary aspect, the system [100] further comprises a progress monitoring unit [112] that is connected to at least the registration unit [108]. The progress monitoring
14

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. The initialisation
status can be one of an initialised status and a non-initialised status. The initialised status
is determined in an event where all of the one or more CNFC instances associated with the
5 one or more target CNFC nodes are initialised. 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. The initialization means when one or more
CNFCs receive all the required information of the one or more associated CNFC’s through
the central process, one or more CNFCs inform the central process about their initialization
10 status through an initialization request.
[0051] The system [100] further comprises a clustering unit [312] connected to at least the
progress monitoring unit [112]. The clustering unit [312] is configured to create a cluster
of one or more final CNFC nodes. The final CNFC nodes comprise the CNFC nodes for
15 which the initialised status is determined. The clustering unit [312] of the system [100] is
configured to form a cluster after connecting all the required nodes to monitor one or more CNFC instances status. Furthermore, the clustering unit [312] comprises a cluster manager that is created or formed using the using the exchanged information.
20 [0052] The cluster manager is configured to collect a set of data that includes but not
limited to plurality of configurations related to application, provision of the one or more CNFC and their parameters (number of instances, range type, id etc). The set of data associated with the CNFC is required to decide whether the cluster is going to be standalone or mated pair. Generally, being “standalone” means being able to operate independently
25 without any other machinery/system or program. In addition, mated pair generally refers to
two identical components that work together to provide backup or failover capabilities. Thus, the cluster manager has the information about a plurality of the possible CNFC’s present in the cluster. The set of data is stored in the cluster manager to identify the number of instances present in a cluster, to assign id’s to one or more CNFC instances, and to
30 distribute the range type of data between their instances. The information about the plurality
of CNFC’s present in the cluster is shared with the one or more CNFC instances based on the requirement. The set of data is stored at the cluster manager’s end in cache and file system for persistency.
15

[0053] After successfully initializing the application, registration of each CNFC instance
is performed one by one. During the registration, the system [100] collects the set of data
required for the one or more CNFC instances to connect with the system [100]. The data
5 associated with the registration of the instances are stored in a cache and a file system of
the cluster manager for persistency. Accordingly, the cluster manager sends the required data to the one or more CNFC from the cache or the file system, if available.
[0054] In an exemplary aspect, the system [100] further comprises a storage unit [114]
10 configured to store the extracted information in one or more cache units and a file system.
The storage unit [114] is configured to store data associated with implementation of the
features of the present invention. The cache units are hardware or software components
embedded in an application or device memory that automatically and temporarily stores
data consumed to reduce the data retrieval time, the next time the application or device is
15 accessed. The file system is configured to store and organize the data.
[0055] In an exemplary aspect, 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
20 extracted information. After successfully initializing the application, the registration of one
or mor CNFC instances is performed one by one by the registration unit [108]. During the registration, the present system [100] collects a plurality of details which are required for CNFC instance to connect with the system [100]. The data associated with the registration of the instances are stored in cluster unit [312]. Accordingly, the cluster unit [312] sends
25 the required data to one or more CNFC from the cache and file system, if available.
[0056] In an exemplary aspect, 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 [106], that the extracted information is required for registration of the
30 one or more target CNFC nodes.
[0057] In an exemplary aspect of the present disclosure, in an event of malfunctioning of the one or more CNFC instances, the analysis unit [104] is further configured to reinitiate
16

the system [100]. The system [100], 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. Each of the one or more CNFC nodes
is associated with one or more CNFC instances. In addition, the system [100] after
5 reinitiating, causes 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 determine a registration status of the one or more CNFC nodes. The registration status is one of a registered status and a non-registered status. The registered status is determined in an event all of the one or more
10 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. Further, the system [100] causes the analysis unit to 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
15 registered status. The one or more target CNFC nodes comprise the CNFC nodes where all
the associated CNFC instances are registered. Also, the system [100] causes 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.
20
[0058] The one or more CNFC instance receives required data to notify the application
about successful initialization. The analysis unit [106] checks successful notification
received from the one or more CNFC instances. The analysis unit [106] further monitors
the status of one or more instances and if one or more instance is in inactive mode, it restarts
25 from initial step.
[0059] The present system [100] further monitors to check if a first instance of the one or
more CNFC instances need or require any data about a second instance of the one or more
CNFC instances. If the data is required by the first instance of the one or more CNFC
30 instances, then the system [100] sends required data to other instances. This leads to
efficient and quick exchange of information between the first CNFC instance of the one or more CNFC instances and second instance of the one or more CNFC instances present in cluster.
17

[0060] After receiving the required data, the one or more CNFC instance notifies to the
cluster manager about successful initialization. The cluster manager further checks if all
the successful notification received from one or more CNFC instances. Thus, the cluster
5 manager continuously monitors the status of one or more instances in near real-time or
periodically. If any instance goes down, then the same procedure is followed.
[0061] FIG. 1B illustrates an exemplary block diagram of a system [100] architecture for
management of containerized network function components, in accordance with exemplary
10 embodiments of the present disclosure. The plurality of containerized network function
components (CNFC) instances for example CNFC 1 to CNFC 6 are connected to the central process.
[0062] Further, in accordance with the present disclosure, it is to be acknowledged that
15 the functionality described for the various the components/units can be implemented
interchangeably. While specific embodiments may disclose a particular functionality of
these units for clarity, it is recognized that various configurations and combinations thereof
are within the scope of the disclosure. The functionality of specific units as disclosed in the
disclosure should not be construed as limiting the scope of the present disclosure.
20 Consequently, alternative arrangements and substitutions of units, provided they achieve
the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0063] Referring to Figure 2, an exemplary flow diagram depicting a method [200], for
25 management of containerized network function components (CNFC), in accordance with
exemplary embodiments of the present invention is shown.
[0064] The method initiates at step [202]. Following step [204], the method includes
receiving, at a cluster manager, a registration request from containerized network function
30 component (CNFC). The registration request includes details required for one or more
CNFC instance inter-connection, assigning ID’s to one or more CNFC instance, distribute range type of parameter between one or more CNFC that is required for CNFC initialization. By simply exchanging the required information between one or more CNFC
18

and sending one or more CNFC for their initialization and inter-connectivity a cluster can be formed successfully.
[0065] Next step [206], the cluster manager extracts the required information from
5 containerized network function component (CNFC) registration and store it in cache and
file system for persistency.
[0066] Next step [208], the cluster manager checks whether all instances of the requested
containerized network function component (CNFC) type are registered or not. In case one
10 or more instances are left to register, the method moves to the step [204] of receiving the
request from other instances of containerized network function component (CNFC) type, otherwise moves to the next step [210].
[0067] Next step [210], the cluster manager checks whether the registered containerized
15 network function component (CNFC) requires any further information. In case the
information is required [212], the cluster manager sends the required information to the
registering containerized network function component (CNFC) from the stored cache and
file system for persistency. The required information may be the configured information
and/or information of other containerized network function component (CNFCs).
20 Thereafter, on successful initialization in step [214], the status is updated on the cluster
manager.
[0068] In addition, the cluster manager further checks in step [216], if other registered
containerized network function component (CNFC) also requires the information then the
25 cluster manager passes the required information to other containerized network function
component (CNFCs) as well. After passing the required information, the cluster manager checks in step [418] whether all instances of all containerized network function component (CNFCs) have been initialized or not.
30 [0069] Next step [420], the cluster manager forms the cluster after connecting one or more
required nodes. Thereafter, the cluster manager monitors, in step [222], all the containerized network function component (CNFC) instance status and restart the process in an event one or more instance goes down.
19

[0070] Thereafter, the method terminates at step [224].
5 [0071] It should be noted that FIG. 1-2 should be referred to in conjunction with each other
in order to clearly understand the concepts of the present disclosure.
[0072] Referring to FIG. 3, an exemplary flow diagram indicating the method [300] for
management of containerized network function components (CNFC) is shown, in
10 accordance with exemplary embodiments of the present disclosure. As shown in FIG. 3,
the method [300] starts at step [302]. The method [300] may be implemented using the system [100].
[0073] At step [304], the method [300] as disclosed by the present disclosure comprises
15 receiving, by the transceiver unit [102], the 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 method [300] implemented by the transceiver unit [102] receives the
registration request from one or more CNFC node(s) to form a cluster of containerized
20 network function (CNF). Each of the one or more CNFC nodes is associated with one or
more CNFC instances.
[0074] Next, at step [306], the method [300] as disclosed by the present disclosure comprises extracting, by the extraction unit [104], an information from the registration
25 request for each of the one or more CNFC nodes. The method [300] implemented by
extraction unit [104] of the system [100] extracts information such as all details required for instance inter-connection for registration of each of the one or more CNFC nodes. The extracted required information for CNFC registration is stored in one or more of a cache unit and a file system. In an aspect, the cluster manager stores provisioned information,
30 such as number of instances, range type, id etc. There may be one or more cluster manager,
that work independently or in combination pair. The cluster manager stores the information of which CNFC’s are present in a cluster. The stored data for a CNFC may be used to know the number of instances present in the cluster and may assign Ids to the CNFC instance(s),
20

distribute the range type of data between the instances. This information may also be shared to the CNFC instance(s).
[0075] Next, at step [308], the method [300] as disclosed by the present disclosure
5 comprises 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 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
10 more CNFC instances associated with the one or more CNFC nodes is not registered. The
method [300] implemented by the analysis unit [106] of the system [100] determines registration status of the one or more CNFC nodes, weather the registration status is one of a registered status and/or a non-registered status. The registered status is determined in an event where all of the one or more CNFC instances associated with the one or more CNFC
15 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.
[0076] Next, at step [310], the method [300] as disclosed by the present disclosure
20 comprises 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. The method [300]
implemented by the analysis unit [106] of the system [100] determines requirement of
25 further information for registration of one or more target CNFC nodes. The required
information can be the configured information and/or information of the one or more CNFCs. In an aspect, if other CNFC requires this information, the cluster manager pass on this information to the one or more CNFCs.
30 [0077] Next, at step [312], the method [300] as disclosed by the present disclosure
comprises 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. The method [300] implemented by the registration unit [108]
21

of the system [100] performs registration of the one or more target CNFC nodes based on the extracted information, such as configuration information and/or information of other CNFCs.
5 [0078] Thereafter, the method terminates at step [314].
[0079] In an exemplary aspect of the present disclosure, the method [300] as disclosed by the present disclosure comprises determining, by the progress monitoring unit [112], an initialization status of each of the one or more CNFC instances associated with the one or
10 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 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 at least one of the one or more CNFC instances associated with the one or more target CNFC nodes is not initialised.
15 The method [300] implemented by the progress monitoring unit [112] of the system [100]
determines initialization status of each of the one or more CNFC instances associated with the one or more target CNFC nodes. The cluster manager monitors all the CNFC instance(s) status for checking if any instance(s) down. If any instance goes down or malfunction, cluster manager restarts from initial step. The initialisation status may be one of an
20 initialised status and a non-initialised status and the initialised status is determined in an
event all of the one or more CNFC instances associated with the one or more target CNFC nodes are initialised. The non-initialised status is determined in an event at least one of the one or more CNFC instances associated with the one or more target CNFC nodes is not initialised.
25
[0080] In an exemplary aspect of the present disclosure, the method [300] as disclosed by the present disclosure comprises creating, by the clustering unit [312], the cluster of the one or more final CNFC nodes. The final CNFC nodes comprise the CNFC nodes for which the initialized status is determined. The method [300] implemented by the clustering unit
30 [312] of the system [100] creates the cluster of CNFC nodes for initialized CNFC nodes.
The cluster manager receives notification for each CNFC instance(s) for any types of happening events at instances and/or nodes and may exchange with other instances and/or nodes.
22

[0081] As is evident from the above, the present disclosure provides a technically
advanced solution by providing a method and system that is efficient and reliable to
automatically manage the containerized network function components. The present
5 invention forms the cluster by automate the data exchange between one or more CNFC
instances. It further eases the process and reduces the chances of error while configuration.
Further, by forming the cluster, the present system reduces the time and lot of configuration
work required for CNFC initialization. In addition, the present system eases the task of
assignment and distribution of one or more CNFC related parameters (e.g., Range-type,
10 IDs) between their instances. Moreover, the present system allows making of stand-alone
and mated pair cluster by using configuration change.
[0082] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many
15 changes can be made to the embodiments without departing from the principles of the
present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
20
23

We Claim:
1. A method for management of containerized network functon components (CNFC), the method comprising:
- receiving, by a transceiver unit [102], a registraton request from one or more containerized network functon component (CNFC) nodes in a consecutve sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances;
- extractng, by an extracton unit [104], an informaton from the registraton request for each of the one or more CNFC nodes;
- determining, by an analysis unit [106], a registraton status of the one or more CNFC nodes,
wherein the registraton 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 informaton is required for registraton of one or more target CNFC nodes, in an event, the registraton 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;
- facilitatng, by a registraton unit [108], registraton of the one or more target CNFC nodes based on the determinaton if the extracted informaton is required by the one or more target CNFC nodes.

2. The method as claimed in claim 1, further comprising:
determining, by a progress monitoring unit [112], an initalisaton status of each of the one or more CNFC instances associated with the one or more target CNFC nodes,
wherein the initalisaton status can be one of an initalised status and a non-initalised status, and
wherein the initalised 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 initalised, and the non-initalised 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 initalised; and creatng, by a clustering unit [312], a cluster of one or more fnal CNFC nodes, wherein the fnal CNFC nodes comprise the CNFC nodes for which the initalised status is determined.
3. The method as claimed in claim 1, wherein the informaton extracted for CNFC
registraton is stored, by a storage unit [114], in one or more cache units and a fle
system.
4. The method as claimed in claim 3, wherein prior to the facilitatng, by the
registraton unit [108], the registraton of the one or more target CNFC
nodes based on the extracted informaton, the method comprises:
- fetching, by the registraton unit [108], from the one or more of the cache units and the fle system, the stored extracted informaton.
5. The method as claimed in claim 1, the method comprising:

- sending, by the transceiver unit [102], the extracted informaton, to
the one or more target CNFC nodes, based on the determining, by the
analysis unit, that extracted informaton is required for registraton of
the one or more target CNFC nodes.
6. The method as claimed in claim 1, the method further comprising:
- restartng, by the analysis unit [106], the method in an event of
malfunctoning of the one or more CNFC instances.
7. A system for management of containerized network functon components
(CNFC), the system comprising:
- a transceiver unit [102] confgured to receive a registraton request from one or more containerized network functon component (CNFC) nodes in a consecutve sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances.
- an extracton unit [104] connected to at least the transceiver unit [102], the extracton unit [104] confgured to extract an informaton from the registraton request for each of the one or more CNFC nodes;
- an analysis unit [106] connected to at least the extracton unit [104], the analysis unit [106] confgured to
o determine a registraton status of the one or more CNFC nodes,
wherein the registraton status is one of a registered status and a non-registered 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 informaton is required for
registraton of one or more target CNFC nodes, in an event the registraton 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 registraton unit [108] connected to at least the analysis unit [106],
the registraton unit [108] confgured to facilitate registraton of the
one or more target CNFC nodes based on the determinaton if the
extracted informaton is required by the one or more target CNFC
nodes.
8. The system as claimed in claim 7, the system further comprising:
- a progress monitoring unit [112], connected to at least the registraton
unit [108], wherein the progress monitoring unit [112] is confgured to
determine an initalisaton status of each of the one or more CNFC instances associated with the one or more target CNFC nodes,
wherein the initalisaton status can be one of an initalised status and a non-initalised status, and
wherein the initalised 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 initalised, and the non-initalised 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 initalised; and

- a clustering unit [312] connected to at least a progress monitoring
unit [112], the clustering unit [312] confgured to create a cluster of
one or more fnal CNFC nodes, wherein the fnal CNFC nodes comprise
the CNFC nodes for which the initalised status is determined.
9. The system as claimed in claim 7, further comprising a storage unit [114] confgured to store the extracted informaton in one or more cache units and a fle system.
10. The system as claimed in claim 9, wherein the registraton unit [108], prior to the facilitatng the registraton of the one or more target CNFC nodes based on the extracted informaton, is confgured to:
- fetch, from the one or more cache units and the fle system, the
stored extracted informaton.
11. The system as claimed in claim 7, wherein the transceiver unit [102] is
further confgured to:
- send, to the one or more target CNFC nodes, the extracted
informaton, based on the determining, by the analysis unit, that the
extracted informaton is required for registraton of the one or more
target CNFC nodes.
12. The system as claimed in claim 7, in an event of malfunctoning of the one
or more CNFC instances, the analysis unit [106] is further confgured to:
- reinitate the system, wherein the system, afer reinitatng, causes:
- the transceiver unit [102] to receive a new registraton request from one or more containerized network functon component (CNFC) nodes

in a consecutve sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances.
- the extracton unit [104] to extract an informaton from the new registraton request for each of the one or more CNFC nodes;
- the analysis unit [106] connected to at least the extracton unit [104], to:
o determine a registraton status of the one or more CNFC nodes,
wherein the registraton status is one of a registered status and a non-registered 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 informaton is required for
registraton of one or more target CNFC nodes, in an event the registraton 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 registraton unit [108] connected to at least the analysis unit
[106], to facilitate registraton of the one or more target CNFC nodes
based on the determinaton if the extracted informaton is required by
the one or more target CNFC nodes.

13. A User Equipment (UE) for management of containerized network functon components (CNFC), the UE comprising: a system, wherein the system comprises:
- a transceiver unit [102] confgured to receive a registraton request from one or more containerized network functon component (CNFC) nodes in a consecutve sequence, wherein each of the one or more CNFC nodes is associated with one or more CNFC instances
- an extracton unit [104] connected to at least the transceiver unit [102], the extracton unit [104] confgured to extract an informaton from the registraton request for each of the one or more CNFC nodes;
- an analysis unit [106] connected to at least the extracton unit [104], the analysis unit [106] confgured to
o determine a registraton status of the one or more CNFC nodes,
wherein the registraton status is one of a registered status and a non-registered 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 informaton is required for
registraton of one or more target CNFC nodes, in an event the registraton 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 registraton unit [108] connected to at least the analysis unit [106], the registraton unit [108] confgured to facilitate registraton of the one or more target CNFC nodes based on the determinaton if the extracted informaton is required by the one or more target CNFC nodes.