CN116918361A

CN116918361A - Method and system for communicating internet of vehicles (V2X) information

Info

Publication number: CN116918361A
Application number: CN202280018479.4A
Authority: CN
Inventors: W·怀特; S·V·马斯丘; D·F·范杜伦
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-03-10
Filing date: 2022-01-05
Publication date: 2023-10-20

Abstract

Methods for communicating internet of vehicles (V2X) information to a network node and apparatus for implementing the methods include: transmitting a first V2X message, the first V2X message being associated with a first service and comprising an identifier of a second service; and transmitting a second V2X message associated with a second service and including an identifier of the first service, the second V2X message configured to enable the network node to use information from the first V2X message with the second service. The network node may receive the first V2X message and the second V2X message, and may combine information from the first V2X message with the second service.

Description

Method and system for communicating internet of vehicles (V2X) information

RELATED APPLICATIONS

The present application claims the benefit of priority from U.S. provisional patent application No.63/158,966 entitled "Methods And Systems For Communication Vehicle-To-evaluation (V2X) Information," filed 3/10 at 2021, the entire contents of which are incorporated herein by reference for all purposes.

Background

Various regions of the world are developing standards for vehicle-based communication systems and functionality. Standards for north america developed in the Institute of Electrical and Electronics Engineers (IEEE) and Society of Automotive Engineers (SAE), or standards for europe developed in the European Telecommunications Standards Institute (ETSI) and the european standardization Committee (CEN). The IEEE 802.11p standard is the basis for the Dedicated Short Range Communications (DSRC) and ITS-G5 communications standards. IEEE 1609 is a higher layer standard based on IEEE 802.11 p. The cellular internet of vehicles (C-V2X) standard is a competing standard developed under support of the third 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 to improve the overall efficiency and safety of the highway transportation system. 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.

The C-V2X protocol defines two transmission modes that together provide 360 ° non-line-of-sight perception 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), and provides enhanced communication range and reliability in the dedicated Intelligent Transportation System (ITS) 5.9 gigahertz (GHz) spectrum that is independent of cellular networks. The second transmission mode includes vehicle-to-network communication (V2N) in mobile broadband systems and technologies such as third generation wireless mobile communication technology (3G) (e.g., global system for mobile communications (GSM) evolution (EDGE) system, code Division Multiple Access (CDMA) 2000 system, etc.), fourth generation wireless mobile communication technology (4G) (e.g., long Term Evolution (LTE) system, LTE-advanced system, mobile worldwide interoperability for microwave access (mobile WiMAX) system, etc.), fifth generation new radio wireless mobile communication technology (5G NR system, etc.).

An element of the V2X system is the ability of vehicles to broadcast Basic Security Messages (BSM) in north america or Collaborative Awareness Messages (CAM) in europe, which other vehicles may receive and process to improve traffic safety. Processing of such messages in the transmitting and receiving vehicles occurs in onboard equipment that provides internet of vehicles (V2X) functionality (referred to herein as "V2X onboard equipment").

SUMMARY

Aspects include methods for communicating V2X information to a network node and V2X nodes configured to perform the methods. Some aspects may include: transmitting a first V2X message, the first V2X message being associated with a first service and comprising 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, the second V2X message configured to enable the network node to use information from the first V2X message with the second service.

Some aspects may include: generating an identifier of the first service from a signed certificate of the first service associated with the V2X node; and generating an identifier of the second service from the signed certificate of the second service associated with the V2X node. In some aspects, generating the identifier of the first service from the signed certificate of the first service associated with the V2X node may include: generating a hash of the signed certificate of the first service; and generating an identifier of the second service from the signed certificate of the second service associated with the V2X node may include: a hash of the second service's signed certificate is generated. In some aspects, generating the identifier of the first service from the signed certificate of the first service associated with the V2X node may include: generating a truncated identifier of a signed certificate of the first service; and generating an identifier of the second service from the signed certificate of the second service associated with the V2X node may include: a truncated identifier of the signed certificate of the second service is generated.

Some aspects may include: a third V2X message is transmitted, the third V2X message being associated with the second service and comprising a truncated identifier of the first service. In some aspects, the first V2X message may be a basic security message. In some aspects, the second V2X message may be one of: charging messages, parking in and out messages, road condition messages, geographic networking (geonetwork) messages, or emergency messages.

Aspects include methods for receiving V2X information from V2X nodes and network nodes configured to perform the methods. Some aspects may include: receiving a first V2X message from a V2X node, the first V2X message being associated with a first service and comprising 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 comprising an identifier of the first service; and combining information from the first V2X message with the second service.

