Method and device for subscribing flight event messages, electronic equipment and storage medium

Abstract

The invention provides a subscription method and device for flight event messages, electronic equipment and a storage medium. The method comprises the steps that message subscription conditions of all subscribing users, newly-added flight event data and flight event types corresponding to the newly-added flight event data are acquired; according to a message template corresponding to the flight event type, generating a newly-added flight event message from the newly-added flight event data; different flight event types correspond to different message templates; selecting a target subscription user from all the subscription users according to the message subscription condition of each subscription user, the newly added flight event data and the corresponding flight event type; and sending the newly added flight event message to the target subscription user. Through the mode of the invention, the flight event message can be accurately sent to the subscriber, the efficiency of checking the flight event related to the subscriber by the subscriber is improved, omission of the flight event related to the subscriber is avoided, and the operation and control efficiency of an airport is further improved.

Description

Technical Field

[0001] The present invention relates to the field of information processing technology, and in particular to a flight event message subscription method, device, electronic device and storage medium. Background Art

[0002] A flight event refers to a change in a certain data associated with a flight during the airport flight support process, such as a change in the aircraft type, boarding gate, or departure time. During the flight support process, airport staff need to pay close attention to flight events related to themselves so that they can carry out their work in a timely manner and ensure the normal operation of flights.

[0003] At present, all flight events are generally displayed through the flight data platform, and then users take the initiative to view the flight events related to themselves. However, with the increase in airport business volume, the number of flight events is also increasing. Users are less efficient in viewing flight events related to themselves, and often miss flight events related to themselves, thereby reducing the airport's operation control efficiency. Summary of the invention

[0004] In view of this, the purpose of this application is to provide a subscription method, device, electronic device and storage medium for flight event messages, which can accurately send flight event messages to subscribed users, improve the efficiency of subscribed users in viewing flight events related to themselves, avoid missing flight events related to subscribed users, and thereby improve the airport's operation control efficiency.

[0005] In a first aspect, an embodiment of the present application provides a method for subscribing to a flight event message, the method comprising:

[0006] Get the message subscription conditions, newly added flight event data, and the flight event type corresponding to the newly added flight event data of all subscribed users;

[0007] According to the message template corresponding to the flight event type, the new flight event data is generated into a new flight event message; different flight event types correspond to different message templates;

[0008] Select target subscribers from all subscribers based on the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type;

[0009] Send the new flight event message to the target subscribers.

[0010] In a possible implementation, the method further includes:

[0011] Send a message alignment request to the corresponding client of the target subscriber at a preset time interval, so that the corresponding client of the target subscriber initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous;

[0012] The sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in the order of sending time from the beginning to the end among all flight event messages sent to the corresponding client of the target subscription user;

[0013] Receive a message resending request sent by a client corresponding to a target subscription user, where the message resending request includes a resending sequence number;

[0014] The flight event message with the resending sequence number among the flight event messages corresponding to the target subscriber in the flight event message library is sent to the client corresponding to the target subscriber.

[0015] In a possible implementation, a message template corresponding to each flight event type is generated through the following steps:

[0016] In response to the flight event type to be generated input by the template generating user on the client, the flight attribute field corresponding to the flight event type to be generated is displayed to the client corresponding to the template generating user, so that the template generating user can select a target flight attribute field from the flight attribute field;

[0017] The target flight attribute field generates a message template corresponding to the flight event type to be generated.

[0018] In a possible implementation, according to a message template corresponding to the flight event type, generating a new flight event message from the new flight event data includes:

[0019] Replace each flight attribute field in the message template corresponding to the flight event type with the data corresponding to each flight attribute field in the newly added flight event data.

[0020] In a possible implementation, according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type, a target subscriber is selected from all subscribers, including:

[0021] For each subscribing user, determine whether the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the message subscription conditions of the subscribing user; each message subscription condition includes one or more message subscription condition items;

[0022] If the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the message subscription conditions of the subscriber, the subscriber is determined as the target subscriber.

[0023] In a possible implementation, after selecting a target subscriber from all subscribers, the method further includes:

[0024] The reminder level corresponding to the target subscriber is sent to the client corresponding to the target subscriber, so that the client corresponding to the target subscriber renders the new flight event message according to the reminder style corresponding to the reminder level and then issues a message reminder.

