Methods, architectures, apparatuses, and systems for determining power offset and timing advance information for receive-only point based deployments

Abstract

Processes, methods, architectures, apparatus, systems, devices, and computer program products for determining power offset and timing advance information for a receive-only point based deployment. A wireless transmit receive unit (WTRU) can receive downlink control information from a transmission receive point (TRP) indicating that the WTRU is to transmit a physical random access channel (PRACH) transmission to a receive-only point (ROP). The WTRU can determine a transmission power for the PRACH transmission. The WTRU can transmit a preamble using the determined power. The WTRU can receive a random access response. The random access response can include a timing advance value (TA) for the ROP and / or a power offset for transmissions to the ROP. The WTRU can receive scheduling information for an uplink (UL) transmission to the ROP, and the WTRU can transmit the UL transmission to the ROP using the TA / power offset.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application 63 / 615,122, filed December 27, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, apparatus, and systems related to uplink-only (UL) transmit-receive-point (TRP) operation. Background Technology

[0003] UL-only TRP operation is considered one of the candidate topics for Rel-19 Multiple-Input Multiple-Output (MIMO). The aim is to improve uplink throughput, coverage, and reliability performance of cell-edge user equipment (UEs) and alleviate limitations caused by large path loss and UE transmission power. Furthermore, UL-only TRP operation reduces deployment costs and is easier to deploy due to less consideration for downlink interference planning.

[0004] Because there is no downlink transmission of any kind from any of the UL-only TRPs in this deployment, all downlink (DL) transmissions originate strictly from the serving TRP. A typical deployment includes at least one TRP with both downlink and uplink transmission capabilities, and at least one receiver-only point (ROP). Summary of the Invention

[0005] The purpose of uplink-only deployment is to improve cell capacity, reliability, and coverage by receiving and combining uplink signals received by the TRP and ROP. However, in the absence of a DL reference signal from the ROP, it is not simple to determine how the UE should determine the power, beam direction, and timing advance (TA) for uplink transmission so that the transmitted signal can be correctly received and compatibly combined by both the TRP and ROP.

[0006] Embodiments that are disclosed, described and claimed in the appended claims contribute to further improvements to new radio networks. Attached Figure Description

[0007] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. As with the detailed description, the figures in these drawings are illustrative. Therefore, the drawings and detailed description should not be considered limiting, and other equivalent examples may be possible and are probable. Furthermore, the same reference numerals (“ref”) in the figures indicate the same elements, and wherein: Figure 1AThis is a system diagram illustrating an exemplary communication system; Figure 1B It shows that it can be shown Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used within the communication system shown; Figure 1C It shows that it can be shown Figure 1A System diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used in the communication system shown; Figure 1D It shows that it can be shown Figure 1A System diagrams of additional exemplary RANs and additional exemplary CNs used within the communication system shown; Figure 2 The diagram illustrates conventional (A) and uplink-only (B) TRP operations; Figure 3 Table 1 shows the DCI format 1_0 for the PDCCH command; and Figure 4 Examples of ROP power offsets associated with the measured RSRP ranges in Table 2 are shown; Figure 5 This is a flowchart of the process by which WTRU determines the power settings and power correction for ROP transmission based on RAR information; Figure 6 This is an embodiment of a method for determining the spatial beam for RACH transmission of PDCCH commands; Figure 7 This is a flowchart of a method 700 for determining power offset and TA information for ROP-based deployments, which can be applied, for example, to... Figure 2 Network topology in B); Figure 8 This is a flowchart of a method 800 for determining the beam and power offset for RACH transmission, which can be applied, for example, to... Figure 2 The network topology in B); and Figure 9 This is a flowchart of method 900 according to an embodiment. Detailed Implementation

[0008] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, processes, components, and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of, or in combination with, the embodiments and other examples described, disclosed, or otherwise expressly, implicitly, and / or inherently provided herein (collectively, the “Provided”). Although various embodiments in which apparatuses, systems, devices, etc., and / or any elements thereof perform operations, processes, algorithms, functions, etc., and / or any portions thereof are described and / or claimed herein, it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, device, etc., and / or any element thereof is configured to perform any operation, process, algorithm, function, etc., and / or any portion thereof.

[0009] In the following text, the acronyms PRACH (Physical Random Access Channel) and RACH (Random Access Channel) are used interchangeably to describe embodiments. The principles, methods, and embodiments described are applicable to random access procedures using formats other than PRACH / RACH.

[0010] Abbreviations and Acronyms ACK confirmation A-MPR Additional Maximum Power Reduction BLER block error rate BWP bandwidth portion CAP channel access priority CAPC Channel Access Priority Category CCA Idle Channel Assessment CCE control channel element CE control elements CG configuration authorization or cell group CP loop prefix CP-OFDM conventional OFDM (depending on the cyclic prefix) CQI Channel Quality Indicator CRC Cyclic Redundancy Check CSI Channel Status Information CW Competition Window CWS Competition Window Size CO channel occupancy DAI Downlink Allocation Index DCI downlink control information DFI downlink feedback information DG Dynamic Licensing DL downlink DM-RS demodulation reference signal DRB Data Radio Bearer eLAA Enhanced Authorization Assisted Access FeLAA Further Enhanced Authorized Assisted Access HARQ Hybrid Automatic Repeat Request LAA Authorized Assisted Access LBT listens before speaking LTE Long Term Evolution (e.g., from 3GPP LTE Release 8 and subsequent versions) LTM layer 1 triggers mobility NACK (Negative Confirmation) MAC CE Media Access Control Element MCS Modulation and Coding Scheme MIB Master Information Block MIMO (Multiple Input Multiple Output) MPR maximum power reduction MTRP Multiple Transmitter / Receiver Point NR New Radio OFDM (Orthogonal Frequency Division Multiplexing) OLPC open-loop power control PBCH Physical Broadcast Channel PCI Physical Cell Identifier PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PHY physical layer PID Process ID PL path loss P-MPR power rating maximum power reduction PO paging timing PRACH Physical Random Access Channel PSS master synchronization signal PUCCH (Physical Uplink Control Channel) PUSCH Physical Uplink Shared Channel QCL Quasi-co-addressable RA random access (or procedure) RACH Random Access Channel RAR Random Access Response RCU Radio Access Network Central Unit RF front end RLF radio link failure RLM radio link monitoring RNTI Radio Network Identifier RORACH timing ROP (Receiving Point Only) RRC Radio Resource Control RRM Wireless Resource Management RS reference signal RSRP reference signal received power RSSI Received Signal Strength Indicator RTT round trip time SIB System Information Block SDU Business Data Unit SNR signal-to-noise ratio SRISRS Resource Indicator SRS detection reference signal SS Synchronization Signal SSB Synchronization Signal Block SSS auxiliary synchronization signal SUL supplements uplink SWG switching interval (within a self-contained subframe) SPS semi-persistent scheduling SUL supplements uplink TA scheduled in advance TB transport block TBS Transfer Block Size TCI transmission configuration indication TPC transmission power control TRP Transmit / Receive Point TSC Time-Sensitive Communication TSN Time-Sensitive Network UL uplink URLLC offers highly reliable, low-latency communication. uTAP uplink transmission adjustment parameters WBWP wide bandwidth portion WLAN wireless local area network and related technologies (IEEE 802.xx domain).

[0011] Exemplary communication system The methods, apparatus, and systems provided herein are well-suited for communications involving both wired and wireless networks. Regarding... Figure 1A-1D An overview of various types of wireless devices and infrastructures is provided, wherein various elements of a network can utilize, perform, be arranged according to, and / or be adapted to and / or configured for use with the methods, apparatuses and systems provided herein.

[0012] Figure 1AThis is a system diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources (including wireless broadband). For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail (ZT) Unique Word (UW) Discrete Fourier Transform (DFT) Extended OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0013] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 108, the Internet 110, and other networks 112. However, it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or) user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0014] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly connect to at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b can be any of a base transceiver station (BTS), Node-B (NB), eNode B (eNB), home NodeB (HNB), home eNode B (HeNB), gNode-B (gNB), NR Node-B (NR NB), site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0015] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (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 specific geographic area that may be relatively fixed or may change over time. A cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell or any sector. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0016] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0017] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 104 / 113 and WTRUs 102a, 102b, 102c can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

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

[0019] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

[0020] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for instance, use the dual connectivity (DC) principle to jointly implement LTE radio access and NR radio access. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0021] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global System for Multi-Use Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0022] Figure 1A Base station 114b can be, for example, a wireless router, a home Node-B, a home eNode-B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in localized areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for use by drones), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-a, LTE-a Pro, NR, etc.) to establish any of the following: small cells, pico cells, and femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106 / 115.

[0023] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions (such as user authentication). Although Figure 1AAs not shown, but will be understood, RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs employing the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may be utilizing NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) employing any of the following radio technologies: GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, and Wi-Fi.

[0024] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 114 or a different RAT.

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

[0026] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other components / peripherals 138, etc. It will be understood that, while remaining consistent with the embodiments, WTRU 102 may include any sub-combination of the foregoing components.

[0027] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it will be understood that the processor 118 and transceiver 120 can be integrated together, for example, in an electronic package or chip.

[0028] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In an embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In an embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF signals and optical signals. It will be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0029] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. For example, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0030] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, transceiver 120 can include multiple transceivers for enabling WTRU 102 to communicate via various RATs (e.g., such as NR and IEEE 802.11).