In some aspects, combining information from the first V2X message with the second service may include: an association of the V2X node, the first service, and the second service is generated, the association enabling the network node to use information from the first V2X message with the second service. In some aspects, combining 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 related to the second service using information about the V2X node obtained from the first V2X message. In some aspects, combining information from the first V2X message with the second service may include: determining whether the first V2X message and the second V2X message are received within a threshold period of time; and in response to determining that the first V2X message and the second V2X message are received within the threshold period of time, combining information from the first V2X message with the second service. In some aspects, the first V2X message may be a basic security message. In some aspects, the second V2X message may be one of: charging messages, parking access messages, road condition messages, geographic networking messages, or emergency messages.

A further aspect includes a V2X node comprising a memory and a processor configured to perform the operations of any of the methods outlined above. A further aspect may include a V2X node having various means for performing functions corresponding to any of the methods outlined above. Further aspects may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a V2X node to perform various operations corresponding to any of the methods outlined above.

Brief Description of Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the claims and, together with the general description and the detailed description given, serve to explain the features herein.

Fig. 1A is a system block diagram illustrating an example V2X system suitable for implementing various embodiments.

Fig. 1B is a conceptual diagram illustrating an example V2X communication protocol stack suitable for implementing various embodiments.

FIG. 2 is a component diagram of an example vehicle system including a block diagram of an example of V2X onboard equipment suitable for implementing various embodiments.

Fig. 3A is a conceptual diagram illustrating an example of a V2X message suitable for implementing various embodiments.

Fig. 3B is a conceptual diagram illustrating an example message flow suitable for implementing various embodiments.

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, in accordance with various embodiments.

Fig. 5 is a process flow diagram illustrating operations 500 executable 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.

Fig. 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, in accordance with various embodiments.

Fig. 7 is a process flow diagram illustrating operations 700 executable by a processor of a V2X node as part of a method 600 for receiving V2X information from a V2X node, according to some embodiments.

Fig. 8 is a component block diagram illustrating an example mobile computing device suitable for use with the various embodiments.

Fig. 9 is a component block diagram illustrating an example mobile computing device suitable for use with the various embodiments.

Detailed Description

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

The V2X processing and communication system may be implemented in a variety of vehicles (such as automobiles, trucks, buses, trailers, autonomous vehicles, robotic systems, and the like). In addition, the ITS or other V2X system includes several fixed equipment facilities, 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 facilities, and other devices using a V2X communication infrastructure. Furthermore, the various embodiments may be used in systems that are independent of ITS functionality but utilize V2X capabilities, such as pay-per-view parking garages, wireless payment systems for various commercial applications, emergency medical services, and the like. To cover all implementations of the various embodiments, the term "V2X node" is used throughout this description and in the claims to refer generally to a mobile, semi-mobile, or fixed system that implements V2X communication functionality. A non-limiting example of a V2X node for description is a vehicle, such as an automobile that pays a toll while traveling on a toll road, but citation of this example and other examples is not intended to limit the scope of the claims reciting the V2X node.

A V2X node (e.g., a vehicle) may transmit various V2X messages related to different services. For example, the V2X node may periodically transmit a basic safety message, which may include information about the V2X node, such as an identifier of the V2X node and a location, speed, path, neighboring road conditions, neighboring vehicles, observed road conditions and vehicle behavior, and the like of the V2X node. As used herein, the term "basic security message" includes Basic Security Messages (BSM) as may be used in north america, collaborative Awareness Messages (CAM) as may be used in europe, and other similar messages that may be used in accordance with other Intelligent Transportation System (ITS) protocols or technical standards. The V2X node may also transmit other V2X messages related to other services. For example, the V2X node may transmit information related to a fee collection or toll collection operation, such as a fee upload message (TUM) or similar message, which may include an identifier of the V2X node and a location, path, and other information about the V2X node. As another example, the 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 for vehicles (such as V2X nodes), identifier(s), etc. The information content of the various V2X messages may overlap or be redundant to some extent.

V2X communication systems are typically bandwidth constrained and may involve numerous participating entities, including many vehicles, roadside units, portal frame units, and other network elements, each transmitting numerous V2X messages. Reducing redundancy in the information conveyed by the V2X messages may reduce bandwidth overhead incurred by the V2X messages and may reduce computational overhead of processing each V2X message. However, a common V2X node security mechanism separates applications from each other or "sandboxes" and grants a transmitter (e.g., V2X node) individual permissions for different sets of application activities (which may be governed by individually issued digital signatures or another suitable security measure). Thus, it is not easy to combine messages configured for different services (e.g., BSM, charging, emergency services, etc.) and apply a single digital signature to cover both or all messages. Furthermore, combining only messages configured for different services may cause privacy concerns because applying a single digital signature to many V2X messages may expose the content of all V2X messages to any device that is authorized to view one of the V2X messages.

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 within the ITS (e.g., another vehicle, a Road Side Unit (RSU), etc.) or 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 V2X nodes, including but not limited to V2X nodes.

