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 TO MANAGE ONE OR MORE OPERATIONS AT AN INVENTORY
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 the field of communication network management and more particularly relates to managing one or more operations at an inventory.
BACKGROUND OF THE INVENTION
[0002] With the increase in number of users, a communication network is rapidly evolving to accommodate the surge of request commands and improve user experience. A communication network comprises of many network elements which are configured to operate in specific manners to improve credibility of the communication network. The network incorporates inventories to safe-keep resources required to perform request processing. Inventory Management (IM) service maintains the virtual inventory and limited physical inventory. It maintains the relation between physical and virtual resources with respect to overlay to manage storage memory allocation. Also, it describes physical and virtual resources in view of different attributes using updates from external micro-service. Thus, data accuracy of the inventory management service is dependent upon the micro-services which create, update, delete these resources and at the same time update these events with IM. Other services can query IM relations, attributes etc. using Query APIs (application programming interface) provided by IM. However, changing configuration of IM using these micro-service causes disruption of service known as downtime. Similarly, updating or registering or de-registering a network service may also cause service disruption and failure of current requests which are being processed.
[0003] Presently, there is no mechanism available to perform required changes in various network services like inventory management where creating, deleting or modifying resources in inventory is possible without causing any downtime or disruption of service; or registering a new service that causes shut-down of the network elements for integrating that new service; or de-registering a service where during deregistration ongoing requests may fail There is a need of a mechanism to perform simultaneous modifications in the network services by means of micro-service interfaces when the network is running and processing requests. The said mechanism should be capable of on demand FCAPS (fault, configuration, accounting, performance, and security) Management and on demand registration/deregistration with OAM (orchestration and management) service, which would increase network efficiency. Thus, there is requirement of a system and a method to manage and modify various network services while updating the inventory via an interface without any possible service disruption and create, delete or update required resources with ease and without consuming too much time, so that operation efficacy of a network improves.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for managing one or more operations at an inventory.
[0005] In one aspect of the present invention, the method for managing one or more operations at the inventory is disclosed. The method includes a step of receiving one or more inputs from a user via an interface to execute one or more operations at the inventory. The method further includes the step of generating a request based on receiving the one or inputs from the user. The method further includes the step of transmitting the request to the inventory to execute the one or more operations and receiving a response from the inventory based on transmitting the request to the inventory, the response representing a status of execution of the one or more operations at the inventory. The method further includes the step of notifying the user of the status of the response received from the inventory.
[0006] In an embodiment, the step of receiving the one or more inputs from the user via the interface to execute the one or more operations at the inventory includes the steps of, receiving credentials of the user to log-in via the interface and validating the credentials of the user and receiving one or more commands from the user to execute the one or more operations subsequent to validating the user.
[0007] In an embodiment, the one or more operations includes at least one of, change/set configurations of parameters, monitor performance of counters and severity wise alarms, register/deregister with an orchestration manager, identify status of the inventory or monitor health of the inventory.
[0008] In an embodiment, the request is at least one of, a HyperText Transfer Protocol (HTTP) request.
[0009] In an embodiment, the step of transmitting the request to the inventory to execute the one or more operations further includes the step of inferring transmission of the request to the inventory based on receiving an acknowledgement from the inventory.
[0010] In an embodiment, the status of the response includes at least one of, successful execution of the one or more operations or failure of the execution of the one or more operations at the inventory.
[0011] In an embodiment, the one or more processors communicates with the inventory via a communication channel.
[0012] In an embodiment, the communication channel is an interface between an inventory and a Command Line Interface (CLI).
[0013] In an embodiment, the interface is at least one of, an Inventory Manager Command Line (IM_CL) interface.
[0014] In another aspect of the present invention, the system to manage one or more operations at the inventory is disclosed. The system includes a transceiver configured to receive one or more inputs from a user via an interface to execute one or more operations at the inventory. The system further includes a generating unit configured to generate a request based on receiving the one or inputs from the user. The system further includes the transceiver unit configured to transmit the request to the inventory to execute the one or more operations and receive the response from the inventory via the interface based on transmitting the request to the inventory. The response representing a status of execution of the one or more operations at the inventory. The system further includes a notifying unit configured to notify the user of the status of the response received from the inventory.
[0015] 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 receive one or more inputs from a user via an interface to execute one or more operations at the inventory. The processor is further configured to generate a request based on receiving the one or inputs from the user. The processor is further configured to transmit the request to the inventory to execute the one or more operations. The processor is further configured to receive a response from the inventory based on transmitting the request to the inventory. The response representing a status of execution of the one or more operations at the inventory. The processor is further configured to notify the user of the status of the response received from the inventory.
[0016] 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
[0017] 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.
[0018] FIG. 1 is an exemplary block diagram of an environment to manage one or more operations at an inventory, according to one or more embodiments of the present invention;
[0019] FIG. 2 is an exemplary block diagram of a system to manage one or more operations at the inventory, according to one or more embodiments of the present invention;
[0020] FIG. 3a is an exemplary representation of an interface in a network environment and FIG.3b is a block diagram of an architecture implemented in the system of FIG. 2 to manage one or more operations at the inventory utilizing the IM_CL interface, according to one or more embodiments of the present invention;
[0021] FIG. 4 is an exemplary representation of a flowchart diagram to manage one or more operations at the inventory, according to one or more embodiments of the present invention; and
[0022] FIG. 5 is a schematic representation of a method to manage one or more operations at the inventory, according to one or more embodiments of the present invention.
[0023] FIG. 6 illustrates an architecture framework 600 (e.g., MANO architecture framework), in which the present invention can be implemented, in accordance with an embodiment of the present invention.
[0024] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0025] 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.
[0026] 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.
[0027] 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.
[0028] FIG. 1 illustrates an exemplary block diagram of an environment 100 to manage one or more operations at the inventory, 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 managing one or more operations at the inventory.
[0029] 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”.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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.
[0034] 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 to determine the cause of the anomaly in the network 105. As per one or more embodiments, the system 120 is adapted to be embedded within the server 115 or embedded as an individual entity.
[0035] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0036] FIG. 2 is an exemplary block diagram of the system 120 for managing one or more operations at the inventory, according to one or more embodiments of the present invention.
[0037] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a user interface 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.
[0038] 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.
[0039] In an embodiment, the user interface 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 user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 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.
[0040] 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.
[0041] In order for the system 120 to manage the one or more operations at the inventory, the processor 205 includes one or more modules. In one embodiment, the one or more modules/units includes, but not limited to, a transceiver unit 225, a generating unit 230, and a notifying unit 235 communicably coupled to each other for manage one or more operations at the inventory.
[0042] In one embodiment, each of the transceiver unit 225, the generating unit 230, and the notifying unit 235 can be used in combination or interchangeably for manage one or more operations at the inventory.
[0043] The transceiver unit 225, the generating unit 230, and the notifying unit 235, 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.
[0044] In an embodiment, the transceiver unit 225 is configured to receive one or more inputs from a user via an interface. The interface for example may include a Commend Line Interface (CLI) 305 (as shown in FIG.3) to execute the one or more operations at an inventory. Herein for example, the inventory is an inventory management system 320 (as shown in FIG.3). The CLI 305 is a communication channel between a User Equipment (UE) and the inventory management system 320 to transmit and receive data. The one or more inputs received from the user include user credentials, such as, but not limited to, username and password for logging into the CLI, and operational commands provided after login to execute the one or more operations at the inventory management system 320 such as, but not limited to, changing or setting configuration parameters, monitoring performance counters or severity-wise alarms, registering or deregistering with an orchestration manager, identifying the status of the inventory, and monitoring the health of the inventory.
[0045] The transceiver unit 225 is responsible for managing communication between the user and the inventory management system 320 via the CLI 305, including handling Orchestration and Management (OAM) services and Fault, Configuration, Accounting, Performance and Security (FCAPS) analysis. The transceiver unit 225 is configured to receive the one or more inputs from the user via the CLI 305 to execute the one or more operations at the inventory. At the outset, the transceiver unit 225 receives credentials of the user in order to log-in to the CLI 305. Thereafter, the user credentials are validated. The validation may involve checking the credentials against the database 220 or the authentication service to ensure that the user is authorized to access the CLI 305. When the credentials are correct, access is granted to the user. In cases where the credentials are incorrect, access is denied, and the user is prompted to re-enter the credentials. Only after the user credentials are validated, will the user be allowed to log-in to the CLI 305. Thereafter, depending on the operations required to be executed at the inventory management system 320, the user may select the one or more commands from the CLI 305. The CLI 305 provides a plurality of pre-defined commands in order to execute the one or more operations at the inventory management system 320. In an alternate embodiment, the user may customize the one or more commands in order to execute the operations. Customization may include modifying rules and/or parameters via the CLI 305. In an embodiment, the one or more commands are commands to execute the one or more operations at the inventory management system 320.
[0046] Upon receiving the one or more inputs from the user via the CLI 305 for execution, the generating unit 230 is configured to generate a request based on receiving the one or inputs from the user. In an embodiment, the request is at least one of, a HyperText Transfer Protocol (HTTP) request. The HTTP request is the standard method used by the CLI 305 to communicate with the inventory management system 320. The HTTP request is used to request data or perform one or more operations at the inventory management system 320.
[0047] The one or more operations includes at least one of change/set configurations of parameters, monitor performance of counters and severity wise alarms, register/deregister with an orchestration manager, identify status of the inventory or monitor health of the inventory. The one or more operation further includes tracking the health and performance of various components within the network inventory to ensure they are functioning correctly and to detect potential problems early. Additionally, the one or more operations facilitate FCAPS analysis which includes, but not limited to, monitor network function health, ensure configuration accuracy, track performance metrics, and detect security breaches.
[0048] Upon generating the request based on receiving the one or inputs from the user, the transceiver unit 225 is configured to transmit the request to the inventory management system 320 via the CLI 305. Thereafter, the transceiver unit 225 is configured to infer that the request safely reached the inventory management system 320 based on receiving an acknowledgment from the inventory management system 320. In an embodiment, the acknowledgment from the inventory management system 320 representing that the request has been safely received by the inventory management system 320.
[0049] Thereafter, the transceiver unit 225 is configured to receive a response from the inventory management system 320 based on transmitting the request to the inventory management system 320. In an embodiment, the response representing a status of execution of the one or more operations at the inventory management system 320. The status of execution of the one or more operations at the inventory includes at least one of, successful execution of the one or more operations or failure of execution of the one or more operations at the inventory management system 320.
[0050] Further, the notifying unit 235 may further notify the user to re-initiate the one or more operations using the CLI 305.
[0051] Therefore, advantageously, the CLI 305 acts as a communication channel between a User Equipment (UE) 110 of the user and the inventory management system 320. The interface is configured to at least one of, receive the one or more inputs from the user, transmit the request to the inventory management system 320, receive the response from the inventory management system 320 and notify the user of the status of the response received from the inventory management system 320.
[0052] FIG. 3a is an exemplary representation of an interface in a network environment. FIG.3b is a block diagram of an architecture of the system of FIG. 2 to manage one or more operations at the inventory utilizing an IM_CL interface 315, according to one or more embodiments of the present invention.
[0053] The architecture 300 includes a Commend Line Interface (CLI) 305, an inventory management system 320 which includes a Physical and Virtual Inventory Management (PVIM) 310 and the database 220 and an Inventory Management Commend Line Interface (IM_CL) 315.
[0054] As shown in FIG. 3a, a communication channel is established between the CLI 305 and the inventory (For example, the PVIM 310). The communication channel is an interface. In an embodiment, the interface is at least one of, an Inventory Manager Command Line (IM_CL) interface 315. The IM_CL interface 315 is configured to send and receive data between the PVIM 310 and the CLI 305. In an embodiment, the user interacts with the PVIM 310 via the CLI 305. The user inputs commands and provides credentials for authentication through the CLI 305. The CLI 305 refers to the specialized interface that allows network administrators to interact with and manage network elements and services through commands. Once authenticated, the CLI 305 sends the one or more commands to the IM_CL interface 315. The IM_CL interface 315 converts the one or more commands into HTTP requests. The HTTP requests are processed by the PVIM 310, the PVIM 310 handles various operations which includes, but not limited to, OAM services, FCAPS analysis and the management of virtualized and containerized network functions. After executing the commands, results are relayed back through the IM_CL interface 315 to the CLI 305. The users receive feedback, and detailed logs, configuration data, and performance metrics are stored in the database 220. The system notifies the user of the success or failure of the operations, providing comprehensive feedback on the outcome. The CLI 305 is the entry point for user interaction. The CLI 305 is where the user inputs one or more commands. The CLI 305 is responsible for accepting user credentials such as, but not limited to, username and password, which are validated to grant access to the inventory management system 320. Where the inventory management system 320 includes the PVIM 310 and the database 220, and facilitates the management of various network services, including the Operations, Administration, and Maintenance (OAM) services, Fault, Configuration, Accounting, Performance, and Security (FCAPS) analysis, as well as well as supporting virtualization management in line with Management and Orchestration (MANO) framework. The MANO framework enables efficient orchestration and lifecycle management of physical, virtual, and containerized network functions, ensuring seamless coordination across various network elements within the virtualized environment.
[0055] The CLI 305 communicates with the IM_CL interface 315, which is the crucial component that processes the one or more commands from the user and initiates the one or more operations on the PVIM 310. The IM_CL interface 315 acts as the bridge between the CLI 305 and the inventory management system 320 and transmits the one or more commands as requests. The IM_CL interface 315 processes the user’s one or more commands received from the CLI 305 by parsing and formatting the one or more commands into HTTP requests, which are transmitted to the PVIM 310 for execution. The IM_CL interface 315 ensures that one or more operations such as, FCAPS analysis, configuration changes, performance monitoring, and network function registration/deregistration are properly executed. Additionally, the IM_CL interface 315 integrates with the MANO framework components which includes, but not limited to, the network functions virtualization orchestrator (NFVO), virtualized network function manager (VNFM), and virtualized infrastructure manager (VIM), to handle the orchestration and lifecycle management of virtualized and containerized network functions. The VIM is a critical component of the network management architecture responsible for the management and orchestration of virtualized infrastructure resources. The VIM handles the allocation, management, and operational control of physical and virtual resources, such as, but not limited to, compute, storage, and networking, within the virtualized environment. Once the one or more operations are completed, the IM_CL interface 315 relays the results back to the CLI 305, providing users with feedback on the success or failure of the requested actions, while also logging any errors or outcomes for future reference.
[0056] The PVIM 310 is responsible for executing the one or more commands on the inventory management system 320, including FCAPS analysis and OAM service coordination, and integration with the MANO framework components which includes, but not limited to, NFVO, VNFM, and VIM, to ensure efficient orchestration and lifecycle management of network functions, including both virtualized and containerized network components.
[0057] Once the one or more inputs are received from the user via the CLI 305, the request is created. The request is formatted as the HTTP request, which is the standard method used for communication between the CLI 305 and the PVIM 310.
[0058] The PVIM 310 coordinates with the MANO framework to execute the requested one or more operations, ensuring the effective management of lifecycle events, including configuration changes, performance monitoring, and registration/deregistration of network functions.
[0059] The MANO framework consists of at least one of, but not limited to, the network functions virtualization orchestrator, virtualized network function manager, virtualized infrastructure manager. The MANO provides the structured approach to orchestrating and managing both virtualized and containerized network functions. Through the integration, the PVIM 310 coordinates operations across multiple infrastructures, ensuring efficient lifecycle management of network functions.
[0060] The request generated by the CLI 305 is transmitted to the PVIM 310. The PVIM 310 executes the requested one or more operations, such as, but not limited to, changing configuration parameters, monitoring performance metrics, or registering/deregistering network functions coordinating with the OAM services, and performing the FCAPS analysis. Upon executing the one or more operations, the inventory management system 320 sends the acknowledgment back to the processors 205. The acknowledgment indicates that the operation has been successfully processed. The processors 205 uses the acknowledgment to infer that the transmission of the request was successful.
[0061] After executing the requested one or more operations, the one or more operation details and outcomes are stored in the database 220. Once the one or more operations is successfully completed, the inventory management system 320 sends the response back to the processor 205 via the IM_CL interface 315 which is part of the CLI 305. The response typically includes the status of the operation, indicating whether it was successful or if there was a failure.
[0062] The database 220 storing user credentials and securely holds the credentials used for authenticating users. The database 220 contains configuration data for various inventory management system 320 including settings and parameters and maintains logs of the one or more operations performed through the PVIM 310 such as configuration changes, performance monitoring, and registration/deregistration activities, and the outcomes of the OAM services and the FCAPS analysis. The database 220 also stores detailed information which includes, but not limited to, status, health, and performance metrics, and records responses and acknowledgments from the inventory management system 220 after processing requests. The database 220 provides the complete history of one or more operations and outcomes for reference and troubleshooting.
[0063] Finally, the user is notified of the status of the one or more operations through the CLI 305. The status includes detailed information about the success or failure of the executed one or more operations, including any OAM service management and FCAPS analysis results.
[0064] FIG. 4 is an exemplary representation of a flowchart for managing one or more operations at the inventory which may be implemented in the system 120 of FIG. 2, according to one or more embodiments of the present invention.
[0065] At step 405, the CLI 305 acts as the primary interaction point for the user to input one or more commands and credentials. The user provides the one or more inputs via the CLI 305, which are used to authenticate the user by validating the credentials with database 220. Once validation is successful, access is granted to the PVIM 310. After authentication, the necessary permissions for issuing one or more commands are verified, and the one or more commands are passed to the IM_CL 315. The IM_CL 315 processes the one or more commands entered by the user and converts into the request. The request is formatted as the HTTP request to ensure smooth communication between the CLI 305 and the PVIM 310. The IM_CL 315 then forwards the request to the PVIM 310 for execution of the one or more operations.
[0066] At step 410, the MANO framework acts as the intermediary, by managing how the CLI 305 instructions are interpreted and passed onto the PVIM 310. The MANO framework is responsible for the orchestration of VNFs and the allocation of resources within the NFV infrastructure. The MANO framework handles tasks such as, but not limited to, lifecycle management, scaling operations, instantiation, and termination of VNFs. The MANO framework deploys VNFs via the CLI 305 commands and adjusts resources dynamically with input from the logic module. The MANO framework coordinates with the PVIM 310 for resource allocation and scaling, automating tasks to optimize network performance and minimize manual intervention. The MANO framework also ensures smooth VNF coordination and interoperability within the network.
[0067] At step 415, the MANO framework receives the request from the IM_CL 315 and coordinates with the PVIM 310 to execute the requested one or more commands, which may include one or more operations, such as, but not limited to, performance monitoring, configuration changes, or managing resources. Once the one or more commands are executed, the PVIM 310 sends the acknowledgment back to the IM_CL 315 via the MANO framework, indicating the success or failure of the one or more operations. Additionally, the PVIM 310 also logs the one or more operation details in the database 220 for future reference and instructs the southbound module to ensure the configuration changes and monitoring one or more commands.
[0068] Further, at step 420, the logic module processes the one or more commands, ensuring compliance with business rules and policies for tasks such as, but not limited to, FCAPS analysis, OAM management and integration with the MANO framework. The logic module evaluates each command against predefined rules to verify that the requested one or more operations align with operational guidelines and security protocols. The logic module performs detailed checks for data consistency, operational dependencies, and ensures that the one or more commands are suitable for execution across both virtualized and containerized network functions. The logic module also interacts with the MANO components which includes, but not limited to, NFVO, VNFM, and VIM to facilitate efficient orchestration, lifecycle management, and resource allocation. Once the one or more operations are completed, the logic module compiles and processes the results, which then sends back to the PVIM 310. The PVIM 310 subsequently returns the results to the user via the CLI 305, providing feedback on the success or failure of the executed commands, along with detailed information on any changes or updates made.
[0069] At step 425, the southbound module ensures that configuration changes and monitoring tasks are properly applied. The feedback from the network, such as device status or the success of one or more operations, is collected and passed back to the logic module for further processing. The MANO framework oversees the process, ensuring that the feedback is incorporated into the network’s broader orchestration strategy, enabling automated adjustments or optimizations as necessary.
[0070] FIG. 5 is a schematic representation of a method 500 of managing one or more operations at the inventory, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0071] At step 505, the method 500 includes the step of receiving one or more inputs from a user via an interface to execute one or more operations at the inventory.
[0072] At step 510, the method 500 includes the step of generating a request based on receiving the one or inputs from the user. The request is at least one of, the HTTP requests. The one or more operations includes at least one of, change/set configurations of parameters, monitor performance of counters and severity wise alarms, register/deregister with an orchestration manager, identify status of the inventory or monitor health of the inventory.
[0073] At step 515, the method 500 includes the step of transmitting the request to the inventory to execute the one or more operations and thereafter receiving a response from the inventory based on transmitting the request to the inventory. The response representing a status of execution of the one or more operations at the inventory.
[0074] At step 520, the method 500 includes the step of notifying the user of the status of the response received from the inventory. The status of the response includes at least one of, successful execution of the one or more operations or failure of the execution of the one or more operations at the inventory.
[0075] FIG. 6 illustrates an architecture framework 600 (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 600 includes the user interface 215, a Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) design function module 605, a platform foundation service module 610, a platform core service module 615, and a platform resource adapter and utilities module 620.
[0076] The NFV and SDN design function module 605 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 610 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 610 provides the essential capabilities and resources required for the CNF environment to function effectively.
[0077] The platform core service module 615 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 620 refer 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 620 plays a crucial role in integrating CNFs with underlying infrastructure and services, providing the necessary support for efficient operation, resource utilization, and interoperability.
[0078] The NFV and SDN design function module 610 includes a VNF lifecycle manger 605a, a VNF catalog 605b, a network service catalog 605c, a network slicing and service chaining manger (605d), a physical and virtual resource manager 605e, and a CNF lifecycle manager 605f.
[0079] The VNF lifecycle manager 605a is responsible for managing the entire lifecycle of Virtual Network Functions (VNFs). The VNF lifecycle manager 605a ensures that VNFs or CNFs are deployed, configured, monitored, scaled, and eventually decommissioned effectively. The VNF catalog 605b (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 605b 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 605c 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 605c serves as a central resource for defining, deploying, and managing these services within a containerized network environment.
[0080] The network slicing and service chaining manager 605d 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 physical and virtual resource manager 605e 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 physical and virtual resource manager 605e ensures that the necessary resources are allocated efficiently and effectively to meet the performance, availability, and scalability requirements of containerized network functions.
[0081] Further, the CNF lifecycle manager 605f is 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 CNF lifecycle manager 605f ensures that the CNFs are efficiently deployed, monitored, scaled, updated, and removed, facilitating the smooth operation of network services in a containerized environment.
[0082] The platform foundation service module 610 includes a microservice elastic load balancer 610a, an identity and access manager 610b, a command line interface 610c, a central logging manger 610d and an event routing manger 610e.
[0083] The microservice elastic load balancer 610a 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 610b is a critical component responsible for managing and securing access to containerized network functions and their resources. The identity and access manager 610b 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.
[0084] The central logging manger 610d 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 610e 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 manger 610e 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.
[0085] The platform core service module 615 includes an NFV infrastructure monitoring manager 615a, an assurance manager 615b, a performance manger 615c, a policy execution engine 615d, a capacity monitoring manger 615e,a release management repository 615f, a configuration manger and GCT (615g), a NFV platform decision analytics unit 615h, a platform NoSQL DB 615i, a platform scheduler and Cron Jobs module 615j, a VNF backup & upgrade manger 615k, a micro service auditor 615l, and a platform operation, administration and maintenance manager 615m.
[0086] The NFV infrastructure monitoring manager 615a monitors the underlying infrastructure of NFV environments, including computing, storage, and network resources. The NFV infrastructure monitoring manager 615a provides real-time visibility into resource health, performance, and utilization. Further, the NFV infrastructure monitoring manager 615a detects and alerts infrastructure issues. Further, the NFV infrastructure monitoring manager (615a) integrates with monitoring tools to ensure reliable operation of CNFs.
[0087] The assurance manager 615b manages the quality and reliability of network services by ensuring compliance with service level agreements (SLAs) and operational standards. The performance manger 615c optimizes the performance of CNFs by tracking and analyzing key performance indicators (KPIs). The policy execution engine 615d enforces and applies policies within the CNF environment to manage operations and access. Further, the policy execution engine 615d executes policies related to security, resource allocation, and service quality. Further, the policy execution engine (615d) executes policies translates policy rules into actionable configurations and enforces compliance across CNFs.
[0088] The capacity monitoring manager 615e monitors and manages the capacity of resources within the CNF environment to ensure optimal usage and avoid resource shortages. The release management repository 615f stores and manages software releases, configurations, and versions of CNFs. Further, the release management repository 615f keeps track of different versions of CNFs.
[0089] The configuration manager and Generic Configuration Tool (GCT) 615g manages the configuration of CNFs and related infrastructure components. The NFV platform decision analytics unit 615h analyzes data from a NFV platform to support decision-making and strategic planning.
[0090] The platform NoSQL database (DB) 615i 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 615j manages scheduled tasks and periodic operations within the CNF environment. The VNF backup & upgrade manger 615k oversees the backup and upgrade processes for Virtual Network Functions (VNFs) within the CNF environment.
[0091] The micro service auditor 615l monitors and audits microservices to ensure compliance with operational and security standards. The platform operation, administration and maintenance manager 615m manages the overall operation, administration, and maintenance of the CNF platform.
[0092] The platform resource adapter and utilities module 620 includes a platform external API adaptor and gateway 620a, a generic decoder and indexer 620b, a swarm adaptor 620c, an opensatck API adaptor 620 and a NFV gateway 620e.
[0093] The platform external API adaptor and gateway 620a facilitates communication between the CNF platform and external systems or services by providing an interface for API interactions. The generic decoder and indexer (620b) decodes and indexes various types of data and logs within the CNF environment. The swarm adaptor (620c) facilitates communication between a swarm clusters and the CNF environment, including container deployment, scaling, and management.
[0094] The opensatck API adaptor 620d 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 620e manages and facilitates communication between NFV (Network Functions Virtualization) components and external networks or services.
[0095] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by processor 205. The processor 205 is further configured to receive one or more inputs from the user via the interface to execute one or more operations at the inventory. The processor 205 is further configured to generate the request based on receiving the one or inputs from the user. The processor 205 is further configured to the transceiver configured to transmit the request to the inventory to execute the one or more operations and receive the response from the inventory based on transmitting the request to the inventory the response representing the status of execution of the one or more operations at the inventory. The processor 205 is further configured to notify the user of the status of the response received from the inventory.
[0096] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) 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.
[0097] The present disclosure incorporates technical advancement such as, but not limited to, simplifying communication with the inventory management system by automatically converting user inputs into HTTP-based event requests, unifies FCAPS analysis with OAM services for comprehensive network oversight, provides real-time execution feedback to improve decision-making, securely stores credentials and data for enhanced traceability, and reduces user complexity through the command line -based interface that streamlines command execution without requiring technical expertise.
[0098] The present invention offers multiple advantages to streamline network management by automating requests and integrating FCAPS with OAM for unified oversight, while also leveraging the MANO framework for enhanced orchestration and lifecycle management of virtualized and containerized network functions. The present invention provides real-time feedback, enhances data security, and simplifies user interaction with the commend line interface. The inclusion of on-demand OAM service registration, runtime configuration, and coordination with MANO components guarantees smooth operations and seamless orchestration ensure smooth operations. The present invention reduces manual effort, offers comprehensive network control, and enables quicker troubleshooting. Additionally, it improves accountability through secure data storage and auditability.
[0099] 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

