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

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGEMENT OF ONE OR MORE NETWORK FUNCTIONS IN A NETWORK
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 communication network management, more particularly relates to a method and a system for management of one or more network functions in the communication network.
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. The communication network comprises of many network elements which are configured to operate in specific manners to improve credibility of the communication network. Moreover, to process a request from a user there are several micro-services that are executed within a network function (NF) which are responsible for the operation of the network elements. The network functions which may be container network function (CNF) or virtual network function (VNF) etc. are managed at the backend by manual interventions. Managing each network function (NF) by different interfaces is time and resource inefficient, which may also invoke unwanted co-ordination errors in the network.
[0003] Presently, there is no available technology to manage all network functions, may it be CNF or VNF by means of a single interface. There is a need for a single platform/interface to regulate and manage all the NFs in a network. It is necessary to design an interface which is compatible with all NFs (may it be a CNF/CNFC or VNF) and perform multiple micro-services with ease and without consuming too much time and resources.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for management of one or more network functions in a network.
[0005] In one aspect of the present invention, the system for management of the one or more network functions in the network is disclosed. The system includes a transceiver configured to receive an event request from a user using a User Equipment (UE). The event request pertains to accessing data pertaining to one or more network functions in the network. The system further includes a querying unit configured to query an Inventory Manager (IM) to search for the data pertaining to the one or more network functions based on the received event request. The system further includes a retrieving unit configured to retrieve information of the searched data pertaining to the one or more network functions based on the received event request. The system further includes a generating unit configured to generate an Inventory Manager User Interface (IM_UI) between the user and the IM. The IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM on retrieval of the searched data.
[0006] In an embodiment, the transceiver subsequent to receiving the event request from the user using the UE is further configured to transmit an event acknowledgment response to the user using the UE.
[0007] In an embodiment, the event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).
[0008] In an embodiment, the querying unit queries the IM to search for the data pertaining to the one or more network functions based on the received event request, by assigning, a task to at least a first instance to search for the data pertaining to the one or more network functions at the IM. Thereafter, the querying unit is configured to maintain one or more substitute instances and re-assign the task to the one or more substitute instances when the first instance fails to perform the task.
[0009] In an embodiment, the IM_UI is an async based interface for communication between the user and the IM.
[0010] In an embodiment, the IM includes a database to store the data related to the one or more network functions.
[0011] In an embodiment, modifying the searched data includes operations of one of, create, update, fetch and delete the searched data.
[0012] In an embodiment, the generating unit is further configured to generate one or more flavors pertaining to attributes of the one or more network functions based on the user customizing one or more parameters in one or more categories from the UE. The one or more parameters include at least one of, Central Processing Unit (CPU) and Random Access Memory (RAM).
[0013] In another aspect of the present invention, the method for management of network functions in the network is disclosed. The method includes the step of receiving an event request from a user using a User Equipment (UE). The event request pertains to accessing data pertaining to one or more network functions in the network. The method further includes the step of querying an Inventory Manager (IM) to search for the data pertaining to the one or more network functions based on the received event request. The method further includes the step of retrieving information of the searched data pertaining to the one or more network functions based on the received event request. The method further includes the step of generating an Inventory Manager User Interface (IM_UI) between the user and the IM. The IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM on retrieval of the searched data.
[0014] 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 an event request from a user using a User Equipment (UE). The event request pertains to accessing data pertaining to one or more network functions in the network. The processor is configured to query an Inventory Manager (IM) to search for the data pertaining to the one or more network functions based on the received event request. The processor is configured to retrieve information of the searched data pertaining to the one or more network functions based on the received event request. The processor is configured to generate an Inventory Manager User Interface (IM_UI) between the user and the IM. The IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM on retrieval of the searched data.
[0015] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to transmit, at least one of, an event request to the one or more processors. The event request pertains to accessing data pertaining to one or more network functions in the network.
[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 for management of one or more network functions in a network, according to one or more embodiments of the present invention;
[0019] FIG. 2 is an exemplary block diagram of a system for management of the one or more network functions in the network, according to one or more embodiments of the present invention;
[0020] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0021] FIG. 4 is an exemplary block diagram of an architecture of IM_UI interface, according to one or more embodiments of the present invention;
[0022] FIG. 5 is a signal flow diagram of IM_UI interface, according to one or more embodiments of the present invention; and
[0023] FIG. 6 is a schematic representation of a method for management of the one or more network functions in the network, according to one or more embodiments 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] The present invention discloses a method and a system for management of one or more Network Functions (NF) in a network. The present invention includes an interface which is completely based on micro service architecture. The interface is configured to manage multiple container network functions (CNFs) or virtual network functions (VNFs) simultaneously in terms of network function visualization (NFV). The interface is completely event driven and is based on standard application programming interface (API).
[0029] FIG. 1 illustrates an exemplary block diagram of an environment 100 for management of one or more network functions in a network 106, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, the network 106 and a system 108 communicably coupled to each other for management of the one or more network functions in the network 106.
[0030] In an embodiment, the one or more network functions refer to a specific task or service within the network 106 that is responsible for handling various operations necessary for network communication and management. The one or more network functions include, but are not limited to, routing, switching, firewalling, load balancing, DNS resolution, session management. The managing of the one or more network functions in the network 106 include, but are not limited to, Inventory Management (IM), Network Management Systems (NMS), orchestration systems, policy-based management, event-driven workflows, analytics-driven workflows, User Interfaces (UI) and Application Programming Interfaces (APIs).
[0031] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0032] In an embodiment, the UE 102 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.
[0033] The environment 100 includes the server 104 accessible from the network 106. The server 104 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.
[0034] The network 106 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 106 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.
[0035] The network 106 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 106 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.
[0036] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 from the network 106. The system 108 is configured to manage the one or more network functions in the network 106. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0037] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0038] FIG. 2 is an exemplary block diagram of the system 108 for management of the one or more network functions in the network 106, according to one or more embodiments of the present invention.
[0039] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, and a user interface 206. In an embodiment, an Inventory Manger (IM) 218 is communicably coupled with the system 108. Further, the IM 218 includes a database 208.
[0040] For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processor 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 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.
[0041] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 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 204 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.
[0042] In an embodiment, the user interface 206 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 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0043] The IM 218 is a component responsible for managing and organizing data related to one or more network functions. The IM 218 serves as a central repository and control point for network 106 related information. The IM 218 performs at least one of, data storage, data retrieval, data management, query handling, integration, and reporting. Further, the IM 218 includes the database 208 for storing the data.
[0044] The database 208 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 208 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.
[0045] In order for the system 108 to manage the one or more network functions in the network 106, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a transceiver 210, a querying unit 212, a retrieving unit 214, and a generating unit 216 communicably coupled to each other for management of the one or more network functions in the network 106.
[0046] In one embodiment, the one or more modules includes, but not limited to, the transceiver 210, the querying unit 212, the retrieving unit 214, and the generating unit 216 can be used in combination or interchangeably for management of the one or more network functions in the network 106.
[0047] The transceiver 210, the querying unit 212, the retrieving unit 214, and the generating unit 216 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 202. 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 202 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 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0048] In one embodiment, the transceiver 210 is configured to receive an event request from a user using the UE 102. In another embodiment, the event request from the user is received using the UI 206. The user is an individual or system 108 that interacts with the network 106 to perform specific tasks or access information. The user is at least one of, administrator, network operator, or software application. The event request pertains to accessing data pertaining to one or more network functions in the network 106. The event request is a command sent from the user using the UE 102, indicating the user’s requirements related to the one or more network functions. The event request includes, but is not limited to, data accessing request, data modification request, data retrieving request, data deleting request. The event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).
[0049] In an embodiment, the data refers to the information related to the one or more network functions in the network 106. The data includes, but is not limited to, configuration data, performance metrics, operational data, usage data, service data security data, historical data. The configuration data includes, but is not limited to, bandwidth, Internet Protocol (IP) addresses, routing protocols, network layouts and arrangement of network components. The performance metrics include, but are not limited to, throughput, latency, error rates. The operational data includes, but is not limited to, the status or health of the one or more network functions such as operational, degraded or failed, records of events and activities such as messages, error and warnings. The user data includes, but is not limited to, information about data flow such as amount of data transferred, types of traffic and peak usage times, metrics on how the network resources like Central Processing Unit (CPU), memory and storage are being used. The service data includes, but is not limited to, information related to service quality and compliance with service level agreements (SLAs), data about the allocation and setup of network services such as virtual networks and slices. The security data includes, but is not limited to, information about permissions and user access rights to the one or more network functions, data related to security threats, and vulnerabilities. The historical data includes, but is not limited to, historical performance and usage data used for analysis and forecasting, recording of configuration changes and updates over time.
[0050] Subsequent to receiving the event request from the user using the UE 102, the transceiver 210 is configured to transmit an event acknowledgment response to the user using the UE 102. The event acknowledgment response is a message sent by the system 108 to the user using the UE 102 to confirm the receipt of the event request. In particular, the event acknowledgement response confirms that the event request has been successfully received and is being processed. The event acknowledgement response includes information about the status of the event request. The status of the event request is at least one of, received, in process, or pending.
[0051] Upon receiving the event request from the user using the UE 102, the querying unit 212 is configured to query an Inventory Manager (IM) 218. The IM 218 is queried to search for the data pertaining to the one or more network functions. The IM 218 is a component responsible for managing and organizing data related to the one or more network functions. The IM 218 serves as a central repository and control point for network 106 related information. The IM 218 performs at least one of, data storage, data retrieval, data management, query handling, integration, and reporting. In an embodiment, the IM 218 includes the database 208 to store the data related to the one or more network functions.
[0052] In an embodiment, the querying unit 212 queries the IM 218 by assigning a task to at least a first instance. The task is assigned to the at least first instance to search for the data pertaining to the one or more network functions at the IM 218. The task refers to the activity of searching and retrieving data related to one or more network functions at the IM 218 based on the received event request. The instance is a specific execution thread or process dedicated to performing particular task. More specifically, the first instance is a specific execution thread or process to search for the data pertaining to the one or more network functions at the IM 218. Further, the querying unit 212 maintains one or more substitute instances. The one or more substitute instances are backup processes or threads prepared to take over the task if the first instance encounters issues. The issues refer to problems or disruptions that impact the successful execution of the search task or the overall process. The issues are at least one of, system failures, performance degradation, data retrieval errors, query errors, memory leaks, CPU overload, connectivity issues, network latency, incorrect configurations, version incompatibility, storage failures, or service unavailability. In an embodiment, when the first instance fails to perform the task, the querying unit 212 reassigns the task to the one or more substitute instances.
[0053] Upon searching the data, the retrieving unit 214 is configured to retrieve information of the searched data. More specifically, the retrieving unit 214 retrieves the information of the searched data pertaining to the one or more network functions based on the received event request. The information of the searched data refers to the specific details and data that have been retrieved from the IM 218 in response to the query initiated by the querying unit 212. The searched data includes, but is not limited to, configuration data, status data, performance data.
[0054] Upon retrieving the information of the searched data, the generating unit 216 is configured to generate an Inventory Manager User Interface (IM_UI) between the UE 102 and the IM 218. The IM_UI is an async based interface for communication between the UE 102 and the IM 218. The async based interface refers to an asynchronous interface that allows communication between components or systems in a way that does not require both parties to be simultaneously engaged in the communication process. The asynchronous interface is a type of communication interface in which operations, such as sending requests and receiving responses, are handled without requiring the involved processes or systems to operate in a synchronized manner. In other words, for example, the sender can initiate a request and continue with other tasks without waiting for an immediate response, and the receiver can process the request and respond when it is ready. In an embodiment, the communication between the user and the IM 218 from the IM_UI does not require both the user and the IM 218 to be active or wait for the response simultaneously, instead the data exchanges occur independently. The IM_UI includes, but not limited to, user interaction, customization, data display, real-time updates, and editing functions. Further the IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM 218. The modifying of the searched data includes operations. The operations is at least one of, create, update, fetch, and delete the searched data. In an embodiment, the IM_UI is generated to allow the user to interact with and modify the data that has been searched by the querying unit 212 and retrieved by the retrieving unit 214 from the IM 218. More specifically, the IM_UI is tailored to present the specific data related to the network functions that the user has requested. The IM_UI is designed to facilitate the specific actions the user needs to perform, such as creating, updating, fetching, or deleting the searched data. The IM_UI is likely generated with controls and options that align with the operations such as creating, updating, fetching, or deleting the searched data.
[0055] In an embodiment, the generating unit 216 is configured to generate one or more flavors pertaining to attributes of the one or more network functions. The one or more flavors refers to the specific configurations or sets of attributes that define the resources allocated to one or more network functions. The set of attributes refer to the specific characteristics or properties that define how the network functions operate and perform. The set of attributes of the network function include, but are not limited to, Central Processing Unit (CPU), Random Access Memory (RAM), storage capacity, network bandwidth, security settings, scalability options, Service Level Agreements (SLAs).
[0056] The one or more flavors pertaining to the set of attributes of the one or more network functions is generated based on the user customizing one or more parameters in one or more categories from the UE 102. The one or more parameters refer to the specific adjustable settings or values that define the characteristics and performance of the one or more network functions. The one or more parameters include at least one of, CPU, RAM, storage capacity, and network bandwidth. In an embodiment, the one or more flavors are the customized configurations generated by the system 108 when the user modifies the one or more parameters like CPU and RAM. For example, the user generates a flavor that allocates 4 CPU cores and 8 GB of RAM to the network function for high performance tasks. The flavor might generate just 1 CPU core and 2GB of RAM for basic tasks.
[0057] In an embodiment, the one or more categories refer to the broader groups or classifications that encompass related one or more parameters. The one or more categories represent different aspects of the network function's configuration, where each category includes specific parameters that can be adjusted by the user. The one or more categories include at least one of, processing power, memory, storage, and networking. More specifically, the one or more flavors are generated based on the user modifying one or more parameters in one or more categories refers that the users are allowed to adjust settings within various groups of related parameters. The related parameters are the specific, adjustable settings within the category that directly influence how an attribute of the one or more network functions operate. For example, the user might decide to increase the RAM in the Memory category while also increasing the CPU cores in the Processing Power category.
[0058] By managing the one or more network functions in the network 106, the system 108 enhance the efficiency, reliability, and ease of managing network infrastructure using both Cloud-Native Network Functions (CNFs) and Virtual Network Functions (VNFs). The system 108 reduces the complexity of managing NFs, thereby minimizing the chances of human error and increasing operational efficiency. Further, the system 108 improves the reliability of the network 106 by reducing downtime.
[0059] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 102a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0060] As mentioned earlier in FIG. 1, each of the first UE 102a, the second UE 102b, and the third UE 102c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0061] The one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 102a to transmit the at least one of the event requests to the one or more processors 202. The event request pertains to accessing data pertaining to one or more network functions in the network 106.
[0062] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured to manage the one or more network functions in the network 106. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, and the user interface 206. In an embodiment, an Inventory Manger (IM) 218 is communicably coupled with the system 108. Further, the IM 218 includes a database 208. In the operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0063] Further, the processor 202 includes the transceiver 210, the querying unit 212, the retrieving unit 214, and the generating unit 216. The operations and functions of the transceiver 210, the querying unit 212, the retrieving unit 214, and the generating unit 216 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0064] FIG. 4 is an exemplary block diagram of an architecture 400 of the IM-UI interface, according to one or more embodiments of the present invention.
[0065] The architecture 400 includes the User Interface (UI) 206, a Physical and virtual Inventory Manager (PVIM) 402, and the database 208.
[0066] In an embodiment, the event request from the user is received from the UI 206. The event request pertains to accessing data pertaining to one or more network functions in the network 106. The event request is received from at least one of, a Hypertext Transfer Protocol (HTTP). Upon receiving the event request from the user using the UI 206, the event acknowledgement response is transmitted to the user using the UI 206. Subsequently, the event request is transmitted to the PVIM 402. The PVIM 402 is the inventory manager responsible for handling queries related to the one or more network functions, managing data retrieval, and storing data in the database 208. The PVIM 402 searches the data pertaining to the one or more network functions based on the received event request. Upon searching the data pertaining to the one or more network functions, the PVIM 402 retrieves the information of the searched data from the database 208.
[0067] Subsequently, the UI 206 enables the user to modify the searched data pertaining to the one or more network functions present at the PVIM 402. The modifying the searched data includes operations of at least one of, create, update, fetch and delete the searched data. The searched data includes information related to sites, pods, hosts, VNFs (Virtual Network Functions), and VNFCs (Virtual Network Function Components). Further, the UI 206 facilitates provisioning, updating, or deletion of network resources such as hosts and pods. In an embodiment, the UI 206 is an async based interface for the communication between the user and the PVIM 402. In an embodiment, one or more flavors pertaining to attributes of the one or more network functions are generated based on the user customizing one or more parameters in one or more categories from the UI 206.
[0068] FIG. 5 is a flow diagram 500 of the IM_UI interface, according to one or more embodiments of the present invention.
[0069] The flow diagram 500 includes the UI 206, the PVIM 402, the database 208 and the business logic 502.
[0070] In an embodiment, the event request is received from the user using the UI 206. The event request pertains to accessing data pertaining to the one or more network functions in the network 106. The event request is received via at least one of, a Hypertext Transfer Protocol (HTTP). Upon receiving the event request, the event acknowledgement response is transmitted to the user using the UI 206.
[0071] Subsequently, the PVIM 402 searches for the data pertaining to the one or more network functions based on the received event request. The PVIM 402 searches for the data by assigning the task to at least one instance to search for the data. The PVIM 402 maintains the one or more substitute instances. Thereafter the PVIM 402 re-assigns the tasks to the one or more substitute instances when the first instance fails to perform the task.
[0072] Upon searching the data, the PVIM 402 retrieves the information of the searched data from the database 208. In an embodiment, the business logic 502 component implements the functional operations associated with the event requests. The business logic 502 processes requests sent to the PVIM 402, ensuring that appropriate actions (such as querying, updating, or deleting data) are performed. In an embodiment, the business logic 502 acts as the intermediary that processes event requests, interfaces with the PVIM 402 handles data retrieval and modification and ensures that the UI 206 provides the user with the necessary functionality to manage network functions. The business logic 502 is central to the operation of the system, making sure that all components work together seamlessly.
[0073] Thereafter, the UI 206 enables the user to modify the searched data pertaining to the one or more network functions at the PVIM 402. The modifying the searched data includes operations of at least one of create, update, fetch and delete the searched data. The searched data includes information related to sites, pods, hosts, VNFs (Virtual Network Functions), and VNFCs (Virtual Network Function Components). The VNF is a software implementation of a network function that can run on a virtualized infrastructure (such as virtual machines or containers) instead of being tied to specific hardware. The VNFs can perform various networking tasks like firewalls, load balancers, routers, and more. The VNFC is a smaller, modular component that makes up part of the VNF. The VNFC is typically a software module or a microservice that handles a specific function within the VNF. Multiple VNFCs can be combined to form a complete VNF, allowing for greater flexibility and scalability. Further, the UI 206 facilitates provisioning, updating, or deletion of network resources such as hosts and pods. In an embodiment, the UI 206 is an async based interface for the communication between the user and the PVIM 402. In an embodiment, one or more flavors pertaining to attributes of the one or more network functions are generated based on the user customizing one or more parameters in one or more categories from the UI 206.
[0074] FIG. 6 is a flow diagram of method 600 for management of the one or more network functions in the network 106, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0075] At step 602, the method 600 includes the step of receiving an event request from a user using the UE 102 by the transceiver 210. The event request pertains to accessing data pertaining to one or more network functions in the network 106. Subsequent to receiving the event request from the user using the UE 102, the event acknowledgement response is transmitted to the user using the UE 102. The event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).
[0076] At step 604, the method 600 includes the step of querying the IM 218 to search for the data pertaining to the one or more network functions based on the received event request by the querying unit 212. The querying unit 212 queries the IM 218 to search for the data pertaining to the one or more network functions by assigning the task to at least the first instance to search for the data pertaining to the one or more network functions at the IM 218. Thereafter, the querying unit 212 maintains the one or more substitute instances and reassigns the task to the one or more substitute instances when the first instance fails to perform the task. The IM 218 includes a database to store the data related to the one or more network functions.
[0077] At step 606, the method 600 includes the step of retrieving the information of the searched data pertaining to the one or mor network functions based on the received event request by the retrieving unit 214.
[0078] At step 608, the method 600 includes the step of generating, the IM_UI between the user and the IM 218 by the generating unit 216. The IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM 218 on retrieval of the searched data. The IM_UI is an async based interface for communication between the user and the IM 218. The modifying of the searched data includes operations of at least one of, create, update, fetch and delete the searched data. In an embodiment, generating the one or more flavors pertaining to attributes of the one or more network functions based on the user customizing one or more parameters in one or more categories from the UE 102. The one or more parameters include at least one of, Central Processing Unit (CPU) and Random Access Memory (RAM)
[0079] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive an event request from the user using the UE 102. The event request pertains to accessing data pertaining to one or more network functions in the network 106. The processor 202 is further configured to query the IM 218 to search for the data pertaining to the one or more network functions based on the received event request. The processor 202 is further configured to retrieve the information of the searched data pertaining to the one or more network functions based on the received event request. The processor 202 is further configured to generate the IM_UI between the user and the IM 218. The IM_UI enabling the user to modify the searched data pertaining to the one or more network functions stored at the IM 218.
[0080] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0081] The present disclosure incorporates technical advancement of enhancing the efficiency, reliability, and ease of managing network infrastructure using both Cloud-Native Network Functions (CNFs) and Virtual Network Functions (VNFs). The present invention reduces the complexity of managing NFs, thereby minimizing the chances of human error and increasing operational efficiency. Further, the present invention improves the reliability of the network by reducing downtime. The present invention can deliver faster responses to configuration changes and reduce the overall operational cost, making it more scalable and sustainable. The present invention enhances accuracy and improves the overall consistency of the network environment.
[0082] 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