Various embodiments enable a V2X node (e.g., V2X on-board equipment of 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 portal unit such as a toll portal unit) to perform operations of a second service provided by or associated with the network node using information provided by the V2X node for the first service.

As mentioned above, the V2X node may transmit various V2X messages that may include redundant information content. For example, a fee collection or toll collection system (toll collection system) may need to accurately determine a particular lane location lane of a V2X node so that the system may collect an appropriate fee or toll (e.g., "lane-level accuracy") from the V2X node. Typical charging messages from V2X nodes may include V2X node identity information, account or other financial information, and location information, as well as other information about the V2X node. At the same time, the V2X node performing the maneuver may transmit one or more V2X messages to coordinate with other vehicles to ensure that the maneuver may be performed safely and efficiently. In addition, all V2X equipped vehicles routinely share information such as steering information, location information, etc. in basic safety messages.

Various embodiments include methods for communicating V2X node information in a manner that improves efficiency and reduces processing and communication link overhead required to handle V2X messages, as well as V2X nodes and network nodes configured to perform these methods. In some embodiments, a V2X node (e.g., a V2X processing device in V2X on-board equipment of a vehicle) may transmit a first V2X message for receipt by a network node, the first V2X message associated with a first service and including an identifier of a second service, and the V2X node may transmit a second V2X message associated with a second service and including an identifier of the first service, the second V2X message configured to enable the network node to use information from the first V2X message with the second service. In various embodiments, including the identifier of the service with the V2X messages of other services may enable the recipient network node to create an association between the message for the first service from the V2X node and the message for the second service from the V2X node, thereby enabling the network node to perform operations on the second service on behalf of the V2X node using information provided by the V2X node in the message for the first service. In this way, the V2X node may generate a V2X message for the second service that includes an identifier of the first service, rather than including information in the V2X message for the second service that is redundant to the information in the V2X message for the first service. For example, a V2X node may transmit a basic security message that includes node identification information and a location of the V2X node. The V2X node may also transmit a charging message referencing the basic security message, thereby enabling the recipient network node to use the identification information and/or location information from the basic security message.

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

In some embodiments, the V2X node may generate the identifier from a signed certificate associated with the service. In some embodiments, the V2X node may generate an identifier of a first service from a signed certificate of the first service associated with the V2X node, and may generate an identifier of a second service from a signed certificate of 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 recipient network node.

In some embodiments, the V2X node may generate an identifier of the first service by generating a hash of the signed certificate of the first service and may generate an identifier of the second service by generating a hash of the signed certificate of the second service. In some embodiments, after establishing an association between the message of the first service and the message of the second service, the V2X node may generate a shortened or truncated identifier of the first service in the second service to further reduce the amount of data in each V2X message. In some embodiments, the truncated identifier may be as small as the last three or four bytes in the full hash identifier. In some embodiments, the V2X node may generate a truncated hash of the signed certificate of the first service (e.g., the last three or four bytes in the full hash certificate) and may generate a truncated hash of the signed certificate of the second service (e.g., the last three or four bytes of the full hash certificate). In some embodiments, the recipient network node may readily identify the truncated identifier of each service's signature certificate as being related to the full or larger identifier of each service's signature certificate.

In some embodiments, the V2X node may determine whether a similar credential has been used by another vehicle or network node for a threshold radius and/or a threshold period of time. In response to determining that a similar credential has not been used by another vehicle or network node for a threshold radius and/or a threshold period of time, the V2X node may generate and use a truncated identifier of the service for data included in the message.

In some embodiments, the V2X node may puncture V2X messages that include the full or larger identifier of the service with V2X messages that use the truncated identifier of the service. In this way, the transmitting V2X node may be locally non-ambiguous with respect to the signature certificate associated with the V2X node and service, while periodically including a larger identifier, which is cryptographically safer. For example, an attacker may record a communication session (i.e., a V2X message associated with a service) and replace the V2X message signed by the signature of the V2X node with a message signed by the attacker's certificate. While an attacker may be able to identify available certificates based on truncated identifiers, it is not feasible to identify certificates with longer identifiers. In this way, interleaving V2X messages that include a larger identifier of the service may increase the security of V2X communications.

