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 of U.S. Provisional Patent Application No. 63 / 158,966, titled "Methods And Systems For Communication Vehicle-To-Everything (V2X) Information", filed on March 10, 2021, the entire content of which is incorporated herein by reference for all purposes.

Technical Field

[0002] Relates to methods and systems for communicating vehicle-to-everything (V2X) information.

Background Art

[0003]

[0002] Multiple regions of the world are developing standards for vehicle-based communication systems and functionality. Standards are being developed in the Institute of Electrical and Electronics Engineers (IEEE) and the Society of Automotive Engineers (SAE) for use in North America, or in the European Telecommunications Standards Institute (ETSI) and the European Committee for Standardization (CEN) for use in Europe. The IEEE802.11p standard is the basis for the dedicated short-range communication (DSRC) and ITS-G5 communication standards. IEEE1609 is a higher-layer standard based on IEEE802.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 function as the basis for vehicle-based wireless communication 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 provide 360-degree non-line-of-sight awareness along with enhanced road safety and a higher level of predictability for 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 the 5.9 gigahertz (GHz) spectrum of dedicated intelligent transportation systems (ITS) 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 Systems 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.), and fifth-generation new wireless mobile communication technology (e.g., 5G NR system, etc.).

[0005]

[0004] An element of the V2X system is the ability of a vehicle to broadcast a Basic Safety Message (BSM) in North America or a Cooperative Awareness Message (CAM) in Europe, which other vehicles can receive and process to improve traffic safety. Processing of such messages in the transmitting and receiving vehicles is carried out in onboard equipment (hereinafter referred to as "V2X onboard equipment") that provides vehicle-to-everything (V2X) functionality. [Overview of the project]

[0006]

[0005] Various embodiments include a method for communicating V2X information to a network node and a V2X node configured to perform such method. Some embodiments may include sending a first V2X message associated with a first service and including an identifier for a second service, and sending a second V2X message associated with a second service and including an identifier for the first service, configured to allow a network node to use the information from the first V2X message together with the second service.

[0007]

[0006] In some embodiments, the generation of an identifier for a first service may be generated from a signing certificate of a first service associated with a V2X node, and the generation of an identifier for a second service may be generated from a signing certificate of a second service associated with a V2X node. In some embodiments, the generation of an identifier for a first service may be generated from a signing certificate of a first service associated with a V2X node, and the generation of an identifier for a second service may be generated from a signing certificate of a second

[0008]

[0007] In some embodiments, the transmission of a third V2X message associated with a second service and including an abbreviated identifier for the first service may be a basic safety message. In some embodiments, 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]

[0008] Various embodiments include a method for receiving V2X information from a V2X node, and a network node configured to perform such method. Some embodiments may include receiving a first V2X message from a V2X node that is associated with a first service and includes an identifier for a second service, receiving a second V2X message from the V2X node that is associated with a second service and includes an identifier for the first service, and using the information from the first V2X message together with the second service.

[0010]

[0009] In some embodiments, using information from a first V2X message with a second service may include generating relationships between a V2X node, a first service, and a second service that enable a network node to use information from a first V2X message with a second service. In some embodiments, using information from a first V2X message with a second service may include obtaining information about a V2X node from the first V2X message and using the information about the V2X node obtained from the first V2X message to perform an action for the V2X node related to the second service. In some embodiments, using information from a first V2X message with a second service may include determining whether the first V2X message and the second V2X message were received within a threshold time period and, in response to determining that the first V2X message and the second V2X message were received within a threshold time period, using information from the first V2X message with the second service. In some examples, the first V2X message may be a basic safety message. In some embodiments, the second V2X message may be one of the following: a toll message, a parking access message, a road conditions message, a geonetworking message, or an emergency message.

[0011]

[0010] Further embodiments include a V2X node having memory and a processor configured to perform any of the operations summarized above. Further embodiments may include a V2X node having various means for performing a function corresponding to any of the operations summarized above. Further embodiments may include a non-temporary processor-readable storage medium storing processor-executable instructions configured to cause the processor of the V2X node to perform any of the corresponding operations summarized above. [Brief explanation of the drawing]

[0012]

[0011] The accompanying drawings incorporated herein and constituting part thereof illustrate exemplary embodiments of the claims and, together with the given schematic and detailed descriptions, serve to illustrate the features of the invention. [Figure 1A]

[0012] Figure 1A is a system block diagram illustrating an exemplary V2X system suitable for carrying out various embodiments. [Figure 1B]

[0013] Figure 1B is a conceptual diagram illustrating an exemplary V2X communication protocol stack suitable for implementing various embodiments. [Figure 2]

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

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

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

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

[0018] Figure 5 is a process flow diagram illustrating an operation 500 that can be performed by the processor of a V2X node as part of a method 400 for communicating V2X information to a network node, according to several embodiments. [Figure 6]

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

[0020] Figure 7 is a process flow diagram illustrating an operation 700 that can be performed by the processor of a V2X node as part of a method 600 for receiving V2X information from a V2X node, according to several embodiments. [Figure 8]

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

[0022] Figure 9 is a component block diagram illustrating an exemplary mobile computing device suitable for use with various embodiments. Detailed explanation

[0013]

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

[0014]

[0024] V2X processing and communication systems may be implemented in a variety of vehicles, including automobiles, trucks, buses, trailers, autonomous vehicles, and robotic systems. ITS or other V2X systems may also include several fixed equipment installations, such as RSUs, access nodes, and wireless relay nodes. Various embodiments may be implemented in any of the various V2X-equipped vehicles, fixed equipment, and other devices using V2X communication infrastructure. Furthermore, various embodiments, independent of ITS functionality, may be useful in systems that leverage V2X capabilities, such as toll parking garages, wireless payment systems for various commercial applications, and emergency services. To encompass all implementations of the various embodiments, the term “V2X node” is used in this description and claims to generally refer to a mobile, semi-mobile, or fixed system implementing V2X communication functionality. A non-limiting example of a V2X node used for description is a vehicle, such as an automobile paying tolls while traveling on a toll road, but this and other references are not intended to limit the claims describing a V2X node.

[0015]

[0025] A V2X node (for example, a vehicle) may transmit various V2X messages relating to different services. For example, a V2X node may periodically transmit basic safety messages that may include information about the V2X node, such as the V2X node's identifier and 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 basic safety messages (BSM) that may be used in North America, coordinated recognition messages (CAM) that may be used in Europe, and other similar messages that may be used in accordance with other intelligent transport system (ITS) protocols or technical standards. A V2X node may also transmit other V2X messages relating to other services. For example, a V2X node may transmit information relating to toll collection or toll collection operations, such as toll upload messages (TUM) or similar messages, which may include the V2X node's identifier and 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 the V2X node identifier and the V2X node's location, speed, direction of travel, latitude, longitude, altitude, and other information about the V2X node. As yet another example, a V2X message used by an emergency responder or emergency service provider (e.g., police, fire department, paramedic, etc.) may include location information, vehicle identifiers such as the V2X node, etc. The informational content of various V2X messages may overlap or be redundant to some extent.

[0016]

[0026] A V2X communication system may involve a number of participating entities, typically with bandwidth constraints, 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 V2X messages can reduce the bandwidth overhead incurred by V2X messages and can reduce the computational overhead of processing each V2X message. However, common V2X node security mechanisms separate or "sandbox" applications from each other and give separate permissions (which can be managed by separately issued digital signatures or other appropriate security means) to a transmitter (e.g., a V2X node) for different sets of application activities. Therefore, combining messages configured for different services (e.g., BSM, toll, emergency services, etc.) and applying a single digital signature to cover both or all messages is non-trivial. Further, applying a single digital signature to many V2X messages may expose all the content of the V2X messages to any device permitted to view one of the V2X messages, so simply combining messages configured for different services may raise privacy concerns.

[0017]

[0027] Various embodiments include methods and mechanisms for efficiently communicating V2X information within an Intelligent Transportation System (ITS) to other network elements, which may be network elements within an ITS (e.g., another vehicle, a roadside unit (RSU), etc.) or within another network (e.g., the Internet, a private network, etc.). To include network elements that may be within a non-ITS system as well as IDS network elements, the term "network node" is used herein to refer to a network element at which a V2X node may transmit V2X messages according to various embodiments. Thus, a "network node" may be any computing device within 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 vehicle's V2X equipped device, 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)) and utilize information provided by the V2X node for a first service in the execution of an operation for a second service provided by or associated with the network node.

[0019]

[0029] As described above, a V2X node may send various V2X messages that may contain redundant informational content. For example, a toll collection or toll collection system (toll system) may need to precisely determine the lane location of a V2X node so that the system can charge the V2X node the appropriate toll 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 send one or more V2X messages to coordinate with other vehicles to ensure that the maneuver can be performed safely and efficiently. Furthermore, all V2X-equipped vehicles routinely share information such as maneuver information and location information in basic safety messages.

[0020]

