Methods, apparatuses and systems for random access channel occasions configuration in subband non-overlapping full duplex scenarios

Abstract

NOT VISIBLE DUE TO STATUS OF PATENT

Description

METHODS, APPARATUSES AND SYSTEMS FOR RANDOM ACCESS CHANNEL OCCASIONS CONFIGURATION IN SUBBAND NON-OVERLAPPING FULL DUPLEX SCENARIOSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of US Provisional Patent Application No. 63 / 552,958 filed February 13th, 2024, which is incorporated herein by reference.FIELD OF THE INVENTION

[0002] The present disclosure is generally directed to random access channel occasions configuration in subband non-overlapping full duplex scenarios.BACKGROUND

[0003] The duplex operation in new radio system may be a foundation in improving conventional time division duplexing operation by enhancing uplink coverage, improving capacity, reducing latency, and so forth. The conventional time division duplexing may be based on splitting the time domain between the uplink and downlink.

[0004] Reducing the latency in accessing and connecting to the network may be a key benefit that can be achieved by using subband non-overlapping full duplex (SBFD) scenarios. In new radio, a wireless transmit and receive unit (WTRU) may be configured with random access channel (RACH) occasions in time and frequency domain. In new radio time division duplexing (TDD), the random access occasions (ROs) may be valid only if they coincide with uplink slots in time domain, and the WTRU may avoid physical random access channel (PRACH) transmission if the ROs are in DL-slots. It may not be efficient for an SBFD-capable WTRU to use legacy configured TDD RO configurations in time domain.

[0005] There is a need to improve random access channel occasion for SBFD-capable WTRU.SUMMARY

[0006] In an embodiment, a method implemented in a WTRU, may comprise a step of receiving a first message comprising first configuration information indicating resources for a first type of random access channel occasions (ROs) and for a second type of ROs. The method may further comprise a step of determining whether to use the first type of ROs or the second type of ROs for a physical random access channel (PRACH) transmission based on a determined PRACH power; and a step of transmitting the PRACH transmission in an RO of the determined ROs using the PRACH power.

[0007] On condition of not receiving a random access response following the PRACH transmission in the determined RO, the method may comprise a step of transmitting another PRACH transmission in the not determined RO. On condition of not receiving a random access response following the PRACH transmission in the determined RO, the method may comprise a step of ramping the PRACH power.

[0008] The method may comprise a step of determining the PRACH power for the PRACH transmission; and a step of transmitting in the first type of ROs or in the second type of RO based whether the determined PRACH power exceeds, is equal, or is below a power threshold value.

[0009] More particularly, the method may comprise a step of comprising transmitting in the first type of RO on condition that the determined PRACH power exceeds or is equal to the power threshold value, and / or a step of transmitting in the second type of RO on condition that the determined PRACH power is below the power threshold value. The power threshold value may be a determined maximum transmission power for the PRACH transmission.

[0010] The first type of ROs may be configured in time division duplexing uplink slots and wherein the second type of ROs is configured in subband non-overlapping full duplex (SBFD) slots. The method may comprise a step of determining a SBFD maximum transmission power associated with the second type of ROs; and a step of transmitting the PRACH transmission in the second type of ROs on condition that the PRACH power is below the SBFD maximum transmission power.

[0011] The method may comprise a step of receiving a second message comprising second configuration information indicating one or more repetition threshold values. The method may comprise a step of determining a repetition threshold value based on path loss measurement and determining using repetition of PRACH transmission based on the determined repetition threshold value. The method may comprise a step of transmitting a set of RACH transmissions in the RO of the determined ROs using the PRACH power.

[0012] The method may further comprise a step of determining whether to use the first type of ROs or the second type of ROs for each PRACH transmission of the set of PRACH transmissions based on a PRACH power associated with each PRACH transmission of the set of PRACH transmissions; and on condition that a determined type of ROs of a first PRACH transmission of the set of PRACH transmissions differs from a determined type of ROs of a second PRACH transmission of the set of PRACH transmissions, the method may further comprise a step of transmitting the first and the second PRACH transmission respectively in the determined type ofROs of the first and the second PRACH transmission; and stopping PRACH transmission of the set of PRACH transmissions.

[0013] In an embodiment, a WTRU comprising a processor, a transceiver unit and a storage unit, and may be configured to receive a first message comprising first configuration information indicating resources for a first type of random access channel occasions (ROs) and for a second type of ROs. The WTRU may be further configured to determine whether to use the first type of ROs or the second type of ROs for a physical random access channel (PRACH) transmission based on a determined PRACH power; and to transmit the PRACH transmission in an RO of the determined ROs using the PRACH power.

[0014] In another embodiment, a method, implemented in a wireless transmit / receive unit, WTRU, may comprise a step of receiving a first message comprising first configuration information indicating resources for a first type of random access channel occasions, ROs, and for a second type of ROs. The method may further comprise a step of determining to use the second type of ROs for a physical random access channel, PRACH, transmission based on a determined PRACH power. The method may further comprise a step of transmitting the PRACH transmission in the second type of ROs using the PRACH power. The method may further comprise a step of ramping the PRACH power used for transmitting the PRACH transmission in the second type of ROs. On condition that the PRACH power for a PRACH transmission is capped, the method may further comprise a step of switching from the second type of ROs to the first type of ROs for PRACH transmission; and a step of transmitting the PRACH transmission in the first type of ROs using the PRACH power.

[0015] On condition of not receiving a random access response following the PRACH transmission in the second type of ROs, the method may comprise a step of ramping the PRACH power. The method may further comprise a step of determining the PRACH power for the PRACH transmission; and a step of transmitting in the second type of RO on condition that the determined PRACH power is below a power threshold value. The power threshold value may be a determined maximum transmission power for the PRACH transmission. The first type of ROs may be configured in a non subband non-overlapping full duplex, SBFD, slots (e.g., time division duplexing uplink slots) and the second type of ROs may be configured in subband non-overlapping full duplex, SBFD, slots. The WTRU may be a SBFD capable WTRU.

[0016] The method may further comprise a step of determining a SBFD maximum transmission power associated with the second type of ROs; and a step of transmitting the PRACH transmission in the second type of ROs on condition that the PRACH power is below the SBFD maximumtransmission power. The method may further comprise a step of determining that the PRACH transmission is capped due to capped uplink power for a WTRU-to-WTRU cross-layer interference, CLI, mitigation.

[0017] The method may further comprise a step of receiving a second message comprising second configuration information indicating one or more repetition threshold values. The method may further comprise a step of determining a repetition threshold value based on path loss measurement; and a step of determining using repetition of PRACH transmission based on the determined repetition threshold value. On condition that a determined type of ROs of a first PRACH transmission of the set of PRACH transmissions differs from a determined type of ROs of a second PRACH transmission of the set of PRACH transmissions, the method may further comprise a step of transmitting the first and the second PRACH transmission respectively in the determined type of ROs of the first and the second PRACH transmission; and stopping PRACH transmission of the set of PRACH transmissions.

[0018] In an embodiment, a WTRU, comprising a processor, a transceiver unit and a storage unit, may be configured to receive a first message comprising first configuration information indicating resources for a first type of random access channel occasions, ROs, and for a second type of ROs. The WTRU may be further configured to determine to use the second type of ROs for a physical random access channel, PRACH, transmission based on a determined PRACH power. The WTRU may be further configured to transmit the PRACH transmission in the second type of ROs using the PRACH power. The WTRU may be further configured to ramp the PRACH power used for the PRACH transmission in the second type of ROs. The WTRU may be further configured to switch from the second type of ROs to the first type of ROs for PRACH transmission, on condition that the PRACH power for a PRACH transmission is capped; and to transmit the PRACH transmission in the first type of ROs using the PRACH power.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] 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 are not 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:

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

[0021] 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;

[0022] 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;

[0023] 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;

[0024] FIG. 2 is an example of a block diagram illustrating slots for potential random access channel occasions;

[0025] FIG. 3 is an example of a block diagram illustrating example of slots for random access channel occasions in of subband non-overlapping full duplex;

[0026] FIG. 4 is an example of a block diagram illustrating example of valid / invalid slots for random access channel occasions in time-domain;

[0027] FIG. 5 is a flow chart diagram illustrating an example of a method implemented in a WTRU for random access channel occasion according to an embodiment;

[0028] FIG. 6 is a flow chart diagram illustrating an example of another method implemented in a WTRU for random access channel occasion according to another embodiment; and

[0029] FIG. 7 is a flow chart diagram illustrating an example of another method implemented in a WTRU for random access channel occasion according to another embodiment.DETAILED DESCRIPTION

[0030] 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 any portion 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.

[0031] Hereinafter, ‘a’ and ‘an’ and similar phrases are to be interpreted as ‘one or more’ and ‘at least one’ . Similarly, any term which ends with the suffix ‘(s)’ is to be interpreted as ‘one or more’ and ‘at least one’. The term ‘may’ is to be interpreted as ‘may, for example’.

[0032] A sign, symbol, or mark of forward slash 7’ is to be interpreted as ‘and / or’ unless particularly mentioned otherwise, where for example, ‘A / B’ may imply ‘A and / or B’.

[0033] 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.

[0034] 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.

[0035] 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 industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0036] 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.

[0037] 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.

[0038] 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).

[0039] 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 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 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).

[0040] 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).

[0041] 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).

[0042] 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).

[0043] 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.

[0044] 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 technologysuch 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.

[0045] 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.

[0046] 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.

[0047] 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 includemultiple 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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 twoor more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0052] 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.

[0053] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. 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).

[0054] 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.

[0055] 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.

[0056] 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 light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0057] 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)).

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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 for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

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

[0068] 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 have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.

[0069] 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 signalling. 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.

[0070] 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.

[0071] 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.

[0072] 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 in802.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. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0073] WLAN systems, which may support multiple channels, and channel bandwidths, such as802.1 In, 802.1 lac, 802.1 laf, 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.

[0074] 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.

[0075] 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.

[0076] 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).

[0077] 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).

[0078] 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 standaloneconfiguration, 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.

[0079] 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.

[0080] 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.

[0081] 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 signalling, 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.

[0082] 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 UE 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.

[0083] 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.

[0084] 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 Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0085] 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.

[0086] 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 (e.g., a network node) may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0087] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a network node (e.g., 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.

[0088] Physical random access channel (PRACH) power (e.g., for a PRACH preamble transmission) may be determined by a WTRU. The WTRU may determine the PRACH power based on one or more of a preamble received target power (e.g., PREAMBLE RECEIVED TARGET POWER) and a determined, measured, or calculated pathloss. The WTRU may limit the power by a maximum power (e.g., Pcmax,c which may also be represented by Pcmax,f,c.).

[0089] For example, a WTRU may determine a transmission power for a PRACH, pRACH,b,f,c(z), on active uplink (UL) bandwidth part (BWP) b of carrier f of cell c based on downlink (DL) reference signal (RS) for cell c in transmission occasion z as: pRACH,b,f,c(z)=min{ cMAX,f,c(z), pRACH, target, f,c + PLb,i,e } [dBm],Wherein: cMAX,f,c(z) may be a WTRU configured maximum output power for carrier f of cell c within transmission occasion z, PRACH, target, f,c may be the PRACH target reception power PREAMBLE RECEIVED TARGET POWER for the active UL BWP b of carrier f of cell c, and L / .b.r.c may a pathloss for the active UL BWP b of carrier / based on the DL RS associated with thePRACH transmission on the active DL BWP of cell c. PL i,cmay be calculated by the WTRU in as (referenceSignalPower - higher layer filtered RSRP). The DL RS may be a synchronization signal block (SSB) or a channel state information reference signal (CSLRS).

[0090] The WTRU may determine PREAMBLE RECEIVED TARGET POWER based on a power ramping counter and a power ramping step. For example, PREAMBLE RECEIVED TARGET POWER may be determined as: \preambleReceivedTargetPower + DELTA PREAMBLE +(PREAMBLE POWER RAMPING COUNTER - 7) x PREAMBLE POWER RAMPING STEP + POWER OFFSET 2 STEP RA\

[0091] One or more of preambleReceivedTargetPower, DELTA PREAMBLE, PREAMBLE POWER RAMPING STEP, and POWER OFFSET 2STEP RA may be configured (e.g., received via signalling such as SIB or RRC signalling).

[0092] POWER OFFSET 2 STEP RA may be omitted or set to 0, for example when a 4-step RA procedure is used.

[0093] The WTRU may determine the maximum output power it may use for a transmission based on one or more of the following: the WTRU’s power class maximum power, power reductions allowed for meeting requirements such as emissions or SAR (Specific Absorption Rate) requirements, reductions related to tolerances, and a signalled maximum power, Pcmax,c.

[0094] In new radio, a WTRU may receive RACH configuration in time domain via one or more configuration information. Table 1 may provide an example of RACH configurations for new radio frequency division duplexing (NR-FDD) for a frequency range from 450 MHz to 6 GHz (FR1).TABLE 1 : Example of RACH configuration for FR1 paired spectrumTable 2 may provide an example of RACH configurations for new radio time division duplexing (NR- TDD) for a frequency range from 24,25 GHz to 52,6 GHz, wherein the table includes indications on the slot number that may be used for the configured ROs.TABLE 2: Example of RACH configuration for FR2 unpaired spectrum

[0095] The configured ROs in time-domain may be more consecutive and back-to-back in NR- FDD; however, the configured slot numbers may be more distanced in NR-TDD, for example due to aligning the ROs in time domain with UL-only slots, for example based on configured periodicity.

[0096] Referring to FIG. 2, an example of potential valid RACH occasions is shown. The grey slots of the first line (Legacy TDD RACH Occasions) show the valid ROs based on legacy TDD configurations (only in UL-only slots). However, the grey slots of the second line (New config for SBFD RACH occasions) may show the potentially valid RACH occasions for an SBFD-capable WTRU that is much more than legacy TDD.

[0097] In the description of various embodiment below, ‘a’ and ‘an’ and similar phrases are to be interpreted as ‘one or more’ and ‘at least one’. Similarly, any term which ends with the suffix ‘(s)’ is to be interpreted as ‘one or more’ and ‘at least one’. The term ‘may’ is to be interpreted as ‘may, for example’. A symbol 7’ (e.g., forward slash) may be used herein to represent ‘and / or’, where for example, ‘A / B’ may imply ‘A and / or B’.

[0098] A WTRU may transmit or receive a physical channel or reference signal according to at least one spatial domain filter. In the following description, the term “beam” may be used to refer to a spatial domain filter. The WTRU may transmit a physical channel or signal using the same spatial domain filter as the spatial domain filter used for receiving an RS (such as CSLRS) or a SSB. The WTRU transmission may be referred to as “target”, and the received RS or SS block may be referred to as “reference” or “source”. In such case, the WTRU may be said to transmit the target physical channel or signal according to a spatial relation with a reference to such RS or SS block.

[0099] The WTRU may transmit a first physical channel or signal according to the same spatial domain filter as the spatial domain filter used for transmitting a second physical channel or signal. The first and second transmissions may be referred to as “target” and “reference” (or “source”), respectively. In such case, the WTRU may be said to transmit the first (target) physical channel or signal according to a spatial relation with a reference to the second (reference) physical channel or signal.

[0100] A spatial relation may be implicit, configured by radio resource control (RRC) or signaled by medium access control control element (MAC CE) or downlink control information (DCI). For example, a WTRU may implicitly transmit physical uplink shared channel (PUSCH) and demodulation reference signal (DM-RS) of PUSCH according to the same spatial domain filter as a sounding reference signal (SRS) indicated by a SRS resource indicator (SRI) indicated in DCI or configured by RRC.

[0101] In another example, a spatial relation may be configured by RRC for an SRS resource indicator (SRI) or signaled by MAC CE for a PUCCH. Such spatial relation may also be referred to as a “beam indication”.

[0102] The WTRU may receive a first (target) downlink channel or signal according to the same spatial domain filter or spatial reception parameter as a second (reference) downlink channel or signal. For example, such association may exist between a physical channel such as physical downlink control channel (PDCCH) or (physical downlink shared channel) PDSCH and its respective DM-RS. At least when the first and second signals are reference signals, such association may exist when the WTRU is configured with a quasi-colocation (QCL) assumption type D between corresponding antenna ports. Such association may be configured as a transmission configuration indicator (TCI) state. A WTRU may be indicated an association between a CSI-RS or SS block and a DM-RS by an index to a set of TCI states configured by RRC and / or signaled by MAC CE. Such indication may also be referred to as a “beam indication”.

[0103] In the description of various embodiments below, a transmission and reception point (TRP) may be interchangeably used with one or more of transmission point (TP), reception point (RP), radio remote head (RRH), distributed antenna (DA), base station (BS), a sector of a BS, and a cell (e.g., a geographical cell area served by a BS). In the description of various embodiments below, Multi-TRP may be interchangeably used with one or more of MTRP, M-TRP, and multiple TRPs.

[0104] In the description of various embodiments below, the term “subband” and / or “sub-band” may be used to refer to a frequency-domain resource and may be characterized by at least one ofthe following: a set of resource blocks (RBs); a set of resource block sets (RB sets), e.g. when a carrier has intra-cell guard bands; a set of interlaced resource blocks; a bandwidth part, or portion thereof; and a carrier, or portion thereof. For example, a subband may be characterized by a starting RB and number of RBs for a set of contiguous RBs within a bandwidth part. A subband may also be defined by the value of a frequency-domain resource allocation field and bandwidth part index.

[0105] In the description of various embodiments below, the term “XDD” may be used to refer to a subband-wise duplex (e.g., either UL or DL being used per subband) and may be characterized by at least one of the following: cross division duplex (e.g., subband-wise FDD within a TDD band); subband non-overlapping full duplex (SBFD); subband-based full duplex (e.g., full duplex as both UL and DL are used / mixed on a symbol / slot, but either UL or DL being used per subband on the symbol / slot); frequency-domain multiplexing (FDM) of DL / UL transmissions within a TDD spectrum; a full duplex other than a same-frequency (e.g., spectrum sharing, subband-wise- overlapped) full duplex; and an advanced duplex method, e.g., other than (pure) TDD or FDD

[0106] In the description of various embodiments below, the term “dynamic( / flexible) TDD” may be used to refer to a TDD system / cell which may dynamically (and / or flexibly) change / adjust / switch a communication direction (e.g., a downlink, an uplink, or a sidelink, etc.) on a time instance (e.g., slot, symbol, subframe, and / or the like). In an example, in a system employing dynamic / flexible TDD, a component carrier(CC) or a bandwidth part (BWP) may have one single type among ‘D’, ‘U’, and ‘F’ on a symbol / slot, based on an indication by a group- common(GC)-DCI (e.g., format 2 0) comprising a slot format indicator (SFI), and / or based on TDD-UL-DL-config-common / dedicated configurations. On a given time instance / slot / symbol, a first gNB (e.g., cell, TRP) employing dynamic / flexible TDD may transmit a downlink signal to a first WTRU being communi cated / associated with the first gNB based on a first SFI and / or TDD- UL-DL-config configured / indicated by the first gNB, and a second gNB (e.g., cell, TRP) employing dynamic / flexible TDD may receive an uplink signal transmitted from a second WTRU being communicated / associated with the second gNB based on a second SFI and / or tdd-UL-DL- config configured / indicated by the second gNB. In an example, the first WTRU may determine that the reception of the downlink signal is being interfered by the uplink signal, where the interference caused by the uplink signal may refer to a WTRU-to-WTRU cross-layer interference (CLI).

[0107] A WTRU may report a subset of channel state information (CSI) components, where CSI components may correspond to at least a CSI-RS resource indicator (CRI), a SSB resource indicator (SSBRI), an indication of a panel used for reception at the WTRU (such as a panelidentity or group identity), measurements such as Ll-RSRP, Ll-SINR taken from SSB or CSI-RS (e.g. cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and other channel state information such as at least rank indicator (RI), channel quality indicator (CQI), precoding matrix indicator (PMI), Layer Index (LI), and / or the like.

[0108] A WTRU may receive a synchronization signal / physical broadcast channel (SS / PBCH) block. The SS / PBCH block (SSB) may include a primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH). The WTRU may monitor, receive, or attempt to decode an SSB during initial access, initial synchronization, radio link monitoring (RLM), cell search, cell switching, and so forth.

[0109] A WTRU may measure and report the channel state information (CSI), wherein the CSI for each connection mode may include or be configured with one or more of following:

[0110] (i) CSI Report Configuration, including one or more of the following: CSI report quantity, e.g., Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), CSLRS Resource Indicator (CRI), Layer Indicator (LI), etc; CSI report type, e.g., aperiodic, semi persistent, periodic; CSI report codebook configuration, e.g., Type I, Type II, Type II port selection, etc.; and CSI report frequency.

[0111] (ii) CSLRS Resource Set, including one or more of the following CSI Resource settings: non-zero power channel state information reference signal (NZP-CSI-RS) resource for channel measurement; NZP-CSI-RS resource for interference measurement; and channel state information-interference measurement (CSLIM) resource for interference measurement.

[0112] (iii) NZP CSLRS resources, including one or more of the following: NZP CSLRS resource ID; periodicity and offset; QCL info and TCI-state; and resource mapping, e.g., number of ports, density, code division multiplexing (CDM) type, etc.

[0113] A WTRU may indicate, determine, or be configured with one or more reference signals. The WTRU may monitor, receive, and measure one or more parameters based on the respective reference signals. For example, one or more of the following parameters may apply. The following parameters are non-limiting examples of the parameters that may be included in reference signal(s) measurements. One or more of these parameters may be included. Other parameters may be included. The parameters may be any of:

[0114] (i) Synchronization signal (SS) reference signal received power (SS-RSRP) that may be measured based on the synchronization signals (e.g., demodulation reference signal (DMRS) in PBCH or SSS). It may be defined as the linear average over the power contribution of the resource elements (RE) that carry the respective synchronization signal. In measuring the RSRP, powerscaling for the reference signals may be required. In case SS-RSRP is used for Ll-RSRP, the measurement may be accomplished based on CSI reference signals in addition to the synchronization signals.

[0115] (ii) CSI-RSRP that may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective CSI-RS. The CSI-RSRP measurement may be configured within measurement resources for the configured CSI-RS occasions.

[0116] (iii) SS signal-to-noise and interference ratio (SS-SINR) that may be measured based on the synchronization signals (e.g., DMRS in PBCH or SSS). It may be defined as the linear average over the power contribution of the resource elements (RE) that carry the respective synchronization signal divided by the linear average of the noise and interference power contribution. In case SS- SINR is used for Ll-SINR, the noise and interference power measurement may be accomplished based on resources configured by higher layers.

[0117] (iv) CSI-SINR that may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective CSI-RS divided by the linear average of the noise and interference power contribution. In case CSI-SINR is used for Ll-SINR, the noise and interference power measurement may be accomplished based on resources configured by higher layers. Otherwise, the noise and interference power may be measured based on the resources that carry the respective CSI-RS.

[0118] (v) Received signal strength indicator (RS SI) that may be measured based on the average of the total power contribution in configured OFDM symbols and bandwidth. The power contribution may be received from different resources (e.g., co-channel serving and non-serving cells, adjacent channel interference, thermal noise, and so forth).

[0119] (vi) Cross-Layer interference received signal strength indicator (CLI-RSSI) that may be measured based on the average of the total power contribution in configured OFDM symbols of the configured time and frequency resources. The power contribution may be received from different resources (e.g., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, and so forth)

[0120] (vii) Sounding reference signals RSRP (SRS-RSRP) that may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective SRS.

[0121] (viii) Secondary synchronization signal reference signal received quality (SS-RSRQ) that may be measured based on measurements on the reference signal received power (SS-RSRP) andreceived signal strength (RS SI). In an example, the SS-RSRQ may be calculated as the ratio of NxSS-RSRP / NR carrier RS SI, where N may be determined based on the number of resource blocks that are in the corresponding NR carrier RSSI measurement bandwidth. As such, the measurements to be used in the numerator and denominator may be over the same set of resource blocks.

[0122] (ix) CSI reference signal received quality (CSI-RSRQ) that may be measured based on measurements on the reference signal received power (CSI-RSRP) and received signal strength (RSSI). In an example, the SS-RSRQ may be calculated as the ratio of NxCSI-RSRP / CSIRSSI, where N may be determined based on the number of resource blocks that are in the corresponding CSI-RSSI measurement bandwidth. As such, the measurements to be used in the numerator and denominator may be over the same set of resource blocks.

[0123] In the following description of various embodiments, a property of a grant or assignment may consist of at least one of the following: a frequency allocation; an aspect of time allocation, such as a duration; a priority; a modulation and coding scheme; a transport block size; a number of spatial layers; a number of transport blocks; a TCI state, CRI or SRI; a number of repetitions; whether the repetition scheme is Type A or Type B; whether the grant is a configured grant type 1, type 2 or a dynamic grant; whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment; a configured grant index or a semi-persistent assignment index; a periodicity of a configured grant or assignment; a channel access priority class (CAPC); and any parameter provided in a DCI, by MAC or by RRC for the scheduling the grant or assignment.