In some embodiments, the first V2X message may be a basic security message. In some embodiments, the second V2X message may be related to another service. For example, the second V2X message may be a toll message (e.g., for a toll collection 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, RSU, or network node regarding traffic, observed vehicle behavior, road damage, dangerous road conditions (such as ice or floods, etc.), a geographic networking message (e.g., for a geographic networking message or messaging system), an emergency responder message (e.g., a police, fire, emergency medical technician, or other emergency responder system), or another suitable message or messaging system.

In various embodiments, the network node may receive a first V2X message from the V2X node, the first V2X message associated with the first service and including an identifier of the second service, and the network node may receive a second V2X message from the V2X node, the 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, the association enabling 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 a second service related operation for the V2X node using the information about the V2X node obtained from the first V2X message.

In some embodiments, the network node may determine whether the first V2X message and the second V2X message are received within a threshold period of time. In response to determining that the first V2X message and the second V2X message are received within a threshold period of time, the network node may use information from the first V2X message with the second service. In this way, the network node may increase the security of the association between the V2X message of the first service and the V2X message of the second service and avoid using data (e.g., the location of the mobile vehicle) that may no longer be accurate.

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

For ease of reference, some embodiments are described herein with reference to a vehicle using a vehicle networking (V2X) system and protocol. However, it should be understood that various embodiments encompass any or all of V2X or vehicle-based communication standards, messages, or technologies. Accordingly, nothing in this application should be construed as limiting the claims to V2X systems, basic Security Messages (BSMs), or V2X messages unless explicitly so stated in the claims. Additionally, 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 with mobile devices, mobile computers, road Side Units (RSUs), and other devices equipped to monitor road and vehicle conditions and participate in V2X communications.

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. Referring to fig. 1A and 1B, each vehicle 12, 14, 16 includes V2X onboard 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 the onboard equipment (e.g., 102, 104, 106) of other vehicles.

By sharing vehicle position, speed, direction, braking, and other information, the vehicle can maintain a safe interval and identify and avoid potential collisions. For example, the trailing vehicle 12 that receives the primary safety message 114 from the leading vehicle 16 may determine the speed and position of the vehicle 16, thereby enabling the vehicle 12 to match the speed and maintain the safety separation distance 20. By being notified via the basic safety message 114 when the lead vehicle 16 applies the brakes, the V2X equipment 102 in the trailing vehicle 12 can apply the brakes simultaneously to maintain the safety separation distance 20 even when the lead vehicle 16 suddenly stops. As another example, V2X equipment 104 within the truck vehicle 14 may receive basic safety messages 112, 116 from both vehicles 12, 16 and thus be notified that the truck vehicle 14 should stop at the intersection to avoid a collision. Further, each of the vehicle V2X onboard equipment 102, 104, 106 may communicate with each other using any of a variety of proximity communication protocols.

Additionally, the vehicle may be capable of communicating data and information regarding basic security messages and other V2X communications via the communication network 18 (e.g., V2X, cellular, wiFi, etc.) to the various network elements 132, 134, 136 via the communication links 122, 124, 146. For example, the network element 132 may be incorporated into or in communication with an RSU, a gantry unit, or the like. 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 handling, and the like. The network elements 134, 136 may be configured to communicate with each other over wired or wireless networks 142, 144 to exchange information associated with payment processing, road condition monitoring, emergency provider message handling, and the like.

FIG. 2 is a component diagram of an example vehicle system 200 suitable for implementing various embodiments. Referring to fig. 1A-2, a system 200 may include a vehicle 202, the vehicle 202 including a vehicle processing system 204 (e.g., a telematics control unit or an on-board unit (TCU/OBU)). The V2X processing device 202 may be in communication with various systems and devices, such as an in-vehicle network 210, an infotainment system 212, various sensors 214, various actuators 216, and a radio 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 for authenticating plaintext and ciphertext, as described further below.

The vehicle processing device 204 may include a processor 205, a memory 206, an input module 207, an output module 208, and a radio 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 the methods according to the various embodiments described herein. Further, the processor 205 may be coupled to an output module 208 of a display in the controllable vehicle and to an input module 207 to receive information from vehicle sensors as well as driver inputs.

The vehicle processing system 204 may include a V2X antenna 219 coupled to a radio module 218, the 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, V2X processing device 202 may receive information from a plurality of information sources, such as in-vehicle network 210, infotainment system 212, various sensors 214, various actuators 216, and radio module 218. The V2X processing device 202 may detect an improper behavior condition in a system of the vehicle, such as one of the plurality of information sources 210-218, an application or service executing on the V2X processing device 202, or another system of the vehicle.

Examples of in-vehicle networks include Controller Area Network (CAN), local Interconnect Network (LIN), networks using FlexRay protocol, media Oriented System Transport (MOST) networks, and automotive ethernet networks. Examples of vehicle sensors include location determination systems such as Global Navigation Satellite System (GNSS) systems, cameras, radars, lidar, ultrasonic sensors, infrared sensors, and other suitable sensor devices and systems. Examples of vehicle actuators include various physical control systems, such as for steering, braking, engine operation, lights, direction signals, and the like.

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. Referring to fig. 1-3 b, the V2X message 300 and message flow 350 may be implemented by a processor of a vehicle processing system (e.g., 204) and a network node (e.g., another one of the vehicles 12, 14, 16, 220, RSU 132, network element 134, 136) of the V2X node (e.g., vehicle 12, 14, 16, 202).

The first V2X message 302 may include information such as a payload (e.g., data or information) and/or metadata 304 associated with the first service. The first V2X message 302 may include one or more credentials 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 signed certificate 310 of 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 security message.

The second V2X message 320 may include information such as a payload (e.g., data or information) and/or metadata 322 associated with the second service. The second V2X message 320 may include one or more certificates 324 associated with the second service and a signed certificate 328 of 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).

