Unicast packet addressing and communication

Abstract

Mechanisms for performing unicast packet addressing and communication (e.g., in C-V2X sidelink communication scenarios) are provided. In one aspect, a method for wireless communication performed by a first wireless communication device includes receiving a source identifier associated with a second wireless communication device and determining a destination identifier based on the source identifier associated with the second wireless communication device and a deterministic function. The destination identifier is different than the source identifier. The method further includes generating a packet that includes the destination identifier, where the destination identifier indicates a unicast packet, and transmitting the unicast packet to the second wireless communication device.

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to U.S. Patent Application No. 17 / 447,761, filed September 15, 2021, which in turn claims priority and benefit to U.S. Provisional Patent Application No. 63 / 079,283, filed September 16, 2020, both of which are incorporated herein by reference in their entirety. Technical Field

[0003] This application relates to wireless communication devices, systems, and methods, and more specifically, to devices, systems, and methods for transmitting unicast packets using cellular vehicle-to-everything (C-V2X) communication.

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Wireless multiple access communication systems may include several base stations (BSs), each supporting communication from multiple communication devices simultaneously, which may also be referred to as user equipment (UEs).

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0007] A wireless communication network may include several base stations (BSs) capable of supporting communication between several user equipments (UEs). UEs can communicate with the base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the BS. In some instances, a UE can communicate with one or more other UEs via sidelinks. As will be described in more detail herein, a BS may be referred to as a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5G B-node, etc.

[0008] The multiple access technologies mentioned above have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the city, country, region, and even global levels. New Radio (NR) (also known as 5G) is an enhancement set to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation, using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on the downlink (DL) (CP-OFDM), and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL). However, with the continued growth in demand for mobile broadband access, there is a need for further improvements to LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ them.

[0009] In some aspects, it may be desirable for wireless nodes to communicate without communicating through a BS and / or core network. Cellular sidelink communication schemes provide communication between two or more wireless nodes using some wireless protocols of cellular networks (such as LTE and / or 5G NR). For example, cellular vehicle-to-vehicle (C-V2X) communication (including vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), and / or vehicle-to-cloud (V2C) communication) can allow vehicles to communicate with other vehicle and / or infrastructure nodes (such as traffic signals and signs) without communicating through a BS. To transmit packets using C-V2X, the data link layer of a wireless node can generate a header that includes a source identifier and a destination identifier. The destination identifier is associated with the destination or receiver of the packet. Typically, C-V2X packets are broadcast or multicast to multiple wireless nodes within the transmission range of the transmitting node. An example of C-V2X multicast transmission is the Basic Safety Message (BSM), which conveys location, heading, speed, safety alerts, and / or other information to other devices (e.g., the vehicle) within range of the transmitting node / vehicle. Other multicast transmissions may include Traffic Information Messages (TIM), Signal Phase and Timing (SPAT) messages, Cooperative Awareness Messages (CAM), Distributed Environmental Notification Messages (DENMs), In-Vehicle Information (IVI) messages, and / or any other multicast messages. It will be understood that this list of multicast transmissions is not exclusive, and other types of multicast transmissions / messages are contemplated in this disclosure.

[0010] A brief overview of some examples

[0011] The following outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This overview is not an exhaustive summary of all conceived features of this disclosure, and is neither intended to identify all key or decisive elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its sole purpose is to provide, in an overview form, some concepts of one or more aspects of this disclosure as a prelude to the more detailed description that follows.

[0012] This application describes a mechanism for performing unicast packet transmission in a C-V2X sidelink communication scenario. In one aspect, a transmitting wireless node can generate packets for transmission to a receiving wireless node, the packets including a destination identifier. This destination identifier can be generated based on a source identifier associated with the receiving node and a deterministic function. The deterministic function can be used such that the destination identifier indicates whether the packet is a unicast or multicast packet. The receiving C-V2X node monitors incoming packets including the destination identifier indicating whether the packet is a unicast packet and passes the packet to a higher layer of the node for processing.

[0013] According to one aspect of this disclosure, a method for performing wireless communication by a first wireless communication device includes: receiving a source identifier associated with a second wireless communication device; determining a destination identifier based on the source identifier associated with the second wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier; generating a packet including the destination identifier, wherein the destination identifier indicates a unicast packet; and transmitting the packet to the second wireless communication device.

[0014] According to another aspect of this disclosure, a method for performing wireless communication by a first wireless communication device includes: determining a destination identifier associated with the first wireless communication device based on a source identifier associated with the first wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier; receiving a packet from a second wireless communication device; and determining whether the packet is a unicast packet based on whether the packet includes the destination identifier. In some aspects, determining whether the packet is a unicast packet includes: determining whether the packet is a unicast packet intended for the first wireless communication device.

[0015] According to another aspect of this disclosure, a first wireless communication device includes: a transceiver configured to: receive a source identifier associated with a second wireless communication device; and a processor in communication with the processor, the transceiver configured to: determine a destination identifier based on the source identifier associated with the second wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier; and generate a packet including the destination identifier, wherein the destination identifier indicates a unicast packet, and wherein the transceiver is further configured to: transmit the packet to the second wireless communication device.

[0016] According to another aspect of this disclosure, a first wireless communication device includes: a processor configured to: determine a destination identifier associated with the first wireless communication device based on a source identifier associated with the first wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier; and a transceiver configured to: receive packets from a second wireless communication device, wherein the processor is further configured to: determine whether the packet is a unicast packet based on whether the packet includes the destination identifier.

[0017] According to another aspect of this disclosure, a non-transient computer-readable medium having program code recorded thereon for wireless communication by a first wireless communication device is disclosed. The program code includes: code for causing the first wireless communication device to receive a source identifier associated with a second wireless communication device; code for causing the first wireless communication device to determine a destination identifier based on the source identifier associated with the second wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier; code for causing the first wireless communication device to generate a packet including the destination identifier, wherein the destination identifier indicates a unicast packet; and code for causing the first wireless communication device to transmit the packet to the second wireless communication device.

[0018] According to another aspect of this disclosure, a non-transient computer-readable medium having program code recorded thereon for wireless communication by a first wireless communication device is disclosed. The program code includes: code for causing the first wireless communication device to determine a destination identifier associated with the first wireless communication device based on a source identifier and a deterministic function associated with the wireless communication device, wherein the destination identifier is different from the source identifier; code for causing the first wireless communication device to receive packets from a second wireless communication device; and code for causing the first wireless communication device to determine whether the packet is a unicast packet based on whether the packet includes the destination identifier.

[0019] According to another aspect of this disclosure, a first wireless communication device includes: means for receiving a source identifier associated with a second wireless communication device; means for determining a destination identifier based on the source identifier associated with the second wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier; means for generating a packet including the destination identifier, wherein the destination identifier indicates a unicast packet; and means for transmitting the packet to the second wireless communication device.

[0020] According to another aspect of this disclosure, a first wireless communication device includes: means for determining a destination identifier associated with the first wireless communication device based on a source identifier and a deterministic function, wherein the destination identifier is different from the source identifier; means for receiving packets from a second wireless communication device; and means for determining whether the packet is a unicast packet based on whether the packet includes the destination identifier.

[0021] Other aspects and features of the invention will become apparent to those skilled in the art after reading the following description of specific exemplary aspects of the invention in conjunction with the accompanying drawings. Although features of the invention may be discussed below with respect to certain aspects and drawings, all aspects of the invention may include one or more of the advantageous features discussed herein. In other words, while one or more aspects may be discussed having certain advantageous features, one or more such features may also be used in accordance with various aspects of the invention discussed herein. Similarly, although exemplary aspects may be discussed below as aspects of an apparatus, system, or method, it should be understood that such exemplary aspects can be implemented in various apparatuses, systems, and methods. Brief description of the attached diagram

[0023] Figure 1 The present disclosure explains some aspects of wireless communication networks.

[0024] Figure 2 This is a diagram illustrating the data link layer frame structure according to some aspects of this disclosure.

[0025] Figure 3 The present disclosure describes some aspects of cellular vehicle-to-everything (C-V2X) sidelink communication scenarios.

[0026] Figure 4 This is a signaling diagram illustrating a C-V2X sidelink communication scenario, including unicast and multicast packet transmissions, according to some aspects of this disclosure.

[0027] Figure 5 This is a signaling diagram illustrating a C-V2X sidelink communication scenario, including unicast and multicast packet transmissions, according to some aspects of this disclosure.

[0028] Figure 6 This is a diagram illustrating a method for generating a destination identifier using a deterministic function, according to some aspects of this disclosure.

[0029] Figure 7 This is a block diagram of an exemplary wireless node according to some aspects of this disclosure.

[0030] Figure 8 This is a flowchart of a C-V2X sidelink communication method according to some aspects of this disclosure.

[0031] Figure 9 This is a flowchart of a C-V2X sidelink communication method according to some aspects of this disclosure.

[0032] Detailed description

[0033] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0034] This disclosure generally relates to wireless communication systems (also known as wireless communication networks). Various technologies and apparatuses can be used in various aspects of wireless communication networks, such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, 5G or New Radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0035] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization called the 3rd Generation Partnership Project (3GPP), while cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between various telecommunications association groups that aims to define globally applicable third-generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure focuses on the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond, with particular attention to the development of sidelink communication mechanisms in C-V2X communication scenarios.

[0036] Various other aspects and features of this disclosure are further described below. It should be apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are merely representative and not limiting. Based on the teachings herein, those skilled in the art will appreciate that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice a method. Furthermore, such an apparatus or practice can be implemented using other structures, functionalities, or structures and functionalities that complement or differ from one or more aspects set forth herein. For example, a method can be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. Moreover, an aspect may include at least one element of the claims.

[0037] As explained above, cellular vehicle-to-vehicle (C-V2X) communication (including vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), and / or vehicle-to-cloud (V2C) communication) allows vehicles to communicate with other vehicles and / or infrastructure nodes (such as traffic signals and signs) without requiring communication via a browser-base (BS). To transmit packets using C-V2X, the data link layer (e.g., the Media Access Control (MAC) layer) of a radio node generates a header that includes a source identifier and a destination identifier. The source identifier indicates the address of the packet's source (e.g., the sending node). The destination identifier indicates the address of the packet's intended recipient(s). Typically, C-V2X packets are broadcast or multicast to multiple radio nodes within the transmission range of the sending node. Other radio nodes within the sending node's range receive the multicast packets and determine whether to pass the packet to a higher layer (e.g., the network layer) for further processing.

[0038] In some instances, unicast transmissions to a single radio node, rather than multicast transmissions, may be expected in C-V2X communication scenarios. For example, a radio node might be expected to send and / or receive unicast messages for toll collection to / from a single vehicle, rather than all vehicles within range. In some sidelink communications, the version field in the packet header can be used to indicate whether the packet has a unicast destination (a single intended receiver) or a multicast destination (multiple intended receivers / indiscriminately). However, in some C-V2X communication scenarios, using the version field to indicate whether a packet is intended for unicast transmission may be impossible or impractical. Therefore, in some C-V2X communication scenarios, other nodes may be unable to receive unicast transmissions or distinguish between unicast and multicast transmissions.

[0039] This disclosure describes methods, mechanisms, and algorithms for unicast and multicast transmission in C-V2X communication scenarios. Aspects of this disclosure include generating a destination identifier that indicates whether a packet has a unicast or multicast destination. In one aspect, a radio node is configured to generate a destination identifier based on a source identifier of the intended receiving node and a deterministic function (such as a bitmasking operation, a static mapping operation, or a hash operation). The resulting destination identifier may have a modified structure, wherein a first part indicates whether the packet has a unicast or multicast destination, and a second part indicates the intended receiver(s). In another aspect, the deterministic function may divide several possible values ​​of the destination identifier into unicast and multicast groups. In yet another aspect of this disclosure, a radio node can indicate whether a packet has a unicast or multicast destination by modifying the structure of the source identifier (as a replacement or appendage to the destination identifier).

[0040] Various aspects of this disclosure advantageously provide unicast and multicast packet transmission with minimal changes to higher layers of the packet header structure and protocol stack. These aspects can facilitate more efficient use of network resources and / or reduce network congestion by enabling unicast and multicast transmission. Furthermore, devices can discard or ignore any unicast packets intended for another device, thereby saving device processing time and resources.

[0041] Figure 1 A wireless communication network 100 according to some aspects of this disclosure is described. Network 100 may be a 5G network, an LTE network, or any suitable cellular network and / or a combination thereof. Network 100 includes several base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. BS 105 may be a station communicating with UE 115 and may also be referred to as an evolved B-node (eNB), a next-generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cellular" may refer to that specific geographic coverage area of ​​BS 105 and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0042] BS 105 can provide communication coverage for macrocells or small cells (such as picocells or femtocells), and / or other types of cells. Macrocells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as picocells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femtocells) also typically cover a relatively small geographic area (e.g., a residential area) and, in addition to unrestricted access, allow restricted access by UEs associated with that femtocell (e.g., UEs in a closed subscriber group (CSG), UEs of users in that residence, etc.). A BS used for macrocells may be referred to as a macro BS. A BS used for small cells may be referred to as a small cell BS, pico BS, femtocell BS, or home BS. Figure 1 In the examples shown, BS 105d and 105e can be conventional macro BSs, while BS 105a-105c can be macro BSs with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO enabled. BS 105a-105c can leverage its higher-dimensional MIMO capabilities to increase coverage and capacity using 3D beamforming in both elevation and azimuth beamforming. BS 105f can be a small cell BS, which can be a home node or a portable access point. BS 105 can support one or more (e.g., two, three, four, etc.) cells.

[0043] Network 100 can support synchronous or asynchronous operation. For synchronous operation, each BS can have similar frame timing, and transmissions from different BSs can be roughly aligned in time. For asynchronous operation, each BS can have different frame timing, and transmissions from different BSs may not be aligned in time.

[0044] Each UE 115 is distributed throughout the wireless network 100, and each UE 115 may be stationary or mobile. UE 115 may also be referred to as a terminal, mobile station, subscriber unit, station, etc. UE 115 may be a cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, tablet computer, laptop computer, cordless phone, wireless local loop (WLL) station, etc. In one aspect, UE 115 may be a device including a Universal Integrated Circuit Card (UICC). In another aspect, UE may be a device without a UICC. In some aspects, UE 115 without a UICC may also be referred to as an IoT device or an Internet of Things (IoE) device. UE 115a-115d are examples of mobile smartphone-type devices accessing network 100. UE 115 may also be a machine specifically configured for connected communications (including Machine Type Communication (MTC), Enhanced MTC (eMTC), Narrowband IoT (NB-IoT), etc.). UE 115e-115h are examples of various machines configured for communication within access network 100. UE 115i-115k are examples of vehicles equipped with wireless communication devices configured for sidelink communication and access network 100. UE 115 can communicate with other UE 115s, wireless nodes, or any type of BS (whether macro BS, small cell, etc.). Figure 1 In this context, the lightning bolt (e.g., a communication link) indicates radio transmissions between UE 115 and serving BS 105, desired transmissions between BSs 105, backhaul transmissions between BSs, or sidelink transmissions between UE 115, where serving BS 105 is the BS designated to serve UE 115 on the downlink (DL) and / or uplink (UL).

[0045] In operation, BS 105a-105c can use 3D beamforming and coordinated spatial technologies (such as Coordinated Multipoint (CoMP) or multi-connectivity) to serve UE 115a and 115b. Macro BS 105d can perform backhaul communication with BS 105a-105c and small cell BS 105f. Macro BS 105d can also deliver multicast services subscribed to and received by UE 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information (such as weather emergencies or alerts, such as Amber Alerts or Grey Alerts).

[0046] BS 105 can also communicate with the core network. The core network provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some BS 105s (e.g., examples of gNBs or Access Node Controllers (ANCs)) can interface with the core network via backhaul links (e.g., NG-C, NG-U, etc.) and can perform radio configuration and scheduling for communication with UE 115. In various examples, BS 105s can communicate with each other directly or indirectly (e.g., via the core network) on backhaul links (e.g., X1, X2, etc.), which can be wired or wireless communication links.

[0047] Network 100 can also support mission-critical communication with highly reliable and redundant links for mission-critical devices such as UE 115e, which could be a drone. Redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BS 105f. Other machine-type devices (such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device)) can communicate directly with BSs (such as small cell BS 105f and macro BS 105e) via network 100, or be in a multi-step configuration by communicating with another user equipment that relays its information to the network (e.g., UE 115f relays temperature measurement information to smart meter UE 115g, which is then reported to the network via small cell BS 105f). Network 100 can also provide additional network efficiency through dynamic, low-latency TDD / FDD communication (such as V2V, V2X, V2P and / or C-V2X communication between UEs 115i, 115j or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communication between UEs 115i, 115j or 115k and one or more other wireless nodes, including through the use of sidelink communication according to this disclosure). Reference will be made below. Figure 3-6 Further details are provided regarding sidelink communication applicable to V2V, V2X, V2P, C-V2X, and / or V2I communications.

[0048] In some implementations, network 100 utilizes OFDM-based waveforms for communication. OFDM-based systems can divide the system BW into multiple (K) orthogonal subcarriers, which are often referred to as subcarriers, frequency modulation, frequency slots, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the time interval (TTI) can be scalable.

[0049] In some respects, BS 105 (or UE 115 or other radio nodes in a sidelink communication scenario) may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions (or sidelink transmissions). DL can refer to the transmission direction from BS 105 to UE 115, while UL can refer to the transmission direction from UE 115 to BS 105. Communication may take the form of radio frames. Radio frames may be divided into multiple subframes or time slots, for example, about 10. Each time slot may be further divided into sub-time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe may include a UL subframe in the UL band and a DL subframe in the DL band. In TDD mode, UL and DL transmissions occur using the same frequency band but in different time periods. For example, a subset of subframes in a radio frame (e.g., DL subframes) can be used for DL ​​transmission, and another subset of subframes in a radio frame (e.g., UL subframes) can be used for UL transmission.

[0050] DL subframes and UL subframes can be further divided into several regions. For example, each DL or UL subframe may have a predefined region for the transmission of reference signals, control information, and data. Reference signals are predetermined signals that facilitate communication between BS 105 and UE 115. For example, reference signals may have a specific pilot pattern or structure, wherein the pilot frequencies may span the operating BW or frequency band, and each pilot frequency is positioned at a predefined time and predefined frequency. For example, BS 105 may transmit a cell-specific reference signal (CRS) and / or channel state information-reference signal (CSI-RS) to enable UE 115 to estimate the DL channel. Similarly, UE 115 may transmit a probe reference signal (SRS) to enable BS 105 (or another UE or radio node) to estimate the UL channel (or sidelink channel). Control information may include resource allocation and protocol control. Data may include protocol data and / or operational data. In some aspects, BS 105 and UE 115 may communicate using self-contained subframes. A self-contained subframe may include portions for DL ​​communication and portions for UL communication. The self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL ​​communication than the duration for UL communication. A UL-centric subframe may include a longer duration for UL communication than the duration for DL ​​communication.

