Secure Vehicle Service Communications

Abstract

Secure vehicle service communications are described herein. An example device may include a processor and an external communication component. The external communication component may be coupled to the processor and may be configured to generate an external private key and an external public key in response to determining that a vehicle entity is within a certain proximity of the external communication component, provide the external public key and data to a vehicle communication component associated with the vehicle entity, receive data from the vehicle communication component in response to providing the external public key and data to the vehicle communication component, decrypt the received data using the external private key, and provide services to the vehicle entity based on the decrypted received data.

Description

Technical Field

[0001] The present disclosure relates generally to vehicle-related devices and methods, and more particularly, to secure vehicle services communications. Background Art

[0002] Motor vehicles, such as autonomous and / or non-autonomous vehicles (e.g., cars, sedans, trucks, buses, etc.), can use sensors and / or cameras to obtain information about their surroundings to operate safely. For example, an autonomous vehicle can control its speed and / or direction, and can identify and / or avoid obstacles and / or hazards based on information obtained from sensors and / or cameras. For example, a vehicle can use light detection and ranging (LIDAR), vehicle-to-everything (V2X), RADAR and / or SONAR detection technology, etc., to obtain information about its surroundings. As used herein, an autonomous vehicle may be a vehicle in which at least part of the decision-making and / or control of the vehicle's operation is controlled by computer hardware and / or software / firmware, rather than a human operator. For example, an autonomous vehicle may be an unmanned vehicle. Summary of the invention

[0003] According to one aspect of the present application, a device is provided. The device includes: a processor; and an external communication component coupled to the processor, wherein the external communication component is configured to perform the following operations in response to determining that a vehicle entity is within a specific proximity of the external communication component: generate an external private key and an external public key; provide the external public key and data to a vehicle communication component associated with the vehicle entity; receive data from the vehicle communication component in response to providing the external public key and data to the vehicle communication component; decrypt the received data using the external private key; and provide a service to the vehicle entity based on the decrypted received data.

[0004] According to another aspect of the present application, a method is provided. The method includes: generating an external private key and an external public key; providing the external public key to a vehicle communication component associated with a vehicle entity; receiving a vehicle public key from the vehicle communication component; encrypting data using the vehicle public key; providing the encrypted data to the vehicle communication component; receiving data from the vehicle communication component in response to providing the encrypted data to the vehicle communication component; decrypting the received data using the external private key; and providing a service to the vehicle entity based on the decrypted received data.

[0005] According to another aspect of the present application, a device is provided. The device includes: a processor; and a vehicle communication component coupled to the processor, wherein the vehicle communication component is configured to perform the following operations in response to determining that the vehicle communication component is within a specific proximity of an external communication component: generate a vehicle private key and a vehicle public key; provide the vehicle public key to the external communication component, wherein the external communication component is associated with a service; receive the external public key from the external communication component; encrypt data using the external public key; provide the encrypted data to the external communication component; and receive data from the external communication component in response to providing the encrypted data to the external communication component; decrypt the received data using the vehicle private key; and provide a confirmation of accepting the service in response to the decrypted data indicating the service.

[0006] According to another aspect of the present application, a system is provided. The system includes: a vehicle device of a vehicle entity, which includes: a vehicle processor; and a vehicle communication component, which is coupled to the vehicle processor and configured to generate a vehicle private key and a vehicle public key; and an external device, which is coupled to a transportation auxiliary entity, the external device includes: an external processor; and an external communication component, which is coupled to the external processor and configured to perform the following operations: generate an external private key and an external public key; receive the vehicle public key; and encrypt external data using the vehicle public key, wherein the external data indicates a service to be provided to the vehicle entity; wherein the vehicle communication component is further configured to perform the following operations: receive the external public key and external data; decrypt the external data using the vehicle private key; and encrypt vehicle data using the external public key, wherein the encrypted vehicle data indicates a confirmation of the provided service; and wherein the external communication component is further configured to perform the following operations: receive the encrypted vehicle data; and decrypt the vehicle data using the external private key; and provide the service to the vehicle entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a block diagram of an example vehicle entity according to an embodiment of the present disclosure.

[0008] Figure 2 is a block diagram of an example transportation auxiliary entity (eg, a road or lane including external communication components) according to an embodiment of the present disclosure.

[0009] Figure 3 An example communication system according to an embodiment of the present disclosure is shown.

[0010] Figures 4A to 4B Each shows an example transportation environment including a transportation assistance entity and a vehicle entity according to an embodiment of the present disclosure.

[0011] Figure 5 is a block diagram of an example system including an external communication component and a vehicle communication component according to an embodiment of the present disclosure.

[0012] Figure 6 is a block diagram of an example process for determining multiple parameters according to an embodiment of the present disclosure.

[0013] Figure 7 is a block diagram of an example process for determining multiple parameters according to an embodiment of the present disclosure.

[0014] Figure 8 A block diagram of an example process of verifying a certificate according to an embodiment of the present disclosure.

[0015] Fig. 9 A block diagram of an example process of verifying a signature according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0016] Secure vehicle service communications are described herein. An example device may include a processor and an external communication component. The external communication component may be coupled to the processor and may be configured to generate an external private key and an external public key in response to determining that a vehicle entity is within a certain proximity to the external communication component, provide the external public key and data to a vehicle communication component associated with the vehicle entity, receive data from the vehicle communication component in response to providing the external public key and data to the vehicle communication component, decrypt the received data using the external private key, and provide services to the vehicle entity based on the decrypted received data.

[0017] In some previous approaches, vehicles have used cameras and sensors to obtain information about their surroundings. However, the operation of these cameras and sensors may be dependent on weather conditions and may be hampered by adverse weather conditions. External communication components may provide redundancy and / or additional transportation information that may improve vehicle operation, thereby resulting in technical improvements to the vehicle. For example, if a vehicle camera and / or sensor fails due to, for example, a weather-related event, then information provided by an external communication component that may be located on a transportation assisting entity may be used.

[0018] In some previous approaches, vehicles have used sensors, such as vehicle-to-infrastructure (V2I) sensors, to obtain route information along the route from external communication components, such as overhead radio frequency identification (RFID) readers, cameras, traffic lights, lane markings, street lights, road signs, parking meters, etc. However, in these previous approaches, the communication between the vehicle and the external communication components may be public and insecure. In addition, the communication may not be authenticated, thereby potentially introducing malicious activities that may adversely affect vehicle performance.

[0019] As will be described herein, by introducing a secure form of communication to obtain vehicle services and the ability to accurately identify who is requesting and / or receiving vehicle services, information related to malicious activity regarding these vehicle services can be denied, avoided, discarded, etc. Public keys can be exchanged and used to encrypt data, while private keys, which are kept private and exclusive to a single entity, can be used to decrypt the data. In this way, those without the private key are prevented from intercepting the service data and using it for purposes other than those originally intended. In addition, certificates and signatures can be used to verify the identity of the sender of the data and ensure that the data originates from the expected source.

[0020] Figure 1 1 is a block diagram of an example vehicle entity 102 according to an embodiment of the present disclosure. The vehicle entity 102 may be an autonomous vehicle, a conventional non-autonomous vehicle, an emergency vehicle, a service vehicle, etc., and may be referred to as an apparatus. The vehicle entity 102 may include a vehicle computing device 112, such as an onboard computer. The vehicle computing device 112 may include a processor 114 coupled to a vehicle communication component 116 (e.g., a reader, writer, and / or other computing device capable of performing the functions described below), the vehicle communication component being coupled to (e.g., or including) an antenna 119. The vehicle communication component 116 may include a processor 117 coupled to a memory 118 (e.g., a non-volatile flash memory), but the embodiment is not limited thereto.

[0021] The vehicle computing device 112 may control operating parameters, such as steering and speed, of the vehicle entity 102. For example, a controller (not shown) may be coupled to the steering control system 120 and the speed control system 122. In addition, the vehicle computing device 112 may be coupled to an information system 123. The information system 123 may be configured to display messages, such as route information, and may display visual warnings and / or output audible warnings.

