Method and system for communicating vehicle-to-everything (V2X) information

Abstract

A method and device for implementing a method for communicating vehicle-to-everything (V2X) information to a network node includes transmitting a first V2X message associated with a first service and including an identifier of a second service, and transmitting a second V2X message associated with the second service and including an identifier of the first service configured to enable the network node to use information from the first V2X message with the second service. The network node can receive the first V2X message and the second V2X message and can use the information from the first V2X message with the second service.

Description

Related Applications

[0001]

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 158,966, entitled "Methods And Systems For Communication Vehicle-To-Everything (V2X) Information," filed on March 10, 2021, the entire contents of which are incorporated by reference into this specification for all purposes. [Technical field]

[0002] The present invention relates to a method and system for communicating Vehicle-to-Everything (V2X) information. [Background technology]

[0003]

[0002] Several regions of the world are developing standards for vehicle-based communication systems and functionality. Standards are being developed at the Institute of Electrical and Electronics Engineers (IEEE) and the Society of Automotive Engineers (SAE) for use in North America, or at the European Telecommunications Standards Institute (ETSI) and the European Committee for Standardization (CEN) for use in Europe. The IEEE 802.11p standard is the basis for the Dedicated Short Range Communications (DSRC) and ITS-G5 communication standards. IEEE 1609 is a higher layer standard based on IEEE 802.11p. The Cellular Vehicle-to-Everything (C-V2X) standard is a competing standard developed under the auspices of the 3rd Generation Partnership Project. These standards serve as the basis for vehicle-based wireless communications and may be used to support intelligent highways, autonomous and semi-autonomous vehicles, and improve the overall efficiency and safety of highway transportation systems. Other V2X wireless technologies are also being considered in different regions of the world. The techniques described herein are applicable to any V2X wireless technology.

[0004]

[0003] The C-V2X protocol defines two transmission modes that together provide 360-degree non-line-of-sight awareness and a higher level of predictability for enhanced road safety and autonomous driving. The first transmission mode includes direct C-V2X, which includes vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P), providing extended communication range and reliability in a dedicated Intelligent Transportation System (ITS) 5.9 gigahertz (GHz) spectrum independent of cellular networks. The second transmission mode includes vehicle-to-network communications (V2N) in mobile broadband systems and technologies such as third generation wireless mobile communication technologies (3G) (e.g., Global System for Mobile Communications (GSM) Evolution (EDGE) systems, Code Division Multiple Access (CDMA) 2000 systems, etc.), fourth generation wireless mobile communication technologies (4G) (e.g., Long Term Evolution (LTE) systems, LTE-Advanced systems, Mobile Worldwide Interoperability for Microwave Access (Mobile WiMAX) systems, etc.), and fifth generation new radio wireless mobile communication technologies (e.g., 5G NR systems).

[0005]

[0004] An element of a V2X system is the ability for vehicles to broadcast Basic Safety Messages (BSM) in North America or Cooperative Awareness Messages (CAM) in Europe, which other vehicles can receive and process to improve road safety. The processing of such messages in the transmitting and receiving vehicles is performed in on-board equipment (herein referred to as "V2X on-board equipment") that provides the Vehicle-to-Everything (V2X) functionality. Summary of the Invention

[0006] Various aspects include a method for communicating V2X information to a network node and a V2X node configured to perform the method. Some aspects may include transmitting a first V2X message associated with a first service and including an identifier of a second service, and transmitting a second V2X message associated with the second service and including an identifier of the first service configured to enable the network node to use information from the first V2X message with the second service.

[0007]

[0006] Some aspects may include generating an identifier for a first service from a signing certificate of a first service associated with the V2X node, and generating an identifier for a second service from a signing certificate of a second service associated with the V2X node. In some aspects, generating an identifier for the first service from a signing certificate of the first service associated with the V2X node may include generating a hash of the signing certificate of the first service, and generating an identifier for the second service from a signing certificate of the second service associated with the V2X node may include generating a hash of the signing certificate of the second service. In some aspects, generating an identifier for the first service from a signing certificate of the first service associated with the V2X node may include generating a shortened identifier of the signing certificate of the first service, and generating an identifier for the second service from a signing certificate of the second service associated with the V2X node may include generating a shortened identifier of the signing certificate of the second service.

[0008] Some aspects may include transmitting a third V2X message associated with the second service and including a shortened identifier of the first service. In some aspects, the first V2X message may be a basic safety message. In some aspects, the second V2X message may be one of a tolling message, a parking access message, a road condition message, a geonetworking message, or an emergency message.

[0009] Various aspects include a method for receiving V2X information from a V2X node, a network node configured to perform the method. Some aspects may include receiving a first V2X message from the V2X node, the first V2X message being associated with a first service and including an identifier of a second service, receiving a second V2X message from the V2X node, the second V2X message being associated with the second service and including an identifier of the first service, and using information from the first V2X message with the second service.

[0010] In some aspects, using the information from the first V2X message with the second service may include generating an association of the V2X node, the first service, and the second service that enables the network node to use the information from the first V2X message with the second service. In some aspects, using the information from the first V2X message with the second service may include obtaining information about the V2X node from the first V2X message and performing an operation for the V2X node associated with the second service using the obtained information about the V2X node from the first V2X message. In some aspects, using the information from the first V2X message with the second service may include determining whether the first V2X message and the second V2X message were received within a threshold time period and using the information from the first V2X message with the second service in response to determining that the first V2X message and the second V2X message were received within the threshold time period. In some examples, the first V2X message may be a basic safety message. In some aspects, the second V2X message may be one of a toll message, a parking access message, a road condition message, a geo-networking message, or an emergency message.

[0011]

