Patent Description:
Vehicle to everything communications seek to enable vehicles to communicate with one another to provide a host of services, including vehicle to vehicle communications (V2V), vehicle to infrastructure (V2I) communications, vehicle to grid (V2G) communications and vehicle to people (V2P) communications. Conventional wireless communication relies on network configuring essential physical layer parameter (number of antenna port, number of MIMO layer, MCS, etc.) at a relative slow time scale. Given the high mobility of cars, and the lack of network infrastructure in V2X applications, a more dynamic, autonomous framework should be designed to allow vehicular devices to configure itself with such essential parameters using its own perceived input and the information received from other devices.

<CIT> relates to methods, devices and computer programs for adapting direct vehicle-to-vehicle communication based on information about locationdependent transmission parameters.

After considering this discussion, and particularly after reading the section entitled "Detailed Description" one will understand how the features of this disclosure provide advantages that include improved communications in a wireless network.

In accordance with the present invention, there is provided a method for wireless communication by a first wireless device as set out in claim <NUM>, an apparatus for wireless communication as set out in claim <NUM> and a computer-readable medium as set out in claim <NUM>. Other aspects of the invention can be found in the dependent claims.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for long term evolution (LTE) vehicle-to-everything communications systems and specifically new radio V2X (NR V2X) systems. Embodiments may also be applicable to LTE vehicle-to-everything (LTE-V2X) technologies to address vehicular wireless communications to enhance road safety and the driving experience.

NR V2X systems may support normal (e.g., lower priority) V2X traffic (e.g., for sensor sharing, intention sharing, etc.) in addition to higher priority V2X traffic (e.g., high reliability high range communication (HRHRC) V2X traffic). Compared to normal V2X traffic, higher priority V2X traffic may have a higher range and/or may be sent with higher reliability. Examples of higher priority V2X traffic includes, but is not limited to, data traffic associated with coordinated driving between vehicles, data traffic for intersection management (e.g., to allow intersection crossing(s) without waiting for traffic light(s)), etc. Examples of normal V2X traffic, includes, but is not limited to, data traffic for sensor information sharing between neighbor vehicles, data traffic for intention sharing between vehicles, etc. As the number of devices that support HRHRC continues to increase, it may be expensive to reserve resources for HRHRC in all areas all the time. Accordingly, it may be desirable to provide techniques for efficient resource utilization for HRHRC.

Aspects presented herein provide techniques for zone-based resource partitioning for HRHRC that can be used to provide efficient resource utilization for HRHRC. As described below, one or more geographical zones are configured for wireless devices (e.g., V2X devices) and additional resources may be allocated for HRHRC within the geographical zone(s).

In some aspects, the resources within the geographical zone(s) may be partitioned/allocated between normal resources (e.g., for normal V2X traffic) and HRHRC resources (e.g., for HRHRC V2X traffic). In some aspects, the resources outside of the geographical zone(s) may be designated for normal V2X traffic.

A UE determines whether to use the normal resources or the HRHRC resources based in part on a location of the UE (e.g., whether the UE is within the geographical zone(s) or outside of the geographical zone(s)) and the type of traffic (e.g., low priority traffic, high priority traffic, etc.) the UE wants to exchange. The UE may communicate (e.g., exchange the type of traffic) with at least another wireless device (e.g., another V2X device) using the normal or HRHRC resources in accordance with the determination.

Although particular aspects are described herein, many variations and permutations of these aspects fall within the scope of the disclosure. Although some benefits and advantages of the preferred aspects are mentioned, the scope of the disclosure is not intended to be limited to particular benefits, uses, or objectives. Rather, aspects of the disclosure are intended to be broadly applicable to different wireless technologies, system configurations, networks, and transmission protocols, some of which are illustrated by way of example in the figures and in the following description of the preferred aspects. The detailed description and drawings are merely illustrative of the disclosure rather than limiting, the scope of the disclosure being defined by the appended claims and equivalents thereof.

The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies, such as a <NUM> nextgen/NR network.

NR access (e.g., <NUM> technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., <NUM> or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., <NUM> or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC).

NR introduces the concept of network slicing. For example, a network may have multiple slices, which may support different services, for example, internet of everything (IoE), URLLC, eMBB, vehicle-to-vehicle (V2V) communications, etc. A slice may be defined as a complete logical network that comprises of a set of network functions and corresponding resources necessary to provide certain network capabilities and network characteristics.

