Beam-based PDCCH transmission within NR

Abstract

Systems, methods, and tools are disclosed for beam-based PDCCH transmissions within NR. A set of control resources may be assigned for multi-beam control transmissions. The PDCCH may be transmitted using multiple beams. The CCE mapping may be used for multi-beam transmission. The DCI may support multi-dimensional transmissions with a primary dimension and a secondary dimension. The search space can support multi-beam and multi-TRP transmission.

Description

This application is a divisional application of the Chinese invention patent application with the application date of April 30, 2018, application number 201880029151.6, and invention name “Beam-based PDCCH transmission within NR”. CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 62 / 500,645 filed on May 3, 2017, U.S. Provisional Application No. 62 / 519,555 filed on June 14, 2017, U.S. Provisional Application No. 62 / 543,087 filed on August 9, 2017, and U.S. Provisional Application No. 62 / 599,124 filed on December 15, 2017, the entire contents of which are incorporated herein by reference. Background Art

[0002] Mobile communications are continuously evolving. The fifth generation may be referred to as 5G. Previous or legacy mobile communications may be, for example, 4th generation (4G) long term evolution (LTE). Mobile wireless communications implement various radio access technologies (RATs), such as new radio (NR). Use cases for NR may include, for example, extreme mobile broadband (eMBB), ultra-high reliability and low latency communications (URLLC), and massive machine type communications (mMTC). Summary of the invention

[0003] Disclosed herein are systems, methods, and tools for beam-based PDCCH transmission within NR. A beam-based control resource set (CORESET or coreset) configuration may be used. A control resource set may be assigned for multi-beam control transmission. Multi-beam PDCCH transmission may be utilized. CCE mapping may be used for multi-beam transmission. Per-symbol interleaving and across symbol interleaving may be used. For per-symbol interleaving, the effective search space may be reduced. DCI may support multi-dimensional transmission with a primary dimension and an auxiliary dimension. The search space may support multi-beam, multi-TRP transmission.

[0004] A wireless transmit / receive unit (WTRU) may have a computer processor configured to determine a PDCCH. The WTRU processor is configured to receive a PDCCH transmission from a wireless communication system, the transmission including a control resource set (CORESET) configuration, the configuration including a resource group (REG) bundle; determine whether the REG bundle is interleaved within a symbol or between symbols; if the WTRU determines that the REG bundle is interleaved between symbols, detect the REG bundle by using a beam corresponding to the REG bundle; and / or determine a multi-beam PDCCH by using the detected REG bundle and a multi-beam associated with the PDCCH transmission.

[0005] The WTRU processor may be configured to determine that the received REG bundling is bundled by frequency, such that the REG bundling indicates to the WTRU that the PDCCH transmission is a multi-beam transmission.

[0006] The WTRU processor may be configured to detect the REG bundle using a beam corresponding to the REG bundle and quasi collocated (QCL) information for the REG bundle if the WTRU determines that the REG bundle is interleaved between symbols.

[0007] The WTRU processor may be configured to determine that the received PDCCH transmission is a multi-beam transmission by determining that the WTRU received multiple QCL information corresponding to multiple OFDM symbols within the received PDCCH transmission.

[0008] The CORESET configuration may include one or more of the following: CORESET size, REG bundling type, transmission mode, aggregation level set, DCI information size set, number of PDCCH candidates, the QCL information, and an indication of whether the CORESET is single beam or multi-beam. The QCL information may include one or more of the following: average gain, average delay, Doppler shift, Doppler spread, and spatial receiver parameters. The CORESET configuration may include an indication of REG bundling interleaving mode.

[0009] The WTRU processor may be configured to detect the REG bundling by using PBCH / SYNC beam tracking if the WTRU determines that the REG bundling is interleaved within a symbol.

[0010] The WTRU processor may be configured to determine a single beam PDCCH by using deinterleaving of the detected REG bundles.

[0011] The WTRU processor may be configured to determine from the CORESET configuration whether the REG bundling interleaving mode is one of: time-first bundling without interleaving, time-first bundling with interleaving, frequency-first bundling with per-symbol interleaving, and frequency-first bundling with inter-symbol interleaving. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented.

[0013] Figure 1B is a diagram showing that according to an embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within a communication system is shown.

[0014] Figure 1C is a diagram showing that according to an embodiment, Figure 1A System diagram of an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) used within a communication system is shown.

[0015] Figure 1D is a diagram showing that according to an embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used within the communication system shown.

[0016] Figure 2A is an example of a control resource set with PDCCH candidates that can be sent on beam 1 and / or beam 2.

[0017] Figure 2B This is an example of CORSET.

[0018] Figure 3 is an example of different sets of control resources that may be associated with different beams on different OFDM symbols.

[0019] Figure 4 is an example of four CCEs on two OFDM symbols assigned to a PDCCH candidate.

[0020] Figure 5 is an example of distributing CCEs on multiple / different beams (eg, on the first and second OFDM symbols).

[0021] Figure 6 2 is an example of frequency-first CCE to candidate mapping for PDCCH.

[0022] Figure 7is an example of time-first REG-to-CCE mapping when (eg, all) OFDM symbols of the control region may be associated with one (eg, one) beam and one (eg, one) control resource set.

[0023] Figure 8 This is an example of distributed frequency priority mapping from REG to CCE.

[0024] Fig. 8A An example of interleaving using frequency-first REG bundling with per-symbol interleaving and inter-symbol interleaving within a multi-symbol CORESET.

[0025] Fig. 9 This is an example of cross-beam scheduling.

[0026] Fig.10 An example of a frame structure utilizing cross-beam scheduling.

[0027] Fig.11 This is an example of cross-plane scheduling when there are four planes.

[0028] Fig.12 An example of cross-TRP scheduling with two TRPs.

[0029] Fig.13 An example of cross-TRP scheduling with decoupled downlink / uplink. DETAILED DESCRIPTION

[0030] A detailed description of the illustrative embodiments will now be described with reference to the various drawings. Although the present description provides detailed examples of possible implementations, it should be noted that these details are intended to be exemplary and in no way limit the scope of the present application.

[0031] Figure 1A 1 is a diagram showing an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may 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 tail unique word DFT spread OFDM (ZT UW DTS-sOFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.

[0032] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. 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 a “station” and / or “STA” and may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices working in an industrial and / or automated process chain environment), consumer electronic devices, and devices working on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0033] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a and 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 (e.g., the CN 106 / 115, the Internet 110, and / or other networks 112). For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. Although each of the base stations 114a, 114b is depicted as a single component, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.

[0034] The base station 114a may be part of the RAN 104 / 113, and the RAN 104 / 113 may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals at one or more carrier frequencies, and the base station 114a and / or the base station 114b may be called a cell (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of a licensed and unlicensed spectrum. A cell may provide wireless service coverage for a specific geographic area that is relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, that is, each transceiver corresponds to a sector of the cell. In one embodiment, the 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 may be transmitted and / or received in a desired spatial direction.

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

[0036] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. 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 ​​UL Packet Access (HSUPA).

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

[0038] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using new radio (NR).

[0039] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access (e.g., using dual connectivity (DC) principles). Thus, the air interface used 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).

[0040] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies 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), and GSM EDGE (GERAN), among others.

[0041] Figure 1AThe base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may use any appropriate RAT to facilitate wireless connectivity in a local area, which may be, for example, a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE802.15. In another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-APro, NR, and the like). Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b does not necessarily need to access the Internet 110 via the CN 106 / 115.

[0042] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or may perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 employing NR radio technology, the CN 106 / 115 may also be in communication with other RANs (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0043] The CN 106 / 115 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 that provides plain old telephone service (POTS). The Internet 110 may include a system of globally interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as the RAN 104 / 113.

[0044] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0045] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a numeric 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 should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

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

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

[0048] Although in Figure 1B 102 as a single component, but the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving radio signals over the air interface 116.

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

[0050] The processor 118 of the WTRU 102 may be coupled to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. 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 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 storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, and a secure digital (SD) memory card, among others. In other embodiments, the processor 118 may access information from and store data in memories that are not physically located in the WTRU 102, such as, for example, a server or a home computer (not shown).

[0051] 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 in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

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

[0053] The processor 118 may also be 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 video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. 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 sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0054] The WTRU 102 may include a full-duplex radio for which reception and transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interface management unit 139 to reduce and / or substantially eliminate self-interference by means of hardware (e.g., chokes) or by signal processing by a processor (e.g., a separate processor (not shown) or by the processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., with respect to transmission) and downlink (e.g., with respect to reception)) may be concurrent and / or simultaneous.

[0055] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In addition, the RAN 104 may also communicate with the CN 106.

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

[0057] Each of the eNodeBs 160a, 160b, 160c 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, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0058] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing components is described as being part of the CN 106, it should be appreciated that any of these components may be owned and / or operated by an entity other than the CN operator.

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

[0060] 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 also perform other functions, such as anchoring the user plane during inter-eNB handovers, triggering paging processing when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.

[0061] The SGW 164 may be connected to the PGW 146, 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.

[0062] 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 be in communication with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve 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.

[0063] Although in Figures 1A-1D Although the WTRU is described as a wireless terminal, it should be appreciated that in certain typical embodiments, such a terminal may use a (eg, temporary or permanent) wired communication interface with a communication network.

[0064] In a typical embodiment, the other network 112 may be a WLAN.

[0065] A WLAN using 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 may access or be connected to a distributed system (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating from outside the BSS and destined for the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. The point-to-point traffic may be sent using a direct link establishment (DLS) between the source and destination STAs (e.g., directly between them). In certain typical embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS)). A WLAN using an independent BSS (IBSS) mode does not have an AP, and STAs (eg, all STAs) within or using the IBSS can communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.

[0066] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a width that is dynamically set with the aid of signaling. The primary channel may be a working channel of the BSS and may be used by the STA to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access (CSMA / CA) with collision avoidance (e.g., in an 802.11 system) may be implemented. For CSMA / CA, STAs including the AP (e.g., each STA) may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. In a given BSS, one STA (e.g., only one station) may transmit at any given time.

[0067] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide primary channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).

[0068] Very high throughput (VHT) STA can support channels with widths of 20MHz, 40MHz, 80MHz and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels or by combining two discontinuous 80MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can divide the data into two streams. Inverse fast Fourier transform (IFFT) processing and time domain processing can be completed separately on each stream. The stream can be mapped on two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0069] 802.11af and 802.11ah support sub-1 GHz operating modes. The channel operating bandwidth and carriers 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 typical embodiments, 802.11ah may support instrument type control / machine type communication (e.g., MTC devices in macro coverage areas). MTC devices may have certain capabilities, such as limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include a battery, and the battery life of the battery is above a threshold (e.g., maintaining a very long battery life).

[0070] For a WLAN system that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah), the WLAN system includes a channel that can be designated as a primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a certain STA, where the STA is derived from all STAs operating in the BSS and the STA supports the minimum bandwidth operating mode. In the example about 802.11ah, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz and / or other channel bandwidth operating modes, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the width of the primary channel can be 1MHz. Carrier sensing and / or network allocation vector (NAV) settings can depend on the state of the primary channel. If the primary channel is busy (eg, because a STA (which only supports 1 MHz operating mode) is transmitting to the AP), the entire available band may be considered busy even though most of the band remains idle and available for use.

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

[0072] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As described above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In addition, the RAN 113 may also communicate with the CN 115.

[0073] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. Each of the gNBs 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may use beamforming processing to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple component carriers to WTR 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) techniques. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0074] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with the scalable parameter configurations. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different 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., containing different numbers of OFDM symbols and / or lasting different absolute time lengths).

[0075] 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 other RANs (e.g., the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect to the gNB 180a, 180b, 180c while communicating / connecting to another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principle. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.

[0076] 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, user scheduling in UL and / or DL, support network slicing, implement dual connectivity, implement interworking between NR and E-UTRA, route user plane data to a user plane function (UPF) 184a, 184b, and route control plane information to an access and mobility management function (AMF) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other through the Xn interface.

[0077] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the aforementioned components is described as part of the CN 115, it should be understood that any of these components may be owned and / or operated by entities other than the CN operator.

[0078] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. The AMF 182a, 1823b may use network slicing processing to customize the CN support provided to the WTRU 102a, 102b, 102c based on the service type of the WTRU 102a, 102b, 102c used. As an 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 massive mobile broadband (eMBB) access, and / or services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) using other radio technologies, such as non-3GPP access technologies such as LTE, LTE-A, LTE-A Pro, and / or WiFi.

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

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

[0081] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the CN 108. In addition, the CN 115 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 one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b and through the UPF 184a, 184b.

[0082] In view of Figures 1A-1D and about Figures 1A-1D , one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other one or more devices described herein. These simulation devices may be one or more devices configured to simulate one or more or all of the functions herein. For example, these simulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0083] 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 simulation devices can perform one or more or all functions while being implemented and / or deployed as part of a wired and / or wireless communication network in whole or in part to test other devices inside the communication network. The one or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to other devices to perform the test, and / or can use over-the-air wireless communication to perform the test.