Referring to fig. 3B, a message stream 350 (which may be transmitted by a V2X node, for example) may include V2X messages 352-366. The V2X message of 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. The inclusion of an identifier of another V2X service in each V2X message may enable a recipient device (e.g., a network node) to associate the two services and/or messages from the two services with respect 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 association may enable the network node to use information from the first V2X message to perform operations for the second service of the V2X node.

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

In some embodiments, the V2X node may puncture V2X messages that include the full or longer identifier of the service with V2X messages that use the truncated identifier of the service. For example, V2X messages 360, 362, and 366 may include truncated identifiers of the first service, and V2X message 364 interspersed between V2X messages 362 and 366 may include longer identifiers of the first service. In various embodiments, the larger identifier is cryptographically more secure than the truncated identifier. In this way, the V2X node may reduce the total amount of data or data transferred over the V2X node communication link while maintaining a level of security sufficient to deter an attacker by periodically including longer identifiers.

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, in accordance with various embodiments. Referring to fig. 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).

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

In block 404, the V2X processing device may transmit a second V2X message associated with the second service and including an identifier of the first service, the second V2X message configured to enable the 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 park in and out message, a road condition message, a geographic networking message, or an emergency responder message. The second V2X message may include an identifier of the first service (i.e., the basic secure message service). In various embodiments, including an identifier of the second service in the first V2X message and an identifier of the first service in the second V2X message may enable the network node to use information from the first V2X message (e.g., the basic security message) with the second service. The means for performing the operations of block 404 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

As mentioned above, the V2X processing device may transmit any number of first V2X messages and any number of second V2X messages in the method 400. Further, in some embodiments, the V2X processing device may transmit a third V2X message associated with the second service and including the truncated identifier of the first service.

Fig. 5 is a process flow diagram illustrating operations 500 executable 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. Referring to fig. 1-5, the operations of operation 500 may be performed by a V2X processing device in a V2X node (e.g., 12, 14, 16, 202).

In block 502, the V2X processing device may generate an identifier of a first service associated with the V2X node from a signed certificate of the first service. In some embodiments, the V2X processing device may generate the identifier of the first service by generating a hash of the signed certificate of the first service. In some embodiments, the V2X processing device may generate the identifier of the first service by generating a truncated hash of the signature certificate of the first service. The means for performing the operations of block 502 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

In block 504, the V2X processing device may generate an identifier of a second service associated with the V2X node from the signed certificate of the second service. In some embodiments, the V2X processing device may generate the identifier of the second service by generating a hash of the second service's signed certificate. In some embodiments, the V2X processing device may generate the identifier of the second service by generating a truncated hash of the signature certificate of the second service. The means for performing the operations of block 504 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

Following the operation of block 504, the V2X processing device may proceed to perform the operation of block 402 of method 400, as described.

Fig. 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, in accordance with various embodiments. Referring to fig. 1-6, the operations of method 600 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).

In block 602, the processing device may receive a first V2X message from a V2X node, the first V2X message associated with a first service and including an identifier of a second service. The means for performing the operations of block 602 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

In block 604, the processing device may receive a second V2X message from the V2X node, the second V2X message associated with the second service and including an identifier of the first service. The means for performing the operations of block 604 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, the processor 205, the radio module 218, and the antenna 219.

In block 606, the processing device may combine information from the first V2X message with the second service. In some embodiments, a processing device may obtain information about a V2X node from a first V2X message, and may 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, the association enabling the network node to use information from the first V2X message with the second service. The means for performing the operations of block 602 may include the V2X on-board equipment 102, 104, 106, and the vehicle processing system 204.

Fig. 7 is a process flow diagram illustrating operations 700 executable by a processor of a V2X node as part of a method 600 for receiving V2X information from a V2X node, according to various embodiments. Referring to fig. 1-7, the operations of operation 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).

After performing the operations of block 604 (fig. 6), the processing device may determine in decision block 710 whether the first V2X message and the second V2X message are received within a threshold period of time. In some embodiments, the processing device may determine whether the first V2X message and the second V2X message are received within a threshold period of time of each other. The means for performing the operations of decision block 710 may include the V2X on-board equipment 102, 104, 106, the vehicle processing system 204, and the processor 205.

In response to determining that the first V2X message and the second V2X message are not received within the threshold period of time (i.e., decision block 710 = "no"), the processing device may not use information from the V2X message with the second service in block 712. In some embodiments, the processor may prevent generating the 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 are not received within the threshold period of time. The 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.

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

