Patent ID: 12256330

DETAILED DESCRIPTION

A wireless communications system may include a device, such as a user equipment (UE) or a network entity (e.g., an eNodeB (eNB), a next-generation NodeB or a giga-NodeB, either of which may be referred to as a gNB, or some other base station or network entity), that supports wireless communications using one or multiple radio access technologies. Examples of radio access technologies include 4G systems, such as LTE systems, 5G systems, which may be referred to as NR systems, or other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein (e.g., sixth generation (6G) systems and beyond).

In some wireless communications systems, such as fifth generation (5G) systems, a relatively large amount of power may be consumed by network components in some situations. For example, a network entity in a system that uses beamformed communications, such as a radio unit (RU) or a radio head, may transmit multiple directional beams in multiple directions. Such systems may provide information for use by a UE to access the wireless communications system (e.g., system information that provides parameters for system access) using beam sweeping techniques in which information is provided in multiple different transmissions in multiple different directions. For example, multiple instances of synchronization signal blocks (SSBs) and system information (SI) transmissions (e.g., remaining minimum system information (RMSI) transmissions) may be transmitted across multiple beams in multiple different directions according to a beam sweeping procedure. Such beam sweeping techniques may consume additional power relative to techniques that do not use beam sweeping (e.g., information provided in a single omni-directional transmission may consume less power than transmission of multiple instances of the information in multiple different directions). Further, such beam sweeping transmissions may be transmitted on multiple different cells, such as a primary cell (PCell) and one or more secondary cells (SCells).

In some cases, in order to reduce network power consumption, a network entity may transition to a sleep mode or idle mode in which transmit and receive circuitry is powered down. For example, during off-peak times, there may be no traffic or a light traffic load in a cell, and the network entity may stop or reduce periodic transmissions (e.g., SSB and SI transmissions) and periodic monitoring (e.g., monitoring for random access requests or small data transmission (SDT) communications), and transition to the sleep mode in which periodic active periods are used to monitor for a wake-up signal (WUS) from a served device such as a UE. If the network entity does not detect a WUS, it transitions back to the sleep mode. If one or more WUS is detected, the network entity may maintain an active mode or initiate an active mode in addition to periods during which WUSs are monitored. In some cases, such sleep mode operations may be implemented on one or more SCells, which commonly have less control communications than a PCell and thus are more likely to have periods with light or no traffic, although such techniques may also be used in PCells in some conditions. In some cases, a UE may be configured with a periodicity at which WUSs may be transmitted in accordance with periods during which a cell will monitor for WUSs, which may be referred to as WUS occasions. If data traffic is present in the UE transmit buffer, the UE may transmit a WUS during a WUS occasion to trigger the cell to start or maintain an active state to allow for communications of the UE's data traffic.

In accordance with various aspects discussed herein, techniques are provided in which a WUS may provide additional information in addition to just a binary indication of whether the UE has traffic in a transmit buffer. In some cases, a WUS configuration may be provided to a UE that allows the selection of a particular WUS to indicate one or more attributes of traffic that is present at the UE. A network entity that receives the WUS may use the indication to adjust a wake-up timing, a duration of an associated active period, or any combinations thereof. In some implementations, a WUS may provide an indication that the cell is to wake-up, and also convey information such as buffer status, power headroom, a priority of traffic, latency targets of the traffic, or any combinations thereof. In some cases, the UE may also give a recommendation on how long the network should stay awake. In some cases, the WUS may be a random access preamble, the UE can select a preamble from two or more groups of preambles where each group represents a set of information to be conveyed to the network. The groups and associated traffic attributes may be configured or otherwise signaled to the UE (e.g., via radio resource control (RRC) signaling, via system information associated with the cell, preconfigured in a communications specification, or any combinations thereof). In some cases, a WUS may be transmitted via a control channel (e.g., a physical uplink control channel (PUCCH) transmission with scheduling request (SR)) transmission that may include a payload that conveys information regarding the data to be transmitted by the UE, or traffic attributes. In some cases, a UE may be configured to monitor for different network responses based on the transmitted WUS. For example, if the UE indicates a high priority or low latency requirement in the WUS, the UE may expect a scheduling information transmission (e.g., in downlink control information (DCI) transmitted via a physical downlink control channel (PDCCH)) in an earlier response window than if a lower priority or higher latency is indicated.

Various techniques as discussed herein may provide one or more UE and network enhancements and efficiencies. For example, a network entity may transition to a sleep mode and network power savings may be achieved, and may determine one or more aspects of an active period based on information from a received WUS. Such a network entity may adjust one or more parameters of an active period based on the information conveyed by the WUS, such as a duration of the active period, scheduling priorities for one or more UEs that transmitted WUSs, or a number of transmit or receive chains or antenna ports to activate, to name just a few examples. Further, the information conveyed by the WUS may allow for enhanced scheduling decisions at such a network entity, where priorities of multiple different devices may be used to schedule communications and allocate wireless resources, thus enhancing system efficiency and providing an enhanced user experience.

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 WUS timings, process flows, apparatus diagrams, system diagrams, and flowcharts that relate to wake-up signal traffic indication techniques for wireless communications.

FIG.1illustrates an example of a wireless communications system100that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The wireless communications system100may include one or more network entities105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities105may be dispersed throughout a geographic area to form the wireless communications system100and may include devices in different forms or having different capabilities. In various examples, a network entity105may 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 entities105and UEs115may wirelessly communicate via one or more communication links125(e.g., a radio frequency (RF) access link). For example, a network entity105may support a coverage area110(e.g., a geographic coverage area) over which the UEs115and the network entity105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a network entity105and a UE115may support the communication of signals according to one or more radio access technologies (RATs).

The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be capable of supporting communications with various types of devices, such as other UEs115or network entities105, as shown inFIG.1.

As described herein, a node of the wireless communications system100, which may be referred to as a network node, or a wireless node, may be a network entity105(e.g., any network entity described herein), a UE115(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 UE115. As another example, a node may be a network entity105. 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 UE115, the second node may be a network entity105, and the third node may be a UE115. In another aspect of this example, the first node may be a UE115, the second node may be a network entity105, and the third node may be a network entity105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE115, network entity105, apparatus, device, computing system, or the like may include disclosure of the UE115, network entity105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE115is configured to receive information from a network entity105also discloses that a first node is configured to receive information from a second node.

In some examples, network entities105may communicate with the core network130, or with one another, or both. For example, network entities105may communicate with the core network130via one or more backhaul communication links120(e.g., in accordance with an S1, N2, N3, or other interface protocol). In some examples, network entities105may communicate with one another via a backhaul communication link120(e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities105) or indirectly (e.g., via a core network130). In some examples, network entities105may communicate with one another via a midhaul communication link162(e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link168(e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links120, midhaul communication links162, or fronthaul communication links168may 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 UE115may communicate with the core network130via a communication link155.

One or more of the network entities105described herein may include or may be referred to as a base station140(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 entity105(e.g., a base station140) 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 entity105(e.g., a single RAN node, such as a base station140).

In some examples, a network entity105may 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 entities105, 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 entity105may 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)180system, or any combination thereof. An RU170may 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 entities105in a disaggregated RAN architecture may be co-located, or one or more components of the network entities105may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities105of 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 CU160, a DU165, and an RU170is 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 CU160, a DU165, or an RU170. For example, a functional split of a protocol stack may be employed between a CU160and a DU165such that the CU160may support one or more layers of the protocol stack and the DU165may support one or more different layers of the protocol stack. In some examples, the CU160may 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 CU160may be connected to one or more DUs165or RUs170, and the one or more DUs165or RUs170may 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 CU160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU165and an RU170such that the DU165may support one or more layers of the protocol stack and the RU170may support one or more different layers of the protocol stack. The DU165may support one or multiple different cells (e.g., via one or more RUs170). In some cases, a functional split between a CU160and a DU165, or between a DU165and an RU170may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU160, a DU165, or an RU170, while other functions of the protocol layer are performed by a different one of the CU160, the DU165, or the RU170). A CU160may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU160may be connected to one or more DUs165via a midhaul communication link162(e.g., F1, F1-c, F1-u), and a DU165may be connected to one or more RUs170via a fronthaul communication link168(e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link162or a fronthaul communication link168may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities105that are in communication via such communication links.

In wireless communications systems (e.g., wireless communications system100), 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 network130). In some cases, in an IAB network, one or more network entities105(e.g., IAB nodes104) may be partially controlled by each other. One or more IAB nodes104may be referred to as a donor entity or an IAB donor. One or more DUs165or one or more RUs170may be partially controlled by one or more CUs160associated with a donor network entity105(e.g., a donor base station140). The one or more donor network entities105(e.g., IAB donors) may be in communication with one or more additional network entities105(e.g., IAB nodes104) via supported access and backhaul links (e.g., backhaul communication links120). IAB nodes104may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs165of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs115, or may share the same antennas (e.g., of an RU170) of an IAB node104used for access via the DU165of the IAB node104(e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes104may include DUs165that support communication links with additional entities (e.g., IAB nodes104, UEs115) 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 nodes104or components of IAB nodes104) 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 nodes104, and one or more UEs115. The IAB donor may facilitate connection between the core network130and the AN (e.g., via a wired or wireless connection to the core network130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network130. The IAB donor may include a CU160and at least one DU165(e.g., and RU170), in which case the CU160may communicate with the core network130via an interface (e.g., a backhaul link). IAB donor and IAB nodes104may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally, or alternatively, the CU160may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs160(e.g., a CU160associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.

An IAB node104may refer to a RAN node that provides IAB functionality (e.g., access for UEs115, wireless self-backhauling capabilities). A DU165may act as a distributed scheduling node towards child nodes associated with the IAB node104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node104. 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 nodes104). Additionally, or alternatively, an IAB node104may also be referred to as a parent node or a child node to other IAB nodes104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes104may provide a Uu interface for a child IAB node104to receive signaling from a parent IAB node104, and the DU interface (e.g., DUs165) may provide a Uu interface for a parent IAB node104to signal to a child IAB node104or UE115.

For example, IAB node104may 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 CU160with a wired or wireless connection (e.g., a backhaul communication link120) to the core network130and may act as parent node to IAB nodes104. For example, the DU165of IAB donor may relay transmissions to UEs115through IAB nodes104, or may directly signal transmissions to a UE115, or both. The CU160of IAB donor may signal communication link establishment via an F1 interface to IAB nodes104, and the IAB nodes104may schedule transmissions (e.g., transmissions to the UEs115relayed from the IAB donor) through the DUs165. That is, data may be relayed to and from IAB nodes104via signaling via an NR Uu interface to MT of the IAB node104. Communications with IAB node104may be scheduled by a DU165of IAB donor and communications with IAB node104may be scheduled by DU165of IAB node104.

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 wake-up signal traffic indication techniques for wireless communications as described herein. For example, some operations described as being performed by a UE115or a network entity105(e.g., a base station140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes104, DUs165, CUs160, RUs170, RIC175, SMO180).

A UE115may 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 UE115may 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 UE115may 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 UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the network entities105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1.

The UEs115and the network entities105may wirelessly communicate with one another via one or more communication links125(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 links125. For example, a carrier used for a communication link125may 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 system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may 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 entity105and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity105, may refer to any portion of a network entity105(e.g., a base station140, a CU160, a DU165, a RU170) of a RAN communicating with another device (e.g., directly or via one or more other network entities105).

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 UEs115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs115via 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 links125shown in the wireless communications system100may include downlink transmissions (e.g., forward link transmissions) from a network entity105to a UE115, uplink transmissions (e.g., return link transmissions) from a UE115to a network entity105, 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 system100. 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 system100(e.g., the network entities105, the UEs115, 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 system100may include network entities105or UEs115that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE115may 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 UE115.

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 UE115may 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 UE115may be restricted to one or more active BWPs.

The time intervals for the network entities105or the UEs115may 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 Δfmaxmay represent a supported subcarrier spacing, and Nfmay 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 systems100, 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 system100and 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 system100may 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 UEs115. For example, one or more of the UEs115may 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 UEs115and UE-specific search space sets for sending control information to a specific UE115.

A network entity105may 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 entity105(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 area110or a portion of a coverage area110(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 entity105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas110, 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 UEs115with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity105(e.g., a lower-powered base station140), 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 UEs115with service subscriptions with the network provider or may provide restricted access to the UEs115having an association with the small cell (e.g., the UEs115in a closed subscriber group (CSG), the UEs115associated with users in a home or office). A network entity105may 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 entity105(e.g., a base station140, an RU170) may be movable and therefore provide communication coverage for a moving coverage area110. In some examples, different coverage areas110associated with different technologies may overlap, but the different coverage areas110may be supported by the same network entity105. In some other examples, the overlapping coverage areas110associated with different technologies may be supported by different network entities105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the network entities105provide coverage for various coverage areas110using the same or different radio access technologies.

The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC). The UEs115may 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 UE115may be configured to support communicating directly with other UEs115via a device-to-device (D2D) communication link135(e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs115of a group that are performing D2D communications may be within the coverage area110of a network entity105(e.g., a base station140, an RU170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity105. In some examples, one or more UEs115of such a group may be outside the coverage area110of a network entity105or may be otherwise unable to or not configured to receive transmissions from a network entity105. In some examples, groups of the UEs115communicating via D2D communications may support a one-to-many (1:M) system in which each UE115transmits to each of the other UEs115in the group. In some examples, a network entity105may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs115without an involvement of a network entity105.

The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MIME), 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 UEs115served by the network entities105(e.g., base stations140) associated with the core network130. 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 services150for one or more network operators. The IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

The wireless communications system100may 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 UEs115located 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 system100may 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 system100may support millimeter wave (mmW) communications between the UEs115and the network entities105(e.g., base stations140, RUs170), 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 system100may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system100may 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 entities105and the UEs115may 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 entity105(e.g., a base station140, an RU170) or a UE115may 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 entity105or a UE115may 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 entity105may be located at diverse geographic locations. A network entity105may include an antenna array with a set of rows and columns of antenna ports that the network entity105may use to support beamforming of communications with a UE115. Likewise, a UE115may 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.

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 entity105, a UE115) 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 entity105or a UE115may use beam sweeping techniques as part of beamforming operations. For example, a network entity105(e.g., a base station140, an RU170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity105multiple times along different directions. For example, the network entity105may 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 entity105, or by a receiving device, such as a UE115) a beam direction for later transmission or reception by the network entity105.

Some signals, such as data signals associated with a particular receiving device, may be transmitted by transmitting device (e.g., a transmitting network entity105, a transmitting UE115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity105or a receiving UE115). 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 UE115may receive one or more of the signals transmitted by the network entity105along different directions and may report to the network entity105an indication of the signal that the UE115received with a highest signal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a network entity105or a UE115) 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 entity105to a UE115). The UE115may 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 entity105may 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 UE115may 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 entity105(e.g., a base station140, an RU170), a UE115may 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 UE115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

A receiving device (e.g., a UE115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity105), 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 system100may 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 UE115and a network entity105or a core network130supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

In some cases, in order to reduce network power consumption, a network entity105may transition to a sleep mode or idle mode in which transmit and receive circuitry is powered down. Such network entities105may use periodic active periods to monitor for a WUS from a served device such as a UE115. If the network entity105does not detect a WUS, it may transition back to the sleep mode. If one or more WUS is detected the network entity105may maintain an active mode, or initiate an active mode in addition to periods during which WUSs are monitored. In some cases, such sleep mode operations may be implemented on one or more cells that are served by the network entity105. In some cases, a UE115may be configured with a periodicity at which WUSs may be transmitted in accordance with periods during which a cell will monitor for WUSs, which may be referred to as WUS occasions. If data traffic is present in the UE115transmit buffer, the UE115may transmit a WUS during a WUS occasion to trigger the cell to start or maintain an active state to allow for communications of the UE115data traffic.

In accordance with various aspects discussed herein, techniques are provided in which a WUS may provide information in addition to a binary indication of whether the UE115has traffic in a transmit buffer. In some cases, a WUS configuration may be provided to a UE115that allows the selection of a particular WUS to indicate one or more attributes of traffic that is present at the UE115. A network entity105that receives the WUS may use the indication to adjust a wake-up timing, a duration of an associated active period, or any combinations thereof. In some implementations, a WUS may provide an indication that a cell served by a network entity105is to wake-up, and also convey information such as buffer status, power headroom, a priority of traffic, latency targets of the traffic, or any combinations thereof. In some cases, the UE115may also give a recommendation on how long the network should stay awake. The network entity105may use such information to set one or more parameters for an active period.

FIG.2illustrates an example of a wireless communications system200that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The wireless communications system200may implement or be implemented by aspects of the wireless communications system100. For example, the wireless communications system200may include a network entity105-aand a UE115-a, which may be examples of a network entity105(e.g., an RU170, a DU165, a CU160, a base station140, or some combination thereof) and a UE115as described with reference toFIG.1. The network entity105-aand the UE115-amay communicate with one another via an uplink channel205-aand a downlink channel205-b, which may be examples or components of a communication link125as described with reference toFIG.1. The UE115-aand network entity105-amay support techniques for WUS transmissions that indicate one or more attributes of traffic that is present at the UE115-a. By providing information related to the traffic that is present at the UE115-a, the UE115-aand network entity105-amay promote resource efficiency and reduced power consumption for the wireless communications system200.

In the example ofFIG.2, the network entity105-amay transmit configuration information210to the UE115-a. In some cases, the configuration information210may include information related to cell sleep and active mode periods and WUS occasions. The network entity105-amay initiate a sleep procedure at a cell (e.g., a SCell or PCell that is configured at the UE115-a) based on the configuration information210. In the event that the UE115-ahas traffic in a transmit buffer, the UE115-amay transmit a WUS215during a WUS occasion based on the configuration information210. The network entity105-amay detect the WUS215, and transmit a response message220to the UE115-a.

In accordance with various aspects discussed herein, the WUS215may provide an indication of one or more attributes of the data traffic in the UE115-atransmit buffer. In some cases, the configuration information210may provide a WUS215configuration that allows the WUS to indicate the one or more attributes of the traffic that is present at the UE115-a. For example, a set of WUSs215may include two or more subsets of random access channel (RACH) preambles, where a RACH preamble selection from one of the subsets may indicate the associated one or more attributes of the data traffic. Additionally, or alternatively, the WUS215may be transmitted via a PUCCH (e.g., a SR transmitted via PUCCH), and the WUS215configuration may provide that a payload that is included with the WUS215may indicate the one or more attributes of the data traffic. The network entity105-a, upon receipt of the WUS215, may use the indication to adjust a wake-up timing, determine a duration of an associated active period, activate one or more antenna ports and associated components, or any combinations thereof. In some implementations, the WUS215may convey information such as buffer status, power headroom, a priority of traffic, latency targets of the traffic, or any combinations thereof. In some cases, the UE115-amay also give a recommendation on how long the network should stay awake. In some cases, the configuration information210may be signaled to the UE115-avia RRC signaling, via system information associated with the cell (e.g., via a master information block (MIB), one or more system information block (SIB), or any combinations thereof), may be preconfigured in a communications specification, or any combinations thereof. In some cases, the UE115-amay be configured to monitor for the response message220(e.g., DCI that indicates scheduling information and a resource allocation, a RACH response, etc.) based on the transmitted WUS215. For example, if the UE115-aindicates a high priority or low latency requirement in the WUS215, the UE115-amay expect a scheduling information transmission (e.g., in DCI transmitted via a PDCCH) in an earlier response window than if a lower priority or higher latency is indicated.

FIG.3illustrates an example of a WUS timing300that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The WSU timing300may be implemented by aspects of the wireless communications system100or200. For example, a UE115-band network entity105-b, which may be examples of UEs115and network entities105ofFIGS.1and2, may implement the WUS timing300. As discussed herein, network entity105-bmay transition between a sleep mode305and an active mode310, where the sleep mode305has lower power consumption than the active mode. A WUS configuration may be provided that may trigger the network entity105-bto remain in the active mode310for communications, thus allowing for reduced network power consumption and efficient wake-up procedures, which may enhance overall network efficiency and user experience.

In the example ofFIG.3, the network entity105-benters sleep mode305that provides network power saving, in which periodic active modes310may be used to monitor for wake-up signals and maintain network operation. In some cases, a sleep procedure may be enabled at the network entity105-bbased on traffic loads that are being served. For example, during certain hours (e.g., night hours in office areas) there may have relatively light traffic or no traffic for a cell, and the sleep procedure may help save network power and operational cost. In some cases, different sleep modes may be configured, where some sleep modes will turn off RF chains at the network entity105-bwhile others may not, and thus different sleep modes have different power consumption and require different transition times. However, one or more cells that may implement sleep modes that are served by the network entity105-bmay still have connections with UE115-b, and thus the cell should be aware of whether the UE115-bneeds to go into a connected state or perform some SDT, so that the active mode310can be triggered. In the example ofFIG.3, the network entity105-bmay configure periodic occasions for monitoring for a WUS335, which include a first WUS occasion315and a second WUS occasion325in this example. In this example, during active period320associated with the first WUS occasion315, the network entity105-bmay not detect a WUS and may transition back to sleep mode305. During active period330associated with second WUS occasion325, the network entity105-bmay detect WUS335from the UE115-b, and may maintain the active mode310beyond the duration of the second WUS occasion325in order to provide communications with the UE115-b.

As discussed herein, the WUS335may take different forms such as a RACH preamble or PUCCH transmission. In the example ofFIG.3, the WUS335may be a RACH request340that includes a RACH preamble. In some cases, the RACH preamble may be selected from a set of RACH preambles345, in which a first subset of RACH preambles350and a second subset of RACH preamble355may be associated with different sets of attributes of data traffic of the UE115-b. In some cases, the traffic attributes may include one or more of a buffer status of the UE115-b, an available power headroom at the UE115-b, a signal priority associated with the data traffic, latency targets associated with the data traffic, or any combinations thereof. In some cases, the UE115-bmay also give a recommendation on how long the network should stay in the active mode310(e.g., a time duration T1). In some implementations, the first subset of RACH preambles350may be associated with a first set of attributes of the data traffic, and the second subset of RACH preambles355may be associated with a second set of attributes of the data traffic, and WUS configuration information may provide different attributes of data traffic that are associated with each subset of RACH preambles350and355. In some cases, the WUS configuration information may be transmitted via RRC signaling as part of or after a connection establishment between the UE115-band the network entity105-b. In other cases, other signaling may be used to convey the WUS configuration, such as system information signaling, one or more medium access control (MAC) control elements (CEs), or any combinations thereof.

In some cases, the WUS configuration may provide a table, such as in the below Table 1, in which different subsets or RACH preambles may be associated with different sets of traffic attributes:

TABLE 1PreambleBufferLatencyGroupstatusPHRPriorityTargetRequested T1AShortXLowLowAbufferBLongYLowLowBbufferCShortZHighHighCbuffer
In this example, three subsets of RACH preambles are configured from a set of available RACH preambles, in which a first subset of RACH preambles (e.g., preamble group A) is associated with a short transmit buffer (e.g., where data in the UE115-btransmit buffer is less than a threshold value provided with the WUS configuration), a first power headroom (PHR) status (e.g., where PHR at the UE115-bis within a PHR range or above/below a PHR threshold value provided with the WUS configuration), a low traffic priority (e.g., a priority of the data traffic is below a priority threshold or in an associated priority category), a low latency target (e.g., a latency target of the data traffic is less than a latency threshold), and a first requested time duration (T1=A) of the active mode (e.g., a T1 value that is within a T1 range or above/below a T1 threshold value). In the example of Table 1, a second subset of RACH preambles (e.g., preamble group B) is associated with a long transmit buffer, a second PHR status, a low traffic priority, a low latency target, and a second requested time duration (T1=B). Likewise, a third subset of RACH preambles (e.g., preamble group C) is associated with a short transmit buffer, a third PHR status, a higher traffic priority, a higher latency target, and a third requested time duration (T1=C). It is to be understood that Table 1 is provided as one example of different subsets of RACH preambles and associated data traffic attributes, and numerous other examples of such tables may be readily formulated and are within the scope of the present disclosure, such as examples which may have more or fewer subsets of preambles, more of fewer corresponding traffic attributes, and the like. In other examples, additionally or alternatively, the WUS may be transmitted in a PUCCH transmission, such as illustrated in the example ofFIG.4.

FIG.4illustrates an example of a wake-up signal timing400that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The WSU timing400may be implemented by aspects of the wireless communications system100or200. For example, a UE115-cand network entity105-c, which may be examples of UEs115and network entities105ofFIGS.1and2, may implement the WUS timing400. As discussed herein, network entity105-cmay transition between a sleep mode405and an active mode410, where the sleep mode405has lower power consumption than the active mode410. A WUS configuration may be provided that may trigger the network entity105-cto remain in the active mode410for communications, thus allowing for reduced network power consumption and efficient wake-up procedures, which may enhance overall network efficiency and user experience.

In the example ofFIG.4, the network entity105-centers sleep mode405that provides network power saving, in which periodic active modes410may be used to monitor for wake-up signals and maintain network operation, similarly as discussed with reference toFIG.3. In this example, the network entity105-cagain may configure periodic occasions for monitoring for a WUS435, which include a first WUS occasion415and a second WUS occasion425. In this example, during active period420associated with the first WUS occasion415, the network entity105-cmay not detect a WUS and may transition back to sleep mode405. During active period430associated with second WUS occasion425, the network entity105-cmay detect WUS435from the UE115-c, and may maintain the active mode410beyond the duration of the second WUS occasion425in order to provide communications with the UE115-c.

In this example, the WUS435may be provided via a PUCCH, and may include a PUCCH indication440and a payload445that indicates one or more traffic attributes of data traffic at the UE115-c. The payload445of the PUCCH may convey similar information as discussed with reference toFIG.3, such as a size of the data buffer, a PHR status, a traffic priority, a latency target, a requested time duration (T1), or any combinations thereof. In some cases, separate fields for each traffic attribute may be provided in payload445. In other cases, the network entity105-cmay configure a table with index values, in which each index value is associated with one or more traffic attributes similarly as discussed with reference to Table 1, and the payload445may include the index value associated with the one or more attributes.

In some cases, a UE115as discussed herein may monitor for one or more transmissions based on a particular WUS indication that is transmitted. For example, if the UE115indicated low latency target is associated with data in the transmit buffer, the UE115may monitor for a responsive downlink control channel (e.g., PDCCH) transmission in an earlier response window than if a higher latency target was indicated.

FIG.5illustrates an example of a process flow500that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The process flow500may include a network entity105-dand a UE115-d, which may be examples of a network entity105and a UE115as described with reference toFIGS.1through4. The process flow500may be implemented by the network entity105-dand the UE115-dwhere a WUS from the UE115-dprovides an indication of one or more attributes of data traffic that is present to be transmitted by the UE115-d. Such techniques may provide for power savings at the network entity105-dassociated with a sleep mode, while also enabling faster indication of traffic attributes to the network entity105-dwhich may adjust its behavior based on the WUS indication, which may thereby enhance overall network efficiency and user experience. In the following description of the process flow500, the operations between the network entity105-dand the UE115-dmay be performed in a different order than the example order shown. Some operations may be omitted from the process flow500, and other operations may be added to the process flow500.

At505, the network entity105-dmay transmit, and the UE115-dmay receive, configuration information associated with WUS transmissions. As discussed herein, such configuration information may provide characteristics of WUS occasions, such as, for example, a duration of WUS occasions (e.g., a time duration or number of symbols/slots), a periodicity of WUS occasions (e.g., time period, number of symbols/slots and symbol/slot offset), a frequency band or bandwidth part (BWP), or any combinations thereof. In some cases, the configuration information may be provided via RRC signaling. In some cases, additionally or alternatively, the configuration information may be provided with one or more system information transmissions (e.g., SIB/MIB transmissions), in one or more control channel transmissions (e.g., in DCI), and/or in one or more MAC-CE transmissions.

At510, the network entity105-dmay transition to a sleep mode. In some cases, the sleep mode may be a relatively low power mode at the network entity105-din which some or all transmit/receive components are powered down. At515, the network entity105-dmay transition to an active mode to monitor for a WUS. In some cases, the transition to the active mode may be performed in accordance with a WUS occasion periodicity that is indicated in the configuration information.

At520, the UE115-dmay identify that data traffic is present in a transmit buffer, and may determine one or more attributes of the data traffic. For example, the UE115-dmay determine a priority and latency target associated with the data traffic, an amount of data traffic that is present, a PHR of the UE115-d, or any combinations thereof. In some cases, the UE115-dmay also identify a time duration (T1) that is likely to be used for transmission of the data traffic. At525, the UE115-dmay select a WUS based on the one or more attributes of the data traffic. For example, the UE115-dmay select a RACH preamble or a PUCCH payload as discussed with reference toFIGS.3and4.

At530, the UE115-dmay transmit the WUS to the network entity105-d. As discussed herein, the WUS may be transmitted during a WUS occasion, and the network entity105-d, at535, may detect the WUS. At540, the network entity105-dmay determine one or more active mode parameters based on the one or more attributes indicated by the WUS. In some cases, the network entity105-dmay determine the one or more attributes based on a preamble that is used for the WUS, or a payload content of the WUS. The network entity105-dmay determine, for example, a time duration for the active mode (e.g., based on a T1 indication, buffer size indication, or both), resources that are to be allocated for associated data transmissions (e.g., based on a buffer size indication, a priority of the traffic, a latency target for the traffic, or any combinations thereof), one or more transmission parameters for an associated uplink transmissions (e.g., a MCS based on channel conditions and an indicated PHR), or any combinations thereof. At545, the network entity105-dmay transmit a response message, which may be received at the UE115-d. In some cases, a timing of the response message may be based on one or more attributes indicated by the WUS (e.g., a low latency indication in the WUS may prompt the response message transmission earlier in a response window, and a higher latency indication in the WUS may prompt the response message later in the response window). In some cases, the response message may include a random access response, or a DCI with a resource allocation for an associated uplink transmission.

FIG.6shows a block diagram600of a device605that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The device605may be an example of aspects of a UE115as described herein. The device605may include a receiver610, a transmitter615, and a communications manager620. The device605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver610may 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 wake-up signal traffic indication techniques for wireless communications). Information may be passed on to other components of the device605. The receiver610may utilize a single antenna or a set of multiple antennas.

The transmitter615may provide a means for transmitting signals generated by other components of the device605. For example, the transmitter615may 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 wake-up signal traffic indication techniques for wireless communications). In some examples, the transmitter615may be co-located with a receiver610in a transceiver module. The transmitter615may utilize a single antenna or a set of multiple antennas.

The communications manager620, the receiver610, the transmitter615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include 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 a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager620, the receiver610, the transmitter615, 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 a means for performing the functions described in the present disclosure).

In some examples, the communications manager620may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver610, the transmitter615, or both. For example, the communications manager620may receive information from the receiver610, send information to the transmitter615, or be integrated in combination with the receiver610, the transmitter615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager620may support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager620may be configured as or otherwise support a means for receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The communications manager620may be configured as or otherwise support a means for selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The communications manager620may be configured as or otherwise support a means for transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal.

By including or configuring the communications manager620in accordance with examples as described herein, the device605(e.g., a processor controlling or otherwise coupled with the receiver610, the transmitter615, the communications manager620, or a combination thereof) may support techniques for WUS transmissions that indicate traffic attributes of a UE that is transmitting the WUS. Such techniques may provide for enhanced sleep and active mode transitions at a network entity, which may reduce network power consumption and allow for more efficient utilization of communication resources. Further, latency for communications may be reduced and reliability enhanced through indications of traffic priority or latency targets that may be used at the network entity to select active mode durations and parameters.

FIG.7shows a block diagram700of a device705that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The device705may be an example of aspects of a device605or a UE115as described herein. The device705may include a receiver710, a transmitter715, and a communications manager720. The device705may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver710may 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 wake-up signal traffic indication techniques for wireless communications). Information may be passed on to other components of the device705. The receiver710may utilize a single antenna or a set of multiple antennas.

The transmitter715may provide a means for transmitting signals generated by other components of the device705. For example, the transmitter715may 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 wake-up signal traffic indication techniques for wireless communications). In some examples, the transmitter715may be co-located with a receiver710in a transceiver module. The transmitter715may utilize a single antenna or a set of multiple antennas.

The device705, or various components thereof, may be an example of means for performing various aspects of wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communications manager720may include a configuration manager725, a WUS selection manager730, a WUS transmission manager735, or any combination thereof. The communications manager720may be an example of aspects of a communications manager620as described herein. In some examples, the communications manager720, 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 receiver710, the transmitter715, or both. For example, the communications manager720may receive information from the receiver710, send information to the transmitter715, or be integrated in combination with the receiver710, the transmitter715, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager720may support wireless communication at a UE in accordance with examples as disclosed herein. The configuration manager725may be configured as or otherwise support a means for receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The WUS selection manager730may be configured as or otherwise support a means for selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The WUS transmission manager735may be configured as or otherwise support a means for transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal.

FIG.8shows a block diagram800of a communications manager820that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The communications manager820may be an example of aspects of a communications manager620, a communications manager720, or both, as described herein. The communications manager820, or various components thereof, may be an example of means for performing various aspects of wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communications manager820may include a configuration manager825, a WUS selection manager830, a WUS transmission manager835, a RACH preamble manager840, a WUS payload manager845, a WUS response manager850, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager820may support wireless communication at a UE in accordance with examples as disclosed herein. The configuration manager825may be configured as or otherwise support a means for receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The WUS selection manager830may be configured as or otherwise support a means for selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The WUS transmission manager835may be configured as or otherwise support a means for transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal. In some examples, the first wake-up signal is a random access request transmitted via a RACH, or is request that is transmitted via a control channel.

In some examples, to support selecting the first wake-up signal, the WUS selection manager830may be configured as or otherwise support a means for selecting the first wake-up signal from the set of wake-up signals based on a transmit buffer status of the UE, a power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combinations thereof. In some examples, to support selecting the first wake-up signal, the WUS selection manager830may be configured as or otherwise support a means for selecting the first wake-up signal from the set of wake-up signals based on a time duration that the cell is requested to be in the active state.

In some examples, the set of wake-up signals includes a set of random access preambles, and one or more of the random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE. In some examples, the set of random access preambles includes two or more different subsets of random access preambles, and where each of the two or more different subsets of random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE.

In some examples, the configuration information is received via RRC signaling. In some examples, the RRC signaling maps each subset of the two or more different subsets of random access preambles to a different combination of two or more attributes of traffic that is to be transmitted from the UE.

In some examples, to support transmitting the first wake-up signal, the WUS payload manager845may be configured as or otherwise support a means for transmitting an uplink control channel transmission that includes a payload that indicates the one or more different attributes of traffic that is to be transmitted from the UE. In some examples, the payload includes an index value of a set of index values, where each index value of the set of index values is mapped to a different combination of two or more attributes of traffic that is to be transmitted from the UE.

In some examples, the WUS response manager850may be configured as or otherwise support a means for monitoring for a response communication from the cell based on the first attribute indication of the first wake-up signal. In some examples, to support monitoring, the WUS response manager850may be configured as or otherwise support a means for monitoring for a downlink control channel communication in a time window that is based on a latency associated with the first attribute indication of the first wake-up signal.

FIG.9shows a diagram of a system900including a device905that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The device905may be an example of or include the components of a device605, a device705, or a UE115as described herein. The device905may communicate (e.g., wirelessly) with one or more network entities105, one or more UEs115, or any combination thereof. The device905may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager920, an input/output (I/O) controller910, a transceiver915, an antenna925, a memory930, code935, and a processor940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus945).

The I/O controller910may manage input and output signals for the device905. The I/O controller910may also manage peripherals not integrated into the device905. In some cases, the I/O controller910may represent a physical connection or port to an external peripheral. In some cases, the I/O controller910may 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 controller910may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller910may be implemented as part of a processor, such as the processor940. In some cases, a user may interact with the device905via the I/O controller910or via hardware components controlled by the I/O controller910.

In some cases, the device905may include a single antenna925. However, in some other cases, the device905may have more than one antenna925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver915may communicate bi-directionally, via the one or more antennas925, wired, or wireless links as described herein. For example, the transceiver915may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver915may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas925for transmission, and to demodulate packets received from the one or more antennas925. The transceiver915, or the transceiver915and one or more antennas925, may be an example of a transmitter615, a transmitter715, a receiver610, a receiver710, or any combination thereof or component thereof, as described herein.

The memory930may include random access memory (RAM) and read-only memory (ROM). The memory930may store computer-readable, computer-executable code935including instructions that, when executed by the processor940, cause the device905to perform various functions described herein. The code935may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code935may not be directly executable by the processor940but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory930may 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 processor940may 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 processor940may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor940. The processor940may be configured to execute computer-readable instructions stored in a memory (e.g., the memory930) to cause the device905to perform various functions (e.g., functions or tasks supporting wake-up signal traffic indication techniques for wireless communications). For example, the device905or a component of the device905may include a processor940and memory930coupled with or to the processor940, the processor940and memory930configured to perform various functions described herein.

The communications manager920may support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager920may be configured as or otherwise support a means for receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The communications manager920may be configured as or otherwise support a means for selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The communications manager920may be configured as or otherwise support a means for transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal.

By including or configuring the communications manager920in accordance with examples as described herein, the device905may support techniques for WUS transmissions that indicate traffic attributes of a UE that is transmitting the WUS. Such techniques may provide for enhanced sleep and active mode transitions at a network entity, which may reduce network power consumption and allow for more efficient utilization of communication resources. Further, latency for communications may be reduced and reliability enhanced through indications of traffic priority or latency targets that may be used at the network entity to select active mode durations and parameters.

In some examples, the communications manager920may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver915, the one or more antennas925, or any combination thereof. Although the communications manager920is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager920may be supported by or performed by the processor940, the memory930, the code935, or any combination thereof. For example, the code935may include instructions executable by the processor940to cause the device905to perform various aspects of wake-up signal traffic indication techniques for wireless communications as described herein, or the processor940and the memory930may be otherwise configured to perform or support such operations.

FIG.10shows a block diagram1000of a device1005that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The device1005may be an example of aspects of a network entity105as described herein. The device1005may include a receiver1010, a transmitter1015, and a communications manager1020. The device1005may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1010may 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 device1005. In some examples, the receiver1010may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver1010may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

The transmitter1015may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device1005. For example, the transmitter1015may 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 transmitter1015may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter1015may 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 transmitter1015and the receiver1010may be co-located in a transceiver, which may include or be coupled with a modem.

The communications manager1020, the receiver1010, the transmitter1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include 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 a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager1020, the receiver1010, the transmitter1015, 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 a means for performing the functions described in the present disclosure).

In some examples, the communications manager1020may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1010, the transmitter1015, or both. For example, the communications manager1020may receive information from the receiver1010, send information to the transmitter1015, or be integrated in combination with the receiver1010, the transmitter1015, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager1020may support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communications manager1020may be configured as or otherwise support a means for transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The communications manager1020may be configured as or otherwise support a means for receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion. The communications manager1020may be configured as or otherwise support a means for determining one or more parameters associated with a transition to an active state for communications with the UE based on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

By including or configuring the communications manager1020in accordance with examples as described herein, the device1005(e.g., a processor controlling or otherwise coupled with the receiver1010, the transmitter1015, the communications manager1020, or a combination thereof) may support techniques for WUS transmissions that indicate traffic attributes of a UE that is transmitting the WUS. Such techniques may provide for enhanced sleep and active mode transitions at a network entity, which may reduce network power consumption and allow for more efficient utilization of communication resources. Further, latency for communications may be reduced and reliability enhanced through indications of traffic priority or latency targets that may be used at the network entity to select active mode durations and parameters.

FIG.11shows a block diagram1100of a device1105that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The device1105may be an example of aspects of a device1005or a network entity105as described herein. The device1105may include a receiver1110, a transmitter1115, and a communications manager1120. The device1105may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1110may 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 device1105. In some examples, the receiver1110may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver1110may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

The transmitter1115may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device1105. For example, the transmitter1115may 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 transmitter1115may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter1115may 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 transmitter1115and the receiver1110may be co-located in a transceiver, which may include or be coupled with a modem.

The device1105, or various components thereof, may be an example of means for performing various aspects of wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communications manager1120may include a configuration manager1125, a WUS monitoring manager1130, an active state manager1135, or any combination thereof. The communications manager1120may be an example of aspects of a communications manager1020as described herein. In some examples, the communications manager1120, 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 receiver1110, the transmitter1115, or both. For example, the communications manager1120may receive information from the receiver1110, send information to the transmitter1115, or be integrated in combination with the receiver1110, the transmitter1115, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager1120may support wireless communication at a network entity in accordance with examples as disclosed herein. The configuration manager1125may be configured as or otherwise support a means for transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The WUS monitoring manager1130may be configured as or otherwise support a means for receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion. The active state manager1135may be configured as or otherwise support a means for determining one or more parameters associated with a transition to an active state for communications with the UE based on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

FIG.12shows a block diagram1200of a communications manager1220that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The communications manager1220may be an example of aspects of a communications manager1020, a communications manager1120, or both, as described herein. The communications manager1220, or various components thereof, may be an example of means for performing various aspects of wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communications manager1220may include a configuration manager1225, a WUS monitoring manager1230, an active state manager1235, a RACH preamble manager1240, a WUS attribute manager1245, a WUS payload manager1250, a WUS response manager1255, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity105, between devices, components, or virtualized components associated with a network entity105), or any combination thereof.

The communications manager1220may support wireless communication at a network entity in accordance with examples as disclosed herein. The configuration manager1225may be configured as or otherwise support a means for transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The WUS monitoring manager1230may be configured as or otherwise support a means for receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion. The active state manager1235may be configured as or otherwise support a means for determining one or more parameters associated with a transition to an active state for communications with the UE based on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

In some examples, the first wake-up signal is a random access request transmitted via a RACH, or is request that is transmitted via a control channel. In some examples, the one or more different attributes of traffic that is to be transmitted from the UE include one or more of a transmit buffer status of the UE, a power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combinations thereof. In some examples, the first wake-up signal further indicates a time duration requested for the active state for communications with the UE.

In some examples, the set of wake-up signals includes a set of random access preambles, and one or more of the random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE. In some examples, the set of random access preambles includes two or more different subsets of random access preambles, and where each of the two or more different subsets of random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE.

In some examples, the configuration information is transmitted via RRC signaling. In some examples, the RRC signaling maps each subset of the two or more different subsets of random access preambles to a different combination of two or more attributes of traffic that is to be transmitted from the UE.

In some examples, to support receiving the first wake-up signal, the WUS payload manager1250may be configured as or otherwise support a means for receiving an uplink control channel transmission that includes a payload that indicates the one or more different attributes of traffic that is to be transmitted from the UE. In some examples, the payload includes an index value of a set of index values, where each index value of the set of index values is mapped to a different combination of two or more attributes of traffic that is to be transmitted from the UE.

In some examples, the WUS response manager1255may be configured as or otherwise support a means for transmitting a response communication to the UE based on the first attribute indicated by the first wake-up signal. In some examples, a timing for transmission of the response communication is based on a latency associated with the first attribute indicated by the first wake-up signal.

FIG.13shows a diagram of a system1300including a device1305that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The device1305may be an example of or include the components of a device1005, a device1105, or a network entity105as described herein. The device1305may communicate with one or more network entities105, one or more UEs115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device1305may include components that support outputting and obtaining communications, such as a communications manager1320, a transceiver1310, an antenna1315, a memory1325, code1330, and a processor1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1340).

The transceiver1310may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver1310may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver1310may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device1305may include one or more antennas1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver1310may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas1315, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas1315, from a wired receiver), and to demodulate signals. In some implementations, the transceiver1310may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas1315that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas1315that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver1310may 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 transceiver1310, or the transceiver1310and the one or more antennas1315, or the transceiver1310and the one or more antennas1315and one or more processors or memory components (for example, the processor1335, or the memory1325, or both), may be included in a chip or chip assembly that is installed in the device1305. In some examples, the transceiver may be operable to support communications via one or more communications links (e.g., a communication link125, a backhaul communication link120, a midhaul communication link162, a fronthaul communication link168).

The memory1325may include RAM and ROM. The memory1325may store computer-readable, computer-executable code1330including instructions that, when executed by the processor1335, cause the device1305to perform various functions described herein. The code1330may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1330may not be directly executable by the processor1335but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1325may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1335may 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 processor1335may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1335. The processor1335may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1325) to cause the device1305to perform various functions (e.g., functions or tasks supporting wake-up signal traffic indication techniques for wireless communications). For example, the device1305or a component of the device1305may include a processor1335and memory1325coupled with the processor1335, the processor1335and memory1325configured to perform various functions described herein. The processor1335may 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 code1330) to perform the functions of the device1305. The processor1335may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device1305(such as within the memory1325). In some implementations, the processor1335may 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 device1305). For example, a processing system of the device1305may refer to a system including the various other components or subcomponents of the device1305, such as the processor1335, or the transceiver1310, or the communications manager1320, or other components or combinations of components of the device1305. The processing system of the device1305may interface with other components of the device1305, 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 device1305may 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 device1305may 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 device1305may 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 bus1340may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus1340may 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 device1305, or between different components of the device1305that may be co-located or located in different locations (e.g., where the device1305may refer to a system in which one or more of the communications manager1320, the transceiver1310, the memory1325, the code1330, and the processor1335may be located in one of the different components or divided between different components).

In some examples, the communications manager1320may manage aspects of communications with a core network130(e.g., via one or more wired or wireless backhaul links). For example, the communications manager1320may manage the transfer of data communications for client devices, such as one or more UEs115. In some examples, the communications manager1320may manage communications with other network entities105, and may include a controller or scheduler for controlling communications with UEs115in cooperation with other network entities105. In some examples, the communications manager1320may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities105.

The communications manager1320may support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communications manager1320may be configured as or otherwise support a means for transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The communications manager1320may be configured as or otherwise support a means for receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion. The communications manager1320may be configured as or otherwise support a means for determining one or more parameters associated with a transition to an active state for communications with the UE based on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

By including or configuring the communications manager1320in accordance with examples as described herein, the device1305may support techniques for WUS transmissions that indicate traffic attributes of a UE that is transmitting the WUS. Such techniques may provide for enhanced sleep and active mode transitions at a network entity, which may reduce network power consumption and allow for more efficient utilization of communication resources. Further, latency for communications may be reduced and reliability enhanced through indications of traffic priority or latency targets that may be used at the network entity to select active mode durations and parameters.

In some examples, the communications manager1320may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver1310, the one or more antennas1315(e.g., where applicable), or any combination thereof. Although the communications manager1320is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1320may be supported by or performed by the transceiver1310, the processor1335, the memory1325, the code1330, or any combination thereof. For example, the code1330may include instructions executable by the processor1335to cause the device1305to perform various aspects of wake-up signal traffic indication techniques for wireless communications as described herein, or the processor1335and the memory1325may be otherwise configured to perform or support such operations.

FIG.14shows a flowchart illustrating a method1400that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method1400may be implemented by a UE or its components as described herein. For example, the operations of the method1400may be performed by a UE115as described with reference toFIGS.1through9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1405, the method may include receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by a configuration manager825as described with reference toFIG.8.

At1410, the method may include selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a WUS selection manager830as described with reference toFIG.8.

At1415, the method may include transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by a WUS transmission manager835as described with reference toFIG.8.

FIG.15shows a flowchart illustrating a method1500that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method1500may be implemented by a UE or its components as described herein. For example, the operations of the method1500may be performed by a UE115as described with reference toFIGS.1through9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1505, the method may include receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by a configuration manager825as described with reference toFIG.8.

At1510, the method may include selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by a WUS selection manager830as described with reference toFIG.8.

In some implementations, at1515, the method optionally may include selecting the first wake-up signal from the set of wake-up signals based on a transmit buffer status of the UE, a power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combinations thereof. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a WUS selection manager830as described with reference toFIG.8.

In some implementations, at1520, the method optionally may include selecting the first wake-up signal from the set of wake-up signals based on a time duration that the cell is requested to be in the active state. The operations of1520may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1520may be performed by a WUS selection manager830as described with reference toFIG.8.

At1525, the method may include transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal. The operations of1525may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1525may be performed by a WUS transmission manager835as described with reference toFIG.8.

FIG.16shows a flowchart illustrating a method1600that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method1600may be implemented by a UE or its components as described herein. For example, the operations of the method1600may be performed by a UE115as described with reference toFIGS.1through9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1605, the method may include receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by a configuration manager825as described with reference toFIG.8.

At1610, the method may include selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by a WUS selection manager830as described with reference toFIG.8.

At1615, the method may include transmitting an uplink control channel transmission that provides the first wake-up signal during a wake-up signal occasion, where the uplink control channel transmission includes a payload that indicates the one or more different attributes of traffic that is to be transmitted from the UE. The operations of1615may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1615may be performed by a WUS payload manager845as described with reference toFIG.8.

FIG.17shows a flowchart illustrating a method1700that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method1700may be implemented by a UE or its components as described herein. For example, the operations of the method1700may be performed by a UE115as described with reference toFIGS.1through9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1705, the method may include receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The operations of1705may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1705may be performed by a configuration manager825as described with reference toFIG.8.

At1710, the method may include selecting a first wake-up signal from the set of wake-up signals based on a first attribute of first traffic that is to be transmitted from the UE. The operations of1710may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1710may be performed by a WUS selection manager830as described with reference toFIG.8.

At1715, the method may include transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based on the first attribute indication of the first wake-up signal. The operations of1715may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1715may be performed by a WUS transmission manager835as described with reference toFIG.8.

At1720, the method may include monitoring for a response communication from the cell based on the first attribute indication of the first wake-up signal. The operations of1720may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1720may be performed by a WUS response manager850as described with reference toFIG.8.

In some implementations, at1725, the method optionally may include monitoring for a downlink control channel communication in a time window that is based on a latency associated with the first attribute indication of the first wake-up signal. The operations of1725may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1725may be performed by a WUS response manager850as described with reference toFIG.8.

FIG.18shows a flowchart illustrating a method1800that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method1800may be implemented by a network entity or its components as described herein. For example, the operations of the method1800may be performed by a network entity as described with reference toFIGS.1through5and10through13. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At1805, the method may include transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The operations of1805may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1805may be performed by a configuration manager1225as described with reference toFIG.12.

At1810, the method may include receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion. The operations of1810may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1810may be performed by a WUS monitoring manager1230as described with reference toFIG.12.

At1815, the method may include determining one or more parameters associated with a transition to an active state for communications with the UE based on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal. The operations of1815may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1815may be performed by an active state manager1235as described with reference toFIG.12.

FIG.19shows a flowchart illustrating a method1900that supports wake-up signal traffic indication techniques for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method1900may be implemented by a network entity or its components as described herein. For example, the operations of the method1900may be performed by a network entity as described with reference toFIGS.1through5and10through13. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At1905, the method may include transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE. The operations of1905may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1905may be performed by a configuration manager1225as described with reference toFIG.12.

At1910, the method may include receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion. The operations of1910may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1910may be performed by a WUS monitoring manager1230as described with reference toFIG.12.

At1915, the method may include determining one or more parameters associated with a transition to an active state for communications with the UE based on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal. The operations of1915may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1915may be performed by an active state manager1235as described with reference toFIG.12.

At1920, the method may include transmitting a response communication to the UE based on the first attribute indicated by the first wake-up signal. The operations of1920may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1920may be performed by a WUS response manager1255as described with reference toFIG.12.

The following provides an overview of aspects of the present disclosure:Aspect 1: A method for wireless communication at a UE, comprising: receiving configuration information for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE; selecting a first wake-up signal from the set of wake-up signals based at least in part on a first attribute of first traffic that is to be transmitted from the UE; and transmitting the first wake-up signal during a wake-up signal occasion to indicate to a cell that the cell is requested to be in an active state for a time period outside of the wake-up signal occasion based at least in part on the first attribute indication of the first wake-up signal.Aspect 2: The method of aspect 1, wherein the first wake-up signal is a random access request transmitted via a RACH, or is request that is transmitted via a control channel.Aspect 3: The method of any of aspects 1 through 2, wherein the selecting the first wake-up signal comprises: selecting the first wake-up signal from the set of wake-up signals based at least in part on a transmit buffer status of the UE, a power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combinations thereof.Aspect 4: The method of any of aspects 1 through 3, wherein the selecting the first wake-up signal further comprises: selecting the first wake-up signal from the set of wake-up signals based at least in part on a time duration that the cell is requested to be in the active state.Aspect 5: The method of any of aspects 1 through 4, wherein the set of wake-up signals includes a set of random access preambles, and one or more of the random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE.Aspect 6: The method of aspect 5, wherein the set of random access preambles includes two or more different subsets of random access preambles, and wherein each of the two or more different subsets of random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE.Aspect 7: The method of aspect 6, wherein the configuration information is received via RRC signaling.Aspect 8: The method of aspect 7, wherein the RRC signaling maps each subset of the two or more different subsets of random access preambles to a different combination of two or more attributes of traffic that is to be transmitted from the UE.Aspect 9: The method of any of aspects 1 through 8, wherein the transmitting the first wake-up signal comprises: transmitting an uplink control channel transmission that includes a payload that indicates the one or more different attributes of traffic that is to be transmitted from the UE.Aspect 10: The method of aspect 9, wherein the payload comprises an index value of a set of index values, wherein each index value of the set of index values is mapped to a different combination of two or more attributes of traffic that is to be transmitted from the UE.Aspect 11: The method of any of aspects 1 through 10, further comprising: monitoring for a response communication from the cell based at least in part on the first attribute indication of the first wake-up signal.Aspect 12: The method of aspect 11, wherein the monitoring comprises: monitoring for a downlink control channel communication in a time window that is based at least in part on a latency associated with the first attribute indication of the first wake-up signal.Aspect 13: A method for wireless communication at a network entity, comprising: transmitting configuration information to a UE for a wake-up signal transmission, the configuration information indicates a set of wake-up signals, each wake-up signal of the set of wake-up signals indicating one or more different attributes of traffic that is to be transmitted from the UE; receiving a first wake-up signal from the UE during a wake-up signal monitoring occasion; and determining one or more parameters associated with a transition to an active state for communications with the UE based at least in part on a first attribute of first traffic that is to be transmitted from the UE, the first attribute indicated by the first wake-up signal.Aspect 14: The method of aspect 13, wherein the first wake-up signal is a random access request transmitted via a RACH, or is request that is transmitted via a control channel.Aspect 15: The method of any of aspects 13 through 14, wherein the one or more different attributes of traffic that is to be transmitted from the UE include one or more of a transmit buffer status of the UE, a power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combinations thereof.Aspect 16: The method of any of aspects 13 through 15, wherein the first wake-up signal further indicates a time duration requested for the active state for communications with the UE.Aspect 17: The method of any of aspects 13 through 16, wherein the set of wake-up signals includes a set of random access preambles, and one or more of the random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE.Aspect 18: The method of aspect 17, wherein the set of random access preambles includes two or more different subsets of random access preambles, and wherein each of the two or more different subsets of random access preambles are mapped to the one or more different attributes of traffic that is to be transmitted from the UE.Aspect 19: The method of aspect 18, wherein the configuration information is transmitted via RRC signaling.Aspect 20: The method of aspect 19, wherein the RRC signaling maps each subset of the two or more different subsets of random access preambles to a different combination of two or more attributes of traffic that is to be transmitted from the UE.Aspect 21: The method of any of aspects 13 through 20, wherein the receiving the first wake-up signal comprises: receiving an uplink control channel transmission that includes a payload that indicates the one or more different attributes of traffic that is to be transmitted from the UE.Aspect 22: The method of aspect 21, wherein the payload comprises an index value of a set of index values, wherein each index value of the set of index values is mapped to a different combination of two or more attributes of traffic that is to be transmitted from the UE.Aspect 23: The method of any of aspects 13 through 22, further comprising: transmitting a response communication to the UE based at least in part on the first attribute indicated by the first wake-up signal.Aspect 24: The method of aspect 23, wherein a timing for transmission of the response communication is based at least in part on a latency associated with the first attribute indicated by the first wake-up signal.Aspect 25: An apparatus for wireless communication at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 12.Aspect 26: An apparatus for wireless communication at a UE, comprising at least one means for performing a method of any of aspects 1 through 12.Aspect 27: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 12.Aspect 28: An apparatus for wireless communication at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 13 through 24.Aspect 29: An apparatus for wireless communication at a network entity, comprising at least one means for performing a method of any of aspects 13 through 24.Aspect 30: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 13 through 24.

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).

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.

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.”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can 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” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can 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.