[0083] Environment- 100
[0084] User Equipment (UE)- 102
[0085] Server- 104
[0086] Network- 106
[0087] System -108
[0088] Processor- 202
[0089] Memory- 204
[0090] User Interface- 206
[0091] Database- 208
[0092] Transceiver - 210
[0093] Querying Unit- 212
[0094] Retrieving unit- 214
[0095] Generating Unit- 216
[0096] Inventory Manger (IM)- 218
[0097] One or more primary processor- 302
[0098] Memory 304
[0099] PVIM- 402
[00100] Business logic 502
,CLAIMS:CLAIMS:
We Claim:
1. A method (600) for management of one or more network functions in a network (106), the method (600) comprises the steps of:
receiving, by one or more processors (202), an event request from a user using a User Equipment (UE), the event request pertains to accessing data pertaining to one or more network functions in the network (106);
querying, by the one or more processors (202), an Inventory Manager (IM) (218) to search for the data pertaining to the one or more network functions based on the received event request;
retrieving, by the one or more processors (202), information of the searched data pertaining to the one or more network functions based on the received event request; and
generating, by the one or more processors (202), an Inventory Manager User Interface (IM_UI) between the user and the IM (218), wherein the IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM (218) on retrieval of the searched data.

2. The method (600) as claimed in claim 1, wherein the step of, receiving, an event request from a user using a User Equipment (UE) (102), further includes the step of:
transmitting, by the one or more processors (202), an event acknowledgment response to the user upon receiving the event request.

