CN115277569A - Multimedia communication method, system, related equipment and storage medium - Google Patents

Abstract

Embodiments of the present application disclose a multimedia communication method, system, related equipment, and storage medium. The system includes: at least two edge nodes, at least two central nodes, a node scheduler, a terminal, at least two gateways, and a multimedia server; a node The scheduler receives the target call message sent by the target edge node accessed by the terminal, and identifies the target service type of the target call message; and, according to the load corresponding to each gateway and the target service type, determines the target gateway from at least two gateways , and determine the target central node corresponding to the target gateway; the node scheduler sends the target call message to the target central node, and the target central node transmits the target call message to the multimedia server via the target gateway to establish a connection between the terminal and the multimedia server. signaling link. By implementing the embodiments of the present application, refined load scheduling can be performed on the server at the service level, and the availability of the multimedia communication system can be enhanced.

Description

Multimedia communication method, system, related equipment and storage medium

technical field

The present application relates to the technical field of communication, and specifically relates to a multimedia communication method, system, related equipment and storage medium.

Background technique

Scenarios such as online conferences and online video chats often involve data transmission between two or more devices in a multimedia communication system, and multimedia data interaction between devices can be called a multimedia session. In the prior art, a multimedia session can be established, modified and terminated through application layer protocols such as Session Initiation Protocol (SIP) protocol, GB28181 protocol or Real Time Streaming Protocol (RealTime Streaming Protocol, RTSP) protocol. Before multimedia data transmission, the participants in the multimedia session generally need to perform signaling negotiation based on the foregoing protocol.

The process of signaling negotiation requires the participation of the session protocol server. However, with the expansion of services and the increase in the number of access devices, the concurrency required to be carried by the session protocol server is also increasing, which easily exceeds the tolerance range of the server and reduces the availability of the multimedia communication system.

Contents of the invention

The embodiment of the present application discloses a multimedia communication method, system, related equipment, and storage medium, capable of fine-grained load scheduling for servers at the business level, and is conducive to enhancing the usability of the multimedia communication system.

The embodiment of the present application discloses a multimedia communication method, which is applied to a node scheduler in a multimedia communication system, and the multimedia communication system further includes: edge nodes of at least two session protocol server clusters, and centers of at least two session protocol server clusters A node, a terminal, at least two gateways, and a multimedia server; the node scheduler communicates with each of the edge nodes and each of the central nodes; each gateway corresponds to at least one of the central nodes; the method includes: receiving the target call message sent by the target edge node, and identifying the target service type of the target call message; the target edge node is the edge node accessed by the terminal in each of the edge nodes; according to each of the gateways The load corresponding to the target service type, determine the target gateway from the at least two gateways; determine the target central node corresponding to the target gateway from the at least two central nodes; set the target sending a call message to the target central node, so that the target call message is transmitted to the multimedia server via the target central node and the target gateway, so as to establish signaling between the terminal and the multimedia server link.

The embodiment of the present application discloses a multimedia communication method, which is applied to a network load balancer in a multimedia communication system; the multimedia communication system further includes: edge nodes of at least two session protocol server clusters, at least two session protocol server cluster edge nodes A central node, a node scheduler, a terminal, at least two gateways, and a multimedia server; the node scheduler is respectively connected to each of the edge nodes and each of the central nodes; the terminal is connected to the network load balancer, and the The network load balancer is also respectively connected to each of the edge nodes; each of the gateways corresponds to at least one of the central nodes; the method includes: receiving the target call message sent by the terminal; according to each of the edge nodes Determine the target edge node from each of the edge nodes; send the target call message to the target edge node, so as to send the target call message to the node scheduler through the target edge node , so that the target call message reaches the multimedia server via the node scheduler, the target central node and the target gateway, so as to establish a signaling link between the terminal and the multimedia server; wherein, the target center The node is the central node corresponding to the target gateway among the at least two central nodes; the target gateway is that after the node scheduler recognizes the target service type of the target call message, according to each of the gateways and The load corresponding to the target service type is determined from each of the gateways.

The embodiment of the present application discloses a multimedia communication system, including: edge nodes of at least two session protocol server clusters, central nodes of at least two session protocol server clusters, a node scheduler, a terminal, at least two gateways, and a multimedia server; The node scheduler is respectively connected to each of the edge nodes and each of the central nodes; each of the gateways corresponds to at least one of the central nodes; the terminal is used to initiate a target call message and call the target The message is sent to a target edge node; the target edge node is the edge node accessed by the terminal in each of the edge nodes; the target edge node is used to send the target call message to the node scheduling The node scheduler is configured to determine the target gateway from the at least two gateways according to the load corresponding to each of the gateways and the target service type; and, from the at least two central nodes determining a target central node corresponding to the target gateway, and sending the target call message to the target central node; the target central node is configured to send the target call message to the target gateway; The target gateway is configured to send the target call message to the multimedia server, so as to establish a signaling link between the terminal and the multimedia server.

The embodiment of the present application discloses a node scheduler, which is applied to a multimedia communication system, and the multimedia communication system further includes: edge nodes of at least two session protocol server clusters, and centers of at least two session protocol server clusters A node, a terminal, at least two gateways and a multimedia server; the node scheduler communicates with each of the edge nodes and each of the central nodes; each gateway corresponds to at least one of the central nodes; the node scheduler Including: a communication module, configured to receive a target call message sent by a target edge node, and identify the target service type of the target call message; the target edge node is the edge to which the terminal accesses in each of the edge nodes a node; a determining module, configured to determine the target gateway from the at least two gateways according to the load corresponding to each of the gateways and the target service type; and determine the target gateway from the at least two central nodes A target central node corresponding to the target gateway; the communication module is further configured to send the target call message to the target central node, so that the target call message passes through the target central node and the target gateway sent to the multimedia server to establish a signaling link between the terminal and the multimedia server.

