Methods and systems for management of database operations in a network

Abstract

The present disclosure relates to methods and systems for management of database operations in a network In one example, the method comprises receiving, by a transceiver unit [304] at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit [302], an event request associated with one or more Network Functions (NFs), based on which, a request may be transmitted to one or more databases [404]. The method further comprises receiving, by the transceiver unit [304] at the NPDA unit [302], a response from the one or more databases [404] generated by the one or more databases [404] based on at least one operation associated with the request. Then, based on the received response, the method further comprises transmitting, by the transceiver unit [304] at the NPDA unit [302], an event response.

Description

METHODS AND SYSTEMS FOR MANAGEMENT OF DATABASE OPERATIONS IN A NETWORKFIELD OF INVENTION

[0001] Embodiments of the present disclosure generally relate to operations management. More particularly, embodiments of the present disclosure relate to methods and systems for management of database operations in a network.BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first-generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third- generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] Generally, during the management of the wireless communication networks, several components are utilized, such as a Network Function Virtualization (NFV) Platform Data Analytics (NPDA) server that incorporates real-time analytics capabilities within the wireless communication network. For implementation of the real-time analytics by the NPDA server, the NDPA server interacts with multiple components such as an NF server, and a database. The NFserver may be such as a cloud-native network function (CNF) server / CNF components (CNFC) servers or virtual network function (VNF) server / VNF components (VNFC) servers.

[0005] Based on certain policies and inputs from other microservices servers, the NPDA server may evaluate a hysteresis of an error and may suggest appropriate actions to its adjacent microservice server such as a policy execution engine (PEEGN). The NF server may use certain commands such as create / modify / delete / view for retrieving such policies and appropriate actions. However, in traditional systems, accomplishing dynamic operations related to different policies within the database servers is time consuming. Therefore, making changes in runtime is also an unsolved challenge for the traditional systems. There does not exist a solution that solves this problem properly and provides seamless operations, and allow changes required at runtime.

[0006] Thus, there exists an imperative need in the art for a system for executing operations on NPDA server, which the present disclosure aims to address.SUMMARY

[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] An aspect of the present disclosure may relate to a method for management of database operations in a network. The method comprises receiving, by a transceiver unit at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit, an event request associated with one or more Network Functions (NFs). Based on the event request, the method further comprises transmitting, by the transceiver unit at the NPDA unit, a request to one or more databases. The method further comprises receiving, by the transceiver unit at the NPDA unit, a response from the one or more databases, wherein the response is generated by the one or more databases based on at least one operation associated with the request. Based on the received response, the method further comprises transmitting, by the transceiver unit at the NPDA unit, an event response.

[0009] In an exemplary aspect of the present disclosure, the event request is received from at least one of a Command Line Interface (CLI), a Graphical User Interface (UI), and an Event Routing Manager (ERM).

[0010] In another exemplary aspect of the present disclosure, the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC).

[0011] In another exemplary aspect of the present disclosure, the one or more databases is a nonrelational database.

[0012] In another exemplary aspect of the present disclosure, the NPDAunit and the one or more databases is communicatively coupled over a NPDA_NS interface.

[0013] In another exemplary aspect of the present disclosure, the at least one operation comprises at least one of creation of a set of data, updating the set of data, fetching the set of data, and deleting the set of data.

[0014] In another exemplary aspect of the present disclosure, the set of data comprises one or more policies related to the error event, hysteresis data related to the error event, evaluated hysteresis result, corrective policies related to the error event, and a combination thereof, associated with one or more Network Functions (NFs).

[0015] In another exemplary aspect of the present disclosure, pursuant to transmission of the event request to one or more databases, the method further comprises receiving, by the transceiver unit, a failure response from said one or more databases, wherein the failure response corresponds to an unavailable status of said one or more databases. Then, based on the received failure response, the method also comprises transmitting, by the transceiver unit, the request to another instance of said one or more databases.

[0016] In another exemplary aspect of the present disclosure, based on the received failure response, the method further comprises generating, by a processing unit, an error notification. Then, based on at least the error notification, the method further comprises generating, by the processing unit, the event response.

[0017] Another aspect of the present disclosure may relate to a system for management of database operations in the network. The system includes a Network Function Virtualisation Platform Decision Analytics (NPDA) unit. The NPDA unit further includes a processing unit and atransceiver unit connected at least to the processing unit. The transceiver unit is configured to receive an event request associated with one or more Network Functions (NFs). Based on the event request, the transceiver unit is further configured to transmit a request to one or more databases. The transceiver unit is further configured to receive a response from the one or more databases. The response is generated by the one or more databases based on at least one operation associated with the request. Based on the received response, the transceiver unit is further configured to transmit an event response.

[0018] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for management of database operations in the network. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit, at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit, of the system to receive an event request associated with one or more Network Functions (NFs). Further, the instructions include executable code which, when executed, causes the transceiver unit, at the NPDA unit, to transmit a request to one or more databases based on the event request. Further, the instructions include executable code which, when executed, causes the transceiver unit, at the NPDA unit, to receive a response from the one or more databases. The response is generated by the one or more databases based on at least one operation associated with the request. Further, the instructions include executable code which, when executed, causes the transceiver unit, at the NPDA unit, to transmit an event response based on the received response.OBJECTS OF THE DISCLOSURE

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

