Method and system for managing a container orchestrator service unit in a network environment

Abstract

The present disclosure relates to a method [400] and a system [300] for managing a container orchestrator service unit [308] in a network environment The method [400] comprises receiving, by a transceiver unit [304], at an operation and management (OAM) unit [302], a request for an operation from at least a container orchestrator service (COS) unit [308], wherein the request comprises a set of details related to at least the COS unit [308]. Further, the method comprises storing, by a storing unit [306] connected at least to the transceiver unit [304], at a database [310], the set of details. Furthermore, the method comprises broadcasting, by the transceiver unit [304] from the OAM unit [302], the set of details related to at least the COS unit [308] to one or more service units [320] connected to the OAM unit [302].

Description

METHOD AND SYSTEM FOR MANAGING A CONTAINER ORCHESTRATOR SERVICE UNIT IN A NETWORK ENVIRONMENTFIELD OF DISCLOSURE

[0001] Embodiment of the present disclosure generally relates to field of wireless communication systems. More particularly, the present disclosure may relate to method and system for managing a container orchestrator service unit in a network environment.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. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] A network function virtualization (NFV) software defined networking (SDN) server acts as a single server / platform to manage all the virtual network functions (VNFs) and cloudnative network functions (CNFs) deployed in the network. The NFV SDN server is completely based on micro service architecture and is highly scalable and will be able to handle hundreds ofNFV. The NFV SDN server is also event driven and is based on representational state transfer (REST) application programming interfaces (APIs).

[0005] A SA interface updates inventory for instantiation of CNF using IM interface, if CNF inventory is saved on the same interface. If the SA interface goes down (due to some reason) other servers will not be able to see the CNF inventory and communicate with CNFs. So, there is an operations and management (0AM) server which manages all the IM server instances in order to perform smooth interaction with other services. However, there does not exist an interface server by which all the operations at IM can be performed by facilitating communication between 0AM server and SA server.

[0006] Hence, in view of these and other existing limitations, there arises an imperative need to provide an efficient solution to overcome the above-mentioned and other limitations and to provide a method and a system for managing a container orchestrator service unit in a network environment.SUMMARY

[0007] 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.

[0008] An aspect of the present disclosure may relate to a method for managing a container orchestrator service (COS) unit in a network environment. The method comprises receiving, by a transceiver unit, at an operation and management (0AM) unit, a request for an operation from at least a COS unit, wherein the request comprises a set of details related to at least the COS unit. Further, the method comprises storing, by a storing unit connected at least to the transceiver unit, at a database, the set of details. Furthermore, the method comprises broadcasting, by the transceiver unit from the 0AM unit, the set of details related to at least the COS unit to one or more service units connected to the 0AM unit.

[0009] In an exemplary aspect of the present disclosure, the method further comprises transmitting, by the transceiver unit, from the 0AM unit, to at least one of the COS unit, and the one or more service units, a request for a set of fault, configuration, accounting, performance and security (FCAPS) data. Further, the method comprises receiving, by the transceiver unit, at theOAM unit, from at least one of the COS unit, and the one or more service units, the set of FCAPS data. Furthermore, the method comprises transmitting, by the transceiver unit, from the OAM unit to an element management system (EMS) unit, the received set of FCAPS data.

[0010] In an exemplary aspect of the present disclosure, the operation comprises at least one of a registration operation, a re-registration operation, and a de-registration operation.

[0011] In an exemplary aspect of the present disclosure, in response to the operation being the registration operation, the method comprises storing, by the storing unit, at the database, and in a list of active COS units, the set of details related to at least the COS unit, wherein the active COS units comprise COS units that are currently in operation. Further, the method comprises broadcasting, by the transceiver unit, from the OAM unit, the set of details related to at least the COS unit to at least a load balancer (LB) unit connected to the OAM unit.

[0012] In an exemplary aspect of the present disclosure, in response to the operation being the de-registration operation, the method comprises storing, by the storing unit, at the database, and in a list of inactive COS units, the set of details related to at least the COS unit, wherein the inactive COS units comprise COS units that are currently not in operation. Further, the method comprises broadcasting, by the transceiver unit, from the OAM unit, the set of details related to at least the COS unit to at least a load balancer (LB) unit connected to the OAM unit.

[0013] In an exemplary aspect of the present disclosure, in response to the operation being the re-registration operation, the method comprises retrieving, by the storing unit, from the database, one or more details relating to at least the COS unit being re-registered, wherein the one or more details relate at least to an identity of at least COS unit, and wherein the one or more details are retrieved from the list of inactive COS units. Further, the method comprises storing, by the storing unit, at the database, and in the list of active COS units, the set of details related to at least the COS unit being re-registered. Furthermore, the method comprises broadcasting, by the transceiver unit from the OAM unit, the set of details relating to at least the COS unit, to at least the load balancer unit.

[0014] In an exemplary aspect of the present disclosure, the COS unit and the OAM unit are communicably coupled by an interface, and wherein the interface is an SA OA interface.

[0015] In an exemplary aspect of the present disclosure, the set of details related at least the COS unit comprises at least one of an information of at least the COS unit, one or more instances of at least the COS unit, active instances of at least the COS unit, inactive instances of at least the COS unit, new instances of at least the COS unit, and an IP port address, a path, a context information of at least the COS unit, and health data of at least the COS unit.

[0016] Another aspect of the present disclosure may relate to a system for managing a container orchestrator service (COS) unit in a network environment. The system comprises a transceiver unit configured to receive, at an operation and management (0AM) unit, a request for an operation from at least a COS unit, wherein the request comprises a set of details related to at least the COS unit. Further, the system comprises a storing unit connected at least to the transceiver unit, the storing unit configured to store, at a database, the set of details related to at least the COS unit. Furthermore, the system comprises the transceiver unit configured to broadcast, from the 0AM unit, the set of details related to at least the COS unit to one or more service units connected to the 0AM unit.

[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing one or more instructions for managing a container orchestrator service (COS) unit in a network environment, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to receive, at an operation and management (0AM) unit, a request for an operation from at least a COS unit, wherein the request comprises a set of details related to at least the COS unit. Further, the executable code when executed causes a storing unit of the system to store, at a database, the set of details related to at least the COS unit. Furthermore, the executable code when executed causes the transceiver unit to broadcast, from the 0AM unit, the set of details related to at least the COS unit to one or more service units connected to the 0AM unit.OBJECTS OF THE DISCLOSURE

[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0019] It is an object of the present disclosure to provide a system and a method for managing a container orchestrator service unit in a network environment.

[0020] It is another object of the present disclosure to provide a solution that allows uninterrupted processing of data in the event an instance of SA server goes down.

[0021] It is yet another object of the present disclosure to provide a solution that enables the fault tolerance for the instance.

[0022] It is yet another object of the present disclosure to provide a solution that enables instance management.

[0023] It is yet another object of the present disclosure to provide a solution that enables alarm management.

[0024] It is yet another object of the present disclosure to provide a solution that enables counter management.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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0026] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture, in accordance with exemplary implementations of the present disclosure.

[0027] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure.

[0028] FIG. 3 illustrates an exemplary block diagram of a system for managing a container orchestrator service unit in a network environment, in accordance with exemplary implementations of the present disclosure.

[0029] FIG. 4 illustrates an exemplary method flow diagram for managing a container orchestrator service unit in a network environment, in accordance with exemplary implementations of the present disclosure.

[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED 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 may 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.

[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] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0034] 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 may 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.

[0035] 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 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.

[0036] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (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 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 or processing unit is a hardware processor.

[0037] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least oneinput means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

[0038] As used herein, “storage unit” or “memory unit” refers to a machine or computer- readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0039] As used herein “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also refer to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0040] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0041] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0042] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system for managing a container orchestrator service unit in a network environment. More particularly, the present disclosure provides a solution that allows uninterrupted processing of data in the event an instance of SA server goes down. Also, the present disclosure provides the solution enables the fault tolerance forthe instance. Further, the present disclosure provides the solution enables instance (e.g., microservice instance, docker service instances, etc.) management. Furthermore, the present disclosure provides the solution enables alarm management for the instance. Moreover, the present disclosure provides the solution that enables counter management for the instance.

[0043] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0044] Referring to FIG. 1 an exemplary block diagram representation of a management and orchestration (MANO) architecture

[0100] , in accordance with exemplary implementation of the present disclosure is illustrated. The MANO architecture

[0100] is developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of a network node(s) etc. The MANO architecture

[0100] deploys the network node(s) in the form of Virtual Network Function (VNF) and Cloud-native / Container Network Function (CNF). The system may comprise one or more components of the MANO architecture. The MANO architecture

[0100] is used to auto-instantiate the VNFs into the corresponding environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to the platform. In an implementation, the system comprises a NF V Platform Decision Analytics (NPDA)

[1096] component.

[0045] As shown in FIG. 1, the MANO architecture

[0100] comprises a user interface layer, a network function virtualization (NFV) and software defined network (SDN) design function module

[0104] , a platform foundation services module

[0106] , a platform core services module

[0108] and a platform resource adapters and utilities module

[0112] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0046] The NFV and SDN design function module

[0104] further comprises a VNF lifecycle manager (compute)

[1042] ; a VNF catalogue

[1044] ; a network services catalogue

[1046] ; a network slicing and service chaining manager

[1048] ; a physical and virtual resource manager

[1050] and a CNF lifecycle manager

[1052] , The VNF lifecycle manager (compute)

[1042] is responsible for on which server of the communication network the microservice will be instantiated. The VNF lifecycle manager (compute)

[1042] will manage the overall flow of incoming / outgoing requests during interaction with the user. The VNF lifecycle manager (compute)

[1042] is responsible for determining which sequence to be followed for executing theprocess. For e.g. in an AMF network function of the communication network (such as a 5G network), sequence for execution of processes Pl and P2 etc. The VNF catalogue

[1044] stores the metadata of all the VNFs (also CNFs in some cases). The network services catalogue

[1046] stores the information of the services that need to be run. The network slicing and service chaining manager

[1048] manages the slicing (an ordered and connected sequence of network service / network functions (NFs)) that must be applied to a specific networked data packet. The physical and virtual resource manager

[1050] stores logical and physical inventory of the VNFs. Just like the VNF lifecycle manager (compute)

[1042] , the CNF lifecycle manager

[1052] is similarly used for the CNFs lifecycle management.

[0047] The platforms foundation services module

[0106] further comprises a microservices elastic load balancer

[1062] ; an identify & access manager

[1064] ; a command line interface (CLI)

[1066] ; a central logging manager

[1068] ; and an event routing manager

[1070] , The microservices elastic load balancer

[1062] is used for maintaining the load balancing of the request for the services. The identify & access manager

[1064] is used for logging purposes. The command line interface (CLI)

[1066] is used to provide commands to execute certain processes which requires changes during the run time. The central logging manager