The embodiment of the present application discloses a network load balancer, and the network load balancer is applied to a multimedia communication system; the multimedia communication system further includes: edge nodes of at least two session protocol server clusters, at least two session protocol server clusters a central node, a node scheduler, a terminal, at least two gateways, and a multimedia server; the node scheduler is respectively connected to each of the edge nodes and each of the central nodes; the terminal is connected to the network load balancer, The network load balancer is also respectively connected to each of the edge nodes; each of the gateways corresponds to at least one of the central nodes; the network load balancer includes: a transceiver module for receiving the target sent by the terminal A call message; a balancing module, configured to determine a target edge node from each of the edge nodes according to the load of each of the edge nodes; the transceiver module, further configured to send the target call message to the target edge a node, to send the target call message to the node scheduler through the target edge node, so that the target call message reaches the multimedia server via the node scheduler, the target central node and the target gateway, to establish A signaling link between the terminal and the multimedia server; wherein the target central node is a central node corresponding to the target gateway among the at least two central nodes; the target gateway is the node After the scheduler identifies the target service type of the target call message, it is determined from each of the gateways according to the load of each of the gateways corresponding to the target service type.

The embodiment of the present application discloses a service device, including a memory and a processor. The memory stores a computer program. When the computer program is executed by the processor, the processor implements any of the functions disclosed in the embodiment of the present application. A multimedia communication method.

The embodiment of the present application discloses a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any multimedia communication method disclosed in the embodiment of the present application is implemented.

Compared with related technologies, the embodiments of the present application have the following beneficial effects:

The session protocol server cluster that the multimedia communication system may include may include multiple edge nodes and multiple central nodes, and a node scheduler may be set between the edge nodes and the central nodes. After the terminal initiates the target call message, the node scheduler may receive the target call message sent by the target edge node accessed by the terminal, and identify the target service type of the target call message. The node scheduler can further determine the target gateway from at least two gateways according to the load corresponding to each gateway and the target service type, so as to determine the target central node corresponding to the target gateway according to the corresponding relationship between the gateway and the central node. The node scheduler may send the target call message to the target central node, so that the target call message is transmitted to the multimedia server via the target central node and the target gateway, so as to establish a signaling link between the terminal and the multimedia server.

It can be seen that in the embodiment of this application, by setting a node scheduler between the edge node and the central node to perform internal service bridging scheduling scheme, it is possible to carry out refined load balancing at the service level according to the service type of the call, which is beneficial to reduce The problem of server overloading enhances the availability of multimedia communication systems. Moreover, compared to the architecture in which edge nodes are directly connected to central nodes, the bridge scheduling function provided by the node scheduler can realize efficient cluster scheduling of session protocol servers.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the accompanying drawings that need to be used in the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

Fig. 1 is a schematic structural diagram of a multimedia communication system in the related art;

FIG. 2 is a schematic structural diagram of a multimedia communication system disclosed in an embodiment of the present application;

Fig. 3 is a schematic method flow diagram of a multimedia communication method disclosed in an embodiment of the present application;

FIG. 4 is a schematic structural diagram of another multimedia communication system disclosed by an embodiment of the present application;

FIG. 5 is a schematic flow diagram of another multimedia communication method disclosed by an embodiment of the present application;

Fig. 6 is a schematic structural diagram of a node scheduler disclosed in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a network load balancer disclosed in an embodiment of the present application;

Fig. 8 is a schematic structural diagram of a service device disclosed by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the application with reference to the drawings in the embodiments of the application. Apparently, the described embodiments are only some, not all, embodiments of the application. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

It should be noted that the terms "comprising" and "having" and any variations thereof in the embodiments of the present application and the drawings are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally further includes For other steps or units inherent in these processes, methods, products or apparatuses.

In order to more clearly illustrate the multimedia communication method, system, related equipment, and storage medium disclosed in the embodiments of the present application, the following content first introduces the multimedia communication method in the related art.

For ease of description, the following content uses the SIP protocol as an example for description. Please refer to FIG. 1 . FIG. 1 is a schematic structural diagram of a multimedia communication system in the related art. As shown in FIG. 1 , the multimedia communication system may include: a real-time audio-video (Real-Time Communication, RTC) system 110 , a session protocol server cluster 120 , a SIP terminal 130 , a database cluster 140 and an RTC terminal 150 .

The RTC system 110 may include: a gateway cluster 111 , multiple multimedia servers, and a signaling server cluster (SignalServer-Cluster) 113 . The gateway cluster 111 can be connected to each multimedia server through the signaling server cluster 113, wherein the signaling server cluster 113 and the gateway cluster 111 can communicate based on the Hyper Text Transfer Protocol (Hyper TextTransfer Protocol, HTTP) protocol, and the signaling server cluster 113 and Various multimedia servers can communicate based on Remote Procedure Calls (Remote Procedure Calls, RPC).

The gateway cluster 111 may include multiple gateways. The gateway is an interface that converts the SIP protocol and the multimedia communication protocol. For example, if the gateway cluster 111 communicates with the signaling service cluster 113 through the HTTP protocol, the gateway cluster 111 may be used to convert data transmitted based on the SIP protocol into data corresponding to the HTTP protocol.

The multimedia server 112 can provide audio and video data encoding and decoding services, and provide multimedia data service support for application scenarios such as online meetings, audio and video calls, cloud games, and live broadcasting.

The signaling server cluster 113 can provide signaling interaction services for the gateway cluster 111 and the multimedia server 112 .

The session protocol server cluster 120 may include an edge node directly facing the SIP terminal 130 , and a central node facing the gateway cluster 111 . The session protocol server cluster 120 may include multiple edge nodes and multiple central nodes, such as the edge node 121 and the central node 122 shown in FIG. 1 . Wherein, each central node can communicate with one or more edge nodes.

The database cluster 140 can be used to store various data written by the session protocol server cluster 120 and the RTC system 110, and provide a data query function.

