Communication system and method for supporting multiple V2X RATs
By introducing a multi-mode V2X RAT communication system into vehicles of intelligent transportation systems, the problem of incompatibility of different vehicle standards is solved, multiple RAT communication interoperability in the same row group is realized, and the efficiency and safety of the intelligent transportation system are improved. .
Patent Information
- Application Number
- CN202010403908.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-11
- Filing Date
- 2020-05-13
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-05-13
AI Technical Summary
Due to the incompatibility of standards, different vehicles cannot communicate effectively in the same row, limiting the efficiency and safety of the intelligent transportation system, and the compatibility issues between old vehicles and new vehicles have increased management and control. complexity.
By introducing a multi-mode V2X RAT communication system in the vehicle, multiple wireless communication technologies (such as LTE R14 and LTE R15) can be used for message conversion and intercommunication, ensuring that different vehicles can communicate in the same row even if they use incompatible RATs. .
It realizes wireless communication interoperability between different vehicles, expands the range of collaboration and perceived message transmission of intelligent systems, improves the efficiency and security of intelligent transportation systems, and reduces the risk of technology lock-in for operators and manufacturers.
Smart Images

Figure CN112073935B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to wireless communications, and in particular to a system for providing interoperability between different Vehicle-to-Everything (V2X) wireless communication systems. Background Art
[0002] "Smart" control systems, such as intelligent transport systems, rely on wireless communication between entities (e.g., ground or air vehicles, which may or may not be autonomously or semi-autonomously controlled) to share relevant sensor and other data and to communicate configuration and control messages, among other things. However, there are several possible standards for wireless communication for these purposes, and these standards, as well as the underlying technologies, are constantly evolving. This presents a challenge for operators and manufacturers of equipment, such as vehicles used in intelligent transport systems, to ensure that new equipment continues to be compatible with older equipment. BRIEF DESCRIPTION OF THE DRAWINGS
[0003] In the accompanying drawings, embodiments of the invention are shown by way of example only.
[0004] Figure 1 is an example network topology depicting a system for use by a platooning application or other V2X application;
[0005] Figure 2 yes Figure 1 Variations of the example topology;
[0006] Figure 3 is shown for the Figure 1 and Figure 2 A schematic diagram of a fixed computing system used in the system;
[0007] Figure 4 is a schematic diagram of select components of a V2X-enabled vehicle;
[0008] Figure 5 is a schematic diagram of selected components of an intercommunication unit such as a vehicle;
[0009] Figure 6 is a message transmission diagram illustrating the announcement of an interworking function;
[0010] Figure 7 is a message transmission diagram illustrating formation and configuration of a platoon;
[0011] Figure 8 yes Figure 2 A diagram of the rows in the system;
[0012] Figure 9 is a message transmission diagram illustrating formation or expansion of a platoon;
[0013] Figure 10is a message transmission diagram illustrating the use of intercommunication vehicles to extend a platoon;
[0014] Figure 11 yes Figure 2 A diagram of another bank group in the system;
[0015] Figure 12 is a message transmission diagram illustrating a measurement reporting function of an intercommunication vehicle; and
[0016] Figure 13 is a message transmission diagram illustrating a process for intercommunication of vehicles leaving a platoon. DETAILED DESCRIPTION
[0017] To improve efficiency and safety, intelligent transportation systems, including autonomous and semi-autonomous vehicles, are being developed. Sensor systems (e.g., radar, lidar, sonar, global positioning systems (GPS), etc.) and intelligent measures are being added to vehicles and even to roadside units (RSUs) (e.g., traffic light controllers) to enable vehicles to detect and react to surrounding vehicles, obstacles, and pedestrians while minimizing reliance on human input.
[0018] To facilitate the development of these intelligent systems, communication is required between vehicles and between vehicles and other entities: vehicle-to-vehicle (commonly referred to as V2V), vehicle-to-infrastructure (V2I) (such as roadside units), vehicle-to-pedestrian (V2P), vehicle-to-electronics (V2D), and, particularly in the case of electric or hybrid vehicles, vehicle-to-grid (V2G). Collectively, communication between a vehicle and another entity is referred to as vehicle-to-everything (V2X).
[0019] However, the competing development of V2X architectures and standards (which don't necessarily all use the same wireless communication and transmission protocols) and ongoing technological advancements present challenges for automakers and operators looking to adopt intelligent systems. Consider the example of vehicle platooning or grouping. Platooning groups or links multiple vehicles together that can communicate with each other to form a physical convoy that can, for example, synchronize speed, acceleration, and braking to keep vehicles traveling closer together, or travel at a constant speed. In some implementations, a vehicle in the convoy (e.g., the lead vehicle in a platoon), or a remote vehicle, server, or system not part of the platoon, can control the platoon's vehicles; alternatively, some or all vehicles in the platoon can be controlled autonomously. Platooning can provide efficiencies in the form of improved fuel efficiency and reduced emissions (e.g., because less braking is required), safety (because speed and spacing between vehicles are controlled), and more efficient road use. Of course, if there are humans in the platoon, reducing reliance on human input when driving the vehicle can allow the human to engage in tasks other than driving, reducing fatigue, or enabling longer, continuous journeys.
[0020] In order for a vehicle to be part of a platoon in an intelligent transport system, it needs to be able to communicate with the other members of its platoon to support the collaborative behaviors required of the platoon members. With current technology, this means that all vehicles in the platoon must support a common V2X radio access technology (V2X RAT). However, there are various different V2X architectures and standards, including but not limited to the European Telecommunications Standards Institute (ETSI) Intelligent Transport Systems (ETSI ITS), the Society of Automotive Engineers (SAE) International Dedicated Short Range Communications for Radio Access in a Vehicular Environment (SAE DSRC), and the SAE International Cellular V2X (SAE C-V2X). Cellular-based V2X (C-V2X) technology relies on one or both of fourth-generation cellular / long-term evolution (4G / LTE, also known as Enhanced Universal Mobile Telephone System Terrestrial Radio Access Network (E-UTRAN)) and fifth-generation cellular new radio (5GNR) wireless broadband technologies, while non-cellular V2X technologies (such as ETSI ITS and SAE DSRC) are based on wireless local area networks (WLANs) that rely on one or more of the IEEE 1609, IEEE 802.11bd, and IEEE 802.11p standards. Even V2X architectures that rely on the same physical communication technology may be incompatible because they may use different feature sets, transmission protocols, message transmission formats, and / or applications. For example, ETSI message transmission formats include the Collaborative Awareness Message (CAM) defined in ETSI EN 302 637-2 and the Decentralized Environmental Notification (DENM) defined in ETSI EN 302 637-3. Examples of SAE messaging include the Basic Safety Message (BSM) and the Common Safety Request (CSR), as defined in SAE J2735. These are just a few examples; other types of V2X message transmissions may be used in various V2X systems. Current V2X architectures and standards, as well as associated applications (such as platooning), will be known to those skilled in the art. Therefore, when reference is made herein to different or distinct V2X RATs, these different V2X RATs may include the same standard with different feature sets.
[0021] Currently, it's not always feasible for all vehicles to support a common V2X RAT, either due to cost or because, as standards are phased out and updated, newer vehicles may be equipped with newer generations of technology while older vehicles haven't yet been retired. As a result, vehicles with incompatible V2X RATs may not be able to join a single platoon together, limiting a given vehicle's ability to join the platoons available at a given time and location. The size of a platoon that can be formed using a common V2X RAT may be limited because some otherwise available vehicles must be excluded; this can reduce the overall efficiency of vehicle operation, as some of the benefits of platooning (e.g., fuel efficiency, safety) may be reduced. Additionally, multiple platoons may need to be created to accommodate different V2X RATs, increasing the computational burden on the entities that manage and control the platoons. Furthermore, technical incompatibilities may result in a first vehicle or platoon employing one V2X RAT being unaware of another vehicle employing an incompatible second V2X RAT.
[0022] The requirement that all vehicles in a platoon share a common V2X RAT could result in technology “lock-in” for certain operators or manufacturers, where older V2X technologies are installed in newer vehicles to ensure compatibility with existing vehicles because the cost of replacing the entire fleet is deemed too high. This could slow the adoption of new or competing V2X technologies, which may still be superior to older technologies.
[0023] Therefore, the following examples provide a communication system and method that provides interworking functionality between different entities (e.g., grouped entities) to extend communication from a first RAT to a second RAT and optionally to additional RATs. In the case of an intelligent system that includes groups of autonomous, autonomous, or semi-autonomous entities, the interworking functionality can enable the intelligent system to establish larger fleets or groups of entities that can communicate with each other even if they do not all use the same RAT. This can be used to expand the scope of collaboration and awareness messaging between entities in the intelligent system.
[0024] These concepts refer to Figure 1 To illustrate this, we use the example system described in Figure 1 Schematically depicted are scenarios in which one or more platoons of vehicles may be configured and controlled. Figure 1Several types of entities are depicted: operational entities 170A and 170B; management entities 120, 130; and a server system 150, which can be used to control one or more platoons or management entities 120, 130. In this example, operational entities 170A, 170B are various types of ground vehicles, such as cars, trucks / vans, and semi-autonomous trucks / vans; however, operational entities are not necessarily limited to this, nor do they all need to be of the same type. For example, operational entities can be or can include aerial vehicles, manufacturing machinery or other equipment, mobile machines, or vehicles. Operational entities can be directly controllable by humans (e.g., occupied and driven by humans in the case of ground transportation vehicles) or remotely controllable by humans, or can be controlled by fully autonomous or semi-autonomous systems. In the case of a platoon of ground vehicles, a typical arrangement can have a human-controlled or semi-autonomous lead vehicle, accompanied by a collection of one or more autonomous or semi-autonomous follower vehicles.
[0025] In this example, the operational entities 170A, 170B are each equipped with a communication system, as generally described below, that enables wireless communication using at least one RAT. For example, the operational entity 170A may be provided with a communication system that enables them to communicate using a first RAT, while the operational entity 170B may be provided with a communication system that enables them to communicate using a second RAT. It should be understood that the number of entities 170A, 170B is not limited to the concepts described herein.
[0026] The first RAT and the second RAT may differ due to incompatibilities. For example, the first RAT and the second RAT may employ different wireless communication technologies that the operating entities 170B and 170A are not equipped with (e.g., LTE or other cellular communications instead of wireless local area network (WLAN) communications); or, even if the RATs employ the same wireless communication technology, incompatibilities may exist due to the use of different wireless access standards (e.g., ETSI ITS versus SAE DSRC in the context of V2X communications); or, even when the same technology and standards are employed, the versions of the first RAT and the second RAT may be different, resulting in certain incompatibilities or discontinuities in message transmission or applications. Such incompatibilities may prevent the operating entity 170A from communicating with the operating entity 170B or with the wireless infrastructure supporting the operating entity 170B, or vice versa. Therefore, as in Figure 1 As shown by the arrow in FIG, the operation entity 170A may be able to directly or via a wireless infrastructure (in Figure 1170B).
[0027] An additional entity, referred to as an interworking unit 190, is provided with a communication system that enables wireless communications using more than one RAT, which may include using a single RAT with different versions. As an example, the communication system may be able to use LTE Release 14 (LTE R14) and LTE Release 15 (LTE R15) as a first V2X RAT and a second V2X RAT. These two versions of the same RAT have incompatibilities for V2X operations and require special handling as described in 3GPP TS 36.331. Figure 1 In the example of FIG, the interworking unit 190 is depicted as a fixed system capable of communicating with the respective wireless infrastructures 160A, 160B and, through the infrastructure, with the operating entities 170A, 170B. As described below, the interworking unit 190 can receive messages transmitted using a first RAT from one or more operating entities 170A and convert (e.g., by reformatting) the messages to make them compatible with a second RAT (or convert the messages from one version or release of a single RAT to an alternative version or release, e.g., from LTE R15 to LTE R14) for transmission to the one or more operating entities 170B. The interworking unit 190 thus provides interworking functionality that enables the operating entities and other entities in the system to access multiple RATs simultaneously.
[0028] In the specific example embodiments described below, the operational entities 170A, 170B are depicted as ground vehicles capable of performing platoon applications; therefore, for the purposes of describing these embodiments, it is assumed that Figure 1Entities are platoon entities because they may be included in or associated with a platoon. It is also assumed that the operating entities 170A and 170B are ground vehicles and the RAT employed is a V2X RAT, and they will generally be referred to as such in the following examples. The V2X RAT can be selected from currently available or future available V2X systems, such as, but not limited to, ETSI ITS, SAE DSRC, and SAE C-V2X. Therefore, those skilled in the art will understand the configuration and management of platoons, including message transmission protocols.
[0029] In this case, the platoon can be controlled by a platoon management entity (PME), which determines platoon control and management messages and transmits them to other entities within and outside the managed platoon. The PMEs depicted in the figure are external computing systems 120, 130 that communicate with their respective wireless infrastructures, schematically represented as 160A, 160B, via a public or private wide area network 100 (it should be understood that other network entities, such as gateway systems, have been omitted for ease of illustration). The PMEs can be individual computing systems, such as 120, 130, or can reside in a collection of network servers (e.g., cloud services), such as service 150. In some V2X implementations, the PMEs can be included in or co-located with the RSUs. In this example topology, the PMEs 120, 130 communicate with an interworking unit 190 via the network 100. Of course, it should be understood that appropriate encryption and authentication protocols can be used in communications between any entities in the system to ensure safety and security. Furthermore, in addition to being equipped for V2V communication, some vehicles 170A, 170B may also be able to communicate with a server system such as 150 via the network 100, for example via a cellular radio network (e.g., a 4G / LTE network or a 5GNR network) or via a WLAN (e.g., an IEEE 802.11p / 802.11bd network).
[0030] Those skilled in the art will appreciate that the PME may instead reside in a vehicle of the platoon (e.g., the lead vehicle or intercommunication unit 190). In the figures, the PME is depicted as a separate unit, but it should be understood that if the PME resides in a vehicle of the platoon or in the intercommunication unit 190, communication between the PME and that vehicle or between the PME and the intercommunication unit may not be necessary and may be omitted from the examples discussed below. In other words, for example, in the message transmission diagrams discussed below, communication between PME 120 and intercommunication unit 190 should not be interpreted as limiting communication to non-vehicle PMEs, even if so depicted. Communication between PME 120 and intercommunication unit 190 may represent communication between the lead vehicle of the platoon (e.g., vehicle 170A) in which the PME resides and intercommunication unit 190, even if not explicitly depicted as a vehicle. Modifications to the concepts described below will be within the capabilities of those skilled in the art.
[0031] Furthermore, in the context of V2X communication, the interworking unit 190 may reside in the vehicle rather than a fixed component. Figure 2 Shown Figure 1 A variation of the system in which an interworking unit 190 is included in a vehicle, which is thus able to communicate with the vehicles 170A and 170B and with their respective wireless infrastructures 170A, 170B using their respective V2X RATs. The interworking unit 190 may thus be in direct contact with the PME and may exchange messages with the PME directly (e.g., where the PME resides in a vehicle, such as the lead vehicle in the set of vehicles 170A) and / or in indirect contact with the PME (e.g., where the PME resides in a vehicle, but obstacles or interference prevent direct communication between the PME and the interworking unit; or where the PME resides in a fixed assembly). Figure 2 Not all possible communication paths (vehicle-to-vehicle or vehicle-to-infrastructure) are shown. As another example, the interworking unit 190 may be included in or co-located with the RSU. Again, the examples discussed below should not be considered limiting, even in cases where the interworking unit 190 is depicted as separate from other vehicles. For example, communications between the PME 120 and the interworking unit 190 may include vehicle-to-vehicle communications, even if not depicted as such.
[0032] Figure 3is a schematic diagram of selected functional components of an example PME 120, whether it resides in a stationary computing system or in a vehicle. The PME 120 is a data processing system that includes one or more microprocessors, as shown as a processing unit 210; volatile (RAM / working memory) 220 and non-volatile (NV) memory 230; and various input / output (I / O) subsystems 240, including human-machine interfaces (e.g., display screen, touch screen, keyboard, pointing device, etc.). These human-machine interfaces may be optional, as they may be connected to the system via short-range communications (e.g., Bluetooth) via a communication interface 260. TM , Near Field Communication, ZigBee TM , IEEE 802.15, Ethernet, WLAN, etc.) to remotely access the PME 120. The PME 120 is also provided with at least one V2XRAT interface 250 (which may include a transceiver, digital signal processing and control circuitry) and, if the PME 120 is capable of wireless communication, such as in the case where it resides in a vehicle, a V2XRAT interface 250 is also provided. Figure 3 Alternatively, the PME 120 may use another communication interface 260 to receive and transmit V2X messages through a gateway not shown. The PME 120 may also communicate with external systems such as cloud-based server systems and RSUs via other communication interfaces 260. Those skilled in the art will appreciate that Figure 3 The components shown represent only certain aspects of PME 120 , and other components typically included in such systems, such as power supplies, buses, and other components, have been omitted from the drawings and description for the sake of brevity only.
[0033] Figure 4is a schematic diagram of an onboard communication system 300, including a communication system for a V2X-enabled vehicle such as vehicles 170A and 170B. The onboard system can be built into an onboard unit in the vehicle that interfaces with other control and monitoring circuit systems of the vehicle. One or more microprocessors (processing unit 302) control the operation of system 300. Data can be stored in volatile memory 312 or non-volatile (NV) memory 310. System 300 executes an operating system and various applications (not shown) as needed, such as platooning applications for participating in a platoon with other vehicles, and / or autonomous or semi-autonomous driving. Processor unit 302 interfaces with typical elements of a transportation vehicle, such as an interior touchscreen display 314 and audio system 316, external warning systems 318, and signal features (e.g., hazard lights, headlights, sirens, horns). Processor unit 302 may also be provided in a typical vehicle with interfaces to one or more of the various electronic control units 320 to control various functions, such as the transmission, cruise control, braking system, temperature sensors, environmental controls (e.g., heating, cooling), collision avoidance, power windows, etc. Processing unit 302 may be configured to acquire sensor and status data, such as speed, acceleration, engine temperature, etc., from one or more of these control units. This data may be transmitted to PME 120 or other supervisory entities, or used by autonomous or semi-autonomous applications executed by system 300 to control the vehicle. Similarly, the processing unit may also interface with a power switch 306 that controls power supply 304 and the vehicle ignition 308. The status of these components may also be collected by processing unit 302. The processing unit in the vehicle includes interfaces for various sensors and monitoring systems in the vehicle, including radar, sonar, and / or lidar systems 322; a GPS receiver 324; and a V2X RAT communication subsystem 326, all of which are configured to operate according to a given V2X RAT technology and version (e.g., ETSI ITS). The system 300 may also be provided with other wired or wireless data interfaces 328 (e.g., a Universal Serial Bus (USB) port, a WLAN communication subsystem). The wireless communication subsystem is of course provided with an antenna 330, and any required transceiver, digital signal processor (DSP), and control circuitry.
[0034] Figure 5 The example also contemplates that the system 350 is built into the vehicle and includes the following components: Figure 4Interworking system 350 incorporates many of the same features as system 300. However, rather than including a single-mode V2X RAT subsystem, interworking system 350 includes a multi-mode V2X RAT subsystem 340 capable of transmitting and receiving messages compatible with multiple (at least two) V2X RATs. Depending on the implemented RATs, subsystem 340 may be provided with multiple antennas 330, transceivers, DSPs, and control circuitry as needed; however, in some implementations, using the same physical communication protocol, duplication of these components may not be necessary. In this example, the multi-mode V2X RAT subsystem implements both the SAE DSRC 360 and ETSI ITS 370 protocol stacks. Upon receiving a message compliant with a first V2X RAT, multi-mode subsystem 340 decodes the message and determines its processing. For example, if the message is addressed to interworking unit 190 (e.g., a command to start interworking or an invitation to join a platoon), subsystem 340 may pass the message to processing unit 302 for processing and execution. On the other hand, if the message is a broadcast message or is addressed to another vehicle using a different RAT, subsystem 340 may extract the message according to the other RAT and repackage it (e.g., by reformatting the message or content values) and transmit the reformatted message for receipt by the intended destination.
[0035] The V2X RAT subsystem 340 may implement interworking functionality with or without the processing unit 302. In some examples, the V2X RAT subsystem 340 may be included in a system-on-chip that has sufficient processing power to implement interworking functionality without relying on the processing unit 302. Additionally, it should be noted that although the communication systems 300, 350 are depicted as onboard units installed in a vehicle that includes other features, the communication systems 300, 350 may be provided as separate components from the processor unit 302, the radar / sonar / lidar interface 322, and the like. For example, an interworking communication system consisting of a multimode V2X RAT subsystem with a dedicated processor may be provided as a plug-in component or card to be installed in a vehicle that is already equipped with a processor. Figure 5 Additionally, an interoperable communication system, with or without additional components, may be provided in a portable wireless device capable of interfacing with various onboard vehicle sensors and control systems.
[0036] Figure 6Different examples of interworking unit 190 advertising its interworking capabilities are shown. As a first example, when interworking unit 190 registers itself with a registration database or server system (such as server system 150) by sending a registration message 405 over network 100 using at least one V2X RAT, its capabilities and identification information are included in the indication in its registration information. The identification information may include one or more of the following: a digital certificate, an International Mobile Equipment Identity (IMEI), an IMEI with a software version (IMEI-SV), an International Mobile Subscriber Identity (IMSI), or some other suitable identifier. The interworking capabilities included in the registration message may include an identification of the specific V2X RAT supported by interworking unit 190, and optionally an indication of whether interworking unit 190 is currently providing interworking capabilities and / or its geographic location. If interworking unit 190 is a vehicle currently a member of a platoon, the identification information may also include an identifier for the platoon and, optionally, information regarding the location of interworking unit 190 within the platoon. The identification information for the platoon may be an alphanumeric identifier.
[0037] Alternatively, registration of the intercommunication unit 190 can be triggered by an event, as shown by trigger 400. For example, the intercommunication unit 190 can be triggered to register itself with the server system 150 upon arrival at a predetermined location (e.g., a embarkation station) or when a vehicle including the intercommunication unit 190 is ready to join a platoon. For example, sensors in a transport vehicle can detect when a container has been attached or when a fuel tank has been filled. This event can trigger the intercommunication unit 190 to register with the server system 150. The registering system (e.g., server system 150) can respond with configuration instructions, such as whether the intercommunication unit 190 is to be configured to enable intercommunication functionality.
[0038] Thus, the interworking capability of the interworking unit 190 may be recorded by the server system 150, and a confirmation message 410 may be returned. Subsequently, the PME 120 that is assembling the platoon or currently controlling the platoon may be made aware of the interworking unit 190 by querying 415 the server system 150 for nearby or available vehicles or interworking units. The response 420 from the server system 150 may include an indication of the availability of the interworking unit 190. Subsequently, the PME 120 may request the interworking unit 190 to provide interworking functionality and / or join the platoon, as described below.
[0039] Alternatively or additionally, the interworking unit 190 may advertise its capabilities by transmitting 425 its identification information and indication of the interworking capabilities to a plurality of vehicles 170A, 170B or PMEs 120 within communication range using one or more V2X RATs it supports, for example, in a capability indication message of the interworking capabilities as described above. Typically, such a transmission may or may not receive a response 430, depending on the particular V2X protocol employed; in some cases, a receiving vehicle or PME may transmit a response only if it has determined that it is "interested" in the interworking functionality (e.g., if it is a PME that has determined that it can extend its platoon).
[0040] As another example, in Figure 6 Not shown, the advertisement of the capabilities of the interworking unit 190 may not be transmitted directly by the interworking unit 190. Instead, if the interworking unit 190 has joined the platoon and indicated its interworking capabilities to the PME 120, the PME 120 or another vehicle in the platoon may instead transmit a message to a recipient (either another platoon entity or an entity other than the platoon) to announce the availability of the interworking functionality.
[0041] As described above, the indication sent by the interworking unit 190 can be sent using one or more V2X RATs supported by the interworking unit 190. As an example, existing message transmission protocols (e.g., IEEE 1609.2 message transmission, ETSI BTP / GN message transmission, IEEE 1609 WSA and WSMP message transmission, CAM message transmission, etc.) can be adapted to include relevant data. Tables 1 to 4 below illustrate example modifications that can be made to certain existing protocols to provide an indication of whether the sender of the message currently has active interworking functionality and which V2X technologies are supported. Table 1 illustrates example modifications / updates to the MIB in IEEE 802.11bd for different V2X technologies from a higher-level perspective; Table 2 illustrates example modifications / updates to the MIB in IEEE 802.11bd for different V2X technologies at a lower level (more precisely identifying the V2X message transmission protocol).
[0042]
[0043] Table 1. Example modifications to the MAC and PHY MIBs in IEEE 802.11bd for different V2X technologies.
[0044]
[0045] Table 2. Additional example modifications to the MAC and PHY MIBs in IEEE 802.11bd for different V2X technologies.
[0046] Tables 3 and 4 show example modifications / additions to the ETSI Collaboration Aware Messaging (CAM) listed in Annex A of ETSI EN 302 637-2. Some unchanged content has been edited for brevity. Table 3 lists high-level information, while Table 4 lists more precise details. Also, both include an indication of whether the sender of the message currently has active interworking functionality.
[0047]
[0048]
[0049] Table 3. Example modifications to the ETSI CAM message transmission in ETSI EN 302 637-2 for different V2X technologies.
[0050]
[0051]
[0052]
[0053] Table 4. Additional example modifications to the ETSI CAM message transmission in ETSI EN 302 637-2 for different V2X technologies.
[0054] Table 5 lists example message transmission modifications to IEEE 1609.3 to indicate support for different V2X technologies and whether the sender of the message currently has active interworking capabilities. Table 6 lists the values and descriptions of the "Capability" subfield in Table 5. Tables 7 and 8 list more detailed modifications to IEEE 1609.3, which include more robust details regarding V2X RAT support in the "Capability" subfield.
[0055] WAVE element ID = 9 length ability Information (optional) octet 1 1 2 variable
[0056] Table 5. Example interworking indication modifications for IEEE 1609.3.
[0057]
[0058]
[0059] Table 6. Subfield format for the capability octet of Table 5.
[0060] WAVE element ID = 10 length ability Information (optional) octet 1 1 4 variable
[0061] Table 7. Example interworking indication modifications for IEEE 1609.3.
[0062] Bitmap value describe Bit 0 (MSB) Supports R14 LTE PC5 Bit 1 Supports R15 LTE PC5 Bit 2 Support R16 NR PC5 Bit 3 Support ETS IBT PGN Bit 4 Support IEEE 1609.3 Positions 5-31 reserve
[0063] Table 8. Subfield format for the capability octet of Table 7.
[0064] Tables 9 and 10 list example modifications to the Radio Resource Control (RRC) protocol used over the PC5 interface specified by 3GPP TS 36.331 (Section 6.3.8, Sidelink Information Elements) to indicate which V2X RATs are supported and whether interworking is currently active. Similarly, the second table (Table 10) lists more detailed support information for the interworking functionality.
[0065]
[0066] Table 9. Example modifications to sidechain information in the RRC protocol as defined in 3GPP TS 36.331.
[0067]
[0068]
[0069] Table 10. Example modifications to the side chain information in the RRC protocol as defined in 3GPP TS 36 331.
[0070] Tables 11 and 12 list example modifications to the RRC protocol used over the Uu interface defined in 3GPP TS 36.331 to again indicate which V2X RATs are supported and whether interworking is currently active, with Table 12 listing the support in more detail.
[0071]
[0072]
[0073]
[0074] Table 11. Example modifications to the RRC protocol used over the Uu interface as defined in 3GPP TS 36.331.
[0075]
[0076]
[0077]
[0078] Table 12. Example modifications to the RRC protocol used over the Uu interface as defined in 3GPP TS 36.331.
[0079] Of course, these example modifications are not exhaustive and can be modified in different ways to achieve the same result.
[0080] Having indicated the availability of the interworking unit 190 to the other entities in the system, the next step may be the configuration of a new row. The formation of a row may be automatic ("dynamic row formation"), manual, for example, with human intervention ("static row formation"), or a combination of dynamic and static formation ("semi-static row formation"), ("semi-dynamic row formation"). Figure 7 As in the example of , this can be accomplished using a platoon management entity that can reside in the vehicle, or within a server (e.g., server 120), or in a cloud-based service (e.g., system 150). In this example, PME 120 is shown as a separate entity from the vehicle (e.g., intercommunication unit 190, which can be one or more vehicles 170A), but as described above, Figure 7 The example implementations in are not limiting and may be modified, which would be within the scope of those skilled in the art.
[0081] The PME 120 controls various aspects of the platoon, such as its membership, member status, and configuration, and transmits platoon configuration parameters to all members of the platoon and any other entities or applications used to control or communicate with the platoon. The platoon itself may be composed of vehicles with different parameters and capabilities, which may be determined by the PME. Parameters and capabilities may include vehicle size (e.g., one or more dimensions of the vehicle), destination (e.g., one or more GPS coordinates, one or more predetermined values associated with a specific location, etc.), route waypoints (e.g., one or more GPS coordinates, one or more predetermined values associated with a specific location, etc.), number of antennas, antenna radiation patterns, antenna heights (e.g., in units of measurement (e.g., millimeters)), etc. In these embodiments, the platoon may include vehicles using different communication technologies or feature sets. The PME 120 may use information about the parameters and capabilities of individual vehicles, as well as information about vehicles or other entities capable of acting as interworking units 190, to create a platoon using more than one V2X RAT (e.g., more than one communication protocol or feature set) by relying on the interworking unit 190 to ensure communication between different vehicles with different communication characteristics.
[0082] Figure 7An example interaction in a simple case between a PME 120, a server system 150, an intercommunication unit 190, and vehicles 170A (in this example, a set of vehicles 1…n) communicating using a first V2X RAT is described. As an initial step to create or increase the size of an existing platoon, the PME 120 may transmit an invitation or advertisement 500 to identify itself and its intention to form a platoon and / or increase the size of an existing platoon. The invitation may include information such as the origin, waypoints, and destination points, as well as a departure date / time, and any other information determined to be necessary to allow the receiving vehicles to respond to the advertisement. In this simple example, the advertisement is transmitted only using the first V2X RAT and is therefore received and confirmable by the first group of vehicles (such as vehicle 170A) that are configured to use the same V2X technology. The advertisement message may be sent several times. In more complex examples, such as those discussed below, Figure 9 In some steps, once interworking functionality is available to the PME 120, the PME 120 may initiate transmission of advertisements using one or more V2X RATs. Figure 7 In the example of FIG. 5 , the intercommunication unit 190 (which may be included in a vehicle) and the vehicle 170A receive the advertisement 500 .
[0083] When the vehicle receiving the advertisement is able to join the platoon, the vehicle 190, 170A can then verify the platoon advertisement and / or the identity or location of the PME 120 to ensure that the PME is a valid or authorized PME. This can occur by sending a message to a known server such as the server system 150 and obtaining a response (optional authentication request 505 and response 510).
[0084] If the PME 120 is successfully authenticated, the interested vehicle (including the interworking unit 190) may then transmit a join request message 515, 520, 525 to the PME 120, which utilizes identification information about the interested vehicle and the requesting platoon members to indicate the availability of the interested / sending vehicle to join the platoon, and / or to indicate the capabilities and parameters of the interested vehicle, as described above. This message may be transmitted via other routes through the network 100. The PME 120 may then use the identification information to request authentication information about the requesting vehicle, for example, from the server system 150, before accepting the requesting vehicle into the platoon (optional request 530 and response 535).
[0085] Join requests 515, 520, and 525 may include the vehicle's capabilities and parameters along with the join request; otherwise, the additional information may be sent in a separate message from the join request. Alternatively, PME 120 may obtain this information from a separate source, such as server system 150. Thus, if interworking unit 190 has previously registered with server system 150 as interworking unit 190, PME 120 may receive information about interworking capabilities from system 150. PME 120 uses this information about each vehicle's capabilities and other parameters to determine vehicle membership. For example, it may be desirable to construct a platoon that includes vehicles of a specific size or technological capabilities, and specifically, PME 120 may include interworking unit 190 in the platoon to extend its communication range beyond the single V2X RAT used by vehicle 170A.
[0086] PME 120 then sends an invitation and / or configuration message 540 to the vehicles accepted into the platoon. This message may include common instructions for all accepted vehicles and may be transmitted in a broadcast or multicast format; alternatively, an individual configuration message may be transmitted to each accepted vehicle and may include individual instructions regarding the vehicle's respective configuration and its position within the platoon. Thus, for example, an individual configuration message 540 sent to interworking unit 190 may include instructions to activate the interworking function of interworking unit 190, enabling PME 120 to extend its communication range to vehicles using other technologies. Configuration messages may be transmitted directly between PME 120 and the vehicle; however, in situations where PME 120 is outside the fleet, such as in a remote computing system, configuration information may be propagated within the platoon via transmissions between adjacent vehicles. Direct or multicast messages may be sent using an identifier with specific recipients, while broadcast messages may be intended only for certain recipients but received by more entities. To restrict receipt of information to only platoon members, security measures such as encryption may be used to ensure that the message can only be decrypted and read by the intended recipient.
[0087] Other information included in the message may be information necessary to configure the platoon, including establishing and configuring the members of the platoon, and route information (such as a starting point, waypoints, and destinations), as well as timing including the starting and waypoint target times / dates. Other information in the message may include the platoon identity, one or more identifiers associated with other vehicles in the platoon, the primary V2X RATs supported, an indication of whether an interoperable vehicle 190 is available, and (if an interoperable vehicle 190 is available) one or more identities of the interoperable vehicle 190, its location within the platoon, and other RATs supported. In particular, confirmation of the V2X RAT to be used by the platoon may be useful because it can confirm to vehicles supporting more than one V2X RAT which V2X technology is actually to be used, and to platoon vehicles which protocols are to be used for messaging with entities outside the platoon.
[0088] Configuration message 540 can be considered to be of an invitation or request nature, as those vehicles receiving the configuration message can make a decision to join the platoon after determining that the message is intended for them. If so, the vehicle can then transmit confirmation or acceptance messages 545, 550, 555 to PME 120. Each vehicle that receives and accepts the configuration message will then configure itself accordingly, for example, moving to its designated position in the platoon; in the case of interworking unit 190, it can invoke its interworking function in response to the instruction in configuration message 540 to do so. If the vehicle receiving the configuration message determines that it will not join the platoon, the vehicle receiving the configuration message can send a rejection message to PME 120 (not shown), which may include a reason code for the rejection.
[0089] When all vehicles in the platoon have been configured, or at some predetermined time, or upon a triggering event after configuration, the vehicles will form a platoon. This formation may first begin with some pre-checks, such as the vehicles identifying themselves to each other and their other platoon members, and confirming reliable communication status. Once any pre-checks are completed, the vehicles can then physically arrange themselves so that the lead or primary vehicle is known and can establish itself at the head of the platoon, i.e., the front of the group of vehicles that make up the platoon. If the platoon configuration or some other determination receives or indicates an order, the other vehicles will be arranged in sequence. In the event that any one vehicle has a specific location or position to occupy (for example, an intercommunication vehicle 190 may be required to occupy a specific location to ensure reliable communication throughout the entire platoon), that vehicle will occupy that location in accordance with the actual platoon order. Occupying that location may involve communicating with one or more vehicles already in the formation so that they can communicate in accordance with the PME 120 ( Figure 7 The position requirements for the bank configuration are identified by instructions (not shown).
[0090] The final result of the formation and configuration of the above-mentioned groups can be Figure 8 The result is shown, where a group of vehicles 170A and intercommunication vehicles 190 have formed a platoon (shown as a dashed outline). This example platoon communicates with each other and with the PME 120 using a first V2X RAT.
[0091] Figure 9 Another example of a platoon formation or platoon expansion using an intercommunication unit 190 is depicted. In this example, the PME 120 discovers the availability of an intercommunication vehicle 190. This can generally be done as described with respect to Figure 7 This may occur as described, or alternatively, may occur when the PME 120 queries the server system 150 or other vehicle registration system for information about available vehicles for the platoon or vehicles with specific capabilities (request 600 and response 605). The PME 120 may then instruct the interworking vehicle 190 to provide interworking functionality (request 610). If the interworking unit 190 is available to fulfill the request, the interworking unit 190 may send an acknowledgment confirming the instruction (response 615) or send / transmit a message rejecting the instruction, which may include a reason code for the rejection. Alternatively, the transaction between the PME 120 and the interworking vehicle 190 may be a platoon advertisement and join request, followed by a configuration instruction to begin interworking.
[0092] When interoperable vehicle 190 is operating, PME 120 can transmit a platoon advertisement 625 via interoperable vehicle 190 using multiple V2X RATs. For example, PME 120 can transmit a platoon advertisement 620 in a first V2X RAT between interoperable vehicle 190 and other vehicles using the first V2X RAT. Interoperable vehicle 190 converts the received platoon advertisement 620 to a second V2X RAT format, for example, by extracting information from the message in a first format and reformatting the message in a second format. Additional steps may be required depending on the differences between the two V2X RATs. Interoperable vehicle 190 then transmits the reformatted advertisement message 625 to other vehicles, such as vehicle 170B, that can receive messages using the second V2X RAT. Table 13 lists example modifications (new WSMP frames) to the IEEE 1609.3 platoon advertisement message.
[0093]
[0094] Table 13. Example framework for grouping ads.
[0095] Table 14 lists the new Group Advertisement ANQP element based on IEEE 802.11bd, which can be used to advertise the capabilities of a PME or interworking unit from one 802.11 station to another 802.11 station.
[0096]
[0097] Table 14. Example Group Advertisement ANQP Element Format.
[0098] "Platoon / Interconnected Unit ID" is the identifier of an existing PME or interconnected vehicle. This field also indicates whether the element contains information from a PME or interconnected vehicle. "Vehicle ID List" is a list of identifiers of vehicles belonging to the platoon or interconnected vehicle; however, for privacy reasons, this field may not be used. "Position" is the current location of the PME or interconnected vehicle. This can be an absolute position or a relative position relative to the position of the PME or interconnected vehicle ID. "Info" is an optional field that contains additional information about the platoon / interconnected vehicle, such as safety information.
[0099] The join request 630 from the interested vehicle 170B may be received by the interworking vehicle 190, then converted from the second V2X RAT format to the first V2X RAT format and sent to the PME 120 for processing (join request 635). If the vehicle 170B is accepted, the PME 120 will then transmit configuration information (configuration messages 635, 640) again via the interworking vehicle 190 as described above. As described above, an acceptance message (645, 650) or a rejection message is transmitted back via the interworking vehicle 190, and the rejection message may include a reason code for the rejection.
[0100] Table 15 depicts an example new WSMP frame for an IEEE 1609.3-based platoon join request to accommodate an interworking vehicle, where "Vehicle ID" is the identifier of the vehicle transmitting the element; "Plane / Interworking Unit ID" is the identifier of the existing platoon, PME 120, or interworking vehicle 190 that the requesting vehicle wishes to join; and the optional "Info" field may contain other information about the vehicle, such as safety information.
[0101] WAVE element ID = 12 length Group / intercommunication unit ID Information (optional) octet 1 1 4 variable
[0102] Table 15. Example frame for a platoon join request.
[0103] exist Figure 7 or Figure 9 In either case, during the initial formation of the platoon, the platoon is established with the help of the intercommunication vehicles 190. Figure 10An example of how an additional vehicle can be added to an existing platoon by an interoperable vehicle 190, which may or may not be part of the platoon. If necessary, the interoperable vehicle 190 and the PME 120 may initially exchange information (information exchange message 700) to make each other aware of their capabilities. As part of this information exchange, the PME 120 may instruct the interoperable vehicle 190 to begin providing interoperability functionality (if not already provided). If the interoperable vehicle 190 is already a member of a platoon managed by the PME 120, this information exchange may not be necessary, as the PME 120 may have previously acquired information about the interoperable vehicle's capabilities. This information exchange may also not be necessary if the interoperable vehicle 190 and the PME 120 are located on the same vehicle.
[0104] The intercommunicating vehicle 190 may then transmit a beacon message (Beacon 705 ) using one or more V2X RATs. Figure 10 Two V2X RATs are shown: a first V2X RAT compatible with vehicle 170A and a second V2X RAT compatible with vehicle 170B. A beacon 705 message, which can be a broadcast or multicast message to be received by any V2X-enabled vehicle within communication range, contains an invitation to join the platoon and lists its interworking capabilities and, optionally, the capabilities of the platoon. Interested vehicles can send a request message to join the platoon. For vehicle 170B, a request message (Join Request 710) is transmitted to interworking vehicle 190. Another request message (Join Request 715) is transmitted by the vehicle to PME 120. In this case, it is assumed that PME 120 can be reached via network 100, for example, via an access point or wireless gateway, using the V2X RAT used by the requesting vehicle. On the other hand, if PME 120 and interworking vehicle 190 are located on the same entity (e.g., vehicle, server), there is no need to send separate messages. If the requesting vehicle 170B is not able to access the PME 120, the joining request may be converted by the interoperable vehicle 190 and forwarded to the PME 120, as generally described with reference to FIG. Figure 9 As stated.
[0105] The interoperable vehicle 190 and the PME 120 may then both respond to the request to join (responses 720 and 725, respectively). The responses from the interoperable vehicle 190 and / or the PME 120 may include configuration information and other details about the interoperable vehicle 190 and the platoon. On the other hand, if the request to join is denied, the response 720 or 725 may include one or more reason codes or error codes indicating why the request was denied. Thus, by the interoperable vehicle 190, the platoon may be expanded to add vehicles that communicate using the first V2X RAT or the second V2X RAT. Thus, the platoon may include vehicles that use two, three, or more V2X RATs, as long as the interoperable vehicles 190 in the platoon support them. This is in Figure 11 , where vehicles 170A, 170B, and 190 form a platoon. A first subset of the vehicles in the platoon operate using a first V2X RAT, and a second subset of the vehicles operate using a second V2X RAT. Interoperable vehicle 190 may be considered a member outside of either subset of the platoon / vehicles, but bridging the two subsets of vehicles; or may be considered a member of both subsets of the platoon / vehicles. In some implementations, rather than simply allowing individual vehicles of the second subset to join, the entire subset of vehicles operating using the second V2X RAT may be joined to the first subset via interoperable vehicle 190. This may occur, for example, when two smaller platoons (each using a respective V2X RAT) are merged together to create a super platoon. Accordingly, when the super platoon is split into smaller platoons / sub-platoons, interoperable vehicle 190 may remain a member of one of the new sub-platoons, or indeed all of the new sub-platoons.
[0106] It should be understood that using the intercommunication functionality of the intercommunication vehicle 190, individual vehicles in a platoon and other platoon entities can relay messages to each other even if the individual vehicles are using incompatible V2X RATs. The relayed / intercommunication messages can be used for any purpose, such as controlling the platoon, or presenting an auditory, visual, or tactile alert to the occupants of the vehicle (e.g., the driver). The intercommunication vehicle 190 can also be used to relay / intercommunication information obtained from its own platoon to another platoon or vehicles that are not connected or not part of the platoon. This helps to ensure that all affected vehicles receive V2X messages (e.g., V2X message transmissions related to emergency situations) if all affected vehicles are within communication range of the intercommunication vehicle 190. The intercommunication vehicle 190 can relay / intercommunication messages to other entities in the system, such as the RSU ( Figure 1111p or IEEE 802.11bd), an interoperable vehicle 190 can serve as a mobile hotspot for other vehicles.
[0107] Table 16 lists an example of a new WSMP frame that modifies IEEE 1609.3 for an interworking vehicle invitation (i.e., beacon 705) that can be sent by an interworking vehicle 190, where "Interworking Unit ID" is the identifier of the interworking vehicle 190 and "Reason Code" is an explanation of the reason for issuing the invitation.
[0108] WAVE element ID = 13 length Intercommunication unit ID Reason Code Information (optional) octet 1 1 2 1 variable
[0109] Table 16. Example framework for inter-vehicle invitation.
[0110] Table 17 is an example of a new WSMP frame that modifies IEEE 1609.3 for a vehicle's response to an intercommunication vehicle invitation. The "Reason Code" may include an indication that the invitation was accepted, or may include a reason for rejection or another condition (e.g., delay in request / join, or poor signal).
[0111] WAVE element ID = 14 length Vehicle ID Reason Code Information (optional) octet 1 1 2 1 variable
[0112] Table 17. Example framework for invited vehicle responses.
[0113] Once the vehicles are configured in a platoon, the order or position of the individual vehicles can be determined by PME 120 based on a number of factors. As described above, the order or position can be set during the configuration phase of platoon formation. The decision to assign a given order to a vehicle can be arbitrary and can be performed at any time, or it can be performed based on specific factors, such as vehicle capabilities. At times, it may be necessary to reconfigure or reorder the vehicles in a platoon, for example, to compensate for departing vehicles, changes in the environment, or changes in the capabilities of the vehicles in the platoon. For example, it may be desirable to rearrange the position of interoperable vehicle 190 within the platoon to maximize the radio coverage of interoperable vehicle 190 over the remaining vehicles in the platoon, or to increase the coverage of interoperable vehicle 190 outside the platoon to allow for the addition of additional vehicles using different V2X RATs. Therefore, factors that may determine whether to reposition a vehicle or position it in a specific position within a platoon may include the vehicle's capabilities, which indicate the vehicle's ability to provide radio communications, such as antenna gain, vehicle height, and antenna height / position. These characteristics may be reported by the vehicle when it joins the platoon. Another possible factor is the received signal strength of radio transmissions from other members of the platoon. This can be combined by the platoon management function with other factors such as vehicle capabilities, e.g. antenna height or antenna gain, to enable the platoon management function to determine the optimal position of a particular vehicle within the platoon to maximize the reliability of communications within the platoon and ensure the availability of intercommunication functions within the platoon.
[0114] To facilitate V2X intercommunication within an existing platoon, the interoperable vehicles 190 may need to report the platoon format or order to the PME 120 or make decisions regarding the platoon format or order, for example, to optimize connectivity for all V2X vehicles within the platoon network. This can be done autonomously or in conjunction with an existing PME 120. As input, the interoperable vehicles 190 may require information about the V2X RAT capabilities of other vehicles in the platoon (which V2X RATs are supported, which features and functions of those V2X RATs are supported, which versions of V2X RATs and / or features and functions are supported, etc.), their position in the platoon, and other information related to their ability to move to other positions within the platoon.
[0115] Figure 121 shows possible message transmissions between an interoperable vehicle 190, a PME 120, and other vehicles of the platoon. Initially, the PME 120 or another control entity of the platoon to which the interoperable vehicle 190 belongs transmits instructions that configure measurement actions to be taken by the interoperable vehicle 190 on demand or in response to certain triggering events (a measurement configuration message 750). The measurement configuration message may identify the parameters to be measured (e.g., vehicle speed, signal strength), the identity of the vehicle to be measured (if required), the triggering event, and instructions for filtering the measurements before reporting. This configuration message 750 may be included in the initial configuration message transmitted to the interoperable vehicle 190 when it joins the platoon, or may be transmitted in a separate message, such as Figure 12 The intercommunication vehicle 190 confirms the measurement configuration message and confirms that the configuration is complete (confirmation message 755 ), or transmits a message of rejection instruction, which may include one or more reason codes for rejection.
[0116] Upon occurrence of a trigger event 760, which may be, for example, a request to join the intercommunication vehicle 190 (e.g., reference to Figure 10 expiration of a timer; exceeding a measurement threshold (such as the signal level or quality of a given platoon member falling below a specified level), or an ad hoc request from the PME 120. This may include requests for sensor and other operating parameters from vehicles using the same or different V2X RATs (measurement requests 765), such as Figure 12 As shown. The vehicle provides its sensor readings and other data in response (response 770). In some cases, the intercommunication vehicle 190 can collect some or all of the required data during normal operation of the platoon, as it relays / intercommunication messages between the different platoon entities, and may not need to request some or all of the required measurements. For example, during platoon activity, signal strength and signal quality, current speed, acceleration, location, etc. can be regularly exchanged between vehicles. In some implementations, measurements can also be collected from vehicles that are not members of the platoon and are within communication range of the intercommunication vehicle 190, as this information may be relevant to decisions about reordering the platoon.
[0117] The interoperable vehicle 190 then compiles a measurement report based on its configuration and transmits it to the PME 120 (report 775). The PME 120 may then determine whether to reconfigure the platoon, such as assigning new configuration parameters to one, some, or all members of the platoon. If a reconfiguration is determined, the reconfiguration instructions may then be broadcast, multicast, or sent directly to each vehicle in the platoon (reconfiguration message 780). Each vehicle may acknowledge receipt of the message ( Figure 12In response to the reconfiguration message 780, the vehicle may then perform physical maneuvers consistent with the reconfiguration instructions (e.g., changing order within the platoon, reducing or increasing the gap between the vehicle and the preceding or following vehicle, etc.), and then signal the PME 120 directly when the reconfiguration is complete, or, if the vehicle requires interworking functionality to be able to communicate with the PME 120, signal the PME 120 via the interworking vehicle 190. It should also be noted that, as a result of the reconfiguration, the interworking vehicle 190 may be advantageously placed in the platoon to use an additional V2X RAT that it was not previously using.
[0118] Table 18 lists an example new WSMP frame based on IEEE 1609.3 for implementing platoon reconfiguration associated with interoperable vehicles. This message will be received by the target vehicle in the platoon (identified by "Vehicle ID") and identifies the new location the vehicle should move to.
[0119]
[0120] Table 18. Example frame for bank reconfiguration instructions.
[0121] For reasons such as, but not limited to, equipment failure, the need to save resources, the need to leave the platoon, etc., the interoperable vehicle 190 may need to stop the interoperable operation. The process for the interoperable vehicle 190 to stop the interoperable operation and / or leave the platoon is as follows: Figure 13 800 . First, information is exchanged between an interoperable vehicle 190 and a PME 120, wherein the interoperable vehicle 190 notifies the PME 120 of its intention to leave the platoon and / or cease providing interoperability functionality. This assumes that the interoperable vehicle 190 is able to notify the PME 120 of its planned departure in advance. Alternatively, the decision to cease interoperability may be made by the PME 120 (e.g., due to a reduction in the size of the platoon or its disbanding), in which case the PME 120 will transmit an instruction to the interoperable vehicle 190 to cease interoperability functionality. However, in the example shown, the information from the interoperable vehicle 190 (notification 800 ) may include at least an expected departure time (which may be zero if the interoperable vehicle 190 has already ceased providing interoperability functionality) and may include information such as a reason code for the stop or departure.
[0122] Interoperable vehicle 190 may also transmit a beacon message (beacon 805) to the other vehicles in the platoon to notify them of the cessation of interoperability. The information in this message may be similar to notification 800 and may include additional information about the platoon, such as a platoon identifier. Each vehicle may send an acknowledgment (acknowledgment message 810). As a result of the notification, the vehicle may also send a query to PME 120 requesting updated information about the platoon status (status request 820).
[0123] Once the interoperable vehicle 190 leaves the platoon or terminates / stops its interoperability function, it can send a final departure message (update message 825) to the PME 102 and / or other vehicles. This message can include useful information for other vehicles in the platoon, such as the identities / identifiers of other interoperable vehicles that may be available, departure time, information about the platoon, etc. The PME can also respond to the vehicle's query with updated information about the platoon's status (response 830). The response can include other information, such as reconfiguration instructions in light of the departure of the interoperable vehicle 190, the cessation of interoperability, or information about new interoperable vehicles or platoons that the vehicle can choose to join.
[0124] In some cases, the departure of an interoperable vehicle 190 or the cessation of interoperability may occur without notice. The PME 120 may detect the loss of interoperability when no confirmation or other messages are received from those members of the platoon that rely on the interoperable vehicle 190.
[0125] Table 19 lists an example new WSMP frame based on IEEE 1609.3, which lists the expected deviation of the interoperable vehicle, including the identifier of the interoperable vehicle, the time in milliseconds at which the deviation is expected to occur (absolute time or as an offset time relative to the transmission of the element), and the identifier for the new interoperable vehicle (if it is available and has been identified). In this example, if the "time" field is set to 0, then the deviation has occurred.
[0126]
[0127] Table 19. Example framework for identifying interchanging vehicles that deviate from a platoon.
[0128] Thus, the foregoing examples provide a communication system for supporting multiple RATs, wherein the communication system is configured to advertise its availability to provide interworking functionality to at least one entity in a set of one or more entities (such as a vehicle in a platoon of vehicles), the entity being configured to use a first RAT from the plurality of RATs, thereby enabling the entity in the set to communicate with other entities outside the set, even if those other entities use a second RAT that is incompatible with the first RAT. The interworking functionality effectively provides simultaneous access to the plurality of RATs for the at least one entity in the set, thereby extending its communication range. This can be used to support cooperative awareness messaging (as might be used in a smart system of automated, autonomous, or semi-autonomous entities) by enabling an entity to communicate with other entities using different RATs.
[0129] In particular, the aforementioned example provides a communication system and method for supporting multiple vehicle-to-everything radio access technologies (V2X RATs), including: at least one microprocessor configured to: transmit, using a first V2X RAT from among multiple V2X RATs, to at least one platoon entity of a platoon implementing the first V2X RAT, an indication that the communication system is operable to support interworking functionality to provide simultaneous access to the multiple V2X RATs, the platoon including at least one vehicle; and receive, using one of the multiple V2X RATs, an instruction to provide the interworking functionality. The one of the multiple V2X RATs for receiving the instruction can be the same V2X RAT (i.e., the first V2X RAT), or a different V2X RAT than the first V2X RAT, such as a second V2X RAT or a third V2X RAT. The different or distinct V2X RATs can include the same standard with different feature sets, or different standards.
[0130] In one aspect, the at least one microprocessor is further configured to, while providing interworking functionality, receive a first message in a first V2X RAT format using a first V2X RAT; and transmit information included in the first message in a second message using a second V2X RAT, wherein the second message is in the second V2X RAT format.
[0131] In another aspect, the indication includes an identification of each of the plurality of V2X RATs; an indication of whether the communication system is currently providing interworking functionality; and / or an identifier of the communication system.
[0132] In further aspects, the communication system may be included in a portable mobile device, and / or may be included in a vehicle, a platoon management entity, a server system, or an RSU.
[0133] In another aspect, the indication is transmitted following a triggering event associated with the vehicle including the communication system, wherein the triggering event includes one of: the vehicle including the communication system arriving at a predefined location; and a change in a configuration of the vehicle including the communication system.
[0134] Additionally, the at least one microprocessor is further configured to receive an instruction to join the platoon using one of a plurality of V2X RATs.
[0135] In a further aspect, where the communication system is included in a vehicle and is a member of a platoon, the at least one microprocessor is configured to receive instructions from the platoon management entity to provide intercommunication functionality and may also receive instructions from the platoon management entity to change the physical positioning of the vehicle in the platoon.
[0136] In other aspects, at least one squad entity is a squad management entity and / or a fixed server; the vehicle may be a ground vehicle or an aerial vehicle.
[0137] Also provided are a system and method implemented or achieved by a platoon management entity that manages a first platoon of vehicles, the first platoon including members communicating using a communication system configured to use a first vehicle-to-everything radio access technology (V2X RAT), wherein the method includes: determining that an interworking function for providing simultaneous access to multiple V2X RATs including the first V2X RAT is available from an interworking vehicle including an interworking communication system capable of supporting the interworking function; and the platoon management entity including the interworking vehicles in the first platoon.
[0138] In one aspect, a platoon management entity determines the availability of an additional vehicle including an additional communication system to join a first platoon, the additional communication system being configured to communicate using a second V2X RAT among a plurality of V2X RATs; the platoon management entity transmits a request to join the first platoon to the additional vehicle using both a first V2X RAT and a second V2X RAT among the plurality of V2X RATs via an interworking communication system; the platoon management entity receives an acknowledgment from the additional vehicle via the interworking communication system; and the platoon management entity includes the additional vehicle in the first platoon.
[0139] In another aspect, determining that the interworking functionality is available includes the group management entity receiving an indication from the interworking communication system via the first V2X RAT that the communication system is available to support the interworking functionality.
[0140] In a further aspect, including the interoperable vehicle in the first platoon includes the platoon management entity transmitting, after receiving the indication, an instruction to provide interoperability functionality to the interoperable communication system.
[0141] In yet another aspect, determining the availability of additional vehicles to join the first platoon comprises the platoon management entity receiving an indication of the availability of additional vehicles to join the first platoon from an intercommunication communication system, the additional communication system being in communication with the intercommunication communication system; and / or determining the availability of additional vehicles to join the first platoon comprises obtaining an indication of the availability of additional vehicles to join the first platoon from a server.
[0142] In another aspect, the additional vehicle is a member of a second platoon, and transmitting the request to join the first platoon comprises transmitting the request to a platoon management entity of the second platoon.
[0143] In yet another aspect, after including the interoperable vehicle in the first platoon, the platoon management entity transmits an instruction to the interoperable communication system to change the physical positioning of the interoperable vehicle in the first platoon.
[0144] In another aspect, the platoon management entity transmits a first message to a first vehicle in a first platoon, the first message being in a first V2X RAT format using a first V2X RAT, wherein the first vehicle is configured to communicate using the first V2X RAT; and transmits a second message to a second vehicle in the first platoon, wherein the second vehicle is configured to communicate using a second V2X RAT, comprising transmitting the second message in the first V2X RAT format to the interworking communication system for transmission to the second vehicle using the first V2X RAT.
[0145] In another aspect, the platoon management entity may detect cessation of the interworking functionality; transmit a message to the other vehicle via the interworking communication system to remove the other vehicle from the first platoon; and remove the interworking vehicle from the first platoon.
[0146] In another aspect, the group management entity detecting the cessation of the interworking function comprises receiving an indication of the cessation of the interworking function from the interworking communication system.
[0147] In one aspect, the platoon management entity is included in a vehicle, a server system, or an RSU of the first platoon.
[0148] In a further aspect, the platoon management entity includes the interoperable vehicle in the platoon before determining that the interoperable functionality is available.
[0149] A vehicle platoon is also provided, the vehicle platoon comprising: a first subset of one or more vehicles, the first subset comprising vehicles having corresponding communication systems configured to communicate using a first vehicle-to-all radio access technology (V2X RAT); a second subset of one or more vehicles, the second subset comprising vehicles having corresponding communication systems configured to communicate using a second V2X RAT different from the first V2X RAT; and interoperable vehicles, comprising an interoperable communication system configured to communicate using both the first V2X RAT and the second V2X RAT, the interoperable communication system being configured to receive a first message in a first V2X RAT format using the first V2X RAT and to send information included in the first message in a second message in the second V2X RAT format using the second V2X RAT.
[0150] In one aspect, the communication system of a first vehicle of the first subset is configured to transmit a first message, and the communication system of a second vehicle of the second subset is configured to receive a second message.
[0151] In a further aspect, the communication system of the first vehicle of the first subset is configured to transmit a first message, and the interworking communication system is configured to transmit a second message to the RSU.
[0152] In another aspect, the communication system of the first vehicle of the first subset is configured to transmit a first message, and the interworking communication system is configured to transmit a second message to the base station or access point.
[0153] In yet another aspect, the interworking communication system is further configured to receive a third message in a second V2X RAT format using a second V2X RAT, and to send information included in the third message in a fourth message in the first V2X RAT format using the first V2X RAT.
[0154] In some aspects, the intercommunication vehicles are included in the first subset or the second subset; the platoon may include a platoon management entity, which may be included in the vehicles in the first subset or the second subset. The first subset and the second subset may include ground vehicles.
[0155] The examples and embodiments are given by way of example only and are not intended to limit the scope of the subject matter described herein. Each of the example embodiments presented above may be combined in whole or in part with the other examples. Furthermore, variations of these examples will be apparent to those skilled in the art and are considered to be within the scope of the subject matter described herein. Some steps or actions in a process or method may be reordered or omitted, and features and aspects described with respect to one embodiment may be incorporated into other described embodiments.
[0156] The data used by the systems, devices, and methods described herein can be stored in one or more data repositories. The data repositories can have many different types of storage devices and programming constructs, such as RAM, ROM, flash memory, programming data structures, programming variables, etc. Code suitable for providing the above-mentioned systems and methods can be provided on many different types of computer-readable media (e.g., CD-ROM, floppy disk, RAM, flash memory, computer hard drive, etc.) including computer storage mechanisms, which contain instructions for being executed by one or more processors to perform the operations described herein. The media on which code can be provided are generally considered to be non-transient or physical.
[0157] Computer components, software modules, engines, functions, and data structures may be connected to each other, directly or indirectly, to allow the data flow required for their operation. In order to more particularly emphasize their independent implementation and operation, various functional units have been described, explicitly or implicitly, as modules, engines, or similar terms. Such units may be implemented as code units, subroutine units, objects, applets, scripts, or other forms of code. Such functional units may also be implemented in hardware circuits, including custom VLSI circuits or gate arrays; field programmable gate arrays; programmable array logic; programmable logic devices; commercially available logic chips, transistors, and other such components. Functional units do not have to be physically placed together, but may reside in different locations that can be logically combined for execution, such as on several electronic devices or memory devices. Functional units may also be implemented as a combination of software and hardware, such as a processor operating on a set of operational data or instructions.
[0158] The use of any specific terminology should not be construed as limiting the scope or requiring experimentation to implement the claimed subject matter or embodiments described herein. Any suggestion of alternative data processing systems or environments for other implementations should not be construed as an admission that the invention(s) described herein are abstract, nor should it be construed as implying that a data processing system or its components are not essential to the (telephone) inventions described herein.
[0159] A portion of the disclosure of this patent document contains material that is or may be protected by one or more of copyright, design, or trade dress, whether registered or unregistered. The owner has no objection to the facsimile reproduction of the disclosure as it appears in the Patent Office records to any such material described herein, but otherwise reserves all rights.
Claims
1. A communication system for supporting multiple vehicle-to-everything radio access technologies (V2X RATs), the communication system being included in a first vehicle in a platoon, the communication system include: At least one microprocessor configured to: transmitting, using a first V2X RAT of the plurality of V2X RATs, an indication to at least one platoon entity of a platoon implementing the first V2X RAT, the indication that the communication system is operable to support an interworking function for providing simultaneous access to a second V2X RAT of the plurality of V2X RATs, the platoon comprising at least one vehicle; receiving, using one V2X RAT of the plurality of V2X RATs, an instruction to provide the interworking function from a team management entity; and An instruction to modify a physical position of the first vehicle in the platoon is received from the platoon management entity using one of the plurality of V2X RATs.
2. The communication system according to claim 1, wherein the at least one microprocessor is further configured to: receiving a first message in a first V2X RAT format using the first V2X RAT; and The information included in the first message is transmitted in a second message using the second V2X RAT, wherein the second message is in a second V2X RAT format.
3. The communication system according to claim 1, wherein the indication include: an identifier of each V2X RAT in the plurality of V2X RATs; an indication of whether the communication system is currently providing the interworking functionality; as well as An identifier for the communication system. The communication system of claim 1 , comprised in a portable mobile device.
5. The communication system of claim 1 , wherein the at least one microprocessor is configured to transmit the indication following a triggering event associated with the first vehicle including the communication system, wherein the triggering event comprises one of: the vehicle including the communication system arrives at a predefined location; and A change in the configuration of the vehicle including the communication system.
6. The communication system of claim 1, wherein the at least one microprocessor is further configured to receive an instruction to join the platoon using one of the plurality of V2X RATs.
7. The communication system according to claim 1, wherein the at least one grouping entity is a group management entity.
8. The communication system of claim 1, wherein the at least one platooning entity is a fixed server.
9. The communication system according to claim 1, wherein the plurality of V2X RATs comprises at least one of the following: ETSI ITS, SAE DSRC, and SAE C-V2X.
10. The communication system of claim 1, wherein the first vehicle is a ground vehicle.
11. The communication system of claim 1, wherein the first vehicle is an aerial vehicle.
12. The communication system of claim 1, comprised in a group management entity.
13. The communication system according to claim 1, included in a server system.
14. The communication system of claim 1, included in a roadside unit.
15. A method for supporting multiple vehicle-to-everything radio access technologies (V2X RATs), include: at least one microprocessor in a communication system included in a first vehicle in a platoon, the platoon comprising at least one vehicle, transmitting an indication to at least one platoon entity implementing the first V2X RAT using a first V2X RAT of the plurality of V2X RATs, the indication that the communication system is operable to support an interworking function for providing simultaneous access to the plurality of V2X RATs; The at least one microprocessor receives an instruction from a team management entity using one V2X RAT of the plurality of V2X RATs to provide the interworking function; and The at least one microprocessor receives instructions from the platoon management entity using one of the plurality of V2X RATs to modify a physical position of the first vehicle in the platoon.
16. The method according to claim 15, wherein the interworking function is provided include: receiving a first message in a first V2X RAT format using the first V2X RAT; as well as The information included in the first message is transmitted in a second message using a second V2X RAT among the plurality of V2X RATs, wherein the second message is in a second V2X RAT format.
17. The method according to claim 15, wherein the indication include: an identifier of each V2X RAT in the plurality of V2X RATs; an indication of whether the communication system is currently providing the interworking functionality; as well as An identifier for the communication system.
18. The method of claim 15, wherein the communication system is included in a portable mobile device.
19. The method of claim 15, wherein transmitting the indication occurs after a triggering event associated with the vehicle including the communication system, wherein the triggering event comprises one of: the first vehicle including the communication system arrives at a predefined location; and A change in the configuration of the first vehicle includes the communication system.
20. The method of claim 15, further comprising the at least one microprocessor receiving an instruction to join the platoon using one of the plurality of V2X RATs.
21. The method of claim 15, wherein the at least one grouping entity is a grouping management entity.
22. The method of claim 15, wherein the at least one grouping entity is a fixed server.
23. The method of claim 15, wherein the plurality of V2X RATs comprises at least one of: ETS ITS, SAE DSRC, and SAE C-V2X.
24. The method of claim 15, wherein the vehicle is a ground vehicle.
25. The method of claim 15, wherein the vehicle is an aerial vehicle.
26. The method of claim 15, wherein the communication system is included in a group management entity.
27. The method of claim 15, wherein the communication system is included in a server system.
28. The method of claim 15, wherein the communication system is included in a roadside unit.
29. A method implemented by a platoon management entity managing a first platoon of vehicles, the first platoon comprising members communicating using a communication system configured to use a first vehicle-to-everything radio access technology (V2X RAT), the method include: determining that an interworking function for providing simultaneous access to a plurality of V2X RATs including the first V2X RAT is available from an interworking vehicle, the interworking vehicle including an interworking communication system capable of supporting the interworking function; including the intercommunication vehicle in the first row group; as well as Instructions are transmitted to the intercommunication system to modify the physical positioning of the intercommunication vehicle in the first platoon.
30. The method according to claim 29, further comprising: include: the platoon management entity determining availability of further vehicles including further communication systems to join the first platoon, the further communication systems being configured to communicate using a second V2X RAT of the plurality of V2X RATs; transmitting, by the platoon management entity, a request to join the first platoon to the further vehicle using both the first V2X RAT and a second V2X RAT of the plurality of V2X RATs via the interworking communication system; the platoon management entity receiving a confirmation from the further vehicle via the intercommunication system; and The platoon management entity includes the further vehicle in the first platoon.
31. The method of claim 29, wherein determining that the interworking function is available include: The platoon management entity receives, from the interworking communication system via the first V2X RAT, an indication that the communication system is available to support the interworking function.
32. The method of claim 31, wherein the interoperable vehicles are included in the first platoon include: After receiving the indication, the platoon management entity transmits instructions for providing the interworking function to the interworking communication system.
33. The method of claim 30, wherein determining the availability of the additional vehicle to join the first platoon include: The platoon management entity receives an indication of the availability of the further vehicle to join the first platoon from the intercommunication system with which the further communication system is in communication.
34. The method of claim 30, wherein determining the availability of the additional vehicle to join the first platoon comprises obtaining an indication of the availability of the additional vehicle to join the first platoon from a server.
35. The method of claim 30, wherein the additional vehicle is a member of a second platoon, and wherein transmitting the request to join the first platoon comprises transmitting the request to a platoon management entity for the second platoon.
36. The method according to claim 29, further comprising: include: The platoon management entity transmits a first message to a first vehicle in the first platoon, the first message being in a first V2X RAT format using the first V2X RAT, wherein the first vehicle is configured to communicate using the first V2X RAT; The platoon management entity transmits a second message to a second vehicle in the first platoon, wherein the second vehicle is configured to communicate using a second V2X RAT, including using the first V2X RAT to transmit the second message in a first V2X RAT format to the interworking communication system for transmission to the second vehicle.
37. The method according to claim 30, further comprising the row group management entity: detecting cessation of the intercommunication function; transmitting a message to the additional vehicle via the intercommunication system to remove the additional vehicle from the first platoon; and The interoperable vehicle is removed from the first platoon.
38. The method of claim 37, wherein the group management entity detecting the cessation of the interworking function comprises receiving an indication of the cessation of the interworking function from the interworking communications system.
39. The method of claim 29, wherein the platoon management entity is included in a lead vehicle of the first platoon.
40. The method of claim 29, wherein the platoon management entity includes the interoperable vehicle in the platoon before determining that the interoperable functionality is available.
41. The method of claim 29, wherein the bank management entity is included in a server system.
42. The method of claim 33, wherein the platoon management entity is included in a roadside unit.
43. A computing system comprising at least one microprocessor managing a first platoon of vehicles, the first platoon comprising members communicating using a communication system configured to use a first vehicle-to-everything radio access technology (V2X RAT), wherein the at least one microprocessor is configured to: determining that an interworking function for providing simultaneous access to a plurality of V2X RATs including the first V2X RAT is available from an interworking vehicle, the interworking vehicle including an interworking communication system capable of supporting the interworking function; including the interoperable vehicle in the first platoon; and Instructions are transmitted to the intercommunication system to modify the physical positioning of the intercommunication vehicle in the first platoon.
44. The computing system of claim 43, wherein the at least one microprocessor is further configured to: determining the availability of an additional vehicle including an additional communication system to join the first platoon, the additional communication system being configured to communicate using a second V2X RAT of the plurality of V2X RATs; transmitting, via the interworking communication system, to the other vehicle a request to join the first platoon using both the first V2X RAT and a second V2X RAT of the plurality of V2X RATs; receiving a confirmation from the other vehicle via the intercommunication system; and The further vehicle is included in the first platoon.
45. The computing system of claim 43, wherein determining that the interworking function is available include: An indication is received from the interworking communication system via the first V2X RAT that the communication system is available to support the interworking functionality.
46. The computing system of claim 45, wherein the interoperable vehicles are included in the first platoon include: After receiving the indication, an instruction for providing the interworking function is transmitted to the interworking communication system.
47. The computing system of claim 44, wherein determining the availability of the additional vehicle to join the first platoon include: An indication of the availability of the further vehicle to join the first platoon is received from the intercommunication system, the further communication system being in communication with the intercommunication system.
48. The computing system of claim 44, wherein determining the availability of the additional vehicle to join the first platoon comprises obtaining an indication of the availability of the additional vehicle to join the first platoon from a server.
49. The computing system of claim 44, wherein the additional vehicle is a member of a second platoon, and wherein transmitting the request to join the first platoon comprises transmitting the request to a platoon management entity for the second platoon.
50. The computing system of claim 43, wherein the at least one microprocessor is further configured to: transmitting a first message to a first vehicle in the first platoon, the first message being in a first V2X RAT format using the first V2X RAT, wherein the first vehicle is configured to communicate using the first V2X RAT; Transmitting a second message to a second vehicle in the first platoon, wherein the second vehicle is configured to communicate using a second V2X RAT, comprises transmitting the second message in a first V2X RAT format to the interworking communications system using the first V2X RAT for transmission to the second vehicle.
51. The computing system of claim 44, wherein the at least one microprocessor is further configured to: detecting cessation of the intercommunication function; transmitting a message to the other vehicle via the intercommunication system to remove the other vehicle from the first platoon; and The interoperable vehicle is removed from the first platoon.
52. The computing system of claim 43, wherein the at least one microprocessor is configured to detect the cessation of the interworking functionality by receiving an indication of the cessation of the interworking functionality from the interworking communications system.
53. The computing system of claim 43, included in a lead vehicle of the first platoon.
54. The computing system of claim 43, wherein the at least one microprocessor is configured to include the interoperable vehicle in the platoon prior to determining that the interoperable functionality is available.
55. The computing system of claim 43, included in a server system.
56. The computing system of claim 43, included in a roadside unit.
57. A row of groups, include: a first subset of one or more vehicles, the first subset including a first vehicle having a corresponding communication system configured to communicate using a first vehicle-to-everything radio access technology (V2X RAT); a second subset of one or more vehicles, the second subset including a second vehicle having a corresponding communication system configured to communicate using a second V2X RAT different from the first V2X RAT; as well as An interoperable vehicle, comprising an interoperable communication system configured to communicate using both the first V2X RAT and the second V2X RAT, the interoperable communication system being configured to receive a first message in a first V2X RAT format using the first V2X RAT, to send information included in the first message in a second message in a second V2X RAT format using the second V2X RAT, and to receive an instruction from a platoon management entity to change the physical positioning of the interoperable vehicle in the platoon.
58. The platoon of claim 57, wherein the communication systems of the first vehicles of the first subset are configured to transmit the first message and the communication systems of the second vehicles of the second subset are configured to receive the second message.
59. The platoon of claim 57, wherein the communication systems of the first vehicles of the first subset are configured to transmit the first message, and the intercommunication communication systems are configured to transmit the second message to a roadside unit (RSU).
60. The platoon of claim 57, wherein the communication systems of the first vehicles of the first subset are configured to transmit the first message and the interworking communication systems are configured to transmit the second message to a base station or access point.
61. The bank of claim 57, wherein the interworking communication system is further configured to receive a third message in the second V2X RAT format using the second V2X RAT, and to send information included in the third message in a fourth message in the first V2X RAT format using the first V2X RAT.
62. The platoon of claim 57, wherein the interoperable vehicles are included in the first subset.
63. The platoon of claim 57, wherein the interoperable vehicles are included in the second subset.
64. The bank of claim 57, further comprising a bank management entity.
65. A platoon according to claim 64, wherein the platoon management entity is comprised in a vehicle in the first subset or the second subset.
66. The array of claim 57, wherein the first subset and the second subset include ground vehicles.
Citation Information
Patent Citations
Vehicle to X V2X terminal, system and management for compatible multi-system V2X
CN109215388A
Intelligent vehicle-based communication mangement
CN109275120A
Method for configuring interface in mobile communication system supporting multiple wireless access technologies and apparatus for performing same
US20160212635A1
Interactive sharing of vehicle sensor information
US20180365909A1
Handling interference in multi-rat wtru
US20190013881A1