[00100] Environment- 100
[00101] User Equipment (UE) - 110
[00102] Server - 115
[00103] Network- 105
[00104] System -120
[00105] Processor - 205
[00106] Memory - 210
[00107] User interface - 215
[00108] Database – 220
[00109] Transceiver unit - 225
[00110] Generating unit - 230
[00111] Notifying unit – 235
[00112] Commend Line Interface (CLI) - 305
[00113] Provisioning and Virtual Inventory Management (PVIM) - 310
[00114] Inventory Management Commend Line Interface (IM_CL) – 315
[00115] Inventory management system – 320
[00116] System architecture – 600
[00117] NFV and SDN design function – 605
[00118] VNF lifecycle manger - 605a
[00119] VNF catalog - 605b
[00120] Network service catalog - 605c
[00121] Network slicing and service chaining manger - 605d
[00122] Physical and virtual resource manager - 605e
[00123] CNF lifecycle manger - 605f
[00124] Platform foundation service module - 610
[00125] Microservice elastic load balancer - 610a
[00126] identity and access manager - 610b
[00127] Command line interface - 610c
[00128] Central logging manger - 610d
[00129] Event routing manger - 610e
[00130] platform core service module – 615
[00131] NFV infrastructure monitoring manager - 615a
[00132] Assurance manager - 615b
[00133] Performance manger - 615c
[00134] Policy execution engine - 615d
[00135] Capacity monitoring manger - 615e
[00136] Release management repository - 615f
[00137] Configuration manger and GCT - 615g
[00138] NFV platform decision analytics - 615h
[00139] Platform NoSQL DB - 615i
[00140] Platform scheduler and cron Jobs module - 615j
[00141] VNF backup & upgrade manger - 615k
[00142] Micro service auditor - 615l
[00143] Platform operation, administration and maintenance manager - 615m
[00144] Platform resource adapter and utilities module – 620
[00145] Platform External API adaptor and gateway - 620a
[00146] Generic decoder and indexer - 620b
[00147] Swarm adaptor 620c
[00148] Openstack API adaptor - 620d
[00149] NFV gateway - 620e