[1068] is responsible for keeping the logs of every services. Theses logs are generated by the MANO platform

[0100] , These logs are used for debugging purposes. The event routing manager

[1070] is responsible for routing the events i.e., the application programming interface (API) hits to the corresponding services.

[0048] The platforms core services module

[0108] further comprises NFV infrastructure monitoring manager

[1082] ; an assure manager

[1084] ; a performance manager

[1086] ; a policy execution engine

[1088] ; a capacity monitoring manager

[1090] ; a release management (mgmt.) repository

[1092] ; a configuration manager & (GCT)

[1094] ; an NFV platform decision analytics

[1096] ; a platform NoSQL DB

[1098] ; a platform schedulers and cronjobs

[1100] ; a VNF backup & upgrade manager

[1102] ; a micro service auditor

[1104] ; and a platform operations, administration and maintenance manager

[1106] , The NFV infrastructure monitoring manager

[1082] monitors the infrastructure part of the NFs. For e.g., any metrics such as CPU utilization by the VNF. The assure manager

[1084] is responsible for supervising the alarms the vendor is generating. The performance manager

[1086] is responsible for manging the performance counters. The policy execution engine (PEEGN)

[1088] is responsible for all the managing the policies. The capacity monitoring manager

[1090] is responsible for sending the request to the PEEGN

[1088] , The release management (mgmt.) repository (RMR)

[1092] is responsible for managing the releases and the images of all the vendor network node. The configuration manager& (GCT)

[1094] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA)

[1096] helps in deciding the priority of using the network resources. It is further noted that the policy execution engine (PEEGN)

[1088] , the configuration manager & (GCT)

[1094] and the (NPDA)

[1096] work together. The platform NoSQL DB

[1098] is a database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. The platform schedulers and cron jobs

[1100] schedules the task such as but not limited to triggering of an event, traverse the network graph etc. The VNF backup & upgrade manager

[1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backups on demand in case of server failure. The micro service auditor

[1104] audits the microservices. For e.g., in a hypothetical case, instances not being instantiated by the MANO architecture

[0100] using the network resources then the micro service auditor

[1104] audits and informs the same so that resources can be released for services running in the MANO architecture

[0100] , thereby assuring the services only run on the MANO platform

[0100] , The platform operations, administration and maintenance manager

[1106] is used for newer instances that are spawning.

[0049] The platform resource adapters and utilities module

[0112] further comprises a platform external API adaptor and gateway

[1122] , a generic decoder and indexer (XML, CSV, JSON)

[1124] , a docker service adaptor

[1126] , an API adapter

[1128] , and a NFV gateway

[1130] , The platform external API adaptor and gateway

[1122] may be responsible for handling the external services (to the MANO platform

[0100] ) that requires the network resources. The generic decoder and indexer (XML, CSV, JSON)

[1124] gets directly the data of the vendor system in the XML, CSV, JSON format. The docker service adaptor

[1126] may be the interface provided between the telecom cloud and the MANO architecture

[0100] for communication. The API adapter

[1128] may be used to connect with the virtual machines (VMs). The NFV gateway

[1130] may be responsible for providing the path to each services going to / incoming from the MANO architecture

[0100] ,

[0050] The docker service adapter (DSA)

[1126] is a microservices-based system designed to deploy and manage Container Network Functions (CNFs) and their components (CNFCs) across Docker nodes. The DSA

[1126] offers REST endpoints for key operations, including uploading container images to a Docker registry, terminating CNFC instances, and creating Docker volumes and networks. CNFs, which are network functions packaged as containers, may consist of multiple CNFCs. The DSA

[1126] facilitates the deployment, configuration, and management of these components by interacting with Docker's API, ensuring proper setup and scalability within acontainerized environment. This approach provides a modular and flexible framework for handling network functions in a virtualized network setup.

[0051] Referring to FIG. 2 an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented, in accordance with exemplary implementation of the present disclosure is illustrated. In an implementation, the computing device

[0200] may implement a method for handling an overload condition in a network by utilising a system

[0200] , In another implementation, the computing device

[0200] itself implements the method for handling an overload condition in a network using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0052] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general- purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0053] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and forcontrolling cursor movement on the display

[0212] , The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0054] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0055] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0056] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , a host

[0224] , the local network

[0222] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0057] Referring to FIG. 3 an exemplary block diagram of a system for managing a container orchestrator service unit in a network environment, in accordance with exemplary implementation of the present disclosure is illustrated. The system comprises at least one operation and management (0AM) unit

[0302] , and a container orchestrator service (COS) unit

[0308] , The system

[0300] further comprises an interface

[0312] configured to facilitate communication between the 0AM unit

[0302] , and the COS unit

[0308] , The system

[0300] further comprises a database

[0310] communicably coupled at least to the 0AM unit

[0302] , The COS unit

[0308] further comprises one or more instances [308-1, 308-2. . ,308-N] associated with it. The COS unit

[0308] is further operatively coupled to one or more service units

[0320] in the network environment. The one or more service units

[0320] may be microservices such as those described in FIG. 1. The system

[0300] further comprises at least one transceiver unit

[0304] and at least one storing unit

[0306] , The at least one transceiver unit

[0304] and the at least one storing unit

[0306] are further connected to at least the 0AM unit

[0302] , and the COS unit

[0308] , In an embodiment, the storing unit

[0306] is further connected to the database

[0310] , Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG. 3 all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may reside in a server or the network entity or the system

[0300] may be in communication with the network entity to implement the features as disclosed in the present disclosure.

[0058] The system

