Method and apparatus for efficient power saving in wireless network

Abstract

To disclose methods and apparatus for power saving in a wireless network.SOLUTION: A Wireless Transmit / Receive Unit (WTRU) may comprise a transmitter, a receiver, and a processor. The processor may determine a processing state pertaining to behavior of the WTRU and determine a minimum amount of resources to be processed for one or more sets of physical resources based on the determined processing state. Each respective set of physical resources may comprise resources in time, and any of frequency or space. For each respective set of physical resources, the time may comprise a frame structure associated with a numerology applicable to the respective set of physical resources, the frequency may comprise any of a frequency location, a bandwidth, or the numerology, and the space may comprise one or more beams. The processor may process the determined minimum amount of resources of the one of more sets of physical resources.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] This application relates to power saving features in wireless communications. [Background technology]

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 62 / 373,130, filed August 10, 2016, U.S. Provisional Patent Application No. 62 / 416,404, filed November 2, 2016, U.S. Provisional Patent Application No. 62 / 441,804, filed January 3, 2017, U.S. Provisional Patent Application No. 62 / 453,372, filed February 1, 2017, and U.S. Provisional Patent Application No. 62 / 474,665, filed March 22, 2017, the contents of each of which are incorporated by reference herein as if fully set forth.

[0003] Mobile communications is constantly evolving and is already on the threshold of its fifth incarnation, called the fifth generation ("5G"). As with previous generations, new use cases are being proposed in conjunction with setting requirements for new systems. Summary of the Invention

[0004] Methods, apparatuses, and systems are provided for a wireless transmit / receive unit (WTRU) device to implement power saving features. In one embodiment, the WTRU device may be configured to determine a processing state related to a behavior of the WTRU and determine a minimum amount of resources to be processed for one or more sets of physical resources based on the determined processing state. Each respective set of physical resources may comprise resources in terms of time and either frequency or space. For each respective set of physical resources, the time may comprise a frame structure associated with a numerology applicable to the respective set of physical resources. The frequency may comprise any of a frequency location (e.g., a center frequency), a bandwidth (e.g., a number of physical resource blocks), or a numerology. The space may comprise one or more beams. The WTRU may be further configured to process the determined minimum amount of resources of the one or more sets of physical resources.

[0005] In another embodiment, a WTRU device may be configured to monitor one or more control channels in multiple spectrum operating modes (SOMs). The WTRU may be configured to operate in at least one power saving mode in at least one SOM. The SOM (e.g., each SOM) may be associated with a control channel that carries information for allocating a set of spectrum blocks for the WTRU.

[0006] In another embodiment, a method performed by the WTRU may be configured to determine a set of resources as a function of a processing state of the WTRU. The WTRU may be further configured to monitor one or more control channels using the determined set of resources. The WTRU may be further configured to decode at least one control channel element on the control channel.

[0007] Methods, apparatus, and systems are provided for a network entity to implement a power saving feature. In one embodiment, the network entity may comprise a transmitter, a receiver, and a processor coupled to the transmitter and the receiver. The network entity may be configured to allocate a set of control channel resources to be used by a WTRU to decode at least one downlink control information (DCI). The resources for the control channel may be organized as a control resource set (CORESET). The network entity may allocate configuration information to the WTRU. The configuration information may indicate at least one identifier, each identifier allocated to the WTRU and other WTRUs, for example, to coordinate processing states of the WTRU and other WTRUs. The network entity may be configured to send a signal to the WTRU indicating the set of control channel resources and send another signal including the configuration information to the WTRU.

[0008] Control of applicable resources in time / frequency / space for one or more control channels

[0009] In some embodiments, the UE may be configured to monitor (e.g., minimally or at least monitor) and decode the control channel using different sets of CORESET, temporal (e.g., minislot, slot, or subframe) resources (e.g., control channel elements (CCEs, search space, aggregation level), frequency resources (e.g., applicable bandwidth, frequency location, etc.), spatial resources (e.g., control beams), and / or signaling structure types (e.g., DCI size, DCI format) (e.g., in different combinations from a minimum set to a maximum set).

[0010] Control of decoding requirements with variable strength as a function of control signaling, etc.

[0011] In another embodiment, the UE may vary the intensity of its control channel reception process as a function of received control signaling, reported radio link quality (e.g., detection of blocking for a beam), type of configured service (e.g., eMBB, URLLC), bearer configuration (e.g., data radio bearer (DRB) and / or signaling radio bearer (SRB) and configured QoS parameters), beam characteristics, beam management characteristics (e.g., number of configured beams and / or beam failure events above or below thresholds), activity observed for a given service (e.g., inter-transmission time, buffer filling / emptying, applicable data rate), or any combination thereof.

[0012] The term "intensity" may refer to the frequency of reception of multiple signaling (e.g., control channels, DCI, CCE, etc.), the amount of information set in the received signal, scheduling intensity (e.g., moving from one control channel monitoring state to another control channel monitoring state as a result of a number of grants being received in a given state, measurements over a time window or at a specific time, and / or based on some rules for transitions related to the number of grants), or any combination.

[0013] For example, TCP-like rate control may be used to control such monitoring activity for eMBB-like services, whereby, from the perspective of the rate control function, successful decoding of downlink control information for a transmission (e.g., on the PDCCH) may be considered an acknowledgment (ACK) and more than a certain amount of time since the last such decoding may be considered a negative acknowledgment (NACK). Other examples are provided herein, e.g., in the "Control Channel Decoding Complexity" section.

[0014] Control of data channel reception as a function of various decoding requirements

[0015] In other embodiments, the UE may be configured to minimally receive the data channel using different sets of resources (e.g., PRBs, spectrum blocks) in time (e.g., minislots, slots, subframes), frequency (e.g., applicable bandwidth, frequency location), space (e.g., data channel beams), and / or type of transmission (e.g., applicable transmission modes) with variable strength. Further examples are described herein, for example, in the "Data Bandwidth Configuration" section.

[0016] Controlling data channel reception as a function of various control channel activities

[0017] The UE may vary the power of its data channel reception (eg, the amount of bandwidth handled by the RF) as a function of the power of the associated control channel.

[0018] Adaptation of such control to the applicability to mixed numerology / transmission durations

[0019] In other embodiments, the UE may be configured to apply and control a power saving mode (e.g., traditional discontinuous reception (DRX) or a combination of the methods described herein) using different timing relationships (e.g., different clocks and / or counts when managing timers). For example, the various timing relationships may be a function of the frame duration associated with a given numerology and / or a function of the associated scheduling opportunity / occasion. [Brief description of the drawings]

[0020] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which:

[0021] [Figure 1A] FIG. 1 is a system diagram of an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] FIG. 1B is a system diagram of an example wireless transmit / receive unit (WTRU) that may be used within the communications system shown in FIG. 1A. [Figure 1C] A system diagram of an example radio access network and an example core network that may be used within the communication system shown in FIG. 1A. [Figure 1D] A system diagram of an example radio access network and an example core network that may be used within the communication system shown in FIG. 1A. [Figure 1E] A system diagram of an example radio access network and an example core network that may be used within the communication system shown in FIG. 1A. [Diagram 2] FIG. 2 illustrates an exemplary bandwidth allocation including nominal system bandwidth and channel bandwidth allocated per UE. [Diagram 3] FIG. 1 illustrates an exemplary flexible spectrum allocation. [Figure 4] FIG. 1 is a representative diagram of a DRX cycle. [Figure 5A] FIG. 2 is a representative diagram illustrating UE monitoring of a control channel in two different activity states. [Figure 5B] FIG. 1 illustrates an exemplary monitoring cycle including control channel monitoring behavior on a UE. [Figure 6A] A representative diagram of a search space for a UE in activity state A. [Figure 6B] FIG. 13 is another representative diagram of a search space for a UE in activity state B. [Figure 7A] FIG. 2 is a representative diagram illustrating the portion of bandwidth reserved for a UE during time period T1. [Figure 7B] FIG. 11 is another representative diagram showing another portion of the bandwidth reserved for the UE during another time period T2. [Figure 7C] FIG. 11 is another representative diagram showing another portion of the bandwidth reserved for the UE during another time period T3. [Figure 8]1 is a flow diagram illustrating an exemplary method for conserving power. [Figure 9] 4 is a flow diagram illustrating another exemplary method for conserving power. [Figure 10] 4 is a flow diagram illustrating another exemplary method for conserving power. [Figure 11] 4 is a flow diagram illustrating another exemplary method for conserving power. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] 1A is a diagram of an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messages, broadcasts, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), etc.

[0023] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, consumer electronics devices, and the like.

[0024] The communications system 100 may also include a base station 114a and a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communications networks, such as the core network 106, the Internet 110, and / or the network 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an evolved Node-B (eNode-B), a home Node B, a home eNode B, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0025] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals within a particular geographic area, sometimes referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In another embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell.

[0026] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communications link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0027] More specifically, as mentioned above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0028] In another embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A).

[0029] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.

[0030] The base station 114b of FIG. 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity within a localized area, such as an office, a home, a vehicle, a campus, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.11, to establish a wireless local area network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.15, to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or femtocell utilizing a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.). As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114 b may not be required to access the Internet 110 via the core network 106 .

[0031] The RAN 104 may communicate with the core network 106, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 may provide call control, charging services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and / or the core network 106 may communicate directly or indirectly with other RANs that use the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize E-UTRA radio technology, the core network 106 may also communicate with another RAN (not shown) that uses GSM radio technology.

[0032] The core network 106 may act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs that may use the same RAT as the RAN 104 or a different RAT.

[0033] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may use a cellular-based radio technology, and with a base station 114b, which may use an IEEE 802 radio technology.

[0034] Figure 1B is a system diagram of an example WTRU 102. As shown in Figure 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0035] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of IC, a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated within an electronic package or chip.

[0036] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0037] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0038] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, UTRA and IEEE 802.11.

[0039] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Additionally, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).

[0040] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control the power to other components within the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., Nickel-Cadmium (NiCd), Nickel-Zinc (NiZn), Nickel Metal Hydride (NiMH), Lithium-Ion (Li-Ion), etc.), solar cells, fuel cells, etc.

[0041] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location determination method while remaining consistent with an embodiment.

[0042] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0043] 1C is a system diagram of the RAN 104 and the core network 106 according to an embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using UTRA radio technology. The RAN 104 may also communicate with the core network 106. As shown in FIG. 1C, the RAN 104 may include Node-Bs 140a, 140b, 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 104. The RAN 104 may also include RNCs 142a, 142b. It will be appreciated that the RAN 104 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.

[0044] As shown in FIG. 1C, the Node-Bs 140a, 140b may communicate with the RNC 142a. Additionally, the Node-Bs 140c may communicate with the RNC 142b. The Node-Bs 140a, 140b, 140c may communicate with their respective RNCs 142a, 142b via an Iub interface. The RNCs 142a, 142b may communicate with each other via an Iur interface. Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected. Additionally, each of the RNCs 142a, 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.

[0045] 1C may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. Although each of the foregoing elements is shown as part of the core network 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0046] The RNC 142a in the RAN 104 may be connected to an MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and MGW 144 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communication devices.

[0047] The RNC 142a in the RAN 104 may also be connected to an SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to a GGSN 150. The SGSN 148 and GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0048] As mentioned above, the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0049] 1D is a system diagram of the RAN 104 and the core network 106 according to another embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the core network 106.

[0050] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0051] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, etc. As shown in FIG 1D, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0052] The core network 106 shown in Figure 1D may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is shown as part of the core network 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0053] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0054] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions such as anchoring the user plane during inter-eNode-B handovers, triggering paging when downlink data is available to the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.

[0055] The serving gateway 164 may also be connected to a PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0056] The core network 106 may facilitate communications with other networks. For example, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 106 and the PSTN 108. Additionally, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0057] 1E is a system diagram of the RAN 104 and the core network 106 according to another embodiment. The RAN 104 may be an Access Service Network (ASN) that communicates with the WTRUs 102a, 102b, 102c over the air interface 116 using IEEE 802.16 radio technology. As described further below, communication links between different functional entities, the WTRUs 102a, 102b, 102c, the RAN 104, and the core network 106, may be defined as reference points.

[0058] 1E, the RAN 104 may include base stations 170a, 170b, 170c and an ASN gateway 172, although it will be appreciated that the RAN 104 may include any number of base stations and ASN gateways while remaining consistent with an embodiment. The base stations 170a, 170b, 170c may each be associated with a particular cell (not shown) in the RAN 104 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the base stations 170a, 170b, 170c may implement MIMO technology. Thus, the base station 170a, for example, may use multiple antennas to transmit wireless signals to and receive wireless signals from the WTRU 102a. The base stations 170a, 170b, 170c may also provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, etc. The ASN gateway 172 may act as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 106, etc.

[0059] The air interface 116 between the WTRUs 102a, 102b, 102c and the RAN 104 may be defined as an R1 reference point that implements the IEEE 802.16 standard. Additionally, each of the WTRUs 102a, 102b, 102c may establish a logical interface (not shown) with the core network 106. The logical interface between the WTRUs 102a, 102b, 102c and the core network 106 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0060] The communication link between each of the base stations 170a, 170b, 170c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations. The communication link between the base stations 170a, 170b, 170c and the ASN gateway 172 may be defined as an R6 reference point that may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0061] As shown in Figure IE, the RAN 104 may be connected to a core network 106. The communication link between the RAN 104 and the core network 106 may be defined as an R3 reference point, including protocols for facilitating data transfer and mobility management capabilities, for example. The core network 106 may include a Mobile IP Home Agent (MIP-HA) 174, an Authentication, Authorization, and Accounting (AAA) server 176, and a gateway 178. Although each of the aforementioned elements is shown as part of the core network 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0062] The MIP-HA 174 may be responsible for IP address management and may enable the WTRUs 102a, 102b, 102c to roam between different ASNs and / or different core networks. The MIP-HA 174 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 176 may be responsible for user authentication and supporting user services. The gateway 178 may facilitate interworking with other networks. For example, the gateway 178 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. Additionally, the gateway 178 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0063] Although not shown in FIG. 1E, it will be appreciated that the RAN 104 may be connected to other ASNs and the core network 106 may be connected to other core networks. The communication link between the RAN 104 and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating mobility of the WTRUs 102a, 102b, 102c between the RAN 104 and the other ASNs. The communication link between the core network 106 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between a home core network and a visited core network.

[0064] The following paragraphs provide a general description of possible approaches for designing 5G systems that may accommodate, at least in part, new radio access technologies ("NR"), without limiting the applicability of various embodiments described further herein to such methods, apparatus, and / or systems.

[0065] The 5G air interface can be expected to enable at least the following use cases: improved broadband performance ("IBB"), industrial control and communications ("ICC") and vehicular applications ("V2X"), and high capacity machine type communications ("mMTC").

[0066] The above use cases may have support for ultra-low transmission latency (Low Latency Communication, "LLC"). Round trip time ("RTT") air interface latencies as low as 1 ms may have support for transmission time intervals ("TTI") anywhere between 100 μs and 250 μs (but not longer). Support for ultra-low access latency (e.g., time from initial system access to completion of transmission of the first user plane data unit) may be implemented. At least ICC and V2X may support end-to-end (e2e) latency of less than 10 ms.

[0067] A use case may have support for Ultra Reliable Communications ("URC"). In a representative embodiment, a transmission reliability may be implemented that may be better than what is possible with conventional LTE systems (e.g., much better than, e.g., above a threshold level). For example, a possible target may be close to or about 99.999% transmission success and service availability.

[0068] Another consideration may be support for mobility for speeds in the range 0-500km / h.

[0069] Moreover, at least ICC and V2X will be-6 has (e.g., is likely to have) a packet loss ratio ("PLR") less than

[0070] Use cases may include support for machine type communication ("MTC") operation (including narrowband operation). The air interface may efficiently support narrowband operation (e.g., using less than 200 KHz), extended battery life (e.g., up to 15 years autonomy), and low data rates in the range of 1 to 100 kbps with minimal communication overhead for small and infrequent data transmissions, e.g., access latencies of a few seconds to a few hours.

[0071] Next Generation of Wireless Access - Principles for "5G" or "5gFLEX"

[0072] Orthogonal frequency division multiplexing ("OFDM") may be used as a signal format for data transmission in Long Term Evolution ("LTE", e.g., 3GPP LTE R8 and above) and / or IEEE 802.11. OFDM may essentially effectively divide the spectrum into multiple parallel orthogonal subbands (or subcarriers). The subcarriers (e.g., each subcarrier) may be shaped using a rectangular window in the time domain, resulting in sinc-shaped subcarriers in the frequency domain. OFDMA uses frequency synchronization (e.g., full frequency synchronization) and strict control of uplink ("UL") timing alignment within the duration of the cyclic prefix to maintain orthogonality between signals and minimize inter-carrier interference. Such strict synchronization may be less suitable for systems in which user equipment ("UE") is connected to multiple access points simultaneously. Additional power reduction is applied (e.g., commonly applied) to uplink transmissions corresponding to the spectral emission requirements of adjacent bands, e.g., in the presence of aggregation of fragmented spectrum for UE transmissions.

[0073] It is recognized that some of the shortcomings of conventional (i.e., cyclic prefix) OFDM ("CP-OFDM") can be addressed by more stringent radio front-end ("RF") requirements for implementations and, for example, when operating using large amounts of contiguous spectrum without the need for aggregation. Cyclic prefix ("CP") based OFDM transmission schemes may lead to a downlink ("DL") physical layer for 5G similar to that of legacy systems, e.g., primarily modifications of pilot signal density and location.

[0074] Although other waveform candidates may be implemented for 5G flexible radio access technology ("5gFLEX"), CP-OFDM remains a candidate for 5G systems (at least for the downlink transmission scheme).

[0075] For example, several principles applicable to flexible radio access implementations for 5G are described herein.

[0076] Such description is for exemplary purposes and is not intended to limit in any way the applicability of the embodiments described further herein as they apply to other wireless technologies and / or wireless technologies using different principles, when applicable.

[0077] Principle A - Spectral Flexibility

[0078] The 5gFLEX Radio Access may be characterized by a very high degree of spectrum flexibility, enabling deployment in different frequency bands with different characteristics, including different duplex configurations, different and / or variable sizes of available spectrum, including contiguous and non-contiguous spectrum allocations within the same or different bands. The 5gFLEX Radio Access may support variable timing aspects, including multiple TTI lengths and asynchronous transmission.

[0079] Principle A.1 - Flexibility in duplex configurations

[0080] Time division duplexing ("TDD") and / or frequency division duplexing ("FDD") schemes may be implemented. For FDD operation, the supplemental downlink operation may be implemented using spectrum aggregation. The FDD operation may implement full-duplex and / or half-duplex FDD operation. For TDD operation, the DL / UL allocation may be dynamic, e.g., the DL / UL allocation may not be based on a fixed DL / UL frame configuration, e.g., the length of the DL transmission interval and / or the UL transmission interval may not be set for each transmission opportunity.

[0081] Principle A.2 - Bandwidth flexibility

[0082] One possible characteristic of a 5G air interface implementation is to allow the possibility of different transmission bandwidths on both the uplink and downlink, ranging, for example, from anything between the nominal system bandwidth to a maximum value corresponding to the system bandwidth.

[0083] For single carrier operation, the system bandwidth may include, for example, at least 5, 10, 20, 40, and / or 80 MHz. The system bandwidth may be any bandwidth within a given range, for example, from a few MHz to 160 MHz. The nominal bandwidth may have one or more fixed values. Narrowband transmissions up to 200 KHz may be supported within the operating bandwidth, for example, for MTC devices.

[0084] FIG. 2 illustrates a representative bandwidth allocation including a nominal system bandwidth and a channel bandwidth allocated per UE. System bandwidth 201 herein may refer to the maximum portion of spectrum that can be managed by the network for a given carrier. For a given carrier, the portion that the UE minimally supports for cell acquisition, measurements, and initial access to the network may correspond to the nominal system bandwidth 202. The UEs may be configured with a channel bandwidth that may be within the entire system bandwidth. For example, a channel bandwidth 203, e.g., 10 MHz, that includes the nominal system bandwidth 202 may be allocated to UEx, and another channel bandwidth 204, e.g., 20 MHz, that includes the nominal system bandwidth 202 may be allocated to UEy. The channel bandwidth may or may not include the nominal portion of the system bandwidth. For example, the channel bandwidth 205 allocated to UEz does not include the nominal system bandwidth 202 as shown in FIG. 2.