,CLAIMS: CLAIMS
We Claim:
1. A method (500) to manage one or more operations at an inventory, the method (500) comprising the steps of:
receiving, by one or more processors (205), one or more inputs from a user via an interface to execute one or more operations at the inventory;
generating, by the one or more processors (205), a request based on receiving the one or inputs from the user;
transmitting, by the one or more processors (205), the request to the inventory to execute the one or more operations via the interface;
receiving, by the one or more processors (205), a response from the inventory via the interface based on transmitting the request to the inventory, the response representing a status of execution of the one or more operations at the inventory; and
notifying, by the one or more processors (205), the user the status of the response received from the inventory.

2. The method (500) as claimed in claim 1, wherein the step of, receiving, one or more inputs from a user via an interface to execute one or more operations at the inventory, includes the steps of:
receiving, by the one or more processors (205), credentials of the user to log-in via the interface; and
validating, by the one or more processors (205), the credentials of the user; and
receiving, by the one or more processors (205), one or more commands from the user to execute the one or more operations subsequent to validating the user.

3. The method (500) as claimed in claim 1, wherein the one or more operations includes at least one of:
change/set configurations of parameters;
monitor performance of counters and severity wise alarms;
register/deregister with an orchestration manager;
identify, status of the inventory; or
monitor, health of the inventory.

