Method, apparatus, and system for reduced bandwidth for reduced capability wtru

Abstract

To provide a method, an apparatus, a system, an architecture, and an interface for receiving system information implemented by a wireless transmit receive unit (WTRU) having reduced capabilities.SOLUTION: A method for a WTRU to receive system information includes receiving a physical broadcast channel (PBCH) transmission including a master information block (MIB), receiving a SIB on the basis of receiving a first PDCCH transmission, determining a bandwidth portion (BWP) associated with a reduced capability WTRU on the basis of the SIB, determining a second CORESET#0 on the basis of the SIB, and receiving a second PDCCH transmission in the determined BWP associated with the reduced capability WTRU using the second CORESET#0, provided that the WTRU is a reduced capability WTRU.SELECTED DRAWING: Figure 12

Description

[Background technology]

[0001] The present invention relates to the field of computing and communications, and more particularly to methods, apparatus, systems, architectures, and interfaces for computing and communications in advanced or next generation wireless communication systems, including communications performed using new radio and / or new radio (NR) access technologies and communications systems. Such NR access and technologies, which may be referred to as 5G, and / or other similar wireless communication systems and technologies, may include features and / or techniques for cell search, NR PDCCH and search space, and / or system information (SI). For a cell search procedure, a WTRU acquires time and frequency synchronization with a cell and detects the physical layer cell ID of the cell using a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The WTRU is assigned a set of PDCCH candidates to monitor during blind detection of the PDCCH, for example. The search space or set of search spaces may include a set of PDCCH candidates. Furthermore, the system information (SI) is divided into blocks, for example, master, system, and positioning information. [Brief description of the drawings]

[0002] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numbers indicate similar elements and in which: [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B]1 is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Figure 1C] FIG. 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Diagram 2] A diagram illustrating a 'synchronization signal / physical broadcast channel (SS / PBCH) block structure. [Diagram 3] FIG. 1 illustrates an SSB and / or RMSI CORESET and RMSI PDSCH multiplexing pattern. [Figure 4] FIG. 13 illustrates a second pattern multiplexing technique. [Diagram 5] FIG. 13 illustrates a third pattern multiplexing technique. [Figure 6] FIG. 13 illustrates multiplexing of RC-CORESET0 and RMSI PDSCH according to an embodiment. [Figure 7] FIG. 13 illustrates another multiplexing of RC-CORESET0 and RMSI PDSCH according to an embodiment. [Figure 8] 1 is a diagram illustrating PDCCH monitoring on two OFDM symbols according to an embodiment. [Figure 9] FIG. 1 illustrates a CORESET and SSB on the same OFDM symbol according to an embodiment. [Figure 10] FIG. 1 illustrates REG repetition according to an embodiment. [Figure 11]FIG. 13 illustrates another iteration of REG, according to an embodiment. [Figure 12] 1 illustrates a method, procedure, operation, etc., performed by, for example, a WTRU with reduced capabilities, for receiving system information, according to an embodiment.

[0003] Exemplary Network for Implementing the Embodiments 1A is a diagram illustrating an example 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, broadcasts, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), etc.

[0004] 1A, communications 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 will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0005] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a 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, etc. Although the base stations 114a, 114b are each depicted as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

[0008] More specifically, as noted above, the communications system 100 may be a multiple access system and may use one or more channel access schemes, such as, for example, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a and the WTRUs 102a, 102b, 102c in the RAN 104 / 113 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communications 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 Packet Access (HSUPA).

[0009] 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 LTE-Advanced (LTE-Advanced, LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0010] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology, such as New Radio (NR) radio access, which may establish the air interface 116 using NR technology. 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 implement LTE radio access and NR radio access together, for example, using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

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

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

[0013] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as, for example, different throughput requirements, latency requirements, error 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 perform high-level security functions such as user authentication. 1A, it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate, directly or indirectly, with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0014] 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 public switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

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

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

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

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

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

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

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

[0022] The processor 118 may receive power from the power source 134, but 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 providing power to the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

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

[0024] The processor 118 may further 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 videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

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

[0027] The RAN 104 may include eNodeBs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with an embodiment. The eNodeBs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, the eNodeB 160a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0028] 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, scheduling of users in the UL and / or DL, etc. As shown in FIG 1C, the eNodeBs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0029] 1C 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 elements is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[0031] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNodeB handover, 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.

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

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

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

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

[0036] A WLAN in infrastructure Basic Service Set (BSS) mode may have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS to the STAs may arrive through the AP and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within the BSS may be transmitted, for example, through the AP, where the source STA may transmit traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be viewed and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) in a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" communication mode.

[0037] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) with collision avoidance may be implemented. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0038] A High Throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0039] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz wide channel may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed and the combined data may be sent to the Medium Access Control (MAC).

