TW201907686A - Synchronization signal multiplexing and mappings in nr - Google Patents

Abstract

A wireless transmit/receive unit (WTRU) and a method implemented in the WTRU for receiving a plurality of messages from a base station. The messages include an indication of a synchronization signal (SS) and physical broadcast channel (PBCH) (SS/PBCH) block to be monitored. The SS/PBCH block may be used by the WTRU to acquire the primary synchronization signal (PSS) and secondary synchronization signal (SSS) at a fixed location within the indicated SS/PBCH block. Next the WTRU may acquire one or more PBCHs and then an entire SS/PBCH block based on the determined SS/PBCH block type. The SS/PBCH block includes 4 symbols and the PBCH may be located on 3 of the 4 symbols and the PSS and SSS are each located on a different one of the four symbols from each other. The PBCH symbols may each include its own frequency-multiplexed demodulation reference symbols (DMRS).

Description

Synchronous signal multiplexing and mapping in NR

CROSS- REFERENCE TO RELATED APPLICATIONS [0001] This application claims US Provisional Patent Application No. 62/492, 711, filed on May 1, 2017; US Provisional Patent Application No. 62/543,266, filed on August 9, 2017; The benefit of U.S. Provisional Patent Application No. 62/586,016, the disclosure of which is incorporated herein by reference.

The fifth generation of mobile communication protocols has many uses. Some of these uses can be enhanced mobile broadband (eMBB), large-scale machine type communication (mMTC), and ultra-reliable and low latency communication (URLLC). Different use cases may focus on different needs, such as higher data rates, higher spectral efficiency, lower power and higher energy efficiency, lower latency and higher reliability. A wide range of deployment scenarios are considering a wide range of frequencies from 700MHz to 80GHz. In any case of these uses, an agreement may be required to handle the organization of wireless signal transmission.

A wireless transmit/receive unit (WTRU) for receiving multiple messages from a base station and methods implemented within the WTRU are disclosed. The message includes an indication of the Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) (SS/PBCH) blocks to be monitored. The WTRU may use the SS/PBCH block to acquire a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) at a fixed location within the indicated SS/PBCH block. The WTRU may then acquire one or more PBCHs and subsequent entire SS/PBCH blocks based on the determined SS/PBCH block type. The SS/PBCH block includes four symbols and the PBCH is located on three symbols of the four symbols and the PSS and SSS are each located on a different one of the four symbols. Each of the PBCH symbols may include its own frequency multiplex demodulation reference symbol (DMRS). Furthermore the PBCH may comprise a DMRS located on a resource determined according to an OFDM symbol index. Furthermore, the SS can be located on a symbol between two symbols, each of which contains a PBCH. In addition, the PSS and SS can be located on subcarriers between 56 and 182 within their respective symbols.

FIG. 1A is a diagram showing an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content for a plurality of wireless users, such as voice, data, video, information, broadcast, and the like. The communication system 100 can enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, communication system 100 can use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA). ), single carrier FDMA (SC-FDMA), zero tail unique word DFT extended OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC) and many more.

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

The communication system 100 can also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be configured to have a wireless interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (eg, CN 106/115, Internet) Any type of device of way 110, and/or other network 112). For example, the base stations 114a, 114b may be a base transceiver station (BTS), a node B, an eNodeB, a local node B, a local eNodeB, a gNB, an NR Node B, a website controller, an access point (AP). , as well as wireless routers and so on. While each base station 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b can include any number of interconnected base stations and/or network elements.

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

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

More specifically, as noted above, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, to name a few. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104/113 may implement radio technologies, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA (WCDMA) to establish airborne Interface 115/116/117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and/or High Speed UL Packet Access (HSUPA).

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

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

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

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement the following radio technologies, such as IEEE 802.11 (ie, Wireless Fidelity (WiFi)), IEEE 802.16 (ie, Worldwide Interoperability for Microwave Access (WiMAX)). ), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), for GSM Evolved Enhanced Data Rate (EDGE) and GSM EDGE (GERAN) and more.

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

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

The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include a circuit switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 may include the use of common communication protocols (eg, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP Internet Protocol suite). A system of globally interconnected computer networks and devices. Network 112 may include wired and/or wireless communication networks that are owned and/or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as RAN 104/113.

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

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

The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with the DSP core, a controller, a microcontroller , Dedicated Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), and state machine. The processor 118 can perform signal encoding, 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 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although FIG. 1B depicts processor 118 and transceiver 120 as separate components, it should be understood that processor 118 and transceiver 120 can also be integrated into an electronic package or wafer.

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

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

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

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

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

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

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

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

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

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

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

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

The MME 162 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for verifying the users of the WTRUs 102a, 102b, 102c, performing bearer initiation/deactivation procedures, and selecting a particular service gateway or the like during the initial attachment of the WTRUs 102a, 102b, 102c. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM and/or WCDMA.

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

The SGW 164 can be coupled to the PGW 166, which can provide the WTRUs 102a, 102b, 102c with access to a packet switched network (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and the IP-enabled device. Communication.

The CN 106 can facilitate communication with other networks. For example, CN 106 may provide WTRUs 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communications devices. For example, the CN 106 can include or communicate with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server), and the IP gateway can act as an interface between the CN 106 and the PSTN 108. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers.

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

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

A WLAN of the Infrastructure Basic Service Set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or have another type of wired/wireless network that interfaces with the distributed system (DS) or carries traffic and/or carries the BSS. Traffic originating from the outside of the BSS to the STA can be reached by the AP and delivered to the STA. Traffic originating from the STA to a destination outside the BSS can be sent to the AP for delivery to the corresponding destination. The traffic between the STAs inside the BSS can be sent by the AP, for example, the source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and/or referred to as point-to-point traffic. The point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) with direct link setup (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode does not have an AP, and STAs (eg, all STAs) that are internal to the IBSS or that use the IBSS can communicate directly with each other. Here, the IBSS communication mode can sometimes be referred to as an "ad-hoc" communication mode.

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

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

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

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

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

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

FIG. 1D is a system diagram showing RAN 113 and CN 115, in accordance with an embodiment. As described above, the RAN 113 can communicate with the WTRUs 102a, 102b, 102c via the null plane 116 using NR radio technology. In addition, the RAN 113 can also communicate with the CN 115.

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

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

The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c that employ independent and/or non-independent configurations. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a separate configuration, the WTRUs 102a, 102b, 102c may use signals in the unlicensed band to communicate with the gNBs 180a, 180b, 180c. In a non-independent configuration, the WTRUs 102a, 102b, 102c may communicate/connect with the gNBs 180a, 180b, 180c while communicating/connecting with other RANs (e.g., eNodeBs 160a, 160b, 160c). For example, the WTRUs 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principles. In a non-independent configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and/or throughput to be the WTRU 102a, 102b, 102c provide services.

Each of gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and/or DL, support network Road cutting, implementation of dual connectivity, implementation of interaction between NR and E-UTRA, user plane data routed to user plane functions (UPF) 184a, 184b, and routing to access and mobility management functions (AMF) 182a, 182b control plane information and so on. As shown in FIG. 1D, the gNBs 180a, 180b, and 180c can communicate with each other through the Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possibly a data network (DN) 185a, 185b. While each of the foregoing elements is described as being part of CN 115, it should be understood that any of these elements can be owned and/or operated by other entities than the CN operator.

The AMFs 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, AMFs 182a, 182b may be responsible for verifying users of WTRUs 102a, 102b, 102c, supporting network cuts (eg, handling different PDU sessions with different needs), selecting special SMFs 183a, 183b, managing registration areas, terminating NAS Communication, and mobility management, etc. The AMF 182a, 1823b may use network cut processing to tailor the CN support provided for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. As an example, different network cuts can be established for different use cases, such as services that rely on ultra-reliable low-latency (URLLC) access, services that rely on enhanced large-scale mobile broadband (eMBB) access, and / or services for machine type communication (MTC) access, etc. The AMF 162 may provide for switching between the RAN 113 and other RANs (not shown) that use other radio technologies (eg, non-3GPP access technologies such as LTE, LTE-A, LTE-A Pro, and/or WiFi). Control plane function.

The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via the N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via the N4 interface. The SMFs 183a, 183b can select and control the UPFs 184a, 184b, and can configure traffic routing by the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating WTRU/UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink information notifications, and the like. The PDU session type may be IP based, non-IP based, Ethernet based, etc.

The UPFs 184a, 184b may be coupled 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 a packet switched network (e.g., the Internet 110). Take in order to facilitate communication between the WTRUs 102a, 102b, 102c and the IP-enabled device. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-connection PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring and the like.

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

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

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

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

Based on the general requirements outlined in ITU-R, NGMN, and 3GPP, the broad-scope classification of use cases for emerging 5G systems can be described as follows: Enhanced Mobile Broadband (eMBB), Large Machine Class Communication (mMTC), and Ultra-Reliable Low Latency Communication (URLLC). Different use cases can focus on different needs, such as higher data rates, higher spectral efficiency, lower power and higher energy efficiency, lower latency, and higher reliability. A wide range of bands from 700 MHz to 80 GHz can be considered for various deployment scenarios.

In some cases, as the carrier frequency increases, severe path loss may become an important limitation to ensure adequate coverage. Transmission within a millimeter wave system can additionally suffer from non-line loss, such as diffraction loss, penetration loss, oxygen absorption loss, and foliage loss. During initial access, the base station and the WTRU need to overcome these high path losses and discover each other. For example, using multiple antenna elements to produce a beamformed signal is an effective way to compensate for severe path loss by providing significant beamforming gain. Beamforming techniques may include digital, analog or hybrid beamforming.

Cell search is the process by which the WTRU borrows to synchronize the time and frequency of the cell and detect the cell ID. In LTE, the synchronization signal can be transmitted in the 0th and 5th subframes of each radio frame and used for time and frequency synchronization during initialization. As part of the system acquisition process, the WTRU may sequentially synchronize to OFDM symbols, time slots, sub-frames, half frames, and radio based on synchronization signals (which may be Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS)). frame. PSS can be used to obtain time slots, sub-frames, and half-frame boundaries. The PSS can also provide a physical layer cell identity (PCI) within the cell identity group. SSS can be used to obtain radio frame boundaries. The SSS may further enable the WTRU to determine a cell identity group, which may range from 0 to 167.

After successful synchronization and physical layer cell identity (PCI) acquisition, the WTRU may decode the Physical Broadcast Channel (PBCH) with the assistance of a Cell Specific Reference Symbol (CRS) and obtain information about the system bandwidth and system frame number (SFN). And the main block (MIB) of the entity hybrid ARQ indicator channel (PHICH) configuration.

In LTE, synchronous signals (PSS and SSS) and PBCH can be continuously transmitted according to a standard period. In LTE, a single transmit beam can be used for initial access. In 5G NR, multiple beams can be used and the concept of synchronous signal block (SS block) and synchronous signal burst (SS burst) can be introduced to support the multi-beam. An efficient and flexible design of the SS block may be required for fast acquisition, low complexity, and accurate detection.

By using the multi-beam, SS blocks can be included in the SS burst for initial access. The SS burst can be transmitted periodically (eg, every 20 ms), and the SS burst can include one or more SS blocks.

Each of the SS blocks within the SS burst can be associated with one or more beams. The number of SS blocks within an SS burst can be determined by the gNB based on the number of beams used at the gNB. For example, if N beams are used at the gNB, N SS blocks can be used or transmitted within the SS burst.

Each SS block may include at least one PSS, at least one SSS, and at least one physical broadcast channel (PBCH). Figure 2 shows an exemplary SS burst 200 within a 5G NR having a period of x ms and having multiple SS blocks within the SS burst. That is, an SS burst includes a plurality of (N) SS blocks, which further include PSS, SSS, and PBCH.

The examples disclosed herein can be applied to NR designs for initial access as well as synchronization signals and channels. In particular, examples are described herein for multiplexed SS block design including OFDM symbols for different signals; SS block-to-time slot and subframe multiplexing and mapping; for special SS blocks, conventional The design of the SS block and the blank SS block; and the multiplexing and mapping of the SS burst to the radio frame and the SS burst set. It should be noted that a plurality of blocks, channels, and OFDM symbols are described herein in order from left to right.

Figures 3A through 3K show various examples of exemplary SS block designs.

In FIG. 3A, the exemplary SS block includes two PBCHs 302 and 304, a PSS 306, and an SSS 308, which are arranged in the time domain in the order of PSS, PBCH, SSS, and PBCH.

In FIG. 3B, the exemplary SS block includes three PBCHs 302, 304, and 310, a PSS, and an SSS, which are arranged in the time domain in the order of PSS, PBCH, SSS, PBCH, and PBCH.

In FIG. 3C, the exemplary SS block includes four PBCHs, PSSs, and SSSs, where the SSS is located between two consecutive PBCHs 312 and 314, which are in the time domain according to PSS, PBCH, PBCH, SSS, PBCH, and PBCH. The order is arranged.

In the 3D diagram, the exemplary SS block includes four PBCHs, PSSs, and SSSs, where the SSS is located between a PBCH and three consecutive PBCHs, which are arranged in the order of PSS, PBCH, SSS, PBCH, PBCH, and PBCH. .

In FIG. 3E, the exemplary SS block includes two PBCHs and two SSSs, which are arranged in the order of PBCH, SSS, PBCH, and PSS.

In the 3F and 3G diagrams, the exemplary SS block includes two PBCHs and an SSS/PSS located between the two PBCHs.

In FIG. 3H, the exemplary SS block includes two consecutive PBCHs and SSS/PSSs located to the left of the two consecutive PBCHs, which are arranged in the order of PBCH, PSS, SSS, and PBCH.

In FIG. 3I, the exemplary SS block includes two consecutive PBCHs and SSS/PSSs located to the right of the two consecutive PBCHs, which are arranged in the order of PBCH, PBCH, SSS, and PSS.

In FIG. 3J, the exemplary SS block includes two PBCHs, a PSS, and an SSS and two paging channel combination between the two PBCHs, which are arranged in the order of PSS, PBCH, paging/SSS/paging, and PBCH. It should be noted that in any of Figures 3A through 3K, the page may be replaced with other signals or channels such as PBCH or CSI-RS. In general, an exemplary SS block includes two PBCHs, a PSS, and an SSS between two PBCHs combined with two other signals or channels (OSCs) arranged in the order of PSS, PBCH, OSC/SSS/OSC, and PBCH. If the OSC is paging, it can become the 3J picture. If the OSC is a CSI-RS, it can become a 3K picture. If the OSC is PBCH, it can become the 4B picture.

In FIG. 3K, the exemplary SS block includes two PBCHs, a PSS, and a combination of SSS and two-channel status information reference signals (CSI-RS) 320 and 322 between two PBCHs, which are in accordance with PSS, PBCH, and CSI-RS. The order of /SSS/CSI-RS and PBCH is arranged. This is the case where the paging in the 3J picture is replaced with the CSI-RS or the OSC is the CSI-RS.

The exemplary SS blocks shown in Figures 3A through 3K may include N _reg OFDM symbols. N _reg can be equal to 4. In FIG. 3A, an exemplary SS block may include one OFDM symbol for PSS, one OFDM symbol for SSS, and two OFDM symbols for PBCH. N _PBCH subcarriers may be used for PBCH, and N _SS subcarriers may be used for PSS or SSS. For example, N _PBCH = 288 subcarriers may be used for PBCH, and N _SS = 144 subcarriers may be used for PSS or SSS. The design principle is to make the PBCH as close as possible to the SSS.

As shown in Figures 3B through 3D, multiplexing can be extended to N PBCH OFDM symbols, where N > An exemplary SS block may have N = 3 PBCH OFDM symbols (Fig. 3B), N = 4 PBCH OFDM symbols (alternative 1) (3C picture), and N = 4 PBCH OFDM symbols (alternative) 2) (Fig. 3D). Figure 3E shows an exemplary SS block in which the PSS and SSS can be interchanged. The design principle is to make the SSS closer to the PBCH.

In the 3F figure, the PBCH can be located on both sides while maintaining the PSS and SSS between the PBCHs. Alternatively, as shown in Figure 3G, the PSS and SSS can be interchanged.

Figures 3H and 3I show that two consecutive PBCHs can be on one side while holding the PSS and SSS on the other side. The design principle in Figure 3H is to keep the PSS closer to the SSS while keeping the SSS closer to the PBCH. Alternatively, as shown in Figure 3I, the PSS and SSS can be interchanged. The design principle is also to keep the PSS closer to the SSS while keeping the SSS closer to the PBCH. Therefore, when the PSS is interchanged with the SSS, the PBCH can also be moved to the other side.

Figure 3J shows an example with a paging channel that may exist within a frame. When there is a paging channel, the paging channel can be multiplexed within the exemplary SS block. The paging channel can be located on one or both sides of the SSS in the frequency domain within the same OFDM symbol.

Figure 3K shows an example with a Channel Status Information Reference Signal (CSI-RS), which may be located in a regular or special SS block. In this case, the CSI-RS can be multiplexed with the SSS in a frequency division multiplexing (FDM) manner. The CSI-RS may be located on one or both sides of the SSS in the frequency domain within the same OFDM symbol. The CSI-RS can also be replaced with a Motion Reference Signal (MRS) if needed.

4A and 4B illustrate example SS/PBCH blocks 400A and 400B within a time-frequency structure. In Figure 4A, each SS/PBCH block (402, 404, 406, 408) may include four OFDM symbols in the time domain. SS/PBCH blocks 404 and 408 may include only PBCH, while SS/PBCH block 402 includes PBCH/PSS/PBCH and SS/PBCH block 406 includes PBCH/SSS/PBCH. Figure 4B shows another combination with respect to SS/PBCH block 400B: PSS only; PBCH only; PBCH/SSS/PBCH; PBCH (left to right). This is the case when the paging in the 3J picture is replaced with the PBCH or the OSC is the PBCH.

The PSS, SSS, and PBCH associated with the PBCH Specific Demodulation Reference Signal (DMRS) in Figure 4A may occupy different symbols, as shown in Table 1 below: Table 1 : Resources for PSS , SSS , PBCH, and DMRS for PBCH in the SS/PBCH block (in Figure 4A )

In the example shown in FIG. 4A, in the frequency domain, each block (402, 404, 406, 408) may include from 0 to 239 in each block (402, 404, 406, 408) in ascending order. Numbered 240 consecutive subcarriers. Subcarrier k within a block may correspond to a resource block Subcarrier ,among them, The subcarriers can be expressed in terms of the SCS for the block.

Figure 4B shows another example of an SS block design in the case of considering a time-frequency structure. As shown in FIG. 4A, the SS/PBCH block in FIG. 4B may further include four OFDM symbols numbered from 0 to 3 in ascending order, and includes PSS, SSS or PBCH. Within the SS/PBCH block, the PSS, SSS, or PBCH associated with the PBCH-specific DMRS may occupy the different symbols shown in Table 2 below. Table 2 : Resources for PSS , SSS , PBCH, and DMRS for PBCH in the SS/PBCH block (in Figure 4B )

In the frequency domain, the SS/PBCH block in FIG. 4B may include 216 consecutive subcarriers numbered from 0 to 215 in the SS/PBCH block in ascending order. The subcarrier k in the SS/PBCH block may correspond to a resource block Subcarrier ,among them, The subcarriers may be expressed in accordance with the SCS for the SS/PBCH block.

For SS/PBCH blocks, the WTRU can assume a single antenna 埠 (where p stands for apostrophe), SCS configuration And the same cyclic prefix (CP) length and SCS for PSS, SSS and PBCH. The WTRU may assume that the SS/PBCH block transmitted with the same SS block time index during the SS/PBCH bursting set period is relative to the Doppler spread, Doppler shift, average gain, average delay, and spatial RX parameters. Quasi-co-location (QCL-ed). The WTRU may not assume the QCL of any other SS/PBCH block transmission.

For PSS mapping within an SS/BPCH block, the WTRU may assume that the symbol sequence d _pss (0),..., d _pss (126) constituting the PSS may be scaled by the PSS power allocation factor β _ss and In accordance with the order of k , it is mapped to resource elements (RE)( k,l ) _{p, μ} , where k and l can be given by Tables 1 and 2 and represent the frequency and time indices within an SS/PBCH block, respectively.

For SSS mapping within an SS/PBCH block, the WTRU may assume that the symbol sequence d _sss (0),..., d _sss (126) constituting the SSS may be scaled by the SSS power allocation factor β _ss and In accordance with the order of k , it is mapped to resource elements ( k,l ) _{p, μ} , where k and l can be given by Tables 1 and 2 and represent the frequency and time indices within an SS/PBCH block, respectively.

In order to map the PBCH and the DMRS within the SS/PBCH block, the WTRU may assume that a plurality of value symbol sequences d _PBCH (0),..., d _PBCH ( M _symb -1) constituting the PBCH may be allocated by the PBCH power factor β. _{The PBCH} is scaled and mapped to the resource elements ( k,l ) _{p, μ} that are not used for the PBCH DMRS in order from d _PBCH (0).

The mapping of resource elements ( k,l ) _{p, μ} that are not reserved for other purposes may be performed in the order of the first frequency index k after the time index l , where k and l respectively represent an SS/PBCH block The frequency index and time index within and can be given by Table 1 and Table 2.

The WTRU may assume that a plurality of value symbol sequences r _l (0), ..., r _l (143) constituting a DMRS for an SS/PBCH block may be allocated by a PBCH DMRS power allocation factor Be scaled, and after the first follow increasing order k and l is mapped to the resource elements _{(k, l) p, μ} , k, and l in which the Table 1 and Table 2 Given in the case, and respectively represent the frequency index and time index within an SS/PBCH block. The time domain location that the WTRU monitors for possible SS/PBCH blocks may be predetermined.

In another example, different types of SS blocks and their mapping to time slots and subframes can be addressed. The SS block type may include a special SS block, a regular SS block, a blank SS block, and a measurement SS block.