[0051] In some respects, network 100 may be an NR network deployed on licensed spectrum. BS 105 (or UE 115 in sidelink communication) may transmit synchronization signals (e.g., including primary synchronization signal (PSS) and secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS 105 may broadcast system information associated with network 100 (e.g., including primary information block (MIB), residual system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, BS 105 may broadcast PSS, SSS, and / or MIB in the form of synchronization signal block (SSB) on the physical broadcast channel (PBCH) and may broadcast RMSI and / or OSI on the physical downlink shared channel (PDSCH).

[0052] In some respects, UE 115 attempting to access network 100 can perform an initial cell search by detecting a PSS from BS 105 or from another radio node in the network (e.g., another UE 115 in sidelink communication). The PSS enables time-period timing synchronization and indicates a physical layer identity value. UE 115 can subsequently receive an SSS. The SSS enables radio frame synchronization and provides a cell identity value, which can be combined with a physical layer identity value to identify the cell. The PSS and SSS can be located in the center portion of a carrier or at any suitable frequency within the carrier.

[0053] After receiving the PSS and SSS, UE 115 can receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, UE 115 can receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to the Random Access Channel (RACH) procedure, paging, control resource set (CORESET) for monitoring the Physical Downlink Control Channel (PDCCH), Physical UL Control Channel (PUCCH), Physical UL Shared Channel (PUSCH), power control, and SRS.

[0054] After obtaining the MIB, RMSI, and / or OSI, UE 115 can execute a random access procedure to establish a connection with BS 105. In some examples, the random access procedure can be a four-step random access procedure. For example, UE 115 can transmit a random access preamble, and BS 105 can respond with a random access response. The random access response (RAR) may include the detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or backoff indicator. Upon receiving the random access response, UE 115 can transmit a connection request to BS 105, and BS 105 can respond with a connection response. The connection response may indicate a contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG 1), message 2 (MSG 2), message 3 (MSG 3), and message 4 (MSG 4), respectively. In some examples, the random access procedure can be a two-step random access procedure, where UE 115 can transmit the random access preamble and connection request in a single transmission, and BS 105 can respond by transmitting the random access response and connection response in a single transmission.

[0055] After the connection is established, UE 115 and BS 105 can enter the normal operation phase, during which operational data can be exchanged. For example, BS 105 can schedule UE 115 for UL and / or DL ​​communication. BS 105 can transmit UL and / or DL ​​scheduling permission to UE 115 via PDCCH. The scheduling permission can be transmitted in the form of DL control information (DCI). BS 105 can transmit DL communication signals (e.g., carrying data) to UE 115 via PDSCH based on the DL scheduling permission. UE 115 can transmit UL communication signals to BS 105 via PUSCH and / or PUCCH based on the UL scheduling permission.

[0056] In some respects, BS 105 can use HARQ technology to communicate with UE 115 to improve communication reliability, such as to provide URLLC services. BS 105 can schedule UE 115 for PDSCH communication by transmitting DL permission in the PDCCH. BS 105 can transmit DL data packets to UE 115 according to the scheduling in the PDSCH. DL data packets can be transmitted in transport blocks (TBs). If UE 115 successfully receives DL data packets, UE 115 can transmit a HARQ ACK to BS 105. Conversely, if UE 115 fails to receive DL transmission, UE 115 can transmit a HARQ NACK to BS 105. Once a HARQ NACK is received from UE 115, BS 105 retransmits the DL data packets to UE 115. The retransmission may include the same encoded version of the DL data as the initial transmission. Alternatively, the retransmission may include a different encoded version of the DL data than the initial transmission. UE 115 can apply soft combining to combine encoded data received from the initial transmission and retransmissions for decoding. BS 105 and UE 115 can also use a mechanism substantially similar to DL HARQ to apply HARQ to UL communications.

[0057] In some aspects, network 100 may operate on a system BW or a component carrier (CC) BW. Network 100 may divide the system BW into multiple BWPs (e.g., multiple parts). BS 105 may dynamically assign UE 115 to operate on a particular BWP (e.g., a part of the system BW). The assigned BWP may be referred to as the active BWP. UE 115 may monitor the active BWP to look for signaling information from BS 105. BS 105 may schedule UE 115 to perform UL or DL ​​communication in the active BWP. In some aspects, BS 105 may assign a pair of BWPs within a CC to UE 115 for UL and DL communication. For example, the BWP pair may include one BWP for UL communication and one BWP for DL ​​communication.

[0058] Although most of the above description of network 100 is within the context of communication between UE 115 and BS 105, it will be understood that in sidelink communication scenarios (such as C-V2X communication), the aforementioned mechanisms, elements, structures, and protocols can be performed between UE 115 or the radio node. For example, in some aspects, radio frame structures, channels, signaling, scheduling procedures, and / or connectivity technologies (e.g., HARQ) can be performed between UE 115 / the radio node, rather than between BS 105 and UE 115.

[0059] Sidelink communication refers to communication between user equipment (e.g., UE 115i, 115j, 115k) without tunneling through BS 105 and / or the core network. Sidelink communication can be transmitted on the Physical Sidelink Control Channel (PSCCH) and the Physical Sidelink Shared Channel (PSSCH). The PSCCH and PSSCH are analogous to the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) in downlink (DL) communication between BS 105 and UE 115. For example, the PSCCH may carry Sidelink Control Information (SCI) and the PSSCH may carry sidelink data (e.g., user data). Each PSCCH is associated with a corresponding PSSCH, where the SCI in the PSCCH may carry reservation and / or scheduling information for sidelink data transmission in the associated PSSCH. Use cases for sidelink communication may include V2X, enhanced mobile broadband (eMBB), industrial IoT (IIoT), and / or NR-Lightweight.

[0060] Figure 2 This is a diagram illustrating the structure of the grouping or frame 200 according to some aspects of this disclosure. It has... Figure 2 The structure of the packets described herein can be transmitted and / or received by a wireless node in a sidelink communication scenario (such as a C-V2X communication scenario). The structure of packet 200 can be set and / or used by the data link layer or sublayer (such as the Media Access Control (MAC) sublayer) of the wireless node. In the described embodiment, packet 200 includes a MAC Protocol Data Unit (PDU) 205. PDU 205 includes a MAC header 210, a MAC Service Data Unit (SDU), and optional padding portions 230. In some aspects, the MAC header 210 is generated or set by the MAC layer and includes information associated with the source of packet 200, the destination or address of packet 200, and the version or type of the MAC header 210. In this regard, the MAC header 210 includes a V field (header version), an SRC (source) field 214, and a DST (destination) field 216. However, it will be understood that... Figure 2 The fields described herein are exemplary, and in addition to those concerning... Figure 2 In addition to the fields that are specifically explained and described, the MAC header may also include other fields.

[0061] The V field corresponds to the MAC PDU format version number and indicates the version of the SL-SCH subheader being used. In some aspects, the V field 212 may include four bits. In some aspects, the value set for the V field 212 may indicate the size of the DST field 216 (e.g., in bits). For example, in some aspects, a first value of the V field 212 may indicate that the DST field 216 has 16 bits, and a different second value of the V field 212 may indicate that the DST field 216 has 24 bits. However, other sizes / numbers of bits for the V field 212 and / or the DST field 216 are also contemplated in this disclosure.

[0062] SRC field 214 carries a source identifier, which indicates the identity of the packet's source. In some aspects, SRC field 214 can be randomly assigned. In one exemplary aspect, the source identifier comprises 24 bits. In another aspect, SRC field 214 can be defined as a source 2ID field, and the source identifier can be set to the ProSe UE ID. In some aspects, random assignment of the source identifier can provide some privacy (e.g., anonymity) and consistency in sidelink communication scenarios, minimizing the chance of any two or more nodes having the same source identifier value. However, the source identifier can be non-randomly assigned by the radio node based on an address specifically assigned to the node, for example, by an appropriate administrative authority.

[0063] The DST field 216 carries a destination identifier that indicates the destination of the packet. In some aspects, the destination of the packet can be a multicast destination or a unicast destination. For example, a program or application can assign a multicast destination identifier to the DST field 216, which can allow any one or more nodes within the multicast transmission range that are configured by the program or application to receive (e.g., monitor) the multicast destination identifier to receive and decrypt packets. In another example, as indicated by the destination identifier, the packet can be configured for unicast transmission to a single node. In some sidelink communication scenarios, unicast transmission may involve setting the destination identifier value to the source identifier of the desired receiver. Furthermore, in some aspects, the version identifier of the V field 212 may not allow differentiation between multicast and unicast packet transmissions for a given size (e.g., 24 bits) of the destination identifier. However, in some aspects, it may be advantageous to indicate whether a packet is associated with a unicast or multicast transmission so that unicast transmission can occur in sidelink communication scenarios, especially when the unicast transmission type cannot be indicated in other fields of the MAC header 210 (e.g., the V field 212). As further explained below, this disclosure provides methods, algorithms, and mechanisms for indicating unicast destinations based on destination identifiers generated using one or more deterministic functions.

[0064] In some respects, the destination identifier carried by the DST field 216 comprises 24 bits. However, other numbers of bits / values, whether larger or smaller, are also conceivable. In some respects, the DST field 216 can be defined as a destination layer 2 ID field, and the source identifier can be set to a ProSe UE ID or a ProSe layer 2 group ID.

[0065] MAC Service Data Unit (MAC SDU) 220 can carry packets or frames from higher layers (such as the network layer). Therefore, when a node receives MAC PDU 205, the MAC layer can receive the packet based on the information provided in the MAC header 210 and forward MAC SDU 220 to a higher layer (e.g., the Radio Link Control (RLC) layer) for further processing.

[0066] In some respects, MAC PDU 205 is incorporated into lower-level packets (such as physical layer frames). For example, MAC PDU 205 can be encapsulated into Physical Service Data Units (PSDUs) for transmission at the physical layer of a network or communication scheme (such as LTE V2X). Furthermore, it will be understood that MAC PDU 205, which can also be referred to as a frame, can carry or include packets from higher layers of the protocol stack, such as Radio Link Control (RLC) packets.

[0067] Figure 3 This is an illustration of a C-V2X communication scenario 300 according to various aspects of this disclosure. In an exemplary aspect, C-V2X communication scenario 300 is an LTE V2X communication scenario. As explained, scenario 300 includes multiple nodes 315 or wireless communication devices performing various types of sidelink communication. For example, communication scenario 300 may include unicast and / or multicast communication, including groupcast and / or broadcast communication. Each communication may include the transmission of frames or packets 320 and headers 322 associated with the packets 320. In an exemplary aspect, packets 320 are MAC SDUs, such as MAC SDU 220, and the header is a MAC header, such as... Figure 2 The MAC header 210 is explained in the document. However, other types / layers of frames, packets, and / or PDUs are also envisioned.

[0068] In one aspect, the first node 315a performs multicast transmission, wherein the first packet 320a associated with the first header 322a is multicast to multiple vehicle nodes, including 315b, 315c, 315d, and traffic light node 315e. Specifically, the first node 315a broadcasts the first packet 320a to all other nodes 315b, 315c, 315d, and 315e within a range 350 of the first node 315a. In some embodiments, the header 322a associated with the first packet 320a includes a source identifier associated with the first node 315a and a destination identifier or broadcast destination identifier (e.g., 0xFFFFFF) associated with nodes in a specific group (e.g., multicast). The destination identifier in the packet header 322a may be provided by an application running on the first node 315a and / or other nodes in the group. For example, an application can configure nodes 315b, 315c, 315d, and 315e to monitor incoming packets or frames with destination identifiers set by an application running on the first node 315a. Therefore, the destination identifier may not indicate a unique or individual destination value, but rather a group-based destination value. However, it will be understood that in some instances, multicast packets may be received by only one other node, or not by any node at all. For example, in some instances, there may only be one other node configured to monitor packets with a specific multicast destination identifier within the range 350 of the first node 315a. Therefore, it will be understood that the type of transmission (e.g., unicast or multicast) does not necessarily indicate the number of receivers, but rather the range of the transmission and the potential receivers within range 350.

