Method And System For Executing Operations On An Auditor Node Using A User Interface (Ui)

Jio Platforms Limited
Awaiting Request for Examination App No 202321065808 Computer Science

Patent information

IP India · live record
Application number
202321065808
Filing date
29 September 2023
Status
Awaiting Request for Examination
Publication number
20/2025
Publication type
INA
Invention field
Computer Science

Abstract

The present disclosure relates to a method and a system for executing operations on an auditor node [300A] using a user interface (UI) [202]. The present disclosure encompasses receiving, by a transceiver unit [302] from the user interface [202], a request in a pre-defined format based on at least command. The request is received at the auditor node [300A] over an interface network. The method further comprises executing, by a processing unit [304], at least one operation in response to receipt of the at least one command at the auditor node [300A]. [FIG. 3]

Applicants

1
India
Jio Platforms Limited Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.

Inventors

18
India
Aayush BhatnagarReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Ankit MurarkaReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Rizwan AhmadReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Kapil GillReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Arpit JainReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Shashank BhushanReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Jugal KishoreReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Meenakshi SarohiReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Kumar DebashishReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Supriya Kaushik DeReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Gaurav KumarReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Kishan SahuReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Gaurav SaxenaReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Vinay GaykiReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Mohit BhanwriaReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Durgesh KumarReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Rahul KumarReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.
India
Kunal TelgoteReliance Corporate Park, Thane-Belapur Road, Ghansoli, Navi Mumbai, Maharashtra 400701, India.

Claims

12
1 A method for executing operations on an auditor node [300A] using a user interface (UI) [202], the method comprising: 5 - receiving, by a transceiver unit [302] from the user interface [202], a request in a pre-defined format based on at least command, wherein the request is received at the auditor node [300A] over an interface network; and - executing, by a processing unit [304], at least one operation in response 10 to receipt of the at least one command at the auditor node [300A].
2 The method as claimed in claim 1, wherein the user interface (UI) [202] is a Command Line Interface (CLI). 15 3. The method as claimed in claim 1, wherein the request is a hypertext transfer (HTTP) request.
4 The method as claimed in claim 1, wherein the pre-defined format is JSON format. 20
5 The method as claimed in claim 1, wherein prior to receiving the request, the method comprises: receiving, at the user interface (UI) [202], at least one command for executing operations on the auditor node [300A], wherein the at least one 25 command relates to at least one of registering or deregistering with an orchestration manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms; and converting, at the user interface (UI) [202], the received at least one command to the predefined format. 28
6 The method as claimed in claim 5, wherein prior to receiving the at least one command, the method comprises: - requesting, at the UI [202], credentials of a user; 5 - receiving, at the UI [202], the credentials of the user; and - validating, at the UI [202], the credentials of the user, wherein in response to successful validation of the credentials of the user, the at least one command is received. 10 7. The method as claimed in claim 1, wherein the interface is an AU_CL interface.
8 A system for executing operations on an auditor node [300A] using a user interface (UI) [202], the system comprising: 15 - a transceiver unit [302] configured to receive, from the user interface (UI) [202], a request in a pre-defined format based on at least command, wherein the request is received at the auditor node [300A] over a network; and - a processing unit [304] connected to at least one transceiver unit [302], 20 wherein the processing unit [304] configured to execute at least one operation in response to receipt of the at least one command at the auditor node [300A].
9 The system as claimed in claim 8, wherein the user interface (UI) [202] is a 25 Command Line Interface (CLI).
10 The system as claimed in claim 8, wherein the request is a hypertext transfer (HTTP) request. 29
11 The system as claimed in claim 8, wherein the pre-defined format is JSON format.
12 The system as claimed in claim 8, wherein prior to receiving the request, the 5 system comprises: a user interface (UI) [202] configured to receive at least one command for executing operations on the auditor node [300A], wherein the at least one command relates to at least one of registering or deregistering with an orchestration manager, configuring runtime parameters, and 10 monitoring performance counters and severity-based alarms; and the user interface (UI) [202] configured to convert the received at least one command to the predefined format.
13 The system as claimed in claim 12, wherein prior to receiving the at least 15 one command, the system comprises: - the UI [202] to request credentials of a user; - the UI [202] to receive the credentials of the user; and - the UI [202] to validate the credentials of the user, wherein in response to successful validation of the credentials of the user, the at least one 20 command is received.
14 The system as claimed in claim 8, wherein the interface is an AU_CL interface. 25 15. A user equipment (UE) for executing operations on an auditor node using a user interface (UI), the UE comprising: - the user interface (UI) configured to: o receive at least one command for executing operations on the auditor node, wherein the at least one command relates to at least 30 one of registering or deregistering with an orchestration 30 manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms; and o convert the received at least one command to a predefined format; and 5 o transmit a request in the pre-defined format to the auditor node based on the at least one command.

