CN109246628B

CN109246628B - Wireless dispatching desk based on air bus digital trunking system and implementation method

Info

Publication number: CN109246628B
Application number: CN201811342217.5A
Authority: CN
Inventors: 张嘉旺; 王智超; 姜磊; 赵彦芳; 陈春梅
Original assignee: Tianjin 712 Mobile Communication Co Ltd
Current assignee: Tianjin 712 Mobile Communication Co Ltd
Priority date: 2018-11-13
Filing date: 2018-11-13
Publication date: 2023-06-27
Anticipated expiration: 2038-11-13
Also published as: CN109246628A

Abstract

The invention discloses a wireless dispatching desk based on an air bus digital trunking system and an implementation method thereof. The wireless dispatching desk comprises a dispatching desk terminal program and a background processing program, wherein the background processing program comprises an EADS user part management module, an EADS voice part management module, an EADS short message part management module, a multi-interface display module, a CAD management module and a database management module; the AIRBUS TETRA is used as a core system for secondary development, so that the call functions between the dispatch and the train, between the dispatch and the fixed station, between the train and the fixed station, between the trains and the outside line are realized; the data service functions such as state information, short data information transmission and the like are realized. The method is convenient for the high-efficiency communication among the fixed personnel in the rail transit, and meets the practical communication requirements of the user for simplicity, rapidness and safety.

Description

Wireless dispatching desk based on air bus digital trunking system and implementation method

Technical Field

The invention relates to a wireless dispatching desk, in particular to a wireless dispatching desk based on an air bus digital trunking system and an implementation method thereof.

Background

The wireless dispatching desk provides reliable voice and data information transmission service for a dispatcher, and has the main task of ensuring normal conversation between the dispatching desk and the fixed desk during operation, meeting the requirement of daily driving dispatching and receiving clock signals and train information provided by the CAD server. With the impact of empty passengers on the domestic rail transit market, the market share of the empty passengers tends to be increased day by day. The company is always responsible for the construction work of the wireless communication system software and hardware of the base MOTOROLAT TETRA cluster system such as a subway locomotive station, a dispatching desk and the like, and achieves good results. In recent years, we strive to independently develop a wireless dispatching desk based on an air bus digital trunking system to solve the current situations that trunking products of our company are only bound with motorcycles, bid, purchase, price negotiations and the like are limited, so as to fill the blank of the wireless dispatching desk based on the air bus digital trunking system.

Disclosure of Invention

The invention aims to utilize AIRBUS TETRA as a core system for secondary development, and particularly provides a wireless dispatching desk based on an air bus digital trunking system and an implementation method thereof, so as to realize the conversation functions between dispatching and trains, between dispatching and a fixed station, between trains and the fixed station, between trains and outside lines; the data service functions such as state information, short data information transmission and the like are realized.

The technical scheme adopted by the invention is as follows: the wireless dispatching desk based on the air bus digital cluster system is characterized by comprising a PIC-e card, wherein the PIC-e card is inserted on a PC mainboard, namely, is connected with the PC in a PIC interface mode and is used for processing corresponding commands, compiling instructions identifiable by a computer and communicating with a TCS server through a network port; the wireless dispatching desk also comprises a Roland external sound card which is connected with the PC through a USB interface mode and is used for controlling the sound and the channel of the main sound and the auxiliary sound and the recording interface; the wireless dispatching desk also comprises an external PTT pressing board, namely is connected with the PC machine through a COM interface mode and is used for realizing calling speaking right application/release commands required by a dispatching desk program by clicking the external PTT pressing board.

The invention relates to a method for realizing a wireless dispatching desk based on an air bus digital trunking system, which is characterized in that the wireless dispatching desk comprises a dispatching desk terminal program and a background processing program, and the dispatching desk terminal program comprises a log thread processing flow, a configuration information reading flow and a main interface initialization flow; and respectively performing the following operations:

1. Log thread processing flow

Firstly, waiting for receiving a log message, acquiring current system time after the log message is received, judging whether the acquired system time is successful or not, if so, directly entering a formatted system time character string, then entering log level judgment, if not, using a default system time character string, and then entering log level judgment; judging whether the thread exit message is received or not, and if so, ending the flow; if not, further judging whether the received log message is a common message, if so, processing the common message, adding message content and time into the log content, writing the log document, and returning to the step of waiting for receiving the log message; if the message is not the common message, further judging whether the message is an alarm message, if the message is the alarm message, adding the message content and time into the log content, writing the log document, and returning to the step of waiting for receiving the log message; if the information is not the alarm information, further judging whether the information is an error information, if the information is the error information, adding the information content and time into the log content, writing the information into the log file, and returning to the step of waiting for receiving the log information; if the message is not an error message, the message is regarded as an unknown message, the message content and time are added in the log content, the log file is written, and then the step of waiting for receiving the log message is returned.

2. Flow for reading configuration information

Firstly judging whether the configuration file is successfully opened, if so, reading the IP address, the port and the dispatching desk type of the server, returning to the IP address, the port and the dispatching desk type interface of the server, if not, displaying the configuration file opening failure interface, inputting the IP address, the port and the dispatching desk type of the server by a user, storing the configuration information file, returning to the IP address, the port and the dispatching desk type interface of the server, and ending the flow.

3. Main interface initialization flow

Firstly, reading login information from a configuration file, and if the reading fails, manually inputting the login information and clicking a login button; clicking a login button, connecting a database for information verification, and connecting a CAD (computer aided design), the database and a TCS (TCS) server if the verification is successful; if the verification fails, returning to the login starting step; judging whether the CAD, the database and the TCS server are successfully connected or not; if the CAD connection is successful, user information is acquired from the CAD until user data is successfully acquired; if the CAD connection fails, reconnecting the CAD; if the database is successfully connected, acquiring user information from the database until the user data is successfully acquired; if the database connection fails, reconnecting the database; if the TCS server is successfully connected, user information is acquired from the CAD until user data is successfully acquired; if the TCS server fails to be connected, reconnecting the TCS server; judging whether the user information is successfully obtained from the CAD, the database and the TCS server, if so, comprehensively processing the obtained user information, displaying the obtained user information on a main interface, and ending the flow; if the user information is not successfully acquired from the CAD, the database and the TCS server, the judgment is continued until the user information is successfully acquired.