[0300] is configured for managing a container orchestrator service (COS) unit

[0308] in a network environment with the help of the interconnection between the components / units of the system

[0300] , In one exemplary implementation the COS unit

[0308] may be a Docker Service Adapter (DSA). Further in another exemplary implementation the COS unit

[0308] may be an interface that may allow the integration of docker based service and one or more external systems. Furthermore, the docker based services may include an application or a set of microservices that may be deployed to run inside the docker container. Moreover, COS unit

[0308] may manage the deployment and operation of the containerized application and the set of microservices. Also, the microservice is a small, loosely coupled distributed service and each microservice is designed to perform a specific function. Further, each microservice may be developed and deployed independently. Further, the microservice breaks a service into small and manageable components of services.

[0059] In operation, the transceiver unit

[0304] may receive a request for an operation from at least a COS unit

[0308] at the 0AM unit

[0302] , The request comprises a set of details related to at least the COS unit

[0308] , Further, the operation may comprise at least one of a registration operation, a re-registration operation, and a de-registration operation. Further, the 0AM unit

[0302] may keep track of health of the COS unit

[0308] and the operations performed by the COS unit

[0308] , Furthermore, to keep the track of the health of the COS unit

[0308] , the COS unit

[0308] need to be registered on the 0AM unit

[0302] , Furthermore, the COS unit

[0308] and the 0AM unit

[0302] are communicably coupled by an interface

[0312] , Also, the interface

[0312] is an S A O A interface.

[0060] In an embodiment, the interface

[0312] is configured to facilitate exchange of information using hypertext transfer protocol (http) rest application programming interface (API). In an embodiment, the http rest API is used in conjunction with J SON and / or XML communication media.

[0061] In another embodiment, the interface

[0312] is configured to facilitate exchange of information by establishing a web-socket connection between the 0AM unit

[0302] , and the COS unit

[0308] , A web-socket connection may involve establishing a persistent connectivity between the 0AM unit

[0302] , and the COS unit

[0308] , An example of the web-socket based communication includes, without limitation, a transmission control protocol (TCP) connection. In such a connection, information, such as operational status, health, etc. of different components may be exchanged through the interface using a ping-pong based communication.

[0062] Continuing further, the set of details related to at least the COS unit

[0308] comprises at least one of an information of at least the COS unit

[0308] , one or more instances of at least the COS unit

[0308] , one or more active instances of at least the COS unit

[0308] , one or more inactive instances of at least the COS unit

[0308] , one or more new instances of at least the COS unit

[0308] , and an Internet Protocol (IP) address, port address, a path, a context information of at least the COS unit

[0308] , and the health data of at least the COS unit

[0308] , Furthermore, the storing unit

[0306] may store, at a database

[0310] , the set of details related to at least the COS unit

[0308] ,

[0063] Furthermore, once the set of details related to at least the COS unit

[0308] is stored in the database

[0310] , the transceiver unit

[0304] may broadcast the set of details related to at least the COS unit

[0308] to one or more service units

[0320] connected to the 0AM unit

[0302] , Also, in one exemplary implementation, the one or more service units

[0320] may be one or more microservices connected to the 0AM unit

[0302] , The transceiver unit

[0304] may send the set of details related toat least the COS unit

[0308] to the one or more service units

[0320] connected to the 0AM unit

[0302] by broadcasting the set of details related to at least the COS unit

[0308] , Further, the transceiver unit

[0302] may also broadcast the set of details to a load balancer. The transceiver unit

[0304] , by broadcasting the set of details, may notify the one or more service units

[0320] regarding the registration, the de-regi strati on or the re-registration of the COS unit

[0308] at the 0AM unit

[0302] ,

[0064] Continuing further, the registration operation may relate to registration of the COS unit

[0308] at the 0AM unit

[0302] , The 0AM unit

[0302] may receive a http request from the COS unit

[0308] , The http request may be a request, received by the transceiver unit

[0304] at the 0AM unit

[0302] , to register the COS unit

[0308] at the 0AM

[0302] , Further, the request may include the set details such as, but not limited to, the IP address, port address, capabilities of the COS unit

[0308] , etc. Once the request for registration is received by the 0AM unit

[0302] , the 0AM unit

[0302] may process the request and based on the processing, the 0AM unit may register the COS unit

[0308] ,

[0065] Continuing further, in response to the registration operation, the storing unit

[0306] may store, in a list of active COS units at the database

[0310] , the set of details related to at least the COS unit

[0308] , The active COS units comprise COS units and / instances

[0308] that are currently in operation.

[0066] Once the storing unit

[0306] stores, in the list of active COS units

[0308] at the database

[0310] , the set of details related to the registered COS unit

[0308] , the transceiver unit

[0304] may broadcast the set of details related to at least the COS unit

[0308] to at least a load balancer unit

[0322] connected to the 0AM unit

[0302] , The transceiver unit

[0304] , by broadcasting the set of details, may notify the load balancer unit

[0322] regarding the registration of the COS unit

[0308] at the 0AM unit

[0302] , In an embodiment, the term “load balancer” may refer to a router, a switch, or a dedicated service unit that acts to distribute network or application traffic across a number of network elements.

[0067] Continuing further, the load balancer unit

[0322] , upon receiving the notification related to the registration of the COS unit

[0308] , may update its routing table based on the details of the newly registered COS unit

[0308] , The load balancer unit

[0322] may also update the information related to the health and the availability of the new service unit in the network environment. Furthermore, the load balancer unit

[0322] based on the updated information distributes the traffic among the plurality of the service units

[0320] to maintain the optimal load balance on each serviceunit from the plurality of the service units

[0320] in the network environment, based on the details of the newly registered COS unit

[0308] ,

[0068] Furthermore, the de-regi strati on operation may relate to removal of the COS unit

[0308] from the list of active COS units

[0308] at the database

[0310] , The removed COS unit

[0308] may be stored, by the storing unit

[0306] , in a list of inactive COS units

[0308] at the database

[0310] , The inactive COS units

[0308] comprise COS units

[0308] that are currently not in operation. The COS units

[0308] may become inactive may be due to hardware malfunction, software crash or any other like reason.

[0069] Thereafter, the transceiver unit

[0304] may broadcast, from the 0AM unit

[0302] , the set of details related to at least the COS unit

[0308] to at least the load balancer unit

[0322] connected to the 0AM unit

[0302] , The load balancer unit

[0322] may update its routing table based on the details of the de-registered COS unit

[0308] , The load balancer unit

[0322] based on the updated information may stop routing traffic on the de-registered COS unit

[0308] , Also, it is important to de-register the inactive COS unit

[0308] to maintain the proper distribution of resources and operations of the other plurality of service units

[0320] in the network environment.

[0070] Moreover, the re-registration operation may relate to retrieval of the COS unit

[0308] from the list of inactive COS units

[0308] at the database

[0310] , The storing unit

[0306] , may retrieve from the database

[0310] , one or more details relating to at least the COS unit

[0308] being reregistered. The one or more details relate at least to an identity of at least COS unit

[0308] , The one or more details are retrieved from the list of inactive COS units

[0308] ,

[0071] In an exemplary implementation, the identifier may be a unique identity of the COS unit

[0308] such as, but not limited to, IP address of the COS unit

[0308] , Further, the identifier may be created in the database

[0310] while entering the COS unit

[0308] in the list of the active COS units

[0308] , The other details may be received, by the transceiver unit

[0304] at the 0AM unit

[0302] , along with the registration request by the COS unit

[0308] ,

[0072] Continuing further, in the re-registration operation of the COS unit

[0308] , the COS unit

[0308] already registered and stored in the list of the active COS units

[0308] at the database

[0310] along with an identifier and other details, may be retrieved from the list of the inactive COS units

[0308] ,

[0073] Continuing further, the re-registration operation may also include restoration of the COS unit

[0308] to the list of active COS units

[0308] at the database

[0310] , The storing unit

[0306] may store, at the database

[0310] , and in the list of active COS units

[0308] , the set of details related to at least the COS unit

[0308] being re-registered Further, in the re-registration operation of the COS unit

[0308] , the COS unit

[0308] already registered and stored in the list of the active COS units

[0308] at the database

[0310] along with an identifier and other details, may be restored to the list of the active COS units

[0308] , Furthermore, in the re-registration of the COS unit

[0308] the details related to the COS unit

[0308] may be updated and no new identifier may be created for the same.

[0074] Continuing further, the transceiver unit

[0304] may broadcast, from the 0AM unit

[0302] , the set of details relating to at least the COS unit

[0308] , to at least the load balancer unit

[0322] connected to the 0AM unit

[0302] , In the broadcast the transceiver unit

[0304] may send the details along with the identifier of the re-registered COS unit

[0308] to the load balancer unit

[0322] to update its routing table based on the details of the re-registered COS unit

[0308] , The load balancer unit

[0322] based on the updated information may restart routing the traffic on the reregistered COS unit

[0308] ,

[0075] Furthermore, the transceiver unit

[0304] may transmit, from the 0AM unit

[0302] , to at least one of the COS unit

[0308] , and the one or more service units

[0320] , a request for a set of fault, configuration, accounting, performance and security (FCAPS) data. The set of FCAPS data may include data related to management of all the counters and alarms created at the platform core services module

[0108] of the MANO architecture

[0100] , Next, the transceiver unit

[0304] may receive, at the 0AM unit

[0302] , from at least the COS unit

[0308] , and the one or more service units

[0320] , the set of FCAPS data. Thereafter, the transceiver unit

[0304] may transmit, from the 0AM unit

[0302] , to an element management system (EMS) unit, the received set of FCAPS data. The EMS unit may manage one or more service units

[0320] in the network environment. The EMS unit may provide an interface to control, monitor, and manage one or more service units

[0320] in the network environment.

[0076] Referring to FIG. 4 an exemplary flow diagram of a method

[0400] for managing a COS unit

[0308] in a network environment, in accordance with exemplary implementation of the present disclosure is illustrated. In an implementation the method

[0400] is performed by the system

[0300] , Also, as shown in FIG. 4, the method

[0400] initiates at step

[0402] ,

[0077] At step

[0404] , the method

[0400] comprises receiving, by a transceiver unit

[0304] , at an operation and management (0AM) unit

[0302] , a request for an operation from at least a COS unit

[0308] , The request comprises a set of details related to at least the COS unit

[0308] , Further, the operation may comprise at least one of a registration operation, a re-registration operation, and a de-registration operation. Further, the 0AM unit

[0302] may keep track of health of the COS unit

[0308] and the operations performed by the COS unit

[0308] , Furthermore, to keep the track of the health of the COS unit

[0308] , the COS unit

[0308] need to be registered on the 0AM unit

[0302] , Furthermore, the COS unit

[0308] and the 0AM unit

[0302] are communicably coupled by an interface. Also, the interface is an SA OA interface. Moreover, the interface are self-contained software modules that are reusable independently of each other and may be thought of as micro services.

