Dynamic reliability distance for wireless communication

Abstract

Methods, systems, and devices for wireless communication are described. A vehicle user equipment (VUE) may generate a multicast message for transmission in an Internet of Vehicles (V2X) system. The VUE may transmit the multicast message using a transmit power based on a reliability distance corresponding to an area for providing feedback for the multicast message, wherein the reliability distance is based on one or more positioning parameters of the VUE and one or more environmental parameters associated with the V2X system. The VUE may then monitor feedback for the multicast message.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 460,423, filed September 1, 2023, entitled “DYNAMICRELIABILITY DISTANCE FOR WIRELESS COMMUNICATIONS”, which is assigned to the assignee of this invention and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following discussion relates to wireless communication, including dynamic reliability distances used for wireless communication. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] A vehicle UE (VUE) can communicate with other devices in a wireless communication system that has the VUE (e.g., UEs, network entities, roadside units (RSUs), or any combination thereof). Wireless communication can be associated with a feedback range, allowing devices within the feedback range to provide feedback to the VUE in response to one or more communications from the VUE. Summary of the Invention

[0006] The described technology relates to methods, systems, devices, and apparatuses that support improved dynamic reliability distances for wireless communication. For example, the described technology allows for the dynamic configuration of reliability distances for multicast messages in a vehicle-to-everything (V2X) wireless communication system. A vehicle user equipment (VUE) can implement a transmission power for multicast messages corresponding to the reliability distance, enabling other VUEs within that reliability distance to receive multicast messages and perform maneuver coordination (or provide feedback) within the V2X system. VUEs or network entities (such as roadside units (RSUs)) can dynamically adjust the reliability distance to include interaction points (e.g., intersections) or interaction areas. For example, the reliability distance can be larger to include the interaction area when a VUE approaches the interaction point from a certain distance. Alternatively, the reliability distance can be smaller when the VUE is relatively closer to the interaction point or within the interaction area, thus allowing the VUE to use less transmission power for multicast messages.

[0007] A method for wireless communication by a VUE is described. The method may include: generating a multicast message for transmission by the VUE in a V2X system; transmitting the multicast message using a transmission power based on a reliability distance corresponding to an area used to provide feedback on the multicast message, wherein the reliability distance is based on one or more positioning parameters of the VUE and one or more environmental parameters associated with the V2X system; and monitoring feedback on the multicast message based on its transmission.

[0008] A VUE for wireless communication is described. The VUE may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors may operate individually or jointly to execute the code to cause the VUE to: generate multicast messages for transmission by the VUE in a V2X system; transmit the multicast messages using a transmission power based on a reliability distance corresponding to an area for providing feedback on the multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system; and monitor feedback on the multicast messages based on the transmission of the multicast messages.

[0009] Another VUE for wireless communication is described. The VUE may include: components for generating multicast messages for transmission in a V2X system; components for transmitting the multicast messages using a transmission power based on a reliability distance corresponding to an area for providing feedback on the multicast messages, wherein the reliability distance is based on one or more positioning parameters of the VUE and one or more environmental parameters associated with the V2X system; and components for monitoring feedback on the multicast messages based on their transmission.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor for: generating a multicast message to be transmitted by the VUE in a V2X system; transmitting the multicast message using a transmission power based on a reliability distance corresponding to an area used to provide feedback on the multicast message, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system; and monitoring feedback on the multicast message based on its transmission.

[0011] In some examples of the methods described herein, VUE, and nontransitory computer-readable media, transmitting the multicast message may include operations, features, components, or instructions for transmitting the multicast message using the transmission power, wherein the transmission power may be based on the location of the interaction area associated with the multicast message and based on the interaction area corresponding to the location of the interaction area, wherein the reliability distance may be based on the location of the interaction area associated with the multicast message and based on the interaction area corresponding to the location of the interaction area.

[0012] In some examples of the methods, VUEs, and nontransitory computer-readable media described herein, transmitting the multicast message may include operations, features, components, or instructions for transmitting the multicast message using the transmission power, wherein the transmission power may be based on the vehicle location of the VUE relative to the interaction area associated with the multicast message, wherein the one or more positioning parameters of the VUE include the vehicle location of the VUE.

[0013] In some examples of the methods described herein, VUE, and nontransitory computer-readable media, sending the multicast message may include operations, features, components, or instructions for sending the multicast message based on the reliability distance, wherein the reliability distance may be based on one or more static road parameters, one or more dynamic road parameters, one or more time-specific road parameters, stopping sight distance, or any combination thereof.

[0014] In some examples of the methods described herein, VUEs, and nontransitory computer-readable media, sending the multicast message may include operations, features, components, or instructions for sending the multicast message based on the reliability distance, wherein the reliability distance may be based on the location of the VUE, the motion state of the VUE, or any combination thereof.

[0015] In some examples of the methods described herein, VUE, and nontransitory computer-readable media, sending the multicast message may include operations, features, components, or instructions for sending the multicast message based on the reliability distance, wherein the reliability distance may be based on information from a third-party map service.

[0016] The methods described herein, and some examples of VUEs and nontransitory computer-readable media, may also include operations, features, components, or instructions for receiving an indication of the reliability distance via a unicast message dedicated to the VUE, a radio resource control reconfiguration message, a PC5 radio resource control message, a PC5 sidelink message, a radio resource control message via a Uu communication link, or any combination thereof.

[0017] In the methods described herein, and in some examples of VUE and nontransitory computer-readable media, this indication of the reliability distance may be received from the RSU.

[0018] In some examples of the methods described herein, VUE, and non-transitory computer-readable media, this indication of the reliability distance may be received as part of an advanced driver assistance system (ADAS) map enhancement.

[0019] The methods described herein, examples of VUEs and nontransitory computer-readable media may also include operations, features, components or instructions for receiving indications of one or more environmental parameters associated with the V2X system, wherein the reliability distance may be based on the indications of the one or more environmental parameters associated with the V2X system and on the one or more positioning parameters of the VUE.

[0020] In some examples of the methods described herein, VUEs, and nontransitory computer-readable media, sending the multicast message may include operations, features, components, or instructions for sending the multicast message based on the reliability distance, wherein the reliability distance may be based on the service type of the VUE, the service type of the multicast message, the service type of one or more UEs of the V2X system, or any combination thereof.

[0021] In some examples of the methods described herein, VUE, and nontransitory computer-readable media, the service type includes manipulation sharing, sensor sharing, collective sensing, or any combination thereof.

[0022] A method for wireless communication by a network entity is described. The method may include: obtaining one or more positioning parameters for a VUE within a V2X system; obtaining one or more environmental parameters associated with the V2X system; and outputting an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on the one or more positioning parameters of the VUE and the one or more environmental parameters associated with the V2X system.

[0023] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to enable the network entity to: obtain one or more positioning parameters for a VUE within a V2X system; obtain one or more environmental parameters associated with the V2X system; and output an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on the one or more positioning parameters of the VUE and the one or more environmental parameters associated with the V2X system.

[0024] Another network entity for wireless communication is described. This network entity may include: components for obtaining one or more positioning parameters for a VUE within a V2X system; components for obtaining one or more environmental parameters associated with the V2X system; and components for outputting an indication of a reliability distance corresponding to an area for providing feedback on multicast messages, wherein the reliability distance is based on the one or more positioning parameters of the VUE and the one or more environmental parameters associated with the V2X system.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor for: obtaining one or more positioning parameters for a VUE within a V2X system; obtaining one or more environmental parameters associated with the V2X system; and outputting an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on the one or more positioning parameters of the VUE and the one or more environmental parameters associated with the V2X system.

[0026] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for configuring the reliability distance based on one or more environmental parameters, the service type of the VUE, and the service type of one or more other UEs in the V2X system.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, obtaining the one or more positioning parameters for the VUE may include operations, features, components, or instructions for obtaining the current vehicle location and motion state of the VUE.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of the indication of the reliability distance may include operations, features, components, or instructions for: predicting the future location of the VUE at a future time, the predicted future location of the VUE being based on the VUE’s current vehicle location, the VUE’s motion state, one or more environmental parameters associated with the V2X system, information associated with the VUE’s destination, the VUE’s historical location information, or any combination thereof.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of the indication of the reliability distance may include an operation, feature, component, or instruction for outputting the indication of the reliability distance based on determining the reliability distance based on the predicted future location of the VUE.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of the indication of the reliability distance may include operations, features, components, or instructions for outputting the indication of the reliability distance based on the service type of the V2X system.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of the indication of the reliability distance may include an operation, feature, component, or instruction for: outputting the indication of the reliability distance to the VUE or to one or more other UEs associated with the V2X system, or both.