[0040] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices may have specific capabilities, including, for example, support for (e.g., support only for) specific and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0041] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be configured and / or limited by the STAs among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. For example, if the primary channel is busy due to STAs (that only support the 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band may remain idle and available for use.

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

[0043] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As mentioned above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 113 may also communicate with the CN 115.

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

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

[0046] 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 another RAN (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNodeB 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, while the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

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

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

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

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

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

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

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

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

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

[0056] Synchronization FIG. 2 is a diagram illustrating a synchronization signal / physical broadcast channel (SS / PBCH) block structure.

[0057] Cell search is a procedure performed by a WTRU, for example, to acquire time and frequency synchronization with a cell and to detect the physical layer cell ID of the cell. To acquire time and frequency synchronization, the signals used for synchronization, i.e., synchronization signals (SS), include a primary SS (PSS) and a secondary SS (SSS). With reference to FIG. 2, the physical broadcast channel (PBCH), the PSS, and the SSS are transmitted, for example, in four consecutive symbols to form an SS / PBCH block, which may be referred to as a synchronization signal block (SSB). Upon detecting the SS / PBCH block, the WTRU determines (e.g., detects, acquires, extracts, reads, etc.) a master information block (MIB) from the PBCH. From the MIB (e.g., using the MIB, based on the MIB, etc.), the WTRU determines whether there is a control resource set (CORESET) for a Type 0-PDCCH common search space (CSS), which may be referred to as CORESET0 (e.g., the WTRU determines whether CORESET0 exists and / or is included in the MIB). The Type 0-PDCCH may include a PDCCH for the remaining master system information (RMSI), which may be referred to as system information block (SIB) 1 (SIB1).

[0058] Synchronization signal bursts (SS bursts) may be used when using multiple beams for initial access. SS bursts may be transmitted periodically (e.g., every 20 ms), and each SS burst may include any number (e.g., one or more) of SS / PBCH blocks. One or more (e.g., any number) SSBs in an SS burst may be associated with one or more (e.g., any number) of beams. The number of SSBs in an SS burst may be determined by the gNB, for example, based on the number of beams used at the gNB. For example, N B If N beams are used in a base station (e.g., a gNB), B The SS / PBCH blocks may be used and / or transmitted in (eg, via) an SS burst.

[0059] NR PDCCH and search space A Resource Element Group (REG) may be (e.g., may be considered as) the smallest building block of a physical downlink control channel (PDCCH). (E.g., each) REG may consist of 12 resource elements (RE) over one OFDM symbol in time and one resource block (RB) in frequency. In (e.g., each) REG, 9 REs may be used for control information and 3 REs may be used for demodulation reference signals (DMRSs). Multiple REGs (e.g., 2, 3, or 6) that are adjacent in time and / or frequency may form a REG bundle. The REG bundle may use the same precoder (e.g., for each RE), and the associated DMRSs may be used together for channel estimation. Six REGs (e.g., in the format of 1, 2, or 3 REG bundles) may form one Control Channel Element (CCE), which may be the smallest possible PDCCH. (e.g., each) PDCCH may consist of any number (e.g., one or more) of CCEs (e.g., 1, 2, 4, 8, or 16 CCEs). The number of CCEs for a PDCCH may be referred to (e.g., called its AL) as an aggregation level (AL).

[0060] The mapping of REG bundles may use (e.g., may be for) interleaving or non-interleaving. In non-interleaving mapping, consecutive (e.g., adjacent in frequency) REG bundles may form CCEs, and adjacent CCEs in frequency may form PDCCHs. In interleaving mapping, REGs may be interleaved (or permuted) before being mapped to CCEs, resulting in (e.g., generally) non-adjacent REG bundles in one CCE and non-adjacent CCEs in one PDCCH. A control resource set (CORESET) may include (e.g., CORESET may include / comprise at least one of) and / or be associated with (e.g., may be configured by) any of (1) frequency allocation (e.g., as a chunk of 6 RBs), (2) length of time (e.g., 1-3 OFDM symbols), (3) type of REG bundle, and (4) type of mapping from REG bundles to CCEs (e.g., interleaving or non-interleaving mapping). There may be up to N (e.g., 3) CORESETS in (e.g., each) bandwidth part (BWP). For example, there may be 12 CORESETS in 4 (e.g., possible) bandwidth parts.

[0061] A WTRU may monitor or be assigned a set of PDCCH candidates (e.g., to monitor). For example, the set of PDCCH candidates may be monitored during blind detection of the PDCCH. A search space or set of search spaces (e.g., for multiple ALs) may be (e.g., may include) a set of PDCCH candidates for the WTRU to monitor using (e.g., along with) blind detection. A search space or set of search spaces (e.g., each of them) may be configured by any (e.g., at least one) of (1) an associated CORESET, (2) a number of candidates for or within each aggregation level, and (3) a set of monitoring opportunities. The monitoring opportunities may be determined by any of a monitoring periodicity (e.g., with respect to a slot), a monitoring offset, and a monitoring pattern (e.g., having 14 bits corresponding to possible patterns of symbols in a slot).

[0062] System Information The system information (SI) may include (e.g., may be divided into) an MIB, any number of system information blocks (SIBs), and a positioning SIB (posSIB). The MIB includes parameters required to acquire the first SIB (SIB1) from a cell. The contents of the MIB in New Radio (NR) Release-16 are shown below.

[0063] [Table 1]

[0064] SIB1 is transmitted on a downlink shared channel (DL-SCH). If the WTRU determines during cell search (e.g., from the MIB) that a CORESET exists for the Type-0-PDCCH CSS set, the WTRU (1) determines the number of contiguous resource blocks and the number of contiguous symbols for the CORESET of the Type-0-PDCCH CSS set from controlResourceSetZero in pdcch-ConfigSIB1 in the MIB, and (2) determines the PDCCH monitoring opportunity from searchSpaceZero in pdcch-ConfigSIB1.

[0065] FIG. 3 is a diagram illustrating an SSB and / or RMSI CORESET and RMSI PDSCH multiplexing pattern, while FIGS. 4 and 5 are diagrams illustrating multiplexing techniques for a second and third pattern, respectively.

[0066] The SSBs and corresponding CORESET0 may be multiplexed in three possible patterns, for example, as shown in Figure 3. With reference to Figure 3, the patterns shown are for illustration purposes (e.g., only) and the (e.g., exact) multiplexing pattern may be any suitable pattern and may depend, for example, on subcarrier spacing (SCS), carrier frequency, etc. If the WTRU is not provided with an initial downlink bandwidth portion (BWP) (e.g., parameter initialDownlinkBWP), CORESET0 may indicate (e.g., may also define) the initial downlink BWP.

[0067] For example, referring to Fig. 4 and Fig. 5, respectively, there may be multiplexing techniques for patterns such as pattern 2 and pattern 3. In Fig. 4 and Fig. 5, the SSB and RMSI PDCCH / PDSCH shown in the same pattern are related to each other. For example, Fig. 4 shows a sample multiplexing pattern for time multiplexing of SS / PBCH blocks and associated CORESET0 and PDSCH when the SCS of SSB is 120 kHz and the SCS of CORESET0 / PDSCH is 60 kHz. Referring to Fig. 4, the OFDM symbols of associated SSB / CORESET0 / PDSCH are shown in the same pattern. As an example, SSB is transmitted in OFDM symbol 4 to OFDM symbol 7, the corresponding CORESET0 is transmitted in OFDM symbol 0 in the same slot, and the associated PDSCH is transmitted in OFDM symbols 2 and 3. In the case of Figure 4, the CORESET0 / PDSCH OFDM symbol is twice as long as the SSB OFDM symbol because the subcarrier spacing used for SSB and CORESET0 / PDSCH is different. With reference to Figure 5, there may be (e.g., different) patterns for different sets of SCSs.

[0068] There may be cases of WTRUs with reduced capabilities, which may be referred to as reduced capability (i.e., RedCAP or RC) WTRUs. For RC WTRUs, the maximum transmission bandwidth of the RC WTRU may be smaller than the bandwidth (BW) used in the system. In such cases, for example, in some configurations, the RC WTRU may not be able to receive all of the bandwidth allocated to SSB and CORESET0 in the initial downlink BWP. For example, there may be (e.g., agreed upon) a maximum RC WTRU BW of 100 MHz (e.g., in NR Rel-17). However, in certain configurations and / or cases, the total BW allocated to SSB and associated CORESET0 may exceed 120 MHz. Furthermore, in the above cases or other cases, the number of RC WTRUs in the system may be much larger than the number of regular (e.g., non-reduced capability) WTRUs. In such cases, resource fragmentation between RC WTRUs and regular WTRUs in the initial BWP may adversely affect the performance of regular WTRUs. That is, delays may be observed, for example, during random access procedures.

[0069] RC WTRU in Coverage Enhancement (CE) mode According to an embodiment, the WTRU may have reduced capabilities, in other words, the WTRU may be a RC WTRU. For example, according to an embodiment, the maximum bandwidth supported by the RC WTRU may be less than the bandwidth available in (e.g., supported by) the system (e.g., network). As another example, according to an embodiment, the bandwidth supported by the RC WTRU may be less than the bandwidth used by an aspect of the system. According to an embodiment, the aspect of the system may include any of the following: a BWP, such as a DL BWP or a UL BWP, an initial BWP, a default BWP, a number of RBs required (e.g., associated with) and / or used for CORESET, CORESET0, e.g., a number of RBs required (e.g., associated with) and / or used for (e.g., associated with) or used by a non-reduced capability WTRU.

[0070] According to an embodiment, a RC WTRU may be in a coverage extension (CE) mode, which may refer to a WTRU that supports a transmission scheme for extending coverage. A WTRU may be either (e.g., both) of a RC WTRU and a coverage extension WTRU. According to an embodiment (e.g., without loss of generality), a WTRU may be referred to as either a RC WTRU and an RC / CE WTRU. A non-RC / CE WTRU, or in other words a non-reduced capability / non-coverage extension WTRU, may be referred to as a normal (e.g., or ordinary, conventional, etc.) WTRU. According to an embodiment, any system aspect and / or characteristics of the system aspect (e.g., number of RBs, RB location, time location, RB pattern, time pattern, SCS, among others) may be indicated in the MIB.

[0071] According to an embodiment, a CORESET, such as any of CORESET0, a CORESET of Type 0-PDCCH CSS, and a CORESET of Search Space Zero (SS0), may be different for (e.g., different between) RC / CE WTRUs and / or other types of WTRUs (e.g., non-RC / CE WTRUs). According to an embodiment, a first CORESET0, a first SS0, and any of the first Type 0-PDCCH CSS may be for (e.g., intended for) and / or used by a first set of WTRUs (e.g., a set of one or more non-RC / CE WTRUs), and a second CORESET0, a second SS0, and any of the second Type 0-PDCCH CSS may be for (e.g., intended for) and / or used by a second set of WTRUs (e.g., a set of one or more RC / CE WTRUs). The terms RC-CORESET0, RC-SS0, and RC-Type 0-PDCCH CSS referred to herein may be used for the second CORESET0, second SS0, and second Type 0-PDCCH CSS, respectively. However, the present disclosures and / or embodiments are not limited to such terminology and any suitable names and / or terms may be used and / or referred to herein, including the names of the first CORESET0, SS0, and Type 0-PDCCH CSS, and still be consistent with the embodiments and examples described herein. The terms CORESET#0 and initial BWP referred to herein may be used interchangeably.

[0072] An indication to the WTRU to offload to another initial BWP (CORESET#0) According to an embodiment, the RC WTRU may be an RC-UE and may be provided with parameters (e.g., signaled, informed, indicated, notified, etc.). For example, according to an embodiment, the PBCH / MIB may be used, for example, to provide the RC WTRU with (e.g., some) parameters of the RC-Type 0-PDCCH CSS, e.g., monitoring occasions, and parameters of RC-CORESET0, e.g., number of RBs in RC-CORESET0, frequency location of RC-CORESET0, number of symbols in RC-CORESET, etc. According to an embodiment, the WTRU may either (1) detect the first SS / PBCH block, (2) receive and / or decode the associated PBCH / MIB in the SSB, and (3) calculate a kSSB(ssb-SubcarrierOffset) value from the ssb-SubcarrierOffset bits in the MIB and / or PBCH payload.

[0073] According to an embodiment, if the kSSB value is within a (e.g., specific) range (e.g., kSSB>23 for FR1 and kSSB>11 for FR2), such may indicate, for example, to a normal WTRU, that a CORESET does not exist for a Type 0-PDCCH-CSS set associated with the SS / PBCH block. According to an embodiment, the kSSB (e.g., the same kSSB) value may indicate (e.g., the same) (for example, to a normal WTRU) a channel number of a second SS / PBCH block that has a CORESET for the associated Type 0-PDCCH-CSS. According to an embodiment, the kSSB (e.g., the same kSSB) value may indicate, for example, to an RC-WTRU, that an RC-CORESET exists for the associated RC-Type 0-PDCCH-CSS. According to an embodiment, in the case of the same kSSB value, the RC-WTRU may determine that an RC-CORESET exists for the associated RC-Type 0-PDCCH-CSS. In such a case, according to an embodiment, the RC-WTRU may determine the monitoring occasions of the RC-Type0-PDCCH-CSS and / or the associated RC-CORESET0, and other parameters, from the pdcch-ConfigSIB1 bit in the MIB. According to an embodiment, the kSSB value may be interpreted differently by different WTRUs, for example, according to the WTRU type, which may include and / or be associated with any of the following: WTRU capabilities, WTRU category, maximum supportable bandwidth, number of (e.g., receive) antennas, etc.

[0074] According to an embodiment, at least one bit (e.g., any number of bits) in either the MIB and / or the PBCH payload may indicate, for example, to an RC WTRU that an RC-CORESET is present for an associated RC-Type 0-PDCCH-CSS. For example, according to an embodiment, a (e.g., one) bit in the MIB may indicate (e.g., used to indicate) (e.g., to an RC WTRU) that an RC-Type 0-PDCC-CSS is either present or absent, e.g., by setting the bit to 1 or 0, respectively. Using this bit, the RC-WTRU may determine the presence or absence of an RC-CORESET. According to an embodiment, any number of (e.g., bits) indicators (e.g., in the MIB) may be used simultaneously, and any number of such indicators may be intended for and / or used by any number of different (e.g., types) WTRUs, e.g., RC-WTRUs and non-RC WTRUs.

[0075] According to an embodiment, there may be cases where (1) the kSSB value may be for (e.g., targeted to) and / or used by a normal WTRU, e.g., to determine the presence (or absence) of CORESET0, and (2) a one-bit indicator in the MIB or PBCH may be for (e.g., targeted to) and / or used by the RC-WTRU, e.g., to determine the presence (or absence) of RC-CORESET0. According to an embodiment, there may be cases where the RC-WTRU determines that RC-CORESET0 is present, e.g., from a bit in the MIB / PBCH. In such cases, (1) the kSSB value may be determined to be invalid by the RC-WTRU, e.g., according to a subcarrier offset determined by setting ssb-SubcarrierOffset to a default value such as 0, or (2) the kSSB value may be used to determine a subcarrier offset (e.g., only), and / or the kSSB value may not be used to determine the presence or absence of RC-CORESET0.

[0076] According to an embodiment, there may be, for example, a scenario as described below. In such a scenario, kSSB may be determined by either (e.g., both) of the RC-WTRU and the normal WTRU to be (a) 24≦kSSB≦29 for FR1 or (b) 12≦kSSB≦13 for FR2. According to an embodiment, in such a scenario, the normal WTRU may determine that CORESET0 is not present. Furthermore, in such a scenario, the RC-WTRU may determine whether RC-CORESET0 is present, for example, from a bit in the MIB. If RC-CORESET0 is present, the RC-WTRU may determine search space parameters, for example, according to (e.g., based on, from, etc.) pdcch-ConfigSIB1. According to an embodiment, if there is no such bit in the MIB, the RC-WTRU may determine (e.g., assume by default) that RC-CORESET0 is present, and the RC-WTRU may monitor the PDCCH according to (e.g., using) the search space parameters determined, for example, according to pddch-ConfigSIB1.

[0077] According to some embodiments, according to (e.g., based on, from, etc.) the same set of bits in the MIB (e.g., pdcch-ConfigSIB1 field), either (e.g., both) of the regular WTRU and the RC WTRU may determine any of Type0-PDCCH-CSS, CORESET0, RC-Type0-PDCCH-CSS, and RC-CORESET0. According to embodiments, any of the CORESET0 and SS0 parameters, such as, for example, the SSB / CORESET0 multiplexing pattern, the set of RBs and slot symbols of CORESET0, the PDCCH monitoring opportunities for SS0, etc., may be determined by the regular WTRU. For example, according to embodiments, a WTRU, such as a regular WTRU, may associate (e.g., map, perform a mapping of, etc.) controlResourceSetZero in pdcch-ConfigSIB1 and searchSpaceZero in pdcch-ConfigSIB1 with (e.g., corresponding, map, etc.) entries in a table, for example, for a given subcarrier spacing of SSB and PDCCH. According to an embodiment, the RC WTRU may determine the location of RC-CORESET0 in frequency, for example, by applying an offset (e.g., in terms of RBs and / or subcarriers) to any of the first RB and / or first subcarrier of CORESET0. According to an embodiment, the bandwidth of RC-CORESET0 may be less than the size of CORESET0.

[0078] According to an embodiment, the kSSB value may indicate the presence of a CORESET0 associated with an SSB. According to an embodiment, the RC WTRU may determine not to monitor the Type 0-PDCCH-CSS, for example, if any of the following conditions (e.g., first to eleventh) are met: According to an embodiment, the first condition may be that the BW of the indicated CORESET0 is above a threshold (e.g., or is greater than a predefined value). For example, the condition may be that the BW of CORESET0 is greater than 50 MHz. According to an embodiment, the second condition may be that the total BW including (e.g., the sum of) the BW of the indicated CORESET0 and the BW of the SSB is above a threshold. For example, the condition may be that the total BW is greater than 100 MHz.

[0079] According to an embodiment, the third condition may be that the total BW (e.g., the BW of the indicated CORESET0 combined with the BW of the SSB) minus (e.g., the BW where CORESET0 and SSB overlap) exceeds a threshold. According to an embodiment, the fourth condition may be that the BW from the first subcarrier of CORESET0 to the last subcarrier of SSB exceeds a threshold. In such a case, the first subcarrier of CORESET0 may be determined as the subcarrier on a common grid that overlaps with subcarrier 0 of CORESET0, and the last subcarrier of SSB may be determined as the subcarrier on a common grid that overlaps with the last subcarrier of SSB. According to an embodiment, the fifth condition may be that the BW from the first subcarrier of SSB to the last subcarrier of CORESET0 exceeds a threshold. In such a case, the first and last subcarriers may be determined from the subcarriers in the common grid that overlap with the first subcarrier of SSB and the last subcarrier of CORESET0.

[0080] According to an embodiment, the sixth condition may be that the (e.g., SSB / CORESET0) multiplexing pattern is a particular pattern, such as, for example, Pattern 2 or Pattern 3, as discussed above. According to an embodiment, the seventh condition may be associated with a time multiplexing technique of CORESET0 and SSB. For example, the condition may be that CORESET0 and SSB are transmitted in the same OFDM symbol. According to an embodiment, the eighth condition may be associated with a threshold (e.g., may be used in any of the conditions discussed herein) determined according to (e.g., based on, from, etc.) the maximum WTRU BW, such as, for example, a threshold that is (e.g., equal to) the sum of the maximum WTRU BW and a margin.

[0081] According to an embodiment, the ninth condition may be that the SCS and PDCCH of the SSB belong to a predefined set, e.g., 120 kHz-120 kHz, 240 kHz-120 kHz, etc. According to an embodiment, the tenth condition may be that the frequency band is one of a predefined set of bands, e.g., FR2. According to an embodiment, the eleventh condition may be that the RC-WTRU does not receive (e.g., is unable to receive) a PDCCH in CORESET0 within a (e.g., some, given, etc.) time window. For example, the condition may be that the RC-WTRU does not receive and / or successfully decode (e.g., may not, is unable, etc.) a PDCCH in k frames. According to an embodiment, the time window may be determined according to (e.g., with respect to) any of a frame, a slot, a symbol, and a combination of the like.

[0082] According to an embodiment, if the RC WTRU determines that it does not or does not even monitor Type 0-PDCCH-CSS, the RC WTRU may be provided (e.g., signaled, informed, indicated, configured with) at least one channel to monitor (e.g., the RC WTRU may monitor) either Type 0-PDCCH-CSS or RC-Type 0-PDCCH-CSS. According to an embodiment, the kSSB value may be interpreted (e.g., used) by the WTRU to determine, for example, a global synchronization channel number (GSCN) as GCSN_SSB summed with GCSN_offset to find (e.g., determine) the second SS / PBCH block. For example, according to an embodiment, the RC WTRU may determine any number of GCSN_offset values ​​according to (e.g., based on, from, etc.) kSSB, for example, if kSSB≦23 for FR1 and kSSB≦11 for FR2. According to an embodiment, the RC-WTRU may search a (eg, another) channel to find the second SS / PBCH block without being provided with information indicating such a search.

[0083] According to an embodiment, the RC WTRU may be provided with information indicating whether to monitor a type 0-PDCCH-CSS and / or whether to use CORESET0, e.g., using explicit signaling. According to an embodiment, the RC WTRU may determine whether to monitor a PDCCH or to search for another SSB in another channel, e.g., from at least one bit in the MIB and / or PBCH payload. According to an embodiment, the RC WTRU may receive a configuration in SIB1 of an initial BWP other than the one (e.g., BWP) that (e.g., previously) SIB1 was (e.g., previously) received. According to an embodiment, the RC WTRU may determine to move to the indicated initial BWP according to either an explicit signal or an implicit signal. According to an embodiment, the explicit signal may be provided as either an indication in SIB1 or a paging message. According to an embodiment, in case of implicit signaling, the RC WTRU may determine to camp on the indicated BWP if a random access attempt in the current initial BWP is not successful, e.g., within a predefined and / or signaled (e.g., configured) time window. For example, such a time window may be the time it takes for the RC WTRU to successfully complete a random access in the current initial BWP that is equal to or greater than a minimum time threshold.

[0084] Multiplexing of RC-CORESET0 and RMSI PDCCH / PDSCH According to an embodiment, RC-CORESET0 may be multiplexed (e.g., using either time and / or frequency multiplexing) with any of CORESET0 and / or RMSI PDSCH, for example, according to a (e.g., predefined) pattern. According to an embodiment, in the case of time multiplexing, the RC WTRU may monitor the RC-PDCCH in the same slots as monitored by the normal WTRU, but in different frames and / or half-frames than those monitored by the normal WTRU (e.g., every N frames, such that (SFN) mod N=0). According to an embodiment, the RC WTRU may assume (e.g., operate as if) the monitored half-frame does not include an SSB. For example, the RC WTRU may receive an SSB in half-frame 0 (e.g., or half-frame 1) and monitor the associated RC-PDCCH in half-frame 1 (e.g., or half-frame 0). According to an embodiment, the (e.g., other) parameters of the RC-PDCCH (e.g., CORESET size, frequency location, etc.) may be determined in accordance with (e.g., based on, from, etc.) the MIB, for example, in a manner similar to that of a normal (e.g., NR) WTRU.

[0085] Fig. 6 is a diagram illustrating multiplexing of RC-CORESET0 and RMSI PDSCH according to an embodiment. Fig. 7 is a diagram illustrating another multiplexing of RC-CORESET0 and RMSI PDSCH according to an embodiment.

[0086] According to an embodiment, RC-CORESET0 may be multiplexed with RMSI PDSCH in either the frequency and / or time domain. According to an embodiment, RC-CORESET0 may be transmitted over (e.g., in a portion of) resources of an OFDM symbol that may have (e.g., may carry, may include, may possibly be scheduled with, etc.) an RMSI PDSCH. According to an embodiment, an RC WTRU may monitor RC-Type 0-PDCCH-CSS in at least one of the OFDM symbols that may have an RMSI PDSCH. According to an embodiment, a WTRU, such as an RC WTRU, may determine a BW of an associated CORESET0 in which to monitor control information, which may be considered, for example, as a control channel (e.g., PDCCH) for RMSI. That is, for example, according to an embodiment, the BW of the associated CORESET0 in which to monitor the RMSI (e.g., control information / channel including the RMSI) may be predefined (e.g., configured) such that the total BW for receiving (e.g., required to receive) both the SSB and CORESET0 is less than the maximum WTRU bandwidth (e.g., the maximum BW of the RC WTRU).

[0087] According to an embodiment, for example in the case of FIG. 6 where the y-axis represents the frequency domain, RC-CORESET0 may be (e.g., may be present, may be included, may be carried, etc.) within / on an OFDM symbol where an RMSI PDSCH may be scheduled. According to an embodiment, RC-CORESET0 may be present on two OFDM symbols, for example with reference to FIG. 6, or may be present on one OFDM symbol, for example with reference to FIG. 7. According to an embodiment, a DCI format transmitted within / on a PDCCH on RC-CORESET0 (e.g., via, using, etc.) may be a compact DCI having fewer (e.g., a smaller number of) bits than an RMSI PDCCH, for example, and may indicate to the RC WTRU the frequency location of CORESET0 that the RC WTRU may attempt to receive. According to an embodiment, a dedicated RNTI may be used by the RC WTRU, for example, to receive a specific (e.g., RMSI, special, etc.) PDCCH.

[0088] According to an embodiment, RC-CORESET0 may be configured and / or determined according to (e.g., based on) a subset of CORESET0 resources, where the CORESET0 resources (e.g., a subset thereof) may include any of PRBs, RBs, CCEs, REGs, and REG bundles. According to an embodiment, with respect to CORESET0 resources, a subset of CORESET0 resources for RC-CORESET0 may be determined according to (e.g., based on) a CORESET0 configuration. For example, a subset of CORESET0 resources for RC-CORESET0 may be determined according to the number of RBs and subcarrier spacing used, configured, or determined for CORESET0.

[0089] According to an embodiment, if the number of subcarrier spacings and / or RBs configured and / or determined for CORESET0 is less than a threshold (e.g., or a predefined value), all resources for CORESET0 may be used and / or determined for RC-CORESET0. Otherwise, in such a case, a subset of CORESET0 resources may be used and / or determined for RC-CORESET0. According to an embodiment, with respect to CORESET0 resources, a subset of CORESET0 resources for RC-CORESET0 may be determined according to any of a WTRU identity (e.g., IMSI), a WTRU capability (e.g., number of receive antennas, maximum supportable bandwidth, maximum soft buffer size, etc.), and a service type. According to an embodiment, with respect to CORESET0 resources, if a subset of CORESET0 resources is used for RC-CORESET0, any of a REG index, a CCE index, and a REG bundle index are renumbered.

[0090] Partial repetition of a channel According to an embodiment, a (e.g., one) portion of a channel (e.g., PDCCH, PDSCH, etc.) may be repeated (e.g., retransmitted) using resources other than those used (e.g., associated with) to transmit the original channel. According to an embodiment, there may be cases where the BW of the PDCCH may be N RBs, which may be greater than the maximum WTRU BW of L RBs. In such a case, the WTRU may receive the L RBs of the PDCCH in the original transmission and the remaining NL RBs in other time / frequency resources. According to an embodiment, a (e.g., another) WTRU that has a maximum BW of at least N RBs may continue to receive the original transmission and may determine to ignore the repeated portion.

[0091] Figure 8 is a diagram illustrating PDCCH monitoring on two OFDM symbols according to an embodiment. Figure 9 is a diagram illustrating CORESET and SSB on the same OFDM symbol according to an embodiment. Figure 10 is a diagram illustrating REG repetition according to an embodiment. FIG. 11 is a diagram illustrating another iteration of REG, according to an embodiment.

[0092] According to an embodiment, referring to FIG. 8, the PDCCH may be monitored over two OFDM symbols and the associated CORESET consists of N-1 REGs. According to an embodiment, the SSB may be transmitted over four OFDM symbols and may consist of 20 RBs. In such a case, referring to FIG. 8, the maximum WTRU BW may be sufficient to cover the SSB BW and a portion of the PDCCH. In such a case, according to an embodiment, the six RBs constituting REGs 0 and 1 (e.g., over two OFDM symbols) may not be received (e.g., cannot be received, is not received, etc.) by such a WTRU, for example, because the six RBs are outside the frequency range of the receiver of such a WTRU. According to an embodiment, referring to FIG. 9, a similar scenario is illustrated where the CORESET and the SSB are on the same OFDM symbol.

[0093] According to an embodiment, OFDM symbols transmitted on resources outside the frequency range of a receiver (e.g., of a RC WTRU) may be repeated using in / on / in other resources, e.g., as shown in Figures 10 and 11. According to an embodiment, referring to Figures 10 and 11, REGs 0 and 1 may not be received (e.g., cannot be received) by the WTRU because the maximum WTRU BW is not sufficient. According to an embodiment, in such a case, these REGs (e.g., REGs 0 and 1) may be repeated in other resources that are within the frequency range of the WTRU's receiver, e.g.

[0094] According to an embodiment, the index of the repeated REG may be the same index as the original transmit REG (e.g., may share the same index as the original transmit REG). According to an embodiment, if a CCE to REG mapping is applied by the RC WTRU, the RC WTRU may use the repeated REG (e.g., instead of the original transmit REG) in addition to the REG that is not repeated and is in the frequency range of the RC WTRU's receiver. According to an embodiment, in such a case, the RC WTRU may map the CCE to REG{2:N-1} and the repeated REG{0:1}, for example, while performing blind detection of the PDCCH. According to an embodiment, the demodulation reference signal (DM-RS) may be such that the original transmit REG and the repeated REG have the same DM-RS sequence.

[0095] According to an embodiment, a DM-RS sequence may be generated and / or mapped to a corresponding resource in the repeated REG. For example, according to an embodiment, a DM-RS sequence may be generated to be different (e.g., separate / different) from the (e.g., original) DM-RS sequence in / of the original PDCCH. According to an embodiment, for example, in the case considered above, the length of the DM-RS sequence per OFDM symbol may be, for example, 6, assuming there are 6 repeated RBs in one OFDM symbol and each RB has a reference symbol. * It can be determined as a factor of 4=24.

[0096] New initial BWP According to an embodiment, a WTRU (e.g., any of a normal WTRU and an RC WTRU) may receive an SSB in a first BWP. According to an embodiment, there may be a case where such a WTRU receives and / or monitors an associated CORESET0 (e.g., and / or Type 0-PDCCH-CSS) (for such a WTRU) in a second BWP. According to an embodiment, for example, in such a case, the first BWP may be referred to as an initial BWP and the second BWP may be referred to as an RC initial BWP. According to an embodiment, the RC initial BWP may be used interchangeably (e.g., and / or may refer to) any of the initial BWP, RC initial BWP, associated BWP, or RC-specific initial BWP.

[0097] According to an embodiment, in such a case, the RC initial BWP may be configured and / or determined according to any of the frequency band and a bit field in the MIB. According to an embodiment, to configure according to the frequency band, a time and / or frequency offset from the determined first RB of the SSB (e.g., or the first RB of the initial BWP) may be determined according to the frequency band. For example, according to an embodiment, the SCS for the SSB may be determined according to the frequency band, and the WTRU may monitor and / or blind detect the SSB. According to an embodiment, in such a case, the frequency band may also indicate (e.g., may be used to determine) a time and / or frequency offset of the RC initial BWP.

[0098] According to an embodiment, for configuration according to a bit field in the MIB, a reserved bit in the MIB may be used to indicate a time and / or frequency offset of the RC initial BWP. According to an embodiment, for example, alternatively, an existing bit field may be reinterpreted to indicate a time and / or frequency offset of the RC initial BWP. For example, according to an embodiment, a kSSB value in the MIB may indicate a time and / or frequency offset of the RC initial BWP. According to an embodiment, for example, in the case considered above, a first type WTRU may monitor a Type 0-PDCCH-CSS in the first BWP, and a second type WTRU may monitor a Type 0-PDCCH-CSS in the second BWP. According to an embodiment, in such a case, the WTRU type may be determined according to a maximum bandwidth supported (e.g., by the WTRU). According to an embodiment, in such a case, the first BWP and the second BWP may be the same BWP, for example, if the number of RBs for CORESET0 is less than a threshold for a given subcarrier spacing for CORESET0, otherwise the first BWP and the second BWP may be different.

[0099] According to an embodiment, the second BWP may exist (e.g., may be determined to exist, may be assumed, etc.) under any of the following conditions: (1) the subcarrier spacing of CORESET0 is greater than a threshold, (2) the number of RBs configured for CORESET0 is greater than a threshold, and (3) the network allows a (e.g., certain) type of WTRU (e.g., RC WTRU) to access the network. According to an embodiment, the first BWP and the second BWP may overlap completely or partially. According to an embodiment, the second BWP may be a part of the first BWP. According to an embodiment, if the first BWP and the second BWP overlap completely or partially, the SCS for the second BWP may be the same as the SCS for the first BWP. According to an embodiment, if the first BWP and the second BWP do not overlap, the SCS for the second BWP may be indicated (e.g., in the MIB). According to an embodiment, for example, alternatively, the SCS for the second BWP may be determined according to a corresponding frequency band, for example, independently of the SCS for the first BWP.

[0100] According to an embodiment, CORESET0 (e.g., RC-CORESET0) in the second BWP may be determined according to the configuration of CORESET0 in the first BWP. For example, according to an embodiment, the number of symbols for RC-CORESET0 in the second BWP may be determined according to the number of symbols configured for CORESET0 in the first BWP, e.g., the same number of symbols may be used. According to an embodiment, the REG bundle size for RC-CORESET0 in the second BWP may be determined according to the REG bundle size for CORESET0 in the first BWP. According to an embodiment, the number of RBs for RC-CORESET0 in the second BWP may be scaled according to the number of RBs for CORESET0 in the first BWP.

[0101] According to embodiments, the initial BWP may be located in different time and / or frequency resources according to (e.g., based on, for, etc.) the WTRU type. For example, according to embodiments, the initial BWP for a first type of WTRU may be located in a first time / frequency resource and the initial BWP for a second type of WTRU may be located in a second time / frequency resource. According to embodiments, the WTRU may receive configuration information associated with (e.g., of, for, applying to, etc.) the initial BWP for another type of WTRU and its associated channel configuration (e.g., SSB, PDCCH). According to embodiments, if the initial BWPs for the first type and the second type of WTRU overlap, the WTRU may perform any of puncturing and rate matching around PDSCH REs that may collide with a higher priority channel of the initial BWP associated with another type of WTRU.

[0102] FIG. 12 is a diagram illustrating a method, procedure, operation, etc., performed by a WTRU with reduced capabilities, for receiving system information, according to an embodiment.

[0103] Referring to FIG. 12, according to an embodiment, the WTRU may perform any of the following operations. According to an embodiment, as a first operation, the WTRU may receive a physical broadcast channel (PBCH) transmission of the cell, where the PBCH transmission may include information indicating a first control resource set (CORESET) associated with reception of a system information block (SIB). According to an embodiment, as a second operation, the WTRU may receive a first physical downlink control channel (PDCCH) transmission via the first CORESET including information indicating a first type of SIB associated with the first PDCCH transmission, where the information indicating the first type of SIB may include information indicating a second CORESET that (1) may be associated with reception of a second type of SIB and (2) may have fewer resource blocks (RBs) than the first CORESET. According to an embodiment, as a third operation, the WTRU may receive a second PDCCH transmission via the second CORESET including information indicating a second type of SIB associated with the second PDCCH transmission.

[0104] According to an embodiment, there may be any of the following cases: (1) a first CORESET may be associated with a first bandwidth portion (BWP) of a cell; (2) a second CORESET may be associated with a second BWP of a cell; (3) the second CORESET may have a smaller bandwidth than the first CORESET; (4) the second BWP may have fewer RBs than the first BWP; (5) the second BWP may have a smaller bandwidth than the first BWP; (6) a second PDCCH transmission may be associated with a second BWP of a cell; and (7) a second CORESET is associated with a second BWP of a cell.

[0105] According to an embodiment, there may be cases where (1) the frequency location of the second BWP may be determined according to the frequency location of the first BWP, and (2) the first CORESET and the second CORESET may both be identified as CORESET0. According to an embodiment, there may be cases where the first PDCCH transmission includes downlink control information (DCI) and / or where the set of resources of either the first PDCCH transmission or the second PDCCH transmission may be determined according to information included in the PBCH transmission.

[0106] According to an embodiment, as another operation, the WTRU may determine whether the WTRU may be operating as a normal WTRU or a reduced capacity (RC) WTRU according to the monitoring capability of the WTRU. According to an embodiment, the monitoring capability of the WTRU may be determined according to the WTRU type. According to an embodiment, the information included in the PBCH transmission may indicate either (1) for a normal WTRU, either (i) the absence of a CORESET for the Type 0-PDCCH-CSS set associated with the SS / PBCH block, and (ii) a channel number of another SS / PBCH block that has a CORESET for the associated Type 0-PDCCH-CSS, or (2) for a RC WTRU, either (i) the presence of a RC CORESET for the associated RC-Type 0-PDCCH-CSS, and (ii) information indicating one or more monitoring occasions and other parameters of the RC-Type 0-PDCCH-CSS and / or the associated RC CORESET0.

[0107] According to an embodiment, as another operation, the WTRU may determine whether to monitor a first search space associated with a first set of resources associated with the first PDCCH transmission. According to an embodiment, for example, the RC WTRU may determine whether the WTRU is configured to receive the WTRU BW based on the following conditions: (1) the bandwidth (BW) of CORESET0 exceeds a threshold; (2) the BW of CORESET0 summed with the BW of a synchronization signal block (SSB) (e.g., or SS burst) exceeds a threshold; (3) [BW of CORESET0 summed with the BW of SSB] - [BW of overlap of CORESET0 and SSB] exceeds a threshold; (4) the BW from the first subcarrier of CORESET0 to the last subcarrier of SSB exceeds a threshold; (5) the BW from the first subcarrier of SSB to the last subcarrier of CORESET0 exceeds a threshold; (6) the SSB / CORESET0 multiplexing pattern is a specific pattern; (7) a certain time multiplexing technique of CORESET0 and SSB; (8) a threshold associated with the maximum WTRU BW; (9) the subcarrier spacing (SCS) of SSBs belonging to a predefined set and the downlink control channel (DL CCH), (10) the frequency band is one of the set of bands, and (11) the RC WTRU fails to receive DL CCH in CORESET0 within a certain time window.

[0108] According to an embodiment, as another operation, the RC WTRU may determine not to monitor the first search space, and receive, by the RC WTRU, information indicating at least one channel for monitoring either the Type 0-PDCCH-CSS and the RC-Type 0-PDCCH-CSS. According to an embodiment, as a first operation, the RC WTRU may determine whether to monitor the first search space according to either implicit signaling or explicit signaling. According to an embodiment, the information included in the PBCH transmission may include a Master Information Block (MIB), and the information included in the PBCH transmission may indicate one or more monitoring occasions and any of other parameters of CORESET0, including any of a particular number of RBs in CORESET0, a frequency location of CORESET0, and a number of symbols in CORESET0. According to an embodiment, at least one bit in either the MIB or the PBCH transmission may indicate to the RC WTRU that a RC CORESET exists for the associated RC-Type 0-PDCCH-CSS, and kSSB is a subcarrier offset value determined according to a bit in either the MIB or the payload of the PBCH transmission.

[0109] According to an embodiment, the first CORESET may be associated with a normal WTRU, the second CORESET may be associated with a reduced capability (RC) WTRU, the second CORESET may be multiplexed with either the first CORESET and the remaining system information (RMSI) PDSCH according to a predefined pattern known to the RC WTRU, the second CORESET may be transmitted in a portion of a set of resources on an OFDM symbol scheduled with the RMSI PDSCH, and the second CORESET may be present on any number of OFDM symbols. According to an embodiment, the second CORESET may be associated with a DCI format for compact downlink control information (DCI) having fewer bits than the RMSI PDCCH, and the DCI format may indicate a frequency location of the second CORESET. According to an embodiment, as another operation, the WTRU may receive second information indicating a second set of resources for the first PDCCH transmission. According to an embodiment, the second set of resources may be resources other than the first set of resources associated with the first PDCCH transmission, the second set may be received on condition that the bandwidth (BW) of the first PDCCH transmission exceeds a maximum BW of the WTRU, and the second information may include any number of system information blocks (SIBs).

[0110] conclusion Although the features and elements are described above in certain combinations, those skilled in the art will understand that each feature or element may be used alone or in any combination with the other features and elements. Furthermore, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a UE, a WTRU, a terminal, a base station, an RNC, or any host computer.

[0111] Additionally, in the embodiments described above, processing platforms, computing systems, controllers, and other devices including converging points / servers including constraint servers and processors are described. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of those skilled in the art of computer programming, references to acts and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer-executed," or "CPU-executed."

[0112] Those of ordinary skill in the art will appreciate that the operations and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resultant transformation or reduction of the electrical signals, and maintains the data bits in memory locations of the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be appreciated that the exemplary embodiments are not limited to the platforms or CPUs mentioned above, and that other platforms and CPUs may support the methods provided.

[0113] The data bits may also be maintained on a computer readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read only memory ("ROM")) mass storage system readable by a CPU. The computer readable medium may include computer readable media that resides exclusively on a processing system, or distributed, cooperative, or interconnected among multiple interconnected processing systems that may be local or remote to a processing system. It will be appreciated that representative embodiments are not limited to the memories discussed above, and that other platforms and memories may support the methods described.

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

[0115] There is little distinction between hardware and software implementations of aspects of the system. The use of hardware or software is generally (though not always, in certain circumstances the choice between hardware and software may be meaningful) a design choice that implies a cost vs. efficiency tradeoff. There may be a variety of vehicles (e.g., hardware, software, and / or firmware) in which the processes and / or systems and / or other techniques described herein may be effective, and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may select a primarily hardware and / or firmware vehicle. If flexibility is paramount, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0116] The foregoing detailed description has illustrated various embodiments of devices and / or processes through the use of block diagrams, flow charts, and / or examples. To the extent that such block diagrams, flow charts, and / or examples include one or more functions and / or operations, it will be appreciated by those skilled in the art that each function and / or operation in such block diagrams, flow charts, or examples may be individually and / or collectively implemented by a wide variety of hardware, software, firmware, or substantially any combination thereof. Suitable processors include, by way of example, general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors in association with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), application specific standard products (ASSPs), field programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), and / or state machines.