[0022] The communication component 116 can receive information from an additional computing device (e.g., from a Figure 2 The processor 114 may receive the route information in response to (e.g., based on) the external computing device 233 described in association with the route information. Figure 2The processor 114 may cause the information system 123 to display the route information from the communication component 116, such as the distance to a construction zone, a lane change, an intersection, a track crossing or a detour, the presence of a pedestrian, the presence of another vehicle, etc.

[0023] Figure 2 FIG2 is a block diagram of an example transportation auxiliary entity 233 (e.g., a road or lane including an external communication component) according to an embodiment of the present disclosure. The transportation auxiliary entity 233 may be a road, a road lane, a traffic sign, a street light, an emergency vehicle, a pedestrian, a traffic bureau, a police officer, etc. The transportation auxiliary entity 233 may be a device that can be positioned, attached, or embedded in a vehicle. Figure 1 Any element, object or individual within or on the vehicle entity 102 that is capable of assisting its external communication components.

[0024] The transport assisting entity 233 may include an external computing device 242, such as an onboard computer. The external computing device 242 may include a processor 244 coupled to an external communication component 246 (e.g., a reader, writer, and / or other computing device capable of performing the functions described below), which is coupled to (e.g., or includes) an antenna 249. The vehicle communication component 246 may include a processor 247 coupled to a memory 248 (e.g., a non-volatile flash memory), but the embodiment is not limited thereto. The antenna 249 of the external computing device 242 may communicate with the antenna 119 of the vehicle entity 102.

[0025] In some examples, antennas 249 and 119 may be loop antennas configured as inductor coils (e.g., solenoids). For example, antenna 119 may surround vehicle entity 102. Antenna 119 may generate an electromagnetic field in response to current flowing through antenna 119. For example, the strength of the electromagnetic field may depend on the number of coils and the amount of current. The electromagnetic field generated by antenna 119 may induce a current in antenna 249 that powers the corresponding external computing device 242. As an example, when vehicle entity 102 brings antenna 119 within communication distance (e.g., communication range) of antenna 249, Figure 1The antenna 119 in the vehicle 102 may induce a current in the antenna 249. For example, the communication distance may depend on the strength of the electromagnetic field generated by the antenna 119. The electromagnetic field generated by the antenna 119 may be set by the number of coils of the antenna 119 and / or the current passing through the antenna 119, so that the communication distance may span the left and right lanes of the road. In some examples, the communication distance may be about 50 cm to about 100 cm on both sides of the vehicle entity 102.

[0026] In some examples, the external computing device 242 may include a plurality of wireless communication devices, such as transmitters, transponders, transceivers, and the like. As an example, the external communication component 246 may be such a wireless communication device. In some examples, the wireless communication device may be a passive wireless communication device powered (e.g., powered) by the vehicle entity 102, as described above. The wireless communication device may be positioned along a route (e.g., a road) on which the vehicle entity 102 may travel. In some examples, the route may include a plurality of roads. For example, the wireless communication device may be embedded in the road, embedded and / or located on the wall of a tunnel along the route, located on a sign such as a traffic sign along the route, located in and / or on a traffic control light along the route, located in and / or on other vehicles along the route, on pedestrians along the route (e.g., carried and / or worn by them), and the like.

[0027] The wireless communication device may transmit route information about a route to the vehicle entity 102 in response to being powered by the vehicle entity 102 and / or collect information from the vehicle entity 102 in response to being powered by the vehicle entity 102. In some examples, the route information may include information that may affect the operation of the vehicle entity 102 along the route, such as information that may affect the direction and / or speed of the vehicle entity 102 along the route. For example, the vehicle entity 102 may adjust its operation and / or indicate that its operation should be adjusted in response to the route information.

[0028] The wireless communication device may be a short-range wireless communication device, such as a near field communication (NFC) tag, an RFID tag, etc. In at least one embodiment, the wireless communication device may include a non-volatile storage component that can be respectively integrated into a chip (e.g., a microchip). Each of the respective chips may be coupled to a respective antenna 249. The respective storage component may store the respective route information.

[0029] In some examples, the wireless communication device is reprogrammable and can be reprogrammed wirelessly in the field. For example, the wireless communication device can be reprogrammed with updated route information to reflect road changes, such as due to road construction, flooding, bridge repairs, detours, lane closures, etc. For examples where the wireless communication device is an NFC tag, a wireless device with NFC capabilities and application software that allows the device to reprogram the NFC tag can be used to reprogram the NFC tag.

[0030] The corresponding wireless communication devices may transmit their corresponding route information to the communication component 116 in response to the vehicle entity 102 passing within the communication range of the corresponding wireless communication device. For example, the corresponding wireless communication devices may transmit their corresponding route information in response to being powered by the communication component 116. The information may be transmitted from the wireless communication device to the communication component 116 in the form of a signal such as a radio frequency signal. For example, the communication device and the communication component 116 may communicate using a radio frequency signal.

[0031] For the example where the wireless communication device is an NFC tag, the communication component 116 can be an NFC reader and can communicate with the wireless communication device using an NFC protocol, which can be stored in the memory 118 for processing by the processor 117. For example, according to the ISO / IEC 18000-3 international standard for passive RFID for air interface communications, the communication component 116 and the wireless communication device can communicate at about 13.56 megahertz. For example, information can be transmitted in the form of a signal having a frequency of about 13.56 megahertz.

[0032] In some examples, the communication distance may be set so that the wireless communication device is activated only when the vehicle entity 102 is too close to the wireless communication device. For example, the wireless communication device may transmit information indicating that the vehicle entity 102 is too close (e.g., within six inches, one foot, etc.) to the communication component 116. For example, the wireless communication device may be embedded in the road and / or located in another vehicle along the centerline and / or edge of the road, and the transmitted information may indicate that the vehicle entity 102 is too close to the centerline, the edge of the road, or another vehicle. The communication component 116 may then transmit the information to the processor 114. The processor 114 may cause the information system 123 to display a visual warning and / or sound an audible alarm indicating that the vehicle entity 102 is too close to the centerline, the edge of the road, or another vehicle. In some examples, in response to the transmitted information, the processor 114 may cause the steering system 120 to steer the vehicle entity 102 away from the centerline, the edge of the road, or another vehicle.

[0033] The wireless communication device may contain information specific to and recognized only by a specific vehicle that forms a specific subset of all vehicles that pass by the wireless communication device (e.g., emergency vehicles (e.g., police cars or fire trucks, ambulances, etc.) or service vehicles). In instances where the vehicle entity 102 is such a vehicle, the communication component 116 may be configured to recognize the information.

[0034] In some examples, the wireless communication device can be used to collect information (e.g., traffic information), such as vehicle speed, the number of vehicles passing the communication device, etc. The communication component 116 can be configured to power the communication device and write information to the powered communication device. For example, the current vehicle speed and / or the date and time can be written to the communication device. The communication device can collect such information from each vehicle passing the communication device. For example, the information can be used to determine the number of vehicles passing on a particular day and time (e.g., traffic volume) and / or the speed of the vehicles on a particular date and time.

[0035] Each of the corresponding wireless communication devices may include different route information. However, the wireless communication devices may be distributed over a relatively short distance of the road, and the route information may vary relatively little from wireless communication device to wireless communication device. Therefore, if the vehicle entity 102 fails to receive information from a wireless communication device, the vehicle entity 102 may receive information from another wireless communication device without a large loss of information. For example, wireless communication devices that are in close proximity to each other and without intervening wireless communication devices may include the same information, so that if the vehicle entity 102 fails to receive information from one of the wireless communication devices, there will be no loss of information.

[0036] The wireless communication devices may be worn or carried by different pedestrians along the road. For example, in response to being powered by the communication component 116, the wireless communication devices may send messages indicating the presence of the corresponding pedestrians to the communication component 116.

[0037] Figure 3 An example communication system 350 is shown according to an embodiment of the present disclosure. The system 350 may include a passive wireless communication device, such as a short-range communication device (e.g., NFC tag 304), which may be as previously described. The NFC tag may be in a vehicle entity 302. The vehicle entity 302 may be configured as Figure 1 304 and includes components of the vehicle entity 102 in addition to an NFC tag 304. The NFC tag 304 may include a chip 308 having a non-volatile storage component 306 that stores information, such as user identity information, user financial information for paying tolls, and / or information about the vehicle entity 302, such as the speed of the vehicle entity 302, the number of passengers in the vehicle entity 302, etc. The NFC tag 304 may include an antenna 310.

[0038] System 350 may include a communication device 316, such as an active communication device (e.g., which includes a power source), which may receive information from NFC tag 304 and / or may transmit information to vehicle entity 302. In some examples, the communication device may include a reader (e.g., an NFC reader), such as a toll reader.

[0039] The communication device 316 may include a processor 317, a memory 318 (e.g., a non-volatile memory), and an antenna 319. The memory 318 may include an NFC protocol that allows the communication device 316 to communicate with the NFC tag 304. For example, the communication device 316 and the NFC tag 304 may communicate using the NFC protocol (e.g., at approximately 13.56 megahertz) and in accordance with the ISO / IEC 18000-3 international standard.

[0040] The communication device 316 can communicate with the operation center. For example, the communication device 316 can be wirelessly coupled or hardwired to the communication center. In some examples, the communication device 316 can communicate with the operation center via WIFI or via the Internet. When the vehicle entity 302 brings the antenna 310 within the communication range of the antenna 319, the communication device 316 can power the NFC tag 304, as previously described. The communication distance can be shorter and can provide better security than previous methods using RFID tags.

[0041] In some examples, the communication device 316 may be a toll reader. For example, the NFC tag 304 may transmit user information for paying a toll to the communication device 316 in response to being powered by the communication device 316. In some cases, the communication device 316 may then send a payment confirmation back to the vehicle entity 302.

[0042] In some examples, the communication device 316 may receive real-time information from the operation center and may transmit the information to the vehicle entity 302. For example, the communication device 316 may transmit road conditions, weather conditions, traffic conditions, etc. to the vehicle entity 302. In some examples, multiple communication devices 316 may be embedded in the road along the route of the vehicle entity 302, located at the entrance to the bridge, located in or on the wall of the tunnel, located in or on the road sign, traffic signal. For example, the communication device 316 may be located anywhere the communication device 104 and / or 204 may be located, as previously described.

[0043] Figures 4A to 4B Each shows an example transportation environment 440 including a transportation auxiliary entity 433 and a vehicle entity 402 according to an embodiment of the present disclosure. Figure 4AAs illustrated in , the external communication component 446 may be embedded in, positioned on, or attached to a transport auxiliary entity 433, such as a road lane. As an example, the external communication component 446 may be embedded in the transport auxiliary entity 433. As illustrated, the transport auxiliary entity 433 is a road lane. The vehicle entity 402 may include a vehicle communication component 416 that communicates with the external communication component 446. The vehicle entity 402 may travel along the transport auxiliary entity 433 in a first direction indicated by an arrow 436 and along the transport auxiliary entity 433 in a second direction indicated by an arrow 438. In this way, the vehicle entity may travel toward, across, and / or away from the external communication component 446. As the vehicle communication component 416 of the vehicle entity 402 approaches a specific proximity of the external communication component 446, communication may begin and / or become enhanced. In this example, the specific proximity may refer to a distance between 50 cm and 100 cm. In an example, the specific proximity may depend on the vehicle antenna system and the tag position in the road. Although the transportation assistance entity is illustrated as comprising a road lane, embodiments of the present disclosure are not limited to this example of a transportation assistance entity.

[0044] Figure 4B 4 is a diagram of a vehicle entity 402 at different entry points, junctions, and exit points associated with the transportation services provided within a transportation environment 440. As an example, the vehicle entity 402 may travel on a first position 432-1 of a first road lane portion 433-1. The first road lane portion 433-1 may include a first external communication component 446-1. When the vehicle entity 402 is extremely close to the vehicle communication component external communication component 446-1, the vehicle communication component 416 may communicate with the external communication component 446-1. In this example, extremely close may refer to a distance greater than 1 meter. In an example, extremely close may refer to a distance less than 2 meters. In an example, extremely close may depend on the maximum distance between the road lane and / or the vehicle antenna system. The communication may indicate that the vehicle entity 402 has entered an entrance for receiving transportation services. When at the first position 432-1, the vehicle communication component 416 may send a vehicle public key to the external communication component 446-1, and the external communication component 446-1 may send an external public key to the vehicle communication component 416.

[0045] These public keys (vehicle and external) can be used to encrypt data sent to each corresponding communication component, and to verify the identity of each communication component and exchange invoice, confirmation and payment information. Figures 5 to 9Further described, the vehicle communication component 416 can encrypt data using the received external public key and send the encrypted data to the external communication component 446-1. Similarly, the external communication component 446-1 can encrypt data using the received vehicle public key and send the encrypted data to the vehicle communication component 416. Data such as service data sent by the vehicle entity 402 may include credit card information, phone number, email address, identification information, payment information, etc. If this modality is enabled, the driver of the vehicle entity 402 can manually indicate payment and / or automatically confirm payment. This payment confirmation can be sent with a digital signature to verify the identity of the vehicle entity 402. Information about the service can be provided to the vehicle entity 402 and displayed on the dashboard of the vehicle entity 402 or sent to an email associated with the vehicle entity 402. The driver of the vehicle entity 402 can manually confirm the details of the service, or the service can be previously enabled and automatically accepted at this time in the process.

[0046] In addition, when the vehicle entity 402 travels to the second position 432-2 of the second road lane portion 433-2 as illustrated by arrow 436-1, the vehicle communication component 416 can communicate with the external communication component 446-2 of the second road lane portion 433-2. The communication between the vehicle communication component 416 and the external communication component 446-2 can indicate that the vehicle entity 402 is in the position 432-2 for receiving transportation services. When the vehicle entity 402 travels to the third position 432-3 of the third road lane portion 433-3 as illustrated by arrow 436-2, the proximity of the vehicle communication component 416 to the external communication component 446-3 can indicate that the vehicle entity 402 has received the service and / or paid for the service. In one example, the vehicle leaving can be identified based on the vehicle's identification, VIN number, etc. together with the vehicle digital signature. After receiving and / or paying, the data associated with the vehicle entity 402 can be discarded, erased, cleared, etc. from the database associated with the external communication component 446-3.

[0047] While this example is described as having an external communication component at each portion of the road, the example is not limited thereto. For example, a single external communication component may communicate with the vehicle entity 402 as it travels through each location, and the proximity to the external communication component may indicate which portion of the process the vehicle entity 402 is traveling through, as described above. Furthermore, in an example, all steps of the process may be performed in a single location, with the vehicle entity 402 entering the location, confirming the service (optionally paying), and receiving the service all at the same location. Additionally, payment may occur prior to receiving the service, immediately after receiving the service, or at a later date through the billing process.

[0048] In an example, the transportation services received by the vehicle entity 402 may include public services (e.g., traveling through a toll booth), parking, and / or vehicle washing. Each of the public services may be paid for by exchanging an invoice, confirmation that the vehicle entity 402 wants the service (optionally accompanied by a signature, as described below, to verify the identity of the vehicle entity 402), and payment for the service by the vehicle entity 402. In another example, the transportation services may include services that do not require payment (e.g., vehicle entry and / or exit from a controlled traffic area), private controlled entry (e.g., entry to a truck hub, taxi stand, etc.), family car garage entry, reserved bus station areas (e.g., bus station areas reserved only for specific companies or businesses), taxi parking and / or taxi waiting areas, etc. In the event that the data sent is accompanied by a signature, the vehicle entity 402 may be prevented from subsequently denying that the vehicle entity 402 requested the transportation service after receiving the service.

[0049] In an example, data exchanged between the vehicle entity 402 and the transport assistance entity 433 may have freshness for use by the other. As an example, data sent by the vehicle entity 402 to the transport assistance entity 433 to indicate the exact same instruction may be altered at each of a specific time frame or for a specific amount of data being sent. This may prevent a hacker from intercepting previously sent data and sending the same data again to produce the same result. If the data has been slightly altered but still indicates the same instruction, the hacker will send the same information at a later point in time, and the same instruction will not be executed due to the recipient expecting the altered data to execute the same instruction.

[0050] Data exchanged between the vehicle entity 402 and the transportation assistance entity 433 may be performed using a number of encryption and / or decryption methods as described below. Ensuring data security may ensure that malicious activity is prevented from interfering with services obtained by the vehicle entity 402 and / or interfering with payment and / or currency received for performing services.

[0051] Figure 5 4 is a block diagram of an example system including an external communication component 546 and a vehicle communication component 516 according to an embodiment of the present disclosure. When a vehicle entity (e.g., 402 in FIG. 4 ) is in close proximity to a road lane (e.g., road lane 433-3), the associated vehicle communication component 516 of the vehicle entity (e.g., 416-1 in FIG. 4 ) can exchange data with the external communication component 546 of the road lane using a sensor (e.g., a radio frequency identification sensor (RFID)).

[0052] A computing device may start up in stages using layers, with each layer authenticating and loading subsequent layers and providing increasingly complex runtime services at each layer. Layers may be served by previous layers and serve subsequent layers, thereby creating an interconnected network of layers that build on lower layers and serve higher layers. Figure 5 As described in the above, layer 0 (“L 0 ”)551 and layer 1 (“L 1 ”) 553 within the external communication component. Layer 0 551 may provide a firmware derived secret (FDS) 552 to layer 1 553. The FDS key 552 may describe the identity and other security-related data of the code of layer 1 553. In an example, a specific protocol (e.g., the Robust Internet of Things (RIOT) core protocol) may use the FDS 552 to verify the code of layer 1 546 that it loads. In an example, the specific protocol may include a device identification combination engine (DICE) and / or the RIOT core protocol. As an example, the FDS may include the layer 1 firmware image itself, a manifest that cryptographically identifies the authorized layer 1 firmware, a firmware version number of the signed firmware in the context of a secure boot implementation, and / or security-critical configuration settings of the device. The device secret 558 may be used to generate the FDS 552 and stored in the memory of the external communication component 553.

[0053] The external communication component may transmit data as illustrated by arrow 554 to the vehicle communication component 516. The transmitted data may include a public external identification, a certificate (e.g., an external identification certificate), and / or an external public key. Layer 2 (“L2”) of the vehicle communication component 516 2 ”) 555 can receive the transmitted data and execute the data in the operation of the operating system (“OS”) 557 and on the first application 559-1 and the second application 559-2.