[0078] Next, at step

[0406] , the method

[0400] comprises storing, by a storing unit

[0306] connected at least to the transceiver unit

[0304] , at a database

[0310] , the set of details Further, the set of details related to at least the COS unit

[0308] comprises at least one of an information of at least the COS unit

[0308] , one or more instances of at least the COS unit

[0308] , one or more active instances of at least the COS unit

[0308] , one or more inactive instances of at least the COS unit

[0308] , one or more new instances of at least the COS unit

[0308] , and an Internet Protocol (IP) address, port address, a path, a context information of at least the COS unit

[0308] , and the health data of at least the COS unit

[0308] ,

[0079] Furthermore, at step

[0408] , the method

[0400] comprises broadcasting, by the transceiver unit

[0304] from the 0AM unit

[0302] , the set of details related to at least the COS unit

[0308] to one or more service units

[0320] connected to the 0AM unit

[0302] , Also, in one exemplary implementation, the one or more service units

[0320] may be one or more microservices connected to the 0AM unit

[0302] , The transceiver unit

[0304] may send the set of details related to at least the COS unit

[0308] to the one or more service units

[0320] / microservices connected to the 0AM unit

[0302] by broadcasting the set of details related to at least the container orchestrator service unit. Further, the transceiver unit

[0302] may also broadcast the set of details to a load balancer. The transceiver unit

[0304] , by broadcasting the set of details, may notify the one or more service units

[0320] regarding the registration, the de-registration or the re-registration of the container orchestrator service unit at the 0AM unit

[0302] ,

[0080] Continuing further, the registration operation may relate to registration of the COS unit

[0308] at the 0AM unit

[0302] , The 0AM unit

[0302] may receive a http request from the COS unit

[0308] , The http request may be a request, received by the transceiver unit

[0304] at the OAM unit

[0302] , to register the COS unit

[0308] at the OAM

[0302] , Further, the request may include the set details such as, but not limited to, the IP address, port address, capabilities of the COS unit

[0308] , etc. Once the request for registration is received by the OAM unit

[0302] , the OAM unit

[0302] may process the request and based on the processing, the OAM unit may register the COS unit

[0308] ,

[0081] Continuing further, in response to the registration operation, the storing unit

[0306] may store, in a list of active COS units

[0308] at the database

[0310] , the set of details related to at least the COS unit

[0308] , The active COS units

[0308] comprise COS units

[0308] that are currently in operation.

[0082] Once the storing unit

[0306] stores, in the list of active COS units

[0308] at the database

[0310] , the set of details related to the registered COS unit

[0308] , the transceiver unit

[0304] may broadcast the set of details related to at least the COS unit

[0308] to at least a load balancer unit

[0322] connected to the OAM unit

[0302] , The transceiver unit

[0304] , by broadcasting the set of details, may notify the load balancer regarding the registration of the COS unit

[0308] at the OAM unit

[0302] ,

[0083] Continuing further, the load balancer unit

[0322] , upon receiving the notification related to the registration of the COS unit

[0308] , may update its routing table based on the details of the newly registered COS unit

[0308] , The load balance unit may also update the information related to the health and the availability of the new service unit in the network environment. Furthermore, the load balancer unit

[0322] based on the updated information distributes the traffic among the plurality of the service units

[0320] to maintain the optimal load balance on each service unit from the plurality of the service units

[0320] in the network environment, based on the details of the newly registered COS unit

[0308] ,

[0084] Furthermore, the de-regi strati on operation may relate to removal of the COS unit

[0308] from the list of active COS units

[0308] at the database

[0310] , The removed COS unit

[0308] may be stored, by the storing unit

[0306] , in a list of inactive COS units

[0308] at the database

[0310] , The inactive COS units

[0308] comprise COS units

[0308] that are currently not in operation. The COS units

[0308] may become inactive may be due to hardware malfunction, software crash or any other like reason.

[0085] Thereafter, the transceiver unit

[0304] may broadcast, from the 0AM unit

[0302] , the set of details related to at least the COS unit

[0308] to at least the load balancer unit

[0322] connected to the 0AM unit

[0302] , The load balancer unit

[0322] may update its routing table based on the details of the de-registered COS unit

[0308] , The load balancer unit

[0322] based on the updated information may stop routing traffic on the de-registered COS unit

[0308] , Also, it is important to de-register the inactive COS unit

[0308] to maintain the proper distribution of resources and operations of the other plurality of service units

[0320] in the network environment.

[0086] Moreover, the re-registration operation may relate to retrieval of the COS unit

[0308] from the list of inactive COS units

[0308] at the database

[0310] , The storing unit

[0306] , may retrieve from the database

[0310] , one or more details relating to at least the COS unit

[0308] being reregistered. The one or more details relate at least to an identity of at least COS unit

[0308] , The one or more details are retrieved from the list of inactive COS units

[0308] ,

[0087] In an exemplary implementation, the identifier may be a unique identity of the COS unit

[0308] such as, but not limited to, IP address of the COS unit

[0308] , Further, the identifier may be created in the database

[0310] while entering the COS unit

[0308] in the list of the active COS units

[0308] , The other details may be received, by the transceiver unit

[0304] at the 0AM unit

[0302] , along with the registration request by the COS unit

[0308] ,

[0088] Continuing further, in the re-registration operation of the COS unit

[0308] , the COS unit

[0308] already registered and stored in the list of the active COS units

[0308] at the database

[0310] along with an identifier and other details, may be retrieved from the list of the inactive COS units

