Wireless scheduling method and system compatible with different manufacturer core networks

Abstract

The invention provides a wireless scheduling method and system compatible with different manufacturer core networks. The system comprises a foreground client side and a background SDK service program side. The foreground client side is in communication connection with the background SDK service program side through the communication intermediate layer PRC interface module, and the communication intermediate layer PRC interface module carries out data message transmission in a TCP Socket mode; the business processing logic judgment module is used for judging the corresponding relation between the data message and a plurality of different manufacturer core networks and determining a business interface needing to be called, and the communication intermediate layer PRC interface module transmits the data message according to the determined business interface and the corresponding SDK service module in a format adaptive to an interface function parameter entering rule. According to the invention, the core networks of different manufacturers are compatible, and the problem of service interruption in the switching process is avoided.

Description

Technical Field

[0001] The present invention relates to, specifically, a wireless scheduling method and system compatible with core networks of different manufacturers. Background Art

[0002] LTE (Long Term Evolution) is the long-term evolution of the UMTS (Universal Mobile Telecommunications System) technical standard formulated by the 3GPP (The 3rd Generation Partnership Project).

[0003] The application of the LTE system in private network emergency communication scheduling and command is becoming more and more popular. The interconnection between different core networks of LTE-M, especially the cross-core network interconnection requirement of voice scheduling and command cluster services, is also becoming more and more urgent. However, the LTE system has different developers. For example, the SDK software development kits provided by companies such as Gaoda and TD Tech respectively adopt SDK interfaces developed in C++ at the bottom layer. However, there is an incompatibility in the form of secondary development API interfaces between different core network manufacturers, with different interface functions and different data formats transmitted between SDK modules. At present, the LTE cluster service in rail transit is developing rapidly. For extra-large cities, there is a need to build multiple core network devices of different manufacturers. When a fault occurs, during the process of LTE core network handover, the continuous voice scheduling service often experiences service interruption within this time window. That is to say, this other redundancy method of the core network will inevitably lose part of the service processing ability during the handover process, resulting in the interruption of cluster voice and data services. Patent document CN114157996A discloses an implementation method of a wireless dispatching console based on LTE. Although this patent document can support the continuous operation of the dispatching console for single core network services, it cannot achieve the compatibility of dispatching services between multiple core networks, and cannot ensure that there is no loss of interruption during the service handover of the dispatching console after the disaster recovery handover of core networks of different manufacturers. Summary of the Invention

[0004] Aiming at the defects in the prior art, the purpose of the present invention is to provide a wireless scheduling method and system compatible with core networks of different manufacturers.

[0005] According to a wireless scheduling system compatible with core networks of different manufacturers provided by the present invention, it includes: a foreground client and a background SDK service program end;

[0006] The foreground client includes: a service processing logic judgment module and a communication middleware PRC interface module;

[0007] The background SDK service program end includes multiple SDK service modules of different manufacturers' core networks;

[0008] The foreground client is communicatively connected to the background SDK service program end through the communication middleware PRC interface module, and the communication middleware PRC interface module uses the TCP Socket method for data message transmission;

[0009] Among them, the service processing logic judgment module is used to judge the corresponding relationship between data messages and multiple different manufacturers' core networks, so as to determine the required service interfaces to be called, and the communication middleware PRC interface module performs data message transmission with the corresponding SDK service module according to the parameter passing rules of the adaptation interface function in the format of the determined service interface.

[0010] Further, the SDK service modules include the Gaoda SDK service module and the TD Tech SDK service module, and both the Gaoda SDK service module and the TD Tech SDK service module include corresponding API software toolkits for cluster voice, video, and instant messaging services;

[0011] The data message transmission between the communication middleware PRC interface module and the Gaoda SDK service module uses the JSON format, and the data message transmission between the communication middleware PRC interface module and the TD Tech SDK service module uses the XML format.

[0012] Further, both the Gaoda SDK service module and the TD Tech SDK service module include: login and registration interfaces, resource acquisition interfaces, voice call interfaces, SMS service interfaces, real-time video interfaces, Socket communication processing modules, and audio processing modules;

