阅读说明：本技术 基于区划的中继控制 (Zone-based relay control ) 是由 H·程 K·古拉蒂 吴志斌 J·李 于 2019-08-12 设计创作，主要内容包括：传送方设备可以确定该传送方设备的区划标识符(ID),以及直接向至少一个接收方设备传送包括该区划ID的消息。在某些方面,中继设备可被配置成：接收包括传送方设备的第一区划ID的消息,至少基于第一区划ID来确定是否中继该消息,以及如果该中继设备确定要中继该消息,则传送包括反映第一区划ID的信息的经中继消息。在某些方面,接收方设备可被配置成：标识包括指示传送方设备的第一区划ID的信息的消息,至少基于传送方设备的第一区划ID来确定是否解码该消息的数据,以及基于该确定来解码或抑制解码该消息的数据。(A transmitting device may determine a zone Identifier (ID) of the transmitting device and transmit a message including the zone ID directly to at least one receiving device. In certain aspects, a relay device may be configured to: the method includes receiving a message including a first zone ID of a transmitting device, determining whether to relay the message based at least on the first zone ID, and transmitting a relayed message including information reflecting the first zone ID if the relay device determines to relay the message. In certain aspects, a recipient device may be configured to: the method includes identifying a message including information indicating a first zone ID of a transmitting device, determining whether to decode data of the message based at least on the first zone ID of the transmitting device, and decoding or refraining from decoding data of the message based on the determination.)

1. A method of wireless communication at a transmitting device, comprising:

determining a zone Identifier (ID) of the transmitting device;

generating a message including the zone ID; and

the message is transmitted directly to at least one recipient device.

2. The method of claim 1, wherein the zone ID is included in at least one of a Media Access Control (MAC) header of the message or a Service Data Adaptation Protocol (SDAP) header of the message.

3. The method of claim 1, wherein determining the zone ID of the transmitting device comprises:

determining a geographic location of the transmitting device; and

converting the geographic location to the zone ID.

4. The method of claim 3, wherein the geographic location is converted to the zone ID based on at least one of a preconfigured relationship or information received from a base station or relay device.

5. The method of claim 1, wherein the message further includes a layer 2ID based on at least one of a source ID and a destination ID in addition to the zone ID.

6. The method of claim 5, wherein the source ID comprises a layer 2ID of the transmitting device and the destination ID comprises a broadcast group ID.

7. The method of claim 1, wherein the message further comprises an indicator indicating whether the message should be relayed.

8. The method of claim 1, wherein the message further comprises a designation of a relay device that is expected to forward the message.

9. The method of claim 1, wherein the zone ID is included in control information of the message.

10. The method of claim 1, wherein the message is transmitted based on vehicle-to-vehicle (V2V) communication, internet of vehicles (V2X) communication, or device-to-device communication.

11. A method of wireless communication at a relay device, comprising:

receiving a message including a first zone Identifier (ID) of a transmitting device;

determining whether to relay the message based on at least the first zone ID; and

generating a relayed message including first information indicating the first zone ID if the relay device determines to relay the message.

12. The method of claim 11, wherein the relay device determines to relay the message when the relay device is in a different zone than a zone corresponding to a first zone ID in the message.

13. The method of claim 11, wherein generating the relayed message further comprises:

include second information indicating a second zone ID of the relay device in the relayed message.

14. The method of claim 11, wherein generating the relayed message further comprises:

including additional information indicative of a relay device ID in the relayed message.

15. The method of claim 11, wherein the first information indicating the first zone ID is included in at least one of control information for the relayed message, a scheduling assignment for the relayed message, or a MAC header of the relayed message.

16. The method of claim 11, further comprising:

selecting a radio resource group for sending the relayed message based on a first zone ID included in the message.

17. The method of claim 11, wherein generating the relayed message further comprises:

including a destination ID in the relayed message, wherein the destination ID is based on the first zone ID, a second zone ID of the relay device, and a relay device ID.

18. The method of claim 11, further comprising:

transmitting the relayed message in response to determining to relay the message, wherein the first information indicating the first zone ID is included in control information for the relayed message, wherein transmitting the relayed message comprises:

transmitting the control information in a physical side link control channel (PSCCH); and

transmitting data of the relayed message in a Physical Sidelink Shared Channel (PSSCH).

19. A method of wireless communication at a recipient device, comprising:

identifying a message including information indicating a first zone Identifier (ID) of a transmitting device;

determining whether the message comprises a relayed message;

determining whether to decode data of the message based on at least a first zone ID of the transmitting device when the message comprises the relayed message; and

decoding or refraining from decoding data of the message according to the determination based on the first zone ID.

20. The method of claim 19, further comprising:

determining a second zone ID of the recipient device, wherein determining whether to decode data of the message comprises:

refraining from decoding data of the message when the message includes the relayed message and the first zone ID is the same as the second zone ID.

21. The method of claim 19, wherein identifying the message including the information indicating the first zone ID comprises:

receiving control information for the message, the control information including information indicating the first zone ID.

22. The method of claim 19, further comprising:

determining a set of zone IDs that the receiving device is capable of receiving a message directly from the transmitting device, wherein determining whether to decode data of the message comprises:

refraining from decoding data of the message when the message includes the set of zone IDs includes the first zone ID.

23. The method of claim 19, wherein the recipient device further determines whether to decode data of the message based on a radio resource group receiving the message.

24. The method of claim 19, wherein the information indicating the first zone ID is included in at least one of a MAC header of the message or a SDAP header of the message or control information received in a Physical Sidelink Control Channel (PSCCH).

25. The method of claim 19, wherein the message comprises the relayed message, and the information indicating the first zone ID is indicated in a scheduling assignment for the relayed message.

26. The method of claim 19, wherein the message is received based on vehicle-to-vehicle (V2V) communication, internet of vehicles (V2X) communication, or device-to-device communication.

27. The method of claim 19, wherein the recipient device further determines whether to decode data of the message based on a second zone ID of a relay device.

28. The method of claim 27, wherein the receiver device further determines whether to decode data of the message based on whether the second zone ID is the same as the first zone ID.

29. The method of claim 19, wherein the recipient device further determines whether to decode data of the message based on a relay device ID of a relay device.

30. An apparatus for wireless communication at a recipient device, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

identifying a message including information indicating a first zone Identifier (ID) of a transmitting device;

determining whether to decode data of the message based at least on the first zone ID of the transmitting device; and

decoding or refraining from decoding data of the message according to the determination based on the first zone ID.

Technical Field

The present disclosure relates generally to communication systems, and more particularly to methods and apparatus related to relay control for internet of vehicles (V2X) communication, vehicle-to-vehicle (V2V) communication, enhanced V2X (eV2X) communication, or device-to-device (D2D) communication.

Introduction to the design reside in

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate on a city, country, region, and even global level. Example telecommunication standards are the 5G New Radio (NR) and 4G Long Term Evolution (LTE) standards. The 5G NR is part of a continuous mobile broadband evolution promulgated by the third generation partnership project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)), and other requirements. The 5G NR includes services associated with enhanced mobile broadband (eMBB), large-scale machine type communication (mtc), and ultra-reliable low latency communication (URLLC). Some aspects of the 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Aspects of wireless communication may include direct communication between devices, such as in V2X, V2V, and/or D2D communication. Aspects presented herein provide improvements to V2X, V2V, and/or D2D technologies. These improvements are also applicable to other multiple access techniques and telecommunications standards employing these techniques.

Background

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, computer-readable medium, and apparatus for wireless communication at a transmitting device are provided. The apparatus determines a zone Identifier (ID) of a transmitting device. The apparatus generates a message including a zone ID and transmits the message directly to at least one recipient device.

In another aspect of the disclosure, a method, computer-readable medium, and apparatus for wireless communication at a relay device are provided. The apparatus receives a message including a first zone Identifier (ID) of a transmitting device and determines whether to relay the message based at least on the first zone ID. The apparatus generates a relayed message including first information indicating the first zone ID if the relay device determines to relay the message.

In another aspect of the disclosure, a method, computer-readable medium, and apparatus for wireless communication at a recipient device are provided. The apparatus identifies a message including information indicating a first zone ID of a transmitting device. The apparatus determines whether the message comprises a relayed message and, when the message comprises a relayed message, determines whether to decode data of the message based at least on a first zone ID of the transmitting device. The apparatus then decodes or refrains from decoding data of the message according to the determination based on the first zone ID.

Various additional aspects and features are described in the detailed description that follows.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present description is intended to include all such aspects and their equivalents.

Brief Description of Drawings

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network.

Fig. 2 illustrates an example aspect of a sidelink slot structure.

Fig. 3 is a diagram illustrating an example of a base station and a UE in an access network.

Fig. 4 is a diagram illustrating relay control management in a wireless communication system.

Fig. 5 is a diagram illustrating message relaying in a wireless communication system.

Fig. 6 is a flow chart of a method of wireless communication.

Fig. 7 is a conceptual data flow diagram illustrating the data flow between different devices/components in an example apparatus.

Fig. 8 is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system.

Fig. 9 is a flow chart of a method of wireless communication.

Fig. 10 is a conceptual data flow diagram illustrating the data flow between different devices/components in an example apparatus.

Fig. 11 is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system.

Fig. 12 is a flow chart of a method of wireless communication.

Fig. 13 is a conceptual data flow diagram illustrating the data flow between different devices/components in an example apparatus.

Fig. 14 is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of a telecommunications system will now be presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

As an example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include: a microprocessor, a microcontroller, a Graphics Processing Unit (GPU), a Central Processing Unit (CPU), an application processor, a Digital Signal Processor (DSP), a Reduced Instruction Set Computing (RISC) processor, a system-on-chip (SoC), a baseband processor, a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subprograms, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to in software, firmware, middleware, microcode, hardware description language, or other terminology.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise Random Access Memory (RAM), Read Only Memory (ROM), electrically erasable programmable ROM (eeprom), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the above types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network 100. A wireless communication system, also referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE104, an Evolved Packet Core (EPC)160, and a core network (e.g., 5GC) 190. Base station 102 may include macro cells (high power cellular base stations) and/or small cells (low power cellular base stations). The macro cell includes a base station. Small cells include femtocells, picocells, and microcells.

A base station 102 configured for 4G LTE, collectively referred to as an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with the EPC 160 through a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for NR, collectively referred to as next generation RAN (NG-RAN), may interface with core network 190 over backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: communication of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) over a backhaul link 134 (e.g., an X2 interface). The backhaul link 134 may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102 'may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved node B (eNB) (HeNB), which may provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE104 may include Uplink (UL) (also known as reverse link) transmissions from UE104 to base station 102 and/or Downlink (DL) (also known as forward link) transmissions from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. These communication links may be over one or more carriers. For each carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction, the base station 102/UE104 may use a spectrum of up to a Y MHz (e.g., 5, 10, 15, 20, 100, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL/UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels such as a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Shared Channel (PSSCH), and a Physical Sidelink Control Channel (PSCCH). The D2D communication may be over a variety of wireless D2D communication systems such as, for example, FlashLinQ, WiMedia, bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

The wireless communication system may further include a Wi-Fi Access Point (AP)150 in communication with a Wi-Fi Station (STA)152 via a communication link 154 in a 5GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152/AP 150 may perform a Clear Channel Assessment (CCA) prior to the communication in order to determine whether the channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same 5GHz unlicensed spectrum as used by the Wi-Fi AP 150. A small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and/or increase the capacity of the access network.

Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, g B node (gNB), or other type of base station. Some base stations, such as the gNB 180, may operate in the legacy sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and/or near mmW frequencies to communicate with the UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely High Frequencies (EHF) are part of the RF in the electromagnetic spectrum. The EHF has a range of 30GHz to 300GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this frequency band may be referred to as millimeter waves. Near mmW can be extended down to 3GHz frequencies with 100 mm wavelength. The ultra-high frequency (SHF) band extends between 3GHz to 30GHz, which is also known as a centimeter wave. Communications using the mmW/near mmW radio frequency band have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE104 to compensate for the very high path loss and short range.

Devices may transmit and receive communications using beamforming. For example, fig. 1 illustrates that the base station 180 may transmit a beamformed signal to the UE104 in one or more transmit directions 182'. The UE104 may receive beamformed signals from the base station 180 in one or more receive directions 182 ". The UE104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UEs 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180/UE 104. The transmit direction and the receive direction of the base station 180 may be the same or may be different. The transmit direction and the receive direction of the UE104 may be the same or may be different. Although beamformed signals are illustrated between the UE104 and the base station 102/180, aspects of beamforming may be similarly applied by the UE104 or RSU 107 to communicate with another UE104 or RSU 107, such as based on V2X, V2V, or D2D communications.

The EPC 160 may include a Mobility Management Entity (MME)162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC)170, and a Packet Data Network (PDN) gateway 172. MME 162 may be in communication with Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE104 and EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets pass through the serving gateway 166, which serving gateway 166 itself connects to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to an IP service 176. IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may be used as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting eMBMS-related charging information.

The core network 190 may include an access and mobility management function (AMF)192, other AMFs 193, a Session Management Function (SMF)194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets pass through the UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to the IP service 197. The IP services 197 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services.

A base station may also be called a gbb, a node B, an evolved node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a Transmission Reception Point (TRP), or some other suitable terminology. Base station 102 provides an access point for UE104 to EPC 160 or core network 190. Examples of UEs 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, Personal Digital Assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors/actuators, displays, or any other similar functioning device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, oil pumps, ovens, vehicles, heart monitors, etc.). UE104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Some wireless communication networks may include vehicle-based communication devices that may communicate and/or communicate with other devices from a vehicle-to-vehicle (V2V), a vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node, such as a Road Side Unit (RSU)), a vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes, such as base stations), and/or combinations thereof, which may be collectively referred to as vehicle networking (V2X) communications. The V2X communications may include, for example, eV2X communications, cellular V2X (cV2X) communications, and the like. Referring again to fig. 1, in certain aspects, a UE104 (e.g., a transmitting Vehicle User Equipment (VUE) or other UE) may be configured to transmit a message directly to another UE 104. The communication may be based on V2V/V2X/V2I or other D2D communications, such as proximity services (ProSe), and the like. Communications based on V2V, V2X, V2I, and/or D2D may also be transmitted and received by other transmitting and receiving devices, such as Road Side Units (RSUs) 107, etc. Aspects of the communication may be based on PC5 or sidelink communication, for example, as described in connection with the example in fig. 2. Although the following description may provide examples in conjunction with V2X/V2V/D2D communications, the concepts described herein may be applicable to other similar areas, such as 5G NR, LTE-A, CDMA, GSM, and other wireless technologies.

Referring again to fig. 1, in certain aspects, the transmitting device may include a zone ID component 198 configured to determine a zone ID of the transmitting device or message, and transmit the message including the zone ID for receipt by at least one receiving device (e.g., UE 104'). A transmitting device (e.g., UE 104) may include a vehicle, a device associated with a vehicle, an RSU, a UE, or other device that communicates based on V2X (e.g., eV2X), V2V, D2D, etc. communications. In certain aspects, the relay device (e.g., UE104 ") may include a zone ID relay component 191 configured to determine whether to relay the message based at least on the first zone ID. If the relay device determines to relay the message, the relay device may transmit a relayed message including information reflecting the first zone ID. Relay devices may include vehicles, devices associated with vehicles, RSUs, UEs, or other devices that communicate based on V2X (e.g., eV2X), V2V, D2D, etc. communications. Although fig. 1 illustrates the relay (e.g., UE104 ") as a vehicle, in other examples, the relay may include a stationary device, such as an RSU or a base station. In certain aspects, the recipient device may include a zone ID receiving component 199 configured to identify a first zone ID of the transmitting device for a received message, and determine whether to decode data of the message based at least on the first zone ID of the transmitting device. The recipient device may decode or refrain from decoding data of the message from the determination based on the first zone ID. The recipient device (e.g., UE 104') may include a vehicle, a device included in a vehicle, and/or the like. The recipient devices may include vehicles, devices associated with vehicles, RSUs, UEs, or other devices that communicate based on V2X (e.g., eV2X), V2V, D2D, etc. communications.

Fig. 2 illustrates example diagrams 200 and 210 illustrating example slot structures that may be used for wireless communication (e.g., for side-link communication) between devices, such as UEs 104, 104'. The slot structure may be within a 5G/NR frame structure. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-a, CDMA, GSM, and other wireless technologies. This is merely an example, and other wireless communication technologies may have different frame structures and/or different channels. One frame (10ms) can be divided into 10 equally sized sub-frames (1 ms). Each subframe may include one or more slots. A subframe may also include a mini-slot, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. Diagram 200 illustrates a single-slot transmission, which may correspond to a 0.5ms Transmission Time Interval (TTI), for example. Diagram 210 illustrates example 2 slot aggregation, e.g., aggregation of two 0.5ms TTIs. Diagram 200 illustrates a single RB, while diagram 210 illustrates N RBs. In diagram 210, the use of 10 RBs for control is merely an example. The number of RBs may be different.

A resource grid may be used to represent the frame structure. Each slot may include Resource Blocks (RBs) (also referred to as physical RBs (prbs)) that extend 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme. As illustrated in fig. 2, some REs may include control information, e.g., along with demodulation rs (dmrs). Fig. 2 also illustrates that the symbol(s) may include CSI-RS. The symbols indicated for the DMRS or CSI-RS in fig. 2 indicate that the symbols include DMRS or CSI-RS REs. Such symbols may also include REs that contain data. For example, if the number of ports for DMRS or CSI-RS is 1 and a comb-2 (comb-2) pattern is used for DMRS/CSI-RS, half of the REs may include RSs and the other half of the REs may include data. The CSI-RS resource may start at any symbol of the slot and may occupy 1, 2, or 4 symbols, depending on the number of ports configured. The CSI-RS may be periodic, semi-persistent, or aperiodic (e.g., based on DCI triggers). For time/frequency tracking, the CSI-RS may be periodic or aperiodic. The CSI-RS may be transmitted in bursts of two or four symbols spread across one or two slots. The control information may include Sidelink Control Information (SCI). As described herein, at least one symbol may be used for feedback. Symbols before and/or after feedback may be used to turnaround between data reception and feedback transmission. Although symbol 12 is illustrated for data, it may alternatively be a gap symbol to enable turnaround for feedback in symbol 13. Another symbol (e.g., at the end of the slot) may be used as a gap. The gap enables the device to switch from operating as a transmitting device to preparing (e.g., in a subsequent time slot) to operate as a receiving device. As illustrated, data may be transmitted in the remaining REs. The data may include data messages as described herein. The location of any of the SCI, feedback, and LBT symbols may be different from the example illustrated in fig. 2. Multiple time slots may be grouped together. Fig. 2 also illustrates an example aggregation of two slots. The number of aggregated slots may also be greater than two. When the slots are aggregated, the symbols and/or gap symbols for feedback may be different from the symbols and/or gap symbols for feedback for a single slot. Although feedback is not illustrated for this aggregation example, symbol(s) in a multi-slot aggregation may also be allocated for feedback, as illustrated in one slot example.