[0308] ,

[0089] Continuing further, the re-registration operation may also include restoration of the COS unit

[0308] to the list of active COS units

[0308] at the database

[0310] , The storing unit

[0306] may store, at the database

[0310] , and in the list of active COS units

[0308] , the set of details related to at least the COS unit

[0308] being re-registered Further, in the re-registration operation of the COS unit

[0308] , the COS unit

[0308] already registered and stored in the list of the active COS units

[0308] at the database

[0310] along with an identifier and other details, may be restored to the list of the active COS units

[0308] , Furthermore, in the re-registration of the COS unit

[0308] the details related to the COS unit

[0308] may be updated and no new identifier may be created for the same.

[0090] Continuing further, the transceiver unit

[0304] may broadcast, from the 0AM unit

[0302] , the set of details relating to at least the COS unit

[0308] , to at least the load balancer unit

[0322] connected to the 0AM unit

[0302] , In the broadcast the transceiver unit

[0304] may send the details along with the identifier of the re-registered COS unit

[0308] to the load balancer unit

[0322] to update its routing table based on the details of the re-registered COS unit

[0308] , The load balancer unit

[0322] based on the updated information may restart routing the traffic on the reregistered COS unit

[0308] ,

[0091] Furthermore, the transceiver unit

[0304] may transmit, from the 0AM unit

[0302] , to at least one of the COS unit

[0308] , and the one or more service units

[0320] , a request for a set of fault, configuration, accounting, performance and security (FCAPS) data. The set of FCAPS data may include data related to management of all the counters and alarms created at the platform core services module

[0108] of the MANO architecture

[0100] , Next, the transceiver unit

[0304] may receive, at the 0AM unit

[0302] , from at least the COS unit

[0308] , and the one or more service units

[0320] , the set of FCAPS data. Thereafter, the transceiver unit

[0304] may transmit, from the 0AM unit

[0302] , to an element management system (EMS) unit, the received set of FCAPS data. The EMS unit may manage one or more service units

[0320] in the network environment. The EMS unit may provide an interface to control, monitor, and manage one or more service units

[0320] in the network environment.

[0092] Thereafter, the method

[0400] , terminates at step

[0410] ,

[0093] The present disclosure further relates to a non-transitory computer readable storage medium storing one or more instructions for managing a COS unit

[0308] in a network environment, the instructions include executable code which, when executed by one or more units of a system

[0300] , causes a transceiver unit

[0304] of the system

[0300] to receive, at an operation and management (0AM) unit

[0302] , a request for an operation from at least a COS unit

[0308] , wherein the request comprises a set of details related to at least the COS unit

[0308] , Further, the executable code when executed causes a storing unit

[0306] of the system

[0300] to store, at a database

[0310] , the set of details related to at least the COS unit

[0308] , Furthermore, the executable code when executed causes the transceiver unit

[0304] to broadcast, from the 0AM unit

[0302] , the set of details related to at least the COS unit

[0308] to one or more service units

[0320] connected to the 0AM unit

[0302] ,

[0094] As is evident from the above, the present disclosure provides a technically advanced solution for managing a COS unit

[0308] in a network environment. More particularly, the present solution allows uninterrupted processing of data in the event an instance of SA server goes down. Also, the present solution enables the fault tolerance for the instance. Further, the present solution enables instance (e.g., microservice instance, COS unit

[0308] instances, etc.) management. Furthermore, the present solution enables alarm management for the instance. Moreover, the present solution enables counter management for the instance.

[0095] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations 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.

[0096] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various 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. 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.

Claims

We Claim:

1. A method [400] for managing a container orchestrator service unit [308] in a network environment, the method [400] comprising:- receiving, by a transceiver unit [304], at an operation and management (0AM) unit [302], a request for an operation from at least a container orchestrator service (COS) unit [308], wherein the request comprises a set of details related to at least the COS unit [308];- storing, by a storing unit [306] connected at least to the transceiver unit [304], at a database [310], the set of details; and- broadcasting, by the transceiver unit [304] from the 0AM unit [302], the set of details related to at least the COS unit [308] to one or more service units [320] connected to the 0AM unit [302],2. The method [400] as claimed in claim 1, wherein the method [400] comprises:- transmitting, by the transceiver unit [304], from the 0AM unit [302], to at least one of the COS unit [308], and the one or more service units [320], a request for a set of fault, configuration, accounting, performance and security (FCAPS) data;- receiving, by the transceiver unit [304], at the 0AM unit [302], from at least one of the COS unit [308], and the one or more service units [320], the set of FCAPS data; and- transmitting, by the transceiver unit [304], from the 0AM unit [302] to an element management system (EMS) unit, the received set of FCAPS data.

3. The method [400] as claimed in claim 1, wherein the operation comprises at least one of a registration operation, a re-registration operation, and a de-registration operation.