[0031] The processor 118 of WTRU 102 can be coupled to and receive user input data from: a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Additionally, the processor 118 can access information and store data from any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access information and store data from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)).

[0032] The processor 118 may receive power from the power supply 134 and may be configured to distribute power to other components in the WTRU 102 and / or control power to those other components. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 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, etc.

[0033] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable location determination method.

[0034] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software modules and / or hardware modules / units providing additional features, functions, and / or wired or wireless connectivity. For example, components / peripherals 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (e.g., for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Components / peripherals 138 may include one or more sensors, which may be gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors, or more of these.

[0035] WTRU 102 may include a full-duplex radio, for which the transmission and reception of some or all of the signals (e.g., signals associated with a specific subframe of both the uplink (e.g., for transmission) and the 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 through signal processing via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via processor 118). In embodiments, WTRU 102 may include a half-duplex radio, for which the transmission and reception of some or all of the signals (e.g., signals associated with a specific subframe of both the uplink (e.g., for transmission) and the downlink (e.g., for reception)) are separate.

[0036] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

[0037] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it will be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a.

[0038] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

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

[0040] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0041] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to or from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during eNode-B handover, triggering paging when DL data is available to WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0042] SGW 164 can be connected to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0043] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional terrestrial line communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108, or can communicate with it. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0044] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is conceivable that in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0045] In a representative embodiment, the other network 112 may be a WLAN.

[0046] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may access or interface with a Distribution System (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between a source STA and a destination STA using a Direct Link Setup (DLS) (e.g., directly between them). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this article.

[0047] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented, for example, in an 802.11 system. For CSMA / CA, the AP STA (e.g., each STA) can sense the primary channel. If a particular STA senses / detects that the primary signal is busy and / or determines that the primary signal is busy, that particular STA can back off. In a given BSS, at any given time, only one STA (e.g., only one station) can transmit.

[0048] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0049] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. In the 80+80 configuration, data, after channel coding, can be passed through a fragment parser that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. The streams can be mapped onto the two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

[0050] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV Blank (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument-type control / machine-type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, including, for example, limited capabilities to support (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0051] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STAs operating in the BSS that support the minimum bandwidth operating mode. In the 802.11ah example, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide 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 Sense and / or Network Assignment Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band may be considered busy even if most of the band remains idle and potentially available.

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

[0053] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 may also communicate with CN 115.

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

[0055] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with a scalable set of parameters. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can be varied for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various lengths or scalable lengths (e.g., including different numbers of OFDM symbols and / or absolute times of varying durations).

[0056] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can use one or more of gNBs 180a, 180b, and 180c as mobile anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c while also communicating / connecting with another RAN (such as eNode-Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobile anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput to serve WTRUs 102a, 102b, and 102c.

[0057] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink (UL) and / or downlink (DL), support for network slicing, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

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

[0059] AMF 182a and 182b can connect to one or more of the gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing, for example, to customize CN support for WTRU 102a, 102b, and 102c based on the service types being used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, and services for MTC access. AMF 162 can provide control plane functions for switching between RAN 113 and other RANs (not shown) that employ other radio technologies (such as LTE, LTE-A, LTE-A Pro) and / or non-3GPP access technologies (such as Wi-Fi).

[0060] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure them to route traffic through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, or Ethernet-based.

[0061] UPF 184a and 184b can be connected via the N3 interface to one or more of the gNBs 180a, 180b, and 180c in RAN 113. These gNBs can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110), for example, to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

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

[0063] Given Figures 1A to 1D and Figures 1A to 1D The corresponding description can be performed by one or more of the functions described herein with respect to any of the following: WTRU 102a to 102d, base stations 114a to 114b, eNode-B 160a to 160c, MME 162, SGW 164, PGW 166, gNB 180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b, and / or any other element / device described herein. The simulation device can be one or more devices configured to simulate one or more of the functions described herein. For example, the simulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0064] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices may perform one or more functions when fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices may perform one or more functions when temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communication to perform tests.

[0065] One or more simulation devices may perform one or more functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, a simulation device may be used to test scenarios in a laboratory and / or an undeployed (e.g., tested) wired and / or wireless communication network to perform testing of one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via an RF circuit system (e.g., which may include one or more antennas).

[0066] UL TRP-only operation is considered one of the candidate topics for Rel-19 MIMO. Its aim is to improve uplink throughput, coverage, and reliability performance of cell-edge UEs, and to alleviate limitations caused by large path loss and WTRU transmission power. Furthermore, UL TRP-only operation reduces deployment costs and is easier to deploy due to less consideration for downlink interference planning.

[0067] Because there is no downlink transmission of any kind from any of the UL-only TRPs in this deployment, all DL transmissions originate strictly from the serving TRP. A typical deployment includes at least one TRP with both downlink and uplink transmission capabilities, and at least one receiver-only point (ROP). Figure 2 Two different deployments (A and B) based on a traditional (A) and a UL-only (B) TRP are shown. In the UL-only TRP, the ROP connects to the main TRP via backhaul. Once the ROP receives the uplink signal, after some basic initial processing, the remaining signals, which will be used for further processing, are shared with the main TRP.

[0068] The purpose of uplink-only deployment is to improve cell capacity, reliability, and coverage by receiving and combining uplink signals received by the TRP and ROP. However, without a DL reference signal from the ROP, it is not straightforward to determine the power, beam direction, and TA (timing advance) for uplink transmission so that the transmitted signal can be correctly received and compatibly combined by both the TRP and ROP. For example, uplink transmission should be performed using the following: a) Timing within the available processing windows of both TRP and ROP; b) Sufficiently high power levels for both TRP and ROP without any harmful interference; c) Transmission directions from which both TRP and ROP can benefit.

[0069] In the absence of a DL reference signal from the ROP, it may be of interest to know how to determine the power, beam direction, and TA used for uplink transmission.

[0070] Methods for power offset and TA information WTRU behavior: Determines power offset and TA information for ROP-based deployments. According to an embodiment, determining the power offset and TA information for ROP-based deployment may include one or more of the following steps: In the first step, the WTRU can receive a DCI (Dynamic Indication) (e.g., a PDCCH instruction) from the first (primary, serving) TRP (cell, primary cell, serving cell), which instructs the PRACH preamble to be transmitted to the ROP: a) DCI may include an indication (e.g., a flag) that the transmission destination is a ROP, or a specific DCI format or RNTI may be used to indicate that the transmission destination is a ROP; b) The DCI may indicate (e.g., via TCI status or SRI) the first beam or RS associated with the first TRP (e.g., the SSB or CSI-RS of the first TRP, or the SSB or CSI-RS configured for the first TRP). For example, the first beam / RS indicated by the gNB may be the best beam / RS for communicating with the first TRP, or a beam / RS that is at least sufficient to communicate with each (or both) of the TRP and ROP. c) DCI may indicate a preamble and / or one or more PRACH resources associated with ROP, or a preamble and / or one or more PRACH resources configured for ROP; d) DCI can indicate power offset (e.g., to ensure that the ROP can receive the transmission); In the second step, the WTRU may determine the transmission (Tx) power for PRACH transmission based on at least one of the following: a) Path loss (PL) or RSRP measurement determined for the indicated first beam or RS; b) The indicated power offset, such as the Tx power calculated in general (e.g., based on PL, target SNR, etc.), can be increased by the power offset (Tx power = Tx power + power offset), or, for example, PL can be adjusted by the power offset (e.g., PL = PL + power offset). c) WTRU uses the determined Tx power transmission preamble.

[0071] In the third step, the WTRU can transmit the indicated preamble, or the preamble selected by the WTRU based on the indicated first beam or RS.

[0072] In the fourth step, the WTRU may use resources in the indicated PRACH resources or PRACH resources associated with the indicated first beam or RS to transmit the preamble.

[0073] In the fifth step, the WTRU may receive a Random Access Response (RAR) or another message (e.g., from the first TRP). The RAR or other message may contain one or more of the following: a) TA value for ROP; b) The TA value for the first TRP; c) A TA value, which indicates whether the TA value is for the first TRP or the ROP; d) Power offset values ​​for ROP, such as new or updated power offset values; e) TPC commands for the ROP; f) TPC commands for the TRP; g) A TPC command having an indication of whether the TPC command is for the first TRP or the ROP; h) A second beam or RS used to transmit to the ROP (e.g., it is associated with or configured for the first TRP).

[0074] In the sixth step, the WTRU can receive planning information for UL transmissions to the ROP (such as PUSCH or SRS).

[0075] In step seven, the WTRU can transmit UL data to the ROP: a) The WTRU may use power determined based on at least one of the following to transmit UL transmission to the ROP: a1) The power offset indicated in the DCI that initiates the PRACH transmission; a2) Power offset indicated in the RAR or other messages; a3) TPC commands for ROP indicated in RAR or other messages.

[0076] b) The WTRU may use a second beam or RS to transmit UL transmission to the ROP (e.g., to determine the space filter for UL transmission); c) WTRU can use timing based on the TA value for ROP received in RAR or other messages to transmit UL transmission to ROP.

[0077] Details of PDCCH command RACH and initial power determination for (P)RACH transmission The concepts and embodiments discussed can generally be applied to multi-TRP deployments with any number of TRPs; however, for the sake of simplicity and to facilitate the presentation of embodiments, a 2-TRP deployment is typically used.