Fig. 3 is a block diagram 300 of a first wireless communication device 310 in communication with a second wireless communication device 350, e.g., via V2V/V2X/D2D communication. The device 310 may include a transmitting device that communicates with a receiving device (e.g., device 350) via V2V/V2X/D2D communication. The communication may be based on, for example, a sidelink. The transmitting device 310 may include a UE, RSU, etc. The recipient device may include a UE, RSU, etc. The packets may be provided to a controller/processor 375 that implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer.

The Transmit (TX) processor 316 and the Receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the Physical (PHY) layer, may include error detection on the transport channel, Forward Error Correction (FEC) encoding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to produce a plurality of spatial streams. The channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimate may be derived from a reference signal transmitted by the device 350 and/or channel condition feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

At the device 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to a Receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for device 350. If multiple spatial streams are destined for device 350, they may be combined into a single OFDM symbol stream by RX processor 356. RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the device 310. These soft decisions may be based on channel estimates computed by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the device 310 on the physical channel. These data and control signals are then provided to a controller/processor 359 that implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. A controller/processor 359 may provide demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing. The controller/processor 359 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

Similar to the functionality described in connection with the transmission by device 310, controller/processor 359 may provide RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.

Channel estimates, derived by channel estimator 358 from reference signals or feedback transmitted by device 310, may be used by TX processor 368 to select appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354 TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

The transmission is processed at the device 310 in a manner similar to that described in connection with the receiver function at the device 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. Controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing. The controller/processor 375 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

The TX processor 368, the RX processor 356, or the controller/processor 359 of the device 350, or at least one of the TX 316, the RX processor 370, or the controller/processor 375 may be configured to perform aspects described in connection with 191, 198, and/or 199 of fig. 1.

Various features and aspects presented herein relate to relay communication between devices, e.g., UE-to-UE relay communication. The relay communication may be based on V2X (e.g., including eV2X, cV2X, etc.), V2V, or D2D communication. In proximity-based services (ProSe), the relay of UE-to-UE messages may occur at the application layer. Thus, data packets of a message may be processed by the application layer of the relay device in order for the relay device to determine whether to forward the message. Once the relay device determines that the message is to be forwarded, the data packet of the message may be re-encapsulated, e.g., with a header for the forwarded message. The processing time required for a relay device to process a message in this manner may be too slow for some applications. As one example, the process may be too slow for eV2X, V2V, V2X, or other D2D communications where the end-to-end delay of the data packet may be expected to be short, e.g., a few ms, such as 20ms or less. For example, the message may include data (e.g., data packets) that require high reliability and/or low latency. The message may include mission critical driving data. For example, the message may include data (e.g., data packets) regarding sensor data, road conditions, traffic conditions, driving commands, fleet communications, and the like. The messages may include, for example, V2X messages that require extended range based on associated QoS parameters. By way of example, the messages may include basic security messages or other messages from higher level V2X applications. The format of the message may depend on the application and/or the area in which the device is used. For example, the format of the message may be a WAVE Short Message Protocol (WSMP) defined by IEEE1609.3, a GeoNetworking message format defined by the european telecommunications standards institute-intelligent transport system (ETSI-ITS), or the like.

Aspects presented herein provide a way to relay messages at a lower layer relay mechanism. For the V2X example, the relayed message may be processed by the V2X layer to determine whether to relay the message. By relaying messages at a layer lower than the application layer, processing time may be reduced. Thus, messages can be relayed to other recipient vehicles in a much faster manner. However, relaying messages at lower layers adds challenges. Message relay at lower layers may result in a receiver device having multiple message floods based on a single message from the transmitting vehicle. Such flooding wastes radio resources and will burden the processing power of the receiving device. A processing burden may arise because some information about the message may not be available at lower layers. Thus, the recipient device may receive an unnecessary number of messages and may attempt to process each of these messages.

Fig. 4 illustrates an example 400 of message relaying between devices (e.g., transmitting devices 402, 420, receiving device 404, and relay devices 406, 408). Messages may be communicated using, for example, eV2X, V2X, V2V, and/or D2D communications. The transmitting device 402 may be a transmitting UE, the receiving device 404 may be a receiving UE, and the relay devices 406 and 408 may be stationary devices or mobile devices, such as base stations, relay UEs, vehicles, road side units, and so forth. The relay device may comprise a mobile station or a stationary station. In one example, the relay device may include a road side unit. According to aspects herein, any UE or station, whether mobile, stationary, may serve as a transmitting device, a receiving device, or a relay device. Any vehicle or station may act as a transmitter, receiver, and/or relay of messages. The transmitting device 402 may transmit a message 410, which may be referred to as Msg 0. As illustrated in fig. 4, the recipient device 404 may receive the Msg 0410 directly from the sender device 402. Fig. 4 illustrates an example of a receiver device 404 associated with a vehicle and another example receiver device 404 that is a UE not associated with a vehicle. Aspects may be applied to any recipient device that receives communications based on D2D communications, V2X communications, and so on. Msg 0410 may also be received by relay devices 406, 408, and relay devices 406, 408 may determine to relay Msg 0. Relay device 406 transmits a relayed message Msg 1412 that is based on Msg 0410. Relay device 408 transmits a relayed message Msg 2412 based on Msg 0410. The recipient device 404 may receive all three messages, e.g., Msg 0, Msg 1, and Msg 2.

If the data packet of the message (e.g., Msg 0410) is processed by lower layers (e.g., below the application layer) of the relay device (e.g., 406, 408), the recipient device may process an undesirable number of duplicate messages, such as multiple relayed messages 412, 414, for example, and the original message 410. Not only does the duplication of the original message waste radio resources, but the recipient device 404 may also attempt to process each message. The increased processing places a burden on the processing power of the receiving device and uses additional battery power. As an example, processing multiple copies (e.g., Msg 0, Msg 1, and Msg 2) may use the processing power of the recipient device to some extent, causing the recipient device to drop other messages. For example, the recipient device may not be able to receive a new message 425 from a different sender device 420 because the recipient device unnecessarily processes all three messages corresponding to Msg 0. Therefore, the repeated messages may result in lower reliability and less coverage for the receiving UE. Aspects presented herein facilitate reducing unnecessary message handling at a recipient UE.

Aspects presented herein provide mechanisms for controlling message relay in a manner that helps avoid excessive duplication of messages. As one example, the transmitting device may indicate whether the message 410 should be relayed. For example, the relay device (e.g., 406, 408) may decide to relay the message 410 in accordance with a 5G quality of service (QoS) indicator (5QI)/QoS Class Identifier (QCI), or some flag in a physical layer/medium access control (PHY/MAC) message header, that indicates, e.g., is placed in the message header, e.g., in a Service Data Adaptation Protocol (SDAP) header. The transmitting device transmits a QoS indicator or some other flag for message relaying that indicates to the relay whether the message should be relayed. The QoS or indicia may be based on the expected range of the message. As another example, the relay devices 406, 408 may use the number of hops in the message header to determine whether to relay the message. For example, the original transmitter may have set the hop number to 1 in the message header of Msg 0. The relay device decrements the hop number by 1 (to 0) when relaying the message (e.g., as Msg 1 and Msg 2). If Msg 1 and Msg 2 are received by another relay device, these messages will not be relayed further since the number of hops is 0.

As another example, the geographical partition information of the transmitting device may be mapped to an identifier that may be used in lower layer processing messages. For example, the geographical zone information may be mapped to a layer 2 identifier (L2 ID) of the transmitting UE in order to allow control of message relaying and reception of messages. For example, the partition information may be used as the first 8 bits or the last 8 bits of the L2 ID. The relay device may use the geographical zone information to decide whether to relay the message. The recipient device may use the zone information or other location information regarding its own location (recipient device location) and the location of the transmitting device to determine whether to receive/process the message. The use of geo-partition information may advantageously improve reliability and reduce message processing for V2X, V2V, or eV2X communications.

Fig. 5 is a diagram illustrating additional aspects that facilitate reducing resource waste and/or processing burden of relayed messages using lower layer processing. The transmitting device 502 may be a transmitting UE, the receiving device 504 may be a receiving UE, and the device 506 may be a relay UE. Each of the devices 502, 504, 506 may be capable of transmitting and receiving eV2X, V2V, V2V, and/or D2D communications. Thus, at another time, device 504 may be a transmitting device and device 502 may be a receiving device.

