Cross-band Sidelink Reservation

Abstract

Aspects relate to a mechanism for sidelink reservation across frequency bands. In some examples, a sidelink device may be configured to communicate with one or more other sidelink devices on a first frequency band (e.g., sub-6 gigahertz band) and a second frequency band (e.g., millimeter wave band). The sidelink device may be further configured to perform cross-link resource reservation for sidelink transmissions, where a resource reservation message transmitted on the first frequency band indicates reserved resources within the second frequency band for the sidelink transmission. The sidelink device may then transmit sidelink control information (SCI) within a sidelink control channel on the second frequency band and transmit user data traffic corresponding to the SCI within a sidelink data channel on the second frequency band.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit and priority of non - provisional patent application No. 16 / 896,881, filed on June 9, 2020, and provisional patent application No. 62 / 867,787, filed on June 27, 2019, with the United States Patent and Trademark Office. The entire contents of these applications are incorporated herein by reference as if fully set forth below and for all applicable purposes.

[0003] Introduction

[0004] The techniques discussed below generally relate to wireless communication networks and, in particular, to sidelink wireless communication.

[0005] In many existing wireless communication systems, cellular networks are implemented by enabling wireless user equipment to communicate with each other by signaling with nearby base stations or cells. When the user equipment moves across the service area, handovers occur so that each user equipment maintains communication with each other via its respective cell.

[0006] Another solution for wireless communication systems is a device - to - device (D2D) network, where wireless user equipment can signal directly to each other rather than via an intermediate base station or cell. For example, a D2D communication network can utilize sidelink signaling to facilitate direct communication between user equipment. In some sidelink network configurations, user equipment can further communicate in a cellular network (usually under the control of a base station). Thus, user equipment can be configured to perform uplink and downlink signaling via a base station and further to perform sidelink signaling directly between user equipment without transmissions passing through the base station.

[0007] In wireless communication systems (such as those specified under the standards for 5G New Radio (NR)), both base stations and wireless communication devices can utilize beamforming to compensate for high path loss and short range. Beamforming is a signal - processing technique used with antenna arrays for directional signal transmission and / or reception. For example, antennas in an antenna array can transmit signals combined with other signals from other antennas in the same array in such a way that signals at a particular angle experience constructive interference while other signals experience destructive interference. Beamforming can be implemented in both traditional cellular network configurations and sidelink network configurations at higher frequency bands to support increased data rates.

[0008] Brief Summary

[0009] A brief overview of one or more aspects of the present disclosure is provided below to give a basic understanding of these aspects. This overview is not an exhaustive survey of all contemplated features of the present disclosure, and is neither intended to identify key or critical elements of all aspects of the present disclosure nor to attempt to define the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a prelude to the more detailed description that follows.

[0010] In one example, a method for wireless communication at a first sidelink device is disclosed. The method includes transmitting a resource reservation message on a first frequency band including a first carrier frequency. The resource reservation message includes an indication of reserved resources on a second frequency band including a second carrier frequency for transmitting user data traffic from the first sidelink device to a second sidelink device. The method further includes transmitting a sidelink control channel within the reserved resources on the second frequency band. The sidelink control channel includes sidelink control information (SCI) associated with the user data traffic to be transmitted from the first sidelink device to the second sidelink device. The method further includes transmitting a sidelink data channel including the user data traffic within the reserved resources on the second frequency band.

[0011] Another example provides a first sidelink device including a processor, a wireless transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured to transmit a resource reservation message on a first frequency band including a first carrier frequency via the wireless transceiver. The resource reservation message includes an indication of reserved resources on a second frequency band including a second carrier frequency for transmitting user data traffic from the first sidelink device to a second sidelink device. The processor and the memory are further configured to transmit a sidelink control channel within the reserved resources on the second frequency band. The sidelink control channel includes sidelink control information (SCI) associated with the user data traffic to be transmitted from the first sidelink device to the second sidelink device. The processor and the memory are further configured to transmit a sidelink data channel including the user data traffic within the reserved resources on the second frequency band.

[0012] Another example provides a method for wireless communication at a first sidelink device. The method includes receiving a resource reservation message on a first frequency band including a first carrier frequency. The resource reservation message includes an indication of reserved resources on a second frequency band including a second carrier frequency for transmitting user data traffic from a second sidelink device. The method further includes receiving a sidelink control channel on the second frequency band. The sidelink control channel includes sidelink control information (SCI) associated with the user data traffic to be transmitted from the second sidelink device to the first sidelink device. The method further includes receiving a sidelink data channel including the user data traffic on the second frequency band.

[0013] Another example provides a method for wireless communication at a first sidelink device. The method includes receiving a resource reservation message on a first frequency band including a first carrier frequency. The resource reservation message includes an indication of reserved resources on a second frequency band including a second carrier frequency for transmitting user data traffic from a second sidelink device to a third sidelink device. The method further includes managing interference on the reserved resources based on the resource reservation message.

[0014] These and other aspects of the present disclosure will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary examples of the present disclosure in conjunction with the accompanying drawings, other aspects, features, and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain examples and drawings, all examples of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may be used in accordance with the various examples of the present disclosure discussed herein. In a similar manner, although the examples may be discussed below as examples of devices, systems, or methods, it should be understood that such examples may be implemented in various devices, systems, and methods. Brief Description of the Drawings

[0016] Figure 1 is a diagram illustrating an example of a radio access network for wireless.

[0017] Figure 2 is a diagram illustrating an example of a vehicle-to-everything (V2X) wireless communication network.

[0018] Figure 3 is a schematic diagram illustrating wireless resource organization in an air interface using orthogonal frequency division multiplexing (OFDM).

[0019] Figure 4 is a block diagram illustrating a wireless communication system supporting beamforming and multiple-input multiple-output (MIMO) communication.

[0020] Figure 5 is a diagram illustrating an example of sidelink communication across two different frequency bands in a wireless network.

[0021] Figure 6 is a signaling diagram illustrating an exemplary procedure for performing cross-link resource reservation for sidelink transmission.

[0022] Figure 7 is a signaling diagram illustrating another exemplary procedure for performing cross-link resource reservation for sidelink transmission.

[0023] Figure 8 FIG. is an exemplary format diagram for explaining resource reservation messages for cross-link resource reservation.

[0024] Figure 9 FIG. is a diagram for explaining exemplary reserved resources and scheduled resources for sidelink transmission.

[0025] Figure 10 FIG. is a diagram for explaining an example of the hardware implementation of a sidelink device employing a processing system.

[0026] Figure 11 FIG. is a flowchart of an exemplary method for wireless communication at a transmitter sidelink device.

[0027] Figure 12 FIG. is a flowchart of an exemplary method for wireless communication at a receiver sidelink device.

[0028] Figure 13 FIG. is a flowchart of another exemplary method for wireless communication at a receiver sidelink device.

[0029] DETAILED DESCRIPTION

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

[0031] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). The frequency between FR1 and FR2 is generally referred to as the mid-band frequency. Although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the “sub-6 GHz” band. A similar naming issue sometimes arises with respect to FR2. Although different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) identified by the International Telecommunication Union (ITU) as the “millimeter wave” band, FR2 is typically (interchangeably) referred to as the “millimeter wave” band in documents and articles.

[0032] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, terms such as "sub-6 GHz" can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include intermediate band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if used herein, terms such as "millimeter wave" can generally represent frequencies that can include intermediate band frequencies, can be within FR2, or can be within the EHF band.

[0033] Aspects of the present disclosure relate to mechanisms for cross-band sidelink reservation. In some examples, a sidelink device may be configured to communicate with one or more other sidelink devices using an omnidirectional beam on a first band (e.g., a sub-6 gigahertz band) and using a corresponding directional beam on a second band (e.g., a millimeter wave band). The sidelink device may be further configured to perform cross-link resource reservation for a sidelink transmission, where a resource reservation message transmitted on the first band indicates the reserved resources within the second band for the sidelink transmission. Then, the sidelink device may transmit sidelink control information (SCI) within a sidelink control channel (e.g., a physical sidelink control channel (PSCCH)) on the second band and transmit user data traffic corresponding to the SCI within a sidelink data channel (e.g., a physical sidelink shared channel (PSSCH)) on the second band. The SCI may include scheduling information that indicates the scheduled resources within the reserved resources for the transmission of the user data traffic.

[0034] In some examples, the resource reservation message can be a multicast message transmitted to the target sidelink device of the sidelink transmission and other neighboring sidelink devices. In other examples, the resource reservation message may include both a unicast message transmitted to the target sidelink device and a multicast message transmitted to other neighboring sidelink devices. Neighboring sidelink devices may use the resource reservation message to manage interference on the reserved resources.

[0035] While aspects and examples are described herein by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, or packaging arrangements. For example, the examples and / or uses can be generated via integrated chips and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to particular use cases or applications, a wide applicability of the described innovations can occur. The scope of implementations can range from chip-level or module components to non-module, non-chip-level implementations and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical environments, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., of various sizes, shapes, and constitutions.

[0036] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Now referring to Figure 1 , by way of illustrative example and not limitation, a schematic illustration of a radio access network 100 is provided. The RAN 100 can implement any one or several suitable wireless communication technologies to provide radio access. As an example, the RAN 100 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 100 can operate in a hybrid of 5G NR and the evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, commonly referred to as LTE. 3GPP refers to this hybrid RAN as the next-generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0037] The geographical area covered by the radio access network 100 can be divided into several cellular areas (cells), which can be uniquely identified by user equipment (UE) based on an identifier broadcast over the geographical area from an access point or base station. Figure 1Macro cells 102, 104, and 106, 142, and small cell 108 are illustrated, where each may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by an antenna array, where each antenna is responsible for communicating with UEs in a portion of that cell.

[0038] Generally, a corresponding base station (BS) serves its respective cell. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from UEs in one or more cells. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), Node B (NB), evolved Node B (eNB), next-generation Node B (gNB), or some other suitable term.

[0039] In Figure 1 FIG., three base stations 110, 112, and 146 are shown in cells 102, 104, and 142, respectively; and a third base station 114 is shown controlling a remote radio head (RRH) 116 in cell 106. That is, a base station may have an integrated antenna or may be connected to an antenna or RRH by a feeder cable. In the illustrated example, cells 102, 104, 106, and 142 may be referred to as macro cells because base stations 110, 112, 114, and 146 support cells with large dimensions. Additionally, a base station 118 is shown in small cell 108 (e.g., micro cell, pico cell, femto cell, home base station, home Node B, home evolved Node B, etc.), which may overlap with one or more macro cells. In this example, cell 108 may be referred to as a small cell because base station 118 supports a cell with a relatively small dimension. Cell sizing may be done according to system design and component constraints. It is to be understood that radio access network 100 may include any number of radio base stations and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of a given cell. Base stations 110, 112, 114, 118, 146 provide a wireless access point to the core network for any number of mobile devices.

[0040] Figure 1Further includes a quadcopter or drone 120, which can be configured to be used as a base station. That is, in some examples, the cell may not have to be stationary, and the geographical area of the cell can move according to the position of a mobile base station (such as quadcopter 120).

[0041] Generally, a base station may include a backhaul interface for communicating with a backhaul portion of the network (not shown). The backhaul can provide a link between the base station and the core network (not shown), and in some examples, the backhaul can provide an interconnection between the corresponding base stations. The core network can be part of a wireless communication system and can be independent of the radio access technology used in the radio access network. Various types of backhaul interfaces can be employed, such as a direct physical connection using any suitable transport network, a virtual network, and so on.

[0042] RAN 100 is illustrated as supporting wireless communication for multiple mobile devices. Mobile devices are commonly referred to as user equipment (UE) in the standards and specifications promulgated by the Third Generation Partnership Project (3GPP), but may also be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other suitable term. A UE can be a device that provides a user with access to network services.

[0043] Within this document, a "mobile" device does not necessarily need to have the ability to move and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. For example, some non-limiting examples of mobile devices include mobile equipment, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the "Internet of Things" (IoT). Additionally, a mobile device can be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smartwatch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. A mobile device can also be a digital home or smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, etc. A mobile device can also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device (e.g., a smart grid) that controls electricity, lighting, water, etc., an industrial automation and enterprise device, a logistics controller, an agricultural device, etc. Further, a mobile device can provide connected healthcare or telemedicine support, i.e., healthcare at a distance. Telehealth devices can include telehealth monitoring devices and telehealth supervision devices, and their communication can be given preferential access over other types of information, for example, in the form of prioritized access for critical service data transmission and / or relevant QoS for critical service data transmission.