[0020] It is an object of the present disclosure to provide a system and a method for management of database operations in a network.

[0021] It is another object of the present disclosure to provide a system for executing operations on NPDA server.

[0022] It is another object of the present disclosure to provide a solution that is capable to handle large volumes of data at high speed with a scale-out architecture.

[0023] It is yet another object of the present disclosure to provide a solution that is less time consuming and enables easier roll out of updates.

[0024] It is yet another object of the present disclosure to provide a solution that simplifies management of create, read, update and delete (CRUD) operations pertaining to threshold-based policies or restoration policies at a database server.

[0025] It is yet another object of the present disclosure to provide a solution that enables fault tolerance for any event failure.

[0026] It is yet another object of the present disclosure to provide a solution that works in high availability mode, wherein if one database server instance goes down during request processing then next available instance will continue processing the request.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] 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 reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0028] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture / platform.

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

[0030] FIG. 3 illustrates an exemplary block diagram of a system for management of database operations in a network, in accordance with exemplary implementations of the present disclosure.

[0031] FIG.4 illustrates an exemplary environment for implementing the system for management of database operations in the network, in accordance with exemplary implementations of the present disclosure.

[0032] FIG. 5 illustrates a method flow diagram for management of database operations in the network, in accordance with exemplary implementations of the present disclosure.

[0033] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0034] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0035] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0036] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0037] It should be noted that the terms "first", "second", "primary", "secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another.

[0038] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed but could also have additional steps that may not be included in the figures.

[0039] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0040] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

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

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

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

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

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

[0046] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existingproblems in this field of technology by providing method and system of management of database operations in a network.

[0047] The manner in which the database operations are managed in the network, are explained in detail with respect to FIGS. 1-5.

[0048] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture / platform

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

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

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

[0100] , The MANO architecture

[0100] may be used to automatically instantiate the VNFs into the corresponding environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to the platform. In an implementation, the system may comprise a NFV Platform Decision Analytics (NPDA)

[1096] component.

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

[0100] comprises a user interface layer

[0102] , a network function virtualization (NFV) and software defined network (SDN) design function module

[0104] , a platform foundation services module

[0106] , a platform core services module

[0108] and a platform resource adapters and utilities module

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

[0050] The NFV and SDN design function module

[0104] comprises a network manager

[1042] , a VNF catalogue

[1044] , a network services catalogue

[1046] , a network slicing and service chaining manager

[1048] , a physical and virtual resource manager

[1050] and a CNF lifecycle manager

[1052] , The network manager

[1042] may be responsible for deciding on which server of the communication network the microservice may be instantiated. The network manager

[1042] may manage the overall flow of incoming / outgoing requests during interaction with the user. The network manager may have a VNF lifecycle manager and the CNF lifecycle manager in case the network is working utilising the VNF and CNF. The network manager

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

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

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

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

[1050] stores the logical and physical inventory of the VNFs. Just like the network manager

[1042] , the CNF lifecycle manager

[1052] may be similarly used for the CNFs lifecycle management.

[0051] The platforms foundation services module

[0106] comprises a microservices elastic load balancer

[1062] , an identity & access manager

[1064] , a command line interface (CLI)

[1066] , a central logging manager

[1068] , and an event routing manager

[1070] , The microservices elastic load balancer

[1062] may be used for maintaining the load balancing of the request for the services. The identity & access manager

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

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

[1068] may be responsible for keeping the logs of every service. These logs are generated by the MANO platform

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

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

[0052] The platforms core services module

[0108] comprises NFV infrastructure monitoring manager

[1082] , an assure manager

[1084] , a performance manager

[1086] , a policy execution engine

[1088] , a capacity monitoring manager

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

[1092] , a configuration manager & golden configuration template (GCT)

[1094] , an NFV platform decision analytics

[1096] , a platform NoSQL DB

[1098] , a platform schedulers and cron jobs

[1100] , a VNF backup & upgrade manager

[1102] , a micro service auditor

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

[1106] , The NFV infrastructure monitoring manager

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

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

[1086] may be responsible for managing the performance counters. The policy execution engine (PEEGN)

[1088] may be responsible for managing all the policies. The capacity monitoring manager (CMM)

[1090] may be responsible for sending the request to the PEEGN

[1088] , The release management repository (RMR)

[1092] may be responsible for managing the releases and the images of all of the vendor’s network nodes. The configuration manager & GCT

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

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

[1088] , the configuration manager & (GCT)

[1094] and the (NPDA)

[1096] work together. The platform NoSQL DB

[1098] may be a platform database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF. It may be noted that the platform NoSQL DB

[1098] may be just a narrower implementation of the present disclosure, and any other kind of structure for the database may be implemented for the platform database such as relational or non-relational database. The platform schedulers and cron jobs

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

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

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

[0100] may be using the network resources. In such case, the microservice auditor

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

[0100] , The audit assures that the services only run on the MANO platform

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

[1106] may be used for newer instances that are spawning.

[0053] The platform resource adapters and utilities module

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

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