Fig. 8 is a component block diagram illustrating an example mobile computing device 800 suitable for use with the various embodiments. 1-8, the various embodiments may be implemented in a wide variety of computing systems including in-vehicle equipment as well as mobile computing devices, including an example mobile computing device 800. The mobile computing device 800 may include a processor 802, the processor 802 coupled to a touch screen controller 804 and internal memory 806. The processor 802 may be one or more multi-core integrated circuits designated for general or specific processing tasks. The internal memory 806 may be volatile or non-volatile memory, and may also 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 touch screen controller 804 and the processor 802 may also be coupled to a touch screen panel 812, such as a resistive sensing touch screen, capacitive sensing touch screen, infrared sensing touch screen, or the like. Additionally, the display of the mobile computing device 800 need not have touch screen capabilities.

The mobile computing device 800 can have one or more radio signal transceivers 808 (e.g., peanut, bluetooth, zigbee, wi-Fi, RF radio) coupled to each other and/or to the processor 802, and an antenna 810 for transmitting and receiving communications. Transceiver 808 and antenna 810 may be used in conjunction with the above-mentioned circuitry to implement various wireless transmission protocol stacks and interfaces. The mobile computing device 800 may include a cellular network wireless modem chip 816 that enables communication via a cellular network and is coupled to a processor.

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 configured to accept one type of connection alone or may be configured to accept various types of physical and communication connections, either common or proprietary, such as Universal Serial Bus (USB), fireWire (FireWire), thunderbolt (Thunderbolt), or PCIe. Peripheral connection interface 818 may also be coupled to a similarly configured peripheral connection port (not shown).

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 for containing all or some of the components described herein, the housing constructed of plastic, metal, or a combination of materials. One of ordinary skill 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 or rechargeable battery, coupled to the processor 802. The rechargeable battery may also be coupled to the peripheral device connection port to receive charging current from a source external to the mobile computing device 800. The mobile computing device 800 may also include physical buttons 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.

Fig. 9 is a component block diagram illustrating an example mobile computing device 900 suitable for use with the various embodiments. With reference to fig. 1-9, the various embodiments may be implemented in a wide variety of computing systems including an example mobile computing device 900 (illustrated as a laptop computer). The mobile computing device 900 may include a touch pad touch surface 917 that serves as a pointing device for a computer and, thus, may receive drag, scroll, and flick gestures similar to those implemented on a computing device equipped with a touch screen display and as described above. The mobile computing device 900 will typically include a processor 902 coupled to volatile memory 912 and a mass nonvolatile memory (such as a hard disk drive 913 of flash memory). Additionally, the mobile computing device 900 may have one or more antennas 908 for transmitting and receiving electromagnetic radiation, connectable to a wireless data link, and/or a cellular telephone transceiver 916 coupled to the processor 902. The mobile computing device 900 may also include a floppy disk drive 914 and a Compact Disc (CD) drive 915 coupled to the processor 902. In a notebook configuration, the computer housing includes a touch pad 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 a processor (e.g., via a USB input) as is well known, which may also be used in connection with the various embodiments.

Examples of implementations are described in the following paragraphs. While some of the following implementation examples are described in terms of example methods, further example implementations may include: example methods implemented by a V2X processing device (which may be an on-board unit, a mobile device unit, a mobile computing unit, or a stationary roadside unit), a network node processing device, or a network computing node processing device, which may be a processor including processor-executable instructions configured to perform operations of the following methods implementing the examples, discussed in the following paragraphs; example methods implemented by a V2X processing device, a network node processing device, or a network computing node processing device discussed in the following paragraphs, the processing devices including means for performing the functions of the following example methods; and the example methods discussed in the following paragraphs 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 node processing device, or a network computing node processing device to perform operations of the following methods implementing the examples.

Example 1. A method performed by a processor of a vehicle networking (V2X) node for communicating V2X information to a network node, comprising: transmitting a first V2X message, the first V2X message being associated with a first service and comprising 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, the second V2X message configured to enable the network node to use information from the first V2X message with the second service.

Example 2. The method of example 1, further comprising: generating an identifier of the first service from a signed certificate of the first service associated with the V2X node; and generating an identifier of the second service from the signed certificate of the second service associated with the V2X node.

Example 3 the method of example 2, wherein generating an identifier of the first service from a signed certificate of the first service associated with the V2X node comprises: generating a hash of the signed certificate of the first service; and generating an identifier of the second service from the signed certificate of the second service associated with the V2X node comprises: a hash of the second service's signed certificate is generated.

Example 4 the method of any one of examples 2 or 3, wherein generating an identifier of the first service from a signed certificate of the first service associated with the V2X node comprises: generating a truncated identifier of a signed certificate of the first service; and generating an identifier of the second service from the signed certificate of the second service associated with the V2X node comprises: a truncated identifier of the signed certificate of the second service is generated.

