Air freight message processing method and system, electronic equipment and program product

Abstract

The invention relates to the technical field of air freight, and provides an air freight message processing method and system, electronic equipment and a program product. The method comprises the following steps: respectively docking with at least two message terminals to obtain at least two messages and adding the messages to a received message to-be-processed queue; analyzing the message in the received message to-be-processed queue to obtain a message keyword; classifying and storing the message keywords into a message receiving table; in response to query requests submitted by a plurality of service terminals through a browser, querying corresponding messages from the message receiving table according to the message keywords and feeding back the messages to the service terminals; in response to receiving at least two to-be-sent messages submitted by a plurality of service terminals through a browser, adding the to-be-sent messages to a sent message to-be-processed queue; pushing the to-be-sent messages to a to-be-sent queue according to the telegraph addresses of the to-be-sent messages in the to-be-processed queue for sending the messages; and reading the to-be-sent message from the to-be-sent queue, and sending the to-be-sent message to a corresponding message terminal.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of air freight, and in particular to an air freight message processing method and system, an electronic device, and a program product. BACKGROUND

[0002] In the process of air freight transportation, air freight enterprises interact with each other through Type B telegrams, which is an important message storage and forwarding system in the civil aviation industry and is also widely used in the field of air freight. For example, airport ground agents, airlines, and other air transport enterprises generally receive and send AFTN messages through Aeronautical Fixed Telecommunication Network (AFTN) message terminals and receive and send SITA messages through Societe International De Telecommunications (SITA) message terminals.

[0003] Currently, airports and airlines need to purchase multiple dedicated AFTN message terminals or SITA message terminals to meet the business needs of multiple business departments for sending and receiving telegrams, and lay special line networks for each message terminal, which is relatively high in operating cost. SUMMARY

[0004] The embodiments of the present application provide an air freight message processing method and system, an electronic device, and a program product to solve the problem of high operating cost caused by multiple business departments configuring multiple AFTN message terminals and SITA message terminals.

[0005] In a first aspect, the embodiments of the present application provide an air freight message processing method, which includes: respectively interfacing with at least two kinds of message terminals to obtain at least two kinds of messages; adding the obtained at least two kinds of messages to a received message to-be-processed queue; parsing the messages in the received message to-be-processed queue to obtain message keywords; storing the messages in the received message to-be-processed queue according to the message keywords in a message receiving table; in response to a query request submitted by a plurality of business terminals through a browser, querying the corresponding messages from the message receiving table according to the message keywords and feeding back the messages to the business terminals; the plurality of business terminals are deployed in a plurality of business departments; in response to receiving at least two kinds of to-be-sent messages submitted by the plurality of business terminals through the browser, adding the to-be-sent messages to a to-be-sent message to-be-processed queue; pushing the to-be-sent messages to at least two to-be-sent queues corresponding to the to-be-sent messages respectively according to the telegram addresses of the to-be-sent messages in the to-be-sent message to-be-processed queue; reading the to-be-sent messages from the to-be-sent queues and sending them to the corresponding message terminals.

[0006] In one embodiment, the at least two message terminals include an AFTN message terminal and a SITA message terminal.

[0007] In one embodiment, the interfacing with the at least two message terminals respectively to obtain the at least two messages includes: interfacing with the AFTN message terminal by a serial port mode or a software development kit (SDK) mode to obtain the AFTN message; and / or, interfacing with the SITA message terminal by the SDK mode to obtain the SITA message.

[0008] In one embodiment, the message keyword includes a receiving address, different business departments correspond to different receiving addresses, and each of the plurality of business departments only has the right to query the messages corresponding to the receiving address of the business department; the storing of the messages in the message receiving table according to the message keyword includes: storing the messages in the message receiving table according to the business department corresponding to the message address; and the querying of the corresponding messages from the message receiving table according to the message keyword and the feedback of the messages to the business terminal in response to the query request submitted by the browser of the plurality of business terminals includes: querying the messages corresponding to the first business department from the message receiving table according to the receiving address and feeding back the messages to the business terminal in response to the query request submitted by the browser of at least one business terminal corresponding to the first business department.

[0009] In one embodiment, the pushing of the to-be-sent messages in the sending message processing queue to the at least two to-be-sent queues corresponding to the to-be-sent messages respectively according to the telegraph addresses of the to-be-sent messages in the sending message processing queue includes: pushing the to-be-sent messages to the AFTN message to-be-sent queue according to the address attribute of the telegraph address of each to-be-sent message in the sending message processing queue being a first attribute; the first attribute is the address attribute corresponding to the AFTN message; pushing the to-be-sent messages to the SITA message to-be-sent queue according to the address attribute of the telegraph address of each to-be-sent message in the sending message processing queue being a second attribute; the second attribute is the address attribute corresponding to the SITA message; and the reading of the to-be-sent messages from the to-be-sent queue and the sending of the to-be-sent messages to the corresponding message terminal includes: reading the to-be-sent messages from the AFTN message to-be-sent queue and sending the to-be-sent messages to the AFTN message terminal; and reading the to-be-sent messages from the SITA queue and sending the to-be-sent messages to the SITA message terminal.

[0010] In one embodiment, after the adding of the to-be-sent messages to the sending message processing queue and before the pushing of the to-be-sent messages to the at least two to-be-sent queues corresponding to the to-be-sent messages respectively, the method further includes: setting the sending state of each message in the sending message processing queue to to-be-sent; and after the reading of the to-be-sent messages from the to-be-sent queue and the sending of the to-be-sent messages to the corresponding message terminal, the method further includes: modifying the sending state of the corresponding message to sending completed in response to the sending success.

[0011] In one embodiment, the message key comprises one or more of a sending address, a priority, a receiving address, a sending time group, a message type, a message version, or a message content.

