Methods for discontinuous cell transmission and reception and scheduling requests

Abstract

A method performed by a UE includes receiving a first SR configuration and a second SR configuration; receiving the DTX / DRX configuration of the cell; transmitting the SR to the serving cell such that if the first SR configuration is used, the UE transmits the first SR on a first PUCCH occasion of the first SR configuration occurring during the DRX activity duration of the first cell; and if an uplink grant is not received after at least one cell DTX activity duration has occurred after the first SR transmission, the UE transmits a second SR on a second PUCCH occasion of the first SR configuration occurring during a second cell DRX activity 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 activity duration, and if the 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 activity duration.

Description

[0001] Cross-references to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 445027, filed February 13, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] 3GPP RAN has concluded its research project on network power efficiency in Rel-18. The motivation was to study enhancements that enable networks to minimize power consumption during transmission and reception. This minimization contributes to reduced operating costs and environmental sustainability. The research project was approved and led to the new Rel-18 work project on network power efficiency.

[0003] Compared to earlier systems, the Rel-15's NR design is highly efficient in minimizing network transmission when there is no data. For example, normally open cell-specific reference signals (CRS) are not used in the NR. However, there is still potential to reduce energy consumption.

[0004] For example, even when not transmitting, the network still consumes energy due to other activities, such as baseband (digital) processing for receiving or beamforming. This "idle" power consumption is not negligible in dense networks, even when no UE is being served for a given period. Energy consumption can be reduced if the network can shut down these activities when not transmitting to the UE.

[0005] Unlike LTE, NR does not require the transmission of normally open synchronization or reference signals and supports adaptable bandwidth and MIMO capabilities. While initial operation in R18 is not expected to impact legacy UEs, this adaptation of network resources is anticipated to enable greater efficiency in operating newer deployments and subsequent generations. Attached Figure Description

[0006] A more detailed understanding can be obtained from the following detailed embodiments given by way of example in conjunction with the accompanying drawings. Like the detailed embodiments, the figures in these drawings are illustrative. Therefore, the figures and detailed embodiments should not be considered limiting, and other equivalently effective examples are possible and desirable. Furthermore, similar reference numerals (“references”) in the figures indicate similar elements, and wherein: Figure 1A This is a system diagram illustrating an example communication system; Figure 1B It is illustrated in the diagram. Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system. Figure 1C It is illustrated in the diagram. Figure 1AThe diagram shows a system diagram of an example radio access network (RAN) and an example core network (CN) used in a communication system. Figure 1D It is illustrated in the diagram. Figure 1A The diagram shows another example RAN and another example CN used in the communication system. Figure 2 An adaptation of the scheduling request process according to the features of this disclosure is described; Figure 3 Another adaptation of the scheduling request process according to the features of this disclosure is described; and Figure 4 A flowchart illustrating the features according to this disclosure is provided. Detailed Implementation

[0007] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the 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, processes, components, and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of or in combination with the embodiments and other examples described, disclosed, or otherwise explicitly, implicitly, and / or inherently provided (collectively, the “Provided”). Although various embodiments are described and / or claimed herein in which apparatuses, systems, devices, etc., and / or any elements thereof implement operations, processes, algorithms, functions, etc., and / or any parts thereof, it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, device, etc., and / or any element thereof is configured to implement any operation, process, algorithm, function, etc., and / or any part thereof.

[0008] Example Communication System The methods, apparatus, and systems provided herein are well-suited for communications involving both wired and wireless networks. Regarding Figure 1A-1D This provides an overview of various types of wireless devices and infrastructures, in which various elements of the network can utilize the methods, apparatuses, and systems provided herein, perform the methods, apparatuses, and systems provided herein, are arranged according to the methods, apparatuses, and systems provided herein, and / or are adapted and / or configured for the methods, apparatuses, and systems provided herein.

[0009] Figure 1AThis is a system diagram illustrating an example communication system 100, in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail (ZT) Unique Word (UW) Discrete Fourier Transform (DFT) Extended OFDM (ZT UW DTS-sOFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM (OFDM), Filter Bank Multicarrier (FBMC), etc.

[0010] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 108, the Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0011] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or Network 112. For example, base stations 114a and 114b can be any of the following: base transceiver station (BTS), Node-B (NB), eNode B (eNB), home Node B (HNB), home eNode B (HeNB), gNode-B (gNB), NR Node B (NRNB), site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are depicted as single elements, it should be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0012] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown in the figures), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown in the figures). These frequencies may be located in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide radio service coverage for a specific geographic area, which may be relatively fixed or may vary over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in an embodiment, base station 114a may include three transceivers, one for each sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use 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.

[0013] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

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

[0015] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro) to establish air interface 116.

[0016] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use new radio (NR) to establish air interface 116.

[0017] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can simultaneously implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface utilized by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions to and from multiple types of base stations (e.g., eNBs and gNBs).

[0018] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0019] Figure 1A Base station 114b can be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In embodiments, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In embodiments, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In embodiments, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of the following: small cells, picocells, or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, base station 114b can access Internet 110 without going through CN 106 / 115.

[0020] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to perform the following operations: provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. The data may have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although Figure 1A Although not shown in the diagram, it should be understood that RAN104 / 113 and / or CN106 / 115 can communicate directly or indirectly with other RANs that use the same or different RATs as RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown in the diagram) that uses any of the following radio technologies: GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi.

[0021] CN 106 / 115 can also act as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may employ the same or different RAT as RAN 104 / 114.

[0022] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example, Figure 1AThe WTRU 102c shown can be configured to communicate with a base station 114a that may employ cellular-based radio technology and a base station 114b that may employ IEEE 802 radio technology.

[0023] Figure 1B This is a system diagram illustrating the example WTRU 102. (Example: ...) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other components / peripherals 138, etc. It should be understood that, while remaining consistent with the embodiments, WTRU 102 may include any sub-combination of the above-described components.

[0024] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding / decoding, data processing, power control, input / output processing, and / or any other function that enables WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in, for example, an electronic package or chip.

[0025] Transmitting / receiving element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 may be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 may be configured to transmit and / or receive both radio frequency signals and optical signals. It should be understood that transmitting / receiving element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0026] Although Figure 1BWhile the transmitting / receiving element 122 is depicted as a single element, the WTRU 102 may contain any number of transmitting / receiving elements 122. For example, the WTRU 102 may employ MIMO technology. Therefore, in an embodiment, the WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interface 116.

[0027] Transceiver 120 can be configured to modulate the signal to be transmitted by transmitting / receiving element 122 and demodulate the signal received by transmitting / receiving element 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via various RATs (such as, for example, NR and IEEE 802.11).

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

[0029] The processor 118 can receive power from the power supply 134 and can be configured to distribute power to other components in the WTRU 102 and / or control the power going to other components. The power supply 134 can be any device suitable for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0030] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. Attached to or replacing the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 116, and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable location determination method.

[0031] The processor 118 may also be coupled to other components / 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 component / peripheral 138 may include an accelerometer, electronic compass, satellite transceiver, digital camera (e.g., for photos and / or video), Universal Serial Bus (USB) port, vibration device, television transceiver, hands-free headset, Bluetooth® module, FM radio unit, digital music player, media player, video game player module, internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. The component / peripheral 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor, geolocation sensor; altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biosensor, and / or humidity sensor.

[0032] WTRU 102 may include a full-duplex radio, for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for both 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 for reducing and / or substantially eliminating self-interference via hardware (e.g., a choke) or through signal processing by a processor (e.g., a separate processor (not shown) or through processor 118). In an embodiment, WTRU 102 may include a half-duplex radio, for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for either uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0033] Figure 1CThis is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0034] RAN 104 may include eNodeBs 160a, 160b, and 160c, but it should be understood that RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. eNodeBs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In the embodiments, eNodeBs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNodeB 160a may use multiple antennas to transmit and receive radio signals from WTRU 102a.

[0035] Each of eNodeBs 160a, 160b, and 160c can be associated with a specific cell (not shown in the figure) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink (UL) and / or downlink (DL). Figure 1C As shown, eNodeB 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0036] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. While each of the above elements is depicted as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0037] The MME 162 can connect to each eNodeB 160a, 160b, and 160c in RAN104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0038] The SGW 164 can connect to each eNode B 160a, 160b, and 160c in RAN104 via the S1 interface. The SGW 164 typically routes and forwards user packets to and from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, managing and storing WTRU 102a, 102b, and 102c scenarios, etc.

[0039] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

[0040] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional terrestrial line communication equipment. For example, CN 106 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), which acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0041] Despite Figure 1A-1D The WTRU is described as a wireless terminal, but in some representative embodiments, it is envisioned that such a terminal may communicate with a communication network using (e.g., temporarily or permanently) a wired communication interface.

[0042] In a representative embodiment, another network 112 may be a WLAN.

[0043] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with that AP. The AP may access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and from the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via, for example, an AP, where the source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between the source STA and the destination STA (e.g., directly between the source STA and the destination STA) using a direct link setup (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

[0044] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a bandwidth of 20 MHz) or can be dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by STAs to establish connections with the AP. In some representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example in an 802.11 system. With CSMA / CA, all STAs, including the AP (e.g., each STA), can listen on the primary channel. If a particular STA listens / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0045] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0046] Ultra-High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two non-consecutive 80 MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, data, after channel coding, can be transmitted via a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80 MHz channels and transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

[0047] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine-type communications (MTC), such as MTC devices in macro coverage areas. MTC devices may have specific capabilities, such as supporting (e.g., only supporting) specific and / or limited bandwidth functions. MTC devices may include batteries with a battery life exceeding a threshold (e.g., maintaining a very long battery life).

[0048] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. Taking 802.11ah as an example, for a STA that supports (e.g., only supports) the 1 MHz mode (e.g., MTC type device), the primary channel bandwidth can be 1 MHz, 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 Sense and / or Network Assignment Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy (e.g., due to a STA (which only supports the 1 MHz operating mode)) transmitting to the AP, the entire available band can be considered busy, even if most of the band remains idle and may be available.

[0049] In the United States, the available frequency band for 802.11ah is 902 MHz to 928 MHz. In South Korea, the available frequency band is 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is 916.5 MHz to 927.5 MHz. The total available bandwidth for 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0050] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0051] RAN 113 may include gNBs 180a, 180b, and 180c, but it should be understood that RAN 113 may include any number of gNBs while maintaining consistency with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In embodiments, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from WTRUs 102a, 102b, and 102c. Therefore, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be located on unlicensed spectrum, while the remaining component carriers may be located on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0052] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with an scalable set of parameters. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including different numbers of OFDM symbols and / or absolute time lengths of varying durations).

[0053] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without also accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN (such as eNode-Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, while gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0054] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown in the figure) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0055] Figure 1DThe CN 115 shown 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 above elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0056] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing, for example, to customize CN support for WTRU 102a, 102b, and 102c based on the service types used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for MTC access, etc. The AMF162 can provide control plane functions for handover between 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 Wi-Fi).

[0057] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure traffic routing through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0058] UPF 184a and 184b can be connected to one or more of gNB 180a, 180b, and 180c in RAN 113 via the N3 interface. The N3 interface can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices, for example. UPF 184a and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and so on.

[0059] CN 115 can facilitate communication with other networks. For example, CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or may communicate with such an IP gateway, which acts as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, WTRUs 102a, 102b, and 102c can be connected to local data networks (DNs) 185a and 185b via UPFs 184a and 184b through their N3 interfaces and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0060] Given Figure 1A-1D and Figure 1A-1D The corresponding descriptions herein indicate that one or more of the functions described for any of the following can be performed by one or more emulation components / devices (not shown in the figures): WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other component(s) / devices described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0061] The simulation device may be designed to perform one or more tests on other devices in a laboratory environment and / or a carrier network environment. For example, the one or more simulation devices may perform one or more or all functions, fully or partially implemented and / or deployed as part of a wired and / or wireless communication network, to test other devices within that communication network. The one or more simulation devices may perform one or more or all functions, temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing, and / or may perform tests using over-the-air wireless communication.

[0062] One or more simulation devices can perform one or more functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices can be used in test scenarios within a test laboratory and / or an undeployed (e.g., testing) wired and / or wireless communication network to perform testing on one or more components. One or more simulation devices can be test rigs. Simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0063] The examples provided in this article do not limit the applicability of the subject matter to other wireless technologies that may be applicable based on the same or different principles.

[0064] As explained herein, a wireless transmit / receive unit (WTRU) can be an example of a user equipment (UE). Therefore, the terms UE and WTRU can be used in this document with equivalent scope.

[0065] the term The following terms are used and may be adopted in the following description. 1. CSI: Channel State Information, which may include at least one of the following: Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Index (PMI), L1 channel measurement (e.g., Reference Signal Received Power (RSRP) such as L1-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 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 procedures, Schedule Request (SR), Link Recovery Request (LRR), Configuration 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 that can be determined by the UE based on: UE measurements (e.g., L1 / SINR / RSRP, CQI / Modulation and Coding Scheme (CQI / MCS), channel occupancy, Received Signal Strength Indication (RSSI), power margin, exposure margin), L3 / mobility-based measurements (e.g., RSRP, Reference Signal Received Quality (RSRQ), s-measure), Radio Link Monitoring (RLM) status, and / or channel availability in unlicensed spectrum (e.g., whether the channel is occupied based on a Listen-Before-Speak (LBT) procedure, or whether the channel is considered to have experienced a consistent LBT failure). 4. Physical Random Access Channel (PRACH) resources: PRACH resources (e.g., in frequency), PRACH timing (RO) (e.g., in time), preamble format (e.g., in terms of total preamble duration, sequence length, guard duration and / or cyclic prefix length) and / or a specific preamble sequence used for preamble transmission in the random access process. 5. The attributes of the scheduling information (e.g., uplink grant or downlink assignment) may include at least one of the following: frequency allocation; one aspect of time allocation, such as duration; priority; modulation and coding scheme; transport block size; number of spatial layers; number of transport blocks to be carried; Transport Configuration Indicator (TCI) status or Sounding Reference Signal (SRS) Resource Indicator (SRI); number of repetitions; whether the grant is a configured grant type 1, type 2, or dynamic grant. 6. The indication or indication of the downlink control information (DCI) may include at least one of the following: an explicit indication implemented through a radio network temporary identifier (RNTI) or DCI field used for cyclic redundancy check (CRC) of the physical downlink control channel (PDCCH); an implicit indication implemented through attributes such as DCI format, DCI size, coreset or search space, aggregation level, and the identifier of the first control channel resource of the DCI (e.g., the index of the first control channel element (CCE)), wherein the mapping between attributes and values ​​can be signaled by radio resource control (RRC) or media access control (MAC); or an explicit indication of a downlink (DL) MAC control element (CE).

[0066] In the following description, the terms Network Availability Status, Discontinuous Transmission (DTX) Mode / Configuration, or Network Energy Saving (NES) Status may be used interchangeably.

[0067] Discontinuous Transmission (DTX) and Discontinuous Reception (DRX) Currently, the gNB can use reduced downlink transmission / uplink reception activity without explicit cell DTX / DRX modes, but this is limited by the UE DRX configuration and any configured transmission / reception (e.g., common channels / signals). Each UE configures its current connection mode DRX (C-DRX). Alignment of DRX periods or offsets between different UEs can only be done via RRC. During UE DRX off periods, UEs do not expect to monitor the PDCCH, but are allowed to initiate UL transmissions based on configured resources (e.g., using PUCCH, Random Access Channel (RACH), Scheduling Request (SR), or CG-PUSCH). Alignment / omission of DRX modes across multiple UEs can be implemented via the gNB.

[0068] Cell DTX / DRX is designed to provide a mechanism for notifying the UE whether the cell remains inactive. This may include enhancements to the UE's DRX configuration, such as aligning or omitting the DRX period or the DRX start offset for UEs in connected or idle / inactive modes, potentially providing a longer window for cell inactivity. During cell DTX / DRX, the cell may not transmit / receive or may only maintain limited transmission / reception. For example, the cell may not need to transmit or receive some periodic signals / channels, such as common channels / signals or UE-specific signals / channels.

[0069] Cell DTX / DRX applies at least to UEs in the RRC_CONNECTED state. Periodic cell DTX / DRX (i.e., active and inactive periods) can be configured by the gNB via UE-specific RRC signaling for each serving cell. Cell DTX / DRX modes can be activated / deactivated via dynamic L1 / L2 signaling and UE-specific RRC signaling. Both UE-specific and common L1 / L2 signaling can be considered for activating / deactivating cell DTX / DRX modes. 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. Per-cell DTX / DRX configuration can configure at least the following parameters: periodicity, start timeslot / offset, and on-time duration. In one implementation, cell DTX indication can also be part of a System Information (SI) update or System Information Block (SIB) signaling. A common time for all UEs can be used to determine the cell DTX state.

[0070] Network availability status / Cell DTX mode / NES status The UE can determine whether it can transmit or receive on certain resources based on the network availability state (which implies the gNB's power-saving state). The availability state can correspond to network power-saving state, cell DTX mode, cell DRX mode, and / or gNB activity level. The availability state can be uplink- or downlink-specific and can change from symbol-to-symbol, slot-to-slot, frame-to-frame, or at longer duration granularities. The availability state can be determined by the UE or indicated by the network. The availability state can be, for example, "On," "DL and UL Active," "UL Active Only," "Off," "Tx Power Reduced," "Sleep," "Micro Sleep," "Light Sleep," or "Deep Sleep." Such states can be abstractly described by network (NW) configuration parameters and / or values, and dynamic indications can point to active availability states (e.g., via DCI or MACCE signaling). An "Off" availability state may imply that the gNB's baseband hardware is completely off. A "Sleep" availability state may imply that the gNB periodically wakes up to transmit certain signals (e.g., presence signals, synchronization, or reference signals) or receive certain UL signals. In some availability states, certain DL or UL resources are unavailable for certain time periods, allowing the network to shut down baseband processing and other activities. Some measurement resources (e.g., Synchronization Signal Block (SSB) or CSI-RS) may only be available in certain availability states, including: RLM, Beam Failure Detection (BFD), Radio Resource Management (RRM) measurements, CSI-RS feedback configuration, and / or different power offsets for CSI feedback. Under certain conditions, the UE can also send a request (wake-up request) to the network to modify the availability state to one that makes resources meeting the UE's requirements available.

[0071] The UE can determine the availability status based on, for example, the reception of an availability status indication via L1 / L2 signaling (e.g., group common DCI or indication), or implicitly based on the reception or non-reception of periodic DL signaling.

[0072] The UE can determine whether a resource is available for transmission / reception and / or measurement (if the resource is applicable in an active availability state) based on a determined network availability state. Furthermore, the UE can adapt its active C-DRX cycle, active spatial elements (e.g., antennas or logical ports), active transmit / receive points (TRPs), and paging timing based on the signaled or determined availability state. The UE can be configured with one or more NES transmission and / or reception parameter sets for each availability state, for example, via broadcast or dedicated configuration signaling. The UE can apply the NES parameter sets based on the determined or signaled availability state. The UE can apply one or more applicable configurations based on the determined NES state. The NES parameter sets may include: the number of antenna ports, C-DRX configuration, measurement configuration (e.g., for RRM, RLM, and / or BFD), CSI feedback, CSI-RS configuration, SSB configuration, channel occupancy (CHO) or mobility candidate, and active TRP set.

[0073] Availability status can apply to at least one transmission, reception, or measurement resource. Availability status can apply to at least one time period, such as a time slot or time symbol. Availability status can apply to a serving cell, cell group, frequency band, bandwidth portion, TRP, set of spatial elements, or a frequency range within a bandwidth portion. For example, when the NES status in a cell changes, the UE can receive an availability status change indication indicating that the change applies only to that cell, to all cells at the same frequency, and / or to the same Radio Access Technology (RAT).

[0074] Upon receiving DL signaling that changes the availability state of a cell or TRP, the UE can assume that the active availability state associated with the cell, carrier, TRP, or frequency band is "off," "deep sleep," or "micro sleep." For example, the UE may receive a shutdown command on broadcast signaling, RRC signaling, DCI (e.g., group common DCI), or DL ​​MAC CE (e.g., the indication portion of PDSCH). The UE can determine the availability state based on the reception of an availability state indication, for example, via L1 / L2 signaling (e.g., group common DCI or indication) or broadcast signaling associated with the availability state. For example, the availability state change indication may also be part of an SI update or SIB signaling (e.g., in a separate SIB not read by a legacy UE). A common time can be used for all UEs within the cell to determine the availability state.

[0075] The UE may implicitly assume an availability state (e.g., "off", "deep sleep", "micro sleep", or "dormant") associated with a cell, carrier, TRP, or frequency band based on the following: reception of paging messages (e.g., paging DCI, paging PDSCH, or paging-related signals, i.e., paging advance indication (PEI)), gNB DTX status (whether the gNB is active or the associated activity timer is running), lack of detection of presence indication, availability state of the associated cell, or channel conditions (one or more) measured below or above a threshold.

[0076] The UE can be configured to monitor indications that characterize network activity levels (e.g., availability status). Network activity can be associated with gNBs and / or cells. The UE can assume the same availability status for all cell portions of the same gNB (e.g., cells of the same MAC entity). Network activity indications (e.g., presence indications) can include channels (e.g., PDCCH) and / or signals (e.g., sequences). Activity indications or NES state change indications / commands can indicate to the UE the level of activity that can be expected from the associated gNB and / or cell, e.g., reduced activity. Activity indications can contain activity information from other gNBs / cells. Activity indications can be PDCCHs containing group common signaling. For example, the NW can transmit a group common DCI to a group of UEs (e.g., UEs in the serving cell) that indicates a change in activity status or activity level in the UL and / or DL. The CRC of the PDCCH can be scrambled using a dedicated "Activity Indicator RNTI" or "NES RNTI". The UE can be configured with at least one search space associated with the monitoring timing of the Activity Indicator PDCCH. This indication can include a sleep entry signal, for example, a predefined sequence. When the UE detects this sequence, the UE can anticipate a reduction in activity level for a specific duration. The UE can activate C-DRX during the indicated time period. Alternatively, two sequences can be used to indicate regular activity and reduced activity.

[0077] Signaling or activity indications within the PDCCH may include at least one of the following: 1. The expected activity level (e.g., availability status) of the associated gNB / cell within a specific time interval. The activity level can be predetermined and / or configured, and can include, for example, regular and reduced activity. Signaling can indicate the activity level. For example, a bit "1" can indicate regular activity, while a bit "0" can indicate reduced activity. 2. For each activity level (e.g., availability state), transmission and reception attributes can be defined. For example, during reduced activity, it may not be expected that the UE will monitor certain PDCCH search spaces (including all synchronization signals (SS)), and / or receive a certain type of PDSCH (including all PDSCH), and / or transmit PUCCH / PUSCH, and / or perform certain measurements. The UE can start or stop monitoring PDCCH and / or TCI states associated with the determined NES state, including PDCCH resources or TCI states associated with activated (deactivated) TRPs or spatial elements. 3. Configuration sets can be associated with activity levels and can be used / applied when indicating that activity level (e.g., NES parameter sets). Examples include SS configurations, CSI report configurations, indexes of transported SSBs, etc. Each configuration set can have attributes associated with the activity level. For example, a label can be set to "Reduced Activity". 4. Assume that the time interval of the activity level can be notified by signaling in the PDCCH or part of the activity indication. a. A bitmap can be used to indicate time intervals, where each bit in the bitmap can be associated with a specific duration (e.g., a time slot or frame). For example, a bit "1" can indicate regular activity on the associated frame, and a bit "0" can indicate reduced activity on the associated frame. b. Time intervals can be indicated by the start time and length of the interval. The start time can be defined; for example, it can be determined by adding a fixed offset to the time the indication is received. The length of the interval can be configured in the indication PDCCH or signaled. 5. It is assumed that the time interval for the activity level can be predetermined. The UE may assume an interruption delay (or more generally, the time until the NES state change) after receiving the NES state change command (e.g., after the last symbol or time slot of the command is received). The interruption time can be absolute time, the number of symbols, or the number of time slots.

[0078] If uplink or downlink resources or signals are applicable to an active availability state, the UE can determine that they are available for transmission / reception and / or measurement in the determined network availability state. The UE can determine that a subset of measurement resources and / or signals (e.g., SSB, CSI-RS, Tracking Reference Signal (TRS), Positioning Reference Signal (PRS)) are not applicable in certain availability states. The UE can determine that a subset of uplink or downlink resources (e.g., PRACH, PUSCH, PUCCH) are not applicable in certain availability states. The UE can transmit some uplink signals only in a subset of NW availability states (e.g., SRS, pSRS, PRACH, UCI).

[0079] Possible problems Cell DTX and cell DRX can be configured independently and may not be aligned with each other or with the UE C-DRX, which can affect the UE. During a given on-time duration, the network may only receive, only transmit, and / or perform both. Therefore, UE UL transmissions during cell DRX can cause unnecessary interference in the network.

[0080] Many C-DRX timers that specify an "active time" start after a UL transmission (e.g., after SR, RACH, or CG transmissions), even though the serving cell may only be in cell DTX in the downlink direction. Current specifications require the UE to perform unnecessary retransmissions of such UL signals simply because the NW has not yet had a chance to respond. Furthermore, the UE is considered to be in C-DRX active time after such transmissions, thus wasting battery power. How can we ensure that the UE's C-DRX active time and cell DTX active time are aligned? How to ensure that the UE does not monitor the PDCCH when it is not needed? How can we ensure that the UE does not retransmit the UL signal even if the first transmission is correctly received but the NW has not yet received a response? Furthermore, UE DRX parameters and timers (e.g., on-duration and other timers) may not be aligned with the active cell DTX / cell DRX, leading to unnecessary battery consumption and unnecessary monitoring of the DL channel. Another issue is that some SR (Signal Transfer) events occur when the network is not receiving data due to network power-saving mode. SR retransmissions can waste resources.

[0081] Problem solved The following are proposed solutions to the problems described above. These solutions are further discussed in the detailed description below.

[0082] Adaptation of SR transmission in DTX / DRX of the cell The UE can be configured with a first SR configuration and a second SR configuration. Each SR configuration can be configured with a mapping to a set of logical channels (LCHs). Each LCH or data radio bearer (DRB) can be configured with a mapping to the SR configuration and / or SR UE transmission behavior during cell DTX and / or cell DTX to accommodate SR transmission requirements in cell DTX / DRX. This addresses the issue of SR timing occurring when the network is not receiving data due to network power saving. Further discussion is given in the section entitled “Impact of Cell DTX / DRX on the Scheduling Process”.

[0083] definition The following are several descriptions of embodiments / solutions to the problem defined above, and definitions or aspects of technologies that may be shared. 1. Cell DTX Activity Period: The duration of the configured cell DTX mode activity (e.g., the time period during which the cell DTX mode is active). The UE can be predefined and monitor the PDCCH and other DL signals and channels during this period. This is only applicable after the NW has indicated that the cell DTX configuration should be activated. 2. Cell DTX Inactivity Periods: The duration during which the configured cell DTX mode is neither active nor inactive (e.g., time periods outside the periodic active duration of the cell DTX mode). This may only apply after the NW has already indicated that the cell DTX configuration should be activated. 3. Cell DRX Activity Period: The duration of the configured cell DRX mode activity (e.g., the time period during which the cell DRX mode is active). The UE can be predefined as being allowed to transmit UL signals on the UL channel during such a time period. This can only apply after the NW has already indicated that the cell DRX configuration should be activated. 4. Cell DRX Inactivity Periods: The duration during which the configured cell DRX mode is neither active nor inactive (e.g., time periods outside the periodic active duration of the cell DRX mode). This may only apply after the NW has already indicated that the cell DRX configuration should be activated. 5. Activated cell DRX / DTX: The state of the configured cell DRX or cell DTX mode, wherein this state has been activated by L1 / L2 DL signaling, RRC (re)configuration and / or cell common configuration and has not been deactivated. 6. Deactivated cell DRX / DTX: The state of the configured cell DRX or cell DTX mode, where this state has been deactivated by L1 / L2 DL signaling, RRC (re)configuration and / or cell common configuration. 7. Relationship between Availability State and Cell DTX / DRX. In this document, the two terms are used interchangeably. A UE can implicitly determine the cell DTX state from a given active availability state, and vice versa. A UE can implicitly determine the cell RTX state from a given active availability state, and vice versa. 8. The terms Downlink Configuration Grant (DLCG) and Semi-Permanent Scheduling (SPS) are used interchangeably in this document.

[0084] Cell DTX configuration can define the cell DTX activity period as a set of cell DTX opportunities. Such a set can be parameterized by at least one of the following: the duration between the start and end of a call-through opportunity (cell DTX cycle), the offset of each cell DTX opportunity (cell DTX offset), and the duration (cell DTX duration). For example, such parameters can be expressed in subframes (or milliseconds) in the same manner as long UE DTX cycles. In this case, a cell DTX opportunity can consist of a time period that begins in a subframe satisfying [SFN×10+subframe number]mod(cell DTX cycle)=(cell DTX offset), where SFN is the system frame number, and ends after (cell DTX duration).

[0085] Cell DTX configuration may also include a time slot offset for the start of the subframe relative to the cell DTX timing. At least one parameter of the cell DTX configuration may be signaled via RRC, MAC CE, and / or DCI (UE-specific or UE-group common).

[0086] The UE can be predefined or configured based on the cell DTX and / or the cell DRX configuration having one of the following parameters and behaviors: 1. One or more applicable configuration grants or SPS configurations. For example, the UE may activate such a configuration grant when cell DTX and / or cell DRX configurations are active. The UE may be configured for each configuration grant to specify whether the configuration grant takes precedence over the configured cell DTX and / or cell DRX modes (e.g., whether the UE can transmit or receive on UL or DL ​​CG respectively during cell DRX or cell DTX inactivity periods). 2. Should the UE monitor the PDCCH for dynamic granting or dynamic DL assignment during periods when the cell DTX is inactive? 3. Allow UE to transmit under either dynamic authorization or configuration authorization. 4. PRACH resources or PRACH resource configuration, which may or may not be applicable during cell DRX inactivity periods or when cell DRX configuration is activated. 5. SR / PUCCH resources or SR / PUCCH resource configuration, which may or may not be applicable during cell DRX inactivity periods or when cell DRX configuration is activated. 6. CSI-reporting or CSI-reporting resource configuration, which may or may not be applicable during periods of cell DRX inactivity or when cell DRX configuration is activated. 7. SRS resources or SRS resource configurations, which may or may not be applicable during periods when the cell DRX is inactive or when the cell DRX configuration is activated.

[0087] A UE can have multiple cell DRX and / or cell DTX configurations configured simultaneously in a given serving cell. The UE can be configured with a primary or default cell DRX and / or cell DTX configuration that it can apply by default. Upon receiving signaling to activate a cell DTX and / or cell DRX configuration, the UE can deactivate another cell DTX and / or cell DRX configuration (or all other cell DTX and / or cell DRX configurations). Upon receiving signaling to deactivate a cell DTX and / or cell DRX configuration, the UE can activate another or activate the default cell DTX / DRX configuration. When a timer expires, the UE can fall back to the default cell DRX and / or cell DTX configuration. The UE can reset such timers upon receiving DL signaling, data, or indications from the NW to maintain a given non-default cell DTX or cell DRX state.

[0088] The UE can assume / configure cell DTX for each channel, DL signal (e.g., including PDCCH, RS, PDSCH, etc.), each cell, each channel type, and / or each signal type. The UE can assume / configure cell DTX for each channel, UL signal (e.g., PRACH, PUSCH, PUCCH, SRS, Wake-up Signal (WUS)), or each cell, each channel type, and / or each signal type.

[0089] The UE can be predefined, configured, or determined to prioritize either the configured cell DRX mode or UE-specific channel / signal configuration based on UE capabilities, data priority, delay, and / or control signaling / message type. An example of a UE signal or channel that can take precedence over the configured cell DRX mode is CG transmission, SR transmission, or cell WUS transmission.

[0090] Impact of cell DTX / DRX on the scheduling process SR transmission during cell DTX / DRX Figure 2 and Figure 3 It describes how the UE can adapt to the scheduling request process to ensure that SR is transmitted during the opportune time when the network is active.

[0091] Depending on UE capabilities, data arrival type, and / or configured parameters, a UE may follow a first SR UE transmission behavior and a second behavior during cell DTX and / or cell DRX. For example, a UE capable of transmitting high-priority data, extended reality (XR) data, or low-latency data (e.g., by configuring or activating such services or data radio bearers (DRBs) associated with such services) may follow the first SR transmission behavior during cell DTX / DRX, while an eMBB UE that does not support active transmission of latency-critical data may follow the second UE behavior for SR transmission during cell DTX / DRX. This document describes the first and second SR transmission behaviors. Here, SR may be transmitted on PUCCH or multiplexed on PUSCH.

[0092] The UE can be configured with a first SR configuration and a second SR configuration. Each SR configuration can be configured with a mapping to a set of LCHs. Each LCH or DRB can be configured with a mapping to the SR configuration and / or SR UE transmission behavior during cell DTX and / or cell DRX. Each LCH or DRB can be configured with a flag or priority index that enables the transmission of SRs triggered by such LCHs during cell DTX / DRX using both the first SR UE transmission behavior and the second SR transmission behavior. The UE can imply the configuration of the second SR transmission behavior based on the configuration where the first SR transmission behavior is missing.

[0093] If the triggered SR is mapped to a first SR configuration or triggered by an LCH configured for the first SR transmission action, or if the SR is triggered by a UE with the capability to support the transmission of the first SR transmission action or related services during cell DTX / DRX, the UE may transmit the SR on the next applicable PUCCH timing (possibly from the configured first SR configuration), even if the cell DTX and / or cell DRX modes are inactive (i.e., outside the cell DTX on-duration and / or outside the cell DRX on-duration). Furthermore, even if the cell DTX mode is inactive, the UE may immediately monitor the PDCCH after the SR transmission while the SR is pending.

[0094] If the triggered SR is mapped to a second SR configuration or triggered by an LCH configured for the second SR transmission action (or an LCH not configured for the first action), or if the SR is triggered by a UE that does not have the capability to support the transmission of the first SR transmission action (or related services) during cell DTX / DRX, then the UE may choose to perform at least one of the following for the SR (re)transmission timing: 1. The UE may transmit the SR on the next applicable PUCCH timing, which may come from a second SR configuration (if configured) and may only be available if the SR transmission timing overlaps with the cell DRX activity period. 2. If the prohibition timer has expired, the UE can retransmit the SR after the DTX activity period has elapsed since the last SR transmission. 3. If the cell is in cell DTX, the UE can delay SR transmission to select an SR / PUCCH transmission timing before or overlapping with the next cell DTX / DRX activity period (e.g., cell DTX or cell DRX on-time duration). 4. After the SR transmission, the UE may delay PDCCH monitoring until the next DTX active period. If the UE is in C-DRX, even if the SR is pending, if the serving cell is in a cell DTX inactive period (i.e., the cell DTX configuration has been activated, but during a period that does not overlap with the configured cell DTX activation duration), the UE may consider itself to be inactive (i.e., not in an active period). The UE may apply this behavior per serving cell. 5. After the SR transmission, if the serving cell is in a cell DTX / DRX inactive period, the UE may delay the start of the SR disable timer until the cell DTX / DRX active period (i.e., the on-duration period) begins or just before it (e.g., if the SR timing is selected just before the cell DTX / DRX on-duration period). For example, if the SR timing is transmitted during the UE C-DRX inactivity timer, during a cell DRX inactivity period, or during a cell DTX inactivity period, the UE may delay the start of the disable. The UE may apply this behavior per serving cell. 6. The UE can be configured with an alternative (extended) value for the SR disable timer, which the UE can use when the serving cell is in cell DTX / DRX (e.g., if cell DTX / DRX configuration is active or during cell DTX inactivity periods). For example, if the SR timing is transmitted during the UE C-DRX inactivity timer, during a cell DRX inactivity period, or during a cell DTX inactivity period, the UE can use the alternative configuration value to initiate the disable. The UE can apply this behavior per serving cell.

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

[0096] In one approach, if cell DTX is active and the UE is in C-DRX, the UE can select an SR timing for PUCCH transmission such that the disable timer is aligned with the DTX active period from the set of available next SR timings.

[0097] Figure 2 An arrangement with two Scheduling Request (SR) configurations is described, which can be used by the UE in response to data arrival. The UE can use SR configuration A. In the timeline of SR configuration A, the UE receives a cell DTX indication, followed by data arrival during the cell DTX activity period. The UE can decide to transmit the received uplink data and generate a TX SR using the previously configured SR slot, then wait for the SR inhibit timer duration to allow the serving cell to respond. If no response from the cell (such as a grant / DCI) is received, the TX SR is retransmitted at the next available SR opportunity, and then again waits for the SR inhibit timer duration.

[0098] This action can continue until the next available cell DTX activity period after the TX SR is retransmitted. At this point, the cell can respond by transmitting an authorization / DCI to the UE allowing the UE to transmit its data uplink. Figure 2 This activity of sending multiple SRs is illustrated at position 206. One drawback of using this SR scheduling configuration is that the UE can remain active for most of the duration of multiple SR transmissions 206.

[0099] Figure 2 Alternative SR Configuration B is shown. In the timeline of SR Configuration B, the UE receives a cell DTX indication, and then data arrives during the cell DTX activity period. The UE can decide to transmit the received data uplink and generate a TX SR using the previously configured SR slot, allowing the serving cell to respond after the SR disable timer duration. In this case, the SR disable timer is configured to have a duration exceeding the period between cell DTX activity times. In the example of SR Configuration B, the cell responds to the SR with a grant / DCI for the duration of the SR disable timer shown at 208. This SR Configuration B has the advantage of allowing the UE to save power by being active for a shorter amount of time than in SR Configuration A.

[0100] Figure 3 This illustrates another use case where a UE can employ two or more different SR configurations in response to data arrival. Similar to SR configuration A in Figure 6, this is used when the cell may be inactive. Figure 3The second SR configuration uses multiple SR attempts to request uplink authorization. This is shown at 310, where the initial SR transmission (SR TX) using the PUCCH opportunity is followed by an SR retransmission (SRReTX), and then by the SR inactivation timer duration. Note that in period 310, the SR transmission occurs independently of the (unaligned) cell DRX activity period. SR and SR inactivation timer retransmissions are performed, also independently of the cell DRX timing. Finally, when the cell DRX activity period is available, the final SR TX occurs at the SR opportunity received by the cell during the DRX activity period, and then authorization / DCI for UE uplink data is received.

[0101] Figure 3 The diagram also illustrates the first SR configuration. Using the first SR configuration, the UE receives an indication of cell DRX and can transmit uplink data to the cell upon arrival. At the SR opportunity during cell DRX activity, the UE transmits an SR TX requesting uplink grant. The SR TX is followed by an SR inactive timer duration to allow the cell to respond. If no grant is received, the UE waits until the next available DRX activity period to retransmit the SR (SR ReTX) for uplink data transmission. After the subsequent SR inactive timer duration, the UE can receive the grant / DCI. This is in... Figure 3 It is shown in time period 312. Figure 3 In the first SR configuration, there is a similarity to Figure 2 The SR configuration offers the same power-saving advantages as the B.

[0102] like Figure 3 As shown, the example methods for operating in two SR configurations can be described as follows: 1. The UE receives configurations for one or more LCHs, wherein each LCH is associated with either a first SR configuration (non-exceptional case) or a second SR configuration (exceptional case). 2. The UE receives configuration information indicating cell DRX configuration and cell DTX configuration. The cell DRX configuration and cell DTX configuration respectively include the duration of reception activity and inactivity of one or more cells and the duration of transmission activity and inactivity of one or more cells. 3. The UE determines to send a scheduling request (SR) associated with the first LCH in one or more LCHs. 4. If the SR configuration associated with the first LCH is the first SR configuration, the UE transmits the first SR transmission at the first PUCCH timing of the first SR configuration that occurs during the first cell DRX activity duration. If no UL authorization is received after the first SR transmission and after at least one cell DTX activity duration has occurred, the UE transmits the second SR transmission at the second PUCCH timing of the first SR configuration that occurs during the second cell DRX activity duration. 5. If the SR configuration associated with the first LCH is the second SR configuration, the UE transmits the first SR transmission at the first PUCCH timing of the second SR configuration, regardless of the cell DRX configuration. If no UL authorization is received after the end of the prohibited period, the UE transmits the second SR transmission at the second PUCCH timing of the second SR configuration, regardless of the cell DTX configuration.

[0103] Figure 4 This is a flowchart 400 outlining the method performed by the Wireless Transmit / Receive Unit (WTRU) UE.

[0104] At 405, the WTRU receives configurations for one or more Logical Channels (LCHs), each LCH associated with either 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 the serving cell. At 415, the WTRU transmits an SR to the serving cell using the first LCH from the one or more LCHs. Options regarding the WTRU's behavior include employing steps 420 and 425, or steps 430 and 435.

[0105] At 420, under the condition that the first SR configuration is associated with the first LCH, the WTRU transmits the first SR on the first physical uplink control channel (PUCCH) timing of the first SR configuration that occurs during the first cell DRX activity duration. At 425, if no uplink (UL) grant is received after the first SR transmission and after at least one cell DTX activity duration has occurred, the WTRU transmits the second SR on the second PUCCH timing of the first SR configuration that occurs during the second cell DRX activity duration.

[0106] At 430, with the second SR configuration associated with the first LCH, the WTRU transmits the first SR on the first PUCCH timing of the second SR configuration, independent of the cell DRX activity duration. At 435, if no UL authorization is received, the WTRU transmits the second SR on the second PUCCH timing of the second SR configuration, independent of the cell DRX activity duration.

[0107] The method may also include the following features: the cell DTX configuration includes the transmission active period and transmission inactive period of the serving cell, and the cell DRX configuration includes the reception active period and reception inactive period of the serving cell.

[0108] The method may also include the following feature: triggering a new SR using a WTRU configured with a second SR, even if the WTRU has available uplink (UL) authorization and the available authorization overlaps with the cell DRX inactivity period.

[0109] The method may also include the following feature: using the WTRU configured with the second SR to monitor the physical downlink control channel (PDCCH) when any SR is pending, even if the cell DTX mode is inactive.

[0110] The method may also include the following additional steps: if the pending buffer status report / scheduling request (BSR / SR) is multiplexed on the physical uplink shared channel (PUSCH) payload, and the transmitted payload occurs during the cell DRX activity period, an ACK is received, or the reference received power (RSRP) is measured to be greater than a threshold, then the WTRU cancels the BSR / SR.

[0111] BSR transmission during cell DTX / DRX The UE can apply the above procedure to the transmission of a PUSCH with a multiplexed SR or a multiplexed BSR. For pending BSRs / SRs multiplexed on the PUSCH payload, the UE can cancel only the BSR and / or the associated SR if at least one of the following conditions is met: 1. The transmitted payload during the cell's DRX enabled duration, 2. The UE has received DL signaling, which includes HARQ-ACK feedback as part of the ACK for this payload, i.e., DFI or DCI signaling HARQ ACK feedback. 3. The UE has received another authorization with the same HARQ procedure ID and an NDI flip. 4. The UE has received an instruction indicating the reception of the payload via DCI. 5. The UE has received authorization to transmit new UL data (using the same or a different HARQ procedure ID). 6. The UE has received a DL signal or channel (e.g., PDSCH scheduling). 7. The UE has identified HARQ-ACK feedback as an ACK for this payload.

[0112] The UE can be configured or predefined to transmit PUSCH containing BSR MAC CE only on a subset of CG timings (e.g., a pre-configured mode for PUSCH timings). Once the BSR has been transmitted, once the BSR has been transmitted on such a subset of CG timings, and / or after a period of cell DTX activity has elapsed since the BSR transmission, the UE can (re)start the BSR retransmission timer and / or the BSR periodic timer.

[0113] A UE may transmit a PUSCH containing a BSR and / or multiplex a BSR MAC CE on PUSCH resources if one or more of the following conditions are met: 1. The timing of PUSCH overlaps with the cell DRX activity period. 2. In order to perform channel estimation, beam pair establishment, and select an appropriate SRI for CG transmission, the UE has received the SSB and / or reference signal before transmitting the BSR. 3. The UE has measured one or more channel conditions that are above the threshold. For example, the UE has measured an SSB or CSI-RS that is above the threshold (e.g., RLM or BFD related channels meet the threshold), or a BLER that is below the threshold. 4. The PUSCH timing should be no more than x milliseconds or time slots away from the next cell DTX activity period or the expected PDCCH monitoring timing. 5. BSR is of some type (e.g., regular, filled, or periodic). 6. BSR reports data from a specific LCH or LCG (which can be configured or predefined) or data from a configured priority index.

[0114] For a triggered pending BSR, the UE can choose on which CG (or PUSCH) timing to reuse it based on whether one or more of the above conditions are met.

[0115] If a regular pending BSR has been transmitted but not cancelled, the UE can trigger a new BSR when the new data arrives, even if the priority of the new data is not higher than the highest priority data in the transmitted pending BSRs. This may additionally depend on: the amount of new data arriving is higher than a threshold, the cell DRX activity period overlaps on available PUSCH resources on which the newly triggered BSR can be reused, and / or the new data comes from a subset of DRB / LCH / LCG or associated LCH priorities.

[0116] If the UE has not received additional grants and / or scheduling since the BSR was transmitted, the CG timer for the HARQ procedure associated with the TB carrying the BSR MAC CE has expired, and / or the CG retransmission timer has expired, the UE may trigger another SR / BSR.

[0117] If the serving cell is in cell DTX and / or cell DRX, the UE can be configured with alternative values ​​for the following parameters for its use: periodicBSR-Timer; retxBSR-Timer, logicalChannelSR-DelayTimerApplied, logicalChannelSR-DelayTimer, logicalChannelSR-Mask, and logicalChannelGroup. For example, when activating cell DRX and / or cell DTX, the UE can apply the alternative values ​​configured for such parameters.

[0118] Logical Channel Prioritization (LCP) specific cell DRX limits The configuration of LCP reuse restrictions allows the UE to reuse a subset of LCH on resources that do not overlap with cell DRX activity periods.

[0119] The UE can be configured with LCP logical channel selection restrictions or rules for each LCH or DRB related to uplink data transmission during cell DRX active periods, cell DRX inactive periods, and / or during cell DRX activation periods (i.e., after receiving cell DRX activation data). For example, the UE can be configured such that data from LCH A and B is allowed to be multiplexed on grants overlapping with cell DRX inactive periods. For grants during cell DRX inactive periods, if the UE has already buffered data from LCH A and C, the UE is allowed to multiplex and transmit data from LCH A only for such grants.

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

[0121] The UE can be configured to allow the UE to transmit uplink data and / or signals during cell DRX active periods, cell DRX inactive periods, and / or during cell DRX active periods (i.e., after the cell DRX active period is received). This configuration can be configured via RRC signaling and / or SIB signaling. The UE can determine such configuration based on its capabilities or capability-related configurations.

[0122] In one example embodiment, the method for adapting SR transmission in cell DTX / DRX, as disclosed in the section titled "Impact of Cell DTX / DRX on Scheduling Process / SR Transmission During Cell DTX / DRX" above, may include the following features: 1. The UE is configured with a first SR configuration and a second SR configuration; a. Each SR configuration is configured with a mapping to the LCH set. 2. The UE is configured with cell DTX and cell DRX, including the duration of activity and the duration of inactivity; 3. The UE receives signaling instructing the activation of cell DTX and / or cell DRX in the serving cell; 4. The UE triggers a new SR during C-DRX and cell DTX inactivity periods. The UE can also trigger such an SR if the only available authorization overlaps with a cell DRX inactivity period, even if the UE has an available UL authorization. 5. If the triggered SR is mapped to the first SR configuration (triggered by the first LCH set), a. The UE transmits the SR at the next applicable PUCCH timing configured in the first SR, even if the cell DTX and / or cell DRX modes are inactive. b. The UE monitors the PDCCH while the SR is pending, even if the cell DTX mode is inactive. 6. If the triggered SR is mapped to a second SR configuration (triggered by a second LCH set); a. The UE transmits the SR on the next applicable PUCCH timing of the second SR configuration that overlaps with the cell DRX activity period; b. If the prohibition timer has expired, the UE will retransmit the SR after the DTX activity period has elapsed since the last SR transmission; 7. For pending BSR / SR multiplexed on PUSCH payload, if the transmitted payload occurs during the cell DRX activity period, an ACK is received, or RSRP is measured to be greater than the threshold, the UE may cancel only the BSR / SR.

[0123] in conclusion Although the features and elements are provided above in specific combinations, those skilled in the art will appreciate that each feature or element can be used alone or in any combination with other features and elements. This disclosure is not limited in its description of the specific embodiments described herein, which are intended as illustrative of various aspects. Many modifications and variations can be made without departing from its spirit and scope, as will be apparent to those skilled in the art. Elements, actions, or instructions used in this specification should not be construed as essential or indispensable to the invention unless expressly stated otherwise. In addition to those enumerated herein, functionally equivalent methods and apparatus within the scope of this disclosure will be apparent to those skilled in the art from the above description. Such modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only to the items of the appended claims and the full scope of their equivalents. It should be understood that this disclosure is not limited to any particular method or system.

[0124] For simplicity, the above embodiments are discussed in terms of the terminology and structure of infrared functional devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0125] It should also be understood that the terminology used herein is for describing particular embodiments only and is not intended to be limiting. As used herein, the term “video” or the term “image” may mean any of a snapshot, a single image, and / or multiple images displayed on a time-based basis. As another example, when referred to herein, the term “user equipment” and its abbreviation “UE,” the term “remote,” and / or the term “head-mounted display” or its abbreviation “HMD” may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of many embodiments of a WTRU; (iii) a device configured with some or all of the structure and functions of a WTRU for wireless and / or wired functions (e.g., shared via a mobile phone); (iv) a device configured with less than all the structure and functions of a WTRU for wireless and / or wired functions; and so on. Figures 1A to 1D Details of example WTRUs that may represent any WTRU described herein are provided. As another example, various disclosed embodiments are described above and below herein as utilizing head-mounted displays. Those skilled in the art will appreciate that devices other than head-mounted displays can be utilized, and some or all of this disclosure and the various disclosed embodiments can be modified accordingly without improper experimentation. Examples of such other devices may include drones or other devices configured to allow information to flow to provide an adapted realistic experience.

[0126] Furthermore, the methods described herein can be implemented in computer programs, 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 via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magnetic-optical media, and optical media (such as CD-ROMs and digital versatile discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0127] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the wide variety of applicable embodiments, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the appended claims. For example, embodiments provided herein include handheld devices that may include or utilize any suitable voltage source (such as a battery) to provide any suitable voltage.

[0128] Furthermore, in the embodiments provided above, references to processing platforms, computing systems, controllers, and other devices including processors are mentioned. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions, operations, or instructions can be executed by various CPUs and memories. Such actions and operations or instructions may be referred to as “being executed,” “being executed by the computer,” or “being executed by the CPU.”

[0129] Those skilled in the art will appreciate that the actions and symbols representing operations or instructions include the manipulation of electrical signals by the CPU. Electrical systems represent data bits that can cause a transformation or reduction of electrical signals and maintain data bits at memory locations in a memory system, thereby reconfiguring or otherwise altering the operation of the CPU, and other signal processing. The memory location maintaining the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs mentioned above, and other platforms and CPUs may support the provided methods.

[0130] Data bits can also be maintained on a computer-readable medium, including 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 can include cooperative or interconnected computer-readable media that are exclusively present on the processing system or 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 memories mentioned above, and other platforms and memories may support the provided methods.

[0131] In the illustrative embodiments, any operations, processes, etc., described herein can be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions can be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0132] There is little difference between the hardware and software implementations of the various aspects of the system. The use of hardware or software typically (but not always, as the choice between hardware and software may become important in some contexts) represents a design choice that represents a cost-efficiency trade-off. Various vehicles may exist by which the processes and / or systems and / or other technologies (e.g., hardware, software, and / or firmware) described herein can be implemented, and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are paramount, the implementer may choose a vehicle primarily based on the hardware and / or firmware. If flexibility is paramount, the implementer may choose a primary software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0133] The above detailed description has illustrated various embodiments of the apparatus and / or process using block diagrams, flowcharts, and / or examples. Since such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide variety of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein can be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in an integrated circuit as one or more computer programs running on one or more computers (e.g., implemented as one or more programs running on one or more computer systems), implemented as one or more programs running on one or more processors (e.g., implemented as one or more programs running on one or more microprocessors), implemented as firmware, or virtually any combination thereof, and in light of this disclosure, designing circuits and / or writing code for software and / or firmware will be well within the skill of those skilled in the art. Furthermore, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a variety of program products, and that the illustrative embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used for the actual implementation of the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media, such as floppy disks, hard disks, CDs, DVDs, digital tapes, computer memory, etc.; and transmission media, such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0134] Those skilled in the art will recognize that it is common practice in the art to describe devices and / or processes in the manner set forth herein, and subsequently to use engineering practice 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 can be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system typically includes one or more of the following: a system unit housing, a video display device, memory (such as volatile and non-volatile memory), a processor (such as a microprocessor and a digital signal processor), computing entities (such as an operating system, drivers, a graphical user interface, and applications), one or more interactive devices (such as a touchpad or screen), and / or a control system including feedback loops and control motors (e.g., feedback for sensing position and / or speed, control motors for moving and / or adjusting the number and quantity of components). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0135] The topics described herein sometimes illustrate different components that are included within or connected to different other components. It should be understood that the architectures depicted are merely examples, and in fact, many other architectures can be implemented to achieve the same functionality. Conceptually, any arrangement of components that achieve the same functionality is effectively “associated” to enable the desired functionality. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” with each other to enable the desired functionality, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, physically paired and / or physically interacting components and / or wirelessly interacting components and / or logically interacting and / or potentially interacting components.

[0136] Regarding the use of virtually any plural and / or singular terms herein, those skilled in the art can convert from plural to singular and / or from singular to plural where appropriate for the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0137] Those skilled in the art will understand that, in general, the terminology used herein, and especially in the appended claims (e.g., the body of the appended claims), is intended to be “open” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will further understand that if the intent is a specific number recited in the introduced claim, such intent will be explicitly stated in the claim, and if such a statement is not made, such intent does not exist. For example, the term “single” or similar language may be used where the intent is only one item. As an aid to understanding, the appended claims and / or the description herein may include the use of introductory phrases such as “at least one” and “one or more” to introduce the recitation of the claims. However, the use of such phrases should not be construed as implying that the introduction of a claim by the indefinite article “a” or “an” will include any particular claim contained in such an introduction limited to an embodiment containing only one such claim, 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 as meaning “at least one” or “one or more”). The same applies to the use of definite articles used to introduce a claim. Furthermore, even if a specific number is explicitly stated in the introduced claim, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the number stated (e.g., an unmodified statement of “two statements” without other modifiers means at least two statements or two or more statements). Furthermore, in instances where a convention similar to "at least one of A, B, and C" is used, generally, in the sense that a person skilled in the art would understand, such a construction is intended (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having only A, a system having only B, a system having only C, a system having both A and B, a system having both A and C, a system having both B and C, and / or a system having both A, B, and C, etc.). In instances where a convention similar to "at least one of A, B, or C" is used, generally, in the sense that a person skilled in the art would understand, such a construction is intended (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, a system having only A, a system having only B, a system having only C, a system having both A and B, a system having both A and C, a system having both B and C, and / or a system having both A, B, and C, etc.).Those skilled in the art will further understand that virtually any disjunctive terms and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include the possibility of including one, any, or both of the terms. For example, the phrase “A or B” would be understood to include the possibility of “A” or “B” or “A and B”. Further, as used herein, the term “any one of…” followed by a list of items and / or categories of items is intended to include, alone or in combination with other items and / or categories of items, “any one,” “any combination,” “any plurality,” and / or “any combination of plurality”. Additionally, as used herein, the term “set” is intended to include any number of items, including zero. Furthermore, as used herein, the term “number” is intended to include any number, including zero. Moreover, as used herein, the term “plural” is intended to be synonymous with “multiple.”

[0138] Furthermore, where features or aspects of this disclosure are described in accordance with the Markush group, those skilled in the art will recognize that this disclosure is therefore also described in accordance with any individual member or subgroup of the Markush group.

[0139] As those skilled in the art will understand, for any and all purposes, such as in providing a written description, all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily identified as adequately describing the same scope and capable of being decomposed into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily decomposed into a lower third, middle third, and upper third, etc. As those skilled in the art will also understand, all language such as “up to,” “at least,” “greater than,” “less than,” etc., includes the stated number and refers to a scope that can subsequently be decomposed into subscopes as discussed above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, and so on.

[0140] Furthermore, claims should not be construed as limited to the provided order or elements unless otherwise stated. Additionally, the use of the term "means for..." in any claim is intended to invoke 35 USC §112, ¶ 6 or the "means plus function" claim format, and any claim not containing the term "means for..." is not intended to do so.

Claims

1. A wireless transmit / receive unit (WTRU) including circuitry, said circuitry comprising a transmitter, a receiver, a processor, and a memory, said WTRU being configured to: Receive configurations for one or more logical channels (LCHs), wherein each LCH is associated with a first scheduling request (SR) configuration or a second SR configuration; Receive one or more of the cell discontinuous transmission (cell DTX) configuration and cell discontinuous reception (cell DRX) configuration for the serving cell; The SR is transmitted to the serving cell using the first LCH of the one or more LCHs, such that: Under the condition that the first SR configuration is associated with the first LCH, the WTRU transmits the first SR on the first physical uplink control channel (PUCCH) timing of the first SR configuration during the first cell DRX activity duration, and if no uplink (UL) grant is received after the first SR transmission after at least one cell DTX activity duration has occurred, the WTRU transmits the second SR on the second PUCCH timing of the first SR configuration during the second cell DRX activity duration. as well as When the second SR configuration is associated with the first LCH, the WTRU transmits the first SR on the first PUCCH timing of the second SR configuration independently of the cell DRX activity duration, and if no UL authorization is received, the WTRU transmits the second SR on the second PUCCH timing of the second SR configuration independently of the cell DRX activity duration.

2. The WTRU according to claim 1, wherein, The cell DTX configuration includes the transmission activity period and transmission inactivity period of the serving cell, and the cell DRX configuration includes the cell DRX activity period and cell DRX inactivity period of the serving cell.

3. The WTRU according to claim 2, wherein, Even if the WTRU has available UL authorization and the available authorization overlaps with the cell DRX inactivity period, the WTRU configured with the second SR also triggers a new SR.

4. The WTRU of claim 1, wherein even when the cell DTX mode is inactive, the WTRU configured with the second SR monitors the Physical Downlink Control Channel (PDCCH) when any SR is pending.

5. The WTRU according to claim 1, further configured as follows: If a pending buffer status report / scheduling request (BSR / SR) is multiplexed onto a physical uplink shared channel (PUSCH) payload, the WTRU cancels the BSR / SR if the transmitted payload occurs during a cell DRX activity period, an ACK is received, or the reference received power (RSRP) is measured to be greater than a threshold.

6. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: Receive configurations for one or more logical channels (LCHs), wherein each LCH is associated with a first scheduling request (SR) configuration or a second SR configuration; Receive one or more of the cell discontinuous transmission (cell DTX) configuration and cell discontinuous reception (cell DRX) configuration for the serving cell; The SR is transmitted to the serving cell using the first LCH of the one or more LCHs, such that: Under the condition that the first SR configuration is associated with the first LCH, the WTRU transmits the first SR at the first PUCCH timing of the first SR configuration during the first cell DRX activity duration, and if no uplink (UL) grant is received after the first SR transmission after at least one cell DTX activity duration has occurred, the WTRU transmits the second SR at the second PUCCH timing of the first SR configuration during the second cell DRX activity duration. as well as When the second SR configuration is associated with the first LCH, the WTRU transmits the first SR on the first PUCCH timing of the second SR configuration independently of the cell DRX activity duration, and if no UL authorization is received, the WTRU transmits the second SR on the second PUCCH timing of the second SR configuration independently of the cell DRX activity duration.

7. The method according to claim 6, wherein, Receiving the cell DTX configuration includes: receiving information including the transmission activity period and transmission inactivity period of the serving cell, and the cell DRX configuration includes the cell DRX activity period and cell DRX inactivity period of the serving cell.

8. The method according to claim 7, wherein, If the WTRU transmits the first SR at the first PUCCH timing of the second SR configuration, the WTRU will trigger a new SR even if the WTRU has available UL authorization and the available authorization overlaps with the cell DRX inactivity period.

9. The method according to claim 6, wherein, The method further includes, provided that the WTRU transmits the first SR at the first PUCCH timing of the second SR configuration, the WTRU monitoring the physical downlink control channel (PDCCH) when any SR is pending, even if the cell DTX mode is inactive.

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

11. A non-transitory computer-readable storage medium having instructions, wherein when the instructions are executed by a computer, the method according to any one of claims 6-10 is performed.

Images