The background processing program comprises an EADS user part management module, an EADS voice part management module, an EADS short message part management module, a multi-interface display module, a CAD management module and a database management module; the EADS user part management module, the EADS voice part management module and the EADS short message part management module form a TCS interaction module and interact with the TCS server through a TCS API interface mode of the COM component; the multi-interface display module is responsible for updating the main interface in real time according to the information obtained by the receipt after the TCS interaction module receives the receipt of the TCS server; the CAD management module and the database management module form a CAD interaction module and interact with the CAD server through a TCP/IP interface mode.

The EADS user part management module, the EADS voice part management module and the EADS short message part management module all execute the following interaction flow with the TCS server:

firstly, waiting for an event object, judging whether an exit message is received or not, if so, directly exiting, and ending the flow; if not, judging whether the feedback message is the feedback message of the TCS server; if the feedback information is the feedback information of the TCS server, analyzing the feedback information of the TCS server, storing the feedback information into a log file, updating an interface according to the feedback information of the TCS server, updating parameters according to the feedback information of the TCS server, and finally returning to enter the step of waiting for an event object; if the feedback message is not the feedback message of the TCS server, setting corresponding parameters according to the interaction message; executing corresponding API statements according to the interactive message, and then judging whether the API execution statements are successful or not; if the execution fails, recording an error result of the execution, recording the result into a log file, and returning to the step of waiting for an event object; if the execution is successful, corresponding operation is executed according to the feedback information, the result is recorded in the log file, and finally the step of waiting for the event object is returned.

The EADS voice part management module comprises an initiating duplex call flow, a receiving duplex call flow, an initiating half duplex call flow, a receiving duplex call flow and a speaking right operation flow which realize voice functions, and respectively executes the following operations:

1. initiating duplex call flows

Firstly, selecting a handheld station for initiating a call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the duplex call is successfully initiated or not according to the interaction result, if not, prompting the user to initiate the duplex call to fail, adding the failure result into the log file, and ending the flow; if so, setting the corresponding control to be in a state of initiating duplex call success, and adding the result into a log file; then normal duplex call step is carried out, then whether call ending information is received or not is judged, if not, the call is ended by clicking, necessary parameters are transmitted to the TCS server, and interaction is carried out with the TCS server; judging whether the duplex call is ended or not according to the call result, if so, setting the corresponding control to be in a duplex call ending state, adding the result into a log file, and ending the flow; if not, prompting the user to end the duplex call failure, prompting the user to try to end the duplex call again, adding the failure result into the log file, and ending the flow; if the duplex call ending message is received, the corresponding control is directly set to be in a duplex call ending state, the result is added into the log file, and the process is ended.

2. Receive duplex call flow

Firstly, necessary parameters are transmitted to a TCS server, and interaction with the TCS server is performed; judging whether the duplex call is successfully received or not according to the interaction result, if not, prompting the user that the duplex call is failed to be received, adding the failure result into a log file, and ending the flow; if the duplex call is successful, setting the corresponding control to be in a successful state of receiving the duplex call, adding the result into a log file, and then carrying out a normal duplex call step; judging whether duplex call ending information is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the duplex call is ended or not according to the interaction result, if so, setting the corresponding control to be in a successful state of ending the duplex call, adding the result into a log file, and ending the flow; if not, prompting the user to end the duplex call failure, and adding the failure result into the log file, and ending the flow; if the duplex call ending message is received, the corresponding control is directly set to be in a state of ending duplex call success, the result is added into the log file, and the process is ended.

3. Initiating half duplex call flows

Firstly, selecting a group needing to initiate a half-duplex call, transmitting necessary parameters to a TCS server, interacting with the TCS server, judging whether the half-duplex call is successful or not according to the interaction result, prompting a user to initiate the half-duplex call to fail if the half-duplex call is unsuccessful, adding the failure result to a log file, and ending the flow; if the call is successful, setting the corresponding control to be in a successful state of initiating the half duplex call, and adding the result into a log file; then normal half duplex communication step is carried out, and speaking right operation is carried out; judging whether a half duplex call ending message is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether ending the half duplex call is successful or not according to the call result, if so, setting the corresponding control to be in a state of initiating the half duplex call ending, adding the result into a log file, and ending the flow; if not, prompting the user to end the half duplex call failure, prompting the user to try to end the call again, and adding the failure result into the log file, so that the flow is ended; if the half-duplex call ending message is received, the corresponding control is directly set to be in a state of initiating the half-duplex call ending, the result is added into the log file, and the process is ended.

4. Receiving half duplex call flows

Firstly, receiving a half-duplex call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the half duplex call is successfully received or not according to the interaction result, if not, prompting the user that the half duplex call is failed to be received, adding the failure result into a log file, and ending the flow; if the call is successful, setting a corresponding control to be in a receiving half-duplex call success state, adding the result into a log file, then carrying out a normal half-duplex call step, and entering a speaking right operation; judging whether a half duplex call ending message is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the ending half duplex call is successful or not according to the interaction result, if so, setting the corresponding control to be in a successful state of ending the half duplex call, adding the result into a log file, and ending the flow; if not, prompting the user to end the half duplex call failure, and adding the failure result into the log file, and ending the flow; if the half duplex call ending message is received, the corresponding control is directly set to be in a state of ending the half duplex call success, the result is added into the log file, and the process is ended.

5. Speaking right operation flow