[0013] The SOCKET communication processing module is used to realize data transceiver between each interface in the Gaoda SDK service module or the TD Tech SDK service module and the communication middleware PRC interface module;

[0014] The communication middleware PRC interface module includes: login and registration modules, resource acquisition modules, voice call modules, SMS service modules, and real-time video modules;

[0015] When the foreground client obtains the login name and password, it calls the login and registration interfaces of the Gaoda SDK service module and the TD Tech SDK service module, and initiates corresponding services by reading the corresponding group, virtual associated group, and terminal user data information.

[0016] Further, the wireless dispatching system compatible with different manufacturers' core networks further includes a dispatching data storage server for storing group, virtual associated group, and terminal user data information related to the SDK service module;

[0017] The front-end client further includes a log management module for recording the call process logs of the communication middleware PRC interface module calling the SDK service module, as well as call exception situations.

[0018] Furthermore, the front-end client, the background SDK service program end, and the dispatching data storage server are interconnected through a three-layer Ethernet switch to implement interconnection of different IP address segments, and the background SDK service program end and the dispatching data storage server are in one network.

[0019] According to a wireless dispatching method compatible with heterogeneous vendor core networks provided by the present invention, the wireless dispatching system compatible with heterogeneous vendor core networks is adopted to implement the registration and login process, voice group call initiation process, short message data processing process, and video dispatching process of heterogeneous vendor core networks.

[0020] Furthermore, the registration and login process includes:

[0021] Step 101: Start the SDK service modules of multiple heterogeneous vendor core networks of the background SDK service program end and allocate TCP Socket port numbers;

[0022] Step 102: Configure the front-end client parameters, the IP addresses of the SDK service modules of multiple heterogeneous vendor core networks, and the sending and listening ports of the communication middleware PRC interface module;

[0023] Step 103: Obtain the login names and passwords of the SDK service modules of the heterogeneous vendor core networks. The communication middleware PRC interface module converts the login names and passwords into JSON format and logs in to the Gaoda SDK service module, and converts the login names and passwords into XML format and logs in to the TD Tech SDK service module;

[0024] Step 104: The communication middleware PRC interface module calls the login interface and passes JSON data parameters to initialize the Gaoda SDK service module and obtain the resource interface to implement login and registration; the communication middleware PRC interface module initializes the eLTE_SDK_Init interface of the TD Tech SDK service module, passes data to the eLTE_SDK_Unified_Login unified login interface, and sets a callback function;

[0025] Step 105: The Gaoda SDK service module and the TD Tech SDK service module respectively pass the corresponding callback functions to the front-end client through the communication middleware PRC interface module;

[0026] Step 106: The front-end client displays whether the login is successful. If it fails, it displays the error codes of the corresponding failed SDK service modules.

[0027] Further, the voice group call initiation process includes:

[0028] Step 201: Determine the group of objects to be called according to the group number selected by the user on the front-end client interface;

[0029] Step 202: The service processing logic judgment module determines the group attribution type according to the group of objects to be called, and initiates a simultaneous or single call to the corresponding SDK service module;

[0030] Trigger the communication middleware PRC interface module to send Socket information to connect to the corresponding SDK service module according to the key press event on the front-end client interface;

[0031] Step 203: The Gigaset SDK service module receives the Socket information, calls the Call interface function to pass in the Socket message, waits for the terminal under the Gigaset core network to receive the group call message, and sets the output speaker channel when the call status becomes speaking; and / or,

[0032] The TD Tech SDK service module receives the Socket information, calls the eLTE_SDK_PTTDail interface to pass in the Socket message, waits for the terminal under the TD Tech core network to receive the group call message, and enumerates the output speaker channel when the call status becomes speaking;

[0033] Step 204: The communication middleware PRC interface module sends the status of the voice service callback function to the front-end client via Socket, and the front-end client obtains the call right and turns on the microphone;

[0034] Step 205: Complete the group call according to the release PTT key event on the front-end client interface;

