DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR PARTIALLY TERMINATING A CONTAINER NETWORK FUNCTION (CNF)
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to management of Container Network Functions (CNFs) within a network infrastructure, more particularly relates to, a system and a method for partially terminating a Container Network Function (CNF).
BACKGROUND OF THE INVENTION
[0002] Telecommunications networks rely on agile and flexible network functions that can adapt rapidly to changing demands. Containerization, exemplified by technologies like Docker and Kubernetes, has become a preferred deployment method for network functions due to its ability to provide lightweight, scalable, and portable environments. Container Network Functions (CNFs) are network functions that are encapsulated within containers, making them highly adaptable and suitable for cloud-native and microservices-based architectures.
[0003] CNFs have introduced a paradigm shift in the deployment and management of network functions. Unlike traditional, hardware-based network functions, CNFs can be instantiated, scaled, updated, and decommissioned with great agility. While this flexibility enhances network resource utilization and reduces operational costs, it also introduces significant challenges.
[0004] They introduce challenges related to their lifecycle management and resiliency. One critical aspect is the graceful termination of CNF instances. In a dynamic network environment, CNFs may need to be terminated partially due to various reasons, such as load balancing, resource optimization, or fault tolerance. Partial termination is the process of gracefully terminating a subset of CNF instances while ensuring minimal disruption to network services.
[0005] Existing NFV systems and container orchestration platforms often lack dedicated mechanisms and policies for supporting partial termination effectively. This deficiency can lead to suboptimal resource utilization, service disruptions, and inefficient network operations. There is, therefore, a need for an innovative solution that enables the controlled, efficient, and seamless partial termination of CNFs within containerized environments, especially when integrated with NFV systems.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and system for partially terminating a Container Network Function (CNF).
[0007] In one aspect of the present invention, the method for partially terminating the CNF is disclosed. The method includes the step of, transmitting by one or more processors, a CNF partial termination request to an orchestrator adaptor. The method further includes the step of receiving, by the one or more processors, a response from the orchestrator adaptor pertaining to completion of the CNF partial termination. The method further includes the step of transmitting, by the one or more processors to a Physical Virtual Inventory Manager (PVIM), an inventory management request to manage an inventory database pertaining to one or more resources in response to completion of the CNF partial termination. The method further includes the step of updating, by the one or more processors, the CNF partial termination status at a Release Management Repository (RMR).
[0008] In an embodiment, the CNF partial termination request is transmitted to the orchestrator adaptor in response to receiving by the one or more processors, the CNF partial termination request from a user via a User Interface (UI) module of a User Equipment (UE).
[0009] In an embodiment, the response from the orchestrator adaptor pertains to completion of the CNF partial termination which includes at least one of, termination of all running plurality of Container Network Function Components (CNFCs), or termination of at least one selected CNFC from the plurality of CNFCs based on the CNF partial termination request.
[0010] In an embodiment, the step of transmitting, by the one or more processors, the CNF partial termination request to the orchestrator adaptor further includes the steps of transmitting, by the one or more processors, from the orchestrator adaptor, the CNF partial termination request to a host to partially terminate the CNF. Further, receiving, by the one or more processors, at the orchestrator adaptor, from the host, a status of the CNF partial termination.
[0011] In an embodiment, managing the inventory database based on the inventory management request to the PVIM includes at least one of, release the one or resources which are currently utilized in response to completion of the CNF partial termination and updating the inventory database thereof.
[0012] In an embodiment, the one or more processors, is configured to enable an asynchronized event-based method for utilizing an interface.
[0013] In an embodiment, the method further comprising, in a high availability mode, engaging by the one or more processors, a next available orchestrator adaptor instance during processing the CNF partial termination request. The one or more processors engages the next available orchestrator adaptor instance when a current orchestrator adaptor instance is down.
[0014] In an embodiment, the step of updating, by the one or more processors, the CNF partial termination status at the RMR includes the steps of, transmitting, by the one or more processors, updated CNF partial termination status to the RMR. Further, receiving, by the one or more processors, an acknowledgement from the RMR pertaining to updating of the CNF partial termination in response to the transmitted CNF partial termination status.
[0015] In an embodiment, wherein the interface is an CM_OA between a Container Network Function Lifecycle Manager (CNFLM) and the orchestrator adaptor.
[0016] In an embodiment, the one or more processors, receives a partial termination acknowledgement from the UI via the interface.
[0017] In another aspect of the present invention, the system for partially terminating the CNF is disclosed. The system includes a transmitting unit, configured to transmit a CNF partial termination request to the orchestrator adaptor. The system includes a receiving unit, configured to receive, a response from the orchestrator adaptor pertaining to completion of the CNF partial termination. The transmitting unit, is further configured to transmit, to a Physical Virtual Inventory Manager (PVIM), an inventory management request to manage an inventory database pertaining to one or more resources in response to completion of the CNF partial termination. The system further includes an updating unit, configured to update, the CNF partial termination status at the RMR.
[0018] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to transmit, the CNF partial termination request to the orchestrator adaptor. The processor is configured to receive, the response from the orchestrator adaptor pertaining to completion of the CNF partial termination. The processor is further configured to, transmit, to the PVIM, the inventory management request to manage the inventory database pertaining to one or more resources in response to completion of the CNF partial termination. The processor is configured to update, the CNF partial termination status at the RMR.
[0019] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors. The one or more primary processors is coupled with a memory. The one or more primary processors causes the UE to transmit the partial termination request to the one or more processors pertaining to the CNF partial termination.
[0020] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0021] 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.
[0022] FIG. 1 is an exemplary block diagram of an environment for partially terminating a Container Network Function (CNF), according to one or more embodiments of the present invention;
[0023] FIG. 2 is an exemplary block diagram of a system for partially terminating the CNF, according to one or more embodiments of the present invention;
[0024] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0025] FIG. 4 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0026] FIG. 5 is a signal flow diagram for partially terminating the CNF, according to one or more embodiments of the present invention; and
[0027] FIG. 6 is a schematic representation of a method for partially terminating the CNF, according to one or more embodiments of the present invention.
[0028] FIG. 7 illustrates an architecture framework (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with an embodiment of the present invention.
[0029] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0030] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0031] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0032] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0033] FIG. 1 illustrates an exemplary block diagram of an environment 100 for partially terminating the CNF, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 110, a server 115, a network 105 and a system 120 communicably coupled to each other for partially terminating the CNF.
[0034] As per the illustrated embodiment and for the purpose of description and illustration, the UE 110 includes, but not limited to, a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0035] In an embodiment, the UE 110 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as a 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 computing device.
[0036] The environment 100 includes the server 115 accessible via the network 105. The server 115 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0037] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0038] The network 105 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0039] The environment 100 further includes the system 120 communicably coupled to the server 115 and the UE 110 via the network 105. The system 120 is configured for partially terminating the CNF. As per one or more embodiments, the system 120 is adapted to be embedded within the server 115 or embedded as an individual entity.
[0040] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0041] FIG. 2 is an exemplary block diagram of the system 120 for partially terminating the CNF, according to one or more embodiments of the present invention.
[0042] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a User Interface (UI) 215, and a database 220. For the purpose of description and explanation, the description will be explained with respect to one processor 205 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 120 may include more than one processor 205 as per the requirement of the network 105. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0043] As per the illustrated embodiment, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0044] In an embodiment, the UI 215 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The UI 215 facilitates communication of the system 120. In one embodiment, the UI 215 provides a communication pathway for one or more components of the system 120. Examples of such components include, but are not limited to, the UE 110 and the database 220.
[0045] The database 220 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 220 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0046] In order for the system 120 to partially terminate the CNF, the processor 205 includes one or more modules. In one embodiment, the one or more modules/units includes, but not limited to, a transmitting unit 225, a receiving unit 230, an updating unit 235 and a High-Availability (HA) unit 240 communicably coupled to each other for partially terminating the CNF.
[0047] In one embodiment, the one or more modules includes, but not limited to, the transmitting unit 225, the receiving unit 230, the updating unit 235, and the HA unit 240 can be used in combination or interchangeably for partially terminating the CNF.
[0048] The transmitting unit 225, the receiving unit 230, the updating unit 235 and the HA unit 240, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0049] The transmitting unit 225 is configured to transmit, a Container Network Function (CNF) partial termination request to an orchestrator adaptor 410 (as shown in the FIG.4). The CNF partial request may include information, such as but not limited to, identification of the CNF, list of Container Network Function Components (CNFCs) for termination, and termination preferences.
[0050] In an embodiment, the identification of the CNF refers to a unique reference or identifier that distinguishes a specific CNF from others within the network 105. The identification of the CNF for example may include, User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Policy Control Function (PCF). The CNF is a self-contained network function that is deployed in the containerized environment, responsible for specific tasks within the network 105. Each CNF needs a unique identifier to ensure that may be correctly referenced for management operations, such as, but not limited to, deployment, scaling, or termination.
[0051] The CNF is made up of multiple smaller components, referred to as list of CNFCs. Each CNFC performs a specific role within the overall function of the CNF, such as, but not limited to, handling traffic, managing resources, or enforcing security policies. The list of CNFCs for termination identifies the specified components that should be terminated. The examples of list of CNFCs includes, but not limited to, UPF CNF, AMF CNF, SMF CNF, and PCF CNF. The list of CNFCs indicates how different CNFCs within the CNF may be selectively terminated based on network conditions, resource requirements, or maintenance needs, without disrupting the entire CNF.
[0052] The termination preferences define how the CNFCs listed for termination should be handled. The termination preferences ensure that the process is managed according to some of, but not limited to, network needs, resource availability, and service continuity requirements. The termination preferences include, but not limited to, time-based termination, resource reallocation, and pre-termination notification.
[0053] In an embodiment, the CNF partial termination request is transmitted to the orchestrator adaptor 410 in response to receiving by the receiving unit 230 the CNF partial termination request from a user via the User Interface (UI) 215 of the UE 110. The user may be a network administrator, service operator, and communication provider. The transmitting unit 225 transmits the CNF partial termination request to the orchestrator adaptor 410 to initiate the partial termination of the CNF. The CNF partial termination is an operation in the management of containerized network functions within the network 105. The CNF partial termination request is intended to for at least one of, but not limited to, reducing capacity after the peak event, decommissioning legacy services, maintenance and upgrades, and adapting to changes in user demand. Some of the benefits of the CNF partial termination include enhanced cost efficiency, improved network performance, and increased scalability.
[0054] Subsequent to transmission of the CNF partial termination request by the transmitting unit 225 to the orchestrator adaptor 410, the transmitting unit 225 is further configured to transmit the CNF partial termination request to a host 510 (as shown in FIG. 5) to partially terminate the CNF. Thereafter, the receiving unit 230 is configured to receive from the host 510, the status of the CNF partial termination. The host 510 is the server that has the containerization engine installed and responsible for building and running the containers. The host 510 provides the environment where containers are executed and managed. The host 510 includes, but not limited to, container management, partial termination of CNF, and one or more resource allocation.
[0055] Upon receiving the response from the orchestrator adaptor 410 by the receiving unit 230, the transmitting unit 225 is again configured to transmit an inventory management request to a Physical & Virtual Inventory Manager (PVIM) 505 (as shown in FIG. 5). The request is made to manage the inventory database 220 in response to the completion of the CNF partial termination. The orchestrator adaptor 410 and the CNFLM 405 communicate through the interface, ensuring that management tasks and orchestration actions are coordinated effectively.
[0056] Upon receiving the response from the orchestrator adaptor 410 by the receiving unit 230, the transmitting unit 225 is again configured to transmit, an inventory management request to a Physical Virtual Inventory Manager (PVIM) 505 (as shown in the FIG. 5). The inventory management request is a request to manage the database 220 for example the inventory database, pertaining to one or more resources in response to completion of the CNF partial termination. The PVIM 505 is responsible for managing and maintaining the database 220 of physical and virtual resources within the network 105. The PVIM 505 maintains an up-to-date inventory of all service and network resources, both physical and virtual. Virtual resource levels are discovered via interaction with the Virtual Infrastructure Managers deployed in telecom cloud and physical resource levels are discovered via a network discovery process and helps to take accurate decisions as to where to deploy services. The database 220 is dynamically updated as resources are added, removed, assigned and de-assigned and as services are created, scaled and terminated. The solutions dynamic inventory enables policy-driven scaling and healing of services.
[0057] The PVIM 505 is configured to perform at least one of the tasks, such as, updating records to reflect changes after the CNF partial termination, handling the release and reallocation of resources, and ensuring accurate and efficient resource management. Thereafter, the PVIM 505 coordinates with other components, such as Container Network Function Life Cycle Manager (CNFLM) 405 and the orchestrator adaptor 410 to synchronize the inventory data and provides reporting and auditing capabilities to support visibility and compliance.
[0058] In an embodiment, managing the inventory database based on the inventory management request to the PVIM 505 includes at least one of, release the one or resources which are currently utilized in response to completion of the CNF partial termination and updating the inventory database thereof.
[0059] In an embodiment, the releasing one or more resource refers to the process of making network or computing one or more resources that were allocated to the CNF available for other tasks once the CNF is partially terminated. Releasing on or more resource and updating includes, but not limited to, partial termination, one or more resource allocation, one or more resource release, and database update. Updating the inventory database refers to the process of recording and reflecting changes in one or more resource allocation and availability after the partial termination of the CNF. Updating the inventory database ensures that the inventory system accurately reflects the current state of network resources. Updating the database 220 includes, but not limited to, accurate one or more resource tracking, and efficient one or more resource management.
[0060] Consequently, the updating unit 235 is configured to update the CNF partial termination status at a Release Management Repository (RMR) 515 (as shown in FIG. 5). The RMR 515 refers to a system or the database 220 used for managing and tracking status of releases, updates, and configuration management related to CNF partial termination status. The RMR 515 also includes, but not limited to, coordination and communication, and compliance and auditing.
[0061] The updating unit 235 updates the CNF partial termination status at the RMR 510. After initiating the partial termination of the CNF, the updating unit 235 transmits the updated CNF partial termination status to the RMR 510 and ensures that the RMR 510 remains synchronized with the ongoing changes in the CNF’s lifecycle, thereby maintaining accurate records of CNFs which have been partially terminated.
[0062] Once the status update is transmitted, the updating unit 235 is configured to await the acknowledgment from the RMR 510. The acknowledgment serves as confirmation that the RMR 510 has successfully received and processed the updated CNF partial termination status. The acknowledgment is crucial as validates that the updated CNF partial termination status has been stored in the RMR 510.
[0063] If the updating unit 235 does not receive an acknowledgment from the RMR 510 within the predefined timeout period after transmitting the CNF partial termination status, it may initiate the retry mechanism or generate an alert. The retry mechanism or alert generation ensures that the system operator is notified of the failure to update the CNF partial termination status in the RMR 510. The acknowledgment process enhances the reliability and ensuring that all changes related to CNF partial termination are properly tracked and accurately reflected in the RMR 510 for ongoing management purposes.
[0064] Further, the HA unit 240 is configured to ensure high availability during the processing of the CNF partial termination requests. The HA unit 240 actively monitors the status of the orchestrator adaptor 410 instances and, if the current orchestrator adaptor 410 instance fails, the HA unit 240 automatically engages the next available orchestrator adaptor 410 instance from a pool of redundant instances. This advantageously ensures that the CNF partial termination process continues seamlessly without interruption. The HA unit 240 handles the transition by re-routing requests, managing state or session information, and notifying system operators or logging mechanisms of the switch. The HA unit 240 enhances the system 120 resilience, minimizes downtime, and maintains operational efficiency, thereby supporting reliable and uninterrupted CNF management.
[0065] FIG. 3 describes a preferred embodiment of the system 120 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a and the system 120 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0066] As mentioned earlier in FIG. 1, each of the first UE 110a, the second UE 110b, and the third UE 110c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 110a without deviating from the scope of the present disclosure and limiting the scope of the present disclosure. The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120.
[0067] The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a transmit a partial termination request to the one or more processors 205.
[0068] As mentioned earlier in FIG. 2, the one or more processors 205 of the system 120 is configured for partially terminating the CNF. As per the illustrated embodiment, the system 120 includes the one or more processors 205, the memory 210, the UI 215, and the database 220. The operations and functions of the one or more processors 205, the memory 210, the UI 215, and the database 220 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0069] Further, the processor 205 includes the transmitting unit 225, the receiving unit 230, the updating unit 235, and HA unit 240. The operations and functions of the transmitting unit 225, the receiving unit 230, the updating unit 235, and the HA unit 240 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0070] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 120 for partially terminating the CNF, according to one or more embodiments of the present invention.
[0071] The architecture 400 includes the UI 215, the Container Network Functions Life Cycle Manager (CNFLM) 405, the orchestrator adaptor 410, an infrastructure 415, an container network function lifecycle Manager- Orchestrator Adapter (CM_OA) interface 420, and the database 220.
[0072] The UI 215 acts as the interaction layer between the end-user and the underlying components. The underlying components include, the CNFLM 405, the orchestrator adaptor 410, the infrastructure 415, the CM_OA interface 420, and the database 220. The UI 215 allows users to transmit commands such as initiating CNF partial termination and receive status updates. The partial termination commands are crucial for managing the lifecycle of CNFs within the network 105.
[0073] Further. the UI 215 may configure to transmit partial termination request to the CNFLM 405. The CNFLM 405 manages the lifecycle of CNFs which includes, but not limited to deployment, scaling, updating, and termination. The CNF partial termination request is transmitted to the orchestrator adaptor 410 in response to receiving by the CNFLM 405, the CNF partial termination request from the user via the UI 215 of the UE 110. The CNFLM 405 is configured to enable an asynchronized event-based method for utilizing the CM_OA interface 420. The asynchronous event-based method for utilizing the CM_OA interface 420 between the CNFLM and Orchestrator Adaptor 410 interface refers to the communication approach where the CNFLM 405 and the orchestrator adaptor 410 interact without requiring synchronous, immediate responses. The asynchronous event-based method includes, but not limited to, event generation, non-blocking communication, event handling, error and recovery handling. Further the CNFLM 405 receives the partial termination acknowledgement from the UI 215 via the CM_OA interface 420.
[0074] Thereafter, the CNFLM 405 may configure to transmit the CNF partial termination request to the orchestrator adaptor 410. The orchestrator adaptor 410 performs the CNF termination operation and terminates all running CNFCs of the CNF and delivers back response to CNFLM 405. The orchestrator adaptor 410 act as a bridge between the CNFLM 405 and infrastructure 415. The orchestrator adaptor 410 handles the deployment and termination of CNFs within container environments. The orchestrator adaptor 410 forwards requests from the CNFLM 405 to hosts 510 and reports the status back to the CNFLM 405. The host 510 provides the runtime environment for CNFs to manage by the orchestrator adaptor 410. The host 510 executes the partial terminating CNF components as instructed by the orchestrator adaptor 410.
[0075] Further, the response of the CNF partial termination request is received at the CNFLM 405 from the orchestrator adaptor 410 pertaining to completion of the CNF partial termination. The response from the orchestrator adaptor 410 pertains to completion of the CNF partial termination which includes at least one of, termination of all running plurality of CNFCs, or termination of at least one selected CNFC from the plurality of CNFCs CNF partial termination request. The orchestrator adaptor 410 communicates with the host 510 to initiate the termination process. The host 510 begins the CNF partial termination process by either terminating all running CNFCs or just selected CNFCs. The host 510 sends the status update on the CNF partial termination to the orchestrator adaptor 410.
[0076] The host 410 informs whether the termination process is successful and specifies which components were terminated. Further, the host 410 receives the update on the CNF partial termination from the orchestrator adaptor 410. The orchestrator adaptor 410 transmits the acknowledgement of the partial termination status to the CNFLM 405. The orchestrator adaptor 410 provides updates on the completion of the CNF partial termination process and enables the CNFLM 405 to proceed with one or more resource management tasks and status updates at the database 220. The database 220 stores and manages details of CNFs and resources. The database 220 facilitates such as, but not limited to, up-to-date inventory tracking, event logging for traceability, quick data retrieval for system components, synchronization across the system, and support for asynchronous operations by recording and updating event status.
[0077] After completion of the CNF partial termination, the CNFLM 405 transmits to the PVIM 505 to release the resources associated with the terminated CNFCs and the PVIM 505 updates the database 220, thereby advantageously ensuring that network resources are accurately tracked and made available for other functions. The PVIM 505 manages and tracks the one or more resources and updates the database 220 and one or more resource status based on the changed in the CNF deployment or termination.
[0078] Further the CNFLM 405 transmits the updated CNF partial termination status to the RMR 515 and receives the acknowledgement from the RMR 515. The RMR 515 updates the CNF partial termination status in response to the transmitted CNF partial termination status. The RMR 520 ensures that the CNF termination status is recorded and tracked for future reference and management.
[0079] In an embodiment, container network function lifecycle manager-Orchestrator adaptor (CM_OA) interface 420 is an interface, which serves as an intermediary between the CNFLM 405 and the orchestrator adaptor 410. The CM_OA interface 420 ensures that management tasks and orchestration actions are coordinated effectively. The CM_OA interface 420 facilitates and coordinates with interactions, ensuring that tasks like CNF partial termination are executed smoothly and efficiently. The CM_OA interface 420 plays a crucial role in enabling the CNFLM 405 and orchestrator adaptor 410 to communicate and manage tasks like, but not limited to, dynamic network slicing, real-time QoS adjustment, and fault management.
[0080] In an embodiment, the CNFLM 405 receives the partial termination acknowledgement from the UI 215 via the CNFLM 405. The CNFLM 405 ensures that the CM_OA interface 420 is informed of the successful partial termination and completing the process.
[0081] FIG. 5 is a signal flow diagram for partially terminating the CNF, according to one or more embodiments of the present invention.
[0082] At step 520, the UI 215 initiates the process of the CNF partial termination by transmitting the CNF partial termination request to the CNFLM 405 to request the partial termination of the CNF.
[0083] At step 525 upon receiving the partial termination request from the UI 215, the CNFLM 405 forwards the partial termination request to the orchestrator adaptor 410. Upon receiving the partial termination request, the orchestrator adaptor 410 interacts with the RMR 515 to initiate and complete the deletion of the CNFC images. After completing the deletion of the CNFC images, the orchestrator adaptor 410 is responsible for communicating with the infrastructure 415 to manage the termination of the selected CNFCs.
[0084] At step 530, upon receiving the CNF partial termination request the orchestrator adaptor 410 transmits the CNF partial termination request to the host 510. The host 410 is responsible for initiating the CNF partial termination process by either terminating all running CNFCs or just selected CNFCs.
[0085] At step 535, the host 510 transmits the status update on the CNF partial termination back to the orchestrator adaptor 410. The CNF partial termination status update indicates whether the termination process is successful and specifies which CNFCs are terminated.
[0086] At step 540, upon receiving the status update on the CNF partial termination, the orchestrator adaptor 410 transmits the acknowledgement of the CNF partial termination status to the CNFLM 405. Th acknowledgment of the CNF partial termination status indicates the completion of the process and enables the CNFLM 405 to proceed with resource management and status updates.
[0087] At step 545, upon receiving the acknowledgment of the CNF partial termination status from the orchestrator adaptor 410, the CNFLM 405 transmits the request to the PVIM 505 to release the resources associated with the terminated CNFCs and update the inventory database. The process of transmitting the request to release resources and update the inventory ensuring that network resources are accurately tracked and made available for other functions.
[0088] At step 550, thereafter, the PVIM 505 acknowledges the updates received from the CNFLM 405. The PVIM 505 confirms that the resources have been successfully released and that the database 220 has been updated.
[0089] At step 555, upon receiving the acknowledgment from the inventory update from the PVIM 505, the CNFLM 405 transmits the updated request to the RMR 520 to update the CNF partial termination status of the CNF. The RMR 520 ensures that the CNF partial termination status is accurately recorded and tracked for future reference and management.
[0090] At step 560, the RMR 510 updates the CNF partial termination status based on the updated request received from the CNFLM 405. The updated status in the RMR 510 reflects the completion of the CNF partial termination process within the network management records.
[0091] At step 565, the CNFLM 405 forwards the CNF partial termination acknowledgement received from the orchestrator adaptor 410 to the UI 215. The CNFLM 405 ensures that the UI 215 is informed of the successful CNF partial termination, thereby completing the process.
[0092] FIG. 6 is a flow diagram of a method 600 for partially terminating the CNF, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0093] At step 605, the method 600 includes the step of transmitting, by the one or more processors, the CNF partial termination request to the orchestrator adaptor 410. The CNF partial termination request is transmitted to the orchestrator adaptor 410 in response to receiving by the one or more processors 205, the CNF partial termination request from the user via the UI 215 of the UE 110.
[0094] At step 610, the method 600 includes the step of receiving, by one or more processors 205, the response from the orchestrator adaptor 410 pertaining to completion of the CNF partial termination. The response from the orchestrator adaptor 410 pertains to completion of the CNF partial termination which includes at least one of, termination of all running plurality of the CNFCs, or termination of at least one selected CNFC from the plurality of CNFCs.
[0095] At step 615, the method 600 includes the step of the transmitting by the one or more processors 205 to the PVIM 505, the inventory management request to manage the database such as the inventory database pertaining to one or more resources in response to completion of the CNF partial termination. Managing the inventory database includes at least one of, release the one or resources which are currently utilized in response to completion of the CNF partial termination and updating the inventory database.
[0096] At step 620, the method 600 includes the step of updating by the one or more processors 205, the CNF partial termination status at the RMR 515. Updating, the CNF partial termination status at the RMR, includes the steps of transmitting by the one or more processors 205 updated CNF partial termination status to the RMR 515. Further, receiving by the one or more processors 205 the acknowledgement from the RMR 515 pertaining to updating of the CNF partial termination in response to the transmitted CNF partial termination status.
[0097] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 205. The processor 205 is configured to transmit, the CNF partial termination request to the orchestrator adaptor 410. The processor 205 is further configured to receive the response from the orchestrator adaptor 410 pertaining to completion of the CNF partial termination. The processor 205 is further configured to transmit to the PVIM 505, the inventory management request to manage the inventory database pertaining to one or more resources in response to completion of the CNF partial termination. The processor 205 is further configured to update the CNF partial termination status at the RMR 515.
[0098] FIG. 7 illustrates an architecture framework 700 (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with an embodiment of the present invention. The architecture framework 700 includes the UI 215, a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module 705, a platform foundation service module 710, a platform core service module 715, and a platform resource adapter and utilities module 720.
[0099] The NFV and SDN design function module 705 is crucial for modernizing network infrastructure by enabling virtualized, scalable, and programmable network functions and management systems, particularly within the framework of CNFs. The platform foundation service module 710 refers to the underlying services and infrastructure components that support and enable the deployment, operation, and management of containerized network functions. The platform foundation service module 710 provides the essential capabilities and resources required for the CNF environment to function effectively.
[00100] The platform core service module 715 refers to the fundamental services and components that are essential for the core functionality and operation of containerized network functions. These services are critical for the effective deployment, execution, and management of CNFs, providing the necessary support and infrastructure for their operation. The platform resource adapter and utilities module 720 refers to a set of components and tools designed to manage and adapt various resources and services necessary for the operation of CNFs. The platform resource adapter and utilities module 720 plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.
[00101] The NFV and SDN design function module 710 includes a VNF lifecycle manger 705a, a VNF catalog 705b, a network service catalog 705c, a network slicing and service chaining manger 705d, a physical and virtual resource manager (PVIM) 505, and a CNF lifecycle manager (CNFLM) 405.
[00102] The VNF lifecycle manager 705a is responsible for managing the entire lifecycle of Virtual Network Functions (VNFs). The VNF lifecycle manager 705a ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog 705b (referred to as a CNF catalog) is a repository or registry that stores information about various containerized network functions and their configurations. The VNF catalog 705b serves as a central reference for managing and deploying CNFs, providing details about their capabilities, requirements, and how they can be used within the network environment. The network service catalog 705c is a comprehensive repository that organizes and manages the information related to network services composed of multiple CNFs or other network functions. The network service catalog 705c serves as a central resource for defining, deploying, and managing these services within a containerized network environment.
[00103] The network slicing and service chaining manger 705d is a crucial component responsible for orchestrating and managing network slicing and service chaining functionalities. These functionalities are essential for efficiently utilizing network resources and delivering tailored network services in a dynamic and scalable manner. The PVIM 505 is a critical component responsible for overseeing and managing both physical and virtual resources required to support the deployment, operation, and scaling of CNFs. The PVIM 505 ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.
[00104] Further, the CNFLM 405is a component responsible for overseeing the entire lifecycle of containerized network functions. This includes the management of CNFs from their initial deployment through ongoing operation and maintenance, up to their eventual decommissioning. The CNFLM 405ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.
[00105] The platform foundation service module 710 includes a microservice elastic load balancer 710a, an identity and access manager 710b, a command line interface 710c, a central logging manager 710d and an event routing manger 710e.
[00106] The microservice elastic load balancer 710a is a specific type of load balancer designed to dynamically distribute network traffic across a set of microservices running in a containerized environment. Its primary purpose is to ensure efficient resource utilization, maintain high availability, and improve the performance of network services by evenly distributing incoming traffic among multiple instances of microservices. The identity and access manager 710b is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager 710b ensures that only authorized users and systems can access specific resources, and it enforces policies related to identity verification, authentication, authorization, and auditing within the CNF ecosystem.
[00107] The central logging manger 710d is a component responsible for aggregating, managing, and analyzing log data from various containerized network functions and associated infrastructure components. This centralized approach to logging ensures that logs are collected from disparate sources, consolidated into a single repository, and made accessible for monitoring, troubleshooting, and auditing purposes. The event routing manager 710e is a component responsible for handling the distribution and routing of events and notifications generated by various parts of the CNF environment. This includes events related to system status, performance metrics, errors, and other operational or application-level events. The event routing manager 710e ensures that these events are efficiently routed to the appropriate consumers, such as monitoring systems, alerting systems, or logging infrastructure, for further processing and action.
[00108] The platform core service module 715 includes an NFV infrastructure monitoring manager 715a, an assurance manager 715b, a performance manger 715c, a policy execution engine 715d, a capacity monitoring manger 715e, the RMR 515, a configuration manger and GCT (715g), a NFV platform decision analytics unit 715h, a platform NoSQL DB 715i, a platform scheduler and Cron Jobs module 715j, a VNF backup & upgrade manger 715k, a micro service auditor 715l, and a platform operation, administration and maintenance manager 715m.
[00109] The NFV infrastructure monitoring manager 715a monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager 715a provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager 715a detects and alerts infrastructure issues. Further, the NFV infrastructure monitoring manager (715a) integrates with monitoring tools to ensure reliable operation of CNFs.
[00110] The assurance manager 715b manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manger 715c optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine 715d enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine 715d executes policies related to security, resource allocation, and service quality. Further, the policy execution engine 715d executes policies, translates policy rules into actionable configurations and enforces compliance across CNFs.
[00111] The capacity monitoring manager 715e monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The RMR 515 stores and manages software releases, configurations, and versions of CNFs. Further, the RMR 515 keeps track of different versions of CNFs.
[00112] The configuration manager and Golden Configuration Template (GCT) 715g manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit 715h analyzes data from a NFV platform to support decision-making and strategic planning.
[00113] The platform NoSQL database (DB) 715i is used for storing and managing large volumes of unstructured or semi-structured data within the CNF environment. The platform scheduler and Cron Jobs module 715j manages scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manger 715k oversees the backup and upgrade processes for Virtual Network Functions (VNFs) within the CNF environment.
[00114] The micro service auditor 715l monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager 715m manages the overall operation, administration, and maintenance of the CNF platform.
[00115] The platform resource adapter and utilities module 720 includes a platform external API adaptor and gateway 720a, a generic decoder and indexer 720b, the orchestrator adaptor 410, an opensatck API adaptor 720 and a NFV gateway 720e.
[00116] The platform external API adaptor and gateway 720a facilitates communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer 720b decode and indexes various types of data and logs within the CNF environment. The orchestrator adaptor 410 facilitates communication between a swarm clusters and the CNF environment, including container deployment, scaling, and management.
[00117] The opensatck API adaptor 720d provides an interface for the CNF platform to interact with OpenStack APIs, enabling operations such as provisioning, scaling, and managing virtual resources. The NFV gateway 720e manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.
[00118] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00119] The present disclosure includes technical advancements in the system automatically scales CNF instances based on real-time demand, reduces configuration overhead with global CNF flags, enhances fault tolerance by redistributing components during failures, offers centralized monitoring through the unified dashboard, and integrates seamlessly with existing orchestration tools for improved compatibility and faster implementation.
[00120] The present invention offers multiple advantages in the system can automatically scale CNF instances up or down based on real-time demand and resource availability within the POD, ensuring optimal performance without manual intervention. No replication factor needs to be defined at the design time of CNF and decided automatically as per the hosts present in the POD based on the flag of global CNF. No max instance count needs to be defined at the design time of CNF. Less computation on policy defining services as it’s a flag-based instantiation. Same instance of CNF components can be instantiated using this flag where it must be instantiated in all the hosts residing in selected POD. Ease of user to instantiate all CNFCs for particular CNF to instantiate at all hosts inside POD.
[00121] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[00122] Environment- 100
[00123] User Equipment (UE)- 110
[00124] Server- 115
[00125] Network- 105
[00126] System -120
[00127] Processor- 205
[00128] Memory- 210
[00129] User interface- 215
[00130] Database - 220
[00131] Transmitting unit - 225
[00132] Receiving unit - 230
[00133] Updating unit – 235
[00134] Primary processor - 305
[00135] Primary memory - 310
[00136] Container Network Function-Life Cycle Manager (CNFLM) - 405
[00137] Orchestrator adaptor - 410
[00138] Infrastructure - 415
[00139] Container Network Function Lifecycle manager-Orchestrator Adapter (CM_OA) interface - 420
[00140] Physical Virtual Inventory Manager (PVIM) - 505
[00141] Host - 510
[00142] Resource Management Repository (RMR) – 515
[00143] System architecture – 700
[00144] NFV and SDN design function – 705
[00145] VNF lifecycle manger - 705a
[00146] VNF catalog - 705b
[00147] Network service catalog - 705c
[00148] Network slicing and service chaining manger - 705d
[00149] Platform foundation service module - 710
[00150] Microservice elastic load balancer - 710a
[00151] Identity and access manager - 710b
[00152] Command line interface - 710c
[00153] Central logging manger - 710d
[00154] Event routing manger - 710e
[00155] Platform core service module – 715
[00156] NFV infrastructure monitoring manager - 715a
[00157] Assurance manager - 715b
[00158] Performance manger - 715c
[00159] Policy execution engine - 715d
[00160] Capacity monitoring manger - 715e
[00161] Configuration manger and GCT - 715g
[00162] NFV platform decision analytics - 715h
[00163] Platform NoSQL DB - 715i
[00164] Platform scheduler and cron Jobs module - 715j
[00165] VNF backup & upgrade manger - 715k
[00166] Micro service auditor - 715l
[00167] Platform operation, administration and maintenance manager - 715m
[00168] Platform resource adapter and utilities module – 720
[00169] Platform External API adaptor and gateway - 720a
[00170] Generic decoder and indexer - 720b
[00171] OpenStack API adaptor - 720d
[00172] NFV gateway - 720e
,CLAIMS:CLAIMS:
We Claim:

1. A method (600) for partially terminating a Container Network Function (CNF), the method (600) comprises the steps of:
transmitting, by one or more processors (205), a CNF partial termination request to an orchestrator adaptor (410);
receiving, by the one or more processors (205), a response from the orchestrator adaptor (410) pertaining to completion of the CNF partial termination;
transmitting, by the one or more processors (205), to a Physical Virtual Inventory Manager (PVIM) (505), an inventory management request to manage an inventory database pertaining to one or more resources in response to completion of the CNF partial termination; and
updating, by the one or more processors (205), the CNF partial termination status at a Release Management Repository (RMR) (515).

2. The method (600) as claimed in claim 1, wherein the CNF partial termination request is transmitted to the orchestrator adaptor (410) in response to receiving by the one or more processors (205), the CNF partial termination request from a user via a User Interface (UI) (215) module of a User Equipment (UE) (110).

3. The method (600) as claimed in claim 1, wherein the response from the orchestrator adaptor (410) pertains to completion of the CNF partial termination which includes at least one of,
termination of all running plurality of Container Network Function Components (CNFCs), or
termination of at least one selected CNFC from the plurality of CNFCs based on the CNF partial termination request.

4. The method (600) as claimed in claim 1, wherein the step of transmitting, by the one or more processors (205), the CNF partial termination request to the orchestrator adaptor (410) further includes the steps of:
transmitting, by the one or more processors (205), from the orchestrator adaptor (410), the CNF partial termination request to a host (510) to partially terminate the CNF; and
receiving, by the one or more processors (205), at the orchestrator adaptor (410), from the host (510), a status of the CNF partial termination based on transmitting the CNF partial termination request.