Firstly, judging whether the call ticket is applied, if so, setting call ticket application parameters, then transmitting necessary parameters to a TCS server, interacting with the TCS server, judging whether the call ticket application is successful according to an interaction result, if so, setting a corresponding control to be in a call ticket application success state, adding the result to a log file, and ending the flow; if not, prompting the user to apply the speaking right for failure, prompting the user to try to apply the speaking right again, adding the failure result into the log file, and ending the flow; if the call right is not applied, setting a call right releasing parameter, then transmitting necessary parameters to the TCS server, interacting with the TCS server, judging whether the call right releasing is successful or not according to the interaction result, if so, setting a corresponding control to be in a call right releasing successful state, adding the result to a log file, and ending the flow; if not, prompting the user that the release of the speaking right fails, prompting the user to try to release the speaking right again, and adding the failure result into the log file.

The EADS short message part management module comprises a message storage flow and a message reading flow, and respectively executes the following operations:

1. Message storage flow

Firstly, judging whether a buffer area is full or not, if so, covering the earliest message, and then entering an activated message processing thread; if not, inserting a message at the tail end of the buffer area, and then entering an activated message processing thread; the flow ends.

2. Read report Wen Liucheng

Firstly, comparing the stored and read flag bits, judging whether an unprocessed message exists or not, and if not, ending the flow; if so, returning the unprocessed message, and ending the flow.

The CAD management module comprises an initialization interface flow, an initialization interaction flow with a CAD server, a data receiving flow interacted with the CAD server and a data processing flow, and the following operations are respectively executed:

1. initializing interface flow

Initializing an interface, inputting a user name or a password by a user, judging whether network connection is successful or not, if not, prompting that the network connection is failed, and ending the flow; if the CAD address is successful, the CAD address is pined according to the configuration information, then whether the CAD address is pined is judged, if the CAD address is not pined, the CAD address is prompted to be not opposite, namely, a parameter configuration interface is popped up, parameter configuration is carried out, and the process is finished; if the connection is ping, connecting the CAD database according to the configuration information; judging whether the CAD database is successfully connected or not, if not, prompting that the user name and the password are wrong, and ending the flow; if the connection is successful, returning login success information, and storing the login success information in a log.

2. Initialization and CAD server interaction flow

Firstly, waiting for an event object, judging whether an exit thread message is received or not, if so, directly exiting, and ending the flow; if not, judging whether the CAD is connected, and if so, returning to the step of waiting for the event object; if the CAD is not connected, a Socket is created, whether the CAD is connected successfully or not is judged, if the CAD is not connected successfully, CAD failure is set, connection failure information is stored in a log file, the connection failure information is delayed for 5 seconds, the Socket is released, and the step of waiting for an event object is returned; if the connection is successful, waking up the receiving data thread, setting CAD success, storing the connection success information into a log file, and returning to the step of waiting for the event object.

3. Receive data flow

Firstly, judging whether an exit message is received or not, and if so, ending the flow; if not, continuing to judge whether the CAD server is connected, and if so, waiting for receiving data; judging the function return value of the received data, if the function return value is greater than 0, detecting the message and removing the head and the tail of the message; then storing the complete message into a buffer area to store the message; if the CAD server is not connected and the function return value is smaller than or equal to 0, setting a connection disconnection flag, prompting the connection disconnection of the CAD server, and storing the disconnection information in a log file.

4. Data processing flow

Firstly, judging whether an exit message is received or not, and ending the flow if the exit message is received; if not, continuing to judge whether unprocessed data exists, and if not, returning to the step of waiting for the event object; if so, the unprocessed data is read from the buffer, the message is analyzed, relevant operation is carried out, and the message is read.

The database management module of the invention comprises a read-write database flow and an initialization and database interaction flow, and respectively executes the following operations:

1. read-write database flow

Firstly, judging whether an exit message is received or not, and ending the flow if the exit message is received; if not, further judging whether the database is successfully connected, if so, setting the connection database to be failed, storing the failure information in a log file, and returning to the step of waiting for an event; if the connection is successful, generating a database execution statement according to the read-write information, and executing the database execution statement; judging whether the execution of the database execution statement is successful or not, if so, extracting data according to the execution result, and returning to the step of waiting for an event; if not, setting the connection database to fail, storing the failure information in a log file, and returning to the step of waiting for an event.

2. Initialization and database interaction flow

Firstly, waiting for an event object, judging whether an exit message is received or not, if so, directly exiting, and ending the flow; if not, connecting the database according to the parameters in the configuration information, then judging whether the database is successfully connected, if not, setting the connection database to fail, storing the failure information in a log file, and returning to the step of waiting for an event object after delaying for 5 seconds; if the connection is successful, setting the connection database to be successful, and after 5 seconds of delay, returning to the step of waiting for the event object.

The beneficial effects of the invention are as follows: the AIRBUS TETRA is used as a core system for secondary development, so that the call functions between the dispatch and the train, between the dispatch and the fixed station, between the train and the fixed station, between the trains and the outside line are realized; the data service functions such as state information, short data information transmission and the like are realized. The method is convenient for the high-efficiency communication among the fixed personnel in the rail transit, and meets the practical communication requirements of the user for simplicity, rapidness and safety.

Drawings

FIG. 1 is a schematic block diagram of a hardware connection of the present invention;

FIG. 2 is a diagram of a software architecture of the present invention;

FIG. 3 is a flow chart of a main thread of the program of the present invention;

FIG. 4 is a flow chart of log thread processing in FIG. 3;

FIG. 5 is a flow chart of the read configuration information in FIG. 3;

FIG. 6 is a flow chart of the primary interface initialization process of FIG. 3;

FIG. 7 is a flow chart of interaction with the TCS server of FIG. 3;

FIG. 8 is a flow chart of an originating duplex call of the EADS voice portion management module of FIG. 2;

FIG. 9 is a receive duplex call flow diagram of the EADS voice portion management module of FIG. 2;

FIG. 10 is a flow chart of an initiated half duplex call of the EADS voice portion management module of FIG. 2;

FIG. 11 is a flow chart of a receive duplex call of the EADS voice portion management module of FIG. 2;

FIG. 12 is a flow chart illustrating the operation of the EADS speech portion management module of FIG. 2;