A conventional SS block can be used to carry an NR Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), or a Physical Broadcast Channel (PBCH).

Special SS blocks can be used to carry the downlink (DL) control channel and the uplink (UL) control channel. A special SS block can be used to carry the paging channel. In addition, special SS blocks can be used to carry one or more micro time slots.

Blank SS blocks can be used to reserve resources for future proof and forward compatibility purposes. Blank SS blocks can be blank or almost blank, depending on their design.

The measurement SS block can be used to carry the MRS or channel status information reference signal (CSI-RS).

Figure 5A shows an exemplary conventional SS block 500A that includes N _reg OFDM symbols, where N _reg is equal to four (4). As described previously, the conventional SS block may include one OFDM symbol for the PSS, one OFDM symbol for the SSS, and two OFDM symbols for the PBCH. As shown in FIG. 5A, the PSS, SSS, and PBCH may be arranged in the order of PSS, PBCH, SSS, and PBCH.

Figure 5B shows an exemplary special SS block 500B carrying a DL control channel. Figure 5C shows another special SS block 500C carrying a UL control channel. The special SS block may include N _spec OFDM symbols to carry a DL control channel, a paging channel, or a UL control channel. N _spec is equal to two (2). As shown in FIGS. 5B and 5C, the special SS block may include two OFDM symbols for the DL control channel or the UL control channel, respectively.

Figure 5D shows an exemplary special SS block 500D carrying a micro time slot comprising two ( N _spec ) OFDM symbols. Figure 5E shows an exemplary blank SS block 500E carrying empty N ( N _blank ) OFDM symbols.

FIGS. 6A to 6F show various examples 600A to 600F that combine blocks in FIGS. 5A to 5E. Figure 6A shows an exemplary SS block 600A combining the following: a DL control channel 614 (special SS block shown in Figure 5B), two PSS/PBCH/SSS blocks 602, 604 (in Figure 5A) The two conventional SS blocks are shown, a blank SS block 602 (as shown in Figure 5E), and a UL control channel 616 (the special SS block shown in Figure 5C). Those blocks may include 2, 4+4, 2, and 2 OFDM symbols, respectively.

Figures 6B through 6F show different exemplary combinations of SS blocks contained within Figure 6A. Figure 6B shows a different exemplary SS block 600B in which the blank block 606 is moved to a position between the two PSS/PBCH/SSS 602, 604. Figure 6C shows another different exemplary SS block 600C in which the blank SS block 606 is divided into two parts, and each of the divided parts 608, 610 (each corresponding to an OFDM symbol) is located in a conventional The right side position of the PSS/PBCH/SSS blocks 602, 604. In Figure 6D, successive conventional PSS/PBCH/SSS blocks 602, 604 are located between one partition 608 of the blank SS block and another partition 610. In FIG. 6E, the blank SS block 606 is located at a position before the two consecutive PSS/PBCH/SSS blocks 602, 604. Figure 6F shows a block combination similar to Figure 6A except that the DL control channel 614 is replaced with a micro time slot channel 612. The above SS blocks may be included in one or more SS bursts (eg, SS burst sets). The SS burst set can be placed in a radio frame. "Continuous or localized" or "discontinuous or decentralized" methods can be used in different situations.

For continuous or localized methods, SS blocks or SS bursts can be placed from the beginning of each P-radio frame until all SS blocks or SS bursts have been consumed. P can be 0.5, 1, 2, 4, 8, and 16. For SS blocks or SS bursts, there may be some offset from the beginning of the radio frame. The offset can have a zero value or a non-zero value. There may be some gaps between two consecutive SS blocks or SS bursts. For discontinuous or decentralized methods, SS bursts can be placed from the beginning of the SS burst set, and the SS bursts can be evenly distributed within the SS burst set. Based on the SS burst set period, the number of SS blocks can be defined accordingly. For example, for N _{radio frames} of the set SS burst cycle may be defined accordingly the total N _{radio frames} of each set of SS burst.

For L SS blocks in the SS burst set and N _{ss_brusts} SS bursts, the number of SS blocks sent by each SS burst can be determined according to the following formula:

For L SS blocks in the SS burst set and when N _{ss_brusts} = N _{radio frames} , the number of SS blocks sent by each SS burst can be determined according to the following formula:

The SS burst set may include one or more SS blocks of bits within the SS burst set period. For example, the SS burst set may include L SS blocks and L may be equal to 1, 2, 4, 8, or 64. The SS burst collection period may be N _{radio frames} , which may be equal to two radio frames.

Figures 7A through 7D show examples of conventional SS block mapping to SS burst sets. In Figure 7A, when L = 1, a single SS block can be placed in an SS burst set period with two radio frames, for example at the beginning of a periodic loop. In FIG. 7B, when L=2, the two SS blocks can be placed in the SS burst set period with two radio frames, for example, each SS block is placed in each of the two radio frames. The beginning of the box. In Figure 7C, when L = 4, four SS blocks can be placed in the SS burst set period with two radio frames. The first and second SS blocks can be placed in the first radio frame, and the third and fourth SS blocks can be placed in the second radio frame. In Figure 7D, when L = 8, eight SS blocks can be placed in the SS burst set period of the two radio frames. SS blocks #1, 2, 3, and 4 can be placed in the first radio frame, and SS blocks #5, 6, 7, and 8 can be placed in the second radio frame.

The SS block, burst, and burst set may be SS block/cluster designs that are dependent on carrier frequency. There may be one SS block/cluster multiplex and mapping for one carrier frequency or band, and there may be another SS block/cluster multiplex and mapping for another carrier frequency or band. For example, SS block/cluster multiplexing and mapping schemes can be used for lower frequencies (eg, below 6 GHz), while another SS block/plex multiplex can be used for higher frequencies (eg, above 6 GHz) and Mapping scheme. In addition, there may be different SS block/cluster multiplex and mapping schemes for stand-alone and non-standalone SS block/cluster designs. Further, there may also be SS block/cluster designs that rely on licensed or unlicensed bands.

In one example, system information (SI) may be delivered in a periodic manner, on an as-demand basis, or simultaneously in a periodic and on-demand manner. Periodic and on-demand SI delivery can be stored in the system. When the WTRU requests SI#X (or a set of SI#X), the indicator for the SI#X may be set to "1" or turned on. The WTRU may first check the SI Delivery Indicator (SIDI) before requesting the SI. This may allow SI to be shared between different WTRUs. The SIDI can be carried in a broadcast signal or broadcast channel, such as Minimum System Information (MSI), Remaining Minimum System Information (RMSI), PBCH, Auxiliary Broadcast Signal or Channel, or a combination thereof.

The association between SS blocks, RMSI, and other system information (OSI) can be established. RMSI and OSI can be associated with an SS block index. The SS block may be a time/frequency block composed of the PSS-PBCH-SSS-PBCH described herein. Further, the OSI can also be associated with the RMSI. The WTRU may explicitly receive information about which signal or channel the OSI may be associated with. For example, the WTRU may receive an OSI receipt of a flag or other indication that may be associated with an SS/PBCH block or RMSI. This or other indication can be carried in the SS/PBCH block, NR-PBCH or RMSI. A WTRU may be associated with both an SS/PBCH block and an RMSI. Alternatively, the WTRU may receive an implicit indication as to which block the WTRU may be associated with. For example, if the SS/PBCH block is closer in time to the OSI, the WTRU may be associated with an SS/PBCH block. The WTRU may be associated with the RMSI if the RMSI is closer in time to the OSCI. The explicit indication may override the implicit indication for the WTRU to determine the association. The association can be applied to other signals and/or channels, such as synchronization signals, control channels, data channels, or reference signals.

The WTRU may monitor or measure the best SS block. The WTRU may also discover the RMSI or OSI based on the best SS block based on the association between the SS block and the RMSI or OSI. A broadcast signal or broadcast channel (e.g., PBCH) may indicate a quasi-co-location (QCL) for the SS block and the RMSI or OSI. If the same beam has been used for the SS block and RMSI or OSI, the WTRU may not need to perform a beam scan to discover the RMSI or OSI. When the RMSI or OSI uses a different configuration than the SS block, the beam direction, beamwidth, and beam repetition can be specifically configured.

In an example, if the SS block is a QCL associated with the RMSI or OSI, the WTRU may assume that the RMSI or OSI has the same beam or the same beam direction as the SS block. The WTRU may not need to perform beam scanning for RMSI or OSI. Otherwise, the WTRU may need to perform a beam scan. An indicator (eg, a bitmap indicator) can be used to indicate whether the beam directions are the same for the RMSI or OSI associated with the SS block.

In an example, if the beamwidth indicator indicates a different beamwidth but the QCL is indicated (the same beam direction), the WTRU may not need to perform beam scanning. Otherwise, the WTRU may need to perform a partial or global beam scan. An indicator (eg, a bitmap indicator) can be used to indicate whether the beamwidth is the same for the RMSI associated with the SS block.

In an example, if the beam is repeated, the WTRU may receive an indication of how the beam was repeated or how many SS block beams have been repeated. The WTRU may use a time location associated with the SS block, where the beam may be repeated for RMSI and/or OSI. An indicator (eg, a bitmap indicator) can be used to indicate whether the beam directions are the same for the RMSI associated with the SS block. Further, if the indicator specifies that the beam is repeated for the RMSI or OSI associated with the SS block, the WTRU may assume that the Rth order beam is repeated for the RMSI and/or OSI. The repetition factor R can be indicated within a broadcast signal or broadcast channel (eg, PBCH, RMSI, OSI, PSS, or SSS). Different repetition factors can be used for RMSI and OSI. Moreover, different repetition factors can be used for different cells (eg, one repetition factor can be used for the serving cell and another repetition factor can be used for the non-serving cell).

In the above example described for periodic OSI, a similar approach can be used for RMSI. For "aperiodic SI or OSI" or "on-demand SI or OSI", the WTRU may request a combination of beam and SI via SS block index feedback and SI request signals. The WTRU may request a particular SI to be delivered on a particular beam for SI delivery. The WTRU may discover the best SS block and feed back the SS block index for the gNB, which may use the same beam or beam ID associated with the SS block index to transmit the SI or OSI. The WTRU may wait until the next time location associated with the SS block index to receive the SI or OSI. Alternatively, the WTRU may wait for a fixed time (eg, a time offset) to receive the SI or OSI. The time offset can be T OFDM symbols, T time slots, T micro time slots or T ms, and the like.