[0030] Various embodiments include methods for communicating V2X node information in a manner that improves efficiency and reduces the processing and communication link overhead required to handle V2X messages, as well as V2X nodes and network nodes configured to perform the method. In some embodiments, a V2X node (e.g., a V2X processing device in a vehicle's V2X-equipped device) can send a first V2X message associated with a first service and including an identifier for a second service for reception by a network node, and a second V2X message associated with a second service and including an identifier for the first service, configured to allow the network node to use information from the first V2X message for the second service. In various embodiments, including a service identifier in a V2X message for another service can allow a receiving network node to create a relationship between a message from a V2X node for a first service and a message from a V2X node for a second service, thereby allowing the network node to use information provided by the V2X node in the message for the first service when performing an action on behalf of the V2X node for the second service. In this way, a V2X node can generate a V2X message for a second service that includes an identifier for the first service, rather than including information in the V2X message for the first service that is redundant to the information in the V2X message for the first service. For example, a V2X node can send a basic safety message that includes node identification information and the location of the V2X node. The V2X node can also send 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 and are not intended to require any order or sequence of messages, nor are they intended to limit the scope to just two messages. Furthermore, any number of “first” messages and any number of “second” messages may be transmitted. In addition, an additional message, commonly referred to herein as a “third message,” may also be transmitted, incorporating elements of 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 when performing the operation of the second service. In some embodiments, information from the first service may be provided within the message of the first service. In some embodiments, information from the second service may be used when performing the operation of the first service. In some embodiments, information from the second service may be provided within the message of the second service.

[0022]

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

[0023]

[0033] In some embodiments, a V2X node may generate an identifier for a first service by generating a hash of the signing certificate of a first service, and may generate an identifier for a second service by generating a hash of the signing certificate of a second service. In some embodiments, after the relationships between messages for the first and second services are established, the V2X node may generate a shortened or abbreviated identifier for the first service within the second service to further reduce the amount of data in each V2X message. In some embodiments, the abbreviated identifier may be as small as the last three or four bytes of the full hash identifier. In some embodiments, a V2X node may generate a shortened hash of the signing certificate of a first service (e.g., the last three or four bytes in the full hash certificate), and may generate a shortened hash of the signing certificate of a second service (e.g., the last three or four bytes in the full hash certificate). In some embodiments, a receiving network node can easily identify the shortened identifier of each service's signing certificate as relating to 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 a threshold radius and / or threshold time period, the V2X node may generate and use a shortened identifier for the data contained in the message for the service.

[0025]

[0035] In some embodiments, a V2X node may intersperse V2X messages containing the full or longer identifier of a service within V2X messages that use a shortened identifier of the service. In this way, the sending V2X node may be locally unique for the signing certificate associated with the V2X node and the service, while periodically including the longer identifier, which is more cryptographically secure. For example, an attacker might log a communication session (i.e., V2X messages related to a service) and replace V2X messages signed by the V2X node's signature with messages signed by the attacker's certificate. The attacker might be able to identify a usable certificate based on the shortened identifier, but it would be impossible to identify a certificate with a longer identifier. In this way, interspersing V2X messages containing the longer identifier of a service can increase the security of V2X communication.

[0026]

[0036] In some embodiments, the first V2X message may be a basic safety message. In some embodiments, the second V2X message may relate to another service. For example, the second V2X message may be a toll message (for example, for a toll collection or toll collection system), a parking access message (for example, for a parking payment system), a road condition message (for example, a message to another vehicle, RSU, or network node about traffic, observed vehicle behavior, road damage, dangerous road conditions such as ice or flood), a geonetworking message (for example, for use in a geonetworking message or messaging system), an emergency responder message (for example, police, fire, paramedics, or other emergency responder systems), or another appropriate message or messaging system.

[0027]

[0037] In various embodiments, a network node may receive a first V2X message from a V2X node relating to a first service and containing an identifier for a second service, and may receive a second V2X message from a V2X node relating to a second service and containing an identifier for the first service. In some embodiments, the network node may generate relationships between the V2X node, the first service, and the second service, enabling the network node to use the information from the first V2X message together with the second service. In some embodiments, the network node may use the information from the first V2X message together with the second service. In some embodiments, the network node may obtain information about the V2X node from the first V2X message and use the information about the V2X node obtained from the first V2X message to perform actions for the V2X node relating to the second service.

[0028]

[0038] In some embodiments, a 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 and second V2X messages were received within the threshold period, the network node can use the information from the first V2X message in conjunction with the second service. In this way, the network node can improve the security of the relationship between the V2X messages of the first service and the V2X messages of the second service, and avoid using data that may no longer be accurate (e.g., the location of a moving vehicle).

[0029]

[0039] Thus, various embodiments include methods, V2X processing devices, and network elements configured to perform methods for communicating V2X information in V2X messages in order to improve efficiency and reduce the processing and communication link overhead required to handle such V2X messages.

[0030]

[0040] For ease of reference, some of the embodiments described herein relate to vehicles using Vehicle-to-Everything (V2X) systems and protocols. However, it should be understood that the various embodiments encompass one or all of the V2X or vehicle-based communication standards, messages, or technologies. Therefore, unless expressly stated so in the claims, nothing in this application should be construed as limiting the claims to V2X systems, basic safety messages (BSMs), or V2X messages. In addition, embodiments described herein may refer to V2X processing systems within a vehicle. Other embodiments are contemplated in which the V2X processing system operates in or is included in mobile devices, mobile computers, roadside units (RSUs), and other devices equipped to monitor road and vehicle conditions and participate in V2X communication.

[0031]

[0041] Figure 1A is a system block diagram illustrating an exemplary V2X system 100 suitable for implementing various embodiments. Figure 1B is a conceptual diagram illustrating an exemplary V2X communication protocol stack 150 suitable for implementing various embodiments. Referring to Figures 1A and 1B, each vehicle 12, 14, and 16 respectively includes V2X onboard equipment 102, 104, and 106 configured to send and receive V2X messages, including periodically broadcasting basic safety messages 112, 114, and 116 for reception and processing by onboard equipment in other vehicles (e.g., 102, 104, and 106).

[0032]

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

[0033]

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

[0034]

[0044] Figure 2 is a component diagram of an exemplary vehicle system 200 suitable for implementing various embodiments. Referring to Figure 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 can communicate with various systems and devices such as an on-board 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, a roadside unit 222, a base station 224, and other external devices. The vehicle processing system 204 may be configured to perform operations for authenticating plaintext and ciphertext, as will be further described 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-temporary storage medium) and may consist of processor-executable instructions stored in the memory 206 to perform operations of the methods according to the various embodiments described herein. The processor 205 may also be coupled to an output module 208 which may control an in-vehicle display and an input module 207 for receiving information from vehicle sensors and 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 can detect malfunction conditions in the vehicle's systems, such as one of the multiple sources 210-218, an application or service running on the V2X processing device 202, or another system in the vehicle.