[0044] Within the RAN 100, a cell can include UEs that can communicate with one or more sectors of each cell. For example, UEs 122 and 124 can communicate with base station 110; UEs 126 and 128 can communicate with base station 112; UEs 130 and 132 can communicate with base station 114 via RRH 116; UE 134 can communicate with base station 118; UEs 138 and 140 can communicate with base station 146; and UE 136 can communicate with mobile base station 120. Here, each of base stations 110, 112, 114, 118, 120, and 146 can be configured to provide an access point to the core network (not shown) for all UEs in the corresponding cell. In another example, a mobile network node (e.g., quadcopter 120) can be configured to act as a UE. For example, quadcopter 120 can operate within cell 102 by communicating with base station 110.

[0045] Wireless communication between a RAN 100 and a UE (e.g., UE 122 or 124) may be described as utilizing an air interface. Transmissions on the air interface from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 110). Another way to describe this scenario may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 122) to a base station (e.g., base station 110) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 122).

[0046] For example, DL transmissions may include unicast or broadcast transmissions of control information and / or data (e.g., user data traffic or other types of traffic) from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124), while UL transmissions may include transmissions of control information and / or traffic information originating at a UE (e.g., UE 122). Additionally, uplink and / or downlink control information and / or traffic information may be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit in an orthogonal frequency division multiplexing (OFDM) waveform where each subcarrier carries one resource element (RE). A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme may be utilized to organize the waveform, and the various time divisions of the waveform may have any suitable duration.

[0047] The air interface in RAN 100 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL or reverse link transmissions from UEs 122 and 124 to base station 110, and utilizes orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) to provide multiplexing for DL or forward link transmissions from base station 110 to UEs 122 and 124. Additionally, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes can be utilized to provide it. Furthermore, multiplexing for DL transmissions from base station 110 to UEs 122 and 124 can be provided by time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0048] In addition, the air interface in RAN 100 can utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where both endpoints can communicate with each other in two directions. Full duplex means that both endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full duplex channel generally relies on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full duplex emulation for a wireless link is typically achieved by utilizing frequency division duplexing (FDD) or time division duplexing (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in the other direction, where the direction can change very rapidly, for example, several times per time slot.

[0049] In RAN 100, the ability of a UE to communicate while moving, independent of its location, is referred to as mobility. The various physical channels between the UE and the RAN are generally established, maintained, and released under the control of an access and mobility management function (AMF), which may include a security context management function (SCMF) that manages the security context for both the control plane and user plane functionality, and a security anchor function (SEAF) that performs authentication. In various aspects of the present disclosure, RAN 100 may utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the transfer of the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signals from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or switch from the serving cell to the neighboring (target) cell. For example, UE 124 may move from the geographical area corresponding to its serving cell 102 to the geographical area corresponding to neighbor cell 106. When the signal strength or quality from neighbor cell 106 exceeds the signal strength or quality of its serving cell 102 for a given amount of time, UE 124 may transmit a report message to its serving base station 110 indicating this condition. In response, UE 124 may receive a handover command, and the UE may undergo a handover to cell 106.

[0050] In a network configured for UL-based mobility, the UL reference signal from each UE may be used by the network to select a serving cell for each UE. In some examples, base stations 110, 112, 146, and 114 / 116 may broadcast unified synchronization signals (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 122, 124, 126, 128, 130, 132, 138, and 140 may receive the unified synchronization signals, derive carrier frequency and radio frame timing from these synchronization signals, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 124) may be received concurrently by two or more cells (e.g., base stations 110 and 114 / 116) within the RAN 100. Each of these cells may measure the strength of the pilot signal, and the RAN (e.g., one or more of base stations 110 and 114 / 116 and / or a central node within the core network) may determine a serving cell for UE 124. As UE 124 moves within RAN 100, the network may continue to monitor the uplink pilot signals transmitted by UE 124. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, RAN 100 may handover UE 124 from the serving cell to the neighboring cell with or without notifying UE 124.

[0051] Although the synchronization signal transmitted by base stations 110, 112 and 114 / 116 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone including multiple cells operating on the same frequency and / or having the same timing. The use of zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0052] In various implementations, the air interface in the RAN 100 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. While some technical rules generally still need to be followed to access unlicensed spectrum, any operator or device may obtain access. Shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, the license holder of a portion of licensed spectrum may provide Licensed Shared Access (LSA) to share the spectrum with other parties, e.g., with access obtained using conditions determined by the appropriate license holder.

[0053] To achieve a low block error rate (BLER) on transmissions over the RAN 100 while still achieving a very high data rate, channel coding may be used. That is, wireless communication generally may utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can improve the reliability of the message, enabling any bit errors that may occur due to noise to be corrected.

[0054] In early 5G NR specifications, data was encoded using Quasi-Cyclic Low-Density Parity-Check (LDPC) with two different base graphs: one base graph was used for large code blocks and / or high code rates, and the other base graph was used for other cases. Polar coding based on nested sequences was used to encode control information and the Physical Broadcast Channel (PBCH). For these channels, puncturing, shortening, and repetition were used for rate matching.

[0055] However, those of ordinary skill in the art will understand that aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of the base station and the UE may include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to perform wireless communication using one or more of these channel codes.

[0056] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication among some or all of the devices and equipment within its service area or cell. Within the present disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for a scheduled communication, the UE or the scheduled entity utilizes the resources allocated by the scheduling entity.

[0057] The base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity, thereby scheduling resources for one or more scheduled entities (e.g., one or more other UEs). In other examples, two or more UEs (e.g., UE 138 and 140) can communicate with each other using side link signals 137 without relaying the communication through a base station (e.g., base station 146) and without having to rely on scheduling or control information from the base station. In some examples, UE 138 is being used as a scheduling entity or an initiator (e.g., a transmitter) side link device, and UE 140 can be used as a scheduled entity or a receiver side link device. For example, UE 138 can be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or a mesh network.

[0058] V2X communications involve the exchange of information not only between vehicles themselves, but also between vehicles and external systems such as streetlights, buildings, pedestrians, and wireless communication networks. V2X systems enable vehicles to obtain information about weather, nearby accidents, road conditions, the activities of nearby vehicles and pedestrians, objects near the vehicle, and other relevant information that can be used to improve the vehicle driving experience, increase vehicle safety, and support autonomous vehicles.

[0059] Two main technologies that can be used by V2X networks include dedicated short range communications (DSRC) based on the IEEE 802.11p standard and cellular V2X based on LTE and / or 5G (New Radio) standards. Various aspects of the present disclosure may relate to New Radio (NR) cellular V2X networks, referred to herein as V2X networks for simplicity. However, it should be understood that the concepts disclosed herein may not be limited to a particular V2X standard.

[0060] To facilitate V2X communication on sidelink 137, a UE (e.g., UE 138) may include a sidelink manager 144 configured to establish a corresponding sidelink with one or more other UEs (e.g., UE 140). The sidelink manager 144 may be further configured to reserve resources for sidelink communication with another UE (e.g., UE 140) across frequency bands. In some examples, the sidelink manager 144 may be configured to communicate with one or more other sidelink devices (e.g., UE 140) using an omnidirectional beam on a first frequency band (e.g., sub-6 GHz band) and using corresponding directional beams on a second frequency band (e.g., millimeter wave band). The sidelink manager 144 may be further configured to generate a resource reservation message and transmit the resource reservation message on the first frequency band, the resource reservation message indicating the reserved resources within the second frequency band for sidelink transmission (e.g., sidelink transmission towards UE 140). The sidelink manager 144 may then be configured to transmit an SCI within a PSCCH on the second frequency band and transmit user data traffic corresponding to the SCI within a PSSCH on the second frequency band.

[0061] Figure 2 An example of a wireless communication network 200 configured to support D2D or sidelink communication is illustrated. In some examples, sidelink communication may include V2X communication. V2X communication involves not only direct wireless information exchange between vehicles (e.g., vehicles 202 and 204) themselves, but also direct wireless information exchange between vehicles 202 / 204 and infrastructure 206 (such as streetlights, buildings, traffic cameras, toll booths, or other stationary objects), between vehicles 202 / 204 and pedestrians 208, and between vehicles 202 / 204 and a wireless communication network (e.g., base station 210). In some examples, V2X communication may be implemented according to the new radio (NR) cellular V2X standard defined by 3GPP (Release 15) or other suitable standards.

[0062] V2X communication enables vehicles 202 and 204 to obtain information related to weather, nearby accidents, road conditions, activities of nearby vehicles and pedestrians, objects near the vehicle, and other relevant information that can be used to improve the driving experience of the vehicle and enhance vehicle safety. For example, such V2X data enables autonomous driving and improves road safety and traffic efficiency. For example, V2X-connected vehicles 202 and 204 can utilize the exchanged V2X data to provide collision warnings, road hazard warnings, approaching emergency vehicle warnings, pre-impact / post-impact warnings and information, emergency braking warnings, upcoming traffic jam warnings, lane change warnings, intelligent navigation services, and other similar information in the vehicle. Additionally, the V2X data received by the V2X-connected mobile devices of pedestrians / cyclists 208 can be used to trigger warning sounds, vibrations, flashing lights, etc. in situations where danger is imminent.

[0063] Sidelink communication between vehicles 202 and 204 or between vehicles 202 or 204 and infrastructure 206 or pedestrians 208 occurs on the Proximity Services (ProSe) PC5 interface 212. In various aspects of the present disclosure, the PC5 interface 212 can be further used to support D2D communication in other proximity use cases. Examples of other proximity use cases can include public safety or business (e.g., entertainment, education, office, medical, and / or interactive)-based proximity services. In Figure 2 the example shown, ProSe communication can occur between UEs 214 and 216.

[0064] ProSe communication can support different operating scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to the scenario where UEs 214 and 216 are outside the coverage area of a base station (e.g., base station 210), but each UE is still configured for ProSe communication. Partial coverage refers to the scenario where one of these UEs (e.g., UE 216) is outside the coverage area of a base station (e.g., base station 210), while the other UE (e.g., UE 214) is in communication with the base station 210. In-coverage refers to the scenario where UEs 214 and 216 are in communication with a base station 210 (e.g., gNB) via a Uu (e.g., cellular interface) connection to receive ProSe service authorization and provisioning information to support ProSe operations.

[0065] The sidelink can be used in one or more frequency bands to facilitate communication between various V2X and D2D devices (which may be collectively referred to herein as sidelink devices or sidelink UEs). In some examples, a V2X device (e.g., vehicle 204) may include a sidelink manager 210a that is configured to establish corresponding sidelinks with other nearby V2X devices (e.g., roadside infrastructure 206, pedestrian / bicyclist 208, and other vehicles 202), and manage communication on the corresponding sidelinks. Additionally, a D2D device (e.g., UE 216) may include a sidelink manager 210b that is configured to establish corresponding sidelinks with other nearby D2D devices (e.g., UE 214), and manage communication on the corresponding sidelinks. The sidelink managers 210a and 210b may correspond, for example, to Figure 1 the sidelink manager 144 shown in

[0066] Reference will be made to Figure 3 the OFDM waveform schematically illustrated in

[0067] to describe various aspects of the present disclosure. Those of ordinary skill in the art should understand that the various aspects of the present disclosure can be applied in substantially the same manner as described herein to SC-FDMA waveforms. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms. Figure 3

[0068] Now referring to Figure 3 , an expanded view of an example subframe 302 is illustrated, which shows an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction in terms of OFDM symbols; and frequency is in the vertical direction in terms of subcarriers.The resource grid 304 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation where multiple antenna ports are available, there can be a corresponding number of resource grids 304 available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more information bits. In some examples, an RE block can be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of contiguous subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, and this number is independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of contiguous OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 308) fully corresponds to a single communication direction (transmission or reception for a given device).

[0069] Scheduling of a UE for downlink, uplink, or sidelink transmission generally involves scheduling one or more resource elements 306 within one or more subbands. Thus, a UE generally utilizes only a subset of the resource grid 304. In some examples, an RB can be the smallest resource unit that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of that UE. An RB can be scheduled by a base station (e.g., gNB, eNB, RSU, etc.), or can be self-scheduled by a UE implementing D2D sidelink communication.

[0070] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RBs 308. Additionally, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, but this is merely one possible example.

[0071] Each 1 ms subframe 302 can include one or more contiguous time slots. As an illustrative example, in Figure 3In the example shown, a subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini - slots with a shorter duration (e.g., one to three OFDM symbols). In some cases, these mini - slots may occupy resources scheduled for ongoing time - slot transmissions for the same or different UEs to transmit. Any number of resource blocks may be utilized within a subframe or time slot.