[0035] Step 206: The communication middleware PRC interface module sends Socket information to the corresponding SDK service module;

[0036] Step 207: The Gigaset SDK service module receives the Socket information and calls the Call release interface; and / or, the TD Tech SDK service module receives the Socket information and calls the eLTE_SDK_PTTrelease interface;

[0037] Step 208: After successfully calling the interface, the communication middleware PRC interface module sends Socket information to the front-end client interface.

[0038] Further, the short message data processing process includes:

[0039] Step 301: Obtain the text content to be sent input by the user on the front-end client interface;

[0040] Step 302: According to the terminal number selected or input by the user, the service processing logic judgment module reads the corresponding complete information in the scheduling data storage server and determines which core network the terminal number belongs to;

[0041] Step 303: Send Socket information to the corresponding SDK service module to be called through the communication middleware PRC interface module;

[0042] Step 304: Wait for the status notification of the callback function, and send Socket information to the foreground client through the communication middleware PRC interface module;

[0043] Step 305: When there is TD Tech core network information in the complete information, call the eLTE-SDK-SDSSendmassage interface function of the TD Tech SDK service module, construct the text content into the parameter XML format through the communication middleware PRC interface module, set the point-to-point message sending mode, and send it to the eLTE-SDK-SDSSendmassage interface, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module;

[0044] When there is GIGA core network information in the complete information, call the String message interface function of the GIGA SDK service module, construct the text content into the parameter JSON format through the communication middleware PRC interface module, send it to the Stringmessage interface, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module.

[0045] Further, the video scheduling process includes:

[0046] Step 401: Obtain the terminal number for video scheduling selected or input by the user on the foreground client interface;

[0047] Step 402: According to the terminal number selected or input by the user, the service processing logic judgment module reads the corresponding complete information in the scheduling data storage server and determines which core network the terminal number belongs to;

[0048] Step 403: Send Socket information to the corresponding SDK service module to be called through the communication middleware PRC interface module;

[0049] Step 404: When there is TD Tech core network information in the complete information, call the eLTE_SDK_startrealplay interface function of the TD Tech SDK service module, set the video playback window using the eLTE_SDK_setplaywindow interface function, wait for the status notification of the callback function, and transmit it back to the foreground client through the PRC interface module of the communication middleware layer;

[0050] When there is GIGABIT core network information in the complete information, call the real-time video interface of the GIGABIT SDK service module, wait for the status notification of the callback function, and transmit it back to the foreground client through the PRC interface module of the communication middleware layer.

[0051] Compared with the prior art, the present invention has the following beneficial effects:

[0052] The present invention can realize the reception and selective call of voice calls for terminal handsets and groups belonging to core networks of different manufacturers on a single dispatching PC terminal through a wireless dispatching console that is compatible with the GIGABIT and TD Tech LTE systems, avoiding service interruption problems during the handover process. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] By reading the following detailed description of the non-restrictive embodiments with reference to the accompanying drawings, other features, objects, and advantages of the present invention will become more apparent:

[0054] Figure 1 It is the architecture diagram of the wireless dispatching system of this application;

[0055] Figure 2 It is the interaction schematic diagram of the PRC interface module of the communication middleware layer and the SDK service module;

[0056] Figure 3 It is the network diagram of the wireless dispatching system in the dual-core network state;

[0057] Figure 4 It is the login and registration flowchart;

[0058] Figure 5 It is the flowchart for initiating a voice group call;

[0059] Figure 6 It is the flowchart for sending SMS data;

[0060] Figure 7 It is the video call flowchart. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0061] The present invention will be described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that those of ordinary skill in the art can make several changes and improvements without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0062] A wireless scheduling system and method compatible with heterogeneous vendor core networks according to the present invention, the system includes: a foreground client and a background SDK service program end. The foreground client includes: a human-computer interaction interface, a service processing logic judgment module, and a communication middleware PRC interface module. The background SDK service program end includes SDK service modules of multiple heterogeneous vendor core networks.