The RTC terminal 150 may be any terminal that accesses the RTC system 110 . The RTC terminal 150 can transmit multimedia data with the SIP terminal 130 through the RTC system 110 and the session protocol server cluster 120 .

The SIP protocol is a text-based application layer control protocol that supports the following transport layer protocols: Transmission Control Protocol (Transmission Control Protocol, TCP), User Datagram Protocol (User Datagram Protocol, UDP), Security Transport Layer Protocol (Transport Layer Security, TLS). The SIP protocol specifies the standard for interactive communication between one or more session participants, and can be used to establish, modify, and terminate two-party or multi-party multimedia sessions on the network. Therefore, the participants in the multimedia session need to perform signaling negotiation before transmitting multimedia data to each other. After the signaling negotiation is completed, each participant can establish a multimedia data transmission channel based on communication protocols such as Real-time Transport Protocol (RTP) or Secure Real-time Transport Protocol (SRTP).

Based on the multimedia communication system shown in FIG. 1 , the following content describes the flow of signaling negotiation and multimedia data transmission in the related art.

The SIP terminal 130 initiates a call, and sends a SIP call message corresponding to the call to the accessed edge node 121 . After receiving the SIP call message, the edge node 121 accessed by the SIP terminal 130 sends the SIP call message to the central node 122 communicatively connected with the edge node 121 . The central node 122 sends the SIP call message to the gateway cluster 111 , so that the central node 122 accesses the gateway cluster 111 . The gateway cluster 111 performs protocol conversion on the SIP call message, converts the SIP call message from SIP signaling to HTTP signaling, and sends the converted SIP call message to the multimedia server 112 via the signaling server cluster 113 .

Based on this, the signaling link between the SIP terminal 130 and the multimedia server 112 is established. The signaling link connection relationship in the signaling link includes: the SIP terminal 130 is connected to the edge node 121, and the edge node 121 is connected to the central node. 122, the central node 122 is connected to the gateway cluster 111, and the gateway cluster 111 is connected to the multimedia server 112.

After receiving the SIP call message, the multimedia server 112 can generate a SIP response message, and send the SIP response message to the accessed gateway cluster 111, and the gateway cluster 111 performs protocol conversion, and converts the SIP response message from HTTP signaling to SIP signaling. Command, and send the converted SIP response message to the central node 122, the central node 122 sends the SIP response message to the edge node 121, and then sends the SIP response message to the SIP terminal 130 via the edge node 121.

The SIP call message sent by the SIP terminal 130 can include connection information related to the SIP terminal 130 such as the port of the SIP terminal 130, IP address, life cycle, multimedia capabilities, and supported codec protocols; the SIP response message sent by the multimedia server 112 can include Connection information related to the multimedia server 112 such as the port, IP address, life cycle, multimedia capabilities, and supported codec protocols of the multimedia server 112 .

The SIP terminal 130 completes the signaling negotiation with the multimedia server 112 based on the SIP call message and the SIP response message. Based on the connection information of the SIP terminal 130 received by the multimedia server 112, and the connection information received by the SIP terminal 1300 to the multimedia server 112, the SIP terminal 130 can establish a communication link based on the RTP protocol with the multimedia server 112, and communicate with the multimedia server 112. The communication link carries out the transmission of multimedia data.

It should be noted that the RTC terminal 150 can perform signaling negotiation with the signaling server cluster 113 based on the WebSocket (WS) connection, and establish a communication link based on the RTP protocol with the multimedia server 112 after the signaling negotiation, and communicate with the RTP protocol. The communication link carries out the transmission of multimedia data.

It can be seen that based on the multimedia communication system shown in FIG. 1 , the edge nodes and central nodes in the session protocol server cluster play an important role in the signaling negotiation between the multimedia server and the SIP terminal. However, when the number of terminals connected to the edge node is large, or the terminal initiates calls too frequently in a short period of time, it may increase the load capacity of the session protocol server such as the edge node or the central node, causing the server to crash or go down, thus Reduce the availability of the entire multimedia communication system.

Based on this, the embodiment of the present application discloses a multimedia communication method, system, related equipment, and storage medium, capable of fine-grained load scheduling for servers at the service level, which is beneficial to enhance the usability of the multimedia communication system.

Please refer to FIG. 2 . FIG. 2 is a schematic structural diagram of a multimedia communication system disclosed by an embodiment. As shown in FIG. 2 , the multimedia communication system may include: an RTC system 210 , a session protocol server cluster 220 , and a terminal 230 . Among them, the session protocol server cluster can apply stateful application layer protocols such as SIP, GB28181 or RTSP. For ease of description, the following content uses the SIP protocol as an example for description.

The terminal 230 may be any kind of SIP device, such as a conference collaboration terminal or a personal terminal such as a smart phone.

The RTC system 210 may include: at least two gateways and a multimedia server 214 . As shown in FIG. 2 , the RTC system 210 may include three gateways, namely a gateway 211 , a gateway 212 and a gateway 213 .

It should be noted that the RTC system may also include other service devices such as signaling server clusters, and each gateway may communicate with the multimedia server 214, and the communication process between the gateway and the multimedia server 214 is not limited.

The session protocol server cluster 220 may include: at least two edge nodes, at least two central nodes, and a node scheduler 223 . As shown in FIG. 2 , the session protocol server cluster may include a central node 221 , a central node 222 and an edge node 224 . The node scheduler 223 communicates with each edge node and central node respectively.

The edge nodes and central nodes included in the session protocol server cluster can be used to provide SIP signaling and multimedia data transmission services, and the edge nodes and central nodes can be SIP proxy (SIP Proxy) servers.

Moreover, each gateway included in the RTC system 210 may correspond to one or more central nodes, each gateway may establish a communication connection with the corresponding central node, and transmit data based on the SIP protocol. Taking the gateway 212 as an example, the gateway 212 may correspond to the central node 221 and the central node 222 in the session protocol server cluster 220 respectively, and the gateway 212 may transmit SIP messages with the central node 221 and the central node 222 .

