A method of scheduling cascaded communication between systems and a storage medium

Abstract

The application discloses a method for scheduling inter-system cascade communication and a storage medium, comprising the following steps: regarding all service ends and client ends in each scheduling system as a system node as a whole, and allocating a unique node ID and a main IP address to the system node; meanwhile, allocating different user IDs and slave IP addresses to each client end under each scheduling system; the service ends under the same scheduling system share the unique node ID and the main IP address, and correspond to the service ends under different scheduling systems through the node ID and the main IP address; each scheduling system maintains a node routing table and a connected node table; and the different scheduling systems which establish cascade communication perform instant message cascade communication, register cascade communication and audio and video cascade communication through the node routing table and the connected node table. The application can realize non-perception cascade communication of the client ends between different scheduling systems through the routing forwarding mechanism between the service ends.

Description

Technical Field

[0001] This invention relates to the field of communication technology for scheduling systems, and in particular to a method and storage medium for cascading communication between scheduling systems. Background Technology

[0002] Existing dispatch systems are not interconnected. For example, dispatch system A is deployed in the command center, and dispatch system B is deployed in the command vehicle. If personnel in the command center want to communicate with personnel in the command vehicle, they must perform the following operations:

[0003] Establish a physical link between the command vehicle and the command center;

[0004] All personnel in the command center and command vehicle must log into the dispatch system A on the command center;

[0005] The command center must be equipped with the user system on the command vehicle.

[0006] However, the above operations usually have the following drawbacks:

[0007] (1) The physical networks of the command vehicle and the command center must be fully connected, and the terminals on the command vehicle must be able to be directly connected to the command center's dispatch system.

[0008] (2) Users in the command vehicle need to switch the login server to the command center, which will increase the difficulty of operation for users.

[0009] (3) All user communications (including those on the command vehicle) must be relayed through the command center dispatch system. If the physical bandwidth between the command vehicle and the command center is limited, it will lead to poor communication quality and problems such as video screen tearing and stuttering, and voice delay. Summary of the Invention

[0010] The technical problem to be solved by the present invention is to provide a method and storage medium for cascading communication between scheduling systems, so as to realize seamless cascading communication between clients of different nodes.

[0011] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows:

[0012] A method for cascading communication between scheduling systems, comprising the following steps:

[0013] S1. Treat all servers and clients in each scheduling system as a whole as a system node, and assign it a unique node ID and master IP address. At the same time, assign a different user ID and slave IP address to each client under each scheduling system.

[0014] S2. Servers under the same scheduling system share a unique node ID and master IP address, and are cascaded with servers under different scheduling systems through the node ID and master IP address;

[0015] S3. Each scheduling system maintains a node routing table and a connected node table;

[0016] The node routing table records the node ID of the current system and its corresponding master IP address, as well as the node ID of the connected system and its corresponding master IP address.

[0017] The connected node table records the node IDs of the connected systems and their corresponding master IP addresses, the user IDs of each client in the current system and their corresponding slave IP addresses, and the user IDs of each client in the connected systems and their respective master IP addresses.

[0018] S4. Establish cascaded communication between different scheduling systems through the node routing table and the connected node table, including instant message cascaded communication, registration cascaded communication, and audio / video cascaded communication.

[0019] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows:

[0020] A storage medium for cascading communication between scheduling systems includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the aforementioned method for cascading communication between scheduling systems.

[0021] The beneficial effects of this invention are as follows: This invention provides a method and storage medium for cascading communication between scheduling systems. By treating each scheduling system as a node and assigning a unique node ID and master IP address to each node, the servers of each scheduling system can be directly cascaded through the node ID and master IP address. At the same time, each scheduling system maintains its own node routing table and connected node table. Through the routing and forwarding mechanism between servers, seamless cascading communication between clients across systems is achieved, realizing hierarchical scheduling. Meanwhile, clients under the same scheduling system are not limited by the cascading between systems. Even if the cascading between systems is broken, the client ID and its slave IP address recorded in the connected node table can still be transparently transmitted by the local server under the current scheduling system. That is, communication between users within the same scheduling system does not need to go through the superior scheduling system, effectively saving wired bandwidth resources. Attached Figure Description

[0022] Figure 1 This is a flowchart illustrating a method for cascading communication between scheduling systems according to an embodiment of the present invention;