[0037]

[0047] Examples of in-vehicle networks include Controller Area Networks (CAN), Local Interconnection 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, radar, lidar, ultrasonic sensors, infrared sensors, and other appropriate sensor devices and systems. Examples of vehicle actuators include various physical control systems for steering, braking, engine operation, lights, direction signals, and more.

[0038]

[0048] Figure 3A is a conceptual diagram illustrating an example of a V2X message 300 suitable for implementing various embodiments. Figure 3B is a conceptual diagram illustrating an exemplary message flow 350 suitable for implementing various embodiments. Referring to Figure 1-3B, the V2X message 300 and message flow 350 may be implemented by the vehicle processing system (e.g., 204) of a V2X node (e.g., vehicles 12, 14, 16, 220) and the processors of network nodes (e.g., another vehicle among vehicles 12, 14, 16, 202, RSU 132, network elements 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 relating 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 for 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 security message.

[0040]

[0050] The second V2X message 320 may include information such as a payload (e.g., data or information) and / or metadata 322 relating 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 for 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] Referring to Figure 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 the first service and the second service, respectively, may include identifiers for the other service. For example, V2X message 352 for the first service may include a longer identifier for the second service, and V2X message 354 for the second service may include a longer identifier for the first service. Including identifiers for other V2X services in each V2X message may allow a receiving device (e.g., a network node) to associate the two services and / or messages from the two services with the V2X node. In some embodiments, the network node may generate associations between the V2X node, the first service, and the second service. Such associations may allow the network node to use information from the first V2X messages when performing operations for 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 another service. In some embodiments, the identifier of another service may be, or include, the certificate of another service. In some embodiments, the longer identifier may be the full-size hash of the certificate of another service. In some embodiments, the shortened identifier may be the shortened hash of the certificate of another service. In some embodiments, the shortened identifier may contain enough information to uniquely identify the longer identifier. For example, the shortened hash of a certificate may contain enough information (e.g., a sufficiently long string) to uniquely identify the full-length or full-size hash of the certificate.

[0043]

[0053] In some embodiments, a V2X node may intersperse V2X messages containing the full or longer identifier of a service within a V2X message that uses a shortened identifier of the service. For example, V2X messages 360, 362, and 366 may contain the shortened identifier of a first service, and V2X message 364, interspersed between V2X messages 362 and 366, may contain the longer identifier of the first service. In various embodiments, the longer identifier is cryptographically more secure than the shortened identifier. In this way, a V2X node can reduce the overall amount or volume of data transmitted over the V2X node communication link while maintaining a sufficient level of security to deter attackers by periodically including the longer identifier.

[0044]

[0054] Figure 4 is a process flow diagram illustrating method 400, performed by the processor of a V2X node for communicating V2X information to network nodes, according to various embodiments. Referring to Figure 1-4, the operation of method 400 can 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 a first service and including an identifier for a second service. For example, the V2X processing device may transmit a basic safety message including an identifier for a second service. In some embodiments, the second service may include a toll collection service, a parking access service, a road condition monitoring service, a geonetworking service, or an emergency response service. Means for performing the operation of block 402 may include V2X-equipped devices 102, 104, 106, a vehicle processing system 204, a processor 205, a radio module 218, and an antenna 219.

[0046]

[0056] In block 404, the V2X processing device may transmit a second V2X message that includes an identifier for a first service, which is associated with a second service and configured to allow network nodes to use information from the first V2X message in conjunction with the second service. For example, the second V2X message may be a toll message, a parking access message, a road conditions message, a geonetworking message, or an emergency responder message. The second V2X message may include an identifier for the first service (i.e., a basic safety message service). In various embodiments, including the identifier for the second service in the first V2X message and including the identifier for the first service in the second V2X message may allow network nodes to use information from the first V2X message (e.g., a basic safety message) in conjunction with the second service. Means for performing the operation of block 404 may include V2X-equipped devices 102, 104, 106, a vehicle processing system 204, a processor 205, a radio module 218, and an 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. Furthermore, in some embodiments, the V2X processing device may transmit a third V2X message associated with a second service and containing a shortened identifier of the first service.