[1124] , a docker service adaptor

[1126] , an OpenStack API adapter

[1128] , and a NFV gateway

[1130] , The platform external API adaptor and gateway

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

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

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

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

[0100] for communication. The OpenStack API adapter

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

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

[0100] ,

[0054] The Docker Service Adapter (DSA)

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

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

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

[0055] FIG. 2 illustrates an exemplary block diagram of a computing device

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

[0200] may also implement a method for management of database operations in the network utilising the system

[0300] , In another implementation, the computing device

[0200] itself implements the method for management of database operations in the network using one or more units configured within the computing device

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

[0056] The computing device

[0200] may include a bus

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

[0204] coupled with bus

[0202] for processing information. The hardware processor

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

[0200] may also include a main memory

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

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

[0204] , The main memory

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

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

[0204] , render the computing device

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

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

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

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

[0204] ,

[0057] A storage device

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

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

[0200] may be coupled via the bus

[0202] to a display

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

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

[0202] for communicatinginformation and command selections to the processor

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

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

[0204] , and for controlling cursor movement on the display

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

[0058] The computing device

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

[0200] causes or programs the computing device

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

[0200] in response to the processor

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

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

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

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

[0206] causes the processor

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

[0059] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

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

[0220] that is connected to a local network

[0222] , For example, the communication interface

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

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

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

[0060] The computing device

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

[0220] and the communication interface

[0218] , In the Internet example, a server

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

[0228] , the ISP

[0226] , the local network

[0222] , a host

[0224] and thecommunication interface

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

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

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

[0061] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for management of database operations in the network, is shown, in accordance with the exemplary implementations of the present disclosure. In one example, the system

[0300] may be implemented as or within a Network Function Virtualization (NFV) Platform Decision Analytics (NPDA) unit. Such NPDA unit may be considered to be similar to the NPDA

[1096] as may be understood in conjunction with the FIG. 1.

[0062] In another example, as depicted in FIG. 3, the system

[0300] may include the NPDA unit

[0302] , The NPDA unit

[0302] may include at least one transceiver unit

[0304] , at least one processing unit

[0306] , and at least one storage unit

[0308] ,

[0063] The system

[0300] may also include additional components in communication with the NPDA unit

[0302] , which have not been depicted in FIG. 3, and would be understood to a person skilled in the art. The explanation for the same has not been provided here again for the sake of brevity.

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

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

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

[0300] may comprise multiple such units or the system

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

[0300] may be present in a user device / user equipment to implement the features of the present disclosure. The system

[0300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0065] The system

[0300] may be configured for management of database operations in the network, with the help of the interconnection between the components / units of the system

[0300] ,

[0066] The system

[0300] may be in communication with other network entities / components, as depicted in FIG. 4. Referring to FIG. 4, an exemplary environment

[0400] for implementing the system

[0300] for management of database operations in the network, in accordance with exemplary implementations of the present disclosure, is shown.

[0067] It may be noted that the FIG. 3 and FIG. 4 are explained in conjunction in the foregoing description for explanation / description of the present disclosure.

[0068] In one example, the system

[0300] may be configured for management of database operations in the network, with the help of the interconnection between the components / units of the environment

[0400] , and in another example, the components / units of the MANO architecture / platform

[0100] ,

[0069] It may be noted that any other network entities / components not depicted in FIG. 4 and known to a person skilled in the art, may also be in communication with the system

[0300] , Such network entities / components have not been depicted in FIGS. 3-4 and not explained here for the sake of brevity.

[0070] As depicted in FIG. 4, the exemplary environment

[0400] may include the system

[0300] , a Graphical User Interface (GUI)

[0402] , a Command Line Interface (CLI), an Event Routing Manager (ERM), and one or more databases

[0404] , As depicted in FIG. 4, the CLI and the ERM may be understood and referred to as the CLI

[1066] and the ERM

[1070] explained in conjunction with FIG. 1. The explanation has not been repeated here for the sake of brevity.

[0071] As described previously, the system

[0300] may include the NPDA unit

[0302] which may be connected with the one or more databases

[0404] via an interface used for communication between the system

[0300] and the one or more databases

[0404] , referred to as NPDA_NS interface

[0406] ,

[0072] As would be understood, the GUI

[0402] may refer to a form of user interface that allows users to interact with electronic devices through graphical icons and visual indicators such as secondary notation, symbols, visual metaphors, and pointing devices, etc. Also, while the environment as shown in the FIG. 4 illustrates the GUI

[0402] , the environment may also comprise a User Interface (UI) connected with a user equipment and such examples of UI may be considered to be within the scope of the environment

[0400] , Similarly, the one or more databases

[0404] mayrefer to an organized collection of data or a type of data store which stores an organized collection of structured information or data such as in a computer system, and such databases may also be referred as repositories.

[0073] In operation, for management of database operations in the network, the transceiver unit

[0304] may receive an event request associated with one or more Network Functions (NFs).

[0074] In an exemplary implementation of the present disclosure, the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC). As used herein, the VNF may refer to software applications that deliver network functions such as directory services, routers, firewalls, load balancers, etc. The CNF may be a component or a software service that fulfils certain network functionalities while adhering to cloud-native design principles without requiring any hardware or appliance to house it. The components used for implementing the VNF may be called as the VNF components (VNFC). The components used for implementing the CNF may be called as the CNF components (CNFC).