Specification

Show full textCollapse

FORM 2 THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003 COMPLETE SPECIFICATION (See section 10 and rule 13) “METHOD AND SYSTEM FOR EXECUTING OPERATIONS ON AN AUDITOR NODE USING A USER INTERFACE (UI)” We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India. The following specification particularly describes the invention and the manner in which it is to be performed. 2 METHOD AND SYSTEM FOR EXECUTING OPERATIONS ON AN AUDITOR NODE USING A USER INTERFACE (UI) FIELD OF THE DISCLOSRE 5

[0001] Embodiments of the present disclosure relate generally to the field of wireless communication systems. More particularly, embodiment of the present disclosure relates to a method and system for executing operations on an auditor node using a user interface (UI). 10 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 15 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. 20 [0003] In communication network such as 5G communication network, different microservices perform different services and functionalities as per configurations and operational parameters. The microservice takes up the configuration details from spreadsheets at bootup. After the microservices goes active, if any change is required in the configuration, there is a need to first stop the microservice, perform 25 changes manually, and finally restart the microservice for implementing the changes. These changes impact service, since the microservice has to be stopped from running. Further, to check fault, configuration, accounting, performance and security (FCAPS) and operational efficiency counters of microservices is cumbersome and time-consuming. The existing available solutions are not efficient 30 for measuring microservices performance and implementing the configuration changes for microservices for updates based on the requirement. 3

[0004] Thus, there exists an imperative need in the art to provide an efficient system and method for updating microservices resources and configuration parameters without stopping active or running microservices, which the present disclosure aims 5 to address. SUMMARY

[0005] This section is provided to introduce certain aspects of the present disclosure 10 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.

[0006] An aspect of the present disclosure may relate to a method for executing 15 operations on an auditor node using a user interface (UI), the method comprising receiving, by a transceiver unit from the user interface, a request in a pre-defined format based on at least command, wherein the request is received at the auditor node over an interface network. The method further comprises executing, by a processing unit, at least one operation in response to receipt of the at least one 20 command at the auditor node.

[0007] In an exemplary aspect of the present disclosure, the user interface (UI) is a Command Line Interface (CLI). 25 [0008] In an exemplary aspect of the present disclosure, the request is a hypertext transfer (HTTP) request.

[0009] In an exemplary aspect of the present disclosure, the pre-defined format is JSON format. 30 4

[0010] In an exemplary aspect of the present disclosure, prior to receiving the request, the method comprises receiving, at the user interface (UI), at least one command for executing operations on the auditor node, wherein the at least one command relates to at least one of registering or deregistering with an orchestration 5 manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms. The method further comprises converting, at the user interface (UI), the received at least one command to the predefined format.

[0011] In an exemplary aspect of the present disclosure, prior to receiving the at 10 least one command, the method comprises requesting, at the UI, credentials of a user. The method further comprises receiving, at the UI, the credentials of the user. Furthermore, the method comprises validating, at the UI, the credentials of the user, wherein in response to successful validation of the credentials of the user, the at least one command is received. 15

[0012] In an exemplary aspect of the present disclosure, the interface is an AU_CL interface.

[0013] Another aspect of the present disclosure may relate to a system for executing 20 operations on an auditor node using a user interface (UI), the system comprising a transceiver unit configured to receive, from the user interface (UI), a request in a pre-defined format based on at least command, wherein the request is received at the auditor node over a network. The system further comprises a processing unit connected to at least one transceiver unit, wherein the processing unit configured to 25 execute at least one operation in response to receipt of the at least one command at the auditor node.

[0014] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for executing operations on 30 an auditor node using a user interface (UI), the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit 5 to receive, from the user interface (UI), a request in a pre-defined format based on at least command, wherein the request is received at the auditor node over a network. Further, the instructions include executable code which, when executed causes a processing unit to execute at least one operation in response to receipt of 5 the at least one command at the auditor node.

[0015] Yet another aspect of the present disclosure may relate to a user equipment (UE) for executing operations on an auditor node using a user interface (UI), the UE comprising: the user interface (UI) configured to: receive at least one command 10 for executing operations on the auditor node, wherein the at least one command relates to at least one of registering or deregistering with an orchestration manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms; and convert the received at least one command to a predefined format; and transmit a request in the pre-defined format to the auditor 15 node based on the at least one command. OBJECTS OF THE DISCLOSURE

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

[0017] It is an object of the present disclosure to provide a system and a method for executing operations on an auditor node using a user interface (UI). 25 [0018] It is another object of the present disclosure to provide a system and a method for updating microservice configuration parameters using AU_CL interface.

[0019] It is yet another object of the present disclosure to provide a system and a 30 method for asynchronous event-based implementation to utilize AU_CL interface efficiently. 6

[0020] It is yet another object of the present disclosure to provide a system and a method for performing fault tolerance for any event failure by AU_CL interface in a high availability mode. 5 DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods 10 and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system 15 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. 20 [0022] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture.

[0023] 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 25 exemplary implementation of the present disclosure.

[0024] FIG. 3 illustrates an exemplary block diagram of a system for executing operations on an auditor node using a user interface (UI), in accordance with exemplary implementations of the present disclosure. 30 7

[0025] FIG. 4 illustrates an exemplary flow diagram for executing operations on the auditor node using the user interface (UI), in accordance with exemplary implementations of the present disclosure. 5 [0026] FIG. 5 illustrates a method flow diagram for executing operations on the auditor node using the user interface (UI), in accordance with exemplary implementations of the present disclosure.

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

[0028] In the following description, for the purposes of explanation, various 15 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 20 address any of the problems discussed above or might address only some of the problems discussed above.

[0029] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, 25 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. 30 8

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

[0031] 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 10 diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. 15

[0032] 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 20 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 25 similar to the term “comprising” as an open transition word—without precluding any additional or other elements.

[0033] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for 30 processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality 9 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, 5 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.

[0034] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, 10 “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart 15 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. 20

[0035] 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”), 25 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. 30 [0036] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information 10 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. 5

[0037] 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 10 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.

[0038] As used herein, the transceiver unit include at least one receiver and at least 15 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.

[0039] As discussed in the background section, the current known solutions have 20 several shortcomings. The present disclosure aims to overcome the abovementioned and other existing problems in this field of technology by providing a method and system for executing operations on an auditor node using a user interface (UI). 25 [0040] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0041] FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture/platform [100], in accordance 30 with exemplary implementation of the present disclosure. The MANO architecture

[100] may be developed for managing telecom cloud infrastructure automatically, 11 managing design or deployment design, managing instantiation of a network node(s) etc/service(s). The MANO architecture [100] 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 5 comprise one or more components of the MANO architecture [100]. The MANO architecture [100] 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] 10 component.