[0054] In an example operation, external communication component 546 may read device secret 558, the identity of hash layer 1 553, and perform a calculation including the following:

[0055] K L1 =KDF[Fs, Hash(“immutable information”)]

[0056] Where K L1 is the external public key, KDF (e.g., KDF Specification Publications 800-108 defined in the National Institute of Standards and Technology (NIST)) is the key derivation function (i.e., HMAC-SHA256), and Fs is the device secret 558. FDS 552 may be determined by performing the following:

[0057] FDS = HMAC-SHA256[Fs, SHA256 ("immutable information")]

[0058] Likewise, the vehicle communication component 516 may transmit data including a public vehicle identification, certificate (e.g., a vehicle identification certificate), and / or a vehicle public key as illustrated by arrow 556. Where an authentication mode is used, the vehicle communication component 516 may send a vehicle identification number (VIN) for further authentication, identification, and / or verification of the vehicle entity.

[0059] In at least one example, the vehicle entity may log into the roadlane system (e.g., log into the external communication component 446-3) using either an anonymous login or an authenticated login. Authenticated login may allow the vehicle entity to obtain additional information that may not be available when logged in anonymously in anonymous mode. In at least one example, authentication may include providing a vehicle identification number (VIN) and / or authentication information, such as an exchange of a public key, as will be described below. In either of the anonymous and authenticated modes, the roadlane may communicate with the vehicle entity to provide an external public key associated with the roadlane to the vehicle entity.