[0075] The event request may refer to a request for performance of certain operations in the database and may be received based on an occurrence of certain event. The events may refer to certain conditions based on which the event request may be received, such as error events, requirement of corrective actions, hysteresis analysis event, hysteresis counter event, etc. For example, in a non-limiting exemplary scenario where the PEEGN

[1088] may have stored certain policies in the database, then in such examples, the event request may be a request for fetching such policies such as corrective policies, hysteresis policies. Similarly for storing such policies, the created policies may be sent along with the event request for storing in the repository.

[0076] In some implementations of the present disclosure, the transceiver unit

[0304] may receive the event request from at least one of the Command Line Interface (CLI)

[1066] , the Graphical User Interface (UI)

[0402] , and the Event Routing Manager (ERM)

[1070] , The receiving of the event request from the GUI

[0402] have been indicated by Step 1, in the FIG.4. Similarly, the receiving of the event request from the CLI

[1066] have been indicated by the Step 2, as shown in the FIG. 4. Also, the receiving of the event request from the ERM

[1070] have been indicated by the Step 3, as shown in the FIG. 4.

[0077] In an example, the event request may be received from the GUI

[0402] in a case where a consumer may initiate the event request using the GUI

[0402] , The GUI

[0402] may allow the consumer to interact with the system

[0300] for providing the event request. In such cases, the system

[0300] may handle such event request as per a set of pre-defined network criteria. For example, there may be a scenario of varying permissions for performance of certain operations in the repositories, however, due to some access restrictions, some consumer may not be allowed to perform such operations. The GUI may only allow the consumer to request for the permissible operations.

[0078] In another example, some network operators such as administrators, technical team, developer teams, etc that may be associated with management of network operations, may execute the event request using the CLI

[1066] and may execute certain commands along with the event request. In such cases as well, there may be different scenarios in which the event request comprising some commands may only be executed through such CLIs only, and may not be executed via the GUIs.

[0079] In yet another example, the event request may be received from the ERM

[1070] , which may be routed from certain network function / microservice through the ERM

[1070] , In such cases as well, the event request may be required to be handled accordingly. Hence, in such cases, the present disclosure also encompasses a processor incorporated within the NPDA unit

[0302] , Such processor handles the event request received from different entities such as the GUI

[0402] , the CLI

[1066] the ERM

[1070] , or any other entity, based on certain rules and permissions.

[0080] It may be noted that the aforementioned entities from where the transceiver unit receives the event request is only exemplary, and in no manner is construed to limit the scope of the present subject matter in any manner. The event request may be received from any other network component / entity as well. All such examples would lie within the scope of the present subject matter.

[0081] Continuing further, based on the event request, the transceiver unit

[0304] may transmit a request to one or more databases

[0404] , The request may refer to another request which may be based on the received event request, and may be sent towards the one or more databases

[0404] , In an exemplary implementation of the present disclosure, the one or more databases

[0404] may be a non-relational database. The non-relational database as would be known in the art may refer to a structure of database that does not utilize the tabular schema of rows and columns that may befound in most traditional database systems. A non-limiting example of such non-relational database may include a NoSQL database. In another exemplary implementation of the present disclosure, the one or more databases

[0404] may also be based on a relational database structure based on the requirements of the network operators.

[0082] In order to enable communication between the system

[0300] and the one or more databases

[0404] , an interface NPDA_NS, as described previously, may be used. The interface NPDA_NS may be understood as a communication link or channel, which may allow the one or more databases to communicate and exchange data with the system

[0300] or NPDA unit

[0302] , In an example, the data, obtained by the system

[0300] or the NPDA unit

[0302] by virtue of communication and data exchange with the one or more databases, may be stored in the storage unit

[0308] ,

[0083] In some of the embodiments, the interface that may be used for communication may, in one example, be a Hypertext Transfer Protocol (HTTP) based connection, and may in another example, be a web-socket based connection. In some of the exemplary implementations of the present disclosure, the NPDA NS interface may be configured to facilitate exchange of information using the HTTP- REST Application Programming Interface (API). In another exemplary implementation, the HTTP REST API may be used in conjunction with a JavaScript Object Notation (JSON) format and / or an extensible markup language (XML) format for carrying the information. As would be understood, the web-socket connection may involve establishing a persistent connectivity between the connecting components, such as a transmission control protocol (TCP) connection. In such a connection, information of different components may be exchanged through the interface using a ping-pong-based communication. In such examples, for some information HTTP based connection may be used and for some information web-socket connection as explained in above example and for other type of information exchange, it uses a web-socket connection as explained above.

[0084] Continuing further, the transceiver unit

[0304] may then receive a response from the one or more databases. The response may be generated by the one or more databases based on at least one operation associated with the request. The response may be a reply to the transmitted request based on an execution of the at least one operation.

[0085] For example, the response may indicate a status, for example, success or failure of the at least one operation that may be executed at the one or more databases