[0072] An expanded view of a time slot 310 illustrates the time slot 310 including a control region 312 and a data region 314. Generally, the control region 312 may carry control channels, while the data region 314 may carry data channels. Of course, a time slot may contain all - DL, all - UL, or at least one DL portion and at least one UL portion. Figure 3 The simple structure illustrated is merely exemplary in nature, and different time - slot structures may be utilized and may include one or more of each control region and data region.

[0073] Although not illustrated in Figure 3 Each RE 306 within an RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc., although not illustrated in. Other RE 306 within the RB 308 may also carry pilots or reference signals. These pilots or reference signals are available for a receiving device to perform channel estimation of the corresponding channels, which may enable coherent demodulation / detection of the control and / or data channels within the RB 308.

[0074] In some examples, a time slot 310 may be used for broadcast or unicast communication. For example, in a V2X or D2D network, broadcast communication may refer to a point - to - multi - point transmission by one device (e.g., a vehicle, a base station (e.g., an RSU, a gNB, an eNB, etc.), a UE, or other similar devices) to other devices. Unicast communication may refer to a point - to - point transmission by one device to a single other device.

[0075] In an example of sidelink communication, a control region 312 of a time slot 310 may include a Physical Sidelink Control Channel (PSCCH) that includes sidelink control information (SCI) transmitted by a UE (e.g., a sidelink device such as a V2X or other D2D device) towards a set of one or more other UEs (e.g., other sidelink devices). In some examples, the SCI may include synchronization information for synchronizing communication between sidelink devices over the sidelink channel. Additionally, the SCI may include scheduling information that indicates one or more resource blocks reserved for sidelink communication within a data region 314 by an initiating (or transmitting) sidelink device (e.g., a “scheduling entity”). The data region 314 of the time slot 310 may include a Physical Sidelink Shared Channel (PSSCH) that includes data transmitted by the initiating sidelink device within the reserved resources over the sidelink channel.

[0076] These physical channels are generally multiplexed and mapped to transport channels for handling by the Medium Access Control (MAC) layer. A transport channel carries an information block, which is referred to as a transport block (TB). The transport block size (TBS) (which may correspond to the number of information bits) can be a controlled parameter based on a modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0077] Figure 3 The channels or carriers illustrated are not necessarily all the channels or carriers available between the devices, and one of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be available in addition to those illustrated.

[0078] In some aspects of the present disclosure, a sidelink device (e.g., a V2X or D2D device) may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. For example, in a millimeter wave (mmW) sidelink system, beamformed signals may be used for most channels, including the Physical Sidelink Control Channel (PSCCH) and the Physical Sidelink Shared Channel (PSSCH).

[0079] Figure 4 An example of a wireless communication system 400 that supports beamforming and / or MIMO is illustrated. In a MIMO system, a transmitter 402 includes a plurality of transmit antennas 404 (e.g., N transmit antennas), and a receiver 406 includes a plurality of receive antennas 408 (e.g., M receive antennas). Thus, there are N×M signal paths 408 from the transmit antennas 404 to the receive antennas 410. Each of the transmitter 402 and the receiver 406 may be implemented, for example, in a sidelink device or any other suitable wireless communication device.

[0080] The use of such multi-antenna techniques enables a wireless communication system to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also referred to as layers) on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially pre-coding each data stream (i.e., multiplying these data streams by different weights and phase shifts) and then transmitting each spatially pre-coded stream on the downlink via multiple transmit antennas. The spatially pre-coded data streams arrive at the (a) UE(s) with different spatial signatures, which enable each UE to recover one or more data streams intended for that UE.

[0081] Beamforming is a signal processing technique that can be used at the transmitter 402 or the receiver 406 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 402 and the receiver 406. Beamforming can be achieved by combining signals communicated via the antennas 404 or 408 (e.g., the antenna elements of an antenna array module) such that some of these signals experience constructive interference while other signals experience destructive interference. To create the desired constructive / destructive interference, the transmitter 402 or the receiver 406 can apply amplitude and / or phase offsets to the signals transmitted or received from each of the antennas 404 or 408 associated with the transmitter 402 or the receiver 406.

[0082] A V2X communication system can utilize both the millimeter wave (mmW) band and the sub-6 GHz band. As Figure 4 explained, mmWave beamforming can be used to communicate on a directional beam. For sub-6 GHz band communication, an omnidirectional beam or other similar beam can be used.

[0083] Figure 5 is a diagram illustrating an example of sidelink communication across two different frequency bands in a wireless network. The wireless network 500 includes multiple sidelink devices 502a–502d, each of which can correspond, for example, to Figure 2 one of the V2X or D2D devices shown in

[0084] In Figure 5In the example shown, the sidelink device 502a may be configured to operate simultaneously in at least two frequency bands, for example, such as one or more sub-6 GHz frequency bands and one or more millimeter wave frequency bands. As used herein, the term "simultaneously" may refer to the ability of the sidelink device to communicate on both a first frequency band (e.g., FR1 or sub-6 GHz frequency band) and a second frequency band (e.g., FR2 or millimeter wave frequency band) during an overlapping time period, although the sidelink device may not be able to transmit and / or receive data on both of these frequency bands simultaneously.

[0085] In an example sub-6 GHz communication, the sidelink device 502a may be configured to transmit an omnidirectional beam 504 on FR1. The omnidirectional beam 504 may be received by a plurality of other sidelink devices 502b, 502c, and 502d. In an example millimeter wave communication, the sidelink device 502a may be configured to transmit a directional beam 506a on FR2. Due to the directional characteristics of the beam 506a, the directional transmit beam 506a may be received by a subset of the plurality of sidelink devices. For example, the directional transmit beam 506a may be received by a single receiving sidelink device (e.g., sidelink device 502b). In this example, the receiving sidelink device 502b may utilize a directional receive beam 506b to receive communication from the transmitting sidelink device 502a. The transmit beam 506a and the receive beam 506b together form a beam pair link (BPL) for the signal path between the sidelink devices 502a and 502b on FR2. Due to reciprocity, each beam within the BPL may be used for both transmission and reception.

[0086] In some examples, a unicast connection may be established between the sidelink device 502a and another sidelink device (e.g., sidelink device 502b) on the FR1 sidelink and / or the FR2 sidelink. To establish a unicast connection on the FR1 sidelink (e.g., sub-6 GHz sidelink), the sidelink device 502a may utilize, for example, a D2D (e.g., V2V, V2X, etc.) peer discovery procedure to identify and locate candidate sidelink devices for unicast communication. For example, the sidelink device 502a may locate candidate sidelink devices based on basic service messages (BSMs) broadcast by neighboring sidelink devices (e.g., sidelink devices 502b, 502c, and 502d). The BSM may include location information (e.g., global positioning system (GPS) coordinates), security and identity information, and vehicle information (e.g., speed, trajectory, route, etc.) of the broadcasting sidelink device. After locating another sidelink device (e.g., sidelink device 502b), the sidelink devices 502a and 502b may establish an RRC connection and a signaling radio bearer (SRB) on the FR1 sidelink via, for example, a D2D radio resource control (RRC) interface (e.g., an RRC procedure on the ProSe sidelink (PC5) interface).

[0087] Then, the sidelink devices 502a and 502b can set up the Packet Data Convergence Protocol (PDCP) context, Radio Link Control (RLC) context, Media Access Control (MAC) context, and Physical Layer (PHY) context for the FR1 unicast connection. For example, the PDCP context can indicate whether PDCP duplication is used for the unicast connection. The RLC context can indicate whether to use the acknowledged mode (e.g., using a reordering timer) or the unacknowledged mode for the RLC layer. The MAC context can implement, for example, a Hybrid Automatic Repeat reQuest (HARQ) scheme, a resource selection algorithm, carrier aggregation, or other MAC parameters for the unicast connection. The PHY context can indicate the transmission format and radio resource configuration (e.g., Bandwidth Part (BWP), parameter design, etc.) for the unicast connection.

[0088] A unicast connection between the sidelink device 502a and another sidelink device (e.g., the sidelink device 502b) on the FR2 sidelink (e.g., millimeter wave sidelink) can be established in the Standalone (SA) mode or the Non-Standalone (NSA) mode. In the SA mode, the millimeter wave sidelink can be established without the support of any other previously established communication link in a different frequency band or Radio Access Technology (RAT).

[0089] In the NSA mode, the millimeter wave sidelink can be established with the support of a previously established unicast link (e.g., a sub-6 GHz sidelink). For example, the sidelink device 502a can transmit an RRC reconfiguration message (e.g., an RRC Direct Connection Reconfiguration (RRCDirectConnectionReconfiguraton) message) to the sidelink device 502b on the SRB previously established via the FR1 sidelink. The RRC reconfiguration message can include, for example, the millimeter wave Physical Layer (PHY) configuration for beam direction, timing, location, and / or other Layer 1 (L1) / Layer 2 (L2) parameters in the radio protocol stack (e.g., the Open Systems Interconnection (OSI) model). Then, the sidelink devices 502a and 502b can perform PHY and MAC layer procedures in FR2 to determine the serving BPLs (e.g., beams 506a and 506b), and perform synchronization.

[0090] After establishing a millimeter wave (FR2) sidelink, sidelink device 502a (e.g., source sidelink device 502a) may transmit data to sidelink device 502b (e.g., destination sidelink device) on the FR2 sidelink. In some examples, source sidelink device 502a may utilize selected BPLs (e.g., beams 506a and 506b) to transmit a PSCCH to destination sidelink device 502b on the FR2 sidelink. The PSCCH may include an SCI containing scheduling information that indicates resources (e.g., one or more resource blocks) reserved by source sidelink device 502a for transmitting a PSSCH containing data. Then, source sidelink device 502a may utilize transmit and receive beams 506a and 506b to transmit the PSSCH containing data to destination sidelink device 502b on the reserved resources on the FR2 sidelink.

[0091] Adjacent sidelink devices (e.g., sidelink devices 502c and 502d) may need to have knowledge of the resources reserved for PSSCH transmission to avoid collisions. However, due to the directional nature of transmit beam 506a, other adjacent sidelink devices may not receive the PSCCH and, as a result, may not be aware of the reservation of PSSCH resources by source sidelink device 502a. For example, adjacent sidelink devices 502c and 502d may be communicating on another FR2 sidelink using respective BPLs (e.g., transmit and receive beams 506c and 506d). If adjacent sidelink device 502c does not receive the PSCCH from source sidelink device 502a, adjacent sidelink device 502c may select the same resources for another PSSCH transmitted from adjacent sidelink device 502c to adjacent sidelink device 502d, resulting in interference between these two PSSCH transmissions. Thus, to avoid such interference, source sidelink device 502a may perform beam sweeping of the PSCCH (e.g., transmitting the PSCCH on each of beams 506e - 506g) in FR2 to notify other adjacent sidelink devices (e.g., sidelink device 502c) of the resources reserved by source sidelink device 502a for an upcoming PSSCH transmission. However, broadcasting the reserved unicast resources in multiple beams may result in undesirable overhead.

[0092] Thus, in various aspects of the present disclosure, the source sidelink device 502a may be configured to perform cross-link resource reservation to reserve resources in advance for the FR2 sidelink via the FR1 sidelink. For example, the source sidelink device 502a may be configured to transmit a resource reservation message on FR1 (e.g., on a sub-6 GHz band) to reserve resources on the FR2 sidelink for future sidelink transmissions to the target sidelink device 502b. Then, the source sidelink device 502a may be configured to transmit the PSCCH and PSSCH within the reserved resources on the FR2 sidelink (e.g., on a millimeter wave band). In some examples, the PSCCH may include an SCI containing scheduling information that indicates the scheduled resources within the reserved resources on which the source sidelink device 502a will transmit the PSSCH containing data.

[0093] Based on the resource reservation message, the target sidelink device 502b may beamform towards the source sidelink device 502a using the receive beam 506b to receive the PSCCH and PSSCH within the reserved resources on the FR2 sidelink. Additionally, neighboring sidelink devices may receive the resource reservation message transmitted on FR1, and thus, the source sidelink device 502a may avoid broadcasting the scheduled FR2 unicast resources to multiple neighboring sidelink devices within the communication range of the source sidelink device 502a via beam sweeping. In some examples, the resource reservation message may include a multicast message transmitted on the respective FR1 sidelink to each neighboring sidelink device. The resource reservation message may further be unicast to the target sidelink device 502b on the FR1 sidelink. In some examples, the cross-link resource reservation mechanism described herein may be utilized in the reverse manner to reserve resources on the FR1 carrier using the FR2 carrier.