FIG. 13 is a flow chart of a stored message of the EADS SMS part management module of FIG. 2;

FIG. 14 is a read message flow diagram of the EADS SMS portion management module of FIG. 2;

FIG. 15 is a flowchart of an initialization interface of the CAD management module of FIG. 2;

FIG. 16 is a flowchart illustrating the initialization of the CAD management module of FIG. 2 interacting with a CAD server;

FIG. 17 is a flow chart of received data from the CAD management module of FIG. 2;

FIG. 18 is a process data flow of the CAD management module of FIG. 2;

FIG. 19 is a flow chart of the read/write database of the database management module of FIG. 2;

FIG. 20 is a flow chart illustrating the initialization and database interaction of the database management module of FIG. 2.

Detailed Description

The invention is further described below with reference to the accompanying drawings:

as shown in fig. 1, a wireless dispatching desk based on an air bus digital trunking system comprises a PIC-e card, wherein the PIC-e card is inserted on a main board of a PC, namely is connected with the PC through a PIC interface mode and is used for processing corresponding commands, compiling the commands into commands which can be identified by a computer, and communicating with a TCS server through a network port; the wireless dispatching desk also comprises a Roland external sound card which is connected with the PC through a USB interface mode and is used for controlling the sound and the channel of the main sound and the auxiliary sound and the recording interface; the wireless dispatching desk also comprises an external PTT pressing board, namely is connected with the PC machine through a COM interface mode and is used for realizing calling speaking right application/release commands required by a dispatching desk program by clicking the external PTT pressing board.

The dispatcher station needs to install a PIC-e card on a general purpose PC on the market and install a responsive driver. The dispatcher program needs to process the corresponding command into a command which can be recognized by a computer by means of the PIC-e card and process the PIC-e card, and the command is communicated with the TCS server through a network port. The receipt information of the TCS server is also processed by the PIC-e card to be identified by the dispatcher.

The dispatching desk needs to insert an external PTT pressing board on a general PC machine on the market, and the calling speaking right application/release command required by the dispatching desk program is realized by clicking the external PTT pressing board.

The dispatcher station needs to install an external sound card of Roland Octa-capture on a general purpose PC on the market. The control of the main and auxiliary sound of the dispatching desk and the control of the recording interface are all based on the external sound card.

As shown in fig. 2 and 3, the dispatcher station includes a dispatcher station terminal program and a background processing program, and the dispatcher station terminal program includes a log thread processing flow, a configuration information reading flow and a main interface initialization flow; and respectively performing the following operations:

1. log thread processing flow

As shown in fig. 4: firstly, waiting for receiving a log message, acquiring current system time after the log message is received, judging whether the acquired system time is successful or not, if so, directly entering a formatted system time character string, then entering log level judgment, if not, using a default system time character string, and then entering log level judgment; judging whether the thread exit message is received or not, and if so, ending the flow; if not, further judging whether the received log message is a common message, if so, processing the common message, adding message content and time into the log content, writing the log document, and returning to wait for receiving the log message; if the message is not the common message, further judging whether the message is an alarm message, if the message is the alarm message, adding the message content and time into the log content, writing the log document, and returning to the step of waiting for receiving the log message; if the information is not the alarm information, further judging whether the information is an error information, if the information is the error information, adding the information content and time into the log content, writing the information into the log file, and returning to the step of waiting for receiving the log information; if the message is not an error message, the message is regarded as an unknown message, the message content and time are added in the log content, the log file is written, and then the step of waiting for receiving the log message is returned.

2. Flow for reading configuration information

As shown in fig. 5: firstly judging whether the configuration file is successfully opened, if so, reading the IP address, the port and the dispatching desk type of the server, returning to the IP address, the port and the dispatching desk type interface of the server, if not, displaying the configuration file opening failure interface, inputting the IP address, the port and the dispatching desk type of the server by a user, storing the configuration information file, returning to the IP address, the port and the dispatching desk type interface of the server, and ending the flow.

3. Main interface initialization flow

As shown in fig. 6: firstly, reading login information from a configuration file, and if the reading fails, manually inputting the login information and clicking a login button; clicking a login button, connecting a database for information verification, and connecting a CAD (computer aided design), the database and a TCS (TCS) server if the verification is successful; if the verification fails, returning to the login starting step; judging whether the CAD, the database and the TCS server are successfully connected or not; if the CAD connection is successful, user information is acquired from the CAD until user data is successfully acquired; if the CAD connection fails, reconnecting the CAD; if the database is successfully connected, acquiring user information from the database until the user data is successfully acquired; if the database connection fails, reconnecting the database; if the TCS server is successfully connected, user information is acquired from the CAD until user data is successfully acquired; if the TCS server fails to be connected, reconnecting the TCS server; judging whether the user information is successfully obtained from the CAD, the database and the TCS server, if so, comprehensively processing the obtained user information, displaying the obtained user information on a main interface, and ending the flow; if the user information is not successfully acquired from the CAD, the database and the TCS server, the judgment is continued until the user information is successfully acquired.

As shown in fig. 2, the background processing program includes an EADS user part management module, an EADS voice part management module, an EADS short message part management module, a multi-interface display module, a CAD management module, and a database management module; the EADS user part management module, the EADS voice part management module and the EADS short message part management module form a TCS interaction module and interact with the TCS server through a TCS API interface mode of the COM component; the multi-interface display module is responsible for updating the main interface in real time according to the information obtained by the receipt after the TCS interaction module receives the receipt of the TCS server; the CAD management module and the database management module form a CAD interaction module and interact with the CAD server through a TCP/IP interface mode.