[0032] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for communicating with one or more other UEs within the V2X system to obtain one or more conditions of the V2X system.

[0033] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for using one or more sensors to sense one or more conditions of the V2X system.

[0034] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for communicating with one or more other UEs within the V2X system and configuring the reliability distance based on communication with those one or more other UEs within the V2X system.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the reliability distance may be based on the interaction area corresponding to the location of the interaction area associated with the multicast message and on the interaction area corresponding to that location of the interaction area.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of the indication of the reliability distance may include operations, features, components, or instructions for outputting the indication of the reliability distance, wherein the reliability distance may be based on the vehicle location of the VUE relative to the interaction area.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of the indication of the reliability distance may include an operation, feature, component, or instruction for outputting the indication of the reliability distance, wherein the reliability distance may be based on one or more static road parameters, one or more dynamic parameters, one or more time-specific parameters, stopping sight distance, or any combination thereof.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, obtaining the one or more positioning parameters for the VUE may include operations, features, components, or instructions for obtaining the one or more positioning parameters for the VUE from a third-party map service.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output of this indication of the reliability distance may include operations, features, components, or instructions for outputting this indication of the reliability distance as part of ADAS map enhancement. Attached Figure Description

[0040] Figure 1 An example of a wireless communication system supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown.

[0041] Figure 2 An example of a network architecture supporting dynamic reliable distance for wireless communication is shown, according to one or more aspects of this disclosure.

[0042] Figure 3 , Figure 4A , Figure 4B and Figure 4C An example of a wireless communication system supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown.

[0043] Figure 5 and Figure 6 An example of a process flow supporting dynamic reliability distance for wireless communication is shown, according to one or more aspects of this disclosure.

[0044] Figure 7 and Figure 8 A block diagram of a device supporting dynamic reliability distance for wireless communication is shown, according to one or more aspects of this disclosure.

[0045] Figure 9 A block diagram of a communication manager supporting dynamic reliable distance for wireless communication, according to one or more aspects of this disclosure, is shown.

[0046] Figure 10 A diagram is shown of a system including a device supporting dynamic reliability distance for wireless communication, according to one or more aspects of this disclosure.

[0047] Figure 11 and Figure 12 A block diagram of a device supporting dynamic reliability distance for wireless communication is shown, according to one or more aspects of this disclosure.

[0048] Figure 13 A block diagram of a communication manager supporting dynamic reliable distance for wireless communication, according to one or more aspects of this disclosure, is shown.

[0049] Figure 14 A diagram is shown of a system including a device supporting dynamic reliability distance for wireless communication, according to one or more aspects of this disclosure.

[0050] Figure 15 and Figure 16 A flowchart illustrating a method for supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. Detailed Implementation

[0051] Some wireless communication systems, such as vehicle-to-everything (V2X) systems, support advanced driver assistance systems (ADAS). In these ADAS, user equipment (UE) or vehicle UE (VUE) can transmit sensor information (e.g., sensor sharing data) or maneuvering coordination information to other devices (such as other VUEs, network entities, or roadside units (RSUs)). In some cases, VUEs can use connectionless or distance-based multicast messages to transmit sensor information, maneuvering coordination information, or any combination thereof. For example, VUEs can implement reliable distance-based transmission power, allowing devices within the reliable distance to receive the transmission with a high probability (e.g., a higher than threshold probability of successful reception). In some cases, sensor information and maneuvering coordination information can be transmitted with high reliability to devices at or near the interaction point, such as locations where interactions may occur between vehicles, devices, or objects in a V2X system. For example, an emergency vehicle might send information to devices located within range of an upcoming road intersection. However, implementing high reliability beyond the interaction point can be inefficient in terms of transmission power and overhead. Furthermore, because the distance between the VUE (e.g., an emergency vehicle) and the interaction point (e.g., an intersection) varies as the VUE approaches, passes through, and moves away from the interaction point, the distance used to maintain sufficient reliability can also vary. Therefore, dynamically determining the reliability distance can improve efficiency and reduce overhead.

[0052] VUEs or network entities within a V2X system can dynamically determine the reliability distance for distance-based multicast. For example, the reliability distance can be based on the VUE's location parameters (e.g., vehicle location, vehicle motion state, or any combination thereof) and environmental parameters associated with the V2X system (e.g., road topology, message type, or any combination thereof). The reliability distance can be indicated within a message (which may be sent by the network entity to the VUE), can be part of map augmentation, or, if the VUE is provided with environmental parameters associated with the V2X system, the VUE can determine the reliability distance. In some cases, the network entity or VUE can dynamically adjust the reliability distance as the VUE approaches and moves away from the interaction point. For example, the reliability distance may be relatively larger when the VUE is farther from the interaction point than when the VUE is closer to the interaction point. By reducing the reliability distance as the VUE moves closer to the interaction point, the VUE can save transmission power and reduce overhead.

[0053] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of a wireless communication system and process flow. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to dynamic reliability distances used in wireless communication.

[0054] Figure 1 An example of a wireless communication system 100 supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0055] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0056] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0057] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0058] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0059] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0060] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0061] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Alternatively or additionally, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0062] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0063] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support dynamic reliability distances for wireless communication as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0064] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0065] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0066] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0068] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0069] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0070] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0071] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of the physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0072] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0073] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0074] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0075] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0076] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using V2X communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as RSUs), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0077] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0078] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0079] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0080] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0081] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0082] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0083] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0084] In some cases, the wireless communication system 100 may support V2X communication, and the UE 115 may be a vehicle referred to as VUE 115, and may be able to use connectionless or distance-based multicast to send sensor information and maneuver coordination information to other devices such as other VUEs 115, network entity 105, or RSUs. For example, the VUE 115 may implement a transmission power based on reliability distance, such that devices within the reliability distance can receive and respond to the transmission as appropriate. In some cases, sensor information and maneuver coordination information may be transmitted with high reliability to devices at or near the interaction point, such as locations where interactions may occur between vehicles or objects in the wireless communication system 100. For example, accidents caused by failed communication (e.g., collisions) may be more likely to occur at or near the interaction point, and the wireless communication system 100 may be configured using one or more safety criteria, which may include meeting a certain level of reliability (e.g., high reliability) when transmitting sensor information and maneuver coordination information near the interaction point. A given transmission power, MCS, or repetition rate may be used to transmit high-reliability messages to meet the target reliability. Because the distance between VUE 115 and the interaction point (e.g., an intersection) changes as VUE 115 approaches and moves away from the interaction point, the distance used to maintain sufficient reliability also varies. Therefore, dynamically determining the reliability distance can improve efficiency and reduce overhead.

[0085] The VUE 115 or network entity 105 within the wireless communication system 100 can dynamically determine the reliability distance for distance-based multicast. For example, the reliability distance can be based on the VUE 115's location parameters (e.g., vehicle location, vehicle motion state information such as speed, direction, or any combination thereof) and environmental parameters associated with the wireless communication system 100 (e.g., road topology, message type, or any combination thereof). The reliability distance can be sent to the VUE 115 by the network entity 105, can be part of map augmentation, or the VUE 115 can determine the reliability distance if it is provided with environmental parameters associated with the wireless communication system 100. In some cases, the network entity 105 or the VUE 115 can dynamically adjust the reliability distance as the VUE 115 approaches and moves away from the interaction point. For example, the reliability distance may be relatively larger when the VUE 115 is farther from the interaction point than when the VUE 115 is closer to the interaction point. By reducing the reliability distance when VUE 115 is closer to the interaction point, VUE 115 can save transmit power, improve resource utilization, and reduce overhead.

[0086] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify examples of one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served simultaneously by multiple RU 170-a.

[0087] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Alternatively or additionally, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0088] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can 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 units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0089] DU 165-a may correspond to a logic unit including one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the function splits, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0090] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the implementation of DU 165-a and CU160-a units in cloud-based RAN architectures such as vRAN architectures.

[0091] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage objectives, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can (e.g., via the O1 interface) communicate with components configured according to the 4G RAN. Alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0092] The non-RT RIC 175-a can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) or machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via an E2 interface) that connects one or more CU 160-a, one or more DU 165-a, or both, and an O-eNB 210 to the near-RT RIC 175-b.

[0093] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0094] UE 115 (e.g., VUE) can use connectionless or distance-based multicast to send sensor information and manipulation coordination information to other devices such as other UE 115s, network entities, or RSUs. For example, UE 115 can implement reliable distance-based transmit power, allowing devices within the reliable distance to receive the transmission. In some cases, sensor information and manipulation coordination information can be transmitted with high reliability to devices at or near the interaction point, such as locations where interactions may occur between vehicles or objects in a V2X system. Because the distance between UE 115 and the interaction point (e.g., an intersection) varies as UE 115 approaches and moves away from the interaction point, the distance used to maintain sufficient reliability can also vary. Therefore, dynamically determining the reliable distance can improve efficiency and reduce overhead.