[0025] In a second aspect, an embodiment of the present application further provides a flight event message subscription device, the device comprising:

[0026] The acquisition module is used to obtain the message subscription conditions of all subscribed users, the newly added flight event data, and the flight event type corresponding to the newly added flight event data;

[0027] A generation module, used to generate a new flight event message from the new flight event data according to the message template corresponding to the flight event type; different flight event types correspond to different message templates;

[0028] The selection module is used to select target subscribers from all subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type;

[0029] The sending module is used to send the new flight event message to the target subscribed users.

[0030] In a possible implementation, the device further includes: a receiving module;

[0031] The sending module is further used to send a message alignment request to a client corresponding to a target subscriber at a preset time interval, so that the client corresponding to the target subscriber initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous;

[0032] The sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in the order of sending time from the beginning to the end among all flight event messages sent to the corresponding client of the target subscription user;

[0033] A receiving module, used for receiving a message resending request sent by a client corresponding to a target subscribed user, wherein the message resending request includes a resending sequence number;

[0034] The sending module is also used to send the flight event message with the resending sequence number among the flight event messages corresponding to the target subscribed user in the flight event message library to the client corresponding to the target subscribed user.

[0035] In a possible implementation, the generating module is further used for:

[0036] In response to the flight event type to be generated input by the template generating user on the client, the flight attribute field corresponding to the flight event type to be generated is displayed to the client corresponding to the template generating user, so that the template generating user can select a target flight attribute field from the flight attribute field;

[0037] The target flight attribute field generates a message template corresponding to the flight event type to be generated.

[0038] In a possible implementation, the generation module is specifically configured to replace each flight attribute field in the message template corresponding to the flight event type with data corresponding to each flight attribute field in the newly added flight event data.

[0039] In one possible implementation, the selection module is specifically used to determine, for each subscribing user, whether the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the subscribing user's message subscription conditions; each message subscription condition includes one or more message subscription condition items; if the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the subscribing user's message subscription conditions, the subscribing user is determined as a target subscribing user.

[0040] In a possible implementation, after selecting a target subscriber from all subscribers, the sending module is also used to send the reminder level corresponding to the target subscriber to the client corresponding to the target subscriber, so that the client corresponding to the target subscriber renders the new flight event message according to the reminder style corresponding to the reminder level and then issues a message reminder.

[0041] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to perform the steps of the flight event message subscription method as described in any one of the first aspects.

[0042] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the flight event message subscription method as described in any one of the first aspects are executed.

[0043] The embodiments of the present application provide a flight event message subscription method, device, electronic device and storage medium, the method comprising: obtaining message subscription conditions, newly added flight event data and flight event types corresponding to the newly added flight event data of all subscribed users; generating newly added flight event messages from the newly added flight event data according to the message template corresponding to the flight event type; different flight event types correspond to different message templates; selecting a target subscribed user from all subscribed users according to the message subscription conditions, newly added flight event data and the corresponding flight event type of each subscribed user; and sending the newly added flight event message to the target subscribed user. The present application accurately sends the newly added flight event message generated based on the message template to the target subscribed user selected based on the message subscription conditions, thereby improving the efficiency of subscribed users in viewing flight events related to themselves, avoiding missing flight events related to subscribed users, and thus improving the operation control efficiency of the airport. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 A flowchart of a flight event message subscription method provided by an embodiment of the present application is shown;

[0046] Figure 2 A flowchart showing another method for subscribing to flight event messages provided in an embodiment of the present application is shown;

[0047] Figure 3 A schematic diagram of the structure of a flight event message subscription device provided in an embodiment of the present application is shown;

[0048] Figure 4 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0049] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of order, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0050] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0051] In order to enable those skilled in the art to use the content of this application, the following implementation is provided in conjunction with a specific application scenario, the "field of information processing technology". For those skilled in the art, the general principles defined herein may be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application is mainly described around the "field of information processing technology", it should be understood that this is only an exemplary embodiment.

[0052] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0053] The following is a detailed description of a method for subscribing to flight event messages provided in an embodiment of the present application.

[0054] Reference Figure 1 As shown, it is a flowchart of a flight event message subscription method provided in an embodiment of the present application. The method is applied to the server. The specific execution process of the flight event message subscription method is as follows:

[0055] S101. Obtain message subscription conditions, newly added flight event data, and flight event types corresponding to the newly added flight event data of all subscribed users.

[0056] S102. Generate a new flight event message from the new flight event data according to a message template corresponding to the flight event type.

[0057] S103: Select a target subscriber from all subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type.

[0058] S104: Send the new flight event message to the target subscribed user.

[0059] An embodiment of the present application provides a method for subscribing to flight event messages, the method comprising: obtaining message subscription conditions, newly added flight event data, and flight event types corresponding to the newly added flight event data of all subscribed users; generating newly added flight event messages from the newly added flight event data according to a message template corresponding to the flight event type; different flight event types correspond to different message templates; selecting a target subscribed user from all subscribed users according to the message subscription conditions, newly added flight event data, and the corresponding flight event type of each subscribed user; and sending the newly added flight event message to the target subscribed user. The present application accurately sends the newly added flight event message generated based on the message template to the target subscribed user selected based on the message subscription conditions, thereby improving the efficiency of subscribed users in viewing flight events related to themselves, avoiding missing flight events related to subscribed users, and thereby improving the operation control efficiency of the airport.

[0060] The following is a description of the exemplary steps of the present application embodiment:

[0061] S101. Obtain message subscription conditions, newly added flight event data, and flight event types corresponding to the newly added flight event data of all subscribed users.

[0062] In the implementation manner of the present application, a unified event receiving interface is used to receive newly added flight event data from a business system or a data platform to implement access and storage of flight event data. Newly added flight event data refers to data that has not yet been sent to subscribed users. Each flight event type corresponds to one or more flight events; for example, flight events corresponding to flight event type A include changes in boarding gates and aircraft models, and flight events corresponding to flight event type A include changes in takeoff events; when the newly added flight event data is a change in aircraft model, the flight event type corresponding to the newly added flight event data is the first flight event type A. The specific number of flight event types and the corresponding flight events depend on actual conditions and are not limited here.

[0063] Furthermore, each subscriber has configured message subscription conditions in advance, which include one or more message subscription condition items; each message subscription condition item consists of three parts: flight attribute name or flight event type, operator and condition value. Among them, the flight attribute name can be the airline, terminal, aircraft type, aircraft position, boarding gate, baggage carousel, etc.; the operator is used to represent the specific rules for the flight event data subscribed by the subscriber, such as equal to, greater than, less than, contain, not contain, etc.

[0064] Here, the message subscription conditions are used to filter out the messages that the user is concerned about. The more detailed the message subscription conditions are, the more accurate the subscription is. In order to facilitate configuration and reduce performance consumption, subscription plans can be reused between subscribers, that is, multiple subscribers can reference the same message subscription conditions, or they can choose to customize their own message subscription conditions.

[0065] For example, the subscriber is shuttle bus driver A, whose job is to ensure domestic flights with parking spaces between 101 and 105, terminal T1, airlines Air China and Sichuan Airlines, and flight event type A. Then the subscription conditions for the subscriber include: Message subscription condition item 1: parking spaces (flight attribute name) contains (operator) 101, 102, 103, 104, 105 (condition value); Message subscription condition item 2: terminal (flight attribute name) contains (operator) T1 (condition value); Message subscription condition item 3: airline (flight attribute name) contains (operator) Air China, Sichuan Airlines (condition value); Message subscription condition item 4: flight event type (flight event type) contains (operator) flight event type A (condition value).

[0066] Furthermore, the message subscription conditions are configured through the following steps: in response to a condition configuration request initiated by a subscribing user in the condition configuration interface, all message subscription conditions in the message subscription condition database are displayed in the condition configuration interface, so that the subscribing user can select a message subscription condition from all the message subscription conditions or select a custom message subscription condition; if the subscribing user selects a message subscription condition from all the message subscription conditions, the subscribing user and the message subscription condition selected by the subscribing user are correspondingly stored in the message subscription condition database; if the subscribing user selects a custom message subscription condition, all flight attribute names, operators and condition values ​​are displayed in the condition configuration interface, so that the subscribing user can configure his own message subscription condition from all flight attribute names, operators and condition values; and the subscribing user and the message subscription condition configured by the subscribing user are correspondingly stored in the message subscription condition database.

[0067] The message subscription condition database stores the message subscription conditions of all subscribing users.