[0012] In one embodiment, the method further comprises: displaying an operation interface by the service terminal; the operation interface comprises at least one of a system management module, an address management module, a sending management module, or a message query management module; wherein the system management module comprises one or more of the following controls: a department management control for a user to set department management information; a role management control for a user to set role management information; a user management control for setting user permissions; an automatic printing configuration control for calling a printer to perform a printing operation in response to a printing request of a user; a system log control for recording various system log information; the address management module comprises one or more of the following controls: a sending address management control for a user to manage sending address information; a receiving address management control for a user to manage receiving address information; a receiving address group management control for a user to divide receiving addresses into different groups; the sending management module comprises one or more of the following controls: a message sending control for generating a sending instruction after detecting a touch action of a user; a message template maintenance control for maintaining a message template, and displaying the message template and generating a corresponding message according to a user input; a telegram short phrase maintenance control for maintaining a telegram short phrase and displaying the telegram short phrase; an abnormal message template maintenance control for maintaining an abnormal message template, and displaying the abnormal message template and generating a corresponding message according to a user input; the message query management module comprises one or more of the following controls: a message sending and receiving query control for querying a received message or a sent message in response to a first query instruction submitted by a user; a message processing log query control for querying a message processing log in response to a second query instruction submitted by a user; a message accurate query control for querying a message that exactly matches a query condition input by a user in response to a third query instruction submitted by a user; a message translation control for translating a Chinese message and displaying a translated telegram code in response to a translation instruction submitted by a user.

[0013] In a second aspect, the embodiments of the present application further provide an air cargo message processing system, the system comprising at least an interface layer and a message processing layer; the interface layer is configured to interface with at least two message terminals respectively to obtain at least two messages; and add the obtained at least two messages to a received message to-be-processed queue; the message processing layer comprises: an analysis module configured to read and analyze the messages in the received message to-be-processed queue, and obtain message keywords; and store the messages in the received message to-be-processed queue in a message receiving table according to the message keywords; a query module configured to respond to a query request submitted by a plurality of business terminals through a browser, and query corresponding messages from the message receiving table according to the keywords and feed back the messages to the business terminals; the plurality of business terminals are deployed in a plurality of business departments; a cache module configured to respond to a received to-be-sent message submitted by the plurality of business terminals through the browser, and add the to-be-sent message to a to-be-sent message to-be-processed queue; a shunting module configured to push the to-be-sent messages in the to-be-sent message to-be-processed queue to at least two to-be-sent queues corresponding to the to-be-sent messages respectively according to the telegraph addresses of the to-be-sent messages; and the interface layer is further configured to read the to-be-sent messages from the to-be-sent queues and send the to-be-sent messages to corresponding message terminals.

[0014] In some embodiments, the system further comprises a display layer; the display layer comprises at least one business terminal; the business terminal is configured to display an operation interface; the operation interface comprises at least one of a system management module, an address management module, a message sending management module, or a message query management module; wherein the system management module comprises one or more of the following controls: a department management control for a user to set department management information; a role management control for a user to set role management information; a user management control for setting user permissions; an automatic printing configuration control for calling a printer to perform a printing operation in response to a printing request of a user; a system log control for recording various system log information; the address management module comprises one or more of the following controls: a message sending address management control for a user to manage message sending address information; a message receiving address management control for a user to manage message receiving address information; a message receiving address group management control for a user to divide message receiving addresses into different groups; the message sending management module comprises one or more of the following controls: a message sending control for generating a sending instruction after detecting a touch action of a user; a message template maintenance control for maintaining a message template, and displaying the message template and generating a corresponding message according to a user input; a telegram short phrase maintenance control for maintaining a telegram short phrase and displaying the telegram short phrase; an abnormal message template maintenance control for maintaining an abnormal message template, and displaying the abnormal message template and generating a corresponding message according to a user input; the message query management module comprises one or more of the following controls: a message sending and receiving query control for querying a received message or a sent message in response to a first query instruction submitted by a user; a message processing log query control for querying a message processing log in response to a second query instruction submitted by a user; a message accurate query control for querying a message that is accurately matched with a query condition input by a user in response to a third query instruction submitted by a user; a message translation control for translating a Chinese message and displaying a translated telegram code in response to a translation instruction submitted by a user.

[0015] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory storing a computer program, wherein the processor implements the steps of the air cargo message processing method of the first aspect when executing the program.

[0016] In a fourth aspect, an embodiment of the present application provides a non-transitory computer-readable storage medium, which stores a computer program, wherein the computer program is executed by a processor to implement the steps of the air cargo message processing method of the first aspect.

[0017] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising a computer program, wherein the computer program is executed by a processor to implement the steps of the air cargo message processing method of the first aspect.

[0018] The aviation cargo message processing method and system, the electronic device, and the program product provided in the embodiments of the present application can be implemented based on the B / S architecture. In the message receiving business processing, at least two kinds of messages are obtained by respectively interfacing with at least two kinds of message terminals. For example, taking the case that the at least two kinds of message terminals include an AFTN message terminal and a SITA message terminal, AFTN messages and SITA messages are obtained by respectively interfacing with the AFTN message terminal and the SITA message terminal, and the messages are stored according to the message keywords obtained by analysis. The message query requests can be submitted by the multiple business terminals of the multiple business departments through a browser. After receiving the query requests, the corresponding messages can be fed back to the business terminals of the corresponding business departments according to the message keywords. For example, the classified messages can be stored according to different categories for different business departments, and each business department can only query the messages with the receiving address being the business department. In the message sending business processing, the to-be-sent messages submitted by the multiple business terminals of the multiple business departments through the browser are added to a to-be-sent message processing queue (to-be-sent message processing queue), the messages in the to-be-sent message processing queue are distributed according to the telegraph addresses, and are respectively pushed to an AFTN message to-be-sent queue or a SITA message to-be-sent queue. Similar to the message receiving process, the messages can also be sent out by interfacing with the AFTN message terminal and the SITA message terminal. In this way, the message sending and receiving mechanism based on the B / S architecture can meet the message sending and receiving requirements of the multiple business departments by interfacing with the existing AFTN message terminal and SITA message terminal, without the need to install the special AFTN message terminal or SITA message terminal for each business department. Instead, the message receiving can be implemented by using the general terminal device (for example, a computer), the cost of the general terminal device is greatly reduced compared with the cost of the AFTN message terminal or SITA message terminal, the related special line network does not need to be laid, the implementation difficulty is reduced, the implementation period is shortened, the operation cost is significantly reduced, and the compatibility and universality are higher. BRIEF DESCRIPTION OF DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the present application or the prior art, the following will briefly introduce the drawings needed in the embodiments or the prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without any creative effort.