[0048]

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

[0049]

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

[0050]

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

[0051]

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

[0052]

[0062] Figure 6 is a process flow diagram showing a method 600 performed by a network node's processor to receive V2X information from a V2X node, according to various embodiments. Referring to Figure 1-6, the operation of method 600 may be performed by a processing device (which may be a V2X processing device) within a network node (for example, 12, 14, 16, 132, 134, 136, 220, 222, 224).

[0053]

[0063] In block 602, the processing device may receive a first V2X message from the V2X node, which is associated with a first service and includes an identifier for a second service. Means for performing the operation of block 602 may include V2X-equipped devices 102, 104, 106, a vehicle processing system 204, a processor 205, a radio module 218, and an antenna 219.

[0054]

[0064] In block 604, the processing device may receive a second V2X message from the V2X node, which is associated with a second service and includes an identifier for the first service. Means for performing the operation of block 604 may include V2X-equipped devices 102, 104, 106, a vehicle processing system 204, a processor 205, a radio module 218, and an antenna 219.

[0055]

[0065] In block 606, the processing device may use information from the first V2X message in conjunction with the second service. In some embodiments, the processing device may obtain information about the V2X node from the first V2X message and use the information about the V2X node obtained from the first V2X message to perform actions for the V2X node related to the second service. In some embodiments, the processing device may generate relationships between the V2X node, the first service, and the second service, enabling the network node to use information from the first V2X message in conjunction with the second service. Means for performing the actions in block 602 may include V2X-equipped devices 102, 104, 106 and the vehicle processing system 204.

[0056]

[0066] Figure 7 is a process flow diagram illustrating an operation 700 that may be performed by the 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 Figure 1-7, the operation of operation 700 may be performed by a processing device (which may be a V2X processing device) within a network node (for example, 12, 14, 16, 132, 134, 136, 220, 222, 224).

[0057]

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

[0058]

[0068] In response to the determination that the first and second V2X messages were not received within a threshold time period (i.e., determination block 710 = "No"), the processing device in block 712 does not use the information from the V2X messages with the second service. In some embodiments, the processor may stop generating the relationships between the V2X node, the first service, and the second service in response to the determination that the first and second V2X messages were not received within a threshold time period. Means for performing the operation of determination block 712 may include V2X-equipped devices 102, 104, 106, a vehicle processing system 204, and a processor 205.

[0059]

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

[0060]

[0070] Figure 8 is a conceptual block diagram illustrating an exemplary mobile computing device 800 suitable for use with various embodiments. Referring to Figures 1-8, various embodiments may be implemented in a wide variety of computing systems, including onboard equipment and mobile computing devices including the exemplary mobile computing device 800. The mobile computing device 800 may include a processor 802 coupled to a touchscreen controller 804 and internal memory 806. The processor 802 may be one or more multicore 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 insecure and / or unencrypted memory, or any combination thereof. Examples of memory types that can 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 the touchscreen panel 812, such as a resistive touchscreen, a capacitive touchscreen, an infrared touchscreen, etc. In addition, the display of the mobile computing device 800 does not need to have touchscreen capabilities.

[0061]

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

[0062]

[0072] The mobile computing device 800 may include a peripheral device connectivity interface 818 coupled to the processor 802. The peripheral device connectivity interface 818 may be configured on its own to accept one type of connectivity, or it may be configured to accept various types of common or proprietary physical and communication connectivity, such as Universal Serial Bus (USB), FireWire, Thunderbolt, or PCIe. The peripheral device connectivity interface 818 may also be coupled to a similarly configured peripheral device connectivity 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 made of 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 the dashboard console of a vehicle in an embodiment in which it is mounted. The mobile computing device 800 may also include a power supply 822 coupled to the processor 802, such as a disposable battery or a rechargeable battery. The rechargeable battery may also be coupled to a peripheral device connection port for receiving charging current from a power supply outside 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] Figure 9 is a conceptual block diagram illustrating an exemplary mobile computing device 900 suitable for use with various embodiments. Referring to Figures 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 touch surface 917 of a touchpad that acts as a pointing device for the computer and may thus receive drag, scroll, and flick gestures similar to those performed on computing devices equipped with touchscreen displays as described above. The mobile computing device 900 typically includes a processor 902 coupled to volatile memory 912 and large-capacity non-volatile memory such as a disk drive 913 of flash memory. Additionally, the mobile computing device 900 may have one or more antennas 908 and / or a cellular telephone transceiver 916 coupled to the processor 902 for transmitting and receiving electromagnetic radiation 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 the computing device may include, as is well known, a computer mouse or trackball coupled to the processor (e.g., via a USB input), which may also be used in conjunction with various embodiments.

