Mileage charging method and device

By obtaining the message elements interacting with the roadside equipment, determining the mileage driving data at the vehicle end and billing, the problems of low mileage billing accuracy and easy to tamper with in the existing technology are solved, and the accurate billing effect of the entire road section is achieved.

CN119028034APending Publication Date: 2024-11-26DATANG GOHIGH INTELLIGENT & CONNECTED TECH (CHONGQING) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310594039.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-24
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing mileage billing methods have problems of low accuracy and tampering, especially in highway scenarios and urban road scenarios. It is difficult for the existing technology to achieve accurate trajectory restoration and accurate mileage billing.

Method used

By obtaining message elements that interact with roadside equipment, including vehicle-mounted identification information of vehicle-mounted equipment, roadside identification, road node information and road section information of roadside equipment, mileage driving data at the vehicle end is determined, and billed according to preset charging conditions , utilizes node deployment and message elements of C-V2X devices to achieve accurate mileage billing.

Benefits of technology

The precise charging effect of the entire road section is achieved, the limitations of mileage billing and low accuracy are avoided, the accuracy of billing is ensured and the prevention of human tampering is prevented, and the application scenarios are broadened for mileage tax billing that is applicable to all road sections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119028034A_ABST
    Figure CN119028034A_ABST
Patent Text Reader

Abstract

The invention provides a mileage charging method and device. The method comprises the following steps: acquiring a message element interacting with roadside equipment; the message elements comprise vehicle-mounted identification information of vehicle-mounted equipment, roadside identification of roadside equipment, road node information and road section information; the road node information comprises a global region identifier and / or a local node identifier; the road section information at least comprises an upstream node identifier; according to the vehicle-mounted identification information, the roadside identification, the road node information and the road section information, mileage driving data of the vehicle end are determined; and according to the mileage driving data and a preset charging condition, mileage charging of the vehicle end is determined. According to the scheme of the invention, the mileage driving data of the vehicle end is determined through the interactive message elements of the vehicle end and the roadside equipment, and the method can be suitable for mileage charging of a whole road section, and can achieve the precise charging effect.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle networking technology, and more particularly to a mileage billing method and device. Background Art

[0002] Existing mileage billing methods include the Electronic Toll Collection (ETC) system, mileage billing using an on-board odometer (wheel speedometer), and mileage billing based on the Global Navigation Satellite System (GNSS).

[0003] The ETC method is to charge by road section, not by precise charging. The vehicle's driving path is fitted by the gantries along the way. It can only solve the charging problem of highway scenarios, and a large number of gantry systems need to be built, which is costly. In addition, if one gantry fails, it is easy to cause losses at the road section level. The ETC charging system cannot achieve accurate trajectory restoration.

[0004] The method of using an on-board odometer (wheel speedometer) is the most direct method, but its accuracy and authenticity are not high, and not all the distances traveled by the vehicle need to be charged. The odometer may manually turn off and on the vehicle mileage data collection device, and there is a possibility of human tampering, which makes the mileage data obtained by the device inaccurate, so the mileage data uploaded to the server is wrong. In addition, the mileage is calculated according to the theoretical diameter of the tire. In actual use, the tire is often compressed, which will cause the odometer data to be greater than the mileage. In addition, due to unknown reasons, there are errors in the mileage calculation. If it is not corrected in time, it will also affect the test results. In addition, the mileage data may not be sent out as private data, or shared in the vehicle to everything (V2X) system.

[0005] The GNSS-based method will record the detailed driving trajectory of the vehicle, which will involve the problem of violating user privacy. In addition, the real-time recording of the vehicle's latitude and longitude information will generate a large amount of data, occupying a large amount of unnecessary data overhead. Moreover, the vehicle side is prone to cheating, resulting in incomplete trajectory information and other problems. Summary of the invention

[0006] The purpose of this application is to provide a mileage metering method and device to avoid the limitations of mileage metering in the prior art, the low accuracy of mileage determination, and the easy tampering of mileage.

[0007] To achieve the above purpose, an embodiment of the present application provides a mileage charging method, which is applied to a vehicle side, including:

[0008] Acquire message elements interacting with the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification;

[0009] Determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0010] The mileage billing on the vehicle side is determined based on the mileage driving data and preset charging conditions.

[0011] To achieve the above purpose, the embodiment of the present application further provides a mileage billing method, which is applied in the cloud, including:

[0012] Acquire stored information of the interaction between the vehicle end and the roadside device; the stored information includes message elements of the interaction between the vehicle end and the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification;

[0013] Determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0014] The mileage billing on the vehicle side is determined based on the mileage driving data and preset charging conditions.

[0015] To achieve the above-mentioned purpose, the embodiment of the present application further provides a mileage metering device, which is applied to a vehicle side, and includes:

[0016] A first acquisition module is used to acquire message elements interacting with a roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification;

[0017] A first determination module is used to determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0018] A first determination module, used to determine the mileage driving data of the vehicle end according to the vehicle identification information of the vehicle-mounted device, the roadside identification and the message element;

[0019] The second determination module is used to determine the mileage billing on the vehicle side according to the mileage driving data and preset charging conditions.

[0020] To achieve the above purpose, the embodiment of the present application further provides a mileage metering device, which is applied to the cloud, including:

[0021] A second acquisition module is used to acquire stored information of the interaction between the vehicle end and the roadside device; the stored information includes message elements of the interaction between the vehicle end and the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification;

[0022] A third determination module is used to determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0023] The fourth determination module is used to determine the mileage billing on the vehicle side based on the mileage driving data and preset charging conditions.

[0024] To achieve the above objectives, an embodiment of the present application further provides a readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps in the mileage billing method as described in any of the above items are implemented.

[0025] The beneficial effects of the above technical solution of the present application are as follows:

[0026] In an embodiment of the present application, by obtaining message elements that interact with the roadside equipment; the message elements include the on-board identification information of the on-board equipment, the roadside identification of the roadside equipment, the road node information and the road section information; according to the message elements, the mileage driving data of the vehicle side is determined, and according to the preset charging conditions, the mileage billing of the vehicle side is determined. The solution of the present application can be applied to mileage billing of the entire road section, and can achieve the effect of accurate charging, avoiding the limitations of mileage billing in the prior art, the low accuracy of mileage determination and the problem of easy tampering of mileage. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A flow chart of a mileage billing method applied to a vehicle provided in an embodiment of the present application;

[0028] Figure 2 One of the structural schematic diagrams of the mileage driving path provided in the embodiment of the present application;

[0029] Figure 3 The second structural diagram of the mileage driving path provided in the embodiment of the present application;

[0030] Figure 4 A flow chart of a mileage billing method applied to the cloud provided in an embodiment of the present application;

[0031] Figure 5A schematic diagram of a module of a mileage metering device applied to a vehicle provided in an embodiment of the present application;

[0032] Figure 6 A schematic diagram of a module of a mileage metering device applied to the cloud provided in an embodiment of the present application; DETAILED DESCRIPTION

[0033] In order to make the technical problems, technical solutions and advantages to be solved by the present application clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0034] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present application. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0035] In the various embodiments of the present application, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0036] Before describing the embodiments of the present disclosure in detail, some related concepts are first explained.

[0037] Mileage tax is a tax paid based on the mileage driven. Think of it as a pay-per-mile tax, a kind of "road user fee". The mileage tax on vehicles is based on the number of miles driven within a specific time frame, such as a year or a quarter, so the mileage of the vehicle needs to be counted.

[0038] Mileage tax will help solve the problem of liquefied natural gas, pure electric, hydrogen fuel and other vehicles using the road without paying "road maintenance fees". Countries around the world are exploring the charging method of mileage tax. When vehicles are driving on the road and occupying the road, they will cause road wear and tear, and they need to pay for it. For fuel users of vehicles, if they do not use the road, they should not pay for road maintenance. However, since vehicles using new energy do not use fuel, there is no problem of paying fuel surcharges. They use the road but do not pay, and they benefit without burden, which is obviously unfair.

[0039] It should be noted that the GNSS positioning system, as an essential part of V2X equipment, provides positioning information for V2X equipment, including longitude, latitude, etc.

[0040] In addition, the existing vehicle mileage statistics face the problem of how to accurately count and how to avoid human modification.

[0041] Reference Figure 1 As shown, the embodiment of the present application provides a mileage charging method, which is applied to the vehicle side, including:

[0042] Step 11, obtain message elements for interacting with the roadside equipment; the message elements include the on-board identification information of the on-board equipment, the roadside identification of the roadside equipment, the road node (Node) information and the link (Link) information; the road node information includes the global area identification and / or the local node identification; the link information includes at least the upstream node identification.

[0043] The vehicle identification information may be information that can be used to uniquely identify the vehicle, such as the vehicle ID, the serial number of the vehicle equipment, the license plate number, etc. The roadside identification may be information that can be used to uniquely identify the roadside equipment, such as the ID and serial number of the roadside equipment. The global region identification may be a globally unique region ID.

[0044] Step 12, determining the mileage driving data of the vehicle side according to the vehicle-mounted identification information, the roadside identification, the road node information and the road section information.

[0045] The message elements in the embodiments of the present application can be defined using the message elements in the existing standards, that is, based on the cellular vehicle-to-everything (C-V2X) technology, using the message fields in C-V2X.

[0046] Node, map node (can be referred to as node for short), is the most basic component of the map, which can be an intersection or the end point of a road segment. On the map, two sequential nodes determine a directed road segment.

[0047] Node attributes include node name, node identification (ID), node location, and the set of upstream links connected to the node.

[0048] The road segments contained in a node all take the node as the downstream endpoint, and the road segments starting from the node belong to the data of the downstream nodes of the road segment.

[0049] NodeReferenceID: Node ID, which is composed of a globally unique region ID and a unique node ID within a region.

[0050] In the description of this application, a node may refer to the endpoint of each link information, which may be the intersection of two or more link information, or the starting point or end point of a single link information. Similarly, a node may also be manually calibrated, or automatically generated by image analysis. In general, a node may be described by coding or coordinates, and may optionally have other descriptive information such as node type.

[0051] Link: A road from one node to another adjacent node is called a directed link. Its attributes include name, upstream node ID, speed limit set, lane width, and the lane set and traffic sign set contained in the link.

[0052] Link information records the NodeReferenceID information of the starting point, along the way and the end point. The device stores this path information on the vehicle side, the road side or directly reports it to the cloud billing center system. Two NodeReferenceIDs determine the length of a road section (Link). The road length information is obtained through the calibration of the relevant units of the road side, and this application regards it as a known condition. The vehicle side can pay taxes by billing in installments, storing in installments, or by collecting and paying at certain time intervals (quarters).

[0053] In the description of the present disclosure, a link may refer to the smallest geometric unit used to express the geometric information of a road. Exemplarily, a link may be manually calibrated, or may be automatically generated by image analysis. Generally speaking, a link may be defined by two endpoints, for example, it may be represented as a directed line segment pointing from a starting point to an end point. It should be understood that the direction of a link may be an artificially defined direction, and does not correspond to an actual direction such as a driving direction. In addition, optionally, a link may have other descriptive information such as a road sign, a road grade, and the number of lanes of the road to which it belongs.

[0054] In the description of the present disclosure, the mileage driving data may refer to a connected road segment formed by one or more road segments that terminate and connect, such as a connected road segment between two intersections, or a road between an intersection and a junction.

[0055] Step 13, determine the mileage billing on the vehicle side based on the mileage driving data and preset charging conditions.

[0056] In an embodiment of the present application, after determining the mileage driving data through message elements, the vehicle side can obtain the preset charging conditions corresponding to the mileage driving data. The preset charging conditions may include: mileage charging tax rate, vehicle type charging standard, toll exemption sections and other preset charging conditions. The mileage billing of the vehicle side is determined according to the weighted calculation method.

[0057] Furthermore, the above method also includes:

[0058] The message elements are stored in the vehicle to form storage information, and the storage information is sent to the cloud.

[0059] In this embodiment, during the interaction between the vehicle and the roadside equipment, the vehicle can store the message elements generated by the interaction in the vehicle to form storage information, which can be sent to the cloud for decryption and processing by the cloud to determine the mileage billing of the vehicle; the storage information can also be used for tracing subsequent information; it can also be used by the vehicle to determine the mileage billing of the vehicle based on the storage information.

[0060] It should be noted that if abnormal mileage metering occurs on the vehicle side, the mileage metering on the vehicle side can be corrected based on the stored information through the cloud.

[0061] Optionally, the above step 11 includes:

[0062] Entering the geographic fence of the target roadside device, obtaining the message element for interacting with the target roadside device in the form of broadcast; or,

[0063] Interact with the target roadside device in a unicast manner to obtain message elements of the target roadside device interaction.

[0064] Here, the roadside equipment may be a roadside unit (RSU).

[0065] In one implementation of the present application, when the vehicle enters the geographic fence of the target RSU, the message elements for interacting with the target RSU are obtained through broadcasting. That is, as long as the vehicle enters the geographic fence of the target RSU, after information interaction with the target RSU, the trajectory information is recorded, that is, the message elements are recorded.

[0066] Among them, the broadcast method requires demarcating an area within the coverage of the target RSU that does not overlap with the coverage of other RSUs (i.e., a small map fence is divided around each roadside equipment location point (or Node point) with this as the center), in order to prevent different RSUs from recording the trajectory information of a vehicle at the same time. This application has two methods for uniquely identifying vehicle trajectory points: one is the Node ID information of the road on which the vehicle is traveling, and the other is the Node ID information of the roadside RSU.

[0067] In another implementation of the present application, the message elements are obtained by interacting with the target RSU in a unicast manner. Through this unicast interaction method, non-target RSUs can be prevented from simultaneously recording the trajectory information of a vehicle, thereby improving the accuracy of data interaction.

[0068] In another implementation of the present application, a positioning solution can also be used, that is, the mileage driving data of the vehicle can be recorded in real time by using the GNSS map.

[0069] Optionally, the above step 12 includes:

[0070] Determine the roadside identification of each roadside device passed by the vehicle according to the vehicle identification information;

[0071] Connect the road node information corresponding to each roadside sign and the upstream node sign of the road section information respectively to determine the mileage driving trajectory of the vehicle end;

[0072] Alternatively, the message element is sent to the cloud;

[0073] Receive the mileage driving trajectory of the vehicle side sent by the cloud; the cloud side determines the mileage driving data of the vehicle side according to the vehicle identification information, the roadside identification, the road node information and the road section information.

[0074] In the embodiment of the present application, the vehicle side can determine the roadside identification of each roadside device that the current vehicle passes through based on the vehicle identification information, and respectively connect the Node information corresponding to each roadside device and the upstream node identification of the Link to determine the mileage driving trajectory of the vehicle side. Of course, the message elements, namely the vehicle identification information, the roadside identification, the road node information and the road section information, can be sent to the cloud, and the mileage driving trajectory of the vehicle side that is processed by the cloud and sent to the vehicle side can be received.

[0075] It should be noted that the cloud can determine the mileage trajectory of the vehicle based on the message elements and preset decryption algorithm sent by the vehicle, and send it to the vehicle; it can also determine the mileage trajectory of the vehicle based on the message elements and preset decryption algorithm sent by the roadside equipment, and send it to the vehicle.

[0076] It can be understood that, firstly, the vehicle stores the information of each roadside sign it passes by (or the geographical location of the roadside equipment, or the road node information), and can screen the toll sections in real time or later. The section toll information is marked in the cloud or in the section information to determine the mileage trajectory of the vehicle.

[0077] Second, the roadside equipment or cloud stores the on-board identification information of each vehicle that passes by, and the on-board identification information of each vehicle is restored by decryption in the cloud. All the roadside identification information that the on-board identification information of the same vehicle passes through is summarized and screened to determine the mileage trajectory of the vehicle.

[0078] Optionally, after the above step 12, the method further includes:

[0079] Determining whether the mileage driving track of the vehicle is complete;

[0080] If the mileage driving track is incomplete, then the mileage driving track of the vehicle end is completed;

[0081] If the mileage driving trajectory is complete, the step of determining the mileage billing on the vehicle side according to the mileage driving data and the preset charging conditions is executed.

[0082] In the embodiment of the present application, after determining the mileage driving track of the vehicle side, the mileage driving track of the vehicle side is also judged. If it is determined that the mileage driving track is incomplete, the mileage driving track of the vehicle side is completed, so as to ensure accurate calculation of the driving track or mileage of the vehicle side, and prevent abnormal billing problems in subsequent mileage billing. If it is determined that the mileage driving track is complete, step 13 is executed.

[0083] Optionally, determining whether the mileage driving track of the vehicle is complete includes:

[0084] Determine whether the target upstream node identifier in the road information of the target roadside equipment in the mileage driving trajectory corresponds to the target road node information upstream of the target roadside equipment;

[0085] If the target upstream node identifier does not correspond to the target road node information, it is determined that the mileage driving trajectory is incomplete;

[0086] Otherwise, it is determined that the mileage driving trajectory is complete.

[0087] It should be noted that when determining that the mileage driving track is complete, the upstream node identifier and the target road node information can be consistent; they can also be data with a corresponding relationship, but they do not have to be consistent. Here, preferably, when the upstream node identifier and the target road node information are consistent, it is determined that the mileage driving track is complete.

[0088] In the embodiment of the present application, among the multiple roadside devices in the mileage driving trajectory, the upstream node identification of the target roadside device (the target roadside device is any roadside device among the multiple roadside devices) is obtained to determine whether it corresponds to the target road node upstream of the target roadside device. For example, if the multiple roadside devices include RSU1 to RSU5, the upstream node identification of the target RSU (RSU2) is obtained, and the road node information upstream of the target RSU (RSU2), that is, the Node information of RSU1, is obtained. If the upstream node identification of the target RSU (RSU2) corresponds to the Node information of RSU1, it is determined that the trajectory of the target RSU (RSU2) is complete. Each RSU between RSU1 and RSU5 is further verified, so that the integrity of the mileage driving trajectory can be determined.

[0089] Optionally, if the mileage driving track is incomplete, completing the mileage driving track of the vehicle side includes:

[0090] When it is determined that one of the road node information is missing in the mileage driving trajectory, the mileage driving trajectory of the vehicle is completed by reverse tracing;

[0091] When it is determined that at least two road node information are missing in the mileage driving trajectory, the driving direction and / or driving history trajectory of each road node information is obtained, and the mileage driving trajectory of the vehicle end is completed based on the driving direction and / or the driving history trajectory in combination with the reverse tracing method.

[0092] In one implementation of the present application, when it is determined that a Node information is missing in the mileage driving trajectory, the mileage driving trajectory of the vehicle side is completed in a reverse tracing manner based on the upstream and downstream Node information adjacent to the missing Node information. In another implementation of the present application, when it is determined that at least two Node information are missing in the mileage driving trajectory, the driving direction (such as heading angle, etc.) or driving history trajectory (the vehicle side has a recorded history trajectory) passing through each Node information is retrieved, and the driving direction / driving history trajectory is combined with the Node information to solve the problem of multiple missing points and reduce the search range. The driving direction can accurately locate which upstream node it is, and a reverse search is performed according to this method, and then the mileage driving trajectory of the vehicle side is completed in a reverse tracing manner.

[0093] If the above two methods cannot solve the problem, the missing sections are processed according to the shortest path algorithm of the existing technology (such as Dijkstra algorithm), or the trajectory of the missing sections in the mileage driving trajectory is reconstructed through auxiliary technologies (GNSS, camera, etc.).

[0094] Optionally, the mileage driving track of the vehicle is completed by reverse tracing, including:

[0095] Acquire first node information and second node information in a missing section in the mileage driving trajectory; the second node information is a downstream node of the first node information;

[0096] Determine an upstream node set of the second node information;

[0097] Backtracking each upstream node in the upstream node set to determine a target node that is consistent with the starting point node of the missing section;

[0098] The first node information, the target node and the second node information are spliced ​​together to complete the mileage driving trajectory of the vehicle.

[0099] In this embodiment, by determining the upstream node (first node information) and the downstream node (second node information) in the missing section, the downstream node (second node information) is traced back to determine the upstream node set of the downstream node (second node information), and the upstream node set of the downstream node (second node information) is determined. Figure 2 As shown, there is a missing Node information between Node ID-1 and Node ID-3. Node ID-3 traces back all upstream Node ID information, and Node ID-3 has 3 sections that may pass through this point (these 3 sections are the upstream node set of Node ID-3). Backtrack for each upstream node in the upstream node set, that is, backtrack the upstreamNodeId (upstream Node ID) of these 3 Node IDs respectively. Among them, Node ID-2 has 3 sections that may pass through this point, and determine the target node that is consistent with the starting node of the missing section, such as checking the upstreamNodeId of Node ID-2, finding that the upstreamNodeId matches Node ID-1, and splicing the first node information, the target node and the second node information, that is, splicing Node ID-1, Node ID-2, and Node ID-3 to obtain the missing trajectory information.

[0100] The method of completing the mileage driving track of the vehicle by reverse tracing is explained below by way of example.

[0101] Reference Figure 3 The ambiguous path shown: Between 1 and 5, there are two paths, 1-2-5 and 1-4-5, from the perspective of a rational driver, that is, there are multiple possible driving paths at the starting point and the end point. When a road node information is missing between 4 and 7, it is found that the track is incomplete, and it is reversed through upstreamNodeId. The upstreamNodeId of 7 is 5, and the upstreamNodeId of 5 is 2 and 4. At this time, 4 is consistent with the starting point Node ID-4 of the missing section, and the track restoration is completed.

[0102] When there are many missing Node IDs, this method can restore the possible Node IDs. For example, the trajectory between 1 and 8 is incomplete, and the upstreamNodeId of 8 is 6 and 7, the upstreamNodeId of 6 is 3 and 5, and the upstreamNodeId of 7 is 5... Between 1 and 8, there are possible paths such as 1-2-3-6-8, 1-4-5-7-8, 1-2-5-7-8, etc. Further, the driving direction (heading angle) / driving history trajectory (the vehicle has a recorded history trajectory) passing each point is retrieved to reduce the search range. For example, at point 8, the driving direction / driving trajectory when passing this point is retrieved, whether it is 6->8 or 7->8, and the upstream node can be accurately located in the upstream search point of point 8, and then this method is repeated and searched in reverse order. If it is found to be 6->8, the driving direction / driving history trajectory passing point 6 is retrieved, whether it is 3->6 or 5->6, and in this way, the most likely path can be restored.

[0103] Optionally, the above step 13 includes:

[0104] Determining the preset charging conditions corresponding to the toll road section according to the mileage driving data; the preset charging conditions at least include the toll tax rate;

[0105] The mileage billing on the vehicle side is determined based on a weighted calculation of the mileage driving data and the payment tax rate.

[0106] In the embodiment of the present application, the mileage driving data has been determined above, and it can be determined whether the mileage driving data all belongs to the toll road section for judgment, and the toll road section in the mileage driving data is charged. The toll tax rate is a necessary condition in the preset charging conditions corresponding to the toll road section. Of course, the preset charging conditions can also include a variety of additional conditions, such as: preferential road section information in the toll road section, the charging method of the toll vehicle model, lane type information, etc. According to the weighted calculation of the mileage driving data and the toll tax rate, and the weighted calculation of the additional conditions and the mileage driving data, the final mileage charging of the vehicle end is determined through the results of the two weighted calculations.

[0107] The above processing is explained below through two specific embodiments.

[0108] In the first specific embodiment, such as in a highway scenario:

[0109] When a vehicle reaches the entrance of a highway toll station, information is exchanged between the roadside equipment and the onboard equipment. The roadside equipment broadcasts information about entering the toll road section to the vehicle (or the roadside equipment and the onboard equipment exchange information in real time, the cloud records the vehicle's trajectory, and finally extracts the trajectory of passing the toll road section).

[0110] Take the case where the communication mode is unicast and the recording subject is the vehicle side as an example: a unicast connection is established between the roadside device and the vehicle-mounted device, and the vehicle-mounted device records information, that is, the vehicle passes through the entrance of the highway toll station (marking the starting point of billing, and the vehicle side records the NodeReferenceID at this time (at least fill in the NodeID)).

[0111] The vehicle continues to travel and continuously exchanges information with the roadside equipment. The on-board equipment continuously records the roadside information, including but not limited to the unique identification of the on-board equipment, that is, the on-board identification information (such as the license plate or serial number, etc.), the unique identification of the roadside equipment (such as the serial number of the roadside equipment, etc.), the NodeReferenceID in the Node information (at least fill in the NodeID), the upstreamNodeId in the Link information, and the gantry number. When the vehicle travels to the exit of the highway toll station, the unicast link between the roadside equipment at the exit and the on-board equipment is released, thereby generating relevant information about the vehicle's driving trajectory.

[0112] Next, determine the completeness of the mileage. Use the upstreamNodeId to trace back and match it with the Node ID to find out if there are any missing nodes. If missing node information is found on a long road section, it can be reversed to complete the nodes of this section. However, if there is an ambiguous path road network scenario, the missing sections can be processed according to the shortest path algorithm. Or the trajectory of the missing sections can be reconstructed through auxiliary technologies (GNSS, cameras, etc.). Finally, the mileage of the vehicle obtained through the above steps is combined with other information to calculate the mileage tax.

[0113] In the first specific embodiment, such as in a city road scene:

[0114] When a vehicle reaches the entrance of a highway toll station, information is exchanged between the roadside equipment and the onboard equipment. The roadside equipment broadcasts information about entering the toll road section to the vehicle (or the roadside equipment and the onboard equipment exchange information in real time, the cloud records the vehicle's trajectory, and finally extracts the trajectory of passing the toll road section).

[0115] Take the case where the communication mode is unicast and the recording subject is the vehicle side as an example: a unicast connection is established between the roadside device and the vehicle-mounted device, and the vehicle-mounted device records information, that is, the vehicle passes through the entrance of the toll section of the urban road (marking the starting point of billing, and the vehicle side records the NodeReferenceID at this time (at least fill in the NodeID)).

[0116] The vehicle continues to travel and continuously exchanges information with the roadside equipment. The on-board equipment continuously records the roadside information, including but not limited to the unique identification of the on-board equipment, that is, the on-board identification information (license plate or serial number, etc.), the unique identification of the roadside equipment (such as serial number, etc.), the NodeReferenceID in the Node (at least fill in the NodeID), and the upstreamNodeId in the Link, thereby generating relevant information about the vehicle's driving trajectory.

[0117] When a vehicle reaches the exit of a toll road section in a city, the roadside device broadcasts information to the vehicle that the section is not a toll road section, thereby informing the vehicle that the vehicle has exited the toll road section (marking whether it is the end point of billing), and the unicast link between the roadside device and the on-board device is released.

[0118] Next, determine the completeness of the mileage. Use the upstreamNodeId to track back and match it with the Node ID to find out whether there are any missing nodes. If a node is missing in the missing section information, reverse addressing can be performed; if two nodes are missing in succession, in the chessboard-like road network scenario of the city, the missing sections can be processed according to the shortest path algorithm as shown in the figure above. Alternatively, auxiliary technologies (GNSS, cameras, etc.) can be used to reconstruct the trajectory of the missing sections.

[0119] Finally, the mileage tax is calculated by combining the vehicle mileage obtained through the above steps with other information (such as driving time, etc.).

[0120] In summary, this application utilizes the node deployment method of C-V2X equipment and the message elements in the message set to achieve the effect of accurate charging. At the same time, it avoids the problem of low mileage meter accuracy and easy human tampering, resulting in untrue mileage data. It also achieves the effect of ETC free-flow charging and broadens the application scenarios, which is suitable for mileage tax billing on all road sections.

[0121] Reference Figure 4 As shown, the embodiment of the present application provides a mileage billing method, which is applied in the cloud, including:

[0122] Step 41, obtaining stored information of the interaction between the vehicle end and the roadside device; the stored information includes message elements of the interaction between the vehicle end and the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification;

[0123] Step 42, determining the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0124] Step 43, determine the mileage billing on the vehicle side based on the mileage driving data and preset charging conditions.

[0125] It should be noted that the message elements in the stored information are the same as the message elements obtained by the vehicle end. To avoid repetition, they will not be repeated here.

[0126] In the embodiment of the present application, the biggest difference between the cloud side and the vehicle side is that the storage information of the interaction between the vehicle side and the roadside equipment is obtained through step 41, and the storage information is processed according to the processing capability of the cloud side, and the mileage billing is sent to the vehicle side, which reduces the problem of large storage and processing volume on the vehicle side. The mileage billing determined by the vehicle side itself can also be proofread to prevent abnormal mileage billing problems from occurring.

[0127] Optionally, step 41, obtaining stored information of the interaction between the vehicle terminal and the roadside equipment, includes:

[0128] Obtain the storage information sent by the vehicle end; or,

[0129] Obtain the storage information sent by the roadside equipment.

[0130] In the implementation of the present application, when a vehicle is driving, there are two locations for storing and recording vehicle trajectory information: it can be the vehicle side or the road side. Therefore, the method for obtaining the stored information can be sent by the vehicle side or by the roadside equipment.

[0131] When storing information on the vehicle:

[0132] The vehicle continuously broadcasts / unicasts interactive information with the roadside equipment (RSU) while driving (not relying on GNSS positioning, similar to ETC), or records location information from the cloud and other maps based on real-time positioning information (the recorded information can be the map message in V2X, or it can exist in the on-board map).

[0133] The on-board equipment continuously records the roadside information, including at least the unique identification of the on-board equipment (license plate or serial number, etc.), the unique identification of the roadside equipment (serial number, etc.), the NodeReferenceID in the Node (at least fill in the NodeID), and the upstreamNodeId in the link, so as to obtain the relevant information of the vehicle's driving trajectory.

[0134] It should be noted that there are two types of roadside Nodes: one is the node that expresses the road topology, and the other is the node that expresses the RSU location point.

[0135] It should also be noted that the NodeId and upstreamNodeId in this application can be a directional road segment with a starting point (upstream NodeId) and an end point (downstream NodeId). NodeId and upstreamNodeId are currently used in the C-V2X system. Similar expressions in electronic maps are not excluded.

[0136] When the track information is recorded at the road end:

[0137] Vehicles continuously broadcast / unicast interactive information with roadside equipment while driving. Roadside equipment continuously records vehicle information, including at least the unique identifier of the vehicle-mounted equipment (license plate or serial number, etc.), the unique identifier of the roadside equipment (serial number, etc.), the NodeReferenceID in the Node (at least fill in the NodeID), and the upstreamNodeId in the Link, thereby obtaining the vehicle identification information passing through this roadside equipment. In the future, the cloud computing center will be able to track the driving trajectory of each vehicle through decryption and other methods (here, the interaction process between the roadside and the cloud involves encryption and decryption to ensure information security).

[0138] Optionally, the stored information is formed after the vehicle enters the geographic fence of the target roadside device and interacts with the target roadside device in the form of broadcasting; or,

[0139] The stored information is stored after interacting with the target roadside device in a unicast form.

[0140] In one implementation of the present application, when the vehicle enters the geographic fence of the target RSU, the message elements for interacting with the target RSU are obtained through broadcasting. That is, as long as the vehicle enters the geographic fence of the target RSU, after information interaction with the target RSU, the trajectory information is recorded, that is, the message elements are recorded.

[0141] Among them, the broadcast method requires demarcating an area within the coverage of the target RSU that does not overlap with the coverage of other RSUs (i.e., a small map fence is divided around each roadside equipment location point (or Node point) with this as the center), in order to prevent different RSUs from recording the trajectory information of a vehicle at the same time. This application has two methods for uniquely identifying vehicle trajectory points: one is the Node ID information of the road on which the vehicle is traveling, and the other is the Node ID information of the roadside RSU.

[0142] In another implementation of the present application, the message elements are obtained by interacting with the target RSU in a unicast manner. Through this unicast interaction method, non-target RSUs can be prevented from simultaneously recording the trajectory information of a vehicle, thereby improving the accuracy of data interaction.

[0143] Optionally, the above step 42 includes:

[0144] According to the roadside signs, determining a plurality of vehicle-mounted sign information stored in a roadside device corresponding to each roadside sign;

[0145] The mileage driving data of the vehicle is determined according to the plurality of vehicle-mounted identification information, the road node information and the road section information corresponding to each roadside identification, and a preset decryption algorithm.

[0146] In the embodiment of the present application, the cloud can determine the multiple vehicle identification information reported by each roadside device according to the roadside identification, that is, one roadside RSU can report the vehicle identification information of multiple vehicles. The cloud can determine the mileage driving trajectory of the vehicle end according to the multiple vehicle identification information, the road node information and road section information corresponding to each roadside identification, and the preset decryption algorithm, and send it to the vehicle end.

[0147] It can be understood that the roadside equipment or the cloud stores the vehicle identification information of each vehicle that passes by, and the vehicle identification information of each vehicle is restored by decryption in the cloud, and all the roadside identification information passed by the vehicle identification information of the same vehicle is summarized and screened to determine the mileage trajectory of the vehicle.

[0148] In another implementation method, the cloud can also directly obtain road node information. Since the roadside equipment is arranged at the road node, it can also obtain multiple vehicle identification information reported by each roadside device. Similarly, based on the cloud, based on multiple vehicle identification information, multiple road node information and multiple road section information, as well as a preset decryption algorithm, the mileage driving trajectory of the vehicle side is determined and sent to the vehicle side.

[0149] Optionally, after step 42, the method further includes:

[0150] Determining whether the mileage driving track of the vehicle is complete;

[0151] If the mileage driving track is incomplete, then the mileage driving track of the vehicle end is completed;

[0152] If the mileage driving trajectory is complete, the step of determining the mileage billing on the vehicle side according to the mileage driving data and the preset charging conditions is executed.

[0153] In the embodiment of the present application, after determining the mileage driving track of the vehicle side, the mileage driving track of the vehicle side is also judged. If it is determined that the mileage driving track is incomplete, the mileage driving track of the vehicle side is completed, so as to ensure accurate calculation of the driving track or mileage of the vehicle side, and prevent abnormal billing problems in subsequent mileage billing. If it is determined that the mileage driving track is complete, step 43 is executed.

[0154] Optionally, determining whether the mileage driving track of the vehicle is complete includes:

[0155] Determine whether the target upstream node identifier in the road information of the target roadside equipment in the mileage driving trajectory corresponds to the target road node information upstream of the target roadside equipment;

[0156] If the target upstream node identifier does not correspond to the target road node information, it is determined that the mileage driving trajectory is incomplete;

[0157] Otherwise, it is determined that the mileage driving trajectory is complete.

[0158] In the embodiment of the present application, among the multiple roadside devices in the mileage driving trajectory, the upstream node identification of the target roadside device (the target roadside device is any roadside device among the multiple roadside devices) is obtained to determine whether it corresponds to the target road node upstream of the target roadside device. For example, if the multiple roadside devices include RSU1 to RSU5, the upstream node identification of the target RSU (RSU2) is obtained, and the road node information upstream of the target RSU (RSU2), that is, the Node information of RSU1, is obtained. If the upstream node identification of the target RSU (RSU2) corresponds to the Node information of RSU1, it is determined that the trajectory of the target RSU (RSU2) is complete. Each RSU between RSU1 and RSU5 is further verified, so that the integrity of the mileage driving trajectory can be determined.

[0159] Optionally, if the mileage driving track is incomplete, completing the mileage driving track of the vehicle side includes:

[0160] When it is determined that one of the road node information is missing in the mileage driving trajectory, the mileage driving trajectory of the vehicle is completed by reverse tracing;

[0161] When it is determined that at least two road node information are missing in the mileage driving trajectory, the driving direction and / or driving history trajectory of each road node information is obtained, and the mileage driving trajectory of the vehicle end is completed based on the driving direction and / or the driving history trajectory in combination with the reverse tracing method.

[0162] In one implementation of the present application, when it is determined that a Node information is missing in the mileage driving trajectory, the mileage driving trajectory of the vehicle side is completed in a reverse tracing manner based on the upstream and downstream Node information adjacent to the missing Node information. In another implementation of the present application, when it is determined that at least two Node information are missing in the mileage driving trajectory, the driving direction (such as heading angle, etc.) or driving history trajectory (the vehicle side has a recorded history trajectory) passing through each Node information is retrieved, and the driving direction / driving history trajectory is combined with the Node information to solve the problem of multiple missing points and reduce the search range. The driving direction can accurately locate which upstream node it is, and a reverse search is performed according to this method, and then the mileage driving trajectory of the vehicle side is completed in a reverse tracing manner.

[0163] If the above two methods cannot solve the problem, the missing sections are processed according to the shortest path algorithm of the existing technology (such as Dijkstra algorithm), or the trajectory of the missing sections in the mileage driving trajectory is reconstructed through auxiliary technologies (GNSS, camera, etc.).

[0164] Optionally, the mileage driving track of the vehicle is completed by reverse tracing, including:

[0165] Acquire first node information and second node information in a missing section in the mileage driving trajectory; the second node information is a downstream node of the first node information;

[0166] Determine an upstream node set of the second node information;

[0167] Backtracking each upstream node in the upstream node set to determine a target node that is consistent with the starting point node of the missing section;

[0168] The first node information, the target node and the second node information are spliced ​​together to complete the mileage driving trajectory of the vehicle.

[0169] In this embodiment, by determining the upstream node (first node information) and the downstream node (second node information) in the missing section, the downstream node (second node information) is traced back to determine the upstream node set of the downstream node (second node information), and the upstream node set of the downstream node (second node information) is determined. Figure 2As shown, there is a missing Node information between Node ID-1 and Node ID-3. Node ID-3 traces back all upstream Node ID information, and Node ID-3 has 3 sections that may pass through this point (these 3 sections are the upstream node set of Node ID-3). Backtrack for each upstream node in the upstream node set, that is, backtrack the upstreamNodeId (upstream Node ID) of these 3 Node IDs respectively. Among them, Node ID-2 has 3 sections that may pass through this point, and determine the target node that is consistent with the starting node of the missing section, such as checking the upstreamNodeId of Node ID-2, finding that the upstreamNodeId matches Node ID-1, and splicing the first node information, the target node and the second node information, that is, splicing Node ID-1, Node ID-2, and Node ID-3 to obtain the missing trajectory information.

[0170] Optionally, the above step 43 includes:

[0171] Determining the preset charging conditions corresponding to the toll road section according to the mileage driving data; the preset charging conditions at least include the toll tax rate;

[0172] The mileage billing on the vehicle side is determined based on the weighted calculation of the mileage driving data and the payment tax rate, and the mileage billing is sent to the vehicle side.

[0173] In the embodiment of the present application, the mileage driving data has been determined above, and it can be determined whether the mileage driving data all belongs to the toll road section for judgment, and the toll road section in the mileage driving data is charged. The toll tax rate is a necessary condition in the preset charging conditions corresponding to the toll road section. Of course, the preset charging conditions can also include a variety of additional conditions, such as: preferential road section information in the toll road section, the charging method of the toll vehicle model, lane type information, etc. According to the weighted calculation of the mileage driving data and the toll tax rate, and the weighted calculation of the additional conditions and the mileage driving data, the final vehicle-side mileage billing is determined through the results of the two weighted calculations, and the mileage billing is sent to the vehicle-side.

[0174] In summary, this application utilizes the node deployment method of C-V2X equipment and the message elements in the message set to achieve the effect of accurate charging. At the same time, the cloud processing method can provide proofreading for the vehicle side and reduce the data carrying capacity of the vehicle.

[0175] Reference Figure 5 As shown, the embodiment of the present application also provides a mileage metering device, which is applied to a vehicle side, including:

[0176] The first acquisition module 51 is used to acquire message elements interacting with the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification;

[0177] A first determination module 52, configured to determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0178] The second determination module 53 is used to determine the mileage billing on the vehicle side according to the mileage driving data and preset charging conditions.