[0020] Figure 1 FIG. 1 is a hardware system architecture schematic diagram of an aviation cargo message processing method provided in embodiments of the present application; Figure 2 FIG. 2 is a flow schematic diagram of an aviation cargo message processing method provided in embodiments of the present application; Figure 3 is an interaction flowchart under a software system architecture in some embodiments of the air cargo message processing method provided by the embodiments of the present application; Figure 4 is another software system architecture schematic diagram of the air cargo message processing method provided by the embodiments of the present application; Figure 5 is a functional module architecture schematic diagram of an operable interface in some embodiments of the air cargo message processing method provided by the embodiments of the present application; Figure 6 is a software system architecture schematic diagram of the air cargo message processing system provided by the embodiments of the present application; Figure 7 is a structural schematic diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0021] In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be described clearly and completely below with reference to the drawings in the present application. Obviously, the described embodiments are some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0022] In the air cargo transportation application scenario, the air cargo enterprises interact with each other through Type B telegrams, for example, the airport ground agent and the airline will send air master waybill messages, air sub-waybill messages, waybill status messages, air cargo and mail manifest messages, etc., and the airport ground agent and the airport ground agent will send air cargo and mail manifest messages, abnormal inquiry and notification messages of goods, special goods notification messages, etc. The airport ground agent, the airline and other air transportation enterprises generally receive and send domestic telegrams through the domestic air traffic control AFTN message network and international telegrams through the international SITA message network. The reception and transmission of AFTN messages or SITA messages need to use the terminal provided by the AFTN message network or the terminal provided by the SITA message network.

[0023] Currently, the message terminals provided by these message networks are independently deployed terminal programs, which can only run on a server or a PC computer, and the device is connected to the message network through a dedicated line. Due to business needs, airports and airlines generally have multiple business positions that need to send and receive telegrams. In order to realize the sending and receiving of telegrams by multiple business departments, multiple message terminals are often configured for multiple business departments, and a dedicated line network is laid for each message terminal to meet the needs of all business departments to send and receive telegrams. This not only increases the operating cost, but also greatly increases the implementation period, and has poor compatibility and universality. If there are new business departments or existing business departments that need to increase the telegram sending and receiving business, facing new needs, new terminals need to be reconfigured and the corresponding dedicated line network needs to be laid, which has a long implementation period and is difficult to implement.

[0024] In addition, the AFTN message terminal or the SITA message terminal supports manual telegram sending, but the function of manual telegram sending is relatively single and cannot meet the diversified and personalized needs of users to send and receive telegrams.

[0025] Therefore, the embodiments of the present application provide an air cargo message processing method and system, an electronic device and a program product, which are deployed and implemented by using a B / S architecture to realize the connection with multiple message terminals and realize the sending and receiving of telegrams by multiple business departments, and have strong flexibility and expansibility, can freely cope with the business development needs of users, reduce the operating cost of air cargo enterprises, and improve the efficiency of telegram sending and receiving.

[0026] It should be noted that the technical solutions provided by the embodiments of the present application can be applied to multiple messages, and are not limited to AFTN messages and SITA messages. In the following description, AFTN messages and SITA messages and AFTN message terminals and SITA message terminals are taken as examples for description.

[0027] The B / S architecture used in the embodiments of the present application can be connected with different message terminals, and the core function of message sending and receiving processing is concentrated on the server. The client (business terminal) only needs to install a browser, and the user can access the server through the browser to realize the sending and receiving of multiple messages.

[0028] As shown in Figure 1 , the air cargo message processing method provided by the embodiments of the present application can be executed based on the hardware system architecture shown in Figure 1 . On the user side, a plurality of business terminals are deployed, for example, as shown in Figure 1The diagram shows service terminals B01, B02, B03, and B04. On the service side, a web server S01 is deployed. Multiple service terminals can interact with the web server S01 via a local area network or the internet. The web server S01 can be configured with an interface layer, which can connect to different message terminals. For example, the interface layer can connect to at least SITA message terminals and AFTN message terminals.

[0029] A SITA message terminal is a terminal deployed on a SITA message network specifically for sending and receiving SITA messages. An AFTN message terminal is a terminal deployed on an AFTN message network specifically for sending and receiving AFTN messages.

[0030] Figure 2 This is one of the flowcharts illustrating an air cargo message processing method provided in an embodiment of this application. (Refer to...) Figure 2 This application provides an air cargo message processing method, which may include: Step 101: Connect with at least two types of message terminals to obtain at least two types of messages, and add the obtained at least two types of messages to the message receiving queue.

[0031] For example, at least two types of message terminals, including an AFTN message terminal and a SITA message terminal, are connected to the AFTN message terminal and the SITA message terminal respectively to obtain AFTN messages and SITA messages, and the two types of messages obtained are added to the message waiting queue respectively.

[0032] For example, at least two types of message terminals include AFTN message terminals and SITA message terminals. In step 101, the system interfaces with AFTN message terminals and SITA message terminals respectively to obtain AFTN messages and SITA messages respectively, and then adds the two types of messages to the message receiving queue.

[0033] From a technical implementation perspective, different message terminals have different technical characteristics. For AFTN message terminals, it is necessary to use either a serial port or a software development kit (SDK) to interface with the AFTN message terminal in order to obtain AFTN messages. Serial port interface means that data transmission between the server's interface layer and the AFTN message terminal is achieved through a serial interface, using a bit-by-bit transmission method, and connecting to the AFTN message terminal through a physical interface.

[0034] For SITA message terminals, it is necessary to connect to the SITA message terminal via SDK to obtain SITA messages.

[0035] Step 102: Read and parse the messages in the message waiting queue to obtain the message keywords, and store the messages in the message waiting queue into the message receiving table according to the message keywords.