[0404] , In another example,the response may also include the result of the at least one operation, along with a success status of the execution of the at least one operation.

[0086] In few exemplary implementations of the present disclosure, the at least one operation associated with the request may include actions such as creating a set of data, updating the set of data, fetching the set of data, and deleting the set of data. As would be understood, the creating of data may refer to a creation of the set of data and then storing such created set of data in the one or more databases

[0404] , thus enabling a write operation. Similarly, the updating the set of data may refer to making certain changes in the already stored data and then updating such sets of data with the information provided in the request, thus enabling an update operation. Again, for fetching the set of data, the one or more set of data already stored in the one or more databases

[0404] may be fetched and transmitted as it is without making any changes, thus enabling a read operation. Likewise, for deleting the set of data, the one or more databases

[0404] may remove the pointers for such sets of data, and may remove the information from the one or more databases

[0404] , thus enabling a delete operation.

[0087] In the above-mentioned exemplary implementations of the present disclosure, the set of data may refer to a data or information which may be used for performing the at least operation associated with the one or more databases

[0404] , The set of data may, in different examples, be one or more policies related to the error event, hysteresis data related to the error event, evaluated hysteresis result, corrective policies related to the error event, and a combination thereof. Such sets of data may be associated with one or more Network Functions (NFs). The one or more policies may refer to the set of rules that are made, for example, to manage database operations, managing the resources and allocation of the resources, and may be generated by the PEEGN

[1088] or a policy control function, or any other entity known to (and obvious to) a person skilled in the art. Further, the hysteresis data related to the error event may refer to the probability of occurrence and the actions and policies that were formed in case of the error events occurred in the past and may also indicate a pattern in the occurrence of the error event and may be used for making decisions based on the past data present in the set of data. After the hysteresis data related to the error event may be evaluated, then the result of the hysteresis for the error event may refer to the evaluated hysteresis result. The corrective policies related to the error event may refer to one or more policies which may provide corrective measures which may be taken in case of the error event and to mitigate the problems caused by the error event. The corrective measures that are required to be taken in a specific error event may be already created, and then stored within the one or more databases in form of the one or more policies.

[0088] In an exemplary aspect of the present disclosure, pursuant to transmission of the event request to one or more databases

[0404] , the transceiver unit

[0304] may also receive a failure response from said one or more databases

[0404] , The failure response corresponds to an unavailable status of said one or more databases

[0404] , Such failure response indicates that a selected database from the one or more databases

[0404] is not available at the moment such as due to errors, busy in operations, etc. In such cases, in order to handle multiple requests, some network operators may have additional backups and spare databases, referred to as another instance of the same database, which may be used for the same operations. Thus, in such cases, based on the received failure response, the transceiver unit

[0304] transmits the request to another instance of said one or more databases

[0404] , Then accordingly such database after performance of the at least one operation may again generate the response. In an example, until the spare or backup databases are exhausted, a loop may be formed which may keep on transmitting the request to other backup or spare databases, until the at least one operation is successfully performed. The present disclosure enables fault tolerance in case of any failures, and provides a solution in which if one instance of a database is down, then the processing of the request may be performed by the next available resource / instance which will take care of such requests, thereby providing high-availability.

[0089] Further, based on the received response, the transceiver unit

[0304] transmits an event response. In an example, the transceiver unit

[0304] may transmit the event response to the GUI

[0402] , this has been depicted by Step 4, in the FIG. 4. In other examples, the event request may also be transmitted to the CLI

[1066] and / or the ERM

[1070] . In order to reply to the event request, the response generated by the one or more databases such as the success response or the failure response or the result of the performance of the at least one operation may be transmitted as the event response. The event response may provide information associated with a success or failure or the event request and may also comprise other information which may be present within the response.

[0090] In an exemplary aspect of the present disclosure, based on the received failure response, the processing unit

[0306] may be configured to generate an error notification, such error notification may provide that the at least one operation was unable to be performed using the one or more databases

[0404] , The error notification may refer to an indication which may be provided to either the GUI

[0402] , the CLI

[1066] , or the ERM

[1070] indicating that the one or more databases

[0404] are not able to perform the at least one operation. Then, based on at least the error notification, the processing unit

[0306] may generate the event response. As provided above, theevent response may indicate a failure of the performance of the at least one operation, and may comprise a message indicating the failure. For example, the event response may comprise an HTTP Status code. The HTTP Status code may include an exemplary status code, ranging from 400 to 499 (indicating error at client side) and 500 to 599 (indicating error at server side).

[0091] Referring to FIG. 5, an exemplary method flow diagram

[0500] for management of database operations in the network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0500] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 5, the method

[0500] starts at step

[0502] ,

[0092] In operation, for management of database operations in the network, at step

[0504] , the method

[0500] involves receiving, by a transceiver unit

[0304] at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit

[0302] , an event request associated with one or more Network Functions (NFs).

[0093] In an exemplary implementation of the present disclosure, the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC). As used herein, the VNF may refer to software applications that deliver network functions such as directory services, routers, firewalls, load balancers, etc. The CNF may be a component or a software service that fulfils certain network functionalities while adhering to cloud-native design principles without requiring any hardware or appliance to house it. The components used for implementing the VNF may be called as the VNF components (VNFC). The components used for implementing the CNF may be called as the CNF components (CNFC).