By including the geographical location information or geographical zone information of the transmitting device 502 in the message, message handling at the relay device or the receiving device may be reduced. The relay device may use the zone information to decide whether to relay the message and/or whether to process the message. The determination may be based on, for example, the distance of the receiver/relay device from the transmitter location. At 503, a transmitting device 502 (e.g., transmitting device 502, such as a transmitting UE) may be configured to determine a first zone ID of the transmitting device. The transmitting device may first determine its geographic location, for example, using a Global Positioning System (GPS) or the like. After determining the geographic location, the transmitting device may determine a corresponding zone ID for the message. Alternatively, the satellite location, network location, or other location may be converted to a zone ID. Fig. 4 illustrates an example of a compartment having compartment boundaries. The zone ID may be mapped to the L2 ID of the transmitting device 502 and may be signaled by the transmitting device in connection with the data message. The zone IDs may also be explicitly signaled in a data message (e.g., as part of a message header). For example, each transmitting device 502 may determine a geographic region when it is preparing to transmit the first message 510. The zones for such communications may be predetermined or may vary. The zone separation and/or size may be preconfigured on the transmitting device 502. The zone size may be different for different areas and may also be dynamically provisioned or signaled to the UE. Thus, the zone size and/or location for communication can be broadcast to the transmitting device 502, e.g., by a base station (e.g., eNB/gNB) or other nearby device. The relay 506 may also use the geo-zoning information to decide on the relay action. The L2 ID of the partition may be used by the recipient device 504 to filter out some of the relayed messages.

In some aspects, transmitting device 502 may determine the first zone ID by determining a geographic location of transmitting device 502 and converting the geographic location to the first zone ID. For example, the geographic location may be converted to a first zone ID based on a preconfigured relationship. For example, all geographic locations within a particular area (e.g., within the area defined by the zone boundaries illustrated in fig. 4) may be mapped to the same zone ID. As another example, the geographic location may be converted to a zone ID based on information received from a base station (not shown). As yet another example, the geographic location may be converted to a zone ID based on information received from the relay 506. As such, the first zone ID may indicate the location of the transmitting device 502.

At 505, the transmitting device 502 may generate a first message and a first zone ID. The first message may include a data payload for transmission. The first zone ID may be transmitted along with the first message, whether in a single message or in a separate message. For example, in a first message, which may be referred to as an "original message," the transmitting device 502 may include an indication of the first zone ID. The first source L2 ID may be the L2 ID of the transmitting UE, and the first destination L2 ID may be, for example, the L2 ID of the broadcast group. The L2 ID may be further based on a zone ID corresponding to the geographical location of the transmitting device. For example, the first zone ID may be embedded in the MAC header of the first message or as part of the SDAP header above the PDCP header of the first message.

Thus, in some aspects, the first zone ID may be included in a MAC header of the first message. The transmitting device 502 may include the first zone ID in a MAC header of the first message. In some other aspects, the first zone ID may be included in an SDAP header of the first message. The transmitting device 502 may include the first zone ID in an SDAP header of the first message. In some aspects, the first message further includes an L2 ID further based on at least one of the source ID and the destination ID in addition to the first zone ID. In some aspects, the first message may further include an indicator indicating whether the first message should be relayed. The first message may further include a designation of a relay that is expected to forward the first message. For example, a unicast message may have a corresponding indication of at least one relay that should relay the message to the recipient device. Such an indication enables the transmitting device to avoid excessive duplication of messages by unintended relays. The transmitting device 502 (e.g., 402) may include an indicator in the first message indicating whether the first message should be relayed or may transmit the indication in a separate message.

At 510, the transmitting device 502 may transmit a first message with a corresponding indication of a first zone ID. The relay 506 may receive a first message from the transmitting device 502 that includes an indication of a first zone ID. Relay 506 may use lower layers (e.g., lower than the application layer) to receive and decode or otherwise process the first message. The relay device may receive some control information corresponding to the first message. The control information may indicate that the first message is an original transmission (as opposed to a relayed message).

At 513, the relay 506 may determine whether to relay the first message based at least on the first zone ID. The determination may be performed at a lower layer that receives and processes the message. Using the first zone ID information in the MAC or SDAP header of the first message, relay 506 may decide an action, such as whether to process the message and/or whether to relay the message. If the relay 506 decides to relay the message, the relay may map the first zone ID to a new destination ID. When the relayed message is sent, a new destination ID may be put into the control information for the relayed message. The control information for the relayed message may indicate that the message is a relayed message of the first message. For example, the relay 506 may use zone information reflecting the first zone ID to decide whether to relay the first message. In some aspects, the relay 506 may determine to relay the first message when the relay 506 is in a region different from the region corresponding to the first region ID in the first message. In some aspects, the relay 506 may determine not to relay the first message when the relay 506 is in the same zone as the zone corresponding to the first zone ID in the first message. In some aspects, the relay may determine to relay the first message based on proximity of a zone of the relay and a zone corresponding to the zone ID. The relay may also determine not to relay messages received from nearby regions. Thus, the relay may determine a set of zone IDs that the relay will not relay messages. When a message is received with a corresponding zone ID outside of the set of zone IDs, the relay device may determine to relay the message. The relaying may further base the determination on an indication of whether the message should be relayed and/or an indication of a particular relay that is expected to relay the message.

At 515, if the relay 506 determines to relay the first message, the relay 506 may generate a relayed message, wherein the relayed message includes information reflecting the first zone ID. For example, the information may reflect or otherwise indicate the first zone ID by including the first zone ID, by using resources corresponding to the first zone ID, by scrambling the information using the first zone ID, by generating a different identifier based on the first zone ID, by generating a different identifier as a function of the first zone ID, and/or the like, such that another device may determine the first zone ID based on the information. In some aspects, generating the relayed message may further involve including information reflecting the second zone ID of the relay 506 in the relayed message. For example, the information may reflect the second zone ID by including the second zone ID, by using resources corresponding to the second zone ID, by scrambling the information using the second zone ID, by generating a different identifier based on the second zone ID, by generating a different identifier as a function of the second zone ID, and so on, such that another device may determine the second zone ID based on the information. In some aspects, generating the relayed message further comprises including information reflecting the relay ID in the relayed message. For example, the information may reflect the relay ID by including the relay ID, by using resources corresponding to the relay ID, by scrambling the information using the relay ID, by generating a different identifier based on the relay ID, by generating a different identifier as a function of the relay ID, and so on, such that another device may determine the relay ID based on the information. The relay 506 may generate a relayed message that includes information reflecting the second zone ID and/or the relay ID of the relay 506. In some aspects, generating the relayed message at 515 may further include including a second destination ID in the relayed message, where the second destination ID may include information reflecting the first zone ID, the second zone ID of the relay, and the relay ID.

When relay 506 receives the first message, relay 506 may form a relayed message. For example, the relayed message may include a second source L2 ID and a second destination ID. The second source L2 ID may be the L2 ID of the relay 506. In another example, the second source L2 ID may be the source L2 ID in the received first message. The relay 506 may map the second destination L2 ID according to the zone information (e.g., the first zone ID) in the first message. The first zone ID may be carried in a MAC header or an SDAP header of the first message, which is used for relay 506 to convert the first zone ID to the second destination L2 ID. The second destination L2 ID may include information reflecting the first zone ID. For example, relay 506 may include such information in PHY layer control information regarding data transmission of the relayed message. For example, the first zone ID may be mapped to a second destination L2 ID, which may be included/reflected in the control information for the relayed message. For example, there may be another flag indicating that this is a relayed message.

The second destination ID may further include information reflecting the second zone ID of the relay 506, and/or the relay ID. For example, the second destination ID may be a function of the first zone ID, the second zone ID of the relay, and the relay ID. The relay 506 may map the second destination L2 ID according to the partition information in the first message.

In some aspects, information reflecting the first zone ID may be included in control information for the relayed message. In some aspects, the information reflecting the first zone ID may be indicated in a Scheduling Assignment (SA) for the relayed message. In some aspects, the information reflecting the first zone ID may be indicated in a MAC header of the relayed message. For example, when issuing the relayed message, the second destination L2 ID may be reflected in the control information, for example, in the Scheduling Assignment (SA). For example, the first zone ID may be reflected in the SA as part of the second destination ID in the MAC (or SDAP) header. The SA may be sent in a different channel and radio frame than the data of the relayed message.

In some aspects, relay 506 may select a radio resource group for sending the relayed message based on a second destination ID included in the relayed message reflecting the first zone ID. The radio resource group may include a set of radio resources in time and frequency. Relay 506 may use different radio resource groups for messages from different regions. The control information (e.g., SA) may be sent in a different channel and radio frame than the data of the relayed message. For example, the SA may be transmitted in a physical side link control channel (PSCCH), while the relayed data may be transmitted in a physical side link shared channel (pscsch).

At 520, the relay 506 may transmit a relayed message that includes information reflecting the first zone ID. The relay 506 may transmit the relayed message in response to determining to relay the first message. In some aspects, information reflecting the first zone ID is included in control information for a relayed message, wherein transmitting the relayed message comprises: the control information is transmitted in the PSCCH and the data of the relayed message is transmitted in the PSCCH.