Figure 8 shows an example 800 of system information/other system information (SI/OSI, SI or OSI) delivery. In order for the SI/OSI to be shared by the WTRU in an on-demand operation, an indicator (eg, a mapping indicator or a bit indicator Qn for the number n (SI#n) of SI/OSI) may indicate SI/OSI transmission. The status, for example, whether SI#n is transmitted. When SI#n is being transmitted, Qn can be set to "1" ("ON"), otherwise it is set to "0" ("OFF").

When the WTRU requests the number x (SI#x) of SI/OSI, the bit indicator Qx for the number x of SI/OSIs may be set to "1". The indicator Qx can be carried within a broadcast signal or broadcast channel such as RMSI. The WTRU may first read the RMSI before making a request for SI#x. The WTRU may attempt to request SI#x (802), and the WTRU may read a broadcast signal (804) containing Qx such as RMSI. The WTRU then finds if Qx is set to "1" or "0" (806). If Qx is set to "1" indicating that the corresponding SI#x is transmitting, the WTRU may attempt to read SI#x (818) transmitted within the subsequent broadcast signal.

If the WTRU successfully reads SI#x, it will terminate the SI/OSI delivery process. If the WTRU is unable to read SI#x within subsequent transmissions, the WTRU may continue to attempt to read SI#x transmitted within subsequent transmissions while the counter or timer is running (820). If the counter or timer expires, the WTRU may determine if Qx is "1" (808).

If "Qx" is "0", the WTRU may need to send a request for SI#x (810). The WTRU may wait for the back shift time or apply the back shift power before sending the request. The WTRU may determine the backshift time based on prioritization or latency requirements. The back shift time (or backward shift indicator, backward shift power, etc.) may be enlarged or reduced based on the priority order. For example, if the priority order is high, the back shift time can be reduced, or the backward shift power can be appropriately scaled. Conversely, if the priority order is low, the back shift time can be amplified, or the backward shift power can be appropriately scaled. In another example, if the latency requirement is low (eg, high latency), the backshift time may be amplified, or the backward shift power may be scaled appropriately. Conversely, if the latency requirement is high (eg, low latency), the backshift time can be reduced, or the backward shift power can be scaled appropriately. Different back-shifting processes or post-migration processes (back-shifting time, backward-shifting power, etc.) combinations may be used based on the RACH prioritization. The WTRU may determine the back-shift time based and/or the backward shift power on other parameters or conditions (eg, mobility) other than the priority order or latency requirements. Similarly, power boosts such as power ramping steps or initial transmit power may be based on RACH prioritization or latency requirements. For example, for high priority RACH or low latency RACH, the power boost step size can be large. For low priority RACH or high latency RACH, the power boost step size can be small. For another example, the initial transmission power may be large for a high priority RACH or a low latency RACH. For low priority RACH or high latency RACH, the initial transmission power can be small.

Thereafter, the WTRU may determine whether the request for SI#X has a high priority or low latency requirement (812). If so, the WTRU may wait for a zero back time or a small back time or apply the appropriate back power and send a request for SI#x (814). Otherwise, the WTRU may wait for a random back-off time or apply appropriate back-shift power (816) before sending the request. The WTRU may apply the appropriate power boost step and/or initial transmit power and send a request for SI#x based on RACH and SI prioritization or latency, and the like.

When configuring or indicating the association between the PRACH preamble, the PRACH resource, and the SI, the WTRU may send the request via a Physical Random Access Channel (PRACH) preamble or a random access channel RACH resource (such as RACH message 1 or 3). Upon receiving a request from the WTRU for SI#x, the gNB may set the corresponding indicator Qx to "1" and start transmitting SI#x L times or L times transmissions to SI#x. If the request is sent via the PRACH preamble or RACH message 1, then L can be a predefined value. If the request is sent via RACH message 3, then L may be a predefined value, or L may be indicated in RACH message 3 along with the request for SI#x. Parameters such as estimated power, path loss, coverage, etc. can be used to determine L.

SI#x may be SIB#x, System Block (SIB) set (eg, SIB Set #x), SIB subset (eg, SIB Subset #x), SI Fragment (eg, SI Fragment #x), and the like. Requests for all SIBs can be included in the request for SI#x. For example, for the purpose of requesting simultaneous delivery of all SIBs, a specific RACH preamble, RACH message 1 may be reserved.

Figure 9 shows another example 900 of system information/other system information (SI/OSI, SI or OSI) delivery. Some elements 902 to 914, 924 to 928 are similar to (802 to 808, 818 and 820, and 810 to 816) in FIG. Elements 916, 918, and 920 are newly added in Figure 9.

At 916, the WTRU determines whether the association of the SS block with the PRACH is indicated to the WTRU from the gNB. The indication may be communicated to the WTRU via a communication (eg, a broadcast signal or channel), system information (such as residual minimum system information (RMSI) or other system information (OSI)), RRC messaging, paging or random access channels, and the like. Once the WTRU receives such an indication for association, the WTRU may determine an association between the SS block and the PRACH. At 918, if the association is not indicated, the WTRU may send a request for SI#x via RACH message 3, where the WTRU indicates the number of transmissions (L) for SI#x. At 920, if the association is indicated, the WTRU may send the request via PRACH Preamble or RACH Message 1, and may use a predetermined number of (L) transmissions for SI#x. At 924, the WTRU determines if the request has a high priority or low latency requirement. At 926, if the request has a high priority order, the WTRU waits for a zero back time or a small back time and then sends the request. At 928, if the request does not have a high priority order, the WTRU waits for a random backhaul time and then sends the request. The backward shift indication can be scaled up and down based on the priority order of the RACH. The back shift can be applied to a random back shift time or a power back shift that can be based on the priority order of the RACH. A RACH can have two or more priority categories or levels. Depending on the order of precedence, the back shift can be scaled appropriately to meet this prioritization requirement.

The transmitted SS block may be indicated to the WTRU. If the WTRU is indicated, the WTRU may monitor those indicated SS blocks transmitted (e.g., a subset of the transmitted SS blocks), otherwise the WTRU may monitor all SS blocks. The indication can be carried in system information (such as RMSI or OSI), broadcast channel (eg, NR-PBCH), paging, or RACH. For a monitored SS block, the WTRU may discover the SS block associated with the DL beam. The WTRU may send a UL signal associated with the SS block to indicate a DL beam or SS block. The gNB or Transmission Receive Point (TRP) may use the received UL signal(s) from the WTRU to transmit the associated DL signal to the WTRU. PRACH can be used for this purpose. The PRACH preamble, resource, or beam may be used to indicate to the gNB or TRP an SS block (e.g., the best SS block) or a DL beam (e.g., the best DL beam) for the WTRU. When a WTRU selects a PRACH preamble, resource, and/or beam and transmits to the gNB or TRP using the selected PRACH preamble, resource, and/or beam, the gNB or TRP may know the SS block and/or DL beam for the WTRU. .

The WTRU may also request SI delivery from the gNB or TRP via the UL signal. The UL signal can be associated with both the SI and SS blocks. The WTRU may request simultaneous SI and SS block transmissions via the UL signal associated with the DL signal. There may be an association between the UL signal, the PRACH, the physical uplink control channel (PUCCH), and the UL beam; additionally/alternatively, the DL signal, SI, SS block, PBCH, RMSI, OSI, and DL beam may be associated. .

The PRACH preamble, resource or beam may be used to indicate to the gNB or TRP the requested SI or DL beam for the WTRU. When the WTRU selects a PRACH preamble, resource, and/or beam and transmits to the gNB or TRP using the selected PRACH preamble, resource, and/or beam, the gNB or TRP may know the requested SI, SS block for the WTRU. And / or DL beam.

The following can be used for association of UL signals: PRACH preamble or sequence; PRACH orthogonal cover code (OCC); PRACH resources (eg, time and/or frequency resources); beams (eg, Tx/Rx beams); channel status information (CSI) feedback; CQI; or any combination thereof.

The following can be used for association of DL signals: SS block index; SS block; PSS, SSS; PBCH; DMRS; SI; RMSI; OSI; CSI-RS; paging; or any combination of the above.

In an example, a PRACH resource may be used to indicate an SS block index, and a PRACH preamble may be used to indicate SI. The SS block index #y can be indicated using PRACH #x. A simple association may be x = y; that is, the SS block index #x may be indicated using PRACH #x, and the SS block index #y may be indicated using PRACH #y, and so on. In addition, the PRACH preamble #w can be used to indicate SI #z. A simple association may be w=z; that is, the PRACH preamble sequence #w may be used to indicate SI #w, and the PRACH preamble sequence #z may be used to indicate SI #z, and so on. The WTRU may select PRACH resource #x and may use the selected PRACH resource #x to transmit PRACH Preamble #w to indicate or feedback ss block index #y and request SI #z jointly or simultaneously. In this example, the PRACH resources may be time resources, frequency resources, code resources, beam resources, time and frequency resources, or a combination thereof. Moreover, in this example, the PRACH preamble can be a preamble sequence, a preamble OCC, a preamble format, or a combination thereof.

In an example where the PRACH resource and the PRACH preamble are not used to indicate SI to the WTRU, the WTRU may use the RACH message 3 to indicate the SS block index and request the SI. In a scenario, the WTRU may include the SS block index in the RACH message 3 (eg, a payload to gNB or TRP and a transport message 3 with an SS block index). In another scenario, the WTRU may include an SI request, such as SI(s) that the WTRU may request within RACH message 3 (eg, a payload to gNB or TRP and a transmission message with the requested SI information 3 ). In another scenario, the WTRU may include both the SS block index and the SI request in the RACH message 3 (eg, payload to gNB or TRP and transport message 3 with SS block index and requested SI information) . If the association between the SS block index and the PRACH is configured and indicated to the WTRU, the WTRU may use the PRACH Preamble or Message 1 to indicate and reward the SS block index. Otherwise, the WTRU may use RACH message 3 to indicate and reward the SS block index.

In another example, the RACH resource and the PRACH preamble may be used to indicate the SS block index and SI. Alternatively, the RACH resource and the PRACH preamble group may be used to indicate the SS block index, and the SI may be indicated using the PRACH preamble within the PRACH preamble group. It is also feasible to use the RACH resource and the PRACH preamble to indicate the SS block (or SS block index) and request other combinations of SS or SS(s).

The WTRU may assume that the PDCCH transmitting the PDSCH of the RACH message 2 and the Demodulation Reference Signal (DMRS) of the DMRS may be QCL-compliant with the SS/PBCH block selected by the WTRU for RACH association and transmission. The WTRU may assume that the PDCCH transmitting the RACH message 3 and/or the DMRS retransmitting the grant may be QCL-compliant with the SS/PBCH block selected by the WTRU for RACH association and transmission. The WTRU may assume that the DMRS of the PDSCH transmitting the RACH message 4 and the DMRS of the PDCCH may be QCL-compliant with the SS/PBCH block selected by the WTRU for RACH association and transmission. However, the WTRU may perform SS/PBCH block reporting, SS block SS block reporting, or beam reporting during the RACH procedure. The gNB may indicate to the WTRU to report a gNB Tx beam, SS block, or SS/PBCH block index during the RACH procedure. This report may trigger an indication that the SS/PBCH block, SS block, or beam report may be carried in the SS block, the SS/PBCH block, the NR-PBCH, the random access response (RAR), the RACH message 2, or the message 4. The SS/PBCH block, SS block index or beam report(s) may be carried in RACH message 3, RACH message 1, RACH preamble, or other feedback signal or channel. If the WTRU receives an indication for an SS/PBCH block, an SS block, or a beam report, the WTRU may use the indicated SS/PBCH block, SS block, or beam for the remaining RACH procedures and override the preset QCL association. The WTRU may use the reported SS/PBCH block, SS block or beam for RACH message 4, message 2, or other DL signal/channel reception. The SS block acknowledgement message, the SS/PBCH block acknowledgement message, or the beam acknowledgement message can be used to inform the WTRU whether to use the reported SS/PBCH block, SS/PBCH block or beam (eg, the most recently reported SS block, SS/PBCH block, or Beam). The SS/BPCH block acknowledgement message, the SS block acknowledgement message, or the beam acknowledgement message may be 1 bit or more than 1 bit, which may be included in the downlink control information (DCI) carried in the PDCCH, or may be included in the PDSCH Within the data carried (for example, RAR, RACH Message 2 or Message 4). For example, if the SS block acknowledges that the SS/BPCH block acknowledgment, or beam acknowledgment information is received and indicates "yes" or "acknowledgement", the WTRU may use the reported SS block(s), SS/PBCH block (one Or multiple), or beam(s) for reception. Otherwise, the WTRU may use the indicated SS block(s), SS/PBCH block(s), or beam(s), beam, SS block, subset of SS/PBCH blocks, Or try all beams, SS blocks, SS/PBCH blocks for reception.

An association between the SS block and the PUCCH can be established to enable efficient system operation. The SS block index can be associated with a PUCCH resource and/or sequence. This PUCCH resource may be a time/frequency resource, a PUCCH sequence, a cyclic shift, or a combination thereof.

The PUCCH resource may be associated with an SS block or an SS block index for SS block index reporting. The PUCCH time/frequency, cyclic shift elements, sequences, and/or other parameters may be associated with an SS block or an SS block index. For example, PUCCH #x may be associated with SS block #x or SS block index x. PUCCH #x may be a PUCCH resource #x, a PUCCH index, such as a time index x, a frequency index x, a time/frequency index x, a cyclic shift x, a sequence x, or a combination thereof.

When the WTRU reports an SS block x or SS block index x, the WTRU may use the associated PUSCH and its resources and/or parameters associated with the SS block or SS block index.

An association between the SS block and the physical uplink shared channel (PUSCH) can be established to enable efficient system operation. The association for the PSUCH may include PUSCH time and/or frequency resources.

An association between the SS block and a control resource set (CORESET) for RMSI or OSI can be established to enable efficient system operation. An association of CORESET(s) between RMSI and OSI can also be established. Association between the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) for the RMSI and the PDCCH and PDSCH for the OSI may also be established.

The configuration of the CORESET for RMSI may include frequency location, size (eg, number of physical resource blocks (PRBs) or number of resource block groups (RBGs), time location, period, and bias within time and/or frequency shift. Alternatively, the time position can be predefined and the period can be the same as the RMSI. The number of OFDM symbols for CORESET and the QCL between the SS block and the associated CORESET can be signaled or indicated by a signal.

Information about the system bandwidth can be indicated, for example, within the NR-PBCH and/or RMSI. If the system bandwidth is indicated, the absolute frequency position of the NR-PBCH, CORESET, RMSI, and/or OSI may be indicated. Otherwise, if the system bandwidth is not indicated, the relative frequency position of the NR-PBCH, CORESET, RMSI, and/or OSI may be indicated (eg, relative to a reference point). The reference point can be a location in the NR-PBCH location, the SS block location, and/or the time or frequency of the PSS/SSS. For example, the reference point can be the lowest or highest frequency index of the NR-PBCH, SS block, PSS, or SSS, and the like. The reference point may be an intermediate frequency index of NR-PBCH, SS block PSS, SSS, or the like.

The SS block may be associated with a corresponding PDCCH of RMSI and/or OSI and RMSI and/or OSI. Corresponding PDCCHs of OSI and/or OSI may be associated with corresponding PDCCHs of RMSI and/or RMSI. The beam associated with the SS block can be used for transmission of the RMSI and/or the corresponding PDCCH. Multiple beams associated with the SS block may be used for transmission of the OSI and corresponding PDCCH. Alternatively, a beam associated with the RMSI and/or the corresponding PDCCH may be used for transmission of the OSI and/or the corresponding PDCCH.

For each beam associated with the SS block, there may be different CORESETs for beam level interference mitigation. CORESET can be a function of the SS block index and/or beam index. Configuration or parameters of CORESET for RMSI or OSI (such as frequency location, size (eg, number of physical resource blocks (PRBs) or number of resource block groups (RBGs)), time position, period, time, and/or frequency offset The shift, the number of OFDM symbols for CORESET, and/or the QCL between the SS block and the associated CORESET, etc.) may depend on the SS block index, the beam index, and/or the cell identity. For example, different frequency shifts or offsets of the CORESET per cell can be used for cell level interference mitigation. In another example, different frequency shifts or offsets of CORESET per cell may be associated with SS block or SS block index, beam index, actual transmitted SS block or SS block index, actual transmitted beam or beam index, Or cell identity and so on. The configuration or parameters of the CORESET for RMSI, OSI, or other channels may depend on the time slot index, the micro time slot index, the OFDM symbol index, the subframe index, the frame index, or the system frame number. The configuration or parameter of the CORESET for RMSI, OSI or other channel may be a function of at least one of: SS block or SS block index (within time or frequency), beam index, actual transmitted SS block or SS block index (at Time or frequency), actual transmitted beam or beam index, cell identity, time slot index, micro time slot index, OFDM symbol index, subframe index, frame index, or system frame number.

The CORESET can be indicated by using another CORESET based on the actual transmitted SS block (or beam), or the maximum number of SS blocks (or beams). The WTRU-specific CORESET may be based on the SS block (or beam) detected by the WTRU.

The examples provided herein can be applied to RMSI, OSI, control channels, data channels, or a combination thereof.

The CSI-RS can be multiplexed on the same OFDM symbol as the SS block. If the time/frequency resources of the CSI-RS conflict with the SS block, the following options may be considered: the CSI-RS may be punctured and ignored; and/or the SS block may be punctured and ignored.

An association between the SS block and the CSI-RS can be established. The CSI-RS can be associated with an SS block index. A QCL between SS blocks can be established and indicated. A QCL between CSI-RSs can be established and indicated. A QCL between the SS block and the CSI-RS can also be established and indicated. The repetition factor R for the SS block and/or CSI-RS may be indicated. Different repetition factors R (eg, R1 and R2) may be used and indicated for the SS block and the CSI-RS, respectively.

SS blocks can be identified within wideband operation. The SS block may be identified via at least one of: an SS block time index; an SS block frequency index; and/or a bandwidth portion index.

When the SS block is in non-broadband operation, the SS block can be identified by the SS block time index. When the SS block is in wideband operation, the SS block can be identified by the SS block frequency index and the SS block time index. Regardless of the various operations, multiple SS blocks can coexist in the same time instance in the frequency domain. The SS block can be identified by the bandwidth partial index and the SS block time index. Global indexing for SS blocks within both time and frequency can also be used. This indexing can cover frequency and time indexing. For example, the global SS block index may start at the lowest frequency index followed by the higher frequency index; after the frequency indexing is completed, the global SS block index may start at the next time index, and for each time index, The SS block index can start at the lowest frequency index followed by the higher frequency index and continue until all time indexing is complete.

Figure 10 shows a flow diagram 1000 of how a WTRU acquires a set of SS/PBCH blocks (or SS blocks), a "synchronization signal (SS) set", which is configurable under various multiplex or resource allocation schemes. First, the WTRU receives information or an indicator indicating the set of SSs from at least one access point associated with the WTRU (1002). The WTRU then monitors the identified set of SSs (1004). The WTRU then acquires the PSS or SSS from the identified set of SSs (1006). Based on the acquired PSS or SSS, the WTRU may determine the Block Type (BT) of the SS/PBCH block contained within the SS set (1008). Based on the block type (BT), the WTRU may detect or decode one or more PBCHs within the SS/PBCH block (1010). The location of the PBCH is flexible within the SS/PBCH block and depends on the block type of the SS/PBCH block. The block type may be determined by a number of factors, such as PBCH resource allocation, multiplexing, RE mapping, DMRS location for PBCH, TDM or FDM. Finally, at step 1012, the WTRU acquires the PBCH or the entire set of SSs based on the block type of the SS/PBCH block.

Based on the block type of the SS/PBCH block, the WTRU may discover the location of the PBCH within the SS/PBCH block. In addition, the resource element (RE) allocation of the PBCH is a function of the block type. The RE mapping and multiplexing of the PBCH is a function of the OFDM symbol index. The DMRS location for the PBCH is a block type function. The RE mapping for DMRS within the PBCH is a function of the OFDM symbol index and the cell ID.

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

100‧‧‧Communication system

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

104‧‧‧Radio Access Network (RAN)

106‧‧‧ Core Network (CN)

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧Transmission/receiving components

124‧‧‧Speaker/Microphone

126‧‧‧Keypad

128‧‧‧Display/Touchpad

130‧‧‧ Non-removable memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧Other peripheral devices

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

162‧‧‧Action Management Entity (MME)

164‧‧‧Service Gateway (SGW)

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

180a, 180b, 180c‧‧‧g Node B (gNB)

182a, 182b‧‧‧Access and Mobility Management (AMF)

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

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

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

200‧‧‧Synchronous Signal (SS)

300A, 300B, 300C, 300D, 300E, 300F, 300G, 300H, 300I, 300J, 300K, 500A, 500B, 500C, 500D, 500E, 600A, 600B, 600C, 600D, 600E, 600F‧‧‧ exemplary synchronization signals (SS) block

302, 304, 310, 312, 314‧‧‧ Physical Broadcast Channel (PBCH)

306‧‧‧Primary Synchronization Signal (PSS)

308‧‧‧Auxiliary Synchronization Signal (SSS)

316, 318‧‧ ‧ paging channel

320, 322‧‧‧Channel Status Information Reference Signal (CSI-RS)

400A, 400B, 402, 404, 406, 408‧‧‧ SS/PBCH blocks

602, 604‧‧‧PSS/PBCH/SSS blocks

606‧‧‧Blocks

Section 608, 610‧‧

612‧‧‧Microslot channel

614‧‧‧DL control channel

616‧‧‧UL control channel

800, 900‧‧‧ examples

802, 804, 806, 808, 810, 812, 814, 816, 818, 820, 902, 904, 906, 908, 910, 912, 914, 916, 918, 920, 922, 924, 926, 928 ‧ element

1000‧‧‧flow chart

1002, 1004, 1006, 1008, 1010, 1012‧ ‧ steps

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

A more detailed understanding can be obtained from the following description taken in conjunction with the accompanying drawings, in which like reference numerals System diagram of an exemplary communication system of various embodiments; FIG. 1B is a system diagram showing an exemplary wireless transmission/reception unit (WTRU) that may be used within the communication system illustrated in FIG. 1A, in accordance with an embodiment 1C is a system diagram showing an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) that can be used within the communication system shown in FIG. 1A, according to an embodiment; The figure is a system diagram showing another exemplary RAN and another exemplary CN that can be used inside the communication system shown in FIG. 1A according to an embodiment; FIG. 2 shows the SS burst and the SS block. Examples; Figures 3A through 3K show examples of exemplary SS block designs; Figures 4A through 4B show examples of SS block designs; Figure 5A shows examples of carrying PBCH, PSS, and SSS Example of a SS block design; Figure 5B shows a DL control An example of a special SS block for a channel; Figure 5C shows an example of a special SS block carrying a UL control channel; Figure 5D shows an example of a special SS block carrying a micro time slot; Figure 5E shows an example of carrying An example of a blank SS block of a null OFDM symbol; FIGS. 6A to 6F illustrate an example of mapping an SS block type to a time slot; FIGS. 7A to 7D illustrate a common to two radio frames An example of a conventional SS block mapping of a set of SS bursts with periods and L equal to 1, 2, 4, and 8, respectively; Figures 8 and 9 are flowcharts of a second exemplary SI/OSI transfer method; and FIG. 10 is a flowchart of FIG. Flowchart of an exemplary process for receiving a PDCH or SS/PBCH block.

Claims (12)

A method implemented in a WTRU for receiving a plurality of messages from a base station, the method comprising: receiving a synchronization signal (SS) and a physical broadcast channel (PBCH) to be monitored (SS/ An indication of the PBCH block; acquiring the primary synchronization signal (PSS) and the secondary synchronization signal (SSS) at a fixed location within the indicated SS/PBCH block; and based on the determined SS/PBCH block type, Acquiring one or more PBCHs and a subsequent entire SS/PBCH block; wherein the SS/PBCH block includes four symbols and the PBCH is located on three symbols of the four symbols and each of the PSS and SSS is located One of the four symbols is different from each other. The method of claim 1, wherein the PBCH symbols each include its own frequency multiplex demodulation reference symbol (DMRS). The method of claim 1, wherein the PBCH comprises a DMRS located on a resource determined according to an OFDM symbol index. The method of claim 1, wherein the SSS is located on a symbol between two symbols including the PBCH. The method of claim 1, wherein the PSS and SSS are located on subcarriers between 56 and 182 within their respective symbols. The method of claim 1, wherein the PBCH is located between 0 and 55 in the two symbols of the three symbols and on the subcarrier between 183 and 239 and 0 to the third symbol On subcarriers between 239. A wireless transmit/receive unit (WTRU) for receiving a plurality of information from a base station, the WTRU comprising: a processor and a receiver configured to: receive a synchronization signal (SS) and an entity to be monitored An indication of a Broadcast Channel (PBCH) (SS/PBCH) block; acquiring the primary synchronization signal (PSS) and the secondary synchronization signal (SSS) at a fixed location within the indicated SS/PBCH block; and based on the location Determining an SS/PBCH block type, acquiring one or more PBCHs and a subsequent entire SS/PBCH block; wherein the SS/PBCH block includes four symbols and the PBCH is located on three symbols of the four symbols and the PSS And each of the SSSs is located on a different one of the four symbols. The WTRU as claimed in claim 7, wherein the PBCH symbols each include its own frequency multiplex demodulation reference symbol (DMRS). The WTRU as claimed in claim 7, wherein the PBCH comprises a DMRS located on a resource determined according to an OFDM symbol index. The WTRU as claimed in claim 7, wherein the SSS is located on a symbol between two symbols including the PBCH. The WTRU as described in claim 7 wherein the PSS and SSS are located on subcarriers between 56 and 182 within their respective symbols. The WTRU as claimed in claim 7, wherein the PBCH is located between 0 and 55 in the two symbols of the three symbols and on the subcarrier between 183 and 239 and 0 to the third symbol On subcarriers between 239.