[0023] Figure 2This is a cascade architecture diagram of different scheduling systems according to an embodiment of the present invention;

[0024] Figure 3 This is a schematic diagram illustrating the one-to-one call cascading between different scheduling systems according to an embodiment of the present invention;

[0025] Figure 4 This is a schematic diagram illustrating the cascading of audio and video conferencing between different scheduling systems according to an embodiment of the present invention;

[0026] Figure 5 This is a schematic diagram of intercom cascading between different scheduling systems according to an embodiment of the present invention;

[0027] Figure 6 This is a schematic diagram of the structure of a storage medium for cascading communication between scheduling systems according to an embodiment of the present invention.

[0028] Label Explanation:

[0029] 1. A storage medium for cascading communication between scheduling systems; 2. A memory; 3. A processor. Detailed Implementation

[0030] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0031] Please refer to Figures 1 to 5 A method for cascading communication between scheduling systems, comprising the following steps:

[0032] S1. Treat all servers and clients in the scheduling system as a whole as a system node, and assign it a unique node ID and master IP address. At the same time, assign a different user ID and slave IP address to each client under each scheduling system.

[0033] S2. Servers under the same scheduling system share a unique node ID and master IP address, and are cascaded with servers under different scheduling systems through the node ID and master IP address;

[0034] S3. Each scheduling system maintains a node routing table and a connected node table;

[0035] The node routing table records the node ID of the current system and its corresponding master IP address, as well as the node ID of the connected system and its corresponding master IP address.

[0036] The connected node table records the node IDs of the connected systems and their corresponding master IP addresses, the user IDs of each client in the current system and their corresponding slave IP addresses, and the user IDs of each client in the connected systems and their respective master IP addresses.

[0037] S4. Establish cascaded communication between different scheduling systems through the node routing table and the connected node table, including instant message cascaded communication, registration cascaded communication, and audio / video cascaded communication.

[0038] As described above, the beneficial effects of this invention are as follows: by treating each scheduling system as a node and assigning a unique node ID and master IP address to each node, the servers of each scheduling system can be directly cascaded through the node ID and master IP address. At the same time, each scheduling system maintains its own node routing table and connected node table. Through the routing and forwarding mechanism between servers, seamless cascading communication between clients across systems is achieved, realizing hierarchical scheduling. Meanwhile, clients under the same scheduling system are not limited by the cascading between systems. Even if the cascading between systems is broken, the client ID and its slave IP address recorded in the connected node table can still be transparently transmitted by the local server under the current scheduling system. That is, communication between users within the same scheduling system does not need to go through the superior scheduling system, effectively saving wired bandwidth resources.

[0039] Furthermore, the server includes an application server, a media server, and a media distribution server;

[0040] The application server is used to process instant messages, and the media server and the media distribution server are used to process the registration and audio / video data of the scheduling system and clients.

[0041] As described above, each scheduling system's server consists of an application server, a media server, and a media distribution server. The servers in different scheduling systems are cascaded to achieve cascaded communication with a clear division of labor.

[0042] Furthermore, the instant message cascading communication in step S4 specifically includes:

[0043] S4a.1 Add a list of node IDs and path IDs of the scheduling system where the native client of all instant messages is located;

[0044] S4a.2. For the native real-time messages of each client under the current scheduling system, the application server under the current scheduling system distributes them to other corresponding local clients according to the user ID of the local client and its corresponding slave IP address in the local connected node table.

[0045] Simultaneously, the application server forwards instant messages to other connected scheduling systems based on the user IDs of each client in the connected system and the main IP address of their respective systems in the local connected node table, and adds the node IDs of the other forwarded scheduling systems to the path ID list.

[0046] S41a.3 For instant messages forwarded from other scheduling systems, the application server under the current system distributes them to each local client according to the user ID of the local client and its corresponding slave IP address in the local connected node table;

[0047] S4a.4 When the application server of each scheduling system forwards an instant message to other connected scheduling systems, it removes the scheduling system corresponding to the node ID recorded in the path ID list.

[0048] Furthermore, the instant messaging includes client status and push messages.

