Management and orchestration of heterogeneous network environment using dynamic, robust and network aware microservices

Patent metadata

Field	Value
Publication number	US-11627037-B2
Application number	US-202217663825-A
Country	US
Kind code	B2
Filing date	May 17, 2022
Priority date	Jul 2, 2021
Publication date	Apr 11, 2023
Grant date	Apr 11, 2023

Abstract

State of the art networking solutions are tightly coupled and proprietary in nature due to multiple vendors in the networking domain. Embodiments of the present disclosure provide a method and system for management and orchestration of heterogeneous network environment using dynamic, robust and network aware microservices. The method enables a platform for automatically and dynamically identifying appropriate group of microservices in accordance with network type and service type specified by the user, thus providing a solution that generates network aware microservices for each network in the heterogeneous network landscape. Furthermore, the system manages the identified microservices for each of the network by managing the life cycle of these microservices. The right life cycle management and co-ordination of the microservices for the network is in-line with desired goals/business logic, in a reliable and scalable manner, in heterogeneous network environments.

First claim

What is claimed is:

1. A processor implemented method for management and orchestration of heterogeneous network environment, the method comprising:
detecting, by a Control Unit (CU) executed by one or more hardware processors, an event triggered for a network among a plurality of heterogeneous networks identified by the CU, wherein the event is one of a) a service request for the network and b) a network condition captured by network monitoring tools;
discovering, by the CU, network information using one of a) auto discovery functionality if supported by the network, and b) network information provided in the service request;
obtaining, by the CU, a service information from the event based on one of a) the service information explicitly specified in the service request and b) the service information derived by the CU based on the network condition, wherein the service information specifies a list of service types from among a plurality of service types, and wherein a service type among the list of service types is associated with a label comprising one of i) a critical service and ii) a non-critical service;
identifying, by the CU, a microservice list for each of the plurality of service types in accordance with a) the service type, b) the label and c) the discovered network information;
creating, by the CU, a) one or more Fault Tolerance Groups (FTGs) comprising a first set of microservices from among the identified microservice list for each of the plurality of service types that is tagged as critical and b) one or more Scalability Groups (SCGs) comprising a second set of microservices among the identified microservice list for each of the plurality of service types that are tagged as non-critical,
wherein grouping of the first set of microservices in the one or more FTGs and second set of microservices in the one or more SCGs is dynamically interchanged based on at least one of a) change in the network condition and b) change in the label on detected in an updated service request, and
wherein a master-slave multi-tier combination of microservices in the first set of microservices for the one or more FTGs is dynamically identified by the CU;

creating, by the CU, a plurality of workflows for the first set of microservices of the one or more FTGs and the second set of microservices of the one or more SCGs and mapping the plurality of
workflows to corresponding first set of microservices and the second set of microservices;
deploying, by the CU the first set of microservices of the one or more FTGs and the second set of microservices of the one or more SCGs for the network via an Infrastructure as a Service (IaaS) platform, wherein for each of the deployed FTGs and SCGs there exists an intra-group communication, inter-group communication and communication with the CU via a communication unit, and wherein coordination among the first set of microservices or the second set of microservices, and management of coordination by the CU is performed via a coordination unit; and
managing, by the CU, a life cycle of the deployed first set of microservices and the second set of microservices comprising:
a) configuring one or more of the first set of microservices and one or more of the second set of microservices with initial configurations, wherein the one or more of the first set of microservices and the one or more of the second set of microservices when configured are in idle state;
b) monitoring health of the one or more of the first set of microservices and the one or more of the second set of microservices via the network monitoring tools running currently performing tasks assigned in accordance with the mapped workflows, wherein the one or more of the first set of microservices and the one or more of the second set of microservices when running are in busy state;
c) dynamically updating the initial configuration by interrupting the running one or more of the first set of microservices and one or more of the second set of microservices by reconfiguring, wherein the one or more of the first set of microservices and the one or more of the second set of microservices when re-configured are shifted back to idle state; and
d) removing the one or more of the first set of microservices and the one or more of the second set of microservices from the microservice list on completion of the tasks.

2. The method of claim 1 , further comprising configuring the CU as a primary CU and a secondary CU, wherein the primary CU operates in active mode to perform the network management and orchestration of the network, while the secondary CU operates in a standby mode, wherein the secondary CU communicates with the primary CU for tracking events of the primary CU, and wherein the secondary CU seamlessly takes control on failure of the primary CU based on the tracked events.

3. The method of claim 2 further comprising operating the CU in a distributed environment mode for management and orchestration of the plurality of heterogeneous networks, wherein each of the plurality of heterogeneous networks is controlled by a corresponding primary CU and a corresponding secondary CU, wherein the corresponding primary CU of each of the plurality of heterogeneous networks communicates with each other for tracking the events, and wherein a first primary CU associated with a first network among the plurality of heterogeneous networks seamlessly takes control on failure of a second primary CU associated with a second network among the plurality of heterogeneous networks based on the tracked events.

4. A system for management and orchestration of heterogeneous network environment, the system comprising:
a memory storing instructions,
one or more Input/Output (I/O) interfaces;
one or more hardware processors coupled to the memory via the one or more I/O interfaces,
a Controller Unit (CU), a communication unit and a coordination unit executed by the one or more hardware processors, wherein the CU is configured by the instructions to:
detect an event triggered for a network among a plurality of heterogeneous networks identified by the CU, wherein the event is one of a) a service request for the network and b) a network condition captured by network monitoring tools;
discover network information using one of a) auto discovery functionality if supported by the network, and b) network information provided in the service request;
obtain a service information from the event based on one of a) the service information explicitly specified in the service request and b) the service information derived by the CU based on the network condition, wherein the service information specifies a list of service types from among a plurality of service types, and wherein a service type among the list of service types is associated with a label comprising one of i) a critical service and ii) a non-critical service;
identify a microservice list for each of the plurality of service types in accordance with a) the service type, b) the label and c) the discovered network information;
create a) one or more Fault Tolerance Groups (FTGs) comprising a first set of microservices from among the identified microservice list for each of the plurality of service types that is tagged as critical and b) one or more Scalability Groups (SCGs) comprising a second set of microservices among the identified microservice list for each of the plurality of service types that are tagged as non-critical,
wherein grouping of the first set of microservices in the one or more FTGs and second set of microservices in the one or more SCGs is dynamically interchanged based on at least one of a) change in the network condition and b) change in the label on detected in an updated service request, and
wherein a master-slave multi-tier combination of microservices in the first set of microservices for the one or more FTGs i

Assignees

• Tata Consultancy Services Ltd
• Tata Consultancy Sendees Ltd

Inventors

• Nadaf Shameem Raj Mohinuddin
• Behera Sipra
• Trivedi Nikita
• Panigrahi Bighnaraj
• Rath Hemant Kumar
• Mishra Garima
• Patro Sumanta

Classifications

• H04L41/0663 Primary

  Performing the actions predefined by failover planning, e.g. switching to standby network elements · CPC title

• H04L41/0659

  by isolating or reconfiguring faulty entities · CPC title

• H04L41/0816 Primary

  the condition being an adaptation, e.g. in response to network events · CPC title

• H04L43/0817

  by checking functioning · CPC title

• H04L41/5012

  determining service availability, e.g. which services are available at a certain point in time · CPC title