[0078] When the WTRU is configured in a multi-TRP scenario, where the second TRP is a Receive-Only Point (ROP), the WTRU is expected to use the first TRP as an anchor point for timing synchronization and full access stratum (AS) communication, while the ROP will be used as a diversity receive point for the system, and thus may increase the WTRU UL throughput.

[0079] Since the WTRU is considered to be fully synchronized with the anchored TRP and has a reliable radio link, the gNB can request the WTRU auxiliary system to obtain UL synchronization for the ROP. This means that the WTRU may have to transmit a PRACH preamble or SRS in the UL, which will allow the gNB to assess the UL timing requirements and power for the ROP.

[0080] In the Rel-18 multi-TRP scenario, the PDCCH instruction RACH via DCI format 1_0 allocates one bit (remaining from previous versions) of the 10 reserved bits for inter-cell PCI PRACH target indication. Additionally, it can also be used for intra-cell cross-TRP target indication. Two more bits are allocated to LTM (Layer 1 Triggered Mobility) target inactive PCI for handover purposes. Therefore, seven bits are reserved for potential future uses.

[0081] The current PDCCH instruction RACH, delivered via DCI format 1_0, contains an SSB index or a second RS associated with the TRP that issued the instruction. When the target of the PRACH is different from the TRP that transmitted the PDCCH instruction, its source RS is configured for path loss estimation PCI or TCI (or an RS associated with a QCL) via RRC to a specific configuration.

[0082] See Figure 3 Table 1 in the table shows the DCI format 1_0 (Rel-18) used for the PDCCH instruction.

[0083] In a multi-TRP deployment with one or more ROPs, the WTRU may have to rely on its RS or SSB, which is associated with the primary TRP path loss, as the computational basis for any possible initial power estimation for PRACH.

[0084] According to an embodiment, the WTRU can be configured with specific ROP UL access parameters, which can be one or a combination of the following: a) The set of PRACH preamble indices; b) A specific set of TCI states associated with ROP operation; c) Link to a specific set of SRIs for the ROP operation; d) A specific set of power offsets that can be linked / associated to an RSRP threshold or range, which can be linked to a specific anchor TRP-related SSB set; e) Specific PRACH timing (RO) set; f) A specific UL scan PRACH timing set used for beam pairing.

[0085] The WTRU can be configured with a ROP configuration, which depends on the WTRU's capabilities and allows the WTRU to transmit simultaneously on two beams within the CP, or allows the WTRU to transmit simultaneously on two beams from two or more different panels with a transmission time difference higher than the CP.

[0086] When the WTRU can transmit on two beams with a transmission time difference greater than CP, appropriate timing advance (TA) acquisition may be required, and therefore the WTRU can use PRACH transmission for this purpose. The PDCCH instruction PRACH can be issued by the anchored TRP, and the PDCCH instruction PRACH can contain an indication that the ROP is targeted.

[0087] The current initial PRACH power is determined according to the following equation:

[0088] The PRACH preamble receive power target, along with Delta_Preamble and Preamble_Power_Ramping_Step for different preamble formats, is signaled by the network in the RRC. Essentially, in equation (1), Pcmax is related to the WTRU power level and MPR, A-MPR, or P-MPR as coexistence and exposure parameters, respectively, while the PRACH initial power is: Power_PRACH_target = preambleReceivedTargetPower + Delta_Preamble +(Preamble_Ramping_Counter -1) x Preamble_Power_Ramping_Step Where Preamble_Ramping_Counter = 1, it means: Power_PRACH_target = preambleReceivedTargetPower + Delta_Preamble.

[0089] We notice that "x" represents multiplication.

[0090] When the WTRU receives the ROP target indication on the PDCCH command, the WTRU can interpret the remainder of the DCI information based on the ROP configuration information regarding PRACH initial power determination, PRACH preamble, and mask index.

[0091] According to an embodiment, the WTRU may be configured with one or more power offset values, wherein each power offset value may be associated with a measurement, another configured system parameter, etc.

[0092] In an exemplary embodiment, the configured power offset value may be associated with a downlink measurement (e.g., RSRP).

[0093] In an exemplary embodiment, the WTRU can use and evaluate, for example, the RSRP measured from the RS signaled in DCI format 1_0, and find, for example, that the RSRP falls within one of the power offsets associated with a specific range configured by the RRC. In this case, for example, the WTRU can calculate the initial PRACH power by adding the corresponding configuration offset based on the following relationships in exemplary Table 2, one or more of which can be applied: a) One or more ROP power offset sets can be configured, and one of the sets can be used, wherein the ROP power offset set can be determined based on WTRU location.

[0094] a1) The WTRU location can be based on at least one of the following: a1a) The location of the WTRU within the cell (e.g., actual location, area); The distance between a1b and gNB (e.g., RTT, TA, path loss, RSRP value).

[0095] a 2) Each set can have at least one ROP_offset value.

[0096] a3) The ROP power offset can be determined based on the transmission type.

[0097] (a3a) For example, the WTRU can be configured with more than one ROP power offset, one of which can be applied to the PUSCH, another to the PUCCH, another to the SRS, and so on.

[0098] (a3b) In another example, the ROP power offset can be associated with the priority and content of the transmission. For example, the ROP power offset for a high-priority PUSCH (such as URLLC) can be different from that for a PUSCH transmission with normal priority.

[0099] b) The ROP_offset value can be dynamically indicated (e.g., in the PDCCH instruction).

[0100] According to an alternative embodiment, in addition to the power offset value, the WTRU may also be configured with one or more reference signals and / or timing advance information for PRACH beam determination, each of which may be associated with measurements, other configured system parameters, etc. For example, Figure 4 Table 2 in the table can be expanded to include additional rows to indicate reference signals and / or timing advance information used for PRACH beam determination.

[0101] According to the embodiments, one or more of the following may be applied: a) One or more sets of reference signals and / or timing advance information can be configured for PRACH beam determination, and one of the sets can be used, wherein the ROP reference signal set and / or timing advance information for PRACH beam determination can be determined based on the WTRU location.

[0102] a1) The WTRU location can be based on at least one of the following: a1a) The location of the WTRU within the cell (e.g., actual location, area); The distance between a1b and gNB (e.g., RTT, TA, path loss, RSRP value).

[0103] a2) Each set may have at least one reference signal and / or timing advance information value for PRACH beam determination.

[0104] a3) Reference signals and / or timing advance information for PRACH beam determination can be determined based on the transmission type.

[0105] 3a) For example, the WTRU can be configured with more than one reference signal and / or timing advance information for PRACH beam determination, one of which can be applied to PUSCH, another to PUCCH, another to SRS, and so on.

[0106] (a3b) In another example, the reference signal and / or timing advance information used for PRACH beamforming may be associated with the priority and content of the transmission. For example, the ROP power offset for a high-priority PUSCH (e.g., URLLC) may differ from that for a PUSCH transmission with normal priority.

[0107] b) The ROP_offset value can be dynamically indicated (e.g., in the PDCCH instruction). The RSRP used for estimating PL parameters (e.g., path loss) can be based on a measurement of RS as indicated in the PDCCH directive.

[0108] Therefore, if the RSRP measured for the indicated RS falls within the following Range _2, then WTRU can use, for example, ROP_Offset _2: Power_PRACH_target = preambleReceivedTargetPower + Delta_Preamble +ROP_Offset_2 According to another embodiment, since the network has already received RSRP measurements from the WTRU, the ROP_Offset index can be directly signaled in the PDCCH command. Alternatively, the ROP_Offset can be explicitly signaled in dB using the PDCCH command RACH.

[0109] a) The ROP_offset value can accumulate over time. For example, ROP_Offset_2(k) = ROP_Offset_2(k-1) + delta_ROP_offset, where k is the moment when the ROP offset is calculated, k-1 is the most recent moment during which ROP_Offset_2 is updated, and delta_ROP_offset is indicated by gNB to update the ROP_Offset_2 value.

[0110] The WTRU can be configured with a time window for receiving RARs transmitted in a PRACH configured for a ROP (e.g., a ra-ResponseWindow configured for the presence of a ROP). The RAR time window begins at the time of the symbol transmission preamble of the first symbol of the earliest CORESET that begins after the PRACH timing. A CORESET can be configured with a first TRP or ROP, and the time window can be relative to the CORESET of either TRP. Within this time window, the WTRU monitors the DCI scrambled with RNTI (e.g., RA-RNTI configured for the presence of a ROP) and expects to receive RARs. If the WTRU does not receive a ROP-specific RAR within a particular time window, the WTRU can perform PRACH ramping and retransmission based on the ROP-specific / ROP-configured / PRACH timing configured for the ROP.

[0111] According to another embodiment, the WTRU can use PRACH scanning in consecutive ROs to determine the UL beam associated with the ROP. In this embodiment, the WTRU can receive specific beam scan PRACH instructions, where specific preamble instructions can be used in specific modes, so that upon receiving a RAR message, the specific UL beam with the best ROP correspondence is found and established, the RAR message confirming the pairing by indicating, for example, the preamble index used in the scan in a specific direction.

[0112] Details of PRACH transmission The WTRU can perform PRACH transmissions in cells where ROPs may be used, supported, or deployed. For example, the WTRU can receive ROP-related information during the initial access procedure and / or system information update procedure (e.g., in broadcast signals, SIBs, MIBs, DCIs), and the WTRU can perform PRACH transmissions.