<FIG> illustrates an example wireless communication network <NUM>, such as a new radio (NR) or <NUM> network, in which aspects of the present disclosure may be performed, e.g., for zone-based partitioning of resources for HRHRC communications for NR V2X. For example, as illustrated, the wireless communication network <NUM> may include one or more geographical zones <NUM>-<NUM> and <NUM>-<NUM> in which additional resources are allocated for high priority V2X traffic (e.g., HRHRC V2X traffic), relative to the amount of resources allocated for high priority V2X traffic and/or low priority V2X traffic outside of the geographical zone(s) <NUM>. The wireless communication network <NUM> may include one or more V2X devices that can use the additional resources within the geographical zone(s) <NUM> to communicate with other V2X devices in the wireless communication network <NUM>. In the depicted example, vehicles 120v-<NUM>, 120v-<NUM>, and 120v-<NUM> may be may be one type of UE supported by the wireless communication network <NUM> and may communicate with other vehicles, via V2X communications.

Using the techniques presented herein, a V2X device in the wireless communication network <NUM> may determine based, at least in part, on a location of the V2X device, whether to use the additional resources for the V2X traffic or to use another set of resources for the V2X traffic. As shown in this example, vehicle 120v-<NUM> is located within geographical zone <NUM>-<NUM> and may determine to use the additional resources allocated for the V2X traffic within the geographical zone <NUM>-<NUM>. Similarly, vehicle 120v-<NUM> is located within geographical zone <NUM>-<NUM> and may determine to use the additional resources allocated for the V2X traffic within the geographical zone <NUM>-<NUM>. Vehicle 120v-<NUM>, on the other hand, is located outside of the geographical zones <NUM>-<NUM> and <NUM>-<NUM> and may refrain from using the additional resources allocated for the V2X traffic within the geographical zones <NUM>-<NUM> and <NUM>-<NUM>.

As illustrated in <FIG>, the wireless communication network <NUM> may include a number of base stations (BSs) <NUM> and other network entities. A BS may be a station that communicates with user equipments (UEs). Each BS <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a Node B (NB) and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and next generation NodeB (gNB), NB, new radio base station (NR BS), <NUM> NB, access point (AP), <NUM> BS, or transmission reception point (TRP) may be interchangeable. In some examples, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

In the example shownin <FIG>, a relay station 110r may communicate with the BS 110a and a UE 120r in order to facilitate communication between the BS 110a and the UE 120r.

The UEs <NUM> (e.g., 120x, 120y, 120v, etc.) may be dispersed throughout the wireless communication network <NUM>, and each UE may be stationary or mobile.

OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, subbands, etc. Each subcarrier may be modulated with data.

Aspects of the disclosure relate to apparatus, methods, processing systems, and computer readable mediums related to new radio V2X (NR V2X) systems as non-limiting examples. Other aspects may be applicable, for example, to LTE-V2X technologies, as a non-limiting example.

BSs are not the only entities that may function as a scheduling entity.

<FIG> illustrates an example architecture of a distributed radio access network (RAN) <NUM>, which may be implemented in the wireless communication network <NUM> illustrated in <FIG>. As shown in <FIG>, the distributed RAN includes Core Network (CN) <NUM> and Access Node <NUM>.

The CN <NUM> may host core network functions. CN <NUM> may be centrally deployed. CN <NUM> functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. The CN <NUM> may include the Access and Mobility Management Function (AMF) <NUM> and User Plane Function (UPF) <NUM>. The AMF <NUM> and UPF <NUM> may perform one or more of the core network functions.

The AN <NUM> may communicate with the CN <NUM> (e.g., via a backhaul interface). The AN <NUM> may communicate with the AMF <NUM> via an N2 (e.g., NG-C) interface. The AN <NUM> may communicate with the UPF <NUM> via an N3 (e.g., NG-U) interface. The AN <NUM> may include a central unit-control plane (CU-CP) <NUM>, one or more central unit-user plane (CU-UPs) <NUM>, one or more distributed units (DUs) <NUM>-<NUM>, and one or more Antenna/Remote Radio Units (AU/RRUs) <NUM>-<NUM>. The CUs and DUs may also be referred to as gNB-CU and gNB-DU, respectively. One or more components of the AN <NUM> may be implemented in a gNB <NUM>. The AN <NUM> may communicate with one or more neighboring gNBs.