3. The method (600) as claimed in claim 1, wherein the event request is received by the one or more processors from at least one of, a Hypertext Transfer Protocol (HTTP).

4. The method (600) as claimed in claim 1, wherein the step of, querying, an Inventory Manager (IM) (218) to search for the data pertaining to the one or more network functions based on the received event request, includes the steps of:
assigning, by the one or more processors (202), a task to at least a first instance to search for the data pertaining to the one or more network functions at the IM (218);
maintaining, by the one or more processors (202), one or more substitute instances; and
re-assigning, by the one or more processors (202), the task to the one or more substitute instances when the first instance fails to perform the task.

5. The method (600) as claimed in claim 1, wherein the IM_UI is an async based interface for communication between the user and the IM (218).

6. The method (600) as claimed in claim 1, wherein the IM (218) includes a database (208) to store the data related to the one or more network functions.

7. The method (600) as claimed in claim 1, wherein modifying the searched data includes operations of one of, create, update, fetch and delete the searched data.

8. The method (600) as claimed in claim 1, wherein the method further comprises the step of:
generating, by the one or more processors (202), one or more flavors pertaining to attributes of the one or more network functions based on the user customizing one or more parameters in one or more categories from the UE (102), wherein the one or more parameters include at least one of, Central Processing Unit (CPU) and Random Access Memory (RAM).