Example 5 the method of any one of examples 2-4, further comprising: a third V2X message is transmitted, the third V2X message being associated with the second service and comprising a truncated identifier of the first service.

Example 6 the method of any of examples 1-5, wherein the first V2X message is a basic security message.

Example 7 the method of any one of examples 1-6, wherein the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, or emergency messages.

Example 8. A method performed by a processor of a network node for receiving V2X information from a vehicle networking (V2X) node, comprising: receiving a first V2X message from a V2X node, the first V2X message being associated with a first service and comprising 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 comprising an identifier of the first service; and combining information from the first V2X message with the second service.

Example 9 the method of example 8, wherein using information from the first V2X message with the second service comprises: an association of the V2X node, the first service, and the second service is generated, the association enabling the network node to use information from the first V2X message with the second service.

Example 10 the method of any one of examples 8 or 9, wherein combining information from the first V2X message with the second service comprises: obtaining information about the V2X node from the first V2X message; and performing an operation for the V2X node related to the second service using information about the V2X node obtained from the first V2X message.

Example 11 the method of any of examples 8-10, wherein combining information from the first V2X message with the second service comprises: determining whether the first V2X message and the second V2X message are received within a threshold period of time; and in response to determining that the first V2X message and the second V2X message are received within the threshold period of time, combining information from the first V2X message with the second service.

Example 12 the method of any of examples 8-11, wherein the first V2X message is a basic security message.

Example 13 the method of any one of examples 8-12, wherein the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, or emergency messages.

The foregoing method descriptions and the 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 appreciated by those skilled in the art, the order of operations in the foregoing embodiments may be performed in any order. Words such as "thereafter," "then," "next," etc. are not intended to limit the order of operations; these terms are only used to simply direct the reader through a description of the method. Furthermore, any reference to claim elements in the singular (e.g., using the articles "a," "an," or "the") is not to be construed as limiting the element to the singular.

The various illustrative logical blocks, modules, circuits, and algorithm operations described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative 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 upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the claims.

The hardware used to implement the various illustrative logic, logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an 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, a plurality of 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 dedicated to a given function.

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 implemented in a processor-executable software module, which may reside on a non-transitory computer-readable or processor-readable storage medium. The non-transitory computer-readable or processor-readable storage medium may be any storage medium that can be accessed by a computer or processor. By way of example, and not limitation, such non-transitory computer-readable or processor-readable media can comprise 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 can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk (disk) and disc (disk) as used herein include Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disk) often reproduce data magnetically, while discs (disk) reproduce data optically with lasers. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present claims. 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 claims. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.

Claims

1. A method performed by a processor of a vehicle networking (V2X) node for communicating V2X information to a network node, comprising:

transmitting a first V2X message, the first V2X message being associated with a first service and comprising an identifier of a second service; and

transmitting a second V2X message, the second V2X message being associated with the second service and comprising an identifier of the first service, the second V2X message being configured to enable the network node to use information from the first V2X message with the second service.

2. The method of claim 1, further comprising:

Generating an identifier of the first service from a signed certificate of the first service associated with the V2X node; and

an identifier of the second service is generated from a signed certificate of the second service associated with the V2X node.

3. The method of claim 2, wherein

Generating an identifier of the first service from a signed certificate of the first service associated with the V2X node includes: generating a hash of a signed certificate of the first service; and is also provided with

Generating an identifier of the second service from a signed certificate of the second service associated with the V2X node includes: a hash of the second service's signed certificate is generated.

4. The method of claim 2, wherein:

generating an identifier of the first service from a signed certificate of the first service associated with the V2X node includes: generating a truncated identifier of a signed certificate of the first service; and is also provided with

Generating an identifier of the second service from a signed certificate of the second service associated with the V2X node includes: a truncated identifier of a signed certificate of the second service is generated.

5. The method of claim 2, further comprising: a third V2X message is communicated, the third V2X message being associated with the second service and comprising a truncated identifier of the first service.

6. The method of claim 1, wherein the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, basic security messages, or emergency messages.

7. A vehicle networking (V2X) node, comprising:

a processor configured with processor-executable instructions for:

transmitting a first V2X message to a network node, the first V2X message being associated with a first service and comprising an identifier of a second service; and

transmitting a second V2X message to the network node, the second V2X message being associated with the second service and comprising an identifier of the first service, the second V2X message being configured to enable the network node to use information from the first V2X message with the second service.

8. The V2X node of claim 7, wherein the processor is further configured with processor-executable instructions to:

9. The V2X node of claim 8, wherein the processor is further configured with processor-executable instructions to:

generating a hash of a signed certificate of the first service; and

a hash of the second service's signed certificate is generated.