The CU-CP <NUM> may be connected to one or more of the DUs <NUM>-<NUM>. The CU-CP <NUM> and DUs <NUM>-<NUM> may be connected via a F1-C interface. As shown in <FIG>, the CU-CP <NUM> may be connected to multiple DUs, but the DUs may be connected to only one CU-CP. Although <FIG> only illustrates one CU-UP <NUM>, the AN <NUM> may include multiple CU-UPs. The CU-CP <NUM> selects the appropriate CU-UP(s) for requested services (e.g., for a UE).

The CU-UP(s) <NUM> may be connected to the CU-CP <NUM>. For example, the DU-UP(s) <NUM> and the CU-CP <NUM> may be connected via an E1 interface. The CU-CP(s) <NUM> may connected to one or more of the DUs <NUM>-<NUM>. The CU-UP(s) <NUM> and DUs <NUM>-<NUM> may be connected via a F1-U interface. As shown in <FIG>, the CU-CP <NUM> may be connected to multiple CU-UPs, but the CU-UPs may be connected to only one CU-CP.

A DU, such as DUs <NUM>, <NUM>, and/or <NUM>, may host one or more TRP(s) (transmit/receive points, which may include an Edge Node (EN), an Edge Unit (EU), a Radio Head (RH), a Smart Radio Head (SRH), or the like). A DU may be located at edges of the network with radio frequency (RF) functionality. A DU may be connected to multiple CU-UPs that are connected to (e.g., under the control of) the same CU-CP (e.g., for RAN sharing, radio as a service (RaaS), and service specific deployments). DUs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE. Each DU <NUM>-<NUM> may be connected with one of AU/RRUs <NUM>-<NUM>. The DU may be connected to an AU/RRU via each of the F1-C and F1-U interfaces.

The CU-CP <NUM> may be connected to multiple DU(s) that are connected to (e.g., under control of) the same CU-UP <NUM>. Connectivity between a CU-UP <NUM> and a DU may be established by the CU-CP <NUM>. For example, the connectivity between the CU-UP <NUM> and a DU may be established using Bearer Context Management functions. Data forwarding between CU-UP(s) <NUM> may be via a Xn-U interface.

The distributed RAN <NUM> may support fronthauling solutions across different deployment types. For example, the RAN <NUM> architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The distributed RAN <NUM> may share features and/or components with LTE. For example, AN <NUM> may support dual connectivity with NR and may share a common fronthaul for LTE and NR. The distributed RAN <NUM> may enable cooperation between and among DUs <NUM>-<NUM>, for example, via the CU-CP <NUM>. An inter-DU interface may not be used.

Logical functions may be dynamically distributed in the distributed RAN <NUM>. As will be described in more detail with reference to <FIG>, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, Physical (PHY) layers, and/or Radio Frequency (RF) layers may be adaptably placed, in the N AN and/or UE.

<FIG> illustrates a diagram showing examples for implementing a communications protocol stack <NUM> in a RAN (e.g., such as the RAN <NUM>), according to aspects of the present disclosure. The illustrated communications protocol stack <NUM> may be implemented by devices operating in a wireless communication system, such as a <NUM> NR system (e.g., the wireless communication network <NUM>). In various examples, the layers of the protocol stack <NUM> may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device or a UE. As shown in <FIG>, the system may support various services over one or more protocols. One or more protocol layers of the protocol stack <NUM> may be implemented by the AN and/or the UE.

As shown in <FIG>, the protocol stack <NUM> is split in the AN (e.g., AN <NUM> in <FIG>). The RRC layer <NUM>, PDCP layer <NUM>, RLC layer <NUM>, MAC layer <NUM>, PHY layer <NUM>, and RF layer <NUM> may be implemented by the AN. For example, the CU-CP (e.g., CU-CP <NUM> in <FIG>) and the CU-UP e.g., CU-UP <NUM> in <FIG>) each may implement the RRC layer <NUM> and the PDCP layer <NUM>. A DU (e.g., DUs <NUM>-<NUM> in <FIG>) may implement the RLC layer <NUM> and MAC layer <NUM>. The AU/RRU (e.g., AU/RRUs <NUM>-<NUM> in <FIG>) may implement the PHY layer(s) <NUM> and the RF layer(s) <NUM>. The PHY layers <NUM> may include a high PHY layer and a low PHY layer.

The UE may implement the entire protocol stack <NUM> (e.g., the RRC layer <NUM>, the PDCP layer <NUM>, the RLC layer <NUM>, the MAC layer <NUM>, the PHY layer(s) <NUM>, and the RF layer(s) <NUM>).

