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

Abstract

Procedures, methods, architectures, apparatuses, 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, may receive downlink control information from a transmission-receive point, TRP, indicating the WTRU to transmit a physical random access channel, PRACH, transmission to a receive-only point, ROP. The WTRU may determine transmit power for the PRACH transmission. The WTRU may transmit a preamble using the determined power. The WTRU may receive a random access response. The random access response may comprise a timing advance value, TA, for the ROP, and / or a power offset for transmissions to the ROP. The WTRU may receive scheduling information for an uplink, UL, transmission to the ROP, and the WTRU may transmit the UL transmission to the ROP using the TA / power offset.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR DETERMINING POWER OFFSET AND TIMING ADVANCE INFORMATION FOR A RECEIVE-ONLY POINT BASED DEPLOYMENTCROSS-REFERENCE TO RELATED APPLICATIONS

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

[0001] The present disclosure is generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, systems related to uplink (UL)-only transmission-reception point (TRP) operation.BACKGROUND

[0001] UL-only TRP Operation is among the candidate topics identified for Rel-19 multiple input multiple output (MIMO). The objective is to improve uplink throughput, coverage, and reliability performance for cell edge user equipment (UEs) and mitigate limitations due to large pathloss and UE transmission power. Further, it reduces deployment cost, and it facilitates deployments as there will be less concern for downlink interference planning.

[0002] Since in such deployment, there is no downlink transmission of any form from any of UL-only TRP, all downlink (DL) transmissions are strictly from the serving TRP. A typical deployment consists of at least one TRP with both downlink and uplink transmission capabilities, and at least one receive-only point (ROP).SUMMARYThe objective of an uplink-only deployment is to improve the capacity, reliability, and coverage of a cell by receiving and combining the uplink signal received by a TRP and ROP. However, in absence of a DL reference signal from a ROP, it is not straightforward as how a UE should determine power, beam direction and timing advance (TA) for an uplink transmission such that the transmitted signal can be properly received and constructively combined by both TRP and ROP.

[0003] Embodiments are disclosed, described and claimed in the appended claims, which embodiments contribute to further improvements in New Radio networks.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description arenot to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein:

[0005] FIG. 1 A is a system diagram illustrating an example communications system;

[0006] FIG. IB is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0007] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;

[0008] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0009] FIG. 2 shows conventional (A) and uplink-only (B) TRP operation;

[0010] FIG. 3 shows DCI format 1 0 for PDCCH order in Table 1; and

[0011] FIG. 4 shows example of ROP power offsets linked to measured RSRP ranges in Table 2;

[0012] FIG. 5 is a flowchart of a WTRU procedure of RAR-based information to determine power setting and power correction for ROP transmission;

[0013] FIG. 6 is an embodiment of a method for determination of a spatial beam for PDCCH order RACH transmission;

[0014] FIG. 7 is a flowchart of a method 700 for determining power offset and TA information for a ROP -based deployment, applicable for example in a network topology as in FIG. 2 B);

[0015] FIG. 8 is a flowchart of a method 800 for determining beam and power offset for a RACH transmission, applicable for example in a network topology as in FIG. 2 B); and

[0016] FIG. 9 is a flowchart of a method 900 according to an embodiment.DETAILED DESCRIPTION

[0017] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of 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, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or anyportion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.

[0018] In the following, embodiments are described using the acronyms PRACH (physical random access channel) and RACH (random access channel) interchangeably. The described principles, methods and embodiments are applicable to random access procedures using other formats than PRACH / RACH.

[0019] Abbreviations and AcronymsACK AcknowledgementA-MPR Additional Maximum Power ReductionBLER Block Error RateBWP Bandwidth PartCAP Channel Access PriorityCAPC Channel access priority classCCA Clear Channel AssessmentCCE Control Channel ElementCE Control ElementCG Configured grant or cell groupCP Cyclic PrefixCP-OFDM Conventional OFDM (relying on cyclic prefix)CQI Channel Quality IndicatorCRC Cyclic Redundancy CheckCSI Channel State InformationCW Contention WindowCWS Contention Window SizeCO Channel OccupancyDAI Downlink Assignment IndexDCI Downlink Control InformationDFI Downlink feedback informationDG Dynamic grantDL DownlinkDM-RS Demodulation Reference SignalDRB Data Radio Bearer eLAA enhanced Licensed Assisted AccessFeLAA Further enhanced Licensed Assisted AccessHARQ Hybrid Automatic Repeat RequestLAA License Assisted AccessLBT Listen-Before-TalkLTE Long Term Evolution e.g., from 3GPP LTE R8 and upLTM Layer- 1 Triggered MobilityNACK Negative ACKMAC CE Medim Access Control - Control ElementMCS Modulation and Coding SchemeMIB Master Information BlockMIMO Multiple Input Multiple OutputMPR Maximum Power ReductionMTRP Multiple Transmission and Reception PointNR New RadioOFDM Orthogonal Frequency-Division MultiplexingOLPC Open-Loop Power ControlPBCH Physical Broadcast ChannelPCI Physical Cell IdentityPDCCH Physical Downlink Control ChannelPDSCH Physical Downlink Shared ChannelPHY Physical LayerPID Process IDPL PathlossP-MPR Power Class Maximum Power ReductionPO Paging OccasionPRACH Physical Random Access ChannelPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Downlink Shared ChannelQCL Quasi Co-LocationRA Random Access (or procedure)RACH Random Access ChannelRAR Random Access ResponseRCU Radio access network Central UnitRF Radio Front endRLF Radio Link FailureRLM Radio Link MonitoringRNTI Radio Network IdentifierRO RACH occasionROP Receive Only PointRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSRP Reference Signal Received PowerRS SI Received Signal Strength IndicatorRTT Round-Trip TimeSIB System Information BlockSDU Service Data UnitSNR Signal-to-Noise RatioSRI SRS Resource IndicatorSRS Sounding Reference SignalSS Synchronization SignalSSB Synchronization Signal BlockSSS Secondary Synchronization SignalSUL Supplementary UplinkSWG Switching Gap (in a self-contained subframe)SPS Semi-persistent schedulingSUL Supplemental UplinkTA Timing AdvanceTB Transport BlockTBS Transport Block SizeTCI Transmission Configuration IndicationTPC Transmit Power ControlTRP Transmission / Reception PointTSC Time-sensitive communicationsTSN Time-sensitive networkingUL UplinkURLLC Ultra-Reliable and Low Latency Communications uTAP Uplink Transmission Adjustment Parameter WBWP Wide Bandwidth PartWLAN Wireless Local Area Networks and related technologies (IEEE 802. xx domain)

[0020] Example Communications System

[0021] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and / or be adapted and / or configured for the methods, apparatuses and systems provided herein.

[0022] FIG. 1A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0023] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and / or a "STA", may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0024] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

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

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

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

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

[0033] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing an NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0034] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 114 or a different RAT.

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

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

[0037] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

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

[0039] Although the transmit / receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

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

[0042] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

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

[0044] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The elements / peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a lightsensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0045] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0046] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

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

[0048] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and / or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0049] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the CN operator.

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

