Queue-based protocol interworking

Abstract

Systems, apparatus, processes, and computer-readable media for wireless communication are disclosed. For example, a process may include receiving a plurality of messages using a first type of communication protocol at a network device (e.g., a vehicle or other type of network device), where the network device is part of a queue that includes a plurality of network devices (e.g., a plurality of vehicles or other network devices). The process may include generating, at the network device, a digest message summarizing the plurality of messages. The process may include transmitting the digest message using a second type of communication protocol.

Description

Technical Field

[0001] The present disclosure generally relates to vehicle communications. For example, aspects of the present disclosure relate to a queue-based protocol interworking solution (eg, for cellular vehicle-to-everything (C-V2X) and dedicated short range communications (DSRC)). Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Various aspects of wireless communication may include direct communication between devices, such as in V2X, vehicle to vehicle (V2V), and / or device to device (D2D) communication. There is a need to further improve V2X, V2V, and / or D2D technologies. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0005] Systems, apparatuses, methods, and computer-readable media for queue-based protocol interworking solutions (e.g., for cellular vehicle-to-everything (C-V2X) and dedicated short-range communications (DSRC)) are disclosed. According to at least one example, a method for wireless communication at a network device is provided. The method includes: receiving a plurality of messages at a network device using a first type of communication protocol, wherein the network device is part of a queue including a plurality of network devices; generating a summary message summarizing the plurality of messages at the network device; and sending the summary message using a second type of communication protocol.

[0006] In another example, an apparatus for wireless communication is provided, the apparatus comprising at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to: receive a plurality of messages using a first type of communication protocol, wherein the apparatus is part of a queue including a plurality of network devices; generate a summary message summarizing the plurality of messages; and output the summary message for transmission using a second type of communication protocol.

[0007] In another example, a non-transitory computer-readable medium of a computing device having instructions stored thereon is provided, which instructions, when executed by one or more processors, cause the one or more processors to: receive a plurality of messages using a first type of communication protocol, wherein the computing device is part of a queue including a plurality of network devices; generate a summary message summarizing the plurality of messages; and output the summary message for transmission using a second type of communication protocol.

[0008] In another example, an apparatus for wireless communication is provided. The apparatus includes: receiving a plurality of messages using a first type of communication protocol, wherein the apparatus is part of a queue including a plurality of network devices; generating a summary message summarizing the plurality of messages; and outputting the summary message for transmission using a second type of communication protocol.

[0009] In some aspects, the device is a vehicle (e.g., a car, truck, etc. or a component or system of a car, truck, etc.), a mobile device (e.g., a mobile phone or so-called "smartphone" or other mobile device), a wearable device, an extended reality device (e.g., a virtual reality (VR) device, an augmented reality (AR) device, or a mixed reality (MR) device), a personal computer, a laptop computer, a server computer, a robotic device, or other device or a portion thereof. In some aspects, the device includes a radio detection and ranging (radar) for capturing radio frequency (RF) signals. In some aspects, the device includes one or more light detection and ranging (LIDAR) sensors, radar sensors, or other light-based sensors for capturing light-based (e.g., light frequency) signals. In some aspects, the device includes a camera or multiple cameras for capturing one or more images. In some aspects, the device also includes a display for displaying one or more images, notifications, and / or other displayable data. In some aspects, the above-mentioned device may include one or more sensors, which can be used to determine the location of the device, the state of the device (e.g., temperature, humidity level, and / or other state), and / or for other purposes.

[0010] This summary is neither intended to identify key features or essential features of the claimed subject matter nor is it intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of this patent, any or all drawings, and each claim.

[0011] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Illustrative aspects of the present application are described in detail below with reference to the following drawings:

[0013] Figure 1 is a diagram illustrating an example wireless communication system in accordance with some aspects of the present disclosure.

[0014] Figure 2 is a diagram illustrating an example of a disaggregated base station architecture that may be used by the disclosed system for a queue-based C-V2X and DSRC interworking solution in accordance with some aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating examples of various user equipment (UE) communicating over a direct communication interface (e.g., a cellular-based PC5 sidelink interface, an 802.11p-defined DSRC interface, or other direct interface) and a wide area network (Uu) interface according to some aspects of the present disclosure.

[0016] Figure 4 is a block diagram illustrating an example of a computing system for a vehicle according to some aspects of the present disclosure.

[0017] Figure 5 is a block diagram illustrating an example of a computing system of a user device according to some aspects of the present disclosure.

[0018] Figure 6 is a diagram illustrating an example of devices involved in wireless communications (eg, sidelink communications) according to some aspects of the present disclosure.

[0019] 7A to 7D is a diagram illustrating an example of sensor sharing for cooperative and autonomous driving systems according to some aspects of the present disclosure.

[0020] Figure 8 is a diagram illustrating an example of sensor sharing for cooperative and autonomous driving systems according to some aspects of the present disclosure.

[0021] Fig. 9 is a diagram illustrating an example of a system for sensor sharing in wireless communications (e.g., C-V2X communications) according to some aspects of the present disclosure.

[0022] Fig.10 is a diagram illustrating an example of a vehicle-based message (shown as a sensor sharing message) in accordance with some aspects of the present disclosure.

[0023] Fig.11 is a diagram illustrating an example of a system according to some aspects of the present disclosure that employs a roadside unit (RSU) as a bridge to communicate between vehicles equipped for different types of communications (e.g., C-V2X and DSRC communications).

[0024] Fig.12 is a diagram of a disclosed system for a platoon-based C-V2X and DSRC interworking solution according to some aspects of the present disclosure, wherein some vehicles within the system are collaboratively negotiating the formation of a platoon.

[0025] Fig.13A and Fig. 13B are diagrams of the disclosed system for a queue-based C-V2X and DSRC intercommunication solution according to some aspects of the present disclosure, which together illustrate an example of a queue head operating as a bridge to communicate between vehicles equipped for different types of communications (e.g., C-V2X and DSRC communications).

[0026] Fig.14A and Fig. 14Bare diagrams of the disclosed system for a queue-based C-V2X and DSRC intercommunication solution according to some aspects of the present disclosure, which together illustrate another example of a queue head operating as a bridge to communicate between vehicles equipped for different types of communications (e.g., C-V2X and DSRC communications).

[0027] Fig.15 is a flow chart illustrating an example of a process for queue formation according to some aspects of the present disclosure.

[0028] Fig.16 is a flow chart illustrating an example of a process for wireless communication according to some aspects of the present disclosure.

[0029] Fig.17 An example computing system in accordance with aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0030] For illustrative purposes, certain aspects of the present disclosure are provided below. Without departing from the scope of the present disclosure, alternative aspects may be designed. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand. Some aspects described in this article may be applied independently, and some of them may be applied in combination, which is obvious to those skilled in the art. In the following description, specific details are set forth for explanation purposes to provide a thorough understanding of various aspects of the application. However, it is apparent that various aspects may be implemented without these specific details. Each drawing and description is not intended to be restrictive.

[0031] The following description provides only example aspects and is not intended to limit the scope, applicability or configuration of the present disclosure. On the contrary, the following description of the example aspects will provide a description that can be used to implement the example aspects to those skilled in the art. It should be understood that various changes may be made to the function and arrangement of the elements without departing from the essence and scope of the present application as set forth in the appended claims.

[0032] The terms "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0033] Wireless communication systems are deployed to provide a variety of telecommunication services including telephony, video, data, messaging, broadcasting, etc. Wireless communication systems have evolved over several generations. The 5G mobile standard calls for higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard (also known as "New Radio" or "NR") is designed to provide data rates of tens of megabits per second to each of tens of thousands of users.

[0034] A vehicle is an example of a device or system that may include wireless communication capabilities. For example, a vehicle (e.g., a motor vehicle, an autonomous vehicle, an aircraft, a sea vessel, etc.) may communicate with other vehicles and / or other devices with wireless communication capabilities. Wireless vehicle communication systems include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P) communications, which are collectively referred to as vehicle-to-everything (V2X) communications. V2X communications are vehicle communication systems that support wireless transmission of information from a vehicle to other entities located within a traffic system that may affect the vehicle (e.g., other vehicles, pedestrians with smartphones, and / or other traffic infrastructure). The main purpose of V2X technology is to improve road safety, fuel savings, and traffic efficiency.

[0035] In a V2X communication system, information is sent from vehicle sensors (and other sources) over a wireless link to allow the information to be communicated to other vehicles, pedestrians, and / or traffic infrastructure. The information may be sent using one or more vehicle-based messages (such as C-V2X messages), which may include sensor data sharing messages (SDSMs), basic safety messages (BSMs), collaborative awareness messages (CAMs), collective awareness messages (CPMs), and / or other types of messages. By sharing this information with other vehicles, V2X technology improves the vehicle's (and the driver's) awareness of potential hazards, thereby helping to reduce collisions with other vehicles and entities. In addition, V2X technology improves traffic efficiency by providing vehicles with traffic warnings about upcoming potential road hazards and obstacles so that the vehicle can choose an alternative traffic route.

[0036] As previously mentioned, V2X technology includes V2V communication, which may also be referred to as peer-to-peer communication. V2V communication allows vehicles to communicate wirelessly directly with each other while on the road. Using V2V communication, vehicles can gain situational awareness by receiving information about upcoming road hazards (e.g., unforeseen oncoming vehicles, accidents, and road conditions) from other vehicles.

[0037] The IEEE 802.11p standard supports (uses) a dedicated short-range communication (DSRC) interface for V2X wireless communications. The characteristics of the DSRC interface based on IEEE 802.11p include low latency and the use of an unlicensed 5.9 gigahertz (GHz) band. Cellular V2X (C-V2X) is adopted as an alternative to using the DSRC interface based on IEEE 802.11p for wireless communications. The 5G Automobile Association (5GAA) supports the use of C-V2X technology. In some cases, C-V2X technology uses Long Term Evolution (LTE) as the underlying technology, and C-V2X functionality is based on LTE technology. C-V2X includes multiple operating modes. One operating mode allows wireless communications directly between vehicles through the LTE side link PC5 interface. Similar to the DSRC interface based on IEEE 802.11p, the LTE C-V2X side link PC5 interface operates on the 5.9GHz band. Vehicle-based messages, such as BSM and CAM as application layer messages, are designed to be broadcast wirelessly over the 802.11p-based DSRC interface and the LTE C-V2X sidelink PC5 interface.

[0038] Currently, many commercially available vehicles in the United States are equipped for C-V2X communications to utilize the C-V2X sidelink PC5 interface to communicate with other vehicles similarly equipped for C-V2X communications (e.g., to send and / or receive vehicle-based messages, such as safety and awareness messages and warnings). Some of these vehicles in the United States are also equipped for DSRC communications to utilize an 802.11p-based DSRC interface to communicate with other vehicles similarly equipped for DSRC communications (e.g., to send and / or receive vehicle-based messages). Therefore, these dual communication-capable vehicles are referred to as having heterogeneous C-V2X / DSRC communication capabilities.

[0039] In contrast, for example, in Europe, many commercially available vehicles are only equipped for DSRC communications to utilize an 802.11p-based DSRC interface to communicate (e.g., send and / or receive vehicle-based messages) with other vehicles similarly equipped for DSRC communications. Vehicles equipped only for DSRC communications cannot communicate directly with vehicles that are not equipped for DSRC communications. As a result, vehicle-based messages (e.g., safety, awareness, and / or warning messages) generated by vehicles equipped only for DSRC communications are not easily received by vehicles equipped only for C-V2X communications, and vice versa.

[0040] In some aspects of the present disclosure, systems, apparatus, methods (also referred to as processes), and computer-readable media (collectively referred to herein as "systems and techniques") for providing queue-based protocol intercommunication solutions (e.g., for C-V2X and DSRC intercommunication) are described herein. For example, these systems and techniques may provide solutions for queue-based protocol intercommunication between computing devices configured to communicate using only a first type of communication protocol (e.g., C-V2X), at least one computing device configured to communicate using only a second type of communication protocol (e.g., DSRC), and at least one computing device configured to communicate using both the first type of communication protocol and the second type of communication protocol (e.g., C-V2X and DSRC). Although the various aspects described herein cite vehicles as illustrative examples of computing devices, the systems and techniques described herein may be applied to other types of computing devices.

[0041] In one or more aspects of the present disclosure, multiple vehicles in a grouping (e.g., positioned close to each other within an area or zone of a specified size) that are equipped to communicate using at least a first type of communication protocol (e.g., C-V2X) may form a queue. Multiple vehicles may negotiate with each other to identify one of the vehicles in the queue (or included in the queue) as the head of the queue. In one example, a restriction or requirement on a vehicle to be determined as the head of the queue is that the vehicle has heterogeneous communication capabilities using a first type of communication protocol and a second type of communication protocol (e.g., the vehicle has both C-V2X and DSRC communication functions). In addition to heterogeneous communication capabilities, in some cases, the vehicle may also be determined as the head of the queue based on its position relative to the position of other vehicles in the queue, such as when the vehicle selected as the head of the queue is centered within the multiple vehicles that make up the queue, so that the head of the queue vehicle is within the communication range of all other vehicles in the queue.

[0042] Because the queue head has heterogeneous communication capabilities (e.g., the ability to send / receive messages using both C-V2X and DSRC communication protocols), the queue head can operate as a bridge to communicate (e.g., communication of vehicle-based messages (such as safety and awareness messages and warnings)) between vehicles within the queue (equipped to use at least a first type of communication protocol, such as C-V2X communication) and other vehicles not in the queue that are only equipped for a second type of communication protocol (e.g., DSRC communication).

[0043] Additional aspects of the disclosure are described in more detail below.

[0044] As used herein, the terms "user equipment" (UE) and "network entity" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, and / or a tracking device, etc.), a wearable device (e.g., a smart watch, smart glasses, a wearable ring, and / or an extended reality (XR) device (such as a virtual reality (VR) headset, an augmented reality (AR) headset or glasses, or a mixed reality (MR) headset)), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), and / or an Internet of Things (IoT) device, etc., for a user to communicate on a wireless communication network. A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT," a "client device," a "wireless device," a "subscriber device," a "subscriber terminal," a "subscriber station," a "user terminal" or "UT," a "mobile device," a "mobile terminal," a "mobile station," or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on IEEE 802.11 communication standards, etc.), and the like.

[0045] In some cases, the network entity may be implemented in a converged or monolithic base station or server architecture, or alternatively, in a disaggregated base station or server architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC. In some cases, the network entity may include a server device, such as a multi-access edge computing (MEC) device. A base station or server (e.g., having a converged / monolithic base station architecture or a disaggregated base station architecture) may operate according to one of several RATs to communicate with UEs, roadside units (RSUs), and / or other devices depending on the network in which the base station or server is deployed, and may alternatively be referred to as an access point (AP), a network node, a node B (NB), an evolved node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access of UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, the base station may provide edge node signaling functions, while in other systems, the base station may provide additional control and / or network management functions. The communication link by which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to an uplink, a reverse or downlink, and / or a forward traffic channel.

[0046] The term "network entity" or "base station" (e.g., having an aggregated / monolithic base station architecture or a decomposed base station architecture) may refer to a single physical TRP or multiple physical TRPs, which may or may not be co-located. For example, where the term "network entity" or "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. Where the term "network entity" or "base station" refers to multiple co-located physical TRPs, these physical TRPs may be antenna arrays of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be a serving base station that receives measurement reports from a UE and a neighbor base station whose reference radio frequency (RF) signal (or "reference signal" for short) the UE is measuring. Because, as used herein, a TRP is the point through which a base station transmits and receives wireless signals, references to transmitting from or receiving at a base station should be understood to refer to the specific TRP of a base station.

[0047] In some specific implementations of supporting UE positioning, a network entity or base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections with respect to the UE), but may instead send a reference signal to be measured by the UE to the UE, and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).

[0048] A roadside unit (RSU) is a device that can communicate with a network through a communication link or interface (e.g., a cellular-based sidelink or PC5 interface, an 802.11-based or WiFi-based TM A device that sends and receives messages to and from one or more UEs, other RSUs, and / or base stations (using a dedicated short-range communication (DSRC) interface and / or other interfaces). Examples of messages that can be sent and received by an RSU include vehicle-to-everything (V2X) messages, which are described in more detail below. The RSU may be located on various transportation infrastructure systems, including roads, bridges, parking lots, toll booths, and / or other infrastructure systems. In some examples, the RSU may facilitate communication between UEs (e.g., vehicles, pedestrian user equipment, and / or other UEs) and transportation infrastructure systems. In some implementations, the RSU may communicate with a server, a base station, and / or other systems that may perform centralized management functions.

[0049] The RSU may communicate with the communication system of the UE. For example, the intelligent transportation system (ITS) of the UE (e.g., a vehicle and / or other UE) may be used to generate and sign messages for sending to the RSU and verify messages received from the RSU. The RSU may communicate (e.g., via a PC5 interface, a DSRC interface, etc.) with vehicles traveling along a road, bridge, or other infrastructure system to obtain traffic-related data (e.g., the time, speed, location, etc. of the vehicle). In some cases, in response to obtaining traffic-related data, the RSU may determine or estimate traffic congestion information (e.g., the start of a traffic congestion, the end of a traffic congestion, etc.), travel time, and / or other information of a specific location. In some examples, the RSU may communicate with other RSUs (e.g., via a PC5 interface, a DSRC interface, etc.) to determine traffic-related data. The RSU may send information (e.g., traffic congestion information, travel time information, and / or other information) to other vehicles, pedestrian UEs, and / or other UEs. For example, the RSU may broadcast or otherwise send information to any UE (eg, vehicles, pedestrian UEs, etc.) within the coverage area of ​​the RSU.

[0050] Radio frequency signals or "RF signals" include electromagnetic waves of a given frequency that transmit information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to either a wireless signal or an RF signal.

[0051] According to various aspects, Figure 1An exemplary wireless communication system 100 is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. In some aspects, the base stations 102 may also be referred to as "network entities" or "network nodes". One or more of the base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more of the base stations 102 may be implemented in a decomposed base station architecture and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). On the one hand, the macro cell base station may include an eNB and / or an ng-eNB (where the wireless communication system 100 corresponds to a long term evolution (LTE) network), or a gNB (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include a femto cell, a pico cell, a micro cell, etc.

[0052] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface to one or more location servers 172 (which may be part of the core network 170 or may be external to the core network 170) through the core network 170. Among other functions, the base stations 102 may perform functions related to one or more of the following: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC or 5GC) through a backhaul link 134 (which may be wired and / or wireless).

[0053] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, base station 102 in each coverage area 110 can support one or more cells. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and can be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB) or other protocol types) that can provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" can refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because a TRP is typically a physical transmission point of a cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area (eg, a sector) of a base station, as long as a carrier frequency can be detected and used for communications within some portion of the geographic coverage area 110 .

[0054] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage area 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).

[0055] The communication link 120 between the base station 102 and the UE 104 may include uplink (also known as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (also known as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0056] The wireless communication system 100 may further include a WLAN AP 150 in communication with a WLAN station (STA) 152 via a communication link 154 in an unlicensed spectrum (e.g., 5 gigahertz (GHz)). When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or a listen-before-talk (LBT) procedure before communicating to determine whether the channel is available. In some examples, the wireless communication system 100 may include a device (e.g., UE, etc.) that communicates with one or more UEs 104, base stations 102, APs 150, etc. using an ultra-wideband (UWB) spectrum. The UWB spectrum may range from 3.1 GHz to 10.5 GHz.

[0057] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE and / or 5G in the unlicensed spectrum can boost the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA) or MulteFire.

[0058] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which may operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. The mmW base station 180 may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a decomposed base station architecture (e.g., including one or more of a CU, DU, RU, near RT RIC, or non-RT RIC). Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend down to a frequency of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and is also referred to as centimeter waves. Communications using mmW and / or near mmW radio frequency bands have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. In addition, it should be understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or near-mmW and beamforming. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0059] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node or entity (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node), and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that produces RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to the individual antennas in the correct phase relationship so that the radio waves from the separate antennas are added together in the desired direction to increase the radiation, and canceled in the undesired direction to suppress the radiation.

[0060] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the transmit antennas of the network nodes themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0061] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) the RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain of other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) for the RF signal received from that direction.

[0062] The receive beams may be spatially correlated. The spatial relationship means that the parameters of the transmit beam for the second reference signal may be derived from information about the receive beam for the first reference signal. For example, the UE may receive one or more reference downlink reference signals (e.g., positioning reference signal (PRS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), channel state information reference signal (CSI-RS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal block (SSB), etc.) from a network node or entity (e.g., a base station) using a specific receive beam. The UE may then form a transmit beam based on the parameters of the receive beam for transmitting one or more uplink reference signals (e.g., uplink positioning reference signal (UL-PRS), sounding reference signal (SRS), demodulation reference signal (DMRS), PTRS, etc.) to the network node or entity (e.g., a base station).

[0063] Note that, depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if a network node or entity (e.g., a base station) is forming a downlink beam to send a reference signal to a UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if a network node or entity (e.g., a base station) is forming an uplink beam, the uplink beam is an uplink receive beam, and if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0064] In 5G, the spectrum in which the wireless network nodes or entities (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450MHz to 6000MHz), FR2 (from 24250MHz to 52600MHz), FR3 (above 52600MHz), and FR4 (between FR1 and FR2). In a multi-carrier system (such as 5G), one of the carrier frequencies is called a "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are called "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and can be used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those signaling information and signals specific to the UE may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. This is also true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency or component carrier that some base stations are using to communicate, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0065] For example, still refer to Figure 1, one of the frequencies used by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). In carrier aggregation, the base station 102 and / or the UE 104 may use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz) bandwidth per carrier, with up to a total of Yx MHz (x component carriers) in each direction for transmission. The component carriers may be adjacent to each other or may not be adjacent to each other in the spectrum. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0066] In order to operate on multiple carrier frequencies, the base station 102 and / or the UE 104 are equipped with multiple receivers and / or transmitters. For example, the UE 104 may have two receivers, namely "receiver 1" and "receiver 2", where "receiver 1" is a multi-band receiver that can be tuned to band (i.e., carrier frequency) 'X' or band 'Y', and "receiver 2" is a single-band receiver that can be tuned to only band 'Z'. In this example, if the UE 104 is being served in band 'X', band 'X' will be referred to as the PCell or active carrier frequency, and "receiver 1" will need to tune from band 'X' to band 'Y' (SCell) to measure band 'Y' (and vice versa). In contrast, regardless of whether the UE 104 is being served in band 'X' or band 'Y', due to the separate "receiver 2", the UE 104 can measure band 'Z' without interrupting the service on band 'X' or band 'Y'.

[0067] The wireless communication system 100 may further include a UE 164, which may communicate with the macrocell base station 102 over the communication link 120 and / or communicate with the mmW base station 180 over the mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0068] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In an example, D2D P2P links 192 and 194 can use any well-known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.) to support.

[0069] Figure 2 It is a diagram illustrating an example of a decomposed base station architecture that can be used by the disclosed system for a queue-based C-V2X and DSRC intercommunication solution according to some examples. The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NRBS, a 5G NB, an AP, a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.

[0070] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0071] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0072] As mentioned earlier, Figure 2 A diagram illustrating an example decomposed base station 201 architecture is shown. The decomposed base station 201 architecture may include one or more central units (CUs) 211 that may communicate directly with a core network 223 via a backhaul link, or indirectly with the core network 223 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 227 via an E2 link, or a non-real-time (non-RT) RIC 217 associated with a service management and orchestration (SMO) framework 207, or both. The CU 211 may communicate with one or more distributed units (DUs) 231 via respective midhaul links, such as an F1 interface. The DU 231 may communicate with one or more radio units (RUs) 241 via respective fronthaul links. The RU 241 may communicate with respective UEs 221 via one or more RF access links. In some implementations, a UE 221 may be served simultaneously by multiple RUs 241.

[0073] Each of the units (i.e., CU 211, DU 231, RU 241, and near-RT RIC 227, non-RT RIC 217, and SMO framework 207) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0074] In some aspects, CU 211 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 211. CU 211 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 211 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 211 may be implemented to communicate with DU 131 for network control and signaling.

[0075] DU 231 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 241. In some aspects, DU 231 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 231 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 231 or with control functions hosted by CU 211.

[0076] The lower layer functionality may be implemented by one or more RUs 241. In some deployments, the RU 241 controlled by the DU 231 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 241 may be implemented to handle over-the-air (OTA) communications with one or more UEs 221. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 241 may be controlled by the corresponding DU 231. In some scenarios, this configuration may enable the implementation of the DU 231 and the CU 211 in a cloud-based RAN architecture (such as a vRAN architecture).

[0077] The SMO framework 207 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 207 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 207 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 291) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 211, DU 231, RU 241, and near-RT RIC 227. In some specific implementations, the SMO framework 207 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 213) via the O1 interface. Additionally, in some specific implementations, the SMO framework 207 may communicate directly with one or more RUs 241 via the O1 interface. The SMO framework 207 may also include a non-RT RIC 217 configured to support the functionality of the SMO framework 207 .

[0078] The non-RT RIC 217 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 227. The non-RT RIC 217 may be coupled to or communicate with the near-RT RIC 227 (such as via an A1 interface). The near-RT RIC 227 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 211, one or more DUs 231, or both, and the O-eNB 213 with the near-RT RIC 227.

[0079] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 227, the non-RT RIC 217 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 227 and may be received from a non-network data source or from a network function at the SMO framework 207 or the non-RT RIC 217. In some examples, the non-RT RIC 217 or the near-RT RIC 227 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 217 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 207 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0080] Figure 3 Examples of different communication mechanisms used by various UEs are illustrated. In one example of sidelink communication, Figure 3 The examples illustrate that vehicles 304, 305, and RSU 303 communicate with each other using PC5, DSRC, or other device-to-device direct signaling interfaces. In addition, vehicles 304 and 305 can communicate with base station 302 (shown as BS 302) using a network (Uu) interface. In some examples, base station 302 may include a gNB. Figure 3Also illustrated is that the user equipment 307 uses a network (Uu) interface to communicate with the base station 302. As described below, functionality can be transferred from a vehicle (e.g., vehicle 304) to a user equipment (e.g., user equipment 307) based on one or more characteristics or factors (e.g., temperature, humidity, etc.). In an illustrative example, the V2X functionality can be transferred from the vehicle 304 to the user equipment 307, which can then communicate with other vehicles (e.g., vehicle 305) via a PC5 interface (or other device-to-device direct interface, such as a DSRC interface), as described below. Figure 3 shown.

[0081] Although Figure 3 A specific number of vehicles (e.g., two vehicles 304 and 305) are illustrated as communicating with each other and / or with RSU 303, BS 302, and / or user equipment 307, but the present disclosure is not limited thereto. For example, dozens or hundreds of such vehicles may be communicating with each other and / or with RSU 303, BS 302, and / or user equipment 307. At any given point in time, each such vehicle, RSU 303, BS 302, and / or user equipment 307 may send various types of information as messages to other nearby vehicles, resulting in each vehicle (e.g., vehicles 304 and / or 305), RSU 303, BS 302, and / or user equipment 307 receiving hundreds or thousands of messages per second from other nearby vehicles, RSUs, base stations, and / or other UEs.

[0082] Although in Figure 3 The PC5 interface is shown in FIG. 1 , but various UEs (eg, vehicles, user equipment, etc.) and RSUs may use any suitable type of direct interface such as an 802.11 DSRC interface, a Bluetooth TM For example, a vehicle may communicate with a user equipment through a direct communication interface (e.g., using PC5 and / or DSRC), a vehicle may communicate with another vehicle through a direct communication interface, a user equipment may communicate with another user equipment through a direct communication interface, a UE (e.g., a vehicle, a user equipment, etc.) may communicate with an RSU through a direct communication interface, an RSU may communicate with another RSU through a direct communication interface, and so on.

[0083] Figure 44 is a block diagram of an example of a vehicle computing system 450 for an example vehicle 404. The vehicle 404 is an example of a UE that can communicate with a network (e.g., an eNB, a gNB, a positioning beacon, a position measurement unit, and / or other network entities) via a Uu interface and can communicate with other UEs using V2X communication via a PC5 interface (or other device-to-device direct interface, such as a DSRC interface). As shown, the vehicle computing system 450 may include at least a power management system 451, a control system 452, an infotainment system 454, an intelligent transport system (ITS) 455, one or more sensor systems 456, and a communication system 458. In some cases, the vehicle computing system 450 may include or may be implemented using any type of processing device or system, such as one or more central processing units (CPUs), digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), application processors (APs), graphics processing units (GPUs), visual processing units (VPUs), neural network signal processors (NSPs), microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems.

[0084] The control system 452 may be configured to control one or more operations of the vehicle 404, the power management system 451, the computing system 450, the infotainment system 454, the ITS 455, and / or one or more other systems of the vehicle 404 (e.g., a braking system, a steering system, a safety system other than the ITS 455, a cabin system, and / or other systems). In some examples, the control system 452 may include one or more electronic control units (ECUs). The ECUs may control one or more electrical systems or subsystems in the vehicle. Examples of specific ECUs that may be included as part of the control system 452 include an engine control module (ECM), a powertrain control module (PCM), a transmission control module (TCM), a brake control module (BCM), a central control module (CCM), a central timing module (CTM), and the like. In some cases, the control system 452 may receive sensor signals from one or more sensor systems 456 and may communicate with other systems of the vehicle computing system 450 to operate the vehicle 404.