[0117] Although features and elements are provided above in specific combinations, those of ordinary skill in the art will understand that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in this application, which are intended as illustrations of various aspects. As will be apparent to those skilled in the art, many modifications and variations can be made without departing from the spirit and scope of the present invention. No element, operation, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly set forth as such. In addition to those enumerated herein, functionally equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, together with the full scope of equivalents to which such claims are entitled. It is to be understood that the present disclosure is not limited to any particular method or system.

[0118] It should also be understood that the terms used herein are intended to describe particular embodiments (e.g., only) and are not intended to limit the invention. As used herein, the term "user equipment" and its abbreviation "UE" when referred to herein may mean (1) a wireless transmit and / or receive unit (WTRU), such as the described infrastructure, (2) any of the several embodiments of a WTRU, such as the described infrastructure, (3) a wireless-enabled and / or wired-enabled (e.g., tethered) device configured with some or all of the structure and functionality of a WTRU (e.g., the described infrastructure), among others, (4) a wireless-enabled and / or wired-enabled device configured with less than all of the structure and functionality of a WTRU (e.g., the described infrastructure), or (5) the like. Details of an Exemplary WTRU That May Represent Any WTRU Enumerated herein.

[0119] In certain representative embodiments, some portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein may be equivalently implemented in whole or in part in an integrated circuit as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is within the skill of those skilled in the art in light of this disclosure. Furthermore, those skilled in the art will recognize that the mechanisms of the subject matter described herein may be distributed as program products in various forms, and that the illustrative embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).

[0120] The subject matter described herein at times illustrates different components that are included within or connected to different other components. It should be understood that such depicted architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. Conceptually, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Thus, any two components combined herein to achieve a particular functionality may be viewed as "associated" with one another such that the desired functionality is achieved, regardless of architecture or intermediate components. Similarly, any two components so associated may be considered to be "operably connected" or "operably coupled" with one another to achieve the desired functionality, and any two components that can be so associated may be considered to be "operably coupleable" with one another to achieve the desired functionality. Specific examples of operably coupleable include, but are not limited to, components that can physically mate and / or physically interact, and / or components that can wirelessly interact and / or wirelessly interact, and / or components that can logically interact and / or logically interact.

[0121] With respect to the use of substantially any plural and / or singular term herein, one of ordinary skill in the art can convert from plural to singular and / or from singular to plural as appropriate to the context and / or application. For purposes of clarity, various singular / plural permutations may be expressly described herein.

[0122] In general, those skilled in the art will understand that the terms used in this specification, and particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "non-limiting" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," and the term "including" should be interpreted as "including but not limited to"). Furthermore, those skilled in the art will understand that where a specific number of recitations of an introduced claim are intended, such intent is expressly set forth in the claim, and in the absence of such recitation, no such intent exists. For example, where only one item is intended, the term "single" or similar language may be used. To aid in understanding, the following appended claims and / or the description of this specification may include the use of the introductory phrases "at least one" and "one or more" to introduce the claim recitations. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim that includes such an introduced claim recitation to embodiments that include only one such recitation, even if the same claim contains the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. Moreover, those skilled in the art will recognize that even if a specific number of recitations of an introduced claim are explicitly recited, such recitation should be interpreted to mean at least the recited number (e.g., the simple recitation "two recitations" without other modifiers means at least two recitations, or more than two recitations).Furthermore, when notations similar to "at least one of A, B, and C" are used, such structures are generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). When notations similar to "at least one of A, B, or C" are used, such structures are generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). Those skilled in the art will further appreciate that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" should be understood to include the possibilities of "A" or "B" or "A and B." Additionally, as used herein, the term "any of" followed by a list of items and / or a list of categories of items is intended to include "any of," "any combination of," "any more than one of," and / or "any combination of more than one of" the items and / or categories of items, individually or in combination with other items and / or other categories of items. Additionally, as used herein, the term "set" or "group" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero.

[0123] Furthermore, when features or aspects of the disclosure are described in terms of a Markush group, those skilled in the art will recognize that the disclosure is also described thereby in terms of any individual members or subgroups of members of the Markush group.

[0124] As will be appreciated by those skilled in the art, for all purposes, including in terms of providing a written description, all ranges disclosed herein encompass any possible subranges and combinations of subranges thereof. Any recited range can be readily recognized as fully descriptive and allowing the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be readily broken down into a lower third, a middle third, and an upper third, etc. As will also be appreciated by those skilled in the art, all words such as "up to," "at least," "greater than," "less than," etc., refer to ranges that include the recited numbers and that can be further broken down into subranges as discussed above. Finally, as will be appreciated by those skilled in the art, ranges include each individual element. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to a group having 1, 2, 3, 4, or 5 cells, and so on.

[0125] Moreover, the claims should not be read as limited to the provided order or to the provided elements unless specifically so stated. Moreover, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. 112, paragraph 6, or means-plus-function claim format, and no claim without the term "means for" is intended to do so.

[0126] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC), or any host computer. The WTRU may be used in conjunction with hardware and / or software implemented modules, such as, for example, a Software Defined Radio (SDR), and may be implemented in other components, such as a camera, a video camera module, a video phone, a speaker phone, a vibration device, a speaker, a microphone, a television transceiver, a hands-free headset, a keyboard, a Bluetooth module, a frequency modulation (FM) radio unit, a Near Field Communication (NFC) module, an LCD display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and / or a wireless local area network (WLAN) or Ultra Wide Band (UWB) module.

[0127] Although the present invention has been described with respect to a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In particular embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

[0128] Moreover, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown, but rather various modifications in the details may be made within the scope of the claims and equivalents thereof and without departing from the invention.

Claims

1. 1. A method for receiving system information performed by a wireless transmit / receive unit (WTRU) having reduced capabilities, the method comprising: receiving a physical broadcast channel (PBCH) transmission of a cell, the PBCH transmission including information indicating a first control resource set (CORESET) associated with reception of a system information block (SIB); receiving a first physical downlink control channel (PDCCH) transmission via the first CORESET, the first PDCCH transmission including information indicating a first type of SIB associated with the first PDCCH transmission, the information indicating the first type of SIB including information indicating a second CORESET (1) associated with receiving a second type of SIB and (2) having fewer resource blocks (RBs) than the first CORESET; receiving, via the second CORESET, a second PDCCH transmission that includes information indicating a SIB of the second type associated with the second PDCCH transmission.

2. 2. The method of claim 1, wherein: (1) the first CORESET is associated with a first bandwidth portion (BWP) of the cell; (2) the second CORESET is associated with a second BWP of the cell; (3) the second CORESET has a smaller bandwidth than the first CORESET; (4) the second BWP has fewer RBs than the first BWP; (5) the second BWP has a smaller bandwidth than the first BWP; (6) the second PDCCH transmission is associated with the second BWP of the cell; and (7) the second CORESET is associated with the second BWP of the cell.

3. 3. The method of claim 2, wherein: (1) a frequency location of the second BWP is determined according to a frequency location of the first BWP; and (2) the first CORESET and the second CORESET are both identified as CORESET0.

4. 3. The method of claim 2, wherein the first PDCCH transmission includes downlink control information (DCI), and a set of resources for either the first PDCCH transmission or the second PDCCH transmission is determined according to the information included in the PBCH transmission.

5. The method of at least one of claims 2 to 3, further comprising determining whether the WTRU is operating as a normal WTRU or as a reduced capability (RC) WTRU according to a monitoring capability of the WTRU, the monitoring capability of the WTRU being determined according to a WTRU type.

6. The information included in the PBCH transmission is: (1) for the normal WTRU, either (i) there is no CORESET for a Type 0-PDCCH-CSS set associated with the SS / PBCH block, and (ii) a channel number of another SS / PBCH block that has a CORESET for an associated Type 0-PDCCH-CSS; and (2) for the RC WTRU, either: (i) the presence of a RC CORESET for an associated RC-Type 0-PDCCH-CSS; and (ii) information indicating one or more monitoring opportunities and other parameters of the RC-Type 0-PDCCH-CSS and / or the associated RC CORESET0.

7. The method of claim 5 , further comprising: determining, by the RC WTRU, whether to monitor a first search space associated with a first set of resources associated with the first PDCCH transmission.