[0051] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

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

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

[0054] Although the WTRU is described in FIGs. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0055] In representative embodiments, the other network 112 may be a WLAN.

[0056] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not havean AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.

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

[0058] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0059] Very high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0060] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in 802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.1 lah may support meter type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. TheMTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0061] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.1 In, 802.1 lac, 802.11af, and 802.1 lah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0062] In the United States, the available frequency bands, which may be used by 802.1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 lah is 6 MHz to 26 MHz depending on the country code.

[0063] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

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

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

[0066] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non- standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non- standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non- standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0067] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0068] The CN 115 shown in FIG. ID 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 are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

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

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

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

[0075] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0076] UL-only TRP Operation is among the candidate topics identified for Rel-19 MIMO. The objective is to improve uplink throughput, coverage, and reliability performance for cell edge UEs and mitigate limitations due to large pathloss and WTRU transmission power. Further, it reduces deployment cost, and it facilitates deployments as there will be less concern for downlink interference planning.

[0077] Since in such deployment, there is no downlink transmission of any form from any of UE-only TRP, all DL transmissions are strictly from the serving TRP. A typical deployment consists of at least one TRP with both downlink and uplink transmission capabilities, and at leastone receive-only point (ROP). FIG. 2 shows two different deployments (A and B) based on conventional (A) and UL-only (B) TRP. In the UL-only TRP, the ROP is connected to the main TRP by a backhaul connection. Once an ROP receives an uplink signal, after some basic initial processing, it shares the signal for further processing to the main TRP.

[0078] The objective of an uplink-only deployment is to improve the capacity, reliability, and coverage of a cell by receiving and combining the uplink signal received by a TRP and ROP. However, in the absence of a DL reference signal from ROP, it is not straightforward as how a WTRU should determine power, beam direction and TA (Timing Advance) for an uplink transmission such that the transmitted signal can be properly received and constructively combined by both TRP and ROP. For example, the uplink transmission should be executed with: a) a timing that is in an acceptable to processing window of both TRP and ROP; b) a sufficiently high power level for both TRP and ROP, without any harmful interference; c) a direction of transmission that both TRP and ROP can benefit from.In absence of a DL reference signal from ROP, it may be interesting to know how to determine power, beam direction and TA for an uplink transmission.

[0079] Method of power offset and TA information

[0080] WTRU behavior: Determining power offset and TA information for a ROP-based deployment

[0081] According to an embodiment, determining power offset and TA information for a ROP- based deployment may comprise one or more of the following steps:

[0082] In a first step, a WTRU may receive a DCI (dynamic indication) (e.g., PDCCH order) from a first (main, serving) TRP (cell, main cell, serving cell) indicating to transmit a PRACH preamble to a ROP: a) The DCI may include an indication that the target of the transmission is a ROP (e.g., a flag) or a specific DCI format or RNTI may be used to indicate the target for the transmission is a ROP; b) The DCI may indicate (e.g., via a TCI state or an SRI) a first beam or RS associated with the first TRP (e.g., an SSB or CSLRS of, or configured for, the first TRP), for example, the first beam / RS indicated by the gNB may be the best beam / RS for communication with the first TRP or a beam / RS that may be at least sufficient for communication with each of (or both) the TRP and the ROP; c) The DCI may indicate a preamble and / or one or more PRACH resources associated with or configured for the ROP; d) The DCI may indicate a power offset (e.g., to ensure the ROP hears the transmission);

[0083] In a second step, the WTRU may determine a transmit (Tx) power for the PRACH transmission based on at least one of:a) A pathloss (PL) or RSRP measurement determined for the indicated first beam or RS; b) The indicated power offset, for example, the Tx power calculated normally (e.g., based on PL, target SNR, etc.) may be increased by the power offset (Tx power = Tx power + power offset), or, for example, the PL may be adjusted by the power offset (e.g., PL = PL + power offset); c) The WTRU transmits a preamble using the determined Tx power.

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

[0085] In a fourth step, the WTRU may transmit the preamble using a resource of the indicated PRACH resources or a PRACH resource associated with the indicated first beam or RS.

[0086] In a fifth step, the WTRU may receive a random access response (RAR) or another message (e.g., from the first TRP). The RAR or the other message may contain one or more of the following: a) a TA value for the ROP; b) a TA value for the first TRP; c) a TA value with an indication of whether the TA value is for the first TRP or the ROP; d) a power offset value, e.g., a new or updated power offset value, for the ROP; e) a TPC command for the ROP; f) a TPC command for the TRP; g) a TPC command with an indication of whether the TPC command is for the first TRP or the ROP; h) a second beam or RS (e.g., associated with or configured for the first TRP) for transmission to the ROP.

[0087] In a sixth step, the WTRU may receive scheduling information for an UL transmission (e g., PUSCH or SRS) to the ROP.

[0088] In a seventh step, the WTRU may transmit the UL transmission to the ROP: a) the WTRU may transmit the UL transmission to the ROP using power determined based on at least one of: al) the power offset indicated in the DCI initiating the PRACH transmission; a2) the power offset indicated in the RAR or other message; a3) the TPC command for the ROP indicated in the RAR or other message. b) the WTRU may transmit the UL transmission to the ROP using the second beam or RS (e.g., to determine a spatial filter for the UL transmission); c) the WTRU may transmit the UL transmission to the ROP using timing based on the TA value for the ROP received in the RAR or other message.

[0089] Details of PDCCH order RACH and initial power determination for (P)RACH transmission

[0090] The discussed concepts and embodiments may generally be applicable for a multi TRP deployment with an arbitrary number of TRPs, however, to facilitate the presentation of embodiments, a 2 TRP deployment is often used for brevity.

[0091] When a 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 the anchor for the timing synchronization and full access stratum (AS) communication, while the ROP will serve as a diversity reception point for the system and thus possibly increasing the WTRU UL throughput.

[0092] As the WTRU is considered fully synchronized with the anchor TRP and having a reliable radio link, the gNB may request the WTRU to assist the system to acquire UL synchronization for the ROP. This means that the WTRU may have to transmit in the UL a PRACH preamble or an SRS that would allow the gNB evaluate the UL timing requirement and power for the ROP.

[0093] In Rel-18 multi-TRP scenario, the PDCCH order RACH by DCI format 1 0 uses 1 bit out of 10 reserved (left from previous releases) for inter-cell PCI PRACH target indication. Further, it may also use this bit for intra-cell cross TRP target indication. Another 2 bits are used for the LTM (Layer 1 Triggered Mobility) target inactive PCI for handover purposes. Thus, there are 7 bits left for future potential use.

[0094] The current PDCCH order RACH by DCI format 1 0 contains the SSB index or a second RS that is associated with the TRP issuing the order. When the target of the PRACH is different than the TRP transmitting the PDCCH order, the PCI or the TCI where its source RS is used for the pathloss estimation (or its QCLed RS), is configured through RRC as a specific configuration.

[0095] See Table 1 in FIG. 3, representing DCI format 1 0 for PDCCH order (Rel-18).

[0096] In a multi TRP deployment with one or more ROPs, the WTRU may have to rely on its main TRP pathloss related RSs or SSBs as a base for computation for any possible PRACH initial power estimation.