[0094] Figure 6 is a signaling diagram illustrating an exemplary process for performing cross-link resource reservation for sidelink transmissions between sidelink devices 602 and 604 in a V2X NSA deployment including, for example, sidelink devices 602 and 604 and other neighboring sidelink devices 606. The sidelink devices 602, 604, and 606 may correspond, for example, to Figure 5 the sidelink devices shown in Figure 2 and / or Figure 6 the V2X devices shown in

[0095] In 608, the source and target sidelink devices 602 and 604 may initially establish a sidelink on a first frequency band FR1 (e.g., a sub-6 GHz band), as described above in connection with Figure 5As described. For example, after discovery (e.g., using a V2V peer discovery procedure), the source-side link device 602 may establish a radio resource control (RRC) connection and a signaling radio bearer (SRB) for the FR1 side link. An SRB is a logical communication channel on L2 and higher layers for transmitting control information for a communication session. For example, the SRB may carry a dedicated control channel (DCCH) including PHY layer, MAC layer, and other access layer control information for initiating a communication session. Using the SRB, the configuration of the L2 and higher protocol layers has a semi-static nature that occurs during the establishment of a communication session. PHY layer control is more dynamic in nature based on resource allocation (e.g., time, frequency, space, and / or power), and thus, PHY layer control and adaptation typically occur when data is being exchanged (e.g., transmitted / received).

[0096] The SRB may further establish one or more data radio bearers (DRBs) for the communication session. A data radio bearer is a logical communication on L2 and higher layers for transmitting data for a communication session. For example, the DRB carries dedicated traffic channel (DTCH) data for the communication session. The DRB may be established on the SRB using a radio bearer (RB) establishment procedure.

[0097] At 610, the source and target side link devices 602 and 604 may further use an NSA deployment to establish a side link on a second frequency band FR2 (e.g., millimeter wave band), as described above in connection with Figure 5 As described. For example, the FR2 side link may be established with the support of a side link previously established on FR1. Specifically, the SRB established on FR1 may be used to establish a DRB on FR2. In one example, the source side link device 602 may determine that a data stream for the target side link device 604 should be transmitted on FR2. In some examples, the source side link device 602 may determine that FR2 should be used for the data stream based on the following: the QoS of the data stream (e.g., data rate, throughput, latency, etc.), configuration information (e.g., provided by a network entity such as a base station or an application server), negotiation with the target side link device 604, and / or a specific QoS to side link radio bearer (SLRB) mapping.

[0098] Then, the source sidelink device 602 may transmit an RRC reconfiguration message on the SRB previously established on FR1 to initiate the establishment of the FR2 sidelink. For example, the RRC reconfiguration message transmitted on FR1 may be used to configure L2 and higher layers together with the millimeter wave PHY configuration for beam direction and resources, timing, position, and / or sequence parameters for the L1 / L2 protocol. Then, the source and target sidelink devices 602 and 604 may execute the PHY / MAC protocol in FR2 to select a BPL, perform synchronization, and establish the FR2 sidelink. For example, the source and target sidelink devices 602 and 604 may utilize the geographical location (e.g., GPS coordinates) and V2X data exchanged during the establishment of the FR1 sidelink to assist in selecting the BPL. Thus, signaling on the SRB on FR1 is used to establish the FR2 physical channel (FR2 sidelink) and add a new DRB on FR2.

[0099] After considering QoS constraints and priorities, the source sidelink device 602 may then determine to transmit a data packet (or data packets) to the target sidelink device 604 on the FR2 sidelink. At 612, the source sidelink device 602 may then generate a multicast resource reservation message and transmit it to the target sidelink device 604 and other neighboring sidelink devices 606 selected by the source sidelink device 602 to receive the multicast message. The multicast resource reservation message may be transmitted on FR1 and may be an RRC message in some examples. Thus, the multicast message may be addressed to each of the target sidelink device 604 and the selected other neighboring sidelink devices 606 and transmitted via the respective FR1 sidelinks between the source sidelink device 602 and each of the target sidelink device 604 and these other neighboring sidelink devices 606.

[0100] The multicast resource reservation message may include an indication of the reserved resources (e.g., time-frequency resources) reserved by the source sidelink device 602 within FR2 for future transmission of the data packet (or data packets) to the target sidelink device 604. These other neighboring sidelink devices 606 may utilize the multicast resource reservation message to manage interference on the reserved resources for additional sidelink communication. In some examples, the neighboring sidelink device 606 may avoid using the reserved resources for additional sidelink communication. For example, the neighboring sidelink device 606 may avoid reserving and / or scheduling resources within the reserved resources for additional sidelink transmission from the neighboring sidelink device 606 to another sidelink device (e.g., another neighboring sidelink device, or the source or target sidelink device).

[0101] At 614, the source sidelink device 602 may then generate a PSCCH including sidelink control information (SCI) and transmit the PSCCH on the FR2 sidelink. For example, the SCI may include scheduling information that indicates scheduled resources (e.g., time-frequency resources) within the reserved resources indicated by the multicast resource reservation message that are scheduled for data packet transmission on FR2. The SCI may further include HARQ information (e.g., HARQ ID and an indication of whether the data packet is a new data packet or a retransmitted data packet) and other link adaptation information such as modulation and coding scheme (MCS) and power control commands.

[0102] At 616, the source sidelink device 602 may then transmit a data packet to the target sidelink device 604 on the FR2 sidelink within a PSSCH. Specifically, the source sidelink device 602 may transmit the PSSCH on the scheduled resources indicated in the PSCCH. Additionally, the source sidelink device 602 may utilize the BPL selected in 610 based on the device location information shared in 608. In some examples, one or more reference signals (e.g., DMRS) may further be transmitted on the FR2 sidelink to enable channel estimation and feedback of channel state information (CSI). For example, the CSI may include a channel quality indicator (CQI), a precoding matrix index (PMI), and a rank indicator (RI) for MIMO communication.

[0103] At 618, the target sidelink device 604 may transmit an acknowledgement (ACK) or a negative acknowledgement (NACK) on the physical sidelink feedback control channel (PSFCH) based on the HARQ information. In some examples, the target sidelink device 604 may transmit the PSFCH on the FR2 sidelink.

[0104] Figure 7 is a signaling diagram illustrating an exemplary process for performing cross-link resource reservation for sidelink transmission between sidelink devices 702 and 704 in a V2X NSA deployment including, for example, sidelink devices 702 and 704 and other neighboring sidelink devices 706. The sidelink devices 702, 704, and 706 may correspond, for example, to Figure 5 and / or Figure 6 the sidelink devices shown in Figure 2 and / or Figure 7 the V2X devices shown in

[0105] At 708, the source and target sidelink devices 702 and 704 may initially establish a sidelink on a first frequency band FR1 (e.g., a sub-6 GHz band), as described above in connection with Figure 5 andFigure 6 As described. At 710, the source and target sidelink devices 702 and 704 may further use an NSA deployment to establish a sidelink on a second frequency band FR2 (e.g., millimeter wave frequency band), as described above in connection with Figure 5 and Figure 6 As described. For example, an FR2 sidelink may be established with the support of a sidelink previously established on FR1.

[0106] Then, the source sidelink device 702 may determine to transmit a data packet (or data packets) to the target sidelink device 704 on the FR2 sidelink. At 712, the source sidelink device 702 may then generate a unicast resource reservation message and transmit it to the target sidelink device 704 on the FR1 sidelink. The unicast resource reservation message may be, for example, an RRC message. The unicast resource reservation message may include an indication of the reserved resources (e.g., time-frequency resources) reserved by the source sidelink device 702 within FR2 for future transmission of the data packet (or data packets) to the target sidelink device 704.

[0107] At 714, the source sidelink device 702 may further generate a multicast resource reservation message and transmit it to other adjacent sidelink devices 706 selected by the source sidelink device 702 to receive the multicast message. The multicast resource reservation message may be transmitted on FR1 and may be an RRC message in some examples. Thus, the multicast message may be addressed to each of the selected other adjacent sidelink devices 706 and transmitted via the respective FR1 sidelinks between the source sidelink device 702 and each of these other adjacent sidelink devices 706. In some examples, the multicast resource reservation message may include the same information as the information in the unicast resource reservation message. In other examples, the multicast resource reservation message may include additional information based on the information included in the unicast resource reservation message. For example, the multicast resource reservation message may further include geographical location information associated with the source sidelink device 702 and the target sidelink device 704.

[0108] These other adjacent sidelink devices 706 may utilize the multicast resource reservation message to manage interference on the reserved resources for additional sidelink communication. In some examples, the adjacent sidelink device 706 may avoid using the reserved resources for additional sidelink communication. For example, the adjacent sidelink device 706 may avoid reserving and / or scheduling resources within the reserved resources for additional sidelink transmissions from the adjacent sidelink device 706 to another sidelink device (e.g., another adjacent sidelink device, or the source or target sidelink device).

[0109] At 716, the source sidelink device 702 may then generate a PSCCH including sidelink control information (SCI) and transmit the PSCCH on the FR2 sidelink. For example, the SCI may include scheduling information that indicates the scheduled resources (e.g., time-frequency resources) within the reserved resources indicated by the unicast / multicast resource reservation message that are scheduled for data packet transmission on FR2. The SCI may further include HARQ information (e.g., HARQ ID and an indication of whether the data packet is a new data packet or a retransmitted data packet) and other link adaptation information (such as modulation and coding scheme (MCS) and power control commands).

[0110] At 718, the source sidelink device 702 may then transmit a data packet to the target sidelink device 704 within a PSSCH on the FR2 sidelink. Specifically, the source sidelink device 702 may transmit the PSSCH on the scheduled resources indicated in the PSCCH. Additionally, the source sidelink device 702 may utilize the BPL selected in 710 based on the device location information shared in 708. In some examples, one or more reference signals (e.g., DMRS) may be further transmitted on the FR2 sidelink to enable channel estimation and feedback of channel state information (CSI). For example, the CSI may include a channel quality indicator (CQI), a precoding matrix index (PMI), and a rank indicator (RI) for MIMO communication.

[0111] At 720, the target sidelink device 704 may transmit an acknowledgement (ACK) or a negative acknowledgement (NACK) on the physical sidelink feedback control channel (PSFCH) based on the HARQ information. In some examples, the target sidelink device 704 may transmit the PSFCH on the FR2 sidelink.

[0112] In some examples, Figure 7 the unicast resource reservation message shown in Figure 6 or the multicast resource reservation message shown in

[0113] In some examples, Figure 7 the unicast resource reservation message shown in Figure 6The multicast resource reservation message shown in FIG. may be used as an activation or deactivation message for semi-persistent scheduling (SPS). SPS enables periodic scheduling information (e.g., periodic time-frequency resources) to be signaled only once on the PSCCH, and subsequently, without the need to transmit additional scheduling information, the sidelink device can utilize these periodic time-frequency resources for sidelink transmissions. The periodicity with which the sidelink device can transmit / receive data via the semi-persistent scheduled resources can be established when initially configuring the SPS assignment. Once the SPS assignment is configured, to start using the SPS assignment, the source sidelink device 602 / 702 may transmit an SPS activation message to activate the SPS assignment and enable the source sidelink device to utilize the SPS assignment.

[0114] In some examples, a resource reservation message (e.g., unicast or multicast) may be used as an SPS activation message to activate a previously configured SPS assignment that includes the reserved resources. In other examples, a resource reservation message (e.g., unicast or multicast) may be used as an SPS deactivation message to deactivate a previously configured SPS assignment that includes the reserved resources.

[0115] In some examples, the SPS assignment may be previously configured, for example, via RRC signaling on the FR1 sidelink based on expected data traffic on the FR2 sidelink. For example, the source sidelink device 602 / 702 may configure one or more SPS assignments on the FR2 sidelink via the FR1 sidelink based on expected data traffic on the FR2 sidelink, each SPS assignment having a different SPS schedule. In other examples, the SPS assignment may be configured, for example, based on a V2X application profile. For example, a V2X application running on the source sidelink device 602 / 702 may configure an SPS assignment for data traffic associated with the V2X application. In other examples, the SPS assignment may be configured, for example, for the occurrence of a V2X event (e.g., lane change, approaching an intersection, braking, etc.). In this example, the resource reservation message may then be transmitted as an SPS activation message upon the occurrence of a specific V2X event.

