Wake-up signal traffic indication techniques for wireless communications

Abstract

Methods, systems, and devices are described for wireless communication in which a network entity may use a lower power sleep process to reduce power consumption and monitor a wakeup signal (WUS) from at least one user equipment (UE) during a configured WUS occasion. The WUS from one or more UEs may provide information of one or more attributes of data traffic present at a transmit buffer of the one or more UEs. A WUS configuration may be provided from a network entity that allows a particular WUS to be selected to indicate one or more attributes of the data traffic at the UE. The WUS may deliver information such as buffer status, power headroom, priority of traffic, latency target of traffic, or any combination thereof. The WUS may also give an indication of the requested duration of the activation mode at the network entity.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 898,281, entitled “WAKE-UP SIGNAL TRAFFIC INDICATION TECHNIQUES FOR WIRELESS COMMUNICATIONS,” filed by ABOTABL et al. on August 29, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including wake-up signal traffic indication techniques for wireless communications. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses supporting wake-up signal traffic indication technology for wireless communication. For example, the described technology stipulates that a network entity can use a lower power sleep process to reduce power consumption, and monitor the WUS from at least one user equipment (UE) during a configured wake-up signal (WUS) opportunity. The WUS from one or more UEs may provide information other than a binary indication of whether the UE has traffic in a transmit buffer. In some cases, a WUS configuration may be provided to the UE, which allows the selection of a specific WUS to indicate one or more attributes of the traffic at the UE. In some specific implementations, the WUS may provide an indication that a cell served by the network entity is to be awakened, and also convey information such as buffer status, power headroom, priority of traffic, latency target of traffic, or any combination thereof. In some cases, the UE may also give a recommendation on how long the network should remain awake. The network entity may use such information to set one or more parameters for an associated activation period.

[0006] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; selecting a first wake-up signal from the wake-up signal set based on a first attribute of first traffic to be transmitted from the UE; and transmitting the first wake-up signal during a wake-up signal opportunity based on the first attribute indication of the first wake-up signal to indicate to a cell that the cell is requested to be in an active state during a time period outside the wake-up signal opportunity.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; select a first wake-up signal from the wake-up signal set based on a first attribute of a first traffic to be transmitted from the UE; and transmit the first wake-up signal during a wake-up signal opportunity based on the first attribute indication of the first wake-up signal to indicate to a cell that the cell is requested to be in an activated state during a time period outside the wake-up signal opportunity.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; a component for selecting a first wake-up signal from the wake-up signal set based on a first attribute of a first traffic to be transmitted from the UE; and a component for transmitting the first wake-up signal during a wake-up signal opportunity based on the first attribute indication of the first wake-up signal to indicate to a cell that the cell is requested to be in an activated state during a time period outside the wake-up signal opportunity.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: receive configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; select a first wake-up signal from the wake-up signal set based on a first attribute of first traffic to be transmitted from the UE; and transmit the first wake-up signal during a wake-up signal opportunity based on the first attribute indication of the first wake-up signal to indicate to a cell that the cell is requested to be in an activated state during a time period outside the wake-up signal opportunity.

[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first wake-up signal may be a random access request sent via a random access channel (RACH), or may be a request sent via a control channel. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the selection of the first wake-up signal may include operations, features, components, or instructions for the following items: selecting the first wake-up signal from the wake-up signal set based on the transmit buffer state of the UE, the power headroom available at the UE, the priority of the first traffic, the latency target of the first traffic, or any combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the selection of the first wake-up signal may include operations, features, components, or instructions for the following items: selecting the first wake-up signal from the wake-up signal set based on the duration of time that the cell is requested to be in an activated state.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the wake-up signal set includes a set of random access preambles, and one or more of the random access preambles may be mapped to the one or more different attributes of the traffic to be sent from the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, 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 may be mapped to the one or more different attributes of the traffic to be sent from the UE.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration information may be received via radio resource control (RRC) signaling. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RRC signaling maps each of the two or more different random access preamble subsets to a different combination of two or more attributes of traffic to be sent from the UE.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the sending the first wake-up signal may include operations, features, components, or instructions for: sending an uplink control channel transmission, the uplink control channel transmission including a payload indicating the one or more different attributes of the traffic to be sent from the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the payload includes an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of the traffic to be sent from the UE.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: monitoring a response communication from the cell based on the first attribute indication of the first wake-up signal. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the monitoring may include operations, features, components, or instructions for: monitoring downlink control channel communications in a time window based on a delay associated with the first attribute indication of the first wake-up signal.

[0015] A method for wireless communication at a network entity is described. The method may include: sending configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity; and determining one or more parameters associated with transitioning to an active state for communication with the UE based on a first attribute of first traffic to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

[0016] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: send configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; receive a first wake-up signal from the UE during a wake-up signal monitoring opportunity; and determine one or more parameters associated with transitioning to an active state for communication with the UE based on a first attribute of a first traffic to be transmitted from the UE, the first attribute being indicated by the first wake-up signal.

[0017] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for sending configuration information for wake-up signal transmission to a UE, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE; a component for receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity; and a component for determining one or more parameters associated with transitioning to an active state for communication with the UE based on a first attribute of first traffic to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

[0018] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to: send configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be transmitted from the UE; receive a first wake-up signal from the UE during a wake-up signal monitoring opportunity; and determine one or more parameters associated with transitioning to an active state for communication with the UE based on a first attribute of first traffic to be transmitted from the UE, the first attribute indicated by the first wake-up signal.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first wake-up signal may be a random access request sent via a RACH, or may be a request sent via a control channel. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the one or more different attributes of the traffic to be sent from the UE include one or more of the following: a transmit buffer state 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 combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first wake-up signal also indicates a time duration of the activation state requested for communicating with the UE.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the wake-up signal set 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 the traffic to be sent from the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, 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 is mapped to the one or more different attributes of the traffic to be sent from the UE.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration information may be sent via RRC signaling. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RRC signaling maps each of the two or more different random access preamble subsets to a different combination of two or more attributes of traffic to be sent from the UE.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the receiving the first wake-up signal may include operations, features, components, or instructions for: receiving an uplink control channel transmission, the uplink control channel transmission including a payload indicating the one or more different attributes of the traffic to be sent from the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the payload includes an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of the traffic to be sent from the UE.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a response communication to the UE based on the first attribute indicated by the first wake-up signal. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the timing for sending the response communication may be based on a delay associated with the first attribute indicated by the first wake-up signal. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 An example of a wireless communication system supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated.

[0025] Figure 2 An example of a wireless communication system supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated.

[0026] Figure 3 An example of wake-up signal timing supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated.

[0027] Figure 4 An example of wake-up signal timing supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated.

[0028] Figure 5 An example of a process flow supporting a wake-up signal traffic indication technique for wireless communications in accordance with one or more aspects of the present disclosure is illustrated.

[0029] Figure 6 and Figure 7 A block diagram of a device supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown.

[0030] Figure 8 A block diagram of a communication manager supporting a wake-up signal traffic indication technique for wireless communications is shown in accordance with one or more aspects of the present disclosure.

[0031] Fig. 9 A diagram of a system including a device supporting a wake-up signal traffic indication technique for wireless communication is shown in accordance with one or more aspects of the present disclosure.

[0032] Fig.10 and Fig.11 A block diagram of a device supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown.

[0033] Fig.12A block diagram of a communication manager supporting a wake-up signal traffic indication technique for wireless communications is shown in accordance with one or more aspects of the present disclosure.

[0034] Fig.13 A diagram of a system including a device supporting a wake-up signal traffic indication technique for wireless communication is shown in accordance with one or more aspects of the present disclosure.

[0035] Figures 14 to 19 A flow chart illustrating a method of supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0036] A wireless communication system may include devices such as user equipment (UE) or a network entity (e.g., an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), or some other base station or network entity) that support wireless communication using one or more radio access technologies. Examples of radio access technologies include 4G systems such as LTE systems, 5G systems that 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 above).

[0037] In some wireless communication systems, such as fifth generation (5G) systems, network components may consume relatively large amounts of power in some cases. For example, a network entity in a system using beamforming communications, such as a radio unit (RU) or a radio head, may transmit multiple directional beams in multiple directions. Such systems may provide information (e.g., system information providing parameters for system access) for use by UEs to access a wireless communication system using beam scanning 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 scanning process. Such beam scanning techniques may consume additional power relative to techniques that do not use beam scanning (e.g., information provided in a single omnidirectional transmission may consume less power than multiple instances of information transmitted in multiple different directions). In addition, such beam scanning transmissions may be transmitted on multiple different cells, such as a primary cell (PCell) and one or more secondary cells (SCells).

[0038] In some cases, in order to reduce network power consumption, the network entity may transition to a sleep mode or an idle mode in which the transmission and reception circuits are powered off. For example, during off-peak hours, there may be no traffic or there may be a light traffic load in the cell, and the network entity may stop or reduce periodic transmission (e.g., SSB and SI transmission) and periodic monitoring (e.g., monitoring of random access requests or small data transmission (SDT) communications), and transition to a sleep mode in which a periodic activation period is used to monitor 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 sleep mode. If one or more WUS are detected, the network entity may maintain an activation mode or initiate an activation mode in addition to the period of monitoring the WUS. In some cases, such sleep mode operations may be implemented on one or more SCells, which typically have less control communications than a PCell and are therefore more likely to have periods of light or no traffic, although such techniques may also be used in a PCell under some conditions. In some cases, the UE may be configured with a periodicity that may send a WUS according to the period during which the cell will monitor for WUS (which may be referred to as a WUS opportunity). If there is data traffic in the UE transmit buffer, the UE may send a WUS during the WUS opportunity to trigger the cell to start or maintain an activation state, thereby allowing communication of the UE's data traffic.

[0039] According to various aspects discussed herein, a technique is provided in which a WUS may provide additional information in addition to a binary indication of whether the UE has traffic in the transmit buffer. In some cases, a WUS configuration may be provided to the UE, which allows the selection of a specific WUS to indicate one or more attributes of traffic present at the UE. The network entity receiving the WUS may use the indication to adjust the wake-up timing, the duration of the associated activation period, or any combination thereof. In some specific implementations, the WUS may provide an indication that the cell is to be awakened, and also convey information such as buffer status, power headroom, priority of traffic, delay target of traffic, or any combination thereof. In some cases, the UE may also give advice on how long the network should remain awake. In some cases, the WUS may be a random access preamble, and the UE may select a preamble from two or more preamble groups, each of which represents a set of information to be delivered to the network. These 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 communication specification, or any combination thereof). In some cases, the WUS may be sent via a control channel (e.g., a physical uplink control channel (PUCCH) transmission with a scheduling request (SR)), which may include a payload conveying information about data to be sent by the UE, or traffic attributes. In some cases, the UE may be configured to monitor different network responses based on the WUS sent. For example, if the UE indicates a high priority or low latency requirement in the WUS, the UE may expect scheduling information to be sent in an earlier response window (e.g., in a downlink control information (DCI) sent via a physical downlink control channel (PDCCH)) than if a lower priority or higher latency is indicated.

[0040] The various techniques 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 may achieve network power savings, and may determine one or more aspects of an activation period based on information from a received WUS. Such a network entity may adjust one or more parameters of an activation period based on information conveyed by the WUS, such as the duration of the activation period, the scheduling priority for one or more UEs sending the WUS, or the number of transmit or receive chains or antenna ports to be activated, to name just a few examples. In addition, the information conveyed by the WUS may allow for enhanced scheduling decisions at such a network entity, where communications may be scheduled and wireless resources allocated using the priorities of multiple different devices, thereby enhancing system efficiency and providing an enhanced user experience.

[0041] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated and described with reference to WUS timing, process flows, device diagrams, system diagrams, and flow charts related to wake-up signal traffic indication techniques for wireless communication.

[0042] Figure 1 An example of a wireless communication system 100 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0043] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0044] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0045] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0046] In some examples, the network entities 105 may communicate with the core network 130 or with each other or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162 or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0047] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0048] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0049] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0050] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0051] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. An IAB donor may facilitate a connection between a core network 130 and an AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. An IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0052] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay for transmissions to UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0053] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may directly signal the transmissions to the UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0054] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the wake-up signal traffic indication techniques for wireless communication as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0055] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may 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 communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0056] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1shown.

[0057] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates 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 for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0058] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0059] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0060] 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 wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communications using a particular carrier bandwidth or may be capable of being configured to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

[0061] The signal waveform transmitted via the carrier may include 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 using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number 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), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high rate of communication. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0062] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0063] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources 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).

[0064] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0065] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0066] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0067] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0068] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE 115 that has a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0069] 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 to different types of devices.

[0070] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0071] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication 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.

[0072] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0073] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0074] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0075] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0076] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0077] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in 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 integration, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0078] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct 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 signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0079] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) a beam direction for later transmission or reception by the network entity 105.

[0080] Some signals, such as data signals associated with a particular receiving device, may be sent by a sending device (e.g., sending network entity 105, sending UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0081] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating 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 subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0082] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving 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 receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A 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 the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0083] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers of user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map transport channels to physical channels.

[0084] In some cases, in order to reduce network power consumption, the network entity 105 may be converted to a sleep mode or an idle mode, in which the transmission and reception circuits are powered off. Such network entities 105 may use periodic activation periods to monitor WUS from a served device (such as UE 115). If the network entity 105 does not detect a WUS, it may be converted back to sleep mode. If one or more WUS are detected, the network entity 105 may also maintain an activation mode or initiate an activation mode in addition to monitoring the period of the WUS. In some cases, such sleep mode operations may be implemented on one or more cells served by the network entity 105. In some cases, the UE 115 may be configured with a periodicity that may send a WUS according to the period (which may be referred to as a WUS opportunity) during which the cell will monitor the WUS. If there is data traffic in the UE 115 transmission buffer, the UE 115 may send a WUS during the WUS opportunity to trigger the cell to start or maintain an activation state, thereby allowing communication of data traffic of the UE 115.

[0085] According to various aspects discussed herein, a technique is provided in which a WUS may provide information other than a binary indication of whether a UE 115 has traffic in a transmit buffer. In some cases, a WUS configuration may be provided to the UE 115, which allows the selection of a specific WUS to indicate one or more attributes of traffic present at the UE 115. The network entity 105 receiving the WUS may use the indication to adjust the wake-up timing, the duration of the associated activation period, or any combination thereof. In some specific implementations, the WUS may provide an indication that a cell served by the network entity 105 is to be awakened, and also convey information such as buffer status, power headroom, priority of traffic, latency target of traffic, or any combination thereof. In some cases, the UE 115 may also give a suggestion on how long the network should remain awake. The network entity 105 may use such information to set one or more parameters for the activation period.

[0086] Figure 2An example of a wireless communication system 200 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100 or be implemented by these aspects. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be as described in reference Figure 1 The network entity 105 (e.g., RU 170, DU 165, CU 160, base station 140, or some combination thereof) and the UE 115 are described as examples. The network entity 105-a and the UE 115-a may communicate with each other via an uplink channel 205-a and a downlink channel 205-b, which may be as described in reference to Figure 1 Examples or components of the communication link 125 described herein. The UE 115-a and the network entity 105-a may support techniques for WUS transmission indicating one or more attributes of traffic present at the UE 115-a. By providing information related to traffic present at the UE 115-a, the UE 115-a and the network entity 105-a may improve resource efficiency and reduce power consumption of the wireless communication system 200.

[0087] exist Figure 2 In an example of , the network entity 105-a may send configuration information 210 to the UE 115-a. In some cases, the configuration information 210 may include information related to the cell sleep and activation mode periods and the WUS opportunity. The network entity 105-a may initiate a sleep process at a cell (e.g., an SCell or PCell configured at the UE 115-a) based on the configuration information 210. In the event that the UE 115-a has traffic in the transmit buffer, the UE 115-a may send a WUS 215 during the WUS opportunity based on the configuration information 210. The network entity 105-a may detect the WUS 215 and send a response message 220 to the UE 115-a.

[0088] According to various aspects discussed herein, WUS215 may provide an indication of one or more attributes of data traffic in a transmit buffer of UE 115-a. In some cases, configuration information 210 may provide a WUS215 configuration that allows the WUS to indicate one or more attributes of traffic present at UE 115-a. For example, WUS set 215 may include two or more subsets of random access channel (RACH) preambles, wherein a RACH preamble selected from one of these subsets may indicate one or more attributes associated with data traffic. Additionally or alternatively, WUS215 may be sent via PUCCH (e.g., SR is sent via PUCCH), and the WUS215 configuration may specify that the payload included in WUS215 may indicate one or more attributes of data traffic. Upon receiving WUS215, network entity 105-a may use the indication to adjust wake-up timing, determine the duration of an associated activation period, activate one or more antenna ports and associated components, or any combination thereof. In some specific implementations, WUS215 may convey information such as buffer status, power headroom, priority of traffic, latency target of traffic, or any combination thereof. In some cases, UE 115-a may also give suggestions on how long the network should remain awake. In some cases, configuration information 210 may be signaled to UE 115-a via RRC signaling, via system information associated with the cell (e.g., via a master information block (MIB), one or more system information blocks (SIBs), or any combination thereof), may be pre-configured in a communication specification, or any combination thereof. In some cases, UE 115-a may be configured to monitor response messages 220 (e.g., DCI indicating scheduling information and resource allocation, RACH responses, etc.) based on the sent WUS215. For example, if UE 115-a indicates a high priority or low latency requirement in WUS215, UE 115-a may expect to send scheduling information (e.g., in a DCI sent via PDCCH) in an earlier response window than if a lower priority or higher latency was indicated.

[0089] Figure 3 An example of WUS timing 300 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated. The WUS timing 300 may be implemented by aspects of the wireless communication system 100 or 200. For example, the UE 115-b and the network entity 105-b (which may be Figure 1 and Figure 21 and 105) may implement WUS timing 300. As discussed herein, the network entity 105-b may transition between a sleep mode 305 and an active mode 310, wherein the sleep mode 305 has lower power consumption than the active mode. A WUS configuration may be provided that may trigger the network entity 105-b to remain in the active mode 310 for communication, thereby allowing for reduced network power consumption and an efficient wake-up process, which may enhance overall network efficiency and user experience.

[0090] exist Figure 3 In the example of , the network entity 105-b enters a sleep mode 305 that provides network power savings, where a periodic activation mode 310 may be used to monitor wake-up signals and maintain network operation. In some cases, the sleep process may be enabled at the network entity 105-b based on the traffic load being served. For example, during certain hours (e.g., evening hours in an office area), the cell may have relatively light or no traffic, and the sleep process may help save network power and operating costs. In some cases, different sleep modes may be configured, some of which will shut down the RF chain at the network entity 105-b while others may not, and thus different sleep modes have different power consumptions and require different transition times. However, one or more cells that may implement the sleep mode served by the network entity 105-b may still have a connection with the UE 115-b, and thus the cell should know whether the UE 115-b needs to enter a connected state or perform some SDT so that the activation mode 310 can be triggered. In Figure 3 In the example of FIG. 3 , the network entity 105-b may be configured to monitor periodic occasions for WUS 335, which in this example include a first WUS opportunity 315 and a second WUS opportunity 325. In this example, during an activation period 320 associated with the first WUS opportunity 315, the network entity 105-b may not detect a WUS and may transition back to the sleep mode 305. During an activation period 330 associated with the second WUS opportunity 325, the network entity 105-b may detect a WUS 335 from the UE 115-b and may maintain the activation mode 310 beyond the duration of the second WUS opportunity 325 in order to provide communication with the UE 115-b.

[0091] As discussed herein, WUS 335 may take different forms, such as a RACH preamble or a PUCCH transmission. Figure 3In the example of , the WUS 335 can be a RACH request 340 including a RACH preamble. In some cases, the RACH preamble can be selected from a set of RACH preambles 345, wherein a first subset 350 of RACH preambles and a second subset 355 of RACH preambles can be associated with different sets of attributes of data traffic of the UE 115-b. In some cases, the traffic attributes can include one or more of the following: a buffer status of the UE 115-b, an available power headroom at the UE 115-b, a signal priority associated with the data traffic, a latency target associated with the data traffic, or any combination thereof. In some cases, the UE 115-b can also provide a recommendation on how long the network should stay in the activation mode 310 (e.g., a time duration T1). In some implementations, the first subset 350 of RACH preambles may be associated with a first set of attributes of data traffic, and the second subset 355 of RACH preambles may be associated with a second set of attributes of data traffic, and the WUS configuration information may provide different attributes of data traffic associated with each subset 350 and 355 of RACH preambles. In some cases, the WUS configuration information may be sent via RRC signaling as part of or after the connection establishment between the UE 115-b and the network entity 105-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 combination thereof.

[0092] In some cases, the WUS configuration may provide a table (such as in Table 1 below) where different subsets of RACH preambles may be associated with different sets of traffic attributes:

[0093]

[0094] Table 1

[0095] In this example, three subsets of RACH preambles are configured according to the available RACH preamble set, where the first subset of RACH preambles (e.g., preamble group A) is associated with a short transmit buffer (e.g., where the data in the UE 115-b transmit buffer is less than a threshold provided in the WUS configuration), a first power headroom (PHR) state (e.g., where the PHR at UE 115-b is within a PHR range or is above / below a PHR threshold provided in the WUS configuration), a low traffic priority (e.g., the priority of the data traffic is below the priority threshold or in an associated priority class), a low latency target (e.g., the latency target for the data traffic is less than the latency threshold), and a first requested time duration (T1=A) for an active mode (e.g., a T1 value within the T1 range or above / below the T1 threshold). 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 state, 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 state, a higher traffic priority, a higher latency target, and a third requested time duration (T1=C). It should be appreciated that Table 1 is provided as one example of different subsets of RACH preambles and associated data traffic attributes, and that numerous other examples of such tables may be readily formulated and are within the scope of the present disclosure, such as examples that may have more or fewer preamble subsets, more or fewer corresponding traffic attributes, etc. In other examples, additionally or alternatively, a WUS may be sent in a PUCCH transmission, such as Figure 4 exemplified in the example.

[0096] Figure 4 An example of a wake-up signal timing 400 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated. The WUS timing 400 may be implemented by aspects of the wireless communication system 100 or 200. For example, the UE 115-c and the network entity 105-c (which may be Figure 1 and Figure 2 1 and 105) may implement WUS timing 400. As discussed herein, the network entity 105-c may transition between a sleep mode 405 and an active mode 410, wherein the sleep mode 405 has lower power consumption than the active mode 410. A WUS configuration may be provided that may trigger the network entity 105-c to remain in the active mode 410 for communication, thereby allowing for reduced network power consumption and an efficient wake-up process, which may enhance overall network efficiency and user experience.

[0097] exist Figure 4In the example of FIG. 1 , the network entity 105 - c enters a sleep mode 405 that provides network power conservation, wherein a periodic activation mode 410 may be used to monitor a wake-up signal and maintain network operation, as described in reference to FIG. Figure 3 In this example, the network entity 105-c may again be configured to monitor periodic opportunities for WUS 435, the periodic opportunities including a first WUS opportunity 415 and a second WUS opportunity 425. In this example, during an activation period 420 associated with the first WUS opportunity 415, the network entity 105-c may not detect a WUS and may transition back to the sleep mode 405. During an activation period 430 associated with the second WUS opportunity 425, the network entity 105-c may detect a WUS 435 from the UE 115-c and may maintain the activation mode 410 for a duration exceeding the second WUS opportunity 425 in order to provide communication with the UE 115-c.

[0098] In this example, the WUS 435 may be provided via a PUCCH and may include a PUCCH indication 440 and a payload 445 indicating one or more traffic attributes of the data traffic at the UE 115-c. The payload 445 of the PUCCH may convey information such as the Figure 3 Similar information discussed, such as the size of the data buffer, the PHR status, the traffic priority, the latency target, the requested time duration (T1), or any combination thereof. In some cases, a separate field for each traffic attribute may be provided in the payload 445. In other cases, the network entity 105-c may configure a table with index values, where each index value is associated with one or more traffic attributes, similar to that discussed with reference to Table 1, and the payload 445 may include the index values ​​associated with the one or more attributes.

[0099] In some cases, the UE 115 may monitor one or more transmissions based on a particular WUS indication sent as discussed herein. For example, if the UE 115 indicates that a low latency target is associated with data in a transmit buffer, the UE 115 may monitor a downlink control channel (e.g., PDCCH) transmission for a response in an earlier response window than if a higher latency target is indicated.

[0100] Figure 5 An example of a process flow 500 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is illustrated. The process flow 500 may include a network entity 105-d and a UE 115-d, which may be as described in reference Figures 1 to 4An example of a network entity 105 and a UE 115 described. The process flow 500 may be implemented by a network entity 105-d and a UE 115-d, wherein a WUS from the UE 115-d provides an indication of one or more attributes of data traffic that is present and to be sent by the UE 115-d. Such techniques may provide power savings associated with a sleep mode at the network entity 105-d, while also enabling faster indication of traffic attributes to the network entity 105-d, which may adjust its behavior based on the WUS indication, which may therefore enhance overall network efficiency and user experience. In the following description of the process flow 500, operations between the network entity 105-d and the UE 115-d may be performed in a different order than the example shown. Some operations may be omitted from the process flow 500, and other operations may be added to the process flow 500.

[0101] At 505, the network entity 105-d may send configuration information associated with the WUS transmission, and the UE 115-d may receive the configuration information associated with the WUS transmission. As discussed herein, such configuration information may provide characteristics of the WUS opportunity, such as, for example, the duration of the WUS opportunity (e.g., a time duration or a number of symbols / slots), the periodicity of the WUS opportunity (e.g., a time period, a number of symbols / slots, and a symbol / slot offset), a frequency band or bandwidth part (BWP), or any combination 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 via one or more system information transmissions (e.g., SIB / MIB transmissions), in one or more control channel transmissions (e.g., in a DCI), and / or in one or more MAC-CE transmissions.

[0102] At 510, the network entity 105-d may transition to a sleep mode. In some cases, the sleep mode may be a relatively low power mode at the network entity 105-d in which some or all transmit / receive components are powered down. At 515, the network entity 105-d may transition to an active mode to monitor for WUS. In some cases, the transition to the active mode may be performed according to a WUS opportunity periodicity indicated in the configuration information.

[0103] At 520, the UE 115-d may identify that data traffic is present in the transmit buffer and may determine one or more attributes of the data traffic. For example, the UE 115-d may determine a priority and latency target associated with the data traffic, the amount of data traffic present, the PHR of the UE 115-d, or any combination thereof. In some cases, the UE 115-d may also identify a time duration (T1) that may be used for transmission of the data traffic. At 525, the UE 115-d may select a WUS based on one or more attributes of the data traffic. For example, the UE 115-d may select a RACH preamble or a PUCCH payload, as described in reference to FIG. Figure 3 and Figure 4 discussed.

[0104] At 530, the UE 115-d may send a WUS to the network entity 105-d. As discussed herein, the WUS may be sent during a WUS opportunity, and at 535, the network entity 105-d may detect the WUS. At 540, the network entity 105-d may determine one or more activation mode parameters based on one or more attributes indicated by the WUS. In some cases, the network entity 105-d may determine one or more attributes based on a preamble for the WUS, or a payload content of the WUS. For example, the network entity 105-d may determine a time duration for the activation mode (e.g., based on a T1 indication, a buffer size indication, or both), resources to be allocated for associated data transmission (e.g., based on a buffer size indication, a priority of the traffic, a latency target of the traffic, or any combination thereof), one or more transmission parameters for associated uplink transmission (e.g., based on a channel condition and an MCS of an indicated PHR), or any combination thereof. At 545, the network entity 105-d may send a response message, which may be received at the UE 115-d. In some cases, the 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 a response message to be sent earlier in the response window, and a higher latency indication in the WUS may prompt a response message later in the response window). In some cases, the response message may include a random access response, or a DCI with resource allocations for an associated uplink transmission.

[0105] Figure 6 A block diagram 600 of a device 605 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0106] The receiver 610 may provide 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). The information may be delivered to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0107] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to wake-up signal traffic indication techniques for wireless communication), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0108] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0109] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). 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 that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0110] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0111] In some examples, communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0112] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support a component for receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The communication manager 620 may be configured to or otherwise support a component for selecting a first wake-up signal from the wake-up signal set based on a first attribute of a first traffic to be sent from the UE. The communication manager 620 may be configured to or otherwise support a component for sending a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be in an activated state during a time period outside of the wake-up signal opportunity.

[0113] By including or configuring a communication manager 620 according to examples as described herein, the device 605 (e.g., a processor that controls or otherwise couples with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for WUS transmission that indicate traffic attributes of the UE that is transmitting the WUS. Such techniques can provide enhanced sleep and active mode transitions at network entities, which can reduce network power consumption and allow for more efficient use of communication resources. In addition, communication latency can be reduced and reliability enhanced by indicating traffic priority or latency targets that can be used at the network entity to select active mode duration and parameters.

[0114] Figure 7A block diagram 700 of a device 705 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0115] The receiver 710 may provide 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). The information may be delivered to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0116] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with wake-up signal traffic indication techniques for wireless communications), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0117] The device 705 or its various components may be examples of components for performing various aspects of the wake-up signal traffic indication technology for wireless communication as described herein. For example, the communication manager 720 may include a configuration manager 725, a WUS selection manager 730, a WUS transmission manager 735, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0118] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The configuration manager 725 may be configured to or otherwise support a component for receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The WUS selection manager 730 may be configured to or otherwise support a component for selecting a first wake-up signal from the wake-up signal set based on a first attribute of a first traffic to be sent from the UE. The WUS transmission manager 735 may be configured to or otherwise support a component for transmitting a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be in an activated state during a time period outside the wake-up signal opportunity.

[0119] Figure 8 A block diagram 800 of a communication manager 820 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of the wake-up signal traffic indication technique for wireless communication as described herein. For example, the communication manager 820 may include a configuration manager 825, a WUS selection manager 830, a WUS transmission manager 835, a RACH preamble manager 840, a WUS payload manager 845, a WUS response manager 850, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0120] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The configuration manager 825 may be configured to or otherwise support a component for receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The WUS selection manager 830 may be configured to or otherwise support a component for selecting a first wake-up signal from the wake-up signal set based on a first attribute of a first traffic to be sent from the UE. The WUS transmission manager 835 may be configured to or otherwise support a component for transmitting a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be in an activated state during a time period outside the wake-up signal opportunity. In some examples, the first wake-up signal is a random access request sent via a RACH, or a request sent via a control channel.

[0121] In some examples, to support selecting the first wake-up signal, the WUS selection manager 830 may be configured or otherwise support a component for selecting the first wake-up signal from the wake-up signal set based on a transmit buffer state 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 combination thereof. In some examples, to support selecting the first wake-up signal, the WUS selection manager 830 may be configured or otherwise support a component for selecting the first wake-up signal from the wake-up signal set based on a time duration for which the cell is requested to be in an activated state.

[0122] In some examples, the wake-up signal set includes a set of random access preambles, and one or more of the random access preambles are mapped to one or more different attributes of traffic to be sent from the UE. In some examples, the set of random access preambles includes two or more different subsets of random access preambles, and each of the two or more different subsets of random access preambles is mapped to one or more different attributes of traffic to be sent from the UE.

[0123] In some examples, the configuration information is received via RRC signaling.In some examples, the RRC signaling maps each of two or more different random access preamble subsets to a different combination of two or more attributes of traffic to be sent from the UE.

[0124] In some examples, to support sending the first wake-up signal, the WUS payload manager 845 may be configured to or otherwise support components for sending an uplink control channel transmission that includes a payload indicating one or more different attributes of traffic to be sent from the UE. In some examples, the payload includes an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of traffic to be sent from the UE.

[0125] In some examples, the WUS response manager 850 may be configured or otherwise support components for monitoring a response communication from the cell based on a first attribute indication of the first wake-up signal. In some examples, to support monitoring, the WUS response manager 850 may be configured or otherwise support components for monitoring downlink control channel communications in a time window based on a latency associated with the first attribute indication of the first wake-up signal.

[0126] Fig. 9A diagram of a system 900 including a device 905 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

[0127] I / O controller 910 may manage input and output signals for device 905. I / O controller 910 may also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0128] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired or wireless link, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 925 for transmission, and for demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0129] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0130] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., functions or tasks that support a wake-up signal traffic indication technique for wireless communication). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0131] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The communication manager 920 may be configured to or otherwise support a component for selecting a first wake-up signal from the wake-up signal set based on a first attribute of a first traffic to be sent from the UE. The communication manager 920 may be configured to or otherwise support a component for sending a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be in an activated state during a time period outside of the wake-up signal opportunity.

[0132] By including or configuring a communication manager 920 according to examples as described herein, the device 905 can support techniques for WUS transmission that indicate traffic attributes of the UE that is transmitting the WUS. Such techniques can provide enhanced sleep and active mode transitions at network entities, which can reduce network power consumption and allow more efficient use of communication resources. In addition, communication latency can be reduced and reliability enhanced by indicating traffic priorities or latency targets that can be used at network entities to select active mode durations and parameters.

[0133] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of the wake-up signal traffic indication technique for wireless communication as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0134] Fig.10 A block diagram 1000 of a device 1005 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0136] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0137] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the wake-up signal traffic indication techniques for wireless communications as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0138] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). 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 that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0139] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0140] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0141] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support a component for sending configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The communication manager 1020 may be configured to or otherwise support a component for receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity. The communication manager 1020 may be configured to or otherwise support a component for determining one or more parameters associated with transitioning to an active state for communicating with the UE based on a first attribute of a first traffic to be sent from the UE, the first attribute being indicated by the first wake-up signal.

[0142] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor that controls or otherwise couples with the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support techniques for WUS transmission that indicate traffic attributes of the UE that is transmitting the WUS. Such techniques can provide enhanced sleep and active mode transitions at network entities, which can reduce network power consumption and allow more efficient use of communication resources. In addition, communication latency can be reduced and reliability enhanced by indicating traffic priority or latency targets that can be used at the network entity to select active mode duration and parameters.

[0143] Fig.11 A block diagram 1100 of a device 1105 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0145] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0146] Device 1105 or its various components may be examples of components for performing various aspects of the wake-up signal traffic indication technology for wireless communication as described herein. For example, communication manager 1120 may include configuration manager 1125, WUS monitoring manager 1130, activation state manager 1135, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or integrate with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0147] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The configuration manager 1125 may be configured to or otherwise support a component for sending configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The WUS monitoring manager 1130 may be configured to or otherwise support a component for receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity. The activation state manager 1135 may be configured to or otherwise support a component for determining one or more parameters associated with transitioning to an activation state for communicating with the UE based on a first attribute of a first traffic to be sent from the UE, the first attribute being indicated by a first wake-up signal.

[0148] Fig.12 A block diagram 1200 of a communication manager 1220 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of the wake-up signal traffic indication technique for wireless communication as described herein. For example, the communication manager 1220 may include a configuration manager 1225, a WUS monitoring manager 1230, an activation state manager 1235, a RACH preamble manager 1240, a WUS attribute manager 1245, a WUS payload manager 1250, a WUS response manager 1255, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication 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 the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0149] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The configuration manager 1225 may be configured to or otherwise support a component for sending configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The WUS monitoring manager 1230 may be configured to or otherwise support a component for receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity. The activation state manager 1235 may be configured to or otherwise support a component for determining one or more parameters associated with transitioning to an activation state for communicating with the UE based on a first attribute of a first traffic to be sent from the UE, the first attribute being indicated by the first wake-up signal.

[0150] In some examples, the first wake-up signal is a random access request sent via RACH or a request sent via a control channel. In some examples, the one or more different attributes of the traffic to be sent from the UE include one or more of the following: a transmit buffer state 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 combination thereof. In some examples, the first wake-up signal also indicates a time duration of an activation state requested for communication with the UE.

[0151] In some examples, the wake-up signal set includes a set of random access preambles, and one or more of the random access preambles are mapped to one or more different attributes of traffic to be sent from the UE. In some examples, the set of random access preambles includes two or more different subsets of random access preambles, and each of the two or more different subsets of random access preambles is mapped to one or more different attributes of traffic to be sent from the UE.

[0152] In some examples, the configuration information is sent via RRC signaling.In some examples, the RRC signaling maps each of two or more different random access preamble subsets to a different combination of two or more attributes of traffic to be sent from the UE.

[0153] In some examples, to support receiving the first wake-up signal, the WUS payload manager 1250 may be configured or otherwise support components for receiving an uplink control channel transmission that includes a payload indicating one or more different attributes of traffic to be sent from the UE. In some examples, the payload includes an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of traffic to be sent from the UE.

[0154] In some examples, the WUS response manager 1255 may be configured to or otherwise support components for sending a response communication to the UE based on a first attribute indicated by the first wake-up signal. In some examples, the timing for sending the response communication is based on a latency associated with the first attribute indicated by the first wake-up signal.

[0155] Fig.13 A diagram of a system 1300 including a device 1305 supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and obtain communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0156] As described herein, the transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform the following operations: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination of these operations. In some implementations, the transceiver 1310 or the transceiver 1310 and one or more antennas 1315 or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip integration installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0157] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0158] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., functions or tasks supporting a wake-up signal traffic indication technique for wireless communication). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 1330) to perform functions of the device 1305. The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as in the memory 1325). In some specific implementations, the processor 1335 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1305). For example, the processing system of the device 1305 may refer to a system including various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of the device 1305. The processing system of the device 1305 may interface with other components of the device 1305, and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of the device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. 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 the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1305 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1305 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0159] In some examples, bus 1340 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0160] In some examples, communication manager 1320 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 may manage delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1320 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1320 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0161] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support a component for sending configuration information for wake-up signal transmission to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE. The communication manager 1320 may be configured to or otherwise support a component for receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity. The communication manager 1320 may be configured to or otherwise support a component for determining one or more parameters associated with transitioning to an active state for communicating with the UE based on a first attribute of a first traffic to be sent from the UE, the first attribute being indicated by the first wake-up signal.

[0162] By including or configuring a communication manager 1320 according to examples as described herein, the device 1305 can support techniques for WUS transmission that indicate traffic attributes of the UE that is transmitting the WUS. Such techniques can provide enhanced sleep and active mode transitions at network entities, which can reduce network power consumption and allow more efficient use of communication resources. In addition, communication latency can be reduced and reliability enhanced by indicating traffic priorities or latency targets that can be used at network entities to select active mode durations and parameters.

[0163] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of the wake-up signal traffic indication technique for wireless communication as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0164] Fig.14 A flowchart illustrating a method 1400 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0165] At 1405, the method may include receiving configuration information for wake-up signal transmission, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described configuration manager 825 is executed.

[0166] At 1410, the method may include selecting a first wake-up signal from a set of wake-up signals based on a first attribute of a first traffic to be sent from the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference Figure 8 The described WUS selection manager 830 is executed.

[0167] At 1415, the method may include sending a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be active during a time period outside of the wake-up signal opportunity. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The described WUS is sent to the manager 835 to execute.

[0168] Fig.15 A flowchart illustrating a method 1500 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0169] At 1505, the method may include receiving configuration information for wake-up signal transmission, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The described configuration manager 825 is executed.

[0170] At 1510, the method may include selecting a first wake-up signal from a set of wake-up signals based on a first attribute of a first traffic to be sent from the UE. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference Figure 8 The described WUS selection manager 830 is executed.

[0171] In some implementations, at 1515, the method may optionally include selecting a first wake-up signal from a 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 combination thereof. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The described WUS selection manager 830 is executed.

[0172] In some implementations, at 1520, the method may optionally include selecting a first wake-up signal from a wake-up signal set based on a time duration for which the cell is requested to be in an activated state. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The described WUS selection manager 830 is executed.

[0173] At 1525, the method may include sending a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be in an active state during a time period outside of the wake-up signal opportunity. The operations of 1525 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 8 The described WUS is sent to the manager 835 to execute.

[0174] Fig.16 A flowchart illustrating a method 1600 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0175] At 1605, the method may include receiving configuration information for wake-up signal transmission, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference Figure 8 The described configuration manager 825 is executed.

[0176] At 1610, the method may include selecting a first wake-up signal from a set of wake-up signals based on a first attribute of a first traffic to be sent from the UE. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference Figure 8 The described WUS selection manager 830 is executed.

[0177] At 1615, the method may include sending an uplink control channel transmission providing a first wake-up signal during a wake-up signal opportunity, wherein the uplink control channel transmission includes a payload indicating one or more different attributes of traffic to be sent from the UE. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The described WUS payload manager 845 is executed.

[0178] Fig.17 A flowchart illustrating a method 1700 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0179] At 1705, the method may include receiving configuration information for wake-up signal transmission, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference Figure 8 The described configuration manager 825 is executed.

[0180] At 1710, the method may include selecting a first wake-up signal from a set of wake-up signals based on a first attribute of a first traffic to be sent from the UE. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference Figure 8 The described WUS selection manager 830 is executed.

[0181] At 1715, the method may include sending a first wake-up signal during a wake-up signal opportunity based on a first attribute indication of the first wake-up signal to indicate to the cell that the cell is requested to be active during a time period outside of the wake-up signal opportunity. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 8 The described WUS is sent to the manager 835 to execute.

[0182] At 1720, the method may include monitoring for responsive communications from a cell based on the first attribute indication of the first wake-up signal. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Figure 8 The described WUS response manager 850 is executed.

[0183] In some implementations, at 1725, the method may optionally include monitoring downlink control channel communications in a time window based on a delay associated with a first attribute indication of the first wake-up signal. The operations of 1725 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Figure 8 The described WUS response manager 850 is executed.

[0184] Fig.18 A flowchart illustrating a method 1800 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0185] At 1805, the method may include sending configuration information for wake-up signal transmission to the UE, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The described configuration manager 1225 is executed.

[0186] At 1810, the method may include receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference Fig.12 The described WUS monitoring manager 1230 is executed.

[0187] At 1815, the method may include determining one or more parameters associated with transitioning to an active state for communicating with the UE based on a first attribute of a first traffic to be sent from the UE, the first attribute being indicated by a first wake-up signal. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference Fig.12 The described activation state manager 1235 is executed.

[0188] Fig.19 A flowchart illustrating a method 1900 for supporting a wake-up signal traffic indication technique for wireless communication according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0189] At 1905, the method may include sending configuration information for wake-up signal transmission to the UE, the configuration information indicating a set of wake-up signals, each wake-up signal in the set of wake-up signals indicating one or more different attributes of traffic to be transmitted from the UE. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.12 The described configuration manager 1225 is executed.

[0190] At 1910, the method may include receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference Fig.12 The described WUS monitoring manager 1230 is executed.

[0191] At 1915, the method may include determining one or more parameters associated with transitioning to an active state for communicating with the UE based on a first attribute of a first traffic to be sent from the UE, the first attribute being indicated by a first wake-up signal. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.12 The described activation state manager 1235 is executed.

[0192] At 1920, the method may include sending a response communication to the UE based on the first attribute indicated by the first wake-up signal. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference Fig.12 The described WUS response manager 1255 is executed.

[0193] The following provides an overview of various aspects of the disclosure:

[0194] Aspect 1: A method for performing wireless communication at a UE, the method comprising: receiving configuration information for sending a wake-up signal, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE; selecting a first wake-up signal from the wake-up signal set based at least in part on a first attribute of a first traffic to be sent from the UE; and sending the first wake-up signal during a wake-up signal opportunity based at least in part on the first attribute indication of the first wake-up signal to indicate to a cell that the cell is requested to be activated for a time period outside of the wake-up signal opportunity.

[0195] Aspect 2: The method according to aspect 1, wherein the first wake-up signal is a random access request sent via a RACH, or a request sent via a control channel.

[0196] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the selecting the first wake-up signal includes: selecting the first wake-up signal from the wake-up signal set based at least in part on the transmit buffer status of the UE, the power headroom available at the UE, the priority of the first traffic, the latency target of the first traffic, or any combination thereof.

[0197] Aspect 4: The method according to any one of aspects 1 to 3, wherein the selecting the first wake-up signal further comprises: selecting the first wake-up signal from the wake-up signal set based at least in part on a time duration during which the cell is requested to be in the activated state.

[0198] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the wake-up signal set includes a random access preamble set, and one or more of the random access preambles are mapped to the one or more different attributes of the traffic to be sent from the UE.

[0199] Aspect 6: A method according to Aspect 5, wherein the random access preamble set includes two or more different random access preamble subsets, and wherein each of the two or more different random access preamble subsets is mapped to the one or more different attributes of the traffic to be sent from the UE.

[0200] Aspect 7: The method according to aspect 6, wherein the configuration information is received via RRC signaling.

[0201] Aspect 8: The method according to aspect 7, wherein the RRC signaling maps each of the two or more different random access preamble code subsets to a different combination of two or more attributes of the traffic to be sent from the UE.

[0202] Aspect 9: A method according to any one of Aspects 1 to 8, wherein sending the first wake-up signal includes: sending an uplink control channel transmission, the uplink control channel transmission including a payload indicating the one or more different attributes of the traffic to be sent from the UE.

[0203] Aspect 10: The method according to Aspect 9, wherein the payload includes an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of the traffic to be sent from the UE.

[0204] Aspect 11: The method according to any one of aspects 1 to 10, the method further comprising: monitoring a response communication from the cell based at least in part on the first attribute indication of the first wake-up signal.

[0205] Aspect 12: The method according to aspect 11, wherein the monitoring includes: monitoring downlink control channel communications in a time window based at least in part on a latency associated with the first attribute indication of the first wake-up signal.

[0206] Aspect 13: A method for wireless communication at a network entity, the method comprising: sending configuration information for wake-up signal sending to a UE, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE; receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity; and determining one or more parameters associated with transitioning to an activated state for communicating with the UE based at least in part on a first attribute of the first traffic to be sent from the UE, the first attribute being indicated by the first wake-up signal.

[0207] Aspect 14: The method according to aspect 13, wherein the first wake-up signal is a random access request sent via a RACH, or a request sent via a control channel.

[0208] Aspect 15: A method according to any one of Aspects 13 to 14, wherein the one or more different attributes of the traffic to be sent from the UE include one or more of the following: a transmit buffer status of the UE, power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combination thereof.

[0209] Aspect 16: The method according to any one of aspects 13 to 15, wherein the first wake-up signal further indicates a time duration of the activation state requested for communicating with the UE.

[0210] Aspect 17: A method according to any one of Aspects 13 to 16, wherein the wake-up signal set includes a random access preamble set, and one or more of the random access preambles are mapped to the one or more different attributes of the traffic to be sent from the UE.

[0211] Aspect 18: A method according to Aspect 17, wherein the random access preamble set includes two or more different random access preamble subsets, and wherein each of the two or more different random access preamble subsets is mapped to the one or more different attributes of the traffic to be sent from the UE.

[0212] Aspect 19: The method according to Aspect 18, wherein the configuration information is sent via RRC signaling.

[0213] Aspect 20: The method according to aspect 19, wherein the RRC signaling maps each of the two or more different random access preamble code subsets to a different combination of two or more attributes of the traffic to be sent from the UE.

[0214] Aspect 21: A method according to any one of Aspects 13 to 20, wherein receiving the first wake-up signal includes: receiving an uplink control channel transmission, the uplink control channel transmission including a payload indicating the one or more different attributes of the traffic to be sent from the UE.

[0215] Aspect 22: The method according to Aspect 21, wherein the payload includes an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of the traffic to be sent from the UE.

[0216] Aspect 23: The method according to any one of aspects 13 to 22, the method further comprising: sending a response communication to the UE based at least in part on the first attribute indicated by the first wake-up signal.

[0217] Aspect 24: The method of aspect 23, wherein the 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.

[0218] Aspect 25: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 12.

[0219] Aspect 26: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 12.

[0220] Aspect 27: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 12.

[0221] Aspect 28: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 13 to 24.

[0222] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 13 to 24.

[0223] 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 the method according to any one of aspects 13 to 24.

[0224] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0225] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication 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, and other systems and radio technologies not explicitly mentioned herein.

[0226] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0227] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, 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 an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0228] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0229] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, while optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0230] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0231] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0232] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0233] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0234] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic 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 to be sent from the UE; as well as Based at least in part on the first attribute indication of the first wake-up signal, the first wake-up signal is sent during a wake-up signal occasion to indicate to a cell that the cell is requested to be active during a time period outside of the wake-up signal occasion. 2 . The method according to claim 1 , wherein the first wake-up signal is a random access request sent via a random access channel (RACH) or a request sent via a control channel.

3. The method according to claim 1, wherein the selecting the first wake-up signal comprises: The first wake-up signal is selected 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 combination thereof.

4. The method according to claim 1, wherein the selecting the first wake-up signal further comprises: The first wake-up signal is selected from the set of wake-up signals based at least in part on a duration of time that the cell is requested to be in the active state.

5. The method of claim 1, wherein the wake-up signal set comprises 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 the traffic to be sent from the UE.

6. The method of claim 5, wherein the random access preamble set comprises two or more different random access preamble subsets, and wherein each of the two or more different random access preamble subsets is mapped to the one or more different attributes of the traffic to be sent from the UE. The method of claim 6 , wherein the configuration information is received via radio resource control (RRC) signaling.

8. The method of claim 7, wherein the RRC signaling maps each of the two or more different random access preamble subsets to a different combination of two or more attributes of traffic to be sent from the UE.

9. The method according to claim 1, wherein the sending the first wake-up signal comprises: An uplink control channel transmission is transmitted, the uplink control channel transmission including a payload indicative of the one or more different attributes of traffic to be transmitted from the UE.

10. The method of claim 9, wherein the payload comprises an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of traffic to be sent from the UE.

11. The method according to claim 1, further comprising: Monitoring for responsive communications from the cell is performed based at least in part on the first attribute indication of the first wake-up signal.

12. The method of claim 11, wherein the monitoring comprises: Downlink control channel communications are monitored in a time window based at least in part on a latency associated with the first attribute indication of the first wake-up signal.

13. A method for wireless communication at a network entity, the method comprising: Sending configuration information for wake-up signal transmission to a user equipment (UE), the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE; receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity; as well as One or more parameters associated with transitioning to an active state for communicating with the UE are determined based at least in part on a first attribute of first traffic to be sent from the UE, the first attribute being indicated by the first wake-up signal.

14. The method of claim 13, wherein the first wake-up signal is a random access request sent via a random access channel (RACH) or a request sent via a control channel.

15. The method of claim 13, wherein the one or more different attributes of the traffic to be sent from the UE include one or more of: a transmit buffer status of the UE, power headroom available at the UE, a priority of the first traffic, a latency target of the first traffic, or any combination thereof.

16. The method of claim 13, wherein the first wake-up signal further indicates a time duration of the activation state requested for communicating with the UE.

17. The method of claim 13, wherein the set of wake-up signals comprises 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 to be sent from the UE.

18. The method of claim 17, wherein the random access preamble set comprises two or more different random access preamble subsets, and wherein each of the two or more different random access preamble subsets is mapped to the one or more different attributes of the traffic to be sent from the UE.

19. The method of claim 18, wherein the configuration information is sent via radio resource control (RRC) signaling.

20. The method of claim 19, wherein the RRC signaling maps each of the two or more different random access preamble subsets to a different combination of two or more attributes of traffic to be sent from the UE.

21. The method of claim 13, wherein the receiving the first wake-up signal comprises: An uplink control channel transmission is received, the uplink control channel transmission including a payload indicative of the one or more different attributes of traffic to be sent from the UE.

22. The method of claim 21, wherein the payload comprises an index value in a set of index values, wherein each index value in the set of index values ​​is mapped to a different combination of two or more attributes of traffic to be sent from the UE.

23. The method according to claim 13, further comprising: A response communication is sent to the UE based at least in part on the first attribute indicated by the first wake-up signal.

24. The method of claim 23, wherein 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.

25. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving configuration information for wake-up signal transmission, the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic 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 to be sent from the UE; as well as Based at least in part on the first attribute indicated by the first wake-up signal, the first wake-up signal is sent during a wake-up signal occasion to indicate to a cell that the cell is requested to be active during a time period outside of the wake-up signal occasion.

26. The apparatus of claim 25, wherein the set of wake-up signals comprises 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 to be sent from the UE.

27. The apparatus of claim 25, wherein the instructions for sending the first wake-up signal are executable by the processor to cause the apparatus to: An uplink control channel transmission is transmitted, the uplink control channel transmission including a payload indicative of the one or more different attributes of traffic to be transmitted from the UE.

28. An apparatus for wireless communication at a network entity, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: Sending configuration information for wake-up signal transmission to a user equipment (UE), the configuration information indicating a wake-up signal set, each wake-up signal in the wake-up signal set indicating one or more different attributes of traffic to be sent from the UE; receiving a first wake-up signal from the UE during a wake-up signal monitoring opportunity; as well as One or more parameters associated with transitioning to an active state for communicating with the UE are determined based at least in part on a first attribute of first traffic to be sent from the UE, the first attribute being indicated by the first wake-up signal.

29. The apparatus of claim 28, wherein the set of wake-up signals comprises 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 to be sent from the UE.

30. The apparatus of claim 28, wherein the instructions for receiving the first wake-up signal are executable by the processor to cause the apparatus to: An uplink control channel transmission is received, the uplink control channel transmission including a payload indicative of the one or more different attributes of traffic to be sent from the UE.

Images