[0063] The foreground client is communicatively connected to the background SDK service program end through the communication middleware PRC interface module, and the communication middleware PRC interface module uses the TCP Socket method to transfer data messages. Among them, the service processing logic judgment module is used to judge the corresponding relationship between the data message and multiple heterogeneous vendor core networks, so as to determine the required service interface to be called. The communication middleware PRC interface module transfers data messages to the corresponding SDK service module according to the determined service interface in the format of the parameter input rule of the adaptation interface function.

[0064] Embodiment 1

[0065] The architecture of the wireless scheduling system compatible with heterogeneous vendor core networks of the present invention is as Figure 1 shown. The background SDK service program end includes the Gaoda SDK service module and the TD Tech SDK service module, which include API software toolkits for cluster voice, video, and instant messaging services provided by the manufacturer. After the program runs, it will automatically obtain the PC host peripheral driver.

[0066] The foreground client includes: a human-computer interaction interface, a service processing logic judgment module, and a communication middleware PRC interface module. The human-computer interaction interface mainly includes a group status display module, a system configuration module, a video screen display module, and a text message editing display module. The human-computer interaction interface updates the group talk right information status in the real-time interface with the SDK service module through the communication middleware service layer RPC interface module, and obtains user and group data through the resource acquisition interface provided by the SDK. The service processing logic judgment module realizes the judgment of the core network to which the group belongs, and correlates the service function interface of the SDK service module with the communication middleware PRC interface module. The foreground client also includes a log management module for recording the call process log of the communication middleware PRC interface module calling the SDK service module, as well as call exception situations.

[0067] The system further includes a scheduling data storage server for storing group, virtual association group, and end-user data information related to the SDK service module.

[0068] As Figure 2 shown, the communication middleware PRC interface module mainly realizes the invocation of the SDK service module of Gaoda and Dingqiao. After encapsulating the SDK software toolkit of different manufacturers' core networks into a background program using the node.js development language, it runs independently. The communication interaction method between the foreground client and the background SDK service program uses the TCP Socket method to transmit. The data message transmission format is mainly determined according to the parameter rules of the interface functions of the core network manufacturers. The data message transmission between the communication middleware PRC interface module and the Gaoda SDK service module uses the JSON format, and the data message transmission between the communication middleware PRC interface module and the Dingqiao SDK service module uses the XML format. By dividing the interfaces of different core network manufacturers into two communication middleware PRC interface modules corresponding to the same business type, the internal logic is realized by the business processing logic judgment module to correspondingly call the core network manufacturer's business interface.

[0069] The communication middleware PRC interface module includes: a login and registration module, a resource acquisition module, a voice call module, a short message service module, and a real-time video module. The business IP addresses of the Gaoda and Dingqiao core network scheduling servers are respectively configured in the foreground client. When the login name and password are input on the human-computer interaction interface, the login and registration module of the Gaoda and Dingqiao SDK services is triggered to call the background SDK service program, and specific corresponding services are initiated by reading the corresponding group and end-user information in the database cache.

[0070] As Figure 3As shown in the figure, it is the networking diagram of the heterogeneous vendor core network architecture of the present invention. The figure includes LTE core network devices of different vendors, LTE base stations and handheld devices, three-layer Ethernet switches, dispatching data storage servers, and dispatching console PC terminals. Among them, the dispatching database server and the dispatching console PC terminal are connected to the three-layer Ethernet switch through a wired network. The PTT desktop microphone is connected to the dispatching PC terminal through a USB interface and a microphone input port to obtain the analog audio of the voice module microphone. The speaker is connected to the sound card interface of the dispatching console PC terminal through an analog audio cable to process the sounds of the Gaoda and Dingqiao voice modules in the local SDK service layer. Among them, the three-layer Ethernet switch is responsible for realizing the interconnection of different IP address segments between the LTE core network and the dispatching database server, putting the dispatching database server and the LTE core network in one network, so that the dispatching console PC terminal can obtain a packet data channel through the core network to enable the LTE terminal to provide voice calls, data, video dispatching and other related services for cluster dispatching users. Both the Gaoda SDK service module and the Dingqiao SDK service module include: login and registration interfaces, resource acquisition interfaces, voice call interfaces, SMS service interfaces, real-time video interfaces, Socket communication processing modules, and audio processing modules. The SOCKET communication processing module is used to realize the data transceiver between each interface in the Gaoda SDK service module or the Dingqiao SDK service module and the communication middleware PRC interface module.

