1
FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
5 THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
10 “METHOD AND SYSTEM FOR DISCOVERY MANAGEMENT
OF ONE OR MORE MICROSERVICES”
15 We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre
Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
20
The following specification particularly describes the invention and the manner in
which it is to be performed.
25
2
METHOD AND SYSTEM FOR DISCOVERY MANAGEMENT OF ONE
OR MORE MICROSERVICES
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure relate to a method and a system for
discovery management of one or more microservices.
BACKGROUND
10
[0002] The following description of the related art is intended to provide
background information pertaining to the field of 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
15 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
20 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. 3G technology
marked the introduction of high-speed internet access, mobile video calling, and
25 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
30 technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
3
[0004] The compatibility and synergy between Capacity Management Platform
(CMP) and Orchestrator Manager (OAM) microservices ensure a smooth process
of discovering resources while effectively upholding high availability, thereby
5 mitigating failure scenarios and preserving system integrity. Therefore, it is vital
that there is high availability of the microservices based on easy discoverability
since through this interface, the central server receives essential information such
as IP address, port number, Path data, Component Broadcast Context, and Subscribe
Component Type for IM. Hence it is utmost important to ensure the synergy
10 between CMP and OAM and maintain easy discoverability and high availability of
microservices.
[0005] Thus, there exists an imperative need in the art to manage discoverability
and high availability of microservices based on broadcasting of the context data,
15 which the present disclosure aims to address.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure
20 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.
[0007] An aspect of the present disclosure may relate to a method for discovery
25 management of one or more microservices. The method comprises receiving, by a
transceiver unit at an Orchestrator, a connection request from a plurality of Capacity
Management Platform (CMP) microservices. Based on the connection request, the
method further comprises receiving, by the transceiver unit at the Orchestrator, a
set of configuration details from the plurality of CMP microservices. Based on the
30 set of configuration details, the method further comprises transmitting, by the
transceiver unit at the Orchestrator, one or more action commands to an Element
4
Management System (EMS), wherein the one or more action commands is one of
an alarm trigger command and a fetch FCAPS information command. Based on the
one or more action commands, the method further comprises retrieving, by a
retrieval unit at the Orchestrator, a set of context data from the set of configuration
5 details associated with the plurality of CMP microservices. The method further
comprises broadcasting, by a broadcasting unit at the Orchestrator, the set of context
data associated with the plurality of CMP microservices.
[0008] In an exemplary aspect of the present disclosure, the method further
10 comprises initiating, by an initiation unit at the Orchestrator, a target action
associated with one or more CMP microservices based on the connection request,
wherein the target action comprises at least one of a registration action, a
deregistration action, and a re-registration action.
15 [0009] In an exemplary aspect of the present disclosure, in response to the target
action, the method further comprises establishing, by an establishing unit at the
Orchestrator, a successful connection with the plurality of CMP microservices,
wherein the successful connection comprises establishing a web socket connection
between the Orchestrator and the one or more CMP microservices.
20
[0010] In an exemplary aspect of the present disclosure, the set of configuration
details comprises at least one of an IP address data, a port number data, a path data,
a component broadcast data, a subscribe component type data, a registration detail
data, and an availability data.
25
[0011] In an exemplary aspect of the present disclosure, the method further
comprises transmitting, by the transceiver unit at the Orchestrator, FCAPS requests
to one or more microservice instances. Based on the FCAPS request, the method
further comprises consolidating, by a processing unit at the Orchestrator, one or
30 more FCAPS responses from the one or more microservice instances. The method
5
further comprises relaying, by the processing unit at the Orchestrator, the one or
more FCAPS responses to the EMS in a predefined format.
[0012] In an exemplary aspect of the present disclosure, the set of context data
5 comprises at least one of a set of faults, configurations, accounting, performance
and security (FCAPS) data.
[0013] Another aspect of the present disclosure may relate to a system for discovery
management of one or more microservices. The system comprises an Orchestrator.
10 The orchestrator may include a transceiver unit. The transceiver unit is configured
to receive a connection request from a plurality of Capacity Management Platform
(CMP) microservices. Based on the connection request, the transceiver unit is
further configured to receive a set of configuration details from the plurality of CMP
microservices. Based on the set of configuration details, the transceiver unit is
15 further configured to transmit one or more action commands to an Element
Management System (EMS), wherein the one or more action commands is one of
an alarm trigger command and a fetch FCAPS information command. The
Orchestrator further comprises a retrieval unit connected at least to the transceiver
unit. Based on the one or more action commands, the retrieval unit is configured to
20 retrieve a set of context data from the set of configuration details associated with
the plurality of CMP microservices. The Orchestrator further comprises a
broadcasting unit connected at least to the retrieval unit. The broadcasting unit is
configured to broadcast the set of context data associated with the plurality of CMP
microservices.
25
[0014] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for discovery management
of one or more microservices. The instructions include executable code which,
when executed by one or more units of a system, causes a transceiver unit of the
30 system to receive a connection request from a plurality of Capacity Management
Platform (CMP) microservices. Further, the instructions include executable code
6
which, when executed, causes the transceiver unit to receive a set of configuration
details from the plurality of CMP microservices, based on the connection request.
Further, the instructions include executable code which, when executed, causes the
transceiver unit to transmit one or more action commands to an Element
5 Management System (EMS), based on the set of configuration details, wherein the
one or more action commands is one of an alarm trigger command and a fetch
FCAPS information command. Further, the instructions include executable code
which, when executed, causes a retrieval unit to retrieve a set of context data from
the set of configuration details associated with the plurality of CMP microservices,
10 based on the one or more action commands. Further, the instructions include
executable code which, when executed, causes a broadcasting unit to broadcast the
set of context data associated with the plurality of CMP microservices.
OBJECTS OF THE DISCLOSURE
15
[0015] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0016] It is an object of the present disclosure to provide a system and a method for
20 discovery management of one or more microservices.
[0017] It is another object of the present disclosure to provide a solution that
enhances discoverability and high availability for discovering resources.
25 [0018] It is yet another object of the present disclosure to provide a solution to
prevent failure scenarios and preserve system integrity.
DESCRIPTION OF THE DRAWINGS
30 [0019] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
7
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
5 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.
10
[0020] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture;
[0021] FIG. 2 illustrates an exemplary block diagram of a computing device upon
15 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure;
[0022] FIG. 3 illustrates an exemplary block diagram of a system for discovery
management of one or more microservices, in accordance with exemplary
20 implementations of the present disclosure;
[0023] FIG. 4 illustrates an exemplary network environment comprising an
orchestrator for discovery management of one or more microservices in accordance
with exemplary implementations of the present disclosure; and
25
[0024] FIG. 5 illustrates a method flow diagram for discovery management of one
or more microservices in accordance with exemplary implementations of the
present disclosure.
30 [0025] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
8
DETAILED DESCRIPTION
[0026] In the following description, for the purposes of explanation, various
5 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
10 address any of the problems discussed above or might address only some of the
problems discussed above.
[0027] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
15 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.
20
[0028] 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
25 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0029] 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
30 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
9
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.
5 [0030] 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
10 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
15 any additional or other elements.
[0031] 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
20 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,
25 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.
[0032] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
30 “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
10
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant,
5 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.
10 [0033] 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
15 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.
[0034] As used herein “interface” or “user interface refers to a shared boundary
20 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.
25
[0035] 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
30 microprocessors in association with a DSP core, a controller, a microcontroller,
11
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0036] As used herein the transceiver unit include at least one receiver and at least
5 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.
[0037] The present disclosure aims to overcome the issues discussed in the
10 background section and other existing problems in this field of technology by
broadcasting context data and enhancing discoverability as well as high availability
of CMP node, which plays a pivotal role in realizing fail-safe scenarios and
upholding the system's integrity.
15 [0038] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0039] FIG. 1 illustrates an exemplary block diagram representation of a
management and orchestration (MANO) architecture/platform [100], in accordance
20 with exemplary implementation of the present disclosure. The MANO architecture
[100] 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 [100] deploys the network node(s)
in the form of Virtual Network Function (VNF) and Cloud-native/ Container
25 Network Function (CNF). The system as provided by the present disclosure may
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,
30 the system may comprise a NFV Platform Decision Analytics (NPDA) [1096]
component.
12
[0040] 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
5 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.
10 [0041] 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
15 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
20 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
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
25 (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 VNF lifecycle manager [1042], the CNF lifecycle manager
[1052] may be similarly used for the CNFs lifecycle management.
30 [0042] The platforms foundation services module [106] comprises a
microservices elastic load balancer [1062], an identity & access manager [1064], a
13
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
5 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 [100]. These logs may be used for
debugging purposes. The event routing manager [1070] may be responsible for
10 routing the events i.e., the application programming interface (API) hits to the
corresponding services.
[0043] The platforms core services module [108] comprises NFV infrastructure
monitoring manager [1082], an assure manager [1084], a performance manager
15 [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
20 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
25 the performance counters. The policy execution engine (PEE) [1088] may be
responsible for managing all the policies. The capacity monitoring manager
(CMM) [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
30 manager & GCT [1094] manages the configuration and GCT of all the vendors.
The NFV platform decision analytics (NPDA) [1096] helps in deciding the
14
priority of 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
5 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
10 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 [100] may be using the network resources.
15 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 [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.
20
[0044] The platform resource adapters and utilities module [112] further
comprises a platform external API adaptor and gateway [1122], a generic decoder
and indexer (XML, CSV, JSON) [1124], a docker service adaptor [1126], an API
adapter [1128], and a NFV gateway [1130]. The platform external API adaptor
25 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, 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
30 [100] for communication. The Docker Service Adapter (DSA) is a microservicesbased system designed to deploy and manage Container Network Functions (CNFs)
15
and 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
5 CNFCs. The DSA facilitates the deployment, configuration, and management of
these 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.
10
[0045] The API adapter [1128] may be used to connect with the virtual machines
(VMs). The NFV gateway [1130] may be responsible for providing the path to each
services going to/incoming from the MANO architecture [100].
15 [0046] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
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 [200] may also implement a method for
discovery management of one or more microservices utilising the system. In
20 another implementation, the computing device [200] itself implements the method
for discovery management of one or more microservices using one or more units
configured within the computing device [200], wherein said one or more units are
capable of implementing the features as disclosed in the present disclosure.
25 [0047] The computing device [200] may include a bus [202] or other
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 random30 access memory (RAM), or other dynamic storage device, coupled to the bus [202]
for storing information and instructions to be executed by the processor [204]. The
16
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 special5 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].
10 [0048] 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
15 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
20 information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. This 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.
25 [0049] The computing device [200] 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 [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
30 computing device [200] in response to the processor [204] executing one or more
sequences of one or more instructions contained in the main memory [206]. Such
17
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
5 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0050] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two10 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
15 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.
20
[0051] 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
25 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.
18
[0052] Referring to FIG. 3, an exemplary block diagram of a system [300] for
discovery management of one or more microservices, is shown, in accordance with
the exemplary implementations of the present disclosure, is shown.
5 [0053] In one example, the system [300] may be implemented as or within an
orchestrator. As would be understood, in the context of the present subject matter,
the orchestrator may be understood as a central entity/server device, where the
orchestrator, among other functionalities, may perform operations, administrator,
and maintenance management (OAM). The orchestrator may also manage and
10 coordinate NPDA instances within a network function.
[0054] In another example, as depicted in FIG. 3, the system [300] may include the
orchestrator [300A]. The system [300] may also include additional components in
communication with the orchestrator [300A], which have not been depicted in FIG.
15 3, and would be understood to a person skilled in the art.
[0055] The orchestrator [300A] may include at least one transceiver unit [302], at
least one retrieval unit [304], at least one broadcasting unit [306], at least one
initiation unit [308], at least one establishing unit [310] and at least one processing
20 unit [312].
[0056] Also, all of the 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
25 each other. Also, in FIG. 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 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 to implement the features of the present disclosure. The
30 system [300] 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
19
implementation, the system [300] may reside in a server or a network entity. In yet
another implementation, the system [300] may reside partly in the server/ network
entity and partly in the user device.
5 [0057] FIG. 4 illustrates an exemplary network environment comprising an
orchestrator [300A] for discovery management of one or more microservices in
accordance with exemplary implementations of the present disclosure.
[0058] It may be noted that FIG. 3 and FIG. 4 have been explained simultaneously
10 and may be read in conjunction with each other.
[0059] In one example, the orchestrator [300A] may be in communication with
other network entities/components as depicted in FIG. 4. It may be further noted
that any other network entities/components known to a person skilled in the art and
15 not depicted in FIG. 4, may also be in communication with the orchestrator [300A].
Such network entities/components have not been explained here for the sake of
brevity.
[0060] The system [300] is configured for discovery management of one or more
20 microservices, with the help of the interconnection between the components/units
of the system [300]. The management is made possible through the interconnection
and communication between various components of the system [300].
[0061] In operation, initially, the transceiver unit [302] may receive a connection
25 request from a plurality of Capacity Management Platform (CMP) microservices
[402]. This has been depicted by Step [404] in FIG. 4.
[0062] It may be noted that, although, only two CMP microservices, i.e., CMP
[402-1] and CMP [402-2] have been depicted in FIG. 4, the same is done only for
30 the sake of clarity and explanation. The network environment [400] may include
20
any number of CMP microservices [402], and such examples would also be covered
within the scope of the present subject matter.
[0063] The Capacity Management Platform (CMP) refers to a system or set of
5 microservices designed to handle the management, optimization, and control of
resources in a network or infrastructure. The CMP helps manage various
operational parameters such as performance, security, and capacity through
communication with the Orchestrator [300A].
10 [0064] In an implementation of the present disclosure, the connection request
serves as a trigger for initiating communication between the Orchestrator [300A]
and the CMP microservices [402]. The request is sent by the CMP microservices to
establish a communication link, thereby allowing the Orchestrator [300A] to
manage and interact with these microservices.
15
[0065] Continuing further, in one example, upon receiving the connection request,
the initiation unit [308] may initiate a target action associated with one or more
CMP microservices based on the connection request. The target action may include
at least one of a registration action, a deregistration action, and a re-registration
20 action.
[0066] In an implementation of the present disclosure, upon receiving the
connection request, the initiation unit [308] within the Orchestrator [300A] is
activated. The initiation unit [308] is configured to initiate a target action based on
25 the nature of the received connection request. This target action refers to the specific
task that needs to be performed in response to the request from the CMP
microservices.
[0067] The target action may involve one of three exemplary key operations. In one
30 example, the registration action may involve the initial registration of a CMP
microservice, allowing it to be recognized and integrated into the system [300] for
21
further communication and management. Upon successful registration, a successful
connection between the orchestrator [300A] and the CMP microservice [402] may
be established.
5 [0068] In one example, a web socket connection may be established between the
Orchestrator [300A] and CMP instance using the interface client. The connection is
established after registration. As would be noted and appreciated, the web socket
may allow for a real time, bidirectional communication channel between the
Orchestrator [300A] and the CMP microservices. The web socket connection
10 confirms continuous data exchange, allowing the Orchestrator [300A] to send and
receive information without the need for constant reconnection. This connection
enables the system to handle real time communication and updates between the
CMP microservices and the Orchestrator.
15 [0069] In another example, the deregistration action may involve removing or
disconnecting a CMP microservice from the system [300], confirming that it is no
longer part of the managed services or infrastructure. In yet another example, the
re-registration action may occur when a previously registered CMP microservice
needs to update its registration details or reestablish its connection with the
20 Orchestrator [300A].
[0070] Continuing further with the present example, once the connection request is
received and the connection is established, the transceiver unit may receive a set of
configuration details from the plurality of CMP microservices.
25
[0071] In an implementation of the present disclosure, these configuration details
provide information that the Orchestrator [300A] requires to manage and interact
with the CMP microservices.
22
[0072] In an example, the set of configuration details may include at least one of
an IP address data, a port number data, a path data, a component broadcast data, a
subscribe component type data, a registration detail data, and an availability data.
5 [0073] The IP address data is information about the network location of the CMP
microservices. The port number data is the ports through which the Orchestrator
[300A] may communicate with each microservice. The path data are the directories
or routes that help identify where specific resources or services are located within
the microservices. The component broadcast data is the information regarding the
10 broadcast messages sent by different components of the CMP microservices. The
subscribe component type data are the details about the types of components or
services that are subscribed to within the CMP. The registration detail data is the
information related to the initial or updated registration status of each microservice.
The availability data is the information regarding the availability or status of each
15 microservice, indicating whether they are active, inactive, or under maintenance.
[0074] However, it may be noted that the aforementioned configuration details are
only exemplary, and not be construed to limit the scope of the present subject matter
in any manner. The orchestrator [300A] may receive any other configuration details
20 from the CMP microservices as well, and all such examples would lie within the
scope of the present subject matter.
[0075] Based on the set of configuration details, the transceiver unit may transmit
one or more action commands to an Element Management System (EMS). The one
25 or more action commands may be one of an alarm trigger command and a fetch
FCAPS information command. This has been depicted by Step [406] in FIG. 4.
[0076] In an implementation of the present disclosure, these action commands are
instructions issued to the EMS to perform operations for system management. The
30 Element Management System (EMS) plays an important role in the ongoing
23
management and operational control of the Capacity Management Platform (CMP)
microservices.
[0077] The FCAPS is a framework, well understood to a person skilled in the art,
5 that may be used in telecommunications and network management to monitor and
manage network systems.
[0078] The alarm trigger command may be issued to the EMS when certain
conditions, based on the configuration details or system status, require an alarm to
10 be raised. The alarm indicates issues such as faults, system failures, or capacity
overloads that need immediate attention.
[0079] The fetch FCAPS information command may instruct the EMS to retrieve
detailed information about FCAPS (Fault, Configuration, Accounting,
15 Performance, and Security). The FCAPS is a management framework commonly
used in telecommunications and IT networks to monitor and manage essential
operational aspects. This information helps in monitoring system health,
performance, and security, and in managing the overall network's configuration and
resources.
20
[0080] By transmitting such one or more action commands, the Orchestrator
[300A] confirms that the EMS is kept up to date with the system status and may
take necessary actions to maintain the network's stability and performance.
25 [0081] Continuing further with the present example, once the EMS receives the
action commands, the retrieval unit [304] may retrieve a set of context data from
the set of configuration details associated with the plurality of CMP microservices.
[0082] In an implementation of the present disclosure, the retrieval units [304] is
30 configured to collect a specific set of context data from the configuration details of
the CMP microservices. This context data is for understanding the current
24
operational state and behaviour of the microservices. The retrieval unit [304]
operates based on the action commands (such as an alarm trigger command or a
fetch FCAPS command) that were previously sent. The context data is the detailed
information retrieved from the configuration details of the CMP microservices. This
5 data is for the Orchestrator [300A] to manage, monitor, and interact with the
microservices. The context data may include but not limited to operational details
such as IP address, port number, service state, subscription information and
registration data. The context data retrieved is directly tied to the action command
that was issued.
10
[0083] For example, if the action command was a fetch FCAPS information
command, the set of context data comprises at least one of a set of faults,
configurations, accounting, performance and security (FCAPS) data.
15 [0084] Continuing further, after the retrieval unit [304] collects the relevant context
data from the configuration details of the CMP microservices, the broadcasting unit
[306] may broadcast the set of context data associated with the plurality of CMP
microservices. This has been depicted by Step [408] in FIG. 4. The broadcasting
unit [306] is responsible for broadcasting or distributing this set of context data to
20 the recipients within the system [300].
[0085] The broadcasting context data is the set of context data, which includes
operational details like service configurations, performance metrics, and FCAPS
information, that is sent out to various components within the system. The
25 broadcasted data may be used for real time monitoring, triggering automated
actions, or updating other microservices or systems.
[0086] In another example, the processing unit [312] interacts with a dedicated
registration database to store all relevant registration information for the
30 microservice. This has been depicted by Step [410] in FIG. 4.
25
[0087] In yet another example, as per the approaches of the present subject matter,
the Orchestrator [300A] may also allow the different microservices instances [402]
to share their respective FCAPS data with the EMS.
5 [0088] For example, as per another implementation of the present subject matter,
for allowing the microservice instances to share their respective FCAPS data with
the EMS, the transceiver unit [302] may transmit FCAPS requests to one or more
microservice instances.
10 [0089] By sending FCAPS requests, the Orchestrator [300A] retrieve information
related to faults, configuration, accounting, performance and security from the
microservices.
[0090] Based on the FCAPS requests, each of the plurality of microservice
15 instances may generate FCAPS responses, which may include their respective
FCAPS data. The FCAPS responses may be transmitted by each of the plurality of
microservice instances to the orchestrator [300A]. On receiving the FCAPS
responses, the processing unit [312] may consolidate one or more FCAPS responses
from the one or more microservice instances and relay the one or more FCAPS
20 responses to the EMS in a predefined format.
[0091] For example, the processing unit [312] performs the tasks such as
consolidating FCAPS responses refers as once the individual microservice
instances send back their FCAPS data. The processing unit [312] collects and
25 consolidates these responses. This may involve combining information from
multiple instances, such as fault data, configuration settings, performance metrics,
or security statuses, into a unified dataset. This consolidation helps update the
management process by organizing diverse data into a manageable format for the
Orchestrator [300A].
30
26
[0092] The relaying responses to the EMS means, after consolidating the FCAPS
responses, the processing unit [312] may relay this information to the EMS. The
FCAPS responses are related to the Orchestrator in a predefined format, confirming
consistency and proper interpretation by the EMS. This format confirms that the
5 EMS may process and utilize the FCAPS data for system monitoring, fault
detection, and other management tasks.
[0093] Referring to FIG. 5, an exemplary method flow diagram [500] for discovery
management of one or more microservices, in accordance with exemplary
10 implementations of the present disclosure is shown. In an implementation the
method [500] is performed by the system [300]. Further, in an 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].
15 [0094] At Step [504], the method [500] comprises receiving, by a transceiver unit
[302] at an Orchestrator, a connection request from a plurality of Capacity
Management Platform (CMP) microservices.
[0095] In operation, initially, the transceiver unit [302] may receive a connection
20 request from a plurality of Capacity Management Platform (CMP) microservices
[402].
[0096] In an implementation of the present disclosure, the connection request
serves as a trigger for initiating communication between the Orchestrator [300A]
25 and the CMP microservices [402]. The request is sent by the CMP microservices to
establish a communication link, thereby allowing the Orchestrator [300A] to
manage and interact with these microservices.
[0097] Continuing further, in one example, upon receiving the connection request,
30 the initiation unit [308] may initiate a target action associated with one or more
CMP microservices based on the connection request. The target action may include
27
at least one of a registration action, a deregistration action, and a re-registration
action.
[0098] In an implementation of the present disclosure, upon receiving the
5 connection request, the initiation unit [308] within the Orchestrator [300A] is
activated. The initiation unit [308] is configured to initiate a target action based on
the nature of the received connection request. This target action refers to the specific
task that needs to be performed in response to the request from the CMP
microservices.
10
[0099] In one example, the registration action may involve the initial registration
of a CMP microservice, allowing it to be recognized and integrated into the system
[300] for further communication and management. Upon successful registration, a
successful connection between the orchestrator [300A] and the CMP microservice
15 [402] may be established.
[0100] In one example, a web socket connection may be established between the
Orchestrator [300A] and CMP instance using the interface client.
20 [0101] At Step [506], based on the connection request, the method [500] comprises
receiving, by the transceiver unit [302] at the Orchestrator, a set of configuration
details from the plurality of CMP microservices.
[0102] Continuing further with the present example, once the connection request is
25 received and the connection is established, the transceiver unit may receive a set of
configuration details from the plurality of CMP microservices.
[0103] In an implementation of the present disclosure, these configuration details
provide information that the Orchestrator [300A] requires to manage and interact
30 with the CMP microservices.
28
[0104] In an example, the set of configuration details may include at least one of
an IP address data, a port number data, a path data, a component broadcast data, a
subscribe component type data, a registration detail data, and an availability data.
5 [0105] At Step [508], based on the set of configuration details, the method [500]
comprises transmitting, by the transceiver unit [302] at the Orchestrator, OAM unit,
one or more action commands to an Element Management System (EMS), wherein
the one or more action commands is one of an alarm trigger command and a fetch
FCAPS information command.
10
[0106] For example, based on the set of configuration details, the transceiver unit
may transmit one or more action commands to an Element Management System
(EMS). The one or more action commands may be one of an alarm trigger command
and a fetch FCAPS information command.
15
[0107] In an implementation of the present disclosure, these action commands are
instructions issued to the EMS to perform operations for system management. The
Element Management System (EMS) plays an important role in the ongoing
management and operational control of the Capacity Management Platform (CMP)
20 microservices.
[0108] The alarm trigger command may be issued to the EMS when certain
conditions, based on the configuration details or system status, require an alarm to
be raised. The alarm indicates issues such as faults, system failures, or capacity
25 overloads that need immediate attention.
[0109] The fetch FCAPS information command may instruct the EMS to retrieve
detailed information about FCAPS (Fault, Configuration, Accounting,
Performance, and Security). The FCAPS is a management framework commonly
30 used in telecommunications and IT networks to monitor and manage essential
operational aspects. This information helps in monitoring system health,
29
performance, and security, and in managing the overall network's configuration and
resources.
[0110] By transmitting such one or more action commands, the Orchestrator
5 [300A] confirms that the EMS is kept up to date with the system status and may
take necessary actions to maintain the network's stability and performance.
[0111] At Step [510], based on the one or more action commands, the method [500]
comprises retrieving, by a retrieval unit [304] at the Orchestrator, a set of context
10 data from the set of configuration details associated with the plurality of CMP
microservices.
[0112] Continuing further with the present example, once the EMS receives the
action commands, the retrieval unit [304] may retrieve a set of context data from
15 the set of configuration details associated with the plurality of CMP microservices.
[0113] In an implementation of the present disclosure, the retrieval units [304] is
configured to collect a specific set of context data from the configuration details of
the CMP microservices. This context data is for understanding the current
20 operational state and behaviour of the microservices. The retrieval unit [304]
operates based on the action commands (such as an alarm trigger command or a
fetch FCAPS command) that were previously sent. The context data is the detailed
information retrieved from the configuration details of the CMP microservices. This
data is for the Orchestrator [300A] to manage, monitor, and interact with the
25 microservices. The context data may include but not limited to operational details
such as IP address, port number, service state, subscription information and
registration data. The context data retrieved is directly tied to the action command
that was issued.
30
[0114] For example, if the action command was a fetch FCAPS information
command, the set of context data comprises at least one of a set of faults,
configurations, accounting, performance and security (FCAPS) data.
5 [0115] At Step [512], the method [500] comprises broadcasting, by a broadcasting
unit [306] at the Orchestrator, the set of context data associated with the plurality
of CMP microservices.
[0116] Continuing further, after the retrieval unit [304] collects the relevant context
10 data from the configuration details of the CMP microservices, the broadcasting unit
[306] may broadcast the set of context data associated with the plurality of CMP
microservices. The broadcasting unit [306] is responsible for broadcasting or
distributing this set of context data to the recipients within the system [300].
15 [0117] The broadcasting context data is the set of context data, which includes
operational details like service configurations, performance metrics, and FCAPS
information, that is sent out to various components within the system. The
broadcasted data may be used for real time monitoring, triggering automated
actions, or updating other microservices or systems.
20
[0118] Thereafter, the method terminates at Step [514].
[0119] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for discovery management of one or more
25 microservices. The instructions include executable code which, when executed by
one or more units of a system, causes a transceiver unit [302] of the system to
receive a connection request from a plurality of Capacity Management Platform
(CMP) microservices. Further, the instructions include executable code which,
when executed, causes the transceiver unit to receive a set of configuration details
30 from the plurality of CMP microservices, based on the connection request. Further,
the instructions include executable code which, when executed, causes the
31
transceiver unit to transmit one or more action commands to an Element
Management System (EMS), based on the set of configuration details, wherein the
one or more action commands is one of an alarm trigger command and a fetch
FCAPS information command. Further, the instructions include executable code
5 which, when executed, causes a retrieval unit [304] to retrieve a set of context data
from the set of configuration details associated with the plurality of CMP
microservices, based on the one or more action commands. Further, the instructions
include executable code which, when executed, causes a broadcasting unit [306] to
broadcast the set of context data associated with the plurality of CMP microservices.
10
[0120] As is evident from the above, the present disclosure provides a technically
advanced solution for discovery management of one or more microservices. The
present solution encompasses many advantages, some of which are ensuring
discoverability of CMP node and high availability with associated services. The
15 collaboration between CMP and OAM service ensures a smooth process of
discovering resources while effectively upholding high availability, thereby
mitigating failure scenarios and preserving system integrity.
[0121] While considerable emphasis has been placed herein on the disclosed
20 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
25 and non-limiting.
[0122] 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
30 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
32
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
5 of the present disclosure.
33
We Claim:
1. A method for discovery management of one or more microservices, the
method comprising:
5 - receiving, by a transceiver unit [302] at an Orchestrator [300A], a
connection request from a plurality of Capacity Management Platform
(CMP) microservices;
- based on the connection request, receiving, by the transceiver unit [302] at
the Orchestrator, a set of configuration details from the plurality of CMP
10 microservices;
- based on the set of configuration details, transmitting, by the transceiver unit
[302] at the Orchestrator, one or more action commands to an Element
Management System (EMS), wherein the one or more action commands is
one of an alarm trigger command and a fetch FCAPS information command;
15 - based on the one or more action commands, retrieving, by a retrieval unit
[304] at the Orchestrator [300A], a set of context data from the set of
configuration details associated with the plurality of CMP microservices;
and
- broadcasting, by a broadcasting unit [306] at the Orchestrator [300A], the
20 set of context data associated with the plurality of CMP microservices.
2. The method as claimed in claim 1, further comprising: initiating, by an
initiation unit [308] at the Orchestrator [300A], a target action associated with one
or more CMP microservices based on the connection request, wherein the target
25 action comprises at least one of a registration action, a deregistration action, and a
re-registration action.
3. The method as claimed in claim 2, further comprising: in response to the
target action, establishing, by an establishing unit [310] at the Orchestrator [300A],
30 a successful connection with the plurality of CMP microservices, wherein the
34
successful connection comprises establishing a web socket connection between the
Orchestrator and the one or more CMP microservices.
4. The method as claimed in claim 1, wherein the set of configuration details
5 comprises at least one of an IP address data, a port number data, a path data, a
component broadcast data, a subscribe component type data, a registration detail
data, and an availability data.
5. The method as claimed in claim 1, further comprising:
10 - transmitting, by the transceiver unit [302] at the Orchestrator [300A],
FCAPS requests to one or more microservice instances;
- based on the FCAPS request, consolidating, by a processing unit [312] at
the Orchestrator [300A], one or more FCAPS responses from the one or
more microservice instances; and
15 - relaying, by the processing unit [312] at the Orchestrator [300A], the one or
more FCAPS responses to the EMS in a predefined format.
6. The method as claimed in claim 1, wherein the set of context data comprises
at least one of a set of faults, configurations, accounting, performance and security
20 (FCAPS) data.
7. A system for discovery management of one or more microservices, the
system comprising an Orchestrator [300A], the Orchestrator [300A] comprising:
- a transceiver unit [302] configured to:
25 o receive a connection request from a plurality of Capacity
Management Platform (CMP) microservices;
o based on the connection request, receive a set of configuration
details from the plurality of CMP microservices;
o based on the set of configuration details, transmit one or more action
30 commands to an Element Management System (EMS), wherein the
35
one or more action commands is one of an alarm trigger command
and a fetch FCAPS information command;
- a retrieval unit [304] connected at least to the transceiver unit [302], wherein
the retrieval unit [304] is configured to: based on the one or more action
5 commands, retrieve a set of context data from the set of configuration details
associated with the plurality of CMP microservices; and
- a broadcasting unit [306] connected at least to the retrieval unit [304],
wherein the broadcasting unit [306] is configured to: broadcast the set of
context data associated with the plurality of CMP microservices.
10
8. The system as claimed in claim 7, further comprising an initiation unit [308]
configured to: initiate a target action associated with one or more CMP
microservices based on the connection request, wherein the target action comprises
at least one of a registration action, a deregistration action, and a re-registration
15 action.
9. The system as claimed in claim 8, further comprising an establishing unit
[310], wherein the establishing unit is configured to: in response to the target action,
establish a successful connection with the plurality of CMP microservices, wherein
20 the successful connection comprises establishing a web socket connection between
the Orchestrator[300A] and the one or more CMP microservices.
10. The system as claimed in claim 7, wherein the set of configuration details
comprises at least one of an IP address data, a port number data, a path data, a
25 component broadcast data, a subscribe component type data, a registration detail
data, and an availability data.
11. The system as claimed in claim 7, further comprising:
- the transceiver unit [302] configured to transmit FCAPS requests to one or
30 more microservice instances;
- a processing unit [312] configured to:
36
o based on the FCAPS request, consolidate one or more FCAPS
responses from the one or more microservice instances; and
o relay the one or more FCAPS responses to the EMS in a predefined
format.
12. The system as claimed in claim 7, wherein the set of context data comprises
at least one of a set of faults, configurations, accounting, performance and security
(FCAPS) data.