[0068] S102. Generate a new flight event message from the new flight event data according to a message template corresponding to the flight event type.

[0069] In the implementation manner of the present application, different flight event types correspond to different message templates; each flight event type corresponds to a specific and unique message template, which is used to convert the newly added flight event data into a newly added flight event message. Each message template consists of one or more flight attribute fields, and the position of each flight attribute field in the message template is fixed. Specifically, each flight attribute field in the message template corresponding to the flight event type is replaced with the data corresponding to each flight attribute field in the newly added flight event data.

[0070] Furthermore, the message template corresponding to each flight event type is generated through the following steps:

[0071] Step 1: In response to the flight event type to be generated input by the template generating user on the client, the flight attribute field corresponding to the flight event type to be generated is displayed to the client corresponding to the template generating user, so that the template generating user can select the target flight attribute field from the flight attribute field.

[0072] In the implementation manner of the present application, the types of flight events to be generated are different, and the corresponding flight attribute fields may be the same or different. The flight attribute fields include a flight number field, an estimated departure time field, an aircraft model field, and the like.

[0073] Step 2: Generate a message template corresponding to the flight event type to be generated by using the target flight attribute field.

[0074] In the implementation mode of the present application, an empty message template corresponding to the flight event type to be generated is created; the target flight attribute field is added to the corresponding position in the empty message template to obtain a message template corresponding to the flight event type to be generated. The position of the target flight attribute field in the message template is set by the template generation user.

[0075] Here, the target flight attribute field acts as a placeholder in the message template corresponding to the flight event type to be generated, so that when generating a new flight event message, the new flight event data is used to replace the flight attribute fields in the message text, ensuring the accuracy and timeliness of the message, providing a customized user experience, and enhancing the efficiency and flexibility of processing a large amount of new flight event data.

[0076] Furthermore, the present application can also respond to the message template identifier to be deleted input by the template field deleting user in the client, and display the flight attribute field in the message template corresponding to the message template identifier to be deleted to the client corresponding to the template generating user, so that the template field deleting user can select the flight attribute field to be deleted from the flight attribute field in the message template corresponding to the message template identifier to be deleted; and delete the flight attribute field to be deleted in the message template corresponding to the message template identifier to be deleted.

[0077] Furthermore, the present application can also respond to the flight event type to be added input by the template field adding user in the client, and display the flight attribute field corresponding to the flight event type to be added to the client corresponding to the template generating user, so that the template field adding user selects the flight attribute field to be added from the flight attribute field corresponding to the flight event type to be added; and adds the flight attribute field to be added in the message template corresponding to the flight event type to be added.

[0078] In addition, this application can also realize the message template viewing function.

[0079] S103: Select a target subscriber from all subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type.

[0080] In the present application method, for each subscribing user, it is determined whether the newly added flight event data and the corresponding flight event type meet all the message subscription condition items in the message subscription conditions of the subscribing user; each message subscription condition includes one or more message subscription condition items; if the newly added flight event data and the corresponding flight event type meet all the message subscription condition items in the message subscription conditions of the subscribing user, the subscribing user is determined as the target subscribing user.

[0081] If the newly added flight event data and the corresponding flight event type do not meet one or more message subscription conditions of the subscribing user, it is considered that the newly added flight event data and the corresponding flight event type do not meet the message subscription conditions of the subscribing user, that is, the newly added flight event message will not be sent to the subscribing user.

[0082] Here, through the implementation method of the present application, newly added flight event data can be accurately pushed to subscribed users in need, thereby improving the efficiency and accuracy of message screening and push, reducing the time and energy of subscribed users in handling invalid messages, and improving the practicality and reliability of the flight operation control system.

[0083] S104: Send the new flight event message to the target subscribed user.

[0084] In the implementation manner of the present application, a websocket long connection is used to send the new flight event message to the target subscribed users.

[0085] Among them, WebSocket long connection is a protocol for full-duplex communication on a single TCP connection, which allows the server to actively push data to the client.

[0086] Furthermore, after selecting a target subscriber from all subscribers, the method also includes: sending a reminder level corresponding to the target subscriber to a client corresponding to the target subscriber, so that the client corresponding to the target subscriber renders the new flight event message according to a reminder style corresponding to the reminder level and then issues a message reminder.