It should be noted that the foregoing node scheduler may be an independent service device, or may be a processing module built in any edge node and bound to the edge node, which is not specifically limited.

Optionally, the multimedia communication system may further include: a database 240 . The database 240 can be respectively connected with each gateway and the node scheduler 223 included in the RTC system. Each gateway can write the current load into the database 240 , and the node scheduler 223 can query the load of each gateway by accessing the database 240 . Wherein, the load of each gateway may be represented by the concurrent call tasks being processed by the gateway, but is not limited thereto.

Based on the multimedia communication system shown in FIG. 2 , please refer to FIG. 3 . FIG. 3 is a schematic flowchart of a multimedia communication method disclosed in an embodiment, which can be applied to the aforementioned node scheduler. As shown in Figure 3, the method may include the following steps:

310. Receive the target call message sent by the target edge node accessed by the terminal, and identify the target service type of the target call message.

The target edge node is an edge node accessed by a terminal among the multiple edge nodes included in the multimedia communication system, and the embodiment of the present application does not limit the manner of determining the target edge node. Exemplarily, the target edge node may be an edge node physically closest to the terminal.

The target call message may be a SIP message generated when the terminal initiates a call.

In the embodiment of the present application, the RTC system can be applied to many different types of services, including but not limited to: teleconferencing, video telephony, and game interaction. When the terminal initiates a call, it can determine the target service type corresponding to the call according to the type of the application program that triggered the call, and write the target service type into the target call message, for example, different codes can represent different service types. After receiving the target call message, the node scheduler can read the target service type from the target call message.

320. Determine the target gateway from at least two gateways according to the loads of the respective gateways corresponding to the target service type.

In the embodiment of the present application, each gateway included in the RTC system can be used to process calls of one or more different service types. When the gateway is capable of handling calls of two or more different service types, the corresponding load can be divided for calls of each service type. Exemplarily, if the gateway can handle two types of service calls, conference call and game interaction, the gateway can separately count the load A corresponding to the conference call and the load B corresponding to the game interaction.

It should be noted that the load of the gateway can be represented by the concurrent calls, and the concurrent calls can have different descriptions according to different service types. Exemplarily, for a call whose business type is a conference call, the concurrency can be described as the number of participants in the conference call; for a call whose business type is a video call, the concurrency can be described as the number of simultaneous calls for a video call; for a business type of For game interaction calls, the concurrency can be described as the number of simultaneous online game interaction.

After identifying the target service type corresponding to this call, the node scheduler can obtain the load corresponding to the target service type of each gateway among the multiple gateways. For example, if the target service type is teleconference, and the RTC system includes three gateways, namely gateway 1, gateway 2, and gateway 3, the node scheduler can obtain the respective loads of gateway 1, gateway 2, and gateway 3 corresponding to teleconferencing quantity.

The load of each gateway acquired by the node scheduler may be sent by the gateway to the corresponding central node, and the central node sends the received load data to the node scheduler. or,

As an optional implementation manner, if the multimedia communication system includes the foregoing database, the database may store loads corresponding to each gateway handling calls of two or more different service types. The node scheduler can query the load of each gateway corresponding to the target business type from the database, which can speed up the speed of obtaining the load of the gateway.

In the embodiment of the present application, the node scheduler may select a gateway with a relatively small load corresponding to the target service type as the target gateway from various gateways included in the RTC system.

As an optional implementation manner, the node scheduler may set a threshold corresponding to the load, and compare the load corresponding to each gateway and the target service type with the threshold. If the load corresponding to a certain gateway and the target service type is lower than the threshold, the node scheduler may determine the gateway as the target gateway. Optionally, if there are multiple gateways whose loads corresponding to the service types are lower than the threshold, the node scheduler may randomly determine a gateway from the multiple gateways whose loads are lower than the threshold as the target gateway; or, the node scheduler The controller may also sequentially select a target gateway from multiple gateways whose loads are lower than the threshold according to a preset sequence, which is not specifically limited.

As another optional implementation manner, the node scheduler may sort the gateways included in the RTC system according to the load corresponding to each gateway and the target service type, and determine the gateway with the smallest corresponding load as the target gateway.

330. Determine a target central node corresponding to the target gateway from at least two central nodes.

In the embodiment of the present application, if the target gateway corresponds to a central node, the node scheduler may directly determine the central node corresponding to the target gateway as the target central node.

If the target gateway corresponds to two or more central nodes, the node scheduler may randomly select a central node from the central nodes corresponding to the target gateway as the target central node. Alternatively, the node scheduler may determine the target central node from the multiple central nodes corresponding to the target node according to the operating status of the multiple central nodes corresponding to the target gateway or the load of each central node.

As an optional implementation, the node scheduler can monitor whether each central node included in the session protocol server cluster is down; if a certain central node is monitored to be down, the node scheduler can record the downtime central node; When scheduling and distributing the target call message, the node scheduler may ignore the downtime central node, and distribute the target call message to the non-downtime central node corresponding to the target gateway. That is to say, the node scheduler can determine the central node corresponding to the target gateway and not downtime as the target central node. Wherein, if the multimedia communication system includes a database, the node scheduler can record the information of the downtime central node into the database. When scheduling and distributing the target call message, the node scheduler can query the information of the downtime central node from the database, so as to determine the non-downtime central node.

340. Send the target call message to the target central node, so that the target call message is transmitted to the multimedia server via the target central node and the target gateway, so as to establish a signaling link between the terminal and the multimedia server.

When the target call message reaches the multimedia server, the establishment of the signaling link between the terminal and the multimedia server is completed, and signaling such as a call response message and a call release message can be transmitted on the signaling link.