[0095] Within a V2X system, UE 115 or network entities can dynamically determine the reliability distance for distance-based multicast. For example, the reliability distance can be based on UE 115's location parameters (e.g., vehicle location, vehicle motion state, or any combination thereof) and environmental parameters associated with the V2X system (e.g., road topology, message type being sent, or any combination thereof). The reliability distance can be sent to UE 115 by the network entity, can be part of map enhancement, or UE 115 can determine the reliability distance if it is provided with environmental parameters associated with the V2X system. In some cases, the network entity or UE 115 can dynamically adjust the reliability distance as UE 115 approaches and moves away from the interaction point. For example, the reliability distance can be relatively larger when UE 115 is farther from the interaction point than when UE 115 is closer to the interaction point. By reducing the reliability distance as UE 115 moves closer to the interaction point, UE 115 can save transmit power, improve network efficiency and network resource utilization, and reduce overhead.

[0096] Figure 3 An example of a wireless communication system 300 supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. The wireless communication system 300 may support V2X communication / operation. In some cases, the wireless communication system 300 may also support driver assistance systems, such as ADAS. The wireless communication system 300 may include VUEs 315, which may be as referenced... Figure 1 and Figure 2 Examples of UE 115 and VUE 115 described herein. The wireless communication system 300 may also include one or more RSUs 305, which may be as described in reference... Figure 1 and Figure 2 An example of the described network entity 105.

[0097] In some cases, VUE 315-a can send sensor sharing information, manipulation coordination information, or other application layer V2X messages or information to other devices in the wireless communication system 300, such as other VUE 315-b, VUE 315-c, VUE 315-d, and RSU 305-a, etc. In some cases, VUE 315-a can use connectionless or distance-based multicast messages to send sensor information, manipulation coordination information, or any combination thereof. For example, VUE 315-a can utilize a transmit power corresponding to a reliability distance 330, enabling devices within the reliability distance 330 to receive multicast messages. In some cases, sensor information and manipulation coordination information can be sent to devices within range of interaction point 320 with a given reliability. In some cases, interaction point 320 can be a location within interaction area 325 where interactions between vehicles or objects in the wireless communication system 300 may occur, such as at an intersection. For example, VUE 315-a could be an emergency vehicle and could send information to devices located near an upcoming intersection (e.g., other VUEs 315). However, implementing high reliability beyond the interaction point 320 could be inefficient in terms of transmission power and overhead. Because the distance between VUE 315-a (e.g., the emergency vehicle) and the interaction point 320 (e.g., the intersection) varies as VUE 315-a approaches and moves away from the interaction point, the distance used to maintain sufficient reliability also varies. Therefore, dynamically determining the reliability distance 330 can improve efficiency and reduce overhead.

[0098] To improve efficiency and reduce overhead, a VUE 315-a or network entity (such as RSU 305-a) within the wireless communication system 300 can dynamically determine a reliability distance 330 for distance-based multicast. The reliability distance 330 may correspond to a NACK region, or an area in which VUE 315-a may receive feedback from other devices (e.g., other VUEs 315). The reliability distance 330 can be dynamically determined to include an interaction region 325, which may be an area where manipulation of coordination or sensor information messages is expected. In some cases, knowledge of the interaction region 325 (e.g., region size and proximity) enables dynamic adjustment of the NACK region. For example, based on the reliability distance 330, VUE 315-a may use a transmit power based on the location (e.g., corresponding to) of the interaction region 325 (e.g., the interaction area) to transmit multicast messages. In some cases, the transmit power may also correspond to the location of VUE 315-a relative to the interaction region 325.

[0099] The reliability distance 330 (e.g., NACK distance or NACK area) can be a function of the distance from the interaction point 320 based on location parameters of VUE 315-a (e.g., vehicle location, vehicle motion state, or any combination thereof) and environmental parameters 335 associated with the wireless communication system 300 (e.g., road topology, type of message sent, or any combination thereof). Environmental parameters 335 can be static (e.g., intersection, merging area, roundabout, entrance ramp, exit ramp, etc.) or dynamic (e.g., construction zone or parade, etc.). Environmental parameters 335 can also be time-specific, such as school zones or public transportation routes. Environmental parameters 335 can also be associated with the location and size of the interaction point 320 (e.g., intersection). In the example, environmental parameter 335-a can be an obstacle associated with the road topology (e.g., associated with construction or road damage), and environmental parameter 335-b can be a pedestrian preparing to cross the road. In some cases, the reliability distance 330 may also be based on the service type of VUE 315-a, the service type of multicast messages, the service type of one or more other VUE 315s, the service type of the wireless communication system 300 (e.g., manipulation sharing, sensor information, collective sensing, or any combination thereof), the parking distance (e.g., parking sight distance) associated with VUE 315-a or other VUE 315, or any combination thereof.

[0100] In some cases, reliability distance 330 can be added as a map overlay, such as an overlay for an ADAS map used in VUE 315-a. In some cases, neighboring entities 340 (e.g., cloud entities, network entities, third-party map services) may include a database of environmental parameters 335 and reliability distance 330 for the wireless communication system 300. Neighboring entities 340 may be obtained from the network (e.g., as referenced in the image). Figure 1 The core network described receives location parameters via Basic Security Messages (BSM), cloud, map service inputs, or any combination thereof.

[0101] In some cases, RSU 305-a or a network entity may determine the reliability distance 330. RSU 305-a may communicate with other VUEs 315 (e.g., VUE 315-b, VUE 315-c, and VUE 315-d) to obtain environmental parameters 335. Alternatively, RSU 305-a may obtain environmental parameters 335 via sensors of RSU 305-a (e.g., cameras, traffic lights, traffic signs). RSU 305-a may also communicate with VUE 315-a to obtain the positioning parameters of VUE 315-a. RSU 305-a may communicate with VUE 315 to configure the reliability distance individually or based on groups or areas. RSU 305-a may indicate the reliability distance 330 to VUE 315-a. In some cases, RSU 305-a may indicate a reliability distance 330 to one or more other VUEs 315 (e.g., VUE 315-b). In some cases, RSU 305-a may send dedicated signaling (e.g., application layer signaling), broadcast signaling, multicast signaling, or any combination thereof indicating the reliability distance 330. In some cases, the indication of the reliability distance 330 may include an array of paired values ​​of the NACK distance and the distance to the interaction point 320. For example, if the reliability distance 330 is 300 meters and if the interaction point 320 is 500 meters away from VUE 315-a, the indication of the reliability distance 330 may include an array of paired values ​​(300, 500). In some cases, the indication of the reliability distance 330 may include inputs for a formula (e.g., a formulaic formula). For example, the formula for the reliability distance 330 may be... ,in It could be a reliability distance of 330 (e.g., distance-based multicast feedback (NACK) distance). It can be an interactive area of ​​size 325 (e.g., the diameter of an area used for reliable multicast). This could be the distance to VUE 315-a (e.g., the distance between VUE315-a and interaction point 320), and This can be a NACK range adjustment multiplier. In some cases, the formula for reliability distance 330 may also include an indication of the center of interaction point 320 or interaction region 325, which may include the latitude and longitude of interaction point 320. When reliability distance 330 is determined by a formula, VUE 315-a may receive one or more inputs from the inputs used in the formula (e.g., , , (or any combination thereof). In some cases, the indication of reliability distance may include enumerated values ​​such as latitude and longitude microindication, range values, and distance from the interaction point.

[0102] In some cases, VUE 315-a can determine a reliability distance 330. For example, RSU 305-a can provide environmental parameters 335 to VUE 315-a. Based on environmental parameters 335 and VUE 315-a's location parameters, VUE 315-a can determine the reliability distance. Whether VUE 315-a determines the reliability distance 330 or receives an indication of the reliability distance 330, VUE 315-a can transmit multicast messages using the corresponding transmit power.

[0103] Figure 4A An example of a wireless communication system 400-a supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. The wireless communication system 400-a may support V2X communication / operation. The wireless communication system 400-a may include a VUE 415 and an RSU 405, which may be as described in reference... Figure 3 Examples of VUE 315 and RSU 305 described.

[0104] For reference Figure 3 As described, the reliability distance 430 can be dynamically adjusted based on the environmental parameters of the wireless communication system 400-a and the positioning parameters of the VUE 415-a (e.g., the position of the VUE 415-a relative to the interaction point 420 or the interaction area 425-a).

[0105] The wireless communication system 400-a can indicate the moment when VUE 415-a-1 is approaching the interaction point 420-a. The interaction point 420-a can be within the interaction area 425-a, as shown in the reference. Figure 3 As described. (See reference) Figure 3As described, the reliability distance 430-a corresponding to the NACK area used for multicast messages can be dynamically adjusted (e.g., by RSU 405-a or VUE 415-a-1) to include the interaction area 425-a and can be centered on VUE 415-a-1. For example, based on the reliability distance 430-a, other VUEs 415 of the wireless communication system 400-a can receive multicast messages. For example, VUEs 415-b-1 and VUE 415-d-1 can be within the interaction area 425-a and can receive multicast messages, alternatively, VUE 415-c-1 can be outside the interaction area 425-a and cannot receive multicast messages.

[0106] Figure 4B An example of a wireless communication system 400-b supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. The wireless communication system 400-b may support V2X communication / operation. The wireless communication system 400-b may include a VUE 415 and an RSU 405, which may be as described in reference... Figure 3 The VUE 315 and RSU 305 described herein, as well as those referenced Figure 4A Examples of VUE 415 and RSU 405 described.

[0107] Wireless communication system 400-b may represent wireless communication system 400-a at a second time, in which VUE 415-a-2 may be closer to interaction point 420-b than VUE 415-a-1 is closer to interaction point 420-a. At this second time, the reliability distance 430-b may be dynamically adjusted (e.g., by RSU 405-b or VUE 415-a-2) to include interaction area 425-b. In some cases, the reliability distance 430-b may be smaller than the reliability distance 430-a. In some cases, when VUE 415-a is close to interaction point 420-b, the reliability distance 430-b may be the same size or nearly the same size as interaction area 425-b. In some cases, VUE 415-b-2 and VUE 415-d-2 may be within the reliability distance 415-b and may receive multicast messages. Alternatively, VUE 415-c-2 may be located outside the reliability distance 430-b and may not receive multicast messages.

[0108] Figure 4C An example of a wireless communication system 400-c supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. The wireless communication system 400-c may support V2X communication / operation. The wireless communication system 400-c may include a VUE 415 and an RSU 405, which may be as described in reference... Figure 3 The VUE 315 and RSU 305 described herein, as well as those referenced Figure 4A and Figure 4B Examples of VUE 415 and RSU 405 described.

[0109] Wireless communication system 400-c may represent wireless communication system 400-a and wireless communication system 400-b at a third time (such as when VUE 415-a-3 has passed the interaction point 420-c). At the third time, the reliability distance 430-c may be dynamically adjusted (e.g., by RSU 405-c or VUE 415-a-3) to include the interaction area 425-c. In some cases, the reliability distance 430-c may be greater than the reliability distance 430-b. In some cases, VUE 415-b-3, VUE 415-c-3, and VUE 415-d-3 may be within the reliability distance 430-c and may receive multicast messages.

[0110] Figure 5 An example of a process flow 500 supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure is shown. In some cases, elements may be added to or removed from the process flow 500.

[0111] Environmental parameter 505 can be used to determine the NACK distance 530. In some cases, environmental parameter 505 can be a map-related input. In some cases, such as reference... Figure 3 As described, environmental parameter 505 may include static road topology 510, dynamic road conditions 515, or any combination thereof. In some cases, NACK distance 530 may be related to, as referenced... Figure 3 This corresponds to the reliability distance described in Figure 4. In some cases, the NACK distance 530 may include a map overlay 535, as shown in the reference. Figure 3 As described.

[0112] Location parameter 520 can be used to determine the current location 540 of the VUE. In some cases, location parameter 520 may include the VUE's location and motion status 525. In some cases, the VUE's location and motion status 525 may be received from the VUE, RSU, network entity, third-party map or tracking service, or any combination thereof.

[0113] At position 545, the VUE's current location 540 and positioning parameters 520, along with the NACK distance 530, can be used to predict the VUE's future location. In some cases, the cloud entity can predict the VUE's future location. In some cases, the future location can be based on the VUE's current location and motion state, road topology, destination information from third-party map services, historical motion patterns, time of day, or any combination thereof.

[0114] At 550, the reliability distance can be determined based on the predicted future location of the VUE. In some cases, the reliability distance can be based on the distance-based multicast communication NACK distance. In some cases, the reliability distance can be service type specific, such as in V2X systems that include sensor information, collective sensing, or manipulation coordination systems. In some cases, the reliability distance can be determined by the cloud entity.

[0115] At point 555, based on a determined reliability distance, a cloud entity, RSU, network entity, or any combination thereof can output a reliability distance. In some cases, the reliability distance can be output individually to a VUE via dedicated signaling. In other cases, the reliability distance can be output to multiple VUEs via common signaling.

[0116] Figure 6 An example of a process flow 600 supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure is shown. Process flow 600 can implement reference... Figures 1-5 Various aspects of this disclosure are described. Process flow 500 may include VUE 615-a, VUE 615-b, and RSU 605, which may be as referenced. Figures 1-5 Examples of VUE, RSU, and network entities described.

[0117] It should be understood that the devices described through process flow 600 may communicate or couple with other devices or nodes not illustrated. For example, VUE 615-a and RSU 605 may communicate with one or more other UEs, network entities, or other devices. Alternative examples are possible, some of which may be performed in a different order than described or may not be performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

[0118] In some cases, at 620, VUE 615-a, VUE 615-b, RSU 605, or any combination thereof, can transmit V2X system status. For example, RSU 605 can communicate with VUE 615 to obtain one or more statuses of the V2X system. In some cases, V2X system status may include positioning parameters of VUE 615-a or environmental parameters associated with the V2X system, such as references... Figures 3 to 5 As described.

[0119] At position 625, RSU 605 can obtain positioning parameters. For example, RSU 605 can obtain one or more positioning parameters for VUE 615-a. In some cases, RSU 605 can obtain positioning parameters that may include the current vehicle position of VUE 615-a, the motion state of VUE 615-a (e.g., speed, heading), or any combination thereof. In some cases, based on the positioning parameters, RSU 605 can predict the future position of VUE 615-a at a future time. For example, the predicted future position of VUE 615-a may be based on the current vehicle position of VUE 615-a, environmental parameters associated with the V2X system, information associated with the destination of VUE 615-a, historical location information of VUE 615-a, or any combination thereof. In some cases, the RSU 605 may obtain positioning parameters from VUE 615-a, from one or more sensors of the RSU 605, from third-party map services, from the core network, from cloud entities, or any combination thereof.

[0120] At 630, the RSU 605 can obtain one or more environmental parameters of the V2X system. In some cases, the RSU 605 can obtain environmental parameters from one or more sensors of the RSU 605, from one or more VUE 615s, from third-party map services, from the core network, or any combination thereof.

[0121] In some cases, at 635, the RSU 605 can sense the status of the V2X system. For example, the RSU 605 can use one or more of its sensors (e.g., a camera) to sense the status of the V2X system (e.g., environmental parameters, positioning parameters).

[0122] At position 640, VUE 615-a can generate multicast messages. Multicast messages may include sensor information, manipulation coordination information, or any combination thereof relative to the V2X system. In some cases, multicast messages may include information related to VUE 615-a and the interaction point or interaction area.

[0123] In some cases, at 645, RSU 605 can send one or more environmental parameters, and VUE 615-a can receive these environmental parameters. For example, multicast messages can be sent based on reliability distance, where the reliability distance is based on the location parameters of VUE 615-a and the environmental parameters associated with the V2X system, and if VUE 615-a determines the reliability distance, as referenced... Figure 3 As described, the VUE 615-a can use one or more environmental parameters provided by the RSU 605 in combination with one or more positioning parameters of the VUE 615-a to determine the reliability distance.

[0124] In some cases, at 650, the RSU 605 can be configured with a reliability distance, as shown in the reference. Figure 3 As described, the RSU 605 can be configured with reliability distance based on one or more environmental parameters, the service type of VUE 615-a, the service type of one or more other VUE 615s (e.g., VUE615-b), or any combination thereof. In some cases, the RSU 605 can be configured with reliability distance based on communication with VUE 615-a (e.g., to obtain location parameters) and communication with one or more other VUE 615s (e.g., to obtain location parameters, environmental parameters, or any combination thereof from VUE 615-b).

[0125] At position 655, RSU 605 can output an indication of reliability distance. The reliability distance may correspond to the area used to provide feedback for multicast messages. In some cases, RSU 605 may output the reliability distance indication based on obtained predictions of the future vehicle location for VUE 615-a or other VUE 615. In some cases, RSU 605 may output the reliability distance indication based on the service type of the V2X system.

[0126] In some cases, at 660, RSU 605 may transmit a reliability distance indication, and VUE 615-a may receive this reliability distance indication. In some cases, RSU 605 may transmit the reliability distance indication via a unicast message dedicated to VUE 615-a, a Radio Resource Control (RRC) reconfiguration message, a PC5 RRC message, a PC5 sidelink message, an RRC message via a Uu communication link, or any combination thereof. In some cases, VUE 615-a may receive the reliability distance indication as part of ADAS map enhancement. In some cases, the reliability distance indication may include an array of paired values ​​of NACK distance and interaction point distance. For example, if the reliability distance is 300 meters and if the interaction point is 500 meters away from VUE 615-a, the reliability distance indication may include an array of paired values ​​(300, 500). In some cases, the reliability distance indication may include inputs for a formula. For example, the formula for the reliability distance may be... ,in This could be a reliability distance (e.g., distance-based multicast feedback (NACK) distance). This could be the size of the interaction area (e.g., the diameter of the area used for reliable multicast). This can be the VUE 615-a distance (e.g., the distance between VUE 615-a and the interaction point), and This can be a NACK range adjustment multiplier. In some cases, the formula for reliability distance may also include an indication of the center of the interaction point or interaction area, which may include the latitude and longitude of the interaction point. When the reliability distance is determined by a formula, VUE 615-a may receive one or more inputs from the inputs used in the formula (e.g., , , (or any combination thereof). In some cases, reliability distance indicators may include enumerated values ​​such as latitude and longitude micrometer indicators, range values, and distances from the interaction point.

[0127] Regardless of whether the reliability indication is based on an array of paired values ​​or a formula, VUE 615-a can receive the reliability distance indication via one or more application layer elements, one or more lower-layer information elements, or any combination thereof. Information elements can be sent as unicast transmissions, such as PC5-specific signaling in PC5-RRC messages or PC5-S signaling messages. Information elements can also be sent using specialized signaling, such as Uu-specific signaling in RRC messages.

[0128] At position 665, VUE 615-a can send multicast messages, and other VUEs 615 (e.g., VUE 615-b) can receive these multicast messages. VUE 615-a can send multicast messages using a transmit power corresponding to or based on a reliability distance, which may correspond to an area used to provide feedback on multicast messages (e.g., a NACK area). For example, VUE 615-a can increase the transmit power for a larger reliability distance or decrease the transmit power for a smaller reliability distance.

[0129] At 670, VUE 615-a can monitor feedback on multicast messages based on sending multicast messages at 665.

[0130] In some cases, at point 675, VUE 615-b can send a feedback message related to a multicast message, and VUE 615-a can receive this feedback message. In some cases, the feedback message may include manipulation coordination or sensor information related to the V2X system and interaction points or areas within the V2X system.

[0131] Figure 7A block diagram 700 illustrates a device 705 supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure. Device 705 may be an example of various aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to dynamic reliability distance for wireless communication). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0133] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to dynamic reliability distance for wireless communication), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0134] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of dynamic reliability distance for wireless communication as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0135] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in at least one memory individually or collectively by one or more processors).

[0136] Alternatively or concurrently, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0137] In some examples, the communication manager 720 may be configured to use or otherwise cooperate with the receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0138] The communication manager 720 can support wireless communication according to examples disclosed herein. For example, the communication manager 720 can be configured or operated to support components for generating multicast messages for transmission by a VUE in a V2X system. The communication manager 720 can be configured or operated to support components for transmitting multicast messages using transmission power based on a reliability distance corresponding to the area used to provide feedback on the multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system. The communication manager 720 can be configured or operated to support components for monitoring feedback on multicast messages based on the transmission of multicast messages.

[0139] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720 or a combination thereof or at least one processor coupled thereto) can support techniques for reducing power consumption by allowing relatively small areas for transmitting multicast messages, thereby allowing lower transmission power and more efficient use of communication resources when the VUE is close to the interaction point.

[0140] Figure 8 A block diagram 800 of a device 805 supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0141] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to dynamic reliability distance for wireless communication). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0142] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to dynamic reliability distance for wireless communication), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0143] Device 805 or its various components may be examples of parts used to perform various aspects of dynamic reliability distance for wireless communication as described herein. For example, communication manager 820 may include generation component 825, multicast transmission component 830, feedback monitoring component 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0144] The communication manager 820 may support wireless communication according to examples disclosed herein. The generation component 825 is capable of, configured to, or operable to support components for generating multicast messages for transmission by the VUE in a V2X system. The multicast transmission component 830 is capable of, configured to, or operable to support components for transmitting multicast messages using transmission power based on a reliability distance corresponding to the area used to provide feedback for the multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system. The feedback monitoring component 835 is capable of, configured to, or operable to support components for monitoring feedback for multicast messages based on the transmission of multicast messages.

[0145] Figure 9A block diagram 900 is shown of a communication manager 920 supporting dynamic reliability distance for wireless communication according to one or more aspects of this disclosure. The communication manager 920 may be an example of aspects of the communication manager 720, communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of parts for performing the various aspects of dynamic reliability distance for wireless communication as described herein. For example, the communication manager 920 may include a generation component 925, a multicast transmission component 930, a feedback monitoring component 935, a reliability distance receiving component 940, an environmental parameter receiving component 945, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0146] The communication manager 920 can support wireless communication according to examples disclosed herein. The generation component 925 is capable of, configured to, or operable to support components for generating multicast messages for transmission by the VUE in a V2X system. The multicast transmission component 930 is capable of, configured to, or operable to support components for transmitting multicast messages using transmission power based on a reliability distance corresponding to the area used to provide feedback for the multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system. The feedback monitoring component 935 is capable of, configured to, or operable to support components for monitoring feedback for multicast messages based on the transmission of multicast messages.

[0147] In some examples, to support the transmission of multicast messages, the multicast transmission component 930 is capable of, configured to, or operable to support components for transmitting multicast messages using transmission power, wherein the transmission power is based on the location of the interaction area associated with the multicast message and based on the interaction area corresponding to the location of the interaction area, wherein the reliability distance is based on the location of the interaction area associated with the multicast message and based on the interaction area corresponding to the location of the interaction area.

[0148] In some examples, to support the transmission of multicast messages, the multicast transmission component 930 is capable of, configured to, or operable to support components for transmitting multicast messages using transmission power, wherein the transmission power is based on the vehicle location of the VUE relative to the interaction area associated with the multicast message, wherein one or more positioning parameters of the VUE include the vehicle location of the VUE.

[0149] In some examples, to support the sending of multicast messages, the multicast sending component 930 is capable of, configured to, or operable to support components for sending multicast messages based on a reliability distance, wherein the reliability distance is based on one or more static road parameters, one or more dynamic road parameters, one or more time-specific road parameters, stopping sight distance, or any combination thereof.

[0150] In some examples, in order to support the sending of multicast messages, the multicast sending component 930 is capable of, configured to, or operable to support components for sending multicast messages based on a reliability distance, wherein the reliability distance is based on the location of the VUE, the motion state of the VUE, or any combination thereof.

[0151] In some examples, to support the sending of multicast messages, the multicast sending component 930 can be configured or operable to support components for sending multicast messages based on a reliability distance, wherein the reliability distance is based on information from a third-party map service.

[0152] In some examples, the reliability distance receiving component 940 is capable of, configured to, or operable to support components for receiving an indication of reliability distance via unicast messages dedicated to VUE, radio resource control reconfiguration messages, PC5 radio resource control messages, PC5 sidelink messages, radio resource control messages via Uu communication links, or any combination thereof.

[0153] In some examples, the indication of reliability distance is received from the RSU.

[0154] In some examples, the indication of reliability distance is received as part of ADAS map enhancements.

[0155] In some examples, the environmental parameter receiving component 945 is capable of, configured to, or operable to support components for receiving indications of one or more environmental parameters associated with the V2X system, wherein the reliability distance is based on the indications of one or more environmental parameters associated with the V2X system and on one or more positioning parameters of the VUE.

[0156] In some examples, to support the transmission of multicast messages, the multicast transmission component 930 is capable of, configured to, or operable to support components for transmitting multicast messages based on a reliability distance, wherein the reliability distance is based on the service type of the VUE, the service type of the multicast message, the service type of one or more UEs of the V2X system, or any combination thereof.

[0157] In some examples, service types include manipulation sharing, sensor sharing, collective sensing, or any combination thereof.