[0049] As described above, instant messaging is achieved based on the node IDs and their primary IP addresses recorded in the connected node table, and the user IDs and their secondary IP addresses of the clients. This enables intra-system communication between clients in the current scheduling system and cross-system communication between clients in different scheduling systems. In each scheduling system's connected node table, the secondary IP addresses of clients in other cascaded systems are not recorded; instead, the primary IP address of the client's system is recorded. Instant messaging communication between clients across systems is achieved through cascading between application servers. After an instant message is forwarded from one scheduling system to another, it is then distributed to the specific client, achieving hierarchical scheduling. Simultaneously, when the scheduling system distributes or broadcasts instant messages, it excludes the scheduling system corresponding to the path node ID, effectively preventing message loops.

[0050] Furthermore, the registration of cascaded communication in step S4 specifically includes:

[0051] S4b.1 When the current scheduling system publishes node registration information, the current media server shall actively send the node registration information to other connected scheduling systems at a preset time according to the node ID of the connected system and its corresponding main IP address in the local node routing table.

[0052] S4b.2 When a client in the current scheduling system publishes user registration information, the current media server adds the node ID of the current system, its corresponding main IP address, and the port information of the current media server to the user registration information, and then broadcasts it to other connected scheduling systems according to the node routing table.

[0053] S4b.3 When other scheduling systems forward the user registration information, the media server under its own system adds the current system's node ID, its corresponding main IP address, and the port information of the current media server to the user registration information, and then broadcasts it to other connected scheduling systems according to the node routing table.

[0054] As described above, the node registration information of the scheduling system and the user registration information of the client are both broadcast across systems and distributed within the same system using the media server. This eliminates the need to authenticate the node registration information and user registration information forwarded by other scheduling systems, allowing them to be directly registered to the media server of the current scheduling system, thereby improving the speed of cascading communication between scheduling systems.

[0055] Furthermore, the registration cascaded communication in step S4 also includes:

[0056] S4b.4 Write all the node registration information and the user registration information into the node routing table.

[0057] As described above, writing node registration information and user registration information into the node routing table facilitates subsequent routing processing.

[0058] Furthermore, the audio and video cascaded communication in step S4 includes one-to-one calls, audio and video conferencing, and intercom cascades.

[0059] Furthermore, the one-to-one call specifically refers to:

[0060] S4c.1 When two clients in the current scheduling system conduct a one-to-one call, the media distribution server in the current system transmits the call data to each other based on the user IDs of the two clients and their corresponding slave IP addresses recorded in the connected node table.

[0061] When two clients under different scheduling systems conduct a one-to-one call, the media server under the scheduling system where the two clients are located first transmits the call data to the media server of the other scheduling system according to the user ID of the other client and the main IP address of the system where the client is located, based on the user ID of the other client recorded in its connected node table and the main IP address of the system where the client is located. Then, the media distribution server under the other scheduling system transmits the call data to the specified client according to the user ID of the specified client and the corresponding slave IP address recorded in its connected node table.

[0062] The audio and video conferencing specifically refers to:

[0063] S4c.2 When conducting audio and video conferences between the current scheduling systems, if the clients of the conference members are located under the current scheduling system, the media distribution server under the current scheduling system will transmit the conference data transparently.

[0064] If the client of a meeting member is located under another scheduling system, the meeting data will be transmitted between the media server under the current scheduling system and the media server under the destination scheduling system.

[0065] The intercom cascading is specifically as follows:

[0066] S4c.3 When the current dispatch system performs intercom cascading, if the dispatch system where the intercom group is located is the current dispatch system, then the media distribution server under the current dispatch system will transmit the intercom data transparently.

[0067] If the intercom group is located in another scheduling system, the intercom data will be transmitted between the media server in the current scheduling system and the media server in the destination scheduling system.

[0068] As described above, the hierarchical scheduling of one-to-one calls, audio and video conferencing, and intercom cascading between the scheduling system and its clients, achieved by the cooperation of media server and media distribution server, enables data pass-through, improves communication quality, and effectively avoids problems such as stuttering and delay in audio and video data transmission.

[0069] Furthermore, the connected node table also records the connection time and connection mode of the connected systems;

[0070] The connection modes include active initiation and passive acceptance.

