[go: up one dir, main page]

WO2025057236A1 - Procédé et système de distribution d'une charge de trafic à l'aide d'une interface - Google Patents

Procédé et système de distribution d'une charge de trafic à l'aide d'une interface Download PDF

Info

Publication number
WO2025057236A1
WO2025057236A1 PCT/IN2024/051750 IN2024051750W WO2025057236A1 WO 2025057236 A1 WO2025057236 A1 WO 2025057236A1 IN 2024051750 W IN2024051750 W IN 2024051750W WO 2025057236 A1 WO2025057236 A1 WO 2025057236A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
operational
health status
requests
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IN2024/051750
Other languages
English (en)
Inventor
Aayush Bhatnagar
Ankit Murarka
Rizwan Ahmad
Kapil Gill
Arpit Jain
Shashank Bhushan
Jugal Kishore
Meenakshi Sarohi
Kumar Debashish
Supriya Kaushik DE
Gaurav Kumar
Kishan Sahu
Gaurav Saxena
Vinay Gayki
Mohit Bhanwria
Durgesh KUMAR
Rahul Kumar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025057236A1 publication Critical patent/WO2025057236A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5015—Service provider selection
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/508—Monitor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/541—Client-server

Definitions

  • Embodiments of the present disclosure generally relate to the field of wireless communication system. More particularly, embodiments of the present disclosure relate to a method and a system for distributing a traffic load using an interface.
  • Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements.
  • the first generation of wireless communication technology was based on analog technology and offered only voice services.
  • 2G second-generation
  • 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services.
  • 4G fourth-generation
  • 5G fifth-generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • NFs network functions
  • AMF Access and Mobility Management Function
  • SMF session management function
  • AUSF Authentication Server function
  • NSSF Network Slice Selection Function
  • PCF Policy control function
  • NEF Network Exposure Function
  • CHF Converged Charging Function
  • One or more of the aforementioned NFs communicates with each other, to implement multiple activities on the 5G communication system.
  • CHF is one of the key network functions, which supports charging or billing services for user consumption of services.
  • An aspect of the present disclosure may relate to a method for distributing a traffic load using an interface.
  • the method includes receiving, by a transceiver unit using the interface, one or more requests at a load balancer.
  • the method includes monitoring, by a monitoring unit using the interface, a health status of one or more registered applications and one or more operational microservice instances, in response to the received one or more requests.
  • the method includes fetching, by a retrieval unit, via an orchestrator manager, a real time health status of the one or more operational microservice instances.
  • the method includes determining, by a determination unit using the interface, an optimal server from a plurality of servers based on the health status of the one or more operational microservice instances.
  • the method includes distributing, by the transceiver unit, using the interface, the one or more requests among the one or more operational microservice instances to the optimal server.
  • the one or more requests comprise at least one of: a load balancer request, an HTTP request.
  • the health status of the one or more registered applications and the one or more operational microservice instances comprises of a positive health status and a negative health status.
  • the interface is a Load Balancer- Service Adapter (LB-SA) interface to connect the load balancer with the service adapter.
  • LB-SA Load Balancer- Service Adapter
  • An aspect of the present disclosure may relate to a system for distributing a traffic load using an interface.
  • the system comprises a transceiver unit configured to receive, using the interface, one or more requests at a load balancer.
  • the system further comprises a monitoring unit connected at least to the transceiver unit, the monitoring unit is configured to monitor, using the interface, a health status of one or more registered applications and one or more operational microservice instances, in response to the received one or more requests.
  • the system further comprises a retrieval unit connected at least to the monitoring unit, the retrieval unit is configured to fetch, via an orchestrator manager, a real time health status of the one or more operational microservice instances.
  • the system further comprises a determination unit connected at least to the retrieval unit, the determination unit is configured to determine, using the interface, an optimal server from a plurality of servers based on the health status of the one or more operational microservice instances.
  • the transceiver unit is further configured to distribute, using the interface, the one or more requests among the one or more operational microservice instances to the optimal server.
  • Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for distributing a traffic load using an interface, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive, using the interface, one or more requests at a load balancer; a monitoring unit of the system to monitor, using the interface, a health status of one or more registered applications and one or more operational microservice instances, in response to the received one or more requests; a retrieval unit of the system to fetch, via an orchestrator manager, a real time health status of the one or more operational microservice instances; a determination unit of the system to determine, using the interface, an optimal server from a plurality of servers based on the health status of the one or more operational microservice instances; and the transceiver unit of the system to distribute, using the interface, the one or more requests among the one or more operational microservice instances to the optimal server.
  • LB-SA Load Balancer-Service Adapter
  • FIG. 3 illustrates an exemplary block diagram of a system for distributing a traffic load using an interface, in accordance with exemplary implementations of the present disclosure.
  • FIG. 5 illustrates an exemplary block diagram of a system for distributing a traffic load using an interface, in accordance with exemplary implementations of the present disclosure.
  • a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions.
  • a processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
  • the processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure.
  • a user equipment As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “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 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.
  • the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
  • 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.
  • a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
  • the storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
  • user interface refers to a shared boundary across which two or more separate components of a system exchange information or data.
  • the interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
  • container service adapter (CSA) (may be a docker service adapter) refers to such as, unit, server or service which facilitates communication between container and other services or microservices.
  • a load balancer refers to a device, unit, server, or service that manages incoming and outgoing network traffic.
  • the load balancer stores details of at least the available servers, and microservice instances. It manages traffic by directing and distributing incoming or outgoing traffic to healthy servers or resources.
  • microservice refers to such as, unit, node, server loosely coupled, independent deployable services specialized for performing specific functions related to management and optimization of network operations.
  • the microservice instance refers to single deployment of the microservice.
  • the microservice instances may be used for scaling and load balancing.
  • Each microservice may have a unique identifier.
  • Each microservice instance ’s health and performance is monitored during the operation. If any microservice instance's health or performance degrades, the network may automatically, or manually, replace the instance or transfer the traffic load to a healthy microservice instance.
  • orchestrator manager refers to such as, unit, node, service or server, which manages service operations of different microservices in the network. Orchestrator manager maintains records details of the operational microservices and share details of the microservices with other microservices for the operational communication.
  • IAM node refers to such as, service, unit, platform for providing defence against malicious or unauthorised login activity and safeguards credentials by enabling risk-based access controls, ensuring identity protection and authentication processes.
  • Elastic Load Balancer refers to such as service, unit, platform for managing and distributing incoming traffic efficiently across a group of supported servers, microservices and units in a manner that may increase speed and performance of the network.
  • Event Routing Management refers to such as, node, server, service or platform for monitoring and triggering various actions or responses within the system based on detected event. For example, for any microservice instance down, the ERM may trigger any alert for taking an action to overcome the service breakdown condition in the network.
  • Central Log management System refers to such as service or platform which may collect log data from multiple sources and may consolidate the collected data. This consolidated data is then presented on a central interface which may be accessed by a user such as network administrator or authorised person.
  • Elastic Search Cluster refers to such as, a group of servers, nodes that work together and form a cluster for distributing tasks, searching and indexing across all the nodes in the cluster.
  • the present method and system provide a Load balancer and CSA interface (LB-SA interface), which ensures that no server get overloaded due to bulk traffic.
  • the present system and method provide the LB-SA interface, which distributes incoming/outgoing requests easily among all SA instances.
  • the present method and system enable all instantiation, termination and Containerized Network Function (CNF) information (metrics, state) operations on cloud which may be performed on Management and Orchestration (MANO).
  • CNF Containerized Network Function
  • MANO Management and Orchestration
  • the present method and system support HTTP/HTTPS configurations in parallel.
  • the present method and system routes client requests across all servers in a manner that maximizes speed and capacity utilization.
  • the present method and system may perform header-based routing which may save time and database hits.
  • the NFV and SDN design function module [104] further comprises a VNF lifecycle manager (compute) [1042]; a VNF catalogue [1044]; a network services catalogue [1046]; a network slicing and service chaining manager [1048]; a physical and virtual resource manager [1050] and a CNF lifecycle manager [1052],
  • the VNF lifecycle manager (compute) [1042] is responsible for on which server of the communication network the microservice will be instantiated.
  • the VNF lifecycle manager (compute) [1042] will manage the overall flow of incoming/ outgoing requests during interaction with the user.
  • the VNF lifecycle manager (compute) [1042] is responsible for determining which sequence to be followed for executing the process.
  • the platforms core services module [108] further comprises NFV infrastructure monitoring manager [1082]; an assure manager [1084]; a performance manager [1086]; a policy execution engine [1088]; a capacity monitoring manager [1090]; a release management (mgmt.) repository [1092]; a configuration manager & (GCT) [1094]; an NFV platform decision analytics [1096]; a platform NoSQL DB [1098]; a platform schedulers and cron jobs [1100]; a VNF backup & upgrade manager [1102]; a micro service auditor [1104]; and a platform operations, administration and maintenance manager [1106],
  • the NFV infrastructure monitoring manager [1082] monitors the infrastructure part of the NFs.
  • the computing device [200] also may include a communication interface [218] coupled to the bus [202],
  • the communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222].
  • 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.
  • the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • 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],
  • a server [230] might transmit a requested code for an application program through the Internet [228], the 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.
  • FIG. 3 an exemplary block diagram of a system [300] for distributing a traffic load using an interface is shown, in accordance with the exemplary implementations of the present disclosure.
  • the system [300] comprises at least one transceiver unit [302], at least one monitoring unit [304], at least one retrieval unit [306], and at least one determination unit [308], Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. 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.
  • system [300] may be present in a user device to implement the features of the present invention.
  • the 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).
  • the system [300] may reside in a server or a network entity.
  • the system [300] may reside partly in the server/ network entity and partly in the user device.
  • the system [300] comprises a transceiver unit [302], The transceiver unit [302] is configured to receive, using the interface, one or more requests at a load balancer.
  • the transceiver unit [302] is configured to receive the one or more requests such as, but not limited to, at least one of: a load balancer request, a hypertext transfer protocol (HTTP) request at the load balancer.
  • the one or more requests may be associated with incoming or outgoing network traffic to balance traffic load in the network.
  • the interface is a Load Balancer-Service Adapter (LB-SA) interface to connect the load balancer with the service adapter or container service adapter.
  • LB-SA Load Balancer-Service Adapter
  • the system [300] comprises a retrieval unit [306], The retrieval unit [306] is connected at least to the monitoring unit [304], The retrieval unit [306] is configured to fetch, via an orchestrator manager, a real time health status of the one or more operational microservice instances. After receiving the health status (e.g., positive or negative) from the monitoring unit [304], the retrieval unit [306] may fetch the real-time health status of the one or more operational microservice instances from the orchestrator manager.
  • the one or more microservice (MS) instances may be such as ‘MS-1 instance- 1’, ‘MS-2 instance-2’ and ‘MS-n instance-n’.
  • the retrieval unit [206] may fetch real-time health status such as the positive health status of the ‘MS-1 instance-T, the negative health status of ‘MS-2 instance-2’, and the positive health status of ‘MS-n instance-n’ via the orchestrator manager.
  • the orchestrator manager stores real time health status of the one or more operational microservice instances.
  • the system [300] comprises a determination unit [308], The determination unit [308] is connected at least to the retrieval unit [306], The determination unit [308] is configured to determine, using the interface, an optimal server from a plurality of servers based on the health status of the one or more operational microservice instances.
  • the determination unit [308] is configured to determine the optimal server from the plurality of servers.
  • the load balancers may store details of the plurality of servers such as active servers, capacity of servers, available servers, server location and storage.
  • the determination unit [308] may determine the optimal server based on the stored details of the plurality of servers in the load balancer. In an implementation, the determination unit [308] may use one or more selection algorithm or set of instructions for selecting the optimal server.
  • the system [300] comprises the transceiver unit [302], The transceiver unit [302] is further configured to distribute, using the interface, the one or more requests among the one or more operational microservice instances to the optimal server. After determining the optimal server via the determination unit [308], the transceiver unit [302] is further configured to distribute the one or more requests (e.g., incoming or outgoing) among the one or more operational microservice instances to the optimal server using the LB-SA interface.
  • the transceiver unit [302] is further configured to distribute the one or more requests (e.g., incoming or outgoing) among the one or more operational microservice instances to the optimal server using the LB-SA interface.
  • the load balancer scales atleast one of the one or more registered applications and one or more operational microservice instances based on the traffic load.
  • the load balancer is configured to monitor microservices such as inventory microservice instances and one or more registered applications associated with other microservices details registration. If any inventory instance is down and/or performance is degrading then for managing the traffic load, the load balancer performs scaling of the inventory microservice instance to manage the traffic load.
  • FIG. 4 an exemplary method flow diagram [400], for distributing a traffic load using an interface, in accordance with exemplary implementations of the present disclosure is shown.
  • the method [400] is performed by the system [300], As shown in FIG. 4, the method [400] starts at step [402],
  • the method [400] as disclosed by the present disclosure comprises monitoring, by a monitoring unit [304] using the interface, a health status of one or more registered applications and one or more operational microservice instances, in response to the received one or more requests.
  • the monitoring unit [304] monitors using the LB-SA interface the health status of the one or more registered applications and the one or more operational microservice instances such as a positive health status and a negative health status.
  • the one or more registered application refers to any application or service that is registered within a network management or orchestration framework. Further, the one or more registered applications keep track of their details such as location, status, and available resources.
  • the one or more operational microservice (MS) instances refer to, such as, but not limited to, instances associated with inventory microservice and container service adapter (CSA).
  • the container service adapter may be a docker service adapter.
  • the registered application may be associated with the operational microservice instances, such as registration details procedure application for inventory microservice.
  • the method [400] as disclosed by the present disclosure comprises fetching, by a retrieval unit [306], via an orchestrator manager, a real time health status of the one or more operational microservice instances.
  • the retrieval unit [306] may fetch the real time health status of the one or more operational microservice instances via the orchestrator manager.
  • the one or more microservice (MS) instances may be such as ‘MS-1 instance-1’, ‘MS-2 instance-2’ and ‘MS-n instance-n’.
  • the retrieval unit [306] may fetch real time health status such as positive health status of the ‘MS-1 instance-1’, negative health status of ‘MS-2 instance-2’, and positive health status of ‘MS-n instance-n’ at the orchestrator manager.
  • the orchestrator manager stores real time health status of the one or more operational microservice instances at the orchestrator manager.
  • the method [400] as disclosed by the present disclosure comprises distributing, by the transceiver unit [302], using the interface, the one or more requests among the one or more operational microservice instances to the optimal server.
  • the transceiver unit [302] further may distribute the one or more requests (e.g., incoming or outgoing) among the one or more operational microservice instances to the optimal server using the LB-SA interface.
  • FIG. 5 shows an exemplary block diagram of a system [500] for distributing a traffic load using an interface, in accordance with exemplary implementations of the present disclosure.
  • the system [500] comprises a load balancer (LB) [502] node and a container service adapter (CSA or SA) node [504], More particularly, the LB-SA interface connects the load balancer with the Container service adapter (CSA).
  • the container service adapter may be a docker service adapter.
  • the role of the LB- SA interface is to distribute all incoming and/or outgoing requests to balance load equally in the CSA or SA service.
  • the LB-SA interface automatically distributes incoming traffic across multiple instances of CSA service.
  • the CSA is a microservices-based system designed to deploy and manage Container Network Functions (CNFs) and their components (CNFCs) across container nodes.
  • the container node may be a docker node.
  • the CSA adapter offers representational state transfer (REST) endpoints for key operations, including uploading container images to a container registry, terminating CNFC instances, and creating docker volumes and networks.
  • the container registry may be a docker registry.
  • the container volumes and networks may be docker volumes and networks.
  • CNFs which are network functions packaged as containers, may consist of multiple CNFCs.
  • the CSA facilitates the deployment, configuration, and management of these components by interacting with container's API, ensuring proper setup and scalability within a containerized environment.
  • the container’s API may be a docker’s API.
  • This approach provides a modular and flexible framework for handling network functions in a virtualized network setup.
  • the load balancer monitors a health status of one or more registered applications and one or more operational microservice instances., in response to the received one or more requests. Further, using the interface, the load balancer determines an optimal server from a plurality of servers based on the health status of the one or more operational microservice instances, fetched via an orchestrator manager. Thereafter, using the interface, the load balancer distributes the one or more requests among the one or more operational microservice instances to the optimal server.
  • the system [600] comprises a User Interface (UI/UX) [602], Identity Access Management (IAM) [604] node, Elastic Load Balancer (ELB1) [606a] node, ELB2 [606b] node, Event Routing Management (ERM) node [608], ELB [610a-610b], Container Service Adapter (CSA) [616a-616n], Orchestrator manager (OM) [612], Central Log management System (CLMS) node [614] and Elastic Search Cluster [618], [00079]
  • container service adapter (CSA) may be a docker service adapter
  • CSA refers to such as, unit, server or service which facilitates communication between container and other services or microservices.
  • orchestrator manager refers to such as, unit, node, service or server, which manages service operations of different microservices in the network. Orchestrator manager maintains records details of the operational microservices and share details of the microservices with other microservices for the operational communication.
  • IAM Identity Access Management
  • Elastic Load Balancer [606] refers to such as service, unit, platform for managing and distributing incoming traffic efficiently across a group of supported servers, microservices and units in a manner that may increase speed and performance of the network.
  • Event Routing Management refers to such as, node, server, service or platform for monitoring and triggering various actions or responses within the system based on detected event. For example, for any microservice instance down, the ERM may trigger any alert for taking an action to overcome the service breakdown condition in the network.
  • Central Log management System (CLMS) [614] refers to such as service or platform which may collect log data from multiple sources and may consolidate the collected data. This consolidated data is then presented on a central interface which may be accessed by a user such as network administrator or authorised person.
  • Elastic Search Cluster refers to such as, a group of servers, nodes that work together and form a cluster for distributing tasks, searching and indexing across all the nodes in the cluster.
  • Microservices (MS) instances such as CSA instances, run in n-way active mode.
  • Each MS instance or CSA instance is being served with a pair of Elastic Load Balancers (ELB).
  • ELB Elastic Load Balancers
  • the ELB distributes the load on MS instances in a round-robin manner.
  • ELB ensures that the event acknowledgment against any event that is sent by the MS instance to the subscribed MS is returned to the same MS instance that has published the event.
  • all microservices do not only maintain the state information in their local cache but also persist it in the Elastic Search database.
  • the orchestrator manager detects it and broadcasts the status to other running MS instances and also the ELB serving the MS.
  • the ELB as such distributes the ingress traffic on the remaining available instances.
  • the n- way active model for deployment of MS instances ensures the availability of a microservice to serve the traffic even if any instance goes down.
  • one of the available MS instances takes ownership of the instance which has gone down. It fetches the state information of the incomplete transaction being served by the instance gone down from ES and re-executes them. In case any transaction has not persisted, there may be a timeout, and the publisher MS of that event will re-transmit the same event for execution.
  • the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for distributing a traffic load using an interface, 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, using the interface, one or more requests at a load balancer; a monitoring unit [304] connected at least to the transceiver unit [302], the monitoring unit [304] of the system to monitor, using the interface, a health status of one or more registered applications and one or more operational microservice instances, in response to the received one or more requests; a retrieval unit [306] connected at least to the monitoring unit [304], the retrieval unit [306] of the system to fetch, via an orchestrator manager, a real time health status of the one or more operational microservice instances; a determination unit [308] connected at least to the retrieval unit [306], the determination unit [308] of the system to determine, using the interface, an optimal server from a
  • the present disclosure provides a technically advanced solution of efficient system and method for handling heavy load traffic and distributing the load among servers such that no server is overloaded or overworked.
  • the present method and system provide a LB-SA interface (Load Balancer- Service Adapter interface), which ensures that no server gets overloaded due to bulk traffic.
  • the present system and method provide LB-SA interface, which distributes incoming/outgoing requests easily among all SA instances.
  • the present method and system enable all instantiation, termination and CNF information (metrics, state) operations on the cloud which may be performed on Management and Orchestration (MANO).
  • the present method and system support HTTP/HTTPS configurations in parallel.
  • the present method and system route client requests across all servers in a manner that maximizes speed and capacity utilization.
  • the present method and system may perform header-based routing which may save time and database hits.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un système et un procédé de distribution d'une charge de trafic à l'aide d'une interface. La divulgation comprend la réception, à l'aide de l'interface, d'une ou de plusieurs demandes au niveau d'un équilibreur de charge ; la surveillance, à l'aide de l'interface, d'un état d'une ou de plusieurs applications enregistrées et d'une ou de plusieurs instances de microservice opérationnelles, en réponse à la ou aux demandes reçues ; l'extraction, par l'intermédiaire d'un gestionnaire d'orchestrateur, d'un état en temps réel de la ou des instances de microservice opérationnelles ; la détermination, à l'aide de l'interface, un serveur optimal parmi une pluralité de serveurs sur la base de l'état de la ou des instances de microservice opérationnelles ; et la distribution, à l'aide de l'interface, de la ou les demandes parmi la ou les instances de microservice opérationnelles au serveur optimal.