[0010] A further aspect includes a V2X node including a memory and a processor configured to perform operations of any of the methods summarized above. A further aspect may include a V2X node having various means for performing functions corresponding to any of the methods summarized above. A further aspect may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of the V2X node to perform various operations corresponding to any of the methods summarized above. [Brief description of the drawings]

[0012]

[0011] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the claims and, together with the provided general description and detailed description, serve to explain features of the invention. [Figure 1A] FIG. 1A is a system block diagram illustrating an example V2X system suitable for implementing various embodiments. [Figure 1B]

[0013] FIG. 1B is a conceptual diagram illustrating an example V2X communications protocol stack suitable for implementing various embodiments. [Diagram 2]

[0014] FIG. 2 is a component diagram of an example vehicle system including a block diagram of an example of a V2X-equipped device suitable for implementing various embodiments. [Figure 3A]

[0015] FIG. 3A is a conceptual diagram illustrating an example of a V2X message suitable for implementing various embodiments. [Figure 3B]

[0016] FIG. 3B is a conceptual diagram illustrating an example message flow suitable for implementing various embodiments. [Figure 4]

[0017] FIG. 4 is a process flow diagram illustrating a method 400 performed by a processor of a V2X node for communicating V2X information to a network node, according to various embodiments. [Diagram 5]

[0018] FIG. 5 is a process flow diagram illustrating operations 500 that may be performed by a processor of a V2X node as part of a method 400 for communicating V2X information to a network node, according to some embodiments. [Figure 6]

[0019] FIG. 6 is a process flow diagram illustrating a method 600 performed by a processor of a network node to receive V2X information from a V2X node, according to various embodiments. [Figure 7]

[0020] FIG. 7 is a process flow diagram illustrating operations 700 that may be performed by a processor of a V2X node as part of a method 600 of receiving V2X information from a V2X node, according to some embodiments. [Figure 8]

[0021] FIG. 8 is a component block diagram illustrating an exemplary mobile computing device suitable for use with the various embodiments. [Figure 9]

[0022] FIG. 9 is a component block diagram illustrating an example mobile computing device suitable for use with the various embodiments. Detailed Description

[0013]

[0023] Various embodiments are described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers are used throughout the drawings to refer to the same or like parts. References made to specific examples and implementations are for illustrative purposes only and are not intended to limit the scope of the claims.

[0014]

[0024] The V2X processing and communication system may be implemented in a variety of vehicles, such as automobiles, trucks, buses, trailers, autonomous vehicles, robotic systems, etc. Also, an ITS or other V2X system includes several fixed equipment installations, such as RSUs, access nodes, and wireless relay nodes. The various embodiments may be implemented in any of a variety of V2X-equipped vehicles, fixed installations, and other devices that use a V2X communication infrastructure. Additionally, the various embodiments may be useful in systems that are unrelated to ITS functionality but utilize V2X capabilities, such as paid parking garages, wireless payment systems for various commercial applications, emergency services, etc. To encompass all implementations of the various embodiments, the term "V2X node" is used in the description and claims to generally refer to a mobile, semi-mobile, or fixed system that implements V2X communication functionality. A non-limiting example of a V2X node used for purposes of explanation is a vehicle, such as an automobile, that pays tolls while traveling on a toll road, although reference to this and other examples is not intended to limit the scope of the claims that describe V2X nodes.

[0015]

[0025] A V2X node (e.g., a vehicle) may transmit various V2X messages related to different services. For example, a V2X node may periodically transmit a basic safety message that may include an identifier of the V2X node and information about the V2X node, such as the V2X node's location, speed, route, nearby road conditions, nearby vehicles, observed road conditions, and vehicle behavior. As used herein, the term "basic safety message" includes a Basic Safety Message (BSM) that may be used in North America, a Cooperative Awareness Message (CAM) that may be used in Europe, and other similar messages that may be used according to other Intelligent Transportation System (ITS) protocols or technical standards. A V2X node may also transmit other V2X messages related to other services. For example, a V2X node may transmit information related to tolling or tolling operations, such as a Toll Upload Message (TUM) or similar message that may include an identifier of the V2X node as well as the V2X node's location, route, and other information about the V2X node. As another example, a V2X node may transmit an emergency or distress message, such as an SAE J2735 message, which may include an identifier of the V2X node and the location, speed, heading, latitude, longitude, altitude, and other information about the V2X node. As another example, V2X messages used by emergency responders or emergency service providers (e.g., police, fire, emergency medical technicians, etc.) may include location information, identifiers of vehicles such as the V2X node, etc. The information content of various V2X messages may overlap or be redundant to some extent.

[0016]

[0026] A V2X communication system is typically bandwidth constrained and may involve a large number of participating entities, including many vehicles, roadside units, gantry units, and other network elements, each transmitting a large number of V2X messages. Reducing redundancy in the information carried by the V2X messages can reduce the bandwidth overhead incurred by the V2X messages and can reduce the computational overhead of processing each V2X message. However, typical V2X node security mechanisms isolate or "sandbox" applications from each other and give transmitters (e.g., V2X nodes) separate permissions (which may be managed by separately issued digital signatures or another suitable security measure) for different sets of application activities. Thus, it is not trivial to combine messages configured for different services (e.g., BSM, toll, emergency services, etc.) and apply a single digital signature to cover both or all messages. Furthermore, simply combining messages configured for different services may raise privacy concerns, since applying a single digital signature to many V2X messages may expose all the content of the V2X messages to any device authorized to see one of the V2X messages.

[0017]

[0027] Various embodiments include methods and mechanisms for efficiently communicating V2X information in an Intelligent Transportation System (ITS) to other network elements, which may be network elements in an ITS (e.g., another vehicle, a Roadside Unit (RSU), etc.) or in other networks (e.g., the Internet, a private network, etc.). To encompass network elements that may be in non-ITS systems as well as IDS network elements, the term "network node" is used herein to refer to a network element to which a V2X node may transmit V2X messages according to various embodiments. Thus, a "network node" may be any computing device in a network configured to receive V2X messages from a V2X node, including but not limited to a V2X node.