[0071] Embodiment 2

[0072] The present invention also provides a wireless dispatching method compatible with heterogeneous vendor core networks, which adopts the wireless dispatching system compatible with heterogeneous vendor core networks described in Embodiment 1 to implement the registration and login process, voice group call initiation process, SMS data processing process, and video dispatching process of heterogeneous vendor core networks.

[0073] As Figure 4 shown, the registration and login process includes:

[0074] Step 101: Start the SDK service modules of multiple heterogeneous vendor core networks on the background SDK service program side, allocate TCP Socket port numbers, and implement the process communication of SDK interface calls between the background SDK service program side and the foreground client.

[0075] Step 102: Configure the foreground client parameters, the IP addresses of the SDK service modules of multiple heterogeneous vendor core networks, and the sending and listening ports of the communication middleware PRC interface module.

[0076] Step 103: Obtain the login names and passwords of the SDK service modules of heterogeneous vendor core networks. The communication middleware PRC interface module converts the login names and passwords into JSON format and logs into the Gaoda SDK service module, and converts the login names and passwords into XML format and logs into the Dingqiao SDK service module.

[0077] Step 104: Log in to the GigaDevice SDK service module. The PRC interface module of the communication middleware layer calls the login interface and passes JSON data parameters to initialize the GigaDevice SDK service module, and the resource acquisition interface is implemented for login and registration; log in to the TD Tech SDK service module. The PRC interface module of the communication middleware layer initializes the eLTE_SDK_Init interface of the TD Tech SDK service module, transfers data to the eLTE_SDK_Unified_Login unified login interface, and sets a callback function.

[0078] Step 105: The GigaDevice SDK service module and the TD Tech SDK service module respectively pass the corresponding callback functions to the foreground client through the PRC interface module of the communication middleware layer.

[0079] Step 106: The foreground client displays whether the login is successful. If it fails, the error code of the corresponding failed SDK service module is displayed.

[0080] As Figure 5 shown, the voice group call initiation process includes:

[0081] Step 201: Determine the group to be called according to the group number selected by the user on the foreground client interface.

[0082] Step 202: The service processing logic judgment module judges the group belonging type according to the group to be called, and initiates a simultaneous or single call to the corresponding SDK service module. The group belonging types include ordinary groups of the GigaDevice LTE core network, ordinary groups of the TD Tech LTE core network, and virtual associated groups. The virtual associated group is a virtual group generated by mutually associating and mapping the information of the GigaDevice group and the TD Tech group. If the selected group object is a virtual associated group, the simultaneous voice service interface function call is triggered. Otherwise, the call logic of the corresponding SDK service is triggered according to the selected group type. The method for judging the group belonging type includes: presetting a numerical mapping relationship of the group number in the database. For example, the numerical value 01 represents the GigaDevice core network, 02 represents the TD Tech core network, and 03 represents the virtual associated group. The foreground software reads the enumerated numerical value in the database and passes it to the service processing logic judgment module to judge which SDK service module logic to call.

[0083] Trigger the PRC interface module of the communication middleware layer to send Socket information to connect to the corresponding SDK service module according to the key press event on the foreground client interface.

[0084] Step 203: The Gaoda SDK service module receives the Socket information, calls the Call interface function, passes the JSON data of the Socket message into the Call interface, and waits for the terminal under the Gaoda core network to receive the group call message. When the call status changes to speaking, set the output speaker channel; and / or, the TD Tech SDK service module receives the Socket information, calls the eLTE_SDK_PTTDail interface function, passes the XML data of the Socket message into the eLTE_SDK_PTTDail interface, and waits for the terminal under the TD Tech core network to receive the group call message. When the call status changes to speaking, enumerate the output speaker channels.

