Patent Application
20240430938
The following relates to wireless communications, including random access channel occasion selection.
Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).
The described techniques relate to improved methods, systems, devices, and apparatuses that support random access channel (RACH) occasion (RO) selection. For example, the described techniques provide for a user equipment (UE) to receive or otherwise obtain a downlink signal (e.g., synchronization signal block (SSB)) from a network entity. The downlink signal may be associated with a set of available ROs (e.g., more than one RO associated with each SSB), with each RO in the set defining the resource set (e.g., time/frequency resources, frequency shift, etc.). The UE may perform a RACH procedure with the network entity using at least one RO associated with the downlink signal. In some examples, each RO in the set may be based on a received power level of the downlink signal at the UE. For example, the UE may estimate the received power level of the downlink signal and select a RO from the set that corresponds to the received power level.
A method for wireless communications by a user equipment (UE) is described. The method may include receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity and performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to receive a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity and perform the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
Another UE for wireless communications is described. The UE may include means for receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity and means for performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity and perform the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
Some examples of the method, UE, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for selecting the at least one RO from the set of available ROs based on a received signal strength of the downlink signal.
Some examples of the method, UE, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for selecting, based on the at least one RO, a RACH sequence from a set of available RACH sequences.
Some examples of the method, UE, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for receiving an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs.
In some examples of the method, UE, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for identifying, based on the indication, a time index for each ROs in the set of available ROs, a frequency shift associated with each time index, a random access procedure sequence length, or a combination thereof.
In some examples of the method, UE, and non-transitory computer-readable medium described herein, performing the random access procedure using the at least one RO may include operations, features, means, code, or instructions for backscattering a continuous waveform signal received from the network entity via the resource set defined by the at least one RO, where the backscattering may be based on the continuous waveform signal.
In some examples of the method, UE, and non-transitory computer-readable medium described herein, the resource set defined by the at least one RO includes a frequency resource, a time resource, or both, that may be different than corresponding resource sets defined by a subset of remaining ROs of the set of available ROs.
In some examples of the method, UE, and non-transitory computer-readable medium described herein, the downlink signal includes at least one of a SSB signal, a master information block (MIB) signal, a secondary information block (SIB) signal, a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH) signal, a previously received downlink signal from the network entity, a set of downlink signals received within a time interval, or a combination thereof.
A method for wireless communications by a network entity is described. The method may include transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE and performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to transmit a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE and perform the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
Another network entity for wireless communications is described. The network entity may include means for transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE and means for performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE and perform the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
Some examples of the method, network entity, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for selecting the resource set defined by each RO may be based on a UE distribution pattern for a set of UE located proximate to the network entity.
In some examples of the method, network entity, and non-transitory computer-readable medium described herein, each RO from the set of available ROs may be associated with a received signal strength of the downlink signal at the UE.
Some examples of the method, network entity, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for performing, based on the at least one RO, the random access procedure with the UE using a RACH sequence from a set of available RACH sequences.
Some examples of the method, network entity, and non-transitory computer-readable medium described herein may further include operations, features, means, code, or instructions for transmitting an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs.
In some examples of the method, network entity, and non-transitory computer-readable medium described herein, the indication identifies a time index for each ROs in the set of available ROs, a frequency shift associated with each time index, a random access procedure sequence length, or a combination thereof.
In some examples of the method, network entity, and non-transitory computer-readable medium described herein, performing the random access procedure using the at least one RO may include operations, features, means, code, or instructions for receiving a backscattered continuous waveform signal from the UE via the resource set defined by the at least one RO.
In some examples of the method, network entity, and non-transitory computer-readable medium described herein, the resource set defined by the at least one RO includes a frequency resource, a time resource, or both, that may be different than corresponding resource sets defined by a subset of remaining ROs of the set of available ROs.
In some examples of the method, network entity, and non-transitory computer-readable medium described herein, the downlink signal includes at least one of a SSB signal, a MIB signal, a SIB signal, an PSS, an SSS, a PBCH signal, a previously received downlink signal from the network entity, a set of downlink signals received within a time interval, or a combination thereof.
Wireless networks may include broadcast transmissions supporting random access procedures by user equipment (UE). For example, a network entity may transmit synchronization signal block (SSB) signals detected by UE within its coverage area. Each SSB is generally associated with a corresponding random access channel (RACH) occasion (RO). The RO generally defines the resource set (e.g., time/frequency resources, frequency shift information, and more) that a UE receiving the SSB signal uses for the RACH procedure. Conventionally, the UE would measure the SSB signal strength to calculate the transmit power to use for the RACH procedure (e.g., based on channel reciprocity). Each UE generally selects its transmit power such that the network entity receives RACH preamble transmissions at the same power level over a given RO resource set. However, certain UE types (e.g., passive RFID tags) may use backscattering techniques where a continuous wave (CW) transmitted by the network entity (e.g., reader) is reflected back to the network entity after applying a frequency shift. This may result in RACH transmissions from different UE types being received at different power levels at the network entity.
The described techniques relate to improved methods, systems, devices, and apparatuses that support RO selection. For example, the described techniques provide for a UE to receive or otherwise obtain a downlink signal (e.g., SSB) from a network entity. The downlink signal may be associated with a set of available ROs (e.g., more than one RO associated with each SSB), with each RO in the set defining the resource set (e.g., time/frequency resources, frequency shift, etc.). The UE may perform a RACH procedure with the network entity using at least one RO associated with the downlink signal. In some examples, each RO in the set may be based on a received power level of the downlink signal at the UE. For example, the UE may estimate the received power level of the downlink signal and select a RO from the set that corresponds to the received power level.
Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following advantages. Associating a set of RO for a downlink signal, such as an SSB, may improve RACH procedures between UE and the network entity. The pool of ROs associated with the downlink signal may enable selection of an RO that further improves reception and recovery of the RACH signal at the network entity. The pool of ROs associated with the downlink signal may enable a UE to select a RO based on the downlink signal. Dividing the ROs in the RO pool by downlink signal strength may improve granularity and flexibility by adapting to distribution of UEs within a coverage area of the network entity. Dividing the ROs in the RO pool based on the downlink signal strength may improve backscattering based communications where UE are located at different areas within the coverage area of the network entity.
Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to RO selection.
The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).
The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in
As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link), one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).
The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170). In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c. F1-u), and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
In wireless communications systems (e.g., wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB nodes 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104). Additionally, or alternatively, an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
For example, IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104. For example, the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support RO selection as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).
A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in
The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).
In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology).
The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).
A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (STTIs)).
Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140), as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.
In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.
In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.
Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.
The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
The core network 130 may provide user authentication, access authorization, tracking. Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5 GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.
The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.
Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).
A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
Some signals, such as data signals associated with a particular receiving device, may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).
A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).
The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.
The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
A UE 115 may receive a downlink signal from a network entity 105, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity 105. The UE 115 may perform the random access procedure with the network entity 105 using at least one RO of the set of available ROs, the at least one RO selected based at least in part on the downlink signal.
A network entity 105 may transmit a downlink signal to a UE 115, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE 115. The network entity 105 may perform the random access procedure with the UE 115 using at least one RO of the set of available ROs, the at least one RO selected based at least in part on the downlink signal.
Wireless communications system 200 may implement aspects of wireless communications system 100. Wireless communications system 200 may include a UE 205 and/or a network entity 210, which may be examples of the corresponding devices described herein. In some aspects, the UE 205 and the network entity 210 may communicate, at least to some degree, based on backscattering techniques.
The UE 205 may be an example of a passive device, such as a RFID tag, passive IoT device, or similar device. Generally, references to passive devices generally include any device configured to or otherwise supporting backscattering-based communication techniques, or any other passive communication technologies. For example, a passive device may refer to a device that supports backscattering-based communications (e.g., RFID style communications). In another example, a passive device may refer to an IoT device, such as a passive IoT device (e.g., with limited circuitry/functionality) or a semi-active IoT device (e.g., with more advanced circuitry/functionality). Passive device may include any device with limited capabilities (e.g., limited active circuitry, little or no on-board power source, limited capability, or limited functionality), any device that communicates small amounts of data regularly or as-needed (e.g., MTC type devices), or any device that is able to communicate with a reader device using such backscattering-based communications (e.g., similar to RFID-based communications). A passive device may be an example of an advanced device (e.g., a UE) fully capable of performing wireless communications within a cellular or sidelink wireless network, but may also support such backscattering-based communications.
A reader device (such as the network entity 210) may generally refer to any device capable of communicating with, or otherwise associated with, a passive device using backscattering-based communications. A reader device may be implemented at a single device (e.g., the reader device is both the device transmitting messages or other signals to the passive devices and receiving the backscattered response signals from the passive devices) or spread across multiple devices (e.g., separate transmitting and receiving devices). The reader device may be a stand-alone device or the functionality of the reader device may be a part of a complex/multi-function device (e.g., such as a stand-alone network entity 210).
Reader/passive devices currently rely on RFID communication techniques in the ISM radio frequency spectrum band. Such RFID communication techniques are generally decentralized in that the communications are passive in nature with the passive devices only communicating in the presence of the reader device. That is, there is little or no coordination or management of communication resources, interference management between devices, or related functions, between the reader device and the passive device in support of the passive RFID communications. Broadly speaking, the passive device simply performs the wireless communications with a reader device when the devices are within a range of each other. This may include the reader device transmitting a CW signal that is received at the passive device and reflected back to the reader (e.g., backscattered). The passive device may introduce a frequency and/or phase shift in the reflected signal and/or may modulate information onto the reflected signal using on-off type modulation.
As one non-limiting example, backscattering-based communications may include information modulation methods for such backscatter communications using amplitude shift keying (ASK). ASK generally includes the passive device switching, activating, or otherwise initiating a reflection of a reference signal (e.g., CW) to transmit or otherwise indicate a one (“1”) and switching, deactivating, or otherwise stopping the reflection of the reference signal to transmit or otherwise indicate a zero (“0”). That is, a reader device generally transmits a radio wave (such as a CW) that the passive tag backscatters back to the reader after applying a frequency shift, a delay, and the like.
Wireless devices, which may include passive devices, may also rely on a random access procedure (e.g., a RACH procedure via a physical RACH (PRACH)) to establish connectivity with the network. For example, the UE 205 may monitor for SSB transmissions from the network entity 210. The UE 205 may use the SSB transmission to identify various resources, parameters, or other configurations that allow the UE 205 to initiate the RACH procedure with the network entity 210. In some wireless networks, each SSB transmission is associated with a given RO such that a UE 205 receiving a given SSB is able to locate the time/frequency resources, frequency/phase shift, and the like, of the RO for that SSB. The UE 205 then performs the RACH the procedure with the network during the RO. That is, the RO may define the resources available for a RACH procedure, where the resources may include time resources, frequency resources, frequency shift, phase shift, delay, or other parameter(s) applied during the RO.
However, such techniques may become an issue in terms of passive devices within the wireless network. Traditional devices (e.g., UE(s)) receiving an SSB from the network entity 210 identifying the associated RO and transmit a RACH preamble via the resource set of the RO. When more than one UE receives the same SSB and attempts to transmit the RACH preamble via the RO resource set, this results in multiple signals being received at the network entity 210 at the same time. To mitigate interference, wireless networks are generally configured such that the signals received at the network entity 210 at the same time are received at relatively the same received signal strength level. For example, traditional UEs apply power control techniques to achieve the (pre) configured received signal strength level at the network entity 210. Such UEs measure the received signal strength of the SSB and, based on reciprocity, select a transmit power level designed to achieve the (pre) configured received signal strength level at the network entity 210.
Passive devices, such as the UE 205 in this example, may not include or otherwise support transmit circuitry and/or may be communicating via backscattering techniques, which may not enable them to perform such power control functionality. Instead, such passive devices backscatter the CW transmitted from the network entity 210 using a RO and at an effective transmit power that is dependent upon the received power of the CW signal. Some passive devices may be located near the network entity 210 while others are located away from (e.g., edge devices) the network entity 210, which means the backscattered signals will have different received signal strength levels at the network entity 210. In such systems where there is only one associated RO for each SSB, the received power at the network entity 210 of the reflected (e.g., backscattered) CW from different passive devices being different disrupts the communications. This impact is particularly problematic for passive devices located at the edge of the coverage area of the network entity 210 as the signal strength of the CW at the edge of the coverage area is low. This results in a lower received signal strength of the reflected signal at the network entity 210, which may not be detectable or recoverable.
Accordingly, aspects of the techniques described herein support RO selection where multiple ROs (e.g., a set or pool of ROs) correspond to a downlink signal, such as a SSB transmission. Although the description herein generally discusses the SSB transmission as the downlink signal, it is to be understood that the set of ROs may correspond more generally to a downlink signal from the network entity 210. The downlink signal in this discussion may include a SSB signal, a master information block (MIB) signal, a secondary information block (SIB), a primary synchronization signal (PSS), a secondary synchronization signal, a physical broadcast channel (PBCH) signal, previously received downlink signal(s) from the network entity 210, downlink signal(s) received within a time window or interval, and the like.
The set of ROs may generally include one or more ROs available for a RACH procedure with the network entity 210. For backscattered communications, each RO may define the frequency resource, time resource, spatial resource, transmit power level, and the like, for the CW signal that the network entity 210 will transmit for the RACH procedure. From the perspective of the passive device, each RO may define the frequency shift, phase shift, time delay, and the like, that the passive device (e.g., the UE 205 in this example) will apply to the CW transmitted by the network entity 210 during the RO.
Each RO may generally define a unique resource set available for the RACH procedure. The resource set defined by different ROs in the set may be defined based on a frequency shift and/or a different time index (e.g., slot index) for the RO. Providing a set of available ROs associated with the SSB transmission (e.g., rather than a single RO associated with the SSB transmission) may support improved performance at the network entity 210 when multiple tags choose the same RO to perform the RACH procedure (e.g., receive the same SSB transmission).
Accordingly, at 215 the network entity 210 may transmit or otherwise provide (and the UE 205 may receive or otherwise obtain) a downlink signal (e.g., a SSB transmission). The SSB transmission may be associated with a set of available ROs, with each RO in the set defining a resource set available for a RACH procedure with the network entity 210. The UE 205 may have previously received and/or otherwise been (pre) configured with a mapping or other information linking or otherwise associating a given SSB transmission with the set of available ROs (e.g., based on the index of the SSB). The UE 205 may have identified or otherwise determined the set of available ROs associated with the SSB transmission during a previous and/or active communication session with the network entity 210. The UE 205 may have identified or otherwise determined the set of available ROs associated with the SSB transmission based on the SSB transmission (e.g., information carried or otherwise conveyed via the SSB transmission). The UE 205 may have identified or otherwise determined the set of available ROs associated with the SSB transmission based on dynamic signaling.
In some aspects, each RO in the set of available ROs be associated with a received signal strength of the SSB transmission. For example, the UE 205 may be able to measure, identify, or otherwise determine a received signal strength of the SSB transmission. The UE 205 may apply a weighted average of all received signals to better estimate the pathloss and/or received signal strength of the SSB transmission. The UE 205 may identify or otherwise determine the transmit power used by the network entity 210 when transmitting the SSB transmission (e.g., based on a received signal and/or otherwise (pre) configurated). Each RO in the set of available ROs may be associated with a different received signal strength for the SSB transmission. The UE 205 may use the received signal strength of the SSB transmission to identify, select, or otherwise determine the RO from the set. For example, the UE 205 may identify or otherwise determine which RO in the set of ROs is associated with the determined signal strength of the SSB transmission. The UE 205 may select the appropriate RO from the set of ROs corresponding to the received signal strength of the SSB transmission.
In some examples, the UE 205 may identify, select, or otherwise determine a RACH sequence from a set of available RACH sequences. For example, after the UE 205 selects the RO from the set of available ROs based on the received signal strength of the SSB transmission, the UE 205 may choose, select, or otherwise identify a sequence out of a sequence pool (e.g., such as a Hadamard sequence or other sequence). The RACH sequence selected by the UE 205 may further mitigate interference caused by another UE choosing the same RO.
In some examples, the set of available ROs configuration may define or otherwise include the resource set for each RO and a criteria (e.g., threshold criteria) used to select a RO out of the set of available ROs. The configuration of the set of available ROs and/or threshold criteria may be hard coded and/or (pre) configured for the UE 205. For example, the (pre) configuration may define or otherwise specify the slot indices (e.g., time index) of the RACH slots after receiving a particular SSB transmission that the RO will occur. The (pre) configuration may define or otherwise specify the frequency shift within each RACH slot that the UE 205 will apply to the backscattered CW signal. The (pre) configuration may define or otherwise specify the length of the RACH sequence to be selected and applied by the UE 205 to the backscattered signal. The (pre) configuration may define or otherwise specify the received signal strength associated with each RO in the set of available ROs (e.g., the threshold criteria). For example, the (pre) configuration may define: if rxSignalStrength<x dBm, use RO1; if x dBm<=rxSignalStrength<y, use RO2, and so forth, for each RO in the set of available ROs. The UE 205 may select at least one RO from the set of available ROs based on the received signal strength (rxSignalStrength) of the SSB transmission and the (pre) configuration.
In some examples, the set of available ROs configuration and/or threshold criteria may be dynamically configured for the UE 205. For example, the RO pool may be dynamically configured through some SIB signal transmissions. Within an SIB transmission, the network entity 210 may specify the set of available ROs associated with the SIB transmission and/or the criteria for the RACH RO pool. This dynamic approach provides more flexibility for the network entity 210, while reducing overhead signaling.
In some examples, both hard coded and dynamic configuration of the set of available ROs may be combined or otherwise used together to indicate or otherwise inform the UE 205 of the set of available ROs associated with the SSB. For example, the UE 205 may be hard coded with the configuration of the set of ROs and dynamic signaling may be used to update aspects of the configuration and/or to overwrite the configuration.
Accordingly, at 220 the UE 205 and the network entity 210 may perform the RACH procedure using a RO selected from the set of available ROs. The selection may be based on the received signal strength of the SSB transmission, and the threshold criteria defining received signal strength values for each RO in the set. As discussed above, in this example the UE 205 may be a passive devise such that performing the RACH procedure using the selected RO may include backscattering (e.g., reflecting) a CW transmitted by the network entity 210 via the resource set defined by the RO.
Aspects of the techniques described herein generally provide a pool or set of ROs associated with a given downlink signal, such as an SSB transmission. Some wireless networks associate a RO with each SSB transmission such that a device receiving the SSB transmission locates the associated RO and uses it for a RACH procedure with the network entity. However, this approach is problematic for backscattered-based wireless communications as the passive devices may not support power control techniques. This approach creates interference at the network entity when multiple devices utilize the same RO. This approach may result in a loss of communications for passive device, with increased disruption to passive devices located farter away from the network entity (e.g., the reader).
The network entity may transmit or otherwise provide a downlink signal 315, such as an SSB transmission. However, it is to be understood that the downlink signal 315 is not limited to the SSB transmission and other downlink signal(s) may be used in this context. The UE 305 and the UE 310 may each be passive devices that receive the downlink signal 315. In some aspects, the downlink signal 315 may be a CW signal transmitted from the network entity. The UE 305 may be located farther away from the network entity than the UE 310. For example, the UE 305 may be considered an edge UE and the UE 310 may be considered a near UE (e.g., relative to the physical location of the network entity).
The downlink signal 315 may be associated with a set of available ROs, with the set including four ROs in this non-limiting example. Each RO in the set may define the resource set available for a RACH procedure between a UE and the network entity. The RACH procedure may include the network entity transmitting or otherwise providing a CW at a frequency resource and during a slot after the downlink signal 315 is transmitted. In the non-limiting example illustrated in
In the non-limiting example shown in
For example, RO 330 may be associated with a frequency shift 350 of K1fRC during slot i and RO 340 may also be associated with the frequency shift 350 during slot j. RO 335 may be associated with a frequency shift 355 of K2fRC during slot i and RO 345 may also be associated with the frequency shift 355 during slot j. The ROs in the set of available ROs may be divided or otherwise associated with a different received signal strength of the downlink signal 315. For example, RO 330 may be associated with a received signal strength within a first range (e.g., in dBm), RO 335 may be associated with a received signal strength within a second range, and so forth for each RO in the set. In some aspects, the range of received signal strengths associated with each RO may define the threshold criteria used to select the corresponding RO.
Each UE may select at least one RO from the set of available ROs based on the downlink signal 315. For example, the UE 305 and the UE 310 may each measure, identify or otherwise determine the received signal strength of the downlink signal 315. Each UE may identify, determine, or otherwise select a RO from the set of available ROs based on the received signal strength it determined for the downlink signal 315. The UE 305, being an edge UE, may receive the downlink signal 315 at a relatively low received signal strength while the UE 310, being a near UE, may receive the downlink signal 315 at a relatively higher (e.g., relative to the UE 305) received signal strength. Accordingly, the UE 305 may select a RO 345 (e.g., RO4) from the set based on the RO 345 being associated with a range of received signal strengths satisfying the received signal strength of the downlink signal 315 determined by the UE 305. Similarly, the UE 310 may select a RO 330 (e.g., RO1) from the set based on the RO 330 being associated with a range of received signal strengths satisfying the received signal strength of the downlink signal 315 determined by the UE 310.
Accordingly, each UE may perform the RACH procedure with the network entity using the RO selected from the set of available ROs based on its own received signal strength of the downlink signal 315. For example, during slot i the UE 310 may backscatter the CW 320 to the network entity applying the frequency shift 350 to the backscattered CW signal. During sot j, the UE 305 may backscatter the CW 325 to the network entity applying the frequency shift 355 to the backscattered CW signal.
Providing or otherwise configuring more than one RO for a SSB may include resource reservation/overhead. However, by providing more resources via multiple ROs per SSB, this may reduce collisions, delays, energy drain, and the like, by the wireless devices. For example, this technique may allow a UE to choose a RO so that its PRACH is not destroyed (e.g., overpowered) by another UE closer to reader. When the passive devices are uniformly distributed around the reader, there may be more passive devices at distance x from the reader than passive devices located at distance y, wherein x>y. In some examples, this may lead to allocating or otherwise configuring more ROs (e.g., a finer thresholds for RO binning/selection) when the received signal strength power is relatively lower.
At 405, the UE may receive, identify, or otherwise determine a downlink signal. The downlink signal downlink signal may be an SSB transmission and/or may be other downlink signals transmitted by the network entity. The downlink signal may be associated with a set of available ROs. Each RO in the set may define the resource set available for a RACH procedure with the network entity. The resource set may include or otherwise define the resources associated with a CW signal transmission during the RO and/or the resources applied to the backscattered CW signal by the passive device (e.g., UE).
At 410, the UE may measure, identify, or otherwise determine the received signal strength (e.g., reference signal received power (RSRP)) of the downlink signal. For example, the UE may be aware of the transmit power of the downlink signal and measure the received signal strength to determine the pathloss. The UE may track or otherwise monitor the pathloss associated with the network entity over time and use this pathloss to identify or otherwise determine the received signal strength of the downlink signal.
At 415, the UE may identify or otherwise determine the set of available ROs associated with the downlink signal. For example, the UE may be hard coded and/or dynamically configured with the set of available ROs associated with the downlink signal.
At 420, the UE may select at least one RO from the set of available ROs based on the received signal strength of the downlink signal. For example, each RO in the set may have an associated threshold criteria defining when a UE may use that particular RO. In some examples, the threshold criteria may be based on a range of received signal strength of the downlink signal. Determining the received signal strength of the downlink signal by the UE may be used to select the RO from the set of available ROs. For example, the UE may compare its determined received signal strength for the downlink signal to each range of received signal strengths corresponding to each RO in the set until the UE finds the RO in which the determined received signal strength is satisfied. The UE may select the RO from the set of available ROs based on the comparison and match and use the RO to perform the RACH procedure with the network entity. For example, the UE may receive a CW signal transmitted during the selected RO and backscatter (e.g., reflect) the CW signal back to the network entity using the delay, frequency shift, phase shift, and the like, corresponding to the selected RO.
The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to RO selection). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.
The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to RO selection). In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.
The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of RO selection as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).
Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).
In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 520 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The communications manager 520 is capable of, configured to, or operable to support a means for performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for improved RACH procedures based on associating multiple ROs with a downlink signal, such as an SSB transmission. The multiple ROs may be divided such that each RO in the set is associated with the received signal strength of the downlink signal observed by the UE. This approach may minimize overlapped RO selection by UEs, such as passive devices applying backscattering technologies.
The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to RO selection). Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.
The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to RO selection). In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.
The device 605, or various components thereof, may be an example of means for performing various aspects of RO selection as described herein. For example, the communications manager 620 may include a signal manager 625 an access manager 630, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein. The signal manager 625 is capable of, configured to, or operable to support a means for receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The access manager 630 is capable of, configured to, or operable to support a means for performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
The communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein. The signal manager 725 is capable of, configured to, or operable to support a means for receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The access manager 730 is capable of, configured to, or operable to support a means for performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
In some examples, the signal strength manager 735 is capable of, configured to, or operable to support a means for selecting the at least one RO from the set of available ROs based on a received signal strength of the downlink signal.
In some examples, the sequence manager 740 is capable of, configured to, or operable to support a means for selecting, based on the at least one RO, a random access channel sequence from a set of available random access channel sequences.
In some examples, the threshold manager 745 is capable of, configured to, or operable to support a means for receiving an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs.
In some examples, the threshold manager 745 is capable of, configured to, or operable to support a means for identifying, based on the indication, a time index for each ROs in the set of available ROs, a frequency shift associated with each time index, a random access procedure sequence length, or a combination thereof.
In some examples, to support performing the random access procedure using the at least one RO, the access manager 730 is capable of, configured to, or operable to support a means for backscattering a continuous waveform signal received from the network entity via the resource set defined by the at least one RO, where the backscattering is based on the continuous waveform signal.
In some examples, the resource set defined by the at least one RO includes a frequency resource, a time resource, or both, that are different than corresponding resource sets defined by a subset of remaining ROs of the set of available ROs.
In some examples, the downlink signal includes at least one of a synchronization signal block (SSB) signal, a master information block (MIB) signal, a secondary information block (SIB) signal, an PSS, an SSS, a physical broadcast channel (PBCH) signal, a previously received downlink signal from the network entity, a set of downlink signals received within a time interval, or a combination thereof.
The I/O controller 810 may manage input and output signals for the device 805. The I/O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I/O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 810 may be implemented as part of a processor, such as the processor 840. In some cases, a user may interact with the device 805 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.
In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally, via the one or more antennas 825, wired, or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.
The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 835 may not be directly executable by the processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 830 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting RO selection). For example, the device 805 or a component of the device 805 may include a processor 840 and memory 830 coupled with or to the processor 840, the processor 840 and memory 830 configured to perform various functions described herein.
The communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The communications manager 820 is capable of, configured to, or operable to support a means for performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for improved RACH procedures based on associating multiple ROs with a downlink signal, such as an SSB transmission. The multiple ROs may be divided such that each RO in the set is associated with the received signal strength of the downlink signal observed by the UE. This approach may minimize overlapped RO selection by UEs, such as passive devices applying backscattering technologies, improved RACH procedures based on associating multiple ROs with a downlink signal, such as an SSB transmission. The multiple ROs may be divided such that each RO in the set is associated with the received signal strength of the downlink signal observed by the UE. This approach may minimize overlapped RO selection by UEs, such as passive devices applying backscattering technologies.
In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of RO selection as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.
The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.
The communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of RO selection as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).
Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).
In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 920 may support wireless communications at a network entity in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE. The communications manager 920 is capable of, configured to, or operable to support a means for performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for improved RACH procedures based on associating multiple ROs with a downlink signal, such as an SSB transmission. The multiple ROs may be divided such that each RO in the set is associated with the received signal strength of the downlink signal observed by the UE. This approach may minimize overlapped RO selection by UEs, such as passive devices applying backscattering technologies.
The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.
The device 1005, or various components thereof, may be an example of means for performing various aspects of RO selection as described herein. For example, the communications manager 1020 may include a signal manager 1025 an access manager 1030, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 1020 may support wireless communications at a network entity in accordance with examples as disclosed herein. The signal manager 1025 is capable of, configured to, or operable to support a means for transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE. The access manager 1030 is capable of, configured to, or operable to support a means for performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
The communications manager 1120 may support wireless communications at a network entity in accordance with examples as disclosed herein. The signal manager 1125 is capable of, configured to, or operable to support a means for transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE. The access manager 1130 is capable of, configured to, or operable to support a means for performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
In some examples, the signal strength manager 1135 is capable of, configured to, or operable to support a means for selecting the resource set defined by each RO is based on a UE distribution pattern for a set of UE located proximate to the network entity.
In some examples, each RO from the set of available ROs are associated with a received signal strength of the downlink signal at the UE.
In some examples, the sequence manager 1140 is capable of, configured to, or operable to support a means for performing, based on the at least one RO, the random access procedure with the UE using a random access channel sequence from a set of available random access channel sequences.
In some examples, the threshold manager 1145 is capable of, configured to, or operable to support a means for transmitting an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs.
In some examples, the indication identifies a time index for each ROs in the set of available ROs, a frequency shift associated with each time index, a random access procedure sequence length, or a combination thereof.
In some examples, to support performing the random access procedure using the at least one RO, the access manager 1130 is capable of, configured to, or operable to support a means for receiving a backscattered continuous waveform signal from the UE via the resource set defined by the at least one RO.
In some examples, the resource set defined by the at least one RO includes a frequency resource, a time resource, or both, that are different than corresponding resource sets defined by a subset of remaining ROs of the set of available ROs.
In some examples, the downlink signal includes at least one of a synchronization signal block (SSB) signal, a master information block (MIB) signal, a secondary information block (SIB) signal, an PSS, an SSS, a physical broadcast channel (PBCH) signal, a previously received downlink signal from the network entity, a set of downlink signals received within a time interval, or a combination thereof.
The transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or memory components (for example, the processor 1235, or the memory 1225, or both), may be included in a chip or chip assembly that is installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168).
The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by the processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 1225 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting RO selection). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and memory 1225 coupled with the processor 1235, the processor 1235 and memory 1225 configured to perform various functions described herein. The processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205. The processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within the memory 1225). In some implementations, the processor 1235 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device 1205). For example, a processing system of the device 1205 may refer to a system including the various other components or subcomponents of the device 1205, such as the processor 1235, or the transceiver 1210, or the communications manager 1220, or other components or combinations of components of the device 1205. The processing system of the device 1205 may interface with other components of the device 1205, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the device 1205 may include a processing system and one or more interfaces to output information, or to obtain information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device 1205 may transmit information output from the chip or modem. Additionally, or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device 1205 may obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that a first interface also may obtain information or signal inputs, and a second interface also may output information or signal outputs.
In some examples, a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the device 1205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the memory 1225, the code 1230, and the processor 1235 may be located in one of the different components or divided between different components).
In some examples, the communications manager 1220 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1220 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1220 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105. In some examples, the communications manager 1220 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
The communications manager 1220 may support wireless communications at a network entity in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE. The communications manager 1220 is capable of, configured to, or operable to support a means for performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal.
By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for improved RACH procedures based on associating multiple ROs with a downlink signal, such as an SSB transmission. The multiple ROs may be divided such that each RO in the set is associated with the received signal strength of the downlink signal observed by the UE. This approach may minimize overlapped RO selection by UEs, such as passive devices applying backscattering technologies.
In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of RO selection as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.
At 1305, the method may include receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The operations of block 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a signal manager 725 as described with reference to
At 1310, the method may include performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal. The operations of block 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by an access manager 730 as described with reference to
At 1405, the method may include receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The operations of block 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a signal manager 725 as described with reference to
At 1410, the method may include selecting the at least one RO from the set of available ROs based on a received signal strength of the downlink signal. The operations of block 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a signal strength manager 735 as described with reference to
At 1415, the method may include performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal. The operations of block 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by an access manager 730 as described with reference to
At 1505, the method may include receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity. The operations of block 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a signal manager 725 as described with reference to
At 1510, the method may include selecting, based on the at least one RO, a random access channel sequence from a set of available random access channel sequences. The operations of block 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a sequence manager 740 as described with reference to
At 1515, the method may include performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal. The operations of block 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by an access manager 730 as described with reference to
At 1605, the method may include transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE. The operations of block 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a signal manager 1125 as described with reference to
At 1610, the method may include performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal. The operations of block 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by an access manager 1130 as described with reference to
At 1705, the method may include transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE. The operations of block 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a signal manager 1125 as described with reference to
At 1710, the method may include transmitting an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs. The operations of block 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a threshold manager 1145 as described with reference to
At 1715, the method may include performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based on the downlink signal. The operations of block 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by an access manager 1130 as described with reference to
The following provides an overview of aspects of the present disclosure:
Aspect 1: A method for wireless communications by a UE, comprising: receiving a downlink signal from a network entity, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the network entity; and performing the random access procedure with the network entity using at least one RO of the set of available ROs, the at least one RO selected based at least in part on the downlink signal.
Aspect 2: The method of aspect 1, further comprising: selecting the at least one RO from the set of available ROs based at least in part on a received signal strength of the downlink signal.
Aspect 3: The method of any of aspects 1 through 2, further comprising: selecting, based at least in part on the at least one RO, a RACH sequence from a set of available RACH sequences.
Aspect 4: The method of any of aspects 1 through 3, further comprising: receiving an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs.
Aspect 5: The method of aspect 4, further comprising: identifying, based at least in part on the indication, a time index for each ROs in the set of available ROs, a frequency shift associated with each time index, a random access procedure sequence length, or a combination thereof.
Aspect 6: The method of any of aspects 1 through 5, wherein performing the random access procedure using the at least one RO comprises: backscattering a continuous waveform signal received from the network entity via the resource set defined by the at least one RO, wherein the backscattering is based at least in part on the continuous waveform signal.
Aspect 7: The method of any of aspects 1 through 6, wherein the resource set defined by the at least one RO comprises a frequency resource, a time resource, or both, that are different than corresponding resource sets defined by a subset of remaining ROs of the set of available ROs.
Aspect 8: The method of any of aspects 1 through 7, wherein the downlink signal comprises at least one of a SSB signal, a MIB signal, a SIB signal, an PSS, an SSS, a PBCH signal, a previously received downlink signal from the network entity, a set of downlink signals received within a time interval, or a combination thereof.
Aspect 9: A method for wireless communications by a network entity, comprising: transmitting a downlink signal to a UE, the downlink signal associated with a set of available ROs, each RO in the set of available ROs defining a resource set available for a random access procedure with the UE; and performing the random access procedure with the UE using at least one RO of the set of available ROs, the at least one RO selected based at least in part on the downlink signal.
Aspect 10: The method of aspect 9, further comprising: selecting the resource set defined by each RO is based at least in part on a UE distribution pattern for a set of UE located proximate to the network entity.
Aspect 11: The method of any of aspects 9 through 10, wherein each RO from the set of available ROs are associated with a received signal strength of the downlink signal at the UE.
Aspect 12: The method of any of aspects 9 through 11, further comprising: performing, based at least in part on the at least one RO, the random access procedure with the UE using a RACH sequence from a set of available RACH sequences.
Aspect 13: The method of any of aspects 9 through 12, further comprising: transmitting an indication of the set of available ROs and a threshold criteria associated with each RO in the set of available ROs.
Aspect 14: The method of aspect 13, wherein the indication identifies a time index for each ROs in the set of available ROs, a frequency shift associated with each time index, a random access procedure sequence length, or a combination thereof.
Aspect 15: The method of any of aspects 9 through 14, wherein performing the random access procedure using the at least one RO comprises: receiving a backscattered continuous waveform signal from the UE via the resource set defined by the at least one RO.
Aspect 16: The method of any of aspects 9 through 15, wherein the resource set defined by the at least one RO comprises a frequency resource, a time resource, or both, that are different than corresponding resource sets defined by a subset of remaining ROs of the set of available ROs.
Aspect 17: The method of any of aspects 9 through 16, wherein the downlink signal comprises at least one of a SSB signal, a MIB signal, a SIB signal, an PSS, an SSS, a PBCH signal, a previously received downlink signal from the network entity, a set of downlink signals received within a time interval, or a combination thereof.
Aspect 18: A UE for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 8.
Aspect 19: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 8.
Aspect 20: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 8.
Aspect 21: A network entity for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 9 through 17.
Aspect 22: An apparatus for wireless communications at a network entity, comprising at least one means for performing a method of any of aspects 9 through 17.
Aspect 23: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 9 through 17.
It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”
As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”
The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory) and the like. Also, “determining” may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.
The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