[0018]

[0028] Various embodiments enable a V2X node (e.g., a V2X-equipped equipment in a vehicle, a mobile phone, a laptop, a tablet, or another suitable computing device) to communicate with a network node (e.g., another vehicle, an RSU, or a gantry unit (such as a toll gantry unit)) to utilize information provided by the V2X node for a first service in performing operations for a second service provided by or related to the network node.

[0019]

[0029] As mentioned above, a V2X node may transmit various V2X messages that may contain information content that is redundant. For example, a tolling or toll collection system (toll system) may need to precisely determine the specific lane location of a V2X node so that the system can charge the V2X node the appropriate fee or toll (e.g., "lane level accuracy"). A typical toll message from a V2X node may include V2X node identification information, account number or other financial information, and location information, as well as other information about the V2X node. At the same time, a V2X node performing a maneuver may transmit one or more V2X messages to coordinate with other vehicles to ensure that the maneuver can be performed safely and efficiently. Additionally, all V2X-equipped vehicles routinely share information such as maneuver information, location information, etc. in basic safety messages.

[0020]

[0030] Various embodiments include methods for communicating V2X node information, as well as V2X nodes and network nodes configured to perform the methods, in a manner that improves efficiency and reduces the processing and communication link overhead required to handle V2X messages. In some embodiments, a V2X node (e.g., a V2X processing device in a vehicle's V2X onboard equipment) can transmit a first V2X message associated with a first service and including an identifier for a second service for receipt by the network node, and can transmit a second V2X message associated with the second service and including an identifier for the first service configured to enable the network node to use information from the first V2X message for the second service. In various embodiments, including an identifier for the service in the V2X message for the other service can enable the receiving network node to create an association between a message from the V2X node for the first service and a message from the V2X node for the second service, thereby enabling the network node to use information provided by the V2X node in the message for the first service when performing operations on behalf of the V2X node for the second service. In this manner, the V2X node may generate a V2X message for the second service that includes an identifier for the first service, rather than including information in the V2X message for the second service that is redundant to information in the V2X message for the first service. For example, the V2X node may transmit a basic safety message that includes node identification information and a location of the V2X node. The V2X node may also transmit a toll message that references the basic safety message, allowing a receiving network node to use the identification and / or location information from the basic safety message.

[0021]

[0031] The terms "first message" and "second message" are used to distinguish each message, are not intended to require an order or sequence of messages, and are not intended to be limited to only two messages. Additionally, any number of "first" messages and any number of "second" messages may be transmitted. Additionally, additional messages, generally referred to herein as "third messages," may also be transmitted incorporating elements of the various embodiments. Similarly, the terms "first service" and "second service" are used to distinguish each service. In some embodiments, information from the first service may be used in performing operations of the second service. In some embodiments, information of the first service may be provided within a message of the first service. In some embodiments, information from the second service may be used in performing operations of the first service. In some embodiments, information of the second service may be provided within a message of the second service.

[0022]

[0032] In some embodiments, the V2X node may generate the identifier from a signing certificate associated with the service. In some embodiments, the V2X node may generate an identifier for a first service from a signing certificate for the first service associated with the V2X node, and may generate an identifier for a second service from a signing certificate for the second service associated with the V2X node. In this way, each V2X message may include an identifier that is secure and verifiable by the receiving network node.

[0023]

[0033] In some embodiments, the V2X node may generate an identifier for the first service by generating a hash of the signing certificate of the first service and may generate an identifier for the second service by generating a hash of the signing certificate of the second service. In some embodiments, after the association between the messages for the first service and the second service is established, the V2X node may generate a shortened or abbreviated identifier for the first service in the second service to further reduce the amount of data in each V2X message. In some embodiments, the shortened identifier may be as small as the last 3 or 4 bytes of the full hash identifier. In some embodiments, the V2X node may generate a shortened hash of the signing certificate of the first service (e.g., the last 3 or 4 bytes in the full hash certificate) and may generate a shortened hash of the signing certificate of the second service (e.g., the last 3 or 4 bytes in the full hash certificate). In some embodiments, the receiving network node can easily identify the shortened identifier of each service's signing certificate as being associated with the full or larger identifier of each service's signing certificate.

[0024]

[0034] In some embodiments, the V2X node may determine whether a similar certificate has been used by another vehicle or network node within a threshold radius and / or threshold time period. In response to determining that a similar certificate has not been used by another vehicle or network node within the threshold radius and / or threshold time period, the V2X node may generate and use an abbreviated identifier for data included in messages for the service.

[0025]

[0035] In some embodiments, the V2X node may intersperse V2X messages including the full identifier or a larger identifier of the service among V2X messages using the shortened identifier of the service. In this way, the transmitting V2X node may be locally unique for the signing certificate associated with the V2X node and the service, while periodically including the larger identifier, which is more cryptographically secure. For example, an attacker may record a communication session (i.e., V2X messages related to the service) and replace V2X messages signed by the V2X node's signature with messages signed by the attacker's certificate. While the attacker may be able to identify usable certificates based on the shortened identifier, it is infeasible to identify certificates with longer identifiers. In this way, interspersing V2X messages including the larger identifier of the service can increase the security of V2X communications.

[0026]

[0036] In some embodiments, the first V2X message may be a basic safety message. In some embodiments, the second V2X message may be associated with another service. For example, the second V2X message may be a toll message (e.g., for a toll or toll collection system), a parking access message (e.g., for a parking payment system), a road condition message (e.g., a message to another vehicle, an RSU, or a network node about traffic, observed vehicle behavior, road damage, dangerous road conditions such as ice or flooding, etc.), a geo-networking message (e.g., for use in a geo-networking message or messaging system), an emergency responder message (e.g., police, fire, paramedic, or other emergency responder system), or another suitable message or messaging system.

[0027]

[0037] In various embodiments, the network node may receive from the V2X node a first V2X message associated with the first service and including an identifier of the second service, and may receive from the V2X node a second V2X message associated with the second service and including an identifier of the first service. In some embodiments, the network node may generate an association of the V2X node, the first service, and the second service that enables the network node to use information from the first V2X message with the second service. In some embodiments, the network node may use information from the first V2X message with the second service. In some embodiments, the network node may obtain information about the V2X node from the first V2X message and may perform operations for the V2X node associated with the second service using the information about the V2X node obtained from the first V2X message.

[0028]

[0038] In some embodiments, the network node may determine whether the first V2X message and the second V2X message were received within a threshold time period. In response to determining that the first V2X message and the second V2X message were received within the threshold time period, the network node may use information from the first V2X message with the second service. In this manner, the network node may improve the security of the correlation between the V2X messages of the first service and the V2X messages of the second service and avoid the use of data that may no longer be accurate (e.g., the position of a moving vehicle).

[0029]

[0039] In this manner, various embodiments include methods, V2X processing devices, and network elements configured to perform methods for communicating V2X information in V2X messages in a manner that improves efficiency and reduces the processing and communication link overhead required to handle such V2X messages.

[0030]

[0040] For ease of reference, some of the embodiments are described in this application with respect to vehicles using vehicle-to-everything (V2X) systems and protocols. However, it should be understood that the various embodiments encompass any or all of V2X or vehicle-based communication standards, messages, or technologies. Thus, nothing in this application should be construed as limiting the claims to V2X systems, basic safety messages (BSMs), or V2X messages unless expressly so recited in the claims. In addition, the embodiments described herein may refer to a V2X processing system in a vehicle. Other embodiments are contemplated in which the V2X processing system may operate in or be included in a mobile device, mobile computer, roadside unit (RSU), and other devices equipped to monitor road and vehicle conditions and participate in V2X communications.

[0031]

[0041] FIG 1A is a system block diagram illustrating an example V2X system 100 suitable for implementing various embodiments. FIG 1B is a conceptual diagram illustrating an example V2X communication protocol stack 150 suitable for implementing various embodiments. With reference to FIG 1A and FIG 1B, each vehicle 12, 14, 16 includes V2X on-board equipment 102, 104, 106, respectively, configured to transmit and receive V2X messages, including periodically broadcasting basic safety messages 112, 114, 116 for receipt and processing by on-board equipment (e.g., 102, 104, 106) of other vehicles.

[0032]

[0042] By sharing vehicle position, speed, direction, braking, and other information, the vehicles can maintain a safe separation and identify and avoid potential collisions. For example, a following vehicle 12 receiving a basic safety message 114 from a leading vehicle 16 can determine the speed and position of the vehicle 16, allowing the vehicle 12 to match speeds and maintain a safe separation distance 20. By being notified through the basic safety message 114 when the leading vehicle 16 brakes, the V2X equipment 102 in the following vehicle 12 can simultaneously brake to maintain a safe separation distance 20 even when the leading vehicle 16 suddenly stops. As another example, the V2X equipment 104 in the truck vehicle 14 can receive basic safety messages 112, 116 from the two vehicles 12, 16 and thus be notified that the truck vehicle 14 should stop at an intersection to avoid a collision. Additionally, each of the vehicle V2X onboard equipment 102, 104, 106 can communicate with each other using any of a variety of proximity communication protocols.

[0033]

[0043] In addition, the vehicles may be capable of transmitting data and information related to basic safety messages and other V2X communications to various network elements 132, 134, 136 through communication network 18 (e.g., V2X, cellular, WiFi, etc.) via communication links 122, 124, 146. For example, network element 132 may be incorporated into or in communication with an RSU, a gantry unit, etc. The network elements 134, 136 may be configured to perform functions or services related to the vehicles 12, 14, 16, such as payment processing, road condition monitoring, emergency provider message processing, etc. The network elements 134, 136 may be configured to communicate with each other via wired or wireless networks 142, 144 to exchange information related to payment processing, road condition monitoring, emergency provider message processing, and similar services.

[0034]

[0044] FIG. 2 is a component diagram of an example vehicle system 200 suitable for implementing various embodiments. With reference to FIGS. 1A-2, the system 200 may include a vehicle 202 including a vehicle processing system 204 (e.g., a telematics control unit or on-board unit (TCU / OBU)). The V2X processing device 202 may communicate with various systems and devices, such as an in-vehicle network 210, an infotainment system 212, various sensors 214, various actuators 216, and a wireless module 218. The V2X processing device 202 may also communicate with various other vehicles 220, roadside units 222, base stations 224, and other external devices. The vehicle processing system 204 may be configured to perform operations to authenticate plaintext and ciphertext, as described further below.

[0035]

[0045] The vehicle processing device 204 may include a processor 205, a memory 206, an input module 207, an output module 208, and a wireless module 218. The processor 205 may be coupled to the memory 206 (i.e., a non-transitory storage medium) and may be configured with processor-executable instructions stored in the memory 206 to perform operations of methods according to various embodiments described herein. The processor 205 may also be coupled to the output module 208, which may control an in-vehicle display, and the input module 207 for receiving information from vehicle sensors as well as driver inputs.

[0036]

[0046] The vehicle processing system 204 may include a V2X antenna 219 coupled to a radio module 218 configured to communicate with one or more ITS stations, such as another vehicle 220, a roadside unit 222, and a base station 224 or another suitable network access point. In various embodiments, the V2X processing device 202 may receive information from multiple sources, such as an in-vehicle network 210, an infotainment system 212, various sensors 214, various actuators 216, and the radio module 218. The V2X processing device 202 may detect a malfunction condition in a system of the vehicle, such as one of the multiple sources 210-218, an application or service running on the V2X processing device 202, or another system of the vehicle.

[0037]

[0047] Examples of in-vehicle networks include Controller Area Networks (CAN), Local Interconnect Networks (LIN), networks using the FlexRay protocol, Media Oriented Systems Transport (MOST) networks, and Automotive Ethernet networks. Examples of vehicle sensors include positioning systems (such as Global Navigation Satellite System (GNSS) systems), cameras, radars, lidars, ultrasonic sensors, infrared sensors, and other suitable sensor devices and systems. Examples of vehicle actuators include various physical control systems for steering, braking, engine operation, lights, directional signals, and the like.

[0038]

[0048] FIG 3A is a conceptual diagram illustrating an example of a V2X message 300 suitable for implementing various embodiments. FIG 3B is a conceptual diagram illustrating an example message flow 350 suitable for implementing various embodiments. With reference to FIGs. 1-3B, the V2X message 300 and message flow 350 may be implemented by a processor of a vehicle processing system (e.g., 204) of a V2X node (e.g., vehicle 12, 14, 16, 220) and a network node (e.g., another one of the vehicles 12, 14, 16, 202, RSU 132, network element 134, 136).

[0039]

[0049] The first V2X message 302 may include information such as a payload (e.g., data or information) and / or metadata 304 related to the first service. The first V2X message 302 may include one or more certificates 306 associated with the first service. The first V2X message 302 may also include an identifier 308 of the second service. The first V2X message 302 may include a signing certificate 310 for the first service. The first V2X message 302 may include or be associated with a digital signature (i.e., the first V2X message 302 may be digitally signed). In some embodiments, the first V2X message 302 may be a basic safety message.

[0040]

[0050] The second V2X message 320 may include information such as a payload (e.g., data or information) and / or metadata 322 related to the second service. The second V2X message 320 may include one or more certificates 324 associated with the second service and a signing certificate 328 for the first service. The second V2X message 320 may also include an identifier 326 of the first service. The second V2X message 320 may include or be associated with a digital signature (i.e., the second V2X message 320 may be digitally signed).

[0041]

[0051] With reference to FIG. 3B, a message flow 350 (which may be sent, for example, by a V2X node) may include V2X messages 352-366. The V2X messages for each of the first service and the second service may include an identifier of the other service. For example, the V2X message 352 of the first service may include a longer identifier of the second service, and the V2X message 354 of the second service may include a longer identifier of the first service. Including an identifier for the other V2X service in each V2X message may enable a receiving device (e.g., a network node) to associate the two services and / or messages from the two services to the V2X node. In some embodiments, the network node may generate an association of the V2X node, the first service, and the second service. Such an association may enable the network node to use information from the first V2X message in performing operations of the second service for the V2X node.

[0042]

[0052] V2X messages sent / received after V2X messages 352 and 354, such as V2X messages 356 and 358, may include a shortened identifier of the other service. In some embodiments, the identifier of the other service may be or include a certificate of the other service. In some embodiments, the longer identifier may be a full-sized hash of the certificate of the other service. In some embodiments, the shortened identifier may be a shortened hash of the certificate of the other service. In some embodiments, the shortened identifier may include sufficient information to uniquely identify the longer identifier. For example, the shortened hash of the certificate may include sufficient information (e.g., may be a string of sufficient length) to uniquely identify the full-length or full-sized hash of the certificate.

[0043]

[0053] In some embodiments, the V2X node may intersperse V2X messages that include a full identifier or a larger identifier of a service among V2X messages that use a shortened identifier of the service. For example, V2X messages 360, 362, and 366 may include a shortened identifier of a first service, and V2X message 364, interspersed between V2X messages 362 and 366, may include a longer identifier of the first service. In various embodiments, the larger identifier is cryptographically more secure than the shortened identifier. In this manner, the V2X node may reduce the overall amount or volume of data transmitted over the V2X node communication link while maintaining a sufficient level of security to thwart an attacker by periodically including the longer identifier.

[0044]

[0054] 4 is a process flow diagram illustrating a method 400 performed by a processor of a V2X node for communicating V2X information to a network node, according to various embodiments. With reference to FIGS. 1-4, the operations of method 400 may be performed by a V2X processing device in a V2X node (e.g., 12, 14, 16, 202).

[0045]

[0055] In block 402, the V2X processing device may transmit a first V2X message associated with the first service and including an identifier of the second service. For example, the V2X processing device may transmit a basic safety message including an identifier of the second service. In some embodiments, the second service may include a toll collection service, a parking access service, a road condition monitoring service, a geo-networking service, or an emergency response service. The means for performing the operations of block 402 may include the V2X-equipped equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

[0046]

[0056] In block 404, the V2X processing device may transmit a second V2X message including an identifier of a first service associated with the second service and configured to enable a network node to use information from the first V2X message with the second service. For example, the second V2X message may be a toll message, a parking access message, a road condition message, a geo-networking message, or an emergency responder message. The second V2X message may include an identifier of the first service (i.e., a basic safety message service). In various embodiments, including an identifier of the second service in the first V2X message and including an identifier of the first service in the second V2X message may enable a network node to use information from the first V2X message (e.g., a basic safety message) with the second service. Means for performing the operations of block 404 may include the V2X-equipped equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

[0047]

[0057] As described above, the V2X processing device may transmit any number of first V2X messages and any number of second V2X messages in method 400. Additionally, in some embodiments, the V2X processing device may transmit a third V2X message associated with the second service and including a shortened identifier of the first service.

[0048]

[0058] 5 is a process flow diagram illustrating operations 500 that may be performed by a processor of a V2X node as part of a method 400 for communicating V2X information to a network node, according to various embodiments. With reference to FIGS. 1-5, the operations of operations 500 may be performed by a V2X processing device in a V2X node (e.g., 12, 14, 16, 202).

[0049]

[0059] At block 502, the V2X processing device may generate an identifier for the first service from a signing certificate for the first service associated with the V2X node. In some embodiments, the V2X processing device may generate the identifier for the first service by generating a hash of the signing certificate for the first service. In some embodiments, the V2X processing device may generate the identifier for the first service by generating a truncated hash of the signing certificate for the first service. Means for performing the operations of block 502 may include the V2X onboard equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

[0050]

[0060] At block 504, the V2X processing device may generate an identifier for the second service from a signing certificate of the second service associated with the V2X node. In some embodiments, the V2X processing device may generate the identifier for the second first service by generating a hash of the signing certificate of the second service. In some embodiments, the V2X processing device may generate the identifier for the second service by generating a truncated hash of the signing certificate of the second service. Means for performing the operations of block 504 may include the V2X onboard equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

[0051]

[0061] Following the operations of block 504, the V2X processing device may proceed to perform the operations of block 402 of method 400, as described.

[0052]

[0062] 6 is a process flow diagram illustrating a method 600 performed by a processor of a network node for receiving V2X information from a V2X node, according to various embodiments. With reference to FIGS. 1-6, the operations of method 600 may be performed by a processing device (which may be a V2X processing device) within a network node (e.g., 12, 14, 16, 132, 134, 136, 220, 222, 224).

[0053]

[0063] In block 602, the processing device may receive a first V2X message from a V2X node, the first V2X message being associated with a first service and including an identifier of a second service. Means for performing the operations of block 602 may include the V2X onboard equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

[0054]

[0064] In block 604, the processing device may receive a second V2X message from the V2X node, the second V2X message being associated with the second service and including an identifier of the first service. Means for performing the operations of block 604 may include the V2X onboard equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

[0055]

[0065] In block 606, the processing device may use information from the first V2X message with the second service. In some embodiments, the processing device may obtain information about the V2X node from the first V2X message and perform operations for the V2X node related to the second service using the information about the V2X node obtained from the first V2X message. In some embodiments, the processing device may generate an association of the V2X node, the first service, and the second service that enables the network node to use the information from the first V2X message with the second service. Means for performing the operations of block 602 may include the V2X on-board equipment 102, 104, 106 and the vehicle processing system 204.

[0056]

[0066] 7 is a process flow diagram illustrating operations 700 that may be performed by a processor of a V2X node as part of a method 600 of receiving V2X information from a V2X node, according to various embodiments. With reference to FIGS. 1-7, the operations of operations 700 may be performed by a processing device (which may be a V2X processing device) in a network node (e.g., 12, 14, 16, 132, 134, 136, 220, 222, 224).

[0057]

[0067] After performing the operations of block 604 (FIG. 6), the processing device may determine whether the first V2X message and the second V2X message were received within a threshold time period in decision block 710. In some embodiments, the processing device may determine whether the first V2X message and the second V2X message were received within a threshold time period from each other. Means for performing the operations of decision block 710 may include the V2X-equipped equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

[0058]

[0068] In response to determining that the first V2X message and the second V2X message were not received within the threshold time period (i.e., decision block 710="No"), the processing device does not use information from the V2X messages with the second service at block 712. In some embodiments, the processor may stop creating an association of the V2X node, the first service, and the second service in response to determining that the first V2X message and the second V2X message were not received within the threshold time period. Means for performing the operations of decision block 712 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

[0059]

[0069] In response to determining that the first V2X message and the second V2X message were received within the threshold time period (i.e., decision block 710="Yes"), the processing device may perform the operations of block 606 of method 600 (FIG. 6) as described.

[0060]

[0070] FIG. 8 is a conceptual block diagram illustrating an exemplary mobile computing device 800 suitable for use with various embodiments. With reference to FIGS. 1-8, various embodiments may be implemented in a wide variety of computing systems, including on-board equipment as well as mobile computing devices, including the exemplary mobile computing device 800. The mobile computing device 800 may include a processor 802 coupled to a touch screen controller 804 and an internal memory 806. The processor 802 may be one or more multi-core integrated circuits designated for general purpose or dedicated processing tasks. The internal memory 806 may be volatile or non-volatile memory, and may be secure and / or encrypted memory, or unsecure and / or unencrypted memory, or any combination thereof. Examples of memory types that may be utilized include, but are not limited to, DDR, LPDDR, GDDR, WIDEIO, RAM, SRAM, DRAM, P-RAM, R-RAM, M-RAM, STT-RAM, and embedded DRAM. The touchscreen controller 804 and processor 802 may also be coupled to a touchscreen panel 812, such as a resistive-sensing touchscreen, a capacitive-sensing touchscreen, an infrared-sensing touchscreen, etc. In addition, the display of the mobile computing device 800 need not have touchscreen capabilities.

[0061]

[0071] The mobile computing device 800 may have one or more wireless signal transceivers 808 (e.g., Peanut, Bluetooth, ZigBee, Wi-Fi, RF radio) and antennas 810 coupled to each other and / or to the processor 802 for transmitting and receiving communications. The transceivers 808 and antennas 810 may be used with the circuitry described above to implement various wireless transmission protocol stacks and interfaces. The mobile computing device 800 may include a cellular network wireless modem chip 816 to enable communication over a cellular network and also coupled to the processor.

[0062]

[0072] The mobile computing device 800 may include a peripheral device connection interface 818 coupled to the processor 802. The peripheral device connection interface 818 may be solely configured to accept one type of connection or may be configured to accept a variety of common or proprietary types of physical and communication connections, such as Universal Serial Bus (USB), FireWire, Thunderbolt, or PCIe. The peripheral device connection interface 818 may also be coupled to a similarly configured peripheral device connection port (not shown).

[0063]

[0073] The mobile computing device 800 may also include a speaker 814 for providing audio output. The mobile computing device 800 may also include a housing 820 constructed from plastic, metal, or a combination of materials for housing all or some of the components described herein. Those skilled in the art will recognize that the housing 820 may be a dashboard console of a vehicle in an on-board embodiment. The mobile computing device 800 may include a power source 822, such as a disposable battery or a rechargeable battery, coupled to the processor 802. The rechargeable battery may also be coupled to a peripheral device connection port for receiving charging current from a power source external to the mobile computing device 800. The mobile computing device 800 may also include a physical button 824 for receiving user input. The mobile computing device 800 may also include a power button 826 for turning the mobile computing device 800 on and off.

[0064]

[0074] FIG. 9 is a conceptual block diagram illustrating an exemplary mobile computing device 900 suitable for use with various embodiments. With reference to FIGS. 1-9, various embodiments may be implemented in a wide variety of computing systems, including the exemplary mobile computing device 900 shown as a laptop computer. The mobile computing device 900 includes a touchpad touch surface 917 that serves as a computer pointing device and may thus receive drag, scroll, and flick gestures similar to those described above and implemented on computing devices equipped with touchscreen displays. The mobile computing device 900 typically includes a processor 902 coupled to a volatile memory 912, and a large amount of non-volatile memory, such as a flash memory disk drive 913. Additionally, the mobile computing device 900 may have one or more antennas 908 for transmitting and receiving electromagnetic radiation and / or a cellular telephone transceiver 916 coupled to the processor 902, which may be connected to a wireless data link. The mobile computing device 900 may also include a floppy disk drive 914 and a compact disk (CD) drive 915 coupled to the processor 902. In a notebook configuration, the computer housing includes a touchpad 917, a keyboard 918, and a display 919, all coupled to the processor 902. Other configurations of computing devices may include a computer mouse or trackball coupled to the processor (e.g., via a USB input), as is well known, which may also be used in conjunction with the various embodiments.

[0065]

[0075] Examples are described in the following paragraphs. Although some of the examples below are described in terms of example methods, further example implementations may include example methods described in the following paragraphs implemented by a V2X processing device, which may be an on-board equipment, a mobile device unit, a mobile computing unit, or a fixed roadside unit), a network node, or a computing device including a processor configured to perform the operations of the methods of the following examples with processor-executable instructions, example methods described in the following paragraphs implemented by a V2X processing device, a network node processing device, or a network computing node processing device including means for performing the functions of the methods of the following examples, and example methods described in the following paragraphs that may be implemented as a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a V2X processing device, a network processing device, or a network computing node processing device to perform the operations of the methods of the following examples.