4. The method (500) as claimed in claim 1, wherein the request is at least one of, a HyperText Transfer Protocol (HTTP) request.

5. The method (500) as claimed in claim 1, wherein the step of, transmitting, the request to the inventory to execute the one or more operations, further includes the step of:
inferring, by the one or more processors (205), transmission of the request to the inventory based on receiving an acknowledgement from the inventory.

6. The method (500) as claimed in claim 1, wherein the status of the response includes at least one of, successful execution of the one or more operations or failure of the execution of the one or more operations at the inventory.

7. The method (500) as claimed in claim 1, wherein the one or more processors (205) communicates with the inventory via a communication channel.

8. The method (500) as claimed in claim 7, wherein the communication channel is an interface between the inventory and a Command Line Interface (CLI).

9. The method (500) as claimed in claim 8, wherein the interface is at least one of, an Inventory Manager Command Line (IM_CL) interface.

10. A system (120) to manage one or more operations at an inventory, the system (120) comprising:
a transceiver unit (225), configured to, receive, one or more inputs from a user via an interface to execute one or more operations at the inventory;
a generating unit (230), configured to, generate, a request based on receiving the one or inputs from the user;
the transceiver unit (225), configured to:
transmit, the request to the inventory to execute the one or more operations via the interface;
receive, a response from the inventory via the interface based on transmitting the request to the inventory, the response representing a status of execution of the one or more operations at the inventory; and
a notifying unit (235), configured to, notify, the user the status of the response received from the inventory.