5. The method (600) as claimed in claim 1, wherein managing the inventory database based on the inventory management request to the PVIM (505) includes at least one of, release the one or resources which are currently utilized in response to completion of the CNF partial termination and updating the inventory database thereof.

6. The method (600) as claimed in claim 1, wherein the one or more processors (205) is configured to enable an asynchronized event-based method for utilizing an interface.

7. The method (600) as claimed in claim 1, wherein the method (600) further comprising the step of:
in a high availability mode, engaging, by the one or more processors (205), a next available orchestrator adaptor (410) instance in a high availability mode during processing the CNF partial termination request, wherein the one or more processors (205) engages the next available orchestrator adaptor (410) instance when a current orchestrator adaptor (410) instance is down.

8. The method (600) as claimed in claim 1, wherein the step of, updating, by the one or more processors (205), the CNF partial termination status at a Release Management Repository (RMR) (515), includes the steps of:
transmitting, by the one or more processors (205), updated CNF partial termination status to the RMR (515); and
receiving, by the one or more processors (205), an acknowledgement from the RMR (515) pertaining to updating of the CNF partial termination in response to the transmitted CNF partial termination status.

9. The method (600) as claimed in claim 6, wherein the interface is an CM_OA (420) between a Container Network Function Lifecycle Manager (CNFLM) (405) and the orchestrator adaptor (410).