[0085] Step 204: The communication middleware PRC interface module sends the status of the voice service callback function to the foreground client via Socket, and the foreground client acquires the call right and turns on the microphone.

[0086] Step 205: After the dispatcher voice group call is completed, complete the group call according to the release PTT button event on the foreground client interface.

[0087] Step 206: The communication middleware PRC interface module sends Socket information to the corresponding SDK service module.

[0088] Step 207: The Gaoda SDK service module receives the Socket information and calls the Call release interface; and / or, the TD Tech SDK service module receives the Socket information and calls the eLTE_SDK_PTTrelease interface.

[0089] Step 208: After successfully calling the interface, the communication middleware PRC interface module sends Socket information to the human-computer interaction interface of the foreground client.

[0090] Step 209: The foreground client updates the human-computer interaction interface according to the status information returned by the communication middleware PRC interface module.

[0091] As Figure 6 shown, the SMS data processing flow includes:

[0092] Step 301: Obtain the text content to be sent entered by the user on the foreground client interface.

[0093] Step 302: According to the terminal number selected or input by the user, the service processing logic judgment module reads the corresponding complete information in the scheduling data storage server and determines which core network the terminal number belongs to. The methods for determining which core network the terminal number belongs to include: by presetting a numerical mapping relationship of the terminal number in the database. The foreground software reads the enumerated values in the database and passes them to the service processing logic judgment module to determine which SDK service module logic to call.

[0094] Step 303: Send Socket information to the corresponding SDK service module to be called through the communication middleware PRC interface module.

[0095] Step 304: Wait for the status notification of the callback function, and send Socket information to the foreground client through the communication middleware PRC interface module.

[0096] Step 305: When there is TD Tech core network information in the complete information, call the eLTE-SDK-SDSSendmassage interface function of the TD Tech SDK service module, construct the text content into the parameter XML format through the communication middleware PRC interface module, set the point-to-point message sending mode, and send it to the eLTE-SDK-SDSSendmassage interface, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module;

[0097] When there is GIGABYTE core network information in the complete information, call the String message interface function of the GIGABYTE SDK service module, construct the text content into the parameter JSON format through the communication middleware PRC interface module, send it to the Stringmessage interface, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module.

[0098] As Figure 7 shown, the video scheduling process includes:

[0099] Step 401: Obtain the terminal number selected or input by the user on the foreground client interface for video scheduling.

[0100] Step 402: According to the terminal number selected or input by the user, the service processing logic judgment module reads the corresponding complete information in the scheduling data storage server and determines which core network the terminal number belongs to.

[0101] Step 403: Send Socket information to the corresponding SDK service module to be called through the communication middleware PRC interface module.

[0102] Step 404: When there is TD Tech core network information in the complete information, call the eLTE_SDK_startrealplay interface function of the TD Tech SDK service module, set the video playback window using the eLTE_SDK_setplaywindow interface function, wait for the status notification of the callback function, and transmit it back to the foreground client through the PRC interface module of the communication middleware layer.

[0103] When there is CoreEngine core network information in the complete information, call the real-time video interface of the CoreEngine SDK service module, wait for the status notification of the callback function, and transmit it back to the foreground client through the PRC interface module of the communication middleware layer.

[0104] Step 405: The foreground client displays the real-time video image.

[0105] Those skilled in the art know that in addition to implementing the system and its various devices, modules, and units provided by the present invention in the form of pure computer-readable program code, the method steps can be logically programmed to enable the system and its various devices, modules, and units provided by the present invention to be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers, etc., to achieve the same functions. Therefore, the system and its various devices, modules, and units provided by the present invention can be regarded as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be regarded as the structure within the hardware component; the devices, modules, and units for implementing various functions can also be regarded as either software modules for implementing the method or the structure within the hardware component.

[0106] The specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. Without conflict, the embodiments of the present application and the features in the embodiments can be combined arbitrarily with each other.