[0158] Figure 10A diagram of a system 1000 including a device 1005 supporting dynamic reliable distance for wireless communication, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1045).

[0159] I / O controller 1010 manages the input and output signals of device 1005. I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of one or more processors, such as at least one processor 1040. In some cases, a user may interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0160] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025 as described herein, or via a wired or wireless link. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

[0161] At least one memory 1030 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1030 may store computer-readable, computer-executable code 1035, including instructions that, when executed by at least one processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by at least one processor 1040, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1030 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0162] At least one processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting dynamic reliability distance for wireless communication). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, wherein at least one processor 1040 and at least one memory 1030 are configured to perform the various functions described herein. In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1040 may be a component of a processing system, which may refer to a machine (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) or system of components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 1040 or a processing system including at least one processor 1040 may be configured, capable of being configured, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1030 or otherwise.

[0163] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 is capable of, configured to, or operable to support components for generating multicast messages for transmission by a VUE in a V2X system. The communication manager 1020 is capable of, configured to, or operable to support components for transmitting multicast messages using transmission power based on a reliability distance corresponding to the area used to provide feedback on the multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system. The communication manager 1020 is capable of, configured to, or operable to support components for monitoring feedback on multicast messages based on the transmission of multicast messages.

[0164] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for reducing power consumption by allowing relatively small areas for sending multicast messages, thereby allowing lower transmission power and more efficient use of communication resources when the VUE is close to the interaction point.

[0165] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1015, one or more antennas 1025, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported by or executed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that may be executed by at least one processor 1040 to cause the device 1005 to perform various aspects of dynamic reliability distance for wireless communication as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0166] Figure 11 A block diagram 1100 of a device 1105 supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0168] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Alternatively or concurrently, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0169] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of dynamic reliability distance for wireless communication as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0170] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in at least one memory individually or collectively by one or more processors).

[0171] Alternatively or concurrently, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0172] In some examples, the communication manager 1120 may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0173] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for obtaining one or more location parameters for a VUE within a V2X system. The communication manager 1120 may be capable of, configured to, or operable to support components for obtaining one or more environmental parameters associated with a V2X system. The communication manager 1120 may be capable of, configured to, or operable to support components for outputting an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system.

[0174] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof, or at least one processor coupled thereto) can support techniques for more efficient use of communication resources when the VUE is close to the interaction point by allowing a relatively small area for sending multicast messages.

[0175] Figure 12 A block diagram 1200 of a device 1205 supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205, or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220), may include at least one processor coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0177] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Alternatively or additionally, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0178] Device 1205 or its various components may be examples of parts for performing various aspects of dynamic reliability distance for wireless communication as described herein. For example, communication manager 1220 may include positioning parameter component 1225, environmental parameter component 1230, reliability distance component 1235, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0179] The communication manager 1220 may support wireless communication according to examples disclosed herein. The location parameter component 1225 is capable of, configured to, or operable to support components for obtaining one or more location parameters for a VUE within a V2X system. The environment parameter component 1230 is capable of, configured to, or operable to support components for obtaining one or more environment parameters associated with the V2X system. The reliability distance component 1235 is capable of, configured to, or operable to support components for outputting an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environment parameters associated with the V2X system.

[0180] Figure 13A block diagram 1300 is shown of a communication manager 1320 supporting dynamic reliable distance for wireless communication according to one or more aspects of this disclosure. The communication manager 1320 may be an example of aspects of the communication manager 1120, communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of parts for performing various aspects of dynamic reliable distance for wireless communication as described herein. For example, the communication manager 1320 may include a positioning parameter component 1325, an environmental parameter component 1330, a reliable distance component 1335, a communication component 1340, a sensing component 1345, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0181] The communication manager 1320 may support wireless communication according to examples disclosed herein. The location parameter component 1325 is capable of, configured to, or operable to support components for obtaining one or more location parameters for a VUE within a V2X system. The environment parameter component 1330 is capable of, configured to, or operable to support components for obtaining one or more environment parameters associated with the V2X system. The reliability distance component 1335 is capable of, configured to, or operable to support components for outputting an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environment parameters associated with the V2X system.

[0182] In some examples, the reliability distance component 1335 is capable of, configured to, or operable to support components for configuring reliability distance based on one or more environmental parameters, the service type of the VUE, and the service type of one or more other UEs of the V2X system.

[0183] In some examples, in order to support the acquisition of one or more positioning parameters for the VUE, the positioning parameter component 1325 can be configured or operable to support components for obtaining the current vehicle location and motion state of the VUE.

[0184] In some examples, to support the output of an indication of reliability distance, the reliability distance component 1335 is capable of, configured to, or operable to support components for predicting the future location of the VUE at a future time, the predicted future location of the VUE being based on the VUE’s current vehicle location, the VUE’s motion state, one or more environmental parameters associated with the V2X system, information associated with the VUE’s destination, the VUE’s historical location information, or any combination thereof.

[0185] In some examples, in order to support the output of an indication of reliability distance, the reliability distance component 1335 is capable of, configured to, or operable to support a component for outputting an indication of reliability distance based on a prediction obtained.

[0186] In some examples, in order to support the output of an indication of reliability distance, the reliability distance component 1335 is capable of, configured to, or operable to support the output of an indication of reliability distance for service types of V2X-based systems.

[0187] In some examples, in order to support the output of an indication of reliability distance, the reliability distance component 1335 is capable of, configured to, or operable to support components for outputting an indication of reliability distance to a VUE or to one or more other UEs associated with the V2X system, or both.

[0188] In some examples, the communication component 1340 is capable of, configured to, or operable to support components for communicating with one or more other UEs within the V2X system to obtain one or more conditions of the V2X system.

[0189] In some examples, the sensing component 1345 is capable of, configured to, or operable to support components for sensing one or more conditions of a V2X system using one or more sensors.

[0190] In some examples, communication component 1340 is capable of, configured to, or operable to support components for communicating with one or more other UEs within the V2X system. In some examples, reliability distance component 1335 is capable of, configured to, or operable to support components for configuring reliability distance based on communication with one or more other UEs within the V2X system.

[0191] In some examples, the reliability distance is based on the interaction area corresponding to the location of the interaction area associated with the multicast message and the interaction area corresponding to the location of the interaction area.

[0192] In some examples, in order to support the output of an indication of reliability distance, the reliability distance component 1335 can be, configured, or operated to support components for outputting an indication of reliability distance, wherein the reliability distance is based on the vehicle position of the VUE relative to the interaction area.

[0193] In some examples, in order to support the output of an indication of reliability distance, the reliability distance component 1335 is capable of, configured to, or operable to support components for outputting an indication of reliability distance, wherein the reliability distance is based on one or more static road parameters, one or more dynamic parameters, one or more time-specific parameters, stopping sight distance, or any combination thereof.

[0194] In some examples, in order to support the acquisition of one or more positioning parameters for VUE, the positioning parameter component 1325 can be, configured, or operated to support components for obtaining one or more positioning parameters for VUE from a third-party map service.

[0195] In some examples, in order to support the output of an indication of reliability distance, the reliability distance component 1335 can be, configured, or operated to support a component for outputting an indication of reliability distance as part of ADAS map enhancement.

[0196] Figure 14 A diagram of a system 1400 including a device 1405 supporting dynamic reliable distance for wireless communication, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components supporting output and obtaining communication, such as a communication manager 1420, a transceiver 1410, an antenna 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1440).

[0197] As described herein, transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, transceiver 1410 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1410 may also include a modem for modulating signals to provide modulated signals for transmission (e.g., via one or more antennas 1415, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1415, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0198] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by one or more of at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by one of the at least one processor 1435, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0199] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting dynamic reliability distance for wireless communication). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more of the at least one processor 1435, wherein at least one processor 1435 and at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories of at least one memory 1425). In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1435 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1435) and memory circuitry (which may include at least one memory 1425)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1435 or a processing system including at least one processor 1435 may be configured, can be configured, or can be operated to cause the device 1405 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1425 or otherwise.

[0200] In some examples, bus 1440 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

[0201] In some examples, the communication manager 1420 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1420 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1420 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1420 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0202] The communication manager 1420 may support wireless communication according to examples disclosed herein. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for obtaining one or more location parameters for a VUE within a V2X system. The communication manager 1420 may be capable of, configured to, or operable to support components for obtaining one or more environmental parameters associated with a V2X system. The communication manager 1420 may be capable of, configured to, or operable to support components for outputting an indication of a reliability distance corresponding to an area used to provide feedback for multicast messages, wherein the reliability distance is based on one or more location parameters of the VUE and one or more environmental parameters associated with the V2X system.