4. The method [400] as claimed in claim 3, wherein, in response to the operation being the registration operation, the method [400] comprises:- storing, by the storing unit [306], at the database [310], and in a list of active COS units [308], the set of details related to at least the COS unit [308], wherein the active COS units [308] comprise COS units [308] that are currently in operation; and- broadcasting, by the transceiver unit [304], from the 0AM unit [302], the set of details related to at least the COS unit [308] to at least a load balancer unit [322] connected to the 0AM unit [302],5. The method [400] as claimed in claim 3, wherein, in response to the operation being the de-registration operation, the method [400] comprises:- storing, by the storing unit [306], at the database [310], and in a list of inactive COS units [308], the set of details related to at least the COS unit [308], wherein the inactive COS units [308] comprise COS units [308] that are currently not in operation; and- broadcasting, by the transceiver unit [304], from the 0AM unit [302], the set of details related to at least the COS unit [308] to at least a load balancer unit [322] connected to the 0AM unit [302],6. The method [400] as claimed in claim 5, wherein, in response to the operation being the re-registration operation, the method [400] comprises:- retrieving, by the storing unit [306], from the database [310], one or more details relating to at least the COS unit [308] being re-registered, wherein the one or more details relate at least to an identity of at least COS unit [308], and wherein the one or more details are retrieved from the list of inactive COS units [308];- storing, by the storing unit [306], at the database [310], and in the list of active COS units [308], the set of details related to at least the COS unit [308] being re-registered; and- broadcasting, by the transceiver unit [304] from the 0AM unit [302], the set of details relating to at least the COS unit [308], to at least the load balancer unit [322],7. The method [400] as claimed in claim 1, wherein the COS unit [308] and the 0AM unit [302] are communicably coupled by an interface, and wherein the interface is an SA OA interface.

8. The method [400] as claimed in claim 1, wherein the set of details related at least the COS unit [308] comprises at least one of an information of at least the COS unit [308], one or more instances of at least the COS unit [308], active instances of at least the COS unit [308], inactive instances of at least the COS unit [308], new instances of at least the COS unit [308], and an IP port address, a path, a context information of at least the COS unit [308], and health data of at least the COS unit [308],9. A system [300] for managing a container orchestrator service unit [308] in a network environment, the system [300] comprising:- a transceiver unit [304] configured to receive, at an operation and management (0AM) unit [302], a request for an operation from at least a container orchestrator service (COS) unit [308], wherein the request comprises a set of details related to at least the COS unit [308];- a storing unit [306] connected at least to the transceiver unit [304], the storing unit [306] is configured to store, at a database [310], the set of details related to at least the COS unit [308]; and- the transceiver unit [304] configured to broadcast, from the 0AM unit [302], the set of details related to at least the COS unit [308] to one or more service units [320] connected to the 0AM unit [302],10. The system [300] as claimed in claim 9, wherein the transceiver unit [304] is configured to:- transmit, from the 0AM unit [302], to at least one of the COS unit [308], and the one or more service units [320], a request for a set of fault, configuration, accounting, performance and security (FCAPS) data;- receive, at the 0AM unit [302], from at least the COS unit [308], and the one or more service units [320], the set of FCAPS data; and- transmit, from the 0AM unit [302] to an element management system (EMS) unit, the received set of FCAPS data.

11. The system [300] as claimed in claim 9, wherein the operation comprises at least one of a registration operation, a re-registration operation, and a de-registration operation.

12. The system [300] as claimed in claim 11, wherein, in response to the operation being the registration operation:- the storing unit [306] is configured to store, at the database [310], and in a list of active COS units [308], the set of details related to at least the COS unit [308], wherein the active COS units [308] comprise COS units [308] that are currently in operation; and- the transceiver unit [304] is configured to broadcast, from the 0AM unit [302], the set of details related to at least the COS unit [308] to at least a load balancer unit [322] connected to the 0AM unit [302],13. The system [300] as claimed in claim 11, wherein, in response to the operation being the de-registration operation:- the storing unit [306] is configured to store, at the database [310], and in a list of inactive COS units [308], the set of details related to at least the COS unit [308], wherein the inactive COS units [308] comprise COS units [308] that are currently not in operation; and- the transceiver unit [304] is configured to broadcast, from the 0AM unit [302], the set of details related to at least the COS unit [308] to at least a load balancer unit [322] connected to the 0AM unit [302],14. The system [300] as claimed in claim 13, wherein, in response to the operation being the re-registration operation:- the storing unit [306] is configured to: o retrieve, from the database [310], one or more details relating to at least the COS unit [308] being re-registered, wherein the one or more details relate at least to an identity of at least COS unit [308], and wherein the one or more details are retrieved from the list of inactive COS units [308]; and o store, at the database [310], and in the list of active COS units [308], the set of details related to at least the COS unit [308] being re-registered; and- the transceiver unit [304] is configured to broadcast, from the 0AM unit [302], the set of details relating to at least the COS unit [308], to at least the load balancer unit [322],15. The system [300] as claimed in claim 9, wherein the COS unit [308] and the 0AM unit are communicably coupled by an interface, and wherein the interface is an SA OA interface.

16. The system [300] as claimed in claim 9, wherein the set of details related to at least the COS unit [308] comprises at least one of an information of at least the COS unit [308], one or more instances of at least the COS unit [308], active instances of at least the COS unit [308], inactive instances of at least the COS unit [308], new instances of at least the COS unit [308], and an IP port address, a path, a context information of at least the COS unit [308], and health data of at least the COS unit [308],17. A non-transitory computer readable storage medium storing one or more instructions for managing a container orchestrator service unit [308] in a network environment, the instructions comprising executable code which, when executed by one or more units of a system, causes:- a transceiver unit [304] to receive, at an operation and management (0AM) unit [302], a request for an operation from at least a container orchestrator service (COS) unit [308], wherein the request comprises a set of details related to at least the COS unit [308],- a storing unit [306] to store, at a database [310], the set of details related to at least the COS unit [308],- the transceiver unit [304] to broadcast, from the 0AM unit [302], the set of details related to at least the COS unit [308] to one or more service units [320] connected to the 0AM unit [302],

Images