[0036] In some embodiments, message keywords include one or more of the following: sending address, priority, receiving address, sending date and time group, message type, message version, or message content.

[0037] The sending address is the address of the message sender. Classifying messages based on the sending address can yield multiple groups of messages corresponding to different senders. Using the sending address as a key can help users maintain and manage the senders.

[0038] Priority indicates information such as the importance or category of a message. Classifying messages according to priority allows for different processing methods to be applied to messages with different priorities. For example, high-priority messages can be responded to first in response to query requests submitted by users through their browsers.

[0039] The receiving address is the address of the recipient. Different business departments correspond to different receiving addresses. By classifying messages according to their receiving addresses, it's possible to distinguish which business department a different received message belongs to. This ensures that only the current business department has query permissions for messages whose receiving address is the current business department, thus rejecting query requests from other business departments. In this way, the sending and receiving of messages by different business departments are isolated and do not interfere with each other, which is beneficial for data security and management.

[0040] The sending date and time group allows users to categorize messages based on either the day or hour of their sending time. This means supporting message classification and management according to different time levels such as "day" and "hour." For example, grouping by "day" allows users to query all messages received within a day, while grouping by "hour" allows users to query all messages received within an hour.

[0041] Message type refers to multiple types under one message, such as Freight Flight Manifest (FFM) message, Freight Air Waybill (FWB) message, Freight Consolidation List (FWB) message, etc.

[0042] Message version refers to a version of a message format. Some messages have multiple versions. The message version is the version information of the message currently in use, such as the version information of an FFM message or an FWB message.

[0043] The message content refers to the specific content of the message.

[0044] Step 103: In response to query requests submitted by multiple business terminals through browsers, the corresponding message is retrieved from the message receiving table based on the message keyword and fed back to the business terminal.

[0045] For example, Figure 1 The business terminals B01-B04 shown can be business terminals of four different business departments. Each business terminal can have a browser application installed. Users can submit query requests through the browser. The web server is equipped with a message processing layer. After receiving the query request, the message processing layer in the web server can identify whether the user of the current requesting business department has query permission for the message it requests based on the receiving address. If the receiving address of the message does not belong to that business department, the query request is rejected, and query permission is only granted to the business department whose receiving address matches.

[0046] Specifically, for example, the first business department is defined as any one of multiple business departments, and the second business department is any business department different from the first business department. In response to a query request submitted by at least one business terminal corresponding to the first business department through a browser, the system retrieves the corresponding message (a message in the queue awaiting reception) from the message reception table based on the receiving address and sends it back to the business terminal. In response to a query request submitted by at least one business terminal corresponding to the second business department through a browser, if no message (a message in the queue awaiting reception) corresponding to the second business department is found in the message reception table, the system either rejects the second business department's query request or returns a query result indicating that no message awaiting reception exists. Similarly, if the query request sent by the second business department points to a message awaiting reception from another business department, the system either rejects the query request or returns a query result indicating that the system does not have query permissions for that message.

[0047] For example, business terminal B01 and business terminal B02 belong to different business departments. Business terminal B01 requests a query for messages belonging to its first business department. The server can check the message reception table to see if there are any messages to be received belonging to the first business department. If so, the server responds to the query request and sends the message back to business terminal B01. If business terminal B02 requests a query for messages corresponding to business terminal B01, the server rejects the query request.

[0048] It should be noted that in some embodiments, multiple business departments can configure multiple business terminals, or multiple business departments can configure a single business terminal. In the embodiment where multiple business departments configure a single business terminal, different business departments can configure different user passwords and other identity information to distinguish between them. The server needs to query the corresponding messages based on the business department's identity information and determine whether it has query permissions for the categorized messages. In this way, the message sending and receiving needs of multiple different business departments can be met through only one business terminal.

[0049] In other embodiments, each business unit can be configured with at least one business terminal, meaning a business unit can be configured with multiple business terminals, depending on operating costs. In this application scenario, when classifying and storing messages in the message receiving table using the receiving address as the message keyword, the classification is based on the business unit, not the business terminal. This requires different business terminals within the same business unit to have the same receiving address.

[0050] It should be noted that in the embodiments of this application, the business terminal can also be called a terminal device, that is, a terminal device configured for the business department. For example, it can be a physical portable terminal device such as a computer, smartphone, or ruggedized tablet, or it can be a virtual client, such as a virtual machine.

[0051] Steps 101-103 implement message reception. Steps 104-106 implement message transmission.

[0052] Step 104: In response to receiving at least two types of messages to be sent submitted by multiple service terminals through a browser, add the messages to be sent to the message processing queue.

[0053] For example, in response to receiving AFTN or SITA messages submitted by multiple service terminals B01-B04 through a browser, the AFTN message is sent to the AFTN message waiting queue, and the SITA message is sent to the SITA message waiting queue.

[0054] Step 105: Based on the telegraph address of each message to be sent in the message processing queue, push the messages to be sent to the respective sending queues of at least two types of messages.

[0055] Specifically, features can be extracted from the telegraph addresses (i.e., receiving addresses) of different types of messages to obtain the address attributes corresponding to each type of message. Based on the address attributes, different messages can be distributed to different queues to be sent.

[0056] For example, assuming the address attribute corresponding to an AFTN message is the first attribute and the address attribute corresponding to a SITA message is the second attribute, then if the address attribute of the telegraph address of each message to be sent in the message processing queue is identified as the first attribute, the message to be sent is pushed to the AFTN message sending queue. If the address attribute of the telegraph address of each message to be sent in the message processing queue is identified as the second attribute, the message to be sent is pushed to the SITA message sending queue respectively. The aforementioned first or second attribute can be a common feature extracted from the receiving addresses of multiple AFTN or SITA messages.

[0057] Step 106: Read the message to be sent from the queue to be sent and send it to the corresponding message terminal.

[0058] For example, a message to be sent can be read from the AFTN message queue and sent to the AFTN message terminal, or a message to be sent can be read from the SITA queue and sent to the SITA message terminal.

[0059] Step 106 also requires sending messages by connecting with the AFTN message terminal or SITA message terminal. For the connection method, please refer to step 101 above, which will not be repeated here.