[0069] Still referencing Figure 3Vehicle node 315b performs a unicast transmission of the second packet 320b associated with the second header 322b to vehicle node 315d. The second header 322b includes a source identifier associated with vehicle node 315b and a destination identifier associated with the receiving vehicle node 315d. In some aspects, header 322b may indicate that the second packet 320b is a unicast transmission type and identify the unicast receiver. In an exemplary aspect, the destination identifier may indicate that the second packet 320b has a unicast destination. In one aspect, the receiving vehicle node 315d is configured to monitor packets with a destination identifier that indicates a unicast destination corresponding to its own source identifier. For example, as further explained below, vehicle node 315d may determine its own unicast destination identifier based on its own source identifier and a deterministic function, and monitor packets with that unicast destination identifier. If node 315d determines that packet 320b includes the unicast destination identifier, then node 315d forwards the packet to higher layers in the protocol stack for processing. If node 315d determines that packet 320b does not contain a unicast destination identifier, nor any other destination identifier that node 315d is monitoring (e.g., an application-assigned multicast destination identifier), then node 315d discards packet 320b.

[0070] On the other hand, traffic light node 315e performs a unicast transmission of the third frame 320c associated with the third header 322c to the first node 315a. In some aspects, traffic light node 315e may determine the destination identifier of the unicast packet based on the received broadcast packet 320a. Since the broadcast packet 320a includes the source identifier of the first node 315a, traffic light node 315e can use the source identifier of the first node 315a and a deterministic function to determine the destination identifier of the first node 315a to indicate the unicast transmission type, as further explained below.

[0071] Figure 4 This is a signaling diagram illustrating a method 400 for unicast sidelink communication in a C-V2X communication scenario between a first node 415a and a second node 415b, according to some aspects of this disclosure. Nodes 415a and 415b can be... Figure 1 UE 115 in network 100 (e.g., 115i, 115j, 115k), or Figure 3Any wireless node 315 in the C-V2X communication scenario 300. The steps of method 400 can be performed by the computing devices (e.g., processors, processing circuitry, and / or other suitable components) of nodes 415a, 415b. The steps of method 400 can be performed at the data link layer or sublayers (such as the MAC layer) of wireless nodes 415a, 415b. However, other layers / sublayers, including the physical layer, may also be involved in the steps of method 400. As explained, method 400 includes several enumerated steps, but aspects of method 400 may include additional steps before, after, and between these enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0072] In box 402, the first node 415a sets the source identifier to a random value R1. In some aspects, setting the source identifier may include setting the source layer 2 ID value to a random value R1. The source identifier may be carried in the SRC field of a packet header (such as a MAC PDU header). In one aspect, the source identifier comprises a 24-bit value. However, other sizes of source identifiers are also contemplated, including 16 bits, 20 bits, 36 bits, 48 ​​bits, or any other suitable number of bits, whether larger or smaller.

[0073] In box 404, the first node 415a determines the destination identifier U1 associated with the first node 415a based on the source identifier R1 and a deterministic function. The destination identifier U1 may be a destination identifier intended for unicast transmissions aimed at the first node 415a. In one aspect, the deterministic function includes a bitmasking operation, and determining the destination identifier U1 includes applying a bitmask to the source identifier R1 set in box 402. References will follow. Figure 6 Further explanation of the use of bitmasking operations to determine the destination identifier U1. In some aspects, the number of distinct values ​​that can be represented by U1 is less than the number of distinct values ​​that can be represented by the source identifier determined in box 402. In other aspects, the deterministic function may include static mapping operations and / or hash operations. For example, a static mapping operation may involve a many-to-one correspondence between the source identifier and the destination identifier associated with the unicast transmission type. A static mapping operation may include using a lookup table to determine the destination identifier based on the source identifier of the receiving node. A hash operation may involve using a hash function to map a first value to another value of a fixed size. In some aspects, configuration information regarding the deterministic function used in box 404 may include bitmasking configuration, a lookup table for static mapping operations, and / or a hash function, and may be defined in a specification or standard, decoded or pre-configured in the device prior to deployment, and / or communicated to the device via various means.

[0074] In box 406, first node 415a monitors packets having the destination identifier U1 determined in box 404. By determining the unicast destination identifier U1 for itself, first node 415a can identify unicast packets intended for first node 415a.

[0075] In box 408, the second node 415b sets its source identifier to a random value R2, similar to box 402. In some aspects, setting the source identifier R2 may include setting the source layer 2 ID value to a random value. The source identifier may be carried in the SRC field of a packet header (such as a MAC PDU header). In one aspect, the source identifier comprises a 24-bit value. However, other sizes of source identifiers are also contemplated, including 16 bits, 20 bits, 36 bits, 48 ​​bits, or any other suitable number of bits, whether larger or smaller.

[0076] In block 410, the second node 415b determines the destination identifier U2 associated with the first node 415a for unicast transmission based on the source identifier R2 and a deterministic function. The second node 415b can determine the destination identifier U2 in a similar manner to how the first node 415a determines the destination identifier U1. For example, in one aspect, the deterministic function includes a bitmasking operation, and determining the destination identifier U2 includes applying a bitmask to the source identifier R2 set in block 408. Reference will be made below. Figure 6 Further explanation of using bitmasking operations to determine the destination identifier U2. In some respects, the number of distinct values ​​that can be represented by U2 is less than the number of distinct values ​​that can be represented by the source identifier determined in box 408. In other respects, the deterministic function may include static mapping operations and / or hash operations.

[0077] In box 412, the second node 415b monitors packets having the destination identifier U2 determined in box 410. By determining the unicast destination identifier U2 for unicast packets to be received by the second node 415b, the second node 415b can identify unicast packets intended for the second node 415b.

[0078] In box 414, the first node 415a determines a multicast destination identifier M1 for multicast packet transmission. In some aspects, multicast packet transmission can be broadcast transmission and / or ensemble transmission. In one aspect, the multicast destination identifier M1 is determined or set based on an application running on the first node 415a. For example, the application can specify a packet (which may include a basic security message) that will, for example, be broadcast to all nodes within the scope of the first node 415a, and set the destination identifier M1 accordingly.

[0079] In action 416, the first node broadcasts a packet using a multicast destination identifier M1 and a source identifier R1. Therefore, the broadcast packet can be received by any node within the range of the first node 415a that is configured to receive / monitor packets with the multicast destination identifier M1. In an exemplary aspect, packet broadcasting is performed by the physical layer of a sidelink communication scheme (such as a C-V2X scheme). Specifically, packet broadcasting can be performed by the physical layer of an LTE-V2X communication scheme.

[0080] In box 418, the second node 415b receives a broadcast packet including the source identifier R1 from the first node 415a. In some aspects, box 418 may include determining whether the second node 415b has been configured to monitor the destination identifier M1. If the second node 415b has been configured to monitor the destination identifier M1, it may be configured to pass the packet up to a higher layer in the protocol stack (e.g., the network layer) for further processing and discard packets with a destination identifier that the second node 415b has not yet been configured to monitor.

[0081] If the second node 415b has a packet to unicast to the first node 415a, then in box 420, the second node 415b sets the destination identifier of that packet to U1. The destination identifier U1 is set based on the source identifier R1 received from the first node 415a in box 418 and a deterministic function. As explained above, the deterministic function may include bitmasking operations, static mapping operations, and / or hashing operations. The deterministic function may modify the source identifier value R1 such that the destination identifier U1 obtained by the deterministic function indicates whether the packet is unicast or multicast.

[0082] In action 422, the second node 415b unicasts a packet with destination identifier U1 and source identifier R2 to the first node 415a. In an exemplary aspect, packet transmission is performed by the physical layer of a sidelink communication scheme (such as a C-V2X scheme). Specifically, packet transmission may be performed by the physical layer of an LTE-V2X communication scheme.

[0083] In block 424, first node 415a receives a unicast packet with a destination identifier U1 and a source identifier R2. First node 415a, configured to monitor U1 in block 406, identifies the packet as a unicast packet intended for first node 415a based on the destination identifier U1. Therefore, first node 415a can allow the packet to be passed to a higher level for further processing. Conversely, if the packet does not include the destination identifier U1, and also does not include any multicast destination identifiers that first node 415a is configured to monitor, then first node 415a will discard the packet.

[0084] In block 426, if the first node 415a has a packet for unicast transmission to the second node 415b, then the first node 415a sets the unicast destination identifier of the packet to U2 based on the source identifier R2 of the second node 415b received in block 424 and a deterministic function. As explained above, the deterministic function may include bitmasking operations, static mapping operations, and / or hashing operations. The deterministic function may modify the source identifier value R2 such that the destination identifier U2 obtained by the deterministic function indicates whether the packet is unicast or multicast.

[0085] In action 428, the first node 415a transmits a unicast packet to the second node 415b using the unicast destination identifier U2 and source identifier R1. In an exemplary aspect, the transmission of the unicast packet is performed by the physical layer of a sidelink communication scheme (such as a C-V2X scheme). Specifically, the packet transmission may be performed by the physical layer of an LTE-V2X communication scheme.

[0086] Therefore, nodes 415a and 415b can utilize the resources of the destination identifier (e.g., bits) to indicate not only the address or destination of a packet, but also whether the packet is a unicast or multicast packet. Thus, nodes 415a and 415b can determine whether a given packet is a unicast or multicast packet, and if it is a unicast packet, they can further determine whether the receiving node is the intended destination.

[0087] Figure 5 This is a signaling diagram illustrating the mechanism for unicast sidelink communication in a C-V2X communication scenario between a first node 415a, a second node 415b, and a third node 415c, according to some aspects of this disclosure. Nodes 415a and 415b can be as described above regarding... Figure 4 The same nodes 415a and 415b are described. Nodes 415a, 415b, and 415c can be... Figure 1 Any UE 115 (e.g., 115i, 115j, 115k) or in network 100 Figure 3Any wireless node 315 in the C-V2X communication scenario 300. The steps of method 500 can be performed by computing devices (e.g., processors, processing circuitry, and / or other suitable components) of nodes 415a, 415b, and 415c. The steps of method 500 can be performed at the data link layer or sublayers (such as the MAC layer) of the wireless nodes 415a, 415b, and 415c. However, other layers / sublayers, including the physical layer, may also be involved in the steps of method 500. As explained, method 500 includes several enumerated steps, but aspects of method 500 may include additional steps before, after, and between these enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order than shown.