<FIG> illustrates example components of BS <NUM> and UE <NUM> (as depicted in <FIG>), which may be used to implement aspects of the present disclosure. As noted above, the BS may include a TRP. One or more components of the UE <NUM> may be used to practice aspects of the present disclosure. For example, antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> may be used to perform the operations described herein and illustrated with reference to <FIG>, and/or other various techniques and methods described herein.

The controllers/processors <NUM> and <NUM> may direct the operation at the BS <NUM> and the UE <NUM>, respectively. The processor <NUM> and/or other processors and modules at the UE <NUM> may perform or direct, e.g., the execution of the functional blocks illustrated in <FIG> and <FIG>-<NUM>, and/or other processes for the techniques described herein.

<FIG> illustrates an example system architecture <NUM> for interworking between 5GS (e.g., such as the distributed RAN <NUM>) and E-UTRAN-EPC, in accordance with certain aspects of the present disclosure. As shown in <FIG>, the UE <NUM> may be served by separate RANs 504A and 504B controlled by separate core networks 506A and 506B, where the RAN 504A provides E-UTRA services and RAN 504B provides <NUM> NR services. The UE may operate under only one RAN/CN or both RANs/CNs at a time.

The PSS may provide half-frame timing, and the SS may provide the CP length and frame timing.

LTE vehicle-to-everything (LTE-V2X) has been developed as a technology to address basic vehicular wireless communications to enhance road safety and the driving experience. In other systems, new radio vehicle-to-everything (NR-V2X) has been developed as an additional technology that covers more advanced communication use case to further enhance road safety and driving experience. Non-limiting embodiments for frequencies covered may be, for example, <NUM> to <NUM>. As described below, V2X system methods and apparatus may be applicable to both LTE-V2X and NR-V2X as well as other frequencies. Other frequency spectrums other than those covered by LTE-V2X and NR-V2X are also considered to be applicable to the description and as such, the disclosure should not be considered limiting.

Referring to <FIG>, a V2X system is illustrated with two vehicles. The V2X system, provided in <FIG>, provides two complementary transmission modes. A first transmission mode involves direct communications between participants in the local area. Such communications are illustrated in <FIG>. A second transmission mode involves network communications through a network as illustrated in <FIG>.

Referring to <FIG>, the first transmission mode allows for direct communication between different participants in a given geographic location. As illustrated, a vehicle can have a communication with an individual (V2P) through a PC5 interface. Communications between a vehicle and another vehicle (V2V) may also occur through a PC5 interface. In a like manner, communication may occur from a vehicle to other highway components, such as a signal (V2I) through a PC5 interface. In each embodiment illustrated, two-way communication can take place between elements, therefore each element may be a transmitter and a receiver of information. In the configuration provided, the first transmission mode is a self-managed system and no network assistance is provided. Such transmission modes provide for reduced cost and increased reliability as network service interruptions do not occur during handover operations for moving vehicles. Resource assignments do not need coordination between operators and subscription to a network is not necessary, therefore there is reduced complexity for such self-managed systems.

In one, non-limiting embodiment, the V2X system is configured to work in a <NUM> spectrum, thus any vehicle with an equipped system may access this common frequency and share information. Such harmonized/common spectrum operations allows for safe operation. V2X operations may also co-exist with <NUM>. 11p operations by being placed on different channels, thus existing <NUM>. 11p operations will not be disturbed by the introduction of V2X systems. In one non-limiting embodiment, the V2X system may be operated in a <NUM> band that describes/contains basic safety services. In other non-limiting embodiments, the V2X system may support advanced safety services in addition to basic safety services described above. In another non-limiting embodiment, the V2X system may be used in a <NUM> NR V2X configuration, which is configured to interface with a wide variety of devices. By utilizing a <NUM> NR V2X configuration, multi Gbps rates for download and upload may be provided. In a V2X system that uses a <NUM> NR V2X configuration, latency is kept low, for example <NUM>, to enhance operation of the V2X system, even in challenging environments.

Referring to <FIG>, a second of two complementary transmission modes is illustrated. In the illustrated embodiment, a vehicle may communicate with another vehicle through network communications. These network communications may occur through discrete nodes, such as eNodeB, that send and receive information between vehicles. The network communications may be used, for example, for long range communications between vehicles, such as noting the presence of an accident approximately <NUM> mile ahead. Other types of communication may be sent by the node to vehicles, such as traffic flow conditions, road hazard warnings, environmental/weather reports, service station availability and other like data. Data can be obtained from cloud-based sharing services.