PCT/IN2024/051750 2023-09-13 2024-09-13 Procédé et système de distribution d'une charge de trafic à l'aide d'une interface Pending WO2025057236A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321061572 2023-09-13
IN202321061572 2023-09-13

Publications (1)

Publication Number Publication Date
WO2025057236A1 true WO2025057236A1 (fr) 2025-03-20

Family

ID=95021892

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051750 Pending WO2025057236A1 (fr) 2023-09-13 2024-09-13 Procédé et système de distribution d'une charge de trafic à l'aide d'une interface

Country Status (1)

Country Link
WO (1) WO2025057236A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012088797A (ja) * 2010-10-15 2012-05-10 Kddi Corp サーバ負荷分散方式
US20170208122A1 (en) * 2016-01-18 2017-07-20 Canon Kabushiki Kaisha Server system, method for controlling server system, and storage medium
US20180167453A1 (en) * 2016-12-14 2018-06-14 Huawei Technologies Co., Ltd. Distributed load balancing system, health check method, and service node

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012088797A (ja) * 2010-10-15 2012-05-10 Kddi Corp サーバ負荷分散方式
US20170208122A1 (en) * 2016-01-18 2017-07-20 Canon Kabushiki Kaisha Server system, method for controlling server system, and storage medium
US20180167453A1 (en) * 2016-12-14 2018-06-14 Huawei Technologies Co., Ltd. Distributed load balancing system, health check method, and service node