[0060] Optionally, after adding the message to be sent to the message processing queue, and before pushing the message to be sent to the respective message processing queues of at least two types of messages, the sending status of each message in the message processing queue can be set to pending sending.

[0061] After reading the message to be sent from the queue and sending it to the corresponding message terminal, the sending status of the corresponding message is changed to "sending completed" in response to successful sending.

[0062] It should be noted that a corresponding operable interface, i.e., an interactive interface, can be configured on the business terminal. The interactive interface can be a graphical interface. The interactive interface can include multiple controls for managing and controlling message sending and receiving.

[0063] like Figure 3 As shown, Figure 3 This paper illustrates a feasible software system architecture corresponding to the air cargo message processing method proposed in the embodiments of this application. The following section combines... Figure 3 The software system architecture shown will be further illustrated with examples.

[0064] like Figure 3 As shown, the software system architecture can include an interface layer, a message processing layer, and a presentation layer. Figure 1Correspondingly, the message processing layer and interface layer can be implemented based on a server (such as a web server) or a server cluster, and the presentation layer can be implemented based on a business terminal.

[0065] For example, during the message receiving phase, the interface layer interfaces with the AFTN terminal via serial port or SDK, and with the SITA message terminal via SDK, receiving messages into the message receiving queue. For instance, the interface layer includes, for example,... Figure 3 The module shown is used to interface with the air traffic control AFTN terminal. By interfacing with the AFTN terminal (or AFTN message terminal), it writes the received AFTN messages into the AFTN receive queue. Figure 3 The Incoming Queue_AFTN shown represents the AFTN receive queue, and the Incoming Queue represents the receive queue. The interface layer also includes, for example,... Figure 3 The module shown is used to interface with a SITA message terminal (or SITA message terminal) and write the received SITA messages into the SITA receive queue. Figure 3 The Incoming Queue_SITA shown here represents the SITA receive queue.

[0066] At the message processing layer, pre-installed dedicated programs can be used to read and parse the messages to be received in the message processing queue, extracting message keywords. For example, as mentioned before, message keywords can include sending address, priority, receiving address, sending date and time group, message type, message version, message content, etc. The messages to be received in the message processing queue can be classified according to message keywords and then stored in the message receiving table of the database.

[0067] The message processing layer can also provide a query interface for receiving message query requests. This interface receives query requests (queries for received messages) submitted by users from different business departments through their business terminals. In response to these requests, which can include message keywords, the message processing layer can retrieve the corresponding message to be received from the message receiving table based on the message keywords. The message processing layer can also provide a print interface for receiving automatic message printing requests. This interface receives print requests, also known as print archive requests, submitted by users from different business departments through their business terminals. Similarly, these print requests can also include message keywords. The message processing layer can retrieve the corresponding message through the query interface and return it to the business terminal, enabling the business terminal to perform printing or archiving operations.

[0068] At the presentation layer, various business departments can access the server through a browser. For example, an air cargo message terminal website can be operated based on this server. Each business department can only view the messages received by the message address belonging to its own department, thus achieving message data isolation between departments.

[0069] In this way, multiple business units can receive messages from the AFTN and SITA networks through a single business terminal, without needing to pay attention to the details of the message source.

[0070] During the message sending phase, each business department can respond to the received message through the browser and generate a response message as a message to be sent, or generate a new message to be sent. The message to be sent enters the outgoing message processing queue.

[0071] Next, the message processing layer determines the corresponding sending network (i.e., determines the message terminal) based on the address attribute of the telegraph address of each message to be sent, automatically pushes the message to be sent to the waiting queue of the corresponding message network, and sets the message sending status to be sent.

[0072] For example, suppose there are two messages to be sent, with telegraph addresses DOM0001 and INT0001 respectively. The message processing layer identifies DOM0001 as the receiving address under the AFTN message format based on the different address attributes corresponding to different message networks. Then, the message to DOM0001 can be pushed to the outgoing queue_AFTN corresponding to the domestic AFTN message network. The message to INT0001 is identified as the receiving address under the SITA message format and is pushed to the outgoing queue_SITA corresponding to the international SITA message network.

[0073] Next, at the interface layer, the AFTN queue program reads the messages to be sent from the Outgoing Queue_AFTN queue, connects to it, and sends them to the air traffic control AFTN message terminal. After successful transmission, it changes the message transmission status to "complete." OutgoingQueue_AFTN represents the queue of AFTN messages to be sent. The SITA queue program reads the messages to be sent from the Outgoing Queue_SITA queue, connects to it, and sends them to the SITA message terminal. After successful transmission, it changes the message transmission status to "complete." OutgoingQueue_SITA represents the queue of SITA messages to be sent. The AFTN queue program or SITA queue program is the software code used to implement the writing, sorting, and reading operations of each message in the Outgoing Queue_AFTN queue or Outgoing Queue_SITA queue. This part of the software code can be encapsulated as an independent program or module.

[0074] like Figure 4 As shown, Figure 4 This is another example of a software system architecture corresponding to the air cargo message processing method proposed in the embodiments of this application.

[0075] Based on the above examples, the interface layer is used to interface with AFTN message terminals, SITA message terminals or other systems to receive messages from various telegraph networks and place them into a waiting queue (received message waiting queue), and at the same time read messages from the sent message waiting queue and send them to various message terminals or systems.

[0076] Optionally, the queues in the interface layer, such as the Outgoing Queue_AFTN or Outgoing Queue_SITA, can adopt a master-slave architecture using Rocket MQ (Rocket Message Queue). This architecture can meet the requirements of high throughput and low latency in message processing, while supporting seamless integration with heterogeneous systems. Messages are persistently saved to disk to ensure that message data is not lost. Rocket MQ represents an open-source distributed message middleware and data processing platform, which can be composed of three parts: Producer, Broker, and Consumer. The Producer is responsible for producing messages, the Consumer is responsible for consuming messages, and the Broker is responsible for storing messages.

[0077] like Figure 4 As shown, the interface layer may include an AFTN message sending program, a SITA message sending program, an AFTN message sending and receiving program, and a SITA message receiving program, and each program can be encapsulated as a module.

[0078] The message processing layer is the core business logic processing unit. On one hand, it receives messages from the message waiting queue, parses the messages, and stores them in the received message table. This received message table can be stored in a database, for example, in [a database / system]. Figure 4 The data storage layer shown contains a database. This data storage layer can also deploy a Redis cluster; Redis is a remote dictionary server. The message processing layer can also push notification messages to clients (clients running on business terminals), send automatic message printing requests, and push messages to third-party systems. For example... Figure 4 As shown, the message processing layer may include a message sending program and a message parsing program, as well as deploying at least one website in the message processing layer.

[0079] On the other hand, the message processing layer retrieves messages from the outgoing message queue, parses the message receiving address, analyzes the receiving telegram network, and splits or distributes a message to its respective target queue based on the message network. For example, it analyzes whether the receiving telegram network is an AFTN message network or a SITA message network, and then splits or distributes the message to be sent to the AFTN message queue (Outgoing Queue_AFTN queue) or the SITA message queue (Outgoing Queue_SITA queue) based on the receiving address.

[0080] in, Figure 4 In the message processing layer, IIS+ASP.Net represents a combination of server-side technologies used to build dynamic web applications. IIS (Internet Information Services) represents web server software, and ASP (Active Server Pages) .Net represents a development framework used to build web applications, web APIs, and dynamic websites.

[0081] The presentation layer is used to enable interaction with users through an interactive interface or operation interface. For example, the presentation layer can provide a graphical operation interface to the terminal (such as a business terminal) based on ASP.Net (Active Server Page .Net). Users, business departments or management departments can use various functional modules to query received messages, send messages, manage sending addresses, receiving addresses, address groups, message templates, etc.

[0082] For example, an example of operating a graphical user interface is as follows: Figure 5 As shown, Figure 5This application provides partial functional block diagrams of the graphical user interface provided in its embodiments. The system management module 501 provides users with functions such as department management, role management, user management, automatic printing configuration, and system logs. The address management module 502 provides users with functions such as sending address management, receiving address management, and receiving address group management. The sending management module 503 provides users with functions such as message sending, message template maintenance, telegram abbreviation maintenance, and abnormal message template maintenance. The message query management module 504 provides users with functions such as message sending and receiving query (receiving and sending message query), message processing log query, precise message query, and message translation.

[0083] It should be noted that, Figure 5 This illustration only shows the overall architecture of the user interface and is not intended to limit the specific implementation of the interface. Any user interface that can implement... Figure 5 The various interfaces, some or all, of the functional modules shown.

[0084] For example, Figure 5 The system management module 501 and other functional modules shown can be configured as function areas, each containing at least one control to perform its corresponding function. Specifically, the operation interface includes at least one of the system management module 501, address management module 502, message sending management module 503, or message query management module 504.

[0085] The system management module 501 may include one or more of the following controls: department management control, role management control, user management control, automatic print configuration control, and system log control. The department management control is used by users to set department management information, such as setting the department name and the corresponding terminal ID. The role management control is used by users to set role management information, such as assigning different roles to different terminals with different permissions. The user management control is used to set user permissions, such as granting administrators higher-level permissions and setting the permission scope for ordinary users. The automatic print configuration control is used to invoke the printer to perform printing operations in response to user print requests; for example, in response to user clicks or other actions on the control, a print settings interface may pop up, and in response to user confirmation commands, the corresponding printing operation may be executed. The system log control is used to record various system log information.

[0086] The address management module 502 may specifically include one or more of the following controls: a sending address management control, a receiving address management control, and a receiving address group management control. The sending address management control is used by the user to manage sending address information, such as recording the sending addresses of each received message and categorizing and saving the sending addresses. The receiving address management control is used by the user to manage receiving address information, such as recording the receiving addresses of each sent message. The receiving address group management control is used by the user to divide receiving addresses into different groups for easier management.

[0087] The message sending management module 503 may specifically include one or more of the following controls: message sending control, message template maintenance control, telegram abbreviation maintenance control, and abnormal message template maintenance control. The message sending control generates a sending command after detecting a user's touch action. The message template maintenance control maintains message templates, displays them, and generates corresponding messages based on user input. For example, the system can provide multiple pre-configured message templates, and users can select, add, or delete templates using the message template maintenance control. The telegram abbreviation maintenance control maintains and displays telegram abbreviations. For example, this control can display multiple commonly used telegram abbreviations, which users can click to automatically add to messages, improving message writing efficiency. The abnormal message template maintenance control maintains and displays abnormal message templates and generates corresponding messages based on user input. Here, the abnormal message template refers to the message template used in the air freight field for sending inquiries and feedback regarding abnormal cargo conditions.

[0088] The message query management module 504 includes one or more of the following controls: message sending / receiving query control, message processing log query control, message precise query control, and message translation control. The message sending / receiving query control is used to respond to a first query command submitted by the user to query received or sent messages. For example, the user can use this control to query all messages received or sent within a specified time period. The message processing log query control is used to respond to a second query command submitted by the user to query the message processing log. The message processing log is a log recorded by the operating system for processing each message. This log can be queried from a specified folder based on a specified file storage path. The message precise query control is used to respond to a third query command submitted by the user to query messages that precisely match the user's input query conditions. For example, the user needs to precisely query messages whose content contains specific text, or needs to query messages corresponding to a specific receiving or sending address. The message translation control is used to respond to user-submitted translation instructions, translate Chinese messages, and display the translated telegraphic code, such as translating Chinese into four-digit telegraphic code.

[0089] Refer again Figure 4 The software system architecture can also include a data storage layer. This layer uses a relational database to store system configuration data, user configuration data, and historical data of received and sent messages. It uses a Remote Dictionary Server (Redis) cluster to cache user configuration data, message address attributes, and received message cache data, improving system processing efficiency. The Redis cluster achieves high availability, data sharding, and load balancing by connecting multiple Redis nodes. It allows Redis to provide services simultaneously on different nodes, improving overall performance and reliability.