[0066]

[0076] [Example 1] A method executed by a processor of a vehicle-to-everything (V2X) node for communicating V2X information to a network node, the method including: transmitting a first V2X message associated with a first service and including an identifier of a second service; and transmitting a second V2X message associated with the second service and including an identifier of the first service configured to enable the network node to use information from the first V2X message with the second service.

[0067]

[0077] [Example 2] The method of Example 1, further comprising: generating an identifier for a first service from a signing certificate of a first service associated with the V2X node; and generating an identifier for a second service from a signing certificate of a second service associated with the V2X node.

[0068]

[0078] [Example 3] The method of Example 2, wherein generating an identifier for a first service from a signing certificate for a first service associated with the V2X node includes generating a hash of a signing certificate for the first service, and generating an identifier for a second service from a signing certificate for a second service associated with the V2X node includes generating a hash of a signing certificate for the second service.

[0069]

[0079] [Example 4] A method as described in either Example 2 or 3, wherein generating an identifier for a first service from a signing certificate for a first service associated with the V2X node includes generating a shortened identifier for a signing certificate for the first service, and generating an identifier for a second service from a signing certificate for a second service associated with the V2X node includes generating a shortened identifier for a signing certificate for the second service.

[0070]

[0080] [Example 5] A method as described in any of Examples 2-4, further comprising transmitting a third V2X message associated with the second service and including a shortened identifier of the first service.