[0097] According to an embodiment, a WTRU may be configured with specific ROP UL access parameters that can be one or a combination of the following: a) set of PRACH preambles indexes; b) a set of specific TCI state related to ROP operation; c) a set of specific SRI linked to the ROP operation; d) a specific set of power offsets that may be linked / associated to a RSRP thresholds or ranges that may be linked to a specific set of anchor TRP related SSBs; e) a set of specific PRACH occasions (ROs); f) a set of specific UL sweeping PRACH occasions for beam pairing.

[0098] The WTRU may be configured with a ROP configuration conditional to a WTRU capability allowing the WTRU to transmit within a CP a simultaneous transmission on two beams or a capability of transmitting simultaneously on two beams from two or more different panels with a transmit time different higher than a CP.

[0099] When a WTRU can transmit on two beams with a transmit time difference higher than a CP the appropriate timing advance (TA) acquisition may be required, and thus the WTRU may use a PRACH transmission for this purpose. A PDCCH order PRACH may be issued by the anchor TRP that may contain an indication that is targeting the ROP.

[0100] The current initial PRACH power determination is done according to the following equation:where the PRACH preamble received power target is signaled by network in RRC along with Delta Preamble used for different preamble formats and the Preamble Power Ramping Step. Basically, in equation (1) the Pcmax is related to the WTRU Power Class and MPR, A-MPR or P- MPR that are coexistence and exposure parameters respectively, while the PRACH initial power:Power PRACH target = preambleReceivedTargetPower +Delta Preamble + (Preamble Ramping Counter -1) x Preamble Power Ramping StepWith the Preamble Ramping Counter = 1, meaning:Power PRACH target = preambleReceivedTargetPower + Delta Preamble.We note that 'x' stands for multiplication.

[0101] When the WTRU receives the ROP target indication on a PDCCH order, the WTRU may interpret the rest of the DCI information according to the ROP configured information regarding the PRACH initial power determination, PRACH preamble and mask indexes.

[0102] According to an embodiment, a WTRU may be configured with one or more power offset values where each may be associated to a measurement, another configured system parameters, etc.

[0103] In an exemplary embodiment, the configured power offset value may be associated to a downlink measurement, e.g., RSRP.

[0104] In an exemplary embodiment, the WTRU may use and evaluate the measured RSRP from the signaled RS within DCI format 1 0 for example and finds for example that RSRP falls into one of the specific ranges configured by RRC that is linked to a configured power offset. In this case, for example, the WTRU may compute the initial PRACH power by adding the correspondingconfigured offset according to the following linkage in the exemplary Table 2. One or more of following may apply: a) One or more sets of ROP power offsets may be configured and one of the sets may be used, wherein the set of ROP power offsets may be determined based on WTRU location. al) WTRU location may be based on at least one of following: ala) Position of the WTRU in the cell (e.g., actual position, zone) alb) Distance from the gNB (e.g., RTT, TA, pathloss, RSRP value) a2) Each set may have at least one ROP offset value a3) ROP power offsets may be determined based on the transmission type. a3a) For example, a WTRU may be configured with more than one ROP power offset where one may be applied for PUSCH, another for PUCCH, and another for SRS, etc. a3b) In another example, the ROP power offsets may be tied to the priority and content of a transmission. For example, the ROP power offset for a high priority PUSCH, e.g., URLLC, may be different than a PUSCH transmission with normal priority. b) ROP offset value may be indicated dynamically (e.g., in the PDCCH order)

[0105] According to an alternative embodiment, besides power offset values, a WTRU may be also configured with one or more reference signal for PRACH beam determination and / or timing advance information where each may be associated to a measurement, another configured system parameters, etc. For example, Table 2 in FIG. 4 may be extended to have additional rows to indicate reference signal for PRACH beam determination and / or timing advance information.

[0106] According to an embodiment, one or more of following may apply: a) One or more sets of reference signal for PRACH beam determination and / or timing advance information may be configured and one of the sets may be used, wherein the set of ROP reference signal for PRACH beam determination and / or timing advance information may be determined based on WTRU location. al) WTRU location may be based on at least one of following: ala) Position of the WTRU in the cell (e.g., actual position, zone) alb) Distance from the gNB (e.g., RTT, TA, pathloss, RSRP value) a2) Each set may have at least one reference signal for PRACH beam determination and / or timing advance information value. a3) Reference signal for PRACH beam determination and / or timing advance information may be determined based on the transmission type. a3a) For example, a WTRU may be configured with more than one reference signal for PRACH beam determination and / or timing advance information where one may be applied for PUSCH, another for PUCCH, and another for SRS, etc.a3b) In another example, reference signal for PRACH beam determination and / or timing advance information may be tied to the priority and content of a transmission. For example, the ROP power offset for a high priority PUSCH, e.g., URLLC, may be different than a PUSCH transmission with normal priority. b) ROP offset value may be indicated dynamically (e.g., in the PDCCH order)

[0107] The estimated RSRP that is used for PL parameter (e.g., pathloss) may be based on a measurement from an RS indicated in the PDCCH order.

[0108] Thus, the WTRU may use for example ROP_Offset_2 if the measured RSRP for the indicated RS falls into Range_2 as follows:Power PRACH target = preambleReceivedTargetPower + Delta Preamble + ROP_Offset_2

[0109] According to another embodiment, the ROP Offset index may be signaled directly in the PDCCH order since the network already received RSRP measurements from WTRU. Alternatively, the ROP Offset may be signaled in clear in dB with the PDCCH order RACH. a) The ROP offset value may be accumulated over time. For example, ROP_Offset_2(k) = ROP_Offset_2(k-l)+delta_ROP_offset, wherein k is an occasion ROP offset is calculated and k- 1 is the latest occasion during which ROP_Offset_2 was updated, and the delta ROP offset is indicated from gNB to update the ROP_Offset_2 value

[0110] A WTRU may be configured with a time window for reception of the RAR to the preamble sent in the PRACH configured for the ROP (e.g., a ra-ResponseWindow configured for the case when the ROP is present). The RAR time window starts from the time when the WTRU transmitted the preamble based on the symbol of the first symbol of the earliest CORESET that starts after the PRACH occasion. The CORESET may be configured with the first TRP or the ROP, and the time window may be relative to either TRP's CORESET. In this time window, the WTRU monitors for a DCI scrambled with a RNTI (e.g., RA-RNTI configured for the case when the ROP is present) and expects to receive a RAR. If the WTRU doesn't receive a ROP specific RAR in a specific time window, the WTRU may perform PRACH ramp up power and a retransmission according to PRACH Occasion that may be specific / configured to / for ROP.

[0111] According to another embodiment, the WTRU may use a PRACH sweeping in successive ROs to determine the UL beam associated with the ROP. In this embodiment, the WTRU may receive a specific beam sweeping PRACH order where specific preambles order may be used in a specific pattern, so the specific UL beam with the best ROP correspondence is found and established upon reception of a RAR message confirming the pairing by indicating the preamble index used in sweeping in a specific direction for example.

[0112] Details of PRACH transmission