[0087] In the implementation manner of the present application, different reminder levels correspond to different reminder styles, such as whether there is a sound reminder, the type of sound reminder, the text color corresponding to the new flight event message, whether there is a pop-up reminder, etc.

[0088] Furthermore, after selecting a target subscriber from all subscribers, the method also includes: adding one to the number of all flight event messages that have been sent to the target subscriber, and determining the serial number corresponding to the newly added flight event message; and storing the newly added flight event message corresponding to the target subscriber and the corresponding serial number in a flight event message library.

[0089] The sequence number corresponding to the newly added flight event message refers to the sequence number of the newly added flight event message arranged in descending order according to the sending time among all flight event messages sent to the client corresponding to the target subscription user.

[0090] Furthermore, the method also includes: sending a message alignment request to the corresponding client of the target subscription user at a preset time interval, so that the client corresponding to the target subscription user initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous; wherein the sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in order from front to back according to the sending time among all flight event messages sent to the corresponding client of the target subscription user; receiving a message resending request sent by the client corresponding to the target subscription user, the message resending request including the resending sequence number; and sending the flight event message with the sequence number being the resending sequence number among the flight event messages corresponding to the target subscription user in the flight event message library to the client corresponding to the target subscription user.

[0091] The flight event message library stores flight event messages corresponding to all subscribed users, and the sequence numbers of each flight event message are arranged in descending order according to the sending time among all flight event messages sent to the corresponding client of the subscribed user.

[0092] Here, the present application aligns all flight event messages received by the client corresponding to the target subscribed user at preset time intervals. If all flight event messages received by the client corresponding to the target subscribed user are not continuous, it means that the message is lost, and the flight event messages that have not been successfully received by the client corresponding to each subscribed user need to be resent to the client corresponding to each subscribed user to solve the problem of flight event message sending failure caused by network offline and other problems.

[0093] For example, after the client corresponding to subscribed user A receives the message alignment request, if the sequence numbers of the received flight event messages are 1, 2, 3, and 6 respectively, since the sequence numbers corresponding to all flight event messages received by the client corresponding to subscribed user A are not continuous and the flight event messages with sequence numbers 4 and 5 are missing, sequence numbers 4 and 5 are determined as the resending sequence numbers, and a message resending request is initiated to enable the server to resend the flight event messages with sequence numbers 4 and 5 in the flight event messages corresponding to each subscribed user in the flight event message library.

[0094] Furthermore, after the new flight event message is sent to the target subscriber, the subscription process of the new flight event message is completed in response to the receiving confirmation operation triggered by the target user on the corresponding client; if the receiving confirmation operation is not triggered by the target subscriber on the corresponding client within the first preset time period, the new flight event message is sent to the target subscriber again; if the receiving confirmation operation is not triggered by the target subscriber on the corresponding client within the second preset time period, a new flight event message reception failure warning is triggered; the second preset time period is greater than the first preset time period.

[0095] Here, the method of this application can prevent the loss of flight event messages and form a closed loop of the full subscription process.

[0096] like Figure 2 As shown, it is a flowchart of another method for subscribing to flight event messages provided in an embodiment of the present application. The method is applied to the server. The exemplary steps of the embodiment of the present application are described below:

[0097] S201. Send a message alignment request to a client corresponding to a target subscriber at a preset time interval, so that the client corresponding to the target subscriber initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous.

[0098] Here, the application aligns all flight event messages received by the client corresponding to the target subscribed user at a preset time interval. If all flight event messages received by the client corresponding to the target subscribed user are not continuous, it means that the message is lost, and a message resending request is initiated.

[0099] Among them, the sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in order from the front to the back according to the sending time among all flight event messages sent to the client corresponding to the target subscription user; the message resending request includes the resending sequence number.

[0100] For example, after the client corresponding to subscribed user A receives the message alignment request, if the sequence numbers of the received flight event messages are 1, 2, 3, and 6 respectively, since the sequence numbers of all flight event messages received by the client corresponding to subscribed user A are not continuous and the flight event messages with sequence numbers 4 and 5 are missing, sequence numbers 4 and 5 are determined as the resending sequence numbers.

[0101] S202: Receive a message resending request sent by a client corresponding to a target subscribed user, where the message resending request includes a resending sequence number.