[0085] The vehicle computing system 450 also includes a power management system 451. In some implementations, the power management system 451 may include a power management integrated circuit (PMIC), a backup battery, and / or other components. In some cases, other systems of the vehicle computing system 450 may include one or more PMICs, batteries, and / or other components. The power management system 451 may perform power management functions for the vehicle 404, such as managing the power supply of the computing system 450 and / or other parts of the vehicle. For example, the power management system 451 may provide a stable power supply in view of power fluctuations (such as based on starting the engine of the vehicle). In another example, the power management system 451 may perform thermal monitoring operations, such as by checking the ambient and / or transistor junction temperature. In another example, the power management system 451 may perform a function based on detecting a certain temperature level, such as causing a cooling system (e.g., one or more fans, an air conditioning system, etc.) to cool certain components of the vehicle computing system 450 (e.g., the control system 452, such as one or more ECUs), shutting down certain functionality of the vehicle computing system 450 (e.g., limiting the infotainment system 454, such as by turning off one or more displays, disconnecting from a wireless network, etc.), and other functions.

[0086] The vehicle computing system 450 also includes a communication system 458. The communication system 458 may include a communication system for communicating with the network (e.g., to a gNB or other network entity via a Uu interface) and / or to other UEs (e.g., via a PC5 interface, a WiFi interface (e.g., DSRC), a Bluetooth TM interfaces and / or other wireless and / or wired interfaces to another vehicle or UE) and to receive signals from the network (e.g., from a gNB or other network entity via a Uu interface) and / or from other UEs (e.g., via a PC5 interface, a WiFi interface (e.g., DSRC), Bluetooth TM For example, the communication system 458 is configured to communicate with the user via any suitable wireless network (e.g., 3G network, 4G network, 5G network, WiFi network, Bluetooth network, etc.). TMThe communication system 458 includes various components or devices for performing wireless communication functionality, including an original equipment manufacturer (OEM) subscriber identity module (referred to as a SIM or SIM card) 460, a user SIM 462, and a modem 464. Although the vehicle computing system 450 is shown as having two SIMs and one modem, in some implementations, the computing system 450 can have any number of SIMs (e.g., one SIM or more than two SIMs) and any number of modems (e.g., one modem, two modems, or more than two modems).

[0087] A SIM is a device (e.g., an integrated circuit) that can securely store an International Mobile Subscriber Identity (IMSI) number and associated keys (e.g., encryption-decryption keys) for a particular subscriber or user. The IMSI and keys can be used to identify and authenticate a subscriber on a particular UE. The OEM SIM 460 can be used by the communication system 458 to establish a wireless connection for vehicle-based operations, such as for emergency call (eCall) functions, for communicating with the vehicle manufacturer's communication system (e.g., for software updates, etc.), and other operations. The OEM SIM 460 can be very important for the OEM SIM to support critical services, such as eCall for making emergency calls in the event of a car accident or other emergency. For example, eCall can include services that automatically dial an emergency number (e.g., "9-1-1" in the United States, "1-1-2" in Europe, etc.) in the event of a vehicle accident, and communicate the location of the vehicle to emergency services (such as police, fire, etc.).

[0088] User SIM 462 may be used by communication system 458 to perform wireless network access functions to support user data connections (e.g., for making phone calls, messaging, infotainment-related services, etc.). In some cases, the user's user device may be connected to the user's wireless network through an interface (e.g., via PC5, Bluetooth TM , Wi-Fi TMThe user device may be connected to the vehicle computing system 450 by a wireless communication system (e.g., DSRC), a universal serial bus (USB) port, and / or other wireless or wired interface. Once connected, the user device may transfer the wireless network access functionality from the user device to the communication system 458 of the vehicle, in which case the user device may stop performing the wireless network access functionality (e.g., during the time period when the communication system 458 is performing the wireless access functionality). The communication system 458 may begin interacting with the base station to perform one or more wireless communication operations, such as facilitating a phone call, sending and / or receiving data (e.g., messaging, video, audio, etc.), and other operations. In such a case, other components of the vehicle computing system 450 may be used to output data received by the communication system 458. For example, the infotainment system 454 (described below) may display video received by the communication system 458 on one or more displays, and / or may use one or more speakers to output audio received by the communication system 458.

[0089] A modem is a device that modulates one or more carrier signals to encode digital information for transmission, and demodulates the signals to decode the transmitted information. Modem 464 (and / or one or more other modems of communication system 458) may be used for data communication of OEM SIM 460 and / or user SIM 462. In some examples, modem 464 may include a 4G (or LTE) modem, and another modem (not shown) of communication system 458 may include a 5G (or NR) modem. In some examples, communication system 458 may include one or more Bluetooth TM Modem (e.g. for Bluetooth TM Low Energy (BLE) or other types of Bluetooth communication), one or more WiFi TM modems (e.g., for DSRC communications and / or other WiFi communications), broadband modems (e.g., ultra-wideband (UWB) modems), any combination thereof, and / or other types of modems.

[0090] In some cases, modem 464 (and / or one or more other modems of communication system 458) may be used to perform V2X communications (e.g., with other vehicles for V2V communications, with other devices for D2D communications, with infrastructure systems for V2I communications, with pedestrian UEs for V2P communications, etc.). In some examples, communication system 458 may include a V2X modem for performing V2X communications (e.g., sidelink communications via a PC5 interface or a DSRC interface), in which case the V2X modem may be separate from one or more modems used for wireless network access functions (e.g., for network communications via a network / Uu interface and / or sidelink communications in addition to V2X communications).

[0091] In some examples, the communication system 458 may be or may include a telematics control unit (TCU). In some implementations, the TCU may include a network access device (NAD) (also referred to as a network control unit or NCU in some cases). The NAD may include a modem 464, Figure 4 460, user SIM 462, and / or other components for wireless communication not shown in the figure. In some examples, communication system 458 may include a global navigation satellite system (GNSS). In some cases, GNSS may be part of one or more sensor systems 456, as described below. GNSS may provide vehicle computing system 450 with the ability to perform one or more location services, navigation services, and / or other services that may utilize GNSS functionality.

[0092] In some cases, the communication system 458 may also include one or more wireless interfaces for sending and receiving wireless communications (e.g., including one or more transceivers and one or more baseband processors for each wireless interface), one or more wired interfaces for performing communications via one or more hardwired connections (e.g., serial interfaces such as universal serial bus (USB) inputs, lighting connectors, and / or other wired interfaces), and / or other components that may allow the vehicle 404 to communicate with a network and / or other UEs.

[0093] The vehicle computing system 450 may also include an infotainment system 454 that can control content and one or more output devices of the vehicle 404 that can be used to output content. The infotainment system 454 may also be referred to as an in-vehicle infotainment (IVI) system or an in-car entertainment (ICE) system. The content may include navigation content, media content (e.g., video content, music or other audio content, and / or other media content), and other content. One or more output devices may include one or more graphical user interfaces, one or more displays, one or more speakers, one or more extended reality devices (e.g., VR, AR and / or MR headsets), one or more tactile feedback devices (e.g., one or more devices configured to vibrate seats, steering wheels and / or other parts of the vehicle 404) and / or other output devices.

[0094] In some examples, computing system 450 may include intelligent transport system (ITS) 455. In some examples, ITS 455 may be used to implement V2X communication. For example, an ITS stack of ITS 455 may generate V2X messages based on information from an application layer of the ITS. In some cases, the application layer may determine whether certain conditions have been met to generate messages for use by ITS 455 and / or generate messages to be transmitted to other vehicles (for V2V communication), pedestrian UEs (for V2P communication), and / or infrastructure systems (for V2I communication). In some cases, communication system 458 and / or ITS 455 may obtain vehicle access network (CAN) information (e.g., from other components of the vehicle via a CAN bus). In some examples, communication system 458 (e.g., TCU NAD) may obtain CAN information via a CAN bus and may transmit the CAN information to the PHY / MAC layer of ITS 455. ITS 455 may provide CAN information to the ITS stack of ITS 455. The CAN information may include vehicle-related information, such as the vehicle's heading, the vehicle's speed, braking information, and other information. The CAN information may be provided to the ITS 455 continuously or periodically (eg, every 1 millisecond (ms), every 10 ms, etc.).

[0095] The conditions for determining whether to generate a message may be determined using CAN information based on safety-related applications and / or other applications (including applications related to road safety, traffic efficiency, infotainment, business, and / or other applications). In an illustrative example, ITS 455 may perform lane change assistance or negotiation. For example, using CAN information, ITS 455 may determine that the driver of vehicle 404 is attempting to change lanes from the current lane to an adjacent lane (e.g., based on flashing lights being activated, based on the user turning or turning to an adjacent lane, etc.). Based on determining that vehicle 404 is attempting to change lanes, ITS 455 may determine that a lane change condition has been met, which is associated with a message to be transmitted to other vehicles near the vehicle in the adjacent lane. ITS 455 may trigger the ITS stack to generate one or more messages to send to other vehicles, which may be used to negotiate lane changes with other vehicles. Other examples of applications include forward collision warning, automatic emergency braking, lane departure warning, pedestrian avoidance or protection (e.g., when a pedestrian is detected near the vehicle 404, such as based on V2P communication with the user's UE), traffic sign recognition, etc.

[0096] The ITS 455 may generate messages (e.g., V2X messages) using any suitable protocol. Examples of protocols that the ITS 455 may use include one or more Society of Automotive Engineers (SAE) standards (such as SAE J2735, SAE J2945, SAE J3161, and / or other standards), which are hereby incorporated by reference in their entirety and for all purposes.

[0097] The security layer of ITS 455 can be used to securely sign messages from the ITS stack that are transmitted to and verified by other UEs configured for V2X communication, such as other vehicles, pedestrian UEs, and / or infrastructure systems. The security layer can also verify messages received from such other UEs. In some specific implementations, the signing and verification process can be based on the security context of the vehicle. In some examples, the security context may include one or more encryption-decryption algorithms, public and / or private keys used to generate signatures using encryption-decryption algorithms, and / or other information. For example, each ITS message generated by ITS 455 can be signed by the security layer of ITS 455. The signature can be derived using a public key and an encryption-decryption algorithm. The vehicle, pedestrian UE, and / or infrastructure system that receives the signed message can verify the signature to ensure that the message comes from an authorized vehicle. In some examples, one or more encryption-decryption algorithms may include one or more symmetric encryption algorithms (e.g., Advanced Encryption Standard (AES), Data Encryption Standard (DES), and / or other symmetric encryption algorithms), one or more asymmetric encryption algorithms using public and private keys (e.g., Levitt-Shamir-Adleman (RSA) and / or other asymmetric encryption algorithms), and / or other encryption-decryption algorithms.

[0098] In some examples, the ITS 455 may determine certain operations to be performed (e.g., V2X-based operations) based on messages received from other UEs. These operations may include safety-related and / or other operations, such as operations for road safety, traffic efficiency, infotainment, business, and / or other applications. In some examples, these operations may include causing the vehicle (e.g., the control system 452) to perform automatic functions, such as automatic braking, automatic steering (e.g., maintaining a forward direction in a particular lane), automatic lane change negotiation with other vehicles, and other automatic functions. In an illustrative example, the communication system 458 may receive a message from another vehicle (e.g., via a PC5 interface, a DSRC interface, or other device-to-device direct interface) indicating that the other vehicle is about to stop suddenly. In response to receiving the message, the ITS stack may generate a message or instruction, and may transmit the message or instruction to the control system 452, which may cause the control system 452 to automatically brake the vehicle 404 so that it stops before colliding with the other vehicle. In other illustrative examples, these operations may include triggering the display of a message warning the driver that another vehicle is in a lane adjacent to the vehicle, a message warning the driver to stop the vehicle, a message warning the driver that pedestrians are at an upcoming intersection, a message warning the driver that a toll booth is within a certain distance of the vehicle (e.g., within 1 mile), and the like.

[0099] In some examples, ITS 455 may receive a large number of messages from other UEs (e.g., vehicles, RSUs, etc.), in which case ITS 455 will authenticate (e.g., decode and decrypt) each of the messages and / or determine which operations to perform. This large number of messages may result in a large computational load on the vehicle computing system 450. In some cases, the large computational load may result in an increase in the temperature of the computing system 450. The increase in the temperature of the components of the computing system 450 may adversely affect the ability of the computing system 450 to handle a large number of incoming messages. One or more functionalities may be transferred from the vehicle 404 to another device (e.g., user equipment, RSU, etc.) based on the temperature of the vehicle computing system 450 (or its components) exceeding or approaching one or more thermal levels. Transferring one or more functionalities may reduce the computational load on the vehicle 404, helping to reduce the temperature of the components. A thermal load balancer may be provided that enables the vehicle computing system 450 to perform thermal-based load balancing to control the processing load, depending on the temperature of the computing system 450 and the processing power of the vehicle computing system 450.

[0100] The computing system 450 also includes one or more sensor systems 456 (e.g., a first sensor system to an Nth sensor system, where N is a value equal to or greater than 0). When multiple sensor systems are included, the sensor systems 456 may include different types of sensor systems that may be arranged on or in different parts of the vehicle 404. The sensor systems 456 may include one or more camera sensor systems, LIDAR sensor systems, radio detection and ranging (RADAR) sensor systems, electromagnetic detection and ranging (EmDAR) sensor systems, sound navigation and ranging (SONAR) sensor systems, sound detection and ranging (SODAR) sensor systems, global navigation satellite systems (GNSS) receiver systems (e.g., one or more global positioning system (GPS) receiver systems), accelerometers, gyroscopes, inertial measurement units (IMUs), infrared sensor systems, laser rangefinder systems, ultrasonic sensor systems, infrasound sensor systems, microphones, any combination thereof, and / or other sensor systems. It should be understood that any number of sensors or sensor systems may be included as part of the computing system 450 of the vehicle 404.

[0101] Although the vehicle computing system 450 is shown as including certain components and / or systems, one of ordinary skill in the art will appreciate that the vehicle computing system 450 may include more than Figure 4Those components shown are more or less. For example, the vehicle computing system 450 may also include one or more input devices and one or more output devices (not shown). In some specific implementations, the vehicle computing system 450 may also include (for example, as part of or separate from the control system 452, the infotainment system 454, the communication system 458 and / or the sensor system 456) at least one processor and at least one memory having computer executable instructions executed by the at least one processor. At least one processor communicates with at least one memory and / or is electrically connected to (referred to as "coupled to" or "communicatively coupled to") at least one memory. At least one processor may include, for example, one or more microcontrollers, one or more central processing units (CPUs), one or more field programmable gate arrays (FPGAs), one or more graphics processing units (GPUs), one or more application processors (for example, for running or executing one or more software applications) and / or other processors. At least one memory may include, for example, a read-only memory (ROM), a random access memory (RAM) (for example, a static RAM (SRAM)), an electrically erasable programmable read-only memory (EEPROM), a flash memory, one or more buffers, one or more databases and / or other memories. Computer-executable instructions stored in or on at least the memory may be executed to perform one or more functions or operations described herein.

[0102] Figure 5 An example of a computing system 570 of a user device 507 is illustrated. The user device 507 is an example of a UE that can be used by an end user. For example, the user device 507 may include a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smart watch, glasses, XR devices, etc.), an Internet of Things (IoT) device, and / or other devices used by the user to communicate through a wireless communication network. The computing system 570 includes software and hardware components that can be electrically coupled or communicatively coupled via a bus 589 (or can communicate in other ways, as the case may be). For example, the computing system 570 includes one or more processors 584. The one or more processors 584 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems. The bus 589 may be used by one or more processors 584 to communicate between cores and / or with one or more memory devices 586.

[0103] The computing system 570 may also include one or more memory devices 586, one or more digital signal processors (DSPs) 582, one or more SIMs 574, one or more modems 576, one or more wireless transceivers 578, an antenna 587, one or more input devices 572 (e.g., a camera, a mouse, a keyboard, a touch-sensitive screen, a touchpad, a keypad, a microphone, etc.), and one or more output devices 580 (e.g., a display, a speaker, a printer, etc.).

[0104] The one or more wireless transceivers 578 can receive data from one or more other devices (such as other user devices, vehicles (e.g., the above-mentioned Figure 4 The computing system 570 may include multiple antennas. The wireless signal 588 may be sent via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunication network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a WiFi network), a Bluetooth network, etc. TM network and / or other networks. In some examples, one or more wireless transceivers 578 may include an RF front end that includes one or more components such as an amplifier, a mixer for down-converting a signal (also known as a signal multiplier), a frequency synthesizer (also known as an oscillator) that provides a signal to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, and other components. The RF front end generally handles the selection of wireless signals 588 and the conversion of the wireless signals to baseband or intermediate frequencies, and may convert RF signals to the digital domain.

[0105] In some cases, computing system 570 may include a coding-decoding device (or CODEC) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 578. In some cases, computing system 570 may include an encryption-decryption device or component configured to encrypt and / or decrypt (e.g., in accordance with the AES and / or DES standards) data transmitted and / or received by one or more wireless transceivers 578.

[0106] One or more SIMs 574 can each securely store an IMSI number and associated keys assigned to a user of the user device 507. As noted above, the IMSI and keys can be used to identify and authenticate a subscriber when accessing a network provided by a network service provider or operator associated with one or more SIMs 574. One or more modems 576 can modulate one or more signals to encode information for transmission using one or more wireless transceivers 578. One or more modems 576 can also demodulate signals received by one or more wireless transceivers 578 to decode the transmitted information. In some examples, one or more modems 576 may include a 4G (or LTE) modem, a 5G (or NR) modem, a modem configured for V2X communication, and / or other types of modems. One or more modems 576 and one or more wireless transceivers 578 can be used to communicate data of one or more SIMs 574.

[0107] The computing system 570 may also include (and / or communicate with) one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 586), which may include, but are not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, and / or the like. Such storage devices may be configured to implement any suitable data storage, including, but not limited to, various file systems, database structures, etc.

[0108] In various aspects, the functionality may be stored as one or more computer program products (e.g., instructions or code) in the memory device 586 and executed by the one or more processors 584 and / or the one or more DSPs 582. The computing system 570 may also include software elements (e.g., located within the one or more memory devices 586) including, for example, an operating system, device drivers, executable libraries, and / or other code, such as one or more applications, which may include a computer program that implements the functionality provided by various aspects, and / or may be designed to implement methods and / or configure systems, as described herein.

[0109] Figure 6An example 600 of wireless communication between devices based on sidelink communication (such as V2X or other D2D communication) is illustrated. The communication can be based on a time slot structure. For example, a transmitting UE 602 can send a transmission 614 that can be received by a receiving UE 604, 606, 608, which includes, for example, a control channel and / or a corresponding data channel. At least one UE may include an autonomous vehicle or an unmanned aerial vehicle. The control channel may include information for decoding the data channel and may also be used by the receiving device to avoid interference by avoiding transmission on the occupied resources during data transmission. The number of TTIs and RBs occupied by the data transmission may be indicated in a control message from the transmitting device. In addition to operating as a receiving device, each of the UEs 602, 604, 606, 608 may also be able to operate as a transmitting device. Therefore, the UEs 606, 608 are illustrated as transmitting 616, 620. The transmissions 614, 616, 620 (and 618 by RSU 607) may be broadcast or multicast to nearby devices. For example, UE 614 may transmit communications intended to be received by other UEs within range 601 of UE 614. Additionally / alternatively, RSU 607 may receive communications 618 from and / or transmit communications to UE 602, 604, 606, 608. UE 602, 604, 606, 608 or RSU 607 may include a detection component. UE 602, 604, 606, 608 or RSU 607 may also include a BSM or mitigation component.

[0110] In wireless communications (such as V2X communications), a V2X entity may perform sensor sharing with other V2X entities to achieve collaboration and autonomous driving. Fig. 7A 700, a host vehicle (HV) 702 may detect multiple items within its environment. For example, at block 732, the HV 702 may detect the presence of a non-V2X entity (NV) 706. The HV 702 may notify other entities (such as a first remote vehicle (RV1) 704 or a roadside unit (RSU) 708) of the presence of the NV 706, provided that the RV1 704 and / or RSU 708 itself cannot detect the NV 706. The HV 702 notifies the RV1 704 and / or RSU 708 that the NV 706 is a sharing of sensor information. Figure 7B 710, HV 702 may detect a physical obstacle 712 (such as a pothole, debris, or an object that may be an obstacle in the path of HV 702 and / or RV1 704 that has not yet been detected by RV1 704 and / or RSU 708). HV 702 may notify RV1 and / or RSU 708 of the obstacle 712 so that the obstacle 712 can be avoided. Figure 7C720, the HV 702 may detect the presence of a vulnerable road user (VRU) 722 and may share the detection of the VRU 722 with the RV1 704 and the RSU 708 in instances where the RSU 708 and / or the RV1 704 may not be able to detect the VRU 722. Fig.7D 730, the HV, upon detecting a nearby entity (e.g., NV, VRU, obstacle), may send a sensor data sharing message (SDSM) 734 to the RV and / or RSU to share the detection of the entity. The SDSM 734 may be a broadcast message such that any receiving device in the vicinity of the HV may receive the message. In some instances, the shared information may be relayed to other entities, such as the RV. For example, referring to Figure 8 800, the HV 802 may detect the presence of the NV 806 and / or the VRU 822. The HV 802 may broadcast the SDSM 810 to the RSU 808 to report the detection of the NV 806 and / or the VRU 822. The RSU 808 may relay the SDSM 810 received from the HV 802 to the remote vehicle so that the remote vehicle is aware of the presence of the NV 806 and / or the VRU 822. For example, the RSU 808 may send the SDSM 812 to the RV1 804, wherein the SDSM 812 includes information related to the detection of the NV 806 and / or the VRU 822.

[0111] Fig. 9 is a diagram illustrating an example of a system 900 for sensor sharing in wireless communications (e.g., C-V2X communications) according to some aspects of the present disclosure. Fig. 9 In FIG. 1 , system 900 is shown as including a plurality of equipped (e.g., V2X-enabled) network devices. The plurality of equipped network devices include vehicles (e.g., cars) 910a, 910b, 910c, 910d, and RSU 905. Also shown are a plurality of unequipped network devices, including unequipped vehicles 920, VRUs (e.g., cyclists) 930, and pedestrians 940. System 900 may include Fig. 9 , and / or more or fewer equipped network devices and / or more or fewer unequipped network devices. In addition, system 900 may include more than Fig. 9 More or fewer different types of equipped network devices (e.g., which may include equipped UEs) and / or more or fewer different types of unequipped network devices (e.g., which may include unequipped UEs) are shown in the examples. In addition, in one or more examples, the equipped network devices may be equipped with heterogeneous capabilities, which may include but are not limited to C-V2X / DSRC capabilities, 4G / 5G cellular connectivity, GPS capabilities, camera capabilities, radar capabilities, and / or LIDAR capabilities.

[0112] Multiple equipped network devices may be able to perform V2X communications. In addition, at least some of the equipped network devices are configured to send and receive sensing signals for radar (e.g., RF sensing signals) and / or LIDAR sensing signals (e.g., optical sensing signals) to detect nearby vehicles and / or objects. Additionally or alternatively, in some cases, at least some of the equipped network devices are configured to use one or more cameras to detect nearby vehicles and / or objects (e.g., by processing images captured by the one or more cameras to detect these vehicles / objects). In one or more examples, vehicles 910a, 910b, 910c, 910d and RSU 905 may be configured to send and receive certain sensing signals (e.g., radar and / or LIDAR sensing signals).

[0113] In some examples, some of the equipped network devices may have higher-capability sensors (e.g., GPS receivers, cameras, RF antennas, and / or optical lasers and / or optical sensors) than other equipped network devices of the system 900. For example, the vehicle 910b may be a luxury vehicle and therefore have more expensive, higher-capability sensors than other vehicles that are economical vehicles. In an illustrative example, the vehicle 910b may have one or more LIDAR sensors (e.g., high-capability optical lasers and optical sensors) with higher capabilities than other equipped network devices in the system 900. In an illustrative example, the LIDAR of the vehicle 910b may be able to detect VRUs (e.g., cyclists) 930 and / or pedestrians 940 with a large confidence (e.g., seventy percent confidence). In another example, the vehicle 910b may have a radar (e.g., a high-capability RF antenna) with higher capabilities than other equipped network devices in the system 900. For example, the radar of vehicle 910b may be able to detect VRU (e.g., bicyclist) 930 and / or pedestrian 940 with a certain confidence level (e.g., eighty-five percent confidence level). In another example, vehicle 910b may have a higher-capable camera (e.g., having higher resolution capabilities, higher frame rate capabilities, better lenses, etc.) than other network devices equipped in system 900.

[0114] During operation of the system 900, the equipped network devices (e.g., at least one of the vehicles 910a, 910b, 910c, 910d and / or the RSU 905) may send and / or receive sensing signals (e.g., RF and / or optical signals) to sense and detect vehicles (e.g., vehicles 910a, 910b, 910c, 910d, and 920) and / or objects (e.g., VRU 930 and pedestrian 940) located in and around the road. The equipped network devices (e.g., at least one of the vehicles 910a, 910b, 910c, 910d and / or the RSU 905) may then use the sensing signals to determine the characteristics (e.g., motion, size, type, heading, and speed) of the detected vehicles and / or objects. An equipped network device (e.g., at least one of the vehicles 910a, 910b, 910c, 910d and / or the RSU 905) may generate at least one vehicle-based message 915 (e.g., a C-V2X message, such as a sensor data sharing message (SDSM), a basic safety message (BSM), a collaborative awareness message (CAM), a collective awareness message (CPM), and / or other types of messages) that includes information related to the determined characteristics of the detected vehicles and / or objects.

[0115] The vehicle-based message 915 may include information related to the detected vehicle or object (e.g., the location of the vehicle or object, the accuracy of the location, the speed of the vehicle or object, the direction in which the vehicle or object is traveling, and / or other information related to the vehicle or object), traffic conditions (e.g., low-speed and / or dense traffic, high-speed traffic, information related to accidents, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency or "regular" message, etc.), road topology (line of sight (LOS) or non-LOS (NLOS), etc.), any combination thereof, and / or other information. In some examples, the vehicle-based message 915 may also include information about the preferences of the equipped network device for receiving vehicle-based messages from certain other equipped network devices. In some cases, the vehicle-based message 915 may include the current capabilities of the equipped network device (e.g., vehicles 910a, 910b, 910c, 910d), such as the sensing capabilities of the equipped network device (which may affect the accuracy with which the equipped network device senses the vehicle and / or objects), the processing capabilities, the thermal state of the equipped network device (which may affect the ability of the vehicle to process data), and the health status of the equipped network device.

[0116] In some aspects, the vehicle-based message 915 may include a dynamic neighbor list (also referred to as a local dynamic map (LDM) or dynamic surrounding map) for each of the equipped network devices (e.g., vehicles 910a, 910b, 910c, 910d and RSU 905). For example, each dynamic neighbor list may include a list of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device. In some cases, each dynamic neighbor list includes a map of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device, which may include road and terrain topology.

[0117] In some implementations, the vehicle-based message 915 may include a specific use case or safety warning related to the current status of the equipped network device (e.g., vehicles 910a, 910b, 910c, 910d), such as a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW). In some examples, the vehicle-based message 915 may take the form of a standard Basic Safety Message (BSM), a Collaborative Awareness Message (CAM), a Collective Awareness Message (CPM), a Sensor Data Sharing Message (SDSM) (e.g., SAE J3224 SDSM), and / or other formats.

[0118] Fig.10 is an example of a vehicle-based message (e.g., Fig. 9 FIG1000 is a diagram of an example of a vehicle-based message 915 of FIG1000 . The vehicle-based message 915 is shown as a sensor sharing message (e.g., SDSM), but may include a BSM, CAM, CPM, or other vehicle-based message as described herein. Fig.10, a vehicle-based message 915 is shown as including host data 1020 and detected object data 1010a, 1010b. The host data 1020 of the vehicle-based message 915 may include information related to a sending device of the vehicle-based message 915 (e.g., a network entity such as a sending device of the RSU 905 or an on-board unit (OBU) such as on the vehicles 910a, 910b, 910c, 910d). The detected object data 1010a, 1010b of the vehicle-based message 915 may include information related to a detected vehicle or object (e.g., static or dynamic characteristics related to the detected vehicle or object, and / or other information related to the detected vehicle or object). Specifically, the detected object data 1010a, 1010b may include detected object CommonData, detected object VehicleData, detected object VRUData, detected obstacle ObstacleData, and detected object MisbehavingVehicleData.

[0119] These vehicle-based messages 915 are beneficial because they can provide a means for equipping network devices (e.g., Fig. 9 The vehicles 910a, 910b, 910c, 910d) provide perception and understanding of upcoming potential road hazards (e.g., unforeseen oncoming vehicles, accidents, and road conditions).

[0120] Fig.11 1 is a diagram illustrating an example of a system 1100 that employs a roadside unit (RSU) 1120 as a bridge to communicate between vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f equipped for different types of communication protocols (e.g., C-V2X and DSRC communication protocols) according to some aspects of the present disclosure. Fig.11 In the embodiment, system 1100 is shown as including a plurality of network devices (e.g., UEs, such as vehicles) equipped (e.g., supporting C-V2X and / or supporting DSRC). The plurality of network devices include vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f (e.g., cars) and RSU 1120. System 1100 may include Fig.11 In addition, the system 1100 may also include unequipped network devices, such as unequipped vehicles, VRUs (e.g., cyclists), and / or pedestrians. In addition, the system 1100 may include more or less equipped network devices as shown in FIG. Fig.11More or fewer different types of equipped network devices (e.g., which may include equipped UEs) as shown in . In addition, in one or more examples, the equipped network devices may be equipped with heterogeneous capabilities, which may include, but are not limited to, C-V2X and DSRC capabilities, 4G and 5G cellular connectivity, GPS capabilities, camera capabilities, radar capabilities, LIDAR capabilities, any other combination thereof, and / or other types of communication protocols. Although C-V2X and DSRC are used to describe examples herein for illustrative purposes, these systems and techniques are applicable to other types of communication protocols, such as 4G and 5G cellular connectivity, etc.

[0121] The multiple equipped network devices may be able to perform communications (e.g., C-V2X and / or DSRC communications) with each other. Vehicles 1110b, 1110d, 1110f may be equipped to perform C-V2X communications to utilize the C-V2X side link PC5 interface to communicate with other vehicles similarly equipped for C-V2X communications (e.g., send and / or receive vehicle-based messages, such as safety and perception messages and warnings). Vehicle 1110d, one of these vehicles, may also be equipped for DSRC communications to utilize an 802.11p-based DSRC interface to communicate with other vehicles similarly equipped for DSRC communications (e.g., vehicles 1110a, 1110c, 1110e) (e.g., send and / or receive vehicle-based messages). Vehicle 1110d that may have such dual communication capabilities may be referred to as having heterogeneous C-V2X / DSRC communication capabilities. Similar to the vehicle 1110d, the RSU 1120 may be equipped to perform both C-V2X communications to communicate using the C-V2X side link PC5 interface and DSRC communications to utilize the 802.11p-based DSRC interface.

[0122] The vehicles 1110a, 1110c, 1110e within the system 1100 may be equipped only for DSRC communication to utilize an 802.11p-based DSRC interface to communicate (e.g., send and / or receive vehicle-based messages) with other vehicles similarly equipped for DSRC communication. Therefore, the vehicles 1110a, 1110c, 1110e that may be equipped only for DSRC communication may not be able to communicate directly with the vehicles 1110b, 1110f that are not equipped for DSRC communication. Therefore, the vehicle-based messages (e.g., safety, perception and / or warning messages) generated by the vehicles 1110a, 1110c, 1110e that are equipped only for DSRC communication may not be easily received by the vehicles 1110b, 1110f that may be equipped only for C-V2X communication. Similarly, vehicle-based messages (e.g., safety, perception, and / or warning messages) generated by vehicles 1110b, 1110f that may be equipped only for C-V2X communications may not be easily received by vehicles 1110a, 1110c, 1110e that may be equipped only for DSRC communications.

[0123] In addition, at least some of the equipped network devices (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120) are configured to send and receive sensing signals of radar (e.g., RF sensing signals) and / or sensing signals of LIDAR (e.g., optical sensing signals) to detect nearby vehicles and / or objects. Additionally or alternatively, in some cases, at least some of the equipped network devices are configured to use one or more cameras to detect nearby vehicles and / or objects (e.g., by processing images captured by the one or more cameras to detect these vehicles / objects). In one or more examples, vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120 may be configured to send and receive certain sensing signals (e.g., radar and / or LIDAR sensing signals).

[0124] During operation of the system 1100, the equipped network devices (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120) may send and / or receive sensing signals (e.g., RF and / or optical signals) to sense and detect vehicles (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f) and / or objects (e.g., RSU 1120) located in and around the road. The equipped network devices (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120) may then use the sensing signals to determine characteristics (e.g., motion, size, type, heading, and speed) of the detected vehicles and / or objects. The equipped network devices (eg, vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120) may generate at least one vehicle-based message (eg, Fig.10 The vehicle-based messages 915) may include C-V2X messages such as sensor data sharing messages (SDSM), basic safety messages (BSM), collaborative awareness messages (CAM), collective awareness messages (CPM), and / or other types of messages. The vehicle-based messages may include information related to the determined characteristics of the detected vehicles and / or objects.

[0125] The vehicle-based message 915 may include information related to the detected vehicle or object (e.g., the location of the vehicle or object, the accuracy of the location, the speed of the vehicle or object, the direction in which the vehicle or object is traveling, and / or other information related to the vehicle or object), traffic conditions (e.g., low-speed and / or dense traffic, high-speed traffic, information related to accidents, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency or "regular" message, etc.), road topology (line of sight (LOS) or non-LOS (NLOS), etc.), any combination thereof, and / or other information. In some examples, the vehicle-based message 915 may also include information about the preferences of the equipped network device for receiving vehicle-based messages from certain other equipped network devices. In some cases, the vehicle-based message 915 may include the current capabilities of the equipped network device (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f), such as the sensing capabilities of the equipped network device (which may affect the accuracy with which the equipped network device senses the vehicle and / or objects), the processing capabilities, the thermal state of the equipped network device (which may affect the ability of the vehicle to process data), and the health status of the equipped network device.

[0126] In some aspects, the vehicle-based message 915 may include a dynamic neighbor list (also referred to as a local dynamic map (LDM) or dynamic surrounding map) for each of the equipped network devices (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120). For example, each dynamic neighbor list may include a list of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device. In some cases, each dynamic neighbor list includes a map of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device, which may include road and terrain topology.

[0127] In some implementations, the vehicle-based message 915 may include a specific use case or safety warning related to the current status of the equipped network device (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f), such as a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW). In some examples, the vehicle-based message 915 may take the form of a standard Basic Safety Message (BSM), a Collaborative Awareness Message (CAM), a Collective Awareness Message (CPM), a Sensor Data Sharing Message (SDSM) (e.g., SAE J3224 SDSM), and / or other formats.

[0128] In one or more examples, an equipped network device (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120) may send a vehicle-based message (e.g., vehicle-based message 915) to other equipped network devices (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120) via a message signal (e.g., message signals 1130a, 1130b, 1130c, 1140a, 1140b, 1140c, 1140d) to provide a vehicle-based message to other equipped network devices (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e, 1110f, and RSU 1120). 1120) provides situational awareness (e.g., awareness of potential upcoming road hazards and / or obstacles). Fig.11 in, and in Fig.12 , Fig.13A , Fig. 13B , Fig.14A and Fig. 14B In the example, the message signal represented by the solid line (e.g., Fig.11The message signals 1130a, 1130b, 1130c) may be sent via C-V2X communication, and the message signals represented by the dashed lines (e.g., Fig.11 The message signals 1140a, 1140b, 1140c, 1140d) can be sent via C-V2X communication.

