EP4666776A1

EP4666776A1 - Methods for discontinuous cell transmission and reception and scheduling request

Info

Publication number: EP4666776A1
Application number: EP24711080.2A
Authority: EP
Inventors: Faris ALFARHAN; Paul Marinier; Jaya Rao; Ananth KINI; Erdem Bala; Moon Il Lee
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2023-02-13
Filing date: 2024-02-13
Publication date: 2025-12-24
Also published as: TW202433989A; JP2026506666A; CN120937469A; KR20250147691A; WO2024173328A1; AU2024220330A1

Abstract

A method performed by a UE includes receiving a first and second SR configuration, receiving a cell-DTX/cell-DRX configuration, transmitting a SR to the serving cell such that if the first SR configuration is used, the UE transmits a first SR on a first PUCCH occasion of the first SR configuration that occurs during a first cell DRX active duration, and if an uplink grant is not received after at least one cell DTX active duration has occurred after the first SR transmission, the UE transmits a second SR on a second PUCCH occasion of the first SR configuration that occurs during a second cell DRX active duration. If the second SR configuration is used, the UE transmits the first SR on a first PUCCH occasion of the second SR configuration independently of the cell DRX active duration, and if an uplink grant is not received, the WTRU transmits the second SR on a second PUCCH occasion of the second SR configuration independently of the cell DTX active duration.

Description

METHODS FOR DISCONTINUOUS CEUU TRANSMISSION AND RECEPTION AND SCHEDULING REQUEST

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of US provisional patent application No. 63/445,027 filed 13 February⁷ 2023, which is incorporated by reference herein in its entirety.

BACKGROUND

[0002] 3GPP RAN has concluded a study item on network energy savings for Rel-18. The motivation is to study enhancements enabling the network to minimize its power consumption from transmission and reception. Such minimization is beneficial for reducing operational costs and environmental sustainability. The study item was approved and resulted in anew Rel-18 work item on network energy saving.

[0003] Compared to earlier systems, the design of NR of Rel-15 is very efficient from the perspective of minimizing transmissions from the network when there is no data. For example, always-on cell-specific reference signal (CRS) is not used in NR. However, there is still potential for energy consumption reduction.

[0004] For example, the network still consumes energy when not transmitting from other activities such as baseband (digital) processing for reception or beamforming. Such ‘‘idle” power consumption is not negligible in dense networks even when no UE is served during a given period. If the network could turn off these activities when not transmitting to a UE, energy consumption could be reduced.

[0005] Unlike LTE, NR does not require transmission of always-on synch or reference signals and supports adaptable bandwidth and MIMO capabilities. While initial work in R18 is expected to not impact legacy UEs, it’s anticipated that such adaptation of network resources will enable greater efficiency in operating newer deployments and later generations.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein: [0007] FIG. 1 A is a system diagram illustrating an example communications system; [0008] FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0009] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;

[0010] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0011] FIG. 2 depicts an adaptation of a scheduling request procedure in accordance with features of the disclosure;

[0012] FIG. 3 depicts another adaptation of a scheduling request procedure in accordance with features of the disclosure; and

[0013] FIG. 4 depicts a flow diagram in accordance with features of the disclosure.

DETAILED DESCRIPTION

[0014] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry⁷ out any operation, process, algorithm, function, etc. and/or any portion thereof.

[0015] Example Communications System

[0016] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.

[0017] FIG. 1A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 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), singlecam er FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0018] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104/113, a core network (CN) 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 1 12, though 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. any of which may be referred to as a "station" and/or a "STA", may be configured to transmit and/or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0019] The communications systems 100 may also include a base station 114a and/or 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, e.g.. to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 1 10, and/or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB). a site controller, an access point (AP). a wireless router, and the like. While the base stations 114a, 114b are each depicted 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.

[0020] The base station 114a may be part of the RAN 104/113, 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 on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 1 14a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

[0021] 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 communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0022] More specifically, as noted above, the communications 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, and the like. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c 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).

[0023] In an 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) and/or LTE- Advanced Pro (LTE-A Pro). [0024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0025] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a. 102b, 102c may be characterized by multiple t pes of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).

[0026] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 I X, 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), and the like.

[0027] The base station 114b in FIG. 1 A may be a wireless router, Home Node-B, Home eNode- B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In an 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 an 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 an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE- A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115.

[0028] The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability- requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling. Internet connectivity-, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113, which may be utilizing an NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0029] The CN 106/115 may also serve 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 circuit-sw itched telephone netw orks that provide 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 the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/114 or a different RAT.

[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., 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. 1 A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology⁷.

[0031] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120. a transmit/receive element 122, a speaker/mi crophone 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/or other elements/peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0032] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality⁷ of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller. Application Specific Integrated Circuits (ASICs). Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. 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. While FIG. IB 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 together, e.g., in an electronic package or chip.

[0033] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR. UV, or visible light signals, for example. In an embodiment, the transmit/receive element 122 may be configured to transmit and/or 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.

[0034] Although the transmit/receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit/receive elements 122. For example, the WTRU 102 may employ MIMO technology⁷. Thus, in an 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.

[0035] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802. 11. for example.

[0036] The processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or 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. In addition, the processor 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory⁷ 132. The non-removable memory⁷ 130 may include random-access memory⁷ (RAM), readonly 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, and 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 a home computer (not shown).

[0037] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in 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, and the like.

[0038] The processor 118 may also be coupled to the 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 in lieu of, the 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 1 14a, 1 14b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by w ay of any suitable location-determination method while remaining consistent with an embodiment.

[0039] The processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity. For example, the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and/or augmented reality (VR/AR) device, an activity tracker, and the like. The elements/peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.

[0040] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0041] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b. and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0042] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though 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 an 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.

[0043] Each of the eNode-Bs 160a, 160b, and 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 (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0044] The CN 106 shown in FIG. 1C may include a mobility’ management entity (MME) 162, a serving gateway (SGW) 164. and apacket datanetwork (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator.

[0045] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S I interface and may serve 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 an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.

[0046] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0047] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0048] The CN 106 may facilitate communications with other networks. For example, the CN 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 CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b. 102c with access to the other networks 112. which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

[0049] Although the WTRU is described in FIGs. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [0050] In representative embodiments, the other network 112 may be a WLAN.

[0051] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.1 le DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.

[0052] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary' channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g.. only one station) may transmit at any given time in a given BSS.

[0053] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary' 20 MHz channel with an adj acent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0054] Very’ high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0055] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802. 1 laf and 802. 1 lah relative to those used in 802.1 In, and 802. 1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support meter type control/machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery' life above a threshold (e.g., to maintain a very long battery' life).

[0056] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.1 In, 802. 1 lac. 802.1 laf, and 802.1 lah, include a channel which may be designated as the primary’ channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA. from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, the primary channel may be 1 MHz wide for STAs (e.g., MTC ty pe devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary' channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority⁷ of the frequency bands remains idle and may be available.

[0057] In the United States, the available frequency bands, which may be used by 802. 1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802. 1 lah is 6 MHz to 26 MHz depending on the country code.

[0058] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0059] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example. gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b. 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology⁷. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology⁷. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c). [0060] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0061] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a. 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102a. 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a. 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a. 102b, 102c.

[0062] Each of the gNBs 180a, 180b, 180c 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 UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0063] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b. at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b. 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as sendees relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

[0065] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP -based. non-lP based, Ethernet-based, and the like.

[0066] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, e.g., to facilitate communications between the WTRUs 102a, 102b. 102c and IP-enabled devices. The UPF 184. 184b may perform other functions, such as routing and forw arding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0067] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In an embodiment, the WTRUs 102a, 102b. 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0068] In view of FIGs. 1A-1D, and the corresponding description of FIGs. 1A-1D, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 11 data, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/devices (not shown). The emulation devices maybe one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0069] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

[0070] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0071] Examples provided herein do not limit applicability of the subject matter to other wireless technologies, e.g., using the same or different principles as may be applicable.

[0072] As explained herein, a wireless transmit/receive unit (WTRU) may be an example of a user equipment (UE). Hence the terms UE and WTRU may be used with equal scope herein.

Terminology

[0073] The following terminology is used and can be assumed through the description below. 1. CSI: Channel state information, which may include at least one of the following: channel quality index (CQI), rank indicator (RI), precoding matrix index (PMI), an LI channel measurement (e.g. reference signal received power (RSRP) such as Ll-RSRP, or signal-to- interference-plus-noise ratio (SINR)), CSI Reference Signal (CSI-RS) resource indicator (CRI), synchronization signal/physical broadcast channel (SS/PBCH) block resource indicator (SSBRI), layer indicator (LI) and/or any other measurement quantity measured by the UE from the configured CSI-RS or SS/PBCH block.

2. UCI: Uplink control information, which may include: CSI, Hybrid Automatic Repeat Request (HARQ) feedback for one or more HARQ processes, Scheduling request (SR), Link recovery request (LRR), configured grant UCI (CG-UCI) and/or other control information bits that may be transmitted on the physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH).

3. Channel conditions: any conditions relating to the state of the radio/channel, which may be determined by the UE from: a UE measurement (e.g., Ll/SINR/RSRP, CQI/ modulation coding scheme (CQI/MCS), channel occupancy, Received Signal Strength Indicator (RSSI), power headroom, exposure headroom), L3/mobility-based measurements (e.g. RSRP. Reference Signal Received Quality (RSRQ), s-measure), an Radio Link Monitoring (RLM) state, and/or channel availability in unlicensed spectrum (e.g. whether the channel is occupied based on determination of an listen before talk (LBT) procedure or whether the channel is deemed to have experienced a consistent LBT failure).

4. Physical random access channel (PRACH) resource: a PRACH resource (e.g., in frequency), a PRACH occasion (RO) (e g., in time), a preamble format (e.g., in terms of total preamble duration, sequence length, guard time duration and/or in terms of length of cyclic prefix) and/or a certain preamble sequence used for the transmission of a preamble in a random access procedure.

5. A property of scheduling information (e.g., an uplink grant or a downlink assignment) may include of at least one of the following: a frequency allocation; An aspect of time allocation, such as a duration; A priority; A modulation and coding scheme; A transport block size; A number of spatial layers; A number of transport blocks to be carried; A transmission configuration indication (TCI) state or sounding reference signal (SRS) resource indicator (SRI); A number of repetitions; Whether the grant is a configured grant type 1, type 2 or a dynamic grant.

6. An indication by downlink control information (DCI), or an indication, may include at least one of the following: An explicit indication by a DCI field or by radio network temporary identifier (RNTI) used to mask cyclical redundancy check (CRC) of the physical downlink control channel (PDCCH). An implicit indication by a property such as DCI format, DCI size, Coreset or search space, aggregation level, identity of first control channel resource (e.g., index of first control channel element (CCE)) for a DCI. where the mapping between the property and the value may be signaled by radio resource control (RRC) or medium access control (MAC). An explicit indication by a downlink (DL) MAC control element (CE).

[0074] In the description below, the terms network availability' state, cell discontinuous transmission (DTX) mode/configuration, or Network Energy Savings (NES) state may be used interchangeably.

Cell Discontinuous Transmission (DTX) and Cell Discontinuous Reception (DRX)

[0075] The gNB can currently use reduced downlink transmission/uplink reception activity' without an explicit cell DTX/DRX pattern with restrictions due to UE DRX configurations and any configured transmission/reception, e.g., common channels/signals. Currently connected mode DRX (C-DRX) is configured per UE. The alignment of the DRX cycles or offsets for different UEs can be done only via RRC. During UE DRX off period, the UE does not expect to monitor PDCCH, but it is allowed to initiate UL transmission according to the configured resources (e.g. using PUCCH, random access channel (RACH), scheduling request (SR), or CG-PUSCH). Aligning/Omitting of DRX patterns across multiple UE's can be achieved via gNB implementation.

[0076] Cell DTX/DRX aims at providing mechanisms informing UE whether the cell stays inactive. This may include enhancements to UE DRX configuration, e.g. to align/omit DRX cycles or start offsets of DRX, for UEs in connected mode or idle/inactive mode, potentially allowing longer opportunities for cell inactivity. During a cell DTX/DRX, the cell may have no transmission/reception or only keep limited transmission/reception. For example, the cell does not need to transmit or receive some periodic signals/channels, such as common channels/signals or UE specific signals/channels.

[0077] Cell DTX/DRX is applied to at least UEs in RRC_CONNECTED state. A periodic Cell DTX/DRX (i.e., active and non-active periods) can be configured by gNB via UE-specific RRC signaling per serving cell. Cell DTX/DRX mode can be activated/de-activated via dynamic L1/L2 signaling and UE-specific RRC signaling. Both UE specific and common L1/L2 signaling can be considered for activating/ deactivating the Cell DTX/DRX mode. Cell DTX and Cell DRX modes can be configured and operated separately (e.g., one RRC configuration set for DL and another for uplink (UL)). Cell DTX/DRX can also be configured and operated together. At least the following parameters can be configured per Cell DTX/DRX configuration: periodicity, start slot/offset, on duration. In one realization, Cell DTX indication could also be part of system information (SI) update or system information block (SIB) signaling. There can be a common time for all UEs to determine cell DTX status.

Network Availability States I Cell DTX mode I NES states

[0078] The UE may determine whether it can transmit or receive on certain resources depending on a network availability state, which implies the gNB's power savings status. An availability state may correspond to a network energy savings state, a cell DTX mode, a cell DRX mode, and/or a gNB activity level. An availability state can be uplink or downlink specific, and may change from symbol to symbol, slot to slot, frame to frame, or on longer duration granularity. The availability state may be determined by the UE or indicated by the network. An availability state can be, for example, "On", "DL and UL active", "UL only active”, “off¹, "reduced Tx power", "dormant", "micro sleep", "light sleep", or "deep sleep". Such states can be abstracted by network (NW) configuration parameters and/or values, and dynamic indication may point to the active availability state (e g. by DCI or MAC CE signaling). The "Off¹ availability state may imply that the gNB's baseband hardware is completely turned off. The "sleep" availability state may imply that the gNB wakes up periodically to transmit certain signals (e.g. presence signals, synchronization, or reference signals) or receive certain UL signals. In some availability states, some DL or UL resources are not available during certain periods of time, and this enables the network to turn off baseband processing and other activities. Some measurement resources (e.g. synchronous signal blocks (SSB)s or CSI-RS) may only be made available in certain availability states, including: RLM, beam failure detection (BFD), Radio Resource Management (RRM) measurements, CSI- RS feedback configuration, and/or a different power offset for CS1 feedback. Under certain conditions, the UE may further transmit a request to the network (wake-up request) to modify the availability state to a state for which resources that would satisfy⁷ UE requirements are available.

[0079] The UE may determine an availability state from reception of availability state indication from e.g. by L1/L2 signaling (e.g. a group common DCI or indication), or implicitly determine it form the reception of periodic DL signaling -or lack thereof.

[0080] The UE may determine if a resource is available for transmission/reception and/or measurements for the determined network availability⁷ state if it is applicable in the active availability state. In addition, the UE may also adapt its active C-DRX cycle, active spatial elements (e.g. antenna or logical ports), active Transmission / Reception Point (TRP)s, paging occasions as a function of the signaled or determined availability state. The UE may⁷ be configured with one or more sets of NES transmission and/or reception parameters per availability state, e.g. by broadcast or dedicated configuration signaling. The UE may apply the NES parameter set according to the determined or signaled availability state. The UE may apply one or more applicable configurations depending on the determined NES state. A set of NES parameter may include: a number of antenna ports, a C-DRX configuration, a measurement configuration (e.g. for RRM, RLM. and/or BFD), CSI feedback, a CSI-RS configuration, an SSB configuration, channel occupancy (CHO) or mobility candidates, a set of active TRPs.

[0081] An availability state may be applicable to at least one transmission, reception, or measurement resource. An availability state may be applicable to at least one time period such as a time slot or time symbol. An availability state may be applicable to a serving cell, a cell group, a frequency band, a bandwidth part, a TRP, a set of spatial elements, or a range of frequencies within a bandwidth part. For example, when an NES state changes in a cell, the UE may receive an availability⁷ state change indication indicating that this change is just for that cell, for all cells at the same frequency, or/and same radio access technology (RAT).

[0082] The UE may consider the active availability state associated with a cell, carrier. TRP. or frequency band to be "Off¹, "Deep sleep", or "Micro sleep" after reception of a DL signaling that changes the cell's or TRP's availability state. For example, the UE may receive a turn off command on broadcast signaling. RRC signaling, DCI (e.g. a group common DCI). or a DL MAC CE (e.g. indication part of PDSCH). The UE may determine an availability state from reception of availability state indication from e.g. by L1/L2 signaling (e.g. a group common DCI or indication) or broadcast signaling associated with an availability state. For example, an availability state change indication could also be part of SI update or SIB signaling (e.g. in a separate SIB that is not read by legacy UEs). There can be a common time for all UEs in the cell to determine availability state status.

[0083] The UE may implicitly assume a certain availability state associated with a cell, carrier, TRP, or frequency band (e.g. "Off, "deep sleep", "micro sleep" or dormant") from: reception of a paging message (e.g. paging DCI, paging PDSCH, or a paging related signal , i.e. Paging Early Indication (PEI)), The gNB DTX status (whether the gNB is in active time or an associated activity timer is running), lack of detection of a presence indication, the availability state of an associated cell, or measured channel conditions (s) being below -or a above- a threshold.

[0084] The UE may be configured to monitor an indication that may characterize the level of network activity (e.g. an availability state). The network activity may be associated with a gNB and/or a cell. The UE may assume the same availability state for all cells part of the same gNB, e.g. cells of the same MAC entity. The network activity indication (e.g. the presence indication) may include a channel (e.g., a PDCCH) and/or a signal (e.g., a sequence). The activity indication or the NES state change indication/ command may indicate the level of activity the UE may expect from the associated gNB and/or cell, e.g.. reduced activity. The activity indication may contain activity information of other gNBs/cells. The activity indication may be a PDCCH containing group common signaling. For example, the NW may transmit a group common DCI to a group of UEs (e.g. UEs in the serving cell) indicating a change of an activity state or activity level in UL and/or DL. The CRC of the PDCCH may be scrambled with a dedicated "activity indication RNTI or an NES-RNTI". A UE may be configured with at least one search space associated with the monitoring occasions of the activity⁷ indication PDCCH. The indication may include a go-to-sleep signal, e.g.. a predefined sequence. When UE detects this sequence, UE may expect a reduced activity level over a specific time duration. The UE may activate C-DRX for the period of time indicated. Alternatively, two sequences may be used to indicate regular activity and reduced activity.

[0085] The signaling within the PDCCH or the activity indication may contain at least one of the following:

1 . Expected activity level of the associated gNBs/cells over a specific time interval (e.g. an availability state). The activity levels may be predetermined and/or configured and may, for example, include of regular and reduced activity. The signaling may indicate the activity level. For example, bit ’T' may indicate regular activity and bit ”()" may indicate reduced activity.

2. For each activity level (e.g. availability state), transmission and reception attributes may be defined. For example, during reduced activity , UE may not be expected to monitor certain PDCCH search spaces (including all synchronization signals (SSs)), and/or receive a certain type of PDSCH (including all PDSCH), and/or transmit PUCCH/PUSCH, and/or perform certain measurements. The UE may start or stop monitoring PDCCH and/or TCI states associated with determined NES state, including PDCCH resources or TCI states associated with (de)activated TRPs or spatial elements.

3. A set of configurations may be associated with an activity level and may be used/applied when that activity level is indicated (e.g. an NES parameter set). For example, SS configurations, CSI reporting configurations, indices of transmitted SSBs, etc. Each set of configurations may

have an atribute associated with an activity level. For example, a tag that can be set to "reduced activity".

4. The time interval over which an activity level is assumed may be signaled in the PDCCH or part of the activity indication. a. The time interv al may be indicated using a bitmap where each bit in the bitmap may be associated with a specific duration, e.g., a slot or a frame. For example, bit "1" may indicate regular activity and bit "0" may indicate reduced activity on an associated frame. b. The time interv al may be indicated with a start time and length of interval. The start time may be defined; for example, it may be determined by adding a fixed offset to the time the indication is received. The length of the interval may be configured or signaled in the indication PDCCH.

5. The time interval over which an activity level is assumed may be predetermined. The UE may assume an interruption delay (or more generally a time till the NES state changes) after the NES state change command reception (e.g. after the last symbol or slot on which the command was received). The interruption time can be in absolute time, a number of symbols, or a number of slots.

[0086] The UE may determine that an uplink or downlink resource or signal is available for transmission/ reception and/or measurements for the determined network availability' state if it is applicable in the active availability state. The UE may determine that a subset of measurement resources and/or signals (e.g. SSBs, CSI-RS, tracking reference signal (TRS), positioning reference signal (PRS)) are not applicable in certain availability states. The UE may determine that a subset of uplink or downlink resources (e.g. PRACH, PUSCH, PUCCH) are not applicable in certain availability states. The UE may transmit some uplink signals only in a subset of NW availability states (e.g. SRS, pSRS, PRACH, UCI).

Possible Issues

[0087] Cell DTX and cell DRX can be configured separately and may not be aligned with each other or with the UE C-DRX, which may have impact on the UE. In a given On duration, the network may receive only, transmit only, and/or perform both. UE UL transmissions during cell DRX thus cause unnecessary interference in the network.

[0088] Many C-DRX timers that dictate "Active time" start after UL transmissions (e.g. after SR, RACH, or CG transmissions) though the serving cell may in Cell DTX in the downlink direction only. Current specifications require the UE to perform unnecessary retransmissions of such UL signals, simply because the NW didn't get the chance to reply yet. Further, the UE is considered in C-DRX Active time after such transmissions, thus wasting battery. How to ensure the UE C- DRX active time and Cell DTX active periods are aligned? How to ensure the UE is not monitoring PDCCH when not needed? How to ensure the UE is not retransmitting UL signals even if the first transmission was received correctly but NW didn't get the chance to reply yet?

[0089] Further, UE DRX parameter and timers (e g. On duration and other timers) may not be aligned with the active cell DTX/cell DRX), thus causing unnecessary batten consumption and unwarranted monitoring of DL channels. Another concern is that some SR occasions occur while the network is not receiving due to being in network energy saving state. Retransmission of SR may be wasteful of resources.

Issues Addressed

[0090] The following are proposed solution topics addressing the above issues. These solution topics are further discussed in the detailed descriptions that follow.

Adaptation of SR transmission in Cell DTX/DRX

A UE may be configured with a first SR configuration and a second SR configuration. Each SR configuration may be configured with a mapping to a set of logical channels (LCH)s. Each LCH or Data Radio Bearer (DRB) may be configured with a mapping to an SR configuration and/or an SR UE transmission behavior during Cell DTX and/or Cell DTX to adapt to SR transmission needs in a Cell DTX/DRX. This may address a concern that some SR occasions occur while the network is not receiving due to being in netw ork energy saving state. Further discussion is in the section below entitled “Cell DTX/DRX Impact on Scheduling Procedure”.

Definitions

[0091] The following are definitions or aspects of technologies that may be common to the several descriptions of embodiments/solutions to the issues defined hereinabove.

1. Cell DTX active period: duration of time over which a configured cell DTX pattern is active (e.g. periods of time during an On Duration periods of a Cell DTX pattern). UE may be predefined and to monitor PDCCH and other DL signals and channels during such time. This may be applicable only after a cell DTX configuration has been indicated by the NW to be activated.

2. Cell DTX inactive period: duration of time over which a configured cell DTX pattern is not active/inactive (e.g. periods of time outside periodic On Duration periods of a Cell DTX pattern). This may be applicable only after a cell DTX configuration has been indicated by the NW to be activated.

3. Cell DRX active period: duration of time over which a configured cell DRX pattern is active (e.g. periods of time during an On Duration periods of a Cell DRX pattern). UE may be predefined to be allowed to transmit UL signals and on UL channels during such time. This may be applicable only after a cell DRX configuration has been indicated by the NW to be activated.

4. Cell DRX inactive period: duration of time over which a configured cell DRX pattern is not active/inactive (e g. periods of time outside periodic On Duration periods of a Cell DRX pattern). This may be applicable only after a cell DRX configuration has been indicated by the NW to be activated.

5. Activated Cell DRX/DTX: A state of a configured cell DRX or Cell DTX pattern, where such state has been activated by L1/L2 DL signaling, RRC (re)-configuration, and/or cell common configurations, and has not been de-activated.

6. De-activated Cell DRX/DTX: A state of a configured cell DRX or Cell DTX pattern, where such state has been deactivated by L1/L2 DL signaling, RRC (re)-configuration, and/or cell common configurations.

7. Link between ax ailability state and Cell DTX/DRX. Herein, both terms may be used interchangeably. The UE may determine a cell DTX state implicitly from a determined active availability state, and vice-versa. The UE may determine a cell RTX state implicitly from a determined active availability state, and vice-versa.

8. The terms downlink configured grant (DL CG)" and Semi-persistent scheduling "(SPS)" may be used interchangeably herein.

[0092] A Cell DTX configuration may determine the Cell DTX active period as set of Cell DTX occasions. Such set may be parameterized by at least one of a duration between the start of successive occasions (CelLDTX-cycle). an offset (Cell-DTX-offset) and a duration (Cell-DTX- duration) for each Cell DTX occasion. For example, such parameters may be expressed in units of subframes (or milliseconds) in the same way as the long UE DRX cycle. In such case, a Cell DTX occasion may consist of a time period that starts in a subframe satisfying [SFN x 10 + subframe number] modulo (Cell-DTX-cycle) = (Cell-DTX-offset), where SFN is a system frame number, and ends (Cell-DTX-duration) later.

[0093] The Cell DTX configuration may also include a slot offset with respect to the start of the subframe in which a Cell DTX occasion starts. At least one parameter of the Cell DTX configuration may be signaled by RRC, MAC CE and/or DCI (UE-specific or UE-group common). [0094] The UE may be predefined or configured per Cell DTX and/or a Cell DRX configuration with one of the following parameters and behaviors:

1. One or more applicable configured grant or SPS configuration. For example, the UE may activate such configured grants upon activation of the cell DTX and/or cell DRX configuration. The UE may be configured per configured grant with whether the configured grant has priority over the configured cell DTX and/or cell DRX pattern (e.g. whether the UE can transmit or receive on a UL or DL CG during a cell DRX or cell DTX inactive period, respectively).

2. Whether the UE should monitor PDCCH for dynamic grants or dynamic DL assignments during the cell DTX inactive period.

3. Whether the UE is allowed to transmit on dynamic grants or configured grants

4. PRACH resources or PRACH resource configuration that may be -or may not be- applicable during a Cell DRX inactive period, or if a cell DRX configuration is activated.

5. SR/PUCCH resources or SR/PUCCH resource configuration that may be -or may not be- applicable during a Cell DRX inactive period, or if a cell DRX configuration is activated.

6. CSI-reporting or C Si-reporting resource configurations that may be -or may not be- applicable during a Cell DRX inactive period, or if a cell DRX configuration is activated.

7. SRS resources or SRS resource configuration that may be -or may not be- applicable during a Cell DRX inactive period, or if a cell DRX configuration is activated.

[0095] The UE may be configured with multiple cell DRX and/or cell DTX configurations simultaneously in a given serving cell. The UE may be configured with a primary or a default cell DTX and/or cell DRX configuration, which the UE may apply by default. Upon reception of signaling activating one cell DTX and/or cell DRX configuration, the UE may deactivate another one (or all other ones). Upon reception of signaling deactivating one cell DTX and/or cell DRX configuration, the UE may activate another one or activate a default cell DTX/DRX configuration. Upon expiry of a timer, the UE may fallback to the default cell DRX and/or cell DTX configuration. The UE may reset such timer upon reception of DL signaling or data or an indication from the NW to remain in a given non-default cell DTX or cell DRX state.

[0096] Cell DTX can be assumed/configured by the UE per channel, DL signals (e.g. including PDCCH, RS. PDSCH etc), per cell, per channel type, and/or per signal type. Cell DRX can be assumed/configured by the UE per channel, UL signals (e.g. PRACH, PUSCH, PUCCH, SRS, wake up signal (WUS)), or per cell, per channel ty pe, and/or per signal type.

[0097] Whether the UE prioritizes a configured Cell-DRX pattern vs. the UE-specific channel / signals configuration can be predefined, configured, or determined as a function of: the UE capability, data priority or latency, and/or the control signaling/info type. One example of a UE Signal or channel that may have priority to override a configured cell DRX pattern is a CG transmission, SR transmission, or transmission of a cell WUS.

Cell DTX/DRX Impact on Scheduling Procedure SR Transmission During Cell DTX/DRX [0098] FIG. 2 and 3 depict how the UE can adapt a scheduling request procedure to ensure that a SR is transmitted during occasions while the network is in an active state.

[0099] Depending on the UE capability, type of data arrival, and/or configured parameters, the UE may follow a first SR UE transmission behavior during cell DTX and/or cell DRX vs. a second behavior. For example, a UE capable of transmission of high priority data, Extended Reality (XR) data, low latency data (e.g. by configuration or activation of such services or Data Radio Bearers (DRB)s associated with such services) may follow a first SR transmission behavior during cell DTX/DRX, while an eMBB UE not supporting active transmission of latency critical data may follow a second UE behavior for SR transmission during cell DTX/DRX. The first and second SR transmission behaviors are described herein. An SR here in can be transmitted on PUCCH or multiplexed on PUSCH.

[0100] A UE may be configured with a first SR configuration and a second SR configuration. Each SR configuration may be configured with a mapping to a set of LCHs. Each LCH or DRB may be configured with a mapping to an SR configuration and/or an SR UE transmission behavior during Cell DTX and/or Cell DRX. Each LCH or DRB may be configured with a flag or a prionty index such that SR triggered by such LCH are transmitted using the first SR UE transmission behavior vs. the second SR transmission behavior during cell DTX/DRX. Configuration of the second SR transmission behavior may be implied by the UE from the lack of configuration of the first SR transmission behavior.

[0101] If the triggered SR is mapped to the first SR configuration or triggered by LCHs configured for the first SR transmission behavior or the SR is triggered by a UE is of a capability supporting transmission of the first SR transmission behavior during cell DTX/DRX -or a related service-, the UE may transmit the SR on the next applicable PUCCH occasion, possibly from the configured first SR configuration, even if the cell DTX and/or cell DRX pattern is in the inactive period (i.e. outside of the cell DTX on duration and/or outside of the cell DRX on duration). Further, the UE may monitor PDCCH immediately following the SR transmission while an SR is pending, even if the cell DTX pattern is in the inactive period.

[0102] If the triggered SR is mapped to the second SR configuration or triggered by LCHs configured for the second SR transmission behavior -or LCHs not configured for the first behavior- or the SR is triggered by a UE is not of a capability supporting transmission of the first SR transmission behavior during cell DTX/DRX -or a related service-, the UE may perform at least one of the following for the SR (re)-transmission occasion selections: 1. UE may transmit the SR on the next applicable PUCCH occasion, possibly from the second SR configuration -if configured-, possibly only if the SR transmission occasion overlaps with the cell DRX active period

2. If the prohibit timer has expired, the UE may retransmit the SR after a DTX active period has passed since the last SR transmission.

3. If the cell is in cell DTX, the UE may delay the SR transmission to select the SR/PUCCH transmission occasions that precedes -or overlaps with- the next cell DTX/DRX active period (e.g. a cell DTX or cell DRX on duration).

4. Following an SR transmission, the UE may delay PDCCH monitoring till the next DTX active period. If the UE is in C-DRX, the UE may consider itself in Inactive time (i.e. not in Active Time) even if an SR is pending, if the serving cell is in cell DTX inactive period (i.e. a cell DTX configuration has been activated but during the periods of time not overlapping with configured cell DTX on durations). The UE may apply such behavior per serving cell.

5. Following an SR transmission, the UE may delay the start of the SR prohibit timer if the serving cell is in cell DTX/DRX inactive period, until the cell DTX/DRX active period (i.e. the on duration) starts or just prior to it (e.g. if an SR occasion was selected just prior to the cell DTX/DRX on duration). For example, the UE may delay the start the prohibit if the SR occasion was transmitted during the UE C-DRX inactive timer, during cell DRX inactive period, during cell DTX inactive period. The UE may apply such behavior per serving cell.

6. The UE may be configured with an alternative (prolonged) value for the SR prohibit timer, which the UE may use when the serving cell is in cell DTX/DRX (e.g. if a cell DTX/DRX configuration is activated or during an cell DTX inactive period). For example, the UE may start the prohibit using the alternative configured value if the SR occasion was transmitted during the UE C-DRX inactive timer, during cell DRX inactive period, during cell DTX inactive period. The UE may apply such behavior per serving cell.

[0103] The UE may be configured with an alternative set of values for the following SR parameters for the UE to use if the serving cell is in cell DTX and/or cell DRX: sr-ProhibitTimer, sr-TransMax. Alternatively, the UE may be configured with one or more SR configurations to apply when the serving cell has activated cell DTX and/or cell DRX. If SR is triggered from such SR configuration, the UE may follow either the first or the second UE SR transmission behavior defined above.

[0104] In one method, if cell DTX is activated and the UE is in C-DRX, UE may select the SR occasion for PUCCH transmission such that prohibit timer is aligned with DTX active period from the set of available next SR occasions. [0105] FIG. 2 depicts an arrangement having two schedule request (SR) configurations which can be used by a UE in responding to the arrival of data. The UE may use the SR Configuration

A. In the timeline of SR Configuration A. a Cell DTX indication is received by the UE followed by the arrival of data in a cell DTX Active period. The UE may decide to uplink the received data and generate a TX SR using a previously configured SR timeslot followed by a SR prohibit timer duration to allow the serving cell to respond. If no response from the cell is received, such as a Grant/DCI, the TX SR is retransmitted at the next available SR occasion followed again by a SR prohibit timer duration.

[0106] This action can continue until the next available Cell DTX active period when the TX SR is retransmitted again. At this point the cell can respond by transmitting a Grant/DCI to the UE allowing the UE to uplink its data. This activity of sending multiple SR is shown in FIG. 2 at 206. One disadvantage in using this SR schedule configuration is that the UE can remain active for most of the multiple SR transmission time durations 206.

[0107] An alternative SR configuration B is shown in FIG. 2. In the timeline of SR Configuration

B, a Cell DTX indication is received by the UE followed by the arrival of data in a cell DTX Active period. The UE may decide to uplink the received data and generate a TX SR using a previously configured SR timeslot followed by a SR prohibit timer duration to allow' the serving cell to respond. In this instance, the SR prohibit timer is configured to have a duration in excess of the period between cell DTX active occasions. In the example of SR configuration B, the cell responds to the SR with a Grant/DCI within the SR prohibit timer duration shown at 208. This SR configuration B has the advantage of allowing the UE to save power by being active for a lesser amount of time than the SR configuration A.

[0108] FIG. 3 depicts another use of tw o or more different SR configurations which can be used by a UE in responding to the arrival of data. Similar to the SR Configuration A of FIG.6, the second SR configuration of FIG. 3 uses multiple SR attempts to request an upload grant when the cell may not be active. This is shown at 310 where an initial SR transmission (SR TX) using a PUCCH opportunity is made along with retransmission of the SR (SR ReTX) followed by a SR prohibit timer duration. Note that in the period of 310, the SR transmissions occur independently (not aligned) of the cell DRX Active periods. A retransmission of the SR and the SR prohibit timer duration is made which is also independent of the cell DRX timing. Finally, w'hen a cell DRX Active period is available, the last SR TX occurs at an SR opportunity which the cell receives in the DRX Active period and a Grant/DCI is subsequently received for the uplink data of the UE.

[0109] Also shown in FIG. 3 is a First SR Configuration. Using the First SR configuration, the UE receives an indication of the cell DRX and data arrives which can be uplinked to the cell. At an SR opportunity while the cell DRX is Active, the UE transmits a SR TX requesting an uplink grant. The SR TX is followed by a SR prohibit timer duration to allow the cell to respond. If no grant is received, then the UE waits until the next available DRX Active period to retransmit the SR (SR ReTX) for transmission of uplink data. After a subsequent SR prohibit timer duration, a grant/DCI may be received by the UE. This is shown in period 312 in FIG. 3. In FIG. 3, the first SR configuration has the same pow er saving advantage as the FIG. 2 SR Configuration B.

[0110] An example method for operation with two SR configurations, as in FIG. 3, can be described as follows:

1. The UE receives configuration of one or more LCHs where each is associated with one of a first SR configuration (not exceptional) or a second SR configuration (exceptional).

2. The UE receives configuration information indicating a Cell DRX configuration and a Cell DTX configuration, including one or more cell reception active and inactive durations and one or more cell transmission active and inactive durations, respectively.

3. The UE determines to send a scheduling request (SR) associated with a first LCH of the one or more LCHs.

4. In the event that the SR configuration associated with the first LCH is the first SR configuration, then the UE transmits a first SR transmission on a first PUCCH occasion of the first SR configuration that occurs during a first cell DRX active duration. If an UL grant is not received after at least one cell DTX active duration has occurred after the first SR transmission, the UE transmits a second SR transmission on a second PUCCH occasion of the first SR configuration that occurs during a second cell DRX active duration.

5. In the event that the SR configuration associated with the first LCH is the second SR configuration, then UE transmits the first SR transmission on a first PUCCH occasion of the second SR configuration without considering the Cell DRX configuration. If an UL grant is not received after a prohibit time period has ended, the UE transmits the second SR transmission on a second PUCCH occasion of the second SR configuration without considering the Cell DTX configuration.

[01U] FIG. 4 is a diagram outlining a flow 400 for a method, performed by a wireless transmit/receive unit (WTRU) UE.

[0112] At 405, the WTRU receives a configuration of one or more logical channels (LCH)s, wherein each LCH is associated with a first scheduling request (SR) configuration or a second SR configuration. At 410, the WTRU receives one or more of a cell discontinuous transmission (cell- DTX) configuration and a cell discontinuous receive (cell-DRX) configuration for a serving cell. At 415, the WTRU transmits a SR to the serving cell with a first LCH of the one or more LCHs. Options concerning the behavior of the WTRU include exercising steps 420 and 425, or steps 430 and 435.

[0113] At 420, on condition that the first SR configuration is associated with the first LCH, the WTRU transmits a first SR on a first physical uplink control channel (PUCCH) occasion of the first SR configuration that occurs during a first cell DRX active duration. At 425, if an uplink (UL) grant is not received after at least one cell DTX active duration has occurred after the first SR transmission, the WTRU transmits a second SR on a second PUCCH occasion of the first SR configuration that occurs during a second cell DRX active duration.

[0114] At 430, on condition that the second SR configuration is associated with the first LCH, the WTRU transmits the first SR on a first PUCCH occasion of the second SR configuration independently of the cell DRX active duration. At 435, if an UL grant is not received, the WTRU transmits the second SR on a second PUCCH occasion of the second SR configuration independently of the cell DRX active duration.

[0115] The method may also include the feature that the cell-DTX configuration includes a transmission active period and a transmission inactive period of the serving cell, and the cell-DRX configuration comprises a reception active period and a reception inactive period of the serving cell.

[0116] The method may also include the feature that WTRU using the second SR configuration triggers a new SR even if the WTRU has an available uplink (UL) grant and if the available grants are time-overlapping with the cell-DRX inactive period.

[0117] The method may also include the feature that the WTRU using the second SR configuration monitors a physical downlink control channel (PDCCH) while any SR is pending even if the cell-DTX pattern is in the inactive period.

[0118] The method may also include the additional step of on condition that a pending buffer status report / scheduling request (BSR/SR) is multiplexed on a physical uplink shared channel (PUSCH) payload, the WTRU cancels the BSR/SR if the transmitted payload occurred during a cell-DRX active period, an ACK is received, or reference received power (RSRP) is measured to be greater than a threshold value.

BSR Transmission During Cell DTX/DRX

[0119] The UE may apply the above procedure for the transmission of a PUSCH that has an SR multiplexed or a BSR multiplexed. For a pending BSR/SR multiplexed on a PUSCH payload, the UE may only cancel the BSR and/or the associated SR if at least one of the following is satisfied: 1. The transmitted pay load was during a cell DRX on duration. 2. The UE has received DL signaling containing HARQ-ACK feedback as ACK for such payload, i.e. part of a DFI or a DCI signaling HARQ ACK feedback.

3. The UE has received another grant using the same HARQ process ID with an NDI toggled.

4. The UE has received an indication by DCI indicating the reception of the payload.

5. The UE has received a grant for transmission of new UL data (using the same or a different HARQ process ID).

6. The UE has received a DL signal or channel (e.g. PDSCH scheduling)

7. The UE has determined HARQ-ACK feedback as ACK for such payload.

[0120] The UE may be configured or predefined to transmit PUSCH containing BSR MAC CE only on a subset of CG occasions (e.g. a preconfigured pattern of PUSCH occasion). The UE may (re)start the BSR retx timer and/or the BSR periodic timer once BSR is transmitted, once BSR is transmitted on such subset of CG occasions, and/or after a cell DTX active period has elapsed since the BSR transmission.

[0121] The UE may transmit PUSCH containing BSR and/or multiplex a BSR MAC CE on a PUSCH resource if one or more of the following conditions is satisfied:

1. The PUSCH occasion that overlaps wi th cell DRX active period.

2. The UE has received an SSB and/or reference signal prior to the transmission of the BSR for the purpose of channel estimation, beam pair establishment, selecting a proper SRI for the CG transmission.

3. The UE has made a measurement of one or more channel condition above a threshold. For example, the UE has measured an SSB or CSI-RS above a threshold (e g. an RLM or BFD related channel satisfaction threshold) or the BLER is less than a threshold.

4. The PUSCH occasion is not more than x milliseconds or slots away from the next cell DTX active period or anticipated PDCCH monitoring occasion.

5. The BSR is of a certain type (e.g. regular, padding, or periodic)

6. The BSR reports data from a certain LCH or LCG (which can be configured or predefined) or data of a certain configured priority index.

[0122] For a triggered pending BSR, the UE may select which CG (or PUSCH) occasion to multiplex it on based on whether one or more of the above conditions is satisfied.

[0123] If a regular pending BSR has been transmitted but not cancelled, the UE may trigger a new BSR upon new data arrival even if the priority of new data is not higher than the highest priority data in the transmitted pending BSR, possibly additionally conditioned on: the data volume of new data arrival being above a threshold, the cell DRX active period overlapping on an available PUSCH resource on which the newly triggered BSR can be multiplexed, and/or the newly arrived data is from a certain subset of DRBs/LCHs/LCGs or associated LCH priorities.

[0124] The UE may trigger another SR/BSR if the UE hasn't received an additional grant and/or scheduling since the transmission of the BSR, the CG timer for the HARQ process associated with the TB on which the BSR MAC CE has expired, and/or a CG retransmission timer has expired.

[0125] The UE may be configured with an alternative set of values for the following parameters for the UE to use if the serving cell is in cell DTX and/or cell DRX: periodicBSR-Timer; retxBSR- Timer; logicalChannelSR-DelayTimerApphed; logicalChannelSR-DelayTimer; logical Channel SR-Mask; logicalChannelGroup. For example, upon activation of cell DRX and/or cell DTX, the UE may apply the alternative values configured for such parameters.

Logical Channel Prioritization (LCP) Specific Cell DRX Restrictions

[0126] Configuration of a LCP multiplexing restriction such that the UE can multiplex a subset of LCHs can be multiplex on resources that don't overlap with cell DRX active period.

[0127] The UE may be configured per LCH or DRB with LCP logical channel selection restrictions or rules relating to uplink data transmission during Cell DRX active period, Cell DRX inactive period, and/or during Cell DRX is activated (i.e. after receiving Cell DRX activation period). For example, the UE may be configured such that data from LCHs A and B are allowed to be multiplexed on grants that overlap with cell DRX inactive periods. For a grant during cell DRX inactive period, if the UE has buffered data from LCHs A and C, the UE is allowed to multiplex and transmit data from LCHs A only for such grant.

[0128] The UE may be configured or predefined with rules per SRB (or SRB LCHs). MAC CE (or all MAC CEs) relating to uplink data transmission during Cell DRX active period, Cell DRX inactive period, and/or during Cell DRX is activated (i.e. after receiving Cell DRX activation period). For example, the UE may be predefined or configured such that C-RNTI, BSR or PHR MAC CEs are allowed during Cell DRX inactive periods while others are not allowed to be transmitted until Cell DRX active period. In another example, the UE may be predefined with a subset of SRBs or UL control channels that can be transmitted during cell DRX inactive/active periods (e.g. which SRB LCHs).

[0129] The UE may be configured with a configuration relating to whether the UE is allowed to transmit uplink data and/or signals during Cell DRX active period. Cell DRX inactive period, and/or during Cell DRX is activated (i.e. after receiving Cell DRX activation period). Such configuration can be configured by RRC signaling and/or SIB signaling. The UE may determine such configuration from the UE's capability or a capability related configuration. [0130] In one example embodiment, a method for Adaptation of SR Transmission in Cell DTX/DRX as disclosed in the section above entitled “Cell DTX/DRX Impact on Scheduling Procedure / SR Transmission During Cell DTX/DRX” may include the features of following steps:

1 . UE is configured with a first SR configuration and a second SR configuration; a. Each SR configuration is configured with a mapping to a set of LCHs

2. UE is configured with a Cell DTX and Cell DRX configurations, including active vs. inactive durations;

3. UE receives signaling indicating that Cell DTX and/or Cell DRX is activated in the serving cell;.

4. UE triggers a new SR during C-DRX and during cell DTX inactive period. UE may trigger such SR even if it has an available UL grant if the only available grant is overlapping with the cell DRX inactive period;

5. If the triggered SR is mapped to the first SR configuration (trigger by first set of LCHs), a. UE transmits the SR on the next applicable PUCCH occasion of the first SR configuration, even if the cell DTX and/or cell DRX pattern is in the inactive period; b. UE monitors PDCCH while an SR is pending, even if the cell DTX pattern is in the inactive period;

6. If the triggered SR is mapped to the second SR configuration (trigger by second set of LCHs); a. UE transmits the SR on the next applicable PUCCH occasion of the second SR configuration that overlaps with the cell DRX active period: b. If the prohibit timer has expired, the UE retransmits the SR after a DTX active period has passed since the last SR transmission;

[0131] 7. For a pending BSR/SR multiplexed on a PUSCH payload, the UE may only cancel the BSR/SR if the transmitted payload occurred during a cell DRX active period, an ACK is received, or RSRP is measured ^ threshold.

Conclusion

[0132] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall 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 this disclosure is not limited to particular methods or systems.

[0133] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other sy stems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves. [0134] It is also to 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 term "video" or the term "imagery" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and/or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter aha, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0135] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to. a read only memory (ROM), a random access memory (RAM), a register, 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). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0136] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0137] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory'. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0138] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory' locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0139] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0140] In an illustrative 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.

[0141] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmw are vehicle. If flexibility- is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

[0142] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flow charts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several 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 formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, 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 the circuitry⁷ and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry' out the distribution. Examples of a signal bearing medium include, but are not limited to. the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0143] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory', processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communi cation systems.

[0144] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality' is achieved, irrespective of architectures or intermedia! components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0145] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0146] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies 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 "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage 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 to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have 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 those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have 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 within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities 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 possibilities of "A" or "B" or "A and B." Further, the terms "any of followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of." "any combination of," "any multiple of." and/or "any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" 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. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0147] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0148] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As anon-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken dow n into subranges as discussed above. Finally , as will be understood by one skilled in the art. a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0149] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, T 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMS: What is Claimed:

1 . A wireless transmit/receive unit (WTRU) comprising circuitry, including a transmitter, a receiver, a processor, and memory, the WTRU configured to: receive a configuration of one or more logical channels (LCH)s, wherein each LCH is associated with a first scheduling request (SR) configuration or a second SR configuration; receive one or more of a cell discontinuous transmission (cell-DTX) configuration and a cell discontinuous receive (cell-DRX) configuration for a serving cell; transmit a SR to the serving cell with a first LCH of the one or more LCHs such that: on condition that the first SR configuration is associated with the first LCH, the WTRU transmits a first SR on a first physical uplink control channel (PUCCH) occasion of the first SR configuration that occurs during a first cell DRX active duration, and if an uplink (UL) grant is not received after at least one cell DTX active duration has occurred after the first SR transmission, the WTRU transmits a second SR on a second PUCCH occasion of the first SR configuration that occurs during a second cell DRX active duration; and on condition that the second SR configuration is associated with the first LCH, the WTRU transmits the first SR on a first PUCCH occasion of the second SR configuration independently of the cell DRX active duration, and if an UL grant is not received, the WTRU transmits the second SR on a second PUCCH occasion of the second SR configuration independently of the cell DRX active duration.

2. The WTRU of claim 1, wherein the cell-DTX configuration comprises a transmission active period and a transmission inactive period of the serving cell, and the cell-DRX configuration comprises a cell-DRX active period and a cell-DRX inactive period of the serving cell.

3. The WTRU of claim 2, wherein the WTRU using the second SR configuration triggers a new SR even if the WTRU has an available UL grant and if the available grants are time-overlapping with the cell-DRX inactive period.

4. The WTRU of claim 1 , wherein the WTRU using the second SR configuration monitors a physical downlink control channel (PDCCH) while any SR is pending even if a cell-DTX pattern is in an inactive period.

5. The WTRU of claim 1, further configured to: on condition that a pending buffer status report / scheduling request (BSR/SR) is multiplexed on a physical uplink shared channel (PUSCH) pay load, the WTRU cancels the BSR/SR if a transmitted payload occurred during a cell-DRX active period, an ACK is received, or reference received power (RSRP) is measured to be greater than a threshold value.

6. A method performed by a wireless transmit/receive unit (WTRU), the method comprising: receiving a configuration of one or more logical channels (LCH)s, wherein each LCH is associated with a first scheduling request (SR) configuration or a second SR configuration; receiving one or more of a cell discontinuous transmission (cell-DTX) configuration and a cell discontinuous receive (cell-DRX) configuration for a serving cell; transmitting a SR to the serving cell with a first LCH of the one or more LCHs such that: on condition that the first SR configuration is associated with the first LCH, the WTRU transmits a first SR on a first PUCCH occasion of the first SR configuration that occurs during a first cell DRX active duration, and if an uplink (UL) grant is not received after at least one cell DTX active duration has occurred after the first SR transmission, the WTRU transmits a second SR on a second PUCCH occasion of the first SR configuration that occurs during a second cell DRX active duration; and on condition that the second SR configuration is associated with the first LCH, the WTRU transmits the first SR on a first PUCCH occasion of the second SR configuration independently of a cell DRX active duration, and if an UL grant is not received, the WTRU transmits the second SR on a second PUCCH occasion of the second SR configuration independently of the cell DTX active duration.

7. The method of claim 6, wherein receiving the cell-DTX configuration comprises receiving information including a transmission active period and a transmission inactive period of the serving cell, and the cell-DRX configuration comprises a cell-DRX active period and a cell-DRX inactive period of the serving cell.

8. The method of claim 7, wherein on the condition that the WTRU transmits the first SR on a first PUCCH occasion of the second SR configuration, the WTRU triggers a new SR even if the WTRU has an available UL grant and if the available grants are time-overlapping with the cell- DRX inactive period.

9. The method of claim 6, wherein on the condition that the WTRU transmits the first SR on a first PUCCH occasion of the second SR configuration, the method further comprises monitoring, by the WTRU, a physical downlink control channel (PDCCH) while any SR is pending even if a cell-DTX pattern is in an inactive period.

10. The method of claim 6, further comprising: on condition that a pending buffer status report / scheduling request (BSR/SR) is multiplexed on a physical uplink shared channel (PUSCH) payload, the WTRU canceling the BSR/SR if a transmitted payload occurred during a cell-DRX active period, an ACK is received, or reference received power (RSRP) is measured to be greater than a threshold value.

11. A non-transient computer-readable storage media having instructions therein, wherein when executed by a computer, perform the method of any one of claims 6-10.