[0094] The event request may refer to a request for performance of certain operations in the database and may be received based on an occurrence of certain event. The event may refer to certain conditions based on which the event request may be received, such as error events, requirement of corrective actions, hysteresis analysis event, hysteresis counter event, etc. For example, in a non-limiting exemplary scenario where the PEEGN

[1088] may have stored certain policies in the database, then in such examples, the event request may be a request for fetching such policies such as corrective policies, hysteresis policies. Similarly for storing such policies, the created policies may be sent along with the event request for storing in the repository.

[0095] In an implementation of the present disclosure, the event request may be received from at least one of a Command Line Interface (CLI)

[1066] , a Graphical User Interface (UI)

[0402] , and an Event Routing Manager (ERM)

[1070] ,

[0096] In an example, the event request may be received from the GUI

[0402] in a case where a consumer may initiate the event request using the GUI

[0402] , The GUI

[0402] may allow the consumer to interact with the system

[0300] for providing the event request. In such cases, the system

[0300] may handle such event request as per a set of pre-defined network criteria. For example, there may be a scenario of varying permissions for performance of certain operations in the repositories, however, due to some access restrictions, some consumer may not be allowed to perform such operations. The GUI may only allow the consumer to request for the permissible operations.

[0097] In another example, some network operators such as administrators, technical team, developer teams, etc that may be associated with management of network operations, may execute the event request using the CLI

[1066] and may execute certain commands along with the event request. In such cases as well, there may be different scenarios in which the event request comprising some commands may only be executed through such CLIs only, and may not be executed via the GUIs.

[0098] In yet another example, the event request may be received from the ERM

[1070] , which may be routed from certain network function / microservice through the ERM

[1070] , In such cases as well, the event request may be required to be handled accordingly. Hence, in such cases, the present disclosure also encompasses a processor incorporated within the NPDA unit

[0302] , Such processor handles the event request received from different entities such as the GUI

[0402] , the CLI

[1066] the ERM

[1070] , or any other entity, based on certain rules and permissions.

[0099] It may be noted that the aforementioned entities from where the transceiver unit receives the event request is only exemplary, and in no manner is construed to limit the scope of the present subject matter in any manner. The event request may be received from any other network component / entity as well. All such examples would lie within the scope of the present subject matter.

[0100] Continuing further, based on the event request, at step

[0506] , the method

[0500] leads to transmitting, by the transceiver unit

[0304] at the NPDA unit

[0302] , a request to one or more databases

[0404] , The request may refer to another request which may be based on the received event request, and may be sent towards the one or more databases

[0404] , In an exemplary implementation of the present disclosure, the one or more databases

[0404] may be a non-relational database. The non-relational database as would be known in the art may refer to a structure of database that does not utilize the tabular schema of rows and columns that may be found in most traditional database systems. Anon-limiting example of such non-relational database may include a NoSQL database. In another exemplary implementation of the present disclosure, the one or more databases

[0404] may also be based on a relational database structure based on the requirements of the network operators.

[0101] In order to enable communication between the system

[0300] and the one or more databases

[0404] an interface NPDA_NS, as described previously, may be used. The interface may be understood as a communication link or channel, which may allow the one or more databases to communicate and exchange data with the system

[0300] or NPDA unit

[0302] , In an example, the data, obtained by the system

[0300] or the NPDA unit

[0302] by virtue of communication and data exchange with the one or more databases, may be stored in the storage unit

[0308] ,

[0102] In some of the embodiments, the interface that may be used for communication may, in one example, be a Hypertext Transfer Protocol (HTTP) based connection, and may in another example, be a web-socket based connection. In some of the exemplary implementations of the present disclosure, the NPDA NS interface may be configured to facilitate exchange of information using the HTTP- REST Application Programming Interface (API). In another exemplary implementation, the HTTP REST API may be used in conjunction with a JavaScript Object Notation (JSON) format and / or an extensible markup language (XML) format for carrying the information. As would be understood, the web-socket connection may involve establishing a persistent connectivity between the connecting components, such as a transmission control protocol (TCP) connection. In such a connection, information of different components may be exchanged through the interface using a ping-pong-based communication. In such examples, for some information HTTP based connection may be used and for some information web-socket connection as explained in above example and for other type of information exchange, it uses a web-socket connection as explained above.

[0103] Continuing further, at step

[0508] , the method

[0500] involves receiving, by the transceiver unit

[0304] at the NPDAunit

[0302] , a response from the one or more databases

[0404] , The response may be generated by the one or more databases

[0404] based on at least one operation associated with the request. The response may be a reply to the transmitted request based on an execution of the at least one operation.

[0104] For example, the response may indicate a status, for example, success or failure of the at least one operation that may be executed at the one or more databases

[0404] , In another example, the response may also include the result of the at least one operation, along with a success status of the execution of the at least one operation.

[0105] In few exemplary implementations of the present disclosure, the at least one operation associated with the request may include actions such as creating a set of data, updating the set of data, fetching the set of data, and deleting the set of data. As would be understood, the creating of data may refer to a creation of the set of data and then storing such created set of data in the one or more databases