[0129] For example, Fig.11 As shown, both vehicle 1110b and RSU 1120 may send message signals 1130a to each other via C-V2X communication, and both vehicle 1110d and vehicle 1110f may send message signals 1130c to each other via C-V2X communication. Fig.11 , both the vehicle 1110c and the RSU 1120 may send a message signal 1140a to each other via DSRC communication, both the vehicle 1110c and the vehicle 1110d may send a message signal 1140b to each other via DSRC communication, and both the vehicle 1110c and the vehicle 1110e may send a message signal 1140d to each other via DSRC communication. In addition, both the vehicle 1110d and the RSU 1120 may send the message signals 1130b, 1140c to each other via both C-V2X communication (e.g., for the message signal 1130b) and DSRC communication (e.g., for the message signal 1140c).

[0130] In some cases, the RSU 1120, which may be capable of both C-V2X and DSRC communications, may operate as a bridge (or repeater) to relay message signals (e.g., which include vehicle-based messages) to equipped network devices that cannot directly communicate with other equipped network devices. For example, since vehicle 1110c is only capable of DSRC communications and vehicle 1110b is only capable of C-V2X communications, vehicle 1110c and vehicle 1110b cannot directly communicate vehicle-based messages to each other. In this case, the RSU 1120 may act as a repeater to relay message signals to and from both vehicles 1110c and 1110b. For this example, vehicle 1110c may send message signal 1140a (e.g., including a vehicle-based message from vehicle 1110c) to RSU 1120 via DSRC communications. RSU 1120 may then send a message signal 1130a (e.g., containing a vehicle-based message from vehicle 1110c) to vehicle 1110b via C-V2X communication. Using RSU 1120 as a bridge requires the use of many additional message signals, which may cause congestion in the channel. In addition, RSU 1120 has the following limitation: it must be within the communication range of the vehicle to be able to operate as a bridge between vehicles. In addition, Fig.11 In the embodiment of the present invention, each vehicle in the system capable of both C-V2X communication and DSRC communication (e.g., vehicle 1110d) can actively transmit via both C-V2X communication and DSRC communication. The transmission of all these signals (e.g., the transmission of too many signals via DSRC communication) can also cause congestion in the channel.