[0113] A WTRU may perform a PRACH transmission in a cell where potentially ROP is used, supported, or located. For example, a WTRU may receive information related to ROP (e.g., in broadcasting signal, SIB, MIB, DCI) during initial access procedure and / or system information update procedure, and the WTRU may perform a PRACH transmission.

[0114] According to an embodiment, a WTRU may perform a first type of PRACH transmission when the WTRU received indication that the ROP is supported in the cell; otherwise, the WTRU may perform a second type of PRACH transmission. a) The WTRU may perform one or more of following in the first type of PRACH transmission: al) The WTRU may transmit PRACH with a predetermined transmission power (e.g., Tx power level is configured or indicated in the SIB); a2) A maximum transmission power for the first type of PRACH transmission may be different from that for the second type of PRACH transmission; a3) The WTRU may transmit PRACH preamble in PRACH occasions (ROs) which may be not associated with the SSB index the WTRU determined. Instead, an offset (e.g., SSB-index offset) value may be applied to determine a virtual SSB index which associated with the ROs for the first type of PRACH transmission: a3a) The offset may be provided in the broadcasting signal (e.g., SIB) per SSB index. a4) The WTRU may transmit PRACH with all possible uplink beams. One or more ROs may be configured for uplink beam sweeping for the PRACH transmission; b) The second type of PRACH transmission is legacy PRACH transmission: bl) The WTRU may perform a PRACH preamble transmission in the determined PRACH occasions (ROs), wherein the RO may be determined based on SSB index determined.

[0115] According to another embodiment, a WTRU may receive uplink transmission adjustment parameters (e.g., a power offset, TA) in a message (e.g., RAR, DCI triggering PDCCH order) after the PRACH preamble transmission, the WTRU may apply the indicated transmission adjustment parameters for a subsequent uplink transmission (e.g., Msg3, Msg5). One or more of following may apply: a) The uplink transmission adjustment parameters (uTAPs) may include one or more of the following: al) A TA value for the ROP (or TA value to use for subsequent UL transmission); a2) A TA value for the first TRP, wherein the first TRP may be interchangeably used with primary TRP, uplink TRP associated with downlink reception, anchor TRP, and default TRP; a3) A TA value with an indication of whether the TA value is for the first TRP or the ROP;a4) A power offset value, e.g., a new or updated power offset value, for the ROP. For example, the power offset value may be applied to pathloss parameter in a power control formula; a5) A TPC command for the ROP; a6) A TPC command for the first TRP; a7) A TPC command with an indication of whether the TPC command is for the first TRP or the ROP; a8) A second beam or RS (e.g., associated with or configured for the first TRP) for transmission to the ROP. For example, a WTRU may be indicated a beam information for the UL transmission targeting to ROP, wherein the beam information may be at least one of SSB-index, TCI state, and / or reference signal which may be used for beam indication; a9) One or more pathloss value for one or more ROPs and / or one or more first TRPs. b) The uTAPs may be only applied when a WTRU is indicated to transmit uplink signal to ROP: bl) In an uplink grant, a WTRU may be informed the target TRP (e.g., ROP or first TRP) and if the target TRP is a ROP, the WTRU may apply uTAPs for the uplink transmission. Otherwise, the WTRU may transmit uplink without applying uplink TAPs; b2) A WTRU may be configured with one or more uTAPs which may be associated with one or more ROPs, wherein each uTAPs may be associated with an index. The WTRU may be indicated which uTAPs to apply for an uplink transmission. For example, for an uplink transmission, a WTRU may be configured or indicated uTAPs identity (uTAPs-id).

[0116] According to an embodiment, a WTRU may perform UL transmission to a ROP using transmission power option determined based on following: a) Transmission power options: al) The power offset (e.g., in corresponding uTAPs) indicated in the DCI initiating the PRACH transmission (e.g., PDCCH order); a2) The power offset (e.g., in corresponding uTAPs) indicated in the RAR or other message; a3) The TPC command for the ROP indicated in the RAR or other message. b) A WTRU may determine a transmission power option based on at least one of following: bl) A target TRP (e.g., ROP, first TRP) indicated or configured for the uplink transmission; b2) A TCI state (or SRI) indicated to determine an uplink beam; b3) A beam related information (e.g., second beam) for the uplink transmission.

[0117] Details of RAR-based information to determine power setting and power correction for ROP transmission

[0118] A flowchart of a WTRU procedure (500) is provided in FIG. 5.

[0119] A WTRU may receive (506) information in response to a first PRACH transmission (501) that is received by ROPs / TRPs (502) to determine appropriate power settings and corrections fortransmissions related to the ROPs. This is particularly applicable to instances where the WTRU's transmission power is deemed to be too high or too low. WTRU may receive such information through the RAR message information elements transmitted over PDSCH (505) by the main or primary TRP that prepared (503) and composed (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.

[0120] WTRU may receive a RAR message transmitted on the PDSCH. The RAR message may contain one or more of the following: a) One or multiple more power offset values with respect to the ROP or TRP: al) A power offset value could be a fixed-length bit field; a2) A power offset value may be defined in dB or dBm; a3) The bit field may be encoded to support a range of power adjustments, e.g., -min dB to max dB in X dB increments. b) TPC command for the ROP or TRP, or both: bl) TPC command may be encoded with bits that represent a power adjustment value, e.g., positive values instruct the WTRU to increase its transmit power, whilst negative values instruct a decrease; b2) In one embodiment, a 2-bit TPC command structure for PUSCH / PUCCH / SRS / etc. can be used, e.g., "00" no power adjustment, "01" increment power level, "10" decrement power level, "11" large decrement or specific action per as network configuration; b3) The TPC command step size for power adjustments (e.g., X dB) is defined by the network and can be communicated to the WTRU as part of RRC configuration; b4) The TPC commands can be accumulated overtime, meaning each command adjusts the power level relative to the last power setting. c) TPC command with indication for the TRP or ROP, or both: cl) New bit field can be included in the RAR message to specify if TPC commands are meant for TRP, ROP, or both. For example, a first and second indicator bits can be used, e.g., if both bits are set to " 1 ", it implies that the TPC command are for both TRP and ROP, etc. d) Open loop power control (OLPC) information for WTRU to autonomously adjust it power: dl) OLPC activation flag for instructing WTRU to activate OLPC for subsequent UL transmissions; d2) One or more alpha values for fractional power control. In one embodiment, negative alpha values may be introduced and used to decrease WTRU transmit power (e.g., when WTRU is moving closer to the RP);d3) One or more offset values to alter OLPC curve to account for specific conditions (e.g., presence of nearby ROP). E.g., baseline power level for PUSCH or PUCCH (PO), preamble initial received target power, etc.

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

[0122] 2-step RACH based acquisition of uTAP