[0065]

[0075] Examples are described in the following paragraphs. Some of the following examples describe exemplary methods, but further exemplary implementations may include exemplary methods described in the following paragraphs implemented by a V2X processing device, which may be a computing device including a processor configured to perform the operations of the methods of the following embodiments by onboard equipment, mobile device units, mobile computing units, or fixed roadside units), network nodes, or processor-executable instructions; exemplary 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 embodiments; and exemplary methods described in the following paragraphs which may be implemented by a non-temporary processor-readable storage medium storing processor-executable instructions configured to cause the processor of the V2X processing device, a network processing device, or a network computing node processing device to perform the operations of the methods of the following embodiments.

[0066]

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

[0067]

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

[0068]

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

[0069]

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

[0070]

[0080] [Example 5] The method of any of Examples 2-4, further comprising sending a third V2X message associated with a second service and containing a shortened identifier of the first service.

[0071]

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

[0072]

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

[0073]

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

[0074]

[0084] [Example 9] The method of Example 8, which involves generating a relationship between a V2X node, a first service, and a second service that enables a network node to use information from a first V2X message with a second service.

[0075]

[0085] [Example 10] Using information from a first V2X message in conjunction with a second service is the method of either Example 8 or 9, which includes obtaining information about a V2X node from the first V2X message and using the information about the V2X node obtained from the first V2X message to perform an action for the V2X node associated with the second service.

[0076]

[0086] [Example 11] Using information from a first V2X message with a second service is the method of any of Examples 8-10, which includes determining whether the first V2X message and the second V2X message were received within a threshold period, and, in response to the determination that the first V2X message and the second V2X message were received within a threshold period, using information from the first V2X message with the second service.

[0077]

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

[0078]

[0088] [Example 13] The method in any of Examples 8-12, wherein the second V2X message is one of the following: a toll message, a parking access message, a road condition message, a geonetworking message, or an emergency message.

[0079]

[0089] The above-described method 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 those skilled in the art, the order of operations in the above-described embodiments may be performed in any order. Terms such as “t hereafter,” “then,” and “next” are not intended to limit the order of operations, and these terms are used merely to guide the reader through the description of the method. Furthermore, any reference to a singular claim element using, for example, the articles “a,” “an,” or “the” should not be interpreted as limiting that element to the singular form.