[0060] Figure 6 is a block diagram of an example process for determining multiple parameters according to an embodiment of the present disclosure. Figure 6 654 is an example of determining parameters including an external public identification, an external certificate, and an external public key, which are then sent to a vehicle communication component (eg, Figure 5 516) of layer 2 (e.g., layer 2 555). Figure 6 Layer 0 (“L 0 ”)651 corresponds to Figure 5 Layer 0 551 in , and likewise FDS 652 corresponds to FDS 552 , layer 1 653 corresponds to layer 1 553 , and arrows 654 and 656 correspond to arrows 554 and 556 , respectively.

[0061] The FDS 652 from Layer 0 651 is sent to Layer 1 653 and is used by the Asymmetric ID Generator 661 to generate a Public Identifier (“ID lk公共 ”) 665 and private identifier 667. In the abbreviation “ID lk公共 ”, “lk” indicates layer k (in this example, layer 1), and “public” indicates that the identity is open for sharing. The public identity 665 is illustrated as being shared by an arrow to the right and outside of layer 1 653 extending to an external communication component. The generated private identity 667 is used as a key input into the encryptor 673. The encryptor 673 may be any processor, computing device, etc. for encrypting data.

[0062] Layer 1 653 of the external communication component may include an asymmetric key generator 663. In at least one example, a random number generator (RND) 636 may optionally input a random number into the asymmetric key generator 663. The asymmetric key generator 663 may generate a random number that is compatible with an external communication component (e.g., Figure 5 The public key (“K Lk公共 ”)669 (called the outer public key) and the private key (“K Lk私用 ”) 671 (referred to as the external private key). The external public key 669 may be input (as “data”) into an encryptor 673. The encryptor 673 may generate a result K′ 675 using the input of the external private identification 667 and the external public key 669. The external private key 671 and the result K′ 675 may be input into an additional encryptor 677, thereby producing an output K′ 679. The output K′ 679 is transmitted to layer 2 ( Figure 5 555) of the external certificate ("ID L1 The external certificate 681 may provide the ability to verify and / or authenticate the source of data sent from the device. As an example, data sent from an external communication component may be associated with the identity of the external communication component by verifying the certificate, such as by combining Figure 8 Further description. In addition, the external public key ("K L1公共密钥 ”) 683 is transmitted to layer 2. Therefore, the public identification 665, certificate 681 and external public key 683 of the external communication component 633 can be transmitted to layer 2 of the vehicle communication component.

[0063] Figure 7 is a block diagram of an example process for determining multiple parameters according to an embodiment of the present disclosure. Figure 7 Description of vehicle communication components (e.g. Figure 5 Layer 2 755 of the vehicle communication component 516 in the vehicle communication component 516 generates a vehicle identification ("ID L2公共 ”)766、Vehicle Certificate (“ID L2 Certificate”) 782 and the vehicle public key (“K L2公共密钥 ”)784.

[0064] like Figure 6 As described in the example above, the external public key (“K L1公共密钥 ”) 683 is used by the asymmetric ID generator 762 of the vehicle communication component to generate a public identification (“ID lk公共 ”) 766 and private identifier 768. In the abbreviation “ID lk公共”, “lk” indicates layer k (in this example, layer 2), and “public” indicates that the identity is open for sharing. The public identity 766 is illustrated as being shared by the arrow extending to the right and outside of layer 2 755. The generated private identity 768 is used as a key input into the encryptor 774.

[0065] Layer 2 755 of the vehicle communication component may include an asymmetric key generator 764. In at least one example, the random number generator (RND) 638 may optionally input a random number into the asymmetric key generator 764. The asymmetric key generator 764 may generate a random number that is consistent with the vehicle communication component (e.g., Figure 5 The public key (“K Lk公共 ”) 770 (referred to as the vehicle public key) and the private key (“K Lk私用 ”) 772 (referred to as the vehicle private key). The vehicle public key 770 may be input (as “data”) into an encryptor 774. The encryptor 774 may generate a result K′ 776 using the input of the vehicle private identification 768 and the vehicle public key 770. The vehicle private key 772 and the result K′ 776 may be input into an additional encryptor 778, thereby producing an output K″ 780. The output K″ 780 is transmitted back to layer 1 ( Figure 5 553) vehicle certificate (“ID L2 The vehicle certificate 782 may provide the ability to verify and / or authenticate the source of data sent from the device. As an example, data sent from a vehicle communication component may be associated with the identity of the vehicle communication component by verifying the certificate, such as by combining Figure 8 Further description. In addition, the vehicle public key (“K L2公共密钥 ”) 784 can be transmitted to layer 1. Therefore, the public identification 766, certificate 782 and vehicle public key 784 of the vehicle communication component can be transmitted to layer 1 of the external communication component.

[0066] In an example, in response to the external communication component receiving a public key from the vehicle communication component, the external communication component may encrypt data to be sent to the vehicle communication component using the vehicle public key. Vice versa, the vehicle communication component may encrypt data to be sent to the external communication component using the external public key. In response to the vehicle communication component receiving data encrypted using the vehicle public key, the vehicle communication component may decrypt the data using its own vehicle private key. Likewise, in response to the external communication component receiving data encrypted using the external public key, the external communication component may decrypt the data using its own external private key. Because the vehicle private key is not shared with another device external to the vehicle communication component, and the external private key is not shared with another device external to the external communication component, the data sent to the vehicle communication component and the external communication component remains secure.

[0067] Figure 8 FIG. 1 is a block diagram of an example process of verifying a certificate according to an embodiment of the present disclosure. Figure 8 In the illustrated example, the public key 883, certificate 881, and public identification are received from an external communication component (e.g., from Figure 5 The data of the certificate 881 and the external public key 883 can be used as input to the decryptor 885. The decryptor 885 can be any processor, computing device, etc. for decrypting data. The result of the decryption of the certificate 881 and the external public key 883 can be used as input to the secondary decryptor 887 together with the public identification to produce an output. The external public key 883 and the output from the decryptor 887 can indicate whether the certificate is verified as described at 889, thereby producing a yes or no 891 as an output. In response to the certificate being verified, the data received from the device being verified can be accepted, decrypted and processed. In response to the certificate not being verified, the data received from the device being verified can be discarded, removed and / or ignored. In this way, malicious devices that send malicious data can be detected and avoided. As an example, a hacker who sends data to be processed can be identified and the hacker data is not processed.

[0068] Fig. 9 1 is a block diagram of an example process of verifying a signature according to an embodiment of the present disclosure. In the case where a device is sending data that can be verified in order to avoid subsequent repudiation, a signature can be generated and sent with the data. As an example, a first device can make a request to a second device, and once the second device performs the request, the first device can instruct the first device never to make such a request. Anti-repudiation methods, such as using a signature, can avoid repudiation by the first device and ensure that the second device can perform the requested task without subsequent difficulties.

[0069] Vehicle computing device 912 (e.g., Figure 1The vehicle computing device 112 in the example of FIG. 1 may send data 990 to an external computing device (e.g., external computing device 242). The vehicle computing device 912 may generate a signature 996 at 994 using the vehicle private key 971. The signature 996 may be transmitted to the external computing device 942. The external computing device 942 may verify at 998 using the previously received data 992 and the external public key 969. In this manner, signature verification operates by encrypting the signature using the private key and decrypting the signature using the public key. In this manner, a unique signature for each device may remain private to the device sending the signature while allowing the receiving device to be able to decrypt the signature for verification. This is in contrast to encryption / decryption of data, which is encrypted by the sending device using the public key of the receiving device and decrypted by the receiving device using the private key of the receiver. In at least one example, the vehicle may verify the digital signature by using an internal encryption process, such as an elliptic curve digital signature (ECDSA) or similar process.

[0070] In the foregoing detailed description, reference is made to the accompanying drawings which form part hereof and in which specific examples are shown by way of illustration. In the accompanying drawings, like numerals describe substantially similar components throughout the several views. Other examples may be utilized and structural, logical and / or electrical changes may be made without departing from the scope of the present disclosure.

[0071] The drawings herein follow a numbering convention, wherein one or more first digits correspond to the figure number, and the remaining digits identify the elements or components in the drawings. Similar elements or components between different drawings can be identified by using similar numbers. As will be appreciated, the elements shown in the various embodiments herein can be added, exchanged and / or removed to provide multiple additional embodiments of the present disclosure. In addition, as will be appreciated, the ratios and relative scales of the elements provided in the drawings are intended to illustrate embodiments of the present disclosure and should not be understood in a limiting sense.

[0072] As used herein, "a", "an" or "a plurality of" something may refer to one or more of such things. "A plurality of" something means two or more. As used herein, the term "coupled" may include electrically coupled, directly coupled, and / or directly connected without intervening elements (e.g., by direct physical contact) or indirectly coupled and / or connected with intervening elements. The term coupled may further include two or more elements that cooperate or interact with each other (e.g., as in a cause and effect relationship).

[0073] Although specific examples have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that arrangements calculated to achieve the same results may be substituted for the specific embodiments shown. The present disclosure is intended to cover modifications or variations of one or more embodiments of the present disclosure. It should be understood that the above description has been made in an illustrative and non-restrictive manner. The scope of one or more examples of the present disclosure should be determined by reference to the appended claims and the full scope of equivalents authorized by such claims.

Claims

1. A device comprising: Processor (114, 117, 244, 317); as well as An external communication component (246, 446, 546, 553, 633) coupled to the processor, wherein the external communication component is configured to, in response to determining that a vehicle entity (102, 302, 402) is within a certain proximity of the external communication component: Generate an external private key (671) and an external public key (669, 683, 883, 969); providing the external public key and data to a vehicle communication component (116, 416, 516) associated with the vehicle entity; receiving data from the vehicle communication component in response to providing the external public key and data to the vehicle communication component, wherein the received data includes a vehicle digital signature; determining an identity of the vehicle entity based on the vehicle digital signature, wherein the determined identity prevents subsequent repudiation of services provided; decrypting the received data using the external private key; and The service is provided to the vehicle entity based on the decrypted received data.

2. The apparatus of claim 1, wherein the external communication component is configured to, in response to providing the service to the vehicle entity, perform the following operations: receiving confirmation data encrypted using the external public key from the vehicle communication component; and The confirmation data is decrypted using the external private key.

3. The device of claim 1 , wherein the external communication component is configured to: receiving payment data from the vehicle communication component in response to providing the service to the vehicle entity; and In response to receiving the payment data, data associated with the vehicle entity is removed from a storage device of the external communication component.

4. The apparatus of any one of claims 1 to 3, wherein the service comprises at least one of vehicle washing, passing through a toll booth, parking, and entering an area or facility.

5. Apparatus according to any one of claims 1 to 3, wherein the data provided by the external communication component to the vehicle communication component comprises service data and cost data.

6. The apparatus of any one of claims 1 to 3, wherein the data received from the vehicle communication component includes vehicle identification data, service confirmation data and personal identification data.

7. The apparatus according to any one of claims 1 to 3, wherein the external communication component is configured to: receiving a vehicle public key (784, 770) from the vehicle communication component; and The data is encrypted using the vehicle public key before being provided to the vehicle communication component. 8 . The apparatus of claim 7 , wherein the external communication component is configured to provide the vehicle public key to the vehicle communication component using radio frequency identification (RFID).

9. A method comprising: Generate an external private key (671) and an external public key (669, 683, 883, 969); providing the external public key to a vehicle communication component (116, 416, 516) associated with a vehicle entity (102, 302, 402); receiving a vehicle public key (784, 770) from the vehicle communication component; encrypting data using the vehicle public key; providing the encrypted data to the vehicle communication component; receiving data from the vehicle communication component in response to providing the encrypted data to the vehicle communication component, wherein the received data includes a vehicle digital signature; determining an identity of the vehicle entity based on the vehicle digital signature, wherein the determined identity prevents subsequent repudiation of services provided; decrypting the received data using the external private key; as well as The service is provided to the vehicle entity based on the decrypted received data.

10. The method of claim 9, comprising determining a specific distance of the vehicle entity from an external communication component (246, 446, 546, 553, 633) prior to providing information to or receiving information from the vehicle communication component.

11. The method according to claim 9, comprising: verifying the vehicle digital signature using the external public key; as well as The service is provided in response to verifying the vehicle digital signature.

12. The method of claim 9, wherein subsequent data provided to the vehicle communication component instructing the vehicle communication component to execute the same instruction is modified based on a specific parameter, wherein the modified subsequent data still instructs the vehicle communication component to execute the same instruction.

13. The method according to claim 12, wherein the specific parameter comprises at least one of a time period and a frequency of the same instructions sent.

14. The method of claim 9, wherein the encryption and decryption are performed using a Device Identity Combination Engine (DICE) - Robust Internet of Things (RIOT) protocol.

15. An apparatus comprising: Processor (114, 117, 244, 317); as well as A vehicle communication component (116, 416, 516) coupled to the processor, wherein the vehicle communication component is configured to, in response to determining that the vehicle communication component is within a certain proximity of an external communication component (246, 446, 546, 553, 633): Generate a vehicle private key (772, 971) and a vehicle public key (784, 770); providing the vehicle public key to the external communication component, wherein the external communication component is associated with a service; receiving an external public key (669, 683, 883, 969) from the external communication component; encrypting data using the external public key, wherein the encrypted data includes a vehicle digital signature that indicates the identity of the vehicle communication component and prevents repudiation of the service; providing the encrypted data to the external communication component; receiving data from the external communication component in response to providing the encrypted data to the external communication component; decrypting the received data using the vehicle private key; and Confirmation of acceptance of the service is provided in response to the decrypted data indicative of the service.

16. The apparatus of claim 15, wherein the vehicle communication component is configured to generate an external certificate (681) by: encrypting the vehicle identification (766) and the private vehicle identification to produce an encrypted value; and The encrypted value and the vehicle private key are encrypted.

17. The apparatus of claim 16, wherein the vehicle identification and the private vehicle identification are generated using an asymmetric identification generator (762).

18. The apparatus of claim 16, wherein the external certificate indicates an identity of a vehicle entity associated with the vehicle communication component.

19. A system comprising: The vehicle equipment of the vehicle entity (102, 302, 402) comprises: a vehicle processor (114, 117, 244, 317); and a vehicle communication component (116, 416, 516) coupled to the vehicle processor and configured to generate a vehicle private key (772, 971) and a vehicle public key (784, 770); and An external device, coupled to the transport assistance entity (233, 433), the external device comprising: External processors; and An external communication component (246, 446, 546, 553, 633) coupled to the external processor and configured to perform the following operations: Generate an external private key (671) and an external public key (669, 683, 883, 969); receiving the vehicle public key; and encrypting external data using the vehicle public key; and determining the identity of the vehicle entity based on the vehicle digital signature, wherein the external data indicates a service to be provided to the vehicle entity, and wherein the determined identity of the vehicle entity prevents subsequent repudiation of the services provided; The vehicle communication component is further configured to perform the following operations: receiving the external public key and external data; decrypting the external data using the vehicle private key; and encrypting vehicle data using the external public key, wherein the encrypted vehicle data includes the vehicle digital signature and indicates confirmation of the provided service; and Wherein the external communication component is further configured to perform the following operations: receiving the encrypted vehicle data; decrypting the vehicle data using the external private key; and The service is provided to the vehicle entity.

20. The system of claim 19, wherein: The external communication component is configured to verify the vehicle digital signature; Wherein said verification of said vehicle digital signature prevents said subsequent repudiation of said services provided.

Images