CN115714778A - SIP dynamic load balancing method, system, equipment and storage medium - Google Patents
SIP dynamic load balancing method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN115714778A CN115714778A CN202211220660.1A CN202211220660A CN115714778A CN 115714778 A CN115714778 A CN 115714778A CN 202211220660 A CN202211220660 A CN 202211220660A CN 115714778 A CN115714778 A CN 115714778A
- Authority
- CN
- China
- Prior art keywords
- endpoint
- load balancing
- service
- sip
- micro
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000012544 monitoring process Methods 0.000 claims abstract description 20
- 230000008859 change Effects 0.000 claims abstract description 11
- 238000012545 processing Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000009467 reduction Effects 0.000 abstract description 2
- 240000006740 Cichorium endivia Species 0.000 abstract 1
- 235000003733 chicria Nutrition 0.000 abstract 1
- 238000013515 script Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 4
- 238000007792 addition Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- 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/1025—Dynamic adaptation of the criteria on which the server selection is based
-
- 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/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention provides a method, a system, equipment and a storage medium for SIP dynamic load balancing, wherein the method comprises the steps of reading the IP address of Opensips, the service name of a database mariardb and the names of all micro-services to be monitored; acquiring a mariaddb password; connecting a maridb database according to the password of maridb; starting a kubernetesentroller monitoring service to monitor changes in all endives; if any endpoint is monitored to be changed, matching the changed endpoint with the name of the micro-service in the configuration; acquiring an endpoint pointer of the micro service successfully matched and adding the endpoint pointer to the tail of the workQueue; and analyzing microservice endpoint information in the task of the workQueue. The invention can lead the Opensips micro-service under the cloud native environment to timely and dynamically sense the change of the load balancing route without manual operation; meanwhile, the invention dynamically adapts to the capacity expansion and the capacity reduction of the SIP micro-service, thereby improving the reliability and the adaptability of the system.
Description
Technical Field
The invention belongs to the technical field of communication, and particularly relates to a method, a system, equipment and a storage medium for SIP dynamic load balancing.
Background
SIP (Session Initiation Protocol) is a text-based application-layer signaling control Protocol for multiparty multimedia communication. SIP is independent of underlying transport protocols, is used to establish, modify and terminate two-party or multiparty multimedia sessions over IP networks, and is a signaling protocol for implementing real-time communication applications in IP-based networks. There are two types of SIP messages: client-to-server requests and server-to-client responses.
In the request from the client to the server, when a message is sent from the mobile phone, the SIP load balancing service Opensips receives the message through modules such as SIP access and the like, and balances different message types and loads to corresponding service modules for processing. Traditional opensis provides load balancing capability for micro-services according to routing scripts, but in a cloud native environment, signaling layer message receiving micro-services need to follow a 12-factors methodology, stateless type Deployment of Deployment by using Deployment is not feasible by relying on a constant routing script, and the following two reasons mainly exist: 1. after the micro-service is in error or manually restarted, the IP and pod names in the micro-service k8s cluster are changed, and the Opensips routing script cannot be manually updated in time, so that link failure is caused; 2. when the micro service is expanded and contracted, manual modification is needed, and the manual modification has the problems of time delay and the possibility of errors. Therefore, there is a need to solve the problem that the traditional sip load balancing cannot dynamically update the route in real time in the cloud native environment.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a method, a system, equipment and a storage medium for balancing SIP dynamic load.
In a first aspect, the present invention provides a SIP dynamic load balancing method, including:
reading the IP address of Opensips, the service name of a database mariardb and the names of all micro-services to be monitored;
acquiring a maridb password;
connecting a maridb database according to the password of maridb;
starting a kubernetes controller monitoring service to monitor changes of all endpoints;
if any endpoint is monitored to be changed, matching the changed endpoint with the name of the micro-service in the configuration;
acquiring an endpoint pointer of the micro service successfully matched and adding the endpoint pointer to the tail of the workQueue work queue;
and analyzing the microservice endpoint information in the task of the workQueue.
Further, initiating the kubernets controller monitoring service to monitor changes in all endpoints includes initializing the kubernets controller module.
Further, the analyzing microservice endpoint information in the task of the workQueue includes:
judging the type of the current update;
if the current updating type is the addition or updating of endpoint, updating the IP information of the newly added or updated endpoint, and enabling the state;
if the newly added or updated endpoint does not update the IP information or the state is not enabled, continuing to process the next task;
if the current updating type is deleting endpoint, connecting the maridb database, and deleting the routing information corresponding to the micro service;
adding newly-added items in a mariardb database and recording IP (Internet protocol) and port information of endpoint;
sending an HTTP message to trigger Opensips to update a load balancing route;
if the current updated type is other types that are not supported, processing continues with the next task.
Further, if the type of the current update is to add or update endpoint, the IP information of the newly added or updated endpoint is updated, and the state enable includes:
connecting a mariardb database, and deleting the routing information corresponding to the micro service;
adding newly-added items and recording IP (Internet protocol) and port information of endpoint in a mariardb database;
and sending an HTTP message to trigger Opensps to update the load balancing routing information.
In a second aspect, the present invention provides a SIP dynamic load balancing system, including:
the reading module is used for reading the IP address of Opensps, the service name of the database mariardb and the names of all micro-services to be monitored;
the first acquisition module is used for acquiring the password of maridb;
the connection module is used for connecting a mariaddb database according to the password of the mariaddb;
the monitoring starting module is used for starting a kubernetes controller monitoring service to monitor the change of all endpoints;
the name matching module is used for matching the changed endpoint with the micro-service name in the configuration under the condition that the monitoring starting module monitors the change of any endpoint;
the second acquisition module is used for acquiring an endpoint pointer of the successfully matched micro service and adding the endpoint pointer to the tail of the workQueue work queue;
and the analysis module is used for analyzing microservice endpoint information in the task of the workQueue.
Further, the SIP dynamic load balancing system further includes an initialization module configured to initialize the kubernets controller module.
Further, the parsing module includes:
the judging unit is used for judging the type of the current update;
an updating unit, configured to update the IP information of the endpoint newly added or updated, and state enable, when the determining unit determines that the type of the current update is the endpoint added or updated;
a first task processing unit, configured to continue processing a next task in a case where the update unit does not update the IP information of the newly added or updated endpoint, or the state is not enabled;
the deleting unit is used for connecting the maridb database and deleting the routing information corresponding to the micro service under the condition that the judging unit determines that the current updating type is the deleted endpoint;
the adding unit is used for adding newly-added items in the maridb database and recording IP (Internet protocol) and port information of endpoint;
the sending unit is used for sending HTTP messages to trigger Opensips to update the load balancing route;
and the second task processing unit is used for continuously processing the next task when the judging unit determines that the current updated type is other types which are not supported.
Further, the update unit includes:
the deleting device is used for connecting the mariardb database and deleting the routing information corresponding to the micro service;
the adding device is used for adding newly-added items in the maridb database and recording IP (Internet protocol) and port information of endpoint;
and the sending device is used for sending the HTTP message to trigger Opensips to update the load balancing routing information.
In a third aspect, the invention provides a computer device comprising a processor and a memory; wherein, the processor implements the steps of the SIP dynamic load balancing method according to the first aspect when executing the computer program stored in the memory.
In a fourth aspect, the present invention provides a computer readable storage medium for storing a computer program; the computer program when executed by the processor implements the steps of the SIP dynamic load balancing method of the first aspect.
The invention provides a method, a system, equipment and a storage medium for SIP dynamic load balancing, wherein the method comprises the steps of reading the IP address of Opensips, the service name of a database mariardb and the names of all micro-services to be monitored; acquiring a maridb password; connecting a maridb database according to the password of maridb; starting a kubernetes controller monitoring service to monitor changes of all endpoints; if any endpoint is monitored to be changed, matching the changed endpoint with the micro-service name in the configuration; acquiring an endpoint pointer of the micro service successfully matched and adding the endpoint pointer to the tail of the workQueue work queue; and analyzing microservice endpoint information in the task of the workQueue. The invention can lead the Opensips micro-service under the cloud native environment to timely and dynamically sense the change of the load balancing route without manual operation; meanwhile, the invention dynamically adapts to the capacity expansion and the capacity reduction of the SIP micro-service, thereby improving the reliability and the adaptability of the system.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1 is a flowchart of an SIP dynamic load balancing method according to an embodiment of the present invention;
fig. 2 is a structure diagram of a sip uplink load balancing process in a cloud native environment according to an embodiment of the present invention;
fig. 3 is a flowchart of monitoring SIP dynamic load balancing according to an embodiment of the present invention;
fig. 4 is a flowchart of processing a SIP dynamic load balancing task according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an SIP dynamic load balancing system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As described in the background art, as shown in fig. 2, in a request from a client to a server, when a mobile phone sends a message, the SIP load balancing service Opensips receives the message via modules such as an SIP access module, and balances different message types and loads to corresponding service modules for processing. Traditional opensis provides load balancing capability for micro-services according to routing scripts, but in a cloud native environment, signaling layer message receiving micro-services need to follow a 12-factors methodology, stateless type Deployment of Deployment by using Deployment is not feasible by relying on a constant routing script, and the following two reasons mainly exist: 1. after the micro-service is in error or manually restarted, the IP and pod names in the micro-service k8s cluster are changed, and the Opensips routing script cannot be manually updated in time, so that link failure is caused; 2. when the micro service is expanded and contracted, manual modification is needed, and the manual modification has the problems of time delay and the possibility of errors. Therefore, there is a need to solve the problem that the traditional sip load balancing cannot dynamically update the route in real time in the cloud native environment.
Therefore, in order to solve the above problem, in an embodiment, as shown in fig. 1 and fig. 3, an embodiment of the present invention provides a SIP dynamic load balancing method, including:
And step 103, connecting the maridb database according to the password of the maridb.
Before the step, the method further comprises initializing a kubernets controller module. Changes in endpoints, whether additions or deletions of endpoints or updates of status, IP, etc., are monitored.
And step 105, if any endpoint is monitored to be changed, matching the changed endpoint with the micro-service name in the configuration.
And step 106, acquiring an endpoint pointer of the successfully matched micro-service and adding the endpoint pointer to the tail of the workQueue work queue to ensure the orderliness. If the match is not successful, monitoring continues.
And step 107, analyzing microservice endpoint information in the task of the workQueue.
As shown in fig. 4, in this step, the type of the current update is determined.
And if the type of the current update is addition or update endpoint, updating the IP information of the newly added or updated endpoint, and enabling the state.
Connecting the maridb database, and deleting the routing information corresponding to the micro service; adding newly-added items and recording IP (Internet protocol) and port information of endpoint in a mariardb database; and sending HTTP message to trigger Opensips to update the load balancing routing information.
And if the newly added or updated endpoint does not update the IP information or the state is not enable, continuing to process the next task.
And if the current updating type is deleting endpoint, connecting the maridb database and deleting the routing information of the corresponding micro service.
And adding a newly added entry in the maridb database and recording the IP and port information of endpoint.
The routing data stored for the maridb database is as follows:
HTTP messages are sent to trigger Opensips to update load balancing routing.
If the current updated type is other types that are not supported, processing continues with the next task.
And 101-107, deploying a cloud native micro-service sip-endpoint-watch in the cluster. Although the IP and the port name of the message receiving microservice are both changed, the only change is the name of the service endpoint. The invention can dynamically monitor the change condition of the SIP message receiving micro-service endpoint resource, and maintain a current SIP message receiving micro-service state list in the maridb database for Opensips load balancing routing. The service state list comprises the message type, the IP address and the working state of the SIP micro-service. If the change of any related micro service is monitored, the business logic is judged, if the current routing configuration with balanced load is influenced, an HTTP message is immediately sent to Opposips after the database is successfully updated, and the Opposips is triggered to carry out routing overloading, so that the effect of dynamic load balancing is achieved.
The sip-endpoint-watch module is written by GO language, calls a Client-GO library, and customizes a Kubernets controller for monitoring kubernets resource, wherein the Kubernets controller mainly comprises Clients, informer, callback, workQueue and worker. The invention applies a whole set of kubernets controller logic, customizes service and configuration, and adds a maridb database and sends HTTP message to trigger Opensips update according to the actual service logic of sip load balance in the cloud native environment.
The dynamic load balancing method provided by the invention is a dynamic monitoring and updating method, is not bound with SIP, opensips and database mariaddb services, and can be selected according to specific requirements under a cloud native environment.
Based on the same inventive concept, the embodiment of the present invention further provides an SIP dynamic load balancing system, and since the principle of solving the problem of the system is similar to that of the foregoing SIP dynamic load balancing method, the implementation of the system can refer to the implementation of the SIP dynamic load balancing method, and the repeated parts are not described again.
In another embodiment, an SIP dynamic load balancing system provided by an embodiment of the present invention, as shown in fig. 5, includes:
the reading module 10 is used for reading the IP address of Opensips, the service name of the database mariardb, and the names of all micro-services to be monitored.
A first obtaining module 20, configured to obtain the password of maridb.
And the connection module 30 is used for connecting the mariardb database according to the password of the mariardb.
And the monitoring starting module 40 is used for starting a kubernetes controller monitoring service to monitor the change of all endpoints.
And the name matching module 50 is used for matching the changed endpoint with the micro-service name in the configuration under the condition that the monitoring starting module monitors any endpoint change.
And a second obtaining module 60, configured to obtain an endpoint pointer of the successfully matched micro service and add the endpoint pointer to the tail of the workQueue work queue.
And the analysis module 70 is used for analyzing the microservice endpoint information in the task of the workQueue.
Optionally, the SIP dynamic load balancing system further includes an initialization module, configured to initialize the kubernets controller module.
Optionally, the parsing module includes:
and the judging unit is used for judging the type of the current update.
And the updating unit is used for updating the IP information of the newly added or updated endpoint and enabling the state when the judging unit determines that the type of the current update is the added or updated endpoint.
And the first task processing unit is used for continuously processing the next task under the condition that the updating unit does not update the IP information of the newly added or updated endpoint or the state is not enabled.
And the deleting unit is used for connecting the maridb database and deleting the routing information corresponding to the micro service under the condition that the judging unit determines that the current updating type is endpoint deletion.
And the adding unit is used for adding the newly added entry in the maridb database and recording the IP and port information of the endpoint.
And the sending unit is used for sending the HTTP message to trigger Opensips to update the load balancing route.
And the second task processing unit is used for continuously processing the next task when the judging unit determines that the current updated type is other types which are not supported.
Optionally, the updating unit includes:
and the deleting device is used for connecting the maridb database and deleting the routing information of the corresponding micro service.
And the adding device is used for adding the newly added entries in the maridb database and recording the IP and port information of the endpoint.
And the sending device is used for sending the HTTP message to trigger Opensips to update the load balancing routing information.
For more specific working processes of the modules, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
In another embodiment, an embodiment of the present invention further provides a computer device, including a processor and a memory; the processor implements the SIP dynamic load balancing method disclosed in the foregoing embodiments when executing the computer program stored in the memory.
For more specific processes of the above method, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
In another embodiment, an embodiment of the present invention further provides a computer-readable storage medium for storing a computer program; the computer program when executed by a processor implements the SIP dynamic load balancing method disclosed previously.
For more specific processes of the above method, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The system, the device and the storage medium disclosed by the embodiment correspond to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be substantially or partially embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the method according to the embodiments or some parts of the embodiments.
The invention has been described in detail with reference to specific embodiments and illustrative examples, but the description is not intended to be construed in a limiting sense. Those skilled in the art will appreciate that various equivalent substitutions, modifications or improvements may be made to the technical solution of the present invention and its embodiments without departing from the spirit and scope of the present invention, which fall within the scope of the present invention. The scope of the invention is defined by the appended claims.
Claims (10)
1. A SIP dynamic load balancing method is characterized by comprising the following steps:
reading the IP address of Opensips, the service name of a database mariardb and the names of all micro-services to be monitored;
acquiring a maridb password;
connecting a maridb database according to the password of maridb;
starting a kubernetes controller monitoring service to monitor changes of all endpoints;
if any endpoint is monitored to be changed, matching the changed endpoint with the name of the micro-service in the configuration;
acquiring an endpoint pointer of the micro service successfully matched and adding the endpoint pointer to the tail of the workQueue work queue;
and analyzing microservice endpoint information in the task of the workQueue.
2. The SIP dynamic load balancing method of claim 1, wherein initiating the kubernets controller monitoring service to monitor changes in all endpoints comprises initializing a kubernets controller module.
3. The SIP dynamic load balancing method according to claim 1, wherein the parsing microservice endpoint information in the task of workQueue includes:
judging the type of the current update;
if the current updating type is the addition or updating of endpoint, updating the IP information of the newly added or updated endpoint, and enabling the state;
if the newly added or updated endpoint does not update the IP information or the state is not enabled, continuing to process the next task;
if the current updating type is deleting endpoint, connecting the maridb database, and deleting the routing information corresponding to the micro service;
adding newly-added items in a mariardb database and recording IP (Internet protocol) and port information of endpoint;
sending an HTTP message to trigger Opensps to update the load balancing route;
if the current updated type is other types that are not supported, processing continues with the next task.
4. The SIP dynamic load balancing method according to claim 3, wherein if the current update type is adding or updating endpoint, updating the IP information of the newly added or updated endpoint, and the status enable includes:
connecting the maridb database, and deleting the routing information corresponding to the micro service;
adding newly-added items and recording IP (Internet protocol) and port information of endpoint in a mariardb database;
and sending HTTP message to trigger Opensips to update the load balancing routing information.
5. A SIP dynamic load balancing system, comprising:
the reading module is used for reading the IP address of Opensips, the service name of the database mariardb and the names of all micro-services to be monitored;
the first acquisition module is used for acquiring the password of maridb;
the connection module is used for connecting the maridb database according to the password of the maridb;
the monitoring starting module is used for starting a kubernetes controller monitoring service to monitor the change of all endpoints;
the name matching module is used for matching the changed endpoint with the micro-service name in the configuration under the condition that the monitoring starting module monitors the change of any endpoint;
the second acquisition module is used for acquiring an endpoint pointer of the successfully matched micro service and adding the endpoint pointer to the tail of the workQueue work queue;
and the analysis module is used for analyzing the microservice endpoint information in the task of the workQueue.
6. The SIP dynamic load balancing system of claim 5, further comprising an initialization module configured to initialize the kubernets controller module.
7. The SIP dynamic load balancing system of claim 5, wherein the parsing module comprises:
the judging unit is used for judging the type of the current update;
an updating unit, configured to update the IP information of the endpoint newly added or updated, and state enable, when the determining unit determines that the type of the current update is the endpoint added or updated;
a first task processing unit, configured to continue processing a next task in a case where the update unit does not update the IP information of the newly added or updated endpoint, or the state is not enabled;
the deleting unit is used for connecting the maridb database and deleting the routing information corresponding to the micro service under the condition that the judging unit determines that the current updating type is the deleted endpoint;
the adding unit is used for adding newly-added items in the mariardb database and recording IP (Internet protocol) and port information of endpoint;
the sending unit is used for sending HTTP messages to trigger Opensips to update the load balancing route;
and the second task processing unit is used for continuously processing the next task when the judging unit determines that the current updated type is other unsupported types.
8. The SIP dynamic load balancing system according to claim 7, wherein the updating unit comprises:
the deleting device is used for connecting the mariardb database and deleting the routing information corresponding to the micro service;
the adding device is used for adding newly-added items in the mariardb database and recording IP (Internet protocol) and port information of endpoint;
and the sending device is used for sending the HTTP message to trigger Opensips to update the load balancing routing information.
9. A computer device comprising a processor and a memory; wherein the steps of the SIP dynamic load balancing method of any of claims 1-4 are implemented when the processor executes the computer program stored in the memory.
10. A computer-readable storage medium for storing a computer program; the computer program when executed by a processor implements the steps of the SIP dynamic load balancing method of any of claims 1-4.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211220660.1A CN115714778A (en) | 2022-10-08 | 2022-10-08 | SIP dynamic load balancing method, system, equipment and storage medium |
| PCT/CN2023/119011 WO2024074091A1 (en) | 2022-10-08 | 2023-09-15 | Sip dynamic load balancing method and system, and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211220660.1A CN115714778A (en) | 2022-10-08 | 2022-10-08 | SIP dynamic load balancing method, system, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115714778A true CN115714778A (en) | 2023-02-24 |
Family
ID=85231039
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211220660.1A Pending CN115714778A (en) | 2022-10-08 | 2022-10-08 | SIP dynamic load balancing method, system, equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115714778A (en) |
| WO (1) | WO2024074091A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024074091A1 (en) * | 2022-10-08 | 2024-04-11 | ***数智科技有限公司 | Sip dynamic load balancing method and system, and device and storage medium |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9917746B2 (en) * | 2014-11-04 | 2018-03-13 | Futurewei Technologies, Inc. | Adaptive allocation of server resources |
| US10735553B2 (en) * | 2016-11-23 | 2020-08-04 | Level 3 Communications, Llc | Micro-services in a telecommunications network |
| CN109962904B (en) * | 2017-12-26 | 2020-09-01 | 中移动信息技术有限公司 | Kubernetes-based IMS system |
| CN112000448B (en) * | 2020-07-17 | 2023-08-25 | 北京计算机技术及应用研究所 | Application management method based on micro-service architecture |
| US11729263B2 (en) * | 2020-09-22 | 2023-08-15 | Ribbon Communications Operating Company, Inc. | Methods, apparatus and systems for cloud native application multi-factor load balancing |
| EP4264856A1 (en) * | 2020-12-16 | 2023-10-25 | Telefonaktiebolaget LM Ericsson (publ) | First ims node, second server, subscriber server and methods in a communications network |
| CN115714778A (en) * | 2022-10-08 | 2023-02-24 | ***数智科技有限公司 | SIP dynamic load balancing method, system, equipment and storage medium |
-
2022
- 2022-10-08 CN CN202211220660.1A patent/CN115714778A/en active Pending
-
2023
- 2023-09-15 WO PCT/CN2023/119011 patent/WO2024074091A1/en unknown
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024074091A1 (en) * | 2022-10-08 | 2024-04-11 | ***数智科技有限公司 | Sip dynamic load balancing method and system, and device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024074091A1 (en) | 2024-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020228505A1 (en) | Method, device, and system for selecting mobile edge computing node | |
| US9794365B2 (en) | Re-establishing push notification channels via user identifiers | |
| US10447775B2 (en) | System and method to balance servers based on server load status | |
| EP3389219B1 (en) | Access request conversion method and device | |
| US8140695B2 (en) | Load balancing and failover of distributed media resources in a media server | |
| US10958568B2 (en) | Topology aware load balancing engine | |
| USRE45806E1 (en) | System and method for the optimization of database access in data base networks | |
| US20080162709A1 (en) | System for processing application protocol requests | |
| CN113259479B (en) | Data processing method and equipment | |
| CN113992738A (en) | Reverse proxy method, device, equipment and storage medium based on micro service gateway | |
| US9652367B1 (en) | Exploratory testing on multiple system landscapes | |
| WO2024074091A1 (en) | Sip dynamic load balancing method and system, and device and storage medium | |
| CN113342547A (en) | Remote service calling method and device, electronic equipment and readable storage medium | |
| CN111556135A (en) | Request scheduling method, system and device and electronic equipment | |
| CN113342503B (en) | Real-time progress feedback method, device, equipment and storage medium | |
| CN113191889A (en) | Wind control configuration method, configuration system, electronic device and readable storage medium | |
| CN107682271B (en) | Method and device for generating routing line | |
| CN113746851B (en) | Proxy system and method supporting real-time analysis of GRPC request | |
| US7587449B2 (en) | Method and system for calculating performance metrics using backchannel messaging and information pattern matching | |
| CN112929453B (en) | Method and device for sharing session data | |
| CN114615315A (en) | Communication method, device, equipment and storage medium for online conversation | |
| CN108848175B (en) | Method and device for establishing TCP connection | |
| CN112804291A (en) | Remote equipment auditing method, device and system | |
| CN114448703B (en) | Request processing method, request processing device, electronic equipment and storage medium | |
| CN115102854B (en) | Remote procedure call route management control method, system and equipment for micro-service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |