TW201906487A - Group-common physical downlink control channels for wireless communication - Google Patents

Abstract

A wireless transmit/receive unit (WTRU) may receive a radio resource control (RRC) message that includes one or more monitoring rates for a group-common physical downlink control channel (PDCCH) having a slot format indicator (SFI). The WTRU may monitor for the GC-PDCCH having the SFI at the one or more monitoring rates.

Description

Wireless communication group sharing entity downlink control channel

CROSS- REFERENCE TO RELATED APPLICATIONS [0001] This application claims priority to US Provisional Patent Application No. 62/585,904, filed on Nov. 14, 2017, and U.S. Provisional Patent Application No. 62/555,906, filed on Sep. 8, 2017, and in U.S. Provisional Patent Application No. 62/519,783, filed on June 14.

Fifth-generation (5G) wireless systems and networks can take advantage of new frame, multiplex, and mobile processes to provide enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC) for new radio (NR) access technologies ), huge machine type communication (mMTC), etc. The Shared Entity Downlink Control Channel (PDCCH), Entity Control Format Indicator Channel (PCFICH), and other channels may be utilized to transmit the shared traffic required to schedule the downlink data or to detect the WTRU-specific PDCCH. Expect to be able to effectively communicate shared communications to improve the performance of downlink and uplink URLLC services or 5G services. This is expected for traffic that may be sporadic, infrequent, bursty, with little payload, unscheduled, or unpredictable.

A group shared entity downlink control channel (PDCCH) may be configurable by a WTRU in a cell or beam. The group shared PDCCH may be used together with the shared PDCCH or used independently. The group shared PDCCH may also be assigned to a WTRU group or a WTRU cluster, and multiple group shared PDCCH channels may be delivered or assigned to the WTRU. The group shared PDCCH can be monitored at different rates.

FIG. 1A is a diagram showing an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content for a plurality of wireless users, such as voice, data, video, messaging, broadcast, and the like. The communication system 100 can enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, communication system 100 can use 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 extended orthogonal frequency division multiplexing (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filtering Multi-carrier group (FBMC) and so on.

As shown in FIG. 1A, communication system 100 can include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, radio access network (RAN) 104, core network (CN) 106, public switched telephone network. Path (PSTN) 108, Internet 110, and other networks 112, however, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. For example, any of the WTRUs 102a, 102b, 102c, and 102d may be referred to as "station" and/or "STA," and the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals, And may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, mobile phones, personal digital assistants (PDAs), smart phones, laptops, small laptops, Personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head mounted displays (HMDs), vehicles, drones, medical devices and applications (eg remote surgery) Surgery), industrial devices and applications (such as robotics and/or other wireless devices operating in industrial and/or automated processing chain environments), consumer electronic devices, and devices operating on commercial and/or industrial wireless networks, etc. . Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as UEs.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a and 114b can be configured to have a wireless interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (eg, CN 106, Internet 110) Any type of device, and/or other network 112). For example, the base stations 114a, 114b may be a base transceiver station (BTS), a node B, an eNodeB, a home node B, a home eNodeB, a next generation node b (gNB), a new radio (NR) node B, Site controllers, access points (APs), wireless routers, and more. While each of the base stations 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b can include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104, and the RAN 104 may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), Following the node and so on. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals at one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies can be in the licensed spectrum, unlicensed spectrum, or a combination of authorized and unlicensed spectrum. Cells may provide wireless service coverage for a particular geographic area that is relatively fixed or that may change over time. Cells can be further divided into cell sectors. For example, a cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, that is, one for each sector of the cell. In one embodiment, base station 114a may use multiple input multiple output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals can be transmitted and/or received in a desired spatial direction.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d by an empty intermediation plane 116, which may be any suitable wireless communication link (e.g., radio frequency (RF)) , microwave, centimeter wave, micro wave, infrared (IR), ultraviolet (UV), visible light, etc.). The empty intermediaries 116 can be established using any suitable radio access technology (RAT).

More specifically, as noted above, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, to name a few. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104 may implement some sort of radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA (WCDMA) to establish airborne Interface 116. 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).

In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology, such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and/or LTE-Advanced (LTE) -A) and/or Advanced LTE Pro (LTE-A Pro) to establish an empty intermediation plane 116.

In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology, such as NR radio access, which may use a new radio (NR) to establish an empty intermediation plane 116.

In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a variety of radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may collectively implement LTE radio access and NR radio access (e.g., using a dual connectivity (DC) principle). Thus, the null intermediaries used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or communications to/from multiple types of base stations (e.g., eNBs and gNBs).

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement the following radio technologies, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (ie, Wireless Fidelity (WiFi)), IEEE 802.16 (ie, the world) Interoperating 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 Rate (EDGE) for GSM Evolution, and GSM EDGE (GERAN) and more.

The base station 114b in FIG. 1A may be, for example, a wireless router, a home node B, a home eNodeB, or an access point, and may use any suitable RAT to facilitate a wireless connection in a local area, which may be For example, business premises, homes, vehicles, campuses, industrial facilities, air corridors (eg for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In still another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular based RAT (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or Femtocell. As shown in FIG. 1A, the base station 114b can be directly connected to the Internet 110. Thus, the base station 114b does not necessarily have to access the Internet 110 via the CN 106.

The RAN 104 can communicate with the CN 106, wherein the CN 106 can be configured to provide voice, data, applications, and/or Voice over Internet Protocol (VoIP) to one or more of the WTRUs 102a, 102b, 102c, 102d. Any type of network that serves. The data can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. The CN 106 can provide call control, billing services, mobile location based services, prepaid calling, internet connectivity, video distribution, etc., and/or can perform advanced security functions such as user authentication. Although not shown in FIG. 1A, it should be appreciated that RAN 104 and/or CN 106 can communicate directly or indirectly with other RANs that use the same RAT or different RATs as RAN 104. For example, in addition to being connected to the RAN 104 using NR radio technology, the CN 106 can also communicate with other RANs (not shown) that use GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technologies.

The CN 106 can 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 that provides Plain Old Telephone Service (POTS). Internet 110 may include the use of a shared communication protocol (e.g., Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP Internet Protocol suite). A system of globally interconnected computer networks and devices. The other network 112 may include wired and/or wireless communication networks that are owned and/or operated by other service providers. For example, the other network 112 can include another CN connected to one or more RANs, where the one or more RANs can use the same RAT or a different RAT as the RAN 104.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (eg, the WTRUs 102a, 102b, 102c, 102d may include multiple transceiving communications with different wireless networks over different wireless links) Device). For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that uses a cellular-based radio technology, and with a base station 114b that can use an IEEE 802 radio technology.

FIG. 1B is a system diagram showing an exemplary WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/trackpad 128, a non-removable memory 130, and a removable Memory 132, power source 134, global positioning system (GPS) chipset 136, and/or other peripheral devices 138. It should be appreciated that the WTRU 102 may also include any sub-combination of the aforementioned elements while remaining consistent with the embodiments.

The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with the DSP core, a controller, a microcontroller , Dedicated Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), and state machine. Processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although FIG. 1B depicts processor 118 and transceiver 120 as separate components, it should be understood that processor 118 and transceiver 120 can also be integrated into one electronic component or wafer.

The transmit/receive element 122 can be configured to transmit signals to the base station (e.g., base station 114a) or receive signals from the base station (e.g., base station 114a) via the null intermediate plane 116. For example, in one embodiment, the transmit/receive element 122 can be an antenna configured to transmit and/or receive RF signals. As an example, in one embodiment, the transmit/receive element 122 can be a transmitter/detector configured to transmit and/or receive IR, UV, or visible light signals. In still another embodiment, the transmit/receive element 122 can be configured to transmit and/or receive RF and optical signals. It should be appreciated that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Although the transmission/reception element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmission/reception elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmission/reception elements 122 (e.g., multiple antennas) that transmit and receive wireless signals over the null plane 116.

The transceiver 120 can be configured to modulate signals to be transmitted by the transmission/reception component 122 and to demodulate signals received by the transmission/reception component 122. As noted above, the WTRU 102 may have multi-mode capabilities. Accordingly, transceiver 120 may include multiple transceivers that allow WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

The processor 118 of the WTRU 102 may be coupled to a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may User input data from speaker/microphone 124, keypad 126, and/or display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) is received. The processor 118 can also output user profiles to the speaker/microphone 124, the keypad 126, and/or the display/trackpad 128. In addition, processor 118 can access signals from any suitable memory, such as non-removable memory 130 and/or removable memory 132, and store the data in these memories. Non-removable memory 130 may include random access memory (RAM), read only memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 can include a Subscriber Identity Module (SIM) card, a memory stick, and a secure digital (SD) memory card and the like. In other embodiments, the processor 118 may access information from memory that is not physically located in the WTRU 102 and store the data in the memory. As an example, such memory may be located on a server or a home computer (not shown) ).

The processor 118 can receive power from the power source 134 and can be configured to distribute and/or control the power to other components in the WTRU 102. Power source 134 may be any suitable device that powers WTRU 102. For example, the power source 134 may include one or more dry battery packs (eg, nickel cadmium (Ni-Cd), nickel zinc (Ni-Zn), nickel metal compound (NiMH), lithium ion (Li-ion), etc.), solar cells. , as well as fuel cells and so on.

The processor 118 can also be coupled to a GPS chipset 136 that can be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. The WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) plus or in place of GPS chipset 136 information via null intermediaries 116, and/or based on signal timing received from two or more nearby base stations. To determine its location. It should be appreciated that the WTRU 102 may obtain location information via any suitable positioning method while remaining consistent with the embodiments.

The processor 118 can also be coupled to other peripheral devices 138, which can include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, peripheral device 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photo and/or video), a universal serial bus (USB) port, a vibrating device, a television transceiver, a hands-free headset, Bluetooth ® modules, FM radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and/or augmented reality (VR/AR) devices, and activities Tracker and more. Peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensing , temperature sensor, time sensor, geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, or humidity Detector, etc.

The WTRU 102 may include a full-duplex radio for which some or all of the signals (e.g., specific to UL (e.g., for transmission) and downlink (e.g., for reception) The reception or transmission of the subframes may be parallel or simultaneous, and the like. The full duplex radio may include an interface management unit to reduce the sum via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). / or substantially eliminate self-interference. In one embodiment, the WTRU 102 may include a half-duplex radio for which some or all of the signals (eg, for use with the UL (eg, relative to transmission) or downlink (eg, relative) Transmission and reception associated with the special subframe for reception.

1C is a system diagram showing RAN 104 and CN 106 in accordance with one embodiment. As described above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c via the null plane 116 using E-UTRA radio technology. Also, the RAN 104 can also communicate with the CN 106.

The RAN 104 may include eNodeBs 160a, 160b, 160c, however it should be appreciated that the RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. Each of the eNodeBs 160a, 160b, 160c may include one or more transceivers that communicate with the WTRUs 102a, 102b, 102c via the null plane 116. In one embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNodeB 160a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a.

Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle user scheduling in radio resource management decisions, handover decisions, UL, and/or DL and many more. As shown in FIG. 1C, the eNodeBs 160a, 160b, and 160c can communicate with each other through the X2 interface.

The CN 106 shown in FIG. 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements may be owned and/or operated by entities other than the CN operator.

The MME 162 may be connected to each of the eNodeBs 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 verifying the users of the WTRUs 102a, 102b, 102c, performing bearer initiation/deactivation procedures, and selecting a particular service gateway during the initial attachment process of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM and/or WCDMA.

SGW 164 may be connected to each of eNodeBs 160a, 160b, 160c in RAN 104 via an S1 interface. SGW 164 can typically route and forward user data packets to/from WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during handover between eNBs, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c and many more.

SGW 164 may be coupled to PGW 166, which may provide WTRUs 102a, 102b, 102c with packet switched network (e.g., Internet 110) access to facilitate inter-WTRU 102a, 102b, 102c and IP-enabled devices. communication.

The CN 106 can facilitate communication with other networks. For example, CN 106 may provide circuit-switched network (e.g., PSTN 108) access to WTRUs 102a, 102b, 102c to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communications devices. For example, the CN 106 can include or communicate with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server), and the IP gateway can act as an interface between the CN 106 and the PSTN 108. In addition, CN 106 may provide 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.

Although the WTRU is described as a wireless terminal in Figures 1A through 1D, it should be appreciated that in certain exemplary embodiments, such terminals and communication networks may use (e.g., temporary or permanent) wired communication interfaces. .

In the representative embodiment, the other network 112 can be a WLAN.

A WLAN in an 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 can access or have another type of wired/wireless network that interfaces with a distributed system (DS) or carries traffic and/or carries BSS. Traffic originating outside the BSS and going to the STA can be reached by the AP and delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS can be sent to the AP for delivery to the corresponding destination. The traffic between STAs within the BSS can be sent by the AP, for example, where the source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and/or referred to as point-to-point traffic. The point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) with direct link setup (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may have no AP, and STAs (eg, all STAs) that are internal to the IBSS or that use the IBSS may communicate directly with each other. The IBSS communication mode can also be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure operating mode or similar operating mode, the AP can transmit beacons on fixed channels (eg, primary channels). The main channel can have a fixed width (eg, a bandwidth of 20 MHz) or a dynamically set width set via messaging. The primary channel can be the operational channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, implemented may be carrier sense multiple access with collision avoidance (CSMA/CA) (eg, in an 802.11 system). For CSMA/CA, STAs including APs (eg, each STA) can sense the primary channel. If the special STA senses/detects and/or determines that the primary channel is busy, then the special STA may back off. In a given BSS, there can be one STA (eg, only one station) for transmission at any given time.

High throughput (HT) STAs can communicate using a 40 MHz wide channel (eg, by combining a 20 MHz main channel with a 20 MHz adjacent or non-adjacent channel to form a 40 MHz wide channel).

Ultra High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz and/or 160MHz. 40MHz and/or 80MHz channels can be formed by combining successive 20MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two discrete 80 MHz channels (this combination can be referred to as an 80+80 configuration). For an 80+80 configuration, after channel encoding, the data can be passed through a segmentation parser that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing or time domain processing can be performed separately on each stream. The stream can be mapped on two 80 MHz channels and the data can be transmitted by the STA performing the transmission. At the receiver performing the receiving STA, the above operations for the 80+80 configuration may be reversed and the combined material may be sent to the Media Access Control (MAC).

802.11af and 802.11ah support the next 1 gigahertz (GHz) mode of operation. The channel operation bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control/machine type communication (MTC) (eg, MTC devices in a macro coverage area). The MTC device may have some capability, such as including limited capabilities to support (eg, only support) certain and/or limited bandwidth. The MTC device can include a battery and the battery life of the battery is above a threshold (eg, maintaining a very long battery life).

For WLAN systems that can support multiple channel and channel bandwidths (eg, 802.11n, 802.11ac, 802.11af, and 802.11ah), the WLAN system includes a channel that can be designated as the primary channel. The bandwidth of the primary channel may be equal to the maximum shared operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and/or limited by the STA, where the STA is derived from all STAs operating in the BSS, which supports a minimum bandwidth mode of operation. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth modes of operation, support (eg, only support) 1 MHz mode STAs For a device such as an MTC type, the width of the main channel can be 1 MHz. The carrier sensing and/or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (because the STA (eg, a STA in 1 MHz mode of operation) transmits to the AP), then the entire available frequency band can be considered busy even though most of the frequency bands remain idle and available for use.

In the United States, the available frequency band available for 802.11ah is 902 MHz to 928 MHz. In Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5 MHz to 927.5 MHz. According to the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

Figure 1D is a system diagram showing RAN 104 and CN 106 in accordance with one embodiment. As described above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c via the null plane 116 using NR radio technology. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include gNBs 180a, 180b, 180c, but it should be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, 180c may include one or more transceivers to communicate with WTRUs 102a, 102b, 102c via null intermediaries 116. In one embodiment, gNBs 180a, 180b, 180c may implement MIMO technology. Moreover, in an example, gNBs 180a, 180b, 180c may use beamforming processing to transmit signals to and/or receive signals from WTRUs 102a, 102b, 102c. Thus, for example, gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a. In one embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple component carriers (not shown) to WTR 102a. A subset of these component carriers may be on the unlicensed spectrum, while the remaining component carriers may be on the licensed spectrum. In one embodiment, gNBs 180a, 180b, 180c may implement Cooperative Multipoint (CoMP) technology. For example, the WTRU 102a may receive cooperative communications from the gNBs 180a and gNBs 180b (and/or gNBs 180c).

The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using communications associated with the scalable parameter configuration. For example, the OFDM symbol spacing and/or the OFDM subcarrier spacing (SGS) may be different for different communications, different cells, and/or different portions of the wireless communication spectrum. The WTRUs 102a, 102b, 102c may use subframes or transmission time intervals (TTIs) having different or scalable lengths (e.g., containing different numbers of OFDM symbols and/or continuing different absolute time lengths) to communicate with the gNB 180a, 180b, 180c communicate.

The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c in a discrete configuration and/or a non-discrete configuration. In a separate configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a separate configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a separate configuration, the WTRUs 102a, 102b, 102c may use signals in the unlicensed band to communicate with the gNBs 180a, 180b, 180c. In a non-discrete configuration, the WTRUs 102a, 102b, 102c may communicate/connect with the gNBs 180a, 180b, 180c while communicating/connecting with other RANs (e.g., eNodeBs 160a, 160b, 160c). For example, the WTRUs 102a, 102b, 102c may implement the DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c in a substantially simultaneous manner. In a non-discrete configuration, the eNodeBs 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 be the WTRU 102a, 102b, 102c provide services.

Each of 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, user scheduling in UL and/or DL, support network Road cutting, implementation of dual connectivity, implementation of interaction between NR and E-UTRA, user plane data routed to user plane functions (UPF) 184a, 184b, and routing to access and mobility management functions (AMF) 182a, 182b control plane information and so on. As shown in FIG. 1D, the gNBs 180a, 180b, and 180c can communicate with each other through the Xn interface.

The CN 106 shown in FIG. 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. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements can be owned and/or operated by other entities than the CN operator.

The AMFs 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, AMFs 182a, 182b may be responsible for verifying users of WTRUs 102a, 102b, 102c, supporting network cuts (e.g., handling different protocol data unit (PDU) sessions with different needs), selecting special SMFs 183a, 183b, managing Registration area, termination of non-access layer (NAS) messaging, and mobility management, etc. The AMF 182a, 182b may use network cut processing to tailor the CN support provided for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. As an example, different network cuts can be established for different use cases, such as services that rely on ultra-reliable low-latency communication (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, And/or services for MTC access, etc. The AMFs 182a, 182b may be provided for use in the RAN 104 with non-third generation partner project (3GPP) access technologies using other radio technologies (eg, LTE, LTE-A, LTE-A Pro, and/or WiFi) The control plane function switches between other RANs (not shown).

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 can select and control the UPFs 184a, 184b, and can configure traffic routing by the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink information notifications, and the like. The PDU session type may be IP based, non-IP based, Ethernet based, etc.

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 packet switched network (e.g., Internet 110) access. To facilitate communication between the WTRUs 102a, 102b, 102c and the IP-enabled device. The UPFs 184, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, and providing mobility anchoring, etc. Wait.

The CN 106 can facilitate communication with other networks. For example, CN 106 may include or may be in communication with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and CN 108. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks that other service providers own and/or operate. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the local DN 185a via UPFs 184a, 184b via an N3 interface to UPFs 184a, 184b and an N6 interface between UPFs 184a, 184b and DNs 185a, 185b, 185b.

In view of Figures 1A through 1D and the corresponding descriptions of Figures 1A through 1D, one or more or all of the functions described herein in relation to one or more may be performed by one or more analog devices ( Not shown) to perform: WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMF 183a -b, DN 185 ab and/or any other device or devices described herein. These analog devices may be one or more devices configured to simulate one or more or all of the functions herein. For example, these analog devices can be used to test other devices and/or analog network and/or WTRU functions.

The simulation device can be designed to implement one or more tests on other devices in a laboratory environment and/or an operator network environment. For example, the one or more analog devices can perform one or more or all of the functions while being implemented and/or deployed in whole or in part as part of a wired and/or wireless communication network to test other devices within the communication network . The one or more analog devices may perform one or more or all of the functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The analog device can be directly coupled to other devices to perform the test, and/or can be tested using over-the-air wireless communication.

One or more of the analog devices may perform one or more functions including all functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the simulation device can be used in a test lab and/or in a test scenario of a wired and/or wireless communication network that is not deployed (eg, tested) to perform testing with respect to one or more components. The one or more analog devices can be test devices. The analog device can transmit and/or receive data using direct RF coupling and/or via wireless communication via an RF circuit (which, by way of example, may include one or more antennas).

In wireless communication, reference symbols may be utilized to represent symbols, such as fixed or known complex numbers. Reference symbols can be used as pilots. A reference signal can be utilized to represent a time domain signal that can be generated by processing the reference signal. In OFDM, the reference symbol can be a complex number input to an inverse discrete Fourier transform (IDFT) block, and the reference signal can be the output of the IDFT box. A resource element (RE) may be one or more OFDM symbols on one or more subcarriers, and a resource element group (REG) may include a RE group. The RE group can be used as a building block for the Control Channel Element (CCE) that assigns the RE to the user. REGs that are adjacent in time or frequency, adjacent in time or frequency, grouped together, or clustered, etc., can be designated as REG bundles, which can be associated with the same precoding so that channel estimation can be effectively performed together . The examples given here include different examples of REG size, REG bundling size, or group size, and the like. However, for the embodiments presented herein, any size is configurable.

In LTE, a Shared Entity Downlink Control Channel (PDCCH), an Entity Control Format Indicator Channel (PCFICH), or other control channel may be configured to transmit a shared communication for scheduling downlink information or detecting a WTRU-specific PDCCH. For NR or 5G, NR-REG, NR-CCE or NR-PDCCH are similar to REG, CCE or PDCCH, respectively. Within the NR or 5G, the group shared PDCCH may be configured to carry physical channels for downlink control information (DCI) for the WTRU group or WTRU cluster. Utilizing 5G NRs in millimeter wave (mmW) frequencies, beam based transmissions, or transmission and receive beam based WTRU groups may require diverse control operations. The group shared PDCCH may be used for scheduling by the WTRU set or the WTRU subset within the cell or beam.

The group shared PDCCH may be used with a WTRU specific PDCCH or a shared PDCCH. The group shared PDCCH can also operate independently. When a group shared PDCCH is assigned to a WTRU group or a subset of WTRUs, multiple groups may be configured to share a PDCCH channel. In this configuration, the WTRU may be assigned to one or more group shared PDCCH channels. Assignments can be static, semi-static, or dynamic. In one configuration, group shared PDCCH parameters, or group shared PDCCH search space parameters, etc. may be assigned during WTRU initialization, setup, or registration, and the like. The WTRU may also be added or removed from the group by using WTRU-specific signals delivered by the PDCCH during beam management or reconfiguration, during beam failure, or during beam recovery, and the like.

The group shared PDCCH may include a time slot configuration, a group identification (ID), a starting position of a physical downlink shared channel (PDSCH) in one or more time slots, and a DL control resource set (CORESET) in one or more End position in time slot, UL scheduling request (SR) resource configuration, DL preemption indication for previous time slot, UL preemption indication for previous time slot, DL response (ACK) related to UL data communication or transmission Information about restrictions on the WTRU-specific search space, information about blind decoding on a particular subset of the WTRU's search space, indication of transmission length on the data channel, resource block group (RBG) size, related phase tracking RS (PT-RS) indicates the presence or pattern, DL beam indication, or dynamic configuration of the Interference Measurement Resource (IMR).

The time slot configuration or format may include DL, UL, side link, half duplex, full duplex, reserved, unknown, empty, or blank. The time slot configuration can be related to the current time slot or the aggregate time slot, the aggregate micro time slot, or the next time slot. For a semi-statically configured time slot format, the dynamic time slot configuration overwrites the existing semi-static configuration. The Time Slot Format Indicator (SFI) may indicate the format for one or more time slots. When the SFI indicates the format for multiple time slots, information about the number of time slots can also be explicitly or implicitly included. The SFI can be related to the current time slot, the next time slot, or a plurality of subsequent time slots. The variable bit number can be used to indicate the time slot format. The format indicated as null may advertise no communication or transmission from the gNB and may be used by the WTRU or transceiver for interference estimation and cancellation. A format indicated as unknown may advertise possible communications or transmissions from the gNB. The WTRU may be configured to process an unknown format, or to skip processing of signals received on an unknown time slot, and the like.

A preemptive indication for the UL (which may be passed or transmitted by the group shared PDCCH as one or more bits) may be indicated by one or more previous time slots or one or more code block groups (CBGs) by URLLC Missing communication or transmission by the WTRU, communication or transmission by the eMBB WTRU within the UL. On one or more previous time slots or one or more CBGs, a preemptive indication for the DL (which may be transmitted or transmitted by the group shared PDCCH as one or more bits) may indicate communication or transmission for the URLLC WTRU And the preemption for communication or transmission is for the eMBB WTRU within the DL. The preemptive indication may also indicate how the transceiver or WTRU or the like utilizes the RS during decoding, such as for eMBB or any other wireless device.

For paging and system information, paging messages (such as for Radio Resource Control (RRC) idle mode) may be group shared DCI (GC-DCI) schedules carried by the group shared PDCCH, WTRU specifics carried by the WTRU-specific NR-PDCCH The DCI schedule, or is transmitted or transmitted within the associated NR-PDSCH. Additionally, for indications that limit the WTRU-specific search space, the GC-DCI may include information regarding limiting blind detection of a WTRU-specific PDCCH to a portion or a particular portion of the WTRU-specific search space. For example, the WTRU-specific search space may span multiple OFDM symbols, and the GC-DCI may indicate that blind detection is limited to search space PDCCH candidates on one or more particular OFDM symbols.

For indication of the starting location of the PDSCH in the time slot, the group shared PDCCH may include information about the start of the data channel within the time slot for the WTRU group or the WTRU cluster. The start of the PDSCH may be different or aligned to the end of the control region. For the indication of the transmission length of the data channel, the duration of the data transmission in the data channel can be dynamically indicated or semi-statically configured in the scheduling data communication or the transmitted PDCCH.

The unified GC-DCI or unified group shared PDCCH may have a structure similar to NR-PDCCH. Similar features of the structure may include REG, REG bundling, CCE, CCE aggregation, mapping of CCE to group shared PDCCH, channel coding, or cyclic redundancy check (CRC), and the like. In a unified configuration, the search space for the group shared PDCCH may be similar to the shared search space for the PDCCH. The unified group shared PDCCH may also partially reuse the NR-PDCCH structure. Partial or complete reuse of the PDCCH structure may utilize: REG; REG and REG bundling; REG, REG bundling and CCE; or REG, REG bundling and CCE, and forward error correction (FEC) and CRC structures similar to PDCCH.

2 is a schematic diagram of an exemplary REG structure 200 for a group shared PDCCH. For REG configuration, the group shared PDCCH may utilize a REG structure, such as a REG structure having a DMRS similar to NR-PDCCH and RE mapping, or a REG structure having a unique DMRS structure. In REG structure 200, REGs 0-23 for symbols 202 and 204 may not be grouped into REG bundling for material 206 because REG 0, REG 8, and REG 16 are distributed.

FIG. 3 is a schematic diagram of an exemplary structure 300 for utilizing REG and REG bundling for a group shared PDCCH. When using REG and REG bundling, both REG structures and REG bundling similar to NR-PDCCH configurations with different CCE structures can be used. REGs 0-23 for symbols 302 and 304 are configured with REG, REG bundling, and material 306. Within 300, the REG bundle may include (REG 0, REG 1), (REG 4, REG 5), (REG 8, REG 9), (REG 12, REG 13), and (REG 16, REG 17). However, any combination, sequence, or group, etc. with respect to REGs may include bundling.

Figure 4 is a schematic diagram of an example 400 of utilizing REG, REG bundling and CCE, and FEC and CRC for PDCCH. In 400, the REG bundles in 402 and 404 may include (REG 0, REG 1), (REG 8, REG 9), and (REG 16, REG 17) and data 406. When REG, REG bundling, and CCE are configured, resource mapping can be configured in time or frequency similar to NR-PDCCH, while CCE has 6 REGs. In another configuration, at 408, the REG bundle can include (REG 0, REG 1), (REG 4, REG 5), and (REG 8, REG 9) and CORESET 2 and data 412 within 410. In 400, when REG, REG bundling and CCE, and FEC and CRC similar to PDCCH are used, a transmission scheme, FEC, error detection, or CRC, etc., can be configured similarly to NR-PDCCH.

In some configurations, two types of GC-DCI and two types of group shared PDCCHs can be configured. Light, small or short GC-DCI can be transmitted or transmitted on a light, small or short group shared PDCCH. The extended, large or long GC-DCI may be transmitted or transmitted on the extended, large or long group shared PDCCH. Table 1 shows examples of content for light GC-DCI and extended GC-DCI. Table 1 The light DCI of the group shared PDCCH may include an SFI or preemption indication of one or more bits, and the like.

For the structure and transmission of the light group shared PDCCH, the group shared PDCCH may be transmitted or transmitted within the first OFDM symbol of the time slot. When the group shared PDCCH carries information about the DL CORESET configuration or the DL CORESET duration, etc., the WTRU may configure the PDCCH in the first OFDM symbol of the time slot to identify the time slot configuration as early as possible, thereby reducing the number of blind detection operations. .

Figure 5 is a schematic diagram of an example 500 of mapping a group shared PDCCH to a first OFDM symbol of time slot 1 and CORESET on slot 2. The group shared PDCCH may be mapped to six REGs of symbol 502, which may include 3 bundles of 2 REGs: (REG 0, REG 1), (REG 6, REG 7), and (REG 12, REG 13 ). The REG bundle can be distributed in the frequency domain over the DL CORESET bandwidth. The mapping of resource elements ( k, l ) in the group shared PDCCH to DL CORESET may be performed in ascending order of index k , which may mean that frequency priority mapping is performed when l=1 . In 500, symbol 506 can be configured as a first OFDM symbol of CORESET within time slot 1, and symbols 504 and 508 can be configured as a second OFDM symbol of CORESET within time slot 2.

The group sharing PDCCH may apply different channel coding, error detection, or error correction schemes on the payload for communication or transmission depending on the content. The payload may include data, controls, data and controls, or any other information used for communication or transmission. In some configurations, the group shared PDCCH may be delivered without error detection or correction. As an example, if the group shared PDCCH is carrying a hybrid automatic repeat request (HARQ) corresponding to UL data communication or transmission (such as on an uplink shared channel (UL-SCH) or an entity uplink shared channel (PUSCH)) The ACK response may encode one or more bits of the ACK or negative ACK (NACK) by using repetition coding or simple coding or the like without attaching the CRC to the payload. When the group shared PDCCH is carrying a dynamic indication that the assigned downlink resource portion of the slot is being preempted by another downlink communication or transmission prior to signaling the WTRU group or the WTRU cluster (one or more WTRUs), The indication can then be encoded by using repeated coding or single coding without attaching the CRC to the payload.

In the absence of error detection or correction, the WTRU may need to identify when the group shared PDCCH carries information for that WTRU. For example, the WTRU may receive an indicator regarding the group ID for the WTRU within the DCI carried by the group shared PDCCH. Figure 6 is an exemplary mapping 600 of group IDs to indicators within the DCI. Bits 602 can be mapped to various group IDs 604. The group ID identifies the beam, and the UE group is scheduled to receive information therefrom. At 600, the scheduler can divide the WTRU between 8 groups, where each WTRU group or WTRU cluster can be served by a different beam. In 600 or other configurations, the group ID may be a function of the beam ID over which the group shared PDCCH is transmitted or transmitted.

Figure 7 is an exemplary mapping 700 of the hidden identifiers within the group ID to DCI. In 700, the WTRU may be configured to implicitly infer information about the group ID by using a cyclic shift scrambling sequence, wherein the shift 702 is mapped to the group ID 704. After channel coding, the group shared PDCCH payload can be scrambled using a sequence of functions that can be cell ID, group ID, or beam ID. The WTRU may perform blind detection of the group ID assuming no cyclic shift and one or more cyclic shifts of the scrambling sequence.

As an example, when the WTRU belongs to group 1, the sequences c (0), c(1), ...c(M-1) can be used to sequence b(0), b(1), ...b(M- 1) Perform scrambling. In this configuration, the scrambling sequence is not cyclically shifted. For group 2, the sequences b(0), b(1), ...b can be used for the sequences c(M-1), c(0), c(1), ...c(M-2) M-1) is scrambled, which means that the scrambling sequence is cyclically shifted by 1 element. For group 3, the sequence b(0), b can be used for the sequence c(M-2), c(M-1), c(0), c(1), ...c(M-3) (1), ...b(M-1) are scrambled, which means that the scrambling sequence is cyclically shifted by 2 elements. This technique can be similarly configured for groups 4-6.

Figure 8 is an example 800 of a group ID indication using a block cyclic shift scrambling sequence. At 800, the WTRU may implicitly infer the group ID, where the scrambling sequence is cyclically shifted rather than cyclically shifted element by element. Example 800 includes REG 0-15 (804) and cyclic shifts 0-5 (802). The size of the block may be similar in length to REG (such as 12) or REG bundling (such as 24 for two REG bundlings, or 36 for 3 REG bundling). In the example 800, when the WTRU belongs to group 1, group 2 may include the utilization sequence c(MN), c(M-N+1), ..., c(M-1), c (0), c( 1), ...c(MN-1) scrambled sequences b(0), b(1), ...b(M-1) , where N represents the block length for each cyclic shift.

In some configurations, the group shared PDCCH may be delivered or transmitted with error detection. When the group sharing PDCCH is carrying the slot format configuration and other control information, the CRC may be appended to the payload before the channel encoding. Channel coding can utilize Reed-Muller codes or polar codes, etc., and can depend on the payload or data portion size. If the group shared PDCCH is carrying a HARQ ACK response corresponding to the UL data communication or transmission of the WTRU group or the WTRU cluster (one or more WTRUs), the HARQ from each WTRU within the group after the additional CRC operation The ACK/NACK can be jointly encoded by using a Reed-Muller code or a polar code. In another configuration, if the group shared PDCCH carries paging information or system information, the CEC may be attached to the payload before channel coding.

As explained herein, the WTRU may identify when the group shared PDCCH carries information for the WTRU by detecting a shared RNTI that masks the CRC. The shared RNTI may be assigned to a group of WTRUs or a cluster of WTRUs within the system by a scheduler or other component within the network. A WTRU may be configured with a shared RNTI and a WTRU-specific RNTI.

In some configurations, when error detection is used for the content of the group shared PDCCH, there may be a tradeoff between error correction and error detection based on the minimum Hamming distance. As an example, an error correction code with a minimum Hamming distance d can be used to correct the error of k ₁ bit and detect the error of k ₂ bit, as long as Just fine. When the block error correction code for the coding group shared PDCCH has a large minimum distance, it can be used for error correction and error detection. In a configuration for encoding a payload of a group shared PDCCH, a Reed-Muller code [32, 6, 16] having a length of 32 bits and encoding 6 bits with a minimum Hamming interval 16 may be utilized. Since the minimum Hamming distance of the code is 16, an error of up to 3 bits can be corrected and an error of up to 9 bits can be detected because (2) . This configuration is similar to using a 9-bit CRC length.

Error detection using a threshold for the soft detection metric may also be used for the content of the group shared PDCCH. The WTRU may be configured to use a threshold value for the absolute value of a soft detection metric, such as a Log Likelihood Ratio (LLR), to decode the bit, thereby performing error detection without the CRC. If the corresponding LLR has an absolute value greater than a certain threshold, the WTRU may conclude that the decoded bit is a valid decoded bit. If the corresponding LLR has an absolute value less than a certain threshold, the WTRU may consider the decoded bit to be an invalid decoded bit. If a bit or a number of bits of codewords are invalidated by the WTRU, the decoded codeword can be designated as an error.

A binary error correction code can also be configured for error detection of the content of the PDCCH shared by the group. When a subset of binary error correction codes is configured, the difference between the subset and the entire code or the remainder of the code can be used for error detection. If the decoded codeword does not belong to a specified subset, it may be an error. For example, if Reed-Muller code [32, 16, 8] is used, and instead of encoding 16-bit data, the Reed-Muller code can be used to encode 11-bit information, and an error detection probability of 2-5 can be expected. This is similar to a CRC of length 5.

In some configurations, the extended group shared PDCCH may be used to transmit the extended GC-DCI, which includes the remaining GC-DCIs other than the light GC-DCI. The content of the extended GC-DCI may include a group ID, information about a beam for a WTRU group or a WTRU cluster scheduled to receive information, a starting position of the PDSCH in the time slot, and a DL CORESET in the time slot. End location, UL SR resource configuration, DL preemption indication for previous time slot, DL ACK associated with UL data communication or transmission, or with restrictions on WTRU-specific search space and on a subset of the WTRU-specific search space Perform information about blind decoding. The extended group shared PDCCH may be constructed to partially or fully reuse the NR-PDCCH structure similarly to the unified group shared PDCCH.

In order to transmit the shared PDCCH of the group carrying the SFI, different communication or transmission modes may be configured. The communication or transmission mode can be a function of payload length, CRC, or channel coding. As an example, a CRC based communication or transmission mode may use a polar code as a forward error correction, and a CRC (CRC-less) communication or transmission mode may use a Reed-Muller code. The communication or transmission mode of the shared PDCCH carrying the SFI may be fixed or pre-configured.

The transmission mode can also be configured by information on a physical broadcast channel (PBCH), higher layer communication, or RRC communication. The configuration information of the communication or transmission mode of the group sharing PDCCH carrying the SFI may include the following parameters: CORESET, allocated resources, CCE, REG, REG bundling size, mapping of REG bundling to CCE, coding scheme, polarity code, The Reed-Muller code, the error detection scheme, the CRC information, the monitoring rate of the shared PDCCH of the group carrying the SFI, or the SFI payload size. The WTRU may implicitly infer from other parameters the configuration parameters of the group sharing PDCCH carrying the SFI.

The monitoring rate of the GC-PDCCH is variable. The monitoring rate for a plurality of time slots or polymerization time slots can be changed once for each of the plurality of time slots (and for the case of a single time slot, it can be a time slot per time). When monitoring the rate of once per time slot, the WTRU may determine that the payload bits to n bits, and when the rate is monitored every m polymerization time slot, the WTRU may determine the payload size of up to n bits m Times.

The payload size of the SFI can depend on the monitoring rate. When the SFI carries information corresponding to multiple time slots or aggregation time slots, etc., the payload may be greater than the payload when the SFI carries information for a single time slot. In some configurations, the channel coding scheme can be determined based on the SFI payload size. The WTRU may be configured to determine that the channel coding scheme is a Reed-Muller code when the SFI payload size is less than a threshold, or when the monitoring rate is once per slot. The WTRU may determine that the channel coding scheme is a polarity code when the SFI payload size is greater than a certain threshold, or when the monitoring rate is once per multiple time slots.

The configuration utilizing the CRC can be determined based on the SFI payload size. The WTRU may determine that no CRC is attached to the SFI payload when the SFI payload size is less than a threshold, or when the monitoring rate is once per slot. The WTRU may determine that the CRC is attached to the payload when the SFI payload size is greater than a certain threshold, or when the monitoring rate is once per multiple time slots. The CRC length may be fixed, predetermined, or the WTRU may implicitly determine the CRC length based on the SFI payload.

The allocated resources can be determined based on a channel coding scheme. If polar coding with CRC is configured, the WTRU may determine the degree of aggregation (determining the number of allocated CCEs) is greater than the number of CCEs allocated when Reed-Muller channel coding without CRC is configured. The WTRU may also implicitly derive the location of the allocated resource, such as the first CCE index, based on the channel coding and error detection scheme. The allocated resources can also be determined based on the SFI payload size. When the SFI payload size is less than a threshold, the WTRU may determine that a smaller degree of aggregation is configured. When the SFI payload size is greater than a certain threshold, the WTRU may determine that a greater degree of aggregation is configured.

Figure 9 is a schematic diagram of an example 900 of a dynamic group shared PDCCH with three types of information. Although three types are shown within this example, any number of PDCCH types may be configured or utilized. PDCCH type 1 may include DCI 1-4. PDCCH type 2 may include DCI 2 and DCI 5-7. PDCCH type 3 may include DCI 3-7. The content of the group shared PDCCH may be dynamically changed based on the information passed. The PDCCH type may also be assigned an independent search space parameter, and the WTRU assigned to the group may be signaled by the search space parameter. In addition, the PDCCH type can be delivered in different periods, and the period of a specific GC type is set statically, semi-statically, dynamically, or the like.

FIG. 10 is a diagram of an example 1000 of a dynamic group shared PDCCH with a DCI index. In 1000, the group shared PDCCH may transmit DCI indexes 1, 3, and 4 indicating the contents of PDCCH DCI 1, DCI 3, and DCI 4, respectively. The WTRU may read the index and identify the delivered content based thereon. In addition, the group shared PDCCH may be composed of a limited set, and each has an index indicating the DCI information content to be delivered. The WTRU can read the index and identify the content of the communication or transmission. The index may be delivered along with additional resource information indicating the location of the PDCCH shared by the remaining groups within the light group shared PDCCH.

The GC-DCI can also be passed on the PDCCH. The shared control information for the WTRU group or the WTRU cluster may be configured or constructed similar to the WTRU-specific PDCCH, but the associated CRC is masked with a group shared RNTI, a shared RNTI, or a System Information RNTI (SI-RNTI) or the like. With this configuration, different types of shared DCI or GC-DCI with different corresponding search spaces or different corresponding types of RNTIs can be utilized.

The content of the GC-DCI may include a preemption indication for the downlink, which may indicate to the WTRU group or the WTRU cluster that the set of resources was punctured in the previous one or more time slots. Preemption can also mean using time slots for URLLC devices. The resource granularity within the frequency may be an RBG size, a multiple of the RBG size, a block of k RBGs (k is an integer), a portion of the system bandwidth, or a fraction of the system bandwidth portion, and the like. The granularity of the preemptive indication within the frequency may be semi-statically configured by higher layer communication or RRC communication. The granularity of the preemptive indication within the time may be a symbol of each symbol, a multiple of the symbol, a time slot, or a partial time slot.

The size of the DCI can be reduced by the high granularity of the preemptive indication within time or frequency. The puncturing zone can be a contiguous zone within time and frequency. When continuous, it may be necessary to advertise the start or end of the punched area. If the granularity of the preemptive indication is N _f possible blocks in the frequency and N _t blocks in the time, then at least One bit for transmission, where log(.) is the base 2 logarithm, and Is the number of combinations of 2 in n (or " n choose 2"). As an example, if the granularity indicated in the frequency is 1/20 of the bandwidth, and if the start and end of the preemption can be each of the 14 symbols of the last time slot, the number of bits can be given. for .

The frequency and time indication of the DCI can be mapped separately. For example, the first 190 of the start and end of the frequency may be transmitted by 8 bits, and the 91 of the start and end of the first time may be sent by 7 bits. . In order to map the information to a bit, the available ones can be indexed and the base 2 can be sent.

11 is a flow diagram of an exemplary WTRU process 1100 for group shared PDCCH reception. The CORESET configuration and GC-RNTI (1102) can be obtained by PBCH, RRC communication, or higher layer communication. The shared search space can be monitored for one or more shared DCIs per T2 time slots (1104). Blind detection (1106) and decoding of the shared DCI (1108) may be performed for the group shared PDCCH. If configured, the assigned location or search space can be monitored for the T1 time slot (1110) or at a variable rate for the group sharing PDCCH, and the SFI can be decoded (1112).

When the PDCCH is shared by the unified group, the shared search space can be used to monitor and blindly detect the group shared PDCCH. The shared search space may overlap with the WTRU-specific search space. In this configuration, or when the light has a similar structure to the extended group shared PDCCH, the WTRU may perform multiple blind decodings corresponding to multiple DCI formats on each PDCCH candidate.

Each DCI format of a different payload size may correspond to a light or extended group shared PDCCH. A DCI format (such as a short GC-DCI) corresponding to a light group shared PDCCH may carry a smaller message size, and a DCI format (such as a long GC-DCI) corresponding to an extended group shared PDCCH may carry a larger The size of the message. In this configuration, the WTRU may be configured to perform at least two or more blind decodings for each PDCCH candidate to detect control messages transmitted or transmitted for the WTRU and on the group shared PDCCH.

A single message size, such as GC-DCI, can also be defined for the light and extended group shared PDCCH. In this configuration, the WTRU may perform one blind decoding attempt for each PDCCH candidate to distinguish between different group sharing control messages. The WTRU may descramble the CRC attached to the message and distinguish the light and extended group shared PDCCH based on different identifiers (such as RNTI) of the CRC that mask each group shared message. The WTRU may determine that the indicator that implicitly indicates that the CRC is used for the group common message of the SFI is SFI-RNTI, the identifier for the preemptive indication is PI-RNTI, or an indicator for remaining system information ((RMSI)) -RNTI) and so on.

In another configuration, the WTRU may distinguish between a light and extended group shared PDCCH by detecting an indication field of one or more bits transmitted within the GC-DCI. When configured, the WTRU may utilize the indication field to distinguish between GC-DCI formats between similarly sized messages for the light and extended group shared PDCCH.

The short message corresponding to the light group shared PDCCH may be padded with zero or 1 or the like to ensure that the light and extended group shared PDCCH has a similar payload size. Without padding, the WTRU may need to perform multiple multiple blind decodings corresponding to multiple GC-DCI sizes. Multiple blind decoding may increase computational complexity, burden or power usage.

The Light and Extended Group Shared PDCCH can be configured with different search spaces and structures. The extended group shared PDCCH may be configured with a structure similar to NR-PDCCH and a shared search space may be used. The shared search space may overlap with the WTRU-specific search space. The light group shared PDCCH may be configured with separate search spaces that do not overlap with the WTRU-specific search space.

The monitoring rate can vary for both light and extended group shared PDCCHs. The rate can be once or once in a time slot or the like. The monitoring rate may be semi-statically configured by RRC communication or dynamically configured by the group shared PDCCH to change the monitoring rate over time.

The CORESET information carried by the PBCH may be used by the WTRU to configure the group shared PDCCH for a given parameter configuration and may be used to receive both the group shared PDCCH and the WTRU specific PDCCH. When the PBCH is configured with multiple CORESETs, at least one of the CORESETs may be configured to carry a group shared PDCCH. In this configuration, the WTRU may still be able to receive a WTRU-specific PDCCH carrying a DL assignment or UL grant on the group shared search space.