[0404] , thus enabling a write operation. Similarly, the updating the set of data may refer to making certain changes in the already stored data and then updating such sets of data with the information provided in the request, thus enabling an update operation. Again, for fetching the set of data, the one or more set of data already stored in the one or more databases

[0404] may be fetched and transmitted as it is without making any changes, thus enabling a read operation. Likewise, for deleting the set of data, the one or more databases

[0404] may remove the pointers for such sets of data, and may remove the information from the one or more databases

[0404] , thus enabling a delete operation.

[0106] In the above-mentioned exemplary implementations of the present disclosure, the set of data may refer to a data or information which may be used for performing the at least operation associated with the one or more databases

[0404] , The set of data may, in different examples, be one or more policies related to the error event, hysteresis data related to the error event, evaluated hysteresis result, corrective policies related to the error event, and a combination thereof. Such sets of data may be associated with one or more Network Functions (NFs). The one or more policies may refer to the set of rules that are made, for example, to manage database operations, managing the resources and allocation of the resources, and may be generated by the PEEGN

[1088] or a policy control function, or any other entity known to (and obvious to) a person skilled in the art. Further, the hysteresis data related to the error event may refer to the probability of occurrence and the actions and policies that were formed in case of the error events occurred in the past and mayalso indicate a pattern in the occurrence of the error event and may be used for making decisions based on the past data present in the set of data. After the hysteresis data related to the error event may be evaluated, then the result of the hysteresis for the error event may refer to the evaluated hysteresis result. The corrective policies related to the error event may refer to one or more policies which may provide corrective measures which may be taken in case of the error event and to mitigate the problems caused by the error event. The corrective measures that are required to be taken in a specific error event may be already created, and then stored within the one or more databases in form of the one or more policies.

[0107] In an exemplary aspect of the present disclosure, pursuant to transmission of the event request to one or more databases

[0404] , the method

[0500] may also involve receiving, by the transceiver unit

[0304] , a failure response from said one or more databases

[0404] , The failure response corresponds to an unavailable status of said one or more databases

[0404] , The failure response corresponds to an unavailable status of said one or more databases

[0404] , Such failure response indicates that a selected database from the one or more databases

[0404] is not available at the moment such as due to errors, busy in operations, etc. In such cases, in order to handle multiple requests, some network operators may have additional backups and spare databases, referred to as another instance of the same database, which may be used for the same operations. Thus, in such cases, based on the received failure response, the method

[0500] comprises transmitting, by the transceiver unit

[0304] , the request to another instance of said one or more databases

[0404] , Then accordingly such database after performance of the at least one operation may again generate the response. In an example, until the spare or backup databases are exhausted, a loop may be formed which may keep on transmitting the request to other backup or spare databases, until the at least one operation is successfully performed. The present disclosure enables fault tolerance in case of any failures, and provides a solution in which if one instance of a database is down, then the processing of the request may be performed by the next available resource / instance which will take care of such requests, thereby providing high-availability.

[0108] At step

[0510] , based on the received response, the method

[0500] involves transmitting, by the transceiver unit

[0304] at the NPDAunit

[0302] , an event response. In order to reply to the event request, the response generated by the one or more databases such as the success response or the failure response or the result of the performance of the at least one operation may be transmitted as the event response. The event response may provide information associated with a success or failure or the event request and may also comprise other information which may be present within the response.

[0109] In an exemplary aspect of the present disclosure, based on the received failure response, based on the received failure response, generating, by a processing unit

[0306] , an error notification. Such error notification may provide that the at least one operation was unable to be performed using the one or more databases

[0404] , The error notification may refer to an indication which may be provided to either the GUI

[0402] , the CLI

[1066] , or the ERM

[1070] indicating that the one or more databases

[0404] are not able to perform the at least one operation. Then, based on at least the error notification, generating, by the processing unit

[0306] , the event response. As provided above, the event response may indicate a failure of the performance of the at least one operation, and may comprise a message indicating the failure. For example, the event response may comprise an HTTP Status code. The HTTP Status code may include an exemplary status code, ranging from 400 to 499 (indicating error at client side) and 500 to 599 (indicating error at server side).

[0110] Thereafter, at step

[0512] , the method

[0500] may be terminated.[OHl] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for management of database operations in the network. The instructions include executable code which, when executed by one or more units of a system

[0300] , causes a transceiver unit, at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit, of the system to receive an event request associated with one or more Network Functions (NFs). Further, the instructions include executable code which, when executed, causes the transceiver unit, at the NPDA unit, to transmit a request to one or more databases based on the event request. Further, the instructions include executable code which, when executed, causes the transceiver unit, at the NPDA unit, to receive a response from the one or more databases. The response is generated by the one or more databases based on at least one operation associated with the request. Further, the instructions include executable code which, when executed, causes the transceiver unit, at the NPDA unit, to transmit an event response based on the received response.