In some possible embodiments, the signaling link may include: connecting the terminal to the target edge node, connecting the target edge node to the target central node, connecting the target central node to the target gateway, and connecting the target gateway to the multimedia server. Since the edge node and the central node of the session protocol server cluster are in the same cluster, and based on the session keep-alive mechanism of the session protocol such as SIP, when the node scheduler determines the target central node, and sends the target call message from the target edge node to After the target central node, the target central node can obtain the information of the target edge node from the node scheduler. After the above-mentioned signaling link is established, the target central node can directly communicate with the target edge node without data forwarding via the node scheduler, which can reduce the pressure on the node scheduler to a certain extent.

In some other possible embodiments, the above-mentioned signaling link may also include a node scheduler, and the node scheduler may also serve as a bridge between the target central node and the target edge node, forwarding the signaling sent by the target central node to the target edge node, and/or forward the signaling sent by the target edge node to the target central node.

Exemplarily, with reference to the multimedia communication system shown in FIG. 2 and the multimedia communication method shown in FIG. 3 , the following content describes the process of signaling negotiation and multimedia data transmission based on the multimedia communication system disclosed in the embodiment of the present application.

The terminal 230 can send the target call message to the target edge node 224, and the target edge node 224 can send the target call message to the node scheduler 223, and the node scheduler 224 can identify the target service type of the target call message, and query the RTC from the database 240 Each gateway included in the system 210 corresponds to the load of the target service type. The node scheduler 224 determines the gateway 212 as the target gateway according to the load of each gateway, and then determines the central node 221 as the target central node according to the corresponding relationship between the gateway 212 and the central node. The node scheduler 224 first sends the target call message to the target central node 221, and the target central node 221 sends the target call message to the target gateway 212, and the target gateway 212 sends the target call message to the Multimedia server 214.

Based on this, the signaling link between the terminal 230 and the multimedia server 214 is established. The signaling link connection relationship in the signaling link includes: the terminal 230 is connected to the target edge node 224, and the target edge node 224 is connected to the target center. The node 221 is connected, the target central node 221 is connected to the target gateway 212 , and the target gateway 212 is connected to the multimedia server 214 .

After receiving the call message, the multimedia server 214 may generate a target response message. The target response message is returned to the terminal 230 along the above-mentioned signaling link, and the signaling negotiation is completed.

The target edge node 224 can establish an SRTP connection with the terminal 230 according to the connection information of the terminal 230 in the received target call message; Establish an RTP connection. The interaction of multimedia data between the multimedia server 214 and the terminal 230 may be performed through an SRTP connection and an RTP connection with the target edge node. Wherein, the terminal 230 and the target edge node 224 may be in different networks, so the SRTP connection may be used for multimedia data transmission, so as to improve the security of multimedia data transmission.

In addition, when the call is released, the call release message initiated by the terminal 230 or the multimedia server 214 will be carried out along the original signaling link. That is, the call release message initiated by the terminal 230 will reach the multimedia server 211 via the target edge node 224 , the target central node 221 and the target gateway 212 , thereby completing the call release. Alternatively, the call release message initiated by the multimedia server 211 will reach the terminal 230 via the target gateway 212 , the target central node 221 and the target edge node 224 , thereby completing the call release.

It can be seen that in the foregoing embodiments, by setting a node scheduler between the edge node and the central node to perform internal service bridging scheduling scheme, it is possible to carry out refined load balancing at the service level according to the service type of the call, which is beneficial to reduce the number of servers Overload problems, enhanced availability of multimedia communication systems. Moreover, compared to the architecture in which edge nodes are directly connected to central nodes, the bridge scheduling function provided by the node scheduler can realize efficient cluster scheduling of session protocol servers.

Further, in the foregoing embodiments, each gateway can correspond to multiple central nodes, and the node scheduler can monitor the central nodes. If a central node is down, the node scheduler can skip the downtime when scheduling distribution The server of the target call message is sent to the central node that is not down. That is, multiple central nodes corresponding to the same gateway can back up each other, which can achieve cluster disaster recovery capability, and can also enhance the availability of the entire multimedia communication system.

Please refer to FIG. 4 . FIG. 4 is a schematic structural diagram of another multimedia communication system disclosed by an embodiment. The multimedia communication system shown in FIG. 4 may be optimized on the basis of the multimedia communication system shown in FIG. 2 . Compared with the system shown in FIG. 2 , the multimedia communication system shown in FIG. 4 may further include: a network load balancer 250 .

The network load balancer 250 may be arranged between the terminal 230 and the edge node 221, and the network load balancer may be respectively connected to the terminal 230 and each edge node.

Wherein, the network load balancer 250 may be any kind of service device, which provides a network load balancing (NetworkLoad Balancing, NLB) service.

The network load balancer 250 may allocate a domain name or a virtual IP address (Virtual IP Address, VIP) to the terminal 230 . Multiple terminals included in the multimedia communication system can uniformly access each edge node through their bound domain names or assigned VIPs, and the actual IP addresses of the edge nodes are invisible to the terminals. Therefore, the terminal sends the target call message to the network load balancer according to the assigned domain name or VIP, and the network load balancer determines which edge node to route the target call message to.

Please refer to FIG. 5 . FIG. 5 is a schematic flowchart of another multimedia communication method disclosed by an embodiment. This method can be applied to the aforementioned network load balancer. As shown in Figure 5, the method may include the following steps:

510. Receive the target call message sent by the terminal.

520. Determine a target edge node from each edge node according to the load of each edge node.

In the embodiment of the present application, the load of the edge node may be represented by the concurrency of call tasks being processed by the edge node. The network load balancer can determine the target edge node from multiple edge nodes based on algorithms such as polling and hashing.

As an optional implementation, the network load balancer can also monitor whether each edge node is down, and after receiving the target call message, the network load balancer can skip the edge node that has been down, and will not be down The edge node with a small machine and a small load is determined as the target edge node. The edge node with a small load may be the edge node with the smallest load among the multiple edge nodes, or the edge node with the load lower than the preset load among the multiple edge nodes, which is not specifically limited.

In other words, when an edge node hangs, the network load balancer can skip

530. Send the target call message to the target edge node.

