Method and apparatus for burst transmission

By implementing periodic and semi-persistent search spaces with dynamic activation in WTRUs, the inefficiencies of long search space periodicity are addressed, optimizing power consumption and reducing active times for burst data transmission.

JP7583089B2Active Publication Date: 2024-11-13INTERDIGITAL PATENT HOLDINGS INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023038289
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2018-09-26
Filing Date
2023-03-13
Publication Date
2024-11-13
Estimated Expiration
2039-09-26

AI Technical Summary

Technical Problem

The long periodicity of search spaces in wireless communications increases the active time of wireless transmit/receive units (WTRUs) when burst data arrives, leading to inefficient uplink transmission and increased battery consumption, particularly for infrequent data traffic.

Method used

Configuring WTRUs with periodic and semi-persistent search spaces (P-SS and SP-SS) to monitor control channels, allowing dynamic activation/deactivation based on traffic patterns, and adjusting monitoring periodicity to optimize power consumption and reduce active times.

Benefits of technology

This approach reduces WTRU power consumption and minimizes unnecessary active times by dynamically adapting to burst traffic patterns, enhancing efficiency and battery life.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583089000001
    Figure 0007583089000001
  • Figure 0007583089000002
    Figure 0007583089000002
  • Figure 0007583089000003
    Figure 0007583089000003
Patent Text Reader

Abstract

To provide a method and apparatus for burst transmission.SOLUTION: A wireless transmit / receive unit (WTRU) is configured to receive configuration information for a periodic search space (P-SS) and a semi-persistent search space (SP-SS). The configuration information includes a monitoring periodicity of the P-SS and a monitoring periodicity of the SP-SS. The P-SS is associated with the SP-SS. The WTRU is configured to monitor the P-SS with the periodicity of the P-SS. The WTRU is configured to receive a first message in a first physical downlink control channel (PDCCH) in a slot of the P-SS. The first message indicates an activation of the associated SP-SS. The WTRU is configured to monitor the SP-SS using the periodicity of the SP-SS. The WTRU is configured to receive a second message in a second PDCCH in a slot of the SP-SS.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present application relates to a method and apparatus for burst transmission, and more particularly, to a method and apparatus for burst transmission in wireless communications. [Background technology]

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 62 / 736,874, filed Sep. 26, 2018, the contents of which are incorporated herein by reference.

[0003] A wireless transmit / receive unit (WTRU) may monitor or be assigned a set of physical downlink control channel (PDCCH) candidates to monitor. The set of PDCCH candidates may be monitored during blind detection of the PDCCH. The search space or set of search spaces may be or include, for example, a set of PDCCH candidates to monitor with blind detection. The search space may be configured with a long periodicity to reduce the PDCCH monitoring time to reduce the battery consumption of the WTRU when the WTRU has infrequent data traffic. However, the long periodicity of the search space may increase the WTRU active time when burst data arrives in the buffer, which may require multiple transmissions of the physical downlink shared control channel (PDSCH) or physical uplink shared control channel (PUSCH) to finish transmitting. Since the uplink transmission bandwidth may be further limited based on the WTRU coverage level, a longer active time may be more significant for uplink burst traffic. Summary of the Invention

[0004] A method and apparatus are provided for burst transmission. In an aspect, a wireless transmit / receive unit (WTRU) is configured to receive configuration information for a periodic search space (P-SS) and a semi-persistent search space (SP-SS). The configuration information may include a monitoring periodicity of the P-SS and a monitoring periodicity of the SP-SS. The P-SS may be associated with the SP-SS. The WTRU is configured to monitor the P-SS using the periodicity of the P-SS. The WTRU is configured to receive a message in a control channel of the P-SS. The message may indicate activation of the associated SP-SS. The WTRU is configured to monitor the SP-SS using the periodicity of the SP-SS. The WTRU is configured to receive a message in a physical downlink shared channel in a slot of the SP-SS. The monitoring periodicity may indicate a timeslot repetition. The configuration information may include a monitoring offset and a monitoring mapping. The WTRU may send an indication of a capability to support the SP-SS. The WTRU is configured to stop monitoring the SP-SS based on the SP-SS deactivation decision. The WTRU is configured to monitor in the P-SS with a periodicity of the P-SS. The WTRU is configured to receive a message in a control channel of the P-SS. The message may include an updated periodicity of the P-SS. The WTRU is configured to monitor the P-SS using the updated periodicity.

[0005] In an aspect, a WTRU is configured to receive a first downlink control information (DCI) in a physical downlink control channel (PDCCH) in a periodic search space (P-SS). The first DCI may indicate a scheduling configuration for a first aperiodic search space (A-SS). The WTRU is configured to monitor in a first A-SS based on the first DCI scheduling configuration. The WTRU is configured to receive a second DCI in a PDCCH in the first A-SS. The second DCI indicates a scheduling configuration for the second A-SS. The WTRU is configured to monitor in a second A-SS based on the second DCI scheduling configuration. The WTRU is configured to receive a third DCI in a PDCCH in the second A-SS. The third DCI may include a scheduling configuration for multiple A-SSs.

[0006] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate similar elements and in which: [Brief description of the drawings]

[0007] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed aspects may be implemented. [Figure 1B] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communication system illustrated in FIG. 1A according to an embodiment. [Figure 1C] FIG. 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A according to an embodiment. [Figure 1D] FIG. 1B is a system diagram illustrating a further example RAN and a further example CN that may be used within the communication system illustrated in FIG. 1A according to an embodiment. [Diagram 2] FIG. 1 illustrates an example of discontinuous signal reception (DRX). [Diagram 3]FIG. 1 illustrates an example of a wake-up signal (WUS) and a go-to-sleep (GOS) along with DRX operation. [Figure 4] 1 illustrates an example of a long WTRU active time for bursty traffic. [Diagram 5] FIG. 1 illustrates an example of a semi-persistent search space (SP-SS) for support of bursty traffic along with a long periodic search space (P-SS). [Figure 6] FIG. 1 illustrates an example of using a semi-persistent search space (SP-SS) for support of bursty traffic. [Figure 7] A figure showing an example of a first DCI triggering multiple aperiodic search spaces (A-SS). [Figure 8] A diagram showing an example of DCI triggering a single aperiodic search space (A-SS). [Figure 9] A diagram showing an example method for DCI to trigger a single aperiodic search space (A-SS). [Figure 10] A diagram showing an example of a PDSCH burst transmission with a single DCI scheduling the burst. [Figure 11] FIG. 2 illustrates an exemplary configuration for PDSCH burst transmission. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] 1A is a diagram illustrating an example communication system 100 in which one or more disclosed aspects may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messages, broadcasts, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tailed Unique Word Discrete Fourier Transform Spread OFDM (ZT-UW-DFT-S-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multi-Carrier (FBMC), etc.

[0009] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be appreciated that the disclosed aspects contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and / or receive wireless signals and may include 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, hotspot devices or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, 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 an industrial and / or automated processing chain context), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0010] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a home NodeB, a home eNode B, a next generation NodeB such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0011] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for wireless services in a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one aspect, the base station 114a may include three transceivers, one for each sector of the cell. In an aspect, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

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

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

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

[0015] In an aspect, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.

[0016] In an aspect, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE and NR radio access, e.g., using a dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

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

[0018] The base station 114b in FIG. 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity within a localized area, such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by a drone), a road, etc. In one aspect, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.11, to establish a wireless local area network (WLAN). In one aspect, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.15, to establish a wireless personal area network (WPAN). In yet another aspect, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-Pro, NR, etc.) to establish a picocell or femtocell. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.

[0019] The RAN 104 may communicate with the CN 106, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various Quality of Service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, charging services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and / or the CN 106 may communicate directly or indirectly with other RANs that use the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also communicate with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technologies.

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

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

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

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

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

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

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

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

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

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

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

[0031] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals associated with a particular subframe (e.g., for both UL (e.g., for transmission) and DL (e.g., for reception) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., via a separate processor (not shown) or via the processor 118). In an aspect, the WTRU 102 may include a half-duplex radio for transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or DL ​​(e.g., for reception)).

[0032] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an aspect. As discussed above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

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

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

[0035] 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

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

[0040] Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, it is contemplated that in some representative aspects such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications network.

[0041] In an exemplary embodiment, the other network 112 may be a WLAN.

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

[0043] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or may be dynamically set. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In some representative aspects, carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. With CSMA / CA, STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected by a particular STA and / or determined to be busy by a particular STA, that particular STA may be backed off. One STA (e.g., only one station) may transmit on a given BSS at any given time.

[0044] A high throughput (HT) STA may use a 40 MHz wide channel for communication, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0045] A very high throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz channels. The 40 MHz and / or 80 MHz channels may be formed by combining consecutive 20 MHz channels. The 160 MHz channel may be formed by combining eight consecutive 20 MHz channels or two non-consecutive 80 MHz channels, the latter sometimes referred to as an 80+80 configuration. For the 80+80 configuration, the data after channel encoding may be passed through a segment parser that may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped onto two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed, and the combined data may be sent to the media access control (MAC).

[0046] Sub-1 GHz modes of operation are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah 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, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative aspect, 802.11ah may support MTC, such as meter type control / machine type communication (MTC) devices in macro coverage areas. MTC devices may have some capabilities, for example, limited capabilities including support for some and / or limited bandwidths (e.g., only support for this). MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0047] A WLAN system that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, includes a channel, which may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the smallest bandwidth operating mode from all STAs when operating in the BSS. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only) the 1 MHz mode, even if they are APs, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) setting may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (that only supports 1 MHz mode of operation) transmitting to the AP, all available frequency bands may be considered busy even if the majority of the available frequency bands remain idle.

[0048] In the United States, the available frequency bands that can be used by 802.11ah are 902MHz to 928MHz. In South Korea, the available frequency bands are 917.5MHz to 923.5MHz. In Japan, the available frequency bands are 916.5MHz to 927.5MHz. The total available bandwidth for 802.11ah is 6MHz to 26MHz depending on the country code.

[0049] 1D is a system diagram illustrating the RAN 104 and the CN 106 according to an aspect. As discussed above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 104 may also communicate with the CN 106.

[0050] The RAN 104 may include gNBs 180a, 180b, 180c, although it will be appreciated that the RAN 104 may include any number of gNBs while still being consistent with the aspects. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an aspect, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may transmit wireless signals to and / or receive wireless signals from the WTRU 102a, for example, using multiple antennas. In an aspect, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, and the remaining component carriers may be on a licensed spectrum. In an aspect, the gNBs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).

[0051] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0052] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing any other RAN (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with a gNB 180a, 180b, 180c, but may also communicate / connect with another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRUs 102a, 102b, 102c.

[0053] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support for network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other over an Xn interface.

[0054] 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0055] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating non-access stratum (NAS) signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low-latency (URLLC) access, services relying on enhanced large capacity mobile broadband (eMBB) access, services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-Pro, and / or non-3GPP access technologies, such as WiFi.

[0056] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 106 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 106 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0057] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks such as the Internet 110 to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.

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

[0059] In view of Figures 1A-1D and the corresponding description thereof, one or more, or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network functions and / or WTRU functions.

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

[0061] The one or more emulation devices may perform one or more functions, including but not limited to, while not implemented / deployed as part of a wired and / or wireless communications network. For example, the emulation devices may be utilized in testing laboratories and / or testing scenarios in undeployed (e.g., testing) wired and / or wireless communications networks to perform testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0062] FIG. 2 illustrates an example of discontinuous reception (DRX). DRX may be used for battery conservation. DRX may have a cycle of ON and OFF durations, which may be repetitive or periodically repetitive. During DRX, the WTRU may not monitor a downlink (DL) control channel (e.g., PDCCH). In a radio resource control (RRC) connected mode, the WTRU may use connected mode DRX (C-DRX). The WTRU may monitor a configured PDCCH during the ON duration, and the WTRU may sleep or not monitor during the OFF duration. Although the PDCCH is used herein as a non-limiting example of a DL control channel, any other type of DL control channel may be used. The DRX cycle may be a short DRX cycle or a long DRX cycle. The WTRU may switch between using a short DRX cycle and using a long DRX cycle.

[0063] The DRX inactivity timer may determine or may be used to determine the time after a PDCCH opportunity when a successfully decoded PDCCH indicates a UL user data transmission or a DL user data transmission, e.g., an initial data transmission. This time may be in terms of TTI duration. The DRX inactivity timer may be used to determine when to enter the OFF duration.

[0064] A PDCCH opportunity may be a time period that may include a PDCCH, such as a symbol, a set of symbols, a slot, or a subframe. A DRX ON duration may be a duration at the beginning of a DRX cycle. An ON duration timer may determine or may be used to determine the number of PDCCH opportunities that may or may need to be monitored or decoded by the WTRU. For example, a PDCCH opportunity to monitor or decode may be after a wakeup from a DRX cycle or at the beginning of a DRX cycle. A PDCCH opportunity may be a sequential number of a PDCCH opportunity. A PDCCH opportunity may be a non-sequential PDCCH opportunity.

[0065] The DRX retransmission timer may determine or may be used to determine the number of PDCCH opportunities to monitor when a retransmission may be expected by the WTRU. The DRX retransmission timer may determine or may be used to determine the maximum duration until a DL retransmission may be received or until a grant for a UL retransmission may be received.

[0066] The DRX short cycle may be the first DRX cycle that the WTRU enters after the expiration of the DRX inactivity timer. The WTRU may be in the short DRX cycle until the expiration of the DRX short cycle timer. When the DRX short cycle timer expires, the WTRU may use the long DRX cycle. The DRX short cycle timer may determine, or may be used to determine, the number of consecutive subframes that the WTRU may track a short DRX cycle for after the DRX inactivity timer expires.

[0067] During the OFF duration, the WTRU may not measure or report channel state information (CSI) in subframes configured to measure and / or report periodic CSI.

[0068] The WTRU may or may need to monitor the PDCCH or PDCCH opportunities during active time. Active time may occur during an ON duration or during an OFF duration. Active time may start during an ON duration and continue during an OFF duration. The terms active time and active time of a DRX cycle may be used interchangeably herein.

[0069] The active time may include the time when a timer, such as an ON duration timer, an inactivity timer, a DL retransmission timer, a UL retransmission timer, or a random access contention resolution timer, is running. The active time may include the time when a scheduling request is sent, for example, on the PUCCH and is pending. The active time may include the time when a PDCCH is not received indicating a new transmission addressed to the Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity of the WTRU after successful reception of a random access response to a random access preamble that is not selected by the MAC entity among the contention-based random access preambles.

[0070] The DRX timer may be a timer associated with DRX. One or more DRX timers may be associated with DRX. Examples of DRX timers may include, but are not limited to, a DRX ON duration timer (e.g., drx-onDurationTimer), a DRX inactivity timer (e.g., drx-InactivityTimer), a DRX DL retransmission timer (e.g., drx-RetransmissionTimerDL), a DRX UL retransmission timer (e.g., drx-RetransmissionTimerUL), a DRX Hybrid Automatic Repeat Request Round Trip Timer (HARQ RTT) timer for UL (e.g., drx-HARQ-RTT-TimerUL), and a DRX HARQ RTT timer for DL ​​(e.g., drx-HARQ-RTT-TimerDL).

[0071] The DRX inactivity timer may be a duration after a PDCCH opportunity where the PDCCH indicates an initial uplink user data transmission or an initial downlink user data transmission for the MAC entity. The DRX DL retransmission timer may be a maximum duration before a downlink retransmission is received. Each downlink HARQ process may be associated with a DRX DL retransmission timer. The DRX UL retransmission timer may be a maximum duration before a grant for an uplink retransmission is received. Each uplink HARQ process may be associated with a DRX UL retransmission timer. The DRX HARQ RTT timer for the uplink may be a minimum duration before an uplink HARQ retransmission grant is expected by the WTRU or the MAC entity. Each uplink HARQ process may be associated with a DRX HARQ RTT timer for the uplink. The DRX HARQ RTT timer for the downlink may be a minimum duration before a downlink allocation for a HARQ retransmission grant is expected by the WTRU or the MAC entity. Each downlink HARQ process may be associated with a DRX HARQ RTT timer for the downlink.

[0072] FIG. 3 illustrates an example of a wake-up signal (WUS) and a go-to-sleep (GOS) along with DRX operation. A WUS may be used along with DRX operation. A GOS may be used along with DRX operation. In a system or network, either a WUS or a GOS may be used. Both a WUS and a GOS may be used. A WUS / GOS may be associated with one or more DRX cycles. A WUS / GOS may be transmitted and / or received before an associated time or a portion of an associated DRX cycle. If a WTRU receives a WUS, the WTRU may monitor a PDCCH in an ON duration for one or more DRX cycles. If a WTRU receives a GOS, the WTRU may skip monitoring a PDCCH in an ON duration for one or more DRX cycles and may remain in a sleep mode (e.g., deep sleep).

[0073] In systems such as 3GPP New Radio (NR) for 5G wireless systems, new structures and designs may be adopted for the PDCCH and the Physical Downlink Shared Channel (PDSCH). Slot-based and non-slot-based transmissions and different rate monitoring may be used for the PDCCH.

[0074] A resource element group (REG) may be the smallest building block for a PDCCH. A REG may consist of 12 resource elements (REs) on one OFDM symbol in time and one resource block (RB) in frequency. In a REG, 9 REs may be used for control information and 3 REs may be used for demodulation reference signals (DMRSs). Multiple REGs (e.g., 2, 3, or 6) that are adjacent in time or frequency may form a REG bundle that may be used with the same precoder and their DMRSs may be used together for channel estimation. Six REGs (e.g., in a format of 1, 2, or 3 REG bundles) may form one control channel element (CCE), which may be the smallest possible PDCCH. A PDCCH may consist of one or more CCEs (e.g., 1, 2, 4, 8, or 16 CCEs). The number of CCEs for a PDCCH may be referred to as its aggregation level (AL).

[0075] The mapping of REG bundles may use interleaving or non-interleaving. In non-interleaving mapping, consecutive REG bundles (e.g., adjacent in frequency) may form a CCE, and adjacent CCEs in frequency may form a PDCCH. In interleaving mapping, REGs may be interleaved or permuted before being mapped to CCEs, which may result in non-adjacent REG bundles within one CCE and non-adjacent CCEs within one PDCCH.

[0076] A control resource set (CORESET) may be configured by or may comprise at least one of: i) frequency allocation (e.g., as chunks of 6 RBs); ii) time length (e.g., 1-3 OFDM symbols); iii) type of REG bundle; and iv) type of mapping from REG bundle to CCE, which may use interleaving or non-interleaving. In a bandwidth portion (BWP), there may be up to N (e.g., 3) CORESETs. For example, there may be 12 CORESETs in 4 possible bandwidth portions.

[0077] The WTRU may monitor or be assigned a set of PDCCH candidates to monitor. The set of PDCCH candidates may be monitored during blind detection of the PDCCH. The search space or set of search spaces for multiple aggregation levels may be or include a set of PDCCH candidates to monitor with blind detection, etc. The search space or set of search spaces may be configured by at least one of i) an associated CORESET, ii) a number of candidates for or within each aggregation level, and iii) a set of monitoring opportunities. The monitoring opportunities may include one or more of a monitoring periodicity (e.g., with respect to slots), a monitoring offset, and a monitoring pattern (e.g., 14 bits corresponding to possible patterns of symbols within a slot).

[0078] In NR, the search space may be configured with a long periodicity to lower the PDCCH monitoring time, which may be beneficial for lower WTRU battery consumption when the WTRU has infrequent data traffic, such as bursty traffic. However, as illustrated in FIG. 4, the long periodicity of the search space may increase the WTRU active time when bursty data arrives in the buffer, which may require multiple PDSCH or PUSCH transmissions to finish transmitting. Because the uplink transmission bandwidth may be further limited based on the WTRU coverage level, a longer active time may be more significant for uplink bursty traffic.

[0079] The WTRU may be configured with a CORESET and its associated search space(s). The CORESET configuration may include one or more of the following: frequency domain resources (e.g., a set of resource blocks used for the CORESET), a search space configuration, which may include one or more of the following: number of OFDM symbols, REG bundle size, CCE-REG mapping type, and associated CORESET information (e.g., CORESET-id), monitoring slot periodicity, number of decoding candidates per PDCCH aggregation level, and monitoring symbols in a slot.

[0080] The terms search space, PDCCH search space, and PDCCH monitoring opportunity may be interchangeable herein. A PDCCH monitoring opportunity may be considered a time instance (e.g., slot, subframe, and symbol) during which a WTRU may monitor one or more search spaces. The terms search space periodicity, search space monitoring periodicity, PDCCH monitoring periodicity, search space duty cycle, search space monitoring gap, PDCCH monitoring cycle, PDCCH monitoring opportunity cycle, periodicity, and search space monitoring opportunity cycle may be interchangeable herein.

[0081] When a WTRU monitors a search space, the WTRU may attempt to decode one or more PDCCH candidates in the search space. Each PDCCH candidate may comprise one or more CCEs, and the number of CCEs for a PDCCH candidate may be referred to as an aggregation level (AL). The terms PDCCH candidate, PDCCH decoding candidate, PDCCH blind decoding candidate, decoding candidate, and blind decoding candidate may be used interchangeably herein.

[0082] One or more search space types may be used. Each search space type may have a different time behavior. For example, a first search space type may be a periodic search space (P-SS), and the WTRU may monitor the search space periodically, such as every s slots, once the search space is configured. A second search space type may be a semi-persistent search space (SP-SS), and the WTRU may monitor the SP-SS when the SP-SS is in an active state. A third search space type may be an aperiodic search space (A-SS), and the WTRU may monitor the A-SS in one or more time instances, which may be dynamically indicated.

[0083] The search space type may be determined based on an indication in the RRC configuration for the search space. The search space type may be determined based on an associated DCI format or DCI type that may be monitored within the search space. The DCI format or DCI type may be determined based on a traffic type (e.g., eMBB, URLLC, or mMTC). The search space type may be determined based on a mode of operation (e.g., normal mode, power save mode). For example, the normal mode may be associated with P-SS, and the power save mode may be associated with SP-SS or A-SS.

[0084] The search space type may be used for downlink and / or uplink grants. The downlink grant may be used to schedule the PDSCH, and the uplink grant may be used to schedule the PUSCH. The PDSCH and PUSCH are non-limiting examples of channels and may be substituted for each other in the examples described herein.

[0085] The WTRU may need to monitor one or more search space types in the same slot, and when the number of blind decoding candidates and / or the number of CCEs for channel estimation is greater than a threshold, the WTRU may prioritize search spaces based on search space time domain characteristics (e.g., periodic, semi-persistent, and aperiodic) and may skip monitoring lower priority search spaces. The A-SS may be the highest priority in a WTRU-specific search space. The SP-SS may be of higher priority than the P-SS. A common search space may be of higher priority than a WTRU-specific search space. If one or more search spaces are of the same type of search space or have the same time domain characteristics, a lower search space identity number may have higher priority.

[0086] WTRU power consumption can be lowered during active times by adapting PDCCH monitoring to traffic needs (e.g., bursty traffic) using SPSS. SP-SS may be used with dynamic search space activation / deactivation and / or dynamic indication of search space monitoring periodicity. SP-SS may be used when the WTRU is configured with certain transmission modes, such as, for example, power save mode or burst transmission mode.

[0087] FIG. 5 illustrates an example of an SP-SS for support of bursty traffic with a long P-SS. In FIG. 5, the P-SS is configured with a four-slot periodicity, e.g., shown at slot s, slot s+4, slot s+8, and slot s+12. The WTRU may monitor for a PDCCH in the P-SS (e.g., every four slots). The gNB may have burst data to send to the WTRU. The SP-SS may be activated. The SP-SS may be activated via the associated P-SS. The WTRU may monitor the SP-SS at slot s+5 based on the SP-SS activation. The periodicity for the SP-SS may be configured as one slot, as illustrated in FIG. 5. The WTRU may monitor the SP-SS starting at slot s+5 and every other slot thereafter. The P-SS and SP-SS may overlap in time, e.g., at slot s+8. The SP-SS may be deactivated, e.g., at slot s+10, and the WTRU may stop monitoring the SP-SS. The WTRU may monitor the P-SS based on a 4-slot periodicity, e.g., at slot s+12. The PS-SS monitoring periodicity may be updated with the new periodicity, e.g., at slot s+12, with a 2-slot periodicity. The WTRU may monitor the P-SS with the updated periodicity, e.g., at slots s+14, s+16, etc.

[0088] FIG. 6 illustrates an example of using SP-SS for support of bursty traffic. The WTRU may receive configuration information for one or more search spaces (610). The configuration information may include a monitoring periodicity of the search space. The monitoring periodicity may indicate a time slot or a time slot repetition. The configuration information may include a monitoring offset. The configuration information may include a monitoring pattern. The WTRU may receive configuration information for multiple types of search spaces. For example, the WTRU may receive configuration information for a P-SS and an SP-SS. A SP-SS may be associated with one or more P-SSs. One or more search space configurations of a P-SS may be used or reused in the associated SP-SS. The configuration of the associated P-SS that may activate the SP-SS used to monitor the SP-SS may include DCI configuration, format, content (e.g., presence of TCI condition) i.e. aggregation level, number of PDCCH candidates per aggregation level, number of symbols in a slot or number of monitoring symbols. The SP-SS may be configured with a subset of configuration information for the P-SS. Configuration information for a P-SS that is not in the subset of configuration information may be determined based on the associated P-SS. The WTRU may receive the configuration information from the gNB. The WTRU may receive the configuration information via radio resource control (RRC) signaling or an RRC message.

[0089] The WTRU may send an indication of its capability to support SP-SS. The WTRU may send the indication to the gNB. In an example, if the WTRU has the capability to receive an activation / deactivation signal for SP-SS, the WTRU may support SP-SS. In an example, if the WTRU has the capability to support a power saving mode, the WTRU may support SP-SS. The gNB may have knowledge of the WTRU's capability to support SP-SS without the WTRU sending an indication. The gNB may know if the WTRU supports SP-SS from pre-configuration or based on the WTRU class.

[0090] The WTRU may monitor for a control channel (e.g., PDCCH) in the configured P-SS (620). The P-SS may have a monitoring periodicity, e.g., 4-slot periodicity, as shown in FIG. 5. The WTRU may monitor when the search space is activated or in an active state. The WTRU may not monitor when the search space is deactivated or in an inactive state or in a deactivated state within the search space. The WTRU may monitor the P-SS in a time location according to the configured periodicity and monitoring symbols.

[0091] The WTRU may receive information for activating an SP-SS (630). The information may be received in a PDCCH in a P-SS. The SP-SS to activate may be associated with the P-SS. The information may include an indication to deactivate the SP-SS. The information may be for multiple associated SP-SSs.

[0092] The WTRU may monitor the SP-SS for the PDCCH (640). The SP-SS may be configured with a monitoring periodicity, which may be different from the monitoring periodicity of the associated P-SS. For example, in FIG. 5, the P-SS has a 4-slot periodicity and the SP-SS has a 1-slot periodicity. The search space may be activated or deactivated via L1 signaling, for example, in the DCI received in the PDCCH. The search space may be activated or deactivated via L2 signaling, for example, in the MAC-CE. The WTRU may monitor the search space when it is in an active state (e.g., activated). For example, the search space may be configured and the WTRU may monitor the search space when the WTRU receives activation (e.g., an activation indication or activation signal) for the search space. If information received in the P-SS indicates activation of the SP-SS, the WTRU may monitor for the PDCCH in the SP-SS. The WTRU may monitor in the SP-SS based on the received configuration information. When the SP-SS is activated, the WTRU may skip monitoring the associated P-SS. The WTRU may skip monitoring the associated P-SS if the blind decoding complexity or the number of CCEs for channel estimation is higher than a threshold (e.g., WTRU capability). On condition that the information received in the P-SS indicates deactivation of the SP-SS, the WTRU may stop monitoring in the SP-SS.

[0093] The SP-SS may be activated and / or deactivated from slot #n based on, for example, the DCI, the MAC-CE, a predetermined sequence or preamble, a bit sequence scrambled with the CRC of the PDSCH, or a DM-RS sequence of the PDSCH.

[0094] In the case of a DCI received in slot #nx, the DCI may include activation and / or deactivation information for the search space, where x may be a non-negative integer (e.g., 0, 1, 2, ...). The WTRU may monitor or receive the DCI for SP-SS activation (and / or deactivation) in the P-SS, which may be based on a WTRU-specific PDCCH or a group-common PDCCH. The group-common PDCCH may be shared by a group of WTRUs. One or more Radio Network Temporary Identifiers (RNTIs) may be used for the DCI in the P-SS. If a first RNTI is used to scramble the CRC of the DCI in slot #nx, the associated SP-SS may be activated in slot #n, and the SP-SS may be in an active state until it is deactivated. If a second RNTI is used to scramble the CRC of the DCI, the associated SP-SS may keep its current state (e.g., inactive or active). If the second RNTI is used to scramble the CRC of the DCI, the associated SP-SS may be deactivated. The DCI used to activate the SP-SS herein may also be used to schedule the PDSCH or PUSCH. The x value may be indicated in the DCI.

[0095] In the case of a MAC-CE received in slot #nx, where x may be a non-negative integer, the MAC-CE may include activation and / or deactivation messages for one or more SP-SSs. The x value may be determined based on the HARQ-ACK timing of the PDCCH carrying the MAC-CE. The x value may be indicated within the MAC-CE.

[0096] If the WTRU receives a sequence or preamble in slot #nx, the SP-SS may be activated from slot #n and remain active until it is deactivated. The sequence or preamble may be a WUS. The WUS may be configured or used for the SP-SS. If the search space is a P-SS, wake-up may not be used and the search space may be monitored in the configured slot. The WUS may be configured per search space.

[0097] In the case of a bit sequence scrambled with the CRC of the PDSCH, the PDSCH may be scheduled, for example, in slot #nx. If the CRC of the PDSCH is scrambled with a unique bit sequence, the associated SP-SS may be activated in slot #n, and the PDSCH may be scheduled by the P-SS. One or more bit sequences for scrambling may be used. If the WTRU receives a first bit sequence, the associated SP-SS may remain in its current state (e.g., active or inactive). If the WTRU receives a second bit sequence, the associated SP-SS may be activated in slot #n. In an example, the first bit sequence may be all zeros, and the second bit sequence may be all ones or all zeros except for one bit. If the PDSCH includes multiple code blocks or code block groups, the CRCs of all the code blocks or code block groups may be scrambled with the bit sequence. The CRC of the first or last code block or group of code blocks may be scrambled with the bit sequence.

[0098] In the case of a DM-RS sequence of a PDSCH, the DM-RS sequence may be scrambled with a unique identity. For example, a PDSCH may be scheduled in slot #nx, and if the DM-RS is scrambled with a first identity, the associated SP-SS may keep its current state (e.g., active or inactive). If the DM-RS is scrambled with a second identity, the associated SP-SS may be activated in slot #n. The DM-RS scrambling identification (ID) may determine the activation of the associated SP-SS. The DM-RS scrambling ID may be used for scrambling sequence initialization.

[0099] The WTRU may receive the PDCCH in the SP-SS (650). The WTRU may receive the PDSCH based on the resource allocation in the received PDCCH. For example, the WTRU may receive PDSCH bursts in slots s+5, s+6, s+7, s+8, s+9, and s+10 as shown in FIG.

[0100] The WTRU may stop monitoring the SP-SS based on the deactivation of the SP-SS (660). An active SP-SS may be deactivated based on a timer or a time window. The timer may start from the slot in which the SP-SS was activated. The WTRU may monitor the SP-SS if an associated timer is running. If the timer is stopped, the WTRU may stop monitoring the SP-SS. If the WTRU does not detect a DCI scheduled for the WTRU within K slots (or K consecutive slots), the timer may be stopped. If the WTRU needs to switch bandwidth portions (BWPs), the timer may be stopped. If a predefined or configured time window has passed, the time window may start from the slot in which the SP-SS was activated. The timer may be stopped if a buffer, such as an uplink buffer, is empty. The timer may be stopped if the WTRU receives a timer expiry command. The timer expiry command may be received from the gNB. The time window may be determined based on a reported buffer size. For example, if the reported buffer size is greater than a first threshold, a first time window size may be used, and if the reported buffer size is greater than a second threshold, a second time window size may be used. An active SP-SS may be deactivated if the WTRU receives a deactivation signal. The deactivation signal may be received from a gNB. The deactivation signal may be a go-to-sleep (GOS) signal. The active SP-SS may be deactivated after an indicated number of slots from the activation signal. For example, the activation signal may include a time length the SP-SS is active, which may be based on a number of slots. One or more time length values ​​may be predetermined, predefined, configured, or used, and one time length value may be indicated in the activation signal.

[0101] The time location of the SP-SS may be predetermined based on higher layer configuration. The activation time of the SP-SS may not change the time location of the SP-SS. The WTRU may monitor the SP-SS when it is active at the predetermined location.

[0102] The activation indication may determine whether the WTRU needs to monitor the SP-SS. The time location of the SP-SS may be determined based on the activation time. For example, the periodicity of the SP-SS and monitoring symbols within a slot may be pre-configured, but the starting offset may be determined based on the time location at which the WTRU receives the activation indication or the SP-SS is activated.

[0103] An SP-SS and its associated P-SS may be located or configured in different BWPs. When an SP-SS is activated, the associated P-SS may not be monitored by the WTRU, and the WTRU may switch to the BWP configured for the SP-SS. When an SP-SS is deactivated, the WTRU may switch back to the BWP for the associated P-SS. For example, a first BWP may be configured with a P-SS and a second BWP may be configured with an associated SP-SS. A P-SS may activate / deactivate an associated SP-SS, which may be located in a different BWP. If the WTRU has the capability to receive multiple BWPs simultaneously, both the associated P-SS and SP-SS may be monitored by the WTRU.

[0104] The SP-SS may be used or may be allowed to be used when the P-SS periodicity or associated P-SS periodicity is greater than a threshold. For example, the WTRU may monitor for activation signals for the SP-SS if its associated P-SS periodicity is greater than a threshold. The periodicity of the SP-SS may be longer than that of the associated P-SS. The WTRU may skip monitoring for activation signals for the SP-SS if its associated P-SS periodicity is shorter than a threshold.

[0105] The SP-SS may be activated / deactivated for the downlink, the uplink, or both. For example, if the SP-SS is activated for downlink (DL) traffic or downlink transmission, the WTRU may monitor for DL ​​DCI format in the SP-SS. If the SP-SS is activated for uplink (UL) traffic or uplink transmission, the WTRU may monitor for UL DCI format in the SP-SS. When the WTRU is in an active time during DRX operation to monitor the SP-SS, the WTRU may perform DL measurements (e.g., RRM, RLM, CSI) if the SP-SS is activated for downlink transmission. If the SP-SS is not activated for DL ​​transmission or is activated for UL transmission only, the WTRU may skip performing DL measurements and / or skip reporting periodic measurements (e.g., periodic CSI). If the WTRU is within an active time during DRX operation and the WTRU monitors for SP-SS for UL transmission (e.g., for UL transmission only), the WTRU may skip reporting periodic measurements (e.g., periodic CSI).

[0106] For DRX operation, inactivity or retransmission timers may apply to the P-SS. The WTRU may need to monitor the SP-SS even when activated independently of the DRX status, e.g., in the OFF duration. The SP-SS status (e.g., active) may take precedence over the DRX status (e.g., OFF duration). When the SP-SS is inactive, the WTRU may track the DRX status (e.g., ON or OFF duration). Monitoring the SP-SS may not increase the inactivity or retransmission timers. Configured DRX parameters or operations may not apply to the SP-SS.

[0107] The WTRU may receive an updated configuration for the P-SS (670). The updated configuration may include an updated periodicity. The updated configuration may be received in a DCI on the PDCCH in the P-SS. For example, the WTRU may receive an updated periodicity for the P-SS in slot s+12 in FIG. 5. The WTRU may monitor the P-SS based on the updated periodicity (680). For example, the WTRU may monitor the P-SS in slots s+14, s+16, etc. based on the updated P-SS periodicity.

[0108] The periodicity of the P-SS and / or SP-SS may be changed dynamically. The search space periodicity may be changed with a dynamic indication. The search space periodicity may be changed with or without RRC reconfiguration. The search space monitoring periodicity may be shortened, for example, when burst traffic arrives. The search space monitoring periodicity may be increased, for example, when the data buffer is empty. The periodicity change may be indicated via L1, e.g., in DCI and / or L2 signaling, e.g., in MAC-CE.

[0109] One or more periodicity values ​​may be configured for the search space. A default periodicity may be determined based on a minimum periodicity value. A default periodicity may be determined based on a maximum periodicity value. A default periodicity may be determined based on a first periodicity in a set of configured periodicities. The minimum or maximum periodicity value may be used as the default periodicity. The first periodicity in the set of configured periodicities may also be used as the default periodicity.

[0110] One or more periodicity values ​​may be configured, e.g., via RRC signaling. If a single periodicity value is configured, the periodicity for the search space may be the configured value. If multiple periodicity values ​​are configured, one of the configured periodicity values ​​may be indicated. The WTRU may receive an indication, e.g., via L1 signaling in the DCI and / or L2 signaling in the MAC-CE. The WTRU may use the indicated periodicity, e.g., after receiving the indication. The WTRU may use the indicated periodicity for a configured, indicated, or known time, e.g., after receiving the indication. The WTRU may also use a default value if the WTRU is configured with multiple periodicity values ​​prior to receipt of an indication of the periodicity value from L1 and / or L2 signaling.

[0111] If a periodicity or periodicity change is indicated, e.g., via L1 or L2 signaling, the indicated periodicity or updated periodicity may be valid for the time window. For example, when a WTRU receives a periodicity or updated periodicity for a search space, the WTRU may monitor the search space during the time window using the indicated periodicity and may use or switch back to a previously configured periodicity, a previously indicated periodicity, or a default periodicity before and / or after the time window. The time window may be determined based on higher layer configuration. The time window may be determined based on a timer, such as an inactivity timer. In the case of higher layer configuration, the WTRU may use or switch back to the configured periodicity or default periodicity to monitor the search space after the time window. In the case of a timer, such as an inactivity timer, if the WTRU does not receive a DCI for K slots (e.g., K consecutive slots) when using the indicated or updated periodicity, the WTRU may consider the timer (e.g., the inactivity timer) to have expired and may use or switch back to the configured or default periodicity.

[0112] The time location of the search space with one or more periodicity values ​​may be determined based on configuration information of the search space. When a periodicity value is indicated or updated, the WTRU may monitor the time location associated with the indicated or updated periodicity value x slots after the slot at which the periodicity indication or update was received. For example, the x value may be predefined to a fixed value (e.g., 4). The x value may be a non-negative integer value. The x value may be determined based on numerology. X may be a configured value, for example, configured by the RRC. The x value may be dynamically indicated, for example, by the DCI or MAC-CE. The x value may be included with an indication to change or update the periodicity.

[0113] The periodicity of the search space may be determined or updated based on information such as a unique HARQ process number, the number of negative HARQ-ACKs transmitted, the slot configuration indicated from the slot format indicator, or the first uplink grant after a scheduling request.

[0114] In the case of a unique HARQ process number, the WTRU may receive a downlink or uplink grant with the unique HARQ process number. For example, if the WTRU receives a PDSCH with HARQ process number N (e.g., #16), the WTRU may monitor the search space with an updated periodicity. The gNB may determine the HARQ process number to change the periodicity of the search space. For example, a first set of HARQ process numbers (e.g., 0-3) may be associated with a first search space periodicity, and a second set of HARQ process numbers (e.g., 4-7) may be associated with a second search space periodicity. The WTRU may determine the periodicity of the search space based on the received HARQ process number, e.g., for the latest PDSCH or PUSCH.

[0115] In the case of slot configurations, the first slot configuration may be associated with a first periodicity value of the search space, and the second slot configuration may be associated with a second periodicity value of the search space.

[0116] In the case of a first uplink grant after a scheduling request, the first monitoring periodicity for the search space may be used for monitoring for the uplink grant after the scheduling request is transmitted and before the reception of the first uplink grant. The second monitoring periodicity for the search space may be used if the WTRU receives a HARQ-ACK for an uplink transmission scheduled by the first uplink grant. The HARQ-ACK may be an uplink grant with the same HARQ process number (e.g., with or without a toggled new data indicator). If the WTRU receives a HARQ-ACK for an uplink transmission in slot #nx, the second monitoring periodicity for the search space may be used from slot #n. The second monitoring periodicity for the search space may be used if the first uplink grant includes an indication of monitoring periodicity change or update. The indication may be based on the RNTI. The first monitoring periodicity for the search space may be used to monitor uplink grants after a scheduling request is transmitted and until a monitoring periodicity change command is received.

[0117] The monitoring symbols in a slot for a search space may be dynamically increased or decreased via L1 signaling and / or L2 signaling. The search spaces in different symbols in a slot may schedule PDSCHs in different slots. The PDSCHs may be long PDSCHs (e.g., PDSCH type A) or short PDSCHs (e.g., PDSCH type B).

[0118] A search space may be triggered, scheduled, or indicated to be monitored by a DCI. A search space may be triggered or scheduled X slots or Y OFDM symbols after the slot in which the DCI is transmitted. A DCI may schedule one or more search spaces. A DCI that may trigger one or more search spaces may be referred to herein as a triggering DCI, a reference DCI, or a first DCI.

[0119] The first DCI may trigger multiple aperiodic search spaces (A-SS) or aperiodic monitoring opportunities. The first DCI may include the number of A-SS or monitoring opportunities, a starting slot, a gap between search spaces (e.g., equal spacing), an aggregation level of the A-SS, and / or a REG bundle size.

[0120] FIG. 7 illustrates an example of a first DCI triggering multiple A-SSs. The first DCI may schedule three search spaces (or three monitoring opportunities), such as A-SS1, A-SS2, and A-SS3 in FIG. 7. The spacing between consecutive scheduled / triggered search spaces may be equally spaced apart by m slots, and the spacing between the first triggered or scheduled search space and the slot where the DCI is transmitted may be n slots. n=m. In the example of FIG. 7, the number of A-SSs=3, the starting slot=slot s0+n, and the gap between equally spaced search spaces is m. The spacing in terms of number of slots or symbols between two monitoring opportunities may be different from each other.

[0121] The overhead of the first DCI may be reduced if the triggered search space is placed between two consecutive P-SSs in time. As an example, in FIG. 7, the spacing between the DCI and the next periodic search space is 10 slots. The scheduled search space may be placed on some of these 10 slots. Given the starting slot and either the number of A-SSs or the gap between A-SSs, the WTRU may determine the location of the scheduled search space. The overhead of the first DCI may be further reduced if n=m. In this example, the DCI may indicate the number of A-SSs, and the locations of those search spaces may be selected such that there is an even spacing between the last search space and the slot in which the DCI was transmitted.

[0122] The first DCI may trigger one or more search spaces and may schedule a PDSCH or a PUSCH. The WTRU may receive the first DCI in the P-SS, and the WTRU may receive the second DCI in the triggered A-SS. The first DCI may include information for triggering the A-SS and for scheduling the PUSCH or PDSCH. The second DCI may include scheduling information for the PUSCH or PDSCH. The first and second DCIs may be of the same DCI format, but may differ in content. The DCI size for the first DCI and the DCI size for the second DCI may be different. The associated CORESET for the A-SS may be the same as that of the P-SS in which the WTRU may receive the first DCI.

[0123] The first DCI may trigger one or more search spaces with a pattern that may determine slots within a time window that the WTRU may need to monitor the search space. The time window may be configured via higher layer signaling. The time window may be determined based on the periodicity of the associated P-SS. For example, if the periodicity of the associated P-SS is x, then the time window may be x. The pattern may be a bitmap that may indicate slots within the time window for the A-SS. In the bitmap, each bit may be associated with one or more slots. If a bit in the bitmap indicates a value, e.g., "1", the WTRU may need to monitor the search space in the associated slot. If a bit in the bitmap indicates a different value, e.g., "0", the WTRU may skip monitoring the search space in the associated slot. One or more patterns may be used and indicated by its associated RNTI, which may be scrambled with a CRC. One or more RNTIs may be used and each RNTI may be associated with a pattern.

[0124] The first DCI may schedule search spaces not only between the DCI slot and the subsequent P-SS, but also across multiple periods of the P-SS. For example, the DCI may schedule search spaces between slots [0-9], [10-19], [20-29], etc., assuming the periodicity is 10 slots and the DCI is transmitted on slot 0. The first DCI may also indicate the number of periods for which additional search spaces are scheduled.

[0125] A WTRU that receives DCI may be expected to perform blind decoding of a control channel (eg, a PDCCH) during the scheduled search space and / or the periodic search space.

[0126] The DCI may trigger a single A-SS. The DCI may indicate the presence / absence of a subsequent A-SS. The DCI may indicate a time offset from the current search space. The DCI may indicate the aggregation level of the A-SS. The DCI may indicate the REG bundle size of the A-SS.

[0127] 8 illustrates an example of a DCI triggering a single A-SS. If the DCI is transmitted in a first A-SS, it may trigger a second A-SS. If the DCI is transmitted in a second A-SS, it may trigger a third A-SS, and so on. If the DCI is not detected in the A-SS, the WTRU may not perform blind detection of the A-SS and may only perform blind decoding of the P-SS.

[0128] The DCI may trigger the A-SS. The A-SS may be associated with the same CORESET with the search space in which the DCI was received. A single bit field may indicate the presence / absence of the A-SS. The slot / symbol offset for the time location of the A-SS may be pre-determined or pre-configured. The RNTI may indicate the presence / absence of the A-SS.

[0129] 9 illustrates an example method of DCI triggering a single A-SS. The WTRU may receive a first DCI on a PDCCH in a P-SS (910). The first DCI may schedule A-SS1. The WTRU may monitor the scheduled A-SS1 for the PDCCH based on the first DCI (920). The WTRU may receive a second DCI on a PDCCH in A-SS1 (930). The second DCI may schedule A-SS2. The WTRU may monitor the scheduled A-SS2 for the PDCCH based on the second DCI (940).

[0130] 10 shows an example of a PDSCH burst transmission where a single DCI may carry all or some of the required scheduling information for the entire burst. A PDSCH burst may be N BURST may consist of slots (i.e., N BURST ≦T UE_active ).

[0131] The WTRU may monitor and attempt to decode DCI within a search space for a single DCI burst (SDB) PDSCH transmission. A burst PDSCH transmission may be N bursts spanning one or more slots. BURST It may be a PDSCH transmission.

[0132] Each PDSCH in a burst may be a long PDSCH (PDSCH type A) or a short PDSCH (PDSCH type B). Within a burst PDSCH transmission, all PDSCHs may be of the same PDSCH type. The PDSCH type of the first PDSCH in a burst may determine the PDSCH type for the remainder of the PDSCH transmission.

[0133] The WTRU may determine the number of PDSCHs in a burst (N BURST ) and / or the number of slots. The WTRU may determine an SDB transmission or a single DCI single PDSCH (SDSP) transmission based on, for example, the search space, the periodicity of the search space, the RNTI scrambled with the CRC of the DCI, or a bit field in the DCI.

[0134] The WTRU may be configured with a search space, and the PDSCH transmission scheme (e.g., SDB or SDSP) may be indicated in the search space configuration. BURST) may be in the search space configuration. If the WTRU receives DCI in a first search space, the WTRU may receive or expect a first type of transmission, e.g., a PDSCH burst transmission. If the WTRU receives DCI in a second search space, the WTRU may receive or expect a second type of transmission, e.g., a single PDSCH transmission.

[0135] In the case of search space periodicity, if the periodicity of the search space is greater than a threshold, the WTRU may receive or expect a first type of transmission, e.g., a PDSCH burst transmission with a single DCI scheduling. If the periodicity of the search space is less than a threshold, the WTRU may receive or expect a second type of transmission, e.g., a single PDSCH transmission with a single DCI scheduling. This may apply when the WTRU is in a power saving mode and / or working with bursty traffic. The number of PDSCHs in a burst may be determined based on the periodicity of the search space.

[0136] In the case of an RNTI scrambled with the CRC of the DCI, one or more RNTIs may be used. If the WTRU receives a first RNTI that may be scrambled with the CRC of the DCI, the WTRU may receive or expect a first type of transmission, e.g., an SDB transmission. If the WTRU receives a second RNTI that may be scrambled with the CRC of the DCI, the WTRU may receive or expect a second type of transmission, e.g., an SDSP transmission. The first RNTI may be an SDB-RNTI. The second RNTI may be an SDSP-RNTI or a C-RNTI.

[0137] In the case of a bit field in the DCI, a single bit in the DCI may indicate whether it is for an SDB transmission or an SDSP transmission. A single DCI may schedule one or more PDSCHs, and the DCI may include scheduling information for one or more PDSCHs.

[0138] For SDB PDSCH transmission, the WTRU BURST The resource allocation information field in the DCI may be used for decoding all PDSCH transmissions. This resource allocation information may include carrier BWP, frequency / time domain resource allocation / mapping, ZP CSI-RS, transmit port, TCI, sounding request, reference signal configuration, PUCCH related information regarding the duration of the burst. The WTRU may not need to receive or decode information elements for PDSCH rate matching. The WTRU may assume similar rate matching as the first slot for the remaining slots in the burst. In the absence of DCI in slots following the first slot, the WTRU may assume that the CORSET used in the first slot is used for rate PDSCH rate matching.

[0139] The WTRU is BURST The WTRU may assume fixed MCS information for decoding of the PDSCH slots. The WTRU may dynamically determine the MCS from an information element, e.g., a DCI field, or may dynamically determine the MCS from a semi-static configuration for SDB PDSCH operation.

[0140] For power savings, the WTRU may not maintain its buffer for potential soft combining with future PDSCH transmissions in the next WTRU active-on period. For example, a WTRU in SDB PDSCH mode may assume new data indicator (NDI)=1 and / or redundancy version RV=0 for each burst.

[0141] The WTRU may determine a HARQ process number for one or more PDSCHs in a burst PDSCH transmission with one or more of the following single DCI based:

[0142] The WTRU receives the DCI and for each PDSCH in the burst, assigns HARQ process number N BURST The WTRU may decode N indices in the determined uplink slot. The WTRU may decode a single PDSCH-HARQ timing for the ACK / NACK indication for the entire burst. BURST The WTRU may decode multiple PDSCH-HARQ timings for the ACK / NACK indication corresponding to each PDSCH in the burst. The WTRU may decode multiple PDSCH-HARQ timings for the ACK / NACK indication corresponding to each PDSCH in the burst. BURST This may indicate an ACK / NACK message.

[0143] The WTRU may receive the DCI and decode a single HARQ process number for the entire PDSCH burst. Each PDSCH in the burst may be considered or determined as a Code Block Group (CBG), and the WTRU may report a HARQ-ACK for each PDSCH (e.g., a HARQ-ACK for each CBG). If HARQ-ACK bits for PDSCHs may be bundled for a PDSCH burst transmission, the bundling may be referred to as an exclusive-or (XOR) of the HARQ-ACK bits. Each PDSCH in the burst may be considered or determined as a codeword, and the WTRU may report a HARQ-ACK for each PDSCH as a codeword. If the number of PDSCHs in a burst is greater than a threshold, the HARQ-ACK bits for a group of PDSCHs may be bundled. The number of groups for HARQ-ACK bundling may be determined based on the number of PDSCHs in the burst. The number of groups for HARQ-ACK bundling may be determined based on the uplink resources configured for HARQ-ACK transmission. The WTRU may indicate an ACK if all PDSCH slots in a burst are correctly decoded. The WTRU may expect a retransmission of the same burst over the next active period.

[0144] The WTRU may maintain a soft buffer for failed transmissions for potential combinations in the next burst. In the next active period, the WTRU may determine from the received DCI whether the retransmitted burst has the same transmission characteristics as the previous burst for potential combinations. The WTRU may not attempt to decode slots that were successfully decoded in the previous burst. The HARQ-ACK timing may be determined based on the last slot used for PDSCH burst transmission or the first slot used for PDSCH burst transmission.

[0145] FIG. 11 illustrates the configuration of a PDSCH burst transmission. A single DCI may carry all or some of the required scheduling information for the entire burst. The WTRU may be required to determine the timing of each PDSCH in the burst. The WTRU may determine the timing of each PDSCH slot in the burst by assuming equal spacing within the WTRU active time. The WTRU may determine the spacing information dynamically from the DCI field or through its semi-static configuration.

[0146] A single DCI may schedule one or multiple PDSCHs as PDSCH burst transmissions, and the PDSCHs within a burst may be located in different slots.

[0147] The DCI may indicate a slot offset for a starting slot, e.g., a first PDSCH in a burst. The slots for the remainder of the PDSCH in a burst may be determined based on consecutive downlink slots from the starting slot. The consecutive downlink slots from the starting slot may be used for the remainder of the PDSCH. The downlink slots may be valid downlink slots that may contain more downlink symbols than a threshold. The threshold may be determined based on the number of downlink symbols in the starting slot. The threshold may be a pre-determined value. The slots for the remainder of the PDSCH in a burst may be determined based on an offset value from a previous slot. The offset value may be indicated in the DCI to schedule the PDSCH burst transmission. The offset value may be configured via higher layer signaling.

[0148] The DCI may indicate one or more slot offsets for each PDSCH in the burst. One or more sets of offset values ​​may be configured via higher layer signaling (e.g., RRC and / or MAC-CE), and the set of offset values ​​may be indicated in the DCI.

[0149] Handling bursty traffic with C-DRX is described herein. Examples using SP-SS or search spaces with dynamic or semi-persistent periodicity are described herein.

[0150] The one or more DRX timer values ​​may be determined and may be a function of, for example, the type or periodicity of one or more search spaces, such as one or more search spaces that the WTRU may monitor. DRX timer and DRX timer value may be used interchangeably herein.

[0151] A search space may be configured with or associated with a DRX timer that may be for a search space type. For example, a first DRX timer may be configured for a first search space type (e.g., P-SS) and a second DRX timer may be configured for a second search space type (e.g., SP-SS). The WTRU may use the first DRX timer when monitoring the first search space type or when one or more search spaces of the second search space type (e.g., for a HARQ process) are not configured, are not active, are not activated, or are deactivated. The WTRU may use the second DRX timer when monitoring the second search space type or when the second search space type is active or activated. For example, the WTRU may use a first DRX UL (or DL) retransmission timer when using a first type of search space (e.g., P-SS) and may use a second DRX UL (or DL) retransmission timer when using a second type of search space (e.g., SP-SS).

[0152] Use of the timer may include one or more of the following actions: starting or restarting the timer, stopping the timer, determining an active time (e.g., DRX active time) based on whether the timer is running, performing an action or making a decision based on whether the timer is running, performing an action or making a decision based on whether the timer has expired, and / or monitoring for the PDCCH while the timer is running.

[0153] In examples, one or more actions and / or decisions related to one or more DRX timers may be the same as or similar to actions and / or decisions performed in accordance with the 3GPP LTE standard or the 5G NR standard.

[0154] A set of search spaces may be configured, and a DRX timer may be configured for one or more search spaces in the set of search spaces. When a search space in the set of search spaces is active or activated, a DRX timer associated with the search space may be used or activated. When a search space in the set of search spaces is activated, the WTRU may switch from using a DRX timer associated with a default search space or a previously used search space to using a DRX timer associated with the activated search space. The search spaces in the set of search spaces may be associated with a periodicity. The periodicity may be configured for the search spaces in the set of search spaces.

[0155] For example, a first DRX timer may be associated with or configured for a first search space in the set of search spaces. A second DRX timer may be associated with or configured for a second search space in the set of search spaces. The WTRU may use the first DRX timer i) when using the first search space (e.g., when monitoring for a PDCCH according to the timing or periodicity of the first search space), ii) when the first search space is active or activated, and / or iii) when the first search space is a default search space and SP-SS is not configured or activated. The WTRU may use the second DRX timer i) when using the second search space (e.g., when monitoring for a PDCCH according to the timing or periodicity of the second search space), and / or ii) when the second search space is active or activated. The WTRU may revert to using the first DRX timer when the second search space is deactivated.

[0156] A search space may be associated with and / or configured for a HARQ process. Examples and aspects described herein with respect to a search space or a set of search spaces may be applicable, e.g., separately, to a search space for a HARQ process or a set of search spaces for a HARQ process.

[0157] The search space, search space set, and / or DRX timer configuration may be received by the WTRU, for example, from a gNB. The search space, search space set, and / or DRX timer activation and / or deactivation may be received by the WTRU, for example, from a gNB.

[0158] A search space may be configured with a DRX timer associated with the periodicity of the search space. When the periodicity of the search space is activated, the DRX timer associated with the periodicity may be used or activated.

[0159] The search space may have at least a first periodicity and a second periodicity. The first periodicity may be a default periodicity. The second periodicity may be shorter or longer than the first periodicity. The DRX timer may have a first value associated with the first periodicity and a second value associated with the second periodicity. The second value may be shorter or longer than the first value. The WTRU may use the first DRX timer value when using the first periodicity. The WTRU may use the second DRX timer value when using the second periodicity, e.g., when the second periodicity is activated. The WTRU may revert to the first timer value when the second periodicity is deactivated.

[0160] The DRX timer may be a function of a search space periodicity, such as a multiple of the search space periodicity. When a search space is activated or a search space periodicity is activated, the WTRU may determine a DRX timer value based on the search space periodicity and may use the determined DRX timer value.

[0161] The first periodicity for monitoring the search space or the periodicity of the first search space may have a value T1 (e.g., 10 ms), such as 10 slots, which may allow the WTRU to sleep for a period of time. The DRX HARQ RTT timer for the UL (or DL) for the first periodicity or the first search space may be T-RTT1. The DRX UL (or DL) retransmission timer for the first periodicity or the first search space may be T-RTX1. The second periodicity for monitoring the search space or the periodicity of the second search space may have a value T2 (e.g., 1 ms), such as 1 slot, which may allow the WTRU to receive a PDCCH with grant and / or HARQ more quickly, for example, to handle bursty traffic better. The DRX HARQ RTT timer for the UL (or DL) for the second periodicity or the second search space may be T-RTT2. The DRX UL (or DL) retransmission timer for the second periodicity or the second search space may be T-RTX2. T-RTT2 may be smaller than T-RTT1. T-RTX2 may be smaller than T-RTX1.

[0162] T-RTT1 and / or T-RTX1 may be a function of T1 and / or at least one of a first search space type. T-RTT2 and / or T-RTX2 may be a function of at least one of T1, T2, T-RTT1, T-RTX1, and / or a second search space type.

[0163] The WTRU may use a timer with a value or values ​​T-RTT1 and / or T-RTX1 when using a first search space periodicity or first search space. The WTRU may use a value or timer with values ​​T-RTT2 and / or T-RTX2 when using a second search space periodicity or second search space, e.g., when the second periodicity or second search space is activated. Following using a timer with values ​​T-RTT2 and / or T-RTX2, the WTRU may use timers with other values, such as values ​​T-RTT1 and / or T-RTX1 or T-RTT3 and / or T-RTX3, e.g., when the second search space periodicity or second search space is deactivated or when another search space periodicity or search space is activated.

[0164] A timer (e.g., a DRX timer) or a timer value associated with a search space or search space periodicity may be configured or determined by the WTRU. The WTRU may receive a configuration from the gNB.

[0165] The WTRU may receive a request or indication to stop a DRX timer, such as an RTT timer or a retransmission timer for the UL and / or DL. The request or indication may be received via L1 signaling, e.g., in a DCI in the PDCCH, or via L2 signaling, e.g., in the MAC-CE. In response, the WTRU may stop one or more DRX timers that have been indicated or requested to be stopped.

[0166] The stop may apply to one or more DRX timer types (e.g., UL RTT, DL RTT, UL RTT and DL RTT, UL retransmission, DL retransmission, or UL and DL retransmission). The stop may apply to active DRX timers of one or more DRX types. The stop may apply to all DRX timers of one or more DRX types.

[0167] In the examples and aspects described herein, P-SS and SP-SS may be used as non-limiting examples of search space types. Any other search space may be used and may be consistent with this disclosure.

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

[0169] 100 Communication Systems 102a Receiver Unit (WTRU) 102b Receiver Unit (WTRU) 102c Receiver Unit (WTRU) 102d Receiver Unit (WTRU) 104 Radio Access Network (RAN) 106 Core Network (CN) 108 Public Switched Telephone Network (PSTN) 110 Internet 112 Network 114a base station 114b base station 116 Air Interface 118 processors 120 Walkie Talkie 122 Receiving elements 124 Microphone 126 Keypad 128 Touchpad 130 Non-removable memory 132 Removable Memory 134 Power supply 136 Chipset 138 Peripherals 162 Mobility Management Entity (MME) 164 Serving Gateway (SGW) 166 Gateway (PGW) 182a Mobility Management Function (AMF) 182b Mobility Management Function (AMF) 183a Session Management Facility (SMF) 183b Session Management Facility (SMF) 184a User Plane Function (UPF) 184b User Plane Function (UPF) 185a Data Network (DN) 185b Data Network (DN)

Claims

1. 1. A wireless transmit / receive unit (WTRU) comprising a processor and a memory, the processor and the memory comprising: receiving configuration information associated with a first search space and a second search space, the configuration information including a monitoring periodicity of the first search space and a monitoring periodicity of the second search space; monitoring a physical downlink control channel (PDCCH) transmission via the first search space according to the monitoring periodicity of the first search space; receiving downlink control information (DCI) in a PDCCH transmission received over the first search space, the DCI including an indication of activation of the second search space; In response to the indication of the activation of the second search space, monitor PDCCH transmissions via the second search space using the monitoring periodicity of the second search space. The WTRU is configured to:

2. 2. The WTRU of claim 1, wherein the processor and the memory are further configured to receive an indication of a period of time during which the second search space is active, the second search space being monitored using the monitoring periodicity of the second search space during the period of time.

3. 3. The WTRU of claim 2, wherein the DCI further includes the indication of the period of time during which the second search space is active.

4. 4. The WTRU of claim 3, wherein the processor and the memory are further configured to monitor a PDCCH transmission via the first search space after monitoring a PDCCH transmission via the second search space for the period of time that the second search space is active.

5. 10. The WTRU of claim 1, wherein the processor and the memory are further configured to send an indication of a capability to support search space switching.

6. The WTRU of claim 1 , wherein the DCI is a group-common DCI.

7. 2. The WTRU of claim 1, wherein the configuration information further comprises a monitoring offset associated with the first search space.

8. The processor and the memory include receiving a second DCI in a PDCCH transmission received over the second search space, the DCI including an indication of deactivation of the second search space; In response to the indication of the deactivation of the second search space, monitor PDCCH transmissions via the first search space using the monitoring periodicity of the first search space.

2. The WTRU of claim 1, further configured to:

9. 1. A method implemented by a wireless transmit / receive unit (WTRU), comprising: receiving configuration information associated with a first search space and a second search space, the configuration information including a monitoring periodicity of the first search space and a monitoring periodicity of the second search space; monitoring a physical downlink control channel (PDCCH) transmission via the first search space according to the monitoring periodicity of the first search space; receiving downlink control information (DCI) in a PDCCH transmission received over the first search space, the DCI including an indication of activation of the second search space; monitoring a PDCCH transmission via the second search space using the monitoring periodicity of the second search space in response to the indication of the activation of the second search space; 23. A method comprising:

10. 10. The method of claim 9, further comprising receiving an indication of a period of time during which the second search space is active, the second search space being monitored using the monitoring periodicity of the second search space during the period of time.

11. 11. The method of claim 10, wherein the DCI further includes the indication of the period of time during which the second search space is active.

12. 12. The method of claim 11, further comprising monitoring a PDCCH transmission via the first search space after monitoring a PDCCH transmission via the second search space for the period of time that the second search space is active.

13. 10. The method of claim 9, further comprising sending an indication of a capability to support search space switching.

14. The method according to claim 9 , wherein the DCI is a group common DCI.

15. 10. The method of claim 9, wherein the configuration information further comprises a monitoring offset associated with the first search space.

16. receiving a second DCI in a PDCCH transmission received over the second search space, the DCI including an indication of deactivation of the second search space; and in response to the indication of the deactivation of the second search space, monitoring a PDCCH transmission via the first search space using the monitoring periodicity of the first search space.

10. The method of claim 9, further comprising:

17. A base station comprising a processor and a memory, the processor and the memory comprising: Receive an indication of a capability to support search space switching associated with a wireless transmit / receive unit (WTRU); transmit configuration information associated with a first search space and a second search space based on the indication of the capability to support search space switching associated with the WTRU, the configuration information including a monitoring periodicity of the first search space and a monitoring periodicity of the second search space; determining to switch a transmission associated with the WTRU from the first search space to the second search space; In response to the decision to switch a transmission associated with the WTRU from the first search space to the second search space, transmit downlink control information (DCI) in a PDCCH transmission over the first search space, the DCI including an indication of activation of the second search space. A base station configured as follows.

18. 20. The base station of claim 17, wherein the processor and the memory are further configured to send an indication of a period of time during which the second search space is active.

Citation Information

Patent Citations

  • Methods for communicating on a mobile network

    JP2012525756A