9. A system (108) for management of one or more network functions in a network (106), the system (108) comprising:
a transceiver (210), configured to, receive, an event request from a user using a User Equipment (UE) (102), the event request pertains to accessing data pertaining to one or more network functions in the network (106);
a querying unit (212), configured to, query, an Inventory Manager (IM) (218) to search for the data pertaining to the one or more network functions based on the received event request;
a retrieving unit (214), configured to, retrieve, information of the searched data pertaining to the one or more network functions based on the received event request; and
a generating unit (216), configured to, generate, an Inventory Manager User Interface (IM_UI) between the user and the IM (218), wherein the IM_UI enabling the user to modify the searched data pertaining to the one or more network functions stored at the IM (218) on retrieval of the searched data.

10. The system (108) as claimed in claim 9, wherein the transceiver (210) subsequent to receiving, the event request from the user using the UE (102), is further configured to:
transmit, an event acknowledgment response to the user using the UE (102).

11. The system (108) as claimed in claim 9, wherein the event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).

12. The system (108) as claimed in claim 9, wherein the querying unit (212), queries, the IM (218) to search for the data pertaining to the one or more network functions based on the received event request, by:
assigning, a task to at least a first instance to search for the data pertaining to the one or more network functions at the IM (218);
maintaining, one or more substitute instances; and
re-assigning, the task to the one or more substitute instances when the first instance fails to perform the task.

13. The system (108) as claimed in claim 9, wherein the IM_UI is an async based interface for communication between the user and the IM (218).

14. The system (108) as claimed in claim 9, wherein the IM (218) includes a database (208) to store the data related to the one or more network functions.

15. The system (108) as claimed in claim 9, wherein modifying the searched data includes operations of one of, create, update, fetch and delete the searched data.

16. The system (108) as claimed in claim 9, wherein the generating unit (216) is further configured to:
generate, one or more flavors pertaining to attributes of the one or more network functions based on the user customizing one or more parameters in one or more categories from the UE (102), wherein the one or more parameters include at least one of, Central Processing Unit (CPU) and Random Access Memory (RAM).

17. A User Equipment (UE) (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors causes the UE (102) to:
transmit, at least one of, an event request to the one or more processors (202), the event request pertains to accessing data pertaining to one or more network functions in the network (106);
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.