When utilizing the PBCH, the group shared PDCCH may be transmitted or transmitted on the first OFDM symbol for the time slot of the CORESET. In this configuration, the WTRU may receive the SFI as early as possible in the time slot and rely on the system bandwidth such that a number of bits of the main system block (MIB) are available to communicate other desired information on the PBCH. In an example, for the time duration of three OFDM symbols used to control channel communication or transmission, up to 2 bits may be utilized to indicate the starting OFDM symbol of the CORESET. For this configuration, the WTRU may determine that the CORESET configured by the PBCH begins with the first OFDM symbol within the time slot. In addition, the time duration of the CORESET configured by the PBCH can be configured to be a predetermined or fixed one OFDM symbol length, or independent of the carrier bandwidth. This configuration allows up to two bits within the MIB to be used for other control information.

When CORESET is configured with one CCE to REG mapping, the WTRU may determine interleaved REG to REG mapping for one or more CORESETs configured with PBCH. In the configuration, the REG of a given CCE may be grouped into REG bindings, and then the REG bindings may be interleaved within the CORESET. The REG bundling size of the CORESET(s) configured by the PBCH may be small to optimize or maximize the frequency diversity gain for the group shared PDCCH.

In some configurations, the CORESET information carried by the PBCH may be specific to the frequency resource configuration. Information related to the parameter configuration of the RMSI may be included in the MIB to reduce monitoring of the shared PDCCH of the group carrying time slot format related information (such as SFI) in the time slot. In addition to those CORESETs configured by the PBCH, the CORESET(s) carrying the WTRU-specific search space can be semi-statically configured by utilizing the MIB.