After the network balancer sends the target call message to the target edge node, the target edge node can continue to send the target call message to the aforementioned node scheduler, and the node scheduler performs server scheduling to send the target call message to the RTC multimedia server, Thus, a signaling link between the terminal and the multimedia server is established.

It should be noted that, if the multimedia communication system includes the aforementioned network load balancer, the signaling link between the terminal and the multimedia server may include a network load balancer, and the network load balancer connects the terminal and the target edge node.

In addition, the network load balancer stores the signaling link connection relationship between the target edge node and the terminal that initiates the call in the signaling link. When the call is released, the call release message initiated by the terminal or the multimedia server needs to be forwarded through the network load balancer, so as to ensure that the initiation and release of the call are completed through a consistent signaling link.

That is, after the signaling link is established, the call release message initiated by the terminal is sent by the network load balancer to the target edge node according to the above signaling link connection relationship, and reaches the multimedia network via the target edge node, target central node and target gateway server; or,

After the signaling link is established, the call release message initiated by the multimedia server is sent to the network load balancer through the above-mentioned target gateway, target central node and target edge node, and the network load balancer sends it to the terminal according to the connection relationship of the signaling link .

It can be seen that in the foregoing embodiments, the network load balancer can evenly connect each terminal included in the multimedia communication system to the session protocol server cluster, and connect the terminal and the edge node through the network load balancer, so that each edge node has equivalent functions , the edge nodes in the session protocol server cluster can be expanded infinitely, and the terminals registered on the edge nodes can also be expanded in the same proportion, so that the entire multimedia communication system can theoretically support unlimited access of terminals, which is the SIP access of RTC Ability provides strong performance support.

The embodiment of the present application discloses a multimedia communication system. The system architecture of the multimedia communication system can be shown in FIG. A node, a node scheduler, a terminal, at least two gateways, and a multimedia server; the node scheduler is respectively connected to each edge node and each central node; each gateway corresponds to at least one central node;

The terminal is used to initiate a target call message and send the target call message to a target edge node; the target edge node is an edge node accessed by a terminal in each edge node;

The target edge node is used to send the target call message to the node scheduler;

The node scheduler is used to determine the target gateway from at least two gateways according to the load corresponding to each gateway and the target service type; and determine the target central node corresponding to the target gateway from at least two central nodes, and Send the target call message to the target central node;

The target central node is used to send the target call message to the target gateway;

The target gateway is configured to send the target call message to the multimedia server, so as to establish a signaling link between the terminal and the multimedia server.

In one embodiment, the multimedia communication system further includes: a network load balancer; the network load balancer is respectively connected to the terminal and each edge node. Refer to FIG. 4 for the system structure of the multimedia communication system including the network load balancer.

A network load balancer, configured to receive the target call message sent by the terminal;

The network load balancer is also used to determine the target edge node from at least two edge nodes according to the load of each edge node;

A network load balancer is also used to send targeted call messages to targeted edge nodes.

Please refer to FIG. 6 . FIG. 6 is a schematic structural diagram of a node scheduler disclosed by an embodiment. The node scheduler can be applied to any of the aforementioned multimedia communication systems. As shown in FIG. 6 , the node scheduler 600 may include: a communication module 610 and a determination module 620 .

The communication module 610 is configured to receive the target call message sent by the target edge node, and identify the target service type of the target call message; the target edge node is an edge node accessed by a terminal in each edge node;

The determining module 620 is configured to determine the target gateway from at least two gateways according to the load corresponding to each gateway and the target service type; and determine the target central node corresponding to the target gateway from at least two central nodes;

The communication module 610 is further configured to send the target call message to the target central node, so that the target call message is transmitted to the multimedia server via the target central node and the target gateway, so as to establish a signaling link between the terminal and the multimedia server.

In one embodiment, the determination module 620 is further configured to determine from at least two gateways the target gateway whose load corresponding to the target service type is lower than the threshold; or determine the load corresponding to the target service type from at least two gateways The destination gateway with the smallest amount.

In one embodiment, the multimedia communication system also includes: a database; the database is respectively connected to each gateway and the node scheduler; each gateway handles calls of at least two different service types, and the database stores the different service types handled by each gateway The load corresponding to the call respectively;

The determination module 620 is further configured to query the database for each of the at least two gateways corresponding to the target service type before determining the target gateway from the at least two gateways according to the load corresponding to each gateway and the target service type. load capacity.

In an embodiment, the node scheduler 600 may further include: a monitoring module.

The monitoring module can be used to monitor whether each central node included in the at least two central nodes is down before the determination module 620 determines the target gateway from at least two gateways according to the load corresponding to each gateway and the target service type;

The determining module 620 is further configured to determine a central node that is not down and corresponding to the target gateway from at least two central nodes as the target central node.

It can be seen that implementing the node scheduler disclosed in the foregoing embodiments can perform internal service bridging between the edge node and the central node through the node scheduler, and carry out refined load balancing at the service level according to the service type of the call, which is beneficial to reduce The problem of server overloading enhances the availability of multimedia communication systems. Moreover, compared to the architecture in which edge nodes are directly connected to central nodes, the bridge scheduling function provided by the node scheduler can realize efficient cluster scheduling of session protocol servers.

Please refer to FIG. 7 . FIG. 7 is a schematic structural diagram of a network load balancer disclosed by an embodiment. The network load balancer can be applied to any of the aforementioned multimedia communication systems. As shown in FIG. 7 , the network load balancer 700 may include: a transceiver module 710 and a balancing module 720 .

A transceiver module 710, configured to receive the target call message sent by the terminal;

A balance module 720, configured to determine a target edge node from each edge node according to the load of each edge node;

The transceiver module 710 is also configured to send the target call message to the target edge node, so as to send the target call message to the node scheduler through the target edge node, so that the target call message reaches the multimedia server via the node scheduler, the target central node and the target gateway , to establish a signaling link between the terminal and the multimedia server;