The software of the invention is wholly divided into two parts: a dispatcher terminal UI and a background handler. The call service and the short message service of the dispatching desk are realized by the interaction between the API interface of the COM component (provided by the air passenger) and the TCS server. The background processing part of the dispatching desk is mainly divided into three modules. The first module is an interaction module with the TCS and mainly comprises an EADS user part management module, an EADS voice part management module and an EADS short message part management module. The program realizes interaction with the TCS server through the three sub-modules to realize the dispatcher voice service and the short message service, and also comprises some operations related to user attributes, such as dispatch, acquisition of radio station on-off state and the like. The second module is a multi-interface display module and is mainly responsible for updating the main interface in real time according to the information obtained by the receipt after the TCS interaction module receives the receipt of the TCS server. The third module is an interaction with the CAD server, and is mainly used for interacting with the jurisdictional train information from the CAD and obtaining information of the dispatcher database. Interactions with CAD include applying for clocks, applying for jurisdictional trains, manual grouping, and so forth.

As shown in FIG. 3, the main thread flow of the program of the present invention is mainly divided into an initialization flow, an interaction flow and an exit flow. The initialization flow comprises starting a log thread, reading configuration information, logging in an interface by a user, initializing a main interface, interacting with CAD by initialization, and interacting with a TCS server by initialization. The functional interactions include voice functions, data functions, interaction with CAD, and reading and writing CAD databases. The exit flow includes releasing CAD connection thread, releasing data receiving thread, releasing data processing thread, and releasing TCS resource.

The EADS user part management module, the EADS voice part management module and the EADS short message part management module execute the following interaction flow with the TCS server:

as shown in fig. 7: firstly, waiting for an event object, judging whether an exit message is received or not, if so, directly exiting, and ending the flow; if not, judging whether the feedback message is the feedback message of the TCS server; if the feedback information is the feedback information of the TCS server, analyzing the feedback information of the TCS server, storing the feedback information into a log file, updating an interface according to the feedback information of the TCS server, updating parameters according to the feedback information of the TCS server, and finally returning to enter the step of waiting for an event object; if the feedback message is not the feedback message of the TCS server, setting corresponding parameters according to the interaction message; executing corresponding API statements according to the interactive message, and then judging whether the API execution statements are successful or not; if the execution fails, recording an error result of the execution, recording the result into a log file, and returning to the step of waiting for an event object; if the execution is successful, corresponding operation is executed according to the feedback information, the result is recorded in the log file, and finally the step of waiting for the event object is returned.

1. initiating duplex call flows

As shown in fig. 8: firstly, selecting a handheld station for initiating a call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the duplex call is successfully initiated or not according to the interaction result, if not, prompting the user to initiate the duplex call to fail, adding the failure result into the log file, and ending the flow; if so, setting the corresponding control to be in a state of initiating duplex call success, and adding the result into a log file; then normal duplex call step is carried out, then whether call ending information is received or not is judged, if not, the call is ended by clicking, necessary parameters are transmitted to the TCS server, and interaction is carried out with the TCS server; judging whether the duplex call is ended or not according to the call result, if so, setting the corresponding control to be in a duplex call ending state, adding the result into a log file, and ending the flow; if not, prompting the user to end the duplex call failure, prompting the user to try to end the duplex call again, adding the failure result into the log file, and ending the flow; if the duplex call ending message is received, the corresponding control is directly set to be in a duplex call ending state, the result is added into the log file, and the process is ended.

2. Receive duplex call flow

As shown in fig. 9, the necessary parameters are initially transferred to the TCS server and interacted with the TCS server; judging whether the duplex call is successfully received or not according to the interaction result, if not, prompting the user that the duplex call is failed to be received, adding the failure result into a log file, and ending the flow; if the duplex call is successful, setting the corresponding control to be in a successful state of receiving the duplex call, adding the result into a log file, and then carrying out a normal duplex call step; judging whether duplex call ending information is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the duplex call is ended or not according to the interaction result, if so, setting the corresponding control to be in a successful state of ending the duplex call, adding the result into a log file, and ending the flow; if not, prompting the user to end the duplex call failure, and adding the failure result into the log file, and ending the flow; if the duplex call ending message is received, the corresponding control is directly set to be in a state of ending duplex call success, the result is added into the log file, and the process is ended.

3. Initiating half duplex call flows

As shown in fig. 10, a group needing to initiate a half duplex call is selected, necessary parameters are transmitted to a TCS server, interaction is performed with the TCS server, whether the half duplex call is initiated is judged according to the interaction result, if not, a user is prompted to fail to initiate the half duplex call, the failure result is added into a log file, and the process is finished; if the call is successful, setting the corresponding control to be in a successful state of initiating the half duplex call, and adding the result into a log file; then normal half duplex communication step is carried out, and speaking right operation is carried out; judging whether a half duplex call ending message is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether ending the half duplex call is successful or not according to the call result, if so, setting the corresponding control to be in a state of initiating the half duplex call ending, adding the result into a log file, and ending the flow; if not, prompting the user to end the half duplex call failure, prompting the user to try to end the call again, and adding the failure result into the log file, so that the flow is ended; if the half-duplex call ending message is received, the corresponding control is directly set to be in a state of initiating the half-duplex call ending, the result is added into the log file, and the process is ended.

4. Receiving half duplex call flows

As shown in fig. 11, initially, a half duplex call is received, necessary parameters are transferred to the TCS server, and the TCS server is interacted with; judging whether the half duplex call is successfully received or not according to the interaction result, if not, prompting the user that the half duplex call is failed to be received, adding the failure result into a log file, and ending the flow; if the call is successful, setting a corresponding control to be in a receiving half-duplex call success state, adding the result into a log file, then carrying out a normal half-duplex call step, and entering a speaking right operation; judging whether a half duplex call ending message is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the ending half duplex call is successful or not according to the interaction result, if so, setting the corresponding control to be in a successful state of ending the half duplex call, adding the result into a log file, and ending the flow; if not, prompting the user to end the half duplex call failure, and adding the failure result into the log file, and ending the flow; if the half duplex call ending message is received, the corresponding control is directly set to be in a state of ending the half duplex call success, the result is added into the log file, and the process is ended.

5. Speaking right operation flow

