[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2019099443A1 - Multiples occasions de surveillance au niveau d'un ensemble de ressources de commande de canal d'accès aléatoire - Google Patents

Multiples occasions de surveillance au niveau d'un ensemble de ressources de commande de canal d'accès aléatoire Download PDF

Info

Publication number
WO2019099443A1
WO2019099443A1 PCT/US2018/060907 US2018060907W WO2019099443A1 WO 2019099443 A1 WO2019099443 A1 WO 2019099443A1 US 2018060907 W US2018060907 W US 2018060907W WO 2019099443 A1 WO2019099443 A1 WO 2019099443A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
rach
index
preamble
monitoring
Prior art date
Application number
PCT/US2018/060907
Other languages
English (en)
Inventor
Kyle Jung-Lin Pan
Fengjun Xi
HaoHao QIN
Chunxuan Ye
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2019099443A1 publication Critical patent/WO2019099443A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0035—Resource allocation in a cooperative multipoint environment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/085—Random access procedures, e.g. with 4-step access with collision treatment collision avoidance

Definitions

  • a fifth generation or Next Gen (NG) wireless systems may be referred to as 5G or New Radio (NR).
  • a previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).
  • the RACH CORESETs corresponding to the multiple RACH CORESET monitoring occasions may be multiplexed using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a joint TDM and FDM technique.
  • a wireless transmit/receive unit may identify which one of the multiple RACH CORESET monitoring occasions to use based on a preamble index the WTRU selects for a random access operation or based on a synchronization signal block (SSB) index.
  • the WTRU may determine whether to use the preamble index or the SSB index based on a mapping relationship between the preamble indices and SSB indices configured for the WTRU.
  • the WTRU may use either a preamble index or a SSB index to determine the monitoring occasion. If there is a one-to-many relationship between the SSB indices and the preamble indices, the WTRU may use an SSB index to determine the monitoring occasion. If there is a many-to-one relationship between the SSB indices and the preamble indices, the WTRU may use a preamble index to determine the monitoring occasion.
  • the WTRU may monitor a physical downlink control channel (PDCCH) at the identified monitoring occasion.
  • PDCCH physical downlink control channel
  • the WTRU may take into account the total number of the RACH CORESET monitoring occasions configured for the monitoring time period when determining which of the multiple RACH
  • the WTRU may divide the preamble index or the SSB index by the number of the RACH CORESET monitoring occasions configured for the monitoring time period and select the RACH CORESET monitoring occasion based on a remainder of the division operation.
  • the monitoring time period described herein may correspond to one slot or multiple slots.
  • the monitoring time period may be inside a random access response (RAR) window.
  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A.
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A.
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A .
  • FIG. 2 is a diagram illustrating an example of a PRACH format slot.
  • FIG. 3 is a diagram illustrating an example of a RACH slot Type.
  • FIG. 4 is a diagram illustrating an example of a RACH slot Type.
  • FIG. 5 is a diagram illustrating an example of a RACH slot Type.
  • FIG. 6 is a diagram illustrating an example of having three synchronization signal (SS) blocks within a slot.
  • FIG. 7 is a diagram illustrating an example of having three SS blocks within a slot.
  • FIG. 8 is a diagram illustrating an example of having two SS blocks within a slot.
  • FIG. 9 is a diagram illustrating an example of having one SS block within a slot.
  • FIG. 10 is a diagram illustrating an example of a subframe/slot structure for PRACH transmission.
  • FIG. 11 is a diagram illustrating an example of monitoring time division multiplexed (TDMed) control resource sets (CORESETs) based on a preamble index.
  • TDMed time division multiplexed
  • CORESETs control resource sets
  • FIG. 12 is a diagram illustrating an example of monitoring frequency division multiplexed (FDMed) CORESETs based on a preamble index.
  • FDMed frequency division multiplexed
  • FIG. 13 is a diagram illustrating an example of joint FDMed and TDMed RACFI CORESETs.
  • FIG. 14 is a diagram illustrating an example of monitoring a TDMed monitoring occasion according to a preamble index.
  • FIG. 15 is a diagram illustrating an example of monitoring a FDMed monitoring occasion according to a preamble index.
  • FIG. 16 is a diagram illustrating an example of monitoring joint TDMed and FDMed RACFI CORESETs within a slot.
  • FIG. 17 is a diagram illustrating an example of monitoring joint TDMed and FDMed RACFI CORESETs within a slot.
  • FIG. 18 is a diagram illustrating an example of monitoring a RACFI CORESET based on a mapping relationship between preamble indices and SSB indices.
  • FIG. 19 is a diagram illustrating an example of configuring RACFI CORESETs for different UL carriers.
  • FIG. 20 is a diagram illustrating an example of monitoring RACFI CORESETs for different UL carriers.
  • FIG. 21 is a diagram illustrating an example of frequency hopping of RACFI CORESETs among different RACFI occasions.
  • FIG. 22 is a diagram illustrating an example of monitoring RACFI CORESETs for multiple UL carriers.
  • FIG. 23 is a diagram illustrating an example of different linkage among WTRUs.
  • FIG. 24 is a diagram illustrating an example of configuring different RACFI COREST frequency offsets for different uplink (UL) bandwidth parts (BWPs) linked to the same downlink (DL) BWP.
  • UL uplink
  • BWPs bandwidth parts
  • FIG. 25 is a diagram illustrating an example of separating PRACFI for channel state information - reference signal (CSI-RS) from PRACFI for SSB.
  • CSI-RS channel state information - reference signal
  • FIG. 26 is a diagram illustrating an example of having PRACFI for CSI-RS as a subset of PRACH for SSB.
  • FIG. 27 is a diagram illustrating an example of having different mapping patterns between CSI- RS and RACFI occasions.
  • FIG. 1A is a diagram of an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 1 14b.
  • Each of the base stations 114a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 1 10, and/or the other networks 112.
  • the base stations 1 14a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Flome Node B, a Flome eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 1 14a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 1 14a, 1 14b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 1 14a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (FISPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (FISDPA) and/or High-Speed UL Packet Access (FISUPA).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV- DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV- DO Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for
  • the base station 114b in FIG. 1 A may be a wireless router, Flome Node B, Flome eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE- A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required 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 any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • 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 the other networks 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1 A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • 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/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
  • a base station e.g., base stations 114a, 114b
  • the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C 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 are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a,
  • 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an "ad- hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 h, and 802.11ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 h, 802.11ac, 802.11 af, and 802.11ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 1 15 shown in FIG. 1 D 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 are depicted as part of the CN 1 15, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 162 may provide a control plane function for switching between the RAN 1 13 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N1 1 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 1 15 may facilitate communications with other networks.
  • the CN 1 15 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 1 15 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 1 15 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • FIGS. 1A-1 D In view of FIGS. 1A-1 D, and the corresponding description of FIGS. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b,
  • DN 185a-b, and/or any other device(s) described herein may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • NR 5G New Radio
  • NR may be operable with current and future mobile wireless communications systems.
  • NR may meet requirements set out by ITU-R, NGMN and 3GPP.
  • NR use cases may include, for example, extreme Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra High Reliability and Low Latency Communications (URLLC).
  • eMBB extreme Mobile Broadband
  • mMTC massive Machine Type Communications
  • URLLC Ultra High Reliability and Low Latency Communications
  • Different use cases may focus on different requirements, such as, for example, higher data rate, higher spectrum efficiency, low power and higher energy efficiency, lower latency and higher reliability.
  • a wide range of spectrum bands ranging from 700 MHz to 80 GHz may be considered for a variety of deployment scenarios.
  • path loss may become a limitation in guaranteeing a sufficient coverage area.
  • Transmission in mm wave systems may suffer from non-line-of-sight losses, e.g., diffraction loss, penetration loss, oxygen absorption loss, foliage loss, etc.
  • the base station and WTRU may need to overcome these high path losses and discover each other.
  • Utilizing dozens or even hundreds of antenna elements to generate a beam formed signal may be an effective way to compensate severe path loss (e.g., by providing significant beam forming gain).
  • Beamforming techniques may include digital, analog, and hybrid beamforming.
  • LTE initial synchronization and broadcast channel may be complex.
  • a WTRU may acquire time and frequency synchronization with a cell and may detect the Cell ID of that cell via a cell search procedure.
  • LTE synchronization signals may be transmitted at specific locations in the time domain (e.g., the Oth and 5th subframes of every radio frame).
  • LTE synchronization signals may be used for time and frequency synchronization during initialization.
  • a WTRU may synchronize sequentially to the OFDM symbol, slot, subframe, half-frame, and/or radio frame based on the synchronization signals.
  • the synchronization signals may include a Primary Synchronization Signal (PSS) (e.g., to obtain slot, subframe and/or half-frame boundary, as well as physical layer cell identity (PCI) within the cell identity group) and/or a Secondary Synchronization Signal (SSS) (e.g., to obtain the radio frame boundary, as well as enabling the WTRU to determine the cell identity group, which may range from 0 to 167).
  • PSS Primary Synchronization Signal
  • PCI physical layer cell identity
  • SSS Secondary Synchronization Signal
  • a WTRU may decode the Physical Broadcast Channel (PBCH) with the help of CRS and acquire the MIB information regarding system bandwidth, System Frame Number (SFN), and/or PHICH configuration.
  • PBCH Physical Broadcast Channel
  • SFN System Frame Number
  • PHICH Physical Broadcast Channel
  • the LTE synchronization signals and PBCH may be transmitted continuously, e.g., according to the standardized periodicity.
  • LTE Random Access (RA) procedure may be provided.
  • An eNB and/or a WTRU may use a random access procedure for at least one of: WTRU initial access (for example to a cell or eNB), reset of UL timing (for example to reset or align WTRU UL timing with respect to a certain cell), and reset of timing during handover (for example to reset or align WTRU timing with respect to the handover target cell).
  • the WTRU may transmit a certain physical random access channel (PRACFI) preamble sequence at a certain power PPRACH, which may be based on configured parameters and/or measurements, and the WTRU may transmit the preamble using a certain time-frequency resource or resources.
  • PRACFI physical random access channel
  • the configured parameters may include one or more of initial preamble power (e.g., preamblelnitialReceivedTargetPower), a preamble format based offset (e.g., deltaPreamble), a random access response window (e.g., ra-ResponseWindowSize), a power ramping factor (e.g., powerRampingStep), and/or a maximum number of retransmissions (e.g., preambleTransMax).
  • the PRACFI resources (which may include preambles or sets of preambles and/or time/frequency resources used for preamble transmission) may be provided or configured by the eNB.
  • the measurements may include pathloss.
  • the time-frequency resource(s) may be chosen by the WTRU from an allowed set or may be chosen by the eNB and signaled to the WTRU. Following WTRU transmission of a preamble, if the eNB detects the preamble, it may respond with a random access response (RAR). If the WTRU does not receive an RAR for the transmitted preamble (which may, for example, correspond to a certain preamble index and/or time/frequency resource), within an allotted time (for example, ra-ResponseWindowSize), the WTRU may send another preamble at a later time and/or at a higher power (such as, for example, higher than the previous preamble transmission by powerRampingStep).
  • RAR random access response
  • the transmission power may be limited by a maximum power, which may be configured for the WTRU as a whole (for example PCMAX) or for a certain serving cell of the WTRU (for example PCMAX, c).
  • the WTRU may wait again for receipt of an RAR from the eNB. This sequence of transmitting and waiting may continue until the eNB may respond with an RAR or until the maximum number of random access preamble transmissions (for example,
  • preambleTransMax may have been reached.
  • the eNB may transmit and the WTRU may receive the RAR in response to a single preamble transmission.
  • a particular instance of a random access procedure may be contention -based or contention-free.
  • a contention-free procedure may be initiated by a request, for example from an eNB, which may, for example, be via physical layer signaling such as a PDCCH order or by higher layer signaling such as an RRC reconfiguration message (e.g., an RRC connection reconfiguration message).
  • the signaling may include mobility control information and may, for example, indicate or correspond to a handover request.
  • the WTRU may (e.g., may autonomously) initiate a contention-based procedure for reasons which may include, for example, initial access, restoration of UL synchronization, or recovering from radio link failure. For certain events, for example, events other than recovery from radio link failure, it may not be defined or specified as to how long after such an event the WTRU may send the PRACFI preamble.
  • a network-signaled (e.g., configured by the network) PRACFI preamble may be used, e.g., by a WTRU.
  • the WTRU may autonomously choose a preamble where the preamble format and/or the time/frequency resource(s) available for preamble transmissions may be based on an indication or index (e.g., prach-configlndex) which may be provided or signaled (e.g., configured) by the eNB.
  • an indication or index e.g., prach-configlndex
  • a preamble (e.g., one of the preambles transmitted at the progressively higher transmit powers) may be detected by the eNB.
  • An RAR may be sent by the eNB in response to that detected preamble.
  • a PRACFI preamble may be considered a PRACFI resource.
  • PRACFI resources may include a PRACH preamble, time, and/or frequency resources.
  • RACH resources and PRACH resources may be used interchangeably.
  • RA, RACH, and PRACH may be used interchangeably.
  • PRACH coverage may be an issue when WTRUs are at cell edge or at low SNR regions.
  • PRACH coverage may be enhanced in NR.
  • PRACH may be transmitted with a PRACH preamble format, e.g., to avoid or mitigate inter-symbol interference and/or multi-user interference.
  • PRACH may be transmitted in different RACH slots.
  • PRACH may be transmitted with different patterns of SS blocks (e.g., three SS blocks within one slot, two SS blocks within one slot, one SS block within one slot, etc.).
  • SUL supplementary uplink
  • SUL handling for PRACH may be implemented.
  • SUL may be used to enhance the uplink coverage in NR. For example, by pairing a SUL carrier on lower frequency with a TDD/FDD carrier on higher frequency, uplink coverage may be enhanced.
  • the coverage of SUL carrier may be better than NR UL carrier in some scenarios, e.g., because the frequency is lower and more UL subframes or slots may be available.
  • two or more UL carriers may be configured for a DL carrier of the same cell.
  • one (e.g., only one) PUSCH may be transmitted.
  • a single PUSCH may be transmitted either on SUL or NR UL.
  • a single PUSCH may be transmitted across SUL and NR UL. More than one (e.g., multiple) PUSCH may be transmitted across SUL and NR UL.
  • the RACH configuration for the two or more ULs may include a same PRACH configuration index for the ULs or the RACH configuration may include different PRACH configuration indices for the respective ULs, e.g., to support the RACH transmission occasions on those ULs.
  • a carrier index e.g., SUL carrier index and/or NR UL carrier index
  • RAR random access response
  • RACH message e.g., RACH message 2
  • a WTRU may decode NR-PDCCH with RA-RNTI and may decode the corresponding NR-PDSCH for RAR.
  • the WTRU may decode the NR-PDCCH before decoding the corresponding NR-PDSCH.
  • the WTRU may compare the carrier index (e.g., UL carrier index) in RAR and the carrier index (e.g., UL carrier index) that the WTRU selects. If the carrier index in RAR and the carrier index that the WTRU selects match, the WTRU may decide that the decoded RAR is intended for the WTRU; otherwise, the WTRU may discard the received RAR.
  • the carrier index e.g., UL carrier index
  • the carrier index e.g., UL carrier index
  • a carrier index may be an index to identify which carrier (e.g., SUL carrier, NR UL carrier, autonomous UL (AUL) carrier, etc.) is to be used to carry communication between a WTRU and a gNB (e.g., from a WTRU to a gNB).
  • a carrier index may be in the form of an explicit indication (e.g., bits of information) or an implicit indication (e.g., which may be derived from other relevant information).
  • One or more parameters may be included in RAR. Examples of these parameters may include a RACH occasion index, a RACH resource index, an OFDM symbol index, a PRB index, and/or the like.
  • RACH resources may be based on slot, non-slot, a hybrid of slot/non-slot, or multiple non-slots with different durations.
  • a resource index may indicate a time resource, a frequency resource, or a combination of time and frequency resources.
  • a non slot may be a mini-slot (e.g., smaller (e.g., shorter time period) than a regular slot) or the like.
  • a non-slot may comprise K OFDM symbols (e.g., either consecutive or non-consecutive).
  • K may have a value of 1 , 2, 4 or 7.
  • the value of K may be configured in system information, e.g., in NR-PBCH, in remaining minimum system information (RMSI), or in other system information (OSI).
  • a carrier index (e.g., SUL carrier index, NR UL carrier index, etc.) may be used to determine an RA-RNTI.
  • RA-RNTI may be a function of a carrier index (e.g., an UL carrier index) and/or one or more other parameters (e.g., different RA-RNTIs may be used for different UL carrier indices). These other parameters may include RACFI occasion index, RACFI resource index, OFDM symbol index, PRB index, and/or the like.
  • RACFI resources may be based on slot, non-slot, a hybrid of slot/non-slot, or multiple non slots with different durations.
  • a resource index may indicate a time resource, a frequency resource, or a combination of time and frequency resources.
  • a non-slot may be a mini slot or the like.
  • a non-slot may comprise K OFDM symbols.
  • K may have a value of 1 , 2, 4 or 7.
  • the value of K may be configured in system information, e.g., in NR-PBCH, in RMSI, or in OSI.
  • a carrier index (e.g., SUL carrier index, NR UL carrier index) may be carried in multiple (e.g., two) RARs and used to determine RA-RNTI.
  • a carrier index in RAR may be used to confirm the RA-RNTI determined by carrier index. Double confirmation may be provided and additional protection may be achieved for determining a WTRU's own RAR.
  • the carrier index for SUL may be included in a RAR to identify the carrier that a WTRU may select after decoding the NR-PDCCFI with a corresponding RA-RNTI.
  • Carrier index information may be embedded in the RA-RNTI (e.g., since the RA-RNTI may be a function of the carrier index), making it possible to perform double confirmation. Additional RA-RNTIs may be needed and/or used. Other parameters described herein may be used to determine RA-RNTI. These parameters may be carried in RAR and used to provide double confirmation. Additional protection may be achieved for determining a WTRU's own RAR.
  • SUL may be used for contention-based RACFI resources, e.g., for one or more of beam management, beam failure indication, beam recovery request, etc.
  • SUL may be used for contention-free or dedicated RACFI resources, e.g., for one or more of handover, beam management, beam failure indication, beam recovery request, etc.
  • a WTRU e.g., a WTRU at the edge of a cell
  • a dedicated preamble may be configured for an SUL RACFI occasion, e.g., for handover.
  • a gNB may configure SUL (e.g., send configuration information to a WTRU that the WTRU may use for SUL transmission(s)) and assign a dedicated preamble (e.g., preamble index) and/or a carrier index, e.g., based on one or more of SNR, scenarios, use cases, traffic conditions, service types, etc.
  • a dedicated preamble e.g., preamble index
  • carrier index e.g., based on one or more of SNR, scenarios, use cases, traffic conditions, service types, etc.
  • the gNB may not configure a dedicated preamble on the primary UL. In examples, when SUL is configured, the gNB may only configure dedicated preamble(s) on the SUL.
  • SUL configuration may be based on reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), and/or the like. For example, if a WTRU's RSRP, RSRQ, and/or RSSI is lower than a respective threshold, a gNB may configure a SUL and may configure dedicated preamble(s) (e.g., which may be selected based on configured preamble indices) for the WTRU to use on the SUL. If the WTRU's RSRP, RSRQ, and/or RSSI is equal to or greater than the respective threshold, the gNB may configure a normal NR UL. The respective threshold may be predetermined or may be configured by the gNB.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSRP, RSRQ, and/or RSSI thresholds may be configured by a gNB, e.g., for traffic load balancing between SUL and NR DL carrier.
  • a WTRU may perform initial access based on RACH configuration for an SUL carrier.
  • the configuration information for the SUL carrier may include one or more thresholds (e.g., for RSRP, RSRQ, and/or RSSI).
  • the WTRU may select the SUL carrier for initial access if the RSRP, RSRQ, and/or RSSI measured by the WTRU is lower than the respective configured threshold.
  • the respective RSRP, RSRQ, and/or RSSI thresholds may be indicated in an SS block or in system information such as SS, NR-PBCH, RMSI, OSI or the like.
  • a WTRU may measure RSRP, RSRQ, and/or RSSI on the DL carrier where the WTRU may receive RMSI, SS, and/or NR-PBCH.
  • a PRACH preamble format may be associated with SUL.
  • a PRACH preamble format for SUL may be explicitly and/or implicitly configured to support a larger coverage area (e.g., larger than the area covered by the PRACH preamble format used in normal UL).
  • the preamble formats of SUL and normal UL may be different.
  • Example short sequence PRACH preamble formats are shown in the following Table 1.
  • the preamble formats of SUL may be a subset of the preamble formats for normal UL.
  • the normal UL may use all the PRACH formats in Table 1 above, while SUL may use certain PRACH formats in Table 1 (e.g., a subset of the PRACH formats in Table 1).
  • SUL may use a subset of PRACH format A, B, or C in TABLE 1 (e.g., where A, B and C are PRACH preamble formats).
  • Certain restrictions may be added to one or more SUL preamble formats.
  • a restriction set for preamble formats for SUL may be used. Preamble formats that support larger coverage areas may be included in the restriction set.
  • a gNB may configure the preamble formats of SUL within the restriction set.
  • the restriction set may be configured or otherwise provided, for example, based on the preamble formats configured to NR UL.
  • the restriction set size of a preamble format on SUL may be K, which can be indicated by log2(K) bits.
  • a restriction set can be determined and/or provided as follows. As stated above, a restriction set may be based on NR UL preamble formats. If a long preamble format is configured for NR UL, then long preamble formats (e.g., only long preamble formats) may be configured to SUL. Examples of preamble format restriction sets (e.g., when long preamble formats are configured) may be as the following:
  • Restriction set is ⁇ 1 , 2, 3 ⁇
  • preamble format restriction sets may resemble the following:
  • Restriction sets are ⁇ A1/B1 A2/B2, A3/B3, CO, C2, 0, 1 , 2 ⁇
  • Restriction sets are ⁇ A2/B2, A3/B3, B4, CO, 0, 1 , 2, 3 ⁇
  • Restriction sets are ⁇ A3/B3, B4, CO, C2, 0, 1 , 2, 3 ⁇
  • Restriction sets are ⁇ C2, 0, 1 , 2, 3 ⁇
  • a subcarrier spacing (SCS) restriction set may be used for SUL, NR UL, or both.
  • the SCS of RACH on SUL may be the same as or different from that on NR UL.
  • the PRACH configuration periodicity of multiple (e.g., two) ULs may be configured with different values.
  • SUL one or more of the following may or may not be used: SS block, PDCCH monitoring, DL/UL switch point, dynamic slot format indicator (SFI), and/or semi-static DL/UL scheduling.
  • RACH occasions (ROs) and/or the periodicities of PRACH configuration on multiple (e.g., two) ULs may be configured differently.
  • PRACH preamble formats may be used on multiple (e.g., two) ULs (e.g., SUL may support fewer RACH occasions (ROs) within one slot).
  • PRACH may start from the 1st OFDM symbol within a slot (e.g., SUL may support more ROs within one slot).
  • SUL e.g., if there is no SS block transmitting
  • there may be more resources for PRACH than on normal NR UL e.g., SUL may support more ROs within one slot.
  • SUL may be the only UL resource for a carrier.
  • SUL may be used as a complimentary access link (e.g., for random access) in addition to NR TDD and NR FDD UL.
  • a WTRU may select PRACH resources in NR TDD and/or FDD uplink frequency.
  • a WTRU may select PRACH resources in the SUL frequency.
  • the SUL frequency may be a shared frequency (e.g., shared with LTE UL).
  • a WTRU may support simultaneous transmission on an NR UL frequency and an SUL frequency.
  • the carrier frequency of SUL may be lower than an NR unpaired carrier. There may be more available UL slots (e.g., subframes) on SUL than on an NR unpaired carrier. The UL coverage area of SUL may be larger than that of NR unpaired carrier.
  • a WTRU may be allowed to transmit on UL carriers in different frequency ranges.
  • the WTRU may have the capability to transmit on one of the carriers at a given time.
  • an SRS carrier may be switched with predetermined frequency ranges (e.g., for LTE-NR UL sharing). This may be applied to the NR standalone (SA) operations or NR non-standalone (NSA) operations of a WTRU.
  • SA NR standalone
  • NSA non-standalone
  • a hybrid format based PRACH transmission may be implemented.
  • One PRACH format may be configured for a cell.
  • a hybrid PRACH format may be configured for a cell.
  • format A and format B may be considered as a package for the PRACH configuration.
  • Mixed format A and B or format C may be configured.
  • Hybrid format A/B may be configured, the last PRACH resource within a RACH slot may use the PRACH preamble format B with a guard period and the other PRACH resources within the RACH slot may use format A without guard period. This may reduce inter-symbol interference (ISI) from the same or other WTRUs.
  • PRACH preamble format B4 within a RACH slot may be used in the case of a single PRACH occasion within a RACH slot.
  • Other mixed PRACH preamble formats may be provided.
  • a PRACH format may be configured of PRACH format A0, A1 , A2, and/or A3, mixed within a
  • a PRACH format may be configured of PRACH format A0, A1 , A2, and/or A3 mixed with
  • PRACH format B0, B1 , B2, and/or B3 within a RACH slot may be used.
  • PRACH preamble format A0 may be used for a very small cell (e.g., when the timing advance (TA) may be already known).
  • Preamble format A may not have guard time, and may interfere the uplink data receiving in the following symbol. If no uplink data is transmitting in the following symbol, PRACH format A may be used. The first two symbols may be reserved for DL control such as PDCCH monitoring.
  • FIG. 2 is an example of a PRACH format slot.
  • the PRACH preamble format A may be used at the end of the RACH slot in FIG. 2, since there is no uplink data in the following symbol (e.g., the first symbol of the next slot which may be reserved for PDCCH).
  • a WTRU may receive an indication of whether the DL control or control resource set (CORESET) is present in the first OFDM symbol of a slot, e.g., the next slot.
  • PRACH preamble format A may be configured or used in the last RACH resource of a slot, e.g., if the DL control or CORESET is not present or configured in the first OFDM symbol of the slot (e.g., next slot). Otherwise, PRACH preamble format B may be configured or used in the last RACH resource of a slot.
  • Preamble format B may exhibit performance degradation (e.g., as compared with preamble format A), for example due to the guard time and may need a different FFT block from the PUSCH reception.
  • the coverage of preamble format B may be smaller than preamble format A (e.g., due to the guard time).
  • a PRACH preamble format A1 A3 may be supported within one slot (e.g., when there is no uplink transmission following the last RACH resource or RO of a slot).
  • a hybrid PRACH preamble format may be [A A A A ... A A] or [A A A A ... A B],
  • a WTRU may select (e.g., or be configured to use) PRACH preamble format combination [A A A A ... A A] if uplink transmission following the last RACH resource (or RO of a slot) is not configured or present.
  • a WTRU may select (e.g., or be configured to use) PRACH preamble format combination [A A A A ... A B] if uplink transmission following the last RACH resource (or RO of a slot) is configured or present.
  • a hybrid PRACH preamble format may also be [A A A A ... B B] within one slot.
  • A may be a single PRACH format chosen from one (e.g., only one) of the PRACH formats A0, A1 , A2 or A3.
  • A may be a mixed or hybrid PRACH format chosen from any of A0, A1 , A2 or A3.
  • Combinations of A0, A1 , A2 or A3 may be provided.
  • B may be a single PRACH format chosen from one (e.g., only one) of the PRACH formats B1 , B2, B3 or B4.
  • B may be a mixed or hybrid PRACH format chosen from any of B1 , B2, B3 or B4. Combinations of B1 , B2, B3, or B4 may be provided.
  • RACH slot types may be provided for PRACH resources. Multiple types of RACH slots may be introduced. RACH slot types may be defined based on whether a SS block is present or absent. For example, two types of RACH slots nay be defined: (i) RACH slot Type 1 : in RACH slot Type 1 , one or more (e.g., all) OFDM symbols may be available for PRACH resources; and (ii) RACH slot Type 2: in RACH slot Type 2, there may be some symbols that are unavailable for PRACH resource. A pattern of SS blocks within a slot may be predefined. The types of RACH slots may be based on the SCS of SS block and PRACH (e.g., RACH message 1 or preamble).
  • FIG. 3 is an example of a RACH slot (e.g., a type 2 slot). If the SCS of SS blocks is the same as the SCS of RACH, and one or more (e.g., all) SS blocks (SSB) are transmitted, the pattern of an SSB slot may be as depicted in FIG. 3. The last 4 symbols at the end of the slot may be used as PRACH.
  • SSB SS blocks
  • FIG. 4 shows more examples of RACH slots (e.g., type 2 slots). If the SCS of SS blocks is the same as the SCS of RACH, and one or more (e.g., fewer than all) SSBs are transmitted, the pattern of an SSB slot may be as depicted in FIG. 4.
  • the starting symbol index of PRACH may be the 7th OFDM symbol (e.g., as in the upper example of FIG. 4) or the 11th OFDM symbol (e.g., as in the lower example of FIG. 4).
  • FIG. 5 is an example of a RACH slot (e.g., a type 2 slot).
  • the SCS of SS blocks may be twice the SCS of RACH. If one or more (e.g., all) SS blocks are transmitted, then the pattern of SSB slot may be as depicted in FIG. 5.
  • the 6th - 8th OFDM symbols may be used as PRACH, and/or the 13th and 14th OFDM symbols may be used as PRACH.
  • FIG. 6 shows examples of including three SS blocks (e.g., shown as shaded blocks) within one slot.
  • FIG. 7 shows examples of including three SS blocks (e.g., shown as shaded blocks) within one slot.
  • FIG. 8 shows examples of including two SS blocks (e.g., shown as shaded blocks) within one slot.
  • FIG. 9 shows examples of including one SS block (e.g., shown as shaded blocks) within one slot.
  • a similar approach to the above may be applied to a RACH mini-slot (e.g., a RACH non-slot) with different durations and/or number of OFDM symbols.
  • a RACH configuration may map RACH resources onto one or more slots, for example irrespective of the time locations of actually transmitted SS/PBCH blocks for FDD and/or TDD.
  • An actually transmitted SS/PBCH block may overlap with a RACH resource within a RACH configuration period.
  • predefined rules may be used to indicate which RACH resource(s) may still be valid. These rules may be sent via RRC signaling, may be predefined, and/or may be fixed. DL/UL switching points may be considered. Potential impact due to semi-static or dynamic DL/UL configuration may be considered.
  • SFI dynamic slot format indication
  • RACH may be designed to avoid collisions. This may be achieved by one or more of the following: (i) smart design of a configuration table; (ii) intelligent rules (e.g., which may be predefined or signaled); and/or (iii) using a dynamic indication such as an SFI.
  • the slot duration for PRACH resource mapping for short preamble formats may be based on the numerology of RACH Msg1 , e.g., based on SCS.
  • RACH configurations may be specified using a table, for example, a table indexed by PRACH config index.
  • PRACH transmission occasions may be time multiplexed or frequency multiplexed. Time multiplexed and/or frequency multiplexed PRACH transmission occasions may use the same PRACH Config Index.
  • a WTRU may be indicated (e.g., by a 1-bit indicator) which multiplexing scheme is used (e.g., time multiplexed or frequency multiplexed PRACH transmission occasions).
  • Subcarrier spacing (SCS) and/or PRACH preamble formats may be included in the table.
  • the number of bits used for the RACH configuration may be reduced (e.g., minimized). For example, N bits may be used for RACH configuration and N may be six, eight, ten, or other suitable values.
  • a pattern given by a PRACH Config Index may repeat (e.g., in every RACH configuration period).
  • the density and duration for RACH occasions (e.g., within each RACH configuration period) may be indicated (e.g., configured).
  • a RACH occasion may occur in every slot or non-slot (e.g., a mini-slot).
  • a RACH configuration period may be 10ms, 20ms, 40ms, 80ms, or 160ms.
  • the same values may be used for low and high frequency ranges (e.g., above and below 6GHz). Different values may be used for low and high frequency ranges (e.g., above and below 6GHz).
  • a PRACH configuration may include a PRACH configuration table and/or a PRACH formula indicator.
  • the PRACH formula indicator may indicate one or more of the following: (i) numerology (e.g., subcarrier spacing); (ii) PRACH preamble format; (iii) long sequence or short sequence; and/or (iv) configuration period.
  • the PRACH configuration table may include numerology (e.g., subcarrier spacing) and/or PRACH preamble format (e.g., which may be determined according to a configured PRACH preamble index).
  • a table may be used which may specify the subframe numbers used for RACH. Multiple rules may be used to configure the PRACH occasions and/or period.
  • An example PRACH configuration table is given in Table 2 below.
  • a PRACFI configuration may use one bit to indicate whether a long or short sequence should be used.
  • a PRACFI configuration may use 6 bits to indicate an NR-RACFI configuration Index.
  • a PRACFI configuration may use 7 bits to indicate a frequency offset.
  • a PRACFI configuration may use 3 bits to indicate a frequency index.
  • a PRACFI configuration may use 1 bit to indicate whether SCS is 15khz or 30khz (e.g., when a long sequence is used).
  • a PRACH configuration may use 1 bit to indicate whether SCS is 15khz or 30khz for below 6GHz scenarios (e.g., when a short sequence is used) and may use 1 bit to indicate whether SCS is 60khz or 120khz for above 6GHz scenarios (e.g., when a short sequence is used).
  • FIG. 10 is an example of a subframe/slot structure for PRACH transmission.
  • One or more RACH CORESETs may be monitored (e.g., for a random access response).
  • a remaining minimum system information (RMSI) CORESET configuration may indicate that multiple monitoring occasions may exist within a slot, and/or that a PDCCH monitoring occasion for RMSI may be among the multiple monitoring occasions of the slot (e.g., according to an SSB index).
  • a monitoring occasion as referenced herein may be associated with a point or duration in time (e.g., in the time domain), and/or with a segment in frequency (e.g., in the frequency domain).
  • a PDCCH monitoring occasion and a RACH CORESET monitoring occasion may be used interchangeably herein.
  • a number of (e.g., one or more) RACH CORESETs may be implemented within a time duration (e.g., such as a slot or multiple slots). Such a time duration may be pre-defined, configured, or indicated. It should be noted that although a slot is used in some of the examples described herein, those examples may still be valid if the slot is replaced with a time duration or time period comprising multiple slots.
  • a WTRU may monitor a CORESET (e.g., only one CORESET) according to a preamble index (e.g., the preamble index that the WTRU selected for RACH Msg1) and/or one or more other parameters.
  • Multiple RACH CORESETs within a slot may employ one or more of TDM multiplexing, FDM multiplexing, and/or joint TDM and FDM multiplexing.
  • a WTRU may monitor one or multiple RACH CORESETs according to a preamble index (e.g., the PRACH preamble index that the WTRU selected in Msg1) and/or other parameters.
  • a preamble index e.g., the PRACH preamble index that the WTRU selected in Msg1
  • diversity and/or interference mitigation may be achieved, e.g., for licensed bands or unlicensed bands.
  • a WTRU may monitor one or multiple RACH CORESETs according to one or more of the following: PRACH preamble index, PRACH resource index, and/or SS block index (e.g., such as a combination of PRACH preamble index and resource index that the WTRU selected in Msg1).
  • RACH CORESETs within a slot may be TDMed.
  • a RACH CORESET configuration may indicate that there are more than one monitoring occasion (e.g., in time and/or frequency domain) within a slot, and a WTRU may monitor one (e.g., only one) of the monitoring occasions. The WTRU may decide which CORESET to monitor according to the preamble index with which the PDCCH and/or a RAR are associated.
  • the WTRU may monitor the first PDCCH monitoring occasion if the preamble index of Msg1 is even, and may monitor the second PDCCH monitoring occasion if the preamble index of Msg1 is odd.
  • a WTRU may decide which CORESET to monitor based on a modulo operation.
  • the WTRU may monitor the first PDCCH occasion if the preamble index of Msg1 divided by four results in a remainder 0.
  • the WTRU may monitor the second PDCCH occasion if the preamble index of Msg1 divided by four results in a remainder of 1 .
  • the WTRU may monitor the third PDCCH occasion if the preamble index of Msg1 divided by four results in a remainder 2, and the WTRU may monitor the fourth PDCCH occasion if the preamble index of Msg1 divided by four results in a remainder of 3.
  • FIG. 11 is an example of determining a monitoring occasion (e.g., a PDCCH monitoring occasion) for a TDMed CORESET based on a preamble index.
  • a monitoring occasion e.g., a PDCCH monitoring occasion
  • the WTRU may be configured (e.g., via higher layer signalling or downlink control information) with v TDMed RACH PDCCH monitoring occasions within a slot.
  • the monitoring occasions may be indexed by 0, 1 , 2,... , v-1 , respectively.
  • the WTRU may select an SSB index l.
  • the WTRU may determine (e.g., randomly determine, (e.g., when there is a multiple-to-one relationship between the preamble indices and an SSB index)) a preamble index i within a preamble subset (e.g., the preamble index may uniquely identify a preamble within the preamble subset).
  • the WTRU may send the preamble associated with the preamble index.
  • the preamble (e.g., or preamble subset) may be associated with the selected SSB index Z, e.g., via a type of preamble index to SSB index association.
  • the WTRU may monitor the TDMed PDCCH occasion j in a (e.g., every) slot within a RAR window.
  • the WTRU may detect a corresponding RAR within the RAR window, and the WTRU may send Msg3 using UL resources indicated in the RAR.
  • the WTRU may determine the preamble index i within the preamble subset and may repeat one or more of the operations described herein (e.g., determining a preamble index i within the preamble subset, sending the preamble, etc.).
  • RACH CORESETs may be FDM multiplexed for one or more (e.g., each) RACH PDCCH monitoring occasions.
  • a WTRU may monitor a (e.g., only one) FDMed CORESET, e.g., according to the preamble index of Msg1.
  • FIG. 12 is an example of determining a monitoring occasion (e.g., a PDCCH monitoring occasion) for a FDMed CORESET based on a preamble index.
  • a WTRU may monitor one FDMed CORESET (e.g., using one FDMed RACFI PDCCFI monitoring occasion in the frequency domain) if the preamble index of Msg1 is odd, and may monitor the other FDMed CORESET (e.g., using another RACFI PDCCFI monitoring occasion in the frequency domain) if the preamble index of Msg1 is even.
  • a WTRU may decide which CORESET to monitor based on a modulo operation. For example, there may be a total of l FDMed RACFI CORESETs for a (e.g., each) RACFI monitoring occasion.
  • the CORESETs may be indexed by 0, 1 , 2, .... l -1 , respectively.
  • a WTRU may perform one or more of the following.
  • the WTRU may be configured with a total of l FDMed RACFI PDCCFI monitoring occasions within a slot, indexed by 0, 1 , 2,... , l-1 , respectively.
  • the WTRU may select an SSB index l.
  • the WTRU may determine (e.g., randomly when there is a multiple-to-one relationship between the preamble indices and an SSB index) a preamble index i within the preamble subset (e.g., the preamble index may uniquely identify a preamble within the preamble subset).
  • the WTRU may send the preamble associated with the preamble index.
  • the preamble or preamble subset may be associated with the selected SSB index Z, e.g., via a type of preamble index to SSB index association.
  • the WTRU may monitor the FDMed PDCCFI occasion j in a (e.g., every) slot within a RAR window.
  • the WTRU may detect a corresponding RAR within the RAR window, and the WTRU may send Msg3 in UL resources indicated in the RAR. If the WTRU does not detect a corresponding RAR within the RAR window, the WTRU may determine a preamble index i within a preamble subset and may repeat one or more of the operations described herein.
  • RACFI CORESETs may be joint TDM and FDM multiplexed within a slot.
  • a WTRU may monitor a RACFI CORESET according to the preamble index of Msg1 and/or one or more other parameters.
  • FIG. 13 is an example of determining a monitoring occasion for joint FDM and TDM multiplexed RACFI CORESETs. In the example, there may be two TDMed PDCCFI monitoring occasions within a slot and there may be two FDMed CORESETs for each of the monitoring occasions.
  • a WTRU may monitor one of the FDMed CORESTs at the first monitoring occasion within the slot according to the preamble index of Msg1 , and may monitor another one of the FDMed CORESTs at the second monitoring occasion within the slot according to the preamble index of Msg1 .
  • the WTRU may monitor different FDMed CORESTs at different monitoring occasions within the slot.
  • a frequency location of the RACFI CORESET that the WTRU monitors may depend on the preamble index and/or the RACFI monitoring occasion. For example, the WTRU may monitor one CORESET if the preamble index of Msg1 is odd, and may monitor another CORESET if the preamble index of Msg1 is even.
  • the WTRU may obtain frequency diversity gains for RACH messages such as the RACH messages received in an unlicensed band.
  • a WTRU may perform one or more of the following for joint FDMed and TDMed RACH CORESETs.
  • the WTRU may determine a preamble index i within a preamble subset and send the preamble associated with the preamble index.
  • the preamble or preamble subset may be associated with a selected SSB index l, e.g., via a type of preamble index to SSB index association.
  • the WTRU may monitor the determined joint FDMed and TDMed PDCCH occasion (e.g., the determined RACH CORESET with a frequency domain index of) (e.g., as calculated above) and a time domain index of k in one or more slots (e.g., every slot) of a RAR window.
  • the WTRU may detect a corresponding RAR within the RAR window, and the WTRU may send Msg3 in UL resources indicated in the RAR. If the WTRU does not detect a corresponding RAR within the RAR window, the WTRU may determine the preamble index / within the preamble subset and repeat one or more of the operations described herein.
  • a WTRU may employ joint FDM and TDM multiplexing CORESETs.
  • a WTRU may monitor one or more of the FDMed CORESETs according to a preamble index and monitor one or more of the TDMed CORESETs according to an SSB index.
  • the SSB index may be associated to Msg1 .
  • the WTRU may monitor the RACH CORESET with frequency index mod(i, X) at a first monitoring occasion if the preamble index is even.
  • the WTRU may monitor the RACH CORESET with frequency index mod(i, X) at a second monitoring occasion if the preamble index is odd.
  • the WTRU may monitor one or more of the TDMed CORESETs according to a preamble index and monitor one or more of the FDMed CORESETs according to an SSB index.
  • the SSB index may be associated to Msg1.
  • FIG. 14 is an example of a WTRU monitoring a TDMed monitoring occasion according to a preamble index (e.g., a preamble index associated with Msg 1). As shown, there may be two PDCCH monitoring occasions (e.g., in the time domain) within a slot (e.g., of a RACH monitoring window). A WTRU may be configured to use a first PDCCH monitoring occasion if the preamble index is even and use a second PDCCH monitoring occasion if the preamble index is odd.
  • a preamble index e.g., a preamble index associated with Msg 1).
  • there may be two PDCCH monitoring occasions e.g., in the time domain
  • a slot e.g., of a RACH monitoring window
  • FIG. 15 is an example of a WTRU monitoring a FDMed monitoring occasion according to a preamble index (e.g., a preamble index associated with Msg 1 ). As shown, there may be two RACH CORESET monitoring occasions (e.g., in the frequency domain) within a slot (e.g., of a RACH monitoring window). A WTRU may be configured to monitor a first RACH CORESET if the preamble index is even and monitor a second RACH CORESET if the preamble index is odd.
  • a preamble index e.g., a preamble index associated with Msg 1
  • there may be two RACH CORESET monitoring occasions e.g., in the frequency domain
  • a slot e.g., of a RACH monitoring window.
  • a WTRU may be configured to monitor a first RACH CORESET if the preamble index is even and monitor a second RACH CORESET if the preamble index is odd.
  • FIG. 16 is an example of a WTRU monitoring joint TDMed and FDMed RACH CORESETs within a slot (e.g., inside a RACH monitoring window). As shown, there may be two TDMed PDCCH monitoring occasions within the slot and there may be two FDMed CORESETs for each of the monitoring occasions, resulting in a total of four CORESETs in the slot.
  • the WTRU may determine which CORESET to monitor, e.g., by performing one or more of the following.
  • the WTRU may assign an index k to each of the four CORESETs, for example, based on the respective locations of the CORESETs in the time- frequency domain.
  • the four CORESETs may be assigned an index of 0, 1 , 2, and 3, respectively, as shown in FIG. 16.
  • a first pair of diagonally opposite CORESETs (e.g., based on the locations of the CORESETs in the time-frequency grid) may be assigned even-numbered indices (e.g., 0 and 2) while a second pair of diagonally opposite CORESETs may be assigned odd-numbered indices (e.g., 1 and 3).
  • Other ways for assigning indices to the CORESETs may also be applied (e.g., as shown in FIG. 17).
  • the WTRU may decide to monitor the
  • FIG. 17 is an example of a WTRU monitoring joint TDMed and FDMed RACH CORESETs within a slot (e.g., inside a RACH monitoring window).
  • the CORESETs are assigned indices (e.g., in a different order as that shown in FIG. 16).
  • the WTRU may decide which CORESET among the multiple CORESETs (e.g., four CORESETs) the WTRU should monitor based on a modulo operation (e.g., in a similar manner as illustrated by the example of FIG. 16). It should be noted that because the CORESET indices are assigned in a different order than that in FIG.
  • the specific CORESET selected by the WTRU based on a preamble index may be different than the CORESET selected in the example of FIG. 16. For example, based on a preamble index of 1 , a WTRU in the example of FIG. 17 may select the CORESET at PDCCH monitoring occasion 0 and frequency occasion 1 for monitoring. Based on the same preamble index of 1 , a WTRU in the example of FIG. 16 may select the CORESET at PDCCH monitoring occasion 0 and frequency occasion 0 for monitoring.
  • a WTRU may receive a configuration that indicates the relationship (e.g., an association) between one or more preambles and one or more SSBs.
  • the WTRU may determine which CORESET among a plurality of CORESETs that the WTRU should monitor based on the configured relationship.
  • FIG. 18 shows an example of a WTRU determining which CORESET to monitor based on the relationship (e.g., an association) between preambles and SSBs.
  • the WTRU may receive configuration information relating to SSBs and/or a RACH procedure to be performed by the WTRU.
  • the configuration information may indicate one or more PRACH preamble indices for the WTRU.
  • the configuration information may indicate one or more PRACH resource indices for the WTRU.
  • the configuration information may indicate one or more SSB indices for the WTRU.
  • the configuration information may indicate or the WTRU may determine based on the configuration information a relationship between the one or more SSBs preambles and the one or more PRACH preambles.
  • Such a relationship may be a one-to-one relationship (e.g., one SSB corresponds to one specific PRACH preamble), a many-to-one relationship (e.g., multiple SSBs correspond to one PRACH preamble), or a one-to-many relationship (e.g., one SSB corresponds to multiple PRACH preambles).
  • the WTRU may be further configured with multiple CORESET monitoring occasions, as described herein.
  • the WTRU may select a CORESET monitoring occasion among the multiple configured occasions based on the relationship between the SSBs and PRACH preambles. For example, if the relationship is a one-to-one relationship (e.g., one SSB corresponds to one PRACH preamble), the WTRU may select the CORESET monitoring occasion based on either a preamble index or an SSB index (e.g., by performing a modulo operation on the selected preamble index or SSB index, as described herein).
  • the WTRU may select the CORESET monitoring occasion based on an SSB index (e.g., by performing a modulo operation on the selected SSB index, as described herein). If the relationship is a many-to-one relationship (e.g., multiple SSBs correspond to one PRACH preamble), the WTRU may select the CORESET monitoring occasion based on a preamble index (e.g., by performing a modulo operation on the selected preamble index, as described herein).
  • SUL carriers may be configured, e.g., in addition to a NR UL carrier. For example, there may be multiple UL carriers (e.g., NR UL carrier, SUL carriers, etc.) in NR.
  • a WTRU may choose one of the UL carriers to send a preamble according to preconfigured criterions.
  • a WTRU which sends preambles (e.g., on UL or SUL) may monitor a RACH CORESET on an NR DL carrier.
  • the RACH CORESETs for different UL carrier indexes may be FDM multiplexed on an NR DL carrier.
  • Each FDMed CORESET may be for one (or a subset) of UL carriers.
  • FIG. 19 is an example of RACFI CORESET monitoring for different UL carriers.
  • FDMed RACFI CORESETs for multiple UL carriers may be implemented, where a WTRU may monitor one of the FDMed RACFI CORESETs according to the SUL carrier index or UL carrier index.
  • FIG. 20 is an example of WTRU monitoring a RACFI CORESET when different UL carriers are configured.
  • a WTRU may be configured with multiple (e.g., U, which may correspond to one per UL carrier) RACFI CORESETs (e.g., FDMed) for a (e.g., each) RACFI PDCCFI monitoring occasion (e.g., a RACFI PDCCFI monitoring occasion in the time domain).
  • the WTRU may be configured with a RAR window.
  • the WTRU may select UL carrier index u (e.g., u may be equal to 0, 1 , . . . UA) for RACFI according to preconfigured UL carrier selection criterions.
  • the WTRU may send the preamble on UL carrier u.
  • the WTRU may monitor the RACFI CORESET with UL carrier ndex u in a (e.g., every) RACFI PDCCFI occasion within the RAR window.
  • the WTRU may detect an RAR within the RAR window, and may send the Msg3 in UL resources indicated in the RAR. If the WTRU does not detect an RAR within the RAR window, the WTRU may select a UL carrier index u for RACFI according to preconfigured UL carrier selection criterions. The WTRU may send the preamble on UL carrier u and repeat the one or more of the operations described herein.
  • the RACFI CORESET of a (e.g., one) UL carrier may be frequency hopping among different monitoring occasions (e.g., CORESET or PDCCFI monitoring occasions), for example, in order to obtain frequency diversity gain.
  • FIG. 21 is an example of frequency hopping of RACFI CORESET among different RACFI occasions.
  • a WTRU may be configured with three UL carriers with indexed as 0, 1 , and 2, respectively. The WTRU may choose UL carrier 1 for RACFI, and may monitor RACFI CORESET with frequency index 1 at monitoring occasion 0, monitor RACFI CORESET with frequency index 2 at monitoring occasion 1 , and monitor RACFI CORESET with frequency index 0 at monitoring occasion 2.
  • FIG. 22 is an example of a WTRU implementing RACFI CORESET frequency hopping among different RACFI occasions for UL carriers. As shown, if the WTRU chooses UL carrier index u for RACFI, at RACFI monitoring occasion index k, the WTRU may monitor RACFI CORESET with frequency index mod(u + k, U), where U may be the total number of UL carriers for RACFI.
  • FDMed RACFI CORESETs for multiple UL carriers may be implemented.
  • a WTRU may monitor a RACFI CORESET (e.g., one of the FDMed RACFI CORESETs) according to the UL carrier index and monitoring index. For example, there may be U UL carriers, indexed by 0, 1 , .... U— 1.
  • a WTRU may be configured with U FDMed RACH CORESETs for a (e.g., each) RACH PDCCH monitoring occasion.
  • the WTRU may be configured with a RAR window.
  • the WTRU may select a UL carrier index u for RACH according to preconfigured UL carrier selection criterions.
  • the WTRU may send a preamble on UL carrier u.
  • the WTRU may monitor the RACH CORESET with frequency index of mod(u + k, U).
  • the WTRU may detect the RAR within the RAR window, and may send the Msg3 in the UL resources indicated in RAR. If the WTRU does not detect an RAR within the RAR window, the WTRU may select a UL carrier index u for RACH according to preconfigured UL carrier selection criterions.
  • the WTRU may send a preamble on UL carrier u and repeat one or more of the operations described herein.
  • a gNB may configure whether RACH CORESETs are frequency hopping among different monitoring occasions.
  • a WTRU may receive the configuration and perform one or more of the operations described herein according to the configuration.
  • a leftover RACH occasion may be used for contention free random access (CFRA).
  • RACH resources e.g., RACH occasions or RACH preambles
  • CBRA contention based random access
  • RACH occasions may be configured by PRACH-configuration-index, which may indicate the slot index for a PRACH preamble transmission.
  • the association between SSBs and CBRA resources may be given (e.g., indicated) by one or more of the following parameters: SSB-per-RO (e.g., which may indicate the number of SSBs in a RACH occasion (RO)), and/or CBRApreamble-per-SSB- per-RO (e.g., which may indicate the number of preambles corresponding an SSB in a RACH occasion).
  • SSB-per-RO e.g., which may indicate the number of SSBs in a RACH occasion (RO)
  • CBRApreamble-per-SSB- per-RO e.g., which may indicate the number of preambles corresponding an SSB in a RACH occasion.
  • the actually transmitted SSBs and RACH occasions (ROs) may be associated (e.g., cyclically) within one mapping period. If there are leftover ROs, SSBs may or may not be mapped to the leftover ROs.
  • the leftover ROs (e.g., which may not be used for SSB mapping in CBRA) may be used as dedicated RACH occasions for CFRA.
  • the leftover ROs may be used for CSI-RS mapping.
  • the leftover ROs may be indicated in PDCCH order for PDCCH ordered RACH.
  • a gNB may trigger a PDCCH ordered RACH (e.g., if the gNB requests UL synchronization re establishment or a UL timing adjustment).
  • the gNB may indicate a preamble index and a leftover RO index in PDCCH order to a WTRU.
  • the WTRU may send the preamble at the RO indicated in the PDCCH order, and the gNB may perform the time estimation based on the received preamble.
  • Leftover ROs may be indicated from index 0. There may be 64 leftover ROs (e.g., at most).
  • a six-bit parameter, ROJndex may be used in PDCCH order to indicate a leftover RO. This leftover RO may be used for a WTRU CFRA preamble transmission.
  • a 1 -bit indicator or parameter, leftover_RO may be used to indicate whether the RACH occasion is a dedicated RO or a regular RO.
  • Leftover ROs may be used for CSI-RS mapping.
  • a mapping indication or instruction may follow the CSI-RS based RACH.
  • a leftover RACH occasion may be used for CFRA. In examples, there may be one or more leftover RACH occasions after CBRA mapping.
  • a WTRU may detect a PDCCH order.
  • a parameter e.g., a 6-bit ROJndex
  • a combination of parameters e.g., a 6-bit SSBJndex and a 3-bit ROJndex
  • a preamble index may be indicated in the PDCCH order.
  • the WTRU may generate a Msg1 preamble using the preamble index in PDCCH order, and may send the preamble at the RO that to be used for PDCCH ordered RACH (e.g., according to whether a leftover RO is used).
  • a gNB may receive the WTRU's preamble and may perform UL timing estimation for the WTRU.
  • the timing adjustment command may be sent (e.g., in an RAR).
  • RACH with multiple bandwidth parts may be implemented.
  • a (e.g., each) carrier a (e.g., each) WTRU may be configured with a number of bandwidth parts (BWP) such as up to 4 UL/DL bandwidth parts (BWP).
  • BWP bandwidth parts
  • PRACH configuration/resources on UL BWPs may be linked with DL BWPs.
  • a WTRU may (e.g., only) monitor RAR on DL BWPs that are linked to the used UL PRACH resources. The linkage between DL BWP and UL BWP among WTRUs may be different.
  • FIG. 23 is an example of different linkage among WTRUs.
  • BWP linkage of a first WTRU (e.g., WTRU 1) may be different from another WTRU (e.g., WTRU 2).
  • the numbering of BWP for each WTRU may be internal (e.g., decided by the WTRU).
  • UL BWP 1 of WTRU 1 may be different from UL BWP 1 of WTRU 2.
  • DL BWP 1 of WTRU 1 may be different from the DL BWP 1 of WTRU 2.
  • DL BWP 1 of WTRU 1 may employ the same BWP with DL BWP 2 of WTRU 2, and they may not be the same as the system DL BWP 3.
  • WTRU 1 in FIG. 23 may send Msg1 on UL BWP 1.
  • WTRU 2 in FIG. 23 may send Msg1 with the same preamble index at the same RACH occasion and using the same frequency id as WTRU 1 , but on UL BWP 2.
  • sjd may be the starting symbol index
  • tjd may be the slot index
  • fjd may be the frequency id
  • ul_carrier_id may be the UL carrier ID.
  • the RA- RNTI of the respective preambles for WTRU 1 and WTRU 3 (e.g., two preambles for WTRU 1 and WTRU 2) may be the same.
  • the gNB may transmit RAR in the linked DL BWP 1 of WTRU 1 (e.g., as shown in FIG. 23) and transmit RAR in the linked DL BWP 2 for WTRU 2 (e.g., FIG. 23).
  • the DL BWP 1 of WTRU 1 and the DL BWP 2 of WTRU 2 may be the same DL BWP from gNB's perspective
  • the gNB may send two RARs on the same DL BWP with the same RA-RNTI and with the same preamble index inside the RAR.
  • WTRU 1 and WTRU 2 may not be able to differentiate which RAR is for WTRU 1 and which is for WTRU 2.
  • the gNB may differentiate the two RARs for two WTRUs.
  • RA-RNTI may be a function of UL BWP index.
  • UL BWP index may be a system index which may be consistent for multiple (e.g., all) WTRUs.
  • the system BWP index may be indicated to the WTRU.
  • the WTRU may use the system BWP to calculate the RA-RNTI and receive the PDCCH based on the RA-RNTI (e.g., use the RA- RNTI to accept the PDCCH).
  • An system UL BWP index may be carried in an RAR, and a WTRU may use the decoded BWP information to decide whether the RAR is intended for the WTRU. After decoding the RAR, the WTRU may check the system UL BWP index inside the RAR. The WTRU may decide that the RAR is intended for it if the system UL BWP index is consistent with the UL BWP of Msg1. Otherwise, the WTRU may withdraw the RAR.
  • FDMed RACH CORESTs may be used for different UL BWPs linked to the same DL BWP.
  • the gNB sends the RACH configuration for UL BWP to a WTRU
  • the frequency offset of the RACH CORESET may be configured for that UL BWP.
  • the WTRU may monitor the RACH CORESET at the frequency location of frequency offset on the linked DL BWP.
  • FIG. 24 is an example of different RACH COREST frequency offsets for different UL BWPs linked to the same DL BWP.
  • the gNB may configure frequency offset 1 for RACH COREST, while for system UL BWP 2 (e.g., UL BWP 1 of WTRU 1 as shown in FIG. 24), the gNB may configure a different frequency offset, frequency offset 2, for RACH CORESET.
  • WTRU 1 may monitor the RACH CORESET with frequency offset 2 for receiving RAR with RA-RNTI.
  • WTRU 1 may decide that the RAR is intended for it.
  • WTRU 2 may monitor the RACH CORESET with frequency offset 1 for receiving RAR with RA-RNTI. If the RAR contains the correct preamble index, WTRU 2 may decide that the RAR is for it.
  • the RAR for WTRU 1 and that for WTRU 2 may be differentiated on different FDMed RACH CORESETs.
  • Channel state information - reference signal (CSI-RS) based RACH may be implemented.
  • PRACH information may be employed for CSI-RS mapping.
  • the RACH occasion for CSI-RS may be the associated RO with the SSB (e.g., which may be QCLed with the CSI-RS).
  • IDLE mode e.g., RRC IDLE mode
  • CSI-RS may not have an associated SSB for inter-frequency case.
  • IDLE mode e.g., RRC IDLE mode
  • RACH may be based on CSI-RS.
  • a WTRU needing to report a CSI-RS may perform RACH based on the selected CSI-RS.
  • the RACH occasions for performing RACH based on CSI- RS may be the same as the RACH occasions used in initial access (e.g., that may be configured by parameter PRACH-configuration-index in RMSI).
  • PRACH for CSI-RS may be configured and the number of CSI-RS may be very large (e.g., up to 96).
  • PRACH for CSI-RS may be configured in RMSI.
  • RMSI may be payload limited.
  • RACH occasions for CSI-RS mapping may be configured to be separately FDMed or TDMed from the RACH occasions for SSB mapping (SSB RO).
  • FIG. 25 is an example of separating PRACH for CSI-RS from PRACH for SSB.
  • pattern 1 -1 may be implemented in which CSI-RS RO may be FDMed with SSB RO.
  • CSI-RS RO and SSB RO may be separated.
  • the RACH occasions for CSI-RS mapping may not be used for SSB mapping, and vice versa.
  • Pattern 1 -2 may be implemented in which CSI-RS RO may be TDMed with SSB RO.
  • CSI-RS RO and SSB RO may be separate.
  • the RACH occasions for CSI-RS mapping may not be used for SSB mapping, and vice versa.
  • the time domain configurations for CSI-RS RO may be the same with that for SSB RO.
  • the frequency domain configuration prach-CSI-FDM may be configured separately in the RACH configuration for CSI-RS.
  • the time domain configuration for CSI-RS RO may be configured separately with a different PRACH- configuration-index ; or the time domain configuration may be configured as a partition factor a of the PRACH that may be configured by PRACH-configuration-index in RMSI.
  • Parameter a may be the number of PRACH slots, which may mean that within one PRACH configuration period configured with PRACH- configuration-index, the number of PRACH slots that are for CSI-RS mapping may be the first (e.g., or last) a PRACH slots, and the remaining slots may be used for SSB mapping.
  • Parameter a may be fractional, which may mean that within one PRACH configuration period configured with PRACH-configuration-index, the number of PRACH slots for CSI-RS mapping may be [aN prach ⁇ , where N prach may be the total number of PRACH slots configured by PRACH-configuration-index. The remaining slots may be used for SSB mapping.
  • FIG. 26 is an example showing that PRACH for CSI-RS may be a subset of PRACH for SSB.
  • a pattern (e.g., pattern 2, which may be different than pattern 1 -1 and 1-2 of FIG. 25) may be implemented.
  • RACH occasions for CSI-RS mapping may be the same as or a subset of RACH occasions for SSB mapping, where the RACH occasions for CSI-RS mapping may also be used for SSB mapping.
  • the PRACH for CSI-RS may be configured as a subset of the PRACH for SSB mapping, with one or more of the following parameters: T_offset, F_offset, Windowjength, Window_height, and
  • CSI_RS_PRACH_gap One or more parameters may be fixed for some scenarios.
  • ⁇ T_offset, Fjoffset, Windowjength, Window_height, CSI_RS_PRACH_gap ⁇ may be configured as ⁇ 0, 0, length of the mapping period, prach_FDM, 0 ⁇ , which may mean that all the PRACH for SS may be used for CSI-RS (e.g., at the same time).
  • CSI-RS mapping (e.g., for a WTRU) may be implemented.
  • a WTRU may be configured with a parameter (e.g., a 1-bit parameter CSI_RS_RO_Pattern) that may indicate which pattern described herein (e.g., pattern 1 -1 of FIG. 25, pattern 1-2 of FIG. 25, and/or pattern 2 of FIG. 26) may be used for CSI-RS RO configuration.
  • CSI_RS_RO_Pattern e.g., CSI_RS_RO_Pattern
  • a parameter e.g., a 1 -bit parameter CSI_RS_RO_SS_RO_Multiplexing
  • CSI_RS_RO_SS_RO_Multiplexing may indicate which multiplexing (e.g., TDM or FDM) scheme may be used between CSI-RS RO and SSB RO.
  • TDM multiplexing
  • a parameter a e.g., TDM or FDM
  • Parameter a may indicate the number of CSI-RS RO within a (e.g., each) PRACFI configuration period.
  • the WTRU may perform the mapping between CSI-RS and the CSI-RS RO obtained according to one or more mapping rules for CSI-RS (e.g., mapping rules between PRACFI and CSI-RS, as described herein).
  • a parameter e.g., a 2-bit parameter prach-CSI-FDM
  • prach-CSI-FDM may indicate the number of FDMed CSI-RS RO.
  • the WTRU may perform the mapping between CSI-RS and the CSI-RS RO obtained according to the mapping rule for CSI-RS.
  • T_offset, F_offset, Windowjength, Window_height, and CSI_RS_PRACFI_gap may be configured to indicate the location of CSI RO.
  • the WTRU may perform the mapping between CSI-RS and the CSI-RS RO obtained according to the mapping rule for CSI-RS.
  • mapping e.g., mapping rules
  • FIG. 27 is an example of different mapping patterns between CSI-RS and RACFI occasions.
  • the mapping between CSI-RS and RACFI occasions may be configured as one of the following mapping patterns: one-to-one mapping, one-to-many mapping, many-to-one mapping, and many-to-many mapping.
  • one-to-one mapping there may be only one CSI-RS mapped to one RACFI occasion.
  • one CSI-RS may be mapped to many RACFI occasions.
  • many CSI-RSs may be mapped to one RACFI occasion.
  • many CSI-RS may be mapped to many RACFI occasions.
  • One or more of the following parameters may be used for the CSI-RS and PRACFI mapping pattern configuration: number of CSI-RS associated with one RACFI occasion, N ⁇ o ⁇ RS ⁇ an d number of RACFI occasions that is associated with one CSI-RS, Ncsi_Rs-
  • the CSI-RS may be cell-specific CSI-RS or WTRU-specific CSI-RS.
  • the CSI-RS may be cyclically mapped to RACH occasions in the ascending order (e.g., or descending order) of CSI-RS index.
  • a 1-bit parameter, CSI-RSJndex_order may be used to indicate the ascending (e.g., or descending order) of CSI-RS index.
  • a mapping order between CSI-RS and RACH occasion may be based on priority order or nature order. For example, the following mapping rules may be employed: first in increasing preamble indices within a single CSI-RS RACH occasion; then in increasing number of frequency multiplexed CSI-RS RACH occasions; then in increasing number of time-domain CSI-RS RACH occasions within a CSI-RS RACH slot; and then in increasing number of CSI-RS RACH slots.
  • a mapping order between CSI-RS and RACH occasion may be employed: e.g., first in increasing preamble indices within a single CSI-RS RACH occasion; then in increasing number of time- domain CSI-RS RACH occasions within a CSI-RS RACH slot; then in increasing number of frequency multiplexed CSI-RS RACH occasions; and then in increasing number of CSI-RS RACH slots.
  • a WTRU may be configured with a parameter, e.g., CSI-RS_mapping_order, that indicates which mapping order may be configured.
  • CSI-RS and RO may be associated.
  • a WTRU may be configured by RO for CSI-RS.
  • a WTRU may receive one or more parameters such as CSI-RS Jndex_order and CSI- RSjnappingjorder in RACH configuration for CSI-RS. If the CSI-RS_index_order is 0, then the WTRU index CSI-RS may be in ascending order (e.g., CSI-RS0, CSI-RS1 , .... CSI-RSX may be indexed as 0, 1 ,
  • the WTRU index CSI-RS may be in descending order (e.g., CSI-RSX, CSI-RSX-1 , .... CSI-RS1 , CSI-RS0 may be indexed as 0, 1 , 2, .... X, respectively).
  • the WTRU mapping CSI-RS index may be given as described herein to RACH occasions in the following order: first in increasing preamble indices within a single CSI-RS RACH occasion; then in increasing number of frequency multiplexed CSI-RS RACH occasions; then in increasing number of time-domain CSI-RS RACH occasions within a CSI-RS RACH slot; and then in increasing number of CSI-RS RACH slots.
  • the WTRU mapping CSI-RS index may be given as described herein to RACH occasions in the following order: first in increasing preamble indices within a single CSI-RS RACH occasion; then in increasing number of time-domain CSI-RS RACH occasions within a CSI-RS RACH slot; then in increasing number of frequency multiplexed CSI-RS RACH occasions; and then in increasing number of CSI-RS RACH slots.
  • CSI-RS_mapping_order being 0 or 1 (or other values).
  • PRACH mapping for CSI-RS may be completed and the WTRU may perform CSI-RS based RACH.
  • the proposed implementations and techniques described herein may be used for NR licensed spectrum.
  • the proposed implementations and techniques described herein may be used for NR unlicensed spectrum.
  • the processes and/or methods described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des systèmes, des procédés et des instruments permettant de configurer de multiples occasions de surveillance d'ensemble de ressources de commande (CORESET) de canal d'accès aléatoire (RACH) sur une période de surveillance. Une WTRU peut identifier quelle occasion parmi les multiples occasions de surveillance de CORESET de RACH est à utiliser, sur la base d'un indice de préambule que la WTRU sélectionne en vue d'une opération d'accès aléatoire, ou sur la base d'un indice de bloc de signal de synchronisation (SSB). L'indice de préambule peut être configuré pour la WTRU par un réseau. L'indice de préambule peut être associé à l'indice SSB. Suite à l'identification de l'occasion de surveillance de CORESET de RACH, la WTRU peut surveiller un canal de commande de liaison descendante physique (PDCCH) au niveau de l'occasion de surveillance identifiée. Une porteuse de liaison montante complémentaire (SUL) peut être mise en œuvre et des ressources de canal d'accès aléatoire physique (PRACH) peuvent se trouver sur la porteuse SUL.
PCT/US2018/060907 2017-11-15 2018-11-14 Multiples occasions de surveillance au niveau d'un ensemble de ressources de commande de canal d'accès aléatoire WO2019099443A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201762586616P 2017-11-15 2017-11-15
US62/586,616 2017-11-15
US201862652555P 2018-04-04 2018-04-04
US62/652,555 2018-04-04

Publications (1)

Publication Number Publication Date
WO2019099443A1 true WO2019099443A1 (fr) 2019-05-23

Family

ID=64650514

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/060907 WO2019099443A1 (fr) 2017-11-15 2018-11-14 Multiples occasions de surveillance au niveau d'un ensemble de ressources de commande de canal d'accès aléatoire

Country Status (2)

Country Link
TW (1) TW201937973A (fr)
WO (1) WO2019099443A1 (fr)

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021005575A1 (fr) * 2019-07-10 2021-01-14 Telefonaktiebolaget Lm Ericsson (Publ) Réduction au minimum de charge de signalisation pendant un transfert intercellulaire de ntn
CN112242896A (zh) * 2019-07-18 2021-01-19 三星电子株式会社 Pdcch监视时机的开始时间的确定
WO2021022392A1 (fr) 2019-08-02 2021-02-11 Qualcomm Incorporated Techniques de commutation de porteuse pour accès aléatoire en deux étapes
WO2021026710A1 (fr) * 2019-08-12 2021-02-18 Qualcomm Incorporated Association de blocs de signaux de synchronisation à des occasions d'accès aléatoire
US10945286B2 (en) 2018-08-03 2021-03-09 Qualcomm Incorporated Beam-specific system information scheduling window design
WO2021062126A1 (fr) * 2019-09-27 2021-04-01 Qualcomm Incorporated Gestion de conflits entre une planification dynamique et des ressources d'accès aléatoire
US20210100038A1 (en) * 2019-09-30 2021-04-01 Qualcomm Incorporated Apparatus and methods for synchronization signal and random access communications in full duplex
WO2021066697A1 (fr) * 2019-09-30 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Procédés, équipement utilisateur et noeud de réseau pour gérer des configurations de prach
WO2021180066A1 (fr) * 2020-03-11 2021-09-16 华为技术有限公司 Procédé et appareil de transmission de données de liaison montante
US20210337489A1 (en) * 2020-04-24 2021-10-28 Qualcomm Incorporated Synchronization signal block (ssb) in full-duplex
CN113905434A (zh) * 2020-07-06 2022-01-07 维沃移动通信有限公司 下行控制信息的传输方法、终端设备和网络设备
WO2022031805A1 (fr) * 2020-08-05 2022-02-10 Google Llc Procédures rach pour demander des informations de support de tranche
WO2022052117A1 (fr) * 2020-09-14 2022-03-17 华为技术有限公司 Procédé et appareil pour configurer une liaison montante supplémentaire (sul)
WO2022061564A1 (fr) * 2020-09-23 2022-03-31 Qualcomm Incorporated Accès initial sur la base de ssb 3d
WO2022071755A1 (fr) * 2020-09-29 2022-04-07 엘지전자 주식회사 Procédé et appareil pour émettre et recevoir un signal sans fil dans un système de communication sans fil
CN114499794A (zh) * 2020-11-11 2022-05-13 上海朗帛通信技术有限公司 一种用于无线通信的节点中的方法和装置
CN114762380A (zh) * 2020-02-28 2022-07-15 Oppo广东移动通信有限公司 控制信道资源的确定方法、设备及存储介质
EP4055938A4 (fr) * 2019-11-07 2023-07-19 Qualcomm Incorporated Configuration améliorée pour masque de canal physique d'accès aléatoire et fenêtre de réponse d'accès aléatoire
WO2023137762A1 (fr) * 2022-01-24 2023-07-27 Beijing Unisoc Communications Technology Co., Ltd. Procédé et dispositif pour réseau d'accès aléatoire
US11968634B2 (en) 2020-04-24 2024-04-23 Qualcomm Incorporated Synchronization signal block (SSB) in full-duplex
WO2024092488A1 (fr) * 2022-11-01 2024-05-10 Qualcomm Incorporated Sélections pour des communications de canal d'accès aléatoire physique
EP4256887A4 (fr) * 2021-01-12 2024-06-05 Samsung Electronics Co., Ltd. Équipement utilisateur pour accès aléatoire et procédé associé, station de base pour accès aléatoire et procédé associé
CN114451059B (zh) * 2019-09-30 2024-11-15 高通股份有限公司 用于全双工中的同步信号和随机接入通信的装置和方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC: "On 4-step RACH procedure", vol. RAN WG1, no. Qingdao, P.R. China; 20170627 - 20170630, 26 June 2017 (2017-06-26), XP051300028, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170626] *
MEDIATEK INC: "RAR design supporting muiltiple preamble transmission", vol. RAN WG2, no. Berlin, Germany; 20170821 - 20170825, 20 August 2017 (2017-08-20), XP051317959, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170820] *
ZTE ET AL: "Remaining details of RACH procedure", vol. RAN WG1, no. Prague, Czech Republic; 20171009 - 20171013, 8 October 2017 (2017-10-08), XP051340228, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20171008] *

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10945286B2 (en) 2018-08-03 2021-03-09 Qualcomm Incorporated Beam-specific system information scheduling window design
WO2021005575A1 (fr) * 2019-07-10 2021-01-14 Telefonaktiebolaget Lm Ericsson (Publ) Réduction au minimum de charge de signalisation pendant un transfert intercellulaire de ntn
US12096290B2 (en) 2019-07-10 2024-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Minimizing signaling load during handover for NTN
US11470596B2 (en) 2019-07-18 2022-10-11 Samsung Electronics Co., Ltd. Determination of start time of PDCCH monitoring occasion
CN112242896A (zh) * 2019-07-18 2021-01-19 三星电子株式会社 Pdcch监视时机的开始时间的确定
US11917645B2 (en) 2019-07-18 2024-02-27 Samsung Electronics Co., Ltd. Determination of start time of PDCCH monitoring occasion
WO2021022392A1 (fr) 2019-08-02 2021-02-11 Qualcomm Incorporated Techniques de commutation de porteuse pour accès aléatoire en deux étapes
EP4008145A4 (fr) * 2019-08-02 2023-03-15 QUALCOMM Incorporated Techniques de commutation de porteuse pour accès aléatoire en deux étapes
WO2021026710A1 (fr) * 2019-08-12 2021-02-18 Qualcomm Incorporated Association de blocs de signaux de synchronisation à des occasions d'accès aléatoire
US12035359B2 (en) 2019-09-27 2024-07-09 Qualcomm Incorporated Handling conflicts between dynamic scheduling and random access resource
US11297645B2 (en) 2019-09-27 2022-04-05 Qualcomm Incorporated Handling conflicts between dynamic scheduling and random access resources
WO2021062126A1 (fr) * 2019-09-27 2021-04-01 Qualcomm Incorporated Gestion de conflits entre une planification dynamique et des ressources d'accès aléatoire
CN114521346A (zh) * 2019-09-27 2022-05-20 高通股份有限公司 处置动态调度与随机接入资源之间的冲突
WO2021067001A1 (fr) * 2019-09-30 2021-04-08 Qualcomm Incorporated Appareil et procédés de communications de signal de synchronisation et d'accès aléatoire en duplex intégral
WO2021066697A1 (fr) * 2019-09-30 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Procédés, équipement utilisateur et noeud de réseau pour gérer des configurations de prach
US20210100038A1 (en) * 2019-09-30 2021-04-01 Qualcomm Incorporated Apparatus and methods for synchronization signal and random access communications in full duplex
US11503652B2 (en) 2019-09-30 2022-11-15 Qualcomm Incorporated Apparatus and methods for synchronization signal and random access communications in full duplex
CN114451059A (zh) * 2019-09-30 2022-05-06 高通股份有限公司 用于全双工中的同步信号和随机接入通信的装置和方法
CN114451059B (zh) * 2019-09-30 2024-11-15 高通股份有限公司 用于全双工中的同步信号和随机接入通信的装置和方法
EP4055938A4 (fr) * 2019-11-07 2023-07-19 Qualcomm Incorporated Configuration améliorée pour masque de canal physique d'accès aléatoire et fenêtre de réponse d'accès aléatoire
CN114762380A (zh) * 2020-02-28 2022-07-15 Oppo广东移动通信有限公司 控制信道资源的确定方法、设备及存储介质
WO2021180066A1 (fr) * 2020-03-11 2021-09-16 华为技术有限公司 Procédé et appareil de transmission de données de liaison montante
CN115428388A (zh) * 2020-04-24 2022-12-02 高通股份有限公司 全双工中的同步信号块(ssb)
CN115428388B (zh) * 2020-04-24 2024-06-11 高通股份有限公司 全双工中的同步信号块(ssb)
US11968634B2 (en) 2020-04-24 2024-04-23 Qualcomm Incorporated Synchronization signal block (SSB) in full-duplex
US12063604B2 (en) * 2020-04-24 2024-08-13 Qualcomm Incorporated Synchronization signal block (SSB) in full-duplex
US20210337489A1 (en) * 2020-04-24 2021-10-28 Qualcomm Incorporated Synchronization signal block (ssb) in full-duplex
CN113905434A (zh) * 2020-07-06 2022-01-07 维沃移动通信有限公司 下行控制信息的传输方法、终端设备和网络设备
WO2022031805A1 (fr) * 2020-08-05 2022-02-10 Google Llc Procédures rach pour demander des informations de support de tranche
WO2022052117A1 (fr) * 2020-09-14 2022-03-17 华为技术有限公司 Procédé et appareil pour configurer une liaison montante supplémentaire (sul)
WO2022061564A1 (fr) * 2020-09-23 2022-03-31 Qualcomm Incorporated Accès initial sur la base de ssb 3d
WO2022071755A1 (fr) * 2020-09-29 2022-04-07 엘지전자 주식회사 Procédé et appareil pour émettre et recevoir un signal sans fil dans un système de communication sans fil
CN114499794A (zh) * 2020-11-11 2022-05-13 上海朗帛通信技术有限公司 一种用于无线通信的节点中的方法和装置
WO2022100638A1 (fr) * 2020-11-11 2022-05-19 上海朗帛通信技术有限公司 Procédé et appareil utilisés dans un nœud pour des communications sans fil
EP4256887A4 (fr) * 2021-01-12 2024-06-05 Samsung Electronics Co., Ltd. Équipement utilisateur pour accès aléatoire et procédé associé, station de base pour accès aléatoire et procédé associé
WO2023137762A1 (fr) * 2022-01-24 2023-07-27 Beijing Unisoc Communications Technology Co., Ltd. Procédé et dispositif pour réseau d'accès aléatoire
WO2024092488A1 (fr) * 2022-11-01 2024-05-10 Qualcomm Incorporated Sélections pour des communications de canal d'accès aléatoire physique