[0113] According to an embodiment, when the WTRU receives an indication that ROP is supported in the cell, the WTRU may perform a first type of PRACH transmission; otherwise, the WTRU may perform a second type of PRACH transmission.

[0114] a) In the first type of PRACH transmission, the WTRU may perform one or more of the following operations: a1) The WTRU can transmit PRACH at a predetermined transmission power (e.g., configured or indicated in the SIB at the Tx power level); a2) The maximum transmission power used for the first type of PRACH transmission may differ from the maximum transmission power used for the second type of PRACH transmission; a3) The WTRU can transmit the PRACH preamble in a PRACH timing (RO), which may not be associated with an SSB index determined by the WTRU. Instead, an offset (e.g., SSB index offset) value can be applied to determine a virtual SSB index associated with the RO used for the first type of PRACH transmission: a3a) The offset can be provided by SSB index in the broadcast signal (e.g., SIB).

[0115] a4) The WTRU can transmit PRACH using all possible uplink beams. One or more ROs can be configured for uplink beam scanning used for PRACH transmission; b) The second type of PRACH transmission is the traditional PRACH transmission: b1) WTRU can perform PRACH preamble transmission at a determined PRACH timing (RO), where the RO can be determined based on a determined SSB index.

[0116] According to another embodiment, the WTRU can receive uplink transmission adjustment parameters (e.g., power offset TA) in a message (e.g., RAR, DCI triggering PDCCH instruction) after the PRACH preamble transmission. The WTRU can then apply the indicated transmission adjustment parameters to subsequent uplink transmissions (e.g., Msg3, Msg5). One or more of the following can be applied: a) Uplink Transmission Adjustment Parameters (uTAP) may include one or more of the following: a1) TA value for ROP (or TA value for subsequent UL transmission); a2) For the TA value of the first TRP, wherein the first TRP can be used interchangeably with the primary TRP, the uplink TRP associated with downlink reception, the anchor TRP, and the default TRP; a3) TA value, which indicates whether the TA value is for the first TRP or the ROP; a4) Power offset values ​​for ROP, such as new or updated power offset values. For example, power offset values ​​can be applied to path loss parameters in power control formulas; a5) TPC commands for the ROP; a6) TPC commands for the first TRP; a7) A TPC command, which has an indication of whether the TPC command is for the first TRP or the ROP; a8) A second beam or RS used for transmission to the ROP (e.g., associated with or configured for the first TRP). For example, the WTRU may be indicated with beam information for UL transmission targeted at the ROP, wherein the beam information may be at least one of an SSB index, TCI status, and / or a reference signal that can be used for beam indication; a9) One or more path loss values ​​for one or more ROPs and / or one or more first TRPs.

[0117] b) uTAP can be applied only when the WTRU is instructed to transmit uplink signals to the ROP: b1) During uplink authorization, the WTRU can be notified of the target TRP (e.g., ROP or first TRP), and if the target TRP is ROP, the WTRU can apply uTAP to the uplink transmission. Otherwise, the WTRU can transmit the uplink without applying the uplink TAP; b2) A WTRU can be configured to have one or more uTAPs, which can be associated with one or more ROPs, where each uTAP can be associated with an index. The WTRU can indicate which uTAPs should be used for uplink transmissions. For example, for uplink transmissions, the WTRU can be configured or indicate a uTAP identifier (uTAP-id).

[0118] According to an embodiment, the WTRU can perform UL transmission to the ROP using transmission power options determined based on the following: a) Transmission power option: a1) The power offset indicated in the DCI (e.g., PDCCH instruction) that initiates the PRACH transmission (e.g., in the corresponding uTAP); a2) Power offset indicated in RAR or other messages (e.g., in the corresponding uTAP); a3) TPC commands for ROP indicated in RAR or other messages.

[0119] b) The WTRU may determine the transmission power option based on at least one of the following: b1) Indicate or configure the target TRP (e.g., ROP, first TRP) for uplink transmission; b2) TCI status (or SRI), which is indicated to determine the uplink beam; b3) Beam-related information used for uplink transmission (e.g., the second beam).

[0120] Based on RAR information, details of power settings and power correction for ROP transmission are determined. Figure 5 A flowchart of the WTRU process (500) is provided.

[0121] The WTRU can receive (506) information in response to the first PRACH transmission (501) received by the ROP / TRP (502) to determine the appropriate power settings and corrections for the ROP-related transmission. This is particularly useful when the WTRU's transmission power is considered too high or too low. The WTRU can receive such information via RAR message information elements transmitted on the PDSCH (505) by the primary TRP or main TRP, which prepares (503) and assembles (504) the RAR message. The information in the RAR message may include power offset values ​​(503a), TPC commands (503b), or open-loop power control (OLPC) related parameters (503c). The WTRU applies (507) the received adjustments in subsequent uplink transmissions (508) based on the information received in the RAR.

[0122] The WTRU can receive RAR messages transmitted on the PDSCH. The RAR message may contain one or more of the following: a) One or more power offset values ​​for ROP or TRP: a1) The power offset value can be a fixed-length bit field; a2) Power offset values ​​can be defined in dB or dBm. a3) Bit fields can be encoded to support a range of power adjustments, for example, from -min dB to max dB in X dB increments.

[0123] b) TPC commands for ROP or TRP, or both ROP and TRP: b1) TPC commands can be encoded using bits that represent power adjustment values; for example, a positive value indicates that the WTRU increases its transmission power, while a negative value indicates a decrease. b2) In one embodiment, a 2-bit TPC command structure for PUSCH / PUCCH / SRS, etc., can be used, for example, "00" no power adjustment, "01" increasing power level, "10" decreasing power level, "11" large decrease, or a specific action according to network configuration. b3) The TPC command step size (e.g., X dB) used for power adjustment is defined by the network and can be transmitted to the WTRU as part of the RRC configuration; b4) TPC commands can accumulate over time, meaning that each command adjusts the power level relative to the last power setting.

[0124] c) A TPC command with instructions for the TRP or ROP, or both ROP and TRP: c1) New bit fields can be included in the RAR message to specify whether the TPC command is for TRP, ROP, or both TRP and ROP. For example, a first indicator bit and a second indicator bit can be used; for instance, if both bits are set to "1", this means the TPC command is for both TRP and ROP, and so on.

[0125] d) Open-loop power control (OLPC) information for WTRU to autonomously adjust its power: d1) OLPC activation flag, used to indicate to the WTRU to activate OLPC for subsequent UL transfer; d2) One or more alpha values ​​used for fractional power control. In one embodiment, a negative alpha value may be introduced and used to reduce the WTRU transmission power (e.g., when the WTRU moves closer to the RP); d3) One or more offset values ​​used to modify the OLPC curve to suit specific conditions (e.g., the presence of a ROP nearby). Examples include the baseline power level (P0) for PUSCH or PUCCH, the initial receive target power for the preamble, etc.

[0126] The WTRU can decode the RAR message transmitted on the PDSCH (506) and can use power information to apply corresponding adjustments (507) to the UL transmission (508) to the ROP, such as: a) The power offset value (503a); b) The TPC command (503b) for the ROP, TRP, or both ROP and TRP; c) Open-loop power control related parameters (503c), such as OLPC activation flag, alpha value, offset value, etc.

[0127] uTAP Acquisition Based on 2-Step RACH According to another embodiment, the WTRU can use a two-step RACH procedure configured for operation in a cell with a first TRP and ROP, wherein the WTRU transmits msgA consisting of a preamble associated with the PRACH timing and a PUSCH associated with the PUSCH timing.

[0128] a) The WTRU can receive a configuration that links the PRACH timing with the PUSCH timing. The WTRU transmits the preamble and PUSCH in two different time slots before receiving the msgB response from the network. The msgB contains the RAR and contention resolution.

[0129] b) The WTRU may receive an RSRP threshold for a two-step RACH involving a ROP, and if the WTRU determines that the RSRP of at least one of the first TRP or the ROP is higher than the threshold, the WTRU may choose to transmit a preamble for the two-step RACH procedure involving the ROP.

[0130] c) The WTRU can be configured with a transmit power offset for msgA, and if the WTRU determines to perform a two-step RACH procedure using msgA, the WTRU can apply the transmit power offset to the msgA transmission. The WTRU can be configured to have different preamble receive target powers as a function of the first TRP or ROP. The WTRU can adjust the transmit power during PUSCH timing by adding a power offset of the ROP to the power control formula, and determine the preamble receive target power for the first TRP or ROP based on the RSRP threshold.

[0131] c1) Alternatively, the WTRU can determine the power offset value and transmit it as part of the msgA PUSCH payload. The network can send msgB in response to msgA, where the network can acknowledge the value determined by the WTRU.

[0132] c2) Alternatively, the network may indicate uTAP in the msgB payload. The WTRU may be configured with a msgB response window after sending msgA, where the WTRU monitors and expects to receive a msgB response. If the response window expires without receiving msgB, the WTRU may fall back to either a transmit power with a pre-configured offset or a target receive power. Alternatively, the WTRU may fall back to a transmit power without offset and apply the fallback target receive power.

[0133] d) After receiving msgB, WTRU can apply uTAP to the transport on the next PUSCH planned by dynamic authorization or configuration authorization.

[0134] WTRU behavior: Determines the beam and power offset for PRACH transmission In the first step, the WTRU is configured for UL transport in a modeROP deployment. For example, it receives configuration information from the (master or service) TRP.