Wherein, the target central node is the central node corresponding to the target gateway among at least two central nodes; the target gateway is that after the node scheduler recognizes the target service type of the target call message, according to the load corresponding to each gateway and the target service type, the identified in each gateway.

In one embodiment, the balancing module 720 can also be used to monitor whether each edge node is down, and determine the non-downtime edge node from at least two edge nodes as the target edge node according to the load of each edge node.

In one embodiment, the transceiver module 710 is also configured to send a call release message initiated by the terminal to the target edge node according to the stored signaling link connection relationship between the target edge node and the terminal in the signaling link, so that the terminal initiates The call release message reaches the multimedia server via the target edge node, the target central node and the target gateway.

Alternatively, the transceiver module 710 is also configured to receive a call release message sent by the target edge node and initiated by the multimedia server, and send the multimedia server the The initiated call release message is sent to the terminal; wherein, the call release message initiated by the multimedia server is transmitted to the target edge node via the target gateway and the target central node.

It can be seen that, by implementing the network load balancer disclosed in the foregoing embodiments, each terminal included in the multimedia communication system can be evenly connected to the session protocol server cluster, and the terminal and the edge node are connected through the network load balancer, so that each edge node has an equivalent Function, the edge nodes in the session protocol server cluster can be infinitely expanded, and the terminals registered on the edge nodes can also be expanded in the same proportion, so that the entire multimedia communication system can theoretically support unlimited access of terminals, which is the basis for RTC's SIP interface. The input capability provides strong performance support.

Please refer to FIG. 8 . FIG. 8 is a schematic structural diagram of a service device disclosed by an embodiment. The service device may be the aforementioned node scheduler or network load balancer. As shown in Figure 8, the node scheduler may include:

a memory 810 storing executable program code;

a processor 820 coupled to the memory 810;

Wherein, the processor 820 invokes the executable program code stored in the memory 810 to execute any one of the multimedia communication methods disclosed in the embodiments of the present application.

The embodiment of the present application discloses a computer-readable storage medium, which stores a computer program, wherein, when the computer program is executed by a processor, any multimedia communication method applied to a node scheduler disclosed in the embodiment of the present application is implemented.

The embodiment of the present application discloses a computer-readable storage medium, which stores a computer program, wherein, when the computer program is executed by a processor, any multimedia communication method using a network load balancer disclosed in the embodiment of the present application is implemented.

The embodiment of the present application discloses a computer program product, the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable the computer to execute any application disclosed in the embodiment of the present application A multimedia communication method based on a node scheduler or a network load balancer.

It should be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Thus, appearances of "in one embodiment" or "in an embodiment" in various places throughout the specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. Those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

In various embodiments of the present application, it should be understood that the sequence numbers of the above-mentioned processes do not necessarily mean the order of execution. The implementation of the examples constitutes no limitation.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, located in one place, or distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the above-mentioned integrated units are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a memory , including several requests to make a computer device (which may be a personal computer, server, or network device, etc., specifically, a processor in the computer device) execute some or all of the steps of the above-mentioned methods in various embodiments of the present application.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium includes read-only Memory (Read-Only Memory, ROM), Random Access Memory (Random Access Memory, RAM), Programmable Read-Only Memory (Programmable Read-only Memory, PROM), Erasable Programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), One-time Programmable Read-Only Memory (OTPROM), Electronically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CompactDisc Read -Only Memory, CD-ROM) or other optical disk storage, magnetic disk storage, tape storage, or any other computer-readable medium that can be used to carry or store data.

The multimedia communication method, system, related equipment, and storage medium disclosed in the embodiments of the present application have been introduced in detail above. In this paper, specific examples have been used to illustrate the principles and implementation methods of the present application. The descriptions of the above embodiments are only used to help Understand the method of this application and its core idea. At the same time, for those skilled in the art, based on the idea of this application, there will be changes in the specific implementation and application scope. In summary, the content of this specification should not be construed as limiting the application.

Claims (14)