[0071]

[0081] [Example 6] The method described in any of Examples 1-5, wherein the first V2X message is a basic safety message.

[0072]

[0082] [Example 7] The method of any of Examples 1-6, wherein the second V2X message is one of a toll message, a parking access message, a road condition message, a geo-networking message, or an emergency message.

[0073]

[0083] [Example 8] A method executed by a processor of a network node for receiving vehicle-to-everything (V2X) information from a V2X node, the method comprising: receiving a first V2X message from the V2X node, the first V2X message being associated with a first service and including an identifier of a second service; receiving a second V2X message from the V2X node, the second V2X message being associated with the second service and including an identifier of the first service; and using information from the first V2X message in conjunction with the second service.

[0074]

[0084] [Example 9] The method of Example 8, wherein using the information from the first V2X message with the second service includes generating an association between the V2X node, the first service, and the second service that enables the network node to use the information from the first V2X message with the second service.

[0075]

[0085] [Example 10] A method as described in any of Examples 8 or 9, wherein using the information from the first V2X message with the second service includes obtaining information about the V2X node from the first V2X message, and using the information about the V2X node obtained from the first V2X message to perform an operation for the V2X node associated with the second service.

[0076]

[0086] [Example 11] A method as described in any of Examples 8-10, wherein using information from the first V2X message with the second service includes determining whether the first V2X message and the second V2X message are received within a threshold period, and in response to determining that the first V2X message and the second V2X message are received within the threshold period, using information from the first V2X message with the second service.