Claims

1. A wireless scheduling system compatible with core networks of different manufacturers, characterized in that It includes: A front-end client and a back-end SDK service program end; The front-end client includes: a service processing logic judgment module and a communication middleware PRC interface module; The back-end SDK service program end includes multiple SDK service modules of different manufacturers' core networks; The front-end client is communicatively connected to the back-end SDK service program end through the communication middleware PRC interface module, and the communication middleware PRC interface module uses the TCP Socket method for data message transmission; Among them, the service processing logic judgment module is used to judge the correspondence between data messages and multiple different manufacturers' core networks, so as to determine the required service interfaces to be called, and the communication middleware PRC interface module performs data message transmission with the corresponding SDK service module according to the format of the parameter input rules of the adaptation interface function.

2. The radio scheduling system compatible with core networks of different manufacturers according to claim 1, wherein The SDK service modules include a Gaoda SDK service module and a TD Tech SDK service module, and both the Gaoda SDK service module and the TD Tech SDK service module include corresponding: API software toolkits for cluster voice, video, and instant messaging services; The data message transmission between the communication middleware PRC interface module and the Gaoda SDK service module uses the JSON format, and the data message transmission between the communication middleware PRC interface module and the TD Tech SDK service module uses the XML format.

3. The radio scheduling system compatible with core networks of different manufacturers according to claim 2, wherein Both the Gaoda SDK service module and the TD Tech SDK service module include: a login and registration interface, a resource acquisition interface, a voice call interface, a short message service interface, a real-time video interface, a Socket communication processing module, and an audio processing module; The SOCKET communication processing module is used to realize the data sending and receiving between each interface in the Gaoda SDK service module or the TD Tech SDK service module and the communication middleware PRC interface module; The communication middleware PRC interface module includes: a login and registration module, a resource acquisition module, a voice call module, a short message service module, and a real-time video module; When the front-end client obtains the login name and password, it calls the login and registration interfaces of the Gaoda SDK service module and the TD Tech SDK service module, and initiates corresponding services by reading the corresponding group, virtual associated group, and terminal user data information.

4. The wireless scheduling system compatible with heterogeneous core networks according to claim 1, characterized in that The wireless dispatching system compatible with different manufacturers' core networks further includes a dispatching data storage server for storing the group, virtual associated group, and terminal user data information related to the SDK service module; The front-end client further includes a log management module for recording the call process log of the communication middleware PRC interface module calling the SDK service module and the call exception situation.

5. The wireless scheduling system compatible with core networks of different manufacturers according to claim 4, wherein The front-end client, the back-end SDK service program end, and the dispatching data storage server are interconnected through a three-layer Ethernet switch to realize different IP address network segments, and the back-end SDK service program end and the dispatching data storage server are in one network.

6. A wireless scheduling method compatible with core networks of different manufacturers, characterized in that Adopt the wireless scheduling system compatible with heterogeneous core networks described in any one of claims 1-5 to implement the registration and login process, voice group call initiation process, SMS data processing process, and video scheduling process of heterogeneous core networks.

7. The wireless scheduling method compatible with core networks of different manufacturers according to claim 6, characterized in that, The registration and login process includes: Step 101: Start the SDK service modules of multiple heterogeneous core networks on the background SDK service program side and allocate TCPSocket port numbers; Step 102: Configure the foreground client parameters, the IP addresses of the SDK service modules of multiple heterogeneous core networks, and the sending and listening ports of the communication middleware PRC interface module; Step 103: Obtain the login names and passwords of the SDK service modules of heterogeneous core networks. The communication middleware PRC interface module converts the login names and passwords into JSON format and enters them into the Gaoda SDK service module, and converts the login names and passwords into XML format and enters them into the TD Tech SDK service module; Step 104: The communication middleware PRC interface module calls the login interface and passes JSON data parameters to initialize the Gaoda SDK service module and obtain the resource interface to implement login and registration; the communication middleware PRC interface module initializes the eLTE_SDK_Init interface of the TD Tech SDK service module, passes data to the eLTE_SDK_Unified_Login unified login interface, and sets the callback function; Step 105: The Gaoda SDK service module and the TD Tech SDK service module respectively pass the corresponding callback functions to the foreground client through the communication middleware PRC interface module; Step 106: The foreground client displays whether the login is successful. If it fails, it displays the error code of the corresponding failed SDK service module.