[0203] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for more efficient use of communication resources when the VUE is close to the interaction point by allowing a relatively small area for sending multicast messages.

[0204] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that may be executed by one or more of the at least one processor 1435 to cause the device 1405 to perform various aspects of the dynamic reliability distance for wireless communication as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations individually or jointly.

[0205] Figure 15 A flowchart illustrating a method 1500 for supporting dynamic reliable distance for wireless communication according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be implemented by, as referenced... Figures 1 to 10 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Alternatively or concurrently, the UE may use dedicated hardware to perform aspects of the described functions.

[0206] At 1505, the method may include generating a multicast message for the VUE to send in the V2X system. The operation of box 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be derived from references... Figure 9 The described generation component 925 is executed.

[0207] At 1510, the method may include transmitting multicast messages using a transmission power based on a reliability distance corresponding to the area used to provide feedback for the multicast messages, wherein the reliability distance is based on one or more positioning parameters of the VUE and one or more environmental parameters associated with the V2X system. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 9 The multicast sending component 930 described is executed.

[0208] At 1515, the method may include monitoring feedback to multicast messages based on the transmission of multicast messages. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 9 The feedback monitoring component 935 described is executed.

[0209] Figure 16 A flowchart illustrating a method 1600 for supporting dynamic reliable distance for wireless communication according to various aspects of this disclosure is shown. The operation of method 1600 may be implemented by a network entity or its components as described herein. For example, the operation of method 1600 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0210] At 1605, the method may include obtaining one or more positioning parameters for the VUE within the V2X system. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be derived from references... Figure 13 The described positioning parameter component 1325 is executed.

[0211] At 1610, the method may include obtaining one or more environmental parameters associated with the V2X system. The operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 13 The described environmental parameter component 1330 is executed.

[0212] At 1615, the method may include outputting an indication of a reliability distance corresponding to a region used to provide feedback for multicast messages, wherein the reliability distance is based on one or more positioning parameters of the VUE and one or more environmental parameters associated with the V2X system. Operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1615 may be provided by reference to [reference needed]. Figure 13 The reliability distance component 1335 is described.

[0213] The following provides an overview of the various aspects of this disclosure:

[0214] Aspect 1: A method for wireless communication by a VUE, the method comprising: generating a multicast message for transmission by the VUE in a V2X system; transmitting the multicast message using a transmission power at least partially based on a reliability distance corresponding to an area for providing feedback on the multicast message, wherein the reliability distance is at least partially based on one or more positioning parameters of the VUE and at least partially based on one or more environmental parameters associated with the V2X system; and monitoring feedback on the multicast message at least partially based on the transmission of the multicast message.

[0215] Aspect 2: According to the method of aspect 1, sending the multicast message includes: using the transmission power to send the multicast message, wherein the transmission power is based at least in part on the location of the interaction area associated with the multicast message and at least in part on the interaction area corresponding to the location of the interaction area, wherein the reliability distance is based at least in part on the location of the interaction area associated with the multicast message and at least in part on the interaction area corresponding to the location of the interaction area.

[0216] Aspect 3: According to the method of aspect 2, sending the multicast message includes: using the transmission power to send the multicast message, wherein the transmission power is based at least in part on the vehicle location of the VUE relative to the interaction area associated with the multicast message, wherein the one or more positioning parameters of the VUE include the vehicle location of the VUE.

[0217] Aspect 4: The method according to any one of Aspects 1 to 3, wherein sending the multicast message comprises: sending the multicast message at least in part based on the reliability distance, wherein the reliability distance is at least in part based on one or more static road parameters, one or more dynamic road parameters, one or more time-specific road parameters, stopping sight distance, or any combination thereof.

[0218] Aspect 5: The method according to any one of Aspects 1 to 4, wherein sending the multicast message comprises: sending the multicast message at least in part based on the reliability distance, wherein the reliability distance is at least in part based on the location of the VUE, the motion state of the VUE, or any combination thereof.

[0219] Aspect 6: According to the method of aspect 5, sending the multicast message includes: sending the multicast message based at least in part on the reliability distance, wherein the reliability distance is based at least in part on information from a third-party map service.

[0220] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving an indication of the reliability distance via a unicast message dedicated to the VUE, a radio resource control reconfiguration message, a PC5 radio resource control message, a PC5 sidelink message, a radio resource control message via a Uu communication link, or any combination thereof.

[0221] Aspect 8: According to the method of aspect 7, wherein the indication of the reliability distance is received from a roadside unit (RSU).

[0222] Aspect 9: The method according to any one of Aspects 7 to 8, wherein the indication of the reliability distance is received as part of an advanced driver assistance system (ADAS) map enhancement.

[0223] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: receiving an indication of the one or more environmental parameters associated with the V2X system, wherein the reliability distance is based at least in part on the indication of the one or more environmental parameters associated with the V2X system and at least in part on the one or more positioning parameters of the VUE.

[0224] Aspect 11: The method according to any one of Aspects 1 to 10, wherein sending the multicast message further comprises: sending the multicast message at least in part based on the reliability distance, wherein the reliability distance is at least in part based on the service type of the VUE, the service type of the multicast message, the service type of one or more UEs of the V2X system, or any combination thereof.

[0225] Aspect 12: The method according to aspect 11, wherein the service type includes manipulation sharing, sensor sharing, collective sensing, or any combination thereof.

[0226] Aspect 13: A method for wireless communication by a network entity, the method comprising: obtaining one or more positioning parameters for a VUE within a vehicle-to-everything (V2X) system; and obtaining one or more environmental parameters associated with the V2X system; and outputting an indication of a reliability distance corresponding to an area for providing feedback for multicast messages, wherein the reliability distance is based at least in part on the one or more positioning parameters of the VUE and the one or more environmental parameters associated with the V2X system.

[0227] Aspect 14: The method according to aspect 13, the method further comprising: configuring the reliability distance based at least in part on the one or more environmental parameters, the service type of the VUE, and the service type of one or more other UEs of the V2X system.

[0228] Aspect 15: The method according to any one of Aspects 13 to 14, wherein obtaining the one or more positioning parameters for the VUE further includes: obtaining the current vehicle location of the VUE and the motion state of the VUE.

[0229] Aspect 16: The method according to any one of Aspects 13 to 15, wherein the output of the indication of the reliability distance further comprises: predicting the future location of the VUE at a future time, the predicted future location of the VUE being based at least in part on the current vehicle location of the VUE, the motion state of the VUE, the one or more environmental parameters associated with the V2X system, information associated with the destination of the VUE, historical location information of the VUE, or any combination thereof.

[0230] Aspect 17: According to the method of aspect 16, the output of the indication of the reliability distance further includes: outputting the indication of the reliability distance based at least in part on the predicted future location of the VUE.

[0231] Aspect 18: The method according to aspect 17, wherein outputting the indication of the reliability distance further comprises: outputting the indication of the reliability distance based at least in part on the service type of the multicast message.

[0232] Aspect 19: The method according to any one of Aspects 13 to 18, wherein outputting the indication of the reliability distance further comprises: outputting the indication of the reliability distance to the VUE or outputting the indication of the reliability distance to one or more other UEs associated with the V2X system, or both of these operations.

[0233] Aspect 20: The method according to any one of aspects 13 to 19, the method further comprising: communicating with one or more other UEs within the V2X system to obtain one or more conditions of the V2X system.

[0234] Aspect 21: The method according to any one of aspects 13 to 20, the method further comprising: using one or more sensors to sense one or more conditions of the V2X system.

[0235] Aspect 22: The method according to any one of aspects 13 to 21, the method further comprising: communicating with one or more other UEs within the V2X system; and configuring the reliability distance based at least in part on the communication with the one or more other UEs within the V2X system.

[0236] Aspect 23: The method according to any one of Aspects 13 to 22, wherein the reliability distance is based at least in part on the interaction region corresponding to the location of the interaction region associated with the multicast message and at least in part on the interaction region corresponding to the location of the interaction region.

[0237] Aspect 24: According to the method of aspect 23, the output of the indication of the reliability distance further includes: outputting the indication of the reliability distance, wherein the reliability distance is based at least in part on the vehicle position of the VUE relative to the interaction area.

[0238] Aspect 25: The method according to any one of Aspects 13 to 24, wherein outputting the indication of the reliability distance further comprises: outputting the indication of the reliability distance, wherein the reliability distance is based at least in part on one or more static road parameters, one or more dynamic parameters, one or more time-specific parameters, stopping sight distance, or any combination thereof.

[0239] Aspect 26: The method according to any one of Aspects 13 to 25, wherein obtaining the one or more positioning parameters for the VUE further comprises: obtaining the one or more positioning parameters for the VUE from a third-party map service.

