A cross-server group call scheduling method, system, device, and storage medium

Abstract

In this embodiment of the invention, when the scheduling server receives a server group call request initiated by a user, if the request is valid, it replies to the scheduling terminal agreeing to the cross-server group call request and checks whether the scheduling terminal has a corresponding configuration file. If not, it sends the configuration file corresponding to the target server to the scheduling terminal. Upon receiving the configuration file, the scheduling terminal sends a first logout request to the current server and logs out from the current server; if the configuration file exists, it logs out from the current server. Then, the scheduling terminal sends a first login request to the target server according to the corresponding server configuration file. A connection channel is established between the scheduling terminal and the target server using the corresponding configuration file, allowing the scheduling terminal to join at least one preset group for group call scheduling communication. Thus, when cross-server group call scheduling is required, it is not necessary to modify the existing independently deployed cluster system; only the scheduling terminal needs to be modified to achieve cross-server group call scheduling.

Description

Technical Field

[0001] This invention relates to the field of group call scheduling technology, specifically to a cross-server group call scheduling method, system, device, and storage medium. Background Technology

[0002] A cluster dispatch system refers to a dedicated dispatch system where multiple departments and users share communication channels. It is suitable for large-scale collaborative dispatch and command across multiple fields, regions, and departments, including production dispatch, emergency communication, and military command. The core of a cluster dispatch system is the dispatch machine, and the dispatch software running on the dispatch machine enables collaborative dispatching of various terminals.

[0003] In practical use, most cluster scheduling systems are deployed as a single node, with one server deployed in a closed area or unit to achieve scheduling and command of various terminals within that unit or area.

[0004] Current cluster scheduling systems are mainly deployed independently, with no connection between them. Scheduling terminals can only register on their respective servers and implement scheduling group call services. When cross-regional and cross-departmental command and dispatch are required, there are two solutions: (1) abandon the existing independent deployment system and rebuild a distributed, full-coverage cluster scheduling system, with scheduling terminals roaming between servers to realize cross-server cluster scheduling services; (2) add a comprehensive management system on top of the existing system to interconnect the existing independent deployment systems, and use the comprehensive management system to connect the servers, thereby realizing cross-server cluster scheduling services. Regardless of the solution, it is necessary to modify the existing server system and add new hardware and software facilities, which is costly. Summary of the Invention

[0005] To address this issue, embodiments of the present invention provide a cross-server group call scheduling method, system, device, and storage medium to solve the technical problem in the prior art that existing independently deployed cluster systems must be modified when cross-server group call scheduling is required.

[0006] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0007] According to a first aspect of the present invention, a cross-server group call scheduling method is provided, characterized in that the method is applied to a scheduling server and includes:

[0008] Receive a server switching request from the scheduling terminal and determine whether the server switching request is a legitimate request;

[0009] If the server switching request is a valid request, a message allowing cross-server group calls is sent back to the scheduling terminal, and the terminal sends a first logout request to the current server to log out from the current server;

[0010] Receive the user's first login account information and the user's first login password information;

[0011] Determine whether the scheduling terminal has a corresponding preset configuration file for the target server;

[0012] If the scheduling terminal has the corresponding preset configuration file, then determine whether the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file;

[0013] If the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file, then a first login request is sent to the target server according to the corresponding server configuration file.

[0014] Establish a connection channel between the scheduling terminal and the target server, enabling the scheduling terminal to establish a connection with at least one preset group for group call scheduling communication.

[0015] The scheduling terminal supports cluster scheduling group call services, and both the current server and the target server are independently deployed servers.

[0016] Furthermore, if the scheduling terminal does not have a corresponding preset configuration file, then it is determined whether the scheduling terminal has a server directory, including:

[0017] If the scheduling terminal does not have a server directory, then a server directory is constructed using at least one preset server information.

[0018] Build a configuration file subdirectory based on the server directory;

[0019] A corresponding configuration file is generated using the corresponding first server information and first user information;

[0020] The first server information includes a preset first server name, a first server address, and a first server login password, and the first user information includes a first preset user account and a first preset user password.

[0021] The configuration file is stored in the non-volatile memory of the scheduling terminal.

[0022] Preferably, a cross-server group call scheduling method further includes:

[0023] The scheduling server receives a request to delete the target server information and sends it to the scheduling terminal;

[0024] Retrieve the server information to be deleted and the user information to be deleted corresponding to the target server name from the subdirectory of the configuration file;

[0025] Delete the corresponding server information and user information to be deleted for the target server.

[0026] Preferably, a cross-server group call scheduling method further includes:

[0027] The scheduling server receives a request to modify the target server information and sends it to the scheduling terminal;

[0028] Obtain the second server information and second user information corresponding to the target server from the configuration file subdirectory;

[0029] Delete the second server information and the second user information;

[0030] Add the preset third server information and third user information to the configuration file subdirectory of the target server name.

[0031] Furthermore, the list of preset groups is a tree structure, with the first level being the server name and the second level being the list of intercom groups to which the current account belongs on the corresponding server.

[0032] According to a second aspect of the present invention, a cross-server group call scheduling system is provided, the system comprising:

[0033] The first receiving module is used to receive the server switching request from the scheduling terminal and determine whether the server switching request is a legitimate request.

[0034] The logout module is used to send a first logout request to the current server and log out from the current server if the server switch request is a valid request.

[0035] The second receiving module is used to receive the user's first login account information and the user's first login password information;

[0036] The configuration file judgment module is used to determine whether the scheduling terminal has a corresponding preset configuration file for the target server; if the scheduling terminal has the corresponding preset configuration file, it determines whether the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file.

[0037] The login request sending module is used to send a first login request to the target server according to the corresponding server configuration file if the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file.

[0038] The connection establishment module is used to establish a connection channel between the scheduling terminal and the target server, enabling the scheduling terminal to establish a connection with at least one preset group for group call scheduling communication.

[0039] The scheduling terminal supports cluster scheduling group call services, and both the current server and the target server are independently deployed servers.

[0040] According to a third aspect of the present invention, a cross-server group call scheduling device is provided, the device comprising: a processor and a memory;

[0041] The memory is used to store one or more program instructions;

[0042] The processor is configured to run one or more program instructions to perform the steps of a cross-server group call scheduling method as described in any of the preceding claims.

[0043] According to a fourth aspect of the present invention, a computer-readable storage medium is provided, on which a computer program is stored, wherein when executed by a processor, the computer program implements the steps of a cross-server group call scheduling method as described in any of the preceding claims.

[0044] The embodiments of the present invention have the following advantages:

[0045] In this embodiment of the invention, when the scheduling server receives a server group call request initiated by a user, if the request is valid, it replies to the scheduling terminal with an agreement to cross-server group call. It then determines whether the scheduling terminal has a corresponding preset configuration file for the target server. If not, it sends the corresponding configuration file to the scheduling terminal. Upon receiving the file, the terminal sends a first logout request to the current server to log out. If the scheduling terminal has the corresponding preset configuration file, it sends a first logout request to the current server to log out. Then, the scheduling terminal sends a first login request to the target server based on the corresponding server configuration file. A connection channel is established between the scheduling terminal and the target server using the corresponding configuration file, allowing the scheduling terminal to join at least one preset group for group call scheduling communication. Thus, when cross-server group call scheduling is required, it is not necessary to modify the existing independently deployed cluster system; only the scheduling terminal needs to be modified to achieve cross-server group call scheduling. Attached Figure Description

[0046] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.

[0047] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0048] Figure 1 A schematic diagram of the logical structure of a cross-server group call scheduling system provided in an embodiment of the present invention;

[0049] Figure 2 A flowchart illustrating a cross-server group call scheduling method provided in an embodiment of the present invention;

[0050] Figure 3 This is a flowchart illustrating the deletion of target server information in a cross-server group call scheduling method provided in an embodiment of the present invention.

[0051] Figure 4 This is a flowchart illustrating the process of modifying target server information in a cross-server group call scheduling method provided in an embodiment of the present invention. Detailed Implementation

[0052] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0053] Current cluster scheduling systems are mainly deployed independently, with no connection between them. Scheduling terminals can only register on their respective servers and implement scheduling group call services. When cross-regional and cross-departmental command and dispatch are required, there are two solutions: (1) abandon the existing independent deployment system and rebuild a distributed, full-coverage cluster scheduling system, with scheduling terminals roaming between servers to realize cross-server cluster scheduling services; (2) add a comprehensive management system on top of the existing system to interconnect the existing independent deployment systems, and use the comprehensive management system to connect the servers, thereby realizing cross-server cluster scheduling services. Regardless of the solution, it is necessary to modify the existing server system and add new hardware and software facilities, which is costly.

[0054] To address the aforementioned technical issue of needing to modify existing independently deployed cluster systems when cross-server group call scheduling is required.

[0055] refer to Figure 1 This invention discloses a cross-server group call scheduling system, which includes: a first receiving module 1; a logout module 2; a second receiving module 3; a configuration file judgment module 4; a login request sending module 5; and a connection establishment module 6.

[0056] Corresponding to the cross-server group call scheduling system disclosed above, this invention also discloses a cross-server group call scheduling method. The following details the cross-server group call scheduling method disclosed in this invention, in conjunction with the cross-server group call scheduling system described above.

