CN115293699A

CN115293699A - Logistics data query method and related device

Info

Publication number: CN115293699A
Application number: CN202210958509.1A
Authority: CN
Inventors: 李纯云
Original assignee: Shenzhen Xiecheng Technology Network Co ltd
Current assignee: Shenzhen Xiecheng Technology Network Co ltd
Priority date: 2022-08-09
Filing date: 2022-08-09
Publication date: 2022-11-04

Abstract

The embodiment of the application provides a logistics data query method and a related device, aiming at a logistics list number with a query type of track query, the method determines a transportation type corresponding to the logistics list number; then according to the transportation type, determining one or more corresponding first crawler servers from the logistics server cluster, wherein each first crawler server in the one or more first crawler servers stores logistics track subdata corresponding to the transportation type; sending a first acquisition request aiming at the logistics track sub-data to each first crawler server; receiving the logistics track sub-data sent by an external data source service of the one or more first crawler servers to obtain one or more logistics track sub-data, and storing the one or more logistics track sub-data as target logistics data; and sending the target logistics data to the API gateway equipment. In this way, one-stop type inquiry of different transportation tracks based on the transportation types is realized.

Description

Logistics data query method and related device

Technical Field

The application belongs to the technical field of network information, and particularly relates to a logistics data query method and a related device.

Background

The cross-border electronic commerce is an international business activity which belongs to transaction main bodies of different relations, achieves transaction and payment settlement through an electronic commerce platform, and delivers commodities through cross-border logistics to complete the transaction.

Currently, in China, the real-time tracking and query of packages are basically realized thanks to the high-speed development of the commodity industry of the electronic commerce in China. However, in the query method for cross-border logistics including the intra-border section and the extra-border section, each query website can only query a single logistics track, for example, shipping can only query at a special shipping logistics website, train transportation can only query at a special train transportation logistics website, and the query mode is single, so that if one package needs to query different transportation modes, the query efficiency is low.

Disclosure of Invention

The embodiment of the application provides a logistics data query method and a related device, aiming at realizing one-stop query of different transportation tracks based on transportation types.

In a first aspect, an embodiment of the present application provides a method for querying logistics data, which is applied to a query server, and includes:

acquiring a query request aiming at target logistics data from API gateway equipment, wherein the query request is generated based on a logistics list number imported by a user at user equipment, and the target logistics data refers to logistics data corresponding to the logistics list number;

determining a query type of the query request;

if the query type is track query, determining a transportation type corresponding to the logistics single number;

determining one or more corresponding first crawler servers from a logistics server cluster according to the transportation type, wherein each first crawler server in the one or more first crawler servers stores logistics track sub data corresponding to the transportation type;

sending a first acquisition request aiming at the logistics track sub-data to each first crawler server;

receiving the logistics track sub-data sent by an external data source service of the one or more first crawler servers to obtain one or more logistics track sub-data, and storing the one or more logistics track sub-data as target logistics data;

and sending the target logistics data to the API gateway device, wherein the one or more logistics track sub-data are used for providing an instruction for forwarding the one or more logistics track sub-data to the user equipment for the API gateway device, and providing an instruction for drawing a transportation track broken line and a transportation node on a map for the user equipment.

In a second aspect, an embodiment of the present application provides a method for querying logistics data, which is applied to a user equipment, and the method includes:

acquiring a logistics list number and an inquiry type input by a user through an input box, wherein the logistics list number and the inquiry type are used for providing an instruction for generating an inquiry request for the API gateway device, the inquiry request is used for providing an instruction for an inquiry server to acquire target logistics data from a corresponding first crawler server, the target logistics data is logistics data corresponding to the logistics list number, and the inquiry type comprises track inquiry;

sending the logistics list number and the query type to API gateway equipment;

receiving target logistics data sent by the API gateway equipment; when the query type is track query, the target logistics data comprise one or more logistics track subdata, and the one or more logistics track subdata are respectively stored in one or more first crawler servers in a logistics server cluster; the logistics list number is used for providing an indication for determining the transportation type of the logistics list number for the query server; the transportation type is used for providing an instruction for the query server to acquire the one or more logistics track subdata from the one or more first crawler servers and send the one or more logistics track subdata to the API gateway equipment;

and drawing a logistics track broken line and a transportation node in a map of a display interface based on the one or more logistics track sub-data to obtain a logistics track map corresponding to the logistics single number.

In a third aspect, an embodiment of the present application provides a method for querying logistics data, where the method is applied to an API gateway device, and the method includes:

receiving a logistics list number and an inquiry type from the user equipment, wherein the inquiry type comprises track inquiry;

generating a query request aiming at target logistics data according to the logistics list number and the query type, wherein the target logistics data refer to logistics data corresponding to the logistics list number;

sending the query request to a query server;

receiving the target logistics data from the query server, wherein when the query type is track query, the target logistics data comprises one or more logistics track subdata, and the one or more logistics track subdata are respectively stored in one or more first crawler servers in a logistics server cluster; the logistics list number is used for providing an indication for determining the transportation type of the logistics list number for the query server; the transportation type is used for providing an instruction for the query server to acquire the one or more logistics track subdata from the one or more first crawler servers and send the one or more logistics track subdata to the API gateway equipment;

and sending the target logistics data to the user equipment, wherein the one or more logistics track sub-data are used for providing an instruction for drawing a transportation track broken line and a transportation node on a map for the user equipment.

In a fourth aspect, an embodiment of the present application provides a user interface of a user equipment, where the user equipment includes a display screen, the user interface is displayed on the display screen, and the user interface is a software interface; the user interface is controlled by inputting a touch instruction through the display screen by a user, or the user controls the user interface by inputting a control instruction through an input device by the user;

the user interface comprises an initial interface and a query result display interface, the initial interface comprises a plurality of input boxes and a query control, and the input boxes are respectively used for inputting the logistics list number and the query type; the query result display interface comprises a plurality of display sub-interfaces, and each display sub-interface in the plurality of display sub-interfaces corresponds to one query type; the query type comprises a track query;

and when the logistics list number and the query type are input into the input boxes, if the click operation aiming at the query control is received, jumping from the initial interface to a display sub-interface corresponding to the query type.

In a fifth aspect, an embodiment of the present application provides an electronic device, including a processor, a memory, a communication interface, and one or more programs, stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps of any of the first to third aspects of the embodiments of the present application.

In a sixth aspect, an embodiment of the present application provides a computer storage medium, which is characterized by storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform some or all of the steps described in any one of the first aspect to the third aspect of the present embodiment.

In a seventh aspect, this application embodiment provides a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, where the computer program is operable to cause a computer to perform some or all of the steps as described in any of the first to third aspects of this application embodiment. The computer program product may be a software installation package.

It can be seen that, in the embodiment of the present application, first, an inquiry request for target logistics data from an API gateway device is obtained; then determining the query type of the query request; if the query type is track query, determining a transportation type corresponding to the logistics single number; determining one or more corresponding first crawler servers from a logistics server cluster according to the transportation type, wherein each first crawler server in the one or more first crawler servers stores logistics track sub data corresponding to the transportation type; sending a first acquisition request aiming at the logistics track sub-data to each first crawler server; then receiving the logistics track sub-data sent by an external data source service of the one or more first crawler servers to obtain one or more logistics track sub-data, and storing the one or more logistics track sub-data as target logistics data; and sending the target logistics data to the API gateway equipment, wherein user equipment displays the target logistics data. In this way, one-stop type inquiry of different transportation tracks based on the transportation types is realized.

Drawings

In order to more clearly illustrate the embodiments of the present application 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 some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a diagram of a logistics inquiry system architecture provided in an embodiment of the present application;

fig. 2 is a schematic flowchart of a logistics data query method provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of a transportation process for four order types provided by an embodiment of the present application;

FIG. 4 is a schematic interface diagram of a query result display interface provided in an embodiment of the present application;

fig. 5 is a schematic structural diagram of a logistics data query device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a logistics data query device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a logistics data query device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all 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 application.

The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, system, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

The following description will first be made with respect to terms related to the present application.

VGM (veriied GROSS MASS, VERIFIED total container weight): is the sum of the total weight of the cargo and the tare weight of the container, including packaging and dunnage. The requirement to verify the gross weight of a container is a commitment to security, and the misinformation of gross weight of a container poses a risk to domestic, foreign personnel, inland and marine cargo and equipment and causes accidents, and regulations to verify the gross weight of a container (VGM) aim to reduce such accidents.

API gateway: the API Gateway (API Gateway, APIG) is an API hosting service provided by China for cloud. An API (Application Programming Interface) is a predefined function, and an Application encapsulates its service capability into an API and opens the API to a user for calling through an API gateway. The API includes basic information, request paths and parameters of the front and back ends, and request-related protocols.

At present, in a cross-border logistics query method including an intra-border section and an extra-border section, each query website can only query a single logistics track, for example, shipping can only query at a special shipping logistics website, train transportation can only query at a special train transportation logistics website, and the query mode is single, so that if one package needs to query different transportation modes, the query efficiency is low.

In order to solve the above problem, an embodiment of the present application provides a method for querying logistics data. The method can be applied to the scene of transnational logistics inquiry. The query request for the target logistics data from the API gateway equipment can be obtained; then determining the query type of the query request; if the query type is track query, determining a transportation type corresponding to the logistics single number; determining one or more corresponding first crawler servers from a logistics server cluster according to the transportation type, wherein each first crawler server in the one or more first crawler servers stores logistics track sub data corresponding to the transportation type; sending a first acquisition request aiming at the logistics track sub-data to each first crawler server; then receiving the logistics track sub-data sent by an external data source service of the one or more first crawler servers to obtain one or more logistics track sub-data, and storing the one or more logistics track sub-data as target logistics data; and sending the target logistics data to the API gateway equipment, wherein user equipment displays the target logistics data. In this way, one-stop type inquiry of different transportation tracks based on the transportation types is realized. The present solution may be applicable to a variety of scenarios, including but not limited to the application scenarios mentioned above.

The following describes a system architecture according to an embodiment of the present application.

Fig. 1 is an architecture diagram of a logistics inquiry system according to an embodiment of the present application, where the logistics inquiry system includes a user device 10, an API gateway device 20, an inquiry server 30, and a logistics server cluster 40. The user performs a corresponding query operation through the website or software displayed on the user equipment 10, for example, inputting a logistics list number, clicking to trigger a related function control, and the like. After detecting the query operation of the user, the user device 10 sends relevant data (such as a logistics bill number and a query type) of the query operation to the API gateway device 20; the API gateway device 20 performs single number preprocessing to generate a query request, and then sends the query request to a crawler request data preprocessing service of the query server 30; the crawler request data preprocessing service performs data format conversion on the query request, so that the query request meets the format requirement of a crawler machine in the logistics server cluster 40, and forwards the query request to the distribution service of the query server 30; the distribution service determines a crawler machine with machine parameters corresponding to the related data from the logistics server cluster 40, and then forwards the query request after data format conversion to the crawler machine; the external data source service in the crawler machine sends the corresponding target logistics data to the query server 30 according to the query request; the distribution service acquires a corresponding analysis method according to the logistics provider KEY, analyzes the target logistics data, organizes the target logistics data into a uniform data format, and then sends the target logistics data to a socket service in the query server 30; the socket service stores the target logistics data into a Redis database and a mongodb database, and then forwards the target logistics data to the API gateway device 20; the API gateway device 20 forwards the target logistics data to the user device 10; the user equipment 10 displays the target logistics data on a display screen.

Specifically, the single number preprocessing comprises the following steps:

a, filtering an unnormalized single number;

b, filtering the repeated single number;

c, filtering the single number exceeding the upper limit of the current processing;

d, acquiring logistics merchants corresponding to the single number in a cache (a single number basic information set locally pre-stored by the API gateway device 20), destination country brevity codes and delivery time;

e, if the corresponding physical distribution provider is not obtained in the cache (the cache refers to the local cache of the API gateway device 20), matching the physical distribution provider according to the single number rule (the single number rule refers to the data format of the physical distribution single numbers of different physical distribution providers, for example, the single number of international postal service includes a large packet, a small packet and EMS, such as CP123456789CN, RR123456789CN and EE123456789CN, respectively, and the single number of the third-party international physical distribution company, such as the international physical distribution single number of DHL, FEDEX, UPS, TNT, and the like);

f, marking whether the single number needs to be inquired by two sections of tracks (indicating that the logistics information of the sending country and the logistics information of the target country correspond to different inquiry website links respectively and the logistics information needs to be inquired by respective logistics merchant inquiry interfaces respectively);

g, when the API gateway device 20 inquires that the local cached data exists and the update time of the cached data does not exceed 10 minutes (the time is the self-defined requirement of the enterprise), and the logistics provider in the single number is not the logistics provider selected by the user/enterprise itself but the logistics provider configured by default in the system, the cached data is organized and returned to the foreground device.

And H, for other needing to be queried in real time, the API gateway device 20 interacts with the query server 30 to check whether the number of the crawler request data preprocessing service connections of the query server 30 reaches an upper limit, if not, a request (a track real-time query request of a target logistics single number) is sent to the service, otherwise, a system busy exception is returned.

The specific method is described in detail below.

Referring to fig. 2, the present application further provides a method for querying logistics data, applied to a query server, including:

step 201, obtaining a query request from the API gateway device for the target logistics data.

The query request is generated based on a logistics list number imported by a user at user equipment, and the target logistics data refers to logistics data corresponding to the logistics list number.

Step 202, determining the query type of the query request.

For example, the query type includes a track query, a statistical data query, a distributed data query, an order status information query, and the like, and other types of information queries may also be included, which is not limited herein.

And 203, if the query type is track query, determining the transportation type corresponding to the logistics list number.

Step 204, according to the transportation type, determining one or more corresponding first crawler servers from a logistics server cluster, wherein each first crawler server in the one or more first crawler servers stores logistics track sub-data corresponding to the transportation type.

In one possible embodiment, the transportation type includes a first transportation type and a second transportation type; the determining one or more corresponding first crawler servers from the logistics server cluster according to the transportation type includes:

if the logistics list number only comprises a first transportation type or a second transportation type, determining a first crawler server in an idle state from the logistics server cluster, wherein the idle state refers to the fact that the first obtaining request can be responded at the current moment, the first crawler server stores the first logistics track sub-data/the second logistics track sub-data, the first logistics track sub-data is logistics track sub-data corresponding to the first transportation type, and the second logistics track sub-data is logistics track value data corresponding to the second transportation type;

if the logistics list number comprises a first transportation type and a second transportation type, determining one or more first crawler servers in an idle state from the logistics server cluster; when a first crawler server is determined, the first crawler server stores the first logistics track sub-data and the second logistics track sub-data; when a plurality of first crawler servers are determined, the first logistics track sub-data and the second logistics track sub-data are respectively stored by the plurality of first crawler servers.

Illustratively, the first type of transportation includes marine and/or air transportation and the second type of transportation includes card and/or train.

For example, the transportation type may be determined by a transportation identifier, and different transportation identifiers are associated with different transportation types, and the transportation identifier may be formed by numbers and/or letters in the logistics list number or a combination of numbers and/or letters in the logistics list number, or may be other transportation identifiers, which is not limited herein.

In a specific implementation, in a cross-country logistics, different packages are different in transportation mode due to different destination countries. The destination country of some packages is in a land adjacent country, so the transportation mode can be air transportation or card navigation, and after the packages are delivered to the destination country, the packages can be transported by using card navigation or trains; some of the destination countries of the packages are separated by sea, so that the transportation mode can be sea transportation or air transportation, and the packages can be transported by using a card or a train after being delivered to the destination countries. It is understood that after the package is transported to the destination country by air or sea, the customer may directly go to the airport or port to pick up the package, and the package does not need to be transported by land transportation (card, train, etc.), and the package may be specifically selected according to the need, and is not limited herein.

Specifically, if the package corresponding to the logistics list number only includes a first transportation type, such as shipping, an IP address associated with a destination country is obtained, and the first crawler machine is determined according to the IP address.

It can be seen that, in this embodiment, different crawler machines are determined based on different transportation types, and then, targeted query on different transportation types is realized.

Step 205, sending a first obtaining request for the logistics track sub-data to each first crawler server.

Step 206, receiving the logistics track sub-data sent by the external data source service of the one or more first crawler servers to obtain one or more logistics track sub-data, and storing the one or more logistics track sub-data as target logistics data.

In one possible embodiment, the receiving the logistics track sub-data sent by the external data source service of the one or more first crawler servers includes:

if the logistics list number only comprises a first transportation type, receiving a first transportation tool identifier, a first transportation track and a first current transportation state sent by an external data source service of the first crawler server, wherein the first transportation type comprises sea transportation and/or air transportation, and the first transportation tool identifier comprises a ship number and/or a flight number;

if the logistics list number only comprises a second transportation type, receiving a second transportation tool identifier, a second transportation track and a second current transportation state which are sent by an external data source service of the first crawler server, wherein the first transportation type comprises a card boat and/or a train, and the second transportation tool identifier comprises a license plate number/a train number;

and if the logistics list number comprises a first transportation type and a second transportation type, receiving a first transportation tool identifier, a first transportation track, a first current transportation state, a second transportation tool identifier, a second transportation track and a second current transportation state sent by an external data source service of the one or more crawler servers.

For example, the first current transportation state refers to a transportation node of a first transportation process where a package corresponding to the logistics single number is currently located, and the first transportation process is a first transportation type transportation process; the second current transportation state refers to a transportation node of a second transportation process where the package corresponding to the logistics single number is currently located, and the second transportation process is a transportation process of a second transportation type.

For example, the logistics track sub-data includes, but is not limited to, a vehicle identification, a transportation track, and a current transportation status, and the transportation track includes, but is not limited to, a coordinate signal and track information of a vehicle.

In specific implementation, the transportation processes of different transportation types are different, so that different logistics track sub-data can be received for each transportation type. When the transportation of the package needs multiple transportation types, corresponding logistics track subdata needs to be obtained from multiple logistics merchants, namely the logistics track subdata is obtained from multiple first crawler servers, and then multiple logistics track subdata is obtained.

It can be seen that, in this embodiment, based on different transportation types, corresponding logistics track subdata is obtained from different crawler servers, and then accurate obtaining of logistics track subdata is achieved.

And step 207, sending the target logistics data to the API gateway equipment.

The one or more logistics track sub-data are used for providing an indication for the API gateway device to forward the one or more logistics track sub-data to the user equipment, and providing an indication for the user equipment to draw a transportation track broken line and a transportation node on a map.

In a possible embodiment, after receiving the target logistics data, the API gateway device caches part or all of the data in the target logistics data, and if the user performs the same query again within a preset time, the API gateway device directly obtains corresponding target cache data from the cache in the API gateway and sends the target cache data to the user equipment, thereby improving the query efficiency.

In one possible embodiment, the query type comprises a statistical data query; after the logistics track data is sent to the API gateway device, the method further includes:

if the query type is the statistical data query, determining one or more corresponding second crawler servers from the logistics server cluster, wherein each second crawler server in the one or more second crawler servers stores statistical data, the statistical data comprises aging data, the aging data comprises logistics provider aging data and/or national aging data, the logistics provider aging is the first average time length for a logistics provider to transport packages, and the national aging is the second average time length from a delivery country to a destination country;

sending a second acquisition request for the logistics provider aging data and/or the country aging data to the one or more second crawler servers;

receiving the logistics provider aging data and/or the country aging data sent by the external data source service of the one or more second crawler servers to obtain one or more logistics provider aging data and/or country aging data, and storing the one or more logistics provider aging data and/or country aging data as the target logistics data;

and sending the target logistics data to the API gateway equipment, wherein one or more logistics provider aging data and/or national aging data are used for providing an indication for displaying a logistics provider aging statistical table and/or a national aging statistical table on a display sub-window for the user equipment, the logistics provider aging statistical table comprises the logistics provider aging data, the national aging statistical table comprises the national aging data, the logistics provider aging statistical table is used for displaying the logistics provider, the first transportation package quantity and the first average time length corresponding to the logistics provider, and the national aging statistical table is used for displaying the target country, the second transportation package quantity and the second average time length corresponding to the target country.

In specific implementation, in order to enable a user to better understand a logistics merchant or a destination country for the user to refer when selecting a logistics merchant, or for logistics merchant summary, etc., the embodiment provides statistical data query. The statistical data comprise aging data, if the query type input by the user is statistical data query, the second crawler server is determined, and corresponding logistics merchant aging data and/or national aging data are/is obtained from the second crawler server; and then the information is sent to the user equipment through the API gateway equipment to display a corresponding logistics merchant aging statistical table and/or a corresponding country aging statistical table.

Specifically, if the statistical data query is a query only for the logistics provider aging data, the logistics provider aging data is only acquired from a second crawler server storing the logistics provider aging data; similarly, if the statistical data query is a query only for the national aging data, the national aging data is only acquired from a second crawler server storing the national aging data. In addition, the logistics merchant aging data and the country aging data can be acquired from the two second crawler servers at the same time.

It can be seen that, in this embodiment, for the statistical data query, the corresponding statistical data is acquired from the crawler server storing the corresponding statistical data, so that the query of the statistical data such as the aging statistical table is realized, and the logistics query types are enriched.

In one possible embodiment, the query type further includes a distribution data query; after the sending of the logistics track data to the API gateway device, the method further includes:

if the query type is the distribution data query, determining one or more corresponding third crawler servers from the logistics server cluster, wherein the one or more third crawler servers store distribution data, the distribution data comprises single number country distribution data, and the single number country distribution refers to the distribution condition of the single number stored in the database in a plurality of destination countries;

sending a third acquisition request aiming at the single number country distribution data to one or more third crawler servers;

receiving the single number country distribution data sent by an external data source service of the one or more third crawler servers to obtain one or more single number country distribution data, and storing the one or more single number country distribution data as the target logistics data;

and sending the target logistics data to the user equipment, wherein the single country distribution data is used for providing an indication for the user equipment to display a single country distribution statistical table on a display sub-window, and the single country distribution statistical table is used for displaying the single country distribution.

In a specific implementation, in order to assist a user in knowing about a main business of a logistics provider, the embodiment provides a logistics list number distribution data query of the logistics provider. The distribution data comprises single country distribution data, which reflects the distribution situation of the logistics single number of each logistics provider in each country, and further obtains the business layout situation of each logistics provider in each country.

It can be seen that, in this embodiment, by obtaining the single country distribution statistical table of the logistics single number of the logistics provider in each country, the service layout condition of each logistics provider in each country is provided for the user, which is helpful for the user to accurately select the logistics provider.

In a possible embodiment, after the sending the target logistics data to the API gateway device, the method further includes:

if the query type is the query of order state information, determining the order type corresponding to the logistics order number;

acquiring a transportation process corresponding to the order type, wherein the transportation process comprises a plurality of transportation nodes;

determining the current transport node of the logistics list number from the plurality of transport nodes;

determining one or more corresponding fourth crawler servers from the logistics server cluster according to the transportation nodes;

sending a fourth acquisition request aiming at the order state information to the one or more fourth crawler servers;

receiving order state information sent by an external data source service of the one or more fourth crawler servers, and storing the order state information as the target logistics data;

and sending the target logistics data to the user equipment, wherein the order state information is used for providing an indication for the user equipment to display the order state information in a display sub-window.

Specifically, in the logistics industry, there are multiple order types, and the transportation process of each of the multiple order types is different. As shown in fig. 3, fig. 3 is a schematic diagram of a transportation flow of four order types, wherein the exporter's total package cross-border transportation flow is: order reception → total head journey transportation → export customs → trunk transportation → import clearance → tail Cheng Peisong; the overseas warehouse-out cross-border transportation flow comprises the following steps: order reception → warehouse-out execution → transit execution → export customs → trunk transportation → import clearance → tail Cheng Peisong; the cross-border transport flow from the consignment to the warehouse is as follows: order reception → sign-in for a warehouse → transit execution → exit customs → trunk transportation → entry clearance → tail Cheng Peisong; the generation of the delivery cross-border transport stream is as follows: order reception → production planning → production execution → head journey transportation → transit execution → export customs → trunk transportation → import clearance → tail Cheng Peisong.

In a specific implementation, when the query type input by the user is an order state information query, it indicates that the user needs to know the current state of the package corresponding to the logistics order number, and therefore, the order type of the logistics order needs to be determined first, a corresponding transportation process needs to be determined according to the order type, and then order state information corresponding to the current transportation node is obtained from one or more fourth crawler servers.

It can be seen that, in the embodiment, the query of the order state information is realized.

The embodiment of the application further provides a logistics data query method, which is applied to user equipment, and the method comprises the following steps:

sending the logistics list number and the query type to API gateway equipment;

receiving target logistics data sent by the API gateway equipment; when the query type is track query, the target logistics data comprise one or more logistics track sub-data, and the one or more logistics track sub-data are respectively stored in one or more first crawler servers in a logistics server cluster; the logistics list number is used for providing an indication for determining the transportation type of the logistics list number for the query server; the transportation type is used for providing an instruction for the query server to acquire the one or more logistics track subdata from the one or more first crawler servers and send the one or more logistics track subdata to the API gateway equipment;

In the specific implementation, when a user needs to inquire logistics data, the user logs in an inquiry website or software maintained by the logistics inquiry system, inputs a corresponding logistics single number and an inquiry type in a user interface of the website or software, then sends the input logistics single number and the inquiry type to the API gateway equipment, performs corresponding single number preprocessing by the API gateway equipment, further generates an inquiry request, and finally receives target logistics data fed back by an inquiry server side by the API gateway equipment and sends the target logistics data to the user equipment, and the user equipment displays the target logistics data, so that the user can check the logistics data to be inquired.

It can be seen that, in this embodiment, a logistics list number and an inquiry type input by a user are obtained through user equipment, an inquiry request is generated by API gateway equipment according to the logistics list number and the inquiry type, if the inquiry server determines that the inquiry type is track inquiry, a transportation type corresponding to the logistics list number is further determined, a corresponding logistics track subdata obtaining operation is executed according to the transportation type, the logistics track subdata is obtained from a logistics server cluster as target logistics data, and finally the target logistics data is returned to the user equipment through the inquiry server and the API gateway equipment, and the user equipment displays corresponding logistics information according to the target logistics data. In this way, one-stop type inquiry of different transportation tracks based on the transportation types is realized.

The embodiment of the present application further provides a method for querying logistics data, which is applied to API gateway equipment, and the method includes:

generating a query request aiming at target logistics data according to the logistics list number and the query type, wherein the target logistics data refers to the logistics data corresponding to the logistics list number;

sending the query request to a query server;

In the concrete implementation, when API gateway equipment receives a logistics list number and an inquiry type sent by user equipment, a logistics provider corresponding to the logistics list number is obtained in a cache of the equipment, a corresponding list number rule is matched according to the logistics provider, then the matched logistics provider and list number rule, the logistics list number and the inquiry type are together generated into an inquiry request, the inquiry request is sent to an inquiry server, the inquiry server obtains target logistics data from a crawler server corresponding to a logistics server cluster, then the target logistics data are returned to the API gateway equipment, and the API gateway equipment forwards the target logistics data to the user equipment for display.

It can be seen that, in this embodiment, a logistics list number and an inquiry type input by a user are obtained by user equipment, an inquiry request is generated by API gateway equipment according to the logistics list number and the inquiry type, if the inquiry type is determined by an inquiry server as track inquiry, a transportation type corresponding to the logistics list number is further determined, a corresponding logistics track subdata obtaining operation is executed according to the transportation type, the logistics track subdata is obtained from a logistics server cluster as target logistics data, and is finally returned to the user equipment through the inquiry server and the API gateway equipment in sequence, and the user equipment displays corresponding logistics information according to the target logistics data. In this way, one-stop inquiry of different transportation tracks based on the transportation type is realized.

In a possible embodiment, if it is determined according to a single number rule that the logistics single number can obtain a complete logistics track only if the logistics single number needs to be queried by a plurality of logistics providers, obtaining logistics track sub-data from sixth crawlers corresponding to the logistics providers respectively to obtain a plurality of logistics track sub-data; and then sending the data to user equipment, and the user equipment combines the plurality of logistics track sub-data of the same logistics list number and displays the data on a track graph by using a complete logistics track. The logistics track sub-data comprises head pass data and tail pass data.

It can be seen that, in this embodiment, the logistics track splicing function is realized by merging and displaying the logistics track sub-data of different logistics merchants.

The embodiment of the application also provides a user interface of the user equipment, which is characterized in that the user equipment comprises a display screen, the user interface is displayed on the display screen, and the user interface is a software interface; the user interface is controlled by inputting a touch instruction through the display screen by a user, or the user controls the user interface by inputting a control instruction through an input device by the user;

and when the logistics list number and the query type are input into the input boxes, if a click operation aiming at the query control is received, jumping from the initial interface to a display sub-interface corresponding to the query type.

In a specific implementation, a user inputs a corresponding touch instruction through interaction with an initial interface in the user interface, for example, inputs a logistics list number and a query type from a control such as an input box/a selection box, and after receiving target logistics data returned by the API gateway device, jumps to a query result display interface to display a corresponding query result.

As shown in fig. 4, the inquiry result display interface displays a logistics list number, a list number status (e.g., "in transit" in the figure), a logistics provider (e.g., "XX logistics provider" in the figure), basic information, transportation information, planning actions, a transportation flow 401, and the like. The basic information is package information corresponding to the logistics list number, and as shown in fig. 4, the transportation type of the package is marine transportation, so the basic information includes a receiving location, a loading port, a discharging port, a delivery location, a database address, a service mode, a container number, a gross weight, a volume, a list number, a predicted shipment date, a VGM expiration date, and an expiration date (arrival date). The container information includes container number, size/type, lead seal number, service type, quantity, mode, VGM, current status and date. The planning actions include the projected arrival date, location, and projected arrival vessel/voyage. The transportation flow 401 includes a plurality of transportation nodes, and the current transportation node is highlighted. In addition, the query result display interface further comprises controls such as a copy link, a copy result and a track translation, the copy link control can copy the link of the query result display page, the copy result control can copy all contents in the query result display page, and the track translation can display a track graph according to the query result.

It can be seen that, in the embodiment, the target logistics data is displayed in the query result display interface, so that the user can overview the logistics information and can display the track map, the visualization degree of query is improved, and the viewing efficiency of the logistics information is improved.

The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It will be appreciated that the mobile electronic device, in order to carry out the above-described functions, comprises corresponding hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. 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 application.

In the embodiment of the present application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Referring to fig. 5, the present application further provides a logistics data query device 50, applied to a query server, including:

an obtaining unit 51, configured to obtain an inquiry request for target logistics data from an API gateway device, where the inquiry request is generated based on a logistics single number imported by a user at a user device, and the target logistics data is logistics data corresponding to the logistics single number;

a determining unit 52, configured to determine a query type of the query request; when the query type is track query, determining the transportation type corresponding to the logistics single number; determining one or more corresponding first crawler servers from a logistics server cluster according to the transportation type, wherein each first crawler server in the one or more first crawler servers stores logistics track sub data corresponding to the transportation type;

a first sending unit 53, configured to send a first obtaining request for the logistics track sub-data to each first crawler server;

a receiving unit 54, configured to receive the logistics track sub-data sent by the external data source service of the one or more first crawler servers, to obtain one or more logistics track sub-data, and store the one or more logistics track sub-data as target logistics data;

a second sending unit 55, configured to send the target logistics data to the API gateway device, where the one or more logistics track sub-data are used to provide, for the API gateway device, an instruction to forward the one or more logistics track sub-data to the user equipment, and provide, for the user equipment, an instruction to draw a transportation track broken line and a transportation node on a map.

It can be seen that, in this embodiment, first, an inquiry request for target logistics data from the API gateway device is obtained; then determining the query type of the query request; if the query type is track query, determining a transportation type corresponding to the logistics single number; determining one or more corresponding first crawler servers from a logistics server cluster according to the transportation type, wherein each first crawler server in the one or more first crawler servers stores logistics track sub data corresponding to the transportation type; sending a first acquisition request aiming at the logistics track sub-data to each first crawler server; then receiving the logistics track sub-data sent by an external data source service of the one or more first crawler servers to obtain one or more logistics track sub-data, and storing the one or more logistics track sub-data as target logistics data; and sending the target logistics data to the API gateway equipment, wherein user equipment displays the target logistics data. In this way, one-stop type inquiry of different transportation tracks based on the transportation types is realized.

In one possible embodiment, the transport type includes a first transport type and a second transport type; in the aspect of determining one or more corresponding first crawler servers from the logistics server cluster according to the transportation type, the determining unit 52 is specifically configured to:

if the logistics list number comprises a first transportation type and a second transportation type, determining one or more first crawler servers in an idle state from the logistics server cluster; when a first crawler server is determined, the first crawler server stores the first logistics track subdata and the second logistics track subdata; when a plurality of first crawler servers are determined, the first logistics track sub-data and the second logistics track sub-data are respectively stored by the plurality of first crawler servers.

In a possible embodiment, in terms of receiving the logistics track sub-data sent by the external data source service of the one or more first crawler servers, the receiving unit 54 is specifically configured to:

In one possible embodiment, the query type comprises a statistical data query; after sending the logistics track data to the API gateway device, the apparatus further includes:

the determining unit 52 is further configured to determine, when the query type is the statistical data query, one or more corresponding second crawler servers from the logistics server cluster, where each second crawler server in the one or more second crawler servers stores statistical data, the statistical data includes aging data, the aging data includes logistics provider aging data and/or national aging data, the logistics provider aging is a first average duration of package transportation by a logistics provider, and the national aging is a second average duration of a delivery country to a destination country;

the first sending unit 53 is further configured to send a second obtaining request for the logistics provider aging data and/or the country aging data to the one or more second crawler servers;

the receiving unit 54 is further configured to receive the logistics provider aging data and/or the country aging data sent by the external data source service of the one or more second crawler servers, obtain one or more logistics provider aging data and/or the country aging data, and store the one or more logistics provider aging data and/or the country aging data as the target logistics data;

the second sending unit 55 is further configured to send the target logistics data to the API gateway device, where the one or more logistics provider aging data and/or country aging data are used to provide an indication for the user device to display a logistics provider aging statistical table and/or a country aging statistical table on a display sub-window, the logistics provider aging statistical table includes the logistics provider aging data, the country aging statistical table is used to display the logistics provider, the first transportation package quantity and the first average duration corresponding to the logistics provider, and the country aging statistical table is used to display the destination country, the second transportation package quantity and the second average duration corresponding to the destination country.

In one possible embodiment, the query type further comprises a distributed data query; after the sending of the logistics track data to the API gateway device, the method further includes:

the determining unit 52 is further configured to determine, when the query type is the distribution data query, one or more corresponding third crawler servers from the logistics server cluster, where the one or more third crawler servers store distribution data, where the distribution data includes single country distribution data, and the single country distribution refers to a distribution condition of a single number stored in the database in multiple destination countries;

the first sending unit 53 is further configured to send a third obtaining request for the single country distribution data to the one or more third crawler servers;

the receiving unit 54 is further configured to receive the single number country distribution data sent by the external data source service of the one or more third crawler servers, obtain one or more single number country distribution data, and store the one or more single number country distribution data as the target logistics data;

the second sending unit 55 is further configured to send the target logistics data to the user equipment, where the country distribution data of the single number is used to provide an indication for the user equipment to display a country distribution statistical table of the single number in a display sub-window, and the country distribution statistical table of the single number is used to display the country distribution of the single number.

In a possible embodiment, after sending the target logistics data to the API gateway device, the method further includes:

the determining unit 52 is further configured to determine an order type corresponding to the logistics order number when the query type is an order state information query; determining the current transport node of the logistics list number from the plurality of transport nodes; determining one or more corresponding fourth crawler servers from the logistics server cluster according to the transportation nodes;

the obtaining unit 51 is further configured to obtain a transportation process corresponding to the order type, where the transportation process includes a plurality of transportation nodes;

the first sending unit 53 is further configured to send a fourth obtaining request for the order status information to the one or more fourth crawler servers;

the receiving unit 54 is further configured to receive order state information sent by an external data source service of the one or more fourth crawler servers, and store the order state information as the target logistics data;

the second sending unit 55 is further configured to send the target logistics data to the user equipment, where the order status information is used to provide an indication for the user equipment to display the order status information in a display sub-window.

Referring to fig. 6, the present application further provides a logistics data query apparatus 60, applied to a user equipment, where the method includes:

an obtaining unit 61, configured to obtain a logistics list number and a query type that are input by a user through an input box, where the logistics list number and the query type are used to provide an instruction for generating a query request for the API gateway device, the query request is used to provide an instruction for a query server to obtain target logistics data from a corresponding first crawler server, the target logistics data is logistics data corresponding to the logistics list number, and the query type includes track query;

a sending unit 62, configured to send the logistics list number and the query type to an API gateway device;

a receiving unit 63, configured to receive target logistics data sent by the API gateway device; when the query type is track query, the target logistics data comprise one or more logistics track subdata, and the one or more logistics track subdata are respectively stored in one or more first crawler servers in a logistics server cluster; the logistics list number is used for providing an indication for determining the transportation type of the logistics list number for the query server; the transportation type is used for providing an instruction for the query server to acquire the one or more logistics track subdata from the one or more first crawler servers and send the one or more logistics track subdata to the API gateway equipment;

and the drawing unit 64 is configured to draw a logistics track broken line and a transportation node in a map of a display interface based on the one or more logistics track sub-data, so as to obtain a logistics track map corresponding to the logistics single number.

Referring to fig. 7, the present application further provides a logistics data query apparatus 70, applied to an API gateway device, where the method includes:

a first receiving unit 71, configured to receive a logistics list number and an inquiry type from the user equipment, where the inquiry type includes a track inquiry;

a generating unit 72, configured to generate a query request for target logistics data according to the logistics list number and the query type, where the target logistics data is logistics data corresponding to the logistics list number;

a first sending unit 73, configured to send the query request to a query server;

a second receiving unit 74, configured to receive the target logistics data from the query server, where when the query type is track query, the target logistics data includes one or more logistics track sub-data, and the one or more logistics track sub-data are respectively stored in one or more first crawler servers in a logistics server cluster; the logistics list number is used for providing an indication for determining the transportation type of the logistics list number for the query server; the transportation type is used for providing an instruction for the query server to acquire the one or more logistics track subdata from the one or more first crawler servers and send the one or more logistics track subdata to the API gateway equipment;

a second sending unit 75, configured to send the target logistics data to the user equipment, where the one or more logistics track sub-data are used to provide, to the user equipment, an instruction for drawing a transportation track broken line and a transportation node on a map.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

The present application also provides an electronic device 80, as shown in fig. 8, that includes at least one processor (processor) 81; a display screen 82; and a memory (memory) 83, and may further include a communication Interface (Communications Interface) 85 and a bus 84. The processor 81, the display 82, the memory 83 and the communication interface 85 can communicate with each other through the bus 84. The display screen 82 is configured to display a user guidance interface preset in the initial setting mode. The communication interface 85 may transmit information. The processor 81 may call logic instructions in the memory 83 to perform the method in the above embodiment.

Optionally, the electronic device 80 may be a mobile electronic device, an electronic device or other devices, and is not limited herein.

In addition, the logic instructions in the memory 83 may be implemented in the form of software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products.

The memory 83 is a computer-readable storage medium and can be configured to store software programs, computer-executable programs, such as program instructions or modules corresponding to the methods in the embodiments of the present disclosure. The processor 81 executes functional applications and data processing by executing software programs, instructions or modules stored in the memory 83, that is, implements the methods in the above-described embodiments.

The memory 83 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the electronic device 80, and the like. Further, the memory 83 may include a high-speed random access memory, and may also include a nonvolatile memory. For example, a variety of media that can store program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, may also be transient storage media.

Embodiments of the present application further provide a computer storage medium, where the computer storage medium stores a computer program for electronic data exchange, the computer program enables a computer to execute part or all of the steps of any one of the methods as described in the above method embodiments, and the computer includes an electronic device.

Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods as described in the above method embodiments. The computer program product may be a software installation package, the computer comprising an electronic device.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus and system may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative; for example, the division of the unit is only a logic function division, and there may be another division manner in actual implementation; for example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and 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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately and physically included, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: u disk, removable hard disk, magnetic disk, optical disk, volatile memory or non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM). And the like, which may store program code.

Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications can be easily made by those skilled in the art without departing from the spirit and scope of the present invention, and it is within the scope of the present invention to include different functions, combination of implementation steps, software and hardware implementations.

Claims

1. A logistics data query method is applied to a query server and comprises the following steps:

determining a query type of the query request;

2. The method of claim 1, wherein the transportation type comprises a first transportation type and a second transportation type; the determining one or more corresponding first crawler servers from the logistics server cluster according to the transportation type includes:

3. The method of claim 2, wherein receiving the logistics track sub-data sent by an external data source service of the one or more first crawler servers comprises:

if the logistics list number only comprises a second transportation type, receiving a second transportation tool identifier, a second transportation track and a second current transportation state which are sent by an external data source service of the first crawler server, wherein the first transportation type comprises a card navigation and/or a train, and the second transportation tool identifier comprises a license plate number/a train number;

4. The method of any of claims 1-3, wherein the query type comprises a statistical data query; after the logistics track data is sent to the API gateway device, the method further includes:

if the query type is the statistical data query, determining one or more corresponding second crawler servers from the logistics server cluster, wherein each second crawler server in the one or more second crawler servers stores statistical data, the statistical data comprises aging data, the aging data comprises logistics merchant aging data and/or national aging data, the logistics merchant aging is the first average duration of the logistics merchant transporting the packages, and the national aging is the second average duration from the delivery country to the destination country;

receiving the logistics merchant aging data and/or the country aging data sent by the external data source service of the one or more second crawler servers to obtain one or more logistics merchant aging data and/or the country aging data, and storing the one or more logistics merchant aging data and/or the country aging data as the target logistics data;

5. The method of any of claims 1-3, wherein the query type further comprises a distributed data query; after the logistics track data is sent to the API gateway device, the method further includes:

receiving the single number country distribution data sent by the external data source service of the one or more third crawler servers to obtain one or more single number country distribution data, and storing the one or more single number country distribution data as the target logistics data;

and sending the target logistics data to the user equipment, wherein the single country distribution data is used for providing an indication for displaying a single country distribution statistical table on a display sub-window for the user equipment, and the single country distribution statistical table is used for displaying the single country distribution.

6. The method of any of claims 1-3, wherein after sending the target logistics data to the API gateway device, the method further comprises:

determining the current transportation node of the logistics single number from the plurality of transportation nodes;

determining one or more corresponding fourth crawler servers from the logistics server cluster according to the transportation node;

7. A logistics data query method is applied to user equipment, and the method comprises the following steps:

acquiring a logistics list number and an inquiry type input by a user through an input box, wherein the logistics list number and the inquiry type are used for providing an instruction for generating an inquiry request for the API gateway device, the inquiry request is used for providing an instruction for an inquiry server to acquire target logistics data from a corresponding first crawler server, the target logistics data are logistics data corresponding to the logistics list number, and the inquiry type comprises track inquiry;

sending the logistics list number and the query type to API gateway equipment;

8. A logistics data query method is applied to API gateway equipment, and the method comprises the following steps:

sending the query request to a query server;

9. The user interface of the user equipment is characterized in that the user equipment comprises a display screen, the user interface is displayed on the display screen, and the user interface is a software interface; the user interface is controlled by inputting a touch instruction through the display screen by a user, or the user controls the user interface by inputting a control instruction through an input device by the user;

10. An electronic device comprising a processor, memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps in the method of any of claims 1-6.

11. A computer-readable storage medium, characterized by storing a computer program for electronic data exchange, wherein the computer program causes a computer to execute instructions of the steps in the method according to any one of claims 1-6.