[0112] As is evident from the above, the present disclosure provides a technically advanced solution for management of database operations in a network. The present solution provides a solution that is capable to handle large volumes of data at high speed with a scale-out architecture. The present disclosure provides a solution that is less time consuming and enables easier roll out of updates. The present disclosure provides a solution that simplifies management of create, read, update and delete (CRUD) operations pertaining to threshold-based policies or restoration policies at a database server. The present disclosure provides a solution that enables fault tolerance for anyevent failure. The present disclosure provides a solution that works in high availability mode, wherein if one database server instance goes down during request processing then next available instance will continue processing the request.

[0113] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0114] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

We Claim:

1. A method for management of database operations in a network, the method comprising: receiving, by a transceiver unit [304] at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit [302], an event request associated with one or more Network Functions (NFs); based on the event request, transmitting, by the transceiver unit [304] at the NPDA unit [302], a request to one or more databases [404]; receiving, by the transceiver unit [304] at the NPDA unit [302], a response from the one or more databases [404], wherein the response is generated by the one or more databases [404] based on at least one operation associated with the request; and based on the received response, transmitting, by the transceiver unit [304] at the NPDA unit [302], an event response.

2. The method as claimed in claim 1, wherein the event request is received from at least one of a Command Line Interface (CLI) [1066], a Graphical User Interface (UI) [402], and an Event Routing Manager (ERM) [1070],3. The method as claimed in claim 1, wherein the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC).

4. The method as claimed in claim 1, wherein the one or more databases [404] is a nonrelational database.

5. The method as claimed in claim 1, wherein the NPDA unit [302] and the one or more databases [404] is communicatively coupled over a NPDA_NS interface [406],6. The method as claimed in claim 1, wherein the at least one operation comprises at least one of creation of a set of data, updating the set of data, fetching the set of data, and deleting the set of data.

7. The method as claimed in claim 6, wherein the set of data comprises one or more policies related to the error event, hysteresis data related to the error event, evaluated hysteresis result,corrective policies related to the error event, and a combination thereof, associated with one or more Network Functions (NFs).

8. The method as claimed in claim 1, further comprising: pursuant to transmission of the event request to one or more databases, receiving, by the transceiver unit [304], a failure response from said one or more databases [404], wherein the failure response corresponds to an unavailable status of said one or more databases [404]; and based on the received failure response, transmitting, by the transceiver unit [304], the request to another instance of said one or more databases [404],9. The method as claimed in claim 8, further comprising: based on the received failure response, generating, by a processing unit [306], an error notification; and based on at least the error notification, generating, by the processing unit [306], the event response.

10. A system [300] for management of database operations in a network, the system [300] comprising a Network Function Virtualisation Platform Decision Analytics (NPDA) unit [302], wherein the NPDA unit [302] comprises: a processing unit [306]; and a transceiver unit [304] connected at least to the processing unit [306], wherein the transceiver unit [304] is configured to: o receive an event request associated with one or more Network Functions (NFs); o based on the event request, transmit a request to one or more databases; o receive a response from the one or more databases, wherein the response is generated by the one or more databases based on at least one operation associated with the request; and o based on the received response, transmit an event response.

11. The system [300] as claimed in claim 10, wherein the transceiver unit [304] is configured to receive the event request from at least one of a Command Line Interface (CLI) [1066], a Graphical User Interface (UI) [402], and an Event Routing Manager (ERM) [1070],12. The system [300] as claimed in claim 10, wherein the Network Function (NF) is one of Virtual Network Function (VNF), Container Network Function (CNF), and a combination thereof, wherein the VNF comprises one or more VNF components (VNFC) and the CNF comprises one or more CNF components (CNFC).

13. The system [300] as claimed in claim 10, wherein the one or more databases is a nonrelational database.

14. The system [300] as claimed in claim 10, wherein the NPDA unit [302] and the one or more databases [404] is communicatively coupled over a NPDA_NS interface [406],15. The system [300] as claimed in claim 10, wherein the at least one operation comprises at least one of creation of a set of data, updating the set of data, fetching the set of data, and deleting the set of data.

16. The system [300] as claimed in claim 15, wherein the set of data comprises one or more policies related to the error event, hysteresis data related to the error event, evaluated hysteresis result, corrective policies related to the error event, and a combination thereof, associated with one or more Network Functions (NFs).

17. The system [300] as claimed in claim 10, wherein the transceiver unit is further configured to: pursuant to transmission of the event request to one or more databases [404], receive a failure response from said one or more databases [404], wherein the failure response corresponds to an unavailable status of said one or more databases [404]; and based on the received failure response, transmit the request to another instance of said one or more databases.

18. The system [300] as claimed in claim 17, wherein the processing unit [306] is further configured to: based on the received failure response, generate an error notification; and based on at least the error notification, generate the event response.

19. A non-transitory computer-readable storage medium storing instructions for management of database operations in a network, the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [304], at a Network Function Virtualisation Platform Decision Analytics (NPDA) unit [302], to receive an event request associated with one or more NetworkFunctions (NFs); the transceiver unit [304], at the NPDA unit [302], to transmit a request to one or more databases [404] based on the event request; the transceiver unit [304], at the NPDA unit [302], to receive a response from the one or more databases [404], wherein the response is generated by the one or more databases[404] based on at least one operation associated with the request; and the transceiver unit [304], at the NPDA unit [302], to transmit an event response based on the received response.

Images