[0090] In summary, the solution proposed in this application, by interfacing with multiple message networks such as the AFTN network and the SITA telegraph network and parsing at least two telegraph network protocols, enables the reception and transmission of domestic and international messages. Through B / S architecture deployment, air cargo companies only need to use one application to meet the international and domestic message sending and receiving needs of multiple business departments, without the need to configure multiple dedicated message terminals for multiple business departments or lay dedicated network lines.

[0091] In addition, by mapping users to sending addresses, the system achieves data isolation between the sending and receiving of messages by various business departments, thus preventing data pollution and confusion. The system automatically distributes messages to their respective telegram networks by configuring the address attributes of the receiving telegram address, achieving one-point access and multi-network integration.

[0092] As can be seen, the technical solution proposed in this application can flexibly connect to various domestic and international telegraph networks, providing a unified technical solution for air cargo companies. Customers no longer need to deploy multiple message terminals, saving on terminal purchase and leased network costs. Furthermore, due to the B / S architecture deployment, users can expand their user base without limitation within the same local area network, responding to new message sending and receiving needs at zero cost, offering greater scalability and reduced operating costs. In addition, this application provides a unified graphical user interface, which is more intuitive and convenient to operate. It can be used on common terminal devices such as computers, reducing the training costs for employees to learn professional message terminal operation skills. Users can easily get started without needing to worry about the telegraph network behind message sending and receiving; they only need to focus on business processing, greatly improving message business processing efficiency.

[0093] The air cargo message processing system provided in the embodiments of this application is described below. The air cargo message processing system described below can be referred to in correspondence with the air cargo message processing method described above.

[0094] This application provides an air cargo message processing system. The corresponding product for this system can be an electronic device deployed on the server side to implement the corresponding functions, such as a server or server cluster. Figure 6 As shown, the system may consist of only an interface layer and a message processing layer.

[0095] The interface layer is used to interface with at least two types of message terminals to obtain at least two types of messages; and to add the obtained at least two types of messages to the received message processing queue. For example, it interfaces with at least AFTN message terminals and SITA message terminals to obtain AFTN messages and SITA messages.

[0096] The interface layer is also used to read messages to be sent from the queue and send them to the corresponding message terminal.

[0097] like Figure 6 As shown, the message processing layer includes a parsing module 601, a query module 602, a caching module 603, and a traffic splitting module 604.

[0098] The parsing module 601 is used to read and parse the messages in the message waiting queue, obtain the message keywords, and store the messages in the message waiting queue into the message receiving table according to the message keywords.

[0099] The query module 602 is used to respond to query requests submitted by multiple business terminals through a browser, and retrieve the corresponding message from the message receiving table based on the keyword and send it back to the business terminal; the multiple business terminals are deployed in multiple business departments.

[0100] The caching module 603 is used to add the messages to be sent to the message waiting queue in response to receiving messages to be sent submitted by multiple business terminals through the browser.

[0101] The splitting module 604 is used to push the messages to be sent to the respective sending queues of at least two types of messages according to the telegraph address of each message to be sent in the message processing queue.

[0102] The system described above may also include a presentation layer. Unlike the message processing layer and the interface layer, the presentation layer is typically deployed on the user side. The presentation layer can be implemented based on at least one business terminal.

[0103] The business terminal is used to display the operation interface, which can be a graphical user interface. See details below. Figure 5 The examples shown and their corresponding textual descriptions are not repeated here.

[0104] Figure 7 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 7As shown, the electronic device may include: a processor 710, a communication interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communication interface 720, and the memory 730 communicate with each other via the communication bus 740. The processor 710 can call a computer program in the memory 730 to execute the steps of an air cargo message processing method, such as including: The system interfaces with at least two types of message terminals to obtain at least two types of messages; adds the obtained at least two types of messages to the received message processing queue; parses the messages in the received message processing queue to obtain message keywords; categorizes and stores the messages in the received message processing queue according to the message keywords into a message receiving table; responds to query requests submitted by multiple business terminals through browsers, retrieves the corresponding message from the message receiving table according to the message keywords, and feeds it back to the business terminal; multiple business terminals are deployed in multiple business departments; responds to receiving at least two types of messages to be sent submitted by multiple business terminals through browsers, adds the messages to be sent to the sent message processing queue; pushes the messages to be sent to the respective sent queues of at least two types of messages according to the telegraph address of each message to be sent in the sent message processing queue; reads the messages to be sent from the sent queues and sends them to the corresponding message terminals.

[0105] Furthermore, the logical instructions in the aforementioned memory 730 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0106] On the other hand, embodiments of this application also provide a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the air cargo message processing method provided in the above embodiments, such as including: The system interfaces with at least two types of message terminals to obtain at least two types of messages; adds the obtained at least two types of messages to the received message processing queue; parses the messages in the received message processing queue to obtain message keywords; categorizes and stores the messages in the received message processing queue according to the message keywords into a message receiving table; responds to query requests submitted by multiple business terminals through browsers, retrieves the corresponding message from the message receiving table according to the message keywords, and feeds it back to the business terminal; multiple business terminals are deployed in multiple business departments; responds to receiving at least two types of messages to be sent submitted by multiple business terminals through browsers, adds the messages to be sent to the sent message processing queue; pushes the messages to be sent to the respective sent queues of at least two types of messages according to the telegraph address of each message to be sent in the sent message processing queue; reads the messages to be sent from the sent queues and sends them to the corresponding message terminals.

[0107] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to perform the steps of the methods provided in the above embodiments, such as including: The system interfaces with at least two types of message terminals to obtain at least two types of messages; adds the obtained at least two types of messages to the received message processing queue; parses the messages in the received message processing queue to obtain message keywords; categorizes and stores the messages in the received message processing queue according to the message keywords into a message receiving table; responds to query requests submitted by multiple business terminals through browsers, retrieves the corresponding message from the message receiving table according to the message keywords, and feeds it back to the business terminal; multiple business terminals are deployed in multiple business departments; responds to receiving at least two types of messages to be sent submitted by multiple business terminals through browsers, adds the messages to be sent to the sent message processing queue; pushes the messages to be sent to the respective sent queues of at least two types of messages according to the telegraph address of each message to be sent in the sent message processing queue; reads the messages to be sent from the sent queues and sends them to the corresponding message terminals.