[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 hardware and software compatibility, various exemplary components, blocks, modules, circuits, and operations have generally been described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. While an expert may implement the described functionality in a way that varies for each specific application, such a decision on implementation should not be construed as a departure from the claims.

[0081]

[0091] The hardware used to implement the various exemplary logics, logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or run by 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. The general-purpose processor may be a microprocessor, but alternatively, this processor may be any conventional processor, controller, microcontroller, or state machine. The 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 working with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuits 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 codes on a non-temporary computer-readable medium or a non-temporary processor-readable medium. The operation of the methods or algorithms disclosed herein may be embodied in a processor-executable software module which may reside on a non-temporary computer-readable storage medium or a processor-readable storage medium. The non-temporary computer-readable or processor-readable storage medium may be any storage medium which may be accessed by a computer or processor. Such non-temporary computer-readable or processor-readable medium may include, but are not limited to, RAM, ROM, EEPROM®, FLASH® memory, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium which may be used to store desired program code in the form of instructions or data structures and which may be accessed by a computer. As used herein, disks and discs include compact discs (CDs), laserdiscs (registered trademarks), optical discs, digital multipurpose discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, and discs optically reproduce data using a laser. The above combinations also fall within the scope of non-temporary computer-readable media and processor-readable media. Additionally, the operation of a method or algorithm may exist as one or any combination or set of code and / or instructions on non-temporary processor-readable media and / or computer-readable media that can 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 manufacture or use the claims. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles set forth herein can be applied to other embodiments without departing from the claims. Accordingly, the present invention is not intended to be limited to the embodiments shown herein, but should be limited to the following claims and the broadest scope that corresponds to the principles and novel features disclosed herein. The invention described in the original claims of this application is listed below. [C1] A method executed by the processor of a V2X node for communicating vehicle-to-everything (V2X) information to a network node, Sending a first V2X message associated with the first service and containing the identifier of the second service, A method comprising: sending a second V2X message which includes an identifier for the first service that is associated with the second service and configured to enable the network node to use information from the first V2X message together with the second service. [C2] To generate the identifier of the first service from the signing certificate of the first service associated with the V2X node, To generate the identifier of the second service from the signing certificate of the second service associated with the V2X node, A method of C1 comprising: [C3] Generating the identifier of the first service from the 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 the 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 described in C2. [C4] Generating the identifier of the first service from the 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 the 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 described in C2. [C5] The method of C2, further comprising transmitting a third V2X message associated with the second service and including an abbreviated identifier for the first service. [C6] The method according to C1, wherein the second V2X message is one of the following: a toll message, a parking access message, a road condition message, a geonetworking message, a basic safety message, or an emergency message. [C7] A vehicle-to-everything (V2X) node equipped with a processor, The aforementioned processor, A first V2X message, associated with the first service and containing the identifier of the second service, is sent to the network node. A V2X node comprising a processor-executable instruction to send a second V2X message to the network node, which includes an identifier for the first service, associated with the second service and configured to enable the network node to use information from the first V2X message together with the second service. [C8] The aforementioned processor, The identifier for the first service is generated from the signing certificate of the first service associated with the V2X node. A V2X node as described in C7, further comprising processor-executable instructions to generate the identifier of the second service from the signing certificate of the second service associated with the V2X node. [C9] The aforementioned processor, Generate a hash of the signing certificate of the first service described above, A V2X node as described in C8, further comprising processor-executable instructions to generate a hash of the signing certificate of the second service. [C10] The aforementioned processor, Generate a shortened identifier for the signing certificate of the first service, A V2X node as described in C8, further comprising processor-executable instructions to generate a shortened identifier for the signing certificate of the second service. [C11] The aforementioned processor, A V2X node as described in C8, further comprising a processor-executable instruction to transmit a third V2X message, which is associated with the second service and includes a shortened identifier for the first service. [C12] The aforementioned processor, The V2X node described in C7 is further comprised of processor-executable instructions such that the second V2X message is one of the following: a toll message, a parking access message, a road condition message, a geonetworking message, a basic safety message, or an emergency message. [C13] A vehicle-to-everything (V2X) node, A means for sending a first V2X message to a network node, which is associated with a first service and includes an identifier for a second service, Means for sending a second V2X message to the network node, which includes an identifier for the first service and is associated with the second service, and is configured to enable the network node to use information from the first V2X message together with the second service; A V2X node equipped with these features. [C14] Means for generating the identifier of the first service from the signing certificate of the first service associated with the V2X node, Means for generating the identifier of the second service from the signing certificate of the second service associated with the V2X node, The V2X node described in C13 is further equipped with the features described above. [C15] Means for generating the identifier of the first service from the signing certificate of the first service associated with the V2X node include means for generating a hash of the signing certificate of the first service, Means for generating the identifier of the second service from the signing certificate of the second service associated with the V2X node include means for generating a hash of the signing certificate of the second service. V2X node as described in C14. [C16] Means for generating the identifier of the first service from the signing certificate of the first service associated with the V2X node include means for generating a shortened identifier of the signing certificate of the first service, Means for generating the identifier of the second service from the signing certificate of the second service associated with the V2X node include means for generating a shortened identifier of the signing certificate of the second service, V2X node as described in C14. [C17] The V2X node described in C14, further comprising means for transmitting a third V2X message associated with the second service and including a shortened identifier of the first service. [C18] The second V2X message is one of the following V2X nodes as described in C13: a toll message, a parking access message, a road conditions message, a geonetworking message, a basic safety message, or an emergency message. [C19] A method performed by the processor of a network node to receive vehicle-to-everything (V2X) information from a V2X node, The V2X node receives a first V2X message associated with the first service and containing the identifier of the second service, The V2X node receives a second V2X message associated with the second service and containing the identifier of the first service, The information from the first V2X message is used together with the second service, A method that includes [a certain feature]. [C20] The method according to C19, wherein using information from the first V2X message together with the second service includes generating a relationship between the V2X node, the first service, and the second service that enables the network node to use information from the first V2X message together with the second service. [C21] Using the information from the first V2X message in conjunction with the second service is: The method according to C19, comprising: 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 action for the V2X node related to the second service. [C22] Using the information from the first V2X message in conjunction with the second service is: To determine whether the first V2X message and the second V2X message were received within a threshold time period, In response to the determination that the first V2X message and the second V2X message were received within the threshold time period, the information from the first V2X message is used together with the second service, Methods of C19, including those described above. [C23] The method according to C19, wherein the second V2X message is one of the following: a toll message, a parking access message, a road condition message, a geonetworking message, a basic safety message, or an emergency message. [C24] A network node equipped with a processor, The aforementioned processor, A Vehicle-to-Everything (V2X) node receives a first V2X message associated with a first service and containing the identifier of a second service, The V2X node receives a second V2X message associated with the second service and containing the identifier of the first service, A network node comprising processor-executable instructions to use information from the first V2X message in conjunction with the second service. [C25] The aforementioned processor, The network node described in C24, further comprising processor-executable instructions to generate relationships between the V2X node, the first service, and the second service, enabling the network node to use information from the first V2X message together with the second service. [C26] The aforementioned processor, Information about the V2X node is obtained from the first V2X message. A network node as described in C24, further comprising processor-executable instructions to perform an action for the V2X node related to the second service, using the information about the V2X node obtained from the first V2X message. [C27] The aforementioned processor, Determine whether the first V2X message and the second V2X message were received within a threshold time period. In response to the determination that the first V2X message and the second V2X message were received within the threshold time period, the system further comprises processor-executable instructions to use the information from the first V2X message together with the second service. Network node as described in C24. [C28] The aforementioned processor, A network node as described in C24, further comprising processor-executable instructions such that the second V2X message is one of the following: a toll message, a parking access message, a road condition message, a geonetworking message, a basic safety message, or an emergency message. [C29] Network node, A means for receiving a first V2X message from a vehicle-to-everything (V2X) node, which is associated with a first service and includes an identifier for a second service, Means for receiving a second V2X message from the V2X node, which is associated with the second service and includes an identifier for the first service, Means for using information from the first V2X message together with the second service, A network node equipped with these features. [C30] The network node according to C29, wherein the means for using information from the first V2X message together with the second service includes means for generating relationships between the V2X node, the first service, and the second service, enabling the network node to use information from the first V2X message together with the second service. [C31] Means for using information from the first V2X message in conjunction with the second service are: A means for obtaining information about the V2X node from the first V2X message, Means for performing an operation for the V2X node related to the second service using the information about the V2X node obtained from the first V2X message, Network nodes as described in C29, including those listed. [C32] Means for using information from the first V2X message in conjunction with the second service are: Means for determining whether the first V2X message and the second V2X message were received within a threshold time period, In response to the determination that the first V2X message and the second V2X message were received within the threshold time period, means for using the information from the first V2X message together with the second service, Network nodes as described in C29, including those listed. [C33] The second V2X message is one of the following network nodes as described in C29: a toll message, a parking access message, a road conditions message, a geonetworking message, a basic safety message, or an emergency message.

Claims

1. A method executed by the processor of a V2X node for communicating vehicle-to-everything (V2X) information to a network node, Sending a first V2X message associated with a first service, wherein the first V2X message includes an identifier for a second service different from the first service, and the information in the first V2X message for the first service includes duplicate information that overlaps with the information used for the second service. Sending a second V2X message associated with the second service, wherein the second V2X message includes an identifier for the first service, which does not contain the duplicate information but is configured to allow the network node to use the duplicate information from the first V2X message together with the second service. A method that includes [a certain feature].

2. To generate the identifier of the first service from the signing certificate of the first service associated with the V2X node, To generate the identifier of the second service from the signing certificate of the second service associated with the V2X node, The method according to claim 1, further comprising:

3. Generating the identifier of the first service from the 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 the 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 according to claim 2.

4. Generating the identifier of the first service from the 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 the 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 according to claim 2.

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

6. The method according to claim 1, wherein the second V2X message is one of a toll message, a parking access message, a road condition message, a geonetworking message, a basic safety message, or an emergency message.

7. A method performed by the processor of a network node to receive vehicle-to-everything (V2X) information from a V2X node, Receiving a first V2X message associated with a first service from a V2X node, wherein the first V2X message includes an identifier for a second service different from the first service, and the information in the first V2X message for the first service includes duplicate information that overlaps with the information used for the second service. Receiving a second V2X message associated with the second service from the V2X node, wherein the second V2X message does not include the duplicate information but includes the identifier of the first service. Using the information from the first V2X message together with the second service, A method that includes [a certain feature].

8. The method according to claim 7, wherein using information from the first V2X message together with the second service includes generating a relationship between the V2X node, the first service, and the second service that enables the network node to use information from the first V2X message together with the second service.

9. Using the information from the first V2X message in conjunction with the second service is: Obtaining information about the V2X node from the first V2X message, Using the information about the V2X node obtained from the first V2X message, perform the operation for the V2X node related to the second service, The method according to claim 7, including the method described in claim 7.

10. Using the information from the first V2X message in conjunction with the second service is: To determine whether the first V2X message and the second V2X message were received within a threshold time period, In response to the determination that the first V2X message and the second V2X message were received within the threshold time period, the information from the first V2X message is used together with the second service, The method according to claim 7, including the method described in claim 7.

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

12. A vehicle-to-everything (V2X) node, Means for transmitting a first V2X message associated with a first service to a network node, wherein the first V2X message includes an identifier for a second service different from the first service, and the information in the first V2X message for the first service includes duplicate information that overlaps with information used for the second service. Means for transmitting a second V2X message associated with the second service to the network node, wherein the second V2X message includes an identifier for the first service, which does not contain the duplicate information but is configured to allow the network node to use the duplicate information from the first V2X message together with the second service. Equipped with, V2X node.

13. A vehicle-to-everything (V2X) node according to claim 12, further comprising means for carrying out the method described in any one of claims 2 to 6.

14. Network node, Means for receiving a first V2X message associated with a first service from a vehicle-to-everything (V2X) node, wherein the first V2X message includes an identifier for a second service different from the first service, and the information in the first V2X message for the first service includes duplicate information that overlaps with information used for the second service. Means for receiving a second V2X message associated with the second service from the V2X node, wherein the second V2X message does not include the duplicate information but includes an identifier for the first service. Means for using information from the first V2X message together with the second service, A network node equipped with these features.

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

Images