11. The system (120) as claimed in claim 10, wherein the transceiver unit (225) is configured to receive, the one or more inputs from the user via the interface to execute the one or more operations at the inventory, by:
receiving, credentials of the user to log-in via the interface; and
validating, the credentials of the user; and
receiving, one or more commands from the user to execute the one or more operations subsequent to validating the user.

12. The system (120) as claimed in claim 10, wherein the one or more operations includes at least one of:
change/set configurations of parameters;
monitor performance of counters and severity wise alarms;
register/deregister with an orchestration manager;
identify, status of the inventory; or
monitor, health of the inventory.

13. The system (120) as claimed in claim 10, wherein the request is at least one of, a HyperText Transfer Protocol (HTTP) request.

14. The system (120) as claimed in claim 10, wherein the transceiver unit (225) is further configured to:
infer, transmission of the request to the inventory based on receiving an acknowledgement from the inventory.

15. The system (120) as claimed in claim 10, wherein the status of the response includes at least one of, successful execution of the one or more operations or failure of the execution of the one or more operations at the inventory.

16. The system (120) as claimed in claim 10, wherein the one or more processors (205) communicates with the inventory via a communication channel.

17. The system (120) as claimed in claim 16, wherein the communication channel is an interface between the inventory and a Command Line Interface (CLI).

18. The system (120) as claimed in claim 17, wherein the interface is at least one of, an Inventory Manager Command Line (IM_CL) interface.