[0102] S203: Send the flight event message with the resending sequence number among the flight event messages corresponding to the target subscribed user in the flight event message library to the client corresponding to the target subscribed user.

[0103] An embodiment of the present application provides another method for subscribing to flight event messages, which can avoid the problem of failure in sending flight event messages due to network disconnection, offline and other problems, and improve the orderliness and reliability of the messages.

[0104] Based on the same inventive concept, an embodiment of the present application also provides a flight event message subscription device corresponding to the flight event message subscription method. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned flight event message subscription method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0105] Reference Figure 3 FIG. 1 is a schematic diagram of a flight event message subscription device provided in an embodiment of the present application, the device comprising:

[0106] The acquisition module 301 is used to acquire the message subscription conditions of all subscribed users, the newly added flight event data, and the flight event type corresponding to the newly added flight event data;

[0107] A generating module 302 is used to generate a new flight event message from the new flight event data according to a message template corresponding to the flight event type; different flight event types correspond to different message templates;

[0108] The selection module 303 is used to select a target subscriber from all subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type;

[0109] The sending module 304 is used to send the newly added flight event message to the target subscribing user.

[0110] In a possible implementation, the device further includes: a receiving module 305;

[0111] The sending module 304 is further used to send a message alignment request to a client corresponding to the target subscriber at a preset time interval, so that the client corresponding to the target subscriber initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous;

[0112] The sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in the order of sending time from the beginning to the end among all flight event messages sent to the corresponding client of the target subscription user;

[0113] The receiving module 305 is used to receive a message resending request sent by a client corresponding to a target subscribed user, wherein the message resending request includes a resending sequence number;

[0114] The sending module 304 is further configured to send the flight event message with the resending sequence number among the flight event messages corresponding to the target subscribed user in the flight event message library to the client corresponding to the target subscribed user.

[0115] In a possible implementation, the generating module 302 is further configured to:

[0116] In response to the flight event type to be generated input by the template generating user on the client, the flight attribute field corresponding to the flight event type to be generated is displayed to the client corresponding to the template generating user, so that the template generating user can select a target flight attribute field from the flight attribute field;

[0117] The target flight attribute field generates a message template corresponding to the flight event type to be generated.

[0118] In a possible implementation, the generation module 302 is specifically configured to replace each flight attribute field in the message template corresponding to the flight event type with data corresponding to each flight attribute field in the newly added flight event data.

[0119] In one possible implementation, the selection module 303 is specifically used to determine, for each subscribing user, whether the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the subscribing user's message subscription conditions; each message subscription condition includes one or more message subscription condition items; if the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the subscribing user's message subscription conditions, the subscribing user is determined as a target subscribing user.

[0120] In a possible implementation, after selecting a target subscriber from all subscribers, the sending module 304 is further used to send the reminder level corresponding to the target subscriber to the client corresponding to the target subscriber, so that the client corresponding to the target subscriber renders the new flight event message according to the reminder style corresponding to the reminder level and then issues a message reminder.

[0121] The embodiment of the present application provides a flight event message subscription device, the method includes: an acquisition module 301, which is used to obtain the message subscription conditions, newly added flight event data, and the flight event type corresponding to the newly added flight event data of all subscribed users; a generation module 302, which is used to generate a newly added flight event message from the newly added flight event data according to the message template corresponding to the flight event type; different flight event types correspond to different message templates; a selection module 303, which is used to select a target subscribed user from all subscribed users according to the message subscription conditions, newly added flight event data and the corresponding flight event type of each subscribed user; a sending module 304, which is used to send the newly added flight event message to the target subscribed user. The present application accurately sends the newly added flight event message generated based on the message template to the target subscribed user screened based on the message subscription conditions, thereby improving the efficiency of the subscribed user in viewing the flight events related to themselves, avoiding missing flight events related to the subscribed user, and thus improving the operation control efficiency of the airport.

[0122] like Figure 4 As shown, an electronic device 400 provided in an embodiment of the present application includes: a processor 401, a memory 402 and a bus, the memory 402 stores machine-readable instructions executable by the processor 401, when the electronic device is running, the processor 401 and the memory 402 communicate through the bus, and the processor 401 executes the machine-readable instructions to perform the steps of the subscription method for flight event messages as described above.