Also Published As

Publication number Publication date
TW201937973A (zh) 2019-09-16

Similar Documents

Publication Publication Date Title
US11871384B2 (en) Random access in new radio (NR) and other beamforming systems
US11844105B2 (en) Initial access and channel access in new radio/new radio-unlicensed (NR/NR-U)
WO2019099443A1 (fr) Multiples occasions de surveillance au niveau d&#39;un ensemble de ressources de commande de canal d&#39;accès aléatoire
EP3603241B1 (fr) Transmission de messagerie par mise en forme de faisceau
CA3130285A1 (fr) Procedes et appareil de transmission de msg-a dans un rach a deux etapes
WO2018232123A1 (fr) Procédures rach dans un spectre sans licence
EP3577793A1 (fr) Gestion de faisceau de liaison montante
WO2020033513A1 (fr) Transmission et détection d&#39;informations de commande dans des systèmes sans fil
US20210135825A1 (en) Methods and apparatuses for non-orthogonal multiple access
WO2019160849A1 (fr) Ordonnancement et transmission pour noma
WO2019195585A1 (fr) Procédé et appareil pour une atténuation de collision et une réduction de complexité dans des transmissions noma
WO2020076953A1 (fr) Procédés et procédures d&#39;accès aléatoire physique simplifié pour nr-u
WO2018204351A1 (fr) Multiplexage et mappage de signaux de synchronisation en nr
WO2023055934A1 (fr) Approches de partie bwp robustes pour atténuer l&#39;impact d&#39;un brouilleur à bande étroite haute puissance
JP7582877B2 (ja) ビームフォーミングシステムにおけるＮｅｗ Ｒａｄｉｏランダムアクセス
US20230363006A1 (en) Rach Enhancements for Radar Coexistence
WO2024211401A1 (fr) Commande de puissance de transmission de prach avec un indice de transmission dans un ordre de pdcch
WO2024173407A1 (fr) Transmission de wtru d&#39;une indication pour changer un motif de blocage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18815426

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18815426

Country of ref document: EP

Kind code of ref document: A1