As shown in fig. 12, firstly, judging whether the call ticket is applied, if yes, setting call ticket application parameters, then transmitting necessary parameters to a TCS server, interacting with the TCS server, judging whether the call ticket application is successful according to the interaction result, if successful, setting a corresponding control to be in a call ticket application success state, adding the result to a log file, and ending the flow; if not, prompting the user to apply the speaking right for failure, prompting the user to try to apply the speaking right again, adding the failure result into the log file, and ending the flow; if the call right is not applied, setting a call right releasing parameter, then transmitting necessary parameters to the TCS server, interacting with the TCS server, judging whether the call right releasing is successful or not according to the interaction result, if so, setting a corresponding control to be in a call right releasing successful state, adding the result to a log file, and ending the flow; if not, prompting the user that the release of the speaking right fails, prompting the user to try to release the speaking right again, and adding the failure result into the log file.

The EADS short message part management module comprises a message storage flow and a message reading flow, and the following operations are respectively executed:

1. Message storage flow

As shown in fig. 13, the character string to be stored is copied, firstly, whether the buffer area is full is judged, if so, the earliest message is covered, and then the activated message processing thread is started; if not, inserting a message at the tail end of the buffer area, and then entering an activated message processing thread; the flow ends.

2. Read report Wen Liucheng

As shown in fig. 14, the process starts, compares the stored and read flag bits, determines whether there is an unprocessed message, and if not, the process ends; if so, returning the unprocessed message, and ending the flow.

The CAD management module comprises an initialization interface flow, an initialization interaction flow with the CAD server, a data receiving flow and a data processing flow which interact with the CAD server, and the following operations are respectively executed:

1. initializing interface flow

As shown in fig. 15, the interface is initialized, the user inputs a user name or a password, whether the network connection is successful is judged, if not, the network connection failure is prompted, and the process is finished; if the CAD address is successful, the CAD address is pined according to the configuration information, then whether the CAD address is pined is judged, if the CAD address is not pined, the CAD address is prompted to be not opposite, namely, a parameter configuration interface is popped up, parameter configuration is carried out, and the process is finished; if the connection is ping, connecting the CAD database according to the configuration information; judging whether the CAD database is successfully connected or not, if not, prompting that the user name and the password are wrong, and ending the flow; if the connection is successful, returning login success information, and storing the login success information in a log.

2. Initialization and CAD server interaction flow

As shown in fig. 16, the process starts, waits for an event object, determines whether an exit thread message is received, and if so, directly exits, and the process ends; if not, judging whether the CAD is connected, and if so, returning to the step of waiting for the event object; if the CAD is not connected, a Socket is created, whether the CAD is connected successfully or not is judged, if the CAD is not connected successfully, CAD failure is set, connection failure information is stored in a log file, the connection failure information is delayed for 5 seconds, the Socket is released, and the step of waiting for an event object is returned; if the connection is successful, waking up the receiving data thread, setting CAD success, storing the connection success information into a log file, and returning to the step of waiting for the event object.

3. Receive data flow

As shown in fig. 17, the process starts, waits for an event object, first determines whether an exit message is received, and if so, the process ends; if not, continuing to judge whether the CAD server is connected, and if so, waiting for receiving data; judging the function return value of the received data, if the function return value is greater than 0, detecting the message and removing the head and the tail of the message; then storing the complete message into a buffer area to store the message; if the CAD server is not connected and the function return value is smaller than or equal to 0, setting a connection disconnection flag, prompting the connection disconnection of the CAD server, and storing the disconnection information in a log file.

4. Data processing flow

As shown in fig. 18, the process starts, waits for an event object, first determines whether an exit message is received, and if so, the process ends; if not, continuing to judge whether unprocessed data exists, and if not, returning to the step of waiting for the event object; if so, the unprocessed data is read from the buffer, the message is analyzed, relevant operation is carried out, and the message is read.

The database management module comprises a read-write database flow and an initialization and database interaction flow, and the following operations are respectively executed:

1. read-write database flow

As shown in fig. 19, the process starts, waits for an event object, first determines whether an exit message is received, and if so, the process ends; if not, further judging whether the database is successfully connected, if so, setting the connection database to be failed, storing the failure information in a log file, and returning to the step of waiting for an event; if the connection is successful, generating a database execution statement according to the read-write information, and executing the database execution statement; judging whether the execution of the database execution statement is successful or not, if so, extracting data according to the execution result, and returning to the step of waiting for an event; if not, setting the connection database to fail, storing the failure information in a log file, and returning to the step of waiting for an event.

2. Initialization and database interaction flow

As shown in fig. 20, the process starts, waits for an event object, judges whether an exit message is received, and if so, directly exits, and the process ends; if not, connecting the database according to the parameters in the configuration information, then judging whether the database is successfully connected, if not, setting the connection database to fail, storing the failure information in a log file, and returning to the step of waiting for an event object after delaying for 5 seconds; if the connection is successful, setting the connection database to be successful, and after 5 seconds of delay, returning to the step of waiting for the event object.

The invention adopts standard Airbus (air bus) EADS cluster system to carry out secondary development, namely modularized development, designs a dispatching desk as a dispatching terminal UI module, a background processing program module and an SQL server database processing module, wherein an EADS user management part, an EADS voice management part and an EADS data short message management part of the background processing module adopt a COM component mode of an Airbus TCS, the background processing program module and the Airbus TCS system are communicated by adopting an SCTP protocol unique to the TCS system to carry out control plane signaling interaction, and adopts an RTP protocol to carry out voice plane data transmission. The communication among the modules adopts protocol interfaces, message transmission and interface calling.

The EADS user part management module, the EADS voice part management module and the EADS short message part management module interact with the TCS server through a TCS API mode. The CAD management module and the database management module interact with the CAD server through a TCP/IP mode. And the execution results of the EADS user part management module, the EADS voice part management module, the EADS short message part management module, the CAD management module and the database management module and the receiving information are displayed on the dispatching desk terminal through the multi-interface display module. The user login and dispatch function is the operation performed by the EADS user part management module on the dispatching desk terminal through the multi-interface display module. The group calling, the individual calling, the emergency calling and the broadcast calling are operations performed on the dispatching desk terminal by the EADS voice part management module through the multi-interface display module. The short message and dispatch command is the operation of the EADS short message part management module on the dispatching desk terminal through the multi-interface display module. The history record, the application clock, the application for train administration and the manual transfer are operations performed on the dispatching desk terminal by the CAD management module through the multi-interface display module. Inquiring configuration information and exiting software is the function of dispatching the terminal.