1. A multimedia communication method, characterized in that, it is applied to a node scheduler in a multimedia communication system, and the multimedia communication system also includes: edge nodes of at least two session protocol server clusters, at least two session protocol server clusters A central node, a terminal, at least two gateways, and a multimedia server; the node scheduler communicates with each of the edge nodes and each of the central nodes; each gateway corresponds to at least one of the central nodes; the method includes : receiving the target call message sent by the target edge node, and identifying the target service type of the target call message; the target edge node is the edge node accessed by the terminal in each of the edge nodes; Determining a target gateway from the at least two gateways according to the load corresponding to each of the gateways and the target service type; determining a target central node corresponding to the target gateway from the at least two central nodes; sending the target call message to the target central node, so that the target call message is transmitted to the multimedia server via the target central node and the target gateway, so as to establish a relationship between the terminal and the multimedia server signaling link between them. 2. The method according to claim 1, wherein the determining the target gateway from the at least two gateways according to the load corresponding to each of the gateways and the target service type includes: Determining, from the at least two gateways, a target gateway whose load corresponding to the target service type is lower than a threshold; or, A target gateway corresponding to the target service type with the smallest load is determined from the at least two gateways. 3. The method according to claim 1, wherein the multimedia communication system further comprises: a database; the database is respectively connected to each of the gateways and the node scheduler; each of the gateways handles at least two different For calls of service types, the database stores loads corresponding to calls of different service types handled by each gateway; And, before determining the target gateway from the at least two gateways according to the load corresponding to each of the gateways and the target service type, the method further includes: Querying the load of each of the at least two gateways corresponding to the target service type from the database. 4. The method according to claim 1, wherein before determining the target central node corresponding to the target gateway from the at least two central nodes, the method further comprises: monitoring whether each of the central nodes included in the at least two central nodes is down; And, determining the target central node corresponding to the target gateway from the at least two central nodes includes: A central node that is not down and corresponding to the target gateway is determined from the at least two central nodes as the target central node. 5. The method according to claim 1, wherein the multimedia communication system further comprises: a network load balancer; the network load balancer is respectively connected to the terminal and each of the edge nodes, and the terminal Accessing the target edge node through the domain name or virtual IP address allocated by the load balancer; The target edge node is determined by the network load balancer from the at least two edge nodes according to the load of each edge node after receiving the target call message sent by the terminal; The target call message is sent to the target edge node by the network load balancer. 6. The method according to claim 5, wherein the target edge node is the non-downtime node determined from the at least two edge nodes by the network load balancer according to the load of each of the edge nodes. machine edge nodes. 7. The method according to claim 5, wherein the network load balancer stores a signaling link connection relationship between the target edge node and the terminal in the signaling link; After the signaling link is established, the call release message initiated by the terminal is sent by the network load balancer to the target edge node according to the connection relationship of the signaling link, and is sent via the target edge node, The target central node and the target gateway reach the multimedia server; or, After the signaling link is established, the call release message initiated by the multimedia server is transmitted to the network load balancer via the target gateway, the target central node and the target edge node, and the network load balancer The equalizer sends to the terminal according to the connection relationship of the signaling link. 8. A multimedia communication method, characterized in that it is applied to a network load balancer in a multimedia communication system; the multimedia communication system also includes: edge nodes of at least two session protocol server clusters, at least two session protocol server clusters a central node, a node scheduler, a terminal, at least two gateways, and a multimedia server; the node scheduler is respectively connected to each of the edge nodes and each of the central nodes; the terminal is connected to the network load balancer, The network load balancer is also respectively connected to each of the edge nodes; each of the gateways corresponds to at least one of the central nodes; the method includes: receiving a target call message sent by the terminal; determining a target edge node from each of the edge nodes according to the load of each of the edge nodes; sending the target call message to the target edge node, so that the target call message is sent to the node scheduler through the target edge node, so that the target call message passes through the node scheduler, target center a node and a target gateway reach the multimedia server to establish a signaling link between the terminal and the multimedia server; Wherein, the target central node is the central node corresponding to the target gateway among the at least two central nodes; the target gateway is that after the node scheduler recognizes the target service type of the target call message, It is determined from each of the gateways according to the load of each of the gateways corresponding to the target service type. 9. A multimedia communication system, comprising: edge nodes of at least two session protocol server clusters, central nodes of at least two session protocol server clusters, a node scheduler, a terminal, at least two gateways, and a multimedia server; The node scheduler is respectively connected to each of the edge nodes and each of the central nodes; each of the gateways corresponds to at least one of the central nodes; The terminal is configured to initiate a target call message, and send the target call message to a target edge node; the target edge node is the edge node accessed by the terminal in each of the edge nodes; The target edge node is configured to send the target call message to the node scheduler; The node scheduler is configured to determine the target gateway from the at least two gateways according to the load of each of the gateways corresponding to the target service type; and determine the target gateway from the at least two central nodes a target central node corresponding to the target gateway, and sending the target call message to the target central node; The target central node is configured to send the target call message to the target gateway; The target gateway is configured to send the target call message to the multimedia server, so as to establish a signaling link between the terminal and the multimedia server. 10. The system according to claim 9, wherein the multimedia communication system further comprises: a network load balancer; the network load balancer is respectively connected to the terminal and each of the edge nodes; The network load balancer is configured to receive the target call message sent by the terminal; The network load balancer is further configured to determine a target edge node from the at least two edge nodes according to the load of each of the edge nodes; The network load balancer is further configured to send the target call message to the target edge node. 11. A node scheduler, characterized in that, the node scheduler is applied to a multimedia communication system, and the multimedia communication system further comprises: edge nodes of at least two session protocol server clusters, at least two session protocol server cluster edge nodes A central node, a terminal, at least two gateways, and a multimedia server; the node scheduler communicates with each of the edge nodes and each of the central nodes; each gateway corresponds to at least one of the central nodes; the node scheduler Devices include: A communication module, configured to receive a target call message sent by a target edge node, and identify a target service type of the target call message; the target edge node is the edge node accessed by the terminal in each of the edge nodes; A determining module, configured to determine the target gateway from the at least two gateways according to the load corresponding to the target service type of each of the gateways; and determine the target gateway from the at least two central nodes The target central node corresponding to the target gateway; The communication module is further configured to send the target call message to the target central node, so that the target call message is transmitted to the multimedia server via the target central node and the target gateway, so as to establish the A signaling link between the terminal and the multimedia server. 12. A network load balancer, characterized in that the network load balancer is applied to a multimedia communication system; the multimedia communication system also includes: edge nodes of at least two session protocol server clusters, at least two session protocol server clusters The central node of the cluster, a node scheduler, a terminal, at least two gateways, and a multimedia server; the node scheduler is respectively connected to each of the edge nodes and each of the central nodes; the terminal is connected to the network load balancer , the network load balancer is also respectively connected to each of the edge nodes; each of the gateways corresponds to at least one of the central nodes; the network load balancer includes: a transceiver module, configured to receive the target call message sent by the terminal; A balance module, configured to determine a target edge node from each of the edge nodes according to the load of each of the edge nodes; The transceiver module is further configured to send the target call message to the target edge node, so that the target call message is sent to the node scheduler through the target edge node, so that the target call message passes through The node scheduler, target central node and target gateway reach the multimedia server to establish a signaling link between the terminal and the multimedia server; Wherein, the target central node is the central node corresponding to the target gateway among the at least two central nodes; the target gateway is that after the node scheduler recognizes the target service type of the target call message, It is determined from each of the gateways according to the load of each of the gateways corresponding to the target service type. 13. A service device, characterized by comprising a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor realizes the process according to claims 1 to 7. Or the method described in any one of 8. 14. A computer-readable storage medium on which a computer program is stored, wherein the computer program implements the method according to any one of claims 1 to 7 or 8 when executed by a processor.

Images