[0135] In the second step, the WTRU (from the primary TRP or serving TRP) receives the SRS configuration, where 'usage' is set to an uplink beam management function, such as 'beamManagement', and this configuration includes one or more of the following: a) At least two SRS resources configured in the SRS resource set; b) At least one additional configuration for associating the SRS resource of each configuration in the resource set with a reference signal, wherein the qcl type of the reference signal is set to 'typeD' in the QCL information of the indicated TCI state.

[0136] In the third step, the WTRU receives a DCI trigger to transmit SRS using the configured SRS resources: a) The DCI includes an index for selecting one of the configured SRS resource associations, which is associated with the TCI or as a reference signal for the source.

[0137] In the fourth (beam scanning) step, the WTRU transmits each SRS resource according to the indicated TCI state. Once an SRS is transmitted, both the (primary, serving) TRP and the ROP receive it. The ROP then shares its received signal quality for each transmitted SRS resource with the (primary, serving) TRP via the backhaul link between the ROP and the (primary, serving) TRP. The (primary, serving) TRP then determines which SRS resource is the best choice for both itself and the ROP based on the signal quality reported by the ROP and its own received signal quality. The best choice can be based on, for example, maximum total power, minimum inter-cell or intra-cell interference. After determining the best SRS resource, which is essentially the best beam, the (primary, serving) TRP sends a PDCCH to trigger a PRACH transmission (PDCCH directive RACH), where the corresponding DCI includes the SRI associated with the best-determined beam to be used for the PRACH transmission. Note that the PDCCH directive RACH is a physical random access procedure triggered when a PDCCH directive requests a PRACH transmission.

[0138] In the fifth step, the WTRU receives the PDCCH instruction RACH, wherein the received DCI also includes at least the SRI: a) If configured, the DCI can also indicate the power offset associated with the indicated SRI; b) If configured, DCI can also indicate timing advance information associated with the indicated SRI.

[0139] In the sixth step, the WTRU transmits the PRACH preamble based on the indicated SRI and its associated power offset (if available): a) If the power offset associated with the indicated SRI is not available, the WTRU may transmit the PRACH preamble based on the default power or based on the measured path loss of the reference signal configured from the master TRP. b) If the timing advance information associated with the indicated SRI is unavailable, the WTRU may transmit the PRACH preamble based on the configured TA, which is based on the master TRP configuration.

[0140] In the seventh step, WTRU determines the TA and additional adjustments for offset power or beam based on the RAR.

[0141] In the eighth step, the WTRU transmits the subsequent UL transmission to the ROP based on the determined TA / power offset.

[0142] Figure 6 An exemplary embodiment for determining the spatial beam for PDCCH command RACH transmission is shown. As described below, the WTRU may first determine the optimal direction or spatial filter for transmitting the PRACH preamble before transmitting the PRACH preamble to accurately determine the TA information and / or power level. In a multi-TRP deployment with at least one ROP, the meaning of optimal beam, optimal TA, and optimal power is determined based on the collective satisfaction of all receiving points, including the conventional TRP and the ROP.

[0143] According to an embodiment, the WTRU can be configured (e.g., via RRC commands) to operate in a multi-TRP transmission. Furthermore, the WTRU can receive an indication that one or more TRPs used for uplink transmissions are ROPs, which can be interpreted as the uplink transmission being in a modeROP. This indication can be based on a semi-static configuration or a dynamic indication (e.g., MAC CE, DCI, etc.). In the case of a semi-static configuration, when the WTRU can receive configuration for a modeROP, this can also mean operation in a multi-TRP, and separate sequential configurations for the multi-TRPs and modeROPs may not be required. In another embodiment, when the WTRU is configured in multi-TRP operation mode, it can dynamically switch in and out of modeROPs for inter-cell interference management based on gNB scheduler decisions.

[0144] Details of beam determination for PDCCH command RACH transmission According to an embodiment, once the WTRU is configured or indicated to operate under modeROP, the WTRU can (be configured to) transmit at least one SRS resource for determining the UL beam of the RACH transmission for the PDCCH instruction RACH transmission. According to an embodiment, the transmission of the SRS for determining the spatial beam of the PDCCH instruction RACH can be based on aperiodic, semi-persistent, or periodic operation, wherein in each case, the WTRU can receive configuration for determining the transmission resource and timing.

[0145] At least one SRS resource can be configured in an SRS resource set associated with parameters (e.g., 'usage') indicating UL beam management (e.g., 'beamManagement') and / or based on a mode of ROP for such SRS transmission. The WTRU can receive at least one additional configuration for associating each configured SRS resource in the SRS resource set with a reference signal (e.g., DL RS, TCI state) that satisfies spatial parameters (e.g., qcl type is set to 'typeD'), for example, to determine the reference beam direction for SRS transmission based on the associated reference signal of the configuration. The reference signal can be transmitted from a first TRP, and the WTRU can transmit at least one SRS resource that can be beam-scanned around the reference signal (e.g., targeting a ROP). According to an embodiment, for each SRS transmission, the WTRU can apply different spatial beams based on the indicated SRS resource.

[0146] a) According to an embodiment, the WTRU can determine and apply power and TA information based on downlink signals received from a TRP (e.g., a primary or serving TRP). Alternatively, in order to enable SRS transmission and determine the spatial beam for the PDCCH instruction RACH, according to an embodiment, the WTRU can also receive a configuration for transmitting default power and / or TA information for the indicated SRS resource.

[0147] (b) According to an exemplary embodiment, each state in the configured SRS resource and reference signal association table may also be associated with a default power and / or TA. Therefore, in addition to the reference signal used to determine the space beam, the indicated SRS resource may also be associated with specific power and / or TA information.

[0148] According to another embodiment, more than one default power and / or TA information can be configured, wherein the configuration values ​​may not be pre-configured with an association with a reference signal.

[0149] According to another embodiment, the WTRU can determine initial power and TA information based on downlink signals received from a TRP (e.g., a primary or serving TRP), and then adjust the determined values ​​with appropriate offsets before applying the determined power and transmission timing. Alternatively, in order to enable SRS transmission to determine the spatial beam for the PDCCH instruction RACH, according to an embodiment, the WTRU can also receive a configuration for adjusting one or more offset values ​​for power and / or TA information used to transmit the indicated SRS resource.

[0150] a) According to an exemplary embodiment, each state in the configured SRS resource and reference signal association table may also be associated with an offset value for power and / or TA. Therefore, in addition to the reference signal used to determine the space beam, the indicated SRS resource may also be associated with a specific offset value for power and / or TA information.

[0151] b) According to another embodiment, more than one offset value can be configured for power and / or TA information, wherein the configured value may not be pre-configured with an association with a reference signal.

[0152] c) According to another embodiment, the WTRU can, for example, dynamically receive offset values ​​corresponding to power and TA information via a DCI used to trigger the determination of SRS transmission of the space beam for the PDCCH instruction RACH.

[0153] According to an exemplary embodiment, the WTRU can receive a DCI for triggering a transmission of a configured SRS resource used to determine a spatial beam for a PDCCH directive RACH. The SRS transmission can be based on an aperiodic or semi-persistent mode. According to another embodiment, the WTRU can be semi-statically configured for periodic transmissions of SRS resources. The received DCI may include one or more of the following: a) The DCI may include an index for selecting one of the configured SRS resource associations to determine a spatial beam, the association being associated with a TCI or reference signal as a source, wherein the state of each configuration may be associated with power and / or TA information; b) The DCI may include more than one index, wherein a first index is used to select the association between the configured SRS resource and the TCI or reference signal as the source to determine the spatial beam, and the remaining one or more indices are used to select one of the configured default power and / or TA information.

[0154] b1) According to an alternative embodiment, the DCI may explicitly indicate the actual default power and TA information for the indicated SRS resource.

[0155] The WTRU may, for example, receive an indication or configuration in response to the transmission of at least one SRS resource. The indication or configuration may be transmitted from the first TRP to the WTRU, for example, based on a backhaul signaling exchange between the ROP and the first TRP, wherein the ROP may receive (e.g., measure) the transmitted SRS in at least one SRS resource and feed back at least one quality metric (e.g., RSRP, SRS-RSRP, and / or timing advance-related measurement results) to the first TRP via the backhaul link.

[0156] a) According to an embodiment, the received indication may include an indication of at least one SRI associated with a PRACH resource (e.g., PRACH timing, PRACH resource, PRACH ID, etc.). The indication of at least one SRI associated with a PRACH resource may imply that the UL beam direction based on at least one SRI may be a candidate UL beam reference for transmission to the ROP. Based on the received indication or configuration, the WTRU may determine a UL beam reference for PRACH transmission, represented by the associated SRI for PRACH transmission, wherein the PRACH transmission may be triggered by a PDCCH command, for example, for timing acquisition purposes of the ROP.

[0157] b) According to another embodiment, the received indication may include an indication of a power offset associated with the indicated SRI, wherein the indicated SRI may be used to transmit other uplink signals (e.g., PDCCH instruction RACH).

[0158] c) According to an embodiment, the received indication may include an indication of timing advance information, which can be used to transmit other uplink signals (e.g., PDCCH instruction RACH).

[0159] The WTRU can receive PDCCH instructions (e.g., triggering a PRACH transmission, which may be a contention-free PRACH Tx), where the PDCCH instructions include an indication of the PRACH transmission resource and its associated UL beam reference (e.g., as SRI) and / or its associated power offset (if indicated). In one example, the PDCCH instructions can be transmitted from the first TRP.