[0123] According to another embodiment, a WTRU may use a 2-step RACH procedure configured for operation in a cell with a first TRP and a ROP, where a WTRU transmits msgA consisting of a preamble associated to a PRACH occasion, and a PUSCH associated to a PUSCH occasion. a) The WTRU may receive a configuration that links a PRACH occasion with a PUSCH occasion. The WTRU transmits preamble and PUSCH in two different time slots before receiving the msgB response from the network. msgB contains the RAR and contention resolution. b) The WTRU may receive an RSRP threshold for 2-step RACH with ROP, and the WTRU may select to transmit a preamble for the 2-step RACH procedure with ROP if the WTRU determines that the RSRP of at least one of the first TRP or the ROP is above the threshold. c) The WTRU may be configured with a transmission power offset for msgA, and the WTRU may apply the transmission power offset to the msgA transmission if the WTRU determines to perform the 2-step RACH procedure with msgA. The WTRU may be configured with different preamble received target power as a function of the first TRP or the ROP. The WTRU may adjust the transmission power in the PUSCH occasion by adding the power offset for ROP in the power control formula, and determining the preamble received target power for the first TRP or the ROP as a function of the RSRP threshold. cl) Alternatively, the WTRU may determine a power offset value, and may transmit it as part of the msgA PUSCH payload. The network may send a msgB in response to the msgA, where the network may confirm the value determined by the WTRU. c2) Alternatively, the network may indicate the uTAPs in the msgB payload. The WTRU may be configured with a msgB response window after sending the msgA where the WTRU monitors and expects to receive a msgB response. If the response window expires without receiving a msgB, the WTRU may fall back to a transmission power with a different preconfigured offset or targetreceived power. Alternatively, the WTRU may fall back to a transmission power without an offset, and applying a fallback target received power. d) After receiving msgB, the WTRU may apply the uTAPs for transmissions on the next PUSCH scheduled by dynamic or configured grants.

[0124] WTRU behavior: Determining beam and power offset for PRACH transmission

[0125] In a first step, a WTRU is configured for an UL transmission in a modeROP deployment. The configuration information is for example received from the (main or serving) TRP.

[0126] In a second step, the WTRU receives (from the main or serving TRP) SRS configuration with 'usage' set to uplink beam management function, e.g., 'beamManagemenf, where the configuration includes one or more of: a) at least two SRS resources configured in an SRS resource set; b) at least one additional configuration to associate each configured SRS resource in the resource set with a reference signal with qcl-Type set to 'typeD' in QCL-Info of the indicated TCIState.

[0127] In a third step, the WTRU receives a DCI trigger to transmit SRS using the configured SRS resources: a) the DCI includes an index to select one of the configured SRS resource associations to a TCI or a reference signal as source.

[0128] In a fourth (beam sweeping) step, the WTRU transmits each SRS resource according to the indicated TCI state. Once the SRS transmitted, both the (main, serving) TRP and the ROP receive them. Then, the ROP shares the signal quality of its received signal for each transmitted SRS resource with the (main, serving) TRP via the backhaul link between the ROP and the (main, serving) TRP. Then, the (main, serving) TRP, based on the reported signal quality shared by ROP, and its own received signal quality, determines which SRS resource would be the best choice for both itself and ROP. The best choice may be based on, for example, the maximum sum power, least inter-cell or intra-cell interference. After determining the best SRS resource that is basically the best beam, the (main, serving) TRP sends a PDCCH to trigger a PRACH transmission (PDCCH order RACH), where the corresponding DCI includes the SRI associated to the best determined beam to be used for PRACH transmission. Note that a PDCCH order RACH is a physical random access procedure that is triggered upon request of a PRACH transmission by a PDCCH order.

[0129] In a fifth step, the WTRU receives a PDCCH order RACH where the received DCI also includes at least an SRI: a) if configured, the DCI may also indicate a power offset associated to the indicated SRI; b) if configured, the DCI may also indicate a timing advance information associated to the indicated SRI.

[0130] In a sixth step, the WTRU transmits PRACH preamble according to the indicated SRI, and its indicated associated power offset, if available: a) if the power offset associated to the indicated SRI is not available, WTRU may transmit PRACH preamble based on a default power or a measured pathloss based on a configured reference signal from the main TRP; b) if the timing advance information associated to the indicated SRI is not available, WTRU may transmit PRACH preamble based on a configured TA configured based on the main TRP.

[0131] In a seventh step, the WTRU determines the TA and additional adjustments for offset power or beam from the RAR.

[0132] In an eight step, the WTRU transmits subsequent UL transmissions according to the determined TA / power offset to the ROP.

[0133] FIG. 6 shows an exemplary embodiment for determination of the spatial beam for PDCCH order RACH transmission. As described in the following, before transmission of a PRACH preamble for accurate determination of the TA information, and / or power level, a WTRU may first determine the best direction or spatial filter for transmission of the PRACH preamble. In a multi-TRP deployment, where there exists at least one ROP, the meaning of the best beam, best TA and best power is determined based on the collective satisfaction of all points of receptions, including regular TRPs and ROPs.

[0134] According to an embodiment, a WTRU may be configured, e.g., by an RRC command, to operate in a multi-TRP transmission. Further, the WTRU may receive an indication that one or more of TRPs for uplink transmission are ROP that may be interpreted as uplink transmission will be in modeROP. The indication, may 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 a WTRU may receive a configuration for modeROP, it may also imply operation in multi-TRP, and separate sequential configuration of multi-TRP and modeROP may not be needed. In another embodiment, when a WTRU is configured in a multi-TRP mode of operation, it may be dynamically switched in and out of modeROP for inter-cell interference management according to gNB scheduler decision.

[0135] Details of beam determination for PDCCH order RACH transmission

[0136] According to an embodiment, once a WTRU is configured or indicated to operate in modeROP, the WTRU may (be configured to) transmit at least one SRS resource for UL beam determination of a RACH transmission for a PDCCH order RACH transmission. According to an embodiment, the transmission of the SRS for determination of the spatial beam for PDCCH order RACH may be based on an aperiodic, semi-persistent or periodic operation, where for each case,a WTRU may receive a configuration for determination of the transmission resources and opportunities.

[0137] At least one SRS resource may be configured in an SRS resource set associated with a parameter (e.g., 'usage') indicating a UL beam management (e.g., 'beamManagement') and / or a mode based on ROP for such SRS transmissions. The WTRU may receive at least one additional configuration to associate each configured SRS resource in the SRS resource set with a reference signal (e.g., a DL RS, a TCI-state) w.r.t a spatial parameter (e.g., a qcl-Type set to 'typeD'), e.g., to determine a reference beam direction for the SRS transmission based on the configured associated reference signal. The reference signal may be transmitted from the first TRP, and the WTRU may transmit at least one SRS resource which may be beam-swept around the reference signal, e.g., to be targeted toward the ROP. According to an embodiment, for each SRS transmission, a WTRU may apply a different spatial beam according to the indicated SRS resource. a) According to an embodiment, a WTRU may determine and apply the power and TA information based on the received downlink signal from a TRP, e.g., the main or serving TRP. Alternatively, for the purpose of SRS transmission for determination of the spatial beam for a PDCCH order RACH, according to an embodiment, a WTRU may also receive a configuration for a default power and / or TA information for transmission of the indicated SRS resource. b) According to an exemplary embodiment, each state in the configured SRS resource to reference signal association table, may also be associated to a default power and / or TA. Therefore, besides a reference signal for spatial beam determination, the indicated SRS resource may be also associated to a specific power and / or TA information.