[0108] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0109] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0111] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for processing air cargo messages, characterized in that, The method includes: Interact with at least two message terminals to obtain at least two types of messages; add the obtained at least two types of messages to the message receiving queue. Parse the messages in the message waiting queue to obtain message keywords; classify and store the messages in the message waiting queue according to the message keywords into the message receiving table; In response to query requests submitted by multiple business terminals through a browser, the system retrieves the corresponding message from the message receiving table based on the message keyword and sends it back to the business terminal; the multiple business terminals are deployed in multiple business departments. In response to receiving at least two types of messages to be sent submitted by the plurality of service terminals through a browser, the messages to be sent are added to the message processing queue. Based on the telegraph address of each message to be sent in the message processing queue, the messages to be sent are pushed to the respective message queues of the at least two types of messages to be sent. Read the message to be sent from the queue to be sent and send it to the corresponding message terminal.

2. The method according to claim 1, characterized in that, The at least two types of messaging terminals include AFTN messaging terminals and SITA messaging terminals. Interact with at least two message terminals to obtain at least two types of messages, including: The AFTN message terminal is connected via serial port or software development kit (SDK) to obtain AFTN messages. And / or, SITA messages are obtained by connecting to the SITA message terminal via SDK.

3. The method according to claim 1, characterized in that, The message keywords include the receiving address. Different business departments correspond to different receiving addresses. Each of the multiple business departments only has the authority to query messages for the receiving address corresponding to its own business department. The messages are categorized and stored in the message receiving table according to their keywords, including: The messages are categorized and stored in the message receiving table according to the business department corresponding to the receiving address; In response to query requests submitted by multiple service terminals through a browser, the system retrieves the corresponding message from the message receiving table based on the message keyword and sends it back to the service terminal, including: In response to a query request submitted by at least one business terminal corresponding to the first business department through a browser, the message corresponding to the first business department is retrieved from the message receiving table based on the receiving address and fed back to the business terminal.

4. The method according to claim 1, characterized in that, Based on the telegraph address of each message to be sent in the message processing queue, the messages to be sent are pushed to the respective sending queues of the at least two types of messages, including: The message to be sent is pushed to the AFTN message waiting queue based on the address attribute of the telegraph address of each message to be sent in the message waiting queue as the first attribute; the first attribute is the address attribute corresponding to the AFTN message. The addresses of the telegraph addresses of each message to be sent in the message processing queue are used as the second attribute, and the messages to be sent are pushed to the SITA message sending queue respectively; the second attribute is the address attribute corresponding to the SITA message. Reading messages to be sent from the queue to be sent and sending them to the corresponding message terminal includes: Read the messages to be sent from the AFTN message queue and send them to the AFTN message terminal; Read the message to be sent from the SITA message queue and send it to the SITA message terminal.

5. The method according to claim 4, characterized in that, After adding the message to be sent to the message processing queue, the method further includes pushing the message to be sent to the queues corresponding to the at least two types of messages to be sent, respectively. Set the sending status of each message in the message waiting queue to be sent to "pending sending"; After reading the message to be sent from the queue to be sent and sending it to the corresponding message terminal, the method further includes: In response to successful transmission, the transmission status of the corresponding message is changed to "transmission completed".

6. The method according to any one of claims 1-5, characterized in that, The message keywords include one or more of the following: sending address, priority, receiving address, sending date and time group, message type, message version, or message content.

7. The method according to any one of claims 1-5, characterized in that, The method further includes: The operation interface is displayed through the business terminal; The operation interface includes at least one of the following: system management module, address management module, message sending management module, or message query management module; The system management module includes one or more of the following controls: Department management controls are used by users to set department management information; Role management controls are used by users to set role management information; User management controls are used to set user permissions; An automatic print configuration control is used to invoke the printer to perform the print operation in response to a user's print request; The system log control is used to record various system log information; The address management module includes one or more of the following controls: A sending address management control, used by users to manage sending address information; A receiving address management control, used by users to manage receiving address information; A receiving address group management control, used by users to divide receiving addresses into different groups; The message management module includes one or more of the following controls: The message sending control is used to generate a sending command after detecting the user's touch action; The message template maintenance control is used to maintain message templates, display message templates, and generate corresponding messages based on user input. The telegram short message maintenance control is used to maintain and display telegram short messages. An abnormal message template maintenance control is used to maintain abnormal message templates, display the abnormal message templates, and generate corresponding messages based on user input. The message query management module includes one or more of the following controls: The message sending and receiving query control is used to query received or sent messages in response to the first query command submitted by the user. The message processing log query control is used to query the message processing log in response to a second query command submitted by the user. The message precision query control is used to respond to a third query command submitted by the user and query messages that exactly match the query conditions entered by the user. The message translation control is used to translate Chinese messages in response to user-submitted translation instructions and display the translated telegraphic codes.

8. An air cargo message processing system, characterized in that, The system includes at least an interface layer and a message processing layer; The interface layer is used to interface with at least two types of message terminals to obtain at least two types of messages; and to add the obtained at least two types of messages to the message waiting queue. The message processing layer includes: The parsing module is used to read and parse the messages in the message waiting queue to obtain message keywords; and to classify and store the messages in the message waiting queue according to the message keywords into the message receiving table. The query module is used to respond to query requests submitted by multiple business terminals through a browser, and to retrieve the corresponding message from the message receiving table based on the keyword and send it back to the business terminal; the multiple business terminals are deployed in multiple business departments; The caching module is used to add the message to be sent to the message waiting queue in response to receiving the message to be sent submitted by the multiple service terminals through the browser. The splitting module is used to push the messages to be sent to their respective sending queues according to the telegraph address of each message to be sent in the message processing queue. The interface layer is also used to read messages to be sent from the queue to be sent and send them to the corresponding message terminal.

9. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the air cargo message processing method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the air cargo message processing method according to any one of claims 1 to 7.

Images