[0160] According to another embodiment, the PDCCH instruction may (also) indicate a power offset, as described in the example embodiment. In response to receiving the PDCCH instruction, the WTRU may determine to transmit PRACH on the PRACH transport resource (e.g., determined by the PRACH timing associated with the indicated PRACH transport resource), wherein the WTRU may determine to transmit PRACH in that direction based on the SRI associated with the PRACH transport resource.

[0161] The WTRU can transmit PRACH based on the UL beam direction determined by the SRI associated with PRACH and the adjusted power based on the power offset indicated by the PDCCH instruction. The WTRU can receive responses (e.g., RAR) as described in the exemplary embodiments (e.g., from the first TRP based on the return coordination between the first TRP and the ROP).

[0162] According to an exemplary embodiment, as described above, the WTRU can receive all relevant configurations related to SRS resources, source reference signals for PRACH beam determination, PRACH resources, etc. Furthermore, the WTRU can receive the special PDCCH instruction RACH, wherein one or more of the following three steps can be performed sequentially during DCI decoding: a) Trigger SRS using the SRS resources described above, wherein each SRS resource may be associated with one or more source reference signals, default power, TA information, etc., used to determine the space beam; b) Monitor the PDCCH to decode the DCI, thereby determining the SRI, wherein the location of the PDCCH may be pre-configured and indicated by an index, or explicitly indicated in a special PDCCH instruction RACH; c) PRACH transmission, wherein the location of the PRACH transmission timing can be pre-configured and indicated by an index, or explicitly indicated in the special PDCCH instruction RACH.

[0163] In response to receiving such a response (e.g., RAR), the WTRU can, for example, determine the timing advance value of the UL control or data channels or signals to be subsequently transmitted to the ROP based on the ROP-based pattern. This can provide benefits in terms of the accuracy of the PDCCH command RACH transmission, which can be aligned with the UL beam direction toward the location of the ROP.

[0164] Figure 7 It is used to determine, for example, what can be applied to, such as Figure 2 A flowchart of method 700 for power offset and TA information based on ROP deployment in the network topology in B). The method implemented by the wireless transmit / receive unit may include: In 701, downlink control information (DCI) is received from the (serving, primary) transport receiving point (TRP), which indicates that physical random access channel (PRACH) resources carrying random access preambles are transmitted to the receive-only point (ROP). In step 702, the transmission power (transmission power offset, transmission power offset value) used to transmit the PRACH resource is determined. In 703, the random access preamble in the PRACH resource is transmitted to the ROP using the determined transmission power; In 704, in response to the transmission of a random access (RA) preamble, a random access response (RAR) or another message (e.g., a response to the RA preamble) is received. In step 705, planning information for uplink (UL) transmission to the ROP is received; and In 706, the UL transmission is transmitted to the ROP; According to an embodiment of the method, the DCI also indicates one or more of the following: The target for transmitting PRACH resources is ROP; The first beam or reference signal (RS) associated with the TRP; One or more of the following: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; (Transmission) power offset value.

[0165] According to an embodiment, the transmission power is determined based on at least one of the following: Path loss or reference signal received power (RSRP) measured for the first beam or RS; Such as the power offset value indicated by the DCI.

[0166] According to an embodiment, when transmitting a random access preamble, the random access preamble is selected from one of the following: As indicated in the DCI, the random access preamble associated with the ROP; Random access preamble selected based on the first beam or RS as indicated in the DCI.

[0167] According to embodiments, the RAR or another message includes one or more of the following: The timing advance (TA) value for the ROP; The TA value for the TRP; The TA value includes an indication of whether the TA value is for the TRP or the ROP; The new or updated power offset value for the ROP; Transmission Power Control (TPC) commands for the ROP; TPC commands for the TRP; TPC commands, the TPC commands including an indication of whether the TPC command is for the TRP or the ROP; The second beam or RS used for transmission to the ROP.

[0168] According to the implementation method, when transmitting UL transmissions to the ROP, the WTRU uses power determined based on one or more of the following to transmit the UL transmissions: Such as the power offset value indicated in the DCI; The new or updated power offset value is indicated in the RAR or another message; Such as the TPC command for ROP indicated in the RAR or another message.

[0169] According to an embodiment, when transmitting UL data to ROP, the WTRU uses one or more of the following: The second beam or RS as indicated in the RAR or the other message; and Timing based on the TA value for the ROP as indicated in the RAR or the other message.

[0170] A WTRU is also disclosed, which includes at least one processor configured to: Receive downlink control information (DCI) from the transmit receiving point (TRP), the DCI indicating the transmission of physical random access channel (PRACH) resources carrying random access preambles to the receive point only (ROP); Determine the transmission power used to transmit the PRACH resources; Using the transmission power, transmit the random access preamble from the PRACH resource to the ROP; In response to the transmission of the random access preamble, receive a random access response (RAR) or another message; Receive planning information for uplink (UL) transmission to the ROP; and The UL transmission is transmitted to the ROP.

[0171] According to an embodiment, DCI also indicates one or more of the following: The target for transmitting PRACH resources is ROP; The first beam or reference signal (RS) associated with the TRP; One or more of the following: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; Power offset value.

[0172] According to an embodiment, the at least one processor is configured to determine the transmission power based on one or more of the following: Path loss or reference signal received power (RSRP) measurement for the first beam or RS; and The power offset value indicated by the DCI.

[0173] According to an embodiment, the at least one processor is configured to transmit a random access preamble selected from one of the following: Such as the random access preamble associated with ROP as indicated in the DCI; and Random access preamble selected based on the first beam or RS as indicated in the DCI.

[0174] According to embodiments, the RAR or another message includes one or more of the following: The timing advance (TA) value for the ROP; The TA value for the TRP; The TA value includes an indication of whether the TA value is for the TRP or the ROP; The new or updated power offset value for the ROP; Transmission Power Control (TPC) commands for the ROP; TPC commands for the TRP; TPC commands, the TPC commands including an indication of whether the TPC command is for the TRP or the ROP; and The second beam or RS used for transmission to the ROP.

[0175] According to an embodiment, the at least one processor is configured to use a power transmission UL transmission determined based on one or more of the following: Such as the power offset value indicated in the DCI; The new or updated power offset value as indicated in the RAR or another message; and Such as the TPC command for ROP indicated in the RAR or another message.

[0176] According to an embodiment, at least one processor is configured to use one or more of the following to transmit UL data to the ROP: The second beam or RS as indicated in the RAR or the other message; and Timing based on the TA value for the ROP as indicated in the RAR or the other message.

[0177] Figure 8 This is a flowchart of a method 800 for determining the beam and power offset for RACH transmission. The method, implemented by a wireless transmit / receive unit, may include: In 801, configuration information for uplink (UL) transmission is received in receive-only point operation mode; In step 802, the detection reference signal (SRS) configuration information to be used for UL beam management functions is received; In 803, receiving downlink control information (DCI) triggers the transmission of SRS using at least two different SRS resources indicated in the SRS configuration information; In 804, based on the Transmission Configuration Information (TCI) state indicated in the SRS configuration information, SRS is transmitted using at least two different SRS resources (or each of the at least two different SRS resources) to determine the UL space beam for receiving Physical Downlink Control Channel (PDCCH) instruction RACH transmission for Random Access Channel (RACH) transmission. In 805, the PDCCH instruction RACH is received and transmitted; In 806, after receiving the PDCCH instruction RACH transmission, a physical RACH (PRACH) transmission is transmitted according to at least one SRS resource indicator (SRI) included in the DCI to determine timing advance information and / or power offset; In 807, timing advance (TA) and power offset or beam are determined from the random access response received in response to the PRACH transmission; and In 808, subsequent UL transmissions are transmitted based on the determined timing advance and power offset or beam.

[0178] According to an embodiment, the SRS configuration information includes at least two different SRS resources configured in the SRS resource set.

[0179] According to an embodiment, the SRS configuration information includes at least one other configuration for associating the SRS resources of each configuration in the SRS resource set with a reference signal having a quasi-co-address type, which is set to type D in the quasi-co-address information of the indicated TCI state.

[0180] According to embodiments, DCI also includes one or more of the following: An indication of the power offset associated with the SRI; and Timing advance information associated with the SRI.

[0181] According to an embodiment, if the DCI does not include the power offset associated with the SRI, then the PRACH transmission is based on one of the following: Default power value; and Measured path loss based on reference signals from the configuration of the Serving Transmitter Receiver Point (TRP).

[0182] According to an embodiment, if the DCI does not include timing advance information associated with the SRI, then the PRACH transmission is a TA based on the Service Transport Receive Point (TRP) configuration.

[0183] A wireless transmit-receive unit (WTRU) is also disclosed, the WTRU including at least one processor, the at least one processor being configured to: Receive configuration information for uplink (UL) transmission in receive-only point operation mode; Receive the detection reference signal (SRS) configuration information to be used for UL beam management functions; Receive downlink control information (DCI) triggers for transmitting SRS using at least two different SRS resources indicated in the SRS configuration information; Based on the Transmission Configuration Information (TCI) status indicated in the SRS configuration information, SRS is transmitted using at least two different SRS resources (or each of the at least two different SRS resources) to determine the UL space beam for receiving Physical Downlink Control Channel (PDCCH) instruction RACH transmission for Random Access Channel (RACH) transmission. Receive PDCCH command RACH transmission; After receiving the PDCCH instruction RACH transmission, a physical RACH (PRACH) transmission is transmitted according to at least one SRS resource indicator (SRI) included in the DCI to determine timing advance information and / or power offset; Determine timing advance (TA) and power offset or beamwidth from the random access response received in response to the PRACH transmission; and Subsequent UL transmissions are transmitted based on the determined timing advance and power offset or beam.