[0138] According to another embodiment, more than one default power and / or TA information may be configured where the configured values may not be preconfigured with an association to a reference signal.

[0139] According to another embodiment, a WTRU may determine an initial power and TA information based on the received downlink signal from a TRP, e.g., the main or serving TRP, and then adjust the determined values by a corresponding offset before applying the determined power and transmission timing. Alternatively, for the purpose of SRS transmission for determination of the spatial beam for a PDCCH order RACH, according to an embodiment, a WTRU may also receive a configuration for one or more of offset values for adjustment of power and / or TA information for transmission of the indicated SRS resource. a) According to an exemplary embodiment, each state in the configured SRS resource to reference signal association table, may also be associated to an offset value for power and / or TA. Therefore, besides a reference signal for spatial beam determination, the indicated SRS resource may be also associated to a specific offset value for power and / or TA information.b) According to another embodiment, more than one offset value for power and / or TA information may be configured where the configured values may not be preconfigured with an association to a reference signal. c) According to another embodiment, a WTRU may receive offset values corresponding to power and TA information dynamically, e.g., by the DCI triggering the SRS transmission for determination the spatial beam for PDCCH order RACH.

[0140] According to an exemplary embodiment, a WTRU may receive a DCI to trigger transmission of the configured SRS resource for determination of the spatial beam for PDCCH order RACH. The transmission of the SRS may be based on an aperiodic or semi-persistent pattern. According to another embodiment, a WTRU may be configured semi-statically for a periodic transmission of the SRS resource. The received DCI may include one or more of the following: a) The DCI may include an index to select one of the configured SRS resource associations to a TCI or a reference signal as source for determination of the spatial beam, where each configured state may be associated power and / or TA information; b) The DCI may include more than one indices, where a first index is to select one of the configured SRS resource associations to a TCI or a reference signal as source for determination of the spatial beam, and remaining index or indices are to select one of the configured default powers and / or TA information. bl) According to an alternative embodiment, the DCI may explicitly indicate the actual default power and TA information for the indicated SRS resource.

[0141] The WTRU may receive an indication or configuration, e.g., in response to transmitting the at least one SRS resource. The indication or configuration may be transmitted from the first TRP to the WTRU, e.g., based on a backhaul signaling exchange between the ROP and the first TRP, where the ROP may receive (e.g., measure) a transmitted SRS of the at least one SRS resource and feedback at least one quality metric (e.g., RSRP, SRS-RSRP, and / or timing advance related measurement result), to the first TRP via the backhaul link. a) According to an embodiment, the received indication may include indication of at least an SRI that is associated with a PRACH resource (e g., PRACH occasion, PRACH resource, PRACH ID, etc.). The indication of the at least an SRI being associated with the PRACH resource may imply that UL beam direction(s) based on the at least an SRI may be a candidate UL beam reference(s) to be used for transmission toward the ROP. Based on receiving the indication or configuration, the WTRU may determine an UL beam reference for a PRACH transmission, represented by an associated SRI for the PRACH transmission, where the PRACH transmission may be triggered by a PDCCH order, e.g., for the purpose of a timing acquisition for the ROP.b) According to another embodiment, the received indication may include indication of power offset associated to the indicated SRI that may be used for transmission of other uplink signal, e.g., PDCCH order RACH. c) According to an embodiment, the received indication may include indication of a timing advance information that may be used for transmission of other uplink signal, e.g., PDCCH order RACH.

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

[0143] According to another embodiment, the PDCCH order may (also) indicate a power offset, described in the example embodiments. In response to receiving the PDCCH order, the WTRU may determine to transmit a PRACH over the PRACH transmission resource (e.g., determined by a PRACH occasion associated with the indicated PRACH transmission resource), where the WTRU may determine to transmit the PRACH in the direction based on the SRI associated with the PRACH transmission resource.

[0144] The WTRU may transmit the PRACH based on a UL beam direction determined by the SRI associated with the PRACH and an adjusted power based on the power offset indicated by the PDCCH order. The WTRU may receive a response (e.g., from the first TRP based on a backhaul coordination between the first TRP and the ROP) described in the example embodiments, e.g., RAR.

[0145] According to an exemplary embodiment, as described above, a WTRU may receive all related configuration related to SRS resource, source reference signals for PRACH beam determination, PRACH resources, etc. Further, a WTRU may receive a special PDCCH order RACH where upon decoding of the DCI one or more of the following three steps may be done sequentially: a) Triggering of an SRS using the above describes SRS resources where each SRS resource may be associated to one or more of source reference signals for spatial beam determination, default power, TA information, etc.; b) Monitoring PDCCH to decode a DCI to determine the SRI, where the location of the PDCCH may be preconfigured and indicated by an index, or explicitly indicated in the special PDCCH order RACH;c) Transmission of the PRACH, where the location of PRACH transmission opportunity may be preconfigured and indicated by an index, or explicitly indicated in the special PDCCH order RACH.

[0146] In response to receiving the response (e.g., RAR), the WTRU may determine a timing advance value to be used for subsequent transmission of a UL control or data channel or signal toward the ROP, e.g., according to the mode based on ROP. This may provide benefits in terms of the PDCCH order RACH transmission accuracy that may be aligned with a UL beam direction toward where the ROP is located.

[0147] FIG. 7 is a flowchart of a method 700 for determining power offset and TA information for a ROP-based deployment, applicable for example in a network topology as in Figure 2 B). The method, implemented by a wireless transmit-receive unit, may comprise:In 701, receiving downlink control information (DCI) from a (serving, main) transmissionreception point (TRP), the DCI indicating to transmit a physical random access channel (PRACH) resource carrying a random access preamble, to a receive-only point (ROP);In 702, determining a transmit power (transmit power offset, transmit power offset value) for transmitting the PRACH resource;In 703, transmitting a random access preamble in the PRACH resource to the ROP using the determined transmit power;In 704, receiving, in response to transmitting the random access (RA) preamble, a random access response (RAR) or another message (e.g., a response to the RA preamble);In 705, receiving scheduling information for an uplink (UL) transmission to the ROP; andIn 706, transmitting the UL transmission to the ROP;

[0148] According to an embodiment of the method, the DCI further indicates one or more of: a target for transmitting the PRACH resource is a ROP; a first beam or reference signal (RS) associated with the TRP; one or more of: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; a (transmit) power offset value.

[0149] According to an embodiment, the determining a transmit power is based on at least one of: a pathloss or reference signal received power (RSRP) measurement determined for the first beam or RS; the power offset value as indicated by the DCI.

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

[0151] According to an embodiment, the RAR or the another message comprises one or more of: a timing advance (TA) value for the ROP; a TA value for the TRP; a TA value comprising an indication whether the TA value is for the TRP or the ROP; a new or updated power offset value for the ROP; a transmit power control (TPC) command for the ROP; a TPC command for the TRP; a TPC command comprising an indication whether the TPC command is for the TRP or the ROP; a second beam or RS for transmission to the ROP.