[0116] Figure 8FIG. is an example format diagram of a resource reservation message 800 that explains cross-link resource reservation for subsequent sidelink transmissions for one or more data packets. The resource reservation message 800 can be a unicast resource reservation message or a multicast resource reservation message. The resource reservation message 800 includes a source device identifier (ID) 802 that identifies the source sidelink device that generates and transmits the resource reservation message. The resource reservation message 800 further includes a destination device ID 804 that identifies the destination sidelink device for subsequent sidelink transmissions. In an example where the resource reservation message is a multicast resource reservation message, the resource reservation message 800 may further include the device IDs of each neighboring sidelink device to which the multicast message is directed.

[0117] The resource reservation message 800 further includes a time resource window 806 that indicates the start time and time duration reserved for subsequent sidelink transmissions. In some examples, the time resource window 806 may include a starting time slot number and an ending time slot number reserved for subsequent sidelink transmissions. In other examples, the time resource window 806 may include a starting time slot number and the number of sequential time slots after the starting time slot number reserved for subsequent sidelink transmissions. In still other examples, the time resource window 806 may include a starting OFDM symbol number within the starting time slot number and an ending OFDM symbol number within the ending time slot number.

[0118] The resource reservation message 800 further includes a set of frequency resources 808 (e.g., a group of frequency resources) reserved for subsequent sidelink transmissions within the time resource window 806. In some examples, the set of frequency resources may indicate a starting resource block within FR2 and the number of sequential resource blocks after the starting resource block within FR2 reserved for subsequent sidelink transmissions. In other examples, the set of frequency resources may indicate a starting resource block within FR2 and an ending resource block within FR2 reserved for subsequent sidelink transmissions.

[0119] In some examples, the time resource window 806 and the frequency resource set 808 correspond to at least one instance of the periodic time-frequency resources for SPS assignment. In this example, the time resource window 806 and the frequency resource set 808 may be previously configured via RRC signaling on the FR1 sidelink, and as such, including the time resource window 806 and the frequency resource set 808 may enable the target sidelink device to regard the resource reservation message as an SPS activation message. As another example, when the resource reservation message is an SPS activation message including, for example, an SPS activation indicator (not shown), the time resource window 806 and the frequency resource set 808 may be omitted from the resource reservation message. In other examples, the resource reservation message 800 may be used as an SPS deactivation message for an SPS assignment including the time resource window 806 and the frequency resource set 808. For example, by including the time resource window 806 and the frequency resource set 808 previously configured for the SPS assignment in the resource reservation message, the target sidelink device may regard the resource reservation message as an SPS deactivation message for the SPS assignment.

[0120] The resource reservation message 800 further includes an optional source device location 810 and an optional target device location 812. The source and target device locations 810 and 812 may include, for example, the physical geographical locations (e.g., coordinates) of the source sidelink device and the target sidelink device. In some examples, the source and target device locations 810 and 812 may be determined during a device discovery procedure performed for establishing an FR1 sidelink. In an example where the resource reservation message 800 is a unicast resource reservation message, the source and target device locations 810 and 812 may be omitted.

[0121] Figure 9 is a diagram illustrating exemplary reserved resources 904 and scheduled resources 906 for sidelink transmission. The reserved resources 904 include time-frequency resources reserved for subsequent sidelink transmissions, and the scheduled resources 906 include time-frequency resources within the reserved resources 904 that are scheduled for transmitting the PSCCH and PSSCH associated with the sidelink transmission. The target sidelink device may beamform towards the source sidelink device during the reserved resources 904 to receive the PSCCH and PSSCH on the scheduled resources 906.

[0122] The reserved resources 904 include a time resource window corresponding to a first number of time slots (e.g., time slots 902a–902c) reserved for subsequent sidelink transmissions and a first frequency resource set 908 corresponding to a first number of RBs reserved for subsequent sidelink transmissions. The scheduled resources 906 include a second number of time slots (e.g., time slots 902b and 902c) within the reserved resources 904 on which the PSCCH and PSSCH are transmitted and a second frequency resource set 910 (e.g., a second number of RBs). In Figure 9 the example shown, the scheduled resources 906 include fewer resources than all of the reserved resources 904 for sidelink transmissions. However, it should be understood that in other examples, the scheduled resources 906 may include all of the reserved resources 904.

[0123] Figure 10 is a block diagram illustrating an example of a hardware implementation of the sidelink device 1000 employing the processing system 1014. For example, the sidelink device 1000 may correspond to a UE or a V2X device as shown and described above with reference to Figure 1 , 2 , 5, 6, and / or 7.

[0124] The sidelink device 1000 may be implemented with a processing system 1014 that includes one or more processors 1004. Examples of the processor 1004 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, the sidelink device 1000 may be configured to perform any one or more of the functions described herein. That is, the processor 1004 utilized in the sidelink device 1000 may be used to implement any one or more of the processes and procedures described below.

[0125] In this example, the processing system 1014 may be implemented with a bus architecture generally represented by the bus 1002. Depending on the specific application and overall design constraints of the processing system 1014, the bus 1002 may include any number of interconnecting buses and bridges. The bus 1002 links together various circuits including one or more processors (generally represented by the processor 1004), a memory 1005, and a computer-readable medium (generally represented by the computer-readable medium 1006). The bus 1002 may also link various other circuits such as a timing source, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further herein.

[0126] The bus interface 1008 provides an interface between the bus 1002 and the transceiver 1010. The transceiver 1010 provides means for communicating with various other devices via a transmission medium (e.g., an air interface). Depending on the characteristics of the device, a user interface 1012 (e.g., a keypad, a display, a touch screen, speakers, a microphone, control knobs, etc.) may also be provided. Of course, such a user interface 1012 is optional and may be omitted in some examples.

[0127] The processor 1004 is responsible for managing the bus 1002 and general processing, including the execution of software stored on the computer-readable medium 1006. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or other terms. When executed by the processor 1004, the software causes the processing system 1014 to perform the various functions described below for any particular device. The computer-readable medium 1006 and the memory 1005 may also be used to store data manipulated by the processor 1004 when executing the software.

[0128] The computer-readable medium 1006 can be a non-transitory computer-readable medium. As an example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 1006 can reside within the processor system 1014, outside the processor system 1014, or be distributed across multiple entities including the processor system 1014. The computer-readable medium 1006 can be implemented in a computer program product. As an example, the computer program product can include the computer-readable medium in a packaging material. In some examples, the computer-readable medium 1006 can be part of the memory 1005. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0129] In some aspects of the present disclosure, processor 1004 may include circuitry configured for various functions. For example, processor 1004 may include sidelink manager circuitry 1020 configured to establish and manage one or more sidelinks. For example, sidelink manager circuitry 1020 may include communication and processing circuitry 1041 configured to communicate on a sidelink carrier via transceiver 1010 using an associated antenna and / or antenna array 1030 to exchange sidelink control information and sidelink data with other sidelink devices. In some examples, communication and processing circuitry 1041 may be configured to communicate with other sidelink devices on multiple sidelink carriers each associated with one or more sidelinks. For example, communication and processing circuitry 1041 may be configured to communicate on FR1 carriers (e.g., sub-6 GHz carriers) and FR2 carriers (e.g., millimeter wave carriers).

[0130] Each sidelink carrier may be divided in time into a plurality of radio frames, where each radio frame may be divided in time into a plurality of subframes and time slots, such as Figure 3 and Figure 9 the time slots shown in. In some examples, communication and processing circuitry 1041 may be configured to transmit a sidelink control channel (e.g., PSCCH) that may include sidelink control information (SCI) containing scheduled resources for data transmission. The PSCCH may further include a sidelink synchronization signal (S-SS), other control information, and / or pilot signals. Communication and processing circuitry 1041 may be further configured to transmit a sidelink data channel (e.g., PSSCH) that may include the data referenced in the PSCCH. In some examples, communication and processing circuitry 1041 may be configured to: transmit the PSCCH within a time slot on an FR2 carrier and transmit the PSSCH within one or more time slots on the FR2 carrier. Additionally, communication and processing circuitry 1041 may be further configured to receive a sidelink feedback channel (e.g., PSFCH) within a time slot on the FR2 carrier from another sidelink device.

[0131] In other examples, communication and processing circuitry 1041 may be configured to: transmit a sidelink control channel on an FR1 carrier and transmit the PSSCH within one or more time slots on the FR2 carrier. Additionally, communication and processing circuitry 1041 may be further configured to receive a sidelink feedback channel within a time slot on the FR1 carrier.

[0132] In an example where the sidelink device 1000 is the source sidelink device, the communication and processing circuitry 1041 may be further configured to transmit a resource reservation message on a FR1 carrier. The resource reservation message may indicate reserved resources on a FR2 carrier for subsequent transmissions of PSCCH and PSSCH to the target sidelink device. In some examples, the resource reservation message may include a multicast resource reservation message transmitted to two or more other sidelink devices (including the target sidelink device). In other examples, the resource reservation message may include both a unicast resource reservation message transmitted to the target sidelink device and a multicast resource reservation message transmitted to one or more neighboring sidelink devices other than the target sidelink device. In other examples, the resource reservation message may include a broadcast resource reservation message that may be broadcast to a plurality of receiving sidelink devices regardless of whether a corresponding sidelink has been established with each of these receiving sidelink devices.

[0133] In some examples, the unicast or multicast resource reservation message may be used as a paging message to the target sidelink device to activate the FR2 sidelink with the target sidelink device and wake up the target sidelink device for subsequent sidelink transmissions. In other examples, the unicast or multicast resource reservation message may be used as an activation message for semi-persistent scheduling (SPS) to activate a previously configured SPS assignment including the reserved resources, or as an SPS deactivation message to deactivate a previously configured SPS assignment including the reserved resources.

[0134] In other examples, the communication and processing circuitry 1041 may be further configured to transmit a resource reservation message on a FR2 carrier. In this example, the resource reservation message may indicate reserved resources on a FR1 carrier for subsequent transmissions of PSCCH and PSSCH to the target sidelink device. In an example implementation, the sidelink device 1000 may be aware of interference on the FR1 carrier and, thus, may determine to transmit the resource reservation message on the FR2 carrier to the target sidelink device to assist the target sidelink device in receiving PSCCH and PSSCH on the FR1 carrier. Other configurations and implementations that use FR2 to reserve resources on FR1 are within the scope of the present disclosure.

[0135] In an example where the sidelink device 1000 is a receiving sidelink device (e.g., a target or neighbor sidelink device), the communication and processing circuitry 1041 may be configured to receive a resource reservation message on an FR1 carrier via an FR1 sidelink with a source sidelink device. As a target sidelink device, the communication and processing circuitry 1041 may be further configured to receive a PSCCH within a time slot on an FR2 carrier via an FR2 sidelink with the source sidelink device. The communication and processing circuitry 1041 may be further configured to receive a PSSCH within a time slot on an FR2 carrier via an FR2 sidelink with the source sidelink device. Additionally, the communication and processing circuitry 1041 may be configured to transmit a PSFCH within a time slot on an FR2 carrier via an FR2 sidelink with the source sidelink device.

[0136] In other examples, the communication and processing circuitry 1041 may be further configured to receive a resource reservation message on an FR2 carrier via an FR2 sidelink with a source sidelink device. In this example, the resource reservation message may indicate reserved resources on the FR1 carrier for subsequent transmissions of PSCCH and PSSCH to the target sidelink device. Accordingly, the communication and processing circuitry 1041 may be further configured to: receive a PSCCH within a time slot on the FR1 carrier via an FR1 sidelink with the source sidelink device, and further receive a PSSCH within a time slot on the FR1 carrier via the FR1 sidelink. Additionally, the communication and processing circuitry 1041 may be further configured to transmit a PSFCH within a time slot on the FR1 carrier via the FR1 sidelink. The communication and processing circuitry 1041 may be further configured to execute communication and processing software 1051 stored on a computer-readable medium 1006 to implement one or more functions described herein.

[0137] The sidelink manager circuitry 1020 may further include sidelink establishment circuitry 1042, which is configured to establish one or more sidelinks with other sidelink devices on one or more sidelink carriers. In some examples, the sidelink establishment circuitry 1042 may be configured to establish an FR1 sidelink with a target sidelink device on an FR1 sidelink carrier (e.g., in a sub-6 GHz band), as described above in connection with Figure 5 、 6 and / or 7. In some examples, the FR1 sidelink may communicate with the target sidelink using an omnidirectional beam.

[0138] The sidelink establishment circuitry 1042 may be further configured to establish an FR2 sidelink with a target sidelink device on an FR2 sidelink carrier (e.g., in a millimeter wave band) using an NSA deployment, as described above in connection with Figure 5 、 6as described in and / or 7. For example, the FR2 sidelink with the target sidelink device may be established with the support of a sidelink previously established with the same target sidelink device on FR1. Specifically, the SRB established on FR1 may be used to establish the DRB on FR2. In some examples, the FR2 sidelink may communicate with the target sidelink device on the FR2 sidelink using directional beams.

[0139] After establishing the FR1 sidelink and the FR2 sidelink with the target sidelink device, the communication and processing circuitry 1041 may be configured to communicate on each of the FR1 sidelink and the FR2 sidelink to transmit resource reservation messages, PSCCH, and PSSCH to the target sidelink device, as discussed above. In some examples, the communication and processing circuitry 1041 may be further configured to transmit resource reservation messages to other neighboring sidelink devices within the range of the omnidirectional beam via the respective FR1 sidelinks with the neighboring sidelink devices. Additionally, the communication and processing circuitry 1041 may be configured to communicate with the neighboring sidelink devices via the respective directional FR2 beams and the FR2 sidelinks established by the sidelink establishment circuitry 1042. The sidelink establishment circuitry 1042 may be further configured to execute the sidelink establishment software 1052 stored on the computer-readable medium 1006 to implement one or more functions described herein.

[0140] The sidelink manager circuitry 1020 may further include resource assignment and scheduling circuitry 1043, which is configured to generate, schedule, and modify the reservation of time-frequency resources (e.g., a set including one or more RBs) for sidelink transmissions. For example, the resource assignment and scheduling circuitry 1043 may identify time-frequency resources on the FR2 carrier that may be reserved for subsequent sidelink transmissions to the target sidelink device. The reserved resources may include, for example, one or more time slots and one or more RBs on which the source sidelink device 1000 may subsequently transmit PSCCH and PSSCH to the target sidelink device. The resource assignment and scheduling circuitry 1043 may identify the reserved resources based on, for example, resource reservation messages received from other neighboring sidelink devices and / or PDCCH received from other neighboring sidelink devices indicating the scheduled resources on the FR2 carrier.

[0141] Then, the resource allocation and scheduling circuitry 1043 may schedule time-frequency resources on FR1 to carry resource reservation messages (e.g., RRC messages) to the target sidelink device and other neighboring sidelink devices, where the resource reservation message indicates the reserved resources on the FR2 carrier for subsequent sidelink transmissions to the target sidelink device. In some examples, the resource allocation and scheduling circuitry 1043 may schedule corresponding time-frequency resources on the FR1 carrier to transmit unicast resource reservation messages to the target sidelink device and multicast resource reservation messages to other neighboring sidelink devices. In other examples, the resource allocation and scheduling circuitry 1043 may schedule time-frequency resources on the FR1 carrier to transmit multicast resource reservation messages to both the target sidelink device and neighboring sidelink devices.

[0142] The resource allocation and scheduling circuitry 1043 may be further configured to schedule time-frequency resources within the reserved resources on the FR2 carrier to transmit PSCCH and PSSCH to the target sidelink device. Additionally, the resource allocation and scheduling circuitry 1043 may be further configured to schedule time-frequency resources for the target sidelink device to transmit PSFCH to the source sidelink device 1000. In some examples, the source sidelink device may schedule PSFCH resources. In other examples, the target sidelink device may schedule PSFCH resources. The resource allocation and scheduling circuitry 1043 may be further configured to: carry the resource reservation message on the FR1 carrier using an omnidirectional beam, and carry PSCCH and PSSCH on the FR2 carrier using a directional beam (e.g., a selected BPL). Similarly, the resource allocation and scheduling circuitry 1043 may be configured to: schedule resources on the FR1 carrier for transmitting the resource reservation message, and schedule resources within the reserved resources on the FR1 carrier for transmitting PSCCH and PSSCH and for transmitting PSFCH.

[0143] In some examples, the resource assignment and scheduling circuitry 1043 may be further configured to manage interference on the reserved resources indicated in a resource reservation message. For example, the resource assignment and scheduling circuitry 1043 may be configured to avoid scheduling another PSCCH and / or PSSCH within the reserved resources on the FR2 carrier. In some examples, the communication and processing circuitry 1041 may be configured to receive a resource reservation message transmitted by a source sidelink device on FR1 (e.g., via an FR1 sidelink between the source sidelink device and the sidelink device 1000). Then, the resource assignment and scheduling circuitry 1043 may avoid reserving the same resources for another sidelink transmission and / or scheduling another PSCCH and / or PSSCH within the reserved resources on the FR2 carrier indicated by the resource reservation message. The resource assignment and scheduling circuitry 1043 may be further configured to execute resource assignment and scheduling software 1053 stored on the computer-readable medium 1006 to implement one or more of the functions described herein.

[0144] The sidelink manager circuitry 1020 may further include beam management circuitry 1044, which is configured to select a particular beam (or BPL) for communication with another sidelink device. In some examples, the beam management circuitry 1044 may be configured to select an omnidirectional beam when communication is to be transmitted on FR1 and a BPL when communication is to be transmitted on FR2. In some examples, a particular BPL between the sidelink device 1000 and another sidelink device may be selected based on shared device location information exchanged between these sidelink devices during the establishment of the FR2 sidelink. The beam management circuitry 1044 may be further configured to execute beam management software 1054 stored on the computer-readable medium 1006 to implement one or more of the functions described herein.

[0145] The sidelink manager circuitry 1020 may further include SPS management circuitry 1045, which is configured to configure one or more SPS assignments for sidelink data such as V2X data. In some examples, the SPS management circuitry 1045 may be configured to operate in cooperation with the communication and processing circuitry 1041 and the resource assignment and scheduling circuitry 1043 to configure SPS assignments for sidelink data to be periodically communicated on the FR2 sidelink based on expected data traffic on the FR2 sidelink. In this example, the communication and processing circuitry 1041 together with the resource assignment and scheduling circuitry 1043 may configure SPS assignments on the source sidelink device and the target sidelink device via RRC signaling on the FR1 sidelink. The SPS assignment enables the communication and processing circuitry 1041 to periodically transmit sidelink data to the target sidelink device within the periodic resources reserved on the FR2 sidelink.

[0146] In some examples, the SPS management circuitry 1045 may instruct the communication and processing circuitry 1041, along with the resource assignment and scheduling circuitry 1043, to configure two or more SPS assignments on the FR2 sidelink via the FR1 sidelink based on the expected data traffic on the FR2 sidelink, each SPS assignment having a different SPS schedule. For example, the SPS management circuitry 1045 may configure the SPS assignments based on a V2X application profile (e.g., a profile of a V2X application stored in different memory devices such as the computer-readable medium 1006 or the sidelink device 1000). For example, the SPS management circuitry 1045 may configure the SPS assignments for the occurrence of a V2X event (e.g., lane change, approaching an intersection, braking, etc.) that can be detected by the V2X application.

[0147] After configuring the SPS assignments, the SPS management circuitry 1045 may then trigger the communication and processing circuitry 1041 to transmit an SPS activation message to activate the SPS assignments, such that the source sidelink device can transmit periodic sidelink data on the FR2 sidelink. In some examples, the communication and processing circuitry 1041 may transmit a resource reservation message, which serves as the SPS activation message. In this example, the periodic resources associated with the SPS assignment may include the reserved resources indicated by the resource reservation message. Thus, including the reserved resources in the resource reservation message may trigger the activation of the SPS assignment at the target sidelink device. In other examples, the resource reservation message may include an SPS activation indicator to specifically activate the SPS assignment. In this example, the resource reservation message may not include the reserved resources (e.g., the reserved resources were previously reserved during SPS configuration). In this example, the SPS management circuitry 1045 may trigger the transmission of the SPS activation message upon the occurrence of a specific V2X event associated with the SPS assignment.

[0148] The SPS management circuitry 1045 may further trigger the communication and processing circuitry 1041 to transmit an SPS deactivation message to deactivate the SPS assignments. In some examples, the communication and processing circuitry 1041 may transmit a resource reservation message, which serves as the SPS deactivation message. In this example, the periodic resources associated with the SPS assignment may include the reserved resources indicated by the resource reservation message. Thus, including the reserved resources in the resource reservation message may trigger the deactivation of the SPS assignment at the target sidelink device. In other examples, the resource reservation message may further include a specific SPS deactivation indicator to deactivate the SPS assignment and make the reserved resources available for other sidelink data. The SPS management circuitry 1045 may be further configured to execute the SPS management software 1055 stored on the computer-readable medium 1006 to implement one or more of the functions described herein.

[0149] The sidelink manager circuitry 1020 may further include a multicast device identification circuitry 1046 configured to identify and select other neighboring sidelink devices to receive multicast resource reservation messages. In some examples, the multicast device identification circuitry 1046 may select all neighboring sidelink devices having an active FR1 sidelink with the source sidelink device 1000 to receive the multicast resource reservation messages. In other examples, the multicast device identification circuitry 1046 selects neighboring sidelink devices to receive the multicast resource reservation messages based on the geographical location of each potential neighboring sidelink device (e.g., based on geographical location information exchanged during the establishment of the respective FR1 sidelink with each of these neighboring sidelink devices). In this example, the multicast device identification circuitry 1046 may select fewer neighboring sidelink devices than all other neighboring sidelink devices having an active FR1 sidelink with the source sidelink device 1000. For example, the multicast device identification circuitry 1046 may select other neighboring sidelink devices having an FR2 sidelink that may potentially interfere with the FR2 sidelink between the source sidelink device 1000 and the destination sidelink device. The multicast device identification circuitry 1046 may be further configured to execute a multicast device identification software 1056 stored on a computer-readable medium 1006 to implement one or more of the functions described herein.

[0150] Figure 11 is a flowchart 1100 of an exemplary method for wireless communication at a transmitting sidelink device. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be necessary for an implementation. In some examples, the method may be performed by the sidelink device 1000 as described above and illustrated in Figure 10 or by a processor or processing system, or by any suitable means for performing the described functions.

[0151] At block 1102, a first sidelink device (e.g., a transmitting sidelink device) may transmit a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message indicating reserved resources for the transmission of user data traffic (e.g., V2X data or other sidelink data) to a second sidelink device (e.g., a receiving sidelink device) on a second frequency band including a second carrier frequency. In some examples, the first frequency band may correspond to the FR1 frequency band (e.g., the sub-6 GHz band), and the second frequency band may correspond to the FR2 frequency band (e.g., the millimeter wave band). In other examples, the first frequency band may correspond to the FR2 frequency band, and the second frequency band may correspond to the FR1 frequency band.

[0152] In some examples, the resource reservation message can be a unicast message sent to a second sidelink device. In other examples, the resource reservation message can be a multicast message sent to the second sidelink device and other neighboring sidelink devices. In still other examples, the resource reservation message can include both a unicast message sent to the second sidelink device and a multicast or broadcast message sent to other neighboring devices. In some examples, the resource reservation message can be transmitted via an omnidirectional beam. In other examples, the resource reservation message can be transmitted via a directional beam (e.g., BPL) towards the second sidelink device.

[0153] In some examples, the resource reservation message can be used as a paging message to activate a second sidelink established with the second sidelink device on a second frequency band and wake up the second sidelink device. In this example, the first sidelink device can establish a first sidelink between the first sidelink device and the second sidelink device on a first frequency band. The first sidelink device can use the first sidelink at least in part to further establish the second sidelink. For example, the second sidelink can be established using the first sidelink based on, for example, a V2X NSA deployment.

[0154] In some examples, the resource reservation message can be used as an SPS activation or deactivation message. For example, the resource reservation message can be an SPS message that activates or deactivates a semi-persistent configured periodic resource assignment that includes the reserved resources. For example, in the resource assignment and scheduling circuitry 1043, communication and processing circuitry 1041, beam management circuitry 1044, sidelink establishment circuitry 1042, and transceiver 1010 shown and described above in connection with Figure 10 can generate and transmit the resource reservation message.

[0155] In block 1104, the first sidelink device can transmit a sidelink control channel (e.g., PSCCH) on the second frequency band, the sidelink control channel including an SCI associated with user data traffic to be transmitted to the second sidelink device on the second frequency band. The SCI can include scheduling information that indicates the scheduled resources within the reserved resources in which the user data traffic will be transmitted. In some examples, the PSCCH can be transmitted via a directional beam (e.g., BPL) towards the second sidelink device. In other examples, the PSCCH can be transmitted via an omnidirectional beam.

[0156] In some examples, the reserved resources can include a time resource window indicating a start time and a time duration and a frequency resource set indicating a start resource block and a number of resource blocks. In this example, the PSCCH can be transmitted during the time resource window and within the frequency resource set. For example, in the above in connection with Figure 10The resource assignment and scheduling circuitry 1043, communication and processing circuitry 1041, beam management circuitry 1044, and transceiver 1010 shown and described may generate a PSCCH and transmit it to a second sidelink device on a second frequency band.

[0157] In block 1106, a first sidelink device may transmit a sidelink data channel (e.g., PSSCH) including the user data traffic to a second sidelink device on a second frequency band. In some examples, the PSSCH may be transmitted via a directional beam (e.g., BPL) towards the second sidelink device. In other examples, the PSSCH may be transmitted via an omnidirectional beam. In some examples, the PSSCH may be transmitted within a time resource window and a frequency resource set indicated by a resource reservation message. For example, in connection with the Figure 10 resource assignment and scheduling circuitry 1043, communication and processing circuitry 1041, beam management circuitry 1044, and transceiver 1010 shown and described above may transmit the PSSCH to a second sidelink device on a second frequency band.

[0158] Figure 12 is a flowchart 1200 of an exemplary method for wireless communication at a receiving sidelink device. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be necessary for an implementation. In some examples, the method may be performed by a sidelink device 1000 as described above and illustrated in Figure 10 or by a processor or processing system, or by any suitable device for performing the described functions.

[0159] In block 1202, a first sidelink device (e.g., a receiving sidelink device) may receive a resource reservation message from a second sidelink device (e.g., a transmitting sidelink device) on a first frequency band including a first carrier frequency. The resource reservation message may include an indication of reserved resources on a second frequency band including a second carrier frequency for transmitting user data traffic (e.g., V2X data or other sidelink data) from the second sidelink device to a third sidelink device (e.g., a target sidelink device). In some examples, the first frequency band may correspond to a FR1 frequency band (e.g., a sub-6 GHz frequency band), and the second frequency band may correspond to a FR2 frequency band (e.g., a millimeter wave frequency band).

[0160] In some examples, the resource reservation message may be received as a multicast message transmitted to the target sidelink device of the user data traffic and other neighboring sidelink devices. In some examples, the resource reservation message may be received via an omnidirectional beam. For example, in connection with the Figure 10The communication and processing circuitry 1041 shown and described, along with the transceiver 1010, may receive a resource reservation message from a second sidelink device on a first frequency band.

[0161] At block 1204, the first sidelink device may manage interference on the reserved resources based on the resource reservation message. For example, the first sidelink device may avoid using the reserved resources for sidelink communication. As an example, the first sidelink device may avoid scheduling another PSCCH / PSSCH on the same FR2 resources indicated in the resource reservation message. For example, in the context of Figure 10 the resource allocation and scheduling circuitry 1043 shown and described may manage interference on the reserved resources for additional sidelink communication.

[0162] Figure 13 is a flowchart 1300 of another exemplary method for wireless communication at a receiving sidelink device. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be necessary for an implementation. In some examples, the method may be performed by a sidelink device 1000 as described above and illustrated in Figure 10 or by a processor or processing system, or by any suitable means for performing the described functions.

[0163] At block 1302, a first sidelink device (e.g., a receiving sidelink device) may receive a resource reservation message from a second sidelink device (e.g., a transmitting sidelink device) on a first frequency band including a first carrier frequency. The resource reservation message may include an indication of reserved resources on a second frequency band for transmitting user data traffic (e.g., V2X data or other sidelink data) from the second sidelink device to the first sidelink device. In some examples, the first frequency band may correspond to a FR1 frequency band (e.g., a sub-6 GHz band), and the second frequency band may correspond to a FR2 frequency band (e.g., a millimeter wave band). In other examples, the first frequency band may correspond to a FR2 frequency band, while the second frequency band may correspond to a FR1 frequency band.

[0164] In some examples, the resource reservation message may be received as a unicast message sent to the first sidelink device. In other examples, the resource reservation message may be received as a multicast message or a broadcast message sent to the first sidelink device and other neighboring sidelink devices. In some examples, the resource reservation message may be received via an omnidirectional beam. In other examples, the resource reservation message may be received via a directional beam (e.g., BPL).

[0165] In some examples, a resource reservation message can be used as a paging message to activate a second sidelink established with a second sidelink device on a second frequency band and wake up a first sidelink device. In this example, the first sidelink device can establish a first sidelink between the first sidelink device and the second sidelink device on a first frequency band. The first sidelink device can further establish the second sidelink at least in part using the first sidelink. For example, the second sidelink can be established using the first sidelink based on, for example, a V2X NSA deployment.

[0166] In some examples, a resource reservation message can be used as an SPS activation or deactivation message. For example, the resource reservation message can be an SPS message that activates or deactivates a semi-persistent configured periodic resource assignment that includes the reserved resources. For example, in the communication and processing circuitry 1041 shown and described above in connection with Figure 10 the transceiver 1010 can receive a resource reservation message from a second sidelink device on a first frequency band.

[0167] At block 1304, the first sidelink device can receive a sidelink control channel (e.g., PSCCH) on a second frequency band, the sidelink control channel including an SCI associated with user data traffic to be transmitted from the second sidelink device to the first sidelink device. The SCI can include scheduling information that indicates the scheduled resources within the reserved resources in which the user data traffic will be transmitted. In some examples, the reserved resources can include a time resource window indicating a start time and a time duration and a frequency resource set indicating a start resource block and a number of resource blocks. In this example, the PSCCH can be received during the time resource window and within the frequency resource set. In some examples, the first sidelink device can beamform towards the second sidelink device during the time resource window to receive the PSCCH using at least one directional beam. For example, in the communication and processing circuitry 1041, beam management circuitry 1044, and transceiver 1010 shown and described above in connection with Figure 10 can receive the PSCCH from the second sidelink device on a second frequency band.

[0168] At block 1306, the first sidelink device can receive a sidelink data channel (e.g., PSSCH) including the user data traffic from the second sidelink device on a second frequency band. In some examples, the PSSCH can be received during the time resource window and within the frequency resource set. In some examples, the first sidelink device can beamform towards the second sidelink device during the time resource window to receive the PSSCH using at least one directional beam. For example, in the communication and processing circuitry 1041 shown and described above in connection with Figure 10The communication and processing circuitry 1041, beam management circuitry 1044, and transceiver 1010 shown and described may receive a PSSCH from a second sidelink device on a second frequency band.

[0169] In one configuration, sidelink device 1000 includes means for performing the various functions and processes described with respect to Figure 11 - 13 In one aspect, the foregoing means may be the processor 1004 shown in Figure 10 and configured to perform the functions recited by the foregoing means. In another aspect, the foregoing means may be circuitry or any apparatus configured to perform the functions recited by the foregoing means.

[0170] Of course, in the above example, the circuitry included in processor 1004 is provided merely as an example, and other means for performing the described functions may be included within the various aspects of the present disclosure, including but not limited to instructions stored in computer-readable storage medium 1006, or in Figure 1 , 2 and / or any other suitable apparatus or device described in any of 4-7 and utilizing, for example, the processes and / or algorithms described herein with respect to Figure 11 - 13 described.

[0171] Certain aspects of a wireless communication network have been presented with reference to exemplary implementations. As will be readily appreciated by those skilled in the art, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0172] By way of example, the various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile communications (GSM). The various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wide Band (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the particular application and the overall design constraints imposed on the system.

[0173] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or superior to other aspects of the disclosure. Similarly, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to either a direct or an indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C may still be considered to be coupled to each other—even if they are not in direct physical contact with each other. For instance, a first object may be coupled to a second object even if the first object never directly physically contacts the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electronic devices and conductors and software implementations of information and instructions which, when connected and configured, enable the functions described in this disclosure without limitation as to the type of electronic circuit, and which, when executed by a processor, enable the various functions described in this disclosure.

[0174] Figure 1 - 13 One or more of the components, steps, features, and / or functions illustrated in 4 may be rearranged and / or combined into a single component, step, feature, or function, or implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2 The apparatus, devices, and / or components illustrated in 4 - 7 and / or 10 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and / or embedded in hardware.

[0175] It should be understood that the specific order or hierarchy of the steps in the disclosed methods is an illustration of exemplary processes. Based on design preferences, it should be understood that the specific order or hierarchy of the steps in these methods may be rearranged. The appended method claims present the elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented, unless specifically recited herein.

[0176] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein the recitation of a singular element is not intended to mean "one and only one" - unless specifically so stated - but rather "one or more." The term "some / a" refers to one or more unless specifically stated otherwise. The phrase reciting "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. Elements of the various aspects described throughout this disclosure that are presently known or later come to be known to those of ordinary skill in the art as all structural and functional equivalents are hereby expressly incorporated by reference and are intended to be covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims.

Claims

1. A method for wireless communication at a first sidelink device, the method comprising: Transmitting a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included within a sub-6 GHz band, and the second frequency band is included within a millimeter wave band; Transmitting a sidelink control channel within the reserved resources on the second frequency band, the sidelink control channel including sidelink control information (SCI) associated with user data traffic to be transmitted from the first sidelink device to a second sidelink device; And Transmitting a sidelink data channel including the user data traffic within the reserved resources on the second frequency band.

2. The method according to claim 1, wherein transmitting the resource reservation message on the first frequency band further comprises: Transmitting a unicast radio resource control (RRC) resource reservation message on the first frequency band to the second sidelink device; And Transmitting a multicast resource reservation message on the first frequency band to a set including one or more additional sidelink devices.

3. The method according to claim 1, wherein transmitting the resource reservation message on the first frequency band further comprises: Transmitting a multicast resource reservation message on the first frequency band to the second sidelink device and a set including one or more additional sidelink devices, such that the set including one or more additional sidelink devices avoids using the reserved resources for additional sidelink communication.

4. The method according to claim 1, wherein the reserved resources include a time resource window and a frequency resource set, wherein the time resource window includes a start time and a time duration, and the frequency resource set includes a start resource block and a number of resource blocks within the second frequency band.

5. The method according to claim 4, wherein the SCI includes scheduling information, the scheduling information including the scheduled resources within the reserved resources for transmitting the user data traffic.

6. The method according to claim 1, further comprising: Receiving a sidelink feedback channel from the second sidelink device on the second frequency band, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

7. The method according to claim 1, further comprising: Establishing a first sidelink with the second sidelink device on the first frequency band; And Establishing a second sidelink with the second sidelink device on the second frequency band at least in part using the first sidelink.

8. The method according to claim 7, further comprising: Using the resource reservation message to activate the second sidelink to wake up the second sidelink device.

9. The method according to claim 1, wherein the resource reservation message includes a semi-persistent scheduling (SPS) message for activating or deactivating a periodic resource assignment of a semi-persistent configuration, the periodic resource assignment of the semi-persistent configuration including the reserved resources for transmitting periodic user data traffic from the first sidelink device.

10. The method according to claim 9, further comprising: Triggering the transmission of the SPS message based on a vehicle-to-everything (V2X) application associated with the first sidelink device and the second sidelink device or in response to the occurrence of a V2X event.

11. The method according to claim 1, further comprising: Communicating with the second sidelink device on the first frequency band using an omnidirectional beam; And Communicating with the second sidelink device on the second frequency band using at least one directional beam.

12. The method according to claim 1, further comprising: Communicating with the second sidelink device on the first frequency band using at least one directional beam; And Communicating with the second sidelink device on the second frequency band using an omnidirectional beam.

13. A first sidelink device, comprising: A processor; A wireless transceiver communicatively coupled to the processor; And A memory communicatively coupled to the processor, wherein the processor is configured to: Transmit a resource reservation message on a first frequency band including a first carrier frequency via the wireless transceiver, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included within a sub-6 GHz band and the second frequency band is included within a millimeter wave band; Transmit a sidelink control channel within the reserved resources on the second frequency band via the wireless transceiver, the sidelink control channel including sidelink control information (SCI) associated with user data traffic to be transmitted from the first sidelink device to a second sidelink device; And Transmit a sidelink data channel including the user data traffic within the reserved resources on the second frequency band via the wireless transceiver.

14. The first sidelink device according to claim 13, wherein the processor is further configured to: Transmit a unicast radio resource control (RRC) resource reservation message to the second sidelink device on the first frequency band; and Transmit a multicast resource reservation message to a set including one or more additional sidelink devices on the first frequency band.

15. The first sidelink device according to claim 13, wherein the processor is further configured to: Transmit a multicast resource reservation message to the second sidelink device and a set including one or more additional sidelink devices on the first frequency band so that the set including one or more additional sidelink devices avoids using the reserved resources for additional sidelink communication.

16. The first sidelink device according to claim 13, wherein the processor is further configured to: Establish a first sidelink with the second sidelink device on the first frequency band; and At least partially utilize the first sidelink to establish a second sidelink with the second sidelink device on the second frequency band; and Activate the second sidelink using the resource reservation message to wake up the second sidelink device.

17. The first sidelink device according to claim 13, wherein the resource reservation message includes a semi-persistent scheduling (SPS) message for activating or deactivating periodic resource allocation of a semi-persistent configuration, and the periodic resource allocation of the semi-persistent configuration includes the reserved resources for transmitting periodic user data traffic from the first sidelink device.

18. A method for wireless communication at a first sidelink device, the method comprising: Receiving a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band and the second frequency band is included in a millimeter wave band; Receiving a sidelink control channel on the second frequency band, the sidelink control channel including sidelink control information (SCI) associated with user data traffic to be transmitted from a second sidelink device to the first sidelink device; And Receiving a sidelink data channel including the user data traffic on the second frequency band.

19. The method according to claim 18, wherein receiving the resource reservation message on the first frequency band further comprises: Receiving a radio resource control (RRC) message including the resource reservation message from the second sidelink device on the first frequency band.

20. The method according to claim 18, wherein receiving the resource reservation message on the first frequency band further comprises: Receiving a multicast message including the resource reservation message from the second sidelink device on the first frequency band, wherein the multicast message is further transmitted on the first frequency band to a set including one or more additional sidelink devices.

21. The method according to claim 18, wherein the reserved resources include a time resource window and a frequency resource set, wherein the time resource window includes a start time and a time duration, and the frequency resource set includes a start resource block and a number of resource blocks.

22. The method according to claim 21, wherein the SCI includes scheduling information, the scheduling information including the scheduled resources within the reserved resources for transmitting the user data traffic.

23. The method according to claim 21, further comprising: Beamforming towards the second sidelink device during the time resource window to receive the sidelink control channel and the sidelink data channel using at least one directional beam.

24. The method according to claim 18, further comprising: Transmitting a sidelink feedback channel to the second sidelink device on the second frequency band, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

25. The method according to claim 18, further comprising: Establishing a first sidelink with a second sidelink device on the first frequency band; And Establishing a second sidelink with the second sidelink device on the second frequency band at least in part using the first sidelink.

26. The method according to claim 25, further comprising: Wake up and activate the second sidelink in response to receiving the resource reservation message.

27. The method according to claim 18, wherein the resource reservation message includes a semi-persistent scheduling (SPS) message for activating or deactivating a periodic resource assignment with semi-persistent configuration, and the periodic resource assignment with semi-persistent configuration includes the reserved resources.

28. A method for wireless communication at a first sidelink device, the method comprising: Receiving, on a first frequency band including a first carrier frequency, a resource reservation message, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band and the second frequency band is included in a millimeter wave band, and Avoiding utilization of the reserved resources based on the resource reservation message.

29. The method according to claim 28, wherein receiving the resource reservation message on the first frequency band further comprises: Receiving, on the first frequency band, a multicast message including the resource reservation message from a second sidelink device.

30. A first sidelink device, comprising: Means for transmitting a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band and the second frequency band is included in a millimeter wave band; Means for transmitting a sidelink control channel within the reserved resources on the second frequency band, the sidelink control channel including sidelink control information (SCI) associated with user data traffic to be transmitted from the first sidelink device to a second sidelink device; And Means for transmitting a sidelink data channel including the user data traffic within the reserved resources on the second frequency band.

31. The first sidelink device according to claim 30, wherein the means for transmitting the resource reservation message on the first frequency band further comprises: Means for transmitting a unicast radio resource control (RRC) resource reservation message on the first frequency band to the second sidelink device; And Means for transmitting a multicast resource reservation message on the first frequency band to a set including one or more additional sidelink devices.

32. The first sidelink device according to claim 30, wherein the means for transmitting the resource reservation message on the first frequency band further comprises: Means for transmitting a multicast resource reservation message on the first frequency band to the second sidelink device and a set including one or more additional sidelink devices, such that the set including one or more additional sidelink devices can manage interference on the reserved resources for additional sidelink communication.

33. The first sidelink device according to claim 30, further comprising: Means for receiving a sidelink feedback channel on the second frequency band from the second sidelink device, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

34. The first sidelink device as claimed in claim 30, further comprising: means for communicating with the second sidelink device on the first frequency band using an omnidirectional beam; and means for communicating with the second sidelink device on the second frequency band using at least one directional beam.

35. The first sidelink device as claimed in claim 30, further comprising: means for communicating with the second sidelink device on the first frequency band using at least one directional beam; and means for communicating with the second sidelink device on the second frequency band using an omnidirectional beam.

36. A non-transitory computer-readable medium storing instructions that can be executed by one or more processors of a first sidelink device to perform the following operations: Transmit a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included within a sub-6 GHz band and the second frequency band is included within a millimeter wave band; Transmit a sidelink control channel within the reserved resources on the second frequency band, the sidelink control channel including sidelink control information SCI associated with user data traffic to be transmitted from the first sidelink device to a second sidelink device; and Transmit a sidelink data channel including the user data traffic within the reserved resources on the second frequency band.

37. The non-transitory computer-readable medium as claimed in claim 36, further comprising instructions that can be executed by the one or more processors of the first sidelink device to perform the following operations: Transmit a unicast radio resource control RRC resource reservation message to the second sidelink device on the first frequency band; and Transmit a multicast resource reservation message to a set including one or more additional sidelink devices on the first frequency band.

38. The non-transitory computer-readable medium as claimed in claim 36, further comprising instructions that can be executed by the one or more processors of the first sidelink device to perform the following operations: Transmit a multicast resource reservation message to the second sidelink device and a set including one or more additional sidelink devices on the first frequency band, such that the set including one or more additional sidelink devices can manage interference on the reserved resources for additional sidelink communication.

39. The non-transitory computer-readable medium as claimed in claim 36, further comprising instructions that can be executed by the one or more processors of the first sidelink device to perform the following operations: Receive a sidelink feedback channel from the second sidelink device on the second frequency band, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

40. The non-transitory computer-readable medium as claimed in claim 36, further comprising instructions that can be executed by the one or more processors of the first sidelink device to perform the following operations: Communicate with the second sidelink device on the first frequency band using an omnidirectional beam; and Communicate with the second sidelink device on the second frequency band using at least one directional beam.

41. The non-transitory computer-readable medium of claim 36, further comprising instructions executable by the one or more processors of the first sidelink device to: Communicate with the second sidelink device on the first frequency band using at least one directional beam; and Communicate with the second sidelink device on the second frequency band using an omnidirectional beam.

42. A first sidelink device, comprising: One or more memories; And One or more processors, the one or more processors being coupled to the one or more memories and configured to: Receive a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band and the second frequency band is included in a millimeter wave band; Receive a sidelink control channel on the second frequency band, the sidelink control channel including sidelink control information SCI associated with user data traffic to be transmitted from a second sidelink device to the first sidelink device; And Receive a sidelink data channel including the user data traffic on the second frequency band.

43. The first sidelink device of claim 42, further comprising: A transceiver coupled to the one or more processors, wherein the one or more processors are further configured to: Receive a radio resource control RRC message including the resource reservation message from the second sidelink device on the first frequency band via the transceiver.

44. The first sidelink device of claim 42, wherein the one or more processors are further configured to: Receive a multicast message including the resource reservation message from the second sidelink device on the first frequency band, wherein the multicast message is further transmitted on the first frequency band to a set including one or more additional sidelink devices.

45. The first sidelink device of claim 42, wherein the reserved resources include a time resource window and a frequency resource set, wherein the time resource window includes a start time and a time duration and the frequency resource set includes a start resource block and a number of resource blocks, and wherein the processor is further configured to: Beamform towards the second sidelink device during the time resource window to receive the sidelink control channel and the sidelink data channel using at least one directional beam.

46. The first sidelink device of claim 42, wherein the one or more processors are further configured to: Transmit a sidelink feedback channel to the second sidelink device on the second frequency band, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

47. A first sidelink device, comprising: Apparatus for receiving a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included within a sub-6 GHz band and the second frequency band is included within a millimeter wave band; Apparatus for receiving a sidelink control channel on the second frequency band, the sidelink control channel including sidelink control information SCI associated with user data traffic to be transmitted from a second sidelink device to the first sidelink device; and Apparatus for receiving a sidelink data channel including the user data traffic on the second frequency band.

48. The first sidelink device according to claim 47, further comprising: Apparatus for receiving a radio resource control RRC message including the resource reservation message from the second sidelink device on the first frequency band.

49. The first sidelink device according to claim 47, further comprising: Apparatus for receiving a multicast message including the resource reservation message from the second sidelink device on the first frequency band, wherein the multicast message is further transmitted on the first frequency band to a set including one or more additional sidelink devices.

50. The first sidelink device according to claim 47, wherein the reserved resources include a time resource window and a frequency resource set, wherein the time resource window includes a start time and a time duration and the frequency resource set includes a start resource block and a number of resource blocks, and wherein the first sidelink device further comprises: Apparatus for beamforming towards the second sidelink device during the time resource window to receive the sidelink control channel and the sidelink data channel using at least one directional beam.

51. The first sidelink device according to claim 47, further comprising: Apparatus for transmitting a sidelink feedback channel to the second sidelink device on the second frequency band, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

52. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a first sidelink device, cause the first sidelink device to perform the following operations: Receive a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included within a sub-6 GHz band and the second frequency band is included within a millimeter wave band; Receive a sidelink control channel on the second frequency band, the sidelink control channel including sidelink control information SCI associated with user data traffic to be transmitted from a second sidelink device to the first sidelink device; and Receive a sidelink data channel including the user data traffic on the second frequency band.

53. The non-transitory computer-readable medium according to claim 52, further comprising instructions that, when executed by the one or more processors of the first sidelink device, cause the first sidelink device to perform the following operations: Receive a radio resource control (RRC) message including the resource reservation message from the second sidelink device on the first frequency band.

54. The non-transitory computer-readable medium according to claim 52, further comprising instructions executable by the one or more processors of the first sidelink device to: Receive a multicast message including the resource reservation message from the second sidelink device on the first frequency band, wherein the multicast message is further transmitted on the first frequency band to a set including one or more additional sidelink devices.

55. The non-transitory computer-readable medium according to claim 52, wherein the reserved resources include a time resource window and a frequency resource set, wherein the time resource window includes a start time and a time duration and the frequency resource set includes a start resource block and a number of resource blocks, and further comprising instructions executable by the one or more processors of the first sidelink device to: Beamform towards the second sidelink device during the time resource window to receive the sidelink control channel and the sidelink data channel using at least one directional beam.

56. The non-transitory computer-readable medium according to claim 52, further comprising instructions executable by the one or more processors of the first sidelink device to: Transmit a sidelink feedback channel to the second sidelink device on the second frequency band, wherein the sidelink feedback channel includes feedback information corresponding to the user data traffic.

57. A first sidelink device, comprising: One or more memories; And One or more processors, the one or more processors being coupled to the one or more memories and configured to: Receive a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band, and the second frequency band is included in a millimeter wave band, and Avoid utilizing the reserved resources based on the resource reservation message.

58. The first sidelink device according to claim 57, further comprising: A transceiver coupled to the one or more processors, wherein the one or more processors are further configured to: Receive, via the transceiver, a multicast message including the resource reservation message from a second sidelink device on the first frequency band.

59. A first sidelink device, comprising: Means for receiving a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band, and the second frequency band is included in a millimeter wave band, and Means for avoiding utilizing the reserved resources based on the resource reservation message.

60. The first sidelink device according to claim 59, further comprising: Apparatus for receiving a multicast message including the resource reservation message from a second sidelink device on the first frequency band.

61. A non-transitory computer-readable medium storing instructions executable by one or more processors of a first sidelink device to perform the following operations: Receiving a resource reservation message on a first frequency band including a first carrier frequency, the resource reservation message including an indication of reserved resources on a second frequency band including a second carrier frequency, wherein the first frequency band is included in a sub-6 GHz band and the second frequency band is included in a millimeter wave band, and Avoiding utilization of the reserved resources based on the resource reservation message.

62. The non-transitory computer-readable medium of claim 61, further comprising instructions executable by the one or more processors of the first sidelink device to perform the following operation: Receiving a multicast message including the resource reservation message from a second sidelink device on the first frequency band.

Images