10. The method (600) as claimed in claim 2, wherein the one or more processors (205) receives a partial termination acknowledgement from the User Interface (UI) (215) via the interface.

11. A User Equipment (UE) (110), comprising:
one or more primary processors (305) communicatively coupled to the one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (110) to:
transmit, a CNF partial termination request to the one or more processors pertaining to a CNF partial termination, and
wherein the one or more processors is configured to perform the steps as claimed in claim 1.

12. A system (120) for partially terminating a Container Network Function (CNF), the system (120) comprising:

a transmitting unit (225), configured to, transmit, a CNF partial termination request to an orchestrator adaptor (410);
a receiving unit (230), configured to, receive, a response from the orchestrator adaptor (410) pertaining to completion of the CNF partial termination;
the transmitting unit (225), configured to, transmit, to a Physical Virtual Inventory Manager (PVIM) (505), an inventory management request to manage an inventory database pertaining to one or more resources in response to completion of the CNF partial termination; and
an updating unit (235), configured to, update, the CNF partial termination status at a Release Management Repository (RMR) (515).

13. The system (120) as claimed in claim 12, wherein the CNF partial termination request is transmitted to the orchestrator adaptor (410) in response to receiving by the receiving unit (230), the CNF partial termination request from a user via a User Interface (UI) (215) module of a User Equipment (UE) (110).