The search space of the shared PDCCH may have a configuration regarding group shared PDCCH monitoring. A monitoring group sharing PDCCH (such as a PDCCH with SFI) and a PDCCH carrying a shared DCI (such as GC-DCI) may utilize a shared search space or a group shared search space, and utilize a given search space for sharing with the group A fixed or predetermined location of the PDCCH. The shared search space may be monitored by WTRUs within the cell, while the group shared search space may be monitored by WTRUs within the group. The fixed or predetermined location may be a location of a PDCCH candidate with a fixed index inside the shared search space or the group shared search space.

The group shared search space may be a function of a group sharing RNTI (GC-RNTI), a cell ID, or other parameters. The group shared search space may include a plurality of PDCCH candidates having different degrees of aggregation. The group sharing PDCCH carrying the SFI may be transmitted at the beginning of the time slot using the location of one of the candidates of the group shared search space (eg, the candidate with index 0). Monitoring the group shared PDCCH carrying the SFI may vary from the GC-DCI carried by the PDCCH. For example, the group shared search space may be monitored and blindly decoded at each time slot, and the location of the candidate with a fixed index may be monitored for the PDCCH carrying the SFI in each other time slot. Additionally, alternatively, similar locations within the search space may be used in each of the other time slots to monitor the SFI and preemption indications. The group sharing PDCCH carrying the SFI may also be monitored at a fixed location inside the fixed search or the shared search space determined or scrambled by the SI-RNTI.

The SFI can be dynamic and can have an indicator or implicit indication of the time slot format. For this configuration, a mapping between the content of the dynamic SFI delivered or transmitted by the group shared PDCCH and the format of the corresponding one or more time slots may be utilized. An indication of the dynamic time slot format based on the content of the dynamic SFI and the fixed or configurable form can be utilized.

In addition, a dynamic indication of the time slot format for a time slot or time slot set may utilize a table (depending on the SFI payload size) that indicates the time slot format or each time slot in the associated time slot set based on the content of the dynamic SFI The format. Table 2 shows an example of an indication of a time slot format based on dynamic SFI content for a 3-bit payload size. The DL center time slot may mainly include downlink symbols, or may be configured to support time slot based PDSCH without PUSCH. The UL hub time slot may primarily include uplink symbols, or may be configured to support time slot based PUSCH without PDSCH. Unknown centers or unknown time slots can mainly include unknown symbols. Table 2

A table can be utilized to map dynamic SFIs to a format configuration with respect to time slots, or sets of consecutive or discontinuous time slots. The configuration can be advertised by RRC communication or higher layer communication or the like. This configuration can also be set by configuration regarding the dynamic SFI payload size and associated monitoring period or rate.

Table 3 shows an example of different types of dynamic SFI mappings using bit maps. In this example, the four bits advertised within the SFI may indicate the type of dynamic SFI mapping for the time slot or time slot set. table 3

The monitoring period or rate of the dynamic SFI can also be configured by RRC or higher layer communication or the like. Table 4 shows an example of a dynamic SFI monitoring cycle by means of 3 bits. Table 4

The WTRU may implicitly determine the payload size of the dynamic SFI based on the configuration of the dynamic SFI mapping type and the dynamic SFI monitoring period or rate. For example, if dynamic SFI mapping is per-slot slot mapping, and two bits per slot are for four possibilities: DL, UL, unknown, and reserved, and the monitoring period is configured for every two time slots, Then the dynamic SFI payload size can be determined as 2 × 2 = 4 bits. The payload size of the dynamic SFI can also be separately advertised and configured by RRC communication or higher layer communication.

An implicit configuration of the table associated with the dynamic SFI can also be utilized. For this configuration, the mapping of the content of the dynamic SFI to the time slot format can be performed by implicitly configuring the mapping by parameters configured based on RRC communication or higher layer communication. Additionally, the implicit configuration of the table associated with the dynamic SFI can be based on the SFI monitoring rate. For example, a dynamic SFI monitoring period that is less than once every two time slots may indicate that the time slot format is similar to a time slot within a dynamic SFI monitoring cycle. In another example, a dynamic SFI monitoring cycle can reduce dynamic SFI mapping.

In another configuration, the implicit configuration of the table associated with the dynamic SFI may be based on a combination of the SFI monitoring rate and the SFI payload size. In this case, the combination of the SFI monitoring rate and the SFI payload size can implicitly determine the mapping of dynamic SFI content to time slot format. For example, the 8-bit dynamic SFI payload size and the SFI monitoring period once every two time slots can implicitly indicate that the dynamic SFI content-to-time slot format mapping is a bit map per half-time slot, where each half-time slot exists. 4 possibilities. Further, an implicit indication of the mapping of the dynamic SFI content to the time slot format based on the combination of the SFI monitoring rate and the SFI payload size may be predetermined or fixed or the like.

In another configuration, the implicit configuration of the table associated with the dynamic SFI may be based on the number of DL/UL switch points or other attributes of the time slot format. In an example, the attributes of the time slot format for a set of time slots, or sets of consecutive, non-contiguous time slots, may be indicated within a semi-static configuration included in RRC or higher layer communications. For example, a maximum of k DL/UL switching points (one or more) may be indicated in a time slot format for a time slot or time slot set, and the content of the dynamic SFI may be RRC mapped to the time slot according to the attribute indication. Format, where k can be zero or a positive integer. In this example, the implicit indication of the dynamic SFI content to time slot format mapping based on the number of switching points or other attributes of the time slot format may be set by a table, which is predetermined or fixed, and the like.

In another example, the indication of the dynamic time slot format may be based on the contents of the semi-static SFI and the dynamic SFI. The dynamic time slot format of the time slot or time slot set can be based on the content of the semi-static SFI. For example, if the semi-static SFI of the time slot or time slot set indicates a combination of DL and "unknown", the table for the time slot format of the time slot or time slot set may exclude UL and may only include DL and "unknown" .

Although features and elements of a particular combination are described above, those of ordinary skill in the art will recognize that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in a computer program, software or firmware incorporated into a computer readable medium for use by a computer or processor. Examples of computer readable media include electrical signals (transmitted via wired or wireless connections) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor memory devices, magnetic media (eg internal hard drives) And detachable magnetic disks), magneto-optical media, and optical media (such as CD-ROM discs and digital versatile discs (DVD)). A processor associated with the software can be used to implement a radio frequency transceiver for use at a WTRU, UE, terminal, base station, RNC, or any computer host.

100‧‧‧Communication system

102, 102a, 102b, 102c, 102d‧ ‧ ‧ wireless transmit / receive unit (WTRU)

104‧‧‧Radio Access Network (RAN)

106‧‧‧ Core Network (CN)

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧Transmission/receiving components

124‧‧‧Speaker/Microphone

126‧‧‧Keypad

128‧‧‧Display/Touchpad

130‧‧‧ Non-removable memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧ Peripherals

160a, 160b, 160c‧‧‧e Node B

162‧‧‧Action Management Entity (MME)

164‧‧‧Service Gateway (SGW)

166‧‧‧ Packet Data Network (PDN) Gateway (or PGW)

180a, 180b, 180c‧‧‧ gNB

182a, 182b‧‧‧Access and mobility management functions (AMF)

183a, 183b‧‧‧ Session Management Function (SMF)

184a, 184b‧‧‧ User Plane Function (UPF)

185a, 185b‧‧‧ Data Network (DN)

200‧‧‧Resource Element Group (REG) Structure

202, 204, 302, 304, 502, 504, 506, 508 ‧ ‧ symbols

206, 306, 406, 412‧‧‧ Information

300‧‧‧ structure

Examples of 400, 500, 800, 900, 1000‧‧

600, 700‧‧ ‧ mapping

602‧‧ bits

604, 704‧‧‧Group Identification (ID)

702‧‧‧Shift

802‧‧‧cyclic shift 0-5

804‧‧‧REG 0-15

1100‧‧‧WTRU process

CORESET‧‧‧Control Resource Collection

DCI‧‧‧Chain Control Information

DL‧‧‧Chain

GC-RNTI‧‧‧Group sharing RNTI

N2, N3, N4, N6, N11, S1, X2, Xn‧‧ interface

OFDM‧‧ Orthogonal Frequency Division Multiplex

PBCH‧‧‧ entity broadcast channel

PDCCH‧‧‧ entity downlink control channel

RRC‧‧‧ Radio Resource Control

SFI‧‧‧ slot format indicator

A more detailed understanding can be obtained from the following description taken in conjunction with the accompanying drawings, in which like reference numerals System diagram of an example of a communication system of various embodiments; FIG. 1B is a system diagram showing an example of a wireless transmission/reception unit (WTRU) that can be used within the communication system shown in FIG. 1A, according to an embodiment 1C is a system diagram showing an example of a Radio Access Network (RAN) and an exemplary Core Network (CN) that can be used inside the communication system shown in FIG. 1A according to an embodiment; 1D is a system diagram showing another example of a RAN and another example of CN that can be used inside the communication system shown in FIG. 1A according to an embodiment; FIG. 2 is a chain-sharing control for a group sharing entity Schematic diagram of an exemplary resource element group (REG) structure of a channel (PDCCH); FIG. 3 is a schematic diagram of an exemplary structure of REG and REG bundling for a group shared PDCCH; FIG. 4 is a diagram of using REG, REG bundling and control Schematic diagram of Channel Element (CCE) and examples of Forward Error Correction (FEC) and Cyclic Redundancy Code (CEC) for PDCCH; Figure 5 is the first map of group shared PDCCH to control resource set (CORESET) Schematic diagram of an example of an OFDM symbol; FIG. 6 is an exemplary mapping of group identification (ID) to an indicator transmitted within a group shared PDCCH; FIG. 7 is a group ID to downlink control information (DCI) An exemplary mapping of implicit indicators; Figure 8 is an example of a group ID indication using a block-wise cyclically shifted scrambling sequence; Figure 9 is a dynamic group shared PDCCH with three types of information. FIG. 10 is a schematic diagram of an example of a dynamic group shared PDCCH with a DCI index; and FIG. 11 is a flowchart of an exemplary WTRU procedure for group shared PDCCH reception.

Claims (14)

A wireless transmit/receive unit (WTRU), comprising: a transceiver configured to receive a radio resource control (RRC) message, wherein the RRC message includes a group of shared entities having a time slot format indicator (SFI) One or more monitoring rates of a downlink control channel (GC-PDCCH); and a processor configured to monitor the GC-PDCCH having the SFI at the one or more monitoring rates. The WTRU as claimed in claim 1, wherein a control resource set (CORESET) and a group share identification (GC-ID) are received by the WTRU. The WTRU as claimed in claim 1, wherein the WTRU monitors the GC-PDCCH on a first orthogonal frequency division multiplexing (OFDM) symbol of a monitored time slot, and the GC-PDCCH A location within the shared search space is fixed or pre-specified. The WTRU as recited in claim 1, wherein an SFI payload size is determined based on the one or more monitoring rates. The WTRU as claimed in claim 4, wherein the WTRU detects and decodes with a Reed-Muller code in the absence of a cyclic redundancy check (CRC) if the SFI payload size is less than a threshold. The GC-PDCCH, and wherein the SFI is decoded from the GC-PDCCH. The WTRU of claim 5, wherein the WTRU determines the GC-PDCCH for a group common identification (GC-ID) of the WTRU using a cyclic shift scrambling sequence. The WTRU of claim 4, wherein the WTRU detects and decodes the GC based on a polarity code with a cyclic redundancy check (CRC) that utilizes a group-shared identification (GC-ID) scrambling. - PDCCH, and wherein the SFI is decoded from the GC-PDCCH. A method performed by a WTRU, the method comprising: receiving, by the WTRU, a Radio Resource Control (RRC) message, wherein the RRC message includes a group for a time slot format indicator (SFI) One or more monitoring rates of a shared entity downlink control channel (GC-PDCCH); and monitoring, by the WTRU, the GC-PDCCH having the SFI at the one or more monitoring rates. The method of claim 8, wherein a control resource set (CORESET) and a group share identification (GC-ID) are received by the WTRU. The method of claim 8, further comprising: monitoring, by the WTRU, the GC-PDCCH on a first orthogonal frequency division multiplexing (OFDM) symbol of a monitored time slot, and the A location of the GC-PDCCH is fixed or pre-specified within a shared search space. The method of claim 8, wherein an SFI payload size is determined based on the one or more monitoring rates. The method of claim 11, further comprising: using the Reed-Muller code by the WTRU without a cyclic redundancy check (CRC) if the SFI payload size is less than a threshold value The GC-PDCCH is detected and decoded, and the SFI is decoded from the GC-PDCCH. The method of claim 12, further comprising determining, by the WTRU, a GC-PDCCH for a group common identification (GC-ID) of the WTRU using a cyclic shift scrambling sequence. The method of claim 11, further comprising: detecting, by the WTRU, a polar code with a cyclic redundancy check (CRC) using a group-shared identification (GC-ID) scrambling The GC-PDCCH is decoded, and wherein the SFI is decoded from the GC-PDCCH.