10. The V2X node of claim 8, wherein the processor is further configured with processor-executable instructions to:

generating a truncated identifier of a signed certificate of the first service; and

a truncated identifier of a signed certificate of the second service is generated.

11. The V2X node of claim 8, wherein the processor is further configured with processor-executable instructions to: a third V2X message is communicated, the third V2X message being associated with the second service and comprising a truncated identifier of the first service.

12. The V2X node of claim 7, wherein the processor is further configured with processor-executable instructions such that the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, basic security messages, or emergency messages.

13. A vehicle networking (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 comprising an identifier of a second service; and

means for transmitting a second V2X message to the network node, the second V2X message being associated with the second service and comprising an identifier of the first service, the second V2X message configured to enable the network node to use information from the first V2X message with the second service.

14. The V2X node of claim 13, further comprising:

means for generating an identifier of the first service from a signed certificate of the first service associated with the V2X node; and

means for generating an identifier of the second service from a signed certificate of the second service associated with the V2X node.

15. The V2X node of claim 14, wherein

The means for generating an identifier of the first service from a signed certificate of the first service associated with the V2X node comprises: means for generating a hash of a signed certificate of the first service; and is also provided with

The means for generating an identifier of the second service from a signed certificate of the second service associated with the V2X node comprises: means for generating a hash of a signed certificate of the second service.

16. The V2X node of claim 14, wherein:

the means for generating an identifier of the first service from a signed certificate of the first service associated with the V2X node comprises: means for generating a truncated identifier of a signed certificate of the first service; and is also provided with

The means for generating an identifier of the second service from a signed certificate of the second service associated with the V2X node comprises: means for generating a truncated identifier of a signed certificate of the second service.

17. The V2X node of claim 14, further comprising: means for transmitting a third V2X message associated with the second service and including a truncated identifier of the first service.

18. The V2X node of claim 13, wherein the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, basic security messages, or emergency messages.

19. A method performed by a processor of a network node for receiving V2X information from a vehicle networking (V2X) node, comprising:

receiving a first V2X message from a V2X node, the 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 comprising an identifier of the first service; and

information from the first V2X message is used with the second service.

20. The method of claim 19, wherein associating information from the first V2X message with the second service comprises: an association of the V2X node, the first service, and the second service is generated, the association enabling the network node to use information from the first V2X message with the second service.

21. The method of claim 19, wherein associating information from the first V2X message with the second service comprises:

obtaining information about the V2X node from the first V2X message; and

performing an operation for the V2X node related to the second service using information about the V2X node obtained from the first V2X message.

22. The method of claim 19, wherein associating information from the first V2X message with the second service comprises:

determining whether the first V2X message and the second V2X message are received within a threshold period of time; and

information from the first V2X message is used with the second service in response to determining that the first V2X message and the second V2X message are received within the threshold period of time.

23. The method of claim 19, wherein the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, basic security messages, or emergency messages.

24. A network node, comprising:

a processor configured with processor-executable instructions for:

receiving a first V2X message from a network-of-vehicles (V2X) node, the first V2X message being associated with a first service and including an identifier of a second service;

information from the first V2X message is used with the second service.

25. The network node of claim 24, wherein the processor is further configured with processor-executable instructions to: an association of the V2X node, the first service, and the second service is generated, the association enabling the network node to use information from the first V2X message with the second service.

26. The network node of claim 24, wherein the processor is further configured with processor-executable instructions to:

obtaining information about the V2X node from the first V2X message; and

27. The network node of claim 24, wherein the processor is further configured with processor-executable instructions to:

28. The network node of claim 24, wherein the processor is further configured with processor-executable instructions such that the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, basic security messages, or emergency messages.

29. A network node, comprising:

means for receiving a first V2X message from a network-of-vehicles (V2X) node, the first V2X message being associated with a first service and comprising 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 comprising an identifier of the first service; and

means for associating information from the first V2X message with the second service.

30. The network node of claim 29, wherein means for associating information from the first V2X message with the second service comprises: means for generating an association of the V2X node, the first service and the second service, the association enabling the network node to use information from the first V2X message with the second service.

31. The network node of claim 29, wherein means for associating information from the first V2X message with the second service comprises:

means for obtaining information about the V2X node from the first V2X message; and

means for performing an operation for the V2X node related to the second service using information about the V2X node obtained from the first V2X message.

32. The network node of claim 29, wherein means for associating information from the first V2X message with the second service comprises:

means for determining whether the first V2X message and the second V2X message are received within a threshold period of time; and

means for associating information from the first V2X message with the second service in response to determining that the first V2X message and the second V2X message are received within the threshold period of time.

33. The network node of claim 29, wherein the second V2X message is one of: charging messages, parking access messages, road condition messages, geographic networking messages, basic security messages, or emergency messages.