[0084] One or more simulation devices can 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 a test scenario of a wired and / or wireless communication network that is not deployed (e.g., tested) to implement tests on one or more components. The one or more simulation devices can be test devices. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication with the aid of RF circuits (which can include one or more antennas, for example).

[0085] For example, compared to 4G Long Term Evolution (LTE) that supports frequencies below 6 GHz, 5G New Radio (NR) may support millimeter wave communications. Support for millimeter wave communications may involve beam-based (e.g., relative to cell-based) implementations for data and control transmissions. The physical downlink control channel (PDCCH may support LTE downlink control channels. Enhanced PDCCH (EPDCCH) may support LTE advanced downlink control channels. EDPCCH may divide resources between data and control, for example, by using frequency division multiplexing (FDM). The frequency modulation assigned for EDPCCH may cover an entire subframe, rather than, for example, three or four orthogonal frequency division multiplexing (OFDM) symbols. PDCCH and EPDCCH may not support multi-beam control and data transmission for 5G NR. Systems, methods, and tools for PDCCH transmission for cell-based and multi-beam-based architectures are provided herein.

[0086] Cell-based and multi-beam-based architectures may support PDCCH transmissions. For example, by using a 5G beam-based downlink control channel, a 5G NR wireless system may support a wide range of frequencies and WTRUs with different latency and reliability requirements. A cell-based system architecture (e.g., at a lower frequency) may broadcast the PDCCH to all WTRUs within a cell. A beam-based system architecture (e.g., at a higher frequency) may provide a beam-based PDCCH to the WTRUs covered by the beam. Support for multi-beam transmissions may be provided within a transmission / reception point (TRP) or between multiple TRPs while supporting (e.g., simultaneously) unified operation across a frequency range.

[0087] A reference symbol may represent a symbol (such as a complex number that may be fixed and known) and may be used as a pilot. A reference signal may be used to represent a time domain signal that may be generated after processing the reference symbol. In one example (e.g., for OFDM), the reference symbol may be a complex number that may be fed to an inverse discrete Fourier transform (IDFT) block. The reference signal may be the output of the IDFT block. A resource element (RE) may be an OFDM symbol on a subcarrier. A resource element group (REG) may refer to a group of REs that may be used as a building block for a control channel element (CCE), which may be used to assign resource elements to users. REG bundling may include REGs that may be adjacent in time or frequency, grouped together, and associated with the same decoder. NR-REG, NR-CCE, and NR-PDCCH may be used to refer to REGs, CCEs, and PDCCHs for new radios within 5G. WTRU and user may be used interchangeably.

[0088] A control resource set may be assigned for a multi-beam control transmission. The control resource set may include a number of search spaces. A search space (e.g., each search space) may include a number of PDCCH candidates. For a DL control channel that may use beams, the control resource set may be defined and / or configured in a variety of ways. The CORESET configuration may be semi-static and may be accomplished using BCH or higher layer signaling (e.g., RRC). The CORESET configuration may include information such as (or any combination of) the following: CORESET size and resources (e.g., time and frequency); REG bundling type; transmission mode (e.g., distributed, localized, interleaved, and non-interleaved mapping with respect to REG bundling); a set of aggregation levels; a set of DCI format sizes; the number of PDCCH candidates that the WTRU may monitor for each DCI format size and each aggregation level (which may be zero for some combinations); quasi-co-location (QCL) assumption; or whether the CORESET is single-beam or multi-beam.

[0089] Multiple single-beam CORESETs may be used for assignment and / or configuration. Multiple single-beam CORESETs may be assigned and / or configured by using a set of control resources associated with the multiple beams.

[0090] Figure 2A is an example of a control resource set with PDCCH candidates that can be sent on beam 1 and / or beam 2.

[0091] In one example, the control resource (CORESET) set may cover OFDM symbols that may be assigned for downlink control (e.g., all OFDM symbols associated with multiple beams or a combination thereof). Different beams may be used on different OFDM symbols (e.g., Figure 2A exemplarily shown). In the resource set configuration, REG bundles may be configured as adjacent REGs in frequency. The mapping of REG bundles to CCEs may be in a frequency-first manner and may be done with or without interleaving. The CORESET configuration may include QCL assumptions for OFDM symbols that control the resource set. The QCL assumptions may include (e.g., all) QCL parameters (including average gain, average delay, Doppler shift, delay spread, Doppler spread, spatial RX parameters) or a subset thereof. The WTRU may receive a subset of QCL parameters that are common to (e.g., all) OFDM symbols, and may receive (e.g., additional multiple) subsets of QCL parameters corresponding to multiple OFDM symbols contained in the CORESET.

[0092] In order to configure the control resource set as a multi-beam form, the multi-beam attribute of the CORESET may be indicated (e.g., explicitly indicated) during configuration (e.g., via PBCH or RRC). For example, the WTRU may assume that the control resource set is in a multi-beam operation mode (e.g., if the WTRU receives multiple QCL assumptions corresponding to multiple OFDM symbols). The multi-beam attribute of the CORESET may be indicated (e.g., implicitly indicated) based on the REG to CCE mapping configured for the CORESET across multiple OFDM symbols. For example, the WTRU may assume that the control resource set is in a multi-beam operation mode (e.g., if the WTRU is configured with frequency-first REG to CCE mapping (or frequency-first REG bundling)). The WTRU may assume that the control resource set is in a single-beam operation mode (e.g., if the WTRU is configured with time-first REG to CCE mapping).

[0093] By default, the WTRU may assume no QCL (e.g., a CORESET may be configured as multi-beam and may indicate no QCL assumption within its configuration). The WTRU may assume that the same QCL assumption is valid for the CORESET as for the PBCH and / or synchronization signals.

[0094] The search space may include PDCCH candidates located on multiple OFDM symbols of a control resource set that may be sent on multiple beams. (E.g., each) PDCCH candidate may be sent (e.g., only) on (e.g., one) beam (e.g., on one OFDM symbol). Different PDCCH candidates of the search space may be located on different OFDM symbols that may be sent on different beams. A PDCCH candidate (e.g., one PDCCH candidate) may include CCEs located on different OFDM symbols that may be sent on different beams. CCEs may be configured on multiple (e.g., 2) OFDM symbols and may be sent on two different beams. Figure 2B Examples are shown for a single-beam CORESET and three multi-beam CORESETs. Figure 2B From left to right, the following are shown: (i) a single-beam CORESET, where each CORESET is associated with a single beam; (ii) a multi-beam CORESET, where each PDCCH is transmitted on a single beam; (iii) a multi-beam CORESET, where each CCE includes a multi-beam PDDCH transmitted on a single beam; and (iv) a multi-beam CORESET, where interleaved REG bundles include CCEs transmitted on different beams.

[0095] A control resource set may be associated with (eg, only one) beam (eg, a single-beam CORESET).

[0096] Figure 3 is an example of different sets of control resources that may be associated with different beams on different OFDM symbols.

[0097] Different resource control sets may be associated with different beams on different OFDM symbols (e.g., Figure 3). One or more (e.g., all) PDCCH candidates of the search space may be associated with (e.g., only one) beam and (e.g., one) OFDM symbol. One or more (e.g., all) candidates of the search space may be located within (e.g., one) control resource set. Adjacent control resource sets may have different or similar REG to CCE and CCE to candidate mappings. In one example, one control resource set may support localized PDCCH while other control resource sets may support distributed PDCCH. For example, when beams are transmitted on multiple OFDM symbols, one or more (e.g., all) PDCCH candidates of the search space may be associated with (e.g., only one) beam on one or more OFDM symbols. The CORESET single beam attribute may be included as part of the configuration of the CORESET, which may provide (e.g., by implication) a QCL assumption for the entire CORESET. An indication of time-first REG bundling (e.g., or time-first REG to CCE mapping) within the configuration of the CORESET may provide (e.g., implicitly) the single-beam property of the OCRESET and / or the QCL assumption for the entire OCRESET. A single beam may be used by default, and the single-beam REG to CCE mapping may be frequency-first (e.g., in the case where the control resource set spans only one OFDM symbol).

[0098] A multi-beam CORESET with (e.g., each) PDCCH transmitted on a single beam may be used. A CORESET may span multiple OFDM symbols associated with multiple beams (e.g., each beam is associated with one or more OFDM symbols). PDCCH candidates within the CORESET may be on one OFDM symbol and transmitted by one beam. The WTRU may use one QCL hypothesis for PDCCH detection (e.g., which may be associated with the OFDM symbol to which the PDCCH is mapped). Different PDCCH candidates for a WTRU-specific search space (including potential PDCCH candidates for the WTRU) may be associated with different beams. PDCCH candidates for a search space (e.g., all candidates) may be associated with a single beam. Based on (e.g., dynamic) signaling via a group-common PDCCH, the search space may be (e.g., dynamically) restricted to a subset of PDCCH candidates on one beam (e.g., in the case where the WTRU-specific search space is associated with multiple beams).

[0099] A multi-beam CORESET with (e.g., each) CCE transmitted on a single beam may be used. For a multi-beam CORESET, a PDCCH candidate may include two or more CCEs located on different OFDM symbols (e.g., where each CCE may potentially be transmitted on a different beam). A CCE may be mapped entirely on one OFDM symbol and may be transmitted by a single beam. The WTRU may use multiple QCL hypothesis sets for PDCCH detection, where (e.g., each) CCE is associated with a QCL hypothesis of the corresponding OFDM symbol to which it is mapped.

[0100] A multi-beam CORESET with interleaved REG bundles including CCEs may be transmitted on different beams. (E.g., each) REG bundle may be located (e.g., entirely located) on one OFDM symbol and transmitted by a single beam. In the case of interleaved REG bundles on different OFDM symbols of a CORESET, one CCE may include REG bundles located on different OFDM symbols and transmitted by different beams. The WTRU may include multiple QCL hypothesis sets for PDCCH detection, where each REG bundle is associated with a QCL hypothesis of the corresponding OFDM symbol to which it is mapped.

[0101] The REG bundling may follow a frequency-first mapping (e.g., for a multi-beam CORESET where each PDCCH is transmitted on a single beam; for a multi-beam CORESET where each CCE includes a multi-beam PDCCH transmitted on a single beam; and for a multi-beam CORESET where the interleaved REG bundling includes CCEs transmitted on a single beam). The WTRU may assume that within a control channel element within an OFDM symbol for a given PDCCH, a block of complex-valued symbols (e.g., d(0), ..., d(M)) may be used to represent the control channel elements within the OFDM symbol. symb -1)) are mapped to resource elements (kl) on antenna port (p) in increasing order of first k and then l (eg, where k is the frequency index and l is the OFDM symbol index within the subframe).