[0179] Optionally, the mileage metering device further includes:

[0180] The first processing module is used to store the message elements in the vehicle to form storage information, and send the storage information to the cloud.

[0181] Optionally, the first acquisition module 51 includes:

[0182] A first acquisition unit is configured to enter a geographic fence range of a target roadside device and acquire a message element interacting with the target roadside device in a broadcasting manner; or

[0183] The second acquisition unit is used to interact with the target roadside device in a unicast manner to acquire a message element of the target roadside device interaction.

[0184] Optionally, the first determining module 52 includes:

[0185] A first determining unit is used to determine the roadside identification of each roadside device passed by the vehicle according to the vehicle identification information;

[0186] A second determining unit is used to connect the road node information corresponding to each of the roadside signs and the upstream node signs of the road section information respectively to determine the mileage driving trajectory of the vehicle end;

[0187] Alternatively, the message element is sent to the cloud;

[0188] The third determination unit is used to receive the mileage driving trajectory of the vehicle side sent by the cloud; the cloud side determines the mileage driving data of the vehicle side according to the vehicle-mounted identification information, the roadside identification, the road node information and the road section information.

[0189] Optionally, the mileage metering device further includes:

[0190] A first judgment module is used to judge whether the mileage driving track of the vehicle end is complete;

[0191] A second processing module, configured to complete the mileage driving track of the vehicle if the mileage driving track is incomplete;

[0192] The third processing module is used to execute the step of determining the mileage billing on the vehicle side according to the mileage driving data and preset charging conditions if the mileage driving trajectory is complete.

[0193] Optionally, the first determination module includes:

[0194] A fourth determination unit is used to determine whether the target upstream node identifier in the road information of the target roadside equipment in the mileage driving trajectory corresponds to the target road node information upstream of the target roadside equipment;

[0195] a fifth determining unit, configured to determine that the mileage driving trajectory is incomplete if the target upstream node identifier does not correspond to the target road node information;

[0196] A sixth determination unit is used to determine that the mileage driving trajectory is complete otherwise.

[0197] Optionally, the second processing module includes:

[0198] a seventh determining unit, configured to complete the mileage driving trajectory of the vehicle by reverse tracing when determining that one of the road node information is missing in the mileage driving trajectory;

[0199] The eighth determination unit is used to determine that when at least two of the road node information are missing in the mileage driving trajectory, obtain the driving direction and / or driving history trajectory of each of the road node information, and complete the mileage driving trajectory of the vehicle end according to the driving direction and / or the driving history trajectory in combination with the reverse tracing method.

[0200] Optionally, the seventh determining unit includes:

[0201] A first acquisition subunit is used to acquire first node information and second node information in a missing section in the mileage driving trajectory; the second node information is a downstream node of the first node information;

[0202] A first determining subunit, used to determine an upstream node set of second node information;