[0071] As described above, since a scheduling system is considered a node, it means that each server or client under the scheduling system can share the same node ID and its main IP address. That is, each node can act as both a server node and a client node. When acting as a client node, it can actively send requests to establish server connections between systems. When acting as a server node, it can only passively accept node connections requested by clients. Therefore, writing the connection mode into the connected node table facilitates unified management of the cascading modes between connected scheduling systems.

[0072] Please refer to Figure 6 A storage medium for cascading communication between scheduling systems includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the aforementioned method for cascading communication between scheduling systems.

[0073] As can be seen from the above description, the beneficial effects of the present invention are as follows: Based on the same technical concept, and in conjunction with the above-mentioned method for cascading communication between scheduling systems, a storage medium for cascading communication between scheduling systems is provided. By treating each scheduling system as a node and assigning a unique node ID and master IP address to each node, the servers of each scheduling system can be directly cascaded through the node ID and master IP address. At the same time, each scheduling system maintains its own node routing table and connected node table. Through the routing and forwarding mechanism between servers, seamless cascading communication between clients across systems is achieved, realizing hierarchical scheduling. Meanwhile, clients under the same scheduling system are not limited by the cascading between systems. Even if the cascading between systems is broken, the client ID and its slave IP address recorded in the connected node table can still be transparently transmitted by the local server under the current scheduling system. That is, communication between users within the same scheduling system does not need to go through the superior scheduling system, effectively saving wired bandwidth resources.

[0074] This invention provides a method and storage medium for cascading communication between scheduling systems, applicable to scenarios involving seamless cascading communication between clients of different scheduling systems. The following detailed description is provided in conjunction with specific embodiments.

[0075] Please refer to Figure 1 Embodiment 1 of the present invention is as follows:

[0076] A method for cascading communication between scheduling systems, such as Figure 1 As shown, the steps include:

[0077] S1. Treat all servers and clients in each scheduling system as a whole as a system node, and assign it a unique node ID and master IP address. At the same time, assign a different user ID and slave IP address to each client under each scheduling system.

[0078] S2. Servers under the same scheduling system share a unique node ID and master IP address, and are cascaded with servers under different scheduling systems through the node ID and master IP address.

[0079] S3. Each scheduling system maintains a node routing table and a connected node table.

[0080] The node routing table records the node ID of the current system and its corresponding master IP address, and the node ID of the connected system and its corresponding master IP address; the connected node table records the node ID of the connected system and its corresponding master IP address, the user ID of each client under the current system and its corresponding slave IP address, and the user ID of each client under the connected system and its system's master IP address.

[0081] S4. Establish cascaded communication between different scheduling systems through node routing tables and connected node tables, including instant message cascaded communication, registration cascaded communication, and audio / video cascaded communication.

[0082] In this embodiment, each scheduling system is treated as a node, and each node is assigned a unique node ID and master IP address. Thus, the servers of each scheduling system can be directly cascaded through their node IDs and master IP addresses. Simultaneously, each scheduling system maintains its own node routing table and connected node table. Through the routing and forwarding mechanism between servers, seamless cascading communication between clients across systems is achieved, enabling hierarchical scheduling. Furthermore, clients within the same scheduling system are not limited by inter-system cascading. Even if the inter-system cascading is broken, communication can still be relayed through the local client within the current scheduling system based on the client ID and slave IP address recorded in the connected node table. In other words, communication between users within the same scheduling system does not need to go through a higher-level scheduling system, effectively saving wired bandwidth resources.

[0083] The connected node table also records the connection time and connection mode of the connected systems. The connection mode includes active initiation and passive acceptance. In this embodiment, since a scheduling system is considered a node, it means that each server or client under the scheduling system can share the same node ID and its main IP address. That is, each node can act as both a server node and a client node. When acting as a client node, it can actively send requests to establish server connections between systems. When acting as a server node, it can only passively accept node connections requested by clients. Therefore, writing the connection mode into the connected node table facilitates unified management of the cascading modes between connected scheduling systems.

[0084] Please refer to Figures 2 to 5 Embodiment two of the present invention is as follows:

[0085] A method for cascading communication between scheduling systems, based on the above embodiment one, as follows: Figure 2 As shown, taking the cascading of two dispatch systems, the command center and the command vehicle, as an example, the command center is one node and the command vehicle is another node. The node number of the command center node is S0001, which can be used as the node ID of the command center node. The primary IP address assigned to the command center node is 192.168.1.253. Similarly, the node ID of the command vehicle node is S0002, and the primary IP address is 192.168.2.253.

[0086] Meanwhile, both the command center and the command vehicle dispatch systems include... Figure 2The diagram shows two clients, an Android client and a PC client (but not limited to two clients); under the command center node, the Android client's user ID is 100000 and the IP address is 192.168.1.2, and the PC client's user ID is 100001 and the IP address is 192.168.1.3; under the command vehicle node, the Android client's user ID is 100002 and the IP address is 192.168.2.2, and the PC client's user ID is 100003 and the IP address is 192.168.2.3.

[0087] Simultaneously, both the command center node and the command vehicle node maintain a connected node table and a node routing table, respectively. For simplicity, as follows: Figure 2 As shown, in this embodiment, the connected node table (the correspondence between numbers and IP addresses after registration and cascading) and the node routing table are integrated into one table. The connected node table and node routing table in the command center node display the node ID of its own command center and its corresponding primary IP address (S0001→192.168.1.253), the node ID of the command vehicle and its corresponding primary IP address (S0002→192.168.2.253), the user IDs of each client under its own command center and their corresponding secondary IP addresses (100000→192.168.1.2, 100001→192.168.1.3), and the user IDs of each client under the command vehicle and the primary IP address of the command vehicle node they belong to (100002→192.168.2.253, 100000→192.168.2.253, 100000→192.168.2.253, 100000→192.168.1.2, 100001→192.168.1.3). 0003→192.168.2.253); Similarly, the connected node table and node routing table of the command vehicle show the node ID of its own command vehicle center and its corresponding primary IP address (S0002→192.168.2.253), the user IDs of each client under its own command vehicle and their corresponding secondary IP addresses (100002→192.168.2.2, 100003→192.168.2.3), and the user IDs of each client under the command center and the primary IP address of the command center node where they are located (100002→192.168.1.253, 100003→192.168.1.253).

[0088] Therefore, the connected node table and node routing table in each scheduling system do not need to record the slave IP addresses of each client under other scheduling systems of the connected nodes. They only need to record the user ID of each client under other scheduling systems and the master IP address of the scheduling system they belong to. That is, cross-system cascading communication between clients is implemented by the server under each scheduling system through routing scheduling.

[0089] For example Figure 2As shown, the server includes an application server, a media server, and a media distribution server. In this embodiment, instant messaging includes client status, various push messages, and messages generated by the client in real time. The application server processes instant messages sent by the client, while the media server and media distribution server process the registration information and audio / video data of the scheduling system and its clients. That is, each scheduling system's server consists of an application server, a media server, and a media distribution server. The servers under different scheduling systems are cascaded, achieving clearly defined cascaded communication and routing scheduling.

[0090] In this embodiment, the instant message cascading communication in step S4 specifically refers to:

[0091] S4a.1 Add a list of node IDs and path IDs of the scheduling system where the native client of all instant messages resides.

[0092] S4a.2. For the native instant messages of each client under the current scheduling system, the application server under the current scheduling system distributes them to other local clients according to the user ID of the local client and its corresponding slave IP address in the local connected node table. In this embodiment, the application server can use the WebSocket communication protocol to distribute instant messages to different clients in the same system.

[0093] Simultaneously, the application server forwards instant messages to other connected scheduling systems based on the user IDs of each client in the connected system and the main IP address of their respective systems in the local connected node table, and adds the node IDs of the other scheduling systems that have been forwarded to the path ID list.

[0094] S41a.3 For instant messages forwarded from other scheduling systems, the application server in the current system distributes them to local clients based on the user ID of the local client and its corresponding slave IP address in the local connected node table. Similarly, the application server also uses the WebSocket communication protocol to distribute instant messages forwarded from other scheduling systems between different clients in the same system.

[0095] S4a.4 When the application server of each scheduling system forwards real-time messages to other connected scheduling systems, it removes the scheduling system corresponding to the node ID recorded in the path ID list.