[0042] As shown in FIG. 1, the MANO architecture [100] comprises a user interface layer [102], a network function virtualization (NFV) and software defined network (SDN) design function module [104], a platform foundation services 15 module [106], a platform core services module [108] and a platform resource adapters and utilities module [112] 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. 20 [0043] The NFV and SDN design function module [104] comprises a VNF lifecycle manager [1042], a VNF catalog [1044], a network services catalog [1046], a network slicing and service chaining manager [1048], a physical and virtual resource manager [1050] and a CNF lifecycle manager [1052]. The VNF lifecycle manager [1042] may be responsible for deciding on which server of the 25 communication network the microservice may be instantiated. The VNF lifecycle manager [1042] may manage the overall flow of incoming/ outgoing requests during interaction with the user. The VNF lifecycle 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 30 as a 5G network), sequence for execution of processes P1 and P2 etc. The VNF catalog [1044] stores the metadata of all the VNFs (also CNFs in some cases). The 12 network services catalog [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 5 virtual resource manager [1050] stores the logical and physical inventory of the VNFs. Just like the VNF lifecycle manager [1042], the CNF lifecycle manager

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

[0044] The platforms foundation services module [106] comprises a microservices 10 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 15 (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 [100]. These logs may be used for debugging purposes. The event routing manager [1070] may be responsible for routing the events i.e., the 20 application programming interface (API) hits to the corresponding services.

[0045] The platforms core services module [108] 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 25 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 30 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 13

[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 (PEE) [1088] may be responsible for managing all the policies. The capacity monitoring manager (CMM) 5 [1090] may be responsible for sending the request to the PEE [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] manages the configuration and GCT of all the vendors. The NFV platform decision analytics (NPDA) [1096] helps in deciding the priority of 10 using the network resources. It is further noted that the policy execution engine (PEE) [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 15 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 20 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 [100] may be using the network resources. In such case, the microservice auditor [1104] audits and informs the same so that resources can 25 be released for services running in the MANO architecture [100]. The audit assures that the services only run on the MANO platform [100]. The platform operations, administration and maintenance manager [1106] may be used for newer instances that are spawning. 30 [0046] The platform resource adapters and utilities module [112] further comprises a platform external API adaptor and gateway [1122], a generic decoder and indexer 14 (XML, CSV, JSON) [1124], a docker service adaptor [1126], an API adapter [1128], and a NFV gateway [1130]. The platform external API adaptor and gateway [1122] may be responsible for handling the external services (to the MANO platform

[100]) that requires the network resources. The generic decoder and indexer (XML, 5 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 [100] for communication. The Docker Service Adapter (DSA) is a microservices-based system designed to deploy and manage Container Network Functions (CNFs) and 10 their components (CNFCs) across Docker nodes. It offers REST endpoints for key operations, including uploading container images to a Docker registry, terminating CNFC instances, and creating Docker volumes and networks. CNFs, which are network functions packaged as containers, may consist of multiple CNFCs. The DSA facilitates the deployment, configuration, and management of these 15 components by interacting with Docker's API, ensuring proper setup and scalability within a containerized environment. This approach provides a modular and flexible framework for handling network functions in a virtualized network setup.

[0047] The API adapter [1128] may be used to connect with the virtual machines 20 (VMs). The NFV gateway [1130] may be responsible for providing the path to each services going to/incoming from the MANO architecture [100].

[0048] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in 25 accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for executing operations on an auditor node using a user interface (UI) utilising the system. In another implementation, the computing device [200] itself implements the method for executing operations on the auditor node using the user interface 30 (UI) using one or more units configured within the computing device [200], wherein 15 said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0049] The computing device [200] may include a bus [202] or other 5 communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a randomaccess memory (RAM), or other dynamic storage device, coupled to the bus [202] 10 for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special15 purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204]. 20 [0050] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for 25 displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor

[204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction 30 information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees 16 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.

[0051] The computing device [200] may implement the techniques described 5 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more 10 sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present 15 disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0052] The computing device [200] also may include a communication interface

[218] coupled to the bus [202]. The communication interface [218] provides a two20 way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] 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 [218] may be a 25 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 [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information. 30 17

[0053] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the 5 ISP [226], the local network [222], the host [224] and the communication interface

[218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution. 10 [0054] Referring to FIG. 3, an exemplary block diagram of a system [300] for executing operations on an auditor node [300A] using the user interface (UI) [202], is shown, in accordance with exemplary implementations of the present disclosure. In an example, the system [300] may be implemented as or within the auditor unit. In the context of the present invention, the auditor unit may be understood as the 15 processing entity responsible for overseeing, managing, and auditing network components within a system.

[0055] The system [300] comprises at least one transceiver unit [302], at least one processing unit [304], and at least one storage unit [306]. Also, all of the 20 components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in FIG. 3, all units shown within the system [300] should also be assumed to be connected to each other. Also, in Figure 3, only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as 25 required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment

[202] to implement the features of the present disclosure. The system [300] may be a part of the user device [202]/ or may be independent of but in communication with the user device [202] (may also referred herein as a UE). In another 30 implementation, the system [300] may reside in a server or a network entity. In yet 18 another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.

[0056] FIG. 4 illustrates an exemplary flow diagram [400] for executing operations 5 on the auditor node [300A] using the user interface (UI), in accordance with exemplary implementations of the present disclosure. It may be noted that FIG. 3 and FIG. 4 have been explained simultaneously and may be read in conjunction with each other. 10 [0057] In one implementation, the auditor node [300A] may be in communication with other network entities/components depicted in FIG. 4. It may be noted that FIG. 4 may also include other network entities/components known to a person skilled in the art and may also be in communication with the auditor unit. Such network entities/components have not been explained here for the sake of brevity. 15 In one implementation, the auditor node [300A] refers to a component within the system [300] responsible for handling auditing functions.

[0058] The system [300] is configured for executing operations on the auditor node [300A] using the user interface (UI), with the help of the interconnection between 20 the components/units of the system [300].

[0059] The transceiver unit [302] is configured to receive, from the user interface (UI) [202], a request in a pre-defined format. The request is received based on at least one command. The request is received at the auditor node [300A] over a 25 network using REST API communication. In one implementation, the user interface (UI) [202] is a Command Line Interface (CLI). In one implementation, the request is a hypertext transfer (HTTP) request.

[0060] In general, use of an HTTP request enables continuous communication over 30 the network, as HTTP is a standard protocol for data exchange across web-based networks. When the transceiver unit [302] transmits the command in the form of an 19 HTTP request, the request includes a method (e.g., GET, POST, PUT, DELETE, etc.), headers, and the body containing the command data in a predefined format (such as JSON or XML). 5 [0061] In one implementation, prior to receiving the request, the user interface (UI)

[202] may receive at least one command for executing operations on the auditor node [300A] (i.e., STEP 402). The at least one command relates to at least one of registering or deregistering with an orchestration manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms. In one 10 implementation, the user interface (UI) [202] may convert the received at least one command to the predefined format.

[0062] In general, register operation is used to enrol the auditor node [300A] with the system [300]. The UI [202] receives a ‘register’ command from the user. The 15 command includes parameters such as the auditor node's identification, network details, and any other information required to establish communication.

[0063] In general, deregister operation is used to remove the auditor node [300A] from the system [300]. The UI [202] receives the ‘deregister’ command from the 20 user. The deregister command may include identification details for the auditor node [300A] to be deregistered. The deregister operation removes the auditor node [300A] from the orchestration manager.

[0064] In general, configuration operation sets or modifies the runtime parameters 25 and settings for the auditor node [300A]. The UI [202] receives a configuration command containing parameters such as host information, IP addresses, ports, thresholds, or other runtime configurations. This operation alters the operational parameters of the auditor node [300A]. 30 [0065] In general, counter operation monitors and retrieves performance metrics or counters from the auditor node. The UI [202] receives a counter command 20 requesting performance metrics (e.g., CPU usage, memory consumption, or network throughput). This operation allows users to monitor the performance and health of the auditor node [300A] in real time. 5 [0066] In general, alarm operation involves setting up or monitoring of severitybased alarms for the auditor node [300A]. The UI [202] receives an ‘alarm’ command to configure alarm thresholds or to monitor existing alarms. This operation enables proactive monitoring by alerting the user when certain conditions are met, or thresholds are breached. 10

[0067] In general, audit operation involves auditing or reviewing the activities and logs of the auditor node [300A] for compliance or troubleshooting purposes. This operation provides understanding about the activities performed on the auditor node [300A], helping in compliance verification, security checks, or troubleshooting. 15

[0068] In particular, the user interface (UI) [202] enables a user to interact with the auditor node [300A] by sending commands that trigger various operations on the auditor node [300A]. These commands include, but not limited to, registering or deregistering with the orchestration manager, configuring runtime parameters, and 20 monitoring performance counters and severity-based alarms.

[0069] Accordingly, the UI [202] is configured to translate each command into the predefined format before forwarding it to the auditor node [300A]. In one implementation, the pre-defined format is JSON format. 25

[0070] In an implementation, prior to receiving the at least one command, the system [300] is configured to validate credentials of a user. The user herein may represent an individual or a group of people that have access to the UI [202]. Initially, the UI [202] is configured to request credentials of the user. Further, the 30 UI [202] receives the credentials of the user. In particular, the user may enter the credentials via the UI [202]. Once the credentials are entered, the UI [202] is 21 configured to validate the credentials of the user. In response to successful validation of the credentials of the user, the at least one command is received. In response to unsuccessful validation of the credentials of the user, the UI [202] does not allow the user to send the at least one command. 5

[0071] For example, the UI [202] may request the credentials of the user. The credentials may include a username and password or other similar authentication data. Further, the UI [202] receives the credentials entered by the user and initiates the validation process. The UI [202] checks whether the provided credentials match 10 against an existing authentication value stored in a database [310] to confirm the user’s identity and access rights. In response to successful validation of the credentials, the UI [202] receives the at least one command.

[0072] Upon successful validation of the user, the UI [202] converts the at least one 15 command into the predefined format suitable for transmission.

[0073] The request is transmitted over the interface network to the auditor node [300A] using Representational State Transfer (REST) API communication, which is a standard protocol for exchanging information over the web (i.e., STEP 404). 20

[0074] In one embodiment, the interface network is an AU_CL interface.

[0075] In one implementation, the user (e.g., system administrator, network operator, etc.) interacts with the system [300] through text-based commands entered 25 via the CLI.

[0076] The processing unit [304] is then configured to execute at least one operation in response to receipt of the at least one command at the auditor node [300A]. 30 22

[0077] Once the request is received via the transceiver unit [302] at the auditor node [300A], the processing unit [304] is configured to process the request to identify the specific command and associated parameters. In particular, the execution of the command by the processing unit [304] is performed in a manner that line up with 5 the predefined logic and parameters associated with the requested operation.

[0078] In an example, if the request relates to a ‘register’ operation, the processing unit [304] is configured to process this registration request, validate the provided information, and then register itself with the system [300]. 10

[0079] In another example, if the command relates to a ‘deregister’ operation, the processing unit [304] is configured to process the request, verify the node's existence, and perform the deregistration operation. 15 [0080] In yet another example, if the command relates to a ‘configuration operation’, the processing unit [304] is configured to execute this configuration request and adjust the settings as specified in the command.

[0081] In yet another example, if the command relates to a ‘counter’ operation, the 20 processing unit [304] is configured to collect the requested performance counters and send them back to the UI [202].

[0082] In yet another example, if the request is related to setting an ‘alarm’, the processing unit [304] is configured to process this request by either setting alarm 25 thresholds (e.g., when CPU usage exceeds 90%) or by providing current alarm statuses.

[0083] In yet another example, if the command relates to an ‘audit’ operation, the processing unit [304] is configured to retrieve the requested audit logs, which may 30 include command history, configuration changes, resource information in inventory and real-time or system events. 23

[0084] The response to each executed command may be transmitted back to the UI

[202]. 5 [0085] Once the processing unit [304] completes the execution of the operation, the results, relevant data, or logs generated during the execution are transmitted to the database [310] by the storage unit [306] (i.e., STEP 406). The storage unit [306] acts as a centralized repository for storing all data related to the operations performed by the auditor node [300A]. 10

[0086] Referring to FIG. 5, an exemplary method flow diagram [500] for executing operations on the auditor node [300A] using the user interface (UI), in accordance with exemplary implementations of the present disclosure is shown. In an implementation, the method [500] is performed by the system [300]. In an 15 implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 5, the method [500] starts at step [502].

[0087] At step [504], the method [500] comprises receiving, by the transceiver unit 20 [302] from the user interface (UI) [202], the request in the pre-defined format based on at least one command. The request is received at the auditor node [300A] over the interface network. In an implementation, the user interface (UI) is a Command Line Interface (CLI). In another implementation, the user interface (UI) is a Graphical User Interface (GUI). The request is a hypertext transfer (HTTP) request. 25 The pre-defined format is JSON format.

[0088] Prior to receiving the request, the method [500] comprises receiving, at the user interface (UI) [202], at least one command for executing operations on the auditor node [300A]. The at least one command relates to at least one of registering 30 or deregistering with the orchestration manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms. The method [500] 24 also comprises converting, at the user interface (UI) [202], the received at least one command to the predefined format.

[0089] Prior to receiving the at least one command, the method [500] comprises 5 requesting, at the UI [202], credentials of a user. The method [500] further comprises receiving, at the UI [202], the credentials of the user. Furthermore, the method [500] comprises validating, at the UI [202], the credentials of the user. In response to successful validation of the credentials of the user, the at least one command is received. The interface network is an AU_CL interface. 10

[0090] At step [506], the method [500] comprises executing, by the processing unit

[304], at least one operation in response to receipt of the at least one command at the auditor node [300A]. 15 [0091] Thereafter, the method [500] terminates at step [508].

[0092] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for executing operations on an auditor node [300A] using a user interface (UI) [202], the instructions include executable code 20 which, when executed by one or more units of a system, causes: a transceiver unit

[302] to receive, from the user interface (UI) [202], a request in a pre-defined format based on at least one command, wherein the request is received at the auditor node [300A] over a network. Further, the instructions include executable code which, when executed causes a processing unit [304] to execute at least one operation in 25 response to receipt of the at least one command at the auditor node [300A].

[0093] The present disclosure also discloses a user equipment (UE) (e.g., the computing device [200]) for executing operations on the auditor node [300A] using the user interface (UI) [202], the UE [200] comprising: the user interface (UI) [202] 30 configured to: receive at least one command for executing operations on the auditor node [300A], wherein the at least one command relates to at least one of registering 25 or deregistering with an orchestration manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms; and convert the received at least one command to a predefined format; and transmit a request in the pre-defined format to the auditor node [300A] based on the at least one command. 5

[0094] As is evident from the above, the present disclosure provides a technically advanced solution for executing operations on the auditor node using the user interface (UI). The present disclosure provides a solution, which uses Auditor Service microservice and Command Line Interface with AU_CL interface. Auditor 10 service (AU) audits the resources in terms of physical memory, RAM and CPU at Inventory Manager (IM). It may bring inventory in close sync with real time available/used resources and minimizes the mismatch between Inventory Manager (IM) and real time hardware. AU interacts with the microservices to fetch the real time data using various APIs. 15

[0095] The present solution monitors FCAPS of auditor services and configuration required restricted parameters for seamless operations at runtime, using AU_CL interface. Through AU_CL interface, all CLI related operations at AU can be performed. The present solution does not impact other microservices or there is no 20 downtime for microservices. The solution does not require manual updating of real time configuration changes and take lesser time for implementing the configuration changes. The present solution enables a user to change admin level configuration parameters using CLI. 25 [0096] 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 30 be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting. 26

[0097] 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 5 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 10 functionality described herein, are considered to be encompassed within the scope of the present disclosure. 27 We Claim: 1. A method for executing operations on an auditor node [300A] using a user interface (UI) [202], the method comprising: 5 - receiving, by a transceiver unit [302] from the user interface [202], a request in a pre-defined format based on at least command, wherein the request is received at the auditor node [300A] over an interface network; and - executing, by a processing unit [304], at least one operation in response 10 to receipt of the at least one command at the auditor node [300A]. 2. The method as claimed in claim 1, wherein the user interface (UI) [202] is a Command Line Interface (CLI). 15 3. The method as claimed in claim 1, wherein the request is a hypertext transfer (HTTP) request. 4. The method as claimed in claim 1, wherein the pre-defined format is JSON format. 20 5. The method as claimed in claim 1, wherein prior to receiving the request, the method comprises: receiving, at the user interface (UI) [202], at least one command for executing operations on the auditor node [300A], wherein the at least one 25 command relates to at least one of registering or deregistering with an orchestration manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms; and converting, at the user interface (UI) [202], the received at least one command to the predefined format. 28 6. The method as claimed in claim 5, wherein prior to receiving the at least one command, the method comprises: - requesting, at the UI [202], credentials of a user; 5 - receiving, at the UI [202], the credentials of the user; and - validating, at the UI [202], the credentials of the user, wherein in response to successful validation of the credentials of the user, the at least one command is received. 10 7. The method as claimed in claim 1, wherein the interface is an AU_CL interface. 8. A system for executing operations on an auditor node [300A] using a user interface (UI) [202], the system comprising: 15 - a transceiver unit [302] configured to receive, from the user interface (UI) [202], a request in a pre-defined format based on at least command, wherein the request is received at the auditor node [300A] over a network; and - a processing unit [304] connected to at least one transceiver unit [302], 20 wherein the processing unit [304] configured to execute at least one operation in response to receipt of the at least one command at the auditor node [300A]. 9. The system as claimed in claim 8, wherein the user interface (UI) [202] is a 25 Command Line Interface (CLI). 10. The system as claimed in claim 8, wherein the request is a hypertext transfer (HTTP) request. 29 11. The system as claimed in claim 8, wherein the pre-defined format is JSON format. 12. The system as claimed in claim 8, wherein prior to receiving the request, the 5 system comprises: a user interface (UI) [202] configured to receive at least one command for executing operations on the auditor node [300A], wherein the at least one command relates to at least one of registering or deregistering with an orchestration manager, configuring runtime parameters, and 10 monitoring performance counters and severity-based alarms; and the user interface (UI) [202] configured to convert the received at least one command to the predefined format. 13. The system as claimed in claim 12, wherein prior to receiving the at least 15 one command, the system comprises: - the UI [202] to request credentials of a user; - the UI [202] to receive the credentials of the user; and - the UI [202] to validate the credentials of the user, wherein in response to successful validation of the credentials of the user, the at least one 20 command is received. 14. The system as claimed in claim 8, wherein the interface is an AU_CL interface. 25 15. A user equipment (UE) for executing operations on an auditor node using a user interface (UI), the UE comprising: - the user interface (UI) configured to: o receive at least one command for executing operations on the auditor node, wherein the at least one command relates to at least 30 one of registering or deregistering with an orchestration 30 manager, configuring runtime parameters, and monitoring performance counters and severity-based alarms; and o convert the received at least one command to a predefined format; and 5 o transmit a request in the pre-defined format to the auditor node based on the at least one command.

Documents

Sign in to open
Application documents
1 202321065808-STATEMENT OF UNDERTAKING (FORM 3) [29-09-2023(online)].pdf 29 Sep 2023
2 202321065808-PROVISIONAL SPECIFICATION [29-09-2023(online)].pdf 29 Sep 2023
3 202321065808-POWER OF AUTHORITY [29-09-2023(online)].pdf 29 Sep 2023
4 202321065808-FORM 1 [29-09-2023(online)].pdf 29 Sep 2023
5 202321065808-FIGURE OF ABSTRACT [29-09-2023(online)].pdf 29 Sep 2023
6 202321065808-DRAWINGS [29-09-2023(online)].pdf 29 Sep 2023
7 202321065808-Proof of Right [06-02-2024(online)].pdf 06 Feb 2024
8 202321065808-FORM-5 [29-09-2024(online)].pdf 29 Sep 2024
9 202321065808-ENDORSEMENT BY INVENTORS [29-09-2024(online)].pdf 29 Sep 2024
10 202321065808-DRAWING [29-09-2024(online)].pdf 29 Sep 2024
11 202321065808-CORRESPONDENCE-OTHERS [29-09-2024(online)].pdf 29 Sep 2024
12 202321065808-COMPLETE SPECIFICATION [29-09-2024(online)].pdf 29 Sep 2024
13 Abstract.jpg 11 Nov 2024
14 202321065808-ORIGINAL UR 6(1A) FORM 1 & 26-200125.pdf 24 Jan 2025