Patent Application
20220006505
Aspects of the present disclosure generally relate to wireless communications, and more particularly to techniques and apparatuses for vehicle-to-everything (V2X) sidelink beam failure recovery.
Wireless communications systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcasts. Typical wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunications standard is fifth generation (5G) new radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the fourth generation (4G) long term evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunications standards that employ these technologies.
Wireless communications systems may include or provide support for various types of communications systems, such as vehicle related communications systems (e.g., vehicle-to-everything (V2X) communications systems). Vehicle related communications systems may be used by vehicles to increase safety and to help prevent collisions of vehicles. Information regarding inclement weather, nearby accidents, road conditions, and/or other information may be conveyed to a driver via the vehicle related communications system. In some cases, sidelink user equipments (UEs), such as vehicles, may communicate directly with each other using device-to-device (D2D) communications over a D2D wireless link. These communications can be referred to as sidelink communications.
As the demands for sidelink communications increase, different V2X communications systems compete for the same wireless communications resources. Moreover, some sidelink UEs may be power limited. Accordingly, there is a need to improve the efficiency of sidelink wireless communications.
According to aspects of the present disclosure, a method of wireless communication by a first sidelink user equipment (UE) includes measuring multiple reference signals (RSs) periodically transmitted by a second sidelink UE using multiple receive beams corresponding to reference signals in response to a beam failure declared by the first UE. The method also includes selecting a reference signal of the plurality of reference signals that satisfies a condition. The method further includes notifying the second sidelink UE of the selected reference signal using a beam corresponding to the selected reference signal.
According to other aspects, a method of wireless communications by a first sidelink user equipment (UE) includes periodically transmitting, to a second sidelink UE, multiple beam failure recovery (BFR) reference signals (RSs) across multiple transmit beams. The method also includes receiving, from the second sidelink UE, an indication of a selected beam for communications between the first sidelink UE and the second sidelink UE. The method further includes notifying the second sidelink UE of successful beam failure recovery.
According to aspects of the present disclosure, a first sidelink user equipment (UE) includes means for measuring multiple reference signals (RSs) periodically transmitted by a second sidelink UE using multiple receive beams corresponding to reference signals in response to a beam failure declared by the first UE. The first sidelink UE also includes means for selecting a reference signal of the plurality of reference signals that satisfies a condition. The first sidelink UE also includes means for notifying the second sidelink UE of the selected reference signal using a beam corresponding to the selected reference signal.
According to other aspects, a first sidelink user equipment (UE) includes means for periodically transmitting, to a second sidelink UE, multiple beam failure recovery (BFR) reference signals (RSs) across multiple transmit beams. The first sidelink UE also includes means for receiving, from the second sidelink UE, an indication of a selected beam for communications between the first sidelink UE and the second sidelink UE. The first sidelink UE also includes means for notifying the second sidelink UE of successful beam failure recovery.
According to aspects of the present disclosure, an apparatus for wireless communication, in a first sidelink user equipment (UE), includes a processor, memory coupled with the processor, and instructions stored in the memory. The instructions are operable, when executed by the processor, to cause the apparatus to measure multiple reference signals (RSs) periodically transmitted by a second sidelink UE using multiple receive beams corresponding to reference signals in response to a beam failure declared by the first UE. The instructions also cause the apparatus to select a reference signal of the plurality of reference signals that satisfies a condition. The instructions also cause the apparatus to notify the second sidelink UE of the selected reference signal using a beam corresponding to the selected reference signal.
According to yet other aspects of the present disclosure, an apparatus for wireless communication, in a first sidelink user equipment (UE), includes a processor, memory coupled with the processor, and instructions stored in the memory. The instructions are operable, when executed by the processor, to cause the apparatus to periodically transmit, to a second sidelink UE, multiple beam failure recovery (BFR) reference signals (RSs) across multiple transmit beams. The instructions also cause the apparatus to receive, from the second sidelink UE, an indication of a selected beam for communications between the first sidelink UE and the second sidelink UE. The instructions also cause the apparatus to notify the second sidelink UE of successful beam failure recovery.
According to other aspects, a non-transitory computer-readable medium has program code recorded thereon. The program code is executed by a first sidelink user equipment (UE) and comprises program code to measure multiple reference signals (RSs) periodically transmitted by a second sidelink UE using multiple receive beams corresponding to reference signals in response to a beam failure declared by the first UE. The program code also comprises program code to select a reference signal of the plurality of reference signals that satisfies a condition. The program code also includes program code to notify the second sidelink UE of the selected reference signal using a beam corresponding to the selected reference signal.
According to still other aspects, a non-transitory computer-readable medium has program code recorded thereon. The program code is executed by a first sidelink user equipment (UE) and comprises program code to periodically transmit, to a second sidelink UE, multiple beam failure recovery (BFR) reference signals (RSs) across multiple transmit beams. The program code also comprises program code to receive, from the second sidelink UE, an indication of a selected beam for communications between the first sidelink UE and the second sidelink UE. The program code also comprises program code to notify the second sidelink UE of successful beam failure recovery.
Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communications device, and processing system as substantially described with reference to and as illustrated by the accompanying drawings and specification.
The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.
So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.
Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth. In addition, the scope of the disclosure is intended to cover such an apparatus or method, which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth. It should be understood that any aspect of the disclosure disclosed may be embodied by one or more elements of a claim.
Several aspects of telecommunications systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
It should be noted that while aspects may be described using terminology commonly associated with 5G and later wireless technologies, aspects of the present disclosure can be applied in other generation-based communications systems, such as and including 3G and/or 4G technologies.
In cellular communications networks, wireless devices may generally communicate with each other via one or more network entities such as a base station or scheduling entity. Some networks may support device-to-device (D2D) communications that enable discovery of, and communications with, nearby devices using a direct link between devices (e.g., without passing through a base station, relay, or another node). D2D communications can enable mesh networks and device-to-network relay functionality. Some examples of D2D technology include Bluetooth pairing, Wi-Fi Direct, Miracast, and LTE-D. D2D communications may also be referred to as point-to-point (P2P) or sidelink communications.
D2D communications may be implemented using licensed or unlicensed bands. Additionally, D2D communications can avoid the overhead involving the routing to and from the base station. Therefore, D2D communications may improve throughput, reduce latency, and/or increase energy efficiency.
A type of D2D communications may include vehicle-to-everything (V2X) communications. V2X communications may assist autonomous vehicles in communicating with each other. For example, autonomous vehicles may include multiple sensors (e.g., light detection and ranging (LiDAR), radar, cameras, etc.). In most cases, the autonomous vehicle's sensors are line of sight sensors. In contrast, V2X communications may allow autonomous vehicles to communicate with each other for non-line of sight situations.
Sidelink (SL) communications refers to the communications among user equipment (UEs) without tunneling through a base station (BS) and/or a core network. Sidelink communications may be communicated over a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH). The PSCCH and PSSCH are similar to a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) in downlink (DL) communications between a BS and a UE. For instance, the PSCCH may carry sidelink control information (SCI) and the PSSCH may carry sidelink data (e.g., user data). Each PSCCH is associated with a corresponding PSSCH, where SCI in a PSCCH may carry reservation and/or scheduling information for sidelink data transmission in the associated PSSCH. Use cases for sidelink communications may include, among others, vehicle-to-everything (V2X), industrial Internet of things (IIoT), and/or NR-lite.
Sidelink (SL) communications may occur in millimeter wave (mmWave) frequencies. Accordingly, beamforming is employed. With beamforming, a transmitting UE beam and a receiving UE beam should be aligned to create a sidelink channel for communications. When beams between communicating sidelink UEs become misaligned, a signal-to-noise ratio (SNR) drops, adversely impacting communications between the UEs. The beams may become misaligned due to movement of a UE or other changes in the environment, such as when a bus moves between two communicating UEs. It is desirable for a UE to detect the misalignment so the UE may initiate a beam failure recovery process. The beam failure recovery process includes discovering another set of beams to re-establish the sidelink connection between the sidelink UEs.
Beam failure recovery can occur in a number of ways, depending on a UE configuration. For example, a second UE (UE2) may have been configured by a first UE (UE1) with a sidelink contention free random access (SL-CFRA) resource for beam failure recovery. If an SL-CFRA resource is configured for beam failure recovery, UE1 periodically transmits beam failure recovery reference signals from a list of candidate reference signals. UE2 measures reference signals on the candidate list. If a reference signal on the candidate list has a received signal strength (e.g., RSRP (reference signal received power)) at or above a threshold, UE2 selects the reference signal with the signal strength at or above the threshold. UE2 transmits, to UE1, a random access channel (RACH) preamble, based on the selected reference signal and the corresponding transmit beam. Beam failure recovery is complete when the beam failure recovery preamble is received and acknowledged.
In other aspects of the present disclosure, an SL-CFRA resource may not be configured for beam failure recovery. In this case, or if beam failure recovery failed with SL-CFRA, SL-CBRA (sidelink-contention based random access) may occur. With SL-CBRA, UE1 periodically transmits SL SSBs (sidelink synchronization signal blocks), similar to when SL SSBs are transmitted for discovery and SL link establishment. UE2 selects a transmit-receive beam pair based on measuring the SL SSBs. UE2 may transmit to UE1 a SL RACH preamble in time and frequency resources corresponding to a desired beam pair. The UE2 beam used to transmit and the UE1 beam used to receive the SL RACH preamble is the desired beam pair corresponding to a best SL SSB received by UE2, such as the SL SSB with a highest RSRP, for example.
The base stations 102 configured for 4G LTE (collectively referred to as evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) may interface with the EPC 160 through backhaul links 132 (e.g., S1 interface). The base stations 102 configured for 5G NR (collectively referred to as next generation RAN (NG-RAN)) may interface with core network 190 through backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over backhaul links 134 (e.g., X2 interface). The backhaul links 134 may be wired or wireless.
The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communications coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102′ may have a coverage area 110′ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include home evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communications links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communications links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc., MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. The D2D communications link 158 may use the DL/UL WWAN spectrum. The D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communications may be through a variety of wireless D2D communications systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The small cell 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102′ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
A base station 102, whether a small cell 102′ or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmWave) frequencies, and/or near mmWave frequencies in communication with the UE 104. When the gNB 180 operates in mmWave or near mmWave frequencies, the gNB 180 may be referred to as an mmWave base station. Extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmWave may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmWave/near mmWave radio frequency band (e.g., 3 GHz-300 GHz) has extremely high path loss and a short range. The mmWave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180/UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting evolved MBMS (eMBMS) related charging information.
The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with a unified data management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides quality of service (QoS) flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP services 197. The IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and/or other IP services.
The base station 102 may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
Referring again to
Although the following description may be focused on 5G NR, it may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
Other wireless communications technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-S-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies μ 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols/slot and 2μ slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2{circumflex over ( )}μ*15 kHz, where μ is the numerology 0 to 5. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length/duration is inversely related to the subcarrier spacing.
A resource grid may represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
As illustrated in
As illustrated in
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the beam failure recovery component 198 of
In some aspects, the UE 104, 350 may include means for measuring, means for selecting, means for notifying, means for receiving, means for initiating, means for transmitting, means for declaring, and/or means for configuring. Such means may include one or more components of the UE 104, 350 described in connection with
The D2D communications system 400 may use NR radio access technology. Of course, other radio access technologies, such as LTE radio access technology, may be used. In D2D communications (e.g., V2X communications or vehicle-to-vehicle (V2V) communications), the UEs 450, 451 may be on networks of different mobile network operators (MNOs). Each of the networks may operate in its own radio frequency spectrum. For example, the air interface to a first UE 450 (e.g., Uu interface) may be on one or more frequency bands different from the air interface of the second UE 451. The first UE 450 and the second UE 451 may communicate via a sidelink component carrier, for example, via the PC5 interface. In some examples, the MNOs may schedule sidelink communications between or among the UEs 450, 451 in licensed radio frequency spectrum and/or a shared radio frequency spectrum (e.g., 5 GHz radio spectrum bands).
The shared radio frequency spectrum may be unlicensed, and therefore different technologies may use the shared radio frequency spectrum for communications. In some aspects, a D2D communications (e.g., sidelink communications) between or among UEs 450, 451 is not scheduled by MNOs. The D2D communications system 400 may further include a third UE 452.
The third UE 452 may operate on the first network 410 (e.g., of the first MNO) or another network, for example. The third UE 452 may be in D2D communications with the first UE 450 and/or second UE 451. The first base station 420 (e.g., gNB) may communicate with the third UE 452 via a downlink (DL) carrier 432 and/or an uplink (UL) carrier 442. The DL communications may be use various DL resources (e.g., the DL subframes (
The first network 410 operates in a first frequency spectrum and includes the first base station 420 (e.g., gNB) communicating at least with the first UE 450, for example, as described in
In some aspects, the second UE 451 may be on a different network from the first UE 450. In some aspects, the second UE 451 may be on a second network 411 (e.g., of the second MNO). The second network 411 may operate in a second frequency spectrum (e.g., a second frequency spectrum different from the first frequency spectrum) and may include the second base station 421 (e.g., gNB) communicating with the second UE 451, for example, as described in
The second base station 421 may communicate with the second UE 451 via a DL carrier 431 and an UL carrier 441. The DL communications are performed via the DL carrier 431 using various DL resources (e.g., the DL subframes (
In conventional systems, the first base station 420 and/or the second base station 421 assign resources to the UEs for device-to-device (D2D) communications (e.g., V2X communications and/or V2V communications). For example, the resources may be a pool of UL resources, both orthogonal (e.g., one or more frequency division multiplexing (FDM) channels) and non-orthogonal (e.g., code division multiplexing (CDM)/resource spread multiple access (RSMA) in each channel). The first base station 420 and/or the second base station 421 may configure the resources via the PDCCH (e.g., faster approach) or RRC (e.g., slower approach).
In some systems, each UE 450, 451 autonomously selects resources for D2D communications. For example, each UE 450, 451 may sense and analyze channel occupation during the sensing window. The UEs 450, 451 may use the sensing information to select resources from the sensing window. As discussed, one UE 451 may assist another UE 450 in performing resource selection. The UE 451 providing assistance may be referred to as the receiver UE or partner UE, which may potentially notify the transmitter UE 450. The transmitter UE 450 may transmit information to the receiving UE 451 via sidelink communications.
The D2D communications (e.g., V2X communications and/or V2V communications) may be carried out via one or more sidelink carriers 470, 480. The one or more sidelink carriers 470, 480 may include one or more channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH), for example.
In some examples, the sidelink carriers 470, 480 may operate using the PC5 interface. The first UE 450 may transmit to one or more (e.g., multiple) devices, including to the second UE 451 via the first sidelink carrier 470. The second UE 451 may transmit to one or more (e.g., multiple) devices, including to the first UE 450 via the second sidelink carrier 480.
In some aspects, the UL carrier 440 and the first sidelink carrier 470 may be aggregated to increase bandwidth. In some aspects, the first sidelink carrier 470 and/or the second sidelink carrier 480 may share the first frequency spectrum (with the first network 410) and/or share the second frequency spectrum (with the second network 411). In some aspects, the sidelink carriers 470, 480 may operate in an unlicensed/shared radio frequency spectrum.
In some aspects, sidelink communications on a sidelink carrier may occur between the first UE 450 and the second UE 451. In an aspect, the first UE 450 may perform sidelink communications with one or more (e.g., multiple) devices, including the second UE 451 via the first sidelink carrier 470. For example, the first UE 450 may transmit a broadcast transmission via the first sidelink carrier 470 to the multiple devices (e.g., the second and third UEs 451, 452). The second UE 451 (e.g., among other UEs) may receive such broadcast transmission. Additionally or alternatively, the first UE 450 may transmit a multicast transmission via the first sidelink carrier 470 to the multiple devices (e.g., the second and third UEs 451, 452). The second UE 451 and/or the third UE 452 (e.g., among other UEs) may receive such multicast transmission. The multicast transmissions may be connectionless or connection-oriented. A multicast transmission may also be referred to as a groupcast transmission.
Furthermore, the first UE 450 may transmit a unicast transmission via the first sidelink carrier 470 to a device, such as the second UE 451. The second UE 451 (e.g., among other UEs) may receive such unicast transmission. Additionally or alternatively, the second UE 451 may perform sidelink communications with one or more (e.g., multiple) devices, including the first UE 450 via the second sidelink carrier 480. For example, the second UE 451 may transmit a broadcast transmission via the second sidelink carrier 480 to the multiple devices. The first UE 450 (e.g., among other UEs) may receive such broadcast transmission.
In another example, the second UE 451 may transmit a multicast transmission via the second sidelink carrier 480 to the multiple devices (e.g., the first and third UEs 450, 452). The first UE 450 and/or the third UE 452 (e.g., among other UEs) may receive such multicast transmission. Further, the second UE 451 may transmit a unicast transmission via the second sidelink carrier 480 to a device, such as the first UE 450. The first UE 450 (e.g., among other UEs) may receive such unicast transmission. The third UE 452 may communicate in a similar manner.
In some aspects, for example, such sidelink communications on a sidelink carrier between the first UE 450 and the second UE 451 may occur without having MNOs allocating resources (e.g., one or more portions of a resource block (RB), slot, frequency band, and/or channel associated with a sidelink carrier 470, 480) for such communications and/or without scheduling such communications. Sidelink communications may include traffic communications (e.g., data communications, control communications, paging communications and/or system information communications). Further, sidelink communications may include sidelink feedback communications associated with traffic communications (e.g., a transmission of feedback information for previously-received traffic communications). Sidelink communications may employ at least one sidelink communications structure having at least one feedback symbol. The feedback symbol of the sidelink communications structure may allot for any sidelink feedback information that may be communicated in the device-to-device (D2D) communications system 400 between devices (e.g., a first UE 450, a second UE 451, and/or a third UE 452). As discussed, a UE may be a vehicle (e.g., UE 450, 451), a mobile device (e.g., 452), or another type of device. In some cases, a UE may be a special UE, such as a road side unit (RSU).
In the scheme 600, a shared radio frequency band 601 is partitioned into multiple subchannels or frequency subbands 602 (shown as 602S0, 602S1, 602S2) in frequency and multiple sidelink frames 604 (shown as 604a, 604b, 604c, 604d) in time for sidelink communications. The frequency band 601 may be at any suitable frequencies, such as millimeter wave frequencies. The frequency band 601 may have any suitable bandwidth (BW) and may be partitioned into any suitable number of frequency subbands 602. The number of frequency subbands 602 can be dependent on the sidelink communications BW requirement.
Each sidelink frame 604 includes a sidelink resource 606 in each frequency subband 602. A legend 605 indicates the types of sidelink channels within a sidelink resource 606. In some instances, a frequency gap or guard band may be specified between adjacent frequency subbands 602, for example, to mitigate adjacent band interference. The sidelink resource 606 may have a substantially similar structure as an NR sidelink resource. For instance, the sidelink resource 606 may include a number of subcarriers or RBs in frequency and a number of symbols in time. In some instances, the sidelink resource 606 may have a duration between about one millisecond (ms) to about 20 ms. Each sidelink resource 606 may include a PSCCH 610 and a PSSCH 620. The PSCCH 610 and the PSSCH 620 can be multiplexed in time and/or frequency. In the example of
The PSCCH 610 may carry SCI 660 and/or sidelink data. The sidelink data can be of various forms and types depending on the sidelink application. For instance, when the sidelink application is a V2X application, the sidelink data may carry V2X data (e.g., vehicle location information, traveling speed and/or direction, vehicle sensing measurements, etc.). Alternatively, when the sidelink application is an IIoT application, the sidelink data may carry IIoT data (e.g., sensor measurements, device measurements, temperature readings, etc.). The PSFCH can be used for carrying feedback information, for example, HARQ ACK/NACK for sidelink data received in an earlier sidelink resource 606.
In an NR sidelink frame structure, the sidelink frames 604 in a resource pool 608 may be contiguous in time. A sidelink UE (e.g., the UEs 104) may include, in SCI 660, a reservation for a sidelink resource 606 in a later sidelink frame 604. Thus, another sidelink UE (e.g., a UE in the same NR-U sidelink system) may perform SCI sensing in the resource pool 608 to determine whether a sidelink resource 606 is available or occupied. For instance, if the sidelink UE detected SCI indicating a reservation for a sidelink resource 606, the sidelink UE may refrain from transmitting in the reserved sidelink resource 606. If the sidelink UE determines that there is no reservation detected for a sidelink resource 606, the sidelink UE may transmit in the sidelink resource 606. As such, SCI sensing can assist a UE in identifying a target frequency subband 602 to reserve for sidelink communications and to avoid intra-system collision with another sidelink UE in the NR sidelink system. In some aspects, the UE may be configured with a sensing window for SCI sensing or monitoring to reduce intra-system collision.
In some aspects, the sidelink UE may be configured with a frequency hopping pattern. In this regard, the sidelink UE may hop from one frequency subband 602 in one sidelink frame 604 to another frequency subband 602 in another sidelink frame 604. In the illustrated example of
The SCI can also indicate scheduling information and/or a destination identifier (ID) identifying a target receiving sidelink UE for the next sidelink resource 606. Thus, a sidelink UE may monitor SCI transmitted by other sidelink UEs. Upon detecting SCI in a sidelink resource 606, the sidelink UE may determine whether the sidelink UE is the target receiver based on the destination ID. If the sidelink UE is the target receiver, the sidelink UE may proceed to receive and decode the sidelink data indicated by the SCI. In some aspects, multiple sidelink UEs may simultaneously communicate sidelink data in a sidelink frame 604 in different frequency subband (e.g., via frequency division multiplexing (FDM)). For instance, in the sidelink frame 604b, one pair of sidelink UEs may communicate sidelink data using a sidelink resource 606 in the frequency subband 602S2 while another pair of sidelink UEs may communicate sidelink data using a sidelink resource 606 in the frequency subband 602S1.
In some aspects, the scheme 600 is used for synchronous sidelink communications. That is, the sidelink UEs may be synchronized in time and are aligned in terms of symbol boundary, sidelink resource boundary (e.g., the starting time of sidelink frames 604). The sidelink UEs may perform synchronization in a variety of forms, for example, based on sidelink SSBs received from a sidelink UE and/or NR-U SSBs received from a BS (e.g., the BSs 105 and/or 205) while in-coverage of the BS. In some aspects, the sidelink UE may be preconfigured with the resource pool 608 in the frequency band 601, for example, while in coverage of a serving BS. The resource pool 608 may include a plurality of sidelink resources 606. The BS can configure the sidelink UE with a resource pool configuration indicating resources in the frequency band 601 and/or the subbands 602 and/or timing information associated with the sidelink frames 604. In some aspects, the scheme 600 includes mode-2 radio resource allocation (RRA) (e.g., supporting autonomous RRA that can be used for out-of-coverage sidelink UEs or partial-coverage sidelink UEs).
Sidelink communications may occur in millimeter wave (mmWave) frequencies. Accordingly, beamforming is employed. With beamforming, a transmitting UE beam and a receiving UE beam should be aligned to create a sidelink channel for communications. When beams between communicating sidelink UEs become misaligned, a signal-to-noise ratio (SNR) drops, adversely impacting communications between the UEs. The beams may become misaligned due to movement of a UE or other changes in the environment, such as when a vehicle moves between two communicating UEs. It is desirable for a UE to detect the misalignment so the UE may initiate a beam failure recovery process. The beam failure recovery process includes discovering another set of beams to re-establish the sidelink connection between the sidelink UEs.
When a sidelink channel between UE1 and UE2 changes or if one or both of UE1 and UE2 move, the sidelink beams 710, 720 will not be aligned, resulting in the UEs not being able to communicate. Aspects of the present disclosure include techniques to recover when sidelink beams are not aligned. The beam failure recovery process may include discovering another set of beams to re-establish the sidelink connection. This process is referred to as beam failure recovery (BFR).
Beam failure recovery may occur in a number of ways, depending on a UE configuration. For example, UE2 may have been configured by UE1 with a sidelink contention free random access (SL-CFRA) resource for the purpose of beam failure recovery. If an SL-CFRA resource is configured for beam failure recovery, UE1 periodically transmits beam failure recovery reference signals from a list of reference signals (e.g., slCandidateBeamRsList). Each reference signal in the candidate list is transmitted on a certain beam, though not necessarily the same set of beams used to transmit BFD reference signals. The reference signals on the list may be an SL SSB (sidelink synchronization signal block) or an SL CSI-RS (sidelink channel state information-reference signal), in some examples.
Beam failure recovery from a perspective of UE2 includes setting a beam failure recovery (BFR) timer in response to triggering beam failure recovery. UE2 then monitors for reference signals on the candidate list. UE2 may use multiple beams to attempt to receive the reference signals on the list. The beams may not necessarily be the same beams used to receive BFD reference signals. If an SL SSB or SL CSI-RS on the candidate list has a received signal strength (e.g., RSRP) at or above a threshold (e.g., rsrpThresholdSSB or rsrpThresholdCSI-RS), UE2 selects the reference signal with the signal strength at or above the threshold and the corresponding beam used to receive the reference signal.
UE2 sets a random access channel (RACH) preamble, if configured, for the selected reference signal. The SL RACH location associated with the selected SL SSB or SL CSI-RS is used to send the RACH preamble. If UE2 selects a CSI-RS, UE2 may use a random access occasion list or RACH location corresponding to the SL SSB (from the candidate list of reference signals), which is quasi-collocated with the selected CSI-RS. That is, if UE2 selected a CSI-RS, UE2 may set the RACH preamble based on a quasi-collocated SL SSB. UE2 transmits the RACH preamble using the beam corresponding to the selected reference signal, and UE1 uses the beam associated with the RACH occasion corresponding to the chosen reference signal to receive the RACH preamble.
Beam failure recovery is successfully complete when the beam failure recovery preamble is received and acknowledged. For example, UE1 may transmit to UE2, a scrambled physical sidelink control channel (PSCCH), in response to UE2 transmitting the SL RACH preamble. The PSCCH may be scrambled with a cell-radio network temporary identifier (C-RNTI) or may be scrambled with another parameter. The BFR timer is stopped upon successful beam failure recovery. If, however, UE2 does not receive the PSCCH from UE1 before the BFR timer expires (e.g., beam failure recovery failed), UE2 may initiate beam failure recovery without SL-CFRA, as described next.
In some aspects of the present disclosure, an SL-CFRA resource may not be configured for BFR. In this case, or if beam failure recovery failed with SL-CFRA, SL-CBRA (sidelink-contention based random access) beam failure recovery may occur. With SL-CBRA beam failure recovery, it is assumed that UE1 periodically transmits SL SSBs, similar to when the SL SSBs are transmitted for the purpose of discovery and SL link establishment (e.g., during initial access). The SL SSBs are transmitted with a transmit beam sweep (e.g., with multiple different beams), and UE2 selects a transmit-receive beam pair based on measuring the SL SSBs. For example, UE2 may perform a receive beam sweep for the SL SSBs.
Upon selecting a desired transmit-receive beam pair, the UE2 may transmit an SL RACH preamble in time and frequency resources associated with a reference signal on the desired beam. The desired beam may correspond to a best SL SSB that UE2 received. The best SL SSB may be an SL SSB with a highest RSRP, for example.
According to aspects of the present disclosure, preambles may be based on groupings. For example, the set of all preambles may be divided into two groups. A first group may be associated with beam failure recovery, and a second group may be associated with discovery and sidelink establishment. UE2 may select a preamble from a first group to indicate the SL RACH transmission is for beam failure recovery.
Beam failure recovery is successfully complete when the beam failure recovery preamble is received and acknowledged. For example, UE1 may transmit to UE2, a scrambled PSCCH in response to UE2 transmitting the SL RACH. The PSCCH may be scrambled with a cell-radio network temporary identifier (C-RNTI) or may be scrambled with another parameter. If UE2 does not receive the PSCCH from UE1, UE2 declares radio link failure (RLF).
UE1 is configured to transmit SL SSB1 and SL CSI-RS1 to UE2 for beam failure recovery, using transmit beams 908, 910. UE1 selects SL SSB1 and SL CSI-RS1 based on previous measurement reports from UE2. UE1 is configured to monitor SL CFRA time and frequency resources corresponding to SL SSB1 and SL CSI-RS1 for a beam failure recovery RACH preamble from UE2.
UE2 measures the reference signals from the candidate list. At time t1, both reference signals (SL SSB1 and SL CSI-RS1) are received with a signal strength below a threshold on receive (Rx) beam one. At time t2, however, UE2 receives SSB1 on receive beam two with a signal strength above the threshold.
Accordingly, at time t3, UE2 selects a sidelink random access channel (SL RACH) preamble for the selected reference signal, SSB1. The SL RACH location associated with the selected SL SSB is used to send the RACH preamble. As a result of receiving the preamble, UE1 becomes aware of which reference signal UE2 selected based on the time and frequency resources of the RACH preamble. UE1 thus selects the Tx/Rx beam(s) associated with SSB1 for sidelink communication with UE2.
At time t4, UE1 transmits to UE2 a cell-radio network temporary identifier (C-RNTI) scrambled PSCCH in response to UE2 transmitting the SL RACH. Beam failure recovery is deemed successful at time t5, when the beam failure recovery preamble is received and acknowledged, that is upon UE2's receipt of the scrambled PSCCH. In the example of
According to further aspects of the present disclosure, transmission of the beam failure recovery reference signals from the candidate list may be semi-persistent or on demand, instead of always on or periodic, to save resources. In this case, when beam failure is detected, UE2 may send a message to a base station. In response, the base station sends the message to UE1 to trigger UE1 to transmit the beam failure recovery reference signals from the candidate list. Thus, the reference signals are not always transmitted, saving resources.
In other aspects, when UE1 detects beam failure, UE1 may start transmitting reference signals from the candidate list. This may be possible when both UE1 and UE2 transmit beam failure detection reference signals. Such a configuration may occur when the transmit and receive beams for UE1 are different from one another.
As indicated above,
In some aspects, the process 1200 may select a reference signal of the multiple of reference signals that satisfies a condition (block 1204). For example, the UE (e.g., using the controller/processor 359, and/or memory 360) may select the RS and beam. The UE may select the reference signal by selecting one of the SL SSBs with a highest reference signal receive power (RSRP) and select a beam corresponding to the selected SL SSB.
In some aspects, the process 1200 may notify the second sidelink UE of the selected reference signal using a beam corresponding to the selected reference signal (block 1206). For example, the UE (e.g., using the antenna 352, RX/TX 354, TX processor 368, controller/processor 359, and/or memory 360) may notify the second sidelink UE. The UE may select the beam in response to the reference signal having a reference signal received power (RSRP) at or above a threshold level. The reference signal having the RSRP at or above the threshold level is indicated in a candidate list. In some aspects, the second UE is configured for sidelink contention free random access (SL-CFRA). The UE may notify the second sidelink UE of the reference signal having the RSRP at or above the threshold level with a sidelink random access channel (RACH) preamble at a time and frequency location corresponding to the reference signal having the RSRP above the threshold level.
The process 1300 may include receiving, from the second sidelink UE, an indication of a selected beam for communications between the first sidelink UE and the second sidelink UE (block 1304). For example, the UE (e.g., using the antenna 352, RX/TX 354, RX processor 356, controller/processor 359, and/or memory 360) may periodically receive the indication. The indication may be a sidelink random access channel (RACH) preamble, which may be associated with a group of preambles indicating the RACH preamble is related to beam failure recovery.
In some aspects, the process 1300 may notify the second sidelink UE of successful beam failure recovery (block 1306). For example, the UE (e.g., using the controller/processor 359 and/or memory 360) may notify the second sidelink UE. The notifying may be with a scrambled physical sidelink control channel (PSCCH).
Implementation examples are described in the following numbered clauses.
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.
As used, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used, a processor is implemented in hardware, firmware, and/or a combination of hardware and software.
Some aspects are described in connection with thresholds. As used, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.
It will be apparent that systems and/or methods described may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
No element, act, or instruction used should be construed as critical or essential unless explicitly described as such. Also, as used, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used, the terms “has,” “have,” “having,” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
The present application claims the benefit of U.S. Provisional Patent Application No. 63/047,820, filed on Jul. 2, 2020, and titled “SIDELINK BEAM FAILURE RECOVERY,” the disclosure of which is expressly incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63047820 | Jul 2020 | US |