[0152] According to an embodiment, when transmitting the UL transmission to the ROP, the WTRU transmits the UL transmission using a power determined based on one or more of the power offset value as indicated in the DCI; the new or updated power offset value as indicated in the RAR or in the another message; the TPC command for the ROP as indicated in the RAR or in the another message.

[0153] According to an embodiment, when transmitting the UL transmission to the ROP, the WTRU uses one or more of the second beam or RS as indicated in the RAR or in the another message; and timing based on the TA value for the ROP as indicated in the RAR or the another message.

[0154] There is also disclosed a WTRU, comprising at least one processor configured to: receive downlink control information (DCI) from a transmission-reception point (TRP) indicating to transmit a physical random access channel (PRACH) resource carrying a random access preamble, to a receive-only point (ROP); determine a transmit power for transmitting the PRACH resource; transmit a random access preamble in the PRACH resource to the ROP using the transmit power; receive, in response to transmitting the random access preamble, a random access response (RAR) or another message; receive scheduling information for an uplink (UL) transmission to the ROP; and transmit the UL transmission to the ROP.

[0155] According to an embodiment the DCI further indicates one or more of: a target for transmitting the PRACH resource is a ROP; a first beam or reference signal (RS) associated with the TRP; one or more of: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP;a power offset value.

[0156] According to an embodiment, the at least one processor is configured to determine the transmit power based on one or more of: a pathloss or reference signal received power (RSRP) measurement determined for the first beam or RS; and the power offset value as indicated by the DCI.

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

[0158] According to an embodiment, the RAR or the another message comprises one or more of: a timing advance (TA) value for the ROP; a TA value for the TRP; a TA value comprising an indication whether the TA value is for the TRP or the ROP; a new or updated power offset value for the ROP; a transmit power control (TPC) command for the ROP; a TPC command for the TRP; a TPC command comprising an indication whether the TPC command is for the TRP or the ROP; and a second beam or RS for transmission to the ROP.

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

[0160] According to an embodiment, the at least one processor is configured to transmit the UL transmission to the ROP using one or more of: the second beam or RS as indicated in the RAR or in the another message; and timing based on the TA value for the ROP as indicated in the RAR or the another message.

[0161] FIG. 8 is a flowchart of a method 800 for determining beam and power offset for a RACH transmission. The method, implemented by a wireless transmit-receive unit, may comprise:In 801, receiving configuration information for uplink (UL) transmission in a receive-only point mode of operation;In 802, receiving sounding reference signal (SRS) configuration information to be used for an UL beam management function;In 803, receiving downlink control information (DCI) trigger to transmit SRS using at least two different SRS resources indicated in the SRS configuration information;In 804, transmitting SRS using (the / each of) at least two different SRS resources according to a transmission configuration information (TCI) state indicated in the SRS configuration information, for UL spatial beam determination of a random access channel (RACH) transmission for receiving a physical downlink control channel (PDCCH) order RACH transmission;In 805, receiving the PDCCH order RACH transmission;In 806, transmitting, after the receiving of the PDCCH order RACH transmission, a physical RACH (PRACH) transmission according to at least one SRS resource indicator (SRI) comprised in the DCI, for determining timing advance information and / or power offset;In 807, determining a timing advance (TA) and power offset or beam from a random access response received in response to the PRACH transmission; andIn 808, transmitting subsequent UL transmissions according to the determined timing advance and power offset or beam.

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

[0163] According to an embodiment, the SRS configuration information comprises at least a further configuration, for association of each configured SRS resource in the SRS resource set with a reference signal with quasi-colocation type set to Type-D in quasi-colocation information of the indicated TCI state.

[0164] According to an embodiment, the DCI further comprises at one or more of: an indication of a power offset associated with the SRI; and timing advance information associated with the SRI.

[0165] According to an embodiment, the PRACH transmission, if no power offset associated with the SRI is comprised in the DCI, is based on one of: a default power value; or a measured pathloss based on a configured reference signal from a serving transmission-reception point (TRP).

[0166] According to an embodiment, the PRACH transmission is based on a TA configured based on a serving transmission-reception point (TRP), if no timing advance information associated with the SRI is comprised in the DCI.

[0167] There is also disclosed a wireless transmit-receive unit (WTRU), comprising at least one processor configured to: receive configuration information for uplink (UL) transmission in a receive-only point mode of operation;receive sounding reference signal (SRS) configuration information to be used for an UL beam management function; receive downlink control information (DCI) trigger to transmit SRS using at least two different SRS resources indicated in the SRS configuration information; transmit SRS using (the / each of) at least two different SRS resources according to a transmission configuration information (TCI) state indicated in the SRS configuration information, for UL spatial beam determination of a random access channel (RACH) transmission for receiving a physical downlink control channel (PDCCH) order RACH transmission; receive the PDCCH order RACH transmission; transmit, after receiving the PDCCH order RACH transmission, a physical RACH (PRACH) transmission according to at least one SRS resource indicator (SRI) comprised in the DCI, for determining timing advance information and / or power offset; determine a timing advance (TA) and power offset or beam from a random access response received in response to the PRACH transmission; and transmit subsequent UL transmissions according to the determined timing advance and power offset or beam.

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

[0169] According to an embodiment, the SRS configuration information comprises at least a further configuration, for association of each configured SRS resource in the SRS resource set with a reference signal with quasi-colocation type set to Type-D in quasi-colocation information of the indicated TCI state.

[0170] According to an embodiment, the DCI further comprises at one or more of: an indication of a power offset associated with the SRI; and timing advance information associated with the SRI.

[0171] According to an embodiment, the at least one processor is configured to transmit the PRACH transmission, if no power offset associated with the SRI is comprised in the DCI, based on one of: a default power value; or a measured pathloss based on a configured reference signal from a serving transmission-reception point (TRP).

[0172] According to an embodiment, the at least one processor is configured to transmit the PRACH transmission based on a TA configured based on a serving transmission-reception point (TRP), if no timing advance information associated with the SRI is comprised in the DCI.

[0173] FIG. 9 is a flow chart of a method 900, implemented by a wireless transmit-receive unit, WTRU, according to an embodiment. The method comprises:

[0174] receiving (901) downlink control information, DCI, from a transmission-reception point, TRP, indicating to transmit a physical random access channel, PRACH, resource carrying a random access preamble, to a receive-only point, ROP;

[0175] transmitting (902) a random access preamble in the PRACH resource to the ROP with a first transmission power offset value based on information indicated in the DCI;

[0176] receiving (903) a random access response, RAR, from the TRP, in response to transmitting the random access preamble to the ROP;

[0177] receiving (904) scheduling information from the TRP for an uplink, UL, transmission to the ROP; and

[0178] transmitting (905) the UL transmission to the ROP with a second transmission power offset value based on information indicated in the RAR.

[0179] According to an embodiment of the method, the DCI further indicates one or more of:

[0180] a target for transmitting the PRACH is a ROP;

[0181] a first beam or reference signal, RS, associated with the TRP;

[0182] one or more of: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; and

[0183] a power offset value.

[0184] According to an embodiment of the method, the first transmission power offset value is further based on a pathloss or reference signal received power, RSRP, measurement determined for the first beam or RS.