14. The system (120) as claimed in claim 12, wherein the response from the orchestrator adaptor (410) pertains to completion of the CNF partial termination which includes at least one of,
termination of all running plurality of Container Network Function Components (CNFCs), or
termination of at least one selected CNFC from the plurality of CNFCs based on the CNF partial termination request.

15. The system (120) as claimed in claim 12, wherein subsequent to transmission of the CNF partial termination request from the transmitting unit (225) to the orchestrator adaptor, the transmitting unit is further configured to:
transmit, the CNF partial termination request to a host (510) to partially terminate the CNF; and
receive by the receiving unit (230), from the host (510), a status of the CNF partial termination.

16. The system (120) as claimed in claim 12, wherein managing the inventory database based on the inventory management request to the PVIM (505) includes at least one of, release the one or resources which are currently utilized in response to completion of the CNF partial termination and updating the inventory database thereof.

17. The system (120) as claimed in claim 11, wherein the system is configured to enable an asynchronized event-based method for utilizing an interface.

18. The system (120) as claimed in claim 12, wherein an High-Availability unit (HA) (240), is configured to, engage, a next available orchestrator adaptor instance in a high availability mode during processing the CNF partial termination request, wherein the HA unit (240) engages the next available orchestrator adaptor (410) instance when a current orchestrator adaptor (410) instance is down.

19. The system (120) as claimed in claim 12, wherein the updating unit updates the CNF partial termination status at a Release Management Repository (RMR) (515), by:
transmitting, updated CNF partial termination status to the RMR (515); and
receiving, an acknowledgement from the RMR (515) pertaining to updating the CNF partial termination in response to the transmitted CNF partial termination status.

20. The system (120) as claimed in claim 17, wherein the interface is an CM_OA (420) between a Container Network Function Lifecycle Manager CNFLM (405) and the orchestrator adaptor (410).

21. The system (120) as claimed in claim 12, wherein the receiving unit receives a partial termination acknowledgement from the User Interface (UI) (215) via the interface.