[0123] Specifically, the memory 402 and the processor 401 can be general-purpose memories and processors, which are not specifically limited here. When the processor 401 runs the computer program stored in the memory 402, the subscription method for the flight event message can be executed.

[0124] Corresponding to the above-mentioned flight event message subscription method, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned flight event message subscription method are executed.

[0125] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0126] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0127] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0128] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the information processing method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0129] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for subscribing to flight event messages, characterized in that: The method comprises: Obtaining message subscription conditions, newly added flight event data, and flight event types corresponding to the newly added flight event data of all subscribed users; According to the message template corresponding to the flight event type, the newly added flight event data is used to generate a newly added flight event message; different flight event types correspond to different message templates; Selecting a target subscriber from all the subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type; The newly added flight event message is sent to the target subscribed user.

2. The flight event message subscription method according to claim 1, characterized in that: The method further comprises: Sending a message alignment request to the corresponding client of the target subscriber at a preset time interval, so that the client corresponding to the target subscriber initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous; The sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in the order of sending time from the beginning to the end among all flight event messages sent to the client corresponding to the target subscription user; Receiving a message resending request sent by a client corresponding to the target subscribed user, wherein the message resending request includes a resending sequence number; The flight event message having a sequence number being a resending sequence number among the flight event messages corresponding to the target subscribed user in the flight event message library is sent to the client corresponding to the target subscribed user.

3. The flight event message subscription method according to claim 1 or 2, characterized in that: Generate the message template corresponding to each flight event type through the following steps: In response to the flight event type to be generated input by the template generating user on the client, the flight attribute field corresponding to the flight event type to be generated is displayed on the client corresponding to the template generating user, so that the template generating user can select a target flight attribute field from the flight attribute field; The target flight attribute field is used to generate a message template corresponding to the flight event type to be generated.

4. The flight event message subscription method according to claim 3, characterized in that: The generating a new flight event message from the new flight event data according to the message template corresponding to the flight event type includes: Each flight attribute field in the message template corresponding to the flight event type is replaced with data corresponding to each flight attribute field in the newly added flight event data.

5. The flight event message subscription method according to claim 3, characterized in that: The selecting a target subscriber from all the subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type includes: For each subscribing user, determining whether the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the message subscription conditions of the subscribing user; each message subscription condition includes one or more message subscription condition items; If the newly added flight event data and the corresponding flight event type meet all message subscription condition items in the message subscription conditions of the subscriber, the subscriber is determined as a target subscriber.

6. The flight event message subscription method according to claim 1, characterized in that: After selecting a target subscriber from all the subscribers, the method further includes: The reminder level corresponding to the target subscribed user is sent to the client corresponding to the target subscribed user, so that the client corresponding to the target subscribed user renders the new flight event message according to the reminder style corresponding to the reminder level and then issues a message reminder.

7. A flight event message subscription device, characterized in that: The device comprises: An acquisition module, used to acquire message subscription conditions of all subscribed users, newly added flight event data, and flight event types corresponding to the newly added flight event data; A generating module, configured to generate a new flight event message from the new flight event data according to a message template corresponding to the flight event type; different flight event types correspond to different message templates; A selection module, configured to select a target subscriber from all the subscribers according to the message subscription conditions of each subscriber, the newly added flight event data and the corresponding flight event type; The sending module is used to send the newly added flight event message to the target subscribing user.

8. The flight event message subscription device according to claim 7, characterized in that: The device further comprises: a receiving module; The sending module is further used to send a message alignment request to the client corresponding to the target subscriber at a preset time interval, so that the client corresponding to the target subscriber initiates a message resending request when the sequence numbers corresponding to all received flight event messages are not continuous; The sequence number corresponding to each flight event message refers to the sequence number of each flight event message arranged in the order of sending time from the beginning to the end among all flight event messages sent to the client corresponding to the target subscription user; A receiving module, configured to receive a message resending request sent by a client corresponding to the target subscribed user, wherein the message resending request includes a resending sequence number; The sending module is further used to send the flight event message with the resending sequence number among the flight event messages corresponding to the target subscribed user in the flight event message library to the client corresponding to the target subscribed user.

9. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to perform the steps of the flight event message subscription method as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the flight event message subscription method according to any one of claims 1 to 6 are executed.

Images