[0203] A second determination subunit is used to backtrack each upstream node in the upstream node set to determine a target node that is consistent with the starting point node of the missing section;

[0204] The first processing sub-unit is used to splice the first node information, the target node and the second node information to complete the mileage driving trajectory of the vehicle.

[0205] Optionally, the second determining module 53 includes:

[0206] A first processing unit is used to determine the preset charging conditions corresponding to the toll road section according to the mileage driving data; the preset charging conditions at least include a toll tax rate;

[0207] The second processing unit is used to determine the mileage billing on the vehicle side based on the weighted calculation of the mileage driving data and the payment tax rate.

[0208] Among them, the implementation embodiments of the above-mentioned mileage metering method are all applicable to the embodiments of the mileage metering device and can achieve the same technical effect.

[0209] Reference Figure 6 As shown, the embodiment of the present application also provides a mileage metering device, which is applied to the cloud, including:

[0210] The second acquisition module 61 is used to acquire the stored information of the interaction between the vehicle end and the roadside device; the stored information includes the message elements of the interaction between the vehicle end and the roadside device; the message elements include the vehicle identification information of the vehicle-mounted device, the roadside identification of the roadside device, the road node information and the road section information; the road node information includes the global area identification and / or the local node identification; the road section information at least includes the upstream node identification;

[0211] A third determination module 62, configured to determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information;

[0212] The fourth determination module 63 is used to determine the mileage billing on the vehicle side according to the mileage driving data and preset charging conditions.

[0213] Optionally, the second acquisition module 61 includes:

[0214] A third acquisition unit is used to acquire the storage information sent by the vehicle end; or

[0215] The fourth acquisition unit is used to acquire the storage information sent by the roadside equipment.

[0216] Optionally, the stored information is formed after the vehicle enters the geographic fence of the target roadside device and interacts with the target roadside device in the form of broadcasting; or,

[0217] The stored information is stored after interacting with the target roadside device in a unicast form.

[0218] Optionally, the third determining module 62 includes:

[0219] A ninth determining unit, configured to determine, according to the roadside sign, a plurality of vehicle identification information stored in a roadside device corresponding to each roadside sign;

[0220] The tenth determination unit is used to determine the mileage driving data of the vehicle side according to the multiple vehicle-mounted identification information, the road node information and the road section information corresponding to each roadside identification, and a preset decryption algorithm.

[0221] Optionally, the mileage metering device further includes:

[0222] The second judgment module is used to judge whether the mileage driving track of the vehicle end is complete;

[0223] A fourth processing module, configured to complete the mileage driving track of the vehicle end if the mileage driving track is incomplete;

[0224] The fifth processing module is used to execute the step of determining the mileage billing on the vehicle side according to the mileage driving data and preset charging conditions if the mileage driving trajectory is complete.

[0225] Optionally, the second judgment module includes:

[0226] an eleventh determining unit, configured to determine whether a target upstream node identifier in the road information of the target roadside device in the mileage driving trajectory corresponds to target road node information upstream of the target roadside device;

[0227] a twelfth determining unit, configured to determine that the mileage driving trajectory is incomplete if the target upstream node identifier does not correspond to the target road node information;

[0228] A thirteenth determining unit is used to determine that the mileage driving trajectory is complete otherwise.

[0229] Optionally, the fourth processing module includes:

[0230] A fourteenth determining unit, configured to complete the mileage driving trajectory of the vehicle by reverse tracing when determining that one of the road node information is missing in the mileage driving trajectory;

[0231] The fifteenth determination unit is used to determine that when at least two of the road node information are missing in the mileage driving trajectory, obtain the driving direction and / or driving history trajectory of each of the road node information, and complete the mileage driving trajectory of the vehicle end according to the driving direction and / or the driving history trajectory in combination with the reverse tracing method.

[0232] Optionally, the eighteenth determining unit includes:

[0233] A second acquisition subunit is used to acquire first node information and second node information in a missing section in the mileage driving trajectory; the second node information is a downstream node of the first node information;

[0234] A third determining subunit, used to determine an upstream node set of the second node information;

[0235] A fourth determination subunit is used to backtrack each upstream node in the upstream node set to determine a target node that is consistent with the starting point node of the missing section;

[0236] The second processing sub-unit is used to splice the first node information, the target node and the second node information to complete the mileage driving trajectory of the vehicle.

[0237] Optionally, the fourth determining module 63 includes:

[0238] A third processing unit is used to determine the preset charging conditions corresponding to the toll road section according to the mileage driving data; the preset charging conditions at least include a toll tax rate;

[0239] The fourth processing unit is used to determine the mileage billing of the vehicle side according to the weighted calculation of the mileage driving data and the payment tax rate, and send the mileage billing to the vehicle side.

[0240] Among them, the implementation embodiments of the above-mentioned mileage metering method are all applicable to the embodiments of the mileage metering device and can achieve the same technical effect.

[0241] A readable storage medium in an embodiment of the present application stores a program or instruction thereon. When the program or instruction is executed by a processor, the steps in the mileage billing method as described above are implemented and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0242] The processor is the processor in the mileage charging method described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0243] In the embodiment of the present application, module can be implemented with software so that it can be executed by various types of processors. For example, an executable code module of an identification can include one or more physical or logical blocks of computer instructions, for example, it can be constructed as an object, process or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different positions, and when these instructions are logically combined together, it constitutes a module and realizes the specified purpose of the module.

[0244] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed among different programs, and distributed across a plurality of memory devices. Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form. The operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0245] When a module can be implemented by software, considering the level of existing hardware technology, a person skilled in the art can build a corresponding hardware circuit to implement the corresponding function of the module that can be implemented by software without considering the cost. The hardware circuit includes a conventional very large scale integration (VLSI) circuit or gate array and existing semiconductors such as logic chips, transistors, or other discrete components. The module can also be implemented by a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0246] The above exemplary embodiments are described with reference to the accompanying drawings, and many different forms and embodiments are feasible without departing from the spirit and teachings of the present application. Therefore, the present application should not be constructed as a limitation of the exemplary embodiments proposed herein. More specifically, these exemplary embodiments are provided so that the present application will be perfect and complete, and the scope of the present application will be conveyed to those who are familiar with the technology. In these figures, the component sizes and relative sizes may be exaggerated for clarity. The terms used here are only based on the purpose of describing specific exemplary embodiments and are not intended to be limiting. As used herein, unless the text clearly indicates otherwise, the singular forms "one", "an" and "the" are intended to include these multiple forms. It will be further understood that the terms "comprising" and / or "including" when used in this specification indicate the presence of the features, integers, steps, operations, components and / or components, but do not exclude the presence or increase of one or more other features, integers, steps, operations, components, components and / or their groups. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0247] The above is a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles described in the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A mileage charging method, characterized in that: Applied to the vehicle side, including: Acquire message elements interacting with the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification; Determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information; The mileage billing on the vehicle side is determined based on the mileage driving data and preset charging conditions.

2. The method according to claim 1, characterized in that The method further comprises: The message elements are stored in the vehicle to form storage information, and the storage information is sent to the cloud.