At 533, the recipient device 504 may identify a message that includes information reflecting the first zone ID of the transmitting device. The message may be the first message (original message) 510 or a relayed message 520 from a relay. Upon receipt of both messages by the recipient device, the recipient device may perform the identification and determination at 533, 535 for each message. The receiver device 504 may be able to filter relayed messages from zone IDs that the receiver device 504 may want to exclude at lower layers (e.g., PHY layer/MAC control). Filtering of the zone ID may be done at lower layers based on control information for the message. The zone ID may be indicated in the destination L2 ID. For example, the control information may be received in a control channel (e.g., PSCCH). The destination L2 ID may be reflected in the PHY/MAC control information, which may be used by the receiver device 504 to filter the message without processing the actual data packets of the message.

The recipient device 504 can handle the message and perform the decision based on the control information for the message. For example, the recipient device 504 can decide whether to decode the corresponding data block of the message based on control information for the message (such as the SA for the message). Upon receiving the SA, the recipient device 504 has not decoded any of the contents of the header of the message. In this way, processing time may be reduced and processing resources may be saved, which prevents the recipient UE from dropping other messages. Therefore, the reliability and coverage of communication can be advantageously increased.

At 535, the receiving device 504 may determine whether to decode the data of the message based at least on the first zone ID of the transmitting device. Thus, the receiving device may determine the zone ID of the transmitting device, e.g., based on control information that may indicate the destination L2 ID of the message. The recipient device 504 may determine whether to decode the data of the message based on the destination L2 ID (which may include information reflecting the first zone ID). For example, if the transmitting device 502 of the original message is in the same region as the receiving device 504, the receiving device may determine not to decode or otherwise process the relayed message, e.g., filter the message. This may reduce unnecessary processing by the receiving device, as the receiving device is likely to receive the original message directly from the transmitting device in the same zone, and processing the relayed message will unnecessarily repeat processing at the receiving device. In another example, the recipient device can determine that the recipient device will not decode the set of nearby zone IDs of the relayed message.

The recipient device 504 may first determine whether the message is a relayed message. The flag of the message may indicate whether the message is a relayed message or a message directly from the original transmitting device. The receiving device may then determine the zone ID of the transmitting device, and may determine whether the zone ID of the transmitting device is in the same zone as the receiving device 504 or in an excluded zone ID set before continuing to receive/process/decode the data blocks of the relayed message. The filtering determination may be implemented by including such zone ID information in PHY layer/MAC layer control information related to transmission of the relayed message. With this formation, even if the receiver apparatus receives a duplicate message, the receiver apparatus 504 can avoid unnecessary processing.

In some aspects, to determine whether the transmitting device and the receiving device have the same zone ID, the receiving device 504 may further determine a receiving zone ID of the receiving UE. The recipient UE may determine its geographic location and a corresponding zone ID based on the geographic location. When the message includes a relayed message and the first zone ID is the same as the recipient zone ID or a set of excluded zone IDs in the vicinity of the recipient zone ID, the recipient device 504 (e.g., recipient UE) may determine to refrain from decoding data of the message. In another aspect, when the message includes a relayed message and the first zone ID is different from the recipient zone ID, the recipient device 504 may determine to decode data of the message. In some aspects, identifying the message includes receiving control information for the message, where the control information includes information reflecting the first zone ID.

As an example, the recipient device 504 may be configured to: when the destination ID is a broadcast group ID, or the destination ID is from a relay in a different zone than the recipient device 504, the data of the message is decoded. Further, the recipient device 504 can use the ID of the relay or the zone ID of the relay to decide whether to receive from a particular relay. In this way, the recipient device 504 may avoid receiving the relayed message from a relay in the same zone as the recipient device 504.

In some aspects, the recipient device 504 may determine whether to decode the data of the message further based on the relayed second zone ID and whether the message includes a relayed message from the relay. For example, the receiver device 504 may determine whether to decode the data of the message further based on whether the second zone ID is the same as the first zone ID or the receiver device's own zone ID. In some aspects, the recipient device 504 may determine whether to decode the data of the message further based on the relay ID of the relay 506 and whether the message includes a relayed message from the relay 506.

At 537, the recipient device 504 may decode or refrain from decoding data of the message according to the determination based on the first zone ID.