[0131] The present disclosure provides a queue-based communication protocol intercommunication solution (e.g., intercommunication between C-V2X and DSRC protocols) to reduce unnecessary congestion in a channel. For example, a queue may be formed by a grouping of vehicles capable of at least C-V2X communication, wherein at least one of the vehicles in the queue is selected or determined to act as a queue head or leader. The queue head of the queue is capable of both C-V2X and DSRC communications and may act as a bridge between vehicles (e.g., similar to a Fig.11 The RSU 1120 in the queue is used for C-V2X and DSRC communication of message signals. When the queue head acts as a bridge, other vehicles in the queue (e.g., which may be referred to as queue members) may stop transmitting via DSRC communication, which allows reducing congestion in the channel. Fig.12 , Fig.13A , Fig. 13B , Fig.14A , Fig. 14B , Fig.15 and Fig.16 The formation and operation of trains for C-V2X and DSRC communications between vehicles are discussed in detail.

[0132] Fig.12 1 is a diagram of a disclosed system 1200 for a queue-based C-V2X and DSRC interworking solution according to some aspects of the present disclosure, wherein some vehicles 1110b, 1110d, 1110f within the system 1200 are collaboratively negotiating (e.g., via signals 1230a, 1230b) the formation of a queue. Specifically, Fig.12 In the embodiment, the system 1200 may include a plurality of network devices (e.g., UEs, which may be in the form of vehicles) equipped (e.g., supporting C-V2X and / or supporting DSRC). The plurality of network devices may include vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f (e.g., cars). The system 1200 may include Fig.12 The system 1200 may also include unequipped network devices, such as unequipped vehicles, VRUs (e.g., cyclists), and / or pedestrians. In addition, the system 1200 may include more or fewer equipped network devices than those shown in FIG. Fig.12More or fewer different types of equipped network devices (e.g., which may include equipped UEs) are shown in FIG. In addition, in one or more examples, the equipped network devices may be equipped with heterogeneous capabilities, which may include, but are not limited to, C-V2X / DSRC capabilities, 4G / 5G cellular connectivity, GPS capabilities, camera capabilities, radar capabilities, and / or LIDAR capabilities.

[0133] The multiple equipped network devices may be able to perform communications (e.g., C-V2X and / or DSRC communications) with each other. Vehicles 1210b, 1210d, 1210f may be equipped to perform C-V2X communications to utilize the C-V2X side link PC5 interface to communicate with other vehicles similarly equipped for C-V2X communications (e.g., send and / or receive vehicle-based messages, such as safety, perception and / or warning messages). Vehicle 1210d may also be equipped for DSRC communications to utilize an 802.11p-based DSRC interface to communicate with other vehicles similarly equipped for DSRC communications (e.g., vehicles 1210a, 1210c, 1210e) (e.g., send and / or receive vehicle-based messages). A vehicle 1210d having such dual communication capabilities is referred to as having heterogeneous C-V2X / DSRC communication capabilities.

[0134] The vehicles 1210a, 1210c, 1210e may be equipped only for DSRC communication to communicate (e.g., send and / or receive vehicle-based messages) with other vehicles similarly equipped for DSRC communication using an 802.11p-based DSRC interface. Therefore, the vehicles 1210a, 1210c, 1210e that may be equipped only for DSRC communication may not be able to communicate directly with the vehicles 1210b, 1210f that are not equipped for DSRC communication. Therefore, the vehicle-based messages (e.g., safety, perception and / or warning messages) generated by the vehicles 1210a, 1210c, 1210e that may be equipped only for DSRC communication may not be easily received by the vehicles 1210b, 1210f that may be equipped only for C-V2X communication. Vehicle-based messages (e.g., safety, perception, and / or warning messages) generated by vehicles 1210b, 1210f that may be equipped only for C-V2X communications may not be easily received by vehicles 1210a, 1210c, 1210e that may be equipped only for DSRC communications.

[0135] At least some of the equipped network devices (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) may be configured to send and receive sensing signals of radar (e.g., RF sensing signals) and / or sensing signals of LIDAR (e.g., optical sensing signals) to detect nearby vehicles (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) and / or objects (e.g., VRUs and pedestrians). In some cases, at least some of the equipped network devices (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) may be configured to use one or more cameras to detect nearby vehicles and / or objects (e.g., by processing images captured by the one or more cameras to detect these vehicles / objects). In one or more examples, the vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f may be configured to send and receive certain sensing signals (eg, radar and / or LIDAR sensing signals).

[0136] During operation of the system 1200, equipped network devices (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) may send and / or receive sensing signals (e.g., RF and / or optical signals) to sense and detect vehicles (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) and / or objects (e.g., VRUs and pedestrians) located in and around the road. The equipped network device (e.g., vehicle 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) may then use the sensing signals to determine characteristics (e.g., motion, size, type, heading, and speed) of the detected vehicles (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) and / or objects (e.g., VRUs and pedestrians). The equipped network device (e.g., vehicle 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) may generate at least one vehicle-based message (e.g., Fig.10 The vehicle-based messages 915) may include C-V2X messages such as sensor data sharing messages (SDSM), basic safety messages (BSM), collaborative awareness messages (CAM), collective awareness messages (CPM), and / or other types of messages. The vehicle-based messages may include information related to the determined characteristics of the detected vehicles and / or objects.

[0137] In one or more examples, a vehicle-based message (e.g., Fig.10 The vehicle-based message 915 may include information related to the detected vehicle or object (e.g., the location of the vehicle or object, the accuracy of the location, the speed of the vehicle or object, the direction in which the vehicle or object is traveling, and / or other information related to the vehicle or object), traffic conditions (e.g., low-speed and / or dense traffic, high-speed traffic, information related to accidents, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency or "regular" message, etc.), road topology (line of sight (LOS) or non-LOS (NLOS)), any combination thereof, and / or other information. In one or more examples, the vehicle-based message (e.g., Fig.10 The transport-based messages 915) may also include information about the preferences of the equipped network device for receiving transport-based messages from certain other equipped network devices. In some cases, transport-based messages (e.g., Fig.10 The vehicle-based messages 915) may include the current capabilities of the equipped network devices (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f), such as the sensing capabilities of the equipped network devices (which may affect the accuracy with which the equipped network devices sense the vehicle and / or objects), the processing capabilities, the thermal state of the equipped network devices (which may affect the ability of the vehicle to process data), and the health status of the equipped network devices.

[0138] In some examples, a vehicle-based message (e.g., Fig.10 The vehicle-based message 915 may include a dynamic neighbor list (e.g., a local dynamic map (LDM) or a dynamic surrounding map) for each of the equipped network devices (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f). For example, each dynamic neighbor list may include a list of all vehicles (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f) and / or objects (e.g., VRUs and pedestrians) located within a specific predetermined distance (or distance radius) from the corresponding equipped network device. In some cases, each dynamic neighbor list includes a mapping of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device, which may include road and terrain topology.

[0139] In some aspects, a vehicle-based message (e.g., Fig.10Vehicle-based messages 915) may include specific use cases or safety warnings related to the current condition of the equipped network device (e.g., vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f), such as a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW). In some examples, vehicle-based messages (e.g., Fig.10 The vehicle-based message 915) may take the form of a standard basic safety message (BSM), a collaborative awareness message (CAM), a collective awareness message (CPM), a sensor data sharing message (SDSM) (e.g., SAEJ3224 SDSM), and / or other formats.

[0140] In one or more examples, during operation of the disclosed system 1200, vehicles (e.g., vehicles 1210b, 1210d, 1210f) within a formation and equipped for at least C-V2X communication may send queue formation signals 1230a, 1230b to each other (e.g., via C-V2X communication) regarding queue formation. In some examples, after a vehicle (e.g., vehicle 1210b, 1210d, 1210f) has received any C-V2X signal from at least one vehicle, the vehicle (e.g., vehicle 1210b, 1210d, 1210f) may subsequently send a queue formation signal 1230a, 1230b to the vehicle (e.g., via C-V2X communication).

[0141] The platoon may include vehicles (e.g., vehicles 1210b, 1210d, 1210f) within communication range of each other and / or may include vehicles (e.g., vehicles 1210b, 1210d, 1210f) positioned close to each other within a zone of a specified size (e.g., a zone with a predetermined radius). At least one vehicle in the platoon (e.g., vehicle 1210d) needs to be capable of both C-V2X and DSRC communications to act as a bridge for C-V2X and DSRC communications.

[0142] After the queue has been formed, the vehicles (e.g., vehicles 1210b, 1210d, 1210f) may collectively determine (e.g., via queue formation signals 1230a, 1230b) which vehicle in the queue may be designated as the queue head. There may be multiple factors that may be weighed by the vehicles (e.g., vehicles 1210b, 1210d, 1210f) in determining the queue head (e.g., vehicle 1210d), which may include, but are not limited to, the communication capabilities of the vehicles (e.g., the queue head needs to be able to conduct both C-V2X and DSRC communications in order to operate as a bridge to conduct C-V2X and DSRC communications between vehicles), the location of the vehicles (e.g., it may be advantageous to center the queue head within the queue so that the queue head may always be within communication range of other vehicles in the queue), and the processing capabilities of the vehicles (e.g., the queue head will need to be able to process all received vehicle-based messages to generate a summary message). The remaining vehicles in the queue that are not designated as queue heads may be referred to as queue members.

[0143] exist Fig.12 In the example shown, after vehicles (e.g., vehicles 1210b, 1210d, 1210f) form a queue with themselves, the vehicles (e.g., vehicles 1210b, 1210d, 1210f) may select vehicle 1210d as the queue head because vehicle 1210d is capable of both C-V2X and DSRC communications and is centrally located within the queue vehicles (e.g., vehicles 1210b, 1210d, 1210f). After the queue is formed and the queue head has been selected, any queue members (vehicles) within the queue that are capable of C-V2X and DSRC communications may stop transmitting via DSRC communications, which will allow congestion in the channel to be reduced. In one or more examples, queue members (vehicles) within the queue that are capable of C-V2X and DSRC communications may utilize an adaptive algorithm to control their transmissions via DSRC communications when necessary to reduce congestion in the channel.

[0144] In one or more examples, after a queue has been formed, vehicles in the queue (e.g., vehicles 1210b, 1210d, 1210f) (e.g., including queue heads and queue members) may continue to monitor vehicles in the queue and continue to monitor vehicles that are not in the queue and are located near the queue. For example, a vehicle in the queue may monitor the position of the vehicle in the queue for changes in its proximity to other vehicles in the queue. If a vehicle in the queue moves away from other vehicles in the queue (e.g., is no longer located near other vehicles in the queue), the vehicle in the queue (e.g., vehicles 1210b, 1210d, 1210f) may determine that the vehicle should no longer be included in the queue. For another example, a vehicle in the queue may monitor vehicles that are not in the queue and are located near the queue for their position relative to the queue and their communication capabilities (e.g., C-V2X communication capabilities). A vehicle in the queue (e.g., vehicles 1210b, 1210d, 1210f) may decide to include the vehicle in the queue if the vehicle determines that the vehicle is positioned close enough to the queue to be within the communication range of the vehicles in the queue and the vehicle is capable of at least C-V2X communication.

[0145] In one or more examples, after a queue has been formed, vehicles within the queue (e.g., vehicles 1210b, 1210d, 1210f) may continue to monitor the vehicle selected as the queue head (e.g., vehicle 1210d) for its (e.g., vehicle 1210d) communication capabilities (e.g., the queue head needs to be able to conduct both C-V2X and DSRC communications in order to operate as a bridge to conduct C-V2X and DSRC communications between vehicles), position (e.g., it may be advantageous to center the queue head within the queue so that the queue head may always be within communication range of other vehicles in the queue), and / or processing capabilities (e.g., the queue head will need to be able to process received vehicle-based messages to generate a summary message). If a vehicle in a queue (e.g., vehicles 1210b, 1210d, 1210f) determines that the vehicle designated as the head of the queue (e.g., 1210d) is no longer centrally located within the queue such that the vehicle is no longer able to receive communications from all vehicles in the queue and / or is no longer able to process all received vehicle-based messages, the vehicle in the queue (e.g., vehicles 1210b, 1210d, 1210f) may select another vehicle in the queue to operate as the head of the queue rather than the vehicle previously designated as the head of the queue (e.g., vehicle 1110d).

[0146] In one or more examples, after a queue has been formed, vehicles within the queue (e.g., vehicles 1210b, 1210d, 1210f) may continue to monitor the size of the queue. For example, if vehicles within the queue (e.g., vehicles 1210b, 1210d, 1210f) determine that the queue has become too large (e.g., the number of vehicles in the queue is greater than a predetermined maximum number of vehicles in the queue, and / or the number of vehicles in the queue requires too much processing power for the queue head to handle all vehicle-based messages from all vehicles in the queue), the vehicles in the queue (e.g., vehicles 1210b, 1210d, 1210f) may decide to split the queue into multiple separate queues (e.g., two separate queues), each of which will have their own designated queue head.

[0147] Fig.13A and Fig. 13B 1 is a diagram of a disclosed system 1200 for a queue-based C-V2X and DSRC interworking solution according to some aspects of the present disclosure, which together illustrate an example of a queue head (e.g., vehicle 1210d) operating as a bridge to communicate between vehicles (e.g., vehicles 1210a, 1210c, 1210e, 1210f) equipped for different types of communications (e.g., C-V2X and DSRC communications). Specifically, in Fig.13A In the disclosed system 1200, during operation, after a queue has been formed and a queue head (e.g., vehicle 1210d) has been selected, vehicles 1210a, 1210c, 1210e that are only equipped for DSRC communication and are not members of the queue may send message signals 1340a, 1340b, 1340c (e.g., which may include vehicle-based messages, such as safety, awareness, and / or warning messages) to the vehicle 1210d that may operate as the queue head via DSRC communication. After the vehicle 1210d receives all of the message signals 1340a, 1340b, 1340c from the vehicles 1210a, 1210c, 1210e, the vehicle 1210d (e.g., operating as the queue head) may process the vehicle-based messages contained in the message signals 1340a, 1340b, 1340c to summarize the information contained in the vehicle-based messages. After the vehicle 1210d has summarized the information contained in the vehicle-based message, the vehicle 1210d (e.g., operating as a queue head) can generate a summary message containing a summary of the information. In one or more examples, the queue head (e.g., the vehicle 1210d) can add the summary message at the end of the vehicle-based message (e.g., at the end of the BSM).

[0148] exist Fig. 13B, during operation of the disclosed system 1200, after vehicle 1210d (e.g., operating as a queue head) has generated a summary message, vehicle 1210d may send message signals 1330a, 1330b (e.g., via C-V2X communication) containing the summary message to queue members (e.g., vehicles 1210b, 1210f) to provide situational awareness to the queue members (e.g., vehicles 1210b, 1210f).

[0149] Fig.14A and Fig. 14B 1 is a diagram of a disclosed system 1200 for a queue-based C-V2X and DSRC interworking solution according to some aspects of the present disclosure, which together illustrate another example of a queue head (e.g., 1210d) operating as a bridge to communicate between vehicles (e.g., vehicles 1210a, 1210c, 1210e, 1210f) equipped for different types of communications (e.g., C-V2X and DSRC communications). Specifically, in Fig.14A , during operation of the disclosed system 1200, after a queue has been formed and a queue head (e.g., vehicle 1210d) has been selected, vehicles 1210b, 1210f that are members of the queue may send message signals 1430a, 1430b (e.g., which may include vehicle-based messages, such as safety, perception, and / or warning messages) to the vehicle 1210d that may operate as the queue head via C-V2X communication. After the vehicle 1210d receives all of the message signals 1430a, 1430b from the vehicles 1210b, 1210f, the vehicle 1210d operating as the queue head may process the vehicle-based messages contained in the message signals 1430a, 1430b to summarize the information contained in the vehicle-based messages. After the vehicle 1210d has summarized the information contained in the vehicle-based messages, the vehicle 1210d operating as the queue head may generate a summary message containing a summary of the information. In one or more examples, the queue head (eg, vehicle 1210d) can add a summary message at the end of the vehicle-based message (eg, at the end of the BSM).

[0150] exist Fig. 14B , during operation of the disclosed system 1200, after vehicle 1210d (e.g., operating as a queue head) has generated a summary message, vehicle 1210d may send message signals 1440a, 1440b, 1440c (e.g., via DSRC communication) containing the summary message to vehicles 1210a, 1210c, 1210e to provide situational awareness to vehicles 1210a, 1210c, 1210e.

[0151] Fig.15 15 is a flow chart illustrating an example of a process 1500 for forming a platoon according to some aspects of the present disclosure. At block 1510, a vehicle (e.g., Fig.12 , Fig.13A , Fig. 13B , Fig.14A and Fig. 14B At block 1520, a vehicle (e.g., 1210d), which may be equipped for both C-V2X and DSRC communications, may enable its radio so that the vehicle can send and receive both C-V2X and DSRC communications (e.g., turn on C-V2X and DSRC communications).

[0152] At block 1530, a vehicle that may be equipped for C-V2X communication (e.g., vehicle 1210d) may determine whether the vehicle has received any vehicle-based messages via C-V2X communication from any vehicle (e.g., vehicles 1210b, 1210f) that is within the communication range of the vehicle (e.g., 1210d). If the vehicle (e.g., vehicle 1210d) determines that it has not received any vehicle-based messages via C-V2X communication, then at block 1540, the vehicle may simply continue to enable its radio so that the vehicle can send and receive both C-V2X and DSRC communications (e.g., turn on C-V2X and DSRC communications). However, if the vehicle (e.g., vehicle 1210d) determines that it has indeed received at least one vehicle-based message via C-V2X communication, then at block 1550, the vehicle may communicate with the vehicle (e.g., vehicle 1210b, 1210f) that sent the vehicle-based message to the vehicle (e.g., vehicle 1210d) about forming a queue. However, if a queue has already been formed (e.g., a queue including vehicles 1210b, 1210f is formed), then the vehicle (e.g., vehicle 1210d) may join the already formed queue.

[0153] Then, at block 1560, the vehicle (e.g., 1210d) may determine whether a queue has been formed, e.g., where the queue may include the vehicle (e.g., 1210d) and vehicles (e.g., vehicles 1210b, 1210f) that are sending vehicle-based messages to the vehicle (e.g., vehicle 1210d). If the vehicle (e.g., 1210d) determines that a queue has not been formed, then at block 1570, the vehicle may simply continue to enable its radio so that the vehicle can send and receive both C-V2X and DSRC communications (e.g., turn on C-V2X and DSRC communications). However, if the vehicle (e.g., 1210d) determines that a queue has been formed, then at block 1580, DSRC queue mode may be enabled.

[0154] During DSRC platooning mode, a vehicle (e.g., 1210d) designated as the head of the platoon may enable its radio so that the vehicle (e.g., 1210d) can send and receive both C-V2X and DSRC communications (e.g., turn on C-V2X and DSRC communications). Additionally during DSRC platooning mode, other vehicles in the platoon (e.g., vehicles that are not the head of the platoon) (which may be referred to as platoon members) that are capable of sending and receiving both C-V2X and DSRC communications may partially disable their radios so that they may only receive via DSRC communications (e.g., may not be able to send via DSRC communications), but may continue to receive both C-V2X communications and DSRC communications.

[0155] Fig.16 1600 is a flowchart illustrating an example of a process 1600 for wireless communication. The process 1600 may be performed by a network device (e.g., a UE such as a vehicle, a mobile device including a mobile phone or other mobile device, a watch connected to a network, an extended reality device (e.g., a virtual reality (VR) device, an augmented reality (AR) device, a mixed reality (MR) device, etc.) or by a component or system (e.g., a chipset) of the network device. The operations of the process 1600 may be implemented as a processor on one or more processors (e.g., Fig.17 The software components executed and run on the processor 1710 or other processor of the wireless communication device. In addition, the wireless communication device can be enabled to send and receive signals in the process 1600, for example, through one or more antennas and / or one or more transceivers (e.g., wireless transceivers).

[0156] At block 1610, the network device (or a component thereof) may receive a plurality of messages using a first type of communication protocol. The network device is a device including a plurality of network devices (e.g., a plurality of UEs, such as Fig.12In some cases, the plurality of messages are vehicle-based messages, such as one or more sensor data sharing messages (SDSMs), one or more basic safety messages (BSMs), one or more collaborative awareness messages (CAMs), one or more collective awareness messages (CPMs), and / or other types of vehicle-based messages.

[0157] In some aspects, a queue is formed based at least on the location of the network device and the corresponding location of each of the plurality of network devices. In some cases, the network device is the head of a queue based at least on the corresponding location of the network device relative to each of the plurality of network devices and relative to the location of at least one other network device not included in the queue. In some cases, the network device is the head of a queue further based on at least one capability of the network device. For example, the at least one capability may include the ability of the network device to communicate using a first type of communication protocol (e.g., a dedicated short range communication (DSRC) protocol) and a second type of communication protocol (e.g., a cellular vehicle-to-everything (C-V2X) protocol).

[0158] At block 1620, the network device (or a component thereof) may generate a summary message summarizing the plurality of messages. For example, the summary message may include message content from each message (e.g., collision warning, vehicle breakdown indication, vehicle location indication). In some cases, common message information from the plurality of messages may be combined into a single information item (e.g., two messages indicating the location of a pedestrian may be combined into a single message content item indicating the location of the pedestrian). In some cases, the summary message is sent at the end of a vehicle-based message (e.g., in a final or last field of the vehicle-based message), which vehicle-based message may include a BSM, SDSM, CAM, or other type of vehicle-based message.

[0159] At block 1630, the network device (or a component thereof) may send the summary message using a second type of communication protocol. In some cases, the first type of communication protocol is a dedicated short range communication (DSRC) protocol and the second type of communication protocol is a cellular vehicle-to-everything (C-V2X) protocol. In other cases, the first type of communication protocol is C-V2X and the second type of communication protocol is a DSRC protocol. The first communication protocol and the second communication protocol may include any other example of a communication protocol, the first communication protocol being different from the second communication protocol.

[0160] In some aspects, the network device (or its component) may receive multiple messages from at least one network device not included in the queue. In such aspects, the network device (or its component) may send a summary message to multiple network devices included in the queue. In some cases, at least one network device not included in the queue is configured to communicate using a first type of communication protocol (e.g., DSRC protocol) and is not configured to communicate using a second type of communication protocol (e.g., C-V2X protocol), multiple network devices included in the queue are configured to communicate using at least a second type of communication protocol (e.g., C-V2X protocol), and the network device is configured to communicate using a first type of communication protocol (e.g., DSRC protocol) and a second type of communication protocol (e.g., C-V2X protocol).

[0161] In some aspects, the network device (or its component) may receive multiple messages from multiple network devices included in the queue. In such aspects, the network device (or its component) may send a summary message to at least one network device not included in the queue. In some cases, at least one network device not included in the queue is configured to communicate using a second type of communication protocol (e.g., C-V2X protocol) and is not configured to communicate using a first type of communication protocol (e.g., DSRC protocol), multiple network devices included in the queue are configured to communicate using a first type of communication protocol (e.g., DSRC protocol) and in some cases a second type of communication protocol (e.g., C-V2X protocol), and the network device is configured to communicate using a first type of communication protocol (e.g., DSRC protocol) and a second type of communication protocol (e.g., C-V2X protocol).

[0162] In some aspects, the network device (or its component) may determine a first position of the network device. The network device (or its component) may determine a corresponding position and at least one corresponding capability of each of the plurality of network devices included in the queue. The network device (or its component) may also determine a second position of at least one network device not included in the queue. The network device (or its component) may then determine a second network device from the plurality of network devices as a queue head of the queue based on the first position of the network device, the corresponding position and at least one corresponding capability of each of the plurality of network devices included in the queue, and the second position of at least one network device not included in the queue. In some cases, the network device (or its component) may send a message including information indicating the second network device as a queue head (e.g., indicating that the second network device has become a queue head) to the second network device.

[0163] Fig.171 is a block diagram illustrating an example of a computing system 1700 that can be used by the disclosed system for a queue-based C-V2X and DSRC interworking solution according to some aspects of the present disclosure. Specifically, Fig.17 An example of a computing system 1700 is illustrated, which may be any computing device, for example, constituting an internal computing system, a remote computing system, a camera, or any components thereof, wherein the components of the system communicate with each other using a connection 1705. The connection 1705 may be a physical connection using a bus, or a direct connection into the processor 1710, such as in a chipset architecture. The connection 1705 may also be a virtual connection, a networked connection, or a logical connection.

[0164] In some aspects, computing system 1700 is a distributed system in which the functionality described in the present disclosure may be distributed within a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more of the described system components represent a number of such components that each perform some or all of the functionality that the component is described for. In some aspects, each component may be a physical or virtual device.

[0165] The example system 1700 includes at least one processing unit (CPU or processor) 1710 and connections 1705 that communicatively couple various system components including system memory 1715, such as read only memory (ROM) 1720 and random access memory (RAM) 1725, to the processor 1710. The computing system 1700 may include a cache 1712 of high-speed memory directly connected to the processor 1710, in close proximity to the processor, or integrated as part of the processor.

[0166] Processor 1710 may include any general purpose processor and hardware or software services, such as services 1732, 1734, and 1736 stored in storage device 1730, that are configured to control processor 1710 as well as a dedicated processor where software instructions are incorporated into the actual processor design. Processor 1710 may essentially be a completely independent computing system containing multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0167] To enable user interaction, the computing system 1700 includes an input device 1745 that can represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, voice, etc. The computing system 1700 may also include an output device 1735 that can be one or more of a plurality of output mechanisms. In some examples, a multimodal system may enable a user to provide multiple types of input / output to communicate with the computing system 1700.

[0168] The computing system 1700 may include a communication interface 1740, which may generally govern and manage user input and system output. The communication interface may perform or facilitate receiving and / or sending wired or wireless communications using wired and / or wireless transceivers, including using audio jacks / plugs, microphone jacks / plugs, Universal Serial Bus (USB) ports / plugs, Apple TM Lightning TM Ports / plugs, Ethernet ports / plugs, Fiber optic ports / plugs, Dedicated wired ports / plugs, 3G, 4G, 5G and / or other cellular data network wireless signal delivery, Bluetooth TM Wireless signal transmission, Bluetooth TM Low energy (BLE) wireless signal transmission, IBEACON TM Wireless signal transmission, radio frequency identification (RFID) wireless signal transmission, near field communication (NFC) wireless signal transmission, dedicated short range communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, wireless local area network (WLAN) signal transmission, visible light communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), infrared (IR) communication wireless signal transmission, public switched telephone network (PSTN) signal transmission, integrated services digital network (ISDN) signal transmission, ad hoc network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or some combination thereof.

[0169] The communication interface 1740 may also include one or more range finding sensors (e.g., LIDAR sensors, laser range finders, RF radars, ultrasonic sensors, and infrared (IR) sensors) configured to collect data and provide measurements to the processor 1710, whereby the processor 1710 may be configured to perform determinations and calculations required to obtain various measurements of the one or more range finding sensors. In some examples, the measurements may include flight time, wavelength, azimuth, elevation, distance, linear velocity, and / or angular velocity, or any combination thereof. The communication interface 1740 may also include one or more global navigation satellite system (GNSS) receivers or transceivers for determining the location of the computing system 1700 based on receiving one or more signals from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the United States' GPS, Russia's Global Navigation Satellite System (GLONASS), China's Beidou Navigation Satellite System (BDS), and Europe's Galileo GNSS. There is no limitation to operating on any particular hardware arrangement, and thus the underlying features herein may be easily replaced to obtain improved hardware or firmware arrangements as they are developed.

[0170] The storage device 1730 may be a non-volatile and / or non-transitory and / or computer-readable memory device, and may be a hard disk or other type of computer-readable medium that may store data accessible by a computer, such as a magnetic cassette, a flash memory card, a solid-state memory device, a digital versatile disk, a cassette, a floppy disk, a floppy disk, a hard disk, a magnetic tape, a magnetic stripe / magnetic stripe, any other magnetic storage medium, flash memory, a memristor memory, any other solid-state memory, a compact disk-read only memory (CD-ROM) optical disk, a rewritable compact disk (CD) optical disk, a digital video disk (DVD) optical disk, a Blu-ray disc (BDD) optical disk, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, card, a smart card chip, an EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash EPROM (FLASH EPROM), a cache memory (e.g., a layer 1 (L1) cache, a layer 2 (L2) cache, a layer 3 (L3) cache, a layer 4 (L4) cache, a layer 5 (L5) cache, other (L#) cache), a resistive random access memory (RRAM / ReRAM), a phase change memory (PCM), a spin transfer torque RAM (STT-RAM), another memory chip or box, and / or a combination thereof.

[0171] Storage device 1730 may include software services, servers, services, etc., which, when the code defining such software is executed by processor 1710, causes the system to perform functions. In some aspects, hardware services that perform specific functions may include software components for performing functions stored in a computer-readable medium connected to necessary hardware components such as processor 1710, connection 1705, output device 1735, etc. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing or carrying instructions and / or data. Computer-readable media may include non-transitory media in which data may be stored and does not include carrier waves and / or transient electronic signals propagated wirelessly or over a wired connection. Examples of non-transitory media may include, but are not limited to, disks or tapes, optical storage media (such as compact disks (CDs) or digital versatile disks (DVDs)), flash memory, memory, or memory devices. Computer readable media may store thereon code and / or machine executable instructions, which may represent a process, function, subprogram, program, routine, subroutine, module, software package, category, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by transmitting and / or receiving information, data, independent variables, parameters, or memory contents. Information, independent variables, parameters, data, etc. may be transmitted, forwarded, or sent via any suitable means, including memory sharing, message passing, token passing, network sending, etc.

[0172] Specific details are provided in the above description to provide a thorough understanding of the various aspects and examples provided herein, but those skilled in the art will recognize that the application is not limited thereto. Thus, although the exemplary aspects of the present application have been described in detail herein, it is to be understood that each inventive concept can be implemented and adopted in various other ways, and the appended claims are not intended to be interpreted as including these variations, unless limited by the prior art. The various features and aspects of the above-mentioned applications can be used individually or in combination. In addition, without departing from the broader scope of this specification, the various aspects can be used in any number of environments and applications beyond the environment and application described herein. Therefore, the description and the accompanying drawings should be considered as illustrative rather than restrictive. For the purpose of illustration, each method is described in a specific order. It should be appreciated that, in alternative aspects, each method can be performed in a different order than described.

[0173] For clarity of explanation, in some instances, the present technology may be presented as including separate functional blocks, which include devices, device components, steps or routines in the method embodied in software or a combination of hardware and software. Additional components other than those components shown in the drawings and / or described herein may be used. For example, circuits, systems, networks, processes and other components may be shown as components in block diagram form to avoid confusing these aspects in unnecessary details. In other instances, known circuits, processes, algorithms, structures and techniques may be shown without unnecessary details to avoid confusing various aspects.

[0174] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functions in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0175] Various aspects may be described above as a process or method, which is depicted as a flow chart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flow chart may describe an operation as a sequential process, many operations in the operation may be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. The process is terminated when the operation of the process is completed, but the process may have additional steps not included in the accompanying drawings. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, the termination of the process may correspond to the function returning to the calling function or the main function.

[0176] The processes and methods according to the above examples can be implemented using stored computer executable instructions or otherwise obtained from computer readable media. Such instructions may include, for example, instructions and data that configure a general-purpose computer, a special-purpose computer, or a processing device to perform a function or a group of functions. Parts of the computer resources used can be accessed through a network. Computer executable instructions can be, for example, binary, intermediate format instructions such as assembly language, firmware, source code. Examples of computer readable media that can be used to store instructions, information used, and / or information created during the method according to the described examples include disks or optical disks, flash memories, USB devices with non-volatile memory, networked storage devices, etc.

[0177] In some embodiments, computer-readable storage devices, media, and memories may include wired or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media explicitly excludes media such as power consumption, carrier signals, electromagnetic waves, and signals themselves.

[0178] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof in some cases, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0179] Various illustrative logic blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof, and may be implemented in any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., computer program products) for performing necessary tasks may be stored in a computer-readable or machine-readable medium. The processor may perform the necessary tasks. Examples of form factors include: laptops, smartphones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, stand-alone devices, and the like. The functionality described herein may also be embodied in peripheral devices or add-in cards. By way of further example, such functionality may also be implemented on circuit boards in different chips or different processes executed on a single device.

[0180] Instructions, media for communicating such instructions, computing resources for executing them, and other structures for supporting such computing resources are example means for providing the functionality described in this disclosure.

[0181] The technology described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such technology can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication device mobile phones, or integrated circuit devices with multiple uses, including applications in wireless communication device mobile phones and other devices. Any features described as modules or components can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the technology can be implemented at least in part by a computer-readable data storage medium including a program code, which includes instructions for executing one or more of the above-mentioned methods, algorithms, and / or operations when executed. Computer-readable data storage media can form part of a computer program product, which can include packaging materials. Computer-readable media can include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer, such as a propagated signal or wave.

[0182] The program code may be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors may be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, the term "processor" as used herein may refer to any of the aforementioned structures, any combination of the aforementioned structures, or any other structure or device suitable for implementing the techniques described herein.

[0183] It should be understood by those of ordinary skill in the art that the less than ("<") and greater than (">") symbols or terms used herein may be replaced by less than or equal to ("≤") and greater than or equal to ("≥") symbols, respectively, without departing from the scope of the present specification.

[0184] Where a component is described as being “configured to” perform certain operations, such configuration may be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., a microprocessor or other suitable electronic circuits) to perform the operations, or any combination thereof.

[0185] The phrases “coupled to” or “communicatively coupled to” refer to any component being physically connected directly or indirectly to another component, and / or any component being in communication with another component directly or indirectly (e.g., connected to the other component via a wired or wireless connection and / or other suitable communication interface).

[0186] Claim language or other language reciting "at least one of" a set and / or "one or more of" a set indicates that one member of the set or multiple members of the set (in any combination) satisfies the claim. For example, claim language reciting "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, claim language reciting "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, or A and B and C. The language "at least one of" a set and / or "one or more of" a set does not limit the set to the items listed in the set. For example, claim language reciting "at least one of A and B" or "at least one of A or B" may mean A, B, or A and B, and may additionally include items not listed in the set of A and B.

[0187] Illustrative aspects of the present disclosure include:

[0188] Aspect 1. A method for performing wireless communications at a network device, the method comprising: receiving multiple messages at the network device using a first type of communication protocol, wherein the UE is part of a queue including multiple UEs; generating a summary message summarizing the multiple messages at the UE; and sending the summary message using a second type of communication protocol.

[0189] Aspect 2. The method according to aspect 1, wherein the network device is a vehicle, and wherein the plurality of network devices comprises a plurality of vehicles.

[0190] Aspect 3. The method according to any one of Aspects 1 to 2 further includes: receiving the plurality of messages from at least one network device not included in the queue.

[0191] Aspect 4. The method according to any one of Aspects 1 to 3 further includes: sending the summary message to the plurality of network devices included in the queue.

[0192] Aspect 5. A method according to any one of Aspects 1 to 4, wherein: the at least one network device not included in the queue is configured to communicate using the first type of communication protocol and is not configured to communicate using the second type of communication protocol; the multiple network devices included in the queue are configured to communicate using at least the second type of communication protocol; and the network devices are configured to communicate using both the first type of communication protocol and the second type of communication protocol.

[0193] Aspect 6. A method according to any one of Aspects 1 to 5, wherein the first type of communication protocol is a dedicated short range communication (DSRC) protocol, and the second type of communication protocol is a cellular vehicle-to-everything (C-V2X) protocol.

[0194] Aspect 7. The method according to any one of Aspects 1 to 6 further includes: receiving the plurality of messages from the plurality of network devices included in the queue.

[0195] Aspect 8. The method according to any one of Aspects 1 to 7 further comprises: sending the summary message to at least one network device not included in the queue.

[0196] Aspect 9. A method according to any one of Aspects 1 to 8, wherein: the at least one network device not included in the queue is configured to communicate using the second type of communication protocol and is not configured to communicate using the first type of communication protocol; the multiple network devices included in the queue are configured to communicate using at least the first type of communication protocol; and the network devices are configured to communicate using both the first type of communication protocol and the second type of communication protocol.

[0197] Aspect 10. A method according to any one of Aspects 1 to 9, wherein the first type of communication protocol is a cellular vehicle-to-everything (C-V2X) protocol, and the second type of communication protocol is a dedicated short range communication (DSRC) protocol.

[0198] Aspect 11. The method according to any one of aspects 1 to 10, wherein the queue is formed based on at least a location of the network device and a corresponding location of each of the plurality of network devices.

[0199] Aspect 12. A method according to any one of Aspects 1 to 11, wherein the network device is the queue head of the queue based at least on the corresponding position of the network device relative to each of the multiple network devices and the position relative to at least one other network device not included in the queue.

[0200] Aspect 13. The method according to any one of Aspects 1 to 12, wherein further based on at least one capability of the network device, the network device is the queue head of the queue.

[0201] Aspect 14. A method according to any one of Aspects 1 to 13, wherein the at least one capability includes the capability to communicate using the first type of communication protocol and the second type of communication protocol.

[0202] Aspect 15. The method according to any one of Aspects 1 to 14 further includes: determining a first position of the network device; determining a corresponding position and at least one corresponding capability of each of the multiple network devices included in the queue; determining a second position of at least one network device not included in the queue; and determining a second network device from the multiple network devices as a queue head of the queue based on the first position of the network device, the corresponding position and at least one corresponding capability of each of the multiple network devices included in the queue, and the second position of the at least one network device not included in the queue.

[0203] Aspect 16. The method according to any one of Aspects 1 to 15 further includes: sending a message including information indicating that the second network device serves as the queue head to the second network device.

[0204] Aspect 17. The method according to any one of aspects 1 to 16, wherein the plurality of messages are vehicle-based messages.

[0205] Aspect 18. A method according to any one of Aspects 1 to 17, wherein the vehicle-based message includes at least one of a sensor data sharing message (SDSM), a basic safety message (BSM), a collaborative awareness message (CAM), or a collective awareness message (CPM).

[0206] Aspect 19. The method according to any one of aspects 1 to 18, wherein the summary message is sent at the end of a vehicle-based message.

[0207] Aspect 20. An apparatus for wireless communication, comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and configured to: receive a plurality of messages using a first type of communication protocol, wherein the apparatus is part of a queue comprising a plurality of network devices; generate a summary message summarizing the plurality of messages; and output the summary message for transmission using a second type of communication protocol.

[0208] Aspect 21. The apparatus of aspect 20, wherein the apparatus is a computing device of a vehicle, and wherein the plurality of network devices comprises a plurality of vehicles.

[0209] Aspect 22. An apparatus according to any one of Aspects 20 to 21, wherein the at least one processor is configured to: receive the plurality of messages from at least one network device not included in the queue.

[0210] Aspect 23. An apparatus according to any one of Aspects 20 to 22, wherein the at least one processor is configured to: output the summary message to be sent to the plurality of network devices included in the queue.

[0211] Aspect 24. An apparatus according to any one of Aspects 20 to 23, wherein: at least one network device not included in the queue is configured to communicate using the first type of communication protocol and is not configured to communicate using the second type of communication protocol; the multiple network devices included in the queue are configured to communicate using at least the second type of communication protocol; and the apparatus is configured to communicate using both the first type of communication protocol and the second type of communication protocol.

[0212] Aspect 25. According to an apparatus according to any one of Aspects 20 to 24, the first type of communication protocol is a dedicated short range communication (DSRC) protocol, and the second type of communication protocol is a cellular vehicle-to-everything (C-V2X) protocol.

[0213] Aspect 26. An apparatus according to any one of Aspects 20 to 25, wherein the at least one processor is configured to: receive the plurality of messages from the plurality of network devices included in the queue.

[0214] Aspect 27. An apparatus according to any one of aspects 20 to 26, wherein the at least one processor is configured to: output the summary message to be sent to at least one network device not included in the queue.

[0215] Aspect 28. An apparatus according to any one of Aspects 20 to 27, wherein: at least one network device not included in the queue is configured to communicate using the second type of communication protocol and is not configured to communicate using the first type of communication protocol; the multiple network devices included in the queue are configured to communicate using at least the first type of communication protocol; and the apparatus is configured to communicate using both the first type of communication protocol and the second type of communication protocol.

[0216] Aspect 29. An apparatus according to any one of Aspects 20 to 28, wherein the first type of communication protocol is a cellular vehicle-to-everything (C-V2X) protocol, and the second type of communication protocol is a dedicated short range communication (DSRC) protocol.

[0217] Aspect 30. An apparatus according to any one of aspects 20 to 29, wherein the queue is formed based on at least a location of the apparatus and a corresponding location of each of the plurality of network devices.

[0218] Aspect 31. An apparatus according to any one of Aspects 20 to 30, wherein the apparatus is the queue head of the queue based at least on the respective positions of the apparatus relative to each of the plurality of network devices and relative to the position of at least one other network device not included in the queue.

[0219] Aspect 32. An apparatus according to any one of Aspects 20 to 31, wherein further based on at least one capability of the apparatus, the apparatus is the queue head of the queue.

[0220] Aspect 33. An apparatus according to any one of Aspects 20 to 32, wherein the at least one capability comprises the capability to communicate using the first type of communication protocol and the second type of communication protocol.

[0221] Aspect 34. An apparatus according to any one of Aspects 20 to 33, wherein the at least one processor is configured to: determine a first position of the apparatus; determine a corresponding position and at least one corresponding capability of each of the multiple network devices included in the queue; determine a second position of at least one network device not included in the queue; and determine a network device from the multiple network devices as a queue head of the queue based on the first position of the apparatus, the corresponding position and at least one corresponding capability of each of the multiple network devices included in the queue, and the second position of the at least one network device not included in the queue.

[0222] Aspect 35. An apparatus according to any one of Aspects 20 to 34, wherein the at least one processor is configured to: output a message including information indicating that the network device is the head of the queue to send to the network device.

[0223] Aspect 36. An apparatus according to any one of aspects 20 to 35, wherein the plurality of messages are vehicle-based messages.

[0224] Aspect 37. An apparatus according to any one of Aspects 20 to 36, wherein the vehicle-based message includes at least one of a sensor data sharing message (SDSM), a basic safety message (BSM), a collaborative awareness message (CAM), or a collective awareness message (CPM).

[0225] Aspect 38. An apparatus according to any one of aspects 20 to 37, wherein the summary message is sent at the end of a transport-based message.

[0226] Aspect 39. Provided is a non-transitory computer-readable medium having instructions stored thereon, which when executed by one or more processors cause the one or more processors to perform the operations according to any one of aspects 1 to 38.

[0227] Aspect 40. An apparatus for wireless communications, the apparatus comprising: one or more means for performing the operations of any one of aspects 1 to 38.

[0228] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope consistent with the language claims, where an element mentioned in the singular is not intended to mean "one and only one", unless specifically stated otherwise, but rather "one or more".

Claims

1. A method for wireless communication at a network device, the method comprising: receiving, at the network device, a plurality of messages using a first type of communication protocol, wherein the network device is part of a queue including a plurality of network devices; generating, at the network device, a summary message summarizing the plurality of messages; as well as The summary message is sent using a second type of communications protocol. 2 . The method of claim 1 , wherein the network device is a vehicle, and wherein the plurality of network devices comprises a plurality of vehicles.

3. The method according to claim 1, further comprising: The plurality of messages are received from at least one network device not included in the queue.

4. The method according to claim 3, further comprising: The summary message is sent to the plurality of network devices included in the queue.

5. The method according to claim 4, wherein: the at least one network device not included in the queue being configured to communicate using the first type of communication protocol and not configured to communicate using the second type of communication protocol; The plurality of network devices included in the queue are configured to communicate using at least the second type of communication protocol; and The network device is configured to communicate using the first type of communication protocol and the second type of communication protocol.

6. The method of claim 5, wherein the first type of communication protocol is a dedicated short range communication (DSRC) protocol, and the second type of communication protocol is a cellular vehicle-to-everything (C-V2X) protocol.

7. The method according to claim 1, further comprising: The plurality of messages are received from the plurality of network devices included in the queue.

8. The method according to claim 7, further comprising: The summary message is sent to at least one network device not included in the queue.

9. The method according to claim 8, wherein: the at least one network device not included in the queue being configured to communicate using the second type of communication protocol and not configured to communicate using the first type of communication protocol; The plurality of network devices included in the queue are configured to communicate using at least the first type of communication protocol; and The network device is configured to communicate using the first type of communication protocol and the second type of communication protocol.

10. The method of claim 9, wherein the first type of communication protocol is a Cellular Vehicle-to-Everything (C-V2X) protocol, and the second type of communication protocol is a Dedicated Short Range Communication (DSRC) protocol.

11. The method of claim 1, wherein the queue is formed based on at least a location of the network device and a corresponding location of each of the plurality of network devices.

12. The method of claim 11, wherein the network device is a queue head of the queue based at least on the respective position of the network device relative to each of the plurality of network devices and relative to at least one other network device not included in the queue.

13. The method of claim 12, wherein further based on at least one capability of the network device, the network device is the queue head of the queue.

14. The method of claim 13, wherein the at least one capability comprises the ability to communicate using the first type of communication protocol and the second type of communication protocol.

15. The method according to claim 1, further comprising: determining a first location of the network device; determining a respective position and at least one respective capability of each of the plurality of network devices included in the queue; determining a second position of at least one network device not included in the queue; as well as A second network device from the plurality of network devices is determined as a queue head of the queue based on the first position of the network device, the corresponding position and at least one corresponding capability of each of the plurality of network devices included in the queue, and the second position of the at least one network device not included in the queue.

16. The method according to claim 15, further comprising: A message including information indicating that the second network device serves as the head of the queue is sent to the second network device.

17. The method of claim 1, wherein the plurality of messages are vehicle-based messages.

18. The method of claim 17, wherein the vehicle-based message comprises at least one of a sensor data sharing message (SDSM), a basic safety message (BSM), a collaborative awareness message (CAM), or a collective awareness message (CPM).

19. An apparatus for wireless communication, comprising: at least one memory; as well as at least one processor coupled to at least one memory and configured to: receiving a plurality of messages using a first type of communications protocol, wherein the apparatus is part of a queue including a plurality of network devices; generating a summary message summarizing the plurality of messages; and The summary message is output for transmission using a second type of communication protocol.

20. The apparatus of claim 19, wherein the apparatus is a computing device in a vehicle, and wherein the plurality of network devices comprises a plurality of vehicles.

21. The apparatus of claim 19, wherein the at least one processor is configured to: The plurality of messages are received from at least one network device not included in the queue.

22. The apparatus of claim 21, wherein the at least one processor is configured to: The summary message is output to be sent to the plurality of network devices included in the queue.

23. The apparatus of claim 22, wherein: the at least one network device not included in the queue being configured to communicate using the first type of communication protocol and not configured to communicate using the second type of communication protocol; The plurality of network devices included in the queue are configured to communicate using at least the second type of communication protocol; and The apparatus is configured to communicate using the first type of communication protocol and the second type of communication protocol.

24. The apparatus of claim 19, wherein the at least one processor is configured to: The plurality of messages are received from the plurality of network devices included in the queue.

25. The apparatus of claim 24, wherein the at least one processor is configured to: The summary message is output to be sent to at least one network device not included in the queue.

26. The apparatus of claim 25, wherein: the at least one network device not included in the queue being configured to communicate using the second type of communication protocol and not configured to communicate using the first type of communication protocol; The plurality of network devices included in the queue are configured to communicate using at least the first type of communication protocol; and The apparatus is configured to communicate using the first type of communication protocol and the second type of communication protocol.

27. The apparatus of claim 19, wherein the queue is formed based on at least a location of the apparatus and a corresponding location of each of the plurality of network devices.

28. An apparatus according to claim 27, wherein the apparatus is the head of the queue based on at least one of the capabilities of the apparatus or the respective positions of the apparatus relative to each of the plurality of network devices and the position relative to at least one other network device not included in the queue.

29. The apparatus of claim 28, wherein the at least one capability comprises an ability to communicate using the first type of communication protocol and the second type of communication protocol.

30. The apparatus of claim 19, wherein the at least one processor is configured to: determining a first position of the device; determining a respective position and at least one respective capability of each of the plurality of network devices included in the queue; determining a second position of at least one network device not included in the queue; and A network device from the plurality of network devices is determined as a queue head of the queue based on the first position of the apparatus, the corresponding position and at least one corresponding capability of each of the plurality of network devices included in the queue, and the second position of the at least one network device not included in the queue.

Images