For network communications, residential service units (RSUs) may be utilized as well as <NUM>/<NUM> small cell communication technologies to benefit in more highly covered areas to allow real time information to be shared among V2X users. As the number of RSUs diminishes, the V2X systems may rely more on small cell communications, as necessary.

In either of the two complementary transmission modes, higher layers may be leveraged to tune congestion control parameters. In high density vehicle deployment areas, using higher layers for such functions provides an enhanced performance on lower layers due to congestion control for PHY/MAC.

The vehicle systems that use V2X technologies have significant advantages over <NUM>. 11p technologies. Conventional <NUM>. 11p technologies have limited scaling capabilities and access control can be problematic. In V2X technologies, two vehicles apart from one another may use the same resource without incident as there are no denied access requests. V2X technologies also have advantages over <NUM>. 11p technologies as these V2X technologies are designed to meet latency requirements, even for moving vehicles, thus allowing for scheduling and access to resources in a timely manner.

In the instance of a blind curve scenario, road conditions may play an integral part in decision making opportunities for vehicles. V2X communications can provide for significant safety of operators where stopping distance estimations may be performed on a vehicle by vehicle basis. These stopping distance estimations allow for traffic to flow around courses, such as a blind curve, with greater vehicle safety, while maximizing the travel speed and efficiency.

As noted, NR-V2X systems may support the exchange of normal traffic (e.g., for sensor sharing, intention sharing, etc.), as well as high priority/importance (e.g., HRHRC) communications. The high priority communications may have to have a higher reliability and higher range compared to the normal traffic. However, since radio resources may be limited, some UEs may share the radio resources for normal and HRHRC traffic. At the same time, HRHRC traffic may be exchanged relatively infrequently (or not at all) in some areas, and may be triggered more frequently in other areas (e.g., road intersections). However, reserving resources for HRHRC traffic in all areas (e.g., or a large number of areas) at all times may be costly and inefficient.

Aspects presented herein provide a dynamic mechanism for resource sharing, e.g., for HRHRC traffic in V2X systems. More specifically, aspects presented provide techniques for partitioning resources used for HRHRC traffic and/or normal traffic based on one or more different geographical zones. The geographical zone(s) may be defined based on areas that are associated with high levels (e.g., above a threshold) of HRHRC traffic. In aspects, additional resources within the geographical zone(s) may be allocated for HRHRC traffic, and limited resources (or no resources) outside of the geographical zone(s) may be allocated for HRHRC traffic. By providing for a zone-based partitioning of resources for HRHRC traffic, techniques can allow for a more efficient use of resources in the V2X system.

<FIG> illustrates example operations <NUM> for wireless communications, in accordance with aspects of the present disclosure. Operations <NUM> may be performed, for example, by a first wireless device, such as a UE (e.g., UE <NUM> shown in <FIG>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., processor <NUM> of <FIG>). Further, the communicating (e.g., transmission and/or reception of signals) by the first wireless device in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the communicating (e.g., transmission and/or reception of signals) by the first wireless device may be implemented via a bus interface of one or more processors (e.g., processor <NUM>) obtaining and/or outputting signals.

Operations <NUM> begin, at <NUM>, where the first wireless device determines, based at least in part on a location of the first wireless device and a type of traffic associated with the first wireless device, whether to use a first set of resources or a second set of resources for communications between the first wireless device and at least one second wireless device. The first wireless device and the at least one second wireless device may be V2X devices.

At <NUM>, the first wireless device communicates with at least one second wireless device (e.g., another UE <NUM>) on the first set of resources or the second set of resources, in accordance with the determination, wherein the communications involve the type of traffic. The first set of resources may be associated with (e.g., dedicated for) a first type of V2X traffic (e.g., HRHRC V2X traffic). The second set of resources may be associated with (e.g., dedicated for) a different second type of V2X traffic (e.g., normal V2X traffic). The first type of traffic may have a higher priority than the second type of traffic. As used herein, a set of resources may refer to a set of time and/or frequency resources.

In some aspects, one or more geographical zones may be configured for V2X systems. Additional resources (e.g., HRHRC resources) may be configured for exchanging the first type of traffic in the geographical zone(s). For example, if the first wireless device determines its location is within the geographical zone(s), the first wireless device can use the first set of resources to exchange the first type of traffic. In some aspects, there may be priority access for UEs that want to exchange the first type of traffic (e.g., HRHRC V2X traffic) within the geographical zone(s).