[0096] In this embodiment, instant messaging is achieved based on the node IDs and their primary IP addresses recorded in the connected node table, and the user IDs and their secondary IP addresses of the clients. This enables intra-system communication between clients in the current scheduling system and cross-system communication between clients in different scheduling systems. In the connected node table of each scheduling system, the secondary IP addresses of clients in other cascaded systems are not recorded; instead, the primary IP address of the system to which the client resides is recorded. Instant messaging communication between clients in different systems is achieved through cascading between application servers. After an instant message is forwarded from one scheduling system to another, it is then distributed to the client, achieving hierarchical scheduling. At the same time, when the scheduling system distributes or broadcasts instant messages, it excludes the scheduling system corresponding to the path node ID, effectively avoiding message loops.

[0097] In addition, for example Figure 2 As shown, in this embodiment, a database is also added to the command center and command vehicle to store instant messages. That is, when the application server distributes instant messages from the client, it can also write the instant messages to the database synchronously, and then read them directly from the database when needed.

[0098] Please refer to Figure 2 Embodiment 3 of the present invention is as follows:

[0099] A method for cascading communication between scheduling systems, based on the above embodiment one or embodiment two, in this embodiment, as follows: Figure 2 As shown, the registration of cascaded communication in step S4 is specifically as follows:

[0100] S4b.1 When the current scheduling system publishes node registration information, the current media server actively sends the node registration information to other connected scheduling systems at a preset time according to the node ID of the connected system and its corresponding main IP address in the local node routing table. In this embodiment, the preset time can be set to 30s.

[0101] S4b.2 When a client under the current scheduling system publishes user registration information, the current media server adds the node ID of the current system, its corresponding main IP address, and the port information of the current media server to the user registration information, and then broadcasts it to other connected scheduling systems according to the node routing table.

[0102] S4b.3 When other scheduling systems forward user registration information, the media server under its own system adds the current system's node ID, its corresponding main IP address, and the current media server's port information to the user registration information, and then broadcasts it to other connected scheduling systems according to the node routing table.

[0103] In this embodiment, both node registration information of the scheduling system and user registration information of the client are broadcast across systems and distributed within the same system using a media server. This eliminates the need to authenticate node registration information and user registration information forwarded by other scheduling systems; they can be directly registered to the media server of the current scheduling system, thereby improving the rate of cascading communication between scheduling systems. The broadcasting of node registration information and user registration information by the media server can be implemented using the SIP / RTP communication protocol.

[0104] The registration cascading communication in step S4 also includes:

[0105] S4b.4 Write all node registration information and user registration information into the node routing table. This simplifies subsequent routing processing.

[0106] Please refer to Figures 3 to 5 Embodiment four of the present invention is as follows:

[0107] A method for cascading communication between scheduling systems, based on any one of the embodiments one to three above, wherein in this embodiment, as follows: Figures 3 to 5 As shown, audio and video cascaded communication includes one-to-one calls, audio and video conferencing, and intercom cascades.

[0108] One-on-one calls specifically refer to:

[0109] S4c.1 When two clients in the current scheduling system conduct a one-to-one call, the media distribution server in the current system transmits the call data to each other based on the user IDs of the two clients and their corresponding slave IP addresses recorded in the connected node table.

[0110] When two clients under different scheduling systems conduct a one-to-one call, the media servers under the scheduling systems of the two clients first pass the call data to the media server of the other scheduling system based on the user ID of the other client and the main IP address of the system where the client is located, as recorded in their own connected node table. Then, the media distribution server under the other scheduling system passes the call data to the specified client based on the user ID of the specified client and the corresponding slave IP address recorded in its own connected node table.

[0111] That is, Figure 3As shown, when an Android client under the command center node wants to call an Android client under the command vehicle node, the media server under the command center node, based on the user ID 100002 of the Android client under the command vehicle, finds the main IP address of the dispatch system where the client with user ID 100002 is located, which is 192.168.2.253, recorded in the connected node table. Then, it finds the corresponding command vehicle node (command vehicle dispatch system). The media server in the command vehicle node finds the Android client with IP address 192.168.2.2 based on user ID 100002, thus establishing a one-to-one call between the two clients, the Android client with user ID 100000 and the Android client with user ID 100002.

[0112] The audio and video conferencing is specifically as follows:

[0113] S4c.2 When conducting audio and video conferences between the current scheduling systems, if the clients of the conference members are located under the current scheduling system, the media distribution server under the current scheduling system will pass through the conference data.

[0114] If the clients of the meeting members are located under other scheduling systems, the meeting data will be transmitted between the media server under the current scheduling system and the media server under the destination scheduling system.