[0124] In the following description of various embodiments, an indication by DCI may consist of at least one of the following: an explicit indication by a DCI field or by RNTI used to mask or scramble the CRC of the DCI; and an implicit indication by a property such as DCI format, DCI size, coreset or search space, aggregation level, first resource element of the received DCI (e.g., index of first control channel element), where the mapping between the property and the value may be signaled by RRC or MAC.

[0125] Receiving or monitoring for a DCI with or using an RNTI may mean that the CRC of the DCI is masked or scrambled with the RNTI.

[0126] In the following description of various embodiments, a signal may be interchangeably used with one or more of following: sounding reference signal (SRS); channel state information - reference signal (CSI-RS); demodulation reference signal (DM-RS); phase tracking reference signal (PT-RS) and synchronization signal block (SSB)

[0127] In the following description of various embodiments, a channel may be interchangeably used with one or more of following: physical downlink control channel (PDCCH); physical downlink shared channel (PDSCH); physical uplink control channel (PUCCH); physical uplink shared channel (PUSCH); physical random access channel (PRACH); Etc.

[0128] Hereafter, downlink reception may be used interchangeably with Rx occasion, PDCCH, PDSCH, SSB reception.

[0129] Hereafter, uplink transmission may be used interchangeably with Tx occasion, PUCCH, PUSCH, PRACH, SRS transmission. Hereafter, RS may be interchangeably used with one or more of RS resource, RS resource set, RS port and RS port group. Hereafter, RS may be interchangeably used with one or more of SSB, CSI-RS, SRS, and DM-RS.

[0130] Herein, time instance, slot, symbol, and subframe may be used interchangeably. Herein, UL-only and DL-only Tx / Rx occasions may interchangeably be used with legacy TDD UL or legacy TDD DL, respectively. In an example, the legacy TDD UL transmission or legacy DL reception occasions may be the cases where SBFD is not configured and / or where SBFD is disabled.

[0131] Hereinafter, the terms received signal power, received signal energy, received signal strength, SSB EPRE, CSI EPRE, RSRP, RSSI, SINR, RSRQ, SS-RSRP, SS-RSSI, SS-SINR, SS- RSRQ, CSI-RSRP, CSI-RSSI, CSLSINR, and CSLRSRQ may be used interchangeably.

[0132] Herein, the term CLI may be used interchangeably with interference. Herein, the term non-SBFD may be used interchangeably with operation without SBFD, TDD, and legacy TDD. Herein, the terms ‘paired spectrum’ and FDD may be used interchangeably. Herein, the terms ‘unpaired spectrum’ and TDD may be used interchangeably. Herein, the terms ‘WTRU is configured’, ‘WTRU is indicated’, ‘WTRU receives configuration’, and so forth, may imply that the configuration is indicated for example ‘via RRC, MAC-CE, DCI, MIB, SIB, and so forth’, unless indicated otherwise, where for example, ‘WTRU is configured’ may imply ‘UE is configured via RRC, MAC-CE, MIB, SIB, and so forth’ .

[0133] Herein, the term preamble received target power may be used interchangeably with PRACH power, preamble power, UL power, UL RSRP, UL RSSI, PCMAX, P_(CMAX,f,c), P CMAX, and so forth. Herein, the terms PRACH, RACH, random-access, random-access occasion, RACH occasion, PRACH transmission, RACH transmission, RA, and RO, may be used interchangeably.

[0134] In various embodiments, a WTRU may be configured with one or more types of slots within a bandwidth, wherein a first type of slot may be used or determined for a first direction(e.g., downlink); a second type of slot may be used or determined for a second direction (e.g., uplink); a third type of slot may have a first group of frequency resources within the bandwidth for a first direction and a second group of frequency resources within the bandwidth for a second direction.

[0135] The bandwidth may be interchangeably used with bandwidth part (BWP), carrier, subband, and system bandwidth. The first type of slot (e.g., the slot for a first direction) may be referred to as downlink slot. The second type of slot (e.g., slot for a second direction) may be referred to as uplink slot. The third type of slot may be referred to as Sub-Band (non-overlapping) Full Duplex (SBFD) slot. The group of frequency resource for a first direction may be referred to as downlink subband, downlink frequency resource, or downlink RBs. The group of frequency resource for a second direction may be referred to as uplink subband, uplink frequency resource, or uplink RBs. The group of frequency resource for a flexible direction (e.g., that can be configured for a first direction, second direction, etc.) may be referred to as flexible subband, flexible frequency resource, or flexible RBs. The group of frequency resource between a first direction and a second direction may be referred to as guard band, guard frequency resource, or guard RBs.

[0136] In an embodiment, a (e.g., SBFD-enabled) WTRU may receive or be configured with one or more SBFD UL or DL subbands in one or more DL, UL, and / or flexible TDD time instances (e.g., symbols, slots, frames, and so forth). The WTRU may be configured with one or more resource allocations for SBFD subbands. For example, the SBFD configuration may include a flag signal (e.g., enabled / disabled), wherein, as non limited example, a first value (e.g., zero (0)) may indicate a first mode of operation (e.g., SBFD configuration), and a second value (e.g., one (1)) may indicate a second mode of operation (e.g., non-SBFD operation). The modes of operation (e g., SBFD or non-SBFD) may be indicated via, for example MIB, SIB, RRC, MAC-CE, DCI, and so forth.

[0137] In various embodiments, the WTRU may receive the time resources (e.g., one or more symbols, slots, and so forth), for which the first mode of operation (e.g., SBFD) may be defined in for example one or more BWPs, subbands, component carriers (CC), cells, and so forth. The WTRU may receive the frequency resources (e.g., subbands, BWPs, etc. including one or more PRBs) within (active and / or linked) BWP, for which the first mode of operation (e.g., SBFD) may be configured. The time instances (e.g., slots, symbols) may be indicated based on periodic, semi- persistent, or aperiodic configurations. In an example, the time instances may be indicated via a bitmap configuration, where each bit may correspond to a time instance (e.g., slot, symbol,subframe, etc.) and each bit indication may indicate whether corresponding time instance can be used for the first or second mode of operation.

[0138] In an embodiment, a WTRU may be configured with a DL TDD configuration for a component carrier (CC) or a BWP for one or more Rx occasions (e.g., via tdd-UL-DL-config- common, dedicated configurations, slot format indicator (SFI), and so forth). As such, on condition that the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and / or BWPs) may be configured for the transmission in UL channels and / or Tx occasions.

[0139] In another embodiment, the WTRU may be configured with an UL TDD configuration for a component carrier (CC) or a BWP for one or more Tx occasions (e.g., via tdd-UL-DL-config- common, dedicated configurations, slot format indicator (SFI), and so forth). As such, on condition that the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and / or BWPs) may be configured as the DL channels and / or Rx occasions.

[0140] In another embodiment, the WTRU may be configured with a DL, UL, or flexible TDD configuration for a component carrier (CC) or a BWP for one or more Rx / Tx occasions (e.g., via tdd-UL-DL-config-common, dedicated configurations, slot format indicator (SFI), and so forth). As such, on condition that the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and / or BWPs) may be configured for the first mode of operation (e.g., either UL transmission or DL reception based on the configurations).

[0141] The duplexing mode for the first mode of operation (e.g., SBFD configuration (UL / DL)) may be indicated via a flag indication, where for example a first value (e.g., zero (0)) may indicate a first direction (e.g., UL duplexing mode), and a second value (e.g., one (1)) may indicate a second direction (e.g., DL duplexing model).

[0142] The duplexing mode configuration and / or flag for the first mode of operation (e.g., SBFD) may be configured as part of modes of operation configuration, for example via MIB, SIB, RRC, DCI, MAC-CE, etc.

[0143] The duplexing mode configuration and / or flag for the first mode of operation (e.g., SBFD) may be configured as part of resource allocation configuration for a Tx / Rx occasion.

[0144] In various embodiments, a WTRU may be configured with one or more types of slots. The WTRU may be configured with a first slot with a first type, where the first type may be for example SBFD slot. The WTRU may be configured with a second slot with a second type, wherethe second type may be for example non-SBFD slot. As for the first slot with the first type (SBFD), the WTRU may be configured with one or more DL, UL, flexible, guard, etc. subbands in the frequency domain, throughout the BWP, for the duration of the first slot. However, in the second slot with the second type (non-SBFD), the WTRU may be configured with only one direction type, for example DL, UL, flexible, etc., in the frequency domain, throughout the BWP, for the duration of the second slot.

[0145] In an embodiment, on condition that the WTRUE is configured with a second slot with UL direction, this may imply legacy TDD UL slot, UL-only slot, and / or non-SBFD UL slot. In another embodiment, on condition that the WTRU is configured with a third slot with second type (non-SBFD) with DL direction, this may imply legacy TDD DL slot, DL-only slot, and / or non- SBFD DL slot. In another embodiment, on condition that the WTRU is configured with a fourth slot with second type (non-SBFD) with flexible direction, this may imply legacy TDD flexible slot and / or non-SBFD flexible slot, and so forth.

[0146] A WTRU may receive, identify, or be configured with, the time domain resource allocations for one or more (e.g., consecutive) RACH occasions (RO) based on the higher-layer parameter prach-Configurationlndex, or by msgA-PRACH-Configurationlndex, if configured. These parameters may denote the PRACH configuration index corresponding to one or more tables that include random access parameters.

[0147] The WTRU may be configured with one or more of the following parameters:

[0148] (i) Preamble format. For example, the WTRU may be configured with preamble format that may refer to one of the possible formats, namely: Al, A2, A3, Bl, Al / Bl, A2 / B2, A3 / B3, B4, CO, C2. The preamble format may identify the corresponding cyclic prefix (CP) duration, sequence part duration, guard time duration (if applicable), etc.

[0149] (ii) Frame number, subframe number, and / or slot number. For example, the WTRU may be configured with time-domain allocations, subframe number, and / or slot numbers during which the ROs may be configured. Using this parameter, the WTRU may determine the RO slot, for example within the corresponding subframe, wherein the WTRU may transmit the configured PRACH in one or more of the determined ROs.

[0150] (iii) Starting symbol. For example, the WTRU may determine the symbol-level index corresponding to the starting position of the first RO transmission within the indicated and / or configured RO slot.

[0151] (iv) Number of PRACH slots within a 60 kHz slot. For example, the WTRU may be indicated with the number of PRACH slots within a reference 60kHz slot. In an embodiment, theWTRU may be configured with the number of PRACH slots for high SCS values such as 120kHz, 480kHz, 960kHz, etc., where the WTRU may consider the 60kHz PRACH slot as the reference slot.

[0152] (v) Number of time-domain PRACH occasions within a PRACH slot (j\]A'slotf porexample, the WTRU may be configured with the number of consecutive ROs that are located within a PRACH slot in time domain.

[0153] (vi) PRACH duration. For example, the WTRU may be configured with the duration of an RO in number of symbols.

[0154] In various embodiments, a WTRU may receive the frequency domain resource allocations for the ROs based on one or more of the following higher-layer parameters:

[0155] (i) msgl-FrequencyStart or msgA-RO-FrequencyStart, if configured, may indicate the offset of the lowest PRACH transmission occasion in frequency domain with respect to the PRB 0.

[0156] (ii) msgl-FDM or msgA-RO-FDM, if configured, may indicate the number of PRACH transmission occasions that are FDMed in one time-domain RO. The WTRU may receive, identify, or be configured with the number of ROs in frequency domain (M) per each time-domain PRACH occasion based on the higher layer parameter msgl-FDM, msgl-FDM-16, or msgA-RO-FDM, if configured, where msgl-FDM={one, two, four, eight}. The WTRU may number the PRACH frequency resources TIRA={0, 1, ...,M-1}, starting from the lowest frequency, in increasing order in the initial uplink BWP during the initial access or the active uplink BWP otherwise.

[0157] In various embodiments, a WTRU may receive the association and mapping between the SS / PBCH block indexes and PRACH transmission occasions based on higher layer parameter ssb- perRACH-OccasionAndCB-PreamblesPerSSB = {1 / 8,1 / 4,1 / 2,1,2,4,8,16}. The parameter may indicate the number of SS / PBCH block indexes associated with a PRACH transmission occasion in addition to the number of preambles per SS / PBCH block index per PRACH occasion.

[0158] About a selection of RA resources in SFBD systems with capped power, in various embodiments, a WTRU may be configured with any of the following. SBFD-capable WTRU may be configured with a first type of RO (e.g., Type 1 RO) in random access resources that may coincide in time with legacy TDD configurations. The WTRU may be additionally configured with a second type of RO (e.g., Type 2 RO) in random access resources that may coincide in time with SBFD configurations. The WTRU may be configured to use Type 2 ROs for PRACH (e.g., PRACH repetition), wherein the WTRU may determine to fall back to use Type 1 ROs on condition that UL power capping (e.g., due to CLI mitigation) is required in SBFD symbols. Itmay be preferable to define separate configuration for additional valid ROs for the SBFD-capable WTRUs so the same SSB-to-RO association configured for legacy WTRUs can be kept intact