In some aspects, there may be secondary access for UEs that want to exchange the second type of traffic (e.g., normal traffic) within the geographical zones. For example, a UE that wants to transmit normal traffic may perform a sensing mechanism in the first set of resources (e.g., HRHRC resources). If the UE does not detect that another UE (e.g., HRHRC UE) is using the first set of resources, the UE may use the first set of resources to exchange the second type of traffic (e.g., normal V2X traffic). In such cases, the UE may transmit normal V2X traffic in the first set of resources by performing an access procedure, such as a listen-before-talk (LBT) procedure. In some aspects, if another (high priority) UE that has priority access wants to exchange the first type of traffic while the (lower priority) UE is using the first set of resources to exchange the second type of traffic, the (high priority) UE may refrain from using the first set of resources while the (lower priority) UE is using the first set of resources to exchange the second type of traffic. Once the (high priority) UE determines that the (lower priority) UE is no longer using the first set of resources, the (high priority) UE can begin exchanging the first type of traffic on the first set of resources.

In some examples, if the first wireless device determines that its location is outside the geographical zone(s), the first wireless device can use the second set of resources to exchange the second type of traffic. In some aspects, the first wireless device may not use the first set of resources if it determines that its location is outside the geographical zone(s).

In some aspects, the first set of resources (e.g., HRHRC resources) within the geographical zone(s) may be further partitioned into different sets of resources for UEs that are oriented (or travelling) in different directions. For example, the first set of resources may include a (third) set of resources associated with a first direction (e.g., vertical direction) and/or a (fourth) set of resources associated with a second direction (e.g., horizontal direction). A UE may determine which of the third set of resources and the fourth set of resources to use for the first type of traffic (e.g., HRHRC V2X traffic) based on its orientation within the geographical zone(s). For example, if the UE is oriented or traveling in the first direction, the UE may use the third set of resources, and if the UE is oriented or traveling in the second direction, the UE may use the fourth set of resources.

In some aspects, information regarding the resource partitioning, e.g., including the allocated sets of resources, geographical zone(s), etc., may be signaled to the UEs from a base station. In some aspects, the resource partitioning information may be pre-configured for each UE in the network. In some aspects, the UEs may negotiate among each other to determine and agree on the resource partitioning information. For example, each UE may exchange messages with other UE(s) to determine the allocated sets of resources, geographical zone(s), etc. Once agreed, one of the UEs (or a base station) may broadcast the information within the system.

<FIG> illustrates one reference example of zone-based resource partitioning, according to certain aspects of the present disclosure. As shown, a geographical zone <NUM> may be configured, where additional HRHRC resources are configured for HRHRC V2X traffic within the geographical zone <NUM>, e.g., to provide more reliability for HRHRC V2X traffic. On the other hand, there may limited resources (or no resources) allocated for HRHRC V2X traffic outside of the geographical zone <NUM>. The geographical zone <NUM> may be defined in an area associated with frequent exchange of HRHRC V2X traffic, e.g., compared to other geographical areas. In this example, geographical zone <NUM> is defined over an intersection.

UEs (e.g., UEs 120A, 120B) within geographical zone <NUM> may use HRHRC resources to communicate (e.g., send/receive) HRHRC V2X traffic. UEs (e.g., UEs 120C, 120D) outside geographical zone <NUM> may use normal resources to communicate normal V2X traffic and may not use HRHRC resources to communicate HRHRC V2X traffic. In some aspects, HRHRC resources within geographical zone <NUM> may co-exist with normal resources within geographical zone <NUM>. UEs within geographical zone <NUM> that want to transmit HRHRC V2X traffic may have priority access to the HRHRC resources. On the other hand, UEs within geographical zone <NUM> that want to transmit normal V2X traffic may have secondary access to the HRHRC resources. For example, these UEs may first perform a sensing mechanism to determine if another UE is using the HRHRC resources, and if no UE is detected, may perform a LBT-based mechanism to access the HRHRC resources for communicating normal V2X traffic. In some aspects, (high priority) UEs that want to transmit HRHRC V2X traffic may also perform a sensing mechanism to determine if another UE is using the HRHRC resources, e.g., before transmitting HRHRC V2X traffic on the HRHRC resources. For example, if such UEs detect (e.g., based on the sensing mechanism) that the HRHRC resources are being used by a (lower priority) UE to transmit normal V2X traffic, the (high priority) UEs may refrain from communicating on the HRHRC resources until the (lower priority) UE has finished occupying (using) the HRHRC resources.

In some aspects, the HRHRC resources within geographical zone <NUM> may be partitioned into a set of HRHRC resources for a horizontal direction <NUM> and a set of HRHRC resources for a vertical direction <NUM>. If a UE (e.g., UE 120A) determines that it is oriented or traveling in the horizontal direction <NUM>, the UE may use the set of HRHRC resources for the horizontal direction <NUM>. If a UE (e.g., UE 120B) determines that it is oriented or traveling in the vertical direction <NUM>, the UE may use the set of HRHRC resources for the vertical direction <NUM>. The UE may determines its location, orientation, etc., based on sensors (e.g., GPS), communications from other UEs, measurements, etc. Note that <FIG> uses a horizontal direction and vertical direction as reference examples of different orientations that can be associated with different sets of HRHRC resources. Those of ordinary skill in the art will recognize that the HRHRC resources within the geographical zone <NUM> can be partitioned into different sets of HRHRC resources for other orientations (e.g., besides vertical and horizontal).

In some aspects, with a zone-based partitioning of resources, the near/far effect (e.g., in-band interference effect (IBE), inter-symbol interference (ISI), and/or inter-carrier interference (ICI)) can be reduced, e.g., by reducing the maximum distance/pathloss between two concurrent transmitters. In some cases, this can be achieved by allowing UEs in the same zone to transmit at the same time (e.g., partitioning the resources in time domain between different zones).

Operations <NUM> begin, at <NUM>, where the first wireless device determines a location of the first wireless device (e.g., whether the first wireless device is within a geographical zone designated for exchanging the first type of traffic, such as geographical zone <NUM>) and a type of traffic (e.g., first type of traffic, such as HRHRC V2X traffic, or a second type of traffic, such as normal V2X traffic) that the first wireless device wants to exchange (e.g., with at least another wireless device).

At <NUM>, the first wireless device determines if its location is within a geographical zone designated for exchanging at least the first type of traffic (e.g., geographical zone <NUM>). If not, the first wireless device determines to use the second set of resources (e.g., normal resources) for communications (e.g., with at least another wireless device) and exchanges traffic on the second set of resources. For example, as noted, there may limited resources (no resources) allocated for high priority communications, such as HRHRC V2X traffic, outside of the geographical zone.

If, at <NUM>, the first wireless device determines it is within the geographical zone designated for exchanging at least the first type of traffic, the first wireless device determines if the type of traffic is the first type of traffic (<NUM>). If so, the first wireless device determines if the first set of resources (e.g., HRHRC resources) are currently in use (e.g., by another wireless device) (<NUM>). For example, as noted, there may be situations in which a (lower priority) wireless device is using the first set of resources to exchange the second type of traffic (e.g., normal V2X traffic). The first wireless device can determine whether this is case by performing a sensing mechanism prior to using the first set of resources to exchange the first type of traffic. If the first wireless device determines (or detects) that the (lower priority) wireless device is using the first set of resources, the first wireless device refrains from using the first set of resources (e.g., until the (lower priority) wireless device has finished) (<NUM>). On the other hand, if the first wireless device determines that the first set of resources is not in use (<NUM>), the first wireless device uses the first set of resources (<NUM>). For example, the first wireless device can begin exchanging the first type of traffic with at least another wireless device on the first set of resources.

If, at <NUM>, the first wireless device determines that the type of traffic is the second type of traffic, the first wireless device determines if the first set of resources is in use (e.g., by another (higher priority) wireless device) (<NUM>). As noted, in some cases, a (low priority) wireless device that wants to communicate the second type of traffic may have secondary access to the first set of resources. In this case, the (low priority) wireless device may perform a sensing mechanism to determine if the first set of resources is in use by another wireless device. If the first set of resources is not in use, the first wireless device determines to use the first set of resources (<NUM>). On the other hand, if the first set of resources is in use, the first wireless device determines to use the second set of resources (<NUM>).

<FIG> illustrates example operations <NUM> for wireless communications, in accordance with aspects of the present disclosure. Operations <NUM> may be performed, for example, by a first wireless device, such as a UE (e.g., UE <NUM> shown in <FIG>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., processor <NUM> of <FIG>). Further, the communicating (e.g., transmission and/or reception of signals) by the first wireless device in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the communicating (e.g., transmission and/or reception of signals) by the first wireless device may be implemented via a bus interface of one or more processors (e.g., processor <NUM>) obtaining and/or outputting signals. The operations <NUM> may be performed as part of operations <NUM> in <FIG>.