[0057] refer to Figure 2 After receiving the server switching request from the scheduling terminal, the first receiving module determines whether the server switching request is a legitimate request.

[0058] If the request to switch servers is invalid, no response will be given.

[0059] The target server for the server switch is another independently deployed cluster server.

[0060] If the server switch request is a valid request, the logout module 2 sends a first logout request to the current server and logs out from the current server.

[0061] The second receiving module 3 is used to receive the user's first login account information and the user's first login password information.

[0062] Configuration file judgment module 4 determines whether the scheduling terminal has a corresponding preset configuration file for the target server.

[0063] The preset configuration file contains the corresponding parameters for "server list", "server name", "server address", "server login password", "scheduling user account", and "user password".

[0064] If the scheduling terminal has the corresponding preset configuration file, it determines whether the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file.

[0065] If the target server does not have a corresponding preset configuration file, refer to Figure 2 Then determine whether the scheduling terminal has a server directory.

[0066] If the scheduling terminal does not have a server directory, then a server directory is constructed using at least one preset server information.

[0067] A configuration file subdirectory is constructed based on the server directory.

[0068] The corresponding configuration file is generated using the corresponding first server information and first user information.

[0069] The first server information includes the name of the target server, the address of the target server, and the login password of the target server. The first user information includes the preset user account and corresponding password for login.

[0070] The configuration file is stored in the non-volatile memory of the scheduling terminal.

[0071] If the user's first login account information and first login password information match the user's second login account information and second login password information in the corresponding preset configuration file, then the login request sending module 5 sends a first login request to the target server according to the corresponding server configuration file.

[0072] The connection establishment module 6 establishes a connection channel between the scheduling terminal and the target server, enabling the scheduling terminal to establish a connection with at least one preset group for group call scheduling communication.

[0073] After successfully logging into the target server, the dispatch terminal automatically switches to the group where the target server is located.

[0074] Both the server and the dispatch terminal need to support basic cluster dispatch group call functions. The dispatch terminal needs to support dispatch group configuration, login and registration of the dispatch server, and user account configuration (add, delete, modify) functions.

[0075] When the scheduling terminal needs to delete the target server, refer to Figure 3If the received request to delete the target server information is a request to delete the server, select the "Delete Server" option. The dispatch terminal will read the currently saved server information from the configuration file, display the "Server" list, and confirm.

[0076] Select the server to be deleted and click "Confirm Delete". The dispatch terminal will delete the server's configuration information from the configuration file, including "Server Name", "Server Address", "Server Login Password", etc. At the same time, it will delete all user accounts and passwords belonging to the server and save the modified configuration file again.

[0077] If the received request to delete target server information is a request to delete user accounts, after selecting the "Delete Account" option, the scheduling terminal reads the currently saved server and account information under each server from the configuration file and displays the "Server" list and the "Confirm" button. Select the server where the account to be deleted is located and click the "Confirm" button. The scheduling terminal will pop up the list of scheduling user accounts saved under the server information. Select the corresponding account and click "Confirm Delete" to resave the modified configuration file.

[0078] When the scheduling terminal needs to modify the target server, refer to Figure 4 The scheduling terminal receives a request to modify the target server information; retrieves the second server information and the second user information corresponding to the target server from the configuration file subdirectory; deletes the second server information and the second user information; and adds the preset third server information and third user information to the configuration file subdirectory of the target server name.

[0079] If the received request to modify the target server information is a server modification request, after selecting the "Modify Server" option, the dispatch terminal reads the currently saved server information from the configuration file and displays the "Server" list and a "Confirm" button. The user selects the server to be modified and clicks the "Confirm" button. The dispatch terminal then displays the selected server information, including input boxes for "Server Name", "Server Address", and "Server Login Password" as well as a "Save" button. After the user modifies the corresponding parameters and clicks "Save", the dispatch terminal saves the user's modified configuration in the configuration file.

[0080] If the received request to modify target server information is to modify user account information, after selecting the "Modify Account" option, the scheduling terminal reads the currently saved servers and account information under each server from the configuration file and displays the "Server" list and the "Confirm" button. The user selects the server where the account to be modified is located and clicks the "Confirm" button. The scheduling terminal then pops up the account information saved under that server, including input boxes for "Scheduling User Account" and "User Password" and a "Save" button. After the user modifies the corresponding parameters, they click "Save," and the scheduling terminal saves the user's modified configuration in the configuration file.

[0081] The list of preset groups is in a tree structure, with the first level being the server name and the second level being the list of intercom groups to which the current account belongs on the corresponding server.

[0082] In one scenario, when the dispatch terminal is switching servers, the user is unable to perform any operations. The dispatch terminal will then display a message to the user: "Cross-server group switching is in progress, please wait..."

[0083] In addition, embodiments of the present invention also provide a cross-server group call scheduling device, the device comprising: a processor and a memory; the memory for storing one or more program instructions; the processor for running one or more program instructions to perform the steps of a cross-server group call scheduling method as described in any of the preceding embodiments.

[0084] In addition, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of a cross-server group call scheduling method as described in any of the preceding claims.

[0085] In this embodiment of the invention, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0086] The various methods, steps, and logic diagrams disclosed in the embodiments of this invention can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The processor reads information from the storage medium and, in conjunction with its hardware, completes the steps of the above methods.

[0087] The storage medium can be memory, such as volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.

[0088] Among them, non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory.

[0089] Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM).

[0090] The storage media described in the embodiments of the present invention are intended to include, but are not limited to, these and any other suitable types of memory.

[0091] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this invention can be implemented using a combination of hardware and software. When applied as software, the corresponding functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of computer programs from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0092] Although the present invention has been described in detail above with general descriptions and specific embodiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.

Claims

1. A cross-server group call scheduling method, characterized in that, The method is applied to the current server and includes: Receive a server switching request from the scheduling terminal and determine whether the server switching request is a legitimate request; If the server switching request is a valid request, a message allowing cross-server group calls is sent back to the scheduling terminal, and the terminal sends a first logout request to the current server to log out from the current server; Receive the user's first login account information and the user's first login password information; Determine whether the scheduling terminal has a corresponding preset configuration file for the target server; If the scheduling terminal has the corresponding preset configuration file, then determine whether the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file; If the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file, then the scheduling terminal sends a first login request to the target server according to the corresponding server configuration file. Establish a connection channel between the scheduling terminal and the target server, enabling the scheduling terminal to establish a connection with at least one preset group for group call scheduling communication; The scheduling terminal supports cluster scheduling group call services, and both the current server and the target server are independently deployed servers.

2. The cross-server group call scheduling method as described in claim 1, characterized in that, If the scheduling terminal does not have a corresponding preset configuration file, then determine whether the scheduling terminal has a server directory, including: If the scheduling terminal does not have a server directory, then a server directory is constructed using at least one preset server information. Build a configuration file subdirectory based on the server directory; A corresponding configuration file is generated using the corresponding first server information and first user information; The first server information includes a preset first server name, a first server address, and a first server login password, and the first user information includes a first preset user account and a first preset user password. The configuration file is stored in the non-volatile memory of the scheduling terminal.

3. A cross-server group call scheduling method as described in any one of claims 1 or 2, characterized in that, The method further includes: The scheduling server receives a request to delete the target server information and sends it to the scheduling terminal; Retrieve the server information to be deleted and the user information to be deleted corresponding to the target server name from the subdirectory of the configuration file; Delete the corresponding server information and user information to be deleted for the target server.

4. A cross-server group call scheduling method as described in any one of claims 1 or 2, characterized in that, The method further includes: The scheduling server receives a request to modify the target server information and sends it to the scheduling terminal; Obtain the second server information and second user information corresponding to the target server from the configuration file subdirectory; Delete the second server information and the second user information; Add the preset third server information and third user information to the configuration file subdirectory of the target server name.

5. A cross-server group call scheduling method as described in claim 4, characterized in that, The list of preset groups is in a tree structure. The first level is the server name, and the second level is the list of intercom groups that the current account belongs to on the corresponding server.

6. A cross-server group call scheduling system, characterized in that, The system includes: The first receiving module is used to receive the server switching request from the scheduling terminal and determine whether the server switching request is a legitimate request. The logout module is used to send a first logout request to the current server and log out from the current server; The second receiving module is used to receive the user's first login account information and the user's first login password information; The configuration file judgment module is used to determine whether the scheduling terminal has a corresponding preset configuration file for the target server; if the scheduling terminal has the corresponding preset configuration file, it determines whether the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file. The login request sending module is used to send a first login request to the target server according to the corresponding server configuration file if the user's first login account information and user's first login password information match the user's second login account information and user's second login password information in the corresponding preset configuration file. The connection establishment module is used to establish a connection channel between the scheduling terminal and the target server, enabling the scheduling terminal to establish a connection with at least one preset group to conduct group call scheduling communication. The scheduling terminal supports cluster scheduling group call services, and both the current server and the target server are independently deployed servers.

7. A cross-server group call scheduling device, characterized in that, The device includes: a processor and a memory; The memory is used to store one or more program instructions; The processor is configured to run one or more program instructions to perform the steps of a cross-server group call scheduling method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of a cross-server group call scheduling method as described in any one of claims 1 to 5.

Images