[0115] That is, Figure 4 As shown, an Android client with user ID 100000 under the command center node initiates an audio and video conference, specifying user IDs 100000 and 100002 as conference members. After the command center application server creates the conference, the command center media server calls conference members 100000 and 100002. Since conference member 100000 is the client that initiated the conference locally at the command center, 100000 can directly join the conference. The media server finds that the dispatch system where the client with user ID 100002 is located is the command vehicle, and its primary IP address is 192.168.2.253. Therefore, the command center media server calls the command vehicle media server. The command vehicle media server then finds that the secondary IP address of the client with user ID 100002 is 192.168.2.2, and calls the Android client with user ID 100002 to join the conference.

[0116] The specific steps of intercom cascading are:

[0117] S4c.3 When the current dispatch system performs intercom cascading, if the dispatch system where the intercom group is located is the current dispatch system, then the media distribution server under the current dispatch system will transmit the intercom data transparently.

[0118] If the intercom group is located in another scheduling system, the intercom data will be transmitted between the media server under the current scheduling system and the media server under the destination scheduling system.

[0119] That is, Figure 5 As shown, the Android client with user ID 111111100000 under the command center node initiates a two-way communication. The command center application server creates a two-way communication group, specifies the user IDs of the group members as 111111100000 and 122222200002, and initiates a group broadcast to the application servers of other cascaded dispatch systems. The command center media server finds that the client with user ID 111111100000 is an Android client located locally at the command center with a secondary IP address of 192.168.1.2, and directly adds this Android client to the intercom group. The command center media server finds that the client with user ID 122222200002 is located in the command vehicle with a primary IP address of 192.168.2.253. The command center media server then calls the command vehicle media server. The command vehicle media server then finds that the secondary IP address of the client with user ID 122222200002 is 192.168.2.2, and can add the corresponding Android client to the intercom group broadcast in the command vehicle application server.

[0120] In this embodiment, one-to-one calls, audio / video conferencing, and intercom cascading between the scheduling system and its clients utilize a hierarchical scheduling system with the cooperation of a media server and a media distribution server to achieve transparent data transmission, improving communication quality and effectively avoiding issues such as stuttering and delays in audio / video data transmission. Furthermore, in this embodiment, one-to-one calls, audio / video conferencing, and intercom cascading all employ the SIP / RTP communication protocol.

[0121] Please refer to Figure 6 Embodiment five of the present invention is as follows:

[0122] Storage medium 1 for cascading communication between scheduling systems, such as Figure 6 As shown, it includes a memory 2, a processor 3, and a computer program stored in the memory 2 and executable on the processor 3. When the processor 3 executes the computer program, it implements the steps of a method for cascading communication between scheduling systems in any of the embodiments 1 to 4 described above.

[0123] In summary, the method and storage medium for cascading communication between scheduling systems provided by this invention have the following beneficial effects:

[0124] 1. Clients in different scheduling systems are unaware of the cascading operation. Once the cascading between servers is successful, client users can achieve cascading communication across systems.

[0125] 2. Communication between client users within the same scheduling system does not need to go through a higher-level scheduling system, which can save limited bandwidth resources;

[0126] 3. It can realize hierarchical scheduling. After the cascading between nodes of different scheduling systems is disconnected, the communication between clients under the current scheduling system will not be affected and normal communication will continue.

[0127] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for cascading communication between scheduling systems, characterized in that, Including the following steps: S1. Treat all servers and clients in each scheduling system as a whole as a system node, and assign it a unique node ID and master IP address. At the same time, assign a different user ID and slave IP address to each client under each scheduling system. The server-side includes application server-side, media server-side, and media distribution server-side; The application server is used to process instant messages, and the media server and the media distribution server are used to process the registration and audio / video data of the scheduling system and clients. S2. Servers under the same scheduling system share a unique node ID and master IP address, and are cascaded with servers under different scheduling systems through the node ID and master IP address; S3. Each scheduling system maintains a node routing table and a connected node table; The node routing table records the node ID of the current system and its corresponding master IP address, as well as the node ID of the connected system and its corresponding master IP address. The connected node table records the node IDs of the connected systems and their corresponding master IP addresses, the user IDs of each client in the current system and their corresponding slave IP addresses, and the user IDs of each client in the connected systems and their respective master IP addresses. S4. Establish cascaded communication between different scheduling systems through the node routing table and the connected node table, including instant message cascaded communication, registration cascaded communication and audio / video cascaded communication. The instant messaging cascading communication specifically refers to: S4a.1 Add a list of node IDs and path IDs of the scheduling system where the native client of all instant messages is located; S4a.