Operations <NUM> begin at <NUM>, where the first wireless device determines an orientation of the first wireless device within the geographical zone designated for exchanging at least the first type of traffic (e.g., geographical zone <NUM>). As noted, in some cases, the first set of resources within the geographical zone may be further partitioned into different sets of resources allocated for different orientations (or directions). Here, if the first wireless device determines that its orientation is in the first direction (e.g., vertical direction, such as vertical direction <NUM>) (<NUM>), the first wireless device uses the resources associated with the first direction (e.g., the third set of HRHRC resources) (<NUM>). On the other hand, if the first wireless determines that its orientation is in the second direction (e.g., horizontal direction, such as horizontal direction <NUM>), the first wireless device uses the resources associated with the second direction (e.g., the fourth set of HRHRC resources) (<NUM>).

<FIG> illustrates a communications device <NUM> that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in <FIG> and <FIG>-<NUM>. The transceiver <NUM> is configured to transmit and receive signals for the communications device <NUM> via an antenna <NUM>, such as the various signals described herein.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions that when executed by processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG> and <FIG>-<NUM>, or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system <NUM> further includes a communicating component <NUM> for performing the operations illustrated at <NUM> in <FIG>, operations illustrated at <NUM>, <NUM>, and <NUM> in <FIG>, and operations illustrated at <NUM> and <NUM> in <FIG>. Additionally, the processing system <NUM> includes a resource component <NUM> for performing the operations illustrated at <NUM> in <FIG>, operations <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> illustrated in <FIG>, and operations <NUM>, <NUM>, <NUM>, and <NUM> illustrated in <FIG>. The communicating component <NUM> and resource component <NUM> may be coupled to the processor <NUM> via bus <NUM>. In certain aspects, the communicating component <NUM> and resource component <NUM> may be hardware circuits. In certain aspects, the communicating component <NUM> and resource component <NUM> may be software components that are executed and run on processor <NUM>.

In some cases, rather than actually communicating a frame, a device may have an interface to communicate a frame for transmission or reception. For example, a processor may output a frame, via a bus interface, to an RF front end for transmission. Similarly, rather than actually receiving a frame, a device may have an interface to obtain a frame received from another device. For example, a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for transmission.

As used herein, a phrase referring to "at least one of' a list of items refers to any combination of those items, including single members.

For example, means for transmitting, means for sending, means for signaling, means for indicating, means for assigning, means for providing, means for retrieving, means for interacting, means for negotiating, means for exchanging, means for communicating, and/or means for receiving may comprise one or more of a transmit processor <NUM>, a TX MIMO processor <NUM>, a receive processor <NUM>, or antenna(s) <NUM> of the base station <NUM> and/or the transmit processor <NUM>, a TX MIMO processor <NUM>, a receive processor <NUM>, or antenna(s) <NUM> of the user equipment <NUM>. Additionally, means for identifying, means for determining, means for negotiating, means for agreeing, means for signaling, means for storing, means for interacting, means for configuring, means for generating, means for assigning, means for providing, means for updating, means for modifying, means for changing, means for selecting, means for performing, means for using, and/or means for applying may comprise one or more processors, such as the controller/processor <NUM> of the base station <NUM> and/or the controller/processor <NUM> of the user equipment <NUM>.

Claim 1:
A method for wireless communication by a first wireless device, the method comprising:
determining (<NUM>), whether to use a first set of resources associated with a first type of vehicle-to-everything, V2X, traffic within a geographical zone dedicated for exchanging at least the first type of V2X traffic, or a second set of resources associated with a different second type of V2X traffic having a lower priority than the first type of V2X traffic for communications between the first wireless device and at least one second wireless device, based at least in part on a location of the first wireless device being within the geographical zone, a type of traffic associated with the first wireless device, and whether a third wireless device is using the first set of resources; and
communicating (<NUM>) with the at least one second wireless device on the first set of resources or the second set of resources, in accordance with the determination,
wherein the location of the wireless device is within the geographical zone, and
wherein the communications involve the first or second type of traffic; wherein:
when the type of traffic is the first type of traffic, the determination is to use the first set of resources;
when the type of traffic is the second type of traffic, and the first wireless device does not detect that the third wireless device is using the first set of resources, the determination is to use the first set of resources; and
when the type of traffic is the second type of traffic, and the first wireless device detects that the third wireless device is using the first set of resources, the determination is to use the second set of resources.