[0088] Method 500 may include steps similar to or identical to those of method 400. In some aspects, the steps of method 500 illustrate unicast transmission from a first node 415a to multiple nodes (such as nodes 415b and 415c). Furthermore, the steps of method 500 can illustrate the use of broadcast and unicast transmissions in a C-V2X communication scenario between different nodes 415. Method 500 further illustrates packet reception and processing performed by the receiving node to determine whether to process or discard received packets.

[0089] In box 502, the first node 415a determines a destination identifier (M1) for multicast transmission. In some aspects, multicast transmission can be broadcast transmission and / or ensemble transmission. In one aspect, the multicast destination identifier M1 is determined or set based on an application running on the first node 415a. For example, the application can specify that packets (which may include basic security messages) will be broadcast to all nodes within the scope of the first node 415a and set the destination identifier M1 accordingly.

[0090] In action 504, the first node 415a broadcasts the packets received by the second node 415b and the third node 415c.

[0091] In block 506, the first node 415a determines the unicast destination identifier U1 based on the source identifier of the first node 415a (e.g., the source identifier R1 set in block 402 of method 400) and a deterministic function. In one aspect, the deterministic function includes a bitmasking operation, and determining the destination identifier U1 includes applying a bitmask to the source identifier. Reference will be made below. Figure 6 Further explanation of using bitmasking operations to determine the destination identifier U1: In some respects, the number of distinct values ​​that can be represented by U1 is less than the number of distinct values ​​that can be represented by the source identifier. In other respects, the deterministic function may include static mapping operations and / or hash operations.

[0092] In action 508, the second node 415b broadcasts a packet received by the first node 415a and the third node 415c. This packet includes a source identifier R2 associated with the second node 415b. As explained above, the source identifier R2 may be randomly generated / assigned by the second node 415b. In some aspects, the source identifier may include a 24-bit value. However, it will be understood that, without departing from the scope of this disclosure, the source identifier may include other sizes, including 16 bits, 20 bits, 32 bits, 48 ​​bits, or any other suitable value, whether larger or smaller. The packet also includes a multicast destination identifier to enable multiple or all nodes within the range of the second node 415b to be configured to receive the packet.

[0093] In action 510, the third node 415c broadcasts a packet received by the first node 415a and the second node 415b. This packet includes a source identifier R3 associated with the third node 415c. As explained above, the source identifier R3 may be randomly generated / assigned by the third node 415c. In some aspects, the source identifier may include a 24-bit value. However, it will be understood that, without departing from the scope of this disclosure, the source identifier may include other sizes, including 16 bits, 20 bits, 32 bits, 48 ​​bits, or any other suitable value, whether larger or smaller. The packet also includes a multicast destination identifier to enable multiple or all nodes within the range of the third node 415c to be configured to receive the packet.

[0094] In block 512, if the first node 415a has a packet for unicast transmission to the second node 415b, then the first node 415a determines the unicast destination identifier U2 based on the source identifier R2 and a deterministic function. The source identifier R2 is transmitted to the first node 415a in action 508 and received by the first node 415b.

[0095] In block 514, if the first node 415a has packets for unicast transmission to the third node 415c, then the first node 415a determines the unicast destination identifier U3 based on the source identifier R3 and a deterministic function. The source identifier R3 is transmitted to and received by the first node 415a in action 510.

[0096] In action 516, the first node 415a transmits a unicast packet with the destination identifier U2 determined in box 512 to the second node 415b.

[0097] In box 518, the second node 415b receives and processes unicast packets in response to the destination identifier U2. In this regard, the second node 415b can be configured to monitor incoming packets with the destination identifier U2. If the destination identifier of a received packet is equal to U2, the second node 415b passes the packet to higher layers of the protocol stack (e.g., the RLC layer) for further processing. If the destination identifier of a received packet is not equal to U2, and is not equal to any other unicast or multicast destination identifier that the second node 415b is monitoring, the second node 415b may discard the received packet.

[0098] In action 520, the first node 415a transmits a unicast packet with the destination identifier U3 determined in box 514 to the third node 415c.

[0099] In box 522, the third node 415c receives and processes unicast packets in response to the destination identifier U3. In this regard, the third node 415c can be configured to monitor incoming packets with the destination identifier U3. If the destination identifier of a received packet is equal to U3, the third node 415c passes the packet to higher layers of the protocol stack for further processing. If the destination identifier of a received packet is not equal to U3, and is not equal to any other destination identifier that the third node 415c is monitoring, the third node 415c can discard the received packet. For example, if the third node 415c receives a unicast packet with the unicast destination identifier U2 instead of U3, the third node 415c discards the unicast packet.

[0100] Figure 6 This is a diagram illustrating a method 600 for generating a destination identifier based on a source identifier and a deterministic function, according to some aspects of this disclosure. The steps of method 600 can be performed by a wireless node (such as...) Figure 1 One of the UEs 115 shown (e.g., 115i, 115j, 115k), or Figure 3-5 The steps of method 600 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable component) of one of the nodes 315 and 415 shown. The steps of method 600 may be performed at the data link layer or sublayer (such as the MAC layer) of the wireless node. As explained, method 600 includes several enumeration steps, but aspects of method 600 may include additional steps before, after, and between these enumeration steps.

[0101] A wireless node (e.g., node B) can receive packets from another node (e.g., node A) that include a header (such as a MACPDU header 610, which includes a V field 612, an SRC field 614, and a DST field 616). The SRC field 614 carries a source identifier 618, which has multiple bits of a defined value. As explained above, the V field 612 may carry a version number identifier indicating one or more aspects of the packet (such as the size of the DST field 616). In an exemplary aspect, both the SRC field 614 and the source identifier 618 are 24-bit values. In some aspects, the source identifier 618 may be randomly assigned. In other aspects, the source identifier 618 may be non-randomly assigned based on one or more system parameters.

[0102] Bitmask 620 can be used as a deterministic function to generate destination identifier 638 based on source identifier 618 carried by SRC field 614. In the illustrated embodiment, the bitmask includes the most significant bit (MSB) with a value of zero, and the remaining bits have a value of 1. In some aspects, bitmask 620 can be expressed in hexadecimal notation as 0x7FFFFF. As explained below, the zero value of the MSB can be used to indicate the unicast destination in the destination identifier, while the remaining bits of bitmask 620 leave the corresponding bits of source identifier 618 unchanged. However, these particular configurations are not limiting and can be modified in various ways without departing from the scope of this disclosure.

[0103] The destination identifier 638 is determined by applying bitmask 620 to the source identifier 618. In one aspect, a logical AND operation is used to apply bitmask 620. Therefore, as... Figure 6 As explained, the MSB of destination identifier 638 differs from that of source identifier 618, while the remaining bits of destination identifier 638 match the corresponding bits of source identifier 618. It will be understood that allocating bits to destination identifier 638 to indicate whether a packet is a unicast or multicast packet can increase the chance of the packet being unintentionally received by another node within the range of the sending node. In this regard, in scenarios where source identifier 618 is randomly assigned, although unlikely, it is possible that more than one node within the range of the sending node has a source identifier with a shared bit sequence. Therefore, allocating one bit of destination identifier 638 to indicate a unicast / multicast destination can effectively double the chance of collision or unintended reception. In this regard, it might be desirable to use several bits or a single bit to indicate whether a packet's destination is unicast or multicast to minimize the chance of unintentional unicast transmission.

[0104] In some aspects, a destination identifier MSB value of 0 can indicate a multicast destination / transmission, while a destination identifier MSB value of 1 can indicate a unicast destination / transmission. In some aspects, more than one bit of the destination identifier 638 can be used to indicate the transmission type (e.g., unicast, multicast). For example, in some aspects, the first two, three, four, or more bits of the destination identifier 638 can be used to indicate different types of destinations or transmissions. Described differently, bitmask 620 can divide several possible values ​​of the destination identifier into two groups: a first group where the first bit is zero (0x000000–0x7FFFFF); and a second group where the first bit is one (0x800000–0xFFFFFF). Each group can correspond to either a unicast destination or a multicast destination.

[0105] Continue to refer to Figure 6 Node B prepares a packet with MAC header 630. Like the MAC header 610 of a packet received from Node A, MAC header 630 includes a V field 632, an SRC field 634, and a DST field 636. In a C-V2X scenario, V field 632 can carry the same value as V field 612. SRC field 634 carries the source identifier associated with Node B. The source identifier can be randomly assigned or assigned based on parameters specific to Node B. DST field 636 carries the destination identifier 638. As explained above, the MSB can indicate whether the destination is a unicast or multicast destination, while the remaining bits of the destination identifier 638 indicate the value of the expected receiver. For example, the remaining bits can correspond to a portion of the bits of the expected receiver's source identifier.

[0106] Figure 7 This is a block diagram of an exemplary wireless node 700 according to some aspects of this disclosure. Node 700 may be as described above. Figure 1 UE 115 in the network 100 discussed above (e.g., 115i, 115j, 115k) Figure 3 In the C-V2X communication scenario 300 discussed in the article, node 315 and / or from... Figure 4 and 5 The node 415 of communication scenarios 400 and 500 is shown. As illustrated, node 700 may include a processor 702, a memory 704, a unicast packet module 708, a transceiver 710 including a modem subsystem 712 and an RF unit 714, and one or more antennas 716. These components may communicate directly or indirectly with each other, for example, via one or more buses.

[0107] Processor 702 may have various features as a special-purpose processor. For example, these features may include a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein. Processor 702 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0108] Memory 704 may include cache memory (e.g., the cache memory of processor 702), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or combinations of different types of memory. In some aspects, memory 704 may include a non-transient computer-readable medium. Memory 704 may store instructions 706. Instructions 706 may include causing processor 702 to perform the operations described herein when executed by processor 702 (e.g., ...). Figure 1-1 Instructions 706 (and aspects of Figure 14). Instruction 706 may also be referred to as code, which can be broadly interpreted as including any type of computer-readable statement as discussed above.

[0109] The unicast packet module 708 can be implemented via hardware, software, or a combination thereof. For example, the unicast packet module 708 can be implemented as a processor, circuitry, and / or instructions 706 stored in memory 704 and executed by processor 702. In some instances, the unicast packet module 708 can be integrated within a modem subsystem 712. For example, the unicast packet module 708 can be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 712. In some aspects, the unicast packet module 708 can be employed in the data link layer (such as the MAC layer) of a wireless communication node.

[0110] The unicast packet module 708 can communicate with various components of the wireless node (e.g., 315, 415) to perform various aspects of this disclosure, such as... Figure 3-6Aspects of 8 and 9. For example, according to this disclosure, unicast packet module 708 may be configured to generate unicast and / or multicast packets for transmission to another wireless node. Furthermore, in some instances, unicast packet module 708 may be configured to process packets received from another wireless node to determine whether the packet is intended for wireless node 700. For example, when a unicast packet is intended for wireless node 700 (e.g., when the packet includes an indication that the packet is a unicast packet and an identifier associated with wireless node 700), or when a multicast packet is intended for a group of wireless nodes including wireless node 700, the unicast packet module may determine that the packet is intended for the wireless node. In some aspects, unicast packet module 708 may be configured to receive a source identifier associated with a second wireless communication device. Unicast packet module 708 may be further configured to determine a destination identifier based on the source identifier associated with the second wireless communication device and a deterministic function. In some aspects, the destination identifier may be associated with an individual node. The unicast packet module 708 can be further configured to generate unicast packets including a destination identifier and enable the wireless node 700 to transmit the unicast packet to the second wireless communication device.

[0111] On the other hand, the unicast packet module 708 can be configured to determine the destination identifier associated with the first wireless communication device based on the source identifier and a deterministic function associated with the first wireless communication device.

[0112] The unicast packet module 708 may be further configured to process packets received by the wireless node 700 from the second wireless communication device to determine whether the packet is a unicast packet based on whether the packet includes a destination identifier.

[0113] As shown, transceiver 710 may include modem subsystem 712 and RF unit 714. Transceiver 710 may be configured to communicate bidirectionally with other devices, such as other nodes in a sidelink communication scheme. Modem subsystem 712 may be configured to modulate and / or encode data according to MCS (e.g., LDPC coding scheme, turbo coding scheme, convolutional coding scheme, polarization coding scheme, digital beamforming scheme, etc.). RF unit 714 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / coded data (e.g., MAC PDU, source identifier, destination identifier, header version number, static mapping configuration information (e.g., lookup table) and / or hash operations) from modem subsystem 712 (regarding outbound transmissions) or from another source such as wireless nodes 315, 415, 700. RF unit 714 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 710, modem subsystem 712 and / or RF unit 714 may be separate devices coupled together at the wireless node to enable the wireless node to communicate with other devices.

[0114] RF unit 714 can provide modulated and / or processed data (e.g., data packets (or more generally, data messages containing one or more data packets and other information)) to antenna 716 for transmission to one or more other devices. Antenna 716 can further receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at transceiver 710. Transceiver 710 can provide demodulated and decoded data (e.g., Basic Security Message (BSM), MAC PDU, source identifier, destination identifier, header version number, static mapping configuration information (e.g., lookup table), and / or hash operations) to unicast packet module 708 for processing. Antenna 716 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0115] In one aspect, the wireless node 700 may include multiple transceivers 710 implementing different RATs (e.g., NR and LTE). In another aspect, the node 700 may include a single transceiver 710 implementing multiple RATs (e.g., NR and LTE). In yet another aspect, the transceiver 710 may include various components, wherein different combinations of the components can implement different RATs.

[0116] Figure 8 This is a flowchart of a communication method 800 according to some aspects of this disclosure. Aspects of method 800 can be communicated by a first wireless communication device (such as...) Figure 1One of the UEs 115 shown (e.g., 115i, 115j, 115k), and / or Figure 3-5 One of nodes 315 and 415 shown, and / or Figure 7 The steps of method 800 are executed by node 700 (as shown above). A node may include a processor, processing circuitry, and / or any other suitable components or means for performing the steps. For example, node 700 may utilize one or more components (such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716) to perform the steps of method 800. Method 800 may employ methods similar to those described above. Figure 3-6 The mechanisms discussed in schemes 300, 400, 500, and 600 are similar. Aspects of method 800 can be employed in the data link layer (such as the MAC layer) of a wireless communication node. As explained, method 800 includes several enumeration steps, but aspects of method 800 may include additional steps before, after, and between these enumeration steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0117] In block 810, the first wireless communication device receives a source identifier associated with the second wireless communication device. This source identifier can be received in a packet transmitted from the second wireless communication device. Specifically, the packet may include a header having an SRC field, where the source identifier is set to the SRC field value. Therefore, receiving the source identifier may include receiving a packet from the second wireless communication device, wherein the packet includes the source identifier associated with the second wireless communication device. The source identifier may be a randomly generated value comprising multiple bits. In an exemplary aspect, the source identifier is a 24-bit value generated by the second wireless communication device. In some aspects, the first wireless communication device may utilize one or more components, such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and / or one or more antennas 716, to perform aspects of block 810.

[0118] In block 820, the first wireless communication device determines a destination identifier based on a source identifier and a deterministic function associated with the second wireless communication device. In some aspects, the destination identifier differs from the source identifier. In some aspects, the destination identifier is associated with a single or individual node. For example, the destination identifier may be associated with the second wireless communication device. In some aspects, the deterministic function includes at least one of a bitmasking operation, a static mapping operation, or a hashing operation. In some aspects, the source identifier is associated with a first number of possible values, and the destination identifier is associated with a second number of possible values ​​less than the first number. In some aspects, the first wireless communication device may utilize one or more components (such as processor 702, memory 704, and / or unicast packet module 708) to perform the operations of block 820.

[0119] In block 830, a first wireless communication device generates a packet including a destination identifier. In some aspects, the destination identifier indicates a unicast packet. In some aspects, generating the packet includes generating a Media Access Control (MAC) header, wherein the MAC header includes the destination identifier. In some aspects, the MAC header further includes a source identifier associated with the first wireless communication device. In another aspect, the destination identifier includes a first plurality of bits, wherein at least a first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type. In another aspect, the source identifier associated with a second wireless communication device includes a second plurality of bits, and a portion of the first plurality of bits corresponds to a portion of the second plurality of bits. In some aspects, the first wireless communication device may utilize one or more components, such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716, to perform the operation of block 830.

[0120] In block 840, the first wireless communication device transmits packets to the second wireless communication device. In one aspect, transmitting packets to the second wireless communication device includes transmitting unicast using LTE-V2X sidelink communication. In some aspects, the first wireless communication device may utilize one or more components, such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716, to perform the operation of block 840.

[0121] Figure 9 This is a flowchart of a communication method 900 according to some aspects of this disclosure. Aspects of method 900 can be communicated by a first wireless communication device (such as...) Figure 1 One of the UEs 115 shown (e.g., 115i, 115j, 115k), Figure 3-5 One of nodes 315 and 415 shown, and / or Figure 7The steps of method 900 are executed by node 700 (as shown above). A node may include a processor, processing circuitry, and / or any other suitable components or means for performing the steps. For example, node 700 may utilize one or more components (such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716) to perform the steps of method 900. Method 900 may employ methods similar to those described above. Figure 3-6 The mechanisms discussed in schemes 300, 400, 500, and 600 are similar. Aspects of method 900 can be employed in the data link layer (such as the MAC layer) of the wireless communication node. As explained, method 900 includes several enumeration steps, but aspects of method 900 may include additional steps before, after, and between these enumeration steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0122] In block 910, a first wireless communication device determines a destination identifier associated with the first wireless communication device based on a source identifier associated with the first wireless communication device and a deterministic function. In some aspects, the destination identifier differs from the source identifier. In some aspects, the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation. In some aspects, the source identifier is associated with a first number of possible values, and the destination identifier is associated with a second number of possible values ​​less than the first number. In another aspect, the destination identifier includes a first plurality of bits, wherein at least a first bit of the first plurality of bits indicates that the packet is a unicast packet. In another aspect, the source identifier associated with the first wireless communication device includes a second plurality of bits, and a portion of the first plurality of bits corresponds to a portion of the second plurality of bits. In some aspects, the first wireless communication device may utilize one or more components, such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716, to perform the operation of block 910.

[0123] In block 920, the first wireless communication device receives a packet including the destination identifier from the second wireless communication device. In some aspects, receiving the packet includes receiving a Media Access Control (MAC) header. In some aspects, the MAC header includes a source identifier associated with the first wireless communication device. In some aspects, the first wireless communication device may utilize one or more components, such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716, to perform the operation of block 920.

[0124] In block 930, the first wireless communication device determines whether a packet is a unicast packet intended for the first wireless communication device based on whether the packet includes the destination identifier. In some aspects, receiving packets from the second wireless communication device includes receiving packets using LTE-V2X sidelink communication. In some aspects, the first wireless communication device may utilize one or more components, such as processor 702, memory 704, unicast packet module 708, transceiver 710, modem 712, and one or more antennas 716, to perform the operation of block 930.

[0125] In one aspect, method 900 further includes forwarding a packet received in block 920 to a higher layer of the first wireless communication device in response to determining that the packet includes a destination identifier determined in block 910. In another aspect, method 900 further includes discarding a packet received in block 920 in response to determining that the packet does not include a destination identifier determined in block 910.

[0126] This disclosure also includes the following aspects:

[0127] 1. A method for wireless communication performed by a first wireless communication device, comprising:

[0128] Receive the source identifier associated with the second wireless communication device;

[0129] The destination identifier is determined based on the source identifier associated with the second wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier;

[0130] Generate a packet including the destination identifier, wherein the destination identifier indicates a unicast packet; and transmit the packet to a second wireless communication device.

[0131] 2. The method of Clause 1, wherein the deterministic function includes at least one of a bitmasking operation, a static mapping operation, or a hashing operation.

[0132] 3. The method of any of Clauses 1-2, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number.

[0133] 4. The method of any one of clauses 1-3, wherein the destination identifier includes a first plurality of bits, and wherein at least the first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0134] 5. The method of Clause 4, wherein the source identifier associated with the second wireless communication device comprises a second plurality of bits, and wherein a portion of the first plurality of bits corresponds to a portion of the second plurality of bits.

[0135] 6. The method of any one of clauses 1-5, wherein receiving the source identifier associated with the second wireless communication device includes:

[0136] Receive packets from a second wireless communication device, wherein the packets include a source identifier associated with the second wireless communication device.

[0137] 7. The method of any one of Clauses 1-6, wherein generating the packet includes generating a Media Access Control (MAC) header, wherein the MAC header includes the destination identifier.

[0138] 8. The method of Clause 7, wherein the MAC header further includes a source identifier associated with the first wireless communication device.

[0139] 9. The method of any one of Clauses 1-8, wherein transmitting the packet to the second wireless communication device comprises: transmitting the packet using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0140] 10. A method for wireless communication performed by a first wireless communication device, comprising:

[0141] A destination identifier is determined based on a source identifier associated with a first wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier associated with the first wireless communication device;

[0142] Receive packets from a second wireless communication device; and

[0143] Whether a packet is a unicast packet is determined based on whether the packet includes the destination identifier.

[0144] 11. The method of Clause 10, wherein the deterministic function includes at least one of a bitmasking operation, a static mapping operation, or a hashing operation.

[0145] 12. The method of any of Clauses 10-11, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number.

[0146] 13. The method of any of 10-12, wherein the destination identifier includes a first plurality of bits, and wherein at least the first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0147] 14. The method of Clause 13, wherein the source identifier associated with the first wireless communication device includes a second plurality of bits, and wherein a portion of the first plurality of bits corresponds to a portion of the second plurality of bits.

[0148] 15. The method as described in any of Clauses 10-14, further comprising:

[0149] Transmit additional packets, wherein the additional packets include a source identifier associated with the first wireless communication device.

[0150] 16. The method of any of Clauses 10-14, wherein receiving a packet from the second wireless communication device includes: receiving a Media Access Control (MAC) header.

[0151] 17. The method of Clause 16, wherein the MAC header includes a second source identifier associated with the second wireless communication device.

[0152] 18. The method as described in any of Clauses 10-17, further comprising:

[0153] In response to determining that the packet includes the destination identifier, the packet is forwarded to a higher layer of the first wireless communication device.

[0154] 19. The method as described in any of Clauses 10-17, further comprising:

[0155] The packet is discarded in response to the determination that the packet does not contain the destination identifier.

[0156] 20. The method of any one of Clauses 10-19, wherein receiving the packet from the second wireless communication device comprises: receiving the packet using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0157] 21. A first wireless communication device, comprising:

[0158] The transceiver is configured to:

[0159] Receive the source identifier associated with the second wireless communication device;

[0160] as well as

[0161] The processor communicating with the transceiver is configured to:

[0162] A destination identifier is determined based on a source identifier associated with a second wireless communication device and a deterministic function, wherein the destination identifier differs from the source identifier; and

[0163] Generate a packet that includes the destination identifier, where the destination identifier indicates a unicast packet.

[0164] The transceiver is further configured to:

[0165] The packet is transmitted to the second wireless communication device.

[0166] 22. The first wireless communication device as described in Clause 21, wherein the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation.

[0167] 23. A first wireless communication device as described in any of clauses 21-22, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number.

[0168] 24. A first wireless communication device as described in any of clauses 21-23, wherein the destination identifier comprises a first plurality of bits, and wherein at least a first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0169] 25. The first wireless communication device as described in Clause 24, wherein the source identifier associated with the second wireless communication device comprises a second plurality of bits, and wherein a portion of the first plurality of bits corresponds to a portion of the second plurality of bits.

[0170] 26. A first wireless communication device as described in any of clauses 21-25, wherein the transceiver is configured to receive a source identifier associated with a second wireless communication device, including that the transceiver is configured to:

[0171] Receive packets from a second wireless communication device, wherein the packets include a source identifier associated with the second wireless communication device.

[0172] 27. A first wireless communication device as described in any of clauses 21-26, wherein the processor is configured to generate the packet, including that the processor is configured to:

[0173] Generate a Media Access Control (MAC) header, which includes the destination identifier.

[0174] 28. The first wireless communication device as described in Clause 27, wherein the MAC header further includes a source identifier associated with the first wireless communication device.

[0175] 29. A first wireless communication device as described in any of clauses 21-28, wherein the transceiver is configured to transmit the packet to a second wireless communication device, including that the transceiver is configured to:

[0176] The packet is transmitted using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0177] 30. A first wireless communication device, comprising:

[0178] Processor, the processor being configured to:

[0179] A destination identifier is determined based on a source identifier associated with a first wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier associated with the first wireless communication device; and

[0180] The transceiver is configured to:

[0181] Receive packets from the second wireless communication device.

[0182] The processor is further configured as follows:

[0183] Whether a packet is a unicast packet is determined based on whether the packet includes the destination identifier.

[0184] 31. The first wireless communication device as described in Clause 30, wherein the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation.

[0185] 32. A first wireless communication device as described in any of clauses 30-31, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number.

[0186] 33. A first wireless communication device as described in any of clauses 30-32, wherein the destination identifier comprises a first plurality of bits, and wherein at least a first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0187] 34. The first wireless communication device as described in Clause 33, wherein the source identifier associated with the first wireless communication device comprises a second plurality of bits, and wherein a portion of the first plurality of bits corresponds to a portion of the second plurality of bits.

[0188] 35. The first wireless communication device as described in any of clauses 30-34, wherein the transceiver is further configured to:

[0189] Transmit additional packets, wherein the additional packets include a source identifier associated with the first wireless communication device.

[0190] 36. A first wireless communication device as described in any of clauses 30-35, wherein the transceiver is configured to receive the packet from a second wireless communication device, including that the transceiver is configured to:

[0191] Receive Media Access Control (MAC) header.

[0192] 37. The first wireless communication device as described in Clause 36, wherein the MAC header includes a second source identifier associated with the second wireless communication device.

[0193] 38. The first wireless communication device as described in any of clauses 30-37, wherein the processor is further configured to:

[0194] In response to determining that the packet includes the destination identifier, the packet is forwarded to a higher layer of the first wireless communication device.

[0195] 39. The first wireless communication device as described in any of clauses 30-37, wherein the processor is further configured to:

[0196] The packet is discarded in response to the determination that the packet does not contain the destination identifier.

[0197] 40. A first wireless communication device as described in any of clauses 30-39, wherein the transceiver is configured to receive the packet from a second wireless communication device, including that the processor is configured to:

[0198] The packet was received using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0199] 41. A non-transient computer-readable medium having program code recorded thereon for wireless communication by a first wireless communication device, the program code comprising:

[0200] Code used to enable the first wireless communication device to receive the source identifier associated with the second wireless communication device;

[0201] Code for enabling a first wireless communication device to determine a destination identifier based on a source identifier and a deterministic function associated with a second wireless communication device, wherein the destination identifier is different from the source identifier;

[0202] Code for causing a first wireless communication device to generate a packet including the destination identifier, wherein the destination identifier indicates a unicast packet; and

[0203] The code used to enable the first wireless communication device to transmit the packet to the second wireless communication device.

[0204] 42. A non-transient computer-readable medium as described in Clause 41, wherein the deterministic function includes at least one of a bitmasking operation, a static mapping operation, or a hashing operation.

[0205] 43. A non-transient computer-readable medium as described in any of clauses 41-42, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number of possible values.

[0206] 44. A non-transient computer-readable medium as described in any of clauses 41-43, wherein the destination identifier comprises a first plurality of bits, and wherein at least a first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0207] 45. A non-transient computer-readable medium as described in Clause 44, wherein a source identifier associated with a second wireless communication device comprises a second plurality of bits, and wherein a portion of a first plurality of bits corresponds to a portion of the second plurality of bits.

[0208] 46. ​​A non-transient computer-readable medium as described in any of clauses 41-45, wherein the code for enabling a first wireless communication device to receive a source identifier associated with a second wireless communication device comprises:

[0209] Codes used to enable a first wireless communication device to receive packets from a second wireless communication device, wherein the packets include a source identifier associated with the second wireless communication device.

[0210] 47. A non-transient computer-readable medium as described in any of clauses 41-46, wherein the code for causing a first wireless communication device to generate the packet includes:

[0211] Code used to cause a first wireless communication device to generate a Media Access Control (MAC) header, wherein the MAC header includes the destination identifier.

[0212] 48. A non-transient computer-readable medium as described in Clause 47, wherein the MAC header further includes a source identifier associated with the first wireless communication device.

[0213] 49. A non-transient computer-readable medium as described in any of clauses 41-48, wherein the code for causing a first wireless communication device to transmit the packet to a second wireless communication device includes:

[0214] The code used to enable the first wireless communication device to transmit the packet using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0215] 50. A non-transient computer-readable medium having program code recorded thereon for wireless communication by a first wireless communication device, the program code comprising:

[0216] Code for enabling a first wireless communication device to determine a destination identifier based on a source identifier and a deterministic function associated with the first wireless communication device, wherein the destination identifier is different from the source identifier associated with the first wireless communication device;

[0217] Codes used to enable the first wireless communication device to receive packets from the second wireless communication device; and

[0218] Code used to enable a first wireless communication device to determine whether a packet is a unicast packet based on whether the packet includes the destination identifier.

[0219] 51. A non-transient computer-readable medium as described in Clause 50, wherein the deterministic function includes at least one of a bitmasking operation, a static mapping operation, or a hashing operation.

[0220] 52. A non-transient computer-readable medium as described in any of clauses 50-51, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number of possible values.

[0221] 53. A non-transient computer-readable medium as described in any of clauses 50-52, wherein the destination identifier comprises a first plurality of bits, and wherein at least the first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0222] 54. A non-transient computer-readable medium as described in Clause 53, wherein a source identifier associated with a first wireless communication device comprises a second plurality of bits, and wherein a portion of the first plurality of bits corresponds to a portion of the second plurality of bits.

[0223] 55. A non-transient computer-readable medium as described in any of clauses 50-54, wherein the program code further comprises:

[0224] Codes used to enable a first wireless communication device to transmit additional packets, wherein the additional packets include a source identifier associated with the first wireless communication device.

[0225] 56. A non-transient computer-readable medium as described in any of clauses 50-55, wherein the code for enabling a first wireless communication device to receive the packet from a second wireless communication device comprises:

[0226] Code used to enable the first wireless communication device to receive the Media Access Control (MAC) header.

[0227] 57. A non-transient computer-readable medium as described in Clause 56, wherein the MAC header includes a second source identifier associated with a second wireless communication device.

[0228] 58. A non-transient computer-readable medium as described in any of clauses 50-57, wherein the program code further comprises:

[0229] Code used to cause a first wireless communication device to forward a packet to a higher layer of the first wireless communication device in response to determining that the packet includes the destination identifier.

[0230] 59. A non-transient computer-readable medium as described in any of clauses 50-57, wherein the program code further comprises:

[0231] Code used to cause a first wireless communication device to discard a packet in response to determining that the packet does not contain the destination identifier.

[0232] 60. A non-transient computer-readable medium as described in any of clauses 50-59, wherein the code for enabling a first wireless communication device to receive the packet from a second wireless communication device comprises:

[0233] The code used to enable the first wireless communication device to receive the packet using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0234] 61. A first wireless communication device, comprising:

[0235] A means for receiving a source identifier associated with a second wireless communication device;

[0236] Means for determining a destination identifier based on a source identifier associated with a second wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier;

[0237] Means for generating a packet including the destination identifier, wherein the destination identifier indicates a unicast packet; and

[0238] A means for transmitting the packet to a second wireless communication device.

[0239] 62. The first wireless communication device as described in Clause 61, wherein the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation.

[0240] 63. A first wireless communication device as described in any of clauses 61-62, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number.

[0241] 64. A first wireless communication device as described in any of clauses 61-63, wherein the destination identifier comprises a first plurality of bits, and wherein at least a first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

[0242] 65. A first wireless communication device as described in Clause 64, wherein a source identifier associated with a second wireless communication device comprises a second plurality of bits, and wherein a portion of a first plurality of bits corresponds to a portion of the second plurality of bits.

[0243] 66. A first wireless communication device as described in any of clauses 61-65, wherein the means for receiving a source identifier associated with a second wireless communication device comprises:

[0244] A means for receiving packets from a second wireless communication device, wherein the packets include a source identifier associated with the second wireless communication device.

[0245] 67. The first wireless communication device of any of clauses 61-66, wherein the means for generating the packet includes:

[0246] A means for generating a Media Access Control (MAC) header, wherein the MAC header includes the destination identifier.

[0247] 68. The first wireless communication device as described in Clause 67, wherein the MAC header further includes a source identifier associated with the first wireless communication device.

[0248] 69. The first wireless communication device of any of clauses 61-68, wherein the means for transmitting the packet to the second wireless communication device comprises:

[0249] A means for transmitting the packet using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0250] 70. A first wireless communication device, comprising:

[0251] Means for determining a destination identifier based on a source identifier associated with a first wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier associated with the first wireless communication device;

[0252] A means for receiving packets from a second wireless communication device; and

[0253] A means for determining whether a packet is a unicast packet based on whether the packet includes the destination identifier.

[0254] 71. The first wireless communication device as described in Clause 70, wherein the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation.

[0255] 72. A first wireless communication device as described in any of clauses 70-71, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number.

[0256] 73. A first wireless communication device as described in any of clauses 70-72, wherein the destination identifier comprises a first plurality of bits, and wherein at least a first bit of the first plurality of bits indicates a unicast destination.

[0257] 74. The first wireless communication device as described in Clause 73, wherein the source identifier associated with the first wireless communication device comprises a second plurality of bits, and wherein a portion of the first plurality of bits corresponds to a portion of the second plurality of bits.

[0258] 75. The first wireless communication device as described in any one of clauses 70-74, further comprising:

[0259] Means for transmitting additional packets, wherein the additional packets include a source identifier associated with a first wireless communication device.

[0260] 76. The first wireless communication device as described in any of clauses 70-75, wherein the means for receiving the packet from the second wireless communication device comprises:

[0261] A device for receiving Media Access Control (MAC) headers.

[0262] 77. The first wireless communication device as described in Clause 76, wherein the MAC header includes a second source identifier associated with the second wireless communication device.

[0263] 78. The first wireless communication device as described in any of clauses 70-77 further includes:

[0264] Means for forwarding a packet to a higher layer of a first wireless communication device in response to determining that the packet includes the destination identifier.

[0265] 79. The first wireless communication device as described in any of clauses 70-77 further includes:

[0266] Means for discarding a packet in response to determining that the packet does not contain the destination identifier.

[0267] 80. A first wireless communication device as described in any of clauses 70-79, wherein the means for receiving the packet from a second wireless communication device comprises:

[0268] A device for receiving the packet using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

[0269] The various illustrative blocks and modules described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration).

[0270] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the above-described functions may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations. Additionally, as used herein (including in the claims), the word "or" in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration such as [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). The terms "about" or "approximately" may be used to indicate a range of + / - 2%, unless otherwise stated.

[0271] As will be appreciated by those skilled in the art by this time, and depending on the specific application at hand, many modifications, substitutions, and variations can be made to the materials, apparatus, configuration, and methods of use of the devices disclosed herein without departing from the spirit and scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the specific aspects explained and described herein (which are merely examples of this disclosure), but should be fully equivalent to the appended claims and their functional equivalents.

Claims

1. A method for wireless communication performed by a first wireless communication device, comprising: Receive the source identifier associated with the second wireless communication device; A destination identifier associated with the second wireless communication device is determined based on the source identifier and a deterministic function associated with the second wireless communication device, wherein the destination identifier is different from the source identifier, wherein the destination identifier includes a first plurality of bits and the source identifier includes a second plurality of bits, wherein at least one bit of the destination identifier indicates a unicast packet type, and wherein at least a portion of the first plurality of bits corresponds to a portion of the second plurality of bits. Generate a group that includes the destination identifier; as well as The packet is transmitted to the second wireless communication device.

2. The method of claim 1, wherein the deterministic function includes at least one of a bitmasking operation, a static mapping operation, or a hashing operation.

3. The method of claim 1, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number of possible values.

4. The method of claim 1, wherein at least the first bit of the first plurality of bits indicates that the packet is associated with the unicast transmission type.

5. The method of claim 1, wherein receiving the source identifier associated with the second wireless communication device comprises: Receive packets from the second wireless communication device, wherein the packets include the source identifier associated with the second wireless communication device.

6. The method of claim 1, wherein generating the packet includes generating a Media Access Control (MAC) header, wherein the MAC header includes the destination identifier.

7. The method of claim 6, wherein the MAC header further includes a source identifier associated with the first wireless communication device.

8. The method of claim 1, wherein transmitting the packet to the second wireless communication device comprises: The packets are transmitted using Long Term Evolution (LTE) Vehicle-to-Everything (V2X) sidelink communication.

9. A method for wireless communication performed by a first wireless communication device, comprising: A destination identifier associated with the first wireless communication device is determined based on a source identifier and a deterministic function associated with the first wireless communication device, wherein the destination identifier is different from the source identifier, wherein the destination identifier includes a first plurality of bits and the source identifier includes a second plurality of bits, wherein at least one bit of the destination identifier indicates a unicast packet type, and wherein at least a portion of the first plurality of bits corresponds to a portion of the second plurality of bits; Receive packets from the second wireless communication device; as well as Whether a packet is a unicast packet is determined based on whether the packet includes the destination identifier.

10. The method of claim 9, wherein the deterministic function comprises at least one of a bitmasking operation, a static mapping operation, or a hashing operation.

11. The method of claim 9, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number of possible values.

12. The method of claim 9, wherein: At least the first bit of the first plurality of bits indicates that the packet is associated with the unicast transmission type.

13. The method of claim 9, further comprising: Transmit additional packets, wherein the additional packets include the source identifier associated with the first wireless communication device.

14. The method of claim 9, wherein receiving the packet from the second wireless communication device comprises: Receive a Media Access Control (MAC) header, wherein the MAC header includes a second source identifier associated with the second wireless communication device.

15. The method of claim 9, further comprising: In response to determining that the packet includes the destination identifier, the packet is forwarded to a higher layer of the first wireless communication device.

16. The method of claim 9, further comprising: The packet is discarded in response to the determination that the packet does not contain the destination identifier.

17. A first wireless communication device, comprising: Transceiver, the transceiver being configured to: Receive the source identifier associated with the second wireless communication device; as well as The processor communicating with the transceiver is configured to: A destination identifier associated with the second wireless communication device is determined based on the source identifier and a deterministic function associated with the second wireless communication device, wherein the destination identifier is different from the source identifier, wherein the destination identifier includes a first plurality of bits and the source identifier includes a second plurality of bits, wherein at least one bit of the destination identifier indicates a unicast packet type, and wherein at least a portion of the first plurality of bits corresponds to a portion of the second plurality of bits. as well as Generate a group that includes the destination identifier. The transceiver is further configured to: The packet is transmitted to the second wireless communication device.

18. The first wireless communication device of claim 17, wherein the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation.

19. The first wireless communication device of claim 17, wherein the source identifier is associated with a first number of possible values, and wherein the destination identifier is associated with a second number of possible values ​​less than the first number of possible values.

20. The first wireless communication device as claimed in claim 17, wherein: At least the first bit of the first plurality of bits indicates that the packet is associated with the unicast transmission type.

21. The first wireless communication device of claim 17, wherein the transceiver is configured to receive the source identifier associated with the second wireless communication device, including the transceiver being configured to: Receive packets from the second wireless communication device, wherein the packets include the source identifier associated with the second wireless communication device.

22. The first wireless communication device of claim 17, wherein the processor is configured to generate the packet, the processor is configured to: Generate a Media Access Control (MAC) header, wherein the MAC header includes: The destination identifier; as well as The source identifier associated with the first wireless communication device.

23. A first wireless communication device, comprising: Processor, the processor being configured to: A destination identifier associated with the first wireless communication device is determined based on a source identifier associated with the first wireless communication device and a deterministic function, wherein the destination identifier is different from the source identifier, wherein the destination identifier includes a first plurality of bits, and the source identifier includes a second plurality of bits, wherein at least one bit of the destination identifier indicates a unicast packet type, and wherein at least a portion of the first plurality of bits corresponds to a portion of the second plurality of bits; and Transceiver, the transceiver being configured to: Receive packets from the second wireless communication device. The processor is further configured to: Whether a packet is a unicast packet is determined based on whether the packet includes the destination identifier.

24. The first wireless communication device of claim 23, wherein the deterministic function includes at least one of a bit masking operation, a static mapping operation, or a hashing operation.

25. The first wireless communication device as claimed in claim 23, wherein: At least the first bit of the first plurality of bits indicates that the packet is associated with a unicast transmission type.

26. The first wireless communication device of claim 23, wherein the transceiver is further configured to: Transmit additional packets, wherein the additional packets include the source identifier associated with the first wireless communication device.

27. The first wireless communication device of claim 23, wherein the transceiver is configured to receive the packet from the second wireless communication device, the transceiver is configured to: Receive a Media Access Control (MAC) header, wherein the MAC header includes a second source identifier associated with the second wireless communication device.

28. The first wireless communication device of claim 23, wherein the processor is further configured to: In response to determining that the packet includes the destination identifier, the packet is forwarded to a higher layer of the first wireless communication device.

29. The first wireless communication device of claim 23, wherein the processor is further configured to: The packet is discarded in response to the determination that the packet does not contain the destination identifier.

Images