[0102] A (e.g., one) PDCCH may be transmitted using multiple beams. For example, when a control resource set (may) be defined over multiple OFDM symbols, different beams may be used over the available OFDM symbols of the control resource set. PDCCH candidates may be formed and sent over multiple OFDM symbols, for example, using different beams. The beams may, for example, be transmitted by one or more TRPs (e.g., the same TRP or multiple TRPs). Transmitting (e.g., one) PDCCH over different beams may provide beam diversity and may (e.g., greatly) reduce the probability of shadowing and beam blocking.

[0103] Figure 4is an example of four CCEs on two OFDM symbols assigned to a PDCCH candidate. The first and second OFDM symbols may be sent on two different beams. The PDCCH may be sent on multiple beams by, for example, dividing the CCEs of the PDCCH among the multiple beams. In one example (e.g., Figure 4 As shown in FIG. 1 , a PDCCH with an aggregation level (AL) of 4 may have 2 CCEs on a first OFDM symbol (e.g., transmitted on a first beam) and two CCEs on a second OFDM symbol (e.g., transmitted on a second beam). Symbols transmitted on the CCEs of the PDCCH may be, for example, repetitions of each other (e.g., the repetitions are transmitted using different precoding), or may be obtained by, for example, modulating output bits of a common forward error correction code (FEC) (the input bits of the FEC may be downlink control information (DCI)).

[0104] Figure 5 An example of distributing CCEs on multiple / different beams (e.g., on first and second OFDM symbols). In one example, a PDCCH may be sent on multiple beams by, for example, sending (e.g., each) CCE on multiple beams. In one example, a CCE of size 6 may have 3 REGs on a first symbol (e.g., sent on a first beam) and 3 REGs on a second OFDM symbol (e.g., sent on a second beam). Each of a plurality of (e.g., 2) CCEs may be composed of a bundle of multiple (e.g., 2) REGs of size 3 (e.g., sent via multiple (two) different beams). This process is very useful, for example, for adding beam diversity to frequency diversity (e.g., for the distributed PDCCH).

[0105] CCEs may be mapped for multi-beam transmission. CCEs may be mapped to PDCCH candidates, for example, by time-first mapping and / or frequency-first mapping. In the example of frequency-first mapping, consecutive CCEs in frequency (e.g., CCEs on the same OFDM symbol) may be assigned to PDCCH candidates. In the example of time-first mapping, adjacent CCEs in time may be assigned to PDCCH candidates. The remaining CCEs of the PDCCH candidate may be within another PRB, for example, when the aggregation level is greater than the time length of the control resource set.

[0106] In an example, a frequency-first CCE-to-candidate mapping may be used, such as when a set of control resources may cover one (eg, only one) OFDM symbol.

[0107] In an example, a time-first or frequency-first CCE-to-candidate mapping may be used, such as when the control resources may cover multiple OFDM symbols.

[0108] Figure 4 This is an example of time-first CCE to candidate mapping.

[0109] Figure 6 is an example of frequency-first CCE-to-candidate mapping for PDCCH. Frequency-first CCE-to-candidate mapping may be used, for example, when (eg, each) PDCCH may be transmitted on a (eg, one) beam.

[0110] Time-first and frequency-first mapping may be used, for example, to map REGs to CCEs. In an example, time-first REG-to-CCE mapping for beam-based PDCCH transmission may be very useful when, for example, (e.g., all) OFDM symbols of a control region may be associated with a (e.g., single) beam. Time-first REG-to-CCE mapping may be used (e.g., in this case). REGs on the same PRB (e.g., where the REGs are adjacent in time) may be bundled together, for example, to improve channel estimation through RS aggregation. In an example, one or more REGs may use DMRS within adjacent REGs for channel estimation. Figure 7 An example thereof is shown.

[0111] Figure 7 is an example of time-first REG-to-CCE mapping when (eg, all) OFDM symbols of the control region may be associated with one (eg, one) beam and one (eg, one) control resource set.

[0112] In an example, (eg, each) OFDM symbol may be associated with a separate beam. REGs may be mapped to CCEs, for example, by using frequency-first mapping. REG bundling may (eg, also) be performed per frequency. Figure 8 An example of distributed frequency-first mapping of REGs to CCEs is shown.

[0113] Figure 8 is an example of distributed frequency-first mapping of REGs to CCEs. In one example, the REG bundling size may be 3. The first and second OFDM symbols may be associated with multiple (eg, two) different beams.

[0114] Both per-symbol and inter-symbol interleaving can be used. Fig. 8A To use per-symbol interleaving within a multi-symbol CORESET (e.g. Fig. 8A left side) and inter-symbol interleaving (e.g. Fig. 8A An example of interleaving of frequency-first REG bundling (right).

[0115] Frequency-first REG bundling may be used within a multi-symbol CORESET. Interleaving of REG bundling within the CORESET may be accomplished in different ways. REG bundling may be interleaved individually on each symbol (e.g., Fig. 8A As shown on the left side) (e.g., interleaved by symbol). For example, lk REG bundles of a CORESET may be partitioned into l subsets corresponding to l OFDM symbols of the CORESET, each subset containing k REG bundles. The REG bundles within each subset may be interleaved by an interleaver (e.g., the interleaver has design parameters predefined by the specification or configured by RRC). Continuously interleaved REG bundles (e.g., the interleaving indices of these REG bundles are continuous) may be assigned to CCEs. Continuous CCEs may be assigned to PDCCH candidates. CCEs may be located on one OFDM symbol (e.g., corresponding to one beam). PDCCH candidates may be located on one OFDM symbol (e.g., corresponding to one beam). The design parameters of the interleaver on different symbols may be the same or different.

[0116] REG bundles may be interleaved between symbols (e.g., Fig. 8A As shown on the right hand side. In the previous case (e.g., which may be referred to as inter-symbol or inter-symbol interleaving), the lk REG bundles of the CORESET may be interleaved (e.g., with k REG bundles on each of the l symbols of the CORESET) by an interleaver (e.g., the interleaver having design parameters predefined by the specification or configured by RRC). Consecutive interleaved REG bundles (e.g., the interleaving indices of these REG bundles are consecutive) may be assigned to CCEs. Consecutive CCEs may be assigned to PDCCH candidates. CCEs may be located on multiple OFDM symbols (e.g., corresponding to multiple beams). PDCCH candidates may be located on multiple OFDM symbols (e.g., corresponding to multiple beams). This may provide multi-beam diversity for PDCCH transmission. An estimate of the content of each REG bundle may be obtained based on its corresponding beam and / or its corresponding QCL assumption (e.g., in order to achieve multi-beam diversity during PDCCH reception). Multi-beam PDCCH detection may be determined by combining the contents of soft-detected REG bundles on different beams, for example, to achieve beam diversity.

[0117] The interleaving pattern (e.g., inter-symbol or inter-symbol interleaving) may be predefined in the specification or may be included in the CORESET configuration. For example, one bit in the CORESET configuration (e.g., via RRC) may indicate whether the interleaving is by symbol or between symbols. In an example, the indication of the interleaving pattern may be mixed with other parameter configurations of the CORESET. For example, 3 bits in the CORESET configuration may indicate a selection between cases including at least the following: (i) time-first bundling without interleaving; (ii) time-first bundling with interleaving, and the REG bundling size is equal to the length of the CORESET; (iii) time-first bundling with interleaving, and the REG bundling size is equal to the size of the CCE; (iv) frequency-first bundling without interleaving; (v) frequency-first bundling with by-symbol interleaving; and / or (vi) frequency-first bundling with inter-symbol interleaving.

[0118] Symbol-by-symbol interleaving may reduce the effective search space. (E.g., each) PDCCH candidate may be located entirely on one OFDM symbol (e.g., for frequency-first REG bundling with symbol-by-symbol interleaving within a multi-symbol CORESET). The PDCCH candidates of a search space set corresponding to the WTRU (e.g., or search space set) may be divided into multiple parts (e.g., each part corresponds to one OFDM symbol of the CORESET and includes PDCCH candidates located on the corresponding OFDM symbol). The effective search space of the WTRU (e.g., the effective search space set) may be limited to one of those parts (e.g., only one of those parts). The WTRU may perform (e.g., only) blind decoding of PDCCH candidates on specific OFDM symbols within the CORESET (e.g., or a subset of OFDM symbols within the CORESET). The selection of OFDM symbols for the CORESET to limit the effective search space of the WTRU may be based on the proximity between the corresponding beam and beams used by the WTRU for other purposes (e.g., PDSCH). The WTRU may know its corresponding OFDM symbol (e.g., for a restricted effective search space) through signaling from the gNodeB (e.g., through configured explicit information from the gNodeB through the group-common PDCCH) or without additional signaling from the gNodeB. For example, the WTRU may identify its corresponding OFDM symbol (e.g., for a restricted effective search space) without signaling from the gNodeB by using information collected by the WTRU from beam tracking and / or its corresponding beam for the PDSCH.

[0119] In order for the WTRU to implicitly identify the corresponding symbol of the WTRU within the CORESET, the WTRU may compare the beam corresponding to the symbol of the CORESET with one or more beams that the WTRU tracks from an SS / PBCH block, where SS refers to synchronization signal. The WTRU may implicitly identify the corresponding symbol of its CORESET (e.g., if the beam associated with the symbol coincides with the beam or one of the beams associated with the WTRU, or if the beam associated with the symbol is closer to one or more beams associated with the WTRU within the beams associated with the CORESET).

[0120] By comparing the beam associated with each symbol of the CORESET with the WTRU-specific beam set configured by RRC or other higher layer signaling to the WTRU, the WTRU may determine the identity of the corresponding beam of the CORESET.

[0121] To compare the beam associated with the symbol of the CORESET with the beam or beam set associated with the WTRU, the WTRU may use channel estimation information from the DMRS. The criteria for comparing the beam associated with the symbol of the CORESET with the beam or beam set associated with the WTRU may be based on maximizing channel correlation.

[0122] A downlink control indicator (DCI) may be provided for multi-dimensional transmissions having a primary dimension and an auxiliary dimension. Additional transmission dimensions may be defined within NR, such as beams, beam pairing links, planes, and TRPs. In an example, a (e.g., single) NR-PDSCH may be assigned per dimension (e.g., for a multiple NR-PDSCH transmission scenario). In an example (e.g., an alternative example), a (e.g., single) NR-PDSCH may be jointly transmitted in multiple dimensions (e.g., via diversity transmission).

[0123] The NR-PDCCH may be transmitted per dimension, e.g., to send control information for transmission on that dimension. The system may (e.g., alternatively) send (e.g., one) NR-PDCCH, e.g., to enable cross-dimensional scheduling and to send cross-dimensional control information.

[0124] The WTRU may monitor the search space for a dimension (e.g., for each dimension), for example to use the NR-PDCCH per dimension.

[0125] In one example, the NR-PDCCH for a dimension (e.g., each dimension) may be assigned an independent (e.g., unlimited) search space, for example. This may increase the complexity of the blind decoding process of the WTRU and may provide greater flexibility for resource assignment.

[0126] In an example, an NR-PDCCH for a dimension (e.g., each dimension) may be assigned a restricted search space, which may depend on the search space of one or more other dimensions. The restriction may define the size of the search space (e.g., the assigned search space).

[0127] In one example, for example, when a (eg, single) NR-PDCCH may be used for cross-dimensional control channel information transmission, the WTRU may monitor the search space within (eg, one) dimension.

[0128] In one example, one (e.g., a single) dimension may be designated as the primary dimension. The NR-PDCCH may be sent in the primary dimension and resources may be assigned in (e.g., all) other (e.g., secondary) dimensions. The selection of the primary dimension may, for example, depend on the dimension that covers the most reliable dimension for the WTRU and / or the dimension that is available at a particular time.

[0129] In an example of beam-based transmission, the main beam pairing may be based on a wide beam at the TRP that may cover a narrow beam set and a corresponding receive beam at the WTRU. One or more auxiliary beams may be a narrow beam set.

[0130] Fig. 9 is an example of cross-beam scheduling. The DCI within the NR-PDCCH may include an index to a dimension (e.g., a specific dimension) of the duration that the WTRU may (e.g., should) use for the resource. In one example, the NR-PDCCH may occupy the first two symbols of the slot. The WTRU may (e.g., for the first two symbols) switch its beam to the primary beam (e.g., the NR-PDCCH beam) and (e.g., upon reading the NR-DCI) may switch its beam to the indicated or desired receive / transmit beam for the remaining symbols (e.g., the last 5 symbols) of the slot.

[0131] Fig.10 An example of a frame structure utilizing cross-beam scheduling.

[0132] In one example, the gNB and WTRU (e.g., UE) may switch (e.g., in time slot 1) to a main beam paired link (BPL), such as BPL1.

[0133] The gNB and WTRU may remain within the antenna configuration and decode the primary PDCCH (e.g., for the first N OFDM symbols), where N is configurable.

[0134] The PDCCH DCI may inform WTRU1 and WTRU2 of the resources available in the time and frequency domains.

[0135] The PDCCH DCI may inform WTRU1 and WTRU2 of the BPLs (eg, BPL2 and BPL4) that they may (eg, must) use within the resources.

[0136] The WTRU may switch to resource and antenna configurations (eg, there may be a gap period between the PDCCH and PDSCH to allow such switching).

[0137] The WTRUs may decode their PDSCH for the remaining slots.

[0138] The gNB and WTRU may switch back to the main beam paired link (e.g., BPL1) (e.g., in time slot 2).

[0139] The gNB and WTRU may remain within the antenna configuration and decode the primary PDCCH (e.g., for the first N OFDM symbols), where N is configurable and may be different from the resources used in slot 1.

[0140] The PDCCH DCI may inform WTRU1 and WTRU2 of the resources and antenna configuration that may be used in the time and frequency domains. The resources may span (eg, the entire) frequency domain. The WTRU may switch to downlink MU-MIMO mode.

[0141] The WTRU may switch resources and antenna configurations (eg, there may be a gap period between the PDCCH and PDSCH to allow such switching).

[0142] The WTRUs may decode their PDSCH for the remaining timeslots.

[0143] The PDCCH (eg, for the primary beam) may be present (eg, always). In connected mode, the secondary beam may not contain the PDCCH. The secondary beam PDCCH may be sent with different periodicities for beam management.

[0144] The main beam can be sent from the same or different TRP, plane, etc.

[0145] In an example, the (e.g., same) NR-PDCCH may be sent in one or more (e.g., all) dimensions (e.g., for redundancy purposes).

[0146] Cross-dimensional scheduling may be enabled by, for example, defining an indicator for (e.g., each) dimension, for example, so that the WTRU can identify the dimension. The dimension may be global (e.g., unique to all WTRUs) or may be WTRU-specific. This may enable the primary cell to indicate the dimension of specific control information.

[0147] A flag may be provided, for example, to inform the WTRU whether the control information is derived from the primary dimension or independently derived.

[0148] The DCI information may be constructed, for example, to enable independent DCI for (eg, each) dimension (eg, [DCIx, dimension]).

[0149] The DCI information may be constructed, for example, to enable auxiliary DCI for a subset of dimensions (eg, [DCIx, dimension 1, ..., dimension n]).

[0150] The framework (e.g., architecture, configuration, and / or process) may allow cross-beam scheduling, cross-plane scheduling, and cross-TRP scheduling.

[0151] The search space can provide multi-beam, multi-TRP transmission. The multi-TRP used here may include multi-beam (plane).

[0152] In a multi-TRP transmission system, such as Fig.12 As shown in the example, (e.g., each) TRP may transmit (e.g., different) NR-PDSCH transmissions. However, scheduling of (e.g., different) NR-PDSCHs may be accomplished via a single PDCCH (e.g., via cross-TRP scheduling). The gNB may schedule downlink transmissions via at least one TRP by transmitting the NR-PDCCH from the (e.g., primary) TRP.

[0153] The cross-TRP scheduling can be implemented by adding a TRP indicator field (TIF) to each DCI format to indicate relevant information of the NR-PDSCH transmission.

[0154] The TIP may include a bit indicating the index of the TRP to which the PDSCH scheduling corresponds. The master TRP may use a different TIF to send each of the multiple DCIs, thereby indicating multiple scheduling information corresponding to multiple NR-PDSCH payloads. The TIF may include a bit indicating the overall number of TRPs participating in the transmission. The TIF may be a single bit indicating the presence of cross-TRP scheduling.

[0155] The cross-TRP scheduling can be dynamically activated / deactivated by monitoring the presence of TIF in DCI. The gNB can independently enable or disable the cross-TRP scheduling using higher layer signaling (e.g., RRC or similar signaling).

[0156] The WTRU may dynamically determine the starting symbol of the NR-PDSCH for each TRP (e.g., based on the starting symbol field (SSF)). The WTRU may be configured with a starting symbol field for each TRP.

[0157] A TRO (eg, a primary TRP) may transmit a common search space. A TRP (eg, all configured TRPs) may transmit a WTRU-specific search space.

[0158] The WTRU may monitor the common search space on the primary TRP signal (e.g., to determine if it is configured for multiple TRP transmission, for example, in the presence of a TIF). If the WTRU determines that it is configured for multiple TRP transmission, the WTRU may monitor the WTRU-specific search space of (e.g., all) configured TRPs. For example, the WTRU may look for a DCI whose CRC is scrambled with an RNTI. The RNTI may be the C-RNTI of the primary TRP, which indicates that the WTRU context is associated with a common control DCI, or it may be a TRP-specific RNTI.

[0159] The WTRU may have one or more search spaces. The monitoring and detection process may include blind decoding. (Eg, each) WTRU-specific search space may include multiple potential PDCCH candidates, and the WTRU may monitor the multiple potential PDCCH candidates, for example, to find and detect its assigned PDCCH. (Eg, one) search space may belong to (e.g., completely belong to) a control resource set. Different search spaces within different control resource sets may be assigned to the WTRU. In one example, the total number of blind decodings of the WTRU (e.g., the total number of PDCCH candidates in the search space corresponding to the WTRU) may be limited by, for example, a fixed number, which may be independent of the number of search spaces and control resource sets. In a (e.g., alternative) example, there may be a maximum number of blind decodings for each control resource set and / or each beam (e.g., the number is fixed or configured).

[0160] Cross-plane scheduling may be provided. The NR TRP may be equipped with multiple planes. The TRP may transmit (e.g., simultaneously) multiple NR-PDSCHs to the WTRU, and it may allocate (e.g., one) NR-PDSCH for each plane. The (e.g., each) plane may have, for example, its own control resources with its own DCI that may include scheduling assignments. The TRP may send DCI for multiple planes on a (e.g., single) NR-PDCCH, for example, from a master TRP (e.g., compared to sending an NR-PDCCH for each plane).

[0161] Fig.11is an example of cross-plane scheduling in the presence of four planes. In one example, a TRP with four planes may send four NR-PDSCHs to the WTRU, where one (e.g., only one) NR-PDCCH is located on the first plane. The resource assignments for (e.g., each) NR-PDSCH may, for example, be independent. The resource assignments may be placed within the NR-PDCCH and may not overlap with each other. In one example, the WTRU may decode multiple DCIs. The (e.g., each) DCI may include different resource assignments (e.g., scheduled RBs, MCS) for the (e.g., each) NR-PDSCH.

[0162] In an example, the TRP may configure a plane indicator, e.g., to set the starting position of the search space of the (e.g., each) plane, e.g., when cross-plane scheduling may be activated. The TRP may configure the search space, e.g., so that the DCI of the (e.g., each) plane may be allocated on its own NR-PDCCH region. The WTRU may (e.g., later) decode its multi-plane resource assignment from the (e.g., single) plane.

[0163] The starting position of the CCE of the search space of (eg, each) plane may be calculated, for example, according to formula (1): Where m is the NR-PDCCH candidate index, may be the number of NR-PDCCH candidates at aggregation level L, and n PI May be a plane indicator (eg, ranging from 1 to the number of cooperating planes at the P-TRP).

[0164] In one example (e.g., an example with multiple TRPs), the planes may not be co-located (e.g., a first plane may be located at an R-TRP and a second plane may be located at an S-TRP). Collaborative TRPs may perform cross-plane scheduling in a similar manner. In one example, the NR-PDCCH of a P-TRP may be used to send DCI for an R-TRP and an S-TRP. Multiple planes may be accumulated, for example, between collaborative TRPs. The plane indicator may be, for example, the number of collaborative planes from 1 to a combination of a P-TRP and an S-TRP.

[0165] A hash function may be used to determine the search space location.

[0166] The plane indicator may be included in the DCI (e.g., when cross-plane scheduling may be valid), for example, to inform the WTRU which plane the DCI may correspond to. The TRP may, for example, signal (e.g., via higher layer signaling such as RRC) the WTRU that cross-plane scheduling may be valid. Cross-plane scheduling may be indicated to the WTRU (e.g., dynamically) by the presence of the plane indicator in the DCI.

[0167] TRP scheduling may be provided. Multiple TRPs may be coordinated (e.g., similar to multi-plane collaboration), such that (e.g., each) TRP may send its own NR-PDSCH to the WTRU. The WTRU's serving cell may be configured as a primary TRP for the WTRU. The primary TRP may perform cross-TRP scheduling, such as by sending (e.g., via, for example, a single NR-PDCCH) one or more (e.g., all) DCIs that may be directed to multiple TRPs.

[0168] Fig.12 1 is an example of cross-TRP scheduling with two TRPs. In one example, the two TRPs may collaborate. The P-TRP may operate as a serving cell for the WTRU. In one example, (e.g., each) TRP may send its own NR-PDSCH, and (e.g., only) the P-TRP may send NR-PDCCH. The P-TRP may (e.g., may also) use cross-TRP scheduling, e.g., for decoupled downlink / uplink (e.g., such as Fig.13 shown).

[0169] Fig.13 An example of cross-TRP scheduling with decoupled downlink / uplink. In one example, the WTRU may receive NR-PDSCH on the downlink from (e.g., one) cell. The WTRU may send its NR-PUSCH on the uplink, for example, to a second TRP. Multiple (e.g., two) TRPs may collaborate. The P-TRP serving the WTRU on the downlink may send DCI to the WTRU, which may be for its own link as well as for the link of the S-TRP. The DCI may be used on the uplink to the second TRP, for example, for scheduling assignments and / or for power control commands.

[0170] In an (e.g., alternative) example, for example, when cross-TRP scheduling may be valid, the TRP may configure the TRP indicator to set the starting position of the search space for the DCI of (e.g., each) TRP. The TRP may configure the search space, for example, so that the DCI of (e.g., each) TRP may be allocated at its own position in the NR-PDCCH. The WTRU may (e.g., later) decode its multiple TRP resource assignments from the (e.g., single) plane.

[0171] The starting position of the CCE of the search space for (eg, each) plane may be calculated, for example, according to formula (2): Where m is the NR-PDCCH candidate index, may be the number of NR-PDCCH candidates at aggregation level L, and n TI Can be a TRP indicator ranging from 1 to the number of cooperating TRPs.

[0172] A TRP indicator may be included in the DCI (eg, when cross-TRP scheduling may be valid), for example, to inform the WTRU which TRP the DCI may correspond to. The TRP may be signaled (eg, via higher layer signaling such as RRC) to inform the WTRU that cross-TRP scheduling may be valid.

[0173] Cross-TRP scheduling may be indicated to the WTRU (e.g., dynamically) by the presence of a TRP indicator within the DCI. Multi-layer transmissions from multiple TRPs and multiple PDSCH transmissions may be used. Data may be transmitted to the WTRU from multiple TRPs by, for example, transmitting multiple PDSCHs, each from (e.g., one) TRP and scheduled by its corresponding PDCCH, or by transmitting one PDSCH, e.g., scheduled by (e.g., one) PDCCH using layers (e.g., different layers) from different TRPs.

[0174] Corresponding layers from different TRPs may be located on the same or different time and frequency resources for a PDSCH (e.g., a single PDSCH comprising multiple layers transmitted from multiple TRPs). By using spatial division multiple access or simple successive interference cancellation (SIC), the layers may be transmitted on the same time and frequency resources (e.g., if they are multiplexed via power level NOMA). For SIC, reception operations may be coherent or non-coherent (e.g., no synchronization is required).

[0175]

[00136] A PDCCH may be provided for URLLC in a beam-based system. A monitoring time interval may be established in a beam-based system, for example, for URLLC transmissions. The gNB may switch to a beam that may have coverage for a subset (e.g., a large subset) of URLLC WTRUs. The URLLC WTRU and the gNB may negotiate a receive beam (e.g., a best receive beam) for a transmit beam. The gNB may transmit a URLLC control channel (e.g., during a time interval).

[0176] The PDCCH for URLLC WTRUs may be restricted to, for example, (e.g., one) OFDM symbol. The frequency may be restricted. One or more restrictions may, for example, reduce overhead.

[0177] Disclosed herein are systems, methods, and tools for beam-based PSCCH transmission within NR. A control resource set may be assigned for multi-beam control transmission. PDCCH may be transmitted using multiple beams. CCE may be mapped for multi-beam transmission. DCI may support multi-dimensional transmission with primary and secondary dimensions. Search space may support multi-beam, multi-TRP transmission.

[0178] Features, elements, and actions (e.g., processes and tools) are described herein in a non-limiting manner. Although examples may be for LTE, LTE-A, New Radio (NR), or 5G protocols, the subject matter herein may be applicable to other wireless communications, systems, services, and protocols. Each feature, element, action, or other aspect of the subject matter described herein (whether in the drawings or in the specification) may be implemented alone or in any combination, including in any order in combination with other subjects (whether known or unknown), without regard to the examples given herein.

[0179] The WTRU may refer to the identity of a physical device, or an identity of a user, such as a subscription-related identity, such as an MSISDN, SIP URI, etc. The WTRU may refer to an application-based identifier, such as a username that may be used for an application.

[0180] Each computing system described herein may have one or more computer processors with memory, the computer processors being configured with executable instructions or hardware to perform the functions described herein (including determining the parameters described herein) and to send and receive messages between entities (e.g., WTRU and network) to perform the functions described herein. The above processes may be implemented in a computer program, software and / or firmware, which may be embodied in a computer-readable medium for execution by a computer and / or processor.

[0181] The processes described herein may be implemented using a computer program, software, and / or firmware, which may be incorporated into a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or 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, buffer memory, semiconductor memory devices, magnetic media (e.g., but not limited to, internal hard disks and removable disks), magneto-optical media, and / or optical media (e.g., but not limited to CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software is used to implement a radio frequency transceiver used in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

1. A wireless transmit / receive unit WTRU, the WTRU comprising: A processor, wherein the processor is configured to: Receiving a first orthogonal frequency division multiplexing (OFDM) symbol via a first beam; receiving a second OFDM symbol via a second beam; determining a resource element group (REG) bundling using the first OFDM symbol and the second OFDM symbol; and The REG bundling is used to determine Physical Downlink Control Channel (PDCCH) transmission.

2. The WTRU of claim 1 , wherein the PDCCH transmission is a first PDCCH transmission, and wherein the processor is further configured to determine a second PDCCH transmission.

3. The WTRU of claim 1 , wherein the REG bundles are bundled by frequency, and wherein the processor is further configured to determine the frequency.

4. The WTRU of claim 1 , wherein the processor is further configured to determine quasi-co-located QCL information for the REG bundling.

5. The WTRU of claim 4, wherein the processor is configured to determine the PDCCH transmission using the REG bundling and the QCL information.

6. A method performed by a wireless transmit / receive unit WTRU, the method comprising: Receiving a first orthogonal frequency division multiplexing (OFDM) symbol via a first beam; receiving a second OFDM symbol via a second beam; determining a resource element group (REG) bundling using the first OFDM symbol and the second OFDM symbol; and The REG bundling is used to determine Physical Downlink Control Channel (PDCCH) transmission.

7. The method of claim 6, wherein the PDCCH transmission is a first PDCCH transmission, and wherein the method further comprises determining a second PDCCH transmission.

8. The method of claim 6, wherein the REG bundles are bundled by frequency, and wherein the method further comprises determining the frequency.

9. The method of claim 6, wherein the method further comprises determining quasi-co-located QCL information for the REG bundling.

10. The method of claim 9, wherein the method further comprises determining the PDCCH transmission using the REG bundling and the QCL information.

11. A wireless transmit / receive unit WTRU, the WTRU comprising: A processor, wherein the processor is configured to: determining that the WTRU is configured to receive interleaved transmissions; receiving a first beam and a second beam; as well as Transmission of the interlace is determined using the first beam and the second beam.

Images