[0159] More particularly, a WTRU may receive configuration information indicating resources for a first type or set of ROs (e.g., Type 1 ROs) and a second type or set of ROs (e.g., Type 2 ROs). The Type 1 ROs may be legacy ROs, e.g., ROs that may be used by non-SBFD capable WTRUs. The Type 1 ROs may be configured and / or valid in (e.g., only in) TDD UL symbols and / or slots. The Type 2 ROs may be SBFD ROs. The Type 2 ROs may be configured and / or valid in (e.g., only in), SBFD symbols and / or slots. The Type 2 ROs may be used (e.g., only used) by SBFD capable WTRUs.

[0160] Optionally, the WTRU may receive configuration of one or more threshold values, e.g., for determining a number of repetitions for PRACH transmission (e.g., for PRACH preamble or msgl transmission where a msgl transmission may be a PRACH preamble transmission).

[0161] The WTRU may determine an RS, e.g., an SSB or a CSI-RS. In an embodiment, the WTRU may detect or may select an SSB (e.g., a best SSB) or may receive a PDCCH order to perform PRACH transmission, wherein the PDCCH order indicates the RS.

[0162] Optionally, based on at least one of the one or more thresholds (e.g., an RSRP or pathloss measurement that may be associated with or performed for the selected, detected, or indicated SSB or RS), the WTRU may determine to use repetition (e.g., of Nreps) for a PRACH transmission.

[0163] More particularly, in various embodiments, a WTRU may determine whether to use Type 1 ROs or Type 2 ROs for the PRACH transmission (e.g., with repetitions) based on one or more of a PRACH power or PRACH maximum power (e.g., maximum transmission power). ‘Maximum power’ and ‘maximum transmission power’ may be used interchangeably hereafter.

[0164] In an embodiment, the WTRU may determine a PRACH transmission power and may determine to use Type 1 or Type 2 ROs based on the determined PRACH transmission power. For example, on condition that the determined PRACH transmission power exceeds (or is equal to) a power threshold value (e.g., a configured power threshold value) the WTRU may determine to use Type 1 ROs. For example, on condition that the determined PRACH transmission power is below the maximum power threshold value, the WTRU may determine to use Type 2 ROs.

[0165] In an embodiment, the WTRU may determine a maximum transmission power (e.g., configured maximum power or Pcmax,c or Pcmax,f. c) for the PRACH transmission and may determine to use Type 1 or Type 2 ROs based on the determined maximum transmission power. For example, on condition that the determined PRACH transmission power (before limiting based on the maximum power) exceeds (or is equal to) the determined maximum power, the WTRU maydetermine to use Type 1 ROs. For example, if the determined PRACH transmission power (before limiting based on the maximum power) is below (or is equal to) the determined maximum power, the WTRU may determine to use Type 2 ROs

[0166] In an embodiment, the WTRU may determine a maximum power for an SBFD time unit (e.g., symbol, muti-symbol, or slot) transmission differently from the maximum power for a non- SBFD time unit transmission. The WTRU may base the decision to use Type 1 or Type 2 ROs on an SBFD time unit maximum power determination. For example, the SBFD maximum power determination may include an extra power reduction that may be taken from the WTRU power class power. The SBFD maximum power determination may have a separate signaled limit, e.g., a separate Pcmax,c. For example, the SBFD maximum power determination may result in a lower maximum power than a non-SBFD maximum power determination for the same transmission time unit or transmission occasion.

[0167] In an embodiment, the WTRU may transmit a PRACH transmission (e.g. a preamble transmission) in an RO of the determined Type 1 or Type 2 ROs. The RO may be associated with the determined RS. The WTRU may transmit the PRACH transmission with the determined transmission power or with the determined transmission power after applying a maximum power limitation if the determined power exceeds the limit. The maximum power limitation may be determined based on the RO type used for the transmission (e.g., SBFD or non-SBFD).

[0168] For the case of Nrep repetitions, the WTRU may repeat the PRACH transmission for a total of Nrep transmissions. The Nrep repetitions may use the same type of ROs as was determined for the first transmission.

[0169] Optionally, for the case with repetitions, the WTRU may determine whether to use Type 1 ROs or Type 2 ROs based on whether the PRACH transmission is the first transmission of a set of repetitions or a later repetition within the set of repetitions. For example, the WTRU may make the determination to use Type 1 ROs or Type 2 ROs prior to the first transmission of a set of repetitions and may use the determined ROs for all the repetitions in the set of repetitions. For example, the WTRU may make the determination to use Type 1 ROs or Type 2 ROs prior to each transmission of a set of repetitions (e.g., when Type 2 was chosen for the first transmission). On condition that the WTRU determines to use a different RO type than was used for a previous repetition in the set (e.g., Type 1 determined when Type 2 was used for a previous repetition), the WTRU may not transmit the rest of the repetitions.

[0170] In an embodiment, on condition that the WTRU does not receive a random access response (RAR) in response to the PRACH transmission or the set of repeated PRACHtransmissions, the WTRU may ramp the power (e.g., increase the power ramping counter) and / or change to using a different type of ROs and send another PRACH transmission (e.g., with repetitions). For example, on condition that the WTRU used Type 2 ROs, the WTRU may switch to using Type 1 ROs. For the case of repetition, if the WTRU does not transmit all the repetitions (e.g., due to a change in RO type), the WTRU may not ramp the power before transmitting the next set of PRACH repetitions.

[0171] In details, about RACH configuration. A WTRU may determine, may be configured, and / or may be indicated to receive and / or detect one or more SSBs. In an embodiment, the WTRU may determine to perform random access procedure based on at least one of the detected and / or received SSBs. For example, the WTRU may transmit PRACH, Msg 1, Msg 3, etc., or receive random access response (RAR), and further signaling as part of the random access procedure. In another embodiment, the WTRU may receive and / or detect SSBs and perform random access (RA) procedure as part of initial access procedure, beam failure recovery, and so forth. In another embodiment, the WTRU may initiate a random access procedure based on at least one received PDCCH order, where the WTRU may receive configuration information and / or indications on SSB, PRACH preamble, RACH resources, etc.

[0172] The WTRU may receive one or more configuration information and / or indications for performing the random access procedure. For example, the WTRU may receive the configuration information and indications via SIB, RRC, MAC-CE, DCI, and so forth. For example, the configuration information and / or indications may correspond to the transmission of Msg 1 or Msg A, if configured. In an example, the configuration information may include one or more of the following:

[0173] (i) PRACH configuration index. In an embodiment, the WTRU may receive a PRACH configuration index that may indicate the available set of PRACH occasions (ROs) for the transmission of PRACH preamble for Msg 1 or Msg A, if configured. In an embodiment, a WTRU may be configured, indicated, and / or determine to use the configured and / or indicated PRACH configuration index based on one or more duplex configurations. In an embodiment, the WTRU may be configured to use the configured PRACH configuration index as an indication in a first table, where the first table may, for example, be used for WTRUs operating in FDD operation; the WTRU may be configured to use the configured PRACH configuration index as an indication to a second table, where the second table may for example be used for WTRUs operating in TDD operation; the WTRU may be configured to use the configured PRACH configuration index as anindication to a third table, where the third table may for example be used for WTRUs operating in SBFD operation, and so forth.

[0174] (ii) Preamble received target power. In an embodiment, the WTRU may receive initial random access preamble power for the transmission of Msg 1 or Msg A.

[0175] (iii) RSRP Threshold for repetition number X of Msg 1 or MsgA. In an embodiment, the WTRU may receive configuration on the RSRP threshold, based on which the WTRU may determine to perform PRACH preamble repetition for X times. In an embodiment, on condition that the WTRU determines that the measured DL pathloss RSRP is lower than the received threshold for repetition number X, the WTRU may perform PRACH repetition for X times.

[0176] (iv) Power ramping step (e.g., powerRampingStep, msgA-PreamblePowerRampingStep, powerRampingStepHighPriority) . In an embodiemnt, the WTRU may use a configuration with power ramping step for increasing the PRACH transmission power, up to a configured maximum number of times (e.g., preambleTransMax), or until RAR is received.

[0177] (v) Maximum number of preamble transmission (e.g., preambleTransMax, preambleTransMax-Msgl -Repetition, msgA-TransMax, etc.). In an embodiment, the WTRU may be configured with the maximum number of Random Access Preamble transmission (e.g., Y), wherein the WTRU may increase the UL transmission power at each PRACH transmission occasion based on power ramping step (powerRampingStep). In an embodiment, a WTRU that is configured with a repetition number X, may perform PRACH repetition for X times, wherein the WTRU may transmit each repetition up to Y times that is the configured maximum number of allowed preamble transmission times (e.g., preambleTransMax-Msgl -Repetition). The WTRU may stop PRACH transmission if RAR is received. In case RAR is not received, and maximum number of preamble transmission is reached, the WTRU may switch to repetition with the next available higher repetition number.

[0178] In details, about RACH occasion type. In an embodiment, a WTRU may be configured with one or more RACH occasion (RO) types. For example, the WTRU may be configured with a Type 1 RO, where the Type 1 ROs coincide with one or more TDD UL-only time instances. In another embodiment, the WTRU may be configured with a Type 2 RO, where the Type 2 ROs coincide with one or more SBFD time instances. The WTRU may be configured with PRACH transmission based on one or more of the configured RO types. In an embodiment, the random access resources corresponding to different RO types may be mutually exclusive.

[0179] In an embodiment, a WTRU may receive one or more configuration information for determining the random access resources corresponding to Type 2 ROs. In an embodiment, theWTRU may determine, be configured, and / or indicated to use the received and / or configured RACH configuration index to determine the configuration information on the random access resources based on a new table of configurations. In an example, the table of configurations may include indications to the subframe number, slot number, number of PRACH occasions within a slot, PRACH durations. For example, the WTRU may use the indication to the new table to determine Type 2 ROs (e.g., in SBFD slots).

[0180] Referring to FIG. 3, in an embodiment, a WTRU may receive one or more indications and / or configurations on one or more offset values, wherein the WTRU may use the offset values to determine the random access resources corresponding to Type 2 ROs. In an example, the WTRU may use the configured and / or indicated offset value with respect to one or more of the configured Type 1 ROs (e.g., legacy TDD ROs). In an example, the offset value may be indicated as a positive or negative number (e.g., 0 to 40, or -20 to 20, etc.), for example to indicate an SBFD slot, for example within the corresponding subframe. Referring to FIG. 3 as a non-limited example, the WTRU may use the offset value to determine Type 2 ROs (e.g., in SBFD slots).

[0181] In details, about RACH repetition configurations. In various embodiments, a WTRU may receive one or more configurations and / or indications on random access repetition. In an embodiment, the WTRU may receive the configuration and / or indication via SIB, RRC, MAC- CE, DCI, etc. In an embodiment, the WTRU may determine the number of repetitions (e.g., X) based on one or more measured quality parameters and one or more thresholds. In an embodiment, the WTRU may measure DL pathloss RSRP, wherein the WTRU may determine that the measured RSRP is lower than a configured threshold for X-times repetition. As such, the WTRU may determine to perform preamble repetition for the determined X times. The WTRU may determine the random access resources based on the determined repetition (e.g., X), wherein the WTRU may determine the resources based on the association between the determined, selected, and / or configured SSB and configured ROs. In an embodiment, the WTRU may determine if the selected BWP for the random access procedure may be configured with the set(s) of random access resources with RO repetition number X, if the measured RSRP of the downlink pathloss reference is less than configured threshold, e.g., rsrp-threshold-repetitionNumX.

[0182] In various embodiments, the WTRU may determine the random access resources separately for different RO Types. In an embodiment, the WTRU may determine the set of random access resources corresponding to the configured and / or determined repetition times on Type 1 ROs; the WTRU may determine the set of random access resources corresponding to the configured and / or determined repetition times on Type 2 ROs.

[0183] In details, about selecting random access resources. In various embodiments, a WTRU may select ROs to be used for PRACH transmission between different RO types. In an embodiment, the WTRU may select the ROs to be used between ROs in Type 1 ROs (e.g., legacy TDD UL RO slots) or Type 2 ROs (e.g., BFD RO slots) for PRACH repetition. In an embodiment, the WTRU may receive indications and / or configurations to use Type 2 ROs as the main random access resources for PRACH transmission and / or repetition. The WTRU may be configured, be enabled, be allowed to use Type 1 ROs in case required. In an embodiment, the WTRU may determine the set of random access resources corresponding to the configured and / or determined repetition times on Type 2 RO.

[0184] In various embodiments, the WTRU may initiate a PRACH transmission procedure. IN an embodiment, the WTRU may determine to perform power ramping for PRACH transmission, wherein the WTRU may initiate a power ramping counter and / or increment the counter based on the configured power ramping step with each RACH transmission occasion. In an embodiment, the WTRU may initiate and / or calculate a preamble received target power based on an initially configured preamble received target power and the determined power ramping steps and values. In an embodiment, the WTRU may set PREAMBLE RECEIVED TARGET POWER to preambleReceivedTargetPower + (PREAMBLE POWER RAMPING COUNTER - 1) * PREAMBLE POWER RAMPING STEP. The WTRU may add one or more other determined, indicated, and / or configured parameters to the equation for setting the preamble received target power value.

[0185] In various embodiments, a WTRU may determine, be configured, and / or be indicated to cap and / or limit the uplink power for random access transmission occasions. In an embodiment, the WTRU may be indicated or determine to cap and / or limit the UL power in one or more (impacted and / or affected) first SBFD time instances. As such, the WTRU may determine to cap and / or limit the power in Type 2 ROs that coincide in time with the determined and / or indicated first SBFD time instances. In an embodiment, the NW may indicate to WTRU to limit or cap the UL power due to one or more interferences caused by the WTRU, for example due to maximum permissible exposure (MPE), cross-link interference (CLI), etc.

[0186] In an embodiment, the WTRU may determine, be configured, and / or indicated to limit the maximum UL transmission power (e.g., PCMAX), wherein, for example, the WTRU may set the PCMAX to the indicated, configured, and / or determined maximum UL power value. In another embodiment, the WTRU may determine, be configured, and / or indicated to suspend power ramping counter in (impacted and / or affected) first SBFD time instances. As such, the WTRU mayexclude and / or disable using power ramping counter and power ramping step in calculating the preamble received target power.

[0187] In details, about fall back to type 1 RO. In various embodiments, a WTRU that may be configured with RACH transmission and / or repetition in one or more Type 1 ROs may determine, be configured, and / or indicated to fall back to use Type 1 ROs for a RACH repetition procedure, in case the UL transmission power is lower than a determined, indicated, and / or configured threshold. In an embodiment, the WTRU may receive the configuration, indication, and / or one or more threshold values via SIB, RRC, MAC-CE< DCI, etc.

[0188] In an embodiment, the WTRU may determine, be configured, and / or indicated to transmit RACH occasions or repetitions in one or more Type 2 ROs. The WTRU may determine that the UL transmission power may be capped or lower than a determined, configured, and / or indicated threshold. In an embodiment, the WTRU may determine that the maximum UL power is limited and / or capped, wherein the capped and / or limited maximum uplink power is lower than a corresponding threshold. In another embodiment, the WTRU may determine that, due to suspended power ramping counter, the calculated preamble received target power is lower than a corresponding threshold. IN an embodiment, the WTRU may calculate a first preamble received target power based on a first ramping power counter. The WTRU may calculate a second preamble received target power based on suspending ramping power counter. The WTRU may determine the difference between the first and second calculated preamble received target power. The WTRU may determine to fallback to Type 1 RO on condition that the calculated difference is higher than a corresponding threshold.

[0189] In an embodiment, in case the WTRU determines to fallback to Type 1 RO, the WTRU may determine and / or select the set of random access resources corresponding to the configured and / or determined repetition times on Type 1 ROs. The WTRU may transmit the random access preamble using the selected set of random access resources in Type 1 RO, corresponding RA- RNTI (if available), PREAMBLE INDEX, and the first preamble received target power.

[0190] About selecting RA resources for RACH repetition in SFBD systems, in various embodiments, a WTRU may be configured with any of the following. SBFD-capable WTRU may be configured to perform RA repetition and to use Type 1 ROs (legacy TDD UP ROs) for PRACH transmission. The WTRU may determine that the configured set of random access resources in Type 1 RO is not associated with the selected repetition number that is applicable to the random access procedure. The WTRU may determines to use Type 2 RO or a combination of Type 1 and Type 2 ROs based on one or more conditions.

[0191] More particularly, the WTRU may receive configuration information indicating resources for a first type or set of ROs (e.g., Type 1 ROs) and a second type or set of ROs (e.g., Type 2 ROs), as described herein.

[0192] The WTRU may receive configuration of one or more threshold values, e.g., for determining a number of repetitions for PRACH transmission (e.g., for PRACH preamble or msgl transmission where a msgl transmission may be a PRACH preamble transmission). The WTRU may be configured with one or more sets of random access resources associated with the one or more repetition numbers, wherein the sets may be configured separately for Type 1 and Type 2 ROs. The WTRU may be configured with one or more sets of Random Access resources associated with the one or more repetition numbers, where the sets are configured based on combination of RA resources in both Type 1 and Type 2 ROs.

[0193] The WTRU may determine an RS, e.g., an SSB or a CSI-RS. For example, the WTRU may detect or may select an SSB (e.g., a best SSB) or may receive a PDCCH order to perform PRACH transmission. The PDCCH order may indicate the RS.

[0194] Based on at least one of the one or more thresholds (e.g., an RSRP or pathloss measurement that may be associated with or performed for the selected, detected, or indicated SSB or RS), the WTRU may determine to use repetition (e.g., of Nreps) for a PRACH transmission.

[0195] The WTRU may determine whether to use Type 1 ROs, Type 2 ROs, or a combination of type 1 and Type 2 ROs for the PRACH transmission and / or with repetitions, based on availability of random access resources.

[0196] In an embodiment, the WTRU may be configured (via SIB, RRC, MAC-CE, DCI, etc.) to mainly use Type 1 RO (legacy ROs) for PRACH transmission and (e.g., only) use Type 2 RO (SBFD ROs) if required / determined. The WTRU may determine if at least one set of random access resources is available in Type 1 ROs that is associated with the determined PRACH repetition (e.g., Nrep). WTRU may calculate a first PRACH power (e.g., PREAMBLE RECEIVED TARGET POWER), to be used for PRACH transmission in Type 1 ROs, wherein the WTRU may use the selected power ramping counter in calculating the first PRACH power.

[0197] The WTRU may determine to switch to PRACH transmission and / or repetition based on combined RO Types on condition that no sets of random access resources is available in Type 1 ROs that is associated with the determined PRACH repetition (e.g., Nrep).

[0198] The WTRU may calculate a second PRACH power, to be used for PRACH transmission in Type 2 ROs. In an embodiment, the second PRACH power in Type 2 ROs (e.g., in SBFDsymbols) may be lower than the first PRACH power, for example due to potential power ramping suspension, power capping due to CLI mitigation, etc.

[0199] The WTRU may be configured to switch to combined RA resources. The WTRU may determines to use combination of RA resources in both Type 1 and Type 2 ROs, on condition that RA resources for repetition are available and in case the difference between determined first and second PRACH power is lower than a corresponding threshold / range.

[0200] The WTRU may be configured to switch to Type 2 RO. The WTRU may determine to switch to Type 2 RO on condition that RA resources for repetition are available in Type 2 RO and on condition that the difference between determined first and second PRACH power is higher than the corresponding threshold / range.

[0201] The WTRU may transmit the Random Access Preamble using the selected PRACH occasion, corresponding RA-RNTI (if available), PREAMBLE INDEX, and PREAMBLE RECEIVED TARGET POWER. The selected PRACH occasions may be associated with the determined RS.

[0202] In details, about RACH configuration. A WTRU may determine, be configured, and / or indicated to receive and / or detect one or more SSBs. The WTRU may determine to perform random access procedure based on at least one of the detected and / or received SSBs. The WTRU may receive one or more configuration information and / or indications for performing the random access procedure. In an embodiment, the WTRU may receive the configuration information and indications via SIB, RRC, MAC-CE, DCI, and so forth. For example, the configuration information and / or indications may correspond to the transmission of Msg 1 or Msg A, if configured, as described herein.

[0203] The WTRU may be configured with one or more RACH occasion (RO) types. For example, the WTRU may be configured with a Type 1 RO, wherein the Type 1 ROs coincide with one or more TDD UL-only time instances. In another embodiment, the WTRU may be configured with a Type 2 RO, wherein the Type 2 ROs coincide with one or more SBFD time instances. The WTRU may be configured with PRACH transmission based on one or more of the configured RO types, as described herein. In an embodiment, the random access resources corresponding to different RO types may be mutually exclusive.

[0204] The WTRU may receive one or more configurations and / or indications on random access repetition. In an embodiment, the WTRU may determine the number of repetitions (e.g., X) based on one or more measured quality parameters and one or more thresholds. In an embodiment, theWTRU may measure DL pathloss RSRP, wherein the WTRU may determine that the measured RSRP is lower than a configured threshold for X-times repetition.

[0205] The WTRU may determine to perform preamble repetition for the determined X times. The WTRU may determine the random access resources based on the determined repetition (e.g., X), wherein the WTRU may determine the resources based on the association between the determined, selected, and / or configured SSB and configured ROs. In an embodiment, the WTRU may determine whether the selected BWP for the random access procedure is configured with the set(s) of random access resources with RO repetition number X, and whether the measured RSRP of the downlink pathloss reference is less than configured threshold, e.g., rsrp-threshold- repetitionNumX.

[0206] In an embodiment, the WTRU may determine the random access resources separately for different RO Types. For example, the WTRU may determine the set of random access resources corresponding to the configured and / or determined repetition times on Type 1 ROs; the WTRU may determine the set of random access resources corresponding to the configured and / or determined repetition times on Type 2 ROs, and so forth.

[0207] In details, about RA resources configured based on combination of RA Types. In various embodiments, a WTRU may determine, may be indicated, and / or configured to use one or more sets of random access resources, wherein the sets may be configured based on combination of resources in more than one RO type. For example, the WTRU may determine, be indicated, and / or configured to use the sets of random access resources that are associated with one or more determined, indicated, and / or configured RACH repetition numbers (e.g., X).

[0208] In an embodiment, the WTRU may be configured with a first set of RA resources, wherein the first of RA resources set may include Type 1 ROs. In another embodiment, the WTRU may be configured with a second set of RA resources, wherein the second set of RA resources may include Type 2 ROs. In another embodiment, the WTRU may be configured with a third set of RA resources, wherein the third set of RA resources may be configured based on the combination of RA resources in both Type 1 ROs and Type 2 ROs.

[0209] In an embodiment, a WTRU, that may be configured with RA resource sets based on combination of RO types, may determine, or may be configured, and / or indicated to perform PRACH based on a determined, configured, and / or indicated SSB. In an embodiment, the WTRU may determine that the first RA resource in time that is associated with the determined, configured, and / or indicated SSB may be based on a first RO type (e.g., Type 1 RO). In another embodiment, the WTRU may determine that the second, next and / or subsequent RA resource in time that isassociated with the determined, configured, and / or indicated SSB is based on a second RO type (e.g., Type 2 RO). As such, the WTRU may use the first RA resource for the first repetition occasion, the second RA resources for the second repetition occasion, and so forth.

[0210] In other words, a WTRU, that is configured to use at least a set of RA resources based on combination of RO types, may determine the RA resources based on the consecutive configured RA resources in time and the association of RA resources with determined, indicated, and / or configured SSB.

[0211] In details, about selecting RA resources for RACH repetition. In various embodiments, a WTRU may select ROs to be used for PRACH transmission between different RO types. In an embodiment, the WTRU may select the ROs to be used for PRACH repetition between ROs in Type 1 ROs (e g., legacy TDD UL RO slots), Type 2 ROs (e g., BFD RO slots), and / or ROs configured based on combination of both RO types. In an embodiment, the WTRU may receive indications and / or configurations to use Type 1 ROs as the main random access resources for PRACH transmission and / or repetition. The WTRU may be configured, enabled, allowed to use Type 2 ROs, or combination-based ROS in case required. In an embodiment, the WTRU may determine the power ramping counter and may calculate a first preamble receive target power, to be used for PRACH transmission in Type 1 ROs. In an embodiment, the WTRU may attempt to find and / or select at least a set of random access resources corresponding to the configured and / or determined repetition times on Type 1 ROs.

[0212] In various embodiments, a WTRU may determine that the selected BWP for the randomaccess procedure may not be configured with the set(s) of random-access resources with RO repetition number X in a first RO type (e.g. Type 1 RO). That is, the WTRU may determine that the configured set of random-access resources in the first RO type (e.g., Type 1 RO) may not be associated with the selected repetition number that may be applicable to the indicated, configured, and / or determined random-access procedure.

[0213] In various embodiments, a WTRU, that is configured with a prioritized first RO type and a non-prioritized second RO type, may determine to use the second RO type, on condition that the first configured RO type is not configured with set(s) of random-access resources associated with configured RO repetition number in the first RO type. In an embodiment, the WTRU, that is configured to use Type 1 ROs for PRACH transmission and / or repetition, may determine that the Type 1 ROs may not be configured with the set(s) of random-access resources with the configured, indicated, and / or determined RO repetition number. The WTRU may check if RA resources in another configured RO Type may be configured with the set(s) of random-access resources withthe configured, indicated, and / or determined RO repetition number. In an embodiment, the WTRU may check RA resources in Type 2 ROs and may determine if RA resources in Type 2 ROs may be configured with the set(s) of random-access resources with the configured, indicated, and / or determined RO repetition number. In another embodiment, the WTRU may check RA resources in ROs based on combination of Type 1 and Type 2 ROs and may determine if corresponding RA resources may be configured with the set(s) of random-access resources with the configured, indicated, and / or determined RO repetition number.

[0214] In an embodiment, if a second RO type is configured with the set(s) of random-access resources with the configured, indicated, and / or determined RO repetition number, the WTRU may calculate a second preamble received target power to be used for PRACH transmission in RA resources in the second RO type.

[0215] About condition to use RA resources based on combination of RO types. In an embodiment, the WTRU may determine to use RA resources based on combination of a first and second RO types (e.g., based on combination of Type 1 and Type 2 ROs), based on difference in calculated UL power in the first and second RO types. In an embodiment, in case the difference between determined first and second preamble received target power is lower than a corresponding configured, indicated, and / or determine threshold and / or range, the WTRU may determine to use RA resources based on combination of the first and second RO types.

[0216] About Condition to use RA resources based on Type 2 RO. In various embodiments, the WTRU may determine to use RA resources based on second RO types (e.g., Type 2 ROs), based on difference in calculated UL power in the first and second RO types. In an embodiment, in case the difference between determined first and second preamble received target power is higher than a corresponding configured, indicated, and / or determine threshold and / or range, the WTRU may determine to use RA resources based on the configured second RO type.

[0217] In an embodiment, the WTRU may determine and / or select the set of random access resources corresponding to the configured and / or determined repetition times on the selected RA resources. The WTRU may transmit the random access preamble using the selected set of random access resources, corresponding RA-RNTI (if available), PREAMBLE INDEX, and the calculated preamble received target power.

[0218] About determining validity of RACH occasions in SBFD slots, in various embodiments, a WTRU may be configured with any of the following. SBFD-capable WTRU may be configured with a new RACH configuration, or the WTRU may be configured to use the legacy configurationsfor ROs in time and frequency domain. The WTRU may determine whether the configured ROs are valid or not, based on one of more conditions.

[0219] An SBFD-capable WTRU may be configured with one or more RACH occasions, for example based on new configurations or legacy RACH configurations.

[0220] About valid ROs in time domain. The WTRU may determine that a PRACH occasion in a PRACH slot is invalid in time-domain on condition that it is within a DL-only symbol. The WTRU may determine whether the WTRU may use a PRACH occasion in a flexible and / or UL- only symbol, based on: (i) bitmap or mask indications received from gNB indicating valid / invalid ROs, out of the configured ROs in time domain. This may be WTRU-specific. (ii) UL power difference: In case the difference in SBFD and flexible / UL-only symbols is higher than a threshold, the WTRU may not use flexible / UL-only symbols. This is WTRU-specific. (iii) In case the WTRU cannot use a PRACH occasion, the WTRU may consider that PRACH occasion as invalid in time domain.

[0221] About valid ROs in frequency domain. In case of an RO is valid in time domain, the WTRU may determine whether the WTRU can use the RO in frequency domain, that is among the ROs (up to 8) that are FDM-ed, based on: (i) bitmap or mask indications received from gNB indicating valid / invalid ROs, out of the configured ROs in frequency domain. This may be WTRU- specific. (ii) WTRU determination. The WTRU may determine UL power for outer ROs. If the UL transmission power is higher than a determined / configured threshold, for example for ROs that are FDM-ed so that they are closer to the SBFD UL-subband boundaries compared for inner ROs, then the WTRU may considers the ROs as invalid in frequency domain. The WTRU may determine that FDM-ed ROs are out of the UL-subband boundary. The WTRU may determine that FDM-es ROs are out of the valid frequency domain for PRACH transmission boundary.

[0222] The WTRU may receive configuration information on how to handle the invalid ROs, where one of the following options may apply. Option 1, the WTRU does not consider the invalid ROs in associating the SSBs with ROs and the WTRU does not use them: as if the invalid ROs are non-existent. Option 2: The WTRU considers the invalid ROs in associating the SSBs with ROs but the WTRU does not use them: as if this WTRU is disabled / not allowed / rejected to use them.

[0223] The WTRU may determine the SSB and ROs association and may determine the ROs to use for PRACH transmission. The WTRU may transmit PRACH on the valid ROs.

[0224] In details, a WTRU may be configured with one or more configuration information regarding SBFD operation, where the configuration information may include time resources, where SBFD is applied, for example SBFD symbols, slots, subframes, time instances. Theconfiguration information may also include information on frequency resources, subbands, BWPs, CCs, etc., based on which the WTRU may be configured for UL, DL, guard bands, flexible bands, etc. In an embodiment, the WTRU may receive the SBFD configurations via one or more of SIB, RRC, MAC-CE, DCI, etc.

[0225] In various embodiments, the WTRU may be configured with one or more configuration information regarding one or more RACH occasions (RO), where the configuration information may include information on time and frequency resources, preambles, SSB associations with ROs, and so forth. In an embodiment, the WTRU may receive the configuration on RACH occasions via one or more of SIB, RRC, MAC-CE, DCI, etc.

[0226] In an embodiment, the WTRU may receive one or more configuration information on one or more ROs based on (pre)configured configurations, for example based on (legacy) RACH configurations in TDD, FDD, etc. In another embodiment, the WTRU may receive one or more new and / or separate configuration information to be used in time instances, for example other than legacy TDD or FDD occasions, that is for example, in SBFD occasions.

[0227] In various embodiments, a WTRU may determine whether one or more of the configured ROs are valid or invalid for PRACH transmission based on one or more conditions. In an embodiment, the WTRU may receive the RACH configurations in one or more group-common, cell-common, or WTRU-specific configuration information and / or indications. In an embodiment, the WTRU may determine, be configured, and or indicated with valid or invalid ROs out of the configured ROs, based on one or more WTRU-specific, group-based, cell-based, etc. indications and / or configuration information. In an embodiment, the WTRU may perform PRACH transmission on the ROs that are configured, indicated, and / or determined to be valid. Alternatively, in another embodiment, the WTRU may disable, eliminate, exclude, and / or skip PRACH transmission in the ROs that are configured, indicated, and / or determined to be invalid. One of more of the conditions are provided as follow.

[0228] About valid ROs in time domain, in various embodiments, a WTRU, that is configured with TDD and / or SBFD configurations, may determine a configured and / or indicated RACH occasion as invalid if the RO is within a DL-only time unit. The WTRU may consider the configured and / or indicated RO as valid on condition that the RO is within the UL subbands in a time unit. For example, if a DL time unit is configured with one or more UL subbands, as in SBFD configurations, and of the configured RO is configured within the UL subbands, the WTRU may consider the RO as valid. In an example, a time unit may be a symbol, slot, subframe, frame, etc.

[0229] Referring to FIG. 4, a set of configured RO slots (ROS) including 8 consecutive RO slots (gray slots) is shown. The WTRU may determine the RO slots that coincide in time with DL-only slots as invalid. As non-limited example, ROS1 and ROS2 in FIG. 4 may be considered as invalid for PRACH transmission. The WTRU may consider the ROs that do not coincide in time with UL- only slots as potentially valid ROs; however, the WTRU may determine or may be indicated otherwise, as provided as follow.

[0230] About Invalid ROs’ indication (e.g., from a gNB), in various embodiments, a WTRU may receive one or more configuration information and / or indications indicating that one or more ROs out of the configured ROs may be invalid in time-domain. For example, the WTRU may receive the indications from a gNB. In an embodiment, the WTRU may be configured with one or more ROs (e.g., via SIB, RRC, MAC-CE, DCI, etc.) in one or more time instances, wherein the WTRU may receive an indication to consider the ROs that coincide with at least one of the configured time instances are invalid (e.g., via SIB, RRC, MAC-CE, DCI, etc.). In an embodiment, the indication may be WTRU-specific. For example, the NW may determine that one or more configured RO time instances cannot be used for PRACH transmission due to traffic restrictions, scheduling restrictions, power restrictions, CLI mitigation, etc.

[0231] In an embodiment, the WTRU may receive the indication (e.g., from a gNB) via bitmap indications. For example, the WTRU may receive a bitmap corresponding to the configured ROs in time-domain, where each bit in the bitmap may associate with an RO’s time duration, one or more symbols, one or more slots, etc. The WTRU may be configured with the time duration that each bit in the bitmap present and / or is associated with. As such, a first value (e.g. value zero) in the bitmap may indicate that the associated time instances are invalid for PRACH transmission. In other words, the WTRU may skip, disable, eliminate, and / or exclude ROs that coincide with the time instances that are associated with the indicated first value in the configured bitmap. Alternatively, a second value (e.g. value one) in the bitmap may indicate that the associated time instances are valid for PRACH transmission, and that the WTRU may use ROs that coincide with the corresponding time instances.

[0232] In another embodiment, the WTRU may receive the indication (e.g., from a gNB) via mask indications, where the mask indication may indicate the time instances and / or ROs that are not valid for PRACH transmission, in time domain.

[0233] About WTRU-oriented invalid ROs’ determination, in various embodiments, a WTRU may receive and / or be (pre)configured with one or more conditions, thresholds, etc., based on which the WTRU may determine one or more ROs out of the configured ROs to be invalid in time-domain. For example, the WTRU may receive the configuration information, threshold, etc. via SIB, RRC, MAC-CE, DCI, etc. In an embodiment, the WTRU may determine, measure, identify, and / or calculate one or more parameters in time instances that are associated to at least a configured RO. For example, the WTRU may be configured with a first RO that may be associated with a first time instance that may coincide in time with an UL-only time instance, that is for example the Type 1 RO. In another embodiment, the WTRU may be configured with a second RO that may be associated with a second time instance that may coincide in time with an SBFD time instance, that is for example the Type 2 RO.

[0234] The WTRU may compare the parameters that correspond to the first or second ROs with one or more determined, indicated, and / or configured threshold, limits, ranges, etc. In an embodiment, the WTRU may determine that the corresponding parameters are within the valid configured threshold, limit, range, etc., wherein the WTRU may consider the RO that is associated with the corresponding time instance as valid RO. Otherwise, in another embodiment, the WTRU may determine that the corresponding parameters are not within the valid configured threshold, limit, range, etc., wherein the WTRU may consider the RO that is associated with the corresponding time instance as invalid RO.

[0235] About determination based on UL transmission power, in various embodiments, a WTRU, that is configured with RO repetition in a first, second, and / or third time instances, may determine the corresponding ROs as valid in time-domain, on condition that the UL transmission power in all time instances are within an acceptable range. In an embodiment, the WTRU may measure, determine, and / or calculate the UL transmission power for each of the ROs in a configured RO repetition scenario. The WTRU may calculate the difference between UL transmission powers in different ROs in the configured RO repetition scenario. In case the UL transmission power difference between at least a configured first RO with a second configured RO is higher than a threshold, or out of a range, the WTRU may skip using the first RO and consider the first and / or the second RO as invalid. In an embodiment, the WTRU may determine, be configured, and / or indicated with the UL power difference threshold, limits, ranges, etc. via SIB, RRC, MAC-CE, DCI, etc.

[0236] In an example, the WTRU may determine, be configured, and / or indicated to consider one of the configured ROs as the reference for calculating the power difference. In an embodiment, the WTRU may be configured to consider the UL transmission power in ROs that are associated with type 1 ROs as reference. In another embodiment, the WTRU may be configured to consider the UL transmission power in at least an RO that is associated with type 2 ROs as reference. TheWTRU may receive the configuration on the reference RO type in the form of priority levels, wherein the WTRU may be configured and / or indicated to consider the type 1 ROs as higher priority compared to type 2 ROs, or vice-versa, the WTRU may be configured and / or indicated to consider the type 2 ROs as higher priority compared to type 1 ROs. As such, the WTRU may consider the reference power based on the UL transmission power of the RO type that is configured with higher priority. The WTRU may receive the configuration on the reference RO type and / or priority levels between different RO types via SIB, RRC, MAC-CE, DCI, etc.