[0077]

[0087] [Example 12] A method as described in any of Examples 8-11, wherein the first V2X message is a basic safety message.

[0078]

[0088] [Example 13] A method as described in any of Examples 8-12, wherein the second V2X message is one of a toll message, a parking access message, a road condition message, a geo-networking message, or an emergency message.

[0079]

[0089] The foregoing method descriptions and process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the operations of the various embodiments must be performed in the order presented. As will be understood by one of ordinary skill in the art, the order of operations in the foregoing embodiments may be performed in any order. Terms such as "thereafter," "then," and "next" are not intended to limit the order of operations; these terms are merely used to guide the reader through the method descriptions. Additionally, any reference to a claim element in the singular, for example, using the articles "a," "an," or "the," should not be construed as limiting the element to the singular.

[0080]

[0090] The various exemplary logic blocks, modules, circuits, and algorithmic operations described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and operations have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Skilled persons may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the claims.

[0081]

[0091] The hardware used to implement the various example logic, logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed by a general purpose processor, a digital signal processor (DSP), a technical application specific integrated circuit (TCUASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuitry specific to a given function.

[0082]

[0092] In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium or a non-transitory processor-readable medium. The operations of the methods or algorithms disclosed herein may be embodied in a processor-executable software module that may reside on a non-transitory computer-readable storage medium or a processor-readable storage medium. A non-transitory computer-readable or processor-readable storage medium may be any storage medium that may be accessed by a computer or processor. By way of example and not limitation, such non-transitory computer-readable or processor-readable media may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and Blu-ray discs, where disks typically reproduce data magnetically while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of non-transitory computer-readable media and processor-readable media. Additionally, operations of a method or algorithm may exist as one or any combination or set of code and / or instructions on a non-transitory processor-readable medium and / or computer-readable medium, which may be incorporated into a computer program product.

[0083]

[0093] The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the claimed invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the claimed invention. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein in the following claims.

Claims

1. 1. A method for communicating Vehicle-to-Everything (V2X) information to a network node, the method comprising: transmitting a first V2X message associated with a first service and including an identifier of a second service; transmitting a second V2X message including an identifier of the first service associated with the second service and configured to enable the network node to use information from the first V2X message with the second service; A method comprising:

2. generating the identifier of the first service from a signing certificate of the first service associated with the V2X node; generating the identifier of the second service from a signing certificate of the second service associated with the V2X node; The method of claim 1 further comprising:

3. generating the identifier of the first service from a signing certificate of the first service associated with the V2X node includes generating a hash of the signing certificate of the first service; generating the identifier of the second service from a signing certificate of the second service associated with the V2X node includes generating a hash of the signing certificate of the second service. The method of claim 2.

4. generating the identifier of the first service from a signing certificate of the first service associated with the V2X node includes generating a shortened identifier of the signing certificate of the first service; generating the identifier of the second service from a signing certificate of the second service associated with the V2X node includes generating a shortened identifier of the signing certificate of the second service. The method of claim 2.

5. 3. The method of claim 2, further comprising transmitting a third V2X message associated with the second service and including a shortened identifier of the first service.

6. 2. The method of claim 1, wherein the second V2X message is one of a toll message, a parking access message, a road condition message, a geo-networking message, a basic safety message, or an emergency message.

7. A method executed by a processor of a network node for receiving Vehicle-to-Everything (V2X) information from a V2X node, comprising: receiving, from a V2X node, a first V2X message associated with a first service and including an identifier of a second service; receiving a second V2X message from the V2X node, the second V2X message being associated with the second service and including an identifier of the first service; using information from the first V2X message with the second service; and A method comprising:

8. The method of claim 7, wherein using information from the first V2X message with the second service includes creating an association between the V2X node, the first service, and the second service that enables the network node to use information from the first V2X message with the second service.

9. Using information from the first V2X message with the second service, Obtaining information about the V2X node from the first V2X message; and performing an action for the V2X node associated with the second service using the information about the V2X node obtained from the first V2X message; The method of claim 7, comprising:

10. Using information from the first V2X message with the second service, determining whether the first V2X message and the second V2X message are received within a threshold time period; in response to determining that the first V2X message and the second V2X message were received within the threshold time period, using information from the first V2X message with the second service; and The method of claim 7, comprising:

11. The method of claim 7, wherein the second V2X message is one of a toll message, a parking access message, a road condition message, a geo-networking message, a basic safety message, or an emergency message.

12. 1. A vehicle-to-everything (V2X) node, comprising: means for transmitting a first V2X message to a network node, the first V2X message being associated with a first service and including an identifier of a second service; means for transmitting to the network node a second V2X message including an identifier of the first service, the second V2X message being associated with the second service and configured to enable the network node to use information from the first V2X message with the second service; A V2X node comprising:

13. A Vehicle-to-Everything (V2X) node as described in claim 12, further comprising means for performing a method as described in any one of claims 2 to 6.

14. A network node, means for receiving a first V2X message from a Vehicle-to-Everything (V2X) node, the first V2X message being associated with a first service and including an identifier of a second service; means for receiving a second V2X message from the V2X node, the second V2X message being associated with the second service and including an identifier of the first service; means for using information from the first V2X message with the second service; and A network node comprising:

15. A non-transitory computer-readable storage medium storing processor-executable instructions, the processor-executable instructions being executable by one or more processors of a Vehicle-to-Everything (V2X) node to cause the V2X node to perform a method according to any one of claims 1 to 6, or executable by one or more processors of a network node to cause the network node to perform a method according to any one of claims 7 to 11.