The wireless dispatching desk initialization flow is to start a log thread, read a configuration file, log in by a user, initialize a main interface, then initialize interaction with CAD, initialize interaction with a database and initialize interaction with a TCS server. The interaction function of the wireless dispatching desk comprises a database reading and writing function, a CAD interaction function, a TCS server interaction function and a voice function. The wireless dispatching desk exit flow is to release the TCS server connection thread, release the CAD server connection thread, release the data processing thread and release the dispatching desk resource.

Claims

1. The wireless dispatching desk based on the air bus digital trunking system is characterized by comprising a PIC-e card, wherein the PIC-e card is inserted on a PC mainboard, namely is connected with the PC in a PIC interface mode and is used for processing corresponding commands, compiling the commands into commands which can be identified by a computer and communicating with a TCS server through a network port; the wireless dispatching desk also comprises a Roland external sound card which is connected with the PC through a USB interface mode and is used for controlling the sound and the channel of the main sound and the auxiliary sound and the recording interface; the wireless dispatching desk also comprises an external PTT pressing board, namely is connected with the PC machine through a COM interface mode and is used for realizing calling speaking right application/release commands required by a dispatching desk program by clicking the external PTT pressing board;

The wireless dispatching desk comprises a dispatching desk terminal program and a background processing program; the background processing program comprises an EADS user part management module, an EADS voice part management module, an EADS short message part management module, a multi-interface display module, a CAD management module and a database management module; the user login and dispatch of the EADS user part management module is operated on the dispatching desk terminal through the multi-interface display module; the group calling, individual calling, emergency calling and broadcast calling of the EADS voice part management module are operated on the dispatching desk terminal through the multi-interface display module; the short message and dispatch command of the EADS short message part management module are operated on the dispatching desk terminal through the multi-interface display module; the historical record, the application clock, the application management train and the manual transfer group of the CAD management module are operated on the dispatching desk terminal through the multi-interface display module;

the EADS user part management module, the EADS voice part management module and the EADS short message part management module form a TCS interaction module and interact with the TCS server through a TCS API interface mode of the COM component; the multi-interface display module is responsible for updating the main interface in real time according to the information obtained by the receipt after the TCS interaction module receives the receipt of the TCS server; the CAD management module and the database management module form a CAD interaction module and interact with the CAD server through a TCP/IP interface mode.

2. The method for implementing a wireless dispatching desk based on an air bus digital trunking system according to claim 1, wherein the dispatching desk terminal program comprises a log thread processing flow, a configuration information reading flow and a main interface initialization flow; and respectively performing the following operations:

1. log thread processing flow

Firstly, waiting for receiving a log message, acquiring current system time after the log message is received, judging whether the acquired system time is successful or not, if so, directly entering a formatted system time character string, then entering log level judgment, if not, using a default system time character string, and then entering log level judgment; judging whether the thread exit message is received or not, and if so, ending the flow; if not, further judging whether the received log message is a common message, if so, processing the common message, adding message content and time into the log content, writing the log document, and returning to the step of waiting for receiving the log message; if the message is not the common message, further judging whether the message is an alarm message, if the message is the alarm message, adding the message content and time into the log content, writing the log document, and returning to the step of waiting for receiving the log message; if the information is not the alarm information, further judging whether the information is an error information, if the information is the error information, adding the information content and time into the log content, writing the information into the log file, and returning to the step of waiting for receiving the log information; if the information is not the error information, the information is regarded as the unknown information, the information content and time are added in the log content, the log file is written, and then the step of waiting for receiving the log information is returned;

2. Flow for reading configuration information

Firstly judging whether a configuration file is successfully opened, if so, reading the IP address, the port and the dispatching desk type of the server, returning to the IP address, the port and the dispatching desk type interface of the server, if not, displaying a configuration file opening failure interface, inputting the IP address, the port and the dispatching desk type of the server by a user, storing a configuration information file, returning to the IP address, the port and the dispatching desk type interface of the server, and ending the flow;

3. main interface initialization flow

3. The method for implementing a wireless dispatch station based on an air bus digital trunking system according to claim 1, wherein the EADS user part management module, the EADS voice part management module and the EADS short message part management module all execute the following interaction flow with a TCS server:

4. The method for implementing a wireless dispatch station based on an air bus digital trunking system according to claim 3, wherein the EADS voice part management module comprises an originating duplex call flow, a receiving duplex call flow, an originating half duplex call flow, a receiving duplex call flow and a speaking right operation flow for implementing a voice function, and performs the following operations:

1. initiating duplex call flows

Firstly, selecting a handheld station for initiating a call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the duplex call is successfully initiated or not according to the interaction result, if not, prompting the user to initiate the duplex call to fail, adding the failure result into the log file, and ending the flow; if so, setting the corresponding control to be in a state of initiating duplex call success, and adding the result into a log file; then normal duplex call step is carried out, then whether call ending information is received or not is judged, if not, the call is ended by clicking, necessary parameters are transmitted to the TCS server, and interaction is carried out with the TCS server; judging whether the duplex call is ended or not according to the call result, if so, setting the corresponding control to be in a duplex call ending state, adding the result into a log file, and ending the flow; if not, prompting the user to end the duplex call failure, prompting the user to try to end the duplex call again, adding the failure result into the log file, and ending the flow; if the duplex call ending message is received, the corresponding control is directly set to be in a duplex call ending state, the result is added into the log file, and the process is ended;

2. Receive duplex call flow