[0237] In various embodiments, the WTRU may determine, be indicated, and / or configured with RO repetition in a first, second, and third time instances. In an embodiment, the WTRU may determine, be indicated, and / or configured with a first UL power parameter for one or more ROs in a first time instance. In an embodiment, the UL power parameter may include one or more of UL transmission power, maximum UL power, Pcmax, etc. In an embodiment, the first RO may be a type 2 RO, that is the corresponding time instance may be in an SBFD time instance, symbol, slot, etc. The WTRU may determine, be indicated, and / or configured with a second and third UL power parameter for one or more ROs in a second or third time instances, wherein the second and third time instances may be of type 2 RO or type 1 RO (e.g., NR TDD UL-only symbols), respectively. The WTRU may compare the first, second, and / or third UL power parameters. The WTRU may measure and / or calculate a first power difference value based on the difference between the first and second power parameters. The WTRU may measure and / or calculate a second power difference value based on the difference between the first and third power parameters. The WTRU may measure and / or calculate a third power difference value based on the difference between the second and third power parameters.

[0238] In an embodiment, the WTRU may determine, be indicated, and / or configured with one or more thresholds on UL power parameters. For example, a first threshold may correspond to UL power differences that correspond to type 2 ROs, and a second threshold may correspond to UL power differences between type 1 and type 2 ROs.

[0239] In an embodiment, the WTRU may determine that a first RO is valid in time-domain, if the UL power difference for the time instance associated to the first RO is within the configured first range, limit, and / or threshold. In an embodiment, the WTRU may determine that the calculated first and second power difference values are lower than the first and second configured thresholds.

[0240] In another embodiment, the WTRU may determine that the UL power difference between the second and third ROs are not within the configured second range, limit, and / or threshold. Inan embodiment, the WTRU may determine that the calculated power difference value between the first and second ROs (with type 2 ROs) is lower than the first threshold; however, the calculated power difference value between the second RO (type 2 RO) and third RO (type 1 RO) is higher than the second configured threshold. In case the power difference is higher than a corresponding threshold, the WTRU may be configured to prioritize at least one of the RO types. The WTRU may receive the configuration on the RO type in the form of priority levels, wherein the WTRU may be configured and / or indicated to consider the type 1 ROs as higher priority compared to type 2 ROs, or vice-versa, the WTRU may be configured and / or indicated to consider the type 2 ROs as higher priority compared to type 1 ROs.

[0241] Referring to FIG. 4, in an embodiment, a WTRU may be configured with RO repetition in ROs that coincide in RO Slot #5 (ROS5) and ROS8. The ROs that coincide with ROS5 may be considered as type 2 ROs (e.g., in SBFD symbols) and ROs that coincide with ROS8 may be considered as type 1 ROs (e.g., in UL-only ROs). For example, the UL transmission in time instances that coincide in time with ROS5 may be configured with limited, lowered, reduced, capped UL transmission power, e.g., due to CLI mitigation. The WTRU may compare and may calculate the UL power difference between ROs in ROS5 and ROs in ROS8. The WTRU may determine that the UL power difference is higher than the second configured threshold. In this case, if the WTRU may be configured to prioritize RO transmission in type 1 ROs, the WTRU may consider ROs in ROS5 as invalid and ROs in ROS8 as valid. Otherwise, if the WTRU is configured to prioritize RO transmission in type 2 ROs, the WTRU may consider ROs in ROS5 as valid and ROs in ROS8 as invalid.

[0242] It is worth to mention that considering the UL transmission power in time instances associated with ROs, may be due to NW (e.g., gNB) requiring the RO repetitions to be within a same received power range. This may be to avoid phase error in consecutive received repeated ROs. The power differences may happen as the WTRUs may determine, be configured, and / or indicated to cap, reduce, or limit UL transmission power, for example in SBFD symbols due to CLI mitigation requirements.

[0243] About valid ROs in frequency-domain, in various embodiments, a WTRU may determine that an RO that is determined, indicated, and / or configured as valid in time-domain may be valid or invalid in frequency domain. In an embodiment, the WTRU may be configured with one or more PRACH transmission occasions and / or RACH occasions, FDM-ed in a time instance. For example, the FDM-ed ROs may be in a time instance that coincides in type with a Type 2 RO, that is for example an SBFD time instance. In an embodiment, the WTRU may be configured with upto eight RACH occasions (e.g., based on msgl-FDM) that may be FDM-ed in an SBFD time instance. In an embodiment, a time instance may be one or more symbols, slots, subframes, frames, etc.

[0244] In various embodiments, a network may determine and may indicate to the WTRU that one or more configured ROs in frequency domain cannot be used for PRACH transmission due to traffic restrictions, scheduling restrictions, power restrictions, CLI mitigation, etc. In an embodiment, in an UL subband in an SBFD symbols, the ROs that are closer to the middle of the UL subband may potentially cause lower CLI (e.g., inter-subband CLI, WTRU-to-WTRU CLI, etc.); however, the ROs that are closer to the edges of the UL subband may potentially cause higher CLI.

[0245] The WTRU may determine or be indicated that a determined, configured, and / or indicated RO may be valid or invalid, as follow.

[0246] About invalid ROs’ indication, in various embodiments, a WTRU may receive one or more configuration information and / or indications indicating that one or more ROs out of the configured ROs may be invalid in frequency-domain. In an embodiment, the WTRU may receive the indications from a gNB. In an embodiment, the WTRU may be configured with one or more FDM-ed ROs, wherein the WTRU may receive an indication to consider at least one of the ROs as invalid (e.g., via SIB, RRC, MAC-CE, DCI, etc.). In an embodiment, the indication may be WTRU-specific.

[0247] About bitmap indication, in various embodiments, the WTRU may receive the indication (e.g., from a gNB) via bitmap indications. For example, the WTRU may receive a bitmap corresponding to the configured FDM-ed ROs, where each bit in the bitmap may associate with an RO in frequency domain. As such, a first value (e.g. value zero) in the bitmap may indicate that the associated RO may be invalid in frequency domain for PRACH transmission. In other words, the WTRU may skip, disable, eliminate, and / or exclude the ROs in frequency-domain that are associated with the indicated first value in the configured bitmap. Alternatively, a second value (e.g. value one) in the bitmap may indicate that the associated ROs are valid for PRACH transmission, and that the WTRU may use ROs.

[0248] About invalid / masked frequencies, in various embodiments, a WTRU may receive one or more configuration information and / or indications (e.g., from a gNB) including one or more mask indications, where the mask indication may indicate the frequency ranges that are not valid for PRACH transmission, in frequency domain. That is, the WTRU may receive a frequency range, based on one or more subbands, BWPs, RBs, REs, etc., which are invalid for PRACHtransmission, and that the WTRU may not use for RACH occasions. In an embodiment, the WTRU may receive a starting frequency, duration, and / or end frequency for the indication and / or configuration of the configured invalid and / or masked frequency range, subbands, RBs, REs, etc. In an embodiment, the WTRU, that may be configured with one or more FDM-ed ROs, may check and determine if the configured ROs overlap with the configured invalid and / or masked frequency range. In an embodiment, the WTRU may determine that at least one RO partially or fully overlaps with the configured invalid and / or masked frequency range, wherein the WTRU may not use that RO for PRACH transmission. For example, the WTRU may consider the ROs that overlap with configured invalid and / or masked frequency range as invalid ROs.

[0249] About WTRU-oriented invalid ROs’ determination, in various embodiments, a WTRU may receive and / or be (pre)configured with one or more conditions, thresholds, etc., based on which the WTRU may determine one or more ROs out of the configured ROs to be invalid in frequency-domain. In an embodiment, the WTRU may receive the configuration information, threshold, etc. via SIB, RRC, MAC-CE, DCI, etc., for example from a gNB. In an embodiment, one or more thresholds may be configured for one or more different frequency ranges in the configured UL subband. In an embodiment, the WTRU may be configured with different thresholds on the calculated preamble received target power, based on the different frequency ranges. In an embodiment, the WTRU may be configured with a first threshold on preamble received target power for a first frequency range (e.g., frequency subbands, RBs, REs, etc. that are closer to the middle of UL subband); the WTRU may be configured with a second threshold on preamble received target power for a second frequency range (e.g., frequency subbands, RBs, REs, etc. that are closer to the edges of UL subband), and so forth.

[0250] In an embodiment, the WTRU may determine, measure, identify, and / or calculate one or more parameters that are associated to configured ROs, in frequency domain. For example, the WTRU may calculate preamble received target power for one or more ROs. The WTRU may compare the measured preamble received target power with one or more thresholds. In an embodiment, the WTRU may compare the calculated preamble received target power with the first threshold, if the corresponding RO is located in the first frequency range (e.g., frequency subbands, RBs, REs, etc. that are closer to the middle of UL subband); the WTRU may compare the calculated preamble received target power with the second threshold, if the corresponding RO is located in the second frequency range (e.g., frequency subbands, RBs, REs, etc. that are closer to the edges of UL subband), and so forth. The WTRU may determine that the measured parameters are within the valid configured threshold, limit, range, etc., wherein the WTRU may consider theRO that is associated with the corresponding frequency ranges as valid RO. In an embodiment, the WTRU may determine that the calculated preamble received target power for an RO in the first frequency range is lower than the first threshold. In another embodiment, the WTRU may determine that the measured parameters are not within the valid configured threshold, limit, range, etc., wherein the WTRU may consider that RO as invalid RO. For example, the WTRU may determine that the calculated preamble received target power for an RO in the second frequency range is higher than the second threshold.

[0251] About out of UL subband range, in various embodiments, the WTRU may receive one or more configuration information and / or indications (e.g., from a gNB) regarding the UL subband and / or frequency ranges in an SBFD time instance. The WTRU may be configured and / or indicated with the UL subband in an SBFD time instance, based on one or more subbands, BWPs, RBs, REs, etc. The WTRU may be configured with guard bands in the SBFD time instance. In another embodiment, the WTRU may be configured and / or indicated with the subbands in addition to guard bands in an SBFD time instance, based on one or more subbands, BWPs, RBs, REs, etc., wherein the WTRU may determine the UL subbands accordingly. For example, the WTRU may determine or receive a starting frequency, duration, and / or end frequency for the indication and / or configuration of the configured UL subband.

[0252] In an embodiment, the WTRU, that may be configured with one or more FDM-ed ROs, may check and determine whether the configured ROs completely overlap with the configured UL subbands. In other words, the WTRU may check and determine if at least one of the configured ROs fall out of the configured UL subbands, that is the WTRU may check and may determine if the configured ROs partially of fully overlap with guard bands or DL subband. In an embodiment, the WTRU may determine that at least one RO partially or fully overlaps with the configured guard bands and / or DL subband, wherein the WTRU may not use that RO for PRACH transmission. For example, the WTRU may consider the ROs that overlap with configured guard bands and / or DL subbands as invalid ROs.

[0253] About WTRU behavior in case of invalid RACH occasions, in various embodiments, a WTRU may receive one or more configuration information and / or indications on the mode of operation based on indicated, configured, and / or determined invalid ROs. In an embodiment, the WTRU may receive the indications and / or configuration from a gNB, via SIB, RRC, MAC-CE, DCI, etc. In an embodiment, the WTRU may receive a first indication to use a first mode of operation, a second indication to use a second mode of operation, and so forth.

[0254] About the first mode of operation, in various embodiments, the first mode of operation may be based on considering the indicated ROs as non-existent. For example, the WTRU may receive indication to use a first mode of operation for one or more first invalid ROs, wherein the WTRU may consider them as ROs that were not configured and / or non-existence. In an embodiment, the WTRU may receive the first invalid ROs via a cell-common indication, wherein the NW has determined to invalidate one or more first ROs for the entire cell and all WTRUs.