[0185] According to an embodiment of the method, for transmitting the random access preamble, the random access preamble is chosen from one of:

[0186] the random access preamble associated with the ROP as indicated in the DCI; and

[0187] a random access preamble selected based on the first beam or RS as indicated in the DCI.

[0188] According to an embodiment of the method, the RAR comprises one or more of:

[0189] a timing advance, TA, value for the ROP;

[0190] a TA value for the TRP;

[0191] a TA value comprising an indication whether the TA value is for the TRP or the ROP;

[0192] a new or updated power offset value for the ROP;

[0193] a transmit power control, TPC, command for the ROP;

[0194] a TPC command for the TRP;

[0195] a TPC command comprising an indication whether the TPC command is for the TRP or the ROP; and

[0196] a second beam or RS for transmission to the ROP.

[0197] According to an embodiment of the method, when transmitting the UL transmission to the ROP, the WTRU transmits the UL transmission using a power determined based on one or more of:

[0198] the power offset value as indicated in the DCI;

[0199] the new or updated power offset value as indicated in the RAR; and

[0200] the TPC command for the ROP as indicated in the RAR.

[0201] According to an embodiment of the method, when transmitting the UL transmission to the ROP, the WTRU uses one or more of:

[0202] the second beam or RS as indicated in the RAR; and

[0203] timing based on the TA value for the ROP as indicated in the RAR.

[0204] There is also disclosed and described a wireless transmit-receive unit, WTRU, according to an embodiment. The WTRU comprising at least one processor configured to:

[0205] receive downlink control information, DCI, from a transmission-reception point, TRP, indicating to transmit a physical random access channel, PRACH, resource carrying a random access preamble, to a receive-only point, ROP;

[0206] transmit a random access preamble in the PRACH resource to the ROP with a first transmission power offset value based on information indicated in the DCI;

[0207] receive a random access response, RAR, from the TRP, in response to the random access preamble transmitted to the ROP;

[0208] receive scheduling information from the TRP for an uplink, UL, transmission to the ROP; and

[0209] transmit the UL transmission to the ROP with a second transmission power offset value based on information indicated in the RAR.

[0210] According to an embodiment, the DCI further indicates one or more of:

[0211] a target for transmitting the PRACH is a ROP;

[0212] a first beam or reference signal, RS, associated with the TRP;

[0213] one or more of: a random access preamble associated with the ROP; one or more PRACH resources associated with the ROP; and

[0214] a power offset value.

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

[0216] According to an embodiment, the at least one processor is configured to transmit the random access preamble chosen from one of:

[0217] the random access preamble associated with the ROP as indicated in the DCI; and

[0218] a random access preamble selected based on the first beam or RS as indicated in the DCI.

[0219] According to an embodiment, the RAR comprises one or more of:

[0220] a timing advance, TA, value for the ROP;

[0221] a TA value for the TRP;

[0222] a TA value comprising an indication whether the TA value is for the TRP or the ROP;

[0223] a new or updated power offset value for the ROP;

[0224] a transmit power control, TPC, command for the ROP;

[0225] a TPC command for the TRP;

[0226] a TPC command comprising an indication whether the TPC command is for the TRP or the ROP; and

[0227] a second beam or RS for transmission to the ROP.

[0228] According to an embodiment, the at least one processor is configured to transmit the UL transmission using a power determined based on one or more of

[0229] the power offset value as indicated in the DCI;

[0230] the new or updated power offset value as indicated in the RAR; and

[0231] the TPC command for the ROP as indicated in the RAR.

[0232] According to an embodiment, the at least one processor is configured to transmit the UL transmission to the ROP using one or more of

[0233] the second beam or RS as indicated in the RAR; and

[0234] timing based on the TA value for the ROP as indicated in the RAR.

[0235] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0236] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of wireless communication capable devices, (e.g., radio wave emitters and receivers). However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0237] It is also to 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 "imagery" may mean any of a snapshot, single image and / or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and / or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and / or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and / or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0238] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a UE, WTRU, terminal, base station, RNC, or any host computer.

[0239] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and shouldnot be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0240] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0241] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0242] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

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

[0244] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and / or systemsand / or other technologies described herein may be effected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0245] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples may be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and / or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0246] Those skilled in the art will recognize that it is common within the art to describe devices and / or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system viaa reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and / or control systems including feedback loops and control motors (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0247] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0248] With respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0249] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example,where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of' followed by a listing of a plurality of items and / or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and / or "any combination of multiples of the items and / or the categories of items, individually or in conjunction with other items and / or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0250] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0251] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0252] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMSWhat is claimed is:

1. A method, implemented by a wireless transmit-receive unit, WTRU, wherein the method comprises: receiving downlink control information, DCI, from a transmission-reception point, TRP, indicating to transmit a physical random access channel, PRACH, resource carrying a random access preamble, to a receive-only point, ROP; transmitting a random access preamble in the PRACH resource to the ROP with a first transmission power offset value based on information indicated in the DCI; receiving a random access response, RAR, from the TRP, in response to transmitting the random access preamble to the ROP; receiving scheduling information from the TRP for an uplink, UL, transmission to the ROP; and transmitting the UL transmission to the ROP with a second transmission power offset value based on information indicated in the RAR.

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

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

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

5. The method according to any of claims 1 to 4, wherein the RAR comprises one or more of: a timing advance, TA, value for the ROP; a TA value for the TRP; a TA value comprising an indication whether the TA value is for the TRP or the ROP;a new or updated power offset value for the ROP; a transmit power control, TPC, command for the ROP; a TPC command for the TRP; a TPC command comprising an indication whether the TPC command is for the TRP or the ROP; and a second beam or RS for transmission to the ROP.

6. The method according to claim 5, wherein, when transmitting the UL transmission to the ROP, the WTRU transmits the UL transmission using a power determined based on one or more of: the power offset value as 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.

7. The method according to claim 5, wherein, when transmitting the UL transmission to the ROP, the WTRU uses one or more of: 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, memory, and at least one processor configured to: receive downlink control information, DCI, from a transmission-reception point, TRP, indicating to transmit a physical random access channel, PRACH, resource carrying a random access preamble, to a receive-only point, ROP; transmit a random access preamble in the PRACH resource to the ROP with a first transmission power offset value based on information indicated in the DCI; receive a random access response, RAR, from the TRP, in response to the random access preamble transmitted to the ROP; receive scheduling information from the TRP for an uplink, UL, transmission to the ROP; and transmit the UL transmission to the ROP with a second transmission power offset value based on information indicated in the RAR.

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

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

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

12. The WTRU according to any of claims 8 to 11, wherein the RAR comprises one or more of: a timing advance, TA, value for the ROP; a TA value for the TRP; a TA value comprising an indication whether the TA value is for the TRP or the ROP; a new or updated power offset value for the ROP; a transmit power control, TPC, command for the ROP; a TPC command for the TRP; a TPC command comprising an indication whether the TPC command is for the TRP or the ROP; and a second beam or RS for transmission to the ROP.

13. The WTRU according to claim 12, wherein 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 power offset value as 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 according to claim 12, wherein 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 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