8. The RC WTRU is configured to detect the following conditions: (1) the bandwidth (BW) of the CORESET0 exceeds a threshold; (2) the BW of the CORESET0 summed with the BW of a synchronization signal block (SSB) exceeds a threshold; (3) [the BW of the CORESET0 summed with the BW of the SSB] - [the BW of the overlap of the CORESET0 and the SSB] exceeds a threshold; (4) the BW from the first subcarrier of the CORESET0 to the last subcarrier of the SSB exceeds a threshold; (5) the BW from the first subcarrier of the SSB to the last subcarrier of the CORESET0 exceeds a threshold; (6) the SSB / CORESET0 multiplexing pattern is a specific pattern; (7) a certain time multiplexing technique of CORESET0 and the SSB; (8) the maximum WTRU 8. The method of claim 7, wherein the RC WTRU determines to monitor the first search space according to any of the following: (9) a threshold associated with a BW; (10) a subcarrier spacing (SCS) of an SS burst and a downlink control channel (DL CCH) belonging to a predefined set; (11) a frequency band is one of a set of bands; and (12) the RC WTRU fails to receive the DL CCH in the CORESET0 within a time window.

9. 8. The method of claim 7, further comprising receiving, by the RC WTRU, information indicating at least one channel to monitor, either a Type 0-PDCCH-CSS or a RC-Type 0-PDCCH-CSS, on a condition that the RC WTRU determines not to monitor the first search space.

10. The method of claim 7, wherein the RC WTRU determines whether to monitor the first search space according to either implicit signaling or explicit signaling.

11. the information included in the PBCH transmission comprises a Master Information Block (MIB); The information included in the PBCH transmission indicates one or more monitoring opportunities and other parameters of the CORESET0, including any of a particular number of RBs in the CORESET0, a frequency location of the CORESET0, and a number of symbols in the CORESET0; At least one bit in either the MIB or the PBCH transmission indicates to a RC WTRU that a CORESET for an associated RC-Type 0-PDCCH-CSS is present; The method according to at least one of claims 2 to 3, wherein kSSB is a subcarrier offset value determined according to one or more bits in either the MIB or the payload of the PBCH transmission.

12. the first CORESET is associated with a normal WTRU; the second CORESET is associated with a reduced capability (RC) WTRU; the second CORESET is multiplexed with the first CORESET and any remaining system information (RMSI) PDSCH according to a predefined pattern known to the RC WTRU; the second CORESET is transmitted in a portion of the set of resources on OFDM symbols scheduled with the RMSI PDSCH; The method of claim 2 , wherein the second CORESET is present over any number of OFDM symbols.

13. 13. The method of claim 12, wherein the second CORESET is associated with a compact downlink control information (DCI) format having fewer bits than the RMSI PDCCH, the DCI format indicating a frequency location of the second CORESET.

14. receiving second information indicating a second set of resources for the first PDCCH transmission; the second set of resources being other than a first set of resources associated with the first PDCCH transmission; The second set is received under a condition that a bandwidth (BW) of the first PDCCH transmission exceeds a maximum BW of the WTRU; The method of claim 1 , wherein the second information comprises a number of system information blocks (SIBs).

15. determining to move to the first BWP according to one of an explicit signal and an implicit signal; the first BWP is an initial BWP; the second BWP is a RC initial BWP; the initial BWP is located within different time / frequency resources for each type of WTRU; The second BWP is detected according to any one of: a subcarrier spacing of the first CORESET is greater than a threshold; a number of RBs configured for the first CORESET is greater than a threshold; and a network allows a certain type of WTRU to access the network; the first BWP and the second BWP overlap completely or partially; The method according to at least one of claims 2 to 3, wherein a second CORESET in the second BWP is determined according to a configuration of the first CORESET in the first BWP.

16. 1. A wireless transmit receive unit (WTRU) comprising circuitry including any of a transmitter, a receiver, a processor, and a memory, the WTRU comprising: receiving a physical broadcast channel (PBCH) transmission of a cell, the PBCH transmission including information indicating a first control resource set (CORESET) associated with reception of a system information block (SIB); receiving, via the first CORESET, a first physical downlink control channel (PDCCH) transmission including information indicating a first type of SIB associated with the first PDCCH transmission, the information indicating the first type of SIB including information indicating a second CORESET (1) associated with reception of a second type of SIB and (2) having fewer resource blocks (RBs) than the first CORESET; and receiving, via the second CORESET, the second PDCCH transmission including information indicating the second type of SIB associated with the second PDCCH transmission.

17. 17. The WTRU of claim 16, wherein any of the following are present: (1) the first CORESET is associated with a first bandwidth portion (BWP) of the cell; (2) the second CORESET is associated with a second BWP of the cell; (3) the second CORESET has a smaller bandwidth than the first CORESET; (4) the second BWP has fewer RBs than the first BWP; (5) the second BWP has a smaller bandwidth than the first BWP; (6) the second PDCCH transmission or the second CORESET is associated with the second BWP of the cell; and (7) the second CORESET is associated with the second BWP of the cell.

18. 20. The WTRU of claim 17, wherein (1) a frequency location of the second BWP is determined according to a frequency location of the first BWP; and (2) the first CORESET and the second CORESET are both identified as CORESET0.

19. 20. The WTRU of claim 17, wherein the first PDCCH transmission includes downlink control information (DCI), and a set of resources for either the first PDCCH transmission or the second PDCCH transmission is determined according to the information included in the PBCH transmission.

20. The WTRU of claim 17, further configured to perform the method of any one of claims 5 to 15.

Images