[0255] In an embodiment, the WTRU may not consider the first invalid ROs in counting the ROs. The WTRU may not consider the first invalid ROs in determining set(s) of random access resources for PRACH transmission and / or repetition. The WTRU may not consider the first invalid ROs in determining the association of SSBs and ROs. The WTRU may not consider the first invalid ROs in counting the number of SSBs mapped to each RO (e.g., configured via ssb- perRACH-OccasionAndCB-PreamblesPerSSB'). The WTRU may not consider the first invalid ROs in counting the number contention-based random access preambles mapped to each SSB (e.g., configured via ssb-perRACH-OccasionAndCB-PreamblesPerSSB).

[0256] About the second mode of operation, in various embodiments, the second mode of operation may be based on considering the indicated ROs as configured ROs, which are disabled and not allowed to the WTRU to use them. In an embodiment, the WTRU may receive indication to use a second mode of operation for one or more second invalid ROs, wherein the WTRU may consider them as ROs that were configured but the WTRU may be disabled or not allowed to use them. For example, the WTRU may receive the second invalid ROs via a group-common or WTRU-specific indication, wherein the network has determined to invalidate one or more second ROs to be used for one or more WTRUs.

[0257] In various embodiments, the WTRU may consider the second invalid ROs in counting the ROs. The WTRU may consider the second invalid ROs in determining set(s) of random access resources for PRACH transmission and / or repetition. The WTRU may consider the second invalid ROs in determining the association of SSBs and ROs. The WTRU may consider the second invalid ROs in counting the number of SSBs mapped to each RO, the WTRU may consider the second invalid ROs in counting the number contention-based random access preambles mapped to each SSB. In an embodiment, the WTRU may not use the second invalid ROs for RACH occasions and PRACH transmission.

[0258] About validity indication for invalid ROs, in various embodiments, the WTRU may receive one or more indications and / or configurations to indicate that one or more configured first or second invalid ROs may be valid and that the WTRU may use them for PRACH transmissionand / or RACH occasions. In an embodiment, the WTRU may receive the indications and / or configuration on valid ROs from a gNB, via SIB, RRC, MAC-CE, DCI, etc.

[0259] Referring to FIG. 5, in an embodiment, a method 500 implemented in a WTRU, may comprise a step of receiving 510 a first message comprising first configuration information indicating resources for a first type of random access channel occasions (ROs) and for a second type of ROs. The method 500 may further comprise a step of determining 520 whether to use the first type of ROs or the second type of ROs for a physical random access channel (PRACH) transmission based on a determined PRACH power; and a step of transmitting 530 the PRACH transmission in an RO of the determined ROs using the PRACH power.

[0260] On condition of not receiving a random access response following the PRACH transmission in the determined RO, the method 500 may comprise a step of transmitting another PRACH transmission in the not determined RO. On condition of not receiving a random access response following the PRACH transmission in the determined RO, the method 500 may comprise a step of ramping the PRACH power.

[0261] The method 500 may comprise a step of determining the PRACH power for the PRACH transmission; and a step of transmitting in the first type of ROs or in the second type of RO based whether the determined PRACH power exceeds, is equal, or is below a power threshold value.

[0262] More particularly, the method 500 may comprise a step of comprising transmitting in the first type of RO on condition that the determined PRACH power exceeds or is equal to the power threshold value, and / or a step of transmitting in the second type of RO on condition that the determined PRACH power is below the power threshold value. The power threshold value may be a determined maximum transmission power for the PRACH transmission.

[0263] The first type of ROs may be configured in time division duplexing uplink slots and wherein the second type of ROs is configured in subband non-overlapping full duplex (SBFD) slots. The method 500 may comprise a step of determining a SBFD maximum transmission power associated with the second type of ROs; and a step of transmitting the PRACH transmission in the second type of ROs on condition that the PRACH power is below the SBFD maximum transmission power.

[0264] The method 500 may comprise a step of receiving a second message comprising second configuration information indicating one or more repetition threshold values. The method 500 may comprise a step of determining a repetition threshold value based on path loss measurement and determining using repetition of PRACH transmission based on the determined repetition thresholdvalue. The method 500 may comprise a step of transmitting a set of RACH transmissions in the RO of the determined ROs using the PRACH power.

[0265] The method 500 may further comprise a step of determining whether to use the first type of ROs or the second type of ROs for each PRACH transmission of the set of PRACH transmissions based on a PRACH power associated with each PRACH transmission of the set of PRACH transmissions; and on condition that a determined type of ROs of a first PRACH transmission of the set of PRACH transmissions differs from a determined type of ROs of a second PRACH transmission of the set of PRACH transmissions, the method 500 may further comprise a step of transmitting the first and the second PRACH transmission respectively in the determined type of ROs of the first and the second PRACH transmission; and stopping PRACH transmission of the set of PRACH transmissions.

[0266] Referring to FIG. 6, in another embodiment, a method 600 implemented in a WTRU, may comprise a step of receiving 610 a first message comprising first configuration information indicating resources for a first type of random access channel occasions (ROs) and for a second type of ROs. The method 600 may further comprise a step of determining 620 to use the second type of ROs for a physical random access channel (PRACH) transmission based on a determined PRACH power. The method 600 may further comprise a step of transmitting 630 the PRACH transmission in the second type of ROs using the PRACH power. The method 600 may further comprise a step of ramping 640 the PRACH power used for transmitting the PRACH transmission in the second type of ROs. On condition that the PRACH power for a PRACH transmission is capped, the method 600 may further comprise a step of switching 650 from the second type of ROs to the first type of ROs for PRACH transmission; and a step of transmitting 660 the PRACH transmission in the first type of ROs using the PRACH power. The WTRU may be a SBFD capable WTRU.

[0267] More particularly, on condition of not receiving a random access response following the PRACH transmission in the second type of ROs, the method 600 may comprise a step of ramping the PRACH power. The method 600 may further comprise a step of determining the PRACH power for the PRACH transmission; and may further comprise a step of transmitting in the second type of RO on condition that the determined PRACH power is below a power threshold value. The power threshold value may be a determined maximum transmission power for the PRACH transmission. The first type of ROs may be configured in a non subband non-overlapping full duplex, SBFD, slots (e.g., time division duplexing uplink slots) and the second type of ROs may be configured in subband non-overlapping full duplex, SBFD, slots.

[0268] The method 600 may further comprise a step of determining a SBFD maximum transmission power associated with the second type of ROs; and a step of transmitting the PRACH transmission in the second type of ROs on condition that the PRACH power is below the SBFD maximum transmission power. The method 600 may further comprise a step of determining that the PRACH transmission is capped due to capped uplink power for a WTRU-to-WTRU crosslayer interference (CLI) mitigation.

[0269] The method 600 may further comprise a step of receiving a second message comprising second configuration information indicating one or more repetition threshold values. The method 600 may further comprise a step of determining a repetition threshold value based on path loss measurement; and a step of determining using repetition of PRACH transmission based on the determined repetition threshold value. On condition that a determined type of ROs of a first PRACH transmission of the set of PRACH transmissions differs from a determined type of ROs of a second PRACH transmission of the set of PRACH transmissions, the method 600 may further comprise a step of transmitting the first and the second PRACH transmission respectively in the determined type of ROs of the first and the second PRACH transmission; and stopping PRACH transmission of the set of PRACH transmissions.

[0270] Referring to FIG. 7, in an embodiment, a method 700 implemented in a wireless transmit / receive unit (WTRU) may comprise a step wherein the WTRU may receive 710 a message comprising configuration information indicating resources for a first type of random access channel occasions, ROs, and for a second type of ROs, wherein the second type of ROs include an associated physical random access channel (PRACH) power threshold. The WTRU may be a subband non-overlapping full duplex capable WTRU. The method 700 may comprise a step wherein the WTRU may determine 720 a PRACH power level for a PRACH transmission. The method 700 may comprise a step wherein the WTRU may select 730 a type of ROs among the first type of ROs and the second type of ROs for the PRACH transmission based on a comparison between the determined PRACH power level and the PRACH power threshold, and a step wherein the WTRU may transmit 740 the PRACH transmission in the selected type of ROs using the determined PRACH power level. The PRACH transmission may be a PRACH preamble transmission that may include a preamble format.

[0271] The first type of ROs may be configured in time division duplexed uplink slots and wherein the second type of ROs is configured in subband non-overlapping full duplex slots. The method 700 may comprise a step wherein the WTRU may determine a subband non-overlapping full duplex maximum transmission power associated with the second type of ROs; and a stepwherein the WTRU may transmit the PRACH transmission in the second type of ROs on condition that the PRACH power level is below the subband non-overlapping full duplex maximum transmission power.

[0272] The method 700 may comprise a step wherein the WTRU may select the second type of ROs on condition that the determined PRACH power level is lower than the PRACH power threshold. On condition of not receiving a random access response following the PRACH transmission in the second type of ROs, the method may comprise a step wherein the WTRU may ramp the PRACH power level. A level of the PRACH power threshold may be a determined maximum transmission power level for the PRACH transmission.

[0273] The method 700, may comprise a step wherein the WTRU may select the first type of ROs on condition that the determined PRACH power level is higher than the PRACH power threshold. The method 700, may comprise a step wherein the WTRU may determine that the PRACH transmission is capped due to capped uplink power for a WTRU-to-WTRU cross-layer interference (CLI) mitigation.

[0274] Conclusion

[0275] 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.

[0276] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared 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.

[0277] 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.

[0278] 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 WTRU, UE, terminal, base station, RNC, or any host computer.

[0279] 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 should not 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.

[0280] 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."

[0281] 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.

[0282] 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.

[0283] 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.

[0284] 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 systems and / or other technologies described herein may be effected (e.g., hardware, software, and / orfirmware), 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.

[0285] 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.).

[0286] 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 ofthe devices and / or processes described herein may be integrated into a data processing system via a 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.

[0287] 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.

[0288] 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.

[0289] 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 interpretedas "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 toinclude 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".

[0290] 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.

[0291] 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.

[0292] 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

CLAIMS1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving a message comprising configuration information indicating resources for a first type of random access channel occasions, ROs, and for a second type of ROs, wherein the second type of ROs include an associated physical random access channel (PRACH) power threshold; determining a PRACH power level for a PRACH transmission; selecting a type of ROs among the first type of ROs and the second type of ROs for the PRACH transmission based on a comparison between the determined PRACH power level and the PRACH power threshold; and transmitting the PRACH transmission in the selected type of ROs using the determined PRACH power level.

2. The method of claim 1, wherein the first type of ROs is configured in time division duplexed uplink slots and wherein the second type of ROs is configured in subband nonoverlapping full duplex slots.

3. The method of claim 2, comprising: determining a subband non-overlapping full duplex maximum transmission power associated with the second type of ROs; and transmitting the PRACH transmission in the second type of ROs on condition that the PRACH power level is below the subband non-overlapping full duplex maximum transmission power.

4. The method of any of claim 1 to claim 3, comprising selecting the second type of ROs on condition that the determined PRACH power level is lower than the PRACH power threshold.

5. The method of claim 4 comprising: on condition of not receiving a random access response following the PRACH transmission in the second type of ROs, ramping the PRACH power level.

6. The method of any of claim 4 and claim 5, wherein a level of the PRACH power threshold is a determined maximum transmission power level for the PRACH transmission.

7. The method of any of claim 1 to claim 6, comprising selecting the first type of ROs, on condition that the determined PRACH power level is higher than the PRACH power threshold.

8. The method of any of claim 1 to claim 7, comprising determining that the PRACH transmission is capped due to capped uplink power for a WTRU-to-WTRU cross-layer interference (CLI) mitigation.

9. The method of any of claims 1 to 8, wherein the WTRU is a subband non-overlapping full duplex capable WTRU.

10. The method of any of claims 1 to 9, wherein the PRACH transmission is a PRACH preamble transmission.

11. A wireless transmit / receive unit, WTRU, comprising a processor, a transceiver unit and a storage unit, and configured to: receive a message comprising configuration information indicating resources for a first type of random access channel occasions, ROs, and for a second type of ROs, wherein the second type of ROs include an associated physical random access channel (PRACH) power threshold; determine a PRACH power level for a PRACH transmission; select a type of ROs among the first type of ROs and the second type of ROs for the PRACH transmission based on a comparison between the determined PRACH power level and the PRACH power threshold; and transmit the PRACH transmission in the selected type of ROs using the determined PRACH power level.

12. The WTRU of claim 11, wherein the first type of ROs is configured in time division duplexed uplink slots and wherein the second type of ROs is configured in subband nonoverlapping full duplex slots.

13. The WTRU of claim 12, configured to:determine a subband non-overlapping full duplex maximum transmission power associated with the second type of ROs; and transmit the PRACH transmission in the second type of ROs on condition that the PRACH power level is below the subband non-overlapping full duplex maximum transmission power.

14. The WTRU of any of claim 11 to claim 13, configured to select the second type of ROs on condition that the determined PRACH power level is lower than the PRACH power threshold.

15. The WTRU of claim 14 configured to ramp the PRACH power level on condition of not receiving a random access response following the PRACH transmission in the second type of ROs.

16. The WTRU of any of claim 14 and claim 15, wherein a level of the PRACH power threshold is a determined maximum transmission power level for the PRACH transmission.

17. The WTRU of any of claim 11 to claim 16, configured to select the first type of ROs on condition that the determined PRACH power level is higher than the PRACH power threshold.

18. The WTRU of any of claim 11 to claim 17, configured to determine that the PRACH transmission is capped due to capped uplink power for a WTRU-to-WTRU cross-layer interference (CLI) mitigation.

19. The WTRU of any of claim 11 to claim 18, wherein the WTRU is a subband nonoverlapping full duplex capable WTRU.

20. The WTRU of any of claims 11 to 19, wherein the PRACH transmission is a PRACH preamble transmission.