Similar Documents

Publication Publication Date Title
US10445136B1 (en) Randomized subrequest selection using request-specific nonce
WO2025062464A1 (fr) Procédé et système de routage d'événements dans un environnement de réseau
WO2025069101A1 (fr) Procédé et système permettant de gérer des ressources de réseau
WO2025057236A1 (fr) Procédé et système de distribution d'une charge de trafic à l'aide d'une interface
WO2025069077A1 (fr) Procédé et système de distribution de trafic de données dans un réseau
WO2025069083A1 (fr) Procédé et système de distribution du trafic de données dans un réseau
WO2025057238A1 (fr) Procédé et système pour faciliter une interconnexion entre une pluralité de microservices
WO2025069084A1 (fr) Procédé et système de gestion d'une ou de plusieurs instances de moteur d'exécution de politique (peegn)
WO2025057235A1 (fr) Procédé et système de gestion de paramètres de fonctionnement d'une ou de plusieurs fonctions réseau (nf)
WO2025062459A1 (fr) Procédé et système de fourniture d'informations relatives à des ressources de réseau dans un environnement de réseau
WO2025062458A1 (fr) Procédé et système de gestion d'une unité de service orchestrateur de conteneur dans un environnement de réseau
WO2025062433A1 (fr) Procédé et système d'équilibrage de charge entre des instances de gestionnaire de capacité
WO2025069098A1 (fr) Procédé et système de gestion d'instances de fonction de réseau virtuel (vnf) dans un réseau
WO2025069085A1 (fr) Procédé et système pour effectuer une ou plusieurs opérations sur une ou plusieurs fonctions de réseau dans un réseau
WO2025062465A1 (fr) Système et procédé d'équilibrage de charge de demandes
WO2025069081A1 (fr) Procédés et systèmes de gestion d'opérations de base de données dans un réseau
WO2025052486A1 (fr) Procédé et système de mise à jour de politiques relatives à des fonctions de réseau dans un environnement de réseau
WO2025069096A1 (fr) Procédé et système de communication entre un microservice et un moteur d'exécution de politique (peegn)
WO2025069110A1 (fr) Procédé et système de fourniture d'informations de fonction de réseau virtuel au niveau d'un moteur d'exécution de politiques
WO2025069067A1 (fr) Procédé et système de gestion de découverte d'un ou de plusieurs microservices
WO2025069056A1 (fr) Procédé et système de gestion de tolérance de panne associée à une unité de service auditeur
WO2025069060A1 (fr) Procédé et système de gestion d'une fonction de réseau
WO2025074391A1 (fr) Procédés et systèmes de mise en œuvre de gestion et d'orchestration de ressources dynamiques dans un réseau
WO2025062457A1 (fr) Procédé et système de routage d'une demande d'événement
WO2025062461A1 (fr) Procédé et système permettant d'exécuter au moins une tâche de service

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24864941

Country of ref document: EP

Kind code of ref document: A1