[0085] Baseband filtering of frequency domain waveforms can be used to achieve bandwidth flexibility, for example, baseband filtering may avoid the use of additional licensed channel bandwidths within the UE's operating band and the associated RF requirements of these additional licensed channel bandwidths.

[0086] Methods may be implemented for configuring, reconfiguring, and / or dynamically changing a UE's channel bandwidth for single carrier operation and / or for allocating spectrum for narrowband transmissions within a nominal system, system and / or configured channel bandwidth.

[0087] The physical layer of the 5G air interface may be band-agnostic and may support operation in licensed bands below 5 GHz and / or in unlicensed bands in the range 5-6 GHz. For operation in unlicensed bands, a Listen-Before-Talk ("LBT") Cat4-based channel access framework similar to LTE Licensed Assisted Access ("LAA") may be implemented.

[0088] Methods for scaling and managing (eg, scheduling, resource addressing, broadcast signaling, measurement) cell-specific channel bandwidth and / or UE-specific channel bandwidth for arbitrary spectral block sizes may be implemented.

[0089] Principle A.3 - Flexible spectrum allocation

[0090] Downlink control channels and signals may support frequency division multiplexing ("FDM") operation. A UE may acquire a downlink carrier by receiving a transmission using a nominal portion (e.g., only the nominal portion) of the system bandwidth; e.g., the UE may not initially be configured and / or required to receive a transmission covering the entire bandwidth managed by the network for the involved carrier.

[0091] The downlink data channel may be allocated, for example, on a bandwidth that may or may not correspond to a nominal system bandwidth, with no restrictions other than within the UE's configured channel bandwidth. For example, a network may operate a carrier with a 12 MHz system bandwidth using a 5 MHz nominal bandwidth that allows devices supporting up to a 5 MHz maximum RF bandwidth to acquire and access the system, and allocates, for example, +10 to -10 MHz of the carrier frequency to other UEs supporting up to 20 MHz worth of channel bandwidth.

[0092] FIG. 3 shows an example of a flexible spectrum allocation including, for example, a nominal bandwidth 307 that allows devices to acquire and access the system. Flexible spectrum allocations with different sets of subcarriers, for example, 305 and 306, may be assigned to different modes of operation (hereafter spectrum operation modes, SOMs). Different SOMs may be used to fulfill different requirements for different transmissions, for example, spectrum allocations with variable transmission characteristics 303 and 304 disclosed in FIG. 3. A SOM may be associated with a particular numerology. A numerology may be, for example, a set of resource allocations with configured transmission bandwidths in the uplink and / or downlink of a cell. A numerology may be used as a reference for transmitter and receiver radio frequency requirements. A SOM may consist of and / or include at least one of subcarrier spacing, TTI length, and / or one or more reliability aspects, for example, hybrid automatic repeat request ("HARQ") processing aspects, and / or secondary control channels. A SOM may be used to refer to a particular waveform or may relate to processing aspects, such as in supporting coexistence of different waveforms in the same carrier using frequency division multiplexing ("FDM") and / or time division multiplexing ("TDM"). A block of time and frequency resources may be associated with a SOM.

[0093] Principle A.4 - Spectral Operating Mode ("SOM")

[0094] The UE may be configured to perform transmissions with one or more SOMs. The SOMs may be associated with a particular numerology. For example, the SOMs may correspond to transmissions using at least one of a particular TTI duration, a particular initial power level, a particular HARQ processing type, a particular upper limit for successful HARQ reception / transmission, a particular transmission mode, a particular physical channel (e.g., uplink or downlink), a particular waveform type, and / or transmissions with a particular RAT (e.g., legacy LTE or LTE with 5G transmission methods).

[0095] The SOM may comprise a quality of service ("QoS", from a physical layer perspective) level and / or associated aspects, e.g., maximum / target latency, maximum / target block error rate ("BLER"), or something similar. The SOM may comprise a spectrum area and / or a particular control channel or aspects thereof (including search space, downlink control information ("DCI") type, etc.). For example, a UE may be configured with a SOM for each or any of URC type services, LLC type services, and / or bulk broadband ("MBB") type services. For example, a UE may have a configuration for a SOM for system access and / or for transmission / reception of L3 control signaling (e.g., radio resource control, "RRC") in a portion of the spectrum associated with the system, e.g., within a nominal system bandwidth. A block of time and frequency resources may be associated with a SOM. A SOM (each SOM) may be associated with a control channel, e.g., different control channels on different blocks of resources.

[0096] Principle A.5 - Spectrum aggregation

[0097] For single-carrier operation, spectrum aggregation may be implemented, whereby a UE may support transmission and reception of multiple transport blocks on a contiguous or non-contiguous set of physical resource blocks (PRBs) within the same operating band. Mapping of a single transport block to a separate set of PRBs may also be implemented. Support for simultaneous transmissions associated with different SOM requirements may also be implemented.

[0098] For example, multi-carrier operation using contiguous or non-contiguous spectrum blocks within the same operating band or across two or more operating bands may be implemented. Aggregation of spectrum blocks using different modes, e.g., FDD and TDD, and using different channel access methods, e.g., sub-6 GHz licensed and / or unlicensed band operation, may be implemented. Support for configuring, reconfiguring, and / or dynamically changing a UE's multi-carrier aggregation may also be implemented.

[0099] Principle A.6 - Scheduling and rate control

[0100] Scheduling functionality may be supported at the Medium Access Control ("MAC") layer. Two scheduling modes may be considered: network-based scheduling for strict scheduling regarding resources, timing, and transmission parameters of downlink and / or uplink transmissions, and UE-based scheduling for more flexibility regarding timing and transmission parameters. For both modes, the scheduling information may be valid for a single TTI or for multiple TTIs.

[0101] Principle A.6.1 - Network-based scheduling

[0102] Network-based scheduling may allow the network to manage (e.g., tightly manage) available radio resources assigned to different UEs, e.g., to optimize resource sharing. Dynamic scheduling may be implemented.

[0103] Principle A.6.2 - UE-based scheduling

[0104] UE-based scheduling may enable a UE to opportunistically access uplink resources as needed with minimal latency, e.g., within a set of shared or dedicated uplink resources allocated (e.g., dynamically or not) by the network. Both synchronous and asynchronous opportunistic transmissions may be implemented. Both contention-based and contention-free transmissions may be implemented.

[0105] Support for machine-based transmissions (scheduled or unscheduled) may be implemented, for example, to meet the ultra-low latency requirements for 5G and the power saving requirements of mMTC use cases.

[0106] Principle A.7 - Logical channel prioritization

[0107] 5gFLEX may support some form of association between data available for transmission and resources available for uplink transmission. Multiplexing of data with different QoS requirements within the same transport block may be supported, for example, as long as the multiplexing does not introduce adverse effects for services with the most stringent QoS requirements and / or does not introduce unnecessary waste of system resources.

[0108] Principle B - Logical Channels ("LCH")

[0109] Principle B.1-LCH

[0110] An LCH, as used herein, may represent a logical association between data packets and / or protocol data units ("PDUs"). This logical association may be based on the data units being associated with the same bearer and / or the same SOM and / or slice (e.g., processing path using a set of physical resources, etc.), whereby, for example, the association may be characterized by at least one of a chain of processing functions, an applicable physical data (and / or control) channel (or an instance thereof), and / or an instantiation of a protocol stack including certain parts being centralized (e.g., PDCP only, or something beyond parts of physical layer processing, e.g., radio front-end ("RF")) and other parts being closer to the edge (e.g., MAC / physical ("PHY") at a transmit / receive point ("TRP"), or RF only), separated, for example, by a fronthaul interface. The term LCH, as used herein, may have a different and / or broader meaning than similar terms for LTE systems.

[0111] Principle B.2 - Flow-based methods, tuples

[0112] The UE may be configured such that it may determine a relationship between different data units. For example, the relationship may be based on a matching function, e.g., based on a configuration of one or more field values ​​common to data units that are part of the same logical association. The fields may correspond to fields in a protocol header associated with the data unit. For example, the matching function may use a tuple of parameters for fields of the Internet Protocol ("IP") header of the data unit, such as IP source / destination addresses, transport protocol source / destination ports, and / or transport protocol type, including, e.g., IP version, e.g., IPv4 or IPv6.

[0113] For example, data units that are part of the same logical association may share common radio bearers, processing functions, SOMs, and / or correspond to the same LCH and / or logical channel group ("LCG").

[0114] Principle C-LCG

[0115] In this specification, an LCG may consist of and / or include a group of LCHs (or equivalents as defined above), the grouping being based on one or more criteria. The criteria may be that one or more LCHs may be applicable to all LCHs of the same LCG, or may be associated with the same SOM (or type thereof), the same slice (or type thereof), have a similar priority level, whereby, for example, the association may be characterized by at least one of a chain of processing functions, an applicable physical data (and / or control) channel (or an instance thereof), or an instantiation of a protocol stack that includes a particular part that is centralized (e.g., only PDCP and / or something other than RF) and another part that is closer to the edge (e.g., only MAC / PHY and / or RF in the TRP), separated, for example, by a fronthaul interface. The term LCG may have a different and / or broader meaning in this specification than similar terms for LTE systems.

[0116] Principle D - Transport Channel ("TrCH")

[0117] Principle D.1-TrCH

[0118] As used herein, a TrCH may consist of and / or include a particular set of processing operations and / or functions applied to data information that may affect one or more transmission characteristics over the air interface.

[0119] Principle D.2 - TrCH in LTE

[0120] Legacy LTE defines several types of TrCHs, including, for example, the Broadcast Channel (BCH), the Paging Channel (PCH), the Downlink Shared Channel (DL-SCH), the Multicast Channel (MCH), and the Uplink Shared Channel (UL-SCH) in addition to the Random Access Channel (which typically does not carry user plane data). The main transport channels for carrying user plane data are the DL-SCH and UL-SCH for the downlink and uplink, respectively.

[0121] Principle D. TrCH for 3-5G systems

[0122] For 5G systems, an enhanced set of requirements supported by the air interface may lead to the implementation of multiple transport channels for a single UE (e.g., even for a single UE device), for example, for user plane data and / or control plane data. The term TrCH may have a different and / or broader meaning herein than the similar term for LTE systems. For example, a transport channel for ultra-reliable and low latency communications ("URLLC") (e.g., URLLCH) for mobile wideband (MBBCH) and / or for machine type communications ("MTCCH") may be defined for downlink transmissions (e.g., DL-URLLCH, DL-MBBCH, and DL-MTCCH) and for uplink transmissions (e.g., UL-URLLCH, UL-MBBCH, and UL-MTCCH).

[0123] In one example, multiple TrCHs may be mapped to different sets of physical resources (e.g., PhCHs) belonging to the same SOM, which may enable, for example, simultaneous transmission of traffic with different requirements on the same SOM. For example, the URLLCH may be transmitted simultaneously with the MTCCH when the UE is configured with a single SOM.

[0124] In LTE, there are two mode DRX for power saving, eg, connected mode DRX and idle mode DRX.

[0125] Connected Mode DRX may specify minimum Physical Downlink Control Channel (PDCCH) decoding requirements while the UE is configured with Connected Mode DRX. Connected Mode DRX may define active times for decoding of DCI with (Semi-Persistent Scheduling, "SPS"-) Cell Radio Network Identifier (RNTI), Transmit Power Control-Physical Uplink (Shared / Control) Channel, "TPC-PU(S / C)CH"-RNTI, Enhanced Interference Mitigation Traffic Adaptation "eIMTA"-RNTI, and Sidelink (SL)-RNTI, and may be based on a fixed period "On Duration" that occurs once per DRX cycle.

[0126] 4 is a representative diagram of a DRX cycle. A DRX cycle 401 (e.g., each DRX cycle) may consist of or include an On Duration 402 interval and an opportunity for DRX 403 interval. A UE in connected mode DRX may be configured to monitor a PDCCH 404 during an On Duration 402 interval.

[0127] The DRX operation may be controlled by the following timers: (1) onDurationTimer, indicating the number of consecutive PDCCH subframes at the beginning of a DRX cycle; (2) drx-InactivityTimer, indicating the number of consecutive PDCCH subframes after the subframe in which the PDCCH indicates an initial UL user data transmission, an initial DL user data transmission, or an initial SL user data transmission for this MAC entity; (3) longDRX-Cycle, indicating the number of subframes in the long DRX cycle configured by higher layers; (4) shortDRX-Cycle, indicating the number of subframes in the long DRX cycle configured by higher layers; and (5) drxShortCycleTimer, indicating the number of consecutive subframes the MAC entity shall or will follow a short DRX cycle.

[0128] IDLE mode DRX may enable a UE in IDLE mode to non-continuously monitor the PDCCH for paging on the P-RNTI. Two types of paging occasions may be defined, including (1) UE-specific paging occasions defined by the MME in the Non-Access Stratum (NAS) and / or (2) cell-specific paging occasions defined by the eNode-B, for example in System Information Block 2 (SIB2).

[0129] The UE can be paged using the P-RNTI while in IDLE mode DRX for DL ​​data arrival to signal changes in system information in the cell, and for Earthquake or Tsunami Warning System (ETWS). Derivation of paging frames and paging occasions may be based on the UE_ID, as defined in Tables A and B below.

[0130] [Table 1]

[0131] [Table 2]

[0132] One challenge with next generation radio access (often referred to as new radio or NR) relates to UE processing complexity and power consumption. Legacy LTE UEs typically use time-based algorithms to determine when they are required and / or will be used to monitor any applicable control channels (e.g., PDCCH) and / or network-controlled activation / deactivation mechanisms that may be used by the UE to retune the radio front end for additional power savings, at a minimum.

[0133] Legacy LTE enables UE power conservation through connected mode DRX and idle mode DRX procedures. In connected mode DRX, the UE monitors the PDCCH for a time interval defined by the On Duration Period. In idle mode DRX, the UE periodically monitors the PDCCH at specific time instances for potential paging messages received from the network. Respective algorithms ensure that the UE and the network have the same understanding of the subframes in which the UE is minimally required to monitor and / or used for the respective control channel.

[0134] In legacy LTE, a UE may support network-controlled activation / deactivation of secondary cells (SCells), for example, on a per component carrier basis.

[0135] These procedures have some drawbacks when considered for the 5G air interface due to the following new features or characteristics that are unique to NR: (1) support for low latency from available (DL / UL) data for assignment / grant transmissions, (2) support for multiple numerologies that may result in multiple control channels and different timing than currently used in LTE (and different timing in NR as a result of different numerologies), and (3) support for flexible spectrum allocation.

[0136] The following represents new challenges for UE power consumption. One challenge may be to support different numerologies including symbol durations, subcarrier spacing, and TTIs of different, possibly variable, durations. NR may support a new set of services / QoS including those with high throughput ("eMBB") and those with very low latency requirements (1 ms RTT). Traditional DRX mechanisms may not be flexible enough to optimally handle the same UE transmissions in different time intervals (e.g., 1 ms vs. 125 μs). Furthermore, legacy DRX mechanisms may fall short in reaching power usage targets. For example, support of low latency services may be difficult when configured with DRX since care may and / or must be taken to avoid introducing undesirable latency and / or resulting in situations where data may arrive at the UE while the UE is in DRX. UEs may benefit from efficient power saving mechanisms.

[0137] Another challenge may be supporting multiple control channels, including dependencies between channels. In LTE, a single control channel (e.g., PDCCH) exists over the entire bandwidth for a given cell. The duration of the control channel is typically two or three symbols. For NR, the UE may support reception of control information using multiple (to a specific bandwidth) localized control channels. The structure may be useful to allow scaling of control channel resources when load increases and / or to facilitate the addition of new control channels tailored to specific features / services for easier forwarding compatibility.

[0138] Another challenge may be to support flexible / various channel bandwidths (BW). Channel BW for NR may be increased to values ​​beyond those of legacy LTE (e.g., greater than 20 MHz) and may be UE specific. UE power consumption may increase with the amount of bandwidth that the UE is required to process in its baseband and / or used for. Control channel monitoring procedures may explicitly or implicitly control the channel bandwidth applicable to a given UE.

[0139] Another challenge may be to support lean carriers. Control channel decoding in LTE relies on the presence of reference signals. For NR, the amount of "always on" signals may be minimized, for example, primarily to reduce inter-cell interference and / or to support improved network power savings (network DTX). Power saving modes for NR may consider a sparser use of reference signals.

[0140] While new control channel monitoring features, operations, and / or procedures may be used for NR, additional power saving mechanisms, functions, operations, and / or procedures beyond control channel monitoring may be required and / or used to support URLLC and / or eMTC devices (e.g., which may have more stringent battery requirements than LTE).

[0141] Typical UE processing states

[0142] UE Processing State Definitions

[0143] The term state or processing state is generally used hereafter to refer to one or more states related to the behavior of the UE. A processing state may include one or more activity states that may be related to some action taken by the UE when a condition becomes true. This is not intended to limit the applicability of the methods described further herein. An activity state may be equal to or may be a subset of a processing state.

[0144] Representative UE autonomous decisions and network controlled transitions

[0145] In some methods, operations, and / or procedures, the UE may be configured to autonomously determine that a condition becomes true and that the UE should or can perform such an action (e.g., UE autonomous behavior). Alternatively or in addition to an autonomous determination by the UE, the UE may be configured to determine that a condition becomes true and that the UE should or can perform such an action based on an explicit indication received from a signal or from a transmission from the network (e.g., based on network controlled behavior).

[0146] Other typical characterizations of UE processing states

[0147] A UE may be configured to operate under one or more processing states that define and / or govern the behavior of the UE. For example, a processing state may provide a set of minimum requirements for UE behavior, such as behavior related to at least one of the following:

[0148] - control channel processing, e.g. monitoring, reception, decoding and / or configuration management;

[0149] - Spectral bandwidth processing, e.g., system / channel bandwidth tuning, frequency positioning (e.g., center frequency), baseband processing, and / or configuration management. In some embodiments, the spectral bandwidth processing may be applied to the control channel region and the data channel region, together and / or separately, e.g., for bandwidth portions consisting of a group of contiguous physical resource blocks and / or for a portion of the system / channel bandwidth of a carrier;

[0150] - Beam management and processing, e.g., establishing, maintaining, and / or receiving / transmitting using control beams and / or data beams, and / or

[0151] - Reference signal processing, e.g. measurement processing and configuration management.

[0152] Other representative aspects / operations may include at least one of the following.

[0153] - HARQ timing related aspects / operations;

[0154] The processing or activity level may control the UE framing related behavior, e.g. subframe vs. slot vs. minislot usage;

[0155] Framing and / or timing related aspects / operations, e.g., different numerologies, transmission durations, scheduling occasions, subframe, and / or slot and / or minislot operations, and / or HARQ timelines may be associated with (e.g., active) different processing states.

[0156] In some embodiments using a subframe-based DRX active time, the UE may be configured to monitor the control channel at a first (e.g., low) timing granularity while in a first processing state (e.g., a low processing state) for the control channel, e.g., to enable (1) a first particular numerology (e.g., 1 ms transmission duration), (2) a particular set of scheduling occasions (e.g., 1 ms subframes), and / or a HARQ timeline (e.g., a particular value of x, HARQ RTT between scheduling and UL transmission, UL / DL transmission, and associated DL / UL feedback, respectively).

[0157] For example, a UE may be in a low processing state using a 1 ms transmission duration with a 1 ms scheduling occasion, and a x1 ms UE / eNB processing delay, such as x=3, leads to an 8 ms RTT for the HARQ process.

[0158] The smallest unit of time in an OFDM system may generally be referred to as a "symbol". A symbol has a symbol duration. In LTE, there may be 14 symbols per 1 ms subframe, such that the symbol duration is 1 / 14 ms. The symbol duration may be a function of the numerology used for the carrier, which may be the same in LTE.

[0159] In another embodiment using a slot-based DRX active time (e.g., by slot duration and / or minislot duration), the UE may be configured to monitor (e.g., additionally monitor) the control channel using a second (e.g., high) timing granularity while in a second processing state (e.g., high processing state) for the control channel, e.g., to enable a second numerology (e.g., e.g., 125 μs transmission duration, or a minislot of one or a few symbols with approximately 125 μs transmission duration), a particular set of scheduling occasions (e.g., scheduling occasions of one or a few symbols or one or a few minislots), and / or a HARQ timeline (e.g., a particular value x2 between scheduling and UL transmission, transmission, and feedback, HARQ RTT, etc.). For example, a minislot may refer to a duration equal to one or more symbols, a slot may refer to a duration equal to several symbols (e.g., 7 symbols), and a subframe may refer to multiple slots (e.g., 2 slots per subframe). Depending on the numerology, the time duration may differ for either minislots, slots, and / or subframes. For numerologies equal to that of LTE, the same time duration applies (e.g., always applies). In one representative embodiment, the numerology for the default carrier may support LTE numerology.

[0160] For example, a UE may be in a high processing state with a slot transmission duration of 1 ms and a minislot transmission duration of 125 μs, with corresponding reception of control signaling at minislot boundaries, e.g., to allow for different HARQ timelines as a function of received control signaling. The transmission duration, control signaling, and HARQ timeline may depend, e.g., on the type of DCI decoded in the first processing state and / or the second processing state, i.e.,

[0161] - logical channel properties and / or configurations, and / or

[0162] Low-cost signal monitoring configurations and / or behaviors as described herein, for example in the "Control Channel Decoding Complexity" section. may have an impact on

[0163] In some embodiments, any of the above aspects, operations, procedures, functions, and / or characteristics of the UE processing state may be organized and / or structured using patterns over a predefined period of time. The start of the pattern may be configurable using a well-defined and / or well-known reference in time. For example, the UE may be configured to have a reference related to a system frame number, system timing, frame timing, and / or to the reception of a particular signal. For example, such a signal may consist of and / or include a reference signal associated with, for example, a channel to which the pattern is applicable. The pattern may be configurable and / or well-defined between the UE and the network. For example, the UE may be configured to determine the applicable pattern from a table of standardized values ​​and / or from the reception of signaling including the pattern information, such that, for example, the UE behavior is synchronized in time and predictable from the network's perspective.

[0164] In some embodiments, the UE may be configured to adjust control channel processing and / or spectral bandwidth processing according to a pattern-based configuration for a given processing state, and the UE may be configured to adjust other aspects including spectral bandwidth processing, such as beam processing, as a function of changes in the UE's processing state, e.g., according to other methods, operations, and / or procedures described herein.

[0165] In some embodiments, the UE may be configured with a first pattern for receiving and blind decoding one or more control channels. In an embodiment, the UE may be configured to determine (e.g., and perform) blind decoding attempts using different control channels (e.g., one or more control channels) from one control channel scheduling opportunity / occasion to another according to the pattern. For example, the UE may be configured to decode a first control channel at scheduling occasions 3 and 6 from a sequence of 10 occasions (e.g., numbered 0 through 9), while the UE may be configured to decode a second control channel during other occasions for a first processing level. For a second processing level, the UE may not be configured to decode any of the control channels for occasions 0, 1, 2, 8, and 9.

[0166] In other representative embodiments, the UE may be configured to determine (e.g., perform) blind decoding attempts using different sets of control channel resources (e.g., CORESET), CCEs, search spaces, etc. for a given control channel from one control channel scheduling opportunity / occasion to another control channel scheduling opportunity / occasion depending on the pattern.

[0167] In other representative embodiments, the UE may be configured to determine (e.g., and / or receive) a bandwidth portion for a given control channel at a particular frequency location and / or for a given numerology, e.g., from one control channel scheduling opportunity / occasion to another control channel scheduling opportunity / occasion, according to a pattern. For example, the UE may be configured to receive on a single (e.g., default) bandwidth portion and / or CORESET for a first processing level. For a second processing level, the UE may be configured to receive on all configured bandwidth portions and / or CORESET.

[0168] In one representative embodiment, the UE may be configured to determine (e.g., and perform) blind decoding attempts using different aggregation levels (ALs) from one control channel scheduling opportunity / occasion to another according to a pattern. The UE may be configured to decode the control channel using only AL=16 on scheduling occasions 3 and 6 from a sequence of 10 occasions (e.g., numbered 0 to 9), AL=4, 8 on scheduling occasions 4 and 5, and not decode otherwise for the first processing level. For the second processing level, the UE may be configured to decode on all occasions with AL=16. The AL may be configured based on the control channel loading, UE geometry, etc.

[0169] In one representative embodiment, the UE may be configured to determine (e.g., perform) blind decoding attempts using different sets of one or more DCIs from one control channel scheduling opportunity / occasion to another control channel scheduling opportunity / occasion in a pattern.

[0170] In some representative embodiments, the UE may be configured for receiving and / or bandwidth processing, e.g., to determine (e.g., and perform) system / channel bandwidth tuning using a different set of physical resource blocks from one control channel scheduling opportunity / occasion to another control channel scheduling opportunity / occasion depending on the pattern.

[0171] The pattern may correspond to a particular amount of time (eg, per symbol, per millisecond, and / or per scheduling opportunity / occasion) that may be repeated periodically in time.

[0172] The start of the pattern may correspond to a particular time instance (e.g., the first symbol of a minislot, slot, and / or subframe), e.g., to a system frame number, to the first subframe of a frame, or to a received signal (e.g., a reference signal) that may be repeated periodically in time, or to a successfully decoded transmission (e.g., DCI, or MAC CE).

[0173] In some embodiments, a UE processing state may be associated with one such pattern for one or more such aspects, operations, procedures, and / or characteristics, and when the UE changes the applicable processing level, it may be configured to change the applicable pattern, which changes one or more involved aspects, operations, procedures, and / or characteristics.

[0174] The UE may be configured to receive control signaling that configures the UE's operational processing state, for example, according to one of a plurality of processing states. The processing state may be associated with a defined set of properties related to one or more of the configurations described above. For example, the processing state may be associated with a particular control channel configuration, data bandwidth, and / or usage configuration, etc. The properties associated with the processing state (e.g., each processing state) may be predefined, for example, by a specification, a lookup table, a rule, and / or may be dynamically signaled and / or set. In a representative embodiment, the UE may be configured to have the properties of the processing state based on the reception of a signal (e.g., an RRC signal), either through broadcast or dedicated signaling. Such a signal may be associated with a particular control channel monitoring configuration, data bandwidth configuration, and / or usage, HARQ timing configuration, etc. for the particular processing state.

[0175] A processing state may be associated with an index or identifier to identify that particular processing state and to reference that processing state for signaling between the UE and the network, for example.

[0176] Triggers for changing processing state

[0177] Network-controlled migration

[0178] The UE may be configured to determine that the UE should or can move to a different processing state based on receipt of signaling from the network, such as, for example, on a control channel, an RRC message, a MAC CE, a DCI message, a "low cost" signal as described herein, for example, in the "Data Bandwidth Configuration" section, and at least one of timer-based operations controlled by receipt and / or configuration of control signaling.

[0179] Timer-based operations may be controlled by signaling from the network. For example, in one representative embodiment, when a timer is used to control the behavior of the UE, the UE may perform procedure / logical operation A when the timer is running, and otherwise the UE may perform procedure / logical operation B. In another representative embodiment, the timer itself may be controlled by receiving signaling (e.g., the timer may be stopped if control message X is received, restarted if control message Y is received, etc.).

[0180] In some embodiments, the timer may be configured to control the behavior of the UE. For example, when the timer is running, the UE may perform a set of procedures / logical operations. Otherwise, the UE may perform another set of procedures / logical operations, for example when the timer itself may be controlled by receipt of signaling (e.g., the timer may be stopped if control message X is received from the network, restarted if control message Y is received from the network, etc.).

[0181] Such signaling may identify the index of the processing state to be configured, as well as potentially the time at which the processing state change should occur, or the processing state change may occur at a predefined or statically defined time difference between the time the transition message is received and the time at which the configuration change associated with the new processing state should occur.

[0182] UE Determined Transition

[0183] In another embodiment, the UE may be configured to detect a number of events, such as: 1) scheduling activity, an increase or decrease in scheduling activity for one or more control channels; 2) arrival, e.g., activation and / or configuration, of a new service at the UE; 3) availability for transmission and / or successful reception / transmission at the UE of data having a particular property (e.g., low latency requirement); 4) data in the UE buffers dropping above or below a threshold, e.g., for a particular bearer, bearer type, service, e.g., type based on QoS profile, SOM, TrCH, and any equivalent; 5) expiration of a timer related to UE activity or scheduling activity; 6) UE speed exceeding or falling below a certain value; and 7) current battery life. reaching a certain value; 8) triggering and / or initiation of a scheduling request and / or access procedure; 9) initiation and / or transmission autonomously initiated by the UE, e.g., a contention based uplink transmission on the uplink control channel, a grantless transmission, a scheduling request, or a preamble on the PRACH; 10) state of a HARQ process, e.g., exceeding some latency criterion / threshold in time and / or for some retransmissions for a HARQ process; and 11) state of beam management, e.g., a change of beam, a change of beam configuration, a beam failure event occurrence, and / or a successful transmission of a beam restoration request.

[0184] In some embodiments, the UE may be configured to determine the above events for transitioning between one processing state and another processing state based on timer configurations and operations, such as when the timer is (re)started upon receiving corresponding control information and when the timer expires.

[0185] In another embodiment, the UE may be configured to determine the above events for transitioning between one processing state and another processing state based on a counter (e.g., based on an occasion for receiving control signaling or based on a transmission performed).

[0186] In such cases, transitions between processing states may be clearly defined based on certain rules, for example, a particular trigger coupled with a pre-transition (e.g., existing or initial) processing state may use or require a transition to one particular post-transition state.

[0187] The UE may also be configured to request a processing state change using an RRC message, MAC CE, or PHY layer signaling. The processing state change request may contain or include at least one of the following information: processing state, potentially of a particular logical channel or type of data, a particular triggering event that triggered the change in buffer occupancy, a state index (or potentially a list of desired state indexes) of the state to which the UE wishes to transition, and parameters associated with the trigger for the state transition, such as channel measurements, beam measurements, beam management events (e.g., beam switch, change of best beam), beam restoration, and requested duration in the target state.

[0188] The UE may be configured to request a change in processing state as a result of at least one of the following triggers: scheduling activity on one or more control channels, an increase or decrease in scheduling activity, arrival of a new service at the UE (e.g., its startup and / or configuration), availability of transmission and / or successful transmission / reception of data at the UE with particular properties (e.g., low latency requirements), data in a UE buffer exceeding or below a threshold, expiration of a timer related to UE activity or scheduling activity, UE speed exceeding or below a certain value, occurrence of a beam obstruction, and current battery life reaching a particular value.

[0189] The following sections describe specific cases of processing state changes based on specific UE configuration related aspects, operations, procedures, and / or functions. Specific triggers mentioned above are possible, as well as more detailed triggers defined for each specific configuration aspect and / or for a particular configuration aspect.

[0190] Control Channel Decoding Complexity

[0191] The embodiments described herein are equally applicable to any data channel resource (e.g., PRB, bandwidth, beam selection, frame aspects (e.g., slots and minislots), if applicable) unless otherwise specified. Possibly, such applicable data channel resources may alternatively or additionally be determined as a function of the state of the UE. The state of the UE may be used to determine the control channel resources, especially when different control channel resources are used to control different spectrum blocks for data transmission.

[0192] The UE monitors control channels with different numbers of CCEs.

[0193] In one embodiment, as part of the UE power saving mode, the UE may be configured to monitor different sets of CORESETs and / or CCEs depending on its operating mode, e.g., its processing or activity state, and may be configured to autonomously change its operating mode over time.

[0194] The current processing state of the UE may be configured to define a control channel monitoring configuration for the UE. The UE may be configured to process (e.g., monitor, receive, blindly decode, or the like) a control channel with various numbers of CCEs and / or various sets of CCEs. For example, the number of CCEs may be changed and / or the actual CCEs to be used for processing may be changed. For example, the UE may be configured to operate in different processing states of various complexity, and the UE may monitor the control channel on different numbers of CCEs and / or different sets of CCEs. For example, the UE may be configured to execute a power saving mode that varies the number of CCEs. The UE may need, be able to, and / or be required to monitor based on certain factors, which may include scheduling processes and / or UE buffer status. The buffer status on the UE may be coordinated with flexible scheduling between the UE and the eNode-B.

[0195] The UE may be configured to perform control channel monitoring by considering multiple processing states, each processing state having a different number of CCEs to be decoded. One possible benefit is a potential reduction in control channel monitoring complexity.

[0196] For example, the UE may be configured to autonomously determine different sets of control channel resources to monitor based on at least one of the following:

[0197] In one embodiment, the UE may be configured to monitor a subband, multiple subbands, a subset of a frequency band, a subset of a system bandwidth, a frequency location (e.g., a center frequency), or a subset of resources of the control channel, which may include an aggregation level.

[0198] While in a first state (e.g., with a first activity level), the UE may be configured to monitor the control channels defined above, such as a first set of resource elements, a first set of applicable aggregation levels, resource blocks, etc., e.g., a first set of one or more control channels. The UE may then be configured to use a second set of resources (possibly including a different number of control channels) when operating in a second state (e.g., with a second activity level).

[0199] For example, in such a first state, the UE may be configured to monitor downlink control information (e.g., DCI) on a first operating band, which may include, for example, a first channel bandwidth, and in a second state, the UE may be configured to monitor DCI that may occupy a different subset of resource elements than the first operating channel bandwidth.

[0200] For example, in such a first state, the UE may be configured to monitor DCI on a first set of control channels. Such first set may provide scheduling for up to a first user plane data rate. A UE in a second state may be configured to monitor DCI on a second set of control channels. Such second set may provide scheduling for up to a second user plane data rate. The UE may be configured to determine such set as a function of one or more aspects related to the UE's transmissions, such as those further described below.

[0201] The UE is further configured to operate on a first sub-band and a second sub-band (or set thereof) of the operating frequency band when in the first and second states, respectively. A possible advantage of such operation in terms of power consumption may be that the receiver may utilize at least one of a reduced Fast Fourier Transform "FFT" size for control channel decoding and a front end tuned to (e.g., tuned only to) a sub-band of the entire frequency band.

[0202] FIG. 5A is a representative diagram illustrating control channels monitored by a UE in activity state A (shown at 511) and activity state B (shown at 512), respectively. As shown at 511, a UE in activity state A may be configured to monitor a certain number of control channel elements, e.g., CCE1-CCE7 (531-537) on the operating system bandwidth 521. These control channel elements, e.g., CCE1-CCE7 (531-537), represent an active control channel 522 for the UE. The UE may be configured to be in activity state B at other times. However, in a different activity state, e.g., activity state B, the UE may be configured to monitor all of the control channel elements, e.g., CCE1-CCEn (541-5xy), which represent an active control channel 523 on the operating system bandwidth 521, as shown at 512.

[0203] 5B illustrates an exemplary monitoring cycle including control channel monitoring behavior on a UE. The UE may be configured to monitor the control channel during active state duration 504 and not monitor the control channel at other times. The active state duration 504 is configurable, subject to the UE activity state and transmitted via RRC signaling.

[0204] Reducing the number of blind decodings

[0205] In another embodiment, the UE may be configured to perform up to a first number of blind decoding attempts in a first state. In a second state, the UE may be configured to perform up to a second number of blind decoding attempts. The determination of the UE's state may be based on an associated set of control channel resources. For example, for the first and second states, respectively, the UE may be configured to process a first number of search spaces (or a first subset of the search spaces) and a second number of search spaces (or a second subset of the search spaces), a first set of search spaces and a second set of search spaces, a search space aggregation level, or the like. The search space may be equal to that of legacy LTE, or more generally, any collection of control channel resources that the UE uses to perform blind decoding for downlink control channel messages. In NR, such a search space may be defined in time, frequency, and / or space when beamforming is applicable to the control channel.

[0206] For example, a possible advantage of dynamically varying a UE's blind decoding complexity may be that it allows UEs that are to be scheduled by the network less frequently (or have less critical scheduling time requirements) to reduce power consumption associated with blind decoding during periods of time while increasing power under control of the network scheduler during times when the UE may, can, and / or needs to be actively scheduled and / or during periods of higher scheduling load in a system where scheduler flexibility can be maintained.

[0207] Thus, states in which the UE performs decoding of fewer control channel resources may be more suitable for periods of low scheduling activity and / or for periods of scheduling activity associated with best effort, delay tolerant services. States in which the UE is required and / or used to decode a larger number of control channels may be states of greater scheduling flexibility.

[0208] 6A is a representative diagram of a search space for a UE in a representative activity state A. The UE may be configured to search a space with several control channel elements while in activity state A. For example, the UE may be configured to have a search space consisting of the first three aggregation levels 8 (e.g., 611-613), where aggregation level 8 includes eight control channel elements. The UE may be configured to have another search space with the first two aggregation levels 4 (e.g., 621 and 622), where aggregation level 4 includes four control channel elements. The UE may be configured to have another search space with the fourth through ninth aggregation levels 2 (e.g., 631-36), where aggregation level 2 includes two control channel elements, or the UE may be configured to have the twelfth through twenty-first aggregation levels 1 (e.g., 641-650), where aggregation level 1 includes one control channel element.

[0209] FIG. 6B is a representative diagram of a search space for a UE in activity state B. However, the UE may be configured to minimally search a space with a different number of control channel elements in activity state B in a different manner than in FIG. 6A. For example, the UE may be configured to have a search space with a third aggregation level 8 (e.g., 651). The UE may be configured to have another search space with a second aggregation level 4 (e.g., 661). The UE may be configured to have another search space with a seventh through ninth aggregation levels 2 (e.g., 671-673) or another search space with a fifth through twenty-first aggregation level 1 (e.g., 681-687).

[0210] The UE monitors a control channel with a varying number of control channel messages.

[0211] In another embodiment, as part of the UE power saving mode, the UE may be configured to search for a different number of control channel messages depending on its operating mode, and may be configured to autonomously change operating modes.

[0212] A UE may be configured or expected to monitor control channels with different numbers of possible control channel messages that may be received by the UE. For example, a UE may be configured to operate in different complexity states, in which the UE may monitor control channels with different numbers of control channel messages that are receivable. For example, a UE may be configured to execute a power saving mode that varies the number of distinct control channel messages that the UE may need, be able to, and / or must monitor based on factors such as one or more of scheduling activity, UE buffer status, and eNode-B scheduling flexibility requirements.

[0213] The UE may be configured to perform control channel monitoring by considering multiple states and have a different number of control channel messages (e.g., each having a different number of control channel messages) decoded in a state (e.g., each state). In a state (e.g., each state), the UE may be configured to be required and / or used to decode a different number of control channel messages. This may include at least one of a different number of DCI messages used as part of the decoding, different distinct DCI message sizes, a different number of cyclic redundancy check (CRC) patterns to use, and a different number of matching sequences, such as correlation sequences.

[0214] For example, a mode of operation associated with low power (e.g., a smaller number of DCI message sizes compared to other modes) may be associated with control channel messages that enable UE operations such as, but not limited to, paging, power control, system information, low latency data transmission, initial data transmission, etc.

[0215] The benefit of reducing the number of separate control channel messages may be improved performance of less blind decoding for the UE to conserve power during these time instances. A state in which the UE performs less control channel decoding may be a lower power state, while a state in which the UE is required and / or used to decode a larger number of control channels would be a greater scheduling flexibility state.

[0216] Transitions between states

[0217] In one embodiment, the decision of when to transition between two activity states may use behavior similar to the legacy LTE DRX active time.

[0218] In another embodiment, the power saving mode in the UE may be based on a transition by the UE between different states. The UE may be configured to transition between two control channel monitoring states based on a trigger. For example, the UE may be configured to move from a first activity state to a second activity state, which states may have different decoding complexities. The UE may be further configured to evaluate such a trigger periodically, such as every TTI, every N subframes, or with some configured periodicity.

[0219] For example, such transitions between states may be based on one or more of the following triggers: 1) scheduling strength, 2) resources or messages used for scheduling, 3) time triggers, 4) request by the UE, 5) presence or absence of a reference signal, and 6) explicit indication by the eNode-B.

[0220] 1) Scheduling Intensity

[0221] The UE may be configured to move from one control channel monitoring state to another as a result of the number of grants received in a given state and measured over a time window or at a particular time, and based on some rules for the transition related to this number of grants. These rules may take different forms or a combination of the following:

[0222] In one embodiment, the rule may be based on the number of grants received within a period T.

[0223] In a second embodiment, the rule may be based on the number of consecutive grants received, for example, the UE may be configured to move from the low power state to a state with greater scheduling flexibility upon reception of N consecutive grants while in the low power state, or upon reception of N grants received during a time period T while in the low power state.

[0224] In a third embodiment, the rule may be based on the number of consecutive control channel opportunities in which the UE was scheduled or in which the UE was not scheduled. For example, the UE may be configured to move from a state with a higher control channel monitoring complexity to a lower power state after N subframes in which the UE was not scheduled on the control channel.

[0225] In a fourth embodiment, the rules may be based on the type of control channel message sent while in a state. For example, the UE may be configured to move from one state to another upon receiving a particular DCI message type, or upon receiving a control channel message within a particular search space or with a particular aggregation level. Thus, such DCI message types or search space usages, etc., may be reserved for implicitly signaling state changes.

[0226] In a fifth embodiment, the rules may be based on a beam or set of beams for which the UE receives a message while in a state. For example, the UE may be configured to move from one state to another upon receiving a DCI message, e.g., while using a particular subset of monitored beams.

[0227] 2) Resources or messages used for scheduling

[0228] The UE may be configured to transition between states upon reception of N consecutive grants that use a particular search space, search space size, or a particular DCI message.

[0229] 3) Time trigger

[0230] The UE may be configured to transition between states at specific time instances (e.g., at a specific subframe, or frame number) that may be known by the UE or configured by the network. For example, the UE may be configured to always transition between one mode and another mode periodically at a specific frame / subframe number. In another example, the UE may be configured to operate in one mode for a period of time (based on a timer) and transition to another mode upon expiration of the timer.

[0231] 4) Request by UE

[0232] The UE may request to move between states by issuing a request using an SR, a Buffer Status Report (BSR), a MAC CE, or an RRC message.

[0233] The UE may trigger a request to move between the two states as a result of at least one of the following:

[0234] - Activation or termination of a new service in the UE. For example, a UE with an active eMTC service operating in low power mode may request to move out of low power mode upon activation of an eMBB service;

[0235] - the arrival of data associated with a particular service, logical channel, or flow;

[0236] - a determination by the UE that data to be transmitted is time critical or may not meet time requirements without moving out of a low power mode;

[0237] - the buffer status of one or more logical channels or flows at the UE exceeds a certain threshold;

[0238] - the time-criticality (e.g., validity period) of data in the UE buffer or ongoing transmission at the UE falls below a threshold (e.g., the UE has completed transmission of any or most of the time data (e.g., time-critical data) in its buffer); and

[0239] - A beam management process or event (e.g., beam failure detection at the UE). This beam management process or event may include a determination by the UE that a radio link quality associated with a set of beams falls below a certain threshold. For example, the UE may determine such radio link quality based on one or more measurements for reference signals associated with the set of beams.

[0240] The UE may be configured to implicitly indicate its desire to move between states by sending information in an SR (e.g., by transmission on the PRACH and / or on the Physical Uplink Control Channel (PUCCH)), a BSR, a MAC CE, and / or an RRC message (e.g., using transmission on the PUSCH). For example, the UE may assume that sending a BSR with information that a buffer status or timing requirement for data in a particular logical channel is above a threshold will move the UE from or to a low power mode.

[0241] 5) The presence or absence of a reference signal

[0242] The UE may be configured to determine that the UE may need, be able to, and / or need to monitor a subband of the control channel space as a result of a lack of reference signals in other parts of the band. For example, the operating band may be divided into several subbands in which a set of reference signals may be transmitted. If the UE detects that the reference signal power in a particular subband is below a threshold, the UE may be configured to ignore decoding of the control channel for that particular subband and decode the control channel on (e.g., only on) subbands whose reference signal power is above the threshold.

[0243] 6) Explicit instruction by eNode-B

[0244] The UE may be configured to move between different states if the DCI indicates so explicitly or implicitly. For example, the UE may be configured to move from a low power state to a normal state or from a low power state to another low power state (with higher complexity) if the DCI indicates a grant for resources located outside the reduced bandwidth defined by the initial low power state in which the UE is received.

[0245] The UE may be configured to move between states upon receipt of a MAC Control Element (MAC CE) or RRC configuration message.

[0246] The UE may be configured to determine a set of states and / or resources (control and / or data) as a function of at least one of the following:

[0247] One function would be an average transmission rate over a period of time. Such a rate may correspond to an L1 transmission rate, to an L2 transmission rate, to a user plane data transmission rate or similar. Such a rate may be based on successful transmissions during such a period. Such a rate may be based on successful transmissions for which positive HARQ feedback was received (in the case of downlink scheduling) or transmitted (in the case of uplink scheduling) or both (in the case of combined scheduling). As there is a configured offset or threshold, the threshold may be used to vary the scheduling flexibility.

[0248] Another function would be the average inter-packet transmission (uplink or downlink or both). Such transmission may follow the description above.

[0249] Another function could be a rate control algorithm, such as a multiplicative increase / subtractive decrease type algorithm. For example, TCP-like rate control could be applied to determine (e.g., activity) states for control channel processing (and, e.g., data channel processing), where management of a TCP "window" corresponds to a minimum processing requirement for the UE, and such window is, however, increased in a multiplicative manner (as opposed to TCP rate control) and decreased in a subtractive manner. For example, successful detection (or number within a given period) of a DCI would correspond to receipt of a TCP ACK for window management (multiplicative increase), while a period without such detection (or a number less than a certain value within a given period) would correspond to a TCP NACK (subtractive decrease). This could be averaged using a window to minimize rate fluctuations. One advantage of such a method could be that UE processing activity could be matched to the observed transmission rate of a given UE. Such methods may be applied separately to the uplink (e.g., in the case of resources associated with an uplink data channel, e.g., only an uplink data channel), the downlink (e.g., in the case of resources associated with a downlink control and / or data channel only), or a combination to both (if not).

[0250] One advantage of having the UE autonomously modify the control channel configuration may be to allow the UE to transition between one activity state and another with reduced signaling overhead from the network, allowing transitions to occur more frequently without overhead, and therefore improving power efficiency gains with such transitions.

[0251] In one embodiment, the UE may be configured to decode one set of search spaces (potentially the full set) in normal mode and a second set of search spaces (potentially the reduced set) in low complexity mode. The set of search spaces to be decoded in a mode (e.g., each mode) may be known a priori by the UE or may be provided by configuration from the network. The configuration from the network may further be provided as an index (one for normal mode and one for low complexity mode) to a known or standardized search space configuration. In the low complexity mode, the reduced set of search spaces may be further restricted to a reduced set of CCEs, resources, beams, and / or control channel bandwidth, for example, such that the UE may process a reduced (e.g., only reduced) set of resources. The UE may be configured to receive a MAC CE indicating that the UE should move from one mode of decoding to another mode. Upon successful reception of the MAC CE, the UE begins performing control channel decoding in the new mode at the next control channel instance (e.g., the next subframe) or at a particular known instance (e.g., subframe 0, or x subframes following reception of the MAC CE).

[0252] In another exemplary embodiment, the UE may be configured to have two different control channel decoding modes, where the first mode requires decoding of a small set of DCI formats and the second mode requires decoding of the full set of supported DCI formats. The UE operating in the first mode may be configured to transition to the second mode upon receiving a scheduling request in N consecutive control channel occasions / TTIs / subframes or the like. Alternatively, the UE operating in the first mode may be configured to transition to the second mode upon receiving N DCI messages of a particular type (supported in the first mode) within the last T subframes, where N and T are configurable by the network. In the second mode of operation, the UE may be configured to transition to the first mode of operation after expiration of a timer that was set when the second mode was entered. The timer may be further reset (e.g., each time) the UE receives a scheduling request.

[0253] In another representative embodiment, the UE may be configured to follow any of the rules associated with the previous exemplary embodiment and may be further configured to transition temporarily (e.g., for one or several subframes / TTIs / scheduling occasions) to the second mode of operation periodically once every T subframes at a time instance known by both the UE and the network (e.g., the UE may be configured by the network). An advantage of such a periodic fallback may be to ensure that the UE and the network remain synchronized with respect to the transition between the modes of operation. The UE may further receive a message from the network while in the subframe where it falls back to the second mode of operation to resynchronize itself with the network, which would consist of resetting all timers, counters, and state variables related to the transition between the two modes.

[0254] Although the above exemplary embodiment is shown for two states, one skilled in the art will appreciate that the examples and rules for transitions are possible for more than two control channel monitoring states.

[0255] UE L2 processing complexity

[0256] HARQ Configuration

[0257] In one embodiment, as part of a UE power saving mode, the UE may be configured to autonomously change its HARQ configuration and inform the network of such.

[0258] The current activity state of the UE may define the HARQ configuration under which the UE operates. The UE may be configured to autonomously change its HARQ configuration based on certain triggers occurring at the UE. The HARQ configuration may define values, rules, or configurations of the following properties or parameters related to HARQ:

[0259] 1) Number of HARQ processes for DL, UL, SL. For example, in activity states associated with lower UE processing complexity, the UE may be configured with fewer HARQ processes. One advantage may be that it may enable memory savings in the UE, such that buffering may be dynamically adjusted based on the UE activity.

[0260] 2) Applicable transmission modes. For example, in a first state and in a second state, the UE may be configured to use configurations associated with the first and second transmission modes, respectively. This may be useful to enable less processing-intensive physical layer processing during periods of lower activity.

[0261] 3) Mapping of logical channels to HARQ processes: For example, in a particular activity state, there may be specific rules that are followed to associate one or more logical channels with a particular HARQ process.

[0262] 4) Timing of HARQ operations, such as grants to transmission timing or timing of retransmissions.

[0263] 5) Whether autonomous or scheduled retransmission is to be used.

[0264] 6) the maximum number of HARQ retransmissions, and

[0265] 7) Configuring a redundancy version for HARQ transmissions / retransmissions (e.g., each HARQ transmission / retransmission).

[0266] In another embodiment, the power saving mode may depend on the UE state, the UE state transition, or both, with the state (e.g., each state) having a particular set of HARQ parameters or HARQ configuration. The UE may be configured to transition between HARQ configuration states based on a trigger. The UE may be further configured to evaluate such triggers periodically, such as every TTI, every N subframes, or with some configured periodicity. The transition between states may be based on one or more of the following triggers described herein, for example, in the "Control Channel Decoding Complexity" section:

[0267] Additional possible transitions include receiving high priority or low latency data. For example, the UE may be configured to receive a packet or PDU that contains or includes a higher priority than any current priority of data that the UE is currently transmitting. As another example, the UE may be configured to receive a packet or PDU that has timing requirements or TTLs associated with the packet that may use or require a different HARQ configuration.

[0268] Rules for transitioning between HARQ processing states may be further defined based on at least one of the number of such packets received over a configurable amount of time, the size of the received packets, and a priority level or latency level associated with the packets.

[0269] With respect to priority levels or latency levels associated with packets, low latency data may, for example, be associated with different levels of latency (e.g., required latency) (e.g., L1, L2, ...) having decreasing latency requirements, which may comprise data from higher layers.

[0270] Concatenation, segmentation, multiplexing, and / or retransmission

[0271] In another embodiment, as part of a UE power saving mode, the UE may autonomously change its configuration of L2 segmentation, concatenation, and retransmissions and inform the network of such.

[0272] The activity states of a UE may define the behavior of the UE when performing concatenation, segmentation, and multiplexing of logical channels onto transport blocks. A UE may be configured to transition from one activity state to another, and the activity states can be characterized by different values ​​of definitions for the following parameters:

[0273] 1) minimum or maximum segment size for segmentation and / or resegmentation;

[0274] 2) whether segmentation should be performed and, if so, on which logical channels. For example, the UE may be configured to perform segmentation on all logical channels in one activity state, but not perform segmentation in another activity state, and to perform segmentation (e.g., only segmentation) on logical channels of a particular type in another activity state;

[0275] 3) Whether concatenation should be performed, and if so, on which logical channels. For example, the UE may be configured to perform concatenation on all logical channels in one activity state, but not on another, and to perform concatenation (e.g., only concatenation) on logical channels of a particular type in another activity state;

[0276] 4) The size of the window in TX or RX used for ARQ operations, reorganization, retransmissions, or similar operations for all logical channels or for a particular set of logical channels;

[0277] 5) whether segment retransmissions should be performed or whether upper layer retransmissions of complete PDUs (e.g., only upper layer retransmissions) are performed; and

[0278] 6) Whether resegmentation is performed for the retransmission or whether the retransmission requires transmission of the same segment and / or uses it as the initial transmission.

[0279] In a representative embodiment of the UE L2 processing complexity, the UE may be configured in a first mode with an HARQ configuration consisting of N1 parallel HARQ processes and x1 subframes between data transmission and ACK. At the start of a service that uses or requires low latency, the UE may be configured to receive from the upper layer a packet indicating (e.g., that it is necessary to do so) that it transmits data with low latency. If the number of such packets received by the UE from the upper layer within a configurable time T exceeds a certain threshold, the UE may be configured to move to a second mode of operation.

[0280] The UE may be configured to further inform the network about the transition by transmitting a MAC CE (such as a BSR or the like). The UE may be configured to operate in a second mode consisting of or including N2 parallel HARQ processes (where N2 > N1) and x2 subframes between data transmission and ACK (where x2 < x1). The UE may be configured to remain in the second mode while packets of the low latency service are being received. When the number of packets associated with low latency received over a similar time interval T falls below the threshold, the UE may transition to the first mode and may similarly be configured to inform the network about such a thing.

[0281] Data bandwidth configuration

[0282] Modification of data bandwidth configuration

[0283] In an embodiment of the modification of the data bandwidth configuration, as part of the UE power saving mode, the UE may be configured to have different sets of operating bandwidths according to its processing state and may be configured to autonomously change the processing state.

[0284] The set of triggers for the processing state change disclosed herein that determines control channel processing is applicable to the data channel and the data bandwidth configuration.

[0285] The activity state of the UE may be defined with respect to its operating data bandwidth. In one solution, the UE may be configured to operate on different data bandwidths and dynamically change its operating data bandwidth during operation. The UE may further operate under different data bandwidth configurations for UL and DL. For example, the UE may be configured to have an operating bandwidth B1 on carrier C (the overall system BW for this carrier is B > B1). At a certain time, the UE may change its operating bandwidth from B1 to B2 (B1 < B2 < B) and be reconfigured to enable the UE to be scheduled with a large amount of resources. The reconfiguration may consist of, or include, the addition of resource blocks to the overall bandwidth (BW) that the UE is schedulable for data and / or available for UL transmission. It may consist of, or include, the UE processing the entire B2 including the additional resource blocks.

[0286] The UE may be configured to further change the frequency position of the data bandwidth as a result of the bandwidth configuration. For example, the UE may be configured to move the center frequency of its operating bandwidth from one position to another, potentially based on a trigger related to the channel quality of a particular resource, in addition to power consumption considerations. The UE may be configured to further change the available time resources for DL reception and UL transmission based on a certain trigger.

[0287] The UE may be further configured to make such dynamic changes during its operation in such a bandwidth configuration to adapt to the instantaneous scheduling load (uplink or downlink) for that particular UE. The UE may be configured to make such changes in response to specific triggers related to scheduling, load, etc., as will be described in more detail below.

[0288] An advantage of such dynamic data bandwidth configuration change may be that a UE configured with a smaller bandwidth may configure its reception, data processing, measurements, etc., such that it is limited to that segment. For example, a change in bandwidth configuration may result in a retuning by the UE. The UE may be configured to use front-end, FFT / IFFT, or baseband processing that is limited to the segment. For example, a UE configured with bandwidth B1 may receive a data channel utilizing an FFT size F1. When configured with bandwidth B2>B1, the UE may receive a data channel utilizing an FFT size F2>F1. Such a configuration may enable power saving advantages when the load requirements of the UE are not sufficient to ensure that the UE's receiving circuitry / HW / SW operates over the entire BW of a given carrier.

[0289] Identifying UE operating bandwidth by indexing

[0290] In another embodiment of identifying the UE operating bandwidth by indexing, the bandwidth or segment (including resource blocks and their configuration) may be predefined or based on system information broadcasted by the cell. The UE may be configured to receive a set of indices corresponding to one of the possible segments or bandwidths that may be utilized as the UE-specific BW configured for a given time, and the reference made to that segment by the network is based on the corresponding index. Such indexing may be sent by the network to the UE during configuration or may be signaled by the UE to inform the network in case of a UE autonomous change in the UE operating bandwidth.

[0291] Addressable / Allocatable PRB Fixes

[0292] In another embodiment of modifying addressable / allocable PRBs, as part of a UE power saving mode, the UE may be configurable to have different sets of addressable / allocable PRBs within its system bandwidth depending on its operating mode and may autonomously change the operating mode.

[0293] The activity state of a UE may be characterized by the addressable PRBs that are available to the UE in the UL or that are schedulable by the network for that particular UE in the DL. In another solution, the UE may be configured to change its set of addressable PRBs in the UL or DL. The UE may be further configured to make such changes in the set of addressable PRBs based on the scheduling load, the data to be transmitted, the operating characteristics, and other characteristics specific to that UE. In doing so, the UE may be configured to obtain power savings associated with simplified control channel decoding since the addressable space required and / or used for the control channel is limited to the data used by the UE (e.g., data only) and / or the needs of the UE. When modifying the set of addressable PRBs, the UE may be configured to continue to operate over the same data bandwidth and may consider (e.g., only consider) certain PRBs as being eligible to be addressable by the control channel.

[0294] The state transition and / or addressable / allocable PRB modification may consist of and / or include adding or deleting one or more PRBs to the number of addressable / allocable PRBs for the UE. Alternatively, the state transition and / or addressable / allocable PRB modification may consist of and / or include changing from one predefined PRB configuration to another PRB configuration. The PRB configuration may consist of and / or include at least one of: 1) a particular set of PRBs, 2) a size of the PRBs (e.g., each of the PRBs) in the set, 3) allowable modulation and coding schemes (MCSs) that are available on the PRBs (e.g., within each PRB), 4) TTIs and / or numerologies that are available within the particular PRBs, 5) allowable logical channels or services that can be used on the particular PRBs in the PRB set, and 6) a set of beams that receive the set of addressable PRBs.

[0295] Excluded PRBs in the Data Channel Configuration

[0296] The UE may be configured to receive from the network a set of PRBs or data blocks that are not available in the UE's data channel configuration. For example, the UE may be configured to exclude such PRBs in its data channel configuration. Moreover, the frequency location of such excluded data blocks may vary over time based on some predefined or configured hopping pattern.

[0297] Frequency hopping operation

[0298] The UE may be configured to determine its data block location (e.g., a resource block within a frequency band, which may be up to a particular data block) based on a frequency hopping rule, which may include a UE ID and at least one of a frame number or a subframe number.

[0299] In this way, a particular block of data may occupy a different portion of the bandwidth at a particular time.

[0300] 7A-7C are representative block diagrams of a UE with different numbers of addressable PRBs in the system bandwidth during different time periods. In FIG. 7A-7C, there are two reserved PRBs, e.g., 713, 723, and 733.

[0301] 7A is a representative diagram showing a portion of bandwidth reserved for a UE during time period T1 (e.g., 701). In this embodiment, FIG. 7A illustrates that the UE may be identified in activity state A, and there are no addressable PRBs during time period T1.

[0302] 7B is another representative diagram illustrating another portion of the bandwidth reserved for the UE during another time period T2 (e.g., 702). In some embodiments, FIG. 7B illustrates that the UE may be identified in activity state B and configured to transition to activity state B from activity state A. In activity state B, there are three addressable PRBs (e.g., 720-722) for which the UE is configured to decode the three PRBs during time period T2 (e.g., 702).

[0303] 7C is another representative diagram illustrating another portion of the bandwidth reserved for the UE during another time period T3 (e.g., 703). In some embodiments, FIG. 7C illustrates that the UE may be identified in activity state C and may be configured to transition to activity state C from activity state B. In activity state C, there are seven addressable PRBs (e.g., 730-736) such that the UE is configured to decode the seven PRBs during time period T3 (e.g., 703).

[0304] Transition between states for data channel configuration

[0305] In another embodiment of transitioning between states for a data channel configuration, the power saving mode at the UE may be based on transitioning between different states by the UE that are associated with (e.g., each associated with) a particular data bandwidth configuration. The UE may be configured to transition between data bandwidth configuration states based on a trigger.

[0306] The UE may further evaluate such triggers periodically, such as every TTI, every N subframes, or with some configured periodicity. The time period for evaluation may be defined as a number of subframes in the past starting from the current subframe, and such evaluation may be performed by the UE continuously, for each subframe, or over distinctly configured subframes.

[0307] Such transitions between states may be based on one or more, or a combination of, the following triggers:

[0308] 1) Scheduling Intensity

[0309] The UE may be configured to move between one data channel configuration and another based on the amount of resources scheduled by the network. The rules for transitioning between one control channel configuration and another control channel configuration may be based on the following: The rules for transitioning may be based on the amount of resources scheduled over a recent period of time T.

[0310] For example, the UE receives a resource allocation having a size larger than a certain threshold, or the amount of resources allocated over a defined period of time is greater than a threshold. Such a threshold may be defined by the number and / or size of data regions currently configured in the UE. For example, the threshold of resources allocated to move from a x1 resource block to a x2 resource block increases as the amount x2 increases.

[0311] In another example, if a UE is scheduled with a total amount of resources above / below a certain threshold, the UE may be configured to reconfigure its data channel to increase / decrease the number of PRBs.

[0312] The UE may be configured to move between one data channel configuration and another when the UE receives a single resource allocation (UL or DL). For example, the UE may be configured to initially operate over a single minimalistic number of PRBs and move to operation with a larger number of PRBs in that data configuration immediately after receiving a resource allocation.

[0313] The UE may be configured to move between one data channel configuration and another based on the amount of scheduling on the control channel. The triggers may be the same or similar to those described herein related to control channel scheduling.

[0314] The UE may be configured to move between one data channel configuration and another data channel configuration based on a combination of the rules given above, for example, when the number of allocations (e.g., having a resource size greater than a first threshold) received by the UE over a particular time period exceeds a second threshold.

[0315] 2) the quality of one of the PRBs or a particular set of PRBs

[0316] The UE may be configured to move between one data channel configuration and another based on measurements made by the UE on the same or other PRBs. For example, the UE may be configured to move from one data channel configuration to another when a measurement or a reported measurement associated with a particular PRB is above / below a threshold (e.g., to add / remove a PRB from a list of configured PRBs).

[0317] The UE may be configured to move between one data channel configuration and another based on HARQ processing results associated with transmissions on one of the PRBs or a set of PRBs, for example, the UE may be configured to increase / decrease the amount of PRBs in its configuration or increase / decrease its system bandwidth based on the HARQ success rate on one of the PRBs or a set of PRBs.

[0318] In another example, the UE may be configured to remove a particular PRB or set of PRBs from its configuration if the number of HARQ failures associated with transmission of a transport block on that PRB or set of PRBs exceeds a particular failure rate.

[0319] 3) RLC / PDCP / upper L2 error rate, retransmission rate, and / or discards

[0320] The UE may be configured to move between one data channel configuration and another based on an overall upper L2 error rate or retransmission rate over a configurable period of time. For example, a number of consecutive RLC / PDCP retransmissions or a set of errors exceeding a certain threshold may result in a configuration change that increases the overall number of PRBs.

[0321] The UE may be further configured to trigger such a change (increase or decrease) based on, for example, receipt of a status report in an associated layer (eg, RLC or PDCP).

[0322] The UE may be configured to move between one data channel configuration and another data channel configuration based on detection of a discard of another PDU (e.g., a PDCP discard) and / or based on a period of time without discards.

[0323] 4) Time trigger

[0324] The UE may be configured to transition between states at specific moments (e.g., at a specific subframe and / or frame number) that may be known by the UE or configured by the network. For example, the UE may be configured to always transition between one mode and another mode periodically at a specific frame / subframe number. As another example, the UE may be configured to operate in one mode for a period of time (based on a timer) and transition to another mode upon expiration of the timer.

[0325] 5) Request by UE

[0326] The UE may be configured to request to move between states by issuing a request using an SR, a Buffer Status Report (BSR), a MAC CE, or an RRC message.

[0327] The UE may be configured to trigger a request to move between the two states as a result of at least one of the following:

[0328] - Activation or termination of a new service in the UE. For example, a UE with an active eMTC service operating in low power mode may request to move out of low power mode upon activation of an eMBB service;

[0329] - the arrival of data associated with a particular service, logical channel, or flow;

[0330] - a determination by the UE that data to be transmitted is time critical or may not meet time requirements without moving out of a low power mode;

[0331] - the buffer status of one or more logical channels or flows at the UE exceeds a certain threshold;

[0332] - the time-criticality (e.g., validity period) of data in the UE buffer or ongoing transmissions at the UE falls below a threshold (e.g., the UE has completed transmission of any or most of the time-critical data in its buffer); and

[0333] - Upon reception of a packet with high priority or low latency requirements at the UE.

[0334] The UE may also be configured to implicitly indicate its desire to move between states by sending information in an SR, BSR, MAC CE, or RRC message.

[0335] For example, the UE may assume that sending a BSR with information that the buffer status or timing requirements for data in a particular logical channel exceed a threshold will result in a change in the data channel configuration.

[0336] The UE may be configured to determine such rules on a per logical channel basis, for example, the UE may be configured to increase the number of data blocks applicable to logical channels of a particular category based on the overall buffer status for those logical channels having a BSR above a threshold.

[0337] 6) Presence or absence of a reference signal

[0338] The UE may be configured to determine that the UE should change its data bandwidth configuration as a result of the presence or absence of a reference signal in a particular PRB or set of PRBs. For example, the operating band may be divided into several subbands within which a set of reference signals may be transmitted. If the UE detects that the reference signal power in a particular subband falls below a threshold, the UE may be configured to change its data channel configuration accordingly.

[0339] 7) Explicit instruction by eNode-B

[0340] The UE may be configured to move between data channel configurations based on explicit instructions by the eNode-B (RRC, MAC CE, or signaling in the control channel).

[0341] For example, such messaging by the network may include the new data channel configuration, potentially signaled with an index into the detailed control channel configuration.

[0342] In another example, the UE may be configured to receive the data channel configuration (e.g., the required data channel configuration) in the control channel itself, either explicitly (using an index) or implicitly (based on the DCI format detected by the UE).

[0343] 8) Movement between UE states or during mobility events

[0344] The UE may include, but is not limited to,

[0345] - following a handover or UE autonomous mobility event,

[0346] - When moving from one TRP to another, and / or

[0347] - when initiating a connection to the network, such as moving to RRC connected, or moving between a Lightly Connected state and an RRC Connected state; The UE may be configured to move between data channel configurations upon separate UE state transitions and / or mobility events, such as:

[0348] Timing for Transitions Between States for Data Channel Configuration

[0349] In another embodiment of the timing for transitions between states for the data channel configuration, the UE may be further configured to change the data channel configuration at specific time instances or boundaries. Such boundaries may be defined in terms of frame numbers or subframe numbers, such as (frame number mod x=y). Parameters for such boundaries may be statically defined for a particular UE or may be signaled by the network, for example based on a UE identifier. The UE may be further configured to determine triggers for increasing / decreasing the number of data blocks utilized at these specific time boundaries and may perform associated calculations for the conditions for increase / decrease based on information since the previous boundary.

[0350] In an exemplary embodiment of the data bandwidth configuration, the UE may be configured to operate over a subset of data blocks, where the data blocks (e.g., each data block) may contain and / or include several resource blocks that are allocable to the UE. The data blocks may potentially be fully self-sufficient, since they may consist of and / or include a separate control channel that scheduled data resources on the data block. Alternatively, a separate control channel may be assumed for the set of configured data blocks. For example, the system bandwidth may be divided into several data blocks that are non-overlapping and cover the entire system bandwidth (e.g., a system with a bandwidth of 80 MHz may be divided into 8 separate data blocks of 10 MHz each). The UE may further be configured to utilize a subset (e.g., only a subset) of the system's data blocks, whether contiguous or non-contiguous, e.g., over a finite period of time.

[0351] A data block may be further associated with the use of a particular type of service or logical channel or a set of services / logical channels. The UE may assume and / or determine that the UE may use a particular data block if the UE is configured to have a particular service (e.g., only in that case).

[0352] The UE may be further configured to determine the amount of data blocks configured to be used by the UE at periodic opportunities and / or time instances that may be configured by the network. During the power saving mode of the UE, the UE may be configured to determine the data block configuration from one of the indexed sets of data block configurations provided by the network. At periodic opportunities defined by a period P (e.g., some or each of the periodic opportunities), the UE may be configured to send the desired data block configuration to the network, such as within a MAC CE, e.g., within a BSR, along with other data related to the buffer status of the UE.

[0353] The UE may be configured to determine the data block configuration as follows. Based on the set of possible data block configurations, select a configuration in which the total number of PRBs for the UE is included in the range thesh1*X < #PRB < thresh2*X, where thresh1 and thresh2 may be thresholds configured by the network and / or X may be the total number of PRBs allocated to the UE over the previous n*P periodic opportunities. And / or the UE may be configured to select a set of data block configurations that satisfy the above conditions as the data block configuration with the best measurement value determined by the UE.

[0354] In another exemplary embodiment, a minimalist-sized data block (fewer resource blocks) may be configured for a relatively inactive UE. Such a data block may be common to the UE (e.g., all UEs), or the data block may be unique to one or a few UEs.

[0355] The UE may be configured to determine its basic data block based on the UE's identity, which may be network-assigned or self-assigned by the UE. For example, the UE may be configured to determine the frequency location of its basic block based on the UE identity. Such a basic data block may be used, for example, by a UE that does not have an active connection with the network and thus does not have a data channel configuration for active data communication.

[0356] In another example embodiment, the UE may be configured to determine the active PRBs in its data configuration using one or a combination of the following methods:

[0357] The UE may be configured to move from one PRB configuration to another as a function of the data buffer size reported in the BSR. The UE may be configured to calculate the number of PRBs to be activated for a number of the total buffer sizes reported in the BSR, which number may be configured by the UE. The UE may be configured to perform a PRB configuration decision when or every time the BSR is triggered, or based on a certain trigger of the BSR (e.g., only a certain trigger).

[0358] The UE may further assume that a fixed, predefined data channel configuration (e.g., all PRBs are configured or a statically defined data channel configuration is used) occurs on certain subframes, and that this occurs periodically (e.g., for one subframe out of every N radio frames).

[0359] In another example embodiment, the UE may be configured to determine its data bandwidth using one or a combination of the following methods:

[0360] The UE may be configured with an initial data bandwidth configuration, which may include a center frequency (e.g., a location of the data bandwidth). Such an initial configuration may be initiated as a result of the UE connecting to the network;

[0361] - the UE may be configured to increase the data bandwidth by a fixed amount for a configurable time period during which there has been no detected PDCP discard (e.g., each configurable time period); if a PDCP discard is detected during the configurable time period, the UE may be configured to decrease its bandwidth by a fixed amount; and

[0362] The UE may be further configured to reduce its bandwidth to a starting data bandwidth if the amount of data allocated to the UE over a previous configurable time period falls below a threshold.

[0363] In another representative embodiment, the UE may be configured to add or remove a specific number of PRBs from a set of active PRBs, potentially also modifying the active data bandwidth of the UE as a result of the creation of a new logical channel. Upon initiation of a logical channel, the UE may be configured to add a specific set of PRBs to the active data channel configuration. Such PRBs may be predefined based on the configuration for the UE, as those specific PRBs may be associated with a particular logical channel or logical channel type.

[0364] Power-Efficient Signaling

[0365] Low Cost Signal

[0366] As part of the UE power save mode, the UE can be configured to monitor low-cost signals that may define behavior, parameters, and transitions between activity states of the UE.

[0367] The UE may be configured to monitor low-cost signals, which may change an activity state of the UE, change the behavior of the UE within the activity state, provide further information about parameters to be used in a particular activity state, or a combination of the above. One advantage of such a low-cost signal may be that it may be decoded by the UE in a power-efficient manner.

[0368] Low-cost signaling example

[0369] In one embodiment, the low-cost signal may constitute any simplified signaling from the network to the UE, which may use or require limited or small amount of decoding from the UE side, or may not use or require any decoding from the UE side. A low-cost signal may be a signal whose detection or decoding does not use or require a large amount of processing at the UE's receiver. The examples are provided to illustrate possible implementations, but such examples should not be limited to other examples of low-cost signals.

[0370] In one example, the UE may be configured to monitor low-cost signals in the time domain, which may enable the UE to detect the presence of the signal without (e.g., the need for and / or use of) performing FFT, decoding, etc. In this case, the low-cost signal may consist of or include a known time-domain sequence that is detectable by the UE using correlation followed by energy detection. The time-domain sequence may further be transmitted within a particular band or channel of the UE's operating bandwidth and / or the time-domain sequence may be transmitted at a particular time instance known by the UE, which may enable the UE to further reduce power consumption in monitoring for low-cost signals.

[0371] In another example, a low-cost signal may consist of or include one or more separate resource elements associated with the data or control space of a UE. Such low-cost signals may be UE-dedicated, cell-specific, TRP-specific, or associated with a group of UEs.

[0372] Another example of a low-cost signal may be a Random Access Channel (RACH) preamble transmitted by the eNode-B.

[0373] In some embodiments, the low-cost signal may be a synchronization signal transmitted by the network, such as a special form of a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS) and / or a synchronization signal block (SS-block).

[0374] Depending on its format, one advantage of the low-cost signal may be that the UE may do one of the following while monitoring the low-cost signal: turn off all baseband (frequency domain) processing and / or perform monitoring of the signal or special sequence using a limited receiver bandwidth. For example, the UE may be configured to receive the low-cost signal over a defined bandwidth that may be smaller than the overall cell bandwidth or normal UE operating BW.

[0375] Possible behaviors defined by low-cost signals

[0376] The UE may be configured to perform one or a combination of the following actions upon detection of the low-cost signal.

[0377] 1) Start / Stop monitoring of one or more control channels

[0378] Reception of a low-cost signal by the UE may trigger or cancel monitoring of one or more control channels in the UE. For example, the UE may be configured to monitor for (e.g., potentially only for) low-cost signals, and upon detection of the low-cost signal, the UE may be configured to monitor one or more specific or signaled control channels. In another example, the UE may be configured to detect, during monitoring for a control channel, the presence of a low-cost signal that disables or stops monitoring of that control channel or other control channels in the UE.

[0379] The UE may be further configured to initiate monitoring of the control channel when the UE is currently in a particular activity state and the UE receives a low-cost signal, for example, the UE may be configured to receive a low-cost signal indicating the presence of additional UE-specific control information within one or more of the PRBs or within a set of CCEs within the currently configured data bandwidth while having a certain data configuration.

[0380] 2) Transitions between activity states in the UE

[0381] Receipt of the low-cost signal may cause the UE to transition from one activity state to another. For example, the UE may be configured to receive a low-cost signal that causes a change from one control channel monitoring state to another control channel monitoring state. In another example, the UE may be configured to receive a low-cost signal that causes a change from one data channel configuration to another data channel configuration.

[0382] 3) Change the activity state configuration

[0383] The UE may be configured to receive low-cost signals that modify a trigger condition, enable a trigger, or disable a trigger to move between states. For example, the low-cost signals may cause a scheduling-based trigger to change in the UE from one data channel configuration to another.

[0384] 4) Trigger the UE to update its activity state configuration or read it from another signal. For example, the UE may be configured to receive a low-cost signal indicating that activity state information has changed and that the UE should read such information from system information.

[0385] Configuration aspects related to low-cost signals

[0386] In some embodiments of configuration aspects related to low-cost signals, the UE may be configured with certain parameters related to decoding the low-cost signals. Such configuration may include:

[0387] - System information,

[0388] - Based on the system signature for the fixed cell, and

[0389] - fixed and based on a specific UE ID, UE group ID or cell ID; The information may be received or determined via any or a combination of:

[0390] The UE may be further configured to monitor low-cost signals of one or more particular activity states (e.g., only low-cost signals of one or more particular activity states), e.g., if such low-cost signals are used to trigger a transition out of that state.

[0391] The UE may be further configured to monitor low-cost signals of a subset of UE states (e.g., only low-cost signals of the subset of UE states), such as an idle state, a connected state, a lightly connected state, and / or a deep sleep (deep idle) state, that characterize different interactions with the network regarding whether, how much, and how data can be transmitted.

[0392] The UE may be further configured to monitor the low-cost signal upon activation of one or a particular type of service, logical channel, or similar feature.

[0393] In some embodiments, the configuration parameters may include at least one of the time and / or frequency resources in which the low-cost signals may be decoded or detected, the nature (e.g., index) used to generate the sequence, and signal characteristics described below. For example, the UE may be assigned at least one identifier (or group ID) and monitor low-cost signals in a particular resource (e.g., a set of physical resource blocks in a time symbol) associated with the identifier (e.g., each such identifier). The UE may determine an activity state as corresponding to the highest activity level among the activity states indicated by the at least one low-cost signal associated with the identifier (e.g., each identifier).

[0394] Information provided by low-cost sequencing

[0395] The low-cost sequence may provide additional information to the UE through the use of its signal characteristics, such as any or a combination of the following:

[0396] - duration of the sequence,

[0397] - the timing of the sequence (e.g. the subframe or frame in which the sequence is transmitted);

[0398] - a specific sequence to be transmitted if the UE is configured to monitor multiple sequences;

[0399] - time domain properties of sequences (e.g. ZC sequences);

[0400] - the frequency band or subband in which the sequence is transmitted,

[0401] - the beam along which the sequence is transmitted,

[0402] - as part of the payload to be decoded within the low-cost signal

[0403] - the resources occupied by the sequence, in frequency, in time, or both, and

[0404] - The subcarrier spacing used for the sequence.

[0405] The UE may be configured to determine at least one of the following information from the determination of the characteristics of the low-cost signal:

[0406] - the current DL timing of the cell, including, for example, frame number, subframe offset, start of scheduling period for D2D, start of sensing period for LBT;

[0407] - the time instances at which the UE should transition between activity states, or the length of time that the UE should remain in a particular activity state;

[0408] - A particular band, sub-band, or channel on which the UE should wake up, monitor a control channel, operate its data channel, etc. For example, the sequence may signal the UE to wake up on one particular sub-band or channel (e.g., only on one particular sub-band or channel), e.g., to further receive scheduling instructions;

[0409] - a particular beam or set of beams on which the UE may receive the control channel;

[0410] - configuration aspects related to the activity state in the UE, which may consist of or include the nature of the decoding to use on the control or data channels, which may include the particular set of control channel messages or search spaces that may be used to address the UE immediately after deep sleep, the particular resources or resource elements that will be used initially when addressing the UE, the beam angles, beam widths or beam sweep periods used for beamforming, and the decoding algorithms (convolutional, block, etc.), and

[0411] - A UE or set of UEs that are expected to be addressable if D2D communication should and / or is feasible.

[0412] In one embodiment, the UE may be configured with several low-cost signals to monitor. A sequence (e.g., each sequence) may be associated with a bandwidth in which the UE should or can wake up to operate upon detection of that sequence, as well as a set of control messages and / or search spaces that the UE should use to decode the control channel following detection of the low-cost signal. Once the UE successfully decodes an initial message on the control channel using parameters indicated by a particular low-cost sequence used during wake-up, the UE may then be configured to automatically revert to using the entire bandwidth, set of control messages, or search space. Transitioning from one bandwidth to another may be done using mechanisms specified herein, for example, in the "Control Channel Decoding Complexity" section.

[0413] In another embodiment, a UE in a sleep mode (e.g., deep sleep) may be configured to continuously monitor low-cost signals. Alternatively, to ensure further power savings, the UE may be configured to monitor low-cost signals during (e.g., only during) specific time intervals and / or time windows that may be configured by the network. The UE may be configured to transition to an active state upon detection of any of the signals that the UE is monitoring. The times at which the UE needs and / or can wake up may be:

[0414] - Immediately after detection of a low-cost signal,

[0415] - a fixed or network configured time offset following detection of a low-cost signal;

[0416] - the next frame / subframe following detection of a wake-up signal that satisfies certain criteria, such as subframe (mod N)=k, where k may be determined based on the UE ID, cell ID, system signature, etc.; and / or

[0417] - signal duration, a particular sequence, or a time domain nature of a sequence. For example, a UE may be configured to monitor multiple sequences, each sequence representing a different time.

[0418] The UE may be configured to decode the control channel during a defined time period or during N potential control channel instances following detection of the low-cost signal. If the UE does not receive a message within this specified time period following detection of the low-cost signal, the UE may be configured to continue operating / return to operating in a low power state. On the other hand, the UE may be configured to move to an active state once a message is successfully decoded on the control channel.

[0419] The UE may be configured to transition from an active state to a low power state (decoding of a low-cost signal that wakes up) based on any of the following:

[0420] - a dedicated message indicating the transition set to the UE (e.g. via MAC CE, or PHY layer control signaling);

[0421] - The UE may be configured to receive an instruction to remain in an active state in a transition from a low power state to an active state or at any time during the active state. Upon receiving the instruction, the UE may be configured to remain in the active state for the duration of the timer. The UE may then be configured to transition to a low power state if no instruction is received for a specified period of time. The instruction to reset the timer may be further piggybacked on the UL grant and / or DL ​​grant or other control information (e.g., timing advance) sent to the UE;

[0422] The UE may be configured to transition from an active state to a low power state based on decoding of the low-cost signal itself, i.e. failure to decode the low-cost signal for a specified period of time may cause the UE to transition; alternatively, reception of a (potentially different) low-cost signal may force the UE to transition to a low power state; and

[0423] - following several DRX cycles or similar whereby the UE is not scheduled with data on the downlink or on the uplink.

[0424] In another embodiment, the UE may be configured to have DRX operation or idle-like operation (periodic monitoring of the control channel) and may be configured to monitor low-cost signals during inactive periods during the wake-up time (e.g., when the UE is not monitoring the control channel). In this case, detection of a low-cost signal may result in any of the following UE behaviors: shifting the active time of the DRX cycle such that the UE starts with detection of the low-cost signal, resetting the drx inactivity timer for DRX operation, and canceling or disabling the DRX operation for the UE.

[0425] 8 is a representative flow diagram illustrating a method for power conservation by determining and processing a minimum amount of resources based on a processing state of a UE. The method may be performed by either a device or a system, although the method is shown to be performed by a UE or a WTRU.

[0426] The UE may comprise a transmitter, a receiver, and a processor coupled to the transmitter and the receiver. The UE may be configured to determine a processing state related to a behavior of the UE in operation 801. The processing state may comprise one or more states related to a behavior of the UE. The processing state may indicate an activity state of the UE. The UE may determine the processing state based on a scheduling activity. The scheduling activity may comprise one or more scheduling events based on any of: (1) receiving dynamic scheduling information as part of a downlink control information (DCI), (2) semi-statically configured scheduling information, (3) an autonomous transmission of a WTRU, (4) new data becoming available for transmission, or (5) a change in the rate of one or more scheduling events (e.g., a certain threshold may be about to be reached). The UE may determine the processing state using a timer-based function. Determining the processing state based on a timer-based function may include establishing any of: (1) a certain amount of time that has elapsed since a previous scheduling activity or since a previous scheduling event, or (2) a time-based pattern as an established outcome. The UE may further process at least the determined minimum amount of resources of one or more sets of physical resources. The processing state may be a function of the wake-up signal, i.e., reception of the wake-up signal used to determine a change in processing on the UE. The processing state may relate to, but is not limited to, UE actions in at least one of: (1) control channel processing, (2) spectrum bandwidth processing, (3) beam management and processing, (4) reference signal processing, (5) hybrid automatic repeat request (HARQ) timing operations, (6) frame operations, (7) timing operations, or (8) logical channel properties and configurations.

[0427] The processing state may determine that the UE is in a first processing state. The UE may determine to transition from the first processing state to a second processing state based on at least one condition. The at least one condition may include receipt of a message from a network entity such that the message may indicate at least one of an index associated with the second processing state to be configured, a predefined time to transition to the second processing state, and / or a time difference between the time the message was received and the time the transition associated with the second processing state will occur. The message may further include a configuration used by the UE to further define a behavior or action to be performed in the second processing state (e.g., on a control channel, a data channel, and / or other aspects disclosed above). The at least one condition may include receipt of a message from a network entity such that the message may be signaled via at least one of: (1) a radio resource control (RRC) message, (2) a media access control (MAC) control element (CE), (3) a downlink control information (DCI) on a control channel, or (4) a wake-up signal. The at least one condition may be based on at least one of: expiration of a timer, a change in scheduling activity on a control channel, arrival of a new service at the WTRU, availability of a transmission, successful transmission / reception of data at the WTRU, data in a WTRU buffer exceeding or falling below a threshold, expiration of a timer related to the activity state or scheduling activity, speed of the WTRU exceeding or falling below a certain value, battery life reaching a particular value, triggering a scheduling request, initiation of a scheduling request and execution of an access procedure, state of a hybrid automatic repeat request (HARQ) process, presence or absence of a signal such as a reference signal, a change in one or more monitored beams, a beam switch / change, and / or a beam management event (e.g., beam failure). The UE may send a request message to the network, where the request message indicates a change in the first process state.The request message may further comprise at least one of a state index of the target state to which the WTRU attempts to transition, a list of desired state indexes, one or more parameters associated with the conditions for the state transition, buffer occupancy, a particular logical channel, a type of data, a channel measurement, or a time duration in the target state.

[0428] The UE may associate a first processing state with a first configuration for the data channel and a second processing state with a second, different configuration for the data channel. The UE may receive a resource allocation for the second processing state from a network entity, transition to the second processing state, and decode the received resource allocation in the second processing state.

[0429] In operation 802, the UE may determine a minimum amount of resources to be processed for one or more sets of physical resources based on the determined processing state. Each respective set of physical resources may comprise resources in terms of time and either frequency or space. For each respective set of physical resources, the time may correspond to a frame structure associated with a numerology applicable to the respective set of physical resources. The frequency may correspond to either a frequency location (e.g., a center frequency), a bandwidth, or a numerology, and may further correspond to a bandwidth portion of a carrier. The space may correspond to one or more beams.

[0430] The UE may monitor the control channel using either (1) a determined minimum amount of resources of at least one or more sets of physical resources or (2) a type of signaling structure. The determined minimum amount of resources of the one or more sets of physical resources may comprise one or more control channel elements and one or more aggregation levels. The type of signaling structure may comprise (1) a received strength of a signal including downlink control information (DCI) and (2) a size, format, and / or type of each received signal including DCI. The received strength of the signal may comprise a received strength of either a reported radio link quality, a type of configured service, or an activity observed for a given service. In operation 803, the UE may process the determined minimum amount of resources of the one or more sets of physical resources.

[0431] Power Savings Under Multiple SOMs

[0432] A UE may be configured with multiple SOMs, spectrum blocks, bandwidth portions, numerologies, and / or control channels (or equivalent structures), such as those using different sets of DCI. A UE may be configured to operate with multiple SOMs in a TDM manner, or in an FDM manner, or with multiple SOMs in a combination of the two. A SOM (e.g., each SOM) may be associated with a control channel that carries information for allocating a set of spectrum blocks for the UE. Resources may be allocated on that particular SOM and / or spectrum block.

[0433] 1) TDM

[0434] In one embodiment, in a TDM case, the UE may be configured to have periods during which scheduling opportunities for allocating resources may occur every first duration (e.g., 1 ms) alternating with periods during which scheduling opportunities for allocating resources occur every second duration (e.g., 125 μs).

[0435] 2) FDM

[0436] In one embodiment, in the FDM case, the UE may be configured with a spectrum block in which a scheduling opportunity for allocating resources may occur every first duration (e.g., 1 ms) and another spectrum block in which a scheduling opportunity for allocating resources occurs every second duration (e.g., 125 μs).

[0437] 3) Combination of TDM and FDM

[0438] In one embodiment, in the case of a combination of TDM and FDM, the UE may be configured to have periods during which scheduling opportunities for allocating resources as described above may occur per TDM and other periods during which scheduling opportunities for allocating resources as described above may occur per FDM.

[0439] The UE may be configured to monitor the control channel by a time-based algorithm. An embodiment may include a legacy LTE DRX procedure. Another embodiment may include any of the methods and procedures described herein. Such a time-based algorithm may be represented by a timer and / or a counter. In such a case, the UE may be configured to determine an activity time, which consists of the time that the UE is minimally required or used to monitor the control channel. The UE may then be configured to sleep (e.g., by reconfiguring its radio front end) and / or perform DRX (e.g., discontinuously monitor one or more control channels) for all other time instances where the UE is not required or used to monitor the control channel.

[0440] Such time-based control channel monitoring algorithms may be applied together with other methods described herein, either separately or in combination in a configurable manner.

[0441] General principles

[0442] A UE may be configured to determine different levels of power savings over time using approaches based on legacy DRX and / or using methods such as those described herein. A UE may be configured to perform different power saving modes at different times and / or in association with different SOMs. A UE configured with multiple numerologies, with multiple spectrum blocks (or SOMs), and / or with multiple control channels (e.g., one for each numerology, spectrum block, or set thereof) may be configured to perform such determinations using timing references and relationships. The timing references and relationships may correspond to a clock, to a time-based trigger for modifying (e.g., decrementing / incrementing by one unit) one or more timers, and / or to any counting technique (hereinafter referred to as a "clock") used to manage the time-related aspects of such algorithms. In general, a set of one or more timers is used for a given instance of a power saving mode, such as legacy LTE DRX. The clocking may be based on a TTI duration, a minimum time between two scheduling opportunities, or other framing aspects. Thus, the clock generally refers to downlink timing aspects.

[0443] 1) Parameterization of the traditional LTE DRX algorithm

[0444] In one embodiment, legacy timers and associated parameters controlling legacy LTE DRX operation include onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer (one per DL HARQ process except for the broadcast process), longDRX-Cycle, drxStartOffset and optionally values ​​of drxShortCycle timer and shortDRX-Cycle. HARQ RTT timers per DL HARQ process (except for the broadcast process) are also defined. The timers (e.g., each timer) may be timed based on the LTE subframe (e.g., 1 ms PDCCH subframe) in which downlink control signaling is available for reception.

[0445] 2) Method A - At least some timing aspects are timed based on a reference numerology

[0446] In one embodiment, the UE may be configured to control some timing aspects of the power saving function as a function of the frame duration associated with a given numerology and / or as a function of the scheduling opportunity / occasion (hereafter generally referred to as clock / timing) associated with the SOM. This behavior may be the default behavior of the UE's configuration.

[0447] 3) Method B - At least some timing aspects are timed based on a reference numerology

[0448] In another embodiment, the UE may be configured to control at least a first set of timing aspects as a function of timing associated with a reference numerology / SOM / spectrum block. Such a reference numerology may be a configuration aspect of the UE (e.g., layer 3 / RRC configuration, UE-dedicated or "cell / spectrum" specific received by dedicated signaling or broadcasted), or it may correspond to a default numerology of a cell and / or spectrum block, such as one associated with resources used by the UE to initially access the system (e.g., 1 ms) and / or one indicated in the system information. In some embodiments, such a first set of timing aspects may correspond to a configured period during which the UE is reachable after a period of inactivity (e.g., an on-duration period parameterized by onDurationTimer, drxStartOffset, longDRX-Cycle, and optionally drxShortCycle timers, and shortDRX-Cycle in case of legacy DRX). This behavior may be a default behavior of the UE's configuration.

[0449] 4) Method C - At least some timing aspects are timed based on a reference numerology

[0450] In another embodiment, the UE may be configured to control at least a second set of timing aspects as a function of timing associated with a particular numerology / SOM / spectrum block. Such may correspond to a particular control channel, TTI duration, and / or may differ from another based on the UE's configuration. In some embodiments, such a second set of timing aspects may correspond to a period dynamically controlled by the network and / or related to the UE's transmission activity (e.g., active time outside the on duration period parameterized by drx-InactivityTimer, drx-RetransmissionTimer, and in case of legacy DRX, HARQ RTT timer). This behavior may be the default behavior of the UE's configuration.

[0451] 5) Combination of Methods A / B / C

[0452] In some embodiments, the UE may be configured to control one or more power saving aspects (e.g., control channel monitoring, bandwidth adaptation, beam management, etc.) using a combination of the above methods. In a representative embodiment, the UE may be configured to control blind decoding activity (and its associated parameterization) for all control channels using the timing / clock of a reference numerology over a "reachability" period, e.g., an on-duration period, while using that of a numerology scheduled for other aspects when the UE becomes active in transmitting for applicable control channels, such as channels on which the UE actively receives downlink control signaling.

[0453] 6) Method - Representative Realization for FDM

[0454] The above embodiment is particularly applicable to the case where resources associated with different numerologies are configured in an FDM manner. In one embodiment, some timers related to on-duration (and starting offset) may be a function of the default TTI duration and / or scheduling opportunity (e.g., 1 ms), while other timers (non-activity timers, HARQ-related timers, long / short cycle DRX, etc.) may be a function of the numerology associated with the UE's transmission activity when scheduled (e.g., 125 μs if scheduled with the second numerology, 1 ms otherwise). Furthermore, all (or each) control channels associated with a given numerology may have a set of timers following the timing aspects associated with that numerology (e.g., 1 ms clock vs. 125 μs clock, and timer start values). In another embodiment, there may be a set of timers common to all control channels independent of numerology, for example for on-duration and a common starting offset.

[0455] 7) Method - Representative Realization for TDM

[0456] In one embodiment, a UE configured with different numerologies / SOMs / spectrum blocks using TDM may be configured to use a (numerology / SOM / spectrum block) specific DRX instance to control one or more power saving aspects (e.g., control channel monitoring, bandwidth adaptation, beam management, etc.). In such a case, during a period when the resources of a numerology / SOM / spectrum block are not applicable (e.g., an associated physical control channel may not be available and / or a corresponding physical data channel is not schedulable), the associated DRX instance may simply sleep and wait. Otherwise, the associated DRX instance may be timed according to the timing applicable to the involved numerology / SOM / spectrum block.

[0457] In another embodiment, the clock may be a function of the scheduling opportunity, independent of the TTI / frame duration of the respective numerology / SOM / spectrum block. In such a case, a single DRX instance may be used.

[0458] UE specific DRX

[0459] A UE may be configured to have a single power saving mode (e.g., including a control channel monitoring algorithm such as legacy DRX) that applies across all SOMs. For example, a UE may be configured to monitor the control channel in different SOMs and may be configured to have that control channel monitoring algorithm common across all SOMs.

[0460] In such a case, the UE may be configured to apply the UE's DRX across all SOMs or control channels (CCs) associated with such SOMs. Because the SOMs (e.g., each SOM) may have different timing of the control channel (e.g., how frequently the UE may receive scheduling), a method for determining the UE's control channel monitoring behavior under a time-based algorithm is needed and / or used, as described below.

[0461] 1) A UE that operates within one numerology by defining its DRX behavior from the default SOM timing.

[0462] In one embodiment, the UE may be configured to determine its control channel monitoring period, which is configurable by the network, and the allowable DRX period based on a number of control channel scheduling opportunities of a particular numerology or a particular SOM. The UE may or may not be monitoring the control channel on such a default SOM when the UE is configured to perform DRX based on the timing of such a default SOM.

[0463] In another embodiment, the UE may be configured to perform DRX based on a count of subframes in a default numerology. The UE may be further configured to monitor a control channel in a numerology other than the default numerology. The UE may be required and / or used to monitor the control channel for an on duration period of x subframes in the default numerology before the UE can perform DRX. Depending on the numerology or SOM configured in the UE, the number of slots or control channel scheduling occasions may vary during this on duration period.

[0464] The UE may be configured to start one or more timers during the on duration such that the UE is required and / or used to monitor the control channel for a period of the one or more timers longer than the on duration period. Such timers may be timed based on a default numerology. For example, the UE may be configured to receive a DL or UL grant that starts in an activity timer while monitoring the control channel in its configured numerology. The UE may be configured to increment such inactivity timers based on the timing of the default numerology (e.g., once for a subframe (e.g., each subframe) in the default numerology). The UE may be configured to determine that the UE can perform DRX (e.g., the UE does not or does not need to monitor the control channel) upon expiration of any timer started during the on duration period.

[0465] The UE may be configured to begin monitoring the control channel during certain subframes in the default numerology, and such subframes may occur periodically according to some configured period. The UE may select a slot or control channel opportunity.

[0466] - the first control channel opportunity in a configured SOM occurring subsequent to the start of a subframe in the default numerology, or

[0467] - a control channel opportunity occurring closest in time (before or after) to the start of a subframe in the default numerology The method may be further configured to calculate:

[0468] 2) DRX timing defined based on scheduling occasion

[0469] In one embodiment, the UE may be configured to determine the duration of its control channel monitoring and base that timer on the total number of scheduling occasions in the configured numerology. For example, the UE may be configured to have a set of timers that are defined based on the on-duration as well as the number of scheduling occasions for the UE in its configured SOM, which may be configured such that the UE remains active following the on-duration.

[0470] A UE configured with multiple SOMs may be configured to determine the number of scheduling occasions based on the total number of scheduling occasions in the configured SOMs (eg, each of the configured SOMs).

[0471] 3) Combining the timing of different SOMs to derive a single DRX behavior

[0472] In one embodiment, the UE may be configured to combine timings of its different configured SOMs as well as non-configured SOMs, such as a default numerology, to define an overall DRX behavior. For example, the timings of one or more DRX parameters or DRX related timers may be controlled by a first numerology or SOM, while the timings of one DRX parameter or DRX related timer or a different set of DRX parameters or DRX related timers may be controlled by a second numerology. The selection of the SOM and / or the selection of the timers calculated by the associated SOM may depend on the following:

[0473] - network configuration: in an embodiment, if the UE is configured with multiple SOMs, the UE may be configured by the network with the SOM timing to use to determine associated timers (e.g., each of the associated timers); and

[0474] Logical channel configuration: In an embodiment, the UE may be configured to determine the SOM to use based on priority or latency requirements of the logical channels that may be mapped to the SOM (e.g., each SOM), such as by using the logical channel with the highest / lowest priority. The signal may be determined by one of the following:

[0475] In another embodiment, the UE may be configured to use a first numerology or SOM to determine its DRX cycle and / or its on-duration period. Such a first numerology may be a default numerology or SOM. In other words, the UE may be configured to determine the on-duration and wake-up time (e.g., DRX cycle length) based on a number of subframes in the default numerology. The UE may be further configured to increment a timer associated with maintaining the UE's activity time, such as any of the inactivityTimer, retransmissionTimer, ULRetransmissionTimer, shortCycleTimer, etc., using the timing of its configured numerology. In some embodiments where the UE is configured to have multiple non-default SOMs, the UE may be configured to determine a non-default SOM for which the above timers are calculated such that the SOM to which the highest priority logical channel is mapped at any given time.

[0476] 4) Defining DRX behavior as a function of multiple DRX-related timers for different SOMs

[0477] In one embodiment, the UE may be configured to maintain different DRX related timers, such as different instances of any of the InactivityTimer, retransmissionTimer, ULRetransmissionTimer, shortCycle timer, etc. For example, the values ​​of such timers may be configured to be different.

[0478] - logical channels that are mapped to the SOM (e.g., each SOM): for example, selection (e.g., of a control channel) based on the presence of a particular logical channel mapped to the SOM;

[0479] - network-configured inclusion / exclusion of certain SOMs in functions: for example, mapping rules may be based on functions of certain SOMs (e.g., only functions of certain SOMs), and the list of SOMs to be considered may be statically and / or dynamically changed by the network at any time through network signaling;

[0480] - QoS properties of the associated SOM or logical channels mapped to the SOM: for example, the rule may be based on the highest priority logical channel mapped to the SOM at any given time, or on the SOM having a priority higher than a certain threshold;

[0481] - the number of services, logical channels, etc., mapped to a SOM (e.g., each SOM): for example, the rule may be based on having a minimum amount of logical channels mapped to a SOM, the UE-specific active time may be a combination of weighted timers associated with the SOM (e.g., each SOM), and the number of logical channels may determine the weight applied; and

[0482] - the amount of bandwidth or resources available to the SOM (e.g., each SOM): for example, the rule may be based on having a minimum amount of bandwidth configured for the SOM, and / or the UE-specific active time may be a combination of weighted timers associated with the SOM (e.g., each SOM), and the bandwidth may determine the weight applied; The SOM may be configured to determine whether to continue monitoring its control channel based on a function or relationship of one or more of these timers, in addition to the nature of the SOM itself, such as:

[0483] In another embodiment, the UE may be configured to determine its activity time as the time needed and / or used for the timers for the expiring SOMs (e.g., each of the expiring SOMs). The UE may be configured to monitor the control channels for all SOMs as long as the timers (inactivityTimer, RetransmissionTimer, etc.) for all of the active SOMs are still running.

[0484] In another embodiment, the UE may be configured to determine the activity time as the time required and / or used for the timer of one particular SOM that is to expire, which may be semi-statically or dynamically configured by the network (e.g., through RRC signaling or control channel signaling) or may be selected based on the SOM having the highest priority logical channel over other logical channels in the absence of network configuration.

[0485] The above embodiments may be applicable to SOMs that are TDM or FDM. In the TDM case, the UE may be configured to determine which SOM is currently scheduled at a given scheduling occasion. Such a determination may be made based on the following:

[0486] - the control channel numerology for a given slot, minislot, or subframe;

[0487] - a fixed pattern of multiplexing of different numerologies, and

[0488] - by a structure of SOM multiplexing determined via signaling from the network, such as via dynamic signaling from a separate control channel, or via RRC signaling; This may be based on at least one of the following:

[0489] 5) Selection of a timer based on the nature of data received during the active time

[0490] The UE may be configured to select from one of a set of DRX or DRX timer values ​​based on the type of data multiplexed in a transmitted Media Access Control (MAC) Protocol Data Unit (PDU) or transport block. The UE may be configured in a first operation to determine, during an active time, the nature of the data multiplexed into a received MAC PDU and to make a decision of one or more of the applicable DRX timers based on the type of data. Such a decision may be based on the following properties of the data received in the MAC PDU:

[0491] - one or more logical channels or services associated with the MAC PDU;

[0492] - QoS properties of the data within the MAC PDU or associated with a logical channel, a service, or a flow within a logical channel (e.g., each logical channel), such as priority, delay requirements, reliability requirements, rate requirements, and

[0493] - the number of logical channels or services multiplexed into the MAC PDU; The method may be based on one or more of:

[0494] In one embodiment, the UE may be configured to have a separate set of inactivityTimers for a logical channel (e.g., each logical channel) or for a logical channel group (e.g., each logical channel group). The UE may be configured to determine, during an active period, to start an inactiveTimer upon receipt of a grant from the network. The UE may be configured to select an inactiveTimer corresponding to a logical channel group transmitted in a MAC PDU received with the grant. Furthermore, if multiple logical channel groups are transmitted in the same MAC PDU, the UE may be configured to select an inactiveTimer associated with one of the logical channel groups (based on rules such as network configuration, use of highest / lowest priority, etc.).

[0495] In another embodiment, the UE may be configured to determine the DRX time (e.g., the time during which the UE is not required to monitor the control channel) based on a selection of a timer that is specific to a logical channel or logical channel group. The UE may be configured to determine such logical channel or logical channel group for the selection of the timer to be the highest / lowest / most logical channel transmitted within the first / last / most MAC PDUs received during the active time.

[0496] 6) The UE monitors the CC based on the interval of the scheduling opportunity.

[0497] In one embodiment, the UE may be configured to monitor the control channel for a particular SOM over discrete intervals of scheduling opportunities. For example, the UE may be configured to monitor the control channel for a particular SOM where a CC opportunity may occur each slot in a particular numerology (or potentially the UE may be configured to use a single SOM (e.g., only a single SOM).

[0498] In another embodiment, the UE may be configured to monitor every N slots of the control channel in the power saving mode, i.e., slots 0, N-1, 2*(N-1), etc. The UE may be configured to determine the value of N based on a network configuration or based on dynamic signaling. For example, the UE may be configured to receive an indication over the control channel itself to dynamically change the value of N. In some embodiments, the UE may be configured to determine the value of N from a set of predefined values ​​based on a UE state, which may represent a level of activity and / or a power saving state. For example, the UE may be initially configured to have a set of values ​​as {2, 4, 8, 16, ..., M}, where M is an integer power of 2. The UE may be configured to autonomously determine the value of N based on the status of a DRX timer. For example, during a highest activity state, the UE may be configured to choose a value of N (e.g., 2) to be the lowest in the predefined set. During a highest power saving state, the UE may be configured to choose the highest value in the predefined set, e.g., 16. Such a configuration of predefined values ​​may enable UEs to be reachable by the network regardless of understanding of their UE activity state, for example via the highest value in the predefined set.

[0499] The UE may be configured to use the above methods in combination with other methods described herein, or in combination with legacy-like DRX. For example, the UE may be configured to decrement a DRX-related timer, such as an inactivityTimer, every Nth control channel scheduling opportunity (e.g., based on the UE's own monitoring schedule).

[0500] In another embodiment, the UE may be configured to determine certain DRX-related timers based on control channel scheduling occasions and other timers based on its own monitoring occasions (e.g., every N control channel scheduling occasions).

[0501] SOM specific DRX

[0502] The UE may be configured to apply an independent DRX or control channel monitoring algorithm to the SOM (e.g., each SOM). Within the control channel monitoring algorithm that is specific to the SOM (e.g., each SOM), the UE may be further configured to apply any control channel monitoring functions based on the methods described herein. The UE may be further configured by the network as to which algorithm should be applied to a given SOM. The methods described herein provide further aspects, operations, procedures, and functions related to interactions between SOM-specific control channel monitoring algorithms.

[0503] One advantage of independent DRX may be that it allows the UE to shut down parts of its front-end or digital control channel processing (in the case of FDM-based SOMs) based on the expected activity of each SOM independently.

[0504] 1) Monitoring the primary control channel for SOM power saving configuration

[0505] A UE performing independent DRX on different SOMs may be further configured to monitor a primary control channel associated with a particular SOM (which may or may not be configured for the UE) to receive SOM configuration information (e.g., resource blocks, numerology, duration of numerology blocks, etc. associated with the SOM (e.g., each SOM)). Such a primary control channel may span a subset of channels or the entire bandwidth and may use or require the UE to monitor a default numerology. The UE may be configured to monitor the primary channel for a finite period of time (e.g., a fixed number of subframes in a reference numerology).

[0506] The UE may be configured to receive the configuration of the primary control channel from an RRC configuration, from system information, or from an access table, for example, to provide system related information.

[0507] 2) Receiving on / off period information from the primary control channel

[0508] The UE may be configured to perform control channel monitoring or DRX based on receiving dynamic information provided on the primary control channel. Such dynamic information may be used in conjunction with semi-static or pre-configured configurations used by the UE. For example, the UE may be configured to receive an indication of a period for monitoring a SOM-specific CC or an indication of one or more periods of DRX on a particular SOM based on signaling received from the primary control channel as at least one of the following:

[0509] - DRX time to be applied to a particular SOM: the UE may be configured to receive an indication on the primary control channel to perform DRX (e.g., lack of CC monitoring) on ​​a particular SOM for a period of time, which may be pre-configured or may be indicated;

[0510] - Indication for continuous control channel monitoring: the UE may be configured to receive an indication on the primary control channel to perform continuous monitoring of the CC on a particular SOM until further notification from additional signaling on the primary control channel;

[0511] - Active time to be applied to a particular SOM: the UE may be configured to receive an indication on the primary control channel to start monitoring the CC of a particular SOM and to do so for a particular period of time or active period;

[0512] - DRX timer configuration / reconfiguration: The UE may be configured to receive an indication on the primary control channel to reconfigure the timers related to DRX similar to the legacy ones that are to be applied to that particular SOM; and

[0513] - Control channel monitoring algorithm: The UE may be configured to receive instructions on the primary control channel to configure a control channel monitoring algorithm (such as the methods described herein) to be applied to a particular SOM and associated parameters for that algorithm.

[0514] A UE that receives such information of on and off durations for a SOM (e.g., each SOM) from the primary control channel may be configured to monitor the primary control channel (e.g., only the primary control channel) unless indicated to do so by dynamic signaling on the primary control channel.

[0515] 3) Receiving wake-up or DRX corrections from one SOM for another SOM

[0516] In one embodiment, the UE may be configured to receive a change in the DRX configuration of the first SOM from signaling (e.g., PDCCH or similar dynamic signaling) received from the second SOM while operating with an independent DRX for each SOM and while monitoring the SOM-specific CC based on the independent DRX. Such a change in DRX configuration or behavior may include the following:

[0517] - Changes in the DRX cycle,

[0518] - A change in any of the DRX related timer values, such as inactivityTime, retransmissionTime, shortDRXCycle, etc.

[0519] - changes in the offset of the DRX cycle (e.g. the frame / subframe / slot index that defines the start of the active period), and

[0520] - instructions to wake up or start monitoring the control channel at a given time (e.g., immediately or during x number of subframes) for a configurable or predefined period of time; may include at least one of the following:

[0521] In one embodiment, the UE may be configured to monitor the CC for two different SOMs using independent control channel monitoring algorithms. Both such control channel monitoring algorithms may consist of or include a traditional DRX-like operation or may be defined based on the methods described herein. The first SOM may be associated with low latency related data transmission and may consist of or include a short DRX time compared to the second SOM, which may be associated with eMBB. The UE may be configured to receive an indication from the first SOM to immediately wake up to monitor the control channel on the second SOM. Such an immediate or indicated wake up may be associated with a change in the DRX cycle offset such that the active time on the second SOM starts at the indicated time for the UE. In another embodiment, the indication may create a new active time of configurable duration within an existing DRX cycle. The UE may be configured to receive at least one of the following information from the indication:

[0522] - the SOM or SOM index that the UE will wake up (for SOM2);

[0523] - the scheduled time for the UE to wake up;

[0524] - new DRX parameters or timers associated with the reconfiguration, such as new DRX offsets to apply to achieve the indicated wake-up;

[0525] - the amount of time that the UE is configured to monitor the control channel on the SOM in question;

[0526] - specific control channel elements, e.g. decoding specific CCEs or sets of search spaces that the UE is configured to receive;

[0527] - a particular DCI that the UE is configured to monitor during immediate wake-up on the SOM2;

[0528] - a subinterval of the control channel monitoring frequency for SOM2; and

[0529] - Instruction to start / stop DRX or power saving algorithms on SOM2.

[0530] In another embodiment, some or all of the above information may be semi-statically configured in the UE as part of the DRX configuration.

[0531] An advantage of such an embodiment may be to increase the reachability of a UE when operating under different SOMs, i.e., if the UE has control channel activity in a first SOM, the UE may be reachable in a second SOM (e.g., without the network having to wait for UE activity time in that SOM).

[0532] 4) Deriving SOM-specific DRX-related parameters from the default configuration based on changes in numerology

[0533] In one embodiment, the UE may be configured with a set of DRX related parameters, such as, but not limited to, inactiveTime, drxCycle, retransmissionTimer, shortDRXCycle, to be applied to a particular numerology or SOM. The UE may be configured to derive associated parameters to be used on different SOMs based on default parameters, which may be a function of at least one of the following, and a function of one or more scaling relationships:

[0534] - Numerological differences between SOMs (e.g. scaled by differences in subcarrier spacing, etc.),

[0535] - the nature and / or number of logical channels that are mapped to a particular SOM;

[0536] - the logical channel identifier (LCID), logical channel group identifier (LCG ID) or priority identifier associated with the logical channels mapped to a particular SOM;

[0537] a weighted average of the number of logical channels mapped to a particular SOM, where the weights may be provided by the network; and

[0538] - A numerology-specific, network-configured scaling factor that can be provided by RRC signaling or dynamically (e.g., provided on the primary control channel).

[0539] The UE may be further configured to apply different scaling factors or functions to different DRX parameters.

[0540] In one embodiment, the UE may be configured to derive a DRX cycle for a particular SOM by multiplying a default DRX cycle with a scaling factor determined based on the logical channels mapped to that SOM. Such a scaling factor may be provided by the network (e.g., the UE may be configured to receive a specific scaling factor associated with a logical channel (e.g., each logical channel)). In the case where multiple logical channels are mapped to the same SOM, the UE may be further configured to perform a weighted average of the scaling factors on the logical channels (e.g., each of the logical channels) mapped to the SOM. The UE may be configured to directly derive the scaling factor from the LCID, LCG ID, or priority parameters / levels, or the like associated with the logical channel.

[0541] DRX operation following UL / DL transmission - DRX operation following SR transmission

[0542] The UE may be configured to perform DRX-like operations following transmission of a scheduling request (SR) to the network. For example, such DRX-like operations may be characterized by monitoring a control channel for a number (e.g., a fixed number) of scheduling opportunities (N) every M scheduling opportunities. The value of M (referred to as the SR-DRX cycle) and the value of N (referred to as the active period) may be configured by the network.

[0543] The UE may:

[0544] - Direct configuration via the network,

[0545] - A fixed or preconfigured value (e.g., N=1),

[0546] - data arrival is determined based on the logical channel that triggered the SR;

[0547] - based on time-related requirements (e.g., time to live) associated with the arrival of new data that triggered the SR, and

[0548] - Based on the SOM used to submit the SR, The device may be configured to determine the values ​​of either M and / or N based on at least one of:

[0549] A UE that further determines the values ​​of M and / or N may be configured to provide such a decision, or some implicit information related to such a decision, to the gNB as part of the SR. Such information may be provided explicitly within the SR or based on some property associated with the SR transmission, such as resources, power, spreading, MA scheme, preamble sequence, or other property associated with the SR transmission.

[0550] The UE may be configured to continue the above DRX behavior until one or more of the following occurs:

[0551] - the UE receives a grant associated with the triggered SR;

[0552] - A timer expires (which may trigger a new SR),

[0553] - the UE is scheduled on another SOM that can fulfill the request, and

[0554] - The UE receives an indication from the network to continuously monitor a control channel for a grant.

[0555] The UE may be configured to retransmit the SR according to the DRX schedule described above (e.g., the UE may be configured to retransmit the SR following control channel monitoring in every k wake-up periods of the M scheduling opportunities).

[0556] In one embodiment, the UE may be configured to determine the value of M based on the logical channel that triggered the SR, and may assume N=1. For example, the UE may be configured (by the network) or pre-configured with a value of M to be used for a logical channel and / or logical channel type (e.g., each logical channel or logical channel type). The UE may be further configured to transmit an LCID or similar as part of the SR. Once the SR is transmitted, the UE may be configured to monitor the CC every N scheduling opportunities in a particular SOM numerology or in some reference numerology.

[0557] Multi-Level Activity Control

[0558] The UE may be configured to decode downlink control information (e.g., at least one DCI) on a first set of control channel resources (e.g., a common search space, such as a common control channel, such as a PDCCH). Such a configuration may include one or more identifiers (or indexing values). Such a configuration may include a particular RNTI to use for decoding such DCI. Such DCI may consist of or include a particular DCI type. Such a particular DCI type may convey information, such as one or more identifiers (or indexes). Such information may be organized as at least one of the following: values ​​of one or more fields, one or more bitmaps, or the like.

[0559] In some embodiments, at least one parameter used to decode the at least one DCI may be a function of an identifier used for activity control, such as an ID group. For example, such parameters may include an RNTI to use to decode the at least one DCI, or may include a parameter indicating resources on which to attempt to decode the at least one DCI, such as a time symbol, a set of slots or minislots, a set of physical resource blocks, a resource element group, and / or a control channel element. In embodiments, in cases where a UE is configured with multiple identifiers, the UE may be configured to attempt to decode the DCI for an identifier (e.g., each such identifier) ​​using one or more associated parameters.

[0560] From a first state (e.g., a lower activity state) to a second state (e.g., a higher activity state)

[0561] In an embodiment, the UE may be configured to decode a particular DCI on a common search space. The UE may decode the particular DCI using a particular RNTI. It is contemplated that such decoding activity is a function of an activity state. It is contemplated that such decoding activity corresponds to a first time scale (e.g., slots, subframes, etc.). The UE may be configured to determine from successful decoding of such particular DCI that the DCI includes one or more identifiers (or indices). The UE may be configured to determine that such one or more identifiers (or indices) match one or more configurations of the UE. In a representative embodiment, the UE may be configured to determine from such match (e.g., for at least one identifier) ​​that it should move to a second activity state. It is contemplated that such activity state corresponds to a second time scale (e.g., minislots, slots, etc.).

[0562] In representative embodiments, an activity state (e.g., each activity state) may be associated with a certain number of blind decoding attempts. For example, a UE may be configured to perform a small number of blind decoding attempts in a low activity state and a large number of blind decoding attempts in a high activity state. Blind decoding is part of the control channel processing. The dependency of activity state and blind decoding is described herein, for example, in the section entitled "Reducing the Number of Blind Decodes" above.

[0563] From a higher activity state to a lower activity state

[0564] In another embodiment, the UE may be configured to determine, based on the received signaling, that a change in activity state may be performed from a first activity state corresponding to a higher level of activity to a second activity state corresponding to a lower level of activity, such level being dependent on the activity state as described above.

[0565] In some embodiments, in cases where the UE decodes multiple DCI or control signals associated with the configuration identifier, the UE may be configured to determine an appropriate activity state based on predefined rules, e.g., the UE may select the highest state among the indicated activity states.

[0566] Network perspective and possible benefits to scheduling functions

[0567] From the network's perspective, one or more UEs may be configured with the same set of control channel resources, search space, a particular RNTI, etc. The network may be configured to allocate the same identification information to a set of one or more UEs for the purpose of matching activity states of such sets of UEs. The network may further be configured to allocate one or more identifiers (or indices) to a given UE to increase flexibility in determining a subset of one or more UEs that share similar scheduling activities over a given period of time.

[0568] In some embodiments, such control signaling may correspond to a low-cost signal. It is contemplated to configure one or more characteristics of either the control signaling or the low-cost signal. Such characteristics may correspond (e.g., each corresponds) to one particular identifier (or index).

[0569] The activity levels may be further generalized in any number, for example, the number of activity levels may be realized based on any combination of a particular DCI, RNTI, set of control resources, low-cost signal characteristics, and a particular identifier (or index) with a particular level.

[0570] In a representative embodiment, the UE may be configured to monitor a PDCCH (or a common PDCCH) using a particular RNTI in every slot. When the UE successfully decodes a DCI from such a PDCCH (or a common PDCCH), the UE may be configured to determine whether at least one identifier of the configuration matches at least one identifier included in the DCI. If a match is detected, the UE may be configured to determine that a blind decoding attempt may be performed, for example, with (e.g., only with) a low activity state (e.g., no blind decoding at all) for the remainder of the slot (and / or some slots, for example, determined by a higher layer). If the DCI has not been decoded or there is no match, the UE may be configured to perform a blind decoding attempt with a highest activity state.

[0571] In another representative embodiment, the UE may be configured to perform a blind decoding attempt with a high activity state if (e.g., only if) the DCI was not successfully decoded on the PDCCH (or a common PDCCH) or if the DCI was successfully decoded and a matching identity exists as described above. Otherwise, the UE may be configured to perform a blind decoding attempt with a low activity state.

[0572] In another representative embodiment, the UE may perform a blind decoding attempt due to a high activity state if (eg, only if) the DCI is successfully decoded and a matching identity is present as described above.

[0573] 9 is a flow diagram illustrating another representative method for power saving. The representative method may be performed by any device including a wireless transmit / receive unit (WTRU). The WTRU may include a transmitter, a receiver, and a processor coupled to the transmitter and receiver. The processor may be configured to monitor one or more control channels of a plurality of spectrum operating modes (SOMs) in operation 901. The processor may be configured to control the WTRU to operate in at least one power saving mode in at least one SOM in operation 902. The SOM (e.g., each SOM) may be associated with a control channel that carries information for allocating a set of spectrum blocks to the WTRU.

[0574] The processor may be further configured to execute different power saving modes at different times. The power saving modes may be determined based on a timing reference and a relationship. The timing reference and relationship may correspond to either a time-based triggering approach or a counting-based approach. The counting-based approach may manage time-related aspects of the power saving modes based on either a TTI duration, a minimum time between two scheduling opportunities, and other frame aspects.

[0575] The processor may be configured to control timing aspects of the power saving mode as a function of a frame duration associated with a given SOM.

[0576] The processor may be configured to control timing aspects of the power saving modes as a function of a scheduling opportunity or occasion associated with a given SOM.

[0577] The processor may be configured to perform power saving operations in at least one SOM, and to apply a single power saving mode to multiple SOMs (eg, all of the SOMs).

[0578] A processor for monitoring one or more control channels in a plurality of SOMs may be configured to monitor a primary control channel associated with a particular SOM. The processor may be further configured to receive SOM configuration information regarding the monitored primary control channel. The SOM configuration information may include any of the resource blocks, numerology, and / or duration of the numerology blocks associated with the SOM (e.g., each SOM).

[0579] The receiver may receive SOM configuration information from the network via radio resource control (RRC) signaling. The receiver may further receive an indication of a period for monitoring one or more SOM-specific control channels on the primary control channel. The receiver may further receive an indication of a discontinuous reception period (DRX) associated with the particular SOM on the primary control channel. The primary control channel may include information indicating or disclosing any of: (1) a DRX time to be applied to the particular SOM; (2) an indication for continuous control channel monitoring; (3) an active time to be applied to the particular SOM; and (4) a configuration / reconfiguration of a DRX timer and / or a control channel monitoring algorithm.

[0580] The processor may be configured to monitor the primary channel over a period of time. The processor may be configured to perform independent DRX per SOM. The processor may be configured to monitor a SOM-specific control channel based on the independent DRX. The receiver may receive a change in the DRX configuration of the first SOM from signaling received from the second SOM. The change in the DRX configuration may include any of: (1) a change in the DRX cycle, (2) a change in any of the DRX-related timer values, (3) a change in the offset of the DRX cycle, (4) an instruction to wake up, or (5) an instruction to start monitoring the control channel at a predetermined time.

[0581] The processor for monitoring the one or more control channels may be further configured to monitor the one or more control channels for a number N of scheduling opportunities out of every M scheduling opportunities. The processor may be further configured to determine the values ​​of M and N based on any of: (1) configuration by the network, (2) preconfigured values, (3) a logical channel whose data arrival triggered a scheduling request (SR), (4) a time-related requirement associated with the arrival of new data that triggered the SR, and / or (5) a SOM used to transmit the SR. The transmitter may be configured to transmit the SR.

[0582] FIG. 10 is a flow diagram illustrating another representative method for power conservation. The representative method may be performed by any device including a wireless transmit / receive unit (WTRU). The WTR may comprise a transmitter, a receiver, and a processor coupled to the transmitter and the receiver. The processor may be configured to determine a set of resources as a function of a processing state of the WTRU in operation 1001. The processor may be further configured to monitor one or more control channels using the determined set of resources. The processor may be further configured to decode at least one control channel element on the control channel in operation 1002. The processor may be configured to monitor the one or more control channels with a first timing granularity while in a first processing state. The processor may be configured to enable at least one of a first particular numerology, a particular set of scheduling occasions, or a HARQ timeline on the control channel in the first processing state.

[0583] At operation 1003, the processor may be configured to determine that the WTRU is in a first processing state, decode downlink control information (DCI) in the first processing state on a set of control channel resources using the at least one parameter, and determine to transition from the first processing state to a second processing state based on the decoding of the DCI. The set of control channel resources may include at least one of a common search space, a common control channel, or a physical downlink control channel. The at least one parameter may be a function of at least one identifier used for processing control. The at least one parameter may indicate at least one of an RNTI, a time symbol, a set of slots or minislots, a set of physical resource blocks, a set of resource element groups, or a set of control channel elements.

[0584] The processor may be further configured to determine configuration information for the WTRU, such that the configuration information indicates at least one of at least one identifier, at least one indexing value, or a radio network identifier (RNTI) to use for decoding the one or more DCIs.

[0585] The processor may be further configured to determine, based on successful decoding of the DCI, that the DCI includes at least one identifier. The processor may be further configured to determine that the at least one identifier included in the DCI matches at least one identifier indicated in the configuration information for the WTRU. The decision to transition from the first processing state to the second processing state may be further based on a determination that the at least one identifier included in the DCI matches at least one identifier indicated in the configuration information for the WTRU.

[0586] The processor may be configured to decode the DCI for an identifier (e.g., each identifier) ​​of a first processing state on a set of control channel resources using at least one parameter associated with the identifier. The first processing state may correspond to a lower processing level, and the second processing state may correspond to a higher processing level. The first processing state and the second processing state may be associated with a number of decoding attempts of the DCI.

[0587] The processor may be configured to attempt to decode one or more DCI based on a processing level associated with the processing state to which it is transitioned.

[0588] The receiver may be configured to receive a signal from the network that includes configuration information for the WTRU.

[0589] The processor may be configured to determine a pattern. The processor may be further configured to decode at least one control channel element on the control channel based on the determined pattern. The processor may be further configured to decode at least one control channel element on the control channel using a scheduling opportunity and / or occasion based on the determined pattern. The processor may be further configured to decode at least one control channel element on the control channel using a different set of control channel resources, CCEs, and / or search space from the scheduling opportunity and / or occasion based on the determined pattern. The processor may be further configured to decode at least one control channel element on the control channel using a different aggregation level from the scheduling opportunity and / or occasion based on the determined pattern. The processor may be further configured to decode at least one control channel element on the control channel using a different set of one or more downlink control information (DCI) from the scheduling opportunity and / or occasion based on the determined pattern. The pattern may be associated with a processing state of the WTRU. The processor may be further configured to change to a different pattern when changing to a different processing state of the WTRU.

[0590] FIG. 11 is a flow diagram illustrating another representative method for power saving. The representative method may be performed by any device including a network entity, a Node B, an evolved Node-B (eNode-B), etc. The evolved Node-B (eNode-B) may include a transmitter, a receiver, and a processor coupled to the transmitter and the receiver. The processor may be configured to allocate a set of control channel resources to be used by a wireless transmit / receive unit (WTRU) to decode at least one downlink control information (DCI) in operation 1101. The processor may be configured to allocate configuration information to the WTRU in operation 1102. The configuration information may indicate at least one identifier, each identifier being allocated to the WTRU and other WTRUs to coordinate processing states of the WTRU and other WTRUs. The transmitter may be configured to transmit a signal to the WTRU indicating the set of control channel resources in operation 1103, and transmit another signal including the configuration information to the WTRU in operation 1104. The configuration information may further indicate at least one of: at least one indexing value, or a radio network identifier (RNTI) to be used by the WTRU to decode the one or more DCIs. The set of control channel resources may include at least one of a common search space, a common control channel, and / or a physical downlink control channel.

[0591] Although features and elements are described above in certain combinations, one skilled in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. Furthermore, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). Software and associated processors may be used to implement a radio frequency transceiver for use in the WTRU 102, UE, terminal, base station, RNC, or any host computer.

[0592] Furthermore, in the embodiments described above, reference is made to processing platforms, computing systems, controllers, and other devices that contain processors. These devices may contain at least one central processing unit ("CPU") and memory. In accordance with the practices of those skilled in the art of computer programming, references to acts and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer-executed," or "CPU-executed."

[0593] Those skilled in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits, which may cause a resulting transformation or reduction of the electrical signals and the retention of the data bits in memory locations within the memory system, and other processing of the signals, thereby reconfiguring or otherwise altering the operation of the CPU. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the representative embodiments are not limited to the platforms or CPUs mentioned above, and that other platforms and CPUs may support the methods provided.

[0594] The data bits may be maintained on a computer readable medium, including magnetic disks, optical disks, and any other volatile mass storage system (e.g., random access memory ("RAM")) or non-volatile mass storage system (e.g., read only memory ("ROM")) readable by a CPU. The computer readable medium may include cooperating or interconnected computer readable media, which may reside solely on a processing system or distributed among multiple interconnected processing systems, which may be local or remote to the processing system. It is understood that representative embodiments are not limited to the memories discussed above, and that other platforms and memories may support the methods described.

[0595] In an example embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0596] Few distinctions remain between hardware and software implementations of aspects of the system. The use of hardware or software is generally (though not always, as in certain scenarios the choice between hardware and software can be significant) a design choice that represents a cost vs. efficiency tradeoff. There may be a variety of media (e.g., hardware, software, and / or firmware) in which the processes and / or systems and / or other techniques described herein may be performed, and the preferred media may change with the scenario in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer would choose a primarily hardware and / or firmware medium. If flexibility is paramount, the implementer would choose a primarily software implementation. Alternatively, the implementer would choose some combination of hardware, software, and / or firmware.

[0597] The foregoing detailed description has illustrated various embodiments of devices and / or processes through the use of block diagrams, flow charts, and / or examples. To the extent that such block diagrams, flow charts, and / or examples contain one or more functions and / or operations, it will be understood by those skilled in the art that each function and / or operation in such block diagrams, flow charts, or examples may be implemented individually and / or collectively by a wide range of hardware, software, firmware, or virtually any combination thereof. Suitable processors include, by way of example, general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors in association with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), application specific standard products (ASSPs), field programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), and / or state machines.

[0598] Although features and elements are provided above in specific combinations, one skilled in the art will appreciate that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited with respect to the specific embodiments described in this application, which are intended as examples of various aspects. As will be apparent to those skilled in the art, numerous modifications and variations may be made without departing from its spirit and scope. No element, act, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly provided as such. In addition to those enumerated herein, functionally equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to be included within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that the present disclosure is not limited to any particular method or system.

[0599] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the terms "station" and its abbreviation "STA", "user equipment" and its abbreviation "UE" when referenced herein may mean (i) a wireless transmit and / or receive unit (WTRU), such as those described below, (ii) any of several embodiments of a WTRU, such as those described below, (iii) a wireless-enabled and / or wired-enabled (e.g., tetherable) device configured to have, among other things, some or all of the structure and functionality of a WTRU, such as those described below, (iii) a wireless-enabled and / or wired-enabled device configured to have less than all of the structure and functionality of a WTRU, such as those described below, or (iv) the like. Details of an example WTRU, which may represent any UE described herein, are provided below with reference to Figures 1-5.

[0600] In certain representative embodiments, some portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated forms. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein may be equivalently implemented in integrated circuits, in whole or in part, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing circuitry and / or writing software and / or firmware code is well within the skill of those skilled in the art in light of the present disclosure. Furthermore, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed in various forms as a program product, and that the exemplary embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).

[0601] The subject matter described herein may at times depict different components contained within or connected to different other components. It should be understood that such depicted architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. In a conceptual sense, any configuration of components that achieve the same functionality is effectively "associated" such that a desired functionality may be achieved. Thus, any two components herein that are combined to achieve a particular functionality may be considered to be "associated" with each other such that a desired functionality is achieved, regardless of architecture or intermediate components. Similarly, any two components so associated may also be considered to be "operably connected" or "operably coupled" with each other to achieve a desired functionality, and any two components that can be so associated may also be considered to be "operably coupled" with each other to achieve a desired functionality. Specific examples of operably coupleable include, but are not limited to, physically matable and / or physically interacting components, and / or wirelessly interactable and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.

[0602] With respect to the use of substantially any plural and / or singular terms herein, one of ordinary skill in the art may convert from the plural to the singular and / or from the singular to the plural as appropriate to the context and / or application. The various singular / plural permutations may be expressly explained herein for ease of understanding.

[0603] In general, it will be understood by those skilled in the art that the terms used herein, and particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including, but not limited to," the term "having" should be interpreted as "having at least," the term "including" should be interpreted as "including, but not limited to," etc.). It will be further understood by those skilled in the art that if a specific number of recitations of an introduced claim are intended, such intent will be explicitly set forth in the claim, and in the absence of such recitation, no such intent exists. For example, where only one item is intended, the term "single" or similar language may be used. As an aid in understanding, the following appended claims and / or description herein may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed as implying that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim containing such an introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes an introductory phrase such as "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be construed to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. Moreover, even when a specific number of recitations of an introduced claim are explicitly recited, one of ordinary skill in the art will recognize that such recitation should be construed to mean at least the recited number (e.g., the plain recitation of "two recitations," without other modifiers, means at least two recitations, or more than two recitations).Moreover, in instances where a convention similar to "at least one of A, B, and C, etc." is used, such structures are generally intended in the sense that one of ordinary skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B and C together, etc.). In instances where a convention similar to "at least one of A, B, or C, etc." is used, such structures are generally intended in the sense that one of ordinary skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B and C together, etc.). It will be further understood by those skilled in the art that virtually all disjunctive words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B". Furthermore, the term "any of" following a list of multiple items and / or multiple categories of items, as used herein, is intended to include "any of," "any combination of," "any more of," and / or "any combination of more of," the items and / or categories of items, individually or together with other items and / or other categories of items. Furthermore, as used herein, the term "set" or "group" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero.

[0604] Furthermore, when features or aspects of the disclosure are described in terms of a Markush group, those skilled in the art will recognize that the disclosure is also described in terms of any individual members or subgroups of members of the Markush group.

[0605] As will be understood by those skilled in the art, for all purposes related to providing a written specification and the like, all ranges disclosed herein encompass all possible subranges and combinations of subranges. All ranges listed are readily recognizable as fully described and allowing for the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily broken down into a lower third, middle third, and upper third, etc. As will also be understood by those skilled in the art, all phrases such as "up to," "at least," "greater than," "less than," etc., refer to ranges that are inclusive of the recited numbers and can then be broken down into subranges as discussed above. Finally, as will be understood by those skilled in the art, a range includes each individual member. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to a group having 1, 2, 3, 4, or 5 cells, and so on.

[0606] Moreover, the claims should not be read as limited to the order or elements provided unless so stated. Moreover, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. ...

[0607] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC), or any host computer. The WTRU may be used with modules implemented in hardware and / or software, including software defined radios (SDRs), and other components, such as cameras, video camera modules, video phones, speakerphones, vibration devices, speakers, microphones, television transceivers, hands-free headsets, keyboards, Bluetooth modules, frequency modulation (FM) radio units, near field communications (NFC) modules, liquid crystal display (LCD) display units, organic light emitting diode (OLED) display units, digital music players, media players, video game player modules, Internet browsers, and / or any wireless local area network (WLAN) or ultra-wideband (UWB) modules.

[0608] Although the invention has been described with respect to a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In one embodiment, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

[0609] Moreover, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications may be made in the details, within the scope and range of equivalents of the claims, without departing from the invention.

[0610] Throughout this disclosure, those skilled in the art will understand that certain representative embodiments may be used in alternative embodiments or in combination with other representative embodiments.

[0611] Although features and elements are described above in certain combinations, one skilled in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. Furthermore, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). Software and associated processors may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0612] Furthermore, in the embodiments described above, reference is made to processing platforms, computing systems, controllers, and other devices that contain processors. These devices may contain at least one central processing unit ("CPU") and memory. In accordance with the practices of those skilled in the art of computer programming, references to acts and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer-executed," or "CPU-executed."

[0613] Those skilled in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the retention of the data bits in memory locations within the memory system, as well as other processing of the signals, that reconfigures or otherwise alters the operation of the CPU. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits.

[0614] The data bits may be maintained on a computer readable medium, including magnetic disks, optical disks, and any other volatile mass storage system (e.g., random access memory ("RAM")) or non-volatile mass storage system (e.g., read only memory ("ROM")) readable by a CPU. The computer readable medium may include cooperating or interconnected computer readable media, which may reside solely on a processing system or distributed among multiple interconnected processing systems, which may be local or remote to the processing system. It is understood that representative embodiments are not limited to the memories discussed above, and that other platforms and memories may support the methods described.

[0615] No element, act, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly described as such. Furthermore, as used herein, the article "a" is intended to include one or more items. When only one item is intended, the term "a" or similar language is used. Furthermore, the term "any of" following a list of multiple items and / or multiple categories of items, as used herein, is intended to include "any of," "any combination of," "any plurality of," and / or "any combination of a plurality of," of the items and / or categories of items, individually or together with other items and / or other categories of items. Furthermore, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "number" is intended to include any number, including zero.

[0616] Moreover, the claims should not be read as limited to the described order or elements unless so stated. Moreover, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. 112, sixth paragraph, and any claim without the term "means for" is not so intended.

[0617] Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), an application specific standard part (ASSP), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and / or a state machine.

[0618] Although the invention has been described with respect to a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In one embodiment, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

[0619] Moreover, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications may be made in the details, within the scope and range of equivalents of the claims, without departing from the invention.

Claims

1. 1. A wireless transmit / receive unit (WTRU), comprising: A processor, a memory, and a transceiver, the processor and the transceiver comprising: receiving configuration information identifying a plurality of groups of search spaces associated with a control resource set, a first group of the search spaces including a first number of search spaces and associated with a first index, and a second group of the search spaces including a second number of search spaces and associated with a second index; monitoring the first group of the search space for a first physical downlink control channel (PDCCH) transmission according to the configuration information; receiving the first PDCCH transmission via the monitored first group of the search space, the first PDCCH transmission including a particular type of Downlink Control Information (DCI), the DCI including information indicating the index associated with the second group of the search space for monitoring by the WTRU for a second PDCCH transmission; monitoring the second group of the search space for the second PDCCH transmission according to the DCI; transmitting the second PDCCH via the monitored second group of the search space. It is configured as follows: The WTRU, wherein the processor and the transceiver are configured to monitor only one of the first group and the second group of the search space at a time.

2. 2. The WTRU of claim 1, wherein the processor, memory, and transceiver are configured to monitor the first group of the search space for the first PDCCH transmission using either 1) the control resource set or 2) a type of signaling structure.

3. the processor, the memory, and the transceiver; receiving configuration information indicating a time period; monitoring the second group of the search space for the second PDCCH transmission during the time period; transitioning to the first group of monitors of the search space after the expiration of the time period; The WTRU of claim 1 , configured to:

4. 2. The WTRU of claim 1, wherein the processor, memory, and transceiver are configured to determine to transition to monitoring the second group of the search space according to a time at which the first PDCCH transmission is received.

5. 2. The WTRU of claim 1, wherein the processor, memory, and transceiver are configured to transition from monitoring the first group of the search space to monitoring the second group of the search space for the second PDCCH transmission based on a predetermined or statically defined time from when the DCI is received.

6. The WTRU of claim 1 , wherein the DCI includes information indicating a processing state of the WTRU.

7. The WTRU of claim 6, wherein the processing state relates to actions of the WTRU in at least one of: 1) control channel processing, 2) spectral bandwidth processing, 3) beam management and processing, 4) reference signal processing, 5) hybrid automatic repeat request (HARQ) timing operation, 6) framing processing, 7) timing operation, or 8) logical channel properties and configuration.

8. The WTRU of claim 1 , wherein the control resource set comprises any of one or more control channel elements, one or more of the search spaces, or one or more aggregation levels.

9. The WTRU of claim 1 , wherein the DCI is included in a radio resource control (RRC) message.

10. The WTRU of claim 1 , wherein the first number and the second number are different.

11. 1. A method performed by a wireless transmit / receive unit (WTRU), comprising: receiving configuration information identifying a plurality of groups of search spaces associated with a control resource set, a first group of the search spaces including a first number of search spaces and associated with a first index, and a second group of the search spaces including a second number of search spaces and associated with a second index; monitoring the first group of the search space for a first physical downlink control channel (PDCCH) transmission according to the configuration information; receiving the first PDCCH transmission via the monitored first group of the search space, the first PDCCH transmission including a particular type of Downlink Control Information (DCI), the DCI including information indicating the index associated with the second group of the search space for monitoring by the WTRU for a second PDCCH transmission; monitoring the second group of the search space for the second PDCCH transmission in accordance with the DCI; transmitting the second PDCCH over the monitored second group of the search space; and Including, The method, wherein the WTRU monitors only one of the first group and the second group of the search space at a time.

12. 12. The method of claim 11, wherein monitoring the first group of the search space for the first PDCCH transmission uses either 1) the control resource set or 2) a type of signaling structure.

13. receiving configuration information indicating a time period; monitoring the second group of the search space for the second PDCCH transmission during the time period; transitioning to the first group of monitors of the search space after the expiration of the time period; The method of claim 11 further comprising:

14. The method of claim 11 , further comprising: determining to transition to monitoring the second group of the search space according to a time at which the first PDCCH transmission is received.

15. 12. The method of claim 11, further comprising: transitioning from monitoring the first group of the search space to monitoring the second group of the search space for the second PDCCH transmission based on a predetermined or statically determined time from when the DCI is received.

16. The method of claim 11 , wherein the DCI includes information indicating a processing state of the WTRU.

17. 17. The method of claim 16, wherein the processing state relates to actions of the WTRU in at least one of: 1) control channel processing; 2) spectral bandwidth processing; 3) beam management and processing; 4) reference signal processing; 5) Hybrid Automatic Repeat Request (HARQ) timing operations; 6) framing processing; 7) timing operations; or 8) logical channel properties and configurations.

18. 12. The method of claim 11, wherein the control resource set comprises any of one or more control channel elements, one or more of the search spaces, or one or more aggregation levels.

19. The method of claim 11 , wherein the DCI is included in a radio resource control (RRC) message.

20. The method of claim 11 , wherein the first number and the second number are different.

Images