Fig. 6 is a flow diagram 600 of a method of wireless communication at a transmitting device. The method may be performed, for example, by a transmitting UE or a component of a transmitting UE (e.g., UE 104; transmitting devices 402, 502, 1050; apparatus 702/702 '; processing system 814, which may include memory 360/376, and which may be an entire UE or a component of a UE, such as TX processor 368/316, RX processor 356/370, and/or controller processor 359/375) in communication with a relay (e.g., UE104 '; relay devices 406, 408, 506, etc.) and a receiving UE (e.g., UE104 '; receiving devices 404, 504, etc.) in a wireless communication. The method may improve efficient use of wireless resources and improve efficient use of processing power at a recipient device by reducing excessive duplication of relayed messages while providing lower layer processing of messages. The wireless communications may include any of eV2X, V2X, V2V, or D2D communications. The transmitting UE may comprise a vehicle or a device included in a vehicle. To facilitate an understanding of the techniques and concepts described herein, the method of flowchart 600 may be discussed with reference to the examples illustrated in fig. 4 and 5. Optional aspects may be illustrated in dashed lines.

At 608, the transmitting device may determine a first zone ID of the transmitting UE. This determination may be performed, for example, by the zone ID component 708 of the equipment 702. The geographical partition information of the transmitting device may be mapped to the layer 2 identifier (L2 ID) of the transmitting device to allow control of received messages and traffic separation. In some aspects, determining the first zone ID of the transmitting device may include: as illustrated by 610, a geographic location of a transmitting device is determined; and as illustrated by 616, convert the geographic location to the first zone ID. For example, the geographic location may be converted to a first zone ID based on a preconfigured relationship. As another example, the geographic location may be converted to a zone ID based on information received from a base station (not shown). As yet another example, the geographic location may be converted to a zone ID based on information received from the relay.

At 612, the transmitting device may generate a message including the first zone ID. The message may be generated, for example, by message component 712 of equipment 702. For example, in the message, the transmitting device may include a first zone ID, a first source L2 ID, which may be the L2 ID of the transmitting device, and a first destination L2 ID, which may be a broadcast group L2 ID. By providing an indication of the zone ID of the transmitting device in conjunction with the message, the relay device may avoid relaying messages of the transmitting device that are likely to reach a similar coverage level. This may avoid excessive duplication of the message. Likewise, the indication of the zone IDs may facilitate the receiving device to filter the relayed message based on the message that the receiving device also received directly from the transmitting device, in order to avoid decoding the relayed message.

In some aspects, the first zone ID may be included in a MAC header of the message. The transmitting device may include the first zone ID in a MAC header of the message. In some other aspects, the first zone ID may be included in an SDAP header of the message. The transmitting device may include the first zone ID in an SDAP header of the message. The first zone ID may be included in control information of the message. In some aspects, the message further includes an L2 ID based on at least one of the source ID and the destination ID in addition to the first zone ID. The source ID may include the L2 ID of the transmitting device, and the destination ID may include the broadcast group ID. The transmitting device may include an L2 ID in the message based on at least one of the source ID and the destination ID. In some aspects, the message may further include an indicator indicating whether the first message should be relayed. The message may further include a designation of a relay that is expected to forward the message. The designation of whether the message is a relayed message along with the zone ID information from the transmitting device enables the receiving device to filter the message to more efficiently utilize its processing capabilities. The transmitting device may include an indicator in the message indicating whether the message should be relayed.

At 614, the transmitting device may transmit a message including the first zone ID. The message may be transmitted, for example, by a transmission component 706 of the apparatus 702. The message may be transmitted for direct reception by other UEs (e.g., UE 750).

Fig. 7 is a conceptual data flow diagram 700 illustrating the data flow between different apparatuses/components in an example apparatus 702. The method may be performed, for example, by a transmitting device (e.g., UE 104; transmitting device 402, 502, 1050; equipment 702/702', etc.) in wireless communication with a relay device (e.g., UE104 ", 406, 408, 506, 750, equipment 1002/1002', etc.) and/or a receiving device (e.g., UE104 ', receiving device 404, 504, 750; equipment 1302/1302', etc.). The transmitting device may include, for example, a component of the UE or the entire UE. The wireless communications may include eV2X, V2X, V2V, or D2D communications as described herein.

The apparatus includes a zone ID component 708 that determines a zone ID of the apparatus, e.g., as described in connection with 503, 608. The apparatus can also include a source ID component 710 that determines a source ID and a destination ID component 714 that determines a destination ID for the communication. In some aspects, the zone ID component 708 can determine a geographic location of the equipment and convert the geographic location to a zone ID.

The apparatus includes a message component 712 that generates a message including a zone ID, e.g., as described in connection with 505, 612. In some aspects, the first zone ID may be included in a MAC header of the message. The transmitting UE may include the first zone ID in a MAC header of the message. In some other aspects, the first zone ID may be included in an SDAP header of the message. The transmitting UE may include the first zone ID in an SDAP header of the message. The first zone ID may be included in control information of the message. In some aspects, the message further includes an L2 ID based on at least one of the source ID and the destination ID in addition to the first zone ID. The source ID may include the L2 ID of the transmitting UE, and the destination ID may include the broadcast group ID. The transmitting UE may include an L2 ID in the message based on at least one of the source ID and the destination ID. In some aspects, the message may further include an indicator indicating whether the first message should be relayed. The message may further include a designation of a relay that is expected to forward the message. The transmitting UE may include an indicator in the message indicating whether the message should be relayed.

The apparatus includes a transmission component 706 for transmitting a message including a zone ID to a recipient/relay UE, e.g., as described in connection with 510, 614. The apparatus further includes a receiving component 704 that receives feedback from the recipient UE regarding receipt of the message.

The apparatus may include additional components that perform each block of the algorithm in the aforementioned flow diagrams of fig. 5-6. As such, each block in the aforementioned flow diagrams of fig. 5-6 may be performed by a component and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by a processor configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

Fig. 8 is a diagram 800 illustrating an example of a hardware implementation of an apparatus 702' employing a processing system 814. The processing system 814 may be implemented with a bus architecture, represented generally by the bus 824. The bus 824 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 814 and the overall design constraints. The bus 824 links together various circuits including one or more processors and/or hardware components, represented by the processor 804, the components 704, 706, 708, 710, 712, 714, and the computer-readable medium/memory 806. The bus 824 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 814 can be coupled to the transceiver 810. The transceiver 810 is coupled to one or more antennas 820. The transceiver 810 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 810 receives signals from the one or more antennas 820, extracts information from the received signals, and provides the extracted information to the processing system 814 (and in particular the receiving component 704). Additionally, transceiver 810 receives information from processing system 814 (and in particular transmission component 706) and generates a signal to be applied to the one or more antennas 820 based on the received information. The processing system 814 includes a processor 804 coupled to a computer-readable medium/memory 806. The processor 804 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 806. The software, when executed by the processor 804, causes the processing system 814 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 806 may also be used for storing data that is manipulated by the processor 804 when executing software. The processing system 814 further includes at least one of the components 704, 706, 708, 710, 712, 714. These components may be software components running in the processor 804, resident/stored in the computer readable medium/memory 806, one or more hardware components coupled to the processor 804, or some combination thereof. In one configuration, the processing system 814 may be a component of the device 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. Alternatively, the processing system 814 may include the entire UE.

In one configuration, the apparatus for wireless communication 702/702' includes means for determining a zone ID of the apparatus (transmitting device). The apparatus may include means for generating a message including a zone ID. The apparatus may include means for transmitting the message directly to at least one recipient device. The aforementioned means may be the aforementioned components of apparatus 702 and/or one or more components of processing system 814 of apparatus 702' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 814 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

Fig. 9 is a flow diagram 900 of a method of wireless communication at a relay device. The method may be performed, for example, by a relay (e.g., UE104 ", 406, 408, 506, 750, apparatus 1002/1002 '; processing system 1114, which may include memory 360/376 and which may be an entire UE or a component of a UE, such as TX processor 368/316, RX processor 356/370, and/or controller processor 359/375) communicating with a transmitting UE (e.g., UE 104; transmitting device 402, 502 ', etc.) and a receiving UE (e.g., UE104 '; receiving device 404, 504, etc.) in a wireless communication. The relay device may comprise a vehicle or a device installed in a vehicle. To facilitate an understanding of the techniques and concepts described herein, the method of flowchart 900 may be discussed with reference to the examples illustrated in fig. 4-5. Optional aspects may be illustrated in dashed lines.

At 908, the relay device may receive a message including a first zone ID of the transmitting UE. The message may be received, for example, by receiving component 1004 of apparatus 1002. For example, the message may be received directly from the transmitting UE. The message may be communicated based on eV2X, V2V, V2X, or D2D.

At 910, the relay device may determine whether to relay the message based at least on the first zone ID. This determination may be performed, for example, by determining component 1008 of apparatus 1002. Based on the first zone ID information in the MAC or SDAP header of the message, the relay may decide to act, e.g., whether or not to relay the message, and map the first zone ID to a new destination ID if the relay decides to relay. In some aspects, the relay may determine to relay the message when the relay is in a different zone than a zone corresponding to the first zone ID in the message. In some aspects, the relay may determine not to relay the message when the relay is in the same zone as the zone corresponding to the first zone ID in the first message. By using the zone ID of the transmitting device to determine whether to relay messages, the relaying device may avoid relaying messages of the transmitting device that are likely to reach a similar coverage level. This may avoid excessive duplication of messages and may improve efficient use of radio resources.

At 912, if the relay device determines to relay the first message, the relay may generate a relayed message, where the relayed message includes information reflecting the first zone ID. The message may be generated, for example, by message component 1010 of apparatus 1002. In some aspects, generating the relayed message may further include including information reflecting the second zone ID of the relay in the relayed message, as illustrated at 914. The second zone ID may be included, for example, by the second zone ID component 1012. In some aspects, generating the relayed message may further include including information reflecting the relay ID in the relayed message, as illustrated at 916. The relay ID can be included, for example, by the relay ID component 1014. In some aspects, generating the relayed message may further include including a second destination ID in the relayed message, wherein the second destination ID may include information reflecting the first zone ID, the second zone ID of the relay, and the relay ID, as illustrated at 918. The destination ID can be included, for example, by destination ID component 1016 of apparatus 1002.

In some aspects, information reflecting the first zone ID may be included in control information for the relayed message. In some aspects, information reflecting the first zone ID may be indicated in a scheduling assignment for the relayed message. In some aspects, the information reflecting the first zone ID is indicated in a MAC header of the relayed message.

In some aspects, the relay device may select a radio resource group for transmitting the relayed message based on a first zone ID included in the message, as illustrated at 920. The relay may use different radio resource groups for messages from different regions.

At 922, the relay 506 may transmit a relayed message including information reflecting the first zone ID in response to determining to relay the message. The transmission of the relayed message can be performed, for example, by transmission component 1006 of apparatus 1002. In some aspects, information reflecting the first zone ID may be included in control information for a relayed message, wherein transmitting the relayed message comprises: the control information is transmitted in the PSCCH and the data of the relayed message is transmitted in the PSCCH.

Fig. 10 is a conceptual data flow diagram 1000 illustrating the data flow between different apparatuses/components in an example apparatus 1002. The apparatus may be a relay (e.g., UE104 ", 406, 408, 506, equipment 1002/1002', etc.) in wireless communication communicating with a transmitting UE (e.g., UE 104; transmitting device 402, 502, 1050; equipment 702/702', etc.) and a receiving UE (e.g., UE104 '; receiving device 404, 504, 1050 '; equipment 1302/1302', etc.). The wireless communications may include eV2X, V2X, V2V, or D2D communications as described herein. The apparatus may include a component of the UE or the entire UE.

The apparatus includes a receiving component 1004 that receives a message including a first zone ID of a transmitting device, e.g., as described in connection with 510, 908.

The apparatus includes a determination component 1008 that determines whether to relay the message based at least on the first zone ID, e.g., as described in connection with 513, 910. In some aspects, the relay may determine to relay the message when the relay is in a different zone than a zone corresponding to the first zone ID in the message. In some aspects, the relay may determine not to relay the message when the relay is in the same zone as the zone corresponding to the first zone ID in the first message.

The apparatus includes a message component 1010 that generates a relayed message, wherein the relayed message includes information reflecting the first zone ID, e.g., as described in connection with 515, 912. In some aspects, the message component 1010 further includes a second zone ID component 1012 that includes the relayed second zone ID in the relayed message. In some aspects, the message component 1010 further comprises a relay ID component 1014 that includes the relayed ID in the relayed message. In some aspects, the message component 1010 further includes a second destination ID 1016 that includes the relayed second destination ID in the relayed message.

In some aspects, information reflecting the first zone ID may be included in control information for the relayed message. In some aspects, information reflecting the first zone ID may be indicated in a scheduling assignment for the relayed message. In some aspects, the information reflecting the first zone ID is indicated in a MAC header of the relayed message.

The apparatus may include a selecting component 1018 that selects a radio resource group for transmitting the relayed message based on the first zone ID included in the message. The relay device may use different radio resource groups for messages from different regions.

The apparatus may include a transmitting component 1006 that transmits a relayed message including information reflecting the first zone ID in response to determining to relay the message. In some aspects, information reflecting the first zone ID is included in control information for a relayed message, wherein transmitting the relayed message comprises: the control information is transmitted in the PSCCH and the data of the relayed message is transmitted in the PSCCH.

The apparatus may include additional components that perform each block of the algorithm in the aforementioned flow diagrams of fig. 4, 5, and 9. As such, each block in the aforementioned flow diagrams of fig. 4, 5, and 9 may be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by a processor configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

Fig. 11 is a diagram 1100 illustrating an example of a hardware implementation of an apparatus 1002' employing a processing system 1114. The processing system 1114 may be implemented with a bus architecture, represented generally by the bus 1124. The bus 1124 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1114 and the overall design constraints. The bus 1124 links together various circuits including one or more processors and/or hardware components (represented by the processor 1104, the components 1004, 1006, 1008, 1010, 1012, 1014, 1016, 1018, and the computer-readable medium/memory 1106). The bus 1124 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 1114 may be coupled to a transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1110 receives a signal from the one or more antennas 1120, extracts information from the received signal, and provides the extracted information to the processing system 1114 (and in particular the receiving component 1004). In addition, the transceiver 1110 receives information from the processing system 1114 (and in particular the transmission component 1006) and generates a signal to be applied to the one or more antennas 1120 based on the received information. The processing system 1114 includes a processor 1104 coupled to a computer-readable medium/memory 1106. The processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 1106 may also be used for storing data that is manipulated by the processor 1104 when executing software. The processing system 1114 further includes at least one of the components 1004, 1006, 1008, 1010, 1012, 1014, 1016, 1018. These components may be software components running in the processor 1104, resident/stored in the computer readable medium/memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. In one configuration, the processing system 1114 may be a component of the device 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. Alternatively, the processing system 814 may include the entire UE.

In one configuration, the apparatus 1002/1002' for wireless communication includes means for receiving a message including a first zone Identifier (ID) of a transmitting device. The apparatus may include means for determining whether to relay the message based at least on the first zone ID. The apparatus may include means for generating a relayed message including information reflecting the first zone ID. The apparatus may include means for transmitting a message including an indication of a zone ID. The apparatus may include means for including second information indicative of a second zone ID of the relay device in the relayed message. The apparatus may include means for including additional information indicative of a relay device ID in the relayed message. The apparatus may include means for selecting a radio resource group for transmitting a relayed message based on a first zone ID included in the message. The apparatus may include means for including a destination ID in the relayed message, wherein the destination ID is based on the first zone ID, the second zone ID of the relay device, and the relay device ID. The aforementioned means may be the aforementioned components of apparatus 1002 and/or one or more components of processing system 1114 of apparatus 1002' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1114 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

Fig. 12 is a flow diagram 1200 of a method of wireless communication at a recipient device. The method may be performed, for example, by a receiving UE (e.g., UE104 '; receiving device 404, 504, 1050 '; apparatus 1302/1302', processing system 1414, which may include the memory 360/376 and which may be an entire UE or a component of the UE, such as TX processor 368/316, RX processor 356/370, and/or controller processor 359/375) in wireless communication with a transmitting UE (e.g., UE 104; transmitting device 402, 502, 1050; apparatus 702/702', etc.) and a relay (e.g., UE104 ", 406, 408, 506, 750, apparatus 1002/1002', etc.). The wireless communications may include eV2X, V2V, V2X, or D2D communications. The recipient UE may comprise a vehicle or a device installed in a vehicle. To facilitate an understanding of the techniques and concepts described herein, the method of flowchart 1200 may be discussed with reference to the examples illustrated in fig. 4-5. Optional aspects may be illustrated in dashed lines.

At 1202, a receiving device can identify a message that includes information reflecting a first zone ID of a transmitting device. The identification may be performed, for example, by receiving component 1204 of apparatus 1202. The message may be an original message, or a relayed message from a relay device. The message may include messages similar to messages 410, 412, 414, 510, 520.

The recipient device can determine, for example at 1204, whether the message is a relayed message. This determination may be performed, for example, by determining component 1308 of apparatus 1302. If the message is a relayed message, the recipient device can proceed with a determination as to whether to decode the relayed message. If the message is determined to be, for example, an original message that was not relayed, the UE may continue to decode the message at 1206. The transmission may be performed, for example, by transmission component 1306 of apparatus 1302.

At 1214, the receiving device may determine whether to decode data of the message based at least on the first zone ID of the transmitting device. This determination may be performed, for example, by determining component 1308 of apparatus 1302. This determination may be based on aspects described in connection with 535 of FIG. 5. Using the zone ID of the transmitting device to determine whether to decode the message enables the receiving device to filter relayed messages that the UE is likely to receive the same message directly from the transmitting device. This enables the receiving side to avoid unnecessary processing.

In some aspects, as illustrated by 1210, the recipient device may further determine a recipient zone ID of the recipient device. This determination may be performed, for example, by receiver device partition ID component 1310 of apparatus 1302. For example, when the message comprises a relayed message and the first zone ID is the same as the recipient zone ID, the recipient device 504 can determine, at 1216, to refrain from decoding data of the message. In another aspect, when the message includes a relayed message and the first zone ID is different from the recipient zone ID, the recipient UE may determine to decode data of the message. In some aspects, identifying the message includes receiving control information for the message, where the control information includes information reflecting the first zone ID.

In some aspects, the message comprises a relayed message, and information reflecting the first zone ID is indicated in the scheduling assignment for the relayed message. In some aspects, information reflecting the first zone ID is included in control information received in the PSCCH.

In some aspects, as illustrated at 1212, the recipient device may further determine a set of zone IDs that the recipient device is capable of receiving messages directly from the transmitter device. For example, the zone ID set may be determined by the zone ID set component 1312 of the apparatus 1302. For example, when the message comprises a relayed message and the set of zone IDs comprises a first zone ID, the receiving device may determine, at 1216, to refrain from decoding data of the message. In some aspects, the receiving device may determine whether to decode data of the message based further on the radio resource group receiving the message. In some aspects, the first zone ID is included in a MAC header or an SDAP header of the message.

In some aspects, the recipient device may determine whether to decode data of the message further based on the relayed second zone ID and whether the message includes a relayed message from the relay. For example, the recipient device can determine whether to decode the data of the message further based on whether the second zone ID is the same as the first zone ID. In some aspects, the recipient device may determine whether to decode data of the message based further on the relay ID of the relay device and whether the message includes a relayed message from the relay UE.

At 1220, the recipient device can decode or refrain from decoding data of the message according to the determination based on the first zone ID. The decoding may be performed, for example, by decoding component 1314 of apparatus 1302 based on the determination of determining component 1308.

Fig. 13 is a conceptual data flow diagram 1300 illustrating the data flow between different apparatuses/components in an example apparatus 1302. The apparatus may be a receiving UE (e.g., UE104 '; receiving devices 404, 504, 1050 '; apparatus 1302/1302', etc.) in wireless communication with a transmitting UE or relay 1350. The wireless communications may include eV2X, V2X, V2V, or D2D communications as described herein. The apparatus may include a component of the UE or the entire UE.

The apparatus includes a receiving component 1304 that receives a message including information reflecting a first zone ID of a transmitting device, e.g., as described in connection with 533, 1202. The message may be an original message from the transmitting device, or a relayed message from the relay UE.

The apparatus includes a determining component 1308 that determines whether to decode data of the message based at least on a first zone ID of a transmitting device, e.g., as described in connection with 535, 1214. In some aspects, the apparatus may further include a receiver zone ID component 1310 that determines a receiver zone ID of the receiver device, e.g., as described in connection with 1210. When the message includes a relayed message and the first zone ID is the same as the recipient zone ID, the recipient device may determine to refrain from decoding data of the message. In another aspect, when the message includes a relayed message and the first zone ID is different from the recipient zone ID, the recipient UE may determine to decode data of the message.

In some aspects, the apparatus may further include a zone ID set component 1312 that determines a zone ID set for which the receiving device is capable of receiving messages directly from the transmitting device, e.g., as described in connection with 1212. When the message comprises a relayed message and the set of zone IDs comprises a first zone ID, the recipient device may determine to refrain from decoding data of the message. In some aspects, the receiving device may determine whether to decode data of the message based further on the radio resource group receiving the message. In some aspects, the first zone ID is included in a MAC header or an SDAP header of the message.

In some aspects, the apparatus may further include a relay zone ID component 1316 that determines a relay zone ID. In some aspects, the recipient device may determine whether to decode data of the message further based on a relay zone ID of the relay and whether the message includes a relayed message from the relay. For example, the recipient device may determine whether to decode the data of the message further based on whether the relay zone ID is the same as the first zone ID. In some aspects, the recipient device may determine whether to decode data of the message based further on the relay ID of the relay and whether the message includes a relayed message from the relay.

The apparatus includes a decoding component 1314 that decodes data of the message according to the determination based on the first zone ID. The apparatus may include a transmitting component 1306 that transmits a message.

The apparatus may include additional components that perform each block of the algorithm in the aforementioned flow diagrams of fig. 4, 5 and 12. As such, each block in the aforementioned flow diagrams of fig. 4, 5, and 12 may be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by a processor configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

Fig. 14 is a diagram 1400 illustrating an example of a hardware implementation of an apparatus 1302' employing a processing system 1414. The processing system 1414 may be implemented with a bus architecture, represented generally by the bus 1424. The bus 1424 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1414 and the overall design constraints. The bus 1424 links together various circuits including one or more processors and/or hardware components (represented by the processor 1404, the components 1304, 1306, 1308, 1310, 1312, 1314, 1316, and the computer-readable medium/memory 1406). The bus 1424 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 1414 can be coupled to the transceiver 1410. The transceiver 1410 is coupled to one or more antennas 1420. The transceiver 1410 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1410 receives signals from the one or more antennas 1420, extracts information from the received signals, and provides the extracted information to the processing system 1414, and in particular the receiving component 1304. Additionally, transceiver 1410 receives information from processing system 1414 (specifically transmission component 1306) and generates a signal to be applied to the one or more antennas 1420 based on the received information. The processing system 1414 includes a processor 1404 coupled to a computer-readable medium/memory 1406. The processor 1404 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 1406. The software, when executed by the processor 1404, causes the processing system 1414 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 1406 may also be used for storing data that is manipulated by the processor 1404 when executing software. The processing system 1414 further includes at least one of the components 1304, 1306, 1308, 1310, 1312, 1314, 1316. These components may be software components running in the processor 1404, resident/stored in the computer readable medium/memory 1406, one or more hardware components coupled to the processor 1404, or some combination thereof. In one configuration, the processing system 1414 may be a component of the device 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. Alternatively, the processing system 814 may include the entire UE.

In one configuration, the apparatus for wireless communication 1302/1302' includes means for identifying a message that includes information reflecting a first zone ID of a transmitting device. The apparatus may include means for determining whether the message comprises a relayed message. The apparatus may include means for determining whether to decode data of the message based at least on a first zone ID of a transmitting device. The apparatus may include means for decoding or refraining from decoding data of the message according to the determination based on the first zone ID. The apparatus may include means for determining a second zone ID of the recipient device, and the means for determining whether to decode the message may refrain from decoding the message when the message includes a zone ID that is the same as the second zone ID of the recipient device. The apparatus may further include means for determining a set of zone IDs that the receiving device is capable of receiving messages directly from the transmitting device. The aforementioned means may be the aforementioned component of apparatus 1302 and/or one or more components of processing system 1414 of apparatus 1302' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1414 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

Any aspect in the following examples may be combined with any aspect of the previous discussion and/or embodiments described herein without limitation.

Example 1 is a method of wireless communication at a transmitting device, comprising: determining an ID of a transmitting device; generating a message including a zone ID; and transmitting the message directly to at least one recipient device. In example 2, the method of example 1 further comprises: the message is transmitted based on either V2V communication or V2X, or D2D communication. In example 3, the method of any of examples 1-2 further comprising: the zone ID is included in the MAC header of the message. In example 4, the method of any of examples 1-3 further comprising: the zone ID is included in the SDAP header of the message. In example 5, the method of any of examples 1-4 further comprising determining the zone ID of the transmitting device comprises: determine a geographic location of the transmitting device, and convert the geographic location to a zone ID. In example 6, the method of any of examples 1-5, further comprising: the geographic location is converted to a zone ID based on the preconfigured relationship. In example 7, the method of any of examples 1-6 further comprising: the geographic location is converted to a zone ID based on information received from the base station. In example 8, the method of any one of examples 1-7 further includes: the geographic location is converted to a zone ID based on information received from the relay device. In example 9, the method of any one of examples 1-8 further comprising: in addition to the zone IDs, the message further includes a layer 2ID based on at least one of the source ID and the destination ID. In example 10, the method of any of examples 1-9, further comprising: the source ID includes a layer 2ID of the transmitting device, and the destination ID includes a broadcast group ID. In example 11, the method of any of examples 1-10 further comprising: the message further includes an indicator indicating whether the message should be relayed. In example 12, the method of any of examples 1-11 further comprising: the message further includes a designation of a relay device that is expected to forward the message. In example 13, the method of any of examples 1-12 further comprising: the zone ID is included in the control information of the message.

Example 14 is a system or an apparatus comprising means for implementing a method as in any of examples 1-13 or for implementing an apparatus as in any of examples 1-13.

Example 15 is an apparatus comprising one or more processors and memory in electronic communication with the one or more processors, the memory storing instructions executable by the one or more processors to cause a system or apparatus to implement a method as in any of examples 1-13.

Example 16 is a non-transitory computer-readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any one of examples 1-13.

Example 17 is a method of wireless communication at a relay device, comprising: receiving a message including a first ID of a transmitting device; determining whether to relay the message based at least on the first zone ID; and if the relay device determines to relay the message, generating a relayed message including information reflecting the first zone ID. In example 18, the method of example 17 further comprising: when the relay device is located in a region different from the region corresponding to the first region ID in the message, the relay device determines to relay the message. In example 19, the method of any of examples 17-18 further comprising: generating the relayed message further includes including information reflecting the second zone ID of the relay device in the relayed message. In example 20, the method of any of examples 17-19 further comprising: generating the relayed message further includes information reflecting the relay device ID in the relayed message. In example 21, the method of any of examples 17-20 further comprising: information reflecting the first zone ID is included in the control information for the relayed message. In example 22, the method of any of examples 17-21, further comprising: information reflecting the first zone ID is indicated in the scheduling assignment for the relayed message. In example 23, the method of any of examples 17-22 further comprising: information reflecting the first zone ID is included in a MAC header of the relayed message. In example 24, the method of any of examples 17-23 further comprising: a radio resource group for transmitting the relayed message is selected based on the first zone ID included in the message. In example 25, the method of any of examples 17-24 further comprising: the message is received based on a V2V communication, a V2X, or a D2D communication. In example 26, the method of any one of examples 17-25 further comprising, generating the relayed message further comprises: a destination ID is included in the relayed message, wherein the destination ID includes information reflecting the first zone ID, the second zone ID of the relay device, and the relay device ID. In example 27, the method of any of examples 17-26 further comprising: the relayed message is transmitted in response to determining to relay the message. In example 28, the method of any of examples 17-27, further comprising: information reflecting the first zone ID is included in control information for a relayed message, wherein transmitting the relayed message comprises: transmitting the control information in the PSCCH; and transmitting the data of the relayed message in the PSSCH.

Example 29 is a system or an apparatus comprising means for implementing a method as in any of examples 17-28 or for implementing an apparatus as in any of examples 17-28.

Example 30 is an apparatus comprising one or more processors and memory in electronic communication with the one or more processors, the memory storing instructions executable by the one or more processors to cause a system or apparatus to implement a method as in any of examples 17-28.

Example 31 is a non-transitory computer-readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any one of examples 17-28.

Example 32 is a method of wireless communication at a recipient device, comprising: identifying a message including information reflecting a first ID of a transmitting device; determining whether the message comprises a relayed message; determining whether to decode data of the message based at least on a first zone ID of the transmitting device; and decode or refrain from decoding data of the message according to the determination based on the first zone ID. In example 33, the method of example 32, further comprising: determining a second zone ID of the recipient device, wherein determining whether to decode data of the message comprises: refraining from decoding data of the message when the message comprises a relayed message and the first zone ID is the same as the second zone ID. In example 34, the method of any of examples 32-33, further comprising identifying the message including information reflecting the first zone ID includes: control information for the message is received, the control information including information reflecting the first zone ID. In example 35, the method of any of examples 32-34, further comprising: determining a set of zone IDs that a receiving device is capable of receiving a message directly from a transmitting device, wherein determining whether to decode data of the message comprises: when the message comprises a relayed message and the set of zone IDs comprises a first zone ID, refraining from decoding data of the message. In example 36, the method of any of examples 32-35, further comprising: the receiving device further determines whether to decode data of the message based on the radio resource group of the received message. In example 37, the method of any of examples 32-36, further comprising: information reflecting the first zone ID is included in a MAC header of the message. In example 38, the method of any of examples 32-37, further comprising: the first zone ID is included in the SDAP header of the message. In example 39, the method of any of examples 32-38 further comprising: the message includes a relayed message, and information reflecting the first zone ID is indicated in a scheduling assignment for the relayed message. In example 40, the method of any of examples 32-39, further comprising: information reflecting the first zone ID is included in control information received in a physical side link control channel (PSCCH). In example 41, the method of any of examples 32-40, further comprising: the message is received based on a V2V communication, a V2X communication, or a D2D communication. In example 42, the method of any of examples 32-41, further comprising: the recipient device further determines whether to decode data of the message based on the second zone ID of the relay device and whether the message includes a relayed message from the relay device. In example 43, the method of any one of examples 32-42, further comprising: the recipient device further determines whether to decode data of the message based on whether the second zone ID is the same as the first zone ID. In example 44, the method of any of examples 32-43, further comprising: the recipient device further determines whether to decode data of the message based on the relay device ID of the relay device and whether the message includes a relayed message from the relay device.

Example 45 is a system or an apparatus comprising means for implementing a method as in any of examples 32-44 or for implementing an apparatus as in any of examples 32-44.

Example 46 is an apparatus comprising one or more processors and memory in electronic communication with the one or more processors, the memory storing instructions executable by the one or more processors to cause a system or apparatus to implement a method as in any of examples 32-44.

Example 47 is a non-transitory computer-readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any one of examples 32-44.

It should be understood that the specific order or hierarchy of blocks in the processes/flow diagrams disclosed is an illustration of example approaches. It will be appreciated that the specific order or hierarchy of blocks in the processes/flow diagrams may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. The term "some" or "an" refers to one or more, unless specifically stated otherwise. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and/or C, and may include a plurality of a, B, or C. In particular, combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" may be a only, B only, C, A and B, A and C, B and C only, or a and B and C, wherein any such combination may include one or more members of A, B or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The terms "module," mechanism, "" element, "" device, "and the like may not be a substitute for the term" means. As such, no claim element should be construed as a means-plus-function unless the element is explicitly recited using the phrase "means for … …".