Firstly, necessary parameters are transmitted to a TCS server, and interaction with the TCS server is performed; judging whether the duplex call is successfully received or not according to the interaction result, if not, prompting the user that the duplex call is failed to be received, adding the failure result into a log file, and ending the flow; if the duplex call is successful, setting the corresponding control to be in a successful state of receiving the duplex call, adding the result into a log file, and then carrying out a normal duplex call step; judging whether duplex call ending information is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the duplex call is ended or not according to the interaction result, if so, setting the corresponding control to be in a successful state of ending the duplex call, adding the result into a log file, and ending the flow; if not, prompting the user to end the duplex call failure, and adding the failure result into the log file, and ending the flow; if the duplex call ending message is received, the corresponding control is directly set to be in a state of ending duplex call success, the result is added into the log file, and the process is ended;

3. Initiating half duplex call flows

Firstly, selecting a group needing to initiate a half-duplex call, transmitting necessary parameters to a TCS server, interacting with the TCS server, judging whether the half-duplex call is successful or not according to the interaction result, prompting a user to initiate the half-duplex call to fail if the half-duplex call is unsuccessful, adding the failure result to a log file, and ending the flow; if the call is successful, setting the corresponding control to be in a successful state of initiating the half duplex call, and adding the result into a log file; then normal half duplex communication step is carried out, and speaking right operation is carried out; judging whether a half duplex call ending message is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether ending the half duplex call is successful or not according to the call result, if so, setting the corresponding control to be in a state of initiating the half duplex call ending, adding the result into a log file, and ending the flow; if not, prompting the user to end the half duplex call failure, prompting the user to try to end the call again, and adding the failure result into the log file, so that the flow is ended; if the half-duplex call ending message is received, the corresponding control is directly set to be in a state of initiating the half-duplex call ending, the result is added into the log file, and the process is ended;

4. Receiving half duplex call flows

Firstly, receiving a half-duplex call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the half duplex call is successfully received or not according to the interaction result, if not, prompting the user that the half duplex call is failed to be received, adding the failure result into a log file, and ending the flow; if the call is successful, setting a corresponding control to be in a receiving half-duplex call success state, adding the result into a log file, then carrying out a normal half-duplex call step, and entering a speaking right operation; judging whether a half duplex call ending message is received or not, if not, clicking to end the call, transmitting necessary parameters to a TCS server, and interacting with the TCS server; judging whether the ending half duplex call is successful or not according to the interaction result, if so, setting the corresponding control to be in a successful state of ending the half duplex call, adding the result into a log file, and ending the flow; if not, prompting the user to end the half duplex call failure, and adding the failure result into the log file, and ending the flow; if the half-duplex call ending message is received, directly setting a corresponding control to be in a state of ending the half-duplex call success, adding the result into a log file, and ending the flow;

5. Speaking right operation flow

5. The method for implementing a wireless dispatch station based on an air bus digital trunking system according to claim 3, wherein the EADS short message part management module comprises a message storing process and a message reading process, and performs the following operations respectively:

1. Message storage flow

Firstly, judging whether a buffer area is full or not, if so, covering the earliest message, and then entering an activated message processing thread; if not, inserting a message at the tail end of the buffer area, and then entering an activated message processing thread; the flow is finished;

2. read report Wen Liucheng

6. The method for implementing a wireless dispatching desk based on an air bus digital trunking system according to claim 1, wherein the CAD management module comprises an initialization interface process, an initialization and CAD server interaction process, a data receiving process and a data processing process, which interact with the CAD server, and the following operations are respectively executed:

1. initializing interface flow

Initializing an interface, inputting a user name or a password by a user, judging whether network connection is successful or not, if not, prompting that the network connection is failed, and ending the flow; if the CAD address is successful, the CAD address is pined according to the configuration information, then whether the CAD address is pined is judged, if the CAD address is not pined, the CAD address is prompted to be not opposite, namely, a parameter configuration interface is popped up, parameter configuration is carried out, and the process is finished; if the connection is ping, connecting the CAD database according to the configuration information; judging whether the CAD database is successfully connected or not, if not, prompting that the user name and the password are wrong, and ending the flow; if the connection is successful, returning login success information, and storing the login success information in a log;

2. Initialization and CAD server interaction flow

Firstly, waiting for an event object, judging whether an exit thread message is received or not, if so, directly exiting, and ending the flow; if not, judging whether the CAD is connected, and if so, returning to the step of waiting for the event object; if the CAD is not connected, a Socket is created, whether the CAD is connected successfully or not is judged, if the CAD is not connected successfully, CAD failure is set, connection failure information is stored in a log file, the connection failure information is delayed for 5 seconds, the Socket is released, and the step of waiting for an event object is returned; if the connection is successful, waking up the data receiving thread, setting CAD success, storing the connection success information into a log file, and returning to the step of waiting for an event object;

3. receive data flow

Firstly, judging whether an exit message is received or not, and if so, ending the flow; if not, continuing to judge whether the CAD server is connected, and if so, waiting for receiving data; judging the function return value of the received data, if the function return value is greater than 0, detecting the message and removing the head and the tail of the message; then storing the complete message into a buffer area to store the message; if the CAD server is not connected and the function return value is smaller than or equal to 0, setting a connection disconnection mark, prompting the connection disconnection of the CAD server, and storing the disconnection information in a log file;

4. Data processing flow

7. The method for implementing a wireless dispatching desk based on an air bus digital trunking system according to claim 1, wherein the database management module comprises a read-write database flow and an initialization and database interaction flow, and performs the following operations respectively:

1. read-write database flow

Firstly, judging whether an exit message is received or not, and ending the flow if the exit message is received; if not, further judging whether the database is successfully connected, if so, setting the connection database to be failed, storing the failure information in a log file, and returning to the step of waiting for an event; if the connection is successful, generating a database execution statement according to the read-write information, and executing the database execution statement; judging whether the execution of the database execution statement is successful or not, if so, extracting data according to the execution result, and returning to the step of waiting for an event; if not, setting a connection database to fail, storing failure information in a log file, and returning to the step of waiting for an event;

2. Initialization and database interaction flow