CN111510440A - Data exchange method and system - Google Patents
Data exchange method and system Download PDFInfo
- Publication number
- CN111510440A CN111510440A CN202010263864.8A CN202010263864A CN111510440A CN 111510440 A CN111510440 A CN 111510440A CN 202010263864 A CN202010263864 A CN 202010263864A CN 111510440 A CN111510440 A CN 111510440A
- Authority
- CN
- China
- Prior art keywords
- data
- message
- uploaded
- message data
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
- H04L63/0245—Filtering by information in the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/083—Shipping
- G06Q10/0833—Tracking
Abstract
The invention provides a data exchange method and a system, wherein the method comprises the following steps: if the type of the data processing request sent by the user is a data reporting request, acquiring message data to be uploaded corresponding to the data reporting request; analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue; processing the analyzed message data to be uploaded in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue; if the type of the data processing request sent by the user is a data issuing request, acquiring issued message data requested by the data issuing request from a message queue; and feeding back the message data to be sent to the user. According to the scheme, the uploading or issuing of the message data is executed according to the type of the data processing request sent by the user, the sharing of the message data among different units is realized, and therefore the service quality and the service efficiency can be improved by using the luggage message data.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a data exchange method and a data exchange system.
Background
With the development of science and technology, more and more people choose to travel by plane. Passengers typically involve baggage consignment while riding in an airplane, resulting in corresponding baggage message data.
For the management of baggage message data, units such as airports, airlines, customs and the like are usually involved, but the baggage message data of different units are isolated from each other and cannot be shared with each other, so that the baggage message data cannot be utilized to improve the service quality and the service efficiency.
Disclosure of Invention
In view of this, embodiments of the present invention provide a data exchange method and system to solve the problem that the quality and efficiency of service cannot be improved by using baggage message data.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
the first aspect of the embodiments of the present invention discloses a data exchange method, which includes:
executing corresponding data exchange operation according to the type of the data processing request sent by the user;
if the type of the data processing request is a data reporting request, the data exchange operation includes:
acquiring message data to be uploaded corresponding to the data reporting request;
analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue;
processing the message data to be uploaded analyzed in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue;
if the type of the data processing request is a data issuing request, the data exchange operation comprises:
acquiring the message data requested by the data issuing request from the message queue;
and feeding back the message data to be issued to the user.
Preferably, the analyzing the message data to be uploaded and sending the analyzed message data to be uploaded to a middleware message queue includes:
analyzing the message data to be uploaded to obtain the data format and the data semantics of the message data to be uploaded;
based on a check rule, checking the data format and the data semantics of the message data to be uploaded;
if the data format and the data semantics of the message data to be uploaded do not pass the verification, feeding alarm information back to the user;
if the data format and the data semantics of the message data to be uploaded pass the verification, acquiring a queue message handle corresponding to the message data to be uploaded according to the data type of the message data to be uploaded;
and sending the message data to be uploaded to a middleware message queue corresponding to the queue message handle.
Preferably, the processing the message data to be uploaded after being analyzed in the middleware message queue based on the preset processing rule, and storing the processed message data to be uploaded to a database and a message queue includes:
extracting first message data to be uploaded in the middleware message queue one by one;
analyzing the message field of the first message data to be uploaded aiming at each first message data to be uploaded, and eliminating useless information of the first message data to be uploaded to obtain second message data to be uploaded;
assembling and packaging the second message data to be uploaded;
storing the second message data to be uploaded to a database;
and according to the message type of each second message data to be uploaded, distributing the assembled and packaged second message data to be uploaded to a message queue corresponding to the message type.
Preferably, the obtaining of the to-be-delivered message data requested by the data delivery request from the message queue includes:
extracting each message data in the message queue;
pre-analyzing the extracted message data to obtain data information corresponding to the message data;
acquiring a user matching rule corresponding to the data issuing request;
and acquiring the message data of which the data information is matched with the user matching rule to obtain the message data to be issued.
Preferably, before receiving the data processing request sent by the user, the method further includes:
acquiring an account and a password input by a user;
determining whether the account number and the password pass password authentication;
if the password is verified, executing the step of executing corresponding data exchange operation according to the type of the data processing request.
Preferably, after the feeding back the message data to be sent to the user, the method further includes:
and receiving a response message fed back by the user, and determining that the user correctly receives the message data to be issued.
Preferably, after receiving the data processing request sent by the user, the method further includes:
determining whether the frequency of the data processing requests sent by the user exceeds a frequency threshold;
and if the frequency of the data processing request sent by the user does not exceed the frequency threshold, executing a corresponding data exchange operation according to the type of the data processing request.
A second aspect of the embodiments of the present invention provides a data exchange system, where the system includes:
the processing module is used for executing corresponding data exchange operation according to the type of a data processing request sent by a user, executing the message access engine module and the data exchange engine if the type of the data processing request is a data reporting request, and executing the message output gateway if the type of the data processing request is a data issuing request;
the message access engine module is used for acquiring message data to be uploaded corresponding to the data reporting request, analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue;
the data exchange engine is used for processing the message data to be uploaded after being analyzed in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue;
and the message output gateway is used for acquiring the message data requested by the data issuing request from the message queue and feeding back the message data to be issued to the user.
Preferably, the message access engine module includes: the system comprises an access adapter, a message analysis engine, a message checking module and a message processing module;
the access adapter is used for acquiring message data to be uploaded corresponding to the data reporting request;
the message analysis engine is used for analyzing the message data to be uploaded to obtain the data format and the data semantics of the message data to be uploaded;
the message checking module is used for checking the data format and the data semantics of the message data to be uploaded based on a checking rule, feeding back alarm information to the user if the data format and the data semantics of the message data to be uploaded do not pass the checking, and executing the message processing module if the data format and the data semantics of the message data to be uploaded pass the checking;
the message processing module is used for acquiring a queue message handle corresponding to the message data to be uploaded according to the data type of the message data to be uploaded, and sending the message data to be uploaded to a middleware message queue corresponding to the queue message handle.
Preferably, the data exchange engine includes: the system comprises a data reading module, a data storage module, a rule engine module, a data assembling module and a data distributing module;
the data reading module is used for extracting the first message data to be uploaded in the middleware message queue one by one;
the rule engine module is used for analyzing the message field of the first to-be-uploaded message data aiming at each first to-be-uploaded message data, eliminating useless information of the first to-be-uploaded message data and obtaining second to-be-uploaded message data;
the data assembling module is used for assembling and packaging the second message data to be uploaded;
the data storage module is used for storing the assembled and packaged second message data to be uploaded to a database;
and the data distribution module is used for distributing the assembled and packaged second to-be-uploaded message data to a message queue corresponding to the message type according to the message type of each second to-be-uploaded message data.
Based on the above data exchange method and system provided by the embodiments of the present invention, the method is: if the type of the data processing request sent by the user is a data reporting request, acquiring message data to be uploaded corresponding to the data reporting request; analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue; processing the analyzed message data to be uploaded in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue; if the type of the data processing request sent by the user is a data issuing request, acquiring issued message data requested by the data issuing request from a message queue; and feeding back the message data to be sent to the user. According to the scheme, the uploading or issuing of the message data is executed according to the type of the data processing request sent by the user, the sharing of the message data among different units is realized, and therefore the service quality and the service efficiency can be improved by using the luggage message data.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a data exchange method according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating sending message data to be uploaded to a middleware message queue according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating storing processed message data to be uploaded in a database and a message queue according to an embodiment of the present invention;
fig. 4 is a flowchart of acquiring data of a message to be sent according to an embodiment of the present invention;
fig. 5 is another flowchart of a data exchange method according to an embodiment of the present invention;
fig. 6 is a flowchart for feeding back message data to be sent to a user according to the embodiment of the present invention;
fig. 7 is a block diagram of a data exchange system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
As known from the background art, in the management of baggage message data, the baggage message data of different units are isolated from each other and cannot be shared with each other, so that the baggage message data cannot be utilized to improve the service quality and the service efficiency.
Therefore, embodiments of the present invention provide a data exchange method and system, which implement uploading or issuing of message data according to the type of a data processing request sent by a user, thereby implementing sharing of message data among different units.
The user in the embodiment of the present invention is an airport, an airline company, a customs, or the like.
Referring to fig. 1, a flowchart of a data exchange method provided in an embodiment of the present invention is shown, where the data exchange method includes the following steps:
step S101: executing corresponding data exchange operation according to the type of the data processing request sent by the user, executing step S102 if the type of the data processing request is a data reporting request, and executing step S105 if the type of the data processing request is a data issuing request.
In the process of implementing step S101 specifically, the user sends a data reporting request according to actual requirements, and uploads corresponding message data.
For example: for the user of the Shenzhen airport, the Shenzhen airport sets a return rule of local station baggage Message data (BPM), and uploads the baggage Message data of all baggage processing nodes belonging to the Dongfang airline company in the Shenzhen airport, such as extraction, arrival, unloading, arrival transportation, transfer and the like.
It should be noted that the format of the baggage message data includes, but is not limited to, the original text, XM L, JSON, BSMT, and BSMX, and the message fields corresponding to the baggage message data include all the message fields of.
It is understood that the types of baggage message data include, but are not limited to: the method comprises the steps of carrying out BSM message data on luggage of a carrier departure host from different sources, carrying out BSMX message data on luggage of the carrier departure host from different sources, carrying out BSM message data and carrying out BSMX message data on luggage of other Global Distribution System (GDS) hosts or carriers, processing BPM message data of luggage returned by each airport and carrier and processing BPM message data of luggage of other GDS hosts or carriers.
In another specific implementation, the user sends a data issuing request according to actual requirements to acquire corresponding message data.
For example: for the user of Shenzhen airport, the Shenzhen airport needs to acquire the baggage outbound message data of the front airport related to the local station and acquire the baggage inbound message data of the back airport related to the local station. And configuring corresponding rules under the Shenzhen airport user, uploading all baggage message data which are sent from Shanghai hongqiao airport, Shanghai Pudong airport and Beijing capital airport and belong to eastern airlines and comprise all message fields corresponding to baggage processing nodes such as security check, sorting, loading, warehousing, departure transportation, loading, transfer and the like by other units, and issuing the uploaded baggage message data to the Shenzhen airport.
Preferably, before the user sends the data processing request, the user needs to perform related authentication, and the specific authentication manner is as follows: acquiring an account and a password input by a user, determining whether the account and the password pass password authentication, and if the account and the password pass password authentication, executing step S101.
The above authentication method can authenticate and manage basic information of a user and data information that the user can acquire from the switching center, and can authenticate and manage Application Programming Interface (API) information of the switching center that the user can access.
It should be further noted that, after the user passes the authentication, a string of characters in JSON format is generated, and the string of characters includes a field token. The data processing request subsequently sent by the user carries the token passing the verification to carry out verification, so that the safety of the data is ensured.
Meanwhile, the operation log of the user is recorded, the request information of each time of the user is recorded, and the response information of each time is recorded, so that the follow-up data tracking and monitoring are facilitated.
Preferably, when acquiring a data processing request sent by a user, it is necessary to intercept an excessive request of the user, that is, to prevent the user from frequently sending the data processing request. After receiving a data processing request sent by a user, determining whether the frequency (frequency and times) of the data processing request sent by the user exceeds a frequency threshold, and if the frequency of the data processing request sent by the user does not exceed the frequency threshold, executing subsequent operations according to the type of the data processing request. And if the frequency of the data processing request sent by the user exceeds a frequency threshold, feeding back corresponding alarm information.
Preferably, the API called by the user each time is monitored, so as to monitor the legality of the calling API.
Step S102: and acquiring message data to be uploaded corresponding to the data reporting request.
In the process of implementing step S102 specifically, after the user sends the data reporting request according to the preset rule configuration, the user needs to upload corresponding data, that is, message data to be uploaded, for example: and uploading the baggage message data of all baggage processing nodes belonging to the Dongzhen airline company, such as extraction, arrival, unloading, arrival at port transportation, transfer and the like.
It should be noted that, when the user sends the data upload request, the field isProcessed is encapsulated in the HTTP request Header corresponding to the data upload request. The meaning of the values of isprocesed is as follows:
isprocesed is 0, which represents unprocessed data, and the message data to be uploaded is distributed to an unprocessed queue.
isprocesed is 1, which represents processed data, and the message data to be uploaded is distributed to a processed queue.
The isprocesed is 2, which represents unspecified data, and the message data to be uploaded is distributed to 2 specified queues.
It should be noted that, for the bag Source Message data (BSM) and the BPM Message, the default value of isProcessed is 2, and the default values of other messages are 0.
Step S103: and analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue.
In the process of implementing step S103 specifically, the received message data to be uploaded of different sources and different types is analyzed, the analyzed message data to be uploaded is sent to the middleware message queue, for example, the message data such as BSM and BPM is analyzed, and the analyzed message data such as BSM and BPM is sent to the message intermediate RabbitMQ queue. And in the process of analyzing the message data to be uploaded, verifying the message data to be uploaded, and alarming the message data to be uploaded which does not pass the verification.
Step S104: and processing the message data to be uploaded analyzed in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue.
In the process of implementing step S104, the message data to be uploaded is extracted from the middleware message queue and processed, and the processed message data to be uploaded is stored in the corresponding database and message queue.
It should be noted that the types of databases include, but are not limited to, Oracle database and Hbase database.
Step S105: and acquiring the message data requested by the data issuing request from the message queue.
It should be noted that when the user sends the data issuing request, the user needs to be authenticated, and the specific authentication process may refer to the content in step S101.
In the process of implementing step S105 specifically, a message queue of messages to be forwarded is monitored according to a preset configuration, and when a data transmission request sent by a user is received, the transmission message data requested by the user is extracted from the message queue. And performing relevant processing on the extracted message data to be sent back to the user.
Step S106: and feeding back the message data to be sent to the user.
Preferably, after the message data to be issued is fed back to the user, the response message fed back by the user is received, and the user is determined to correctly receive the message data to be issued.
It should be noted that, after receiving the returned result containing the message data to be issued, the user analyzes uuid of the returned result, where uuid is a unique identification code of the BPM message for the user. The user responds or calls a BPM response interface, sends a response message and indicates that the message data to be sent is correctly received. If the user does not send a response message, when the user requests corresponding to the message data to be issued, for example, requests BPM data again, the message data to be issued without an Acknowledgement Character (ACK) may be issued again.
In the embodiment of the invention, if the type of the data processing request sent by the user is the data reporting request, the message data to be uploaded corresponding to the data reporting request is acquired, and after the message data to be uploaded is correspondingly processed, the processed message data to be uploaded is stored in the database and the message queue. If the type of the data processing request sent by the user is a data issuing request, acquiring the issued message data requested by the data issuing request from the message queue, and feeding back the message data to be issued to the user. The sharing of message data among different units is realized, so that the luggage message data can be utilized to improve the service quality and the service efficiency.
In the above-described embodiment of the present invention, referring to fig. 2, a process of sending message data to be uploaded to a middleware message queue, which is related in step S103 in fig. 1, shows a flowchart of sending message data to be uploaded to the middleware message queue, which is provided in the embodiment of the present invention, and includes the following steps:
step S201: and analyzing the message data to be uploaded to obtain the data format and the data semantics of the message data to be uploaded.
In the process of implementing step S201 specifically, the message data to be uploaded, the data format and the data semantics of the message data to be uploaded are analyzed for the message data to be uploaded from different sources and different types.
Step S202: and checking the data format and the data semantics of the message data to be uploaded based on the checking rule. If the data format and the data semantics of the message data to be uploaded do not pass the verification, step S203 is executed, and if the data format and the data semantics of the message data to be uploaded pass the verification, step S204 is executed.
In the process of implementing step S202 specifically, after the message data to be uploaded is analyzed, the corresponding verification needs to be performed on the message data to be uploaded, and the message data to be uploaded that does not conform to the verification rule is screened out and removed. That is to say, based on the verification rule, the data format and the data semantics of the message data to be uploaded are verified, and if the verified message data to be uploaded does not pass the verification, an alarm message indicating that the message data to be uploaded does not pass the verification is fed back to the user.
Step S203: and (5) feeding back alarm information to the user.
Step S204: and acquiring a queue message handle corresponding to the message data to be uploaded according to the data type of the message data to be uploaded.
In the process of implementing step S204 specifically, for the checked to-be-uploaded message data, a queue message handle corresponding to the to-be-uploaded message data is obtained according to the data type of the to-be-uploaded message data. For example: the BSM message data acquires a BSM queue message handle, and the BPM message data acquires a BPM queue message handle.
It should be noted that, because the same data type supports configuration of multiple queues, that is, when a corresponding queue message handle is obtained according to the data type of the message data to be uploaded, multiple queue message handles may be obtained.
Step S205: and sending the message data to be uploaded to a middleware message queue corresponding to the queue message handle.
In the process of implementing step S205 specifically, after the queue message handle of the to-be-uploaded message data is acquired, the checked to-be-uploaded message data is sent to the middleware message queue corresponding to the queue message handle.
That is to say, the checked message data to be uploaded is sent to the middleware message queue cluster according to the above manner.
In the embodiment of the invention, the message data to be uploaded is verified by using the verification rule, and the message data to be uploaded which does not pass the verification is screened out and removed. And acquiring a queue message handle of the message data to be uploaded which passes the verification, and sending the message data to be uploaded which passes the verification to a middleware message queue corresponding to the queue message handle. And screening and related processing of the message data to be uploaded are realized.
In the above-described embodiment of the present invention, referring to fig. 3, a process of storing processed to-be-uploaded message data in a database and a message queue, which is related in step S104 of fig. 1, shows a flowchart of storing processed to-be-uploaded message data in a database and a message queue, which is provided in the embodiment of the present invention, and includes the following steps:
step S301: and extracting the first message data to be uploaded in the middleware message queue one by one.
In the process of implementing step S301 specifically, after the verified message data to be uploaded is stored in the corresponding middleware message queue, the first message data to be uploaded in the middleware message queue is extracted one by one, for example: and extracting the first message data to be uploaded from the RabbitMQ message queue.
Step S302: and analyzing the message field of the first to-be-uploaded message data aiming at each first to-be-uploaded message data, and eliminating useless information of the first to-be-uploaded message data to obtain second to-be-uploaded message data.
In the process of implementing step S302 specifically, for each piece of first to-be-uploaded message data, a message field of the first to-be-uploaded message data is analyzed, useless information of the first to-be-uploaded message data is removed, second to-be-uploaded message data is obtained, and the second to-be-uploaded message data is stored in the database.
For example: and storing the second message data to be uploaded to storage equipment such as an Oracle database or an Hbase database.
Step S303: and assembling and packaging the second message data to be uploaded.
In the process of implementing step S303, the second to-be-uploaded message data is reassembled and packaged according to the actual requirements of the user.
Step S304: and storing the second message data to be uploaded to a database.
Step S305: and according to the message type of each second message data to be uploaded, distributing the assembled and packaged second message data to be uploaded to a message queue corresponding to the message type.
In the process of implementing step S305 specifically, for each assembled and packaged second to-be-uploaded packet data, according to the packet type of the second to-be-uploaded packet data, the assembled and packaged second to-be-uploaded packet data is distributed to a packet message queue corresponding to the packet type, and is used as data for subsequent routing delivery.
For example: and distributing the assembled and packaged second to-be-uploaded message data to a BSM message queue, or distributing the assembled and packaged second to-be-uploaded message data to a BPM message queue.
In the embodiment of the invention, the first message data to be uploaded is extracted from the middleware message queue one by one, and the second message data to be uploaded is obtained after the first message data to be uploaded is subjected to relevant processing. And respectively storing the second message data to be uploaded into the database and the corresponding message queue to realize the uploading of the message data. Other units can share the message data among different units by using the uploaded message data, so that the luggage message data can be used for improving the service quality and the service efficiency.
In the above-mentioned embodiment of the present invention, referring to fig. 4, the process of obtaining the message data to be issued requested by the data issuing request in step S105 in fig. 1 shows a flowchart of obtaining the message data to be issued, which includes the following steps:
step S401: and extracting each message data in the message queue.
In the process of implementing step 401 specifically, when the user sends a data issuing request, that is, the user needs to obtain corresponding data, the message data is extracted from the message queue corresponding to the data issuing request, for example: and extracting message data from the BPM message queue.
Step S402: and pre-analyzing the extracted message data to obtain data information corresponding to the message data.
In the process of implementing step S402, the extracted message data is pre-analyzed to obtain data information corresponding to each extracted message data.
Step S403: and acquiring a user matching rule corresponding to the data issuing request.
In the process of implementing step S403 specifically, a user matching rule corresponding to the data issuing request is obtained, and matching is performed according to the data information obtained by pre-analysis and a preset configured user rule.
Step S404: and acquiring the message data of which the data information is matched with the user matching rule to obtain the message data to be issued.
In the process of implementing step S404, the message data whose data information matches the user matching rule is obtained, and the message data to be issued is obtained. In the subsequent issuing process, forwarding the obtained to-be-issued message data to a message queue corresponding to the user, for example: when the Shenzhen airport needs to acquire message data in the BPM message queue at the back end of the Shenzhen airport, the data issuing request of the Shenzhen airport is routed to the BPM message queue at the back end of the Shenzhen airport, corresponding message data to be issued is acquired, and the acquired message data to be issued is forwarded to the BPM message queue at the Shenzhen airport.
In the embodiment of the invention, when a user needs to acquire message data, the message data is extracted from the message queue and is subjected to relevant processing, so that the message data to be transmitted is obtained. The obtained message data to be issued is fed back to the user, and the sharing of the message data among different units is realized, so that the service quality and the service efficiency can be improved by using the luggage message data.
To better explain the contents in the above embodiments, the contents are illustrated by the contents shown in fig. 5 and fig. 6, and it should be noted that fig. 5 and fig. 6 are only for example.
Referring to fig. 5, another flowchart of a data exchange method provided in an embodiment of the present invention is shown, where the data exchange method includes the following steps:
step S501: the upload service (PushService in fig. 5) acquires the message data in the data source, and performs corresponding processing on the message data.
In the specific implementation step S501, the meaning of the field isProcessed in the Header of the message data in the data source can refer to the relevant content in fig. 1 in the above embodiment of the present invention. Step S502 is performed for unprocessed message data, and step S503 is performed for processed message data.
Step S502: and performing related processing on the BSM message data, the flight dynamic message data and the BPM message data.
Step S503: and distributing the processed BSM message data, the processed flight dynamic message data and the processed BPM message data to each message queue (the user queue in the figure 5) according to the routing rule.
Step S504: the down-sending service (PullService in fig. 5) acquires the message data from each user queue, and feeds back the acquired message data to the user.
It should be noted that, the execution principle of steps S501 to S504 can refer to the contents shown in fig. 1 to fig. 4 of the above embodiments of the present invention.
Referring to fig. 6, a flowchart for feeding back message data to be sent to a user according to an embodiment of the present invention is shown, where the flowchart includes the following steps:
step S601: and acquiring message data from the message queue.
Step S602: and pre-analyzing the acquired message data.
Step S603: and carrying out user rule matching on the message data after the pre-analysis.
Step S604: and feeding back the message data subjected to the user rule matching to the user.
It should be noted that, for the execution principle of the above steps S601 to S604, reference may be made to the content shown in fig. 4 in the above embodiment of the present invention.
In the embodiment of the invention, if the type of the data processing request sent by the user is the data reporting request, the message data to be uploaded corresponding to the data reporting request is acquired, and after the message data to be uploaded is correspondingly processed, the processed message data to be uploaded is stored in the database and the message queue. If the type of the data processing request sent by the user is a data issuing request, acquiring the issued message data requested by the data issuing request from the message queue, and feeding back the message data to be issued to the user. The sharing of message data among different units is realized, so that the luggage message data can be utilized to improve the service quality and the service efficiency.
Corresponding to the data exchange method provided by the above embodiment of the present invention, referring to fig. 7, an embodiment of the present invention further provides a structural block diagram of a data exchange system, where the data exchange system includes: a processing module 701, a message access engine module 702, a data exchange engine 703 and a message output gateway 704;
the processing module 701 is configured to execute a corresponding data exchange operation according to a type of a data processing request sent by a user, execute the message access engine module 702 and the data exchange engine 703 if the type of the data processing request is a data reporting request, and execute the message output gateway 704 if the type of the data processing request is a data issuing request.
The message access engine module 702 is configured to obtain message data to be uploaded corresponding to the data reporting request, analyze the message data to be uploaded, and send the analyzed message data to be uploaded to the middleware message queue.
And the data exchange engine 703 is configured to process the to-be-uploaded message data analyzed in the middleware message queue based on a preset processing rule, and store the processed to-be-uploaded message data to the database and the message queue.
And the message output gateway 704 is configured to obtain the message data requested by the data issuing request from the message queue, and feed back the message data to be issued to the user.
In a specific implementation, the message output gateway 704 is specifically configured to: extracting each message data in the message queue, performing pre-analysis on the extracted message data to obtain data information corresponding to the message data, acquiring a user matching rule corresponding to the data issuing request, acquiring the message data of which the data information is matched with the user matching rule, and acquiring the message data to be issued.
Preferably, the message output gateway 704 is further configured to: the method includes the steps of acquiring an account and a password input by a user, determining whether the account and the password pass password authentication, and if the account and the password pass password authentication, executing a processing module 701.
Preferably, the message output gateway 704 is further configured to: and receiving a response message fed back by the user, and determining that the user correctly receives the message data to be sent.
Preferably, the message output gateway 704 is further configured to: determining whether the frequency of the data processing request sent by the user exceeds a frequency threshold, and if the frequency of the data processing request sent by the user does not exceed the frequency threshold, executing the processing module 701.
Preferably, the message output gateway 704 is further configured to: the method comprises the steps of recording an operation log of a user, recording request information of the user every time, and recording response information of the user every time.
Preferably, the message output gateway 704 is further configured to: and monitoring the API called by the user each time, and monitoring the legality of the called API.
In the embodiment of the invention, if the type of the data processing request sent by the user is the data reporting request, the message data to be uploaded corresponding to the data reporting request is acquired, and after the message data to be uploaded is correspondingly processed, the processed message data to be uploaded is stored in the database and the message queue. If the type of the data processing request sent by the user is a data issuing request, acquiring the issued message data requested by the data issuing request from the message queue, and feeding back the message data to be issued to the user. The sharing of message data among different units is realized, so that the luggage message data can be utilized to improve the service quality and the service efficiency.
Preferably, in combination with the content shown in fig. 7, the message access engine module 702 includes an access adapter, a message parsing engine, a message checking module, and a message processing module, and the execution principle of each module is as follows:
and the access adapter is used for acquiring the message data to be uploaded corresponding to the data reporting request.
And the message analysis engine is used for analyzing the message data to be uploaded to obtain the data format and the data semantics of the message data to be uploaded.
And the message checking module is used for checking the data format and the data semantics of the message data to be uploaded based on the checking rule, feeding back alarm information to a user if the data format and the data semantics of the message data to be uploaded do not pass the checking, and executing the message processing module if the data format and the data semantics of the message data to be uploaded pass the checking.
And the message processing module is used for acquiring a queue message handle corresponding to the message data to be uploaded according to the data type of the message data to be uploaded, and sending the message data to be uploaded to a middleware message queue corresponding to the queue message handle.
In the embodiment of the invention, the message data to be uploaded is verified by using the verification rule, and the message data to be uploaded which does not pass the verification is screened out and removed. And acquiring a queue message handle of the message data to be uploaded which passes the verification, and sending the message data to be uploaded which passes the verification to a middleware message queue corresponding to the queue message handle. And screening and related processing of the message data to be uploaded are realized.
Preferably, in connection with the content shown in fig. 7, the data exchange engine 703 includes: the system comprises a data reading module, a data storage module, a rule engine module, a data assembling module and a data distributing module, wherein the execution principle of each module is as follows:
and the data reading module is used for extracting the first message data to be uploaded in the middleware message queue one by one.
And the rule engine module is used for analyzing the message field of the first to-be-uploaded message data aiming at each first to-be-uploaded message data, eliminating useless information of the first to-be-uploaded message data and obtaining second to-be-uploaded message data.
And the data assembling module is used for assembling and packaging the second message data to be uploaded.
And the data storage module is used for storing the assembled and packaged second message data to be uploaded to a database.
And the data distribution module is used for distributing the assembled and packaged second to-be-uploaded message data to a message queue corresponding to the message type according to the message type of each second to-be-uploaded message data.
In the embodiment of the invention, the first message data to be uploaded is extracted from the middleware message queue one by one, and the second message data to be uploaded is obtained after the first message data to be uploaded is subjected to relevant processing. And respectively storing the second message data to be uploaded into the database and the corresponding message queue to realize the uploading of the message data. Other units can share the message data among different units by using the uploaded message data, so that the luggage message data can be used for improving the service quality and the service efficiency.
In addition to the above functions, the data exchange engine 703 described above has at least the following non-functional characteristics:
(1) high availability: each functional module in the data exchange engine 703 has a high availability of 99.9%, that is, the entire data exchange system does not stop working due to a failure, that is, a data demand party cannot acquire data in time due to a failure.
(2) High performance: the magnitude of the civil aviation luggage message data accessed every day is in the ten million level, and the transaction number/Second (TPS) of the message data accessed in the peak time period is up to thousands of levels. That is, the data processing amount is increased by a high factor, which requires the data exchange engine 703 to have high performance, and reduces the delay of the data exchange system in data processing.
(3) The method can be compatible, wherein for the output message data, the TYPE-B format of the International Air Transport Association (IATA) specification needs to be met, and the Extensible Markup language (XM L) data format and other data formats need to be compatible.
(4) Traceable and traceable: namely, the exchange distribution process can be recorded and tracked for each piece of accessed message data.
In addition to the above functions, the message output gateway 704 has at least the following non-functional characteristics:
(1) high performance: the response time of a single API is within a certain time, for example within 500 ms.
(2) High availability: the API gateway is guaranteed to operate stably for 7 × 24 hours without interruption, that is, the modules in the message output gateway 704 need cluster deployment, and each service in the cluster has load balancing capability.
(3) Can monitor: the service state and the response state of each API can be monitored, and therefore early warning is conducted when abnormality occurs.
It should be further noted that the data exchange system generally needs to process a large amount of data, so that a streaming processing technology can be used to ensure the timeliness of data processing, and a message middleware technology is used to ensure the decoupling, data temporary storage, and data concurrent processing of each system module in the data exchange system.
To sum up, the embodiments of the present invention provide a data exchange method and system, where the method includes: if the type of the data processing request sent by the user is a data reporting request, acquiring message data to be uploaded corresponding to the data reporting request; analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue; processing the analyzed message data to be uploaded in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue; if the type of the data processing request sent by the user is a data issuing request, acquiring issued message data requested by the data issuing request from a message queue; and feeding back the message data to be sent to the user. According to the scheme, the uploading or issuing of the message data is executed according to the type of the data processing request sent by the user, the sharing of the message data among different units is realized, and therefore the service quality and the service efficiency can be improved by using the luggage message data.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method of data exchange, the method comprising:
executing corresponding data exchange operation according to the type of the data processing request sent by the user;
if the type of the data processing request is a data reporting request, the data exchange operation includes:
acquiring message data to be uploaded corresponding to the data reporting request;
analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue;
processing the message data to be uploaded analyzed in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue;
if the type of the data processing request is a data issuing request, the data exchange operation comprises:
acquiring the message data requested by the data issuing request from the message queue;
and feeding back the message data to be issued to the user.
2. The method according to claim 1, wherein the parsing the message data to be uploaded and sending the parsed message data to be uploaded to a middleware message queue comprises:
analyzing the message data to be uploaded to obtain the data format and the data semantics of the message data to be uploaded;
based on a check rule, checking the data format and the data semantics of the message data to be uploaded;
if the data format and the data semantics of the message data to be uploaded do not pass the verification, feeding alarm information back to the user;
if the data format and the data semantics of the message data to be uploaded pass the verification, acquiring a queue message handle corresponding to the message data to be uploaded according to the data type of the message data to be uploaded;
and sending the message data to be uploaded to a middleware message queue corresponding to the queue message handle.
3. The method according to claim 1, wherein the processing the message data to be uploaded after being parsed in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue comprises:
extracting first message data to be uploaded in the middleware message queue one by one;
analyzing the message field of the first message data to be uploaded aiming at each first message data to be uploaded, and eliminating useless information of the first message data to be uploaded to obtain second message data to be uploaded;
assembling and packaging the second message data to be uploaded;
storing the second message data to be uploaded to a database;
and according to the message type of each second message data to be uploaded, distributing the assembled and packaged second message data to be uploaded to a message queue corresponding to the message type.
4. The method according to claim 1, wherein the obtaining the to-be-transmitted message data requested by the data transmission request from the message queue comprises:
extracting each message data in the message queue;
pre-analyzing the extracted message data to obtain data information corresponding to the message data;
acquiring a user matching rule corresponding to the data issuing request;
and acquiring the message data of which the data information is matched with the user matching rule to obtain the message data to be issued.
5. The method of claim 1, wherein before receiving the data processing request sent by the user, the method further comprises:
acquiring an account and a password input by a user;
determining whether the account number and the password pass password authentication;
if the password is verified, executing the step of executing corresponding data exchange operation according to the type of the data processing request.
6. The method according to claim 1, wherein after feeding back the message data to be sent to the user, further comprising:
and receiving a response message fed back by the user, and determining that the user correctly receives the message data to be issued.
7. The method of claim 1, after receiving a data processing request sent by a user, further comprising:
determining whether the frequency of the data processing requests sent by the user exceeds a frequency threshold;
and if the frequency of the data processing request sent by the user does not exceed the frequency threshold, executing a corresponding data exchange operation according to the type of the data processing request.
8. A data exchange system, characterized in that the system comprises:
the processing module is used for executing corresponding data exchange operation according to the type of a data processing request sent by a user, executing the message access engine module and the data exchange engine if the type of the data processing request is a data reporting request, and executing the message output gateway if the type of the data processing request is a data issuing request;
the message access engine module is used for acquiring message data to be uploaded corresponding to the data reporting request, analyzing the message data to be uploaded, and sending the analyzed message data to be uploaded to a middleware message queue;
the data exchange engine is used for processing the message data to be uploaded after being analyzed in the middleware message queue based on a preset processing rule, and storing the processed message data to be uploaded to a database and a message queue;
and the message output gateway is used for acquiring the message data requested by the data issuing request from the message queue and feeding back the message data to be issued to the user.
9. The system of claim 8, wherein the message access engine module comprises: the system comprises an access adapter, a message analysis engine, a message checking module and a message processing module;
the access adapter is used for acquiring message data to be uploaded corresponding to the data reporting request;
the message analysis engine is used for analyzing the message data to be uploaded to obtain the data format and the data semantics of the message data to be uploaded;
the message checking module is used for checking the data format and the data semantics of the message data to be uploaded based on a checking rule, feeding back alarm information to the user if the data format and the data semantics of the message data to be uploaded do not pass the checking, and executing the message processing module if the data format and the data semantics of the message data to be uploaded pass the checking;
the message processing module is used for acquiring a queue message handle corresponding to the message data to be uploaded according to the data type of the message data to be uploaded, and sending the message data to be uploaded to a middleware message queue corresponding to the queue message handle.
10. The system of claim 8, wherein the data exchange engine comprises: the system comprises a data reading module, a data storage module, a rule engine module, a data assembling module and a data distributing module;
the data reading module is used for extracting the first message data to be uploaded in the middleware message queue one by one;
the rule engine module is used for analyzing the message field of the first to-be-uploaded message data aiming at each first to-be-uploaded message data, eliminating useless information of the first to-be-uploaded message data and obtaining second to-be-uploaded message data;
the data assembling module is used for assembling and packaging the second message data to be uploaded;
the data storage module is used for storing the assembled and packaged second message data to be uploaded to a database;
and the data distribution module is used for distributing the assembled and packaged second to-be-uploaded message data to a message queue corresponding to the message type according to the message type of each second to-be-uploaded message data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010263864.8A CN111510440B (en) | 2020-04-07 | 2020-04-07 | Data exchange method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010263864.8A CN111510440B (en) | 2020-04-07 | 2020-04-07 | Data exchange method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111510440A true CN111510440A (en) | 2020-08-07 |
| CN111510440B CN111510440B (en) | 2022-09-20 |
Family
ID=71870888
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010263864.8A Active CN111510440B (en) | 2020-04-07 | 2020-04-07 | Data exchange method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111510440B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114710422A (en) * | 2022-04-02 | 2022-07-05 | 中国民航信息网络股份有限公司 | Luggage message format checking method and related device |
| CN116760566A (en) * | 2022-12-01 | 2023-09-15 | 黄建邦 | Data transmission method, system, first end, intermediate network device and control device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070266084A1 (en) * | 2006-04-28 | 2007-11-15 | Avfinity. Inc | Method, system, apparatus, and program to facilitate communication between systems |
| US20080065480A1 (en) * | 2006-09-08 | 2008-03-13 | Daniel Baker | System for handling air traffic data and related information for supply to customers |
| CN101304424A (en) * | 2008-06-10 | 2008-11-12 | 南京财经大学 | Method for exhibiting data of different source data switching middleware based on XML |
| CN101621463A (en) * | 2009-07-17 | 2010-01-06 | 中国民航大学 | Flight-information data-sharing switching exchanger and processing method thereof |
| CN101964958A (en) * | 2010-09-27 | 2011-02-02 | 北京航空航天大学 | On-board network system and backbone node message processing method thereof |
| CN104954469A (en) * | 2015-06-19 | 2015-09-30 | 长沙廖氏软件科技有限公司 | Information exchange method for heterogeneous system |
| CN105978964A (en) * | 2016-05-09 | 2016-09-28 | 中国民航信息网络股份有限公司 | Aviation logistics data intelligent distribution model and method |
| CN110493571A (en) * | 2019-08-21 | 2019-11-22 | 北京旷视科技有限公司 | Cascade business datum distribution method, device and the monitoring system of trans-regional cluster |
-
2020
- 2020-04-07 CN CN202010263864.8A patent/CN111510440B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070266084A1 (en) * | 2006-04-28 | 2007-11-15 | Avfinity. Inc | Method, system, apparatus, and program to facilitate communication between systems |
| US20080065480A1 (en) * | 2006-09-08 | 2008-03-13 | Daniel Baker | System for handling air traffic data and related information for supply to customers |
| CN101304424A (en) * | 2008-06-10 | 2008-11-12 | 南京财经大学 | Method for exhibiting data of different source data switching middleware based on XML |
| CN101621463A (en) * | 2009-07-17 | 2010-01-06 | 中国民航大学 | Flight-information data-sharing switching exchanger and processing method thereof |
| CN101964958A (en) * | 2010-09-27 | 2011-02-02 | 北京航空航天大学 | On-board network system and backbone node message processing method thereof |
| CN104954469A (en) * | 2015-06-19 | 2015-09-30 | 长沙廖氏软件科技有限公司 | Information exchange method for heterogeneous system |
| CN105978964A (en) * | 2016-05-09 | 2016-09-28 | 中国民航信息网络股份有限公司 | Aviation logistics data intelligent distribution model and method |
| CN110493571A (en) * | 2019-08-21 | 2019-11-22 | 北京旷视科技有限公司 | Cascade business datum distribution method, device and the monitoring system of trans-regional cluster |
Non-Patent Citations (2)
| Title |
|---|
| 习捷: ""消息中间件在数据转换传输平台中的应用"", 《万方》 * |
| 潘宇: ""民航信息共享交换平台建设及相关问题研究"", 《万方》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114710422A (en) * | 2022-04-02 | 2022-07-05 | 中国民航信息网络股份有限公司 | Luggage message format checking method and related device |
| CN116760566A (en) * | 2022-12-01 | 2023-09-15 | 黄建邦 | Data transmission method, system, first end, intermediate network device and control device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111510440B (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10997675B2 (en) | Federated system for centralized management and distribution of content media | |
| US8732258B2 (en) | Method and system for transporting telemetry data across a network | |
| EP3430772B1 (en) | Message transfer system, method of transferring messages and software product | |
| CN110134674B (en) | Currency credit big data monitoring and analyzing system | |
| CN101663842B (en) | Method and device for managing communication channels for data exchange from aircraft | |
| CN111510440B (en) | Data exchange method and system | |
| CN110730181A (en) | Message conversion method, device and adapter | |
| CN104838620A (en) | Event management in telecommunications networks | |
| CN111478900A (en) | Data processing method and system | |
| CN105978964A (en) | Aviation logistics data intelligent distribution model and method | |
| KR20190136364A (en) | Method for interconnecting heterogeneous blockchain platform and gateway apparatus for executing the same | |
| US10360084B1 (en) | System and methods for logging and searching history events such as airline flight or crew history | |
| CN111258760A (en) | Platform management method, system, device and storage medium | |
| CN114422496A (en) | Mass traffic data processing system and method | |
| CN101621530A (en) | Method and device for dispatching load balancing network resource based on light path share | |
| CN114328587A (en) | NDC message distributed analysis system architecture integration method and device | |
| US10623523B2 (en) | Distributed communication and task handling to facilitate operations of application system | |
| CN109558744B (en) | Data processing method and system | |
| US10812379B2 (en) | Baggage messaging handling systems and methods | |
| US8819107B2 (en) | Relay apparatus, recording medium storing a relay program, and a relay method | |
| CN117014445B (en) | Block chain-based data processing method, device, equipment and storage medium | |
| CN117036038B (en) | Transaction processing method, device, equipment and storage medium based on alliance chain | |
| CN117272236B (en) | Multi-source arrival time fusion method and system based on flight time sequence | |
| US20230120915A1 (en) | Security intelligence platform architecture and functionality | |
| Si et al. | Bei-Tab: Enabling Secure and Distributed Airport Baggage Tracking with Hybrid Blockchain-Edge System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |