CN111695713B

CN111695713B - Historical track data processing method and device

Info

Publication number: CN111695713B
Application number: CN201910185878.XA
Authority: CN
Inventors: 李思宇; 孙伟力; 刘兵兵
Original assignee: Beijing Didi Infinity Technology and Development Co Ltd
Current assignee: Beijing Didi Infinity Technology and Development Co Ltd
Priority date: 2019-03-12
Filing date: 2019-03-12
Publication date: 2023-09-15
Anticipated expiration: 2039-03-12
Also published as: CN111695713A

Abstract

The application discloses a method and a device for processing historical track data, which can accurately, rapidly and flexibly acquire the historical track data and can more accurately analyze the historical track data. The historical track data processing method comprises the following steps: acquiring historical driving state information and historical order information uploaded by at least one terminal, wherein the historical order information comprises an order identifier; matching the historical driving state information and the historical order information corresponding to each terminal, and constructing a first database storing the mapping relation between the order identification of each historical order and the matched historical driving state information; when a query request carrying a first target order mark sent by a request end is received, historical driving state information matched with the first target order mark is obtained from a first database, and the obtained historical driving state information is sent to the request end.

Description

Historical track data processing method and device

Technical Field

The application relates to the technical field of data analysis, in particular to a historical track data processing method and device.

Background

In order to optimize urban traffic, urban traffic data such as traffic running trend, congestion occurrence position, traffic flow of different areas and the like are obtained through analysis, and vehicle history track data in a specified time range and a specified space range are required to be obtained. Because the data volume of the historical track data of the vehicle is large, the prior art lacks means for combining the historical track information of the vehicle with the travel condition, so that the historical track data of the vehicle cannot be accurately, rapidly and flexibly obtained, and further the historical track data of the vehicle cannot be accurately analyzed.

Disclosure of Invention

Accordingly, an object of the embodiments of the present application is to provide a method and an apparatus for processing historical track data, which can accurately, rapidly and flexibly obtain historical track data, so that the historical track data can be analyzed more accurately.

In a first aspect, an embodiment of the present application provides a method for processing historical track data, including:

acquiring historical driving state information and historical order information uploaded by at least one terminal, wherein the historical order information comprises an order identifier;

matching the historical driving state information corresponding to each terminal with the historical order information to obtain historical driving state information matched with each historical order executed by each terminal;

Constructing a first database storing the mapping relation between the order identification of each historical order and the matched historical driving state information;

when a query request carrying a first target order mark sent by a request end is received, acquiring historical driving state information matched with the first target order mark from a first database, and sending the acquired historical driving state information to the request end.

In a possible embodiment, the historical driving status information includes: the position coordinates of each track point and the time of passing each track point;

the historical order information further includes: the start time and end time of the historical order.

In a possible implementation manner, after acquiring the historical driving state information and the historical order information uploaded by at least one terminal, the method further comprises:

determining a road section identifier matched with each historical order according to the position coordinates of each track point included in the historical driving state information matched with each historical order;

a second database is constructed storing an order identification for each historical order and a road segment identification that matches each historical order.

In a possible embodiment, the method further comprises:

When a query request carrying a target road section identifier sent by a request end is received, a second target order identifier matched with the target road section identifier is acquired from the second database;

and acquiring historical driving state information matched with the second target order mark from the first database, and transmitting the acquired historical driving state information to the request end.

determining a time identifier matched with each historical order according to the time passing through each track point included in the historical driving state information matched with each historical order;

a third database is constructed storing an order identification for each historical order and a time identification that matches each historical order.

In a possible embodiment, the method further comprises:

when a query request carrying a target time identifier sent by a request end is received, a third target order identifier matched with the target time identifier is obtained from the third database;

and acquiring historical driving state information matched with the third target order mark from the first database, and transmitting the acquired historical driving state information to the request end.

In a possible implementation manner, the matching the historical driving state information corresponding to each terminal with the historical order information to obtain the historical driving state information matched with each historical order executed by each terminal includes:

dividing the historical driving state information falling into a time range of the starting time and the ending time of the same historical order into the same driving state information set according to the time passing through each track point and included in the historical driving state information corresponding to each terminal, wherein each historical order corresponds to one driving state information set;

the construction of a first database storing the mapping relation between the order identification of each historical order and the matched historical driving state information comprises the following steps:

a first database storing a mapping relationship between an order identification of each historical order and a corresponding running state information set is constructed.

In a second aspect, an embodiment of the present application further provides a method for processing historical track data, including:

acquiring historical driving state information with at least one target order mark matched respectively, wherein the historical driving state information comprises at least one of the following information: position coordinates of each track point, time of passing each track point, speed of passing each track point;

Determining historical driving state characteristics based on the historical driving state information corresponding to each target order mark;

wherein the historical driving state characteristics include at least one of the following characteristic information:

the starting point position and/or the ending point position of any one target order;

traffic flow information for any one of the target location areas;

traffic speed information of any one target position area;

and passing time information of any target position area.

In a possible implementation manner, obtaining the historical driving state information with at least one target order identifier respectively matched with the target order identifiers includes:

sending a first query request carrying the at least one target order identifier to a server;

and receiving the historical driving state information which is transmitted by the server and is matched with the at least one target order mark respectively.

sending a second query request carrying at least one target road section identifier to a server;

receiving order identifiers which are respectively matched with the at least one target road section identifier and are sent by the server;

Selecting at least one target order identifier from the received order identifiers;

sending a third query request carrying at least one selected target order identifier to a server;

and receiving the historical driving state information which is transmitted by the server and is respectively matched with the selected at least one target order mark.

sending a fourth query request carrying at least one target time identifier to a server;

receiving order identifiers which are respectively matched with the at least one target time identifier and are sent by the server;

sending a fifth query request carrying at least one selected target order identifier to a server;

In a third aspect, an embodiment of the present application further provides a historical track data processing apparatus, including:

the acquisition module is used for acquiring the historical driving state information and the historical order information uploaded by the at least one terminal, wherein the historical order information comprises an order identifier;

The matching module is used for matching the historical driving state information corresponding to each terminal with the historical order information to obtain historical driving state information matched with each historical order executed by each terminal;

the first construction module is used for constructing a first database storing the mapping relation between the order identification of each historical order and the matched historical driving state information;

the query module is used for acquiring the historical driving state information matched with the first target order mark from the first database when receiving a query request carrying the first target order mark and sent by the request end, and sending the acquired historical driving state information to the request end.

In one possible design, the historical driving status information includes: the position coordinates of each track point and the time of passing each track point;

In one possible design, the apparatus further comprises:

the second construction module is used for determining the road section identification matched with each historical order according to the position coordinates of each track point included in the historical driving state information matched with each historical order; and is further configured to construct a second database storing an identification of road segments for which the order identification of each of the historical orders matches each of the historical orders.

In a possible design, the query module is further configured to obtain, when receiving a query request carrying a target road section identifier sent by a request end, a second target order identifier matched with the target road section identifier from the second database;

In one possible design, the apparatus further comprises:

the third construction module is used for determining a time identifier matched with each historical order according to the time passing through each track point included in the historical driving state information matched with each historical order; and is further configured to construct a third database storing time identifiers for each of the historical orders for which the order identifier matches each of the historical orders.

In a possible design, the query module is further configured to obtain, when receiving a query request carrying a target time identifier sent by a request end, a third target order identifier matched with the target time identifier from the third database;

In a possible design, the matching module is specifically configured to divide, according to a time passing through each track point included in the historical driving state information corresponding to each terminal, the historical driving state information that falls within a time range of a start time and a stop time of the same historical order into the same driving state information set, where each historical order corresponds to one driving state information set;

the first construction module is further configured to construct a first database storing a mapping relationship between an order identifier of each historical order and a corresponding running state information set.

In a fourth aspect, an embodiment of the present application further provides a historical track data processing apparatus, including:

the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring historical driving state information with at least one target order mark matched with the target order mark respectively, and the historical driving state information comprises at least one of the following information: position coordinates of each track point, time of passing each track point, speed of passing each track point;

the characteristic determining module is used for determining the characteristic of the historical driving state based on the historical driving state information corresponding to each target order mark;

traffic flow information for any one of the target location areas;

traffic speed information of any one target position area;

and passing time information of any target position area.

In one possible design, the acquiring module is specifically configured to:

In one possible design, the acquiring module is further configured to:

sending a second query request carrying the at least one target road section identifier to a server;

In one possible design, the acquiring module is further configured to:

sending a fourth query request carrying the at least one target time identifier to a server;

In a fifth aspect, an embodiment of the present application provides an electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the historical track data processing method of the first aspect, or any of the possible implementation manners of the first aspect, when executed.

In a sixth aspect, an embodiment of the present application provides an electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the method of processing historical trace data in the second aspect or any one of the possible embodiments of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor performs the steps of the method for processing historical track data in any one of the possible implementations of the first aspect or the first aspect, and/or performs the steps of the method for processing historical track data in any one of the possible implementations of the second aspect or the second aspect.

According to the historical track data processing method and device, the historical driving state information and the historical order information acquired from each terminal are matched, a first database storing the mapping relation between the order identification of each historical order and the matched historical driving state information is constructed, the historical driving state information can be queried through the target order identification, and further the historical driving state characteristics can be obtained through analysis of the historical driving state information. By matching the historical driving state information with the historical order information, the historical track information of the vehicle is combined with the travel situation, so that the historical track data can be acquired more accurately, rapidly and flexibly, and the historical track data can be analyzed more accurately.

Further, in the embodiment of the present application, when a query request carrying a target road section identifier or a target time identifier sent by a request end is received, a second target order identifier matched with the target road section identifier is obtained from a second database, or a third target order identifier matched with the target time identifier is obtained from a third database, and according to the second target order identifier or the third target order identifier, historical driving state information matched with the second target order identifier or the third target order identifier is obtained from a first database, so that historical track data of a specified time range or a specified space range can be obtained more accurately, rapidly and flexibly, and the historical track data can be analyzed more accurately.

In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 shows a schematic diagram of a possible application scenario provided by an embodiment of the present application;

FIG. 2 is a flowchart of a method for processing historical track data according to an embodiment of the present application;

FIG. 3 is a flowchart of another historical track data processing method according to an embodiment of the application;

FIG. 4 is a schematic diagram of a historical track data processing apparatus according to an embodiment of the present application;

FIG. 5 is a schematic diagram of another historical track data processing apparatus according to an embodiment of the present application;

fig. 6 shows a schematic structural diagram of an electronic device according to an embodiment of the present application;

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

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for the purpose of illustration and description only and are not intended to limit the scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. A flowchart, as used in this disclosure, illustrates operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be implemented out of order and that steps without logical context may be performed in reverse order or concurrently. Moreover, one or more other operations may be added to or removed from the flow diagrams by those skilled in the art under the direction of the present disclosure.

In addition, the described embodiments are only some, but not all, embodiments of the application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.

In order to enable those skilled in the art to make and use the present disclosure, the following embodiments are presented in connection with a specific application scenario "network about car system". It will be apparent to those having ordinary skill in the art that the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the application. While the application is primarily described in the context of a net restraint system, it should be understood that this is but one exemplary embodiment. The application can be applied to any other traffic type

It should be noted that the term "comprising" will be used in embodiments of the application to indicate the presence of the features stated hereafter, but not to exclude the addition of other features.

The terms "passenger," "requestor," "attendant," "service requestor," and "customer" are used interchangeably herein to refer to a person, entity, or tool that may request or subscribe to a service. The terms "driver," "provider," "service provider," and "provider" are used interchangeably herein to refer to a person, entity, or tool that can provide a service. The term "user" in the present application may refer to a person, entity or tool requesting, subscribing to, providing or facilitating the provision of a service. For example, the user may be a passenger, driver, operator, etc., or any combination thereof. In the present application, "passenger" and "passenger terminal" may be used interchangeably, and "driver" and "driver terminal" may be used interchangeably.

The term "order" in the present application may refer to a request initiated by a passenger, a service requester, a driver, a service provider, a vendor, etc., or any combination thereof. The "order" may be received by a passenger, a service requester, a driver, a service provider, a vendor, or the like, or any combination thereof.

The positioning techniques used in the present application may be based on global positioning system (Global Positioning System, GPS), global navigation satellite system (Global Navigation Satellite System, GLONASS), COMPASS navigation system (COMPASS), galileo positioning system, quasi-zenith satellite system (Quasi-Zenith Satellite System, QZSS), wireless fidelity (Wireless Fidelity, wiFi) positioning techniques, or the like, or any combination thereof. One or more of the above-described positioning systems may be used interchangeably in the present application.

In urban traffic, the historical track data of vehicles can be analyzed to obtain urban traffic data such as traffic running trend, congestion occurrence positions, traffic flows of different areas and the like, and the urban traffic data is utilized to optimize the urban traffic. Because the data volume of the historical track data of the vehicle is large, in the prior art, the historical track data can be accurately provided, a track data query system capable of flexibly and rapidly querying the historical track data in a specified time range and a specified space range is lacking, and a track data processing system capable of accurately analyzing and processing the historical track data obtained by query is lacking.

Based on the above, the embodiment of the application provides a method and a device for processing historical track data, which can accurately, rapidly and flexibly acquire the historical track data and can more accurately analyze the historical track data.

Referring to fig. 1, a schematic diagram of a possible application scenario provided by an embodiment of the present application, specifically, a historical track data processing system 100 capable of implementing some embodiments of the present application is shown. For example, the historical track data processing system 100 may be an online transportation service platform for transportation services such as taxis, ride-on services, express, carpools, bus services, driver leases, or airliner services, or any combination thereof. Historical track data processing system 100 may include one or more of a server 110, a network 120, a service requester terminal 130, a service provider terminal 140, and a database 150.

In some embodiments, the server 110 may be a single server or a group of servers. The server farm may be centralized or distributed (e.g., server 110 may be a distributed system). In some embodiments, the server 110 may be local or remote to the terminal.

The server 100 and the terminal may establish a communication connection therebetween, and transmit driving state information, order information, and the like based on the communication connection. The terminal may be the service requester terminal 130 or the service provider terminal 140. For example, for the acquisition and uploading of the driving status information and the order information by using the network vehicle-restraining terminal, the service provider terminal 140 may be a terminal used by the driver, the service requester terminal 130 may be a terminal used by the passenger, and the server 110 may be in communication connection with the terminal used by the driver, so as to obtain the order information and the driving status information recorded in each terminal, for example, the order identifier in each order information, the driving status information generated by the driving of the vehicle by the driver, and the like may be obtained by using the terminal used by the driver.

In the embodiment of the present application, the server 100 may construct the database 150 storing the historical driving status information and the historical order information based on the driving status information and the order information uploaded by the service requester terminal 130 or the service provider terminal 140, so that the service requester terminal 130 or the service provider terminal 140 or other processing devices can query the required historical driving status information. In addition, in the embodiment of the present application, the service requester terminal 130 or the service provider terminal 140 or other processing devices may send a query request to the server 110, so as to obtain the historical driving state information corresponding to the query request from the server 110, and further analyze and process the obtained historical driving state information to obtain the historical driving state feature. For specific implementation, please refer to the following examples.

For the convenience of understanding the present embodiment, a method for processing historical track data disclosed in the embodiment of the present application will be described in detail first.

Example 1

As shown in fig. 2, a method for processing historical track data according to a first embodiment of the present application includes:

s201: and acquiring the historical driving state information and the historical order information uploaded by at least one terminal, wherein the historical order information comprises an order identifier.

Specifically, the terminal may be a terminal used by a driver or a terminal used by a passenger. The order information of the driver and the driving state information generated by the driver driving the vehicle can be uploaded through the terminal used by the driver. The order information of the passenger and the traveling state information generated by the passenger riding on the vehicle can also be acquired through the terminal used by the passenger.

The travel state information and the order information may be stored in a storage device of the terminal, and the history travel state information and the history order information may be formed and uploaded to the server. The server can also receive the running state information and the order information uploaded by the terminal and store the running state information and the order information in a storage device of the server to form historical running state information and historical order information.

Here, the history running state information includes: the position coordinates of each track point and the time of passing each track point; and may also include the speed of passing each trace point.

The historical order information includes, in addition to the order identification: the start time and end time of the historical order.

S202: and matching the historical driving state information corresponding to each terminal with the historical order information to obtain the historical driving state information matched with each historical order executed by each terminal.

Specifically, according to the time range of passing through each track point and the starting time and the ending time of the historical order information corresponding to each terminal, which are included in the historical running information corresponding to each terminal, the historical running state information corresponding to each terminal is matched with the historical order information.

In one possible implementation manner, according to the time passing through each track point included in the historical running state information corresponding to each terminal, the historical running state information falling in the time range of the starting time and the ending time of the same historical order is divided into the same running state information set, wherein each historical order corresponds to one running state information set.

S203: a first database is constructed storing a mapping relationship between the order identifications of each historical order and the matched historical driving state information.

After obtaining the historical driving state information matched with each historical order executed by each terminal, a first database storing the mapping relation between the order identification of each historical order and the corresponding driving state information set is constructed.

In order to flexibly and rapidly inquire the historical track data in a specified space range, a matching relation between the space position coordinates and the historical track data needs to be established. In the case of analysis of urban traffic data, a predetermined road network is typically used to identify spatial location coordinates.

The most basic elements of the road network are road segments (links) and nodes (nodes) in combination with urban traffic road conditions. The road section is a directed line section between two nodes, is the smallest unit of path in the road network, and corresponds to a road section identifier. The nodes are connected with different road sections, usually the inflection points of the road, intersections, parking lots and the like.

Because the road network is used for identifying the space position coordinates, the position coordinates of each track point in the historical driving state information need to be converted into the space position coordinates in the road network, and in general, the position coordinates of each track point in the historical driving state information are longitude and latitude coordinates obtained through a positioning technology, so that in the specific implementation process, the position coordinates of each track point in the historical driving state information need to be converted into the road section identification.

In the process of converting the position coordinates of each track point in the historical driving state information into the road section identification, if the road sections where the position coordinates of two continuous track points fall are discontinuous, between the two continuous track points, according to the number of road sections where the previous track point falls and the road sections where the next track point falls in the two continuous track points, virtual track points with the same number as the number of the road sections at intervals are increased, and each virtual track point corresponds to one road section at interval.

In a possible implementation manner, the road section identifier matched with each historical order can be determined according to the position coordinates of each track point included in the historical driving state information matched with each historical order; and constructing a second database storing the road segment identifications of each historical order with which the order identifications of each historical order match. Therefore, the historical driving state information corresponding to the target road section identifier can be finally determined according to the query request carrying the target road section identifier.

Here, the above-described link identification may be represented by a link number (link_id).

In another possible implementation, in order to flexibly and quickly query the historical track data in a specified time range, a matching relationship between the time identifier and the historical track data needs to be established. The time mark matched with each historical order can be determined according to the time of passing through each track point included in the historical driving state information matched with each historical order; a third database is constructed storing an order identification for each historical order and a time identification that matches each historical order. Therefore, the historical driving state information corresponding to the target time mark can be finally determined according to the query request carrying the target time mark.

Here, the above-mentioned time stamp may be represented by a time stamp.

In yet another possible implementation manner, the time identifier and the road identifier matched with each historical order may be determined according to the matching relationship between the time identifier and the historical track data and between the road identifier and the historical track data, and a fourth database storing the order identifier of each historical order, the road identifier matched with each historical order and the time identifier matched with each historical order is built. Therefore, the historical driving state information of the appointed time range and the appointed road section range can be obtained according to the query request carrying the target road section identifier and the target time identifier.

In addition, since the data amount of the historical driving state information is huge, beijing is taken as an example, and hundreds of millions of historical driving state information are available every day in Beijing. Therefore, in building the database, it is necessary to store the historical driving state information in a distributed system such as Hbase, distributed file system (Hadoop Distributed File System, HDFS) and the like, and to sequence and compress the historical driving state information.

Specifically, the format of the stored historical driving state information can be specified to use binary bytes, and data formats such as character strings (strings), integer (int) or double-precision floating point numbers (double) are avoided. Therefore, each piece of information included in the history running state information, such as the position coordinates of each track point, the time of each track point, and the speed of passing each track point, is converted into a binary byte having a preset format and a preset length, which is a process of serializing the history running state information.

And then, compressing and storing the serialized historical driving state information, and decompressing the acquired historical driving state information after inquiring and acquiring the required historical driving state information.

S204: when a query request carrying a first target order mark sent by a request end is received, historical driving state information matched with the first target order mark is obtained from a first database, and the obtained historical driving state information is sent to the request end.

In a possible implementation manner, in addition to the query request with the first target order identifier sent by the request end, the query request with the target road segment identifier sent by the request end can be received, and when the query request with the target road segment identifier sent by the request end is received, a second target order identifier matched with the target road segment identifier is obtained from a second database; and acquiring the historical driving state information matched with the second target order mark from the first database, and transmitting the acquired historical driving state information to the request end. Thus, the requirement of flexibly and rapidly inquiring the historical track data in the appointed space range is met.

In another possible implementation manner, the method may further receive a query request with a target time identifier sent by the request end, and acquire a third target order identifier matched with the target time identifier from a third database when receiving the query request with the target time identifier sent by the request end; and acquiring the historical driving state information matched with the third target order mark from the first database, and transmitting the acquired historical driving state information to the request end. Thus, the requirement of flexibly and rapidly inquiring the historical track data in the appointed time range is met.

In another possible implementation manner, a query request with a target time identifier and a target road section identifier sent by the request end can be received, and when the query request with the target time identifier and the target road section identifier sent by the request end is received, a fourth target order identifier matched with the target time identifier and the target road section identifier is obtained from a fourth database; and acquiring the historical driving state information matched with the fourth target order mark from the first database, and transmitting the acquired historical driving state information to the request end. Thus, the requirement of flexibly and rapidly inquiring the historical track data in the appointed time range and the appointed space range is met.

Example two

As shown in fig. 3, a method for processing historical track data according to a second embodiment of the present application includes:

s301: acquiring historical driving state information with at least one target order mark matched respectively, wherein the historical driving state information comprises at least one of the following information: the position coordinates of each track point, the time of passing each track point, the speed of passing each track point.

In the implementation process, the query request can be determined according to the analysis requirement and sent to the server, so that the historical driving state information sent by the server is received. In particular by any one of several possible embodiments:

a: sending a first query request carrying at least one target order identifier to a server; and receiving the historical driving state information which is respectively matched with at least one target order mark and is sent by the server.

B: sending a second query request carrying at least one target road section identifier to a server; receiving order identifiers respectively matched with at least one target road section identifier sent by a server; selecting at least one target order identifier from the received order identifiers; sending a third query request carrying at least one selected target order identifier to a server; and receiving historical driving state information which is sent by the server and is respectively matched with the at least one selected target order mark.

C: sending a fourth query request carrying at least one target time identifier to a server; receiving order identifiers respectively matched with at least one target time identifier and sent by a server; selecting at least one target order identifier from the received order identifiers; sending a fifth query request carrying at least one selected target order identifier to a server; and receiving historical driving state information which is sent by the server and is respectively matched with the at least one selected target order mark.

D: a sixth query request carrying at least one target road section identifier is sent to a server; receiving order identifiers respectively matched with at least one target road section identifier sent by a server; a seventh query request carrying order identifiers respectively matched with at least one target road section identifier is sent to a server; and receiving historical driving state information which is sent by the server and is respectively matched with the order identifications in the seventh inquiry request.

E: sending an eighth query request carrying at least one target time identifier to a server; receiving order identifiers respectively matched with at least one target time identifier and sent by a server; a ninth query request carrying order identifiers respectively matched with at least one target time identifier is sent to a server; and receiving historical driving state information which is sent by the server and is respectively matched with the order identifications in the ninth inquiry request.

F: a tenth inquiry request carrying at least one target time identifier and at least one road section identifier is sent to a server; receiving order identifiers which are respectively matched with at least one target time identifier and are respectively matched with the at least one road section identifier and are sent by a server; an eleventh inquiry request carrying order identifiers matched with at least one target time identifier and respectively matched with the at least one road section identifier is sent to a server; and receiving historical driving state information which is sent by the server and is respectively matched with the order identifications in the eleventh inquiry request.

G: transmitting a twelfth query request carrying at least one target time identifier and at least one road section identifier to a server; receiving order identifiers which are respectively matched with at least one target time identifier and are respectively matched with the at least one road section identifier and are sent by a server; selecting at least one target order identifier from the received order identifiers; transmitting a thirteenth query request carrying at least one target order identifier to a server; and receiving historical driving state information which is sent by the server and is respectively matched with the at least one selected target order mark.

S302: determining historical driving state characteristics based on the historical driving state information corresponding to each target order mark;

wherein the historical driving status feature includes at least one of the following feature information:

traffic flow information for any one of the target location areas;

traffic speed information of any one target position area;

and passing time information of any target position area.

Specifically, determining a historical driving status feature based on the historical driving status information corresponding to each target order identification includes: and screening out target track points meeting preset conditions from the historical running state information corresponding to each target order mark, and determining the historical running state characteristics according to the target historical running state information corresponding to the target track points.

Exemplary:

a: when the historical driving state feature includes a start position and/or an end position of any one target order, determining the historical driving state feature based on the historical driving state information corresponding to each target order identifier includes:

and screening target track points corresponding to the starting time and/or the ending time of the target order according to the starting time and/or the ending time of the historical order information.

The position coordinates of the track points in the target historical driving state characteristics corresponding to the starting time of the target order are the starting point positions of the target order; and the position coordinates of the track points in the target historical driving state characteristics corresponding to the ending time of the target order are the end positions of the target order.

In consideration of the phenomena of multiple departure, track interruption and the like in the running process of the vehicle, in the prior art, when the historical running state information of the target order is analyzed, the problems of unobvious and inaccurate starting position and/or ending position of the target order pair are easily caused by the phenomena. Therefore, the embodiment of the application establishes the matching relation between the road section identification and/or the time identification and the order identification in the historical order information, and can accurately determine the starting point position and/or the end point position of any one target order by acquiring the starting time and/or the end time of each order in the historical order information.

In specific implementation, the starting point position of the first target order can be obtained, and the ending point position of the first target order is determined according to the starting point position of the first target order; or acquiring the end position of the first target order, and determining the start position of the first target order according to the end position of the first target order. Wherein the first target order is any one target order.

Illustratively, the process of determining the end position of the first target order from the start position of the first target order includes the steps of:

step 1: since the known information is only the starting point position of one target order, it is necessary to obtain the historical order information such as the target order identifier of the target order according to the starting point position of the target order. The method comprises the steps of obtaining a road section identifier corresponding to a starting point position of a first target order, sending a query request carrying the road section identifier corresponding to the starting point position of the first target order to a server, and receiving the first target order identifier matched with the road section identifier corresponding to the starting point position of the first target order sent by the server.

Step 2: after the first target order mark is obtained, historical order information and historical driving state information are obtained according to the first target order mark. Specifically, a query request carrying a first target order identifier may be sent to the server, historical driving state information matched with the first target order identifier and sent by the server may be received, and the termination time of the first target order may be obtained according to the first target order identifier.

Step 3: and determining the track point with the minimum interval duration between the track point and the termination time of the first target order according to the time of each track point in the historical driving state information in the received historical driving state information matched with the first target order identification according to the termination time of the target order, and obtaining the target track point. And taking the position coordinates of the target track points as the end positions of the first target order.

For example, the starting point position and/or the ending point position of at least one target order passing through the first position coordinate may be determined according to the first position coordinate, where the first position coordinate is any position coordinate, and the method includes the following steps:

step 1: the method comprises the steps of obtaining a road section identifier corresponding to a first position coordinate, sending a query request carrying the road section identifier corresponding to the first position coordinate to a server, and receiving at least one target order identifier matched with the road section identifier corresponding to the first position coordinate sent by the server.

Step 2: and after the at least one target order mark is acquired, acquiring historical order information and historical driving state information matched with the at least one target order mark. And sending a query request carrying the at least one target order identifier to a server, and receiving historical driving state information which is sent by the server and is respectively matched with the at least one target order identifier. And acquiring the starting time and/or the ending time of the target order corresponding to the at least one target order identifier according to the at least one target order identifier.

Step 3: and determining the starting point position and/or the end point position of the first target order according to the historical order information and the historical driving state information matched with the at least one target order identifier. The first target order is any one target order.

And identifying a first target order in the corresponding target orders according to the at least one target order, and determining a track point with the minimum interval duration between the track point and the starting point time of the first target order as a target track point in the received historical driving state information matched with the first target order according to the time of each track point in the historical driving state information matched with the first target order. And taking the position coordinates of the target track points as the starting point positions of the first target orders.

And/or identifying a first target order in the corresponding target orders aiming at the at least one target order, and determining a track point with the minimum interval duration between the termination time of the first target order in the history running state information matched with the first target order according to the time of each track point in the history running state information matched with the first target order in the received history running state information matched with the first target order as a target track point. And taking the position coordinates of the target track point as the end position of the target order.

The determining the starting point position and/or the ending point position of at least one target order passing through the first position coordinates according to the first position coordinates may further analyze the preset time range. And determining the starting point position and/or the ending point position of at least one target order passing through the first position coordinates within a preset time range.

b: in the case where the historical driving status feature includes traffic flow information of a first target location area, where the first target location area is any one target location area, determining the historical driving status feature based on the historical driving status information corresponding to each target order identifier includes:

and counting the number of track points falling into the first target position area to obtain the traffic flow information of the first target position area. The greater the number of trajectory points that fall into the first target location area, the greater the traffic flow in the first target location area.

Specifically, determining the traffic information of the first target location and the first target location may include the steps of:

step 1: at least one target road section identifier in the first target position area is obtained, a query request carrying the at least one target road section identifier is sent to a server, and target order identifiers respectively matched with the at least one target road section identifier and sent by the server are received.

Step 2: and acquiring the historical driving state information matched with the target order identifiers after acquiring the target order identifiers respectively matched with the at least one target road section identifier. And sending a query request carrying the target order identifier to a server, and receiving historical driving state information matched with the target order identifier and sent by the server.

Step 3: and determining the traffic flow information of the first target position area according to the historical driving state information matched with the target order mark.

And based on the received historical driving state information matched with the target order mark, taking the track point falling into the first target position area as a target track point in the historical driving state information according to the position coordinates of the track point in the historical driving state information. And counting the number of target track points in the historical driving state information matched with the target order mark to obtain the traffic flow information of the first target position area.

Here, the first target position area includes: at least one road segment. Alternatively, in order to be closer to the expression mode of the traffic road network in reality, an intersection (junction), a road (road) and an area (area) may be used to identify the first target location area.

When the intersection is used as a first target position area, the road section identifier of each road section in each direction of the intersection connection is used as a target road section identifier in the first target position area. When the road is used as the first target position area, the road section identifier of each road section in each direction on the road is used as the target road section identifier in the first target position area. And when the area is taken as a first target position area, acquiring each intersection and each road covered in the area, and taking the road section identifier of each road section connected with each intersection covered in the area and the road section identifier of each road section covered in the area as the target road section identifier in the first target position area.

c: in the case where the above-mentioned history driving state feature includes the traffic speed information of the first target location area, determining the history driving state feature based on the history driving state information corresponding to each target order identification includes:

the speed of each track point falling into the first target position area can be obtained simply through obtaining the traffic speed information of the first target position area.

The historical running state information in each preset time interval can be obtained according to a plurality of preset time intervals, and the average speed in each preset time interval is calculated based on the speed of the track point in the historical running state information in each preset time interval; and calculating according to the average speed in each preset time interval and the length information corresponding to the first target position area to obtain the traffic speed information of the first target position area.

For example, the traffic speed information of the first target location area may be calculated with 24 hours of any day as the target time range for calculating the traffic speed information of the first target location area, including the steps of:

step 1: and obtaining a target time identifier according to the starting time and the ending time of the target time range, and obtaining at least one target road section identifier according to each road section identifier in the first target position area.

Step 2: and sending a query request carrying the target time identifier and at least one target road section identifier to a server.

Step 3: and receiving a target order identifier matched with the target time identifier and at least one target road section identifier, which is sent by the server.

Step 4: and sending a query request carrying the target order identifier to a server, and receiving historical driving state information matched with the target order identifier and sent by the server.

Step 5: and screening the track points falling in the first target position area as target track points according to the position coordinates of the track points in the historical driving state information matched with the target order mark.

Step 6: for each road segment, according to the target track points which fall in the road segment and are 24 hours a day, calculating the first average speed of the target track points in each hour according to the speed of the target track points in each hour of the road segment at preset time intervals in each hour.

Step 7: and acquiring the length of each road section according to each road section contained in the first target position area.

Step 8: and calculating the corresponding travel time index of each road section according to the first average speed, the second average speed and the length of the road section. And measuring the passing speed information of the target position area according to the travel time indexes respectively corresponding to each road section. When the travel time index is larger, the passing speed of the target position area is lower. The travel time index can be used for analyzing the intra-area contact and the extra-area contact of each node or road section in the road network so as to evaluate the reachability of each node in the road network.

In the urban traffic network, a situation that a lane in one direction is smooth and a lane in the other direction is congested usually occurs, so that in the implementation process, a specific target road can be selected as a target position area to measure the speed of a tide lane of the target road, and the target road comprises two road sections with opposite directions.

After the travel time indexes of the two opposite links are obtained, respectively, a difference value of the travel time indexes of the two opposite links is calculated, and the magnitudes of the travel time indexes of the two opposite links are compared. And calculating to obtain a bidirectional unbalance index by using the absolute value of the difference value of the travel time indexes of the two opposite road sections and the smaller travel time index of the two opposite road sections. And measuring the tidal lane speed of the target road by using the bidirectional unbalance index.

d: in the case where the above-mentioned history driving state feature includes passing time information through the first target location area, determining the history driving state feature based on history driving state information corresponding to each target order identification includes:

when urban traffic data is analyzed, the passing time of traffic light intersections is sometimes required to be analyzed, so that the timing of signal lamps is optimized, and urban traffic is subjected to congestion management and optimization.

For example, an intersection may be used as a first target location area, so as to obtain traffic time information of each traffic mode such as straight, left-turn, right-turn, and the like at the intersection.

Specifically, the intersection traffic mode may be represented by two connected road segments, so for a specific traffic mode, the following steps may be used to calculate the traffic time information of the traffic mode:

step 1: and acquiring the road section identifiers of the two road sections connected in the passing mode as target road section identifiers, sending a query request carrying the target road section identifiers to a server, and receiving target order identifiers respectively matched with the target road section identifiers sent by the server. And sending a query request carrying the target order identifier to a server, and receiving historical driving state information matched with the target order identifier and sent by the server.

Step 2: and screening the track points falling in the first target position area as target track points according to the position coordinates of the track points in the historical driving state information matched with the target order mark.

Step 3: and calculating the passing time information of the passing mode according to the time of each passing through each target track point.

The calculation of the traffic time information for each intersection traffic pattern may be performed within a specific time range, and the traffic time information for each intersection traffic pattern may be calculated based on the historical driving state information within a specific time range, for example, within 7 days.

For example, some predetermined road segments can be selected as the first target location area, the traffic time information of the predetermined road segments is analyzed, and the information of a plurality of traffic events can be obtained. When traffic events such as road repair, road sealing, accidents and the like occur, the passing time of a preset road section where the traffic event occurs is suddenly increased. According to the position coordinates of each track point in the historical track information, track points falling in a preset road section in the historical track information are selected as target track points, and the number of the target track points in a unit time range is calculated. Likewise, traffic events may also affect more historical driving status characteristics such as travel time indicators.

e: the historical driving status feature may further include an upstream road section proportion of the first target location area according to the analysis requirement. In the case where the above-mentioned historical driving status feature includes the upstream link proportion of the first target location area, determining the historical driving status feature based on the historical driving status information corresponding to each target order identification includes:

here, the first target location area may include a road segment or an intersection, and the blood-edge analysis is performed on the first target location area according to calculation of the proportion of the road segment upstream of the first target location area.

Taking the example that the first target location area includes a target intersection. And determining the road section identifier of each road section connected with the target intersection, sending a query request carrying the road section identifier of each road section connected with the target intersection to a server, and receiving the target order identifier which is respectively matched with the road section identifier of each road section connected with the target intersection and is sent by the server. And sending a query request carrying the target order identifier to a server, and receiving historical driving state information matched with the target order identifier and sent by the server.

In an exemplary embodiment, on a road network, position coordinates of an intersection directly connected to a road between target intersections are determined, and according to position coordinates of each track point in the historical driving state information matched with the target order identification, a first track point falling into the target intersection is divided into a first target track point set.

For each first track point in the first target track point set, determining the historical driving state information of the first track point, screening second track points falling into an intersection directly connected with a road between target intersections from the determined historical driving state information, and dividing the screened second track points into a second target track point set. And aiming at each first track point in the first target track point set, acquiring a first target time of the first track point and a second target time of a second track point of the second track point set, which corresponds to the same terminal acquired by the first track point, of the historical driving state information, wherein the second track point with the second target time later than the first target time is selected from the second target track point set as a third track point, and the third track point is divided into the third target track point set.

And calculating the number of third track points in each intersection with the road direct connection with the target intersection according to the intersection with the road direct connection with the target intersection, which each third track point in the third target track point set respectively falls into. And the ratio of the number of the third track points falling into the road junction with the road direct connection with the target road junction to the total number of the third track points in the third target track point set can be calculated for each road junction with the road direct connection with the target road junction.

The above steps are a specific example of performing a blood-edge analysis on a target intersection, and it can be determined through the above steps that a vehicle at the target intersection is mainly driven from an intersection having a road directly connected with the target intersection. And the blood margin analysis is carried out on intersections which are frequently jammed, so that reference data can be provided for optimization of urban road networks.

By adopting the historical track data processing method provided by the embodiment of the application, the historical track data can be accurately, quickly and flexibly acquired, and the historical track data can be analyzed more accurately.

Based on the same design concept, the embodiment of the application also provides a historical track data processing device, electronic equipment and a computer readable storage medium.

Example III

As shown in fig. 4, a historical track data processing apparatus 400 provided in an embodiment of the present application includes:

the acquiring module 401 is configured to acquire historical driving status information and historical order information uploaded by at least one terminal, where the historical order information includes an order identifier;

the matching module 402 is configured to match the historical driving status information corresponding to each terminal with the historical order information, so as to obtain historical driving status information matched with each historical order executed by each terminal;

A first construction module 403, configured to construct a first database storing a mapping relationship between an order identifier of each historical order and the matched historical driving status information;

and the query module 404 is configured to, when receiving a query request carrying a first target order identifier sent by the request end, acquire historical driving state information matched with the first target order identifier from the first database, and send the acquired historical driving state information to the request end.

In one possible design, the apparatus 400 further comprises:

the second construction module 405 is configured to determine, according to the position coordinates of each track point included in the historical driving status information matched with each historical order, a road section identifier matched with each historical order; and is further configured to construct a second database storing an identification of road segments for which the order identification of each of the historical orders matches each of the historical orders.

In one possible design, the query module 404 is further configured to, when receiving a query request carrying a target road segment identifier sent by the request end, obtain a second target order identifier matched with the target road segment identifier from a second database;

And acquiring the historical driving state information matched with the second target order mark from the first database, and transmitting the acquired historical driving state information to the request end.

In one possible design, the apparatus 400 further comprises:

a third construction module 406, configured to determine, according to the time that passes through each track point included in the historical driving status information that matches each historical order, a time identifier that matches each historical order; and is further configured to construct a third database storing time identifiers for each of the historical orders for which the order identifier matches each of the historical orders.

In one possible design, the query module 404 is further configured to, when receiving a query request carrying a target time identifier sent by the request end, obtain a third target order identifier matched with the target time identifier from a third database;

and acquiring the historical driving state information matched with the third target order mark from the first database, and transmitting the acquired historical driving state information to the request end.

In a possible design, the matching module 402 is specifically configured to divide, according to a time passing through each track point included in the historical driving status information corresponding to each terminal, the historical driving status information that falls within a time range of a start time and a stop time of the same historical order into the same driving status information set, where each historical order corresponds to one driving status information set;

The first construction module 403 is further configured to construct a first database storing a mapping relationship between an order identifier of each historical order and a corresponding running state information set.

The historical track data processing device provided by the third embodiment of the application can accurately, rapidly and flexibly acquire the historical track data.

Example IV

As shown in fig. 5, an embodiment of the present application further provides a historical track data processing apparatus 500, including:

an obtaining module 501, configured to obtain historical driving status information that at least one target order identifier matches respectively, where the historical driving status information includes at least one of the following information: position coordinates of each track point, time of passing each track point, speed of passing each track point;

the feature determining module 502 is configured to determine a historical driving status feature based on the historical driving status information corresponding to each target order identifier;

traffic flow information for any one of the target location areas;

traffic speed information of any one target position area;

And passing time information of any target position area.

In one possible design, the obtaining module 501 is specifically configured to:

sending a first query request carrying at least one target order identifier to a server;

and receiving the historical driving state information which is respectively matched with at least one target order mark and is sent by the server.

In one possible design, the acquisition module 501 is further configured to:

receiving order identifiers respectively matched with at least one target road section identifier sent by a server;

and receiving historical driving state information which is sent by the server and is respectively matched with the at least one selected target order mark.

In one possible design, the acquisition module 501 is further configured to:

receiving order identifiers respectively matched with at least one target time identifier and sent by a server;

The historical track data processing device provided by the fourth embodiment of the application can accurately, rapidly and flexibly acquire the historical track data and can analyze the historical track data more accurately.

Example five

Fig. 6 shows an electronic device 600 according to an embodiment of the present application, including a processor 601, a memory 602, and a bus 603, where the memory 602 stores machine-readable instructions executable by the processor 601 (such as execution instructions corresponding to the acquisition module 401, the matching module 402, the first building module 403, and the query module 404 in fig. 4), and when the electronic device 600 is running, the processor 601 communicates with the memory 602 through the bus 603, and the machine-readable instructions when executed by the processor 601 perform the following processing:

The specific processing flow of the processor 601 may refer to the descriptions of the foregoing embodiments, and will not be repeated here.

The electronic equipment provided by the embodiment of the application can accurately, quickly and flexibly acquire the historical track data, and can more accurately analyze the historical track data.

Example six

Fig. 7 illustrates an electronic device 700 provided in an embodiment of the present application, where the memory 702 stores machine-readable instructions executable by the processor 701 (e.g., execution instructions corresponding to the acquisition module 501 and the feature determination module 502 in fig. 5, etc.), and when the electronic device 700 is running, the processor 701 communicates with the memory 702 through the bus 703, and when the machine-readable instructions are executed by the processor 701, the following process is performed:

traffic flow information for any one of the target location areas;

traffic speed information of any one target position area;

and passing time information of any target position area.

The specific processing flow of the processor 701 may refer to the description of the above embodiment, and will not be repeated here.

The historical track data processing device and the electronic equipment provided by the embodiment of the application have the same technical characteristics as the historical track data processing method provided by the embodiment, so that the same technical problems can be solved, and the same technical effects can be achieved.

Example seven

The present embodiment discloses a computer readable storage medium, on which a computer program is stored, which when executed by a processor, performs the method for processing historical track data according to the first embodiment of the method and/or the steps in the method for processing historical track data according to the second embodiment of the method.

The computer program product for performing the historical track data processing method provided by the embodiment of the application comprises a computer readable storage medium storing non-volatile program code executable by a processor, wherein the instructions included in the program code can be used for executing the method in the previous method embodiment, and specific implementation can be referred to the method embodiment and will not be repeated herein.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the method embodiments, and are not repeated in the present disclosure. In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of modules is merely a logical function division, and there may be additional divisions in actual implementation, and for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, indirect coupling or communication connection of devices or modules, electrical, mechanical, or other form.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims

1. A method for processing historical track data, comprising:

acquiring historical driving state information and historical order information uploaded by at least one terminal, wherein the historical order information comprises an order identifier, a starting time and an ending time of a historical order, and the historical driving state information comprises the time of passing through each track point;

constructing a first database storing the mapping relation between the order identification of each historical order and the corresponding running state information set;

2. The method of claim 1, wherein the historical driving status information further comprises: the position coordinates of each track point.

3. The method of claim 2, further comprising, after obtaining the historical driving status information and the historical order information uploaded by the at least one terminal:

4. A method as claimed in claim 3, wherein the method further comprises:

5. The method of claim 2, further comprising, after obtaining the historical driving status information and the historical order information uploaded by the at least one terminal:

6. The method of claim 5, wherein the method further comprises:

7. A method for processing historical track data, comprising:

Based on a first database, acquiring historical driving state information with at least one target order mark matched respectively, wherein the historical driving state information comprises at least one of the following information: the first database stores mapping relations between order identifications of each historical order and corresponding running state information sets, each historical order corresponds to one running state information set, and each running state information set is formed by the following modes: dividing the historical driving state information falling into a time range of the starting time and the ending time of the same historical order into the same driving state information set according to the time passing through each track point included in the historical driving state information corresponding to each terminal;

traffic flow information for any one of the target location areas;

Traffic speed information of any one target position area;

and passing time information of any target position area.

8. The method of claim 7, wherein obtaining historical driving status information for which at least one target order identification matches each other comprises:

9. The method of claim 7, wherein obtaining historical driving status information for which at least one target order identification matches each other comprises:

10. The method of claim 7, wherein obtaining historical driving status information for which at least one target order identification matches each other comprises:

11. A history trace data processing apparatus, comprising:

the system comprises an acquisition module, a control module and a control module, wherein the acquisition module is used for acquiring historical driving state information and historical order information uploaded by at least one terminal, the historical order information comprises an order identifier, a starting time and an ending time of a historical order, and the historical driving state information comprises time passing through each track point;

the matching module is used for dividing the historical driving state information falling into a same driving state information set within a time range of the starting time and the ending time of the same historical order according to the time passing through each track point and included in the historical driving state information corresponding to each terminal, wherein each historical order corresponds to one driving state information set;

The first construction module is used for constructing a first database storing the mapping relation between the order identification of each historical order and the corresponding running state information set;

12. The apparatus of claim 11, wherein the historical driving status information further comprises: the position coordinates of each track point.

13. The apparatus of claim 12, wherein the apparatus further comprises:

14. The apparatus of claim 13, wherein the query module is further configured to obtain a second target order identifier matched with the target road segment identifier from the second database when receiving a query request carrying the target road segment identifier sent by the request end;

15. The apparatus of claim 12, wherein the apparatus further comprises:

16. The apparatus of claim 15, wherein the query module is further configured to, when receiving a query request carrying a target time identifier sent by a request end, obtain a third target order identifier matched with the target time identifier from the third database;

17. A history trace data processing apparatus, comprising:

The system comprises an acquisition module, a storage module and a storage module, wherein the acquisition module is used for acquiring historical driving state information which is matched with at least one target order mark respectively based on a first database, and the historical driving state information comprises at least one of the following information: the first database stores mapping relations between order identifications of each historical order and corresponding running state information sets, each historical order corresponds to one running state information set, and each running state information set is formed by the following modes: dividing the historical driving state information falling into a time range of the starting time and the ending time of the same historical order into the same driving state information set according to the time passing through each track point included in the historical driving state information corresponding to each terminal;

Traffic flow information for any one of the target location areas;

traffic speed information of any one target position area;

and passing time information of any target position area.

18. The apparatus of claim 17, wherein the obtaining module is specifically configured to:

19. The apparatus of claim 17, wherein the acquisition module is further to:

20. The apparatus of claim 17, wherein the acquisition module is further to:

21. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the historical track data processing method of any one of claims 1 to 6 when executed.

22. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the historical track data processing method of any one of claims 7 to 10 when executed.

23. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, performs the historical track data processing method of any one of claims 1 to 6 and/or the steps of the historical track data processing method of any one of claims 7 to 10.