3. The method according to claim 1, characterized in that Get the message elements for interacting with roadside equipment, including: Entering the geographic fence of the target roadside device, obtaining the message element for interacting with the target roadside device in the form of broadcast; or, Interact with the target roadside device in a unicast manner to obtain message elements of the target roadside device interaction.

4. The method according to claim 1, characterized in that: Determine the vehicle's mileage data, including: Determine the roadside identification of each roadside device passed by the vehicle according to the vehicle identification information; Connect the road node information corresponding to each roadside sign and the upstream node sign of the road section information respectively to determine the mileage driving trajectory of the vehicle end; Alternatively, the message element is sent to the cloud; Receive the mileage driving trajectory of the vehicle side sent by the cloud; the cloud side determines the mileage driving data of the vehicle side according to the vehicle identification information, the roadside identification, the road node information and the road section information.

5. The method according to claim 1, characterized in that After determining the mileage data of the vehicle, it also includes: Determining whether the mileage driving track of the vehicle is complete; If the mileage driving track is incomplete, then the mileage driving track of the vehicle end is completed; If the mileage driving trajectory is complete, the step of determining the mileage billing on the vehicle side according to the mileage driving data and the preset charging conditions is executed.

6. The method according to claim 5, characterized in that Determining whether the mileage driving track of the vehicle is complete includes: Determine whether the target upstream node identifier in the road information of the target roadside equipment in the mileage driving trajectory corresponds to the target road node information upstream of the target roadside equipment; If the target upstream node identifier does not correspond to the target road node information, it is determined that the mileage driving trajectory is incomplete; Otherwise, it is determined that the mileage driving trajectory is complete.

7. The method according to claim 5, characterized in that If the mileage driving track is incomplete, the mileage driving track of the vehicle is completed, including: When it is determined that one of the road node information is missing in the mileage driving trajectory, the mileage driving trajectory of the vehicle is completed by reverse tracing; When it is determined that at least two road node information are missing in the mileage driving trajectory, the driving direction and / or driving history trajectory of each road node information is obtained, and the mileage driving trajectory of the vehicle end is completed based on the driving direction and / or the driving history trajectory in combination with the reverse tracing method.

8. The method according to claim 7, characterized in that The mileage track of the vehicle is completed by reverse tracing, including: Acquire first node information and second node information in a missing section in the mileage driving trajectory; the second node information is a downstream node of the first node information; Determine an upstream node set of the second node information; Backtracking each upstream node in the upstream node set to determine a target node that is consistent with the starting point node of the missing section; The first node information, the target node and the second node information are spliced ​​together to complete the mileage driving trajectory of the vehicle.

9. The method according to claim 1, characterized in that: Determine the vehicle-side mileage charges based on mileage data and preset charging conditions, including: Determine the preset charging conditions corresponding to the toll road section according to the mileage driving data; the preset charging conditions at least include the toll tax rate; The mileage billing on the vehicle side is determined based on a weighted calculation of the mileage driving data and the payment tax rate.

10. A mileage charging method, characterized in that: Applied in the cloud, including: Acquire stored information of the interaction between the vehicle end and the roadside device; the stored information includes message elements of the interaction between the vehicle end and the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification; Determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information; The mileage billing on the vehicle side is determined based on the mileage driving data and preset charging conditions.

11. The method according to claim 10, characterized in that Obtain the stored information of the interaction between the vehicle and the roadside equipment, including: Obtain the storage information sent by the vehicle end; or, Obtain the storage information sent by the roadside equipment.

12. The method according to claim 10, characterized in that The stored information is formed after the vehicle enters the geographic fence of the target roadside device and interacts with the target roadside device in the form of broadcasting; or The stored information is stored after interacting with the target roadside device in a unicast form.

13. The method according to claim 10, characterized in that Determine the vehicle's mileage data, including: According to the roadside signs, determining a plurality of vehicle-mounted sign information stored in a roadside device corresponding to each roadside sign; The mileage driving data of the vehicle is determined according to the plurality of vehicle-mounted identification information, the road node information and the road section information corresponding to each roadside identification, and a preset decryption algorithm.

14. The method according to claim 10, characterized in that After determining the mileage data of the vehicle, it also includes: Determining whether the mileage driving track of the vehicle is complete; If the mileage driving track is incomplete, then the mileage driving track of the vehicle end is completed; If the mileage driving trajectory is complete, the step of determining the mileage billing on the vehicle side according to the mileage driving data and the preset charging conditions is executed.

15. The method according to claim 14, characterized in that Determining whether the mileage driving track of the vehicle is complete includes: Determine whether the target upstream node identifier in the road information of the target roadside equipment in the mileage driving trajectory corresponds to the target road node information upstream of the target roadside equipment; If the target upstream node identifier does not correspond to the target road node information, it is determined that the mileage driving trajectory is incomplete; Otherwise, it is determined that the mileage driving trajectory is complete.

16. The method according to claim 14, characterized in that If the mileage driving track is incomplete, the mileage driving track of the vehicle is completed, including: When it is determined that one of the road node information is missing in the mileage driving trajectory, the mileage driving trajectory of the vehicle is completed by reverse tracing; When it is determined that at least two road node information are missing in the mileage driving trajectory, the driving direction and / or driving history trajectory of each road node information is obtained, and the mileage driving trajectory of the vehicle end is completed based on the driving direction and / or the driving history trajectory in combination with the reverse tracing method.

17. The method according to claim 16, characterized in that The mileage track of the vehicle is completed by reverse tracing, including: Acquire first node information and second node information in a missing section in the mileage driving trajectory; the second node information is a downstream node of the first node information; Determine an upstream node set of the second node information; Backtracking each upstream node in the upstream node set to determine a target node that is consistent with the starting point node of the missing section; The first node information, the target node and the second node information are spliced ​​together to complete the mileage driving trajectory of the vehicle.

18. The method according to claim 10, characterized in that Determine the mileage charge of the vehicle end according to the mileage driving data and the preset charging conditions, and send the mileage charge to the vehicle end, including: Determine the preset charging conditions corresponding to the toll road section according to the mileage driving data; the preset charging conditions at least include the toll tax rate; The mileage billing on the vehicle side is determined based on the weighted calculation of the mileage driving data and the payment tax rate, and the mileage billing is sent to the vehicle side.

19. A mileage metering device, characterized in that: Applied to the vehicle side, including: A first acquisition module is used to acquire message elements interacting with a roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification; A first determination module is used to determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information; The second determination module is used to determine the mileage billing on the vehicle side according to the mileage driving data and preset charging conditions.

20. A mileage metering device, characterized in that: Applied in the cloud, including: A second acquisition module is used to acquire stored information of the interaction between the vehicle end and the roadside device; the stored information includes message elements of the interaction between the vehicle end and the roadside device; the message elements include vehicle identification information of the vehicle-mounted device, roadside identification of the roadside device, road node information and road section information; the road node information includes a global area identification and / or a local node identification; the road section information includes at least an upstream node identification; A third determination module is used to determine the mileage driving data of the vehicle end according to the vehicle identification information, the roadside identification, the road node information and the road section information; The fourth determination module is used to determine the mileage billing on the vehicle side based on the mileage driving data and preset charging conditions.

21. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by the processor, the steps in the mileage billing method as described in any one of claims 1 to 9 are implemented, or the steps in the mileage billing method as described in any one of claims 10 to 18 are implemented.