[0184] According to an embodiment, the SRS configuration information includes at least two different SRS resources configured in the SRS resource set.

[0185] According to an embodiment, the SRS configuration information includes at least one other configuration for associating the SRS resources of each configuration in the SRS resource set with a reference signal having a quasi-co-address type, which is set to type D in the quasi-co-address information of the indicated TCI state.

[0186] According to embodiments, DCI also includes one or more of the following: An indication of the power offset associated with the SRI; and Timing advance information associated with the SRI.

[0187] According to an embodiment, the at least one processor is configured to transmit PRACH transmissions based on one of the following if the DCI does not include a power offset associated with the SRI: Default power value; and Measured path loss based on reference signals from the configuration of the Serving Transmitter Receiver Point (TRP).

[0188] According to an embodiment, the at least one processor is configured to transmit PRACH based on the TA transmission receive point (TRP) configuration if the DCI does not include timing advance information associated with the SRI.

[0189] Figure 9 This is a flowchart of a method 900 implemented by a wireless transmit / receive unit (WTRU) according to an embodiment. The method includes: Receive (901) downlink control information DCI from the transmit receiving point TRP, the DCI indicating that physical random access channel (PRACH) resources carrying random access preambles are transmitted to the receive-only point ROP; Based on the information indicated in the DCI, the random access preamble in the PRACH resource is transmitted to the ROP using the first transmission power offset value (902); In response to transmitting the random access preamble to the ROP, a random access response (RAR) is received from the TRP (903); Receive (904) from the TRP planning information for uplink UL transmission to the ROP; and The UL transmission is transmitted to the ROP (905) using a second transmission power offset value based on the information indicated in the RAR.

[0190] According to an embodiment of the method, the DCI also indicates one or more of the following: The target for transmitting PRACH is ROP; The first beam or reference signal RS associated with the TRP; One or more of the following: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; and Power offset value.

[0191] According to an embodiment of the method, the first transmission power offset value is also based on the path loss or reference signal received power RSRP measurement determined for the first beam or RS.

[0192] According to an embodiment of the method for transmitting a random access preamble, the random access preamble is selected from one of the following: Such as the random access preamble associated with ROP as indicated in the DCI; and Random access preamble selected based on the first beam or RS as indicated in the DCI.

[0193] According to embodiments of the method, the RAR includes one or more of the following: The timing advance TA value for the ROP; The TA value for the TRP; The TA value includes an indication of whether the TA value is for the TRP or the ROP; The new or updated power offset value for the ROP; Transmission power control (TPC) commands for the ROP; TPC commands for the TRP; TPC commands, the TPC commands including an indication of whether the TPC command is for the TRP or the ROP; and The second beam or RS used for transmission to the ROP.

[0194] According to an embodiment of the method, when transmitting UL transmissions to the ROP, the WTRU uses power determined based on one or more of the following to transmit the UL transmissions: As indicated in the DCI; As indicated in the new or updated power offset value in the RAR; and The TPC command for ROP is indicated in the RAR.

[0195] According to an embodiment of the method, when transmitting UL data to the ROP, the WTRU uses one or more of the following: Such as the second beam or RS indicated in the RAR; and Timing based on the TA value for ROP as indicated in the RAR.

[0196] According to an embodiment, a wireless transmit / receive unit (WTRU) is also disclosed and described. The WTRU includes at least one processor configured to: Downlink control information (DCI) is received from the transmit receiving point (TRP), and the DCI indicates that physical random access channel (PRACH) resources carrying random access preambles are transmitted to the receive-only point (ROP). Based on the information indicated in the DCI, the random access preamble in the PRACH resource is transmitted to the ROP using the first transmission power offset value; In response to transmitting the random access preamble to the ROP, a random access response (RAR) is received from the TRP; Receive planning information from the TRP for uplink UL transmission to the ROP; and The UL transmission is transmitted to the ROP using a second transmission power offset value based on the information indicated in the RAR.

[0197] According to an embodiment, DCI also indicates one or more of the following: The target for transmitting PRACH is ROP; The first beam or reference signal RS associated with the TRP; One or more of the following: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; and Power offset value.

[0198] According to an embodiment, the at least one processor is configured to determine the first transmission power offset based on a path loss or reference signal received power (RSRP) measurement determined for the first beam or RS.

[0199] According to an embodiment, the at least one processor is configured to transmit a random access preamble selected from one of the following: As indicated in the DCI, the random access preamble associated with the ROP; and Random access preamble selected based on the first beam or RS as indicated in the DCI.

[0200] According to one embodiment, RAR includes one or more of the following: The timing advance TA value for the ROP; The TA value for the TRP; The TA value includes an indication of whether the TA value is for the TRP or the ROP; The new or updated power offset value for the ROP; Transmission power control (TPC) commands for the ROP; TPC commands for the TRP; TPC commands, the TPC commands including an indication of whether the TPC command is for the TRP or the ROP; and The second beam or RS used for transmission to the ROP.

[0201] According to an embodiment, the at least one processor is configured to transmit UL transmission using a power determined based on one or more of the following: As indicated in the DCI; As indicated in the new or updated power offset value in the RAR; and The TPC command for ROP is indicated in the RAR.

[0202] According to an embodiment, at least one processor is configured to use one or more of the following to transmit UL data to the ROP: Such as the second beam or RS indicated in the RAR; and Timing based on the TA value for ROP as indicated in the RAR.

[0203] While features and elements have been provided for the foregoing in specific combinations, those skilled in the art will understand that each feature or element may be used alone or in any combination with other features and elements. This disclosure should not be limited to the specific embodiments described in this application, which are intended to illustrate various aspects. Many modifications and variations are possible without departing from the spirit and scope of the invention, as will be apparent to those skilled in the art. Unless expressly provided so, elements, actions, or instructions used in the description of this application should not be construed as critical or essential to the invention. Functionally equivalent methods and apparatus within the scope of this disclosure, in addition to those listed herein, will be apparent to those skilled in the art based on the foregoing description. These modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terminology of the appended claims and the full scope of their legally enjoyed equivalents. It should be understood that this disclosure is not limited to any particular method or system.

[0204] For simplicity, the foregoing embodiments are discussed in terms of the terminology and structure of devices with wireless communication capabilities (e.g., radio wave transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0205] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" can refer to any of a snapshot, a single image, and / or multiple images displayed over time. As another example, when referenced herein, the term "user equipment" and its abbreviation "UE," the term "remote," and / or the term "head-mounted display" or its abbreviation "HMD" can refer to or include: (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any of several embodiments of a WTRU; (iii) a device with wireless capabilities and / or a device with wired capabilities (e.g., tetherable) configured with some or all of the structure and functions of a WTRU; (iv) a device with wireless capabilities and / or wired capabilities configured with fewer than all the structure and functions of a WTRU; or (iv) a similar device. Figure 1A-1DDetails of exemplary WTRUs (which may be representative of any WTRU described herein) are provided. As another example, the various embodiments disclosed above and below herein are described as utilizing head-mounted displays. Those skilled in the art will recognize that devices other than head-mounted displays can be utilized, and some or all of the contents of this disclosure and the various disclosed embodiments can be modified accordingly without excessive experimentation. Examples of such other devices may include drones or other devices configured to stream information for providing an adaptive, realistic experience.

[0206] Furthermore, the methods provided herein can be implemented in computer programs, software, or firmware incorporated into computer-readable media for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital multifunction discs (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver used in a UE, WTRU, terminal, base station, RNC, or any host computer.

[0207] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the wide variety of applicable embodiments, it should be understood that the illustrated embodiments are merely examples and should not be considered as limiting the scope of the appended claims. For example, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery) that provides any suitable voltage.

[0208] Furthermore, in the embodiments provided above, note the processing platform, computing system, controller, and other devices including the processor. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to actions and symbolic representations of operations or instructions can be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as being “executed,” “computer-executed,” or “CPU-executed.”

[0209] Those skilled in the art will understand that the actions and symbols representing operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause transformations or reductions of electrical signals and the maintenance of data bits at memory locations in a memory system, thereby reconfiguring or otherwise altering the operation of the CPU and other signal processing. The memory location maintaining the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

[0210] Data bits can also be maintained on a computer-readable medium, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system. The computer-readable medium can include cooperative or interconnected computer-readable media that reside exclusively on the processing system or are distributed among multiple interconnected processing systems that may be located locally on or remotely from the processing system. It should be understood that the embodiments are not limited to the aforementioned memories, and other platforms and memories may support the provided methods.

[0211] In exemplary embodiments, any operations, processes, etc., described herein may be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions may be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0212] There is little difference between the hardware and software implementations of various aspects of the system. The use of hardware or software is often (but not always, as the choice between hardware and software may become important in some cases) a design choice representing a trade-off between cost and efficiency. Various vehicles (e.g., hardware, software, and / or firmware) can exist to implement the processes and / or systems and / or other technologies described herein, and the preferred vehicle can vary depending on the context of deploying the processes and / or systems and / or other technologies. For example, if the implementer determines that speed and accuracy are of paramount importance, the implementer may choose a primarily hardware and / or firmware vehicle. If flexibility is of paramount importance, the implementer may choose a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0213] The foregoing detailed description has illustrated various embodiments of the apparatus and / or processes using block diagrams, flowcharts, and / or examples. Where such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or in combination by a wide variety of hardware, software, firmware, or virtually any combination thereof. In embodiments, several portions of the subject matter described herein can be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be implemented, wholly or partially equivalently, in an integrated circuit as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or virtually any combination thereof, and that designing circuit systems and / or writing code for software and / or firmware according to this disclosure will be entirely within the skill of those skilled in the art. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as various forms of program products, and that exemplary embodiments of the subject matter described herein are applicable regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media, such as floppy disks, hard disks, CDs, DVDs, digital magnetic tapes, computer memory, etc., and transmission media, such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0214] Those skilled in the art will recognize that it is common practice in the art to describe devices and / or processes in the manner set forth herein, and subsequently to integrate such described devices and / or processes into data processing systems using engineering practice. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable number of experiments. Those skilled in the art will recognize that a typical data processing system generally includes one or more of the following: a system unit housing, a video display device, a memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, a computing entity such as an operating system, drivers, a graphical user interface and applications, one or more interactive devices such as a touchpad or touchscreen, and / or a control system including feedback loops and control motors (e.g., feedback for sensing position and / or speed, control motors for moving and / or adjusting components and / or numbers). A typical data processing system can be implemented using any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0215] The topics described herein sometimes illustrate different components included within or connected to different other components. It should be understood that the architectures described in this way are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components that implement the same functionality is actively “associated” to achieve the desired functionality. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” with each other to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components that can be so associated can also be considered “operably coupled” to each other to achieve the desired functionality. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interactive components, and / or components that can wirelessly interact and / or perform wireless interactions, and / or logically interactive and / or logically interactive components.

[0216] Regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can convert plural to singular and / or singular to plural as needed by the context and / or application. For clarity, various singular / plural substitutions may be explicitly described herein.

[0217] Those skilled in the art will understand that, in general, the terminology used herein, and especially in the appended claims (e.g., the body of the appended claims), is intended to be “open-ended” (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will also understand that if the intent is to recite a specific number of the introduced claims, such intent will be explicitly stated in the claims, and without such a statement, such intent does not exist. For example, the term “single” or similar language may be used where the intent is to recite only one item. To aid understanding, the appended claims and / or the description herein may include the use of the introductory phrases “at least one” and “one or more” to introduce the recitation of the claims. However, the use of such a phrase should not be construed as implying that the introduction of a claim recount by the indefinite article "a" limits any particular claim to include only one such recount, even when the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" (e.g., "a" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles for introducing a claim recount. Furthermore, even if a specific number of the introduced claim recounts is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the number recounted (e.g., simply stating "two recounts" without other modifiers means at least two recounts, or two or more recounts). Furthermore, in instances where the convention of "at least one of A, B, and C" is used, such a construction is generally intended to be understood by those skilled in the art (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or systems having A, B, and C). In instances where the convention of "at least one of A, B, or C" is used, such a construction is generally intended to be understood by those skilled in the art (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or systems having A, B, and C). Those skilled in the art will also understand that any transitional conjunctions and / or phrases that actually present two or more alternative terms, whether in the specification, claims, or drawings, should be understood to imply the possibility of including one, any, or both of these terms. For example, the phrase “A or B” would be understood to include the possibility of “A” or “B” or “A and B”.Furthermore, as used herein, the term "any of the following" followed by a list of multiple items and / or multiple categories is intended to include "any of the following," "any combination of the following," "any many of the following," and / or "any combination of many of the following": items alone or in combination with other items and / or items of other categories. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "quantity" is intended to include any quantity, including zero. And the term "mutltiple" as used herein is intended to be synonymous with "a plurality."

[0218] Furthermore, in the case of the description of features or aspects of this disclosure in accordance with the Markush group, those skilled in the art will recognize that this disclosure is also described in accordance with any individual member or subgroup member of the Markush group.

[0219] As those skilled in the art will understand, for any and all purposes, such as providing a written description, all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily considered sufficiently descriptive and such that the same scope can be decomposed into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily decomposed into a lower third, a middle third, and an upper third, etc. Those skilled in the art will also understand that all terms such as “up to,” “at least,” “greater than,” “less than,” etc., include the listed numbers and refer to a scope that can subsequently be decomposed into subscopes as described above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1-3 cells means a group having 1, 2, or 3 cells. Similarly, a group having 1-5 cells means a group having 1, 2, 3, 4, or 5 cells, and so on.

[0220] Furthermore, the claims should not be construed as limited to the provided order or elements unless otherwise stated. Additionally, the use of the term "for a means of..." in any claim is intended to invoke 35 U.S.C. §112, 6 or the means plus function claim format, and no claim without the term "for a means of..." is not intended to do so.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), wherein the method comprises: Downlink control information (DCI) is received from the transmit receiving point (TRP), and the DCI indicates that physical random access channel (PRACH) resources carrying random access preambles are transmitted to the receive-only point (ROP). Based on the information indicated in the DCI, the random access preamble in the PRACH resource is transmitted to the ROP using the first transmission power offset value; In response to transmitting the random access preamble to the ROP, a random access response (RAR) is received from the TRP; Receive planning information from the TRP for uplink UL transmission to the ROP; as well as The UL transmission is transmitted to the ROP using a second transmission power offset value based on the information indicated in the RAR.

2. The method of claim 1, wherein the DCI further indicates one or more of the following: The target for transmitting the PRACH is ROP; The first beam or reference signal RS associated with the TRP; One or more of the following: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; and Power offset value.

3. The method according to claim 1 or 2, wherein the first transmission power offset value is further based on a path loss or reference signal received power (RSRP) measurement determined for the first beam or RS.

4. The method according to any one of claims 1 to 3, wherein, In order to transmit the random access preamble, the random access preamble is selected from one of the following: The random access preamble associated with the ROP as indicated in the DCI; and Random access preamble selected based on the first beam or RS as indicated in the DCI.

5. The method according to any one of claims 1 to 4, wherein the RAR comprises one or more of the following: The timing advance TA value for the ROP; The TA value for the TRP; The TA value includes an indication of whether the TA value is for the TRP or the ROP; The new or updated power offset value for the ROP; Transmission power control (TPC) commands for the ROP; TPC commands for the TRP; TPC commands, the TPC commands including an indication of whether the TPC command is for the TRP or the ROP; as well as The second beam or RS used for transmission to the ROP.

6. The method according to claim 5, wherein, When transmitting the UL transmission to the ROP, the WTRU uses power determined based on one or more of the following to transmit the UL transmission: The power offset value indicated in the DCI; The new or updated power offset value as indicated in the RAR; as well as The TPC command for the ROP as indicated in the RAR.

7. The method according to claim 5, wherein, When transmitting the UL transmission to the ROP, the WTRU uses one or more of the following: The second beam or RS as indicated in the RAR; and Timing based on the TA value for the ROP as indicated in the RAR.

8. A wireless transmit-receive unit (WTRU), comprising a transceiver, a memory, and at least one processor, configured to: Downlink control information (DCI) is received from the transmit receiving point (TRP), and the DCI indicates that physical random access channel (PRACH) resources carrying random access preambles are transmitted to the receive-only point (ROP). Based on the information indicated in the DCI, the random access preamble in the PRACH resource is transmitted to the ROP using the first transmission power offset value; In response to transmitting the random access preamble to the ROP, a random access response (RAR) is received from the TRP; Receive planning information from the TRP for uplink UL transmission to the ROP; as well as The UL transmission is transmitted to the ROP using a second transmission power offset value based on the information indicated in the RAR.

9. The WTRU of claim 8, wherein the DCI further indicates one or more of the following: The target for transmitting the PRACH is ROP; The first beam or reference signal RS associated with the TRP; One or more of the following: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; and Power offset value.

10. The WTRU of claim 8 or 9, wherein the transceiver, the memory, and the at least one processor are configured to determine the first transmission power offset based on a path loss or reference signal received power (RSRP) measurement determined for the first beam or RS.

11. The WTRU according to any one of claims 8 to 10, wherein the transceiver, the memory, and the at least one processor are configured to transmit the random access preamble selected from one of the following: The random access preamble associated with the ROP as indicated in the DCI; and Random access preamble selected based on the first beam or RS as indicated in the DCI.

12. The WTRU according to any one of claims 8 to 11, wherein the RAR comprises one or more of the following: The timing advance TA value for the ROP; The TA value for the TRP; The TA value includes an indication of whether the TA value is for the TRP or the ROP; The new or updated power offset value for the ROP; Transmission power control (TPC) commands for the ROP; TPC commands for the TRP; TPC commands, the TPC commands including an indication of whether the TPC command is for the TRP or the ROP; as well as The second beam or RS used for transmission to the ROP.

13. The WTRU of claim 12, wherein the transceiver, the memory, and the at least one processor are configured to transmit the UL transmission using a power determined based on one or more of the following: The power offset value indicated in the DCI; The new or updated power offset value as indicated in the RAR; and The TPC command for the ROP as indicated in the RAR.

14. The WTRU of claim 12, wherein the transceiver, the memory, and the at least one processor are configured to transmit the UL transmission to the ROP using one or more of the following: The second beam or RS as indicated in the RAR; and Timing based on the TA value for the ROP as indicated in the RAR.

Images