2. For the native real-time messages of each client under the current scheduling system, the application server under the current scheduling system distributes them to other corresponding local clients according to the user ID of the local client and its corresponding slave IP address in the local connected node table. Simultaneously, the application server forwards instant messages to other connected scheduling systems based on the user IDs of each client in the connected system and the main IP address of their respective systems in the local connected node table, and adds the node IDs of the other forwarded scheduling systems to the path ID list. S4a.3 For instant messages forwarded from other scheduling systems, the application server under the current system distributes them to each local client according to the user ID of the local client and its corresponding slave IP address in the local connected node table; S4a.4 When the application server of each scheduling system forwards an instant message to other connected scheduling systems, it removes the scheduling system corresponding to the node ID recorded in the path ID list.

2. The method for cascading communication between scheduling systems according to claim 1, characterized in that, The instant messaging includes client status and push messages.

3. The method for cascading communication between scheduling systems according to claim 1, characterized in that, The registration of cascaded communication in step S4 specifically involves: S4b.1 When the current scheduling system publishes node registration information, the current media server shall actively send the node registration information to other connected scheduling systems at a preset time according to the node ID of the connected system and its corresponding main IP address in the local node routing table. S4b.2 When a client in the current scheduling system publishes user registration information, the current media server adds the node ID of the current system, its corresponding main IP address, and the port information of the current media server to the user registration information, and then broadcasts it to other connected scheduling systems according to the node routing table. S4b.3 When other scheduling systems forward the user registration information, the media server under its own system adds the current system's node ID, its corresponding main IP address, and the port information of the current media server to the user registration information, and then broadcasts it to other connected scheduling systems according to the node routing table.

4. The method for cascading communication between scheduling systems according to claim 3, characterized in that, The registration cascading communication in step S4 also includes: S4b.4 Write all the node registration information and the user registration information into the node routing table.

5. The method for cascading communication between scheduling systems according to claim 1, characterized in that, The audio and video cascaded communication in step S4 includes one-to-one calls, audio and video conferencing, and intercom cascades.

6. The method for cascading communication between scheduling systems according to claim 5, characterized in that, The one-on-one call specifically refers to: S4c.1 When two clients in the current scheduling system conduct a one-to-one call, the media distribution server in the current system transmits the call data to each other based on the user IDs of the two clients and their corresponding slave IP addresses recorded in the connected node table. When two clients under different scheduling systems conduct a one-to-one call, the media server under the scheduling system where the two clients are located first transmits the call data to the media server of the other scheduling system according to the user ID of the other client and the main IP address of the system where the client is located, based on the user ID of the other client recorded in its connected node table and the main IP address of the system where the client is located. Then, the media distribution server under the other scheduling system transmits the call data to the specified client according to the user ID of the specified client and the corresponding slave IP address recorded in its connected node table. The audio and video conferencing specifically refers to: S4c.2 When conducting audio and video conferences between the current scheduling systems, if the clients of the conference members are located under the current scheduling system, the media distribution server under the current scheduling system will transmit the conference data transparently. If the client of a meeting member is located under another scheduling system, the meeting data will be transmitted between the media server under the current scheduling system and the media server under the destination scheduling system. The intercom cascading is specifically as follows: S4c.3 When the current dispatch system performs intercom cascading, if the dispatch system where the intercom group is located is the current dispatch system, then the media distribution server under the current dispatch system will transmit the intercom data transparently. If the intercom group is located in another scheduling system, the intercom data will be transmitted between the media server in the current scheduling system and the media server in the destination scheduling system.

7. The method for cascading communication between scheduling systems according to claim 1, characterized in that, The connected node table also records the connection time and connection mode of the connected systems; The connection modes include active initiation and passive acceptance.

8. A storage medium for cascading communication between scheduling systems, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method for cascading communication between scheduling systems as described in any one of claims 1-7.

Images