8. The wireless scheduling method compatible with core networks of different manufacturers according to claim 6, characterized in that The voice group call initiation process includes: Step 201: Determine the group to be called according to the group number selected by the user on the foreground client interface; Step 202: The service processing logic judgment module determines the group belonging type according to the group to be called and initiates a simultaneous or single call to the corresponding SDK service module; Trigger the communication middleware PRC interface module to send Socket information to connect to the corresponding SDK service module according to the key press event on the foreground client interface; Step 203: When the Gaoda SDK service module receives the Socket information, it calls the Call interface function to pass the Socket message in and waits for the terminal under the Gaoda core network to receive the group call message. When the call status becomes speaking, set the output speaker channel; and / or, When the TD Tech SDK service module receives the Socket information, it calls the eLTE_SDK_PTTDail interface to pass the Socket message in and waits for the terminal under the TD Tech core network to receive the group call message. When the call status becomes speaking, enumerate the output speaker channels; Step 204: The communication middleware PRC interface module sends the status of the voice service callback function to the foreground client in Socket mode, and the foreground client obtains the call right and turns on the microphone; Step 205: Complete the group call according to the release of the PTT button event on the foreground client interface; Step 206: The communication middleware PRC interface module sends Socket information to the corresponding SDK service module; Step 207: The GOTA SDK service module receives the Socket information and calls the Callrelease interface; and / or, the TD Tech SDK service module receives the Socket information and calls the eLTE_SDK_PTTrelease interface; Step 208: After successfully calling the interface, the communication middleware PRC interface module sends the Socket information to the foreground client interface.

9. The wireless scheduling method compatible with core networks of different manufacturers according to claim 6, characterized in that The SMS data processing flow includes: Step 301: Obtain the text content to be sent input by the user on the foreground client interface; Step 302: According to the terminal number selected or input by the user, the service processing logic judgment module reads the corresponding complete information in the dispatching data storage server and determines which core network the terminal number belongs to; Step 303: Send Socket information to the corresponding SDK service module to be called through the communication middleware PRC interface module; Step 304: Wait for the status notification of the callback function and send Socket information to the foreground client through the communication middleware PRC interface module; Step 305: When there is TD Tech core network information in the complete information, call the eLTE-SDK-SDSSendmassage interface function of the TD Tech SDK service module, construct the text content into the parameter XML format through the communication middleware PRC interface module, set the point-to-point message sending mode, and send it to the eLTE-SDK-SDSSendmassage interface, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module; When there is GOTA core network information in the complete information, call the String message interface function of the GOTA SDK service module, construct the text content into the parameter JSON format through the communication middleware PRC interface module, send it to the String message interface, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module.

10. The wireless scheduling method compatible with core networks of different manufacturers according to claim 6, characterized in that, The video dispatching flow includes: Step 401: Obtain the terminal number for video dispatching selected or input by the user on the foreground client interface; Step 402: According to the terminal number selected or input by the user, the service processing logic judgment module reads the corresponding complete information in the dispatching data storage server and determines which core network the terminal number belongs to; Step 403: Send Socket information to the corresponding SDK service module to be called through the communication middleware PRC interface module; Step 404: When there is TD Tech core network information in the complete information, call the eLTE_SDK_startrealplay interface function of the TD Tech SDK service module, set the video play window with the eLTE_SDK_setplaywindow interface function, wait for the status notification of the callback function, and return it to the foreground client through the communication middleware PRC interface module; When there is core network information in the complete information, call the real-time video interface of the Gundam SDK service module, wait for the status notification of the callback function, and transmit it back to the foreground client through the communication middleware PRC interface module.

Images