[0240] Aspect 27: The method according to any one of Aspects 13 to 26, wherein outputting the indication of the reliability distance further comprises: outputting the indication of the reliability distance as part of an advanced driver assistance system (ADAS) map enhancement.

[0241] Aspect 28: A VUE for wireless communication, the VUE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 12.

[0242] Aspect 29: A VUE for wireless communication, the VUE comprising at least one component for performing the method according to any one of aspects 1 to 12.

[0243] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 12.

[0244] Aspect 31: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 13 to 27.

[0245] Aspect 32: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 13 to 27.

[0246] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 13 to 27.

[0247] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0248] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0249] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0250] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0251] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0252] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0253] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0254] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of those one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0255] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0256] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0257] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0258] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A vehicle user equipment (UE), the vehicle user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the vehicle UE: Generate multicast messages for transmission by the vehicle UE in the vehicle-to-everything (V2X) system; The multicast message is transmitted using a transmission power at least in part based on a reliability distance corresponding to the area used to provide feedback on the multicast message, wherein the reliability distance is at least in part based on one or more positioning parameters of the vehicle UE and at least in part based on one or more environmental parameters associated with the V2X system; and Feedback to the multicast messages is monitored, at least in part, based on the transmission of the multicast messages.

2. The vehicle UE of claim 1, wherein, in order to send the multicast message, the one or more processors are capable of operating individually or jointly to execute the code to cause the vehicle UE to: The multicast message is transmitted using the transmit power, wherein the transmit power is based at least in part on the location of the interaction area associated with the multicast message and at least in part on the interaction area corresponding to the location of the interaction area, wherein the reliability distance is based at least in part on the location of the interaction area associated with the multicast message and at least in part on the interaction area corresponding to the location of the interaction area.

3. The vehicle UE of claim 2, wherein, in order to send the multicast message, the one or more processors are capable of operating individually or jointly to execute the code to cause the vehicle UE to: The multicast message is transmitted using the transmit power, wherein the transmit power is based at least in part on the vehicle location of the vehicle UE relative to the interaction area associated with the multicast message, wherein the one or more positioning parameters of the vehicle UE include the vehicle location of the vehicle UE.

4. The vehicle UE of claim 1, wherein, in order to send the multicast message, the one or more processors are capable of operating individually or jointly to execute the code to cause the vehicle UE to: The multicast message is sent based at least in part on the reliability distance, wherein the reliability distance is based at least in part on one or more static road parameters, one or more dynamic road parameters, one or more time-specific road parameters, stopping sight distance, or any combination thereof.

5. The vehicle UE of claim 1, wherein, in order to send the multicast message, the one or more processors are capable of operating individually or jointly to execute the code to cause the vehicle UE to: The multicast message is transmitted based at least in part on the reliability distance, wherein the reliability distance is based at least in part on the location of the vehicle UE, the motion state of the vehicle UE, or any combination thereof.

6. The vehicle UE of claim 5, wherein, in order to send the multicast message, the one or more processors are capable of operating individually or jointly to execute the code to cause the vehicle UE to: The multicast message is sent based at least in part on the reliability distance, wherein the reliability distance is based at least in part on information from a third-party map service.

7. The vehicle UE of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the vehicle UE to: The indication of the reliability distance is received via unicast messages dedicated to the vehicle UE, radio resource control reconfiguration messages, PC5 radio resource control messages, PC5 sidelink messages, radio resource control messages via the Uu communication link, or any combination thereof.

8. The vehicle UE of claim 7, wherein the indication of the reliability distance is received from a roadside unit (RSU).

9. The vehicle UE of claim 7, wherein the indication of the reliability distance is received as part of an advanced driver assistance system (ADAS) map enhancement.

10. The vehicle UE of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the vehicle UE to: Receive indications of one or more environmental parameters associated with the V2X system, wherein the reliability distance is based at least in part on the indications of the one or more environmental parameters associated with the V2X system and at least in part on the one or more positioning parameters of the vehicle UE.

11. The vehicle UE of claim 1, wherein, in order to send the multicast message, the one or more processors are individually or jointly capable of further operating to execute the code to cause the vehicle UE to: The multicast message is sent at least in part based on the reliability distance, wherein the reliability distance is at least in part based on the service type of the vehicle UE, the service type of the multicast message, the service type of one or more UEs of the V2X system, or any combination thereof.

12. The vehicle UE of claim 11, wherein the service type includes manipulation sharing, sensor sharing, collective sensing, or any combination thereof.

13. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Obtain one or more positioning parameters for use in vehicle user equipment (UE) within a vehicle-to-everything (V2X) system; Obtain one or more environmental parameters associated with the V2X system; and The output indicates a reliability distance corresponding to the area used to provide feedback for multicast messages, wherein the reliability distance is based at least in part on the one or more positioning parameters of the vehicle UE and the one or more environmental parameters associated with the V2X system.

14. The network entity of claim 13, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The reliability distance is configured at least in part based on one or more environmental parameters, the service type of the vehicle UE, and the service type of one or more other UEs in the V2X system.

15. The network entity of claim 13, wherein, in order to obtain the one or more positioning parameters for the vehicle UE, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: Obtain the current location of the vehicle UE and the motion state of the vehicle UE.

16. The network entity of claim 13, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: The predicted future location of the vehicle UE at a future time is based at least in part on the vehicle UE's current vehicle location, the vehicle UE's motion state, one or more environmental parameters associated with the V2X system, information associated with the vehicle UE's destination, the vehicle UE's historical location information, or any combination thereof.

17. The network entity of claim 16, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: The indication of the reliability distance is output at least in part based on the predicted future location of the vehicle UE.

18. The network entity of claim 17, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: The indication of the reliability distance is output at least in part based on the service type of the multicast message.

19. The network entity of claim 13, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: Output the indication of the reliability distance to the vehicle UE or to one or more other UEs associated with the V2X system, or both.

20. The network entity of claim 13, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Communicate with one or more other UEs within the V2X system to obtain one or more statuses of the V2X system.

21. The network entity of claim 13, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: One or more sensors are used to sense one or more conditions of the V2X system.

22. The network entity of claim 13, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Communicating with one or more other UEs within the V2X system; and The reliability distance is configured at least in part based on communication with one or more other UEs within the V2X system.

23. The network entity of claim 13, wherein the reliability distance is based at least in part on the interaction region corresponding to the location of the interaction region associated with the multicast message and at least in part on the interaction region corresponding to the location of the interaction region.

24. The network entity of claim 23, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: Output the indication of the reliability distance, wherein the reliability distance is based at least in part on the vehicle UE's vehicle position relative to the interaction area.

25. The network entity of claim 13, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: Output the indication of the reliability distance, wherein the reliability distance is based at least in part on one or more static road parameters, one or more dynamic parameters, one or more time-specific parameters, stopping sight distance, or any combination thereof.

26. The network entity of claim 13, wherein, in order to obtain the one or more positioning parameters for the vehicle UE, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: The one or more positioning parameters for the vehicle UE are obtained from a third-party map service.

27. The network entity of claim 13, wherein, in order to output the indication of the reliability distance, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: The output of the indication of the reliability distance is part of the advanced driver assistance system (ADAS) map enhancement.

28. A method for wireless communication by a vehicle user equipment (UE), the method comprising: Generate multicast messages for transmission by the vehicle UE in the vehicle-to-everything (V2X) system; The multicast message is transmitted using a transmission power at least in part based on a reliability distance corresponding to the area used to provide feedback on the multicast message, wherein the reliability distance is at least in part based on one or more positioning parameters of the vehicle UE and at least in part based on one or more environmental parameters associated with the V2X system; and Feedback to the multicast messages is monitored, at least in part, based on the transmission of the multicast messages.

29. The method of claim 28, wherein sending the multicast message comprises: The multicast message is transmitted using the transmit power, wherein the transmit power is based at least in part on the location of the interaction area associated with the multicast message and at least in part on the interaction area corresponding to the location of the interaction area, wherein the reliability distance is based at least in part on the location of the interaction area associated with the multicast message and at least in part on the interaction area corresponding to the location of the interaction area.

30. A method for wireless communication by a network entity, the method comprising: Obtain one or more positioning parameters for use in vehicle user equipment (UE) within a vehicle-to-everything (V2X) system; Obtain one or more environmental parameters associated with the V2X system; and The output indicates a reliability distance corresponding to the area used to provide feedback for multicast messages, wherein the reliability distance is based at least in part on the one or more positioning parameters of the vehicle UE and the one or more environmental parameters associated with the V2X system.

Images