WO2024211545A1 - Requête de planification pour srs - Google Patents
Requête de planification pour srs Download PDFInfo
- Publication number
- WO2024211545A1 WO2024211545A1 PCT/US2024/023038 US2024023038W WO2024211545A1 WO 2024211545 A1 WO2024211545 A1 WO 2024211545A1 US 2024023038 W US2024023038 W US 2024023038W WO 2024211545 A1 WO2024211545 A1 WO 2024211545A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- wtru
- srsp
- network
- transmit
- prs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
- H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
Definitions
- DL positioning method may refer to any positioning method that uses DL resources, such as positioning reference signal (PRS), for positioning.
- PRS positioning reference signal
- a wireless transmit/receive unit (WTRU) may receive multiple reference signals from transmission point(s) (TP(s)) and may measure DL reference signal time difference (RSTD) and/or reference signal received power (RSRP).
- RSTD DL reference signal time difference
- RSRP reference signal received power
- Examples of DL positioning methods include downlink-angle of departure (DL-AoD) and/or downlink-time difference of arrival (DL-TDOA) positioning.
- UL positioning method may refer to any positioning method that uses uplink reference signals, such as sounding reference signal (SRS), for positioning.
- SRS sounding reference signal
- the WTRU may transmit SRS to multiple reception points (RPs), and the RPs may measure the UL relative time of arrival (RTOA) and/or RSRP.
- RPs reception points
- RTOA UL relative time of arrival
- RSRP RSRP
- Examples of UL positioning methods include uplink-time difference of arrival (UL-TDOA) and/or uplink-angle of arrival (UL-AoA) positioning.
- DL & UL positioning method may refer to any positioning method that uses both uplink and downlink reference signals for positioning.
- a WTRU may transmit SRS to multiple transmission-reception points (TRPs), and a gNB may measure Rx-Tx time difference, which may be calculated based on the time of arrival of DL RS (e.g., PRS).
- the gNB may measure RSRP for the received SRS.
- the WTRU may measure the Rx-Tx time difference for PRS transmitted from multiple TRPs.
- the WTRU may measure the RSRP for the received PRS.
- the Rx-TX difference may be used to compute round trip time.
- WTRU Rx - Tx time difference may refer to the difference between arrival time of the reference signal transmitted by the TRP and transmission time of the reference signal transmitted from the WTRU.
- An example of a DL & UL positioning method is multi-round trip time (multi-RTT) positioning.
- a wireless transmit/receive unit may receive a request from an LMF to receive PRS and transmit SRS at a specified timing.
- the WTRU may send a request for a prioritization window to a gNB, which may encompass both DL reception and UL transmission timing.
- the WTRU may receive a request to transmit SRS at a specified timing from the LMF.
- the WTRU may send a request to the gNB.
- the WTRU may receive configurations for more than one SRSp resource.
- the WTRU may receive an activation command, activating one of the SRSp resources.
- the WTRU may determine to send a request to the network for simultaneous PRS reception session (e.g., between the WTRU and PRU).
- the WTRU may receive a session index from the network.
- the WTRU may make measurements on configured PRSs and may send a request for measurements (e.g., from the PRU) associated with the PRS resource index and session index.
- the WTRU may receive the measurements from the network.
- the WTRU may receive a configuration of Ts (SRSp transmission timing) from a network (e.g., from a first network entity such as an LMF).
- a configuration of Ts may be referred to as a "time value.”
- the WTRU may receive an SRSp configuration from the network (e.g., from the first network node or a second network node such as a gNB), where the SRSp configuration may include periodic transmission parameters (e.g., periodicity, repetition factor).
- the WTRU may receive a request from the network (e.g., from the first network node) to transmit SRSp at a time value, which may be the configured timing (e.g., at a time instance after Ts slots from when the WTRU receives the request) or at an absolute time. If the time value (e.g , configured timing) is expressed in terms of absolute time, the WTRU may determine the relative time based on a configured numerology.
- the WTRU may send a request to the network (e.g., to the second network entity) for uplink resources for transmitting the SRSp (e.g., via a SRSp scheduling request) indicating the start time determined by Ts and a duration of SRSp transmission (e.g., repetition factor, periodicity, window of transmission).
- the WTRU may receive a grant for more than one uplink resource (e.g., time and frequency resources) from the second network node, where a (e.g., each) resource may be associated with an index.
- the WTRU may receive a command (e.g., via RRC/MAC-CE) from the network (e g., the second network entity) indicating the index of the resource to be activated for SRSp transmission from the network.
- the WTRU may determine the resource to be activated based on the indicated index and the UL resource indexes received in the grant.
- the WTRU may transmit SRSp at the configured timing.
- the WTRU may terminate SRSp transmission once a termination condition (e.g., time is expired, the WTRU receives the MAC-CE deactivation command, etc.) is met.
- FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
- FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
- WTRU wireless transmit/receive unit
- FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
- FIG. 1 D is a system diagram illustrating a further example RAN and a further example ON that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
- FIG. 2 illustrates an example of scheduled reception of PRS from more than one TRP.
- FIG. 3 illustrates an example of an indication for Rx and Tx timing.
- FIG. 4 illustrates an example of scheduled transmission of PRS.
- FIG. 5 illustrates an example of scheduled reception of SRSp.
- FIG. 6 illustrates examples of the parameters of a measurement gap or PRS processing window.
- FIG. 7 illustrates an example of a Tx prioritization window.
- FIG. 8 illustrates an example of parameters for a Tx prioritization window.
- FIG. 9 illustrates an example of PRS measurement trigger via DCI.
- FIG. 10 shows an example of an indication of reception or transmission timing from a network.
- FIG. 11 illustrates an example of DCI-triggering PRS reception and SRSp transmission.
- FIG. 12 illustrates an example of a Tx and Rx prioritization window.
- FIG. 13 illustrates an example of transmission of more than one SRSp
- FIG. 14 shows an example of SRS transmission timing with respect to subframes or slots.
- FIG. 15 illustrates an example of an activation MAC-CE and a deactivation MAC-CE.
- FIG. 16 illustrates an example of on-demand simultaneous PRS reception for differential processing.
- FIG. 1A is a 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.
- the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail uniqueword DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal FDMA
- SC-FDMA single-carrier FDMA
- ZT UW DTS-s OFDM zero-tail uniqueword DFT-Spread OFDM
- UW-OFDM unique word OFDM
- FBMC filter bank multicarrier
- the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 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.
- WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
- the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fl 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.
- UE user equipment
- PDA personal digital assistant
- HMD head-mounted display
- any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.
- 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 to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the other networks 112.
- the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, 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.
- the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
- BSC base station controller
- RNC radio network controller
- the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
- a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
- the cell associated with the base station 114a may be divided into three sectors.
- the base station 114a may include three transceivers, i.e., one for each sector of the cell.
- the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
- MIMO multiple-input multiple output
- beamforming may be used to transmit and/or receive signals in desired spatial directions.
- the base stations 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).
- RAT radio access technology
- the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
- the base station 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 115/116/117 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 (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
- 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).
- E-UTRA Evolved UMTS Terrestrial Radio Access
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- LTE-A Pro LTE-Advanced Pro
- 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).
- a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
- the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
- 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.
- DC dual connectivity
- the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g, a eNB and a gNB).
- the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
- the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
- the base station 114b may have a direct connection to the Internet 110.
- the base station 114b may not be required to access the Internet 110 via the CN 106/115.
- the RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
- the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
- QoS quality of service
- the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
- the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
- the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
- POTS plain old telephone service
- the Internet 110 may include a global system of interconnected computer networks and devices that use common 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.
- the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
- FIG. 1B is a system diagram illustrating an example WTRU 102.
- the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
- GPS global positioning system
- the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
- the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
- the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
- the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
- the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
- the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
- the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
- the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
- the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
- the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
- the WTRU 102 may have multi-mode capabilities.
- the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
- the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
- the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
- the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
- the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
- the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
- SIM subscriber identity module
- SD secure digital
- the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
- the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
- the power source 134 may be any suitable device for powering the WTRU 102.
- the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
- the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
- the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
- the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
- FM frequency modulated
- the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
- a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
- the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
- the full duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
- the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
- FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
- the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
- the RAN 104 may also be in communication with the CN 106.
- Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
- the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
- the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
- the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
- the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
- the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
- the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
- the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
- the other network 112 may be a WLAN.
- a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
- the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
- Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
- Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
- DS Distribution System
- Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
- the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
- the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
- the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
- a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
- the IBSS mode of communication may sometimes be referred to herein as an ''ad-hoc’’ mode of communication.
- the AP may transmit a beacon on a fixed channel, such as a primary channel.
- the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
- the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
- Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
- the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
- One STA (e.g., only one station) may transmit at any given time in a given BSS.
- High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
- VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
- the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
- a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
- the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
- Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
- IFFT Inverse Fast Fourier Transform
- the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
- the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
- MAC Medium Access Control
- Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
- the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac.
- 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
- 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
- 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
- MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
- the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
- WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 n,
- 802.11 ac, 802.11af, and 802.11 ah 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 ST A, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
- the primary channel may be 1 MHz wide for STAs (e.g , MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
- Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
- STAs e.g , MTC type devices
- NAV Network Allocation Vector
- the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
- FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
- the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
- the RAN 113 may also be in communication with the CN 115.
- the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
- the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
- the gNBs 180a, 180b, 180c may implement MIMO technology.
- gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
- the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
- the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
- the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
- the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
- WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
- CoMP Coordinated Multi-Point
- the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
- the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
- TTIs subframe or transmission time intervals
- the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
- WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode- Bs 160a, 160b, 160c).
- WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
- WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
- WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
- WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously
- eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
- Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
- UPF User Plane Function
- AMF Access and Mobility Management Function
- the CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
- SMF Session Management Function
- the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
- the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
- Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
- different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like.
- URLLC ultra-reliable low latency
- eMBB enhanced massive mobile broadband
- MTC machine type communication
- the AMF 162 may provide a control plane function for switching between the RAN 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.
- 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.
- the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
- the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
- the CN 115 may facilitate communications with other networks.
- 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.
- IP gateway e.g., an IP multimedia subsystem (IMS) server
- IMS IP multimedia subsystem
- 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
- the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
- DN local Data Network
- one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
- the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
- the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions
- the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
- the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
- the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
- the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
- the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
- the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
- the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
- RF circuitry e.g., which may include one or more antennas
- a wireless transmit/receive unit may not be able to request to transmit SRSp or receive PRS at a specified timing.
- SRSp maybe associated with a lower prioritization compared to other uplink (UL) channel signals.
- Scheduled measurements or transmission may happen simultaneously, such that the measurements made by different WTRUs can be collected at the network and processed (e.g., differential processing). Any delays in measurements or transmission among the WTRUs may result in inconsistency in processed measurements.
- the WTRU may not be able to perform measurements or transmission of SRSp at the requested timing(s).
- the WTRU may not obtain configurations in time for scheduled positioning.
- enabling scheduled positioning to occur securely at scheduled timing(s) may be provided for herein.
- the WTRU may send a request to the network for a configuration (e.g., PRS configurations, SRSp configurations) in a PUSCH, PUCCH, UCI, MAC-CE, RRC or LPP message.
- the request from the WTRU may include configurations of a measurement gap, a PRS processing window, and/or a window for transmission of SRS for positioning (SRSp).
- the WTRU may send an acknowledgement message in PUSCH or PUCCH for the grant received from the network.
- a time window (e.g., as described herein) may be configured by the network.
- the WTRU may receive more than one configuration (e.g., duration) of the time window, and the WTRU may determine which time window is activated based on the activation command, received from the network, associated with the window.
- More than one condition/criteria may be used in a combination.
- the WTRU may be configured with more than one conditions and associated WTRU behavior and the WTRU may determine which behavior the WTRU to use based on applicable condition(s).
- the WTRU may measure DL-PRS inside or outside of an active BWP.
- the WTRU may transmit SRSp inside or outside of the active BWP.
- the WTRU may be preconfigured with one or more parameters (e.g. , measurement gaps, PRS processing windows, PRS configurations, SRSp configurations) via a semi-static message (e.g., LPP, RRC).
- parameters e.g. , measurement gaps, PRS processing windows, PRS configurations, SRSp configurations
- a semi-static message e.g., LPP, RRC
- Any actions the WTRU determines to take may be configured by the network.
- the WTRU may be configured with a rule and according to the rule, the WTRU may determine to take an associated action.
- the WTRU may include one or more of the following cell- related measurements: SSB RSRP from the serving cell with corresponding cell ID; SSB RSRP from the neighboring cell(s) with corresponding cell ID(s); RSRP of CSI-RS with CSI-RS resource ID; and/or RSRP of DM-RS.
- network may include an AMP, an LMF, a gNB, an NG-RAN, and/or any other network entity or combination thereof.
- pre-configuration and “configuration”; “non-serving gNB” and “neighboring gNB”; “gNB” and “TRP”; “PRS,” “SRS,” “SRS for positioning,” and/or “SRS for positioning purpose”; “PRS” and “PRS resource”; “PRS(s)” and “PRS resource(s)”; “PRS,” “DL-PRS,” and/or “DL PRS”; and/or “measurement gap” and “measurement gap pattern.”
- An LMF may be a non-limiting example of a node or entity (e.g., network node or entity) that may be used for or to support positioning. Any other node or entity may be substituted for the LMF and still be consistent with the embodiments described herein.
- a node or entity e.g., network node or entity
- the WTRU may receive a preconfigured threshold(s) from the network (e.g., LMF, gNB).
- the network e.g., LMF, gNB.
- the line of sight (LOS) indicator may be a hard (e.g., 1 or O) or soft indicator (e.g., 0, 0.1 , 0.2...,1), and it may indicate the likelihood of the presence of an LOS path between a TRP and the WTRU or along PRS.
- the LOS indicator may be associated with a TRP or PRS resource ID (e.g., index).
- the WTRU may receive the LOS indicator from the network per TRP or resource ID. Alternatively, the WTRU may determine the LOS indicator per TRP or resource ID based on measurements.
- a WTRU location may be expressed in terms of altitude, latitude, geographic coordinate, and/or local coordinate, for example.
- One or more configurations for RS for positioning may be disclosed herein.
- one or more configurations for PRS may be used.
- a PRS configuration may contain one or more of the following parameters: number of symbols, transmission power, number of PRS resources included in PRS resource set, muting pattern for PRS (e.g. , which may be expressed via a bitmap), periodicity, type of PRS (e.g., periodic, semi-persistent, or aperiodic), slot offset for periodic transmission for PRS, vertical shift of PRS pattern in the frequency domain, time gap during repetition, repetition factor, RE (resource element) offset, comb pattern, comb size, spatial relation, QCL information (e.g., QCL target, QCL source) for PRS, number of PRUs, number of TRPs, Absolute Radio-Frequency Channel Number (ARFCN), subcarrier spacing, expected RSTD, uncertainty in expected RSTD, start Physical Resource Block (PRB), bandwidth, BWP ID, number of frequency layers, start/end time for PRS transmission, on/off indicator for PRS, TRP ID, PRS ID, cell ID, global cell ID, PRU
- An SRS for positioning (SRSp) or SRS configuration may include one or more of: resource ID; comb offset values, cyclic shift values; start position in the frequency domain; number of SRSp symbols; shift in the frequency domain for SRSp; frequency hopping pattern; type of SRSp (e.g., aperiodic, semi-persistent or periodic); sequence ID used to generate SRSp, or other IDs used to generate SRSp sequence; spatial relation information, indicating which reference signal (e.g., DL RS, UL RS, CSI- RS, SRS, DM-RS) or SSB (e.g., SSB ID, cell ID of the SSB) the SRSp is related to spatially where the SRSp and DL RS may be aligned spatially; QCL information (e.g., a QCL relationship between SRSp and other reference signals or SSB); QCL type (e.g., QCL
- a reference signal time difference may be defined by the difference in time of arrival between PRSs transmitted from a reference TRP and target TRP
- the WTRU may be configured with the reference TRP index and target TRP index.
- the WTRU may be configured with the PRS resource indices to make measurements.
- the WTRU may determine the time of arrival from the TRP based on one or more PRS resources associated with the TRP.
- the RSTD may be defined as the difference in time of arrival between the reference PRS transmitted from a TRP and the target PRS transmitted from a TRP.
- the term "WTRU Rx - Tx time difference” may refer to the difference between the arrival time of the reference signal transmitted by the TRP and the transmission time of the reference signal transmitted from the WTRU.
- the WTRU Rx-Tx time difference may be associated with a PRS resource ID and/or an SRSp resource ID.
- An indication for scheduled transmission or reception may be used.
- FIG. 2 illustrates an example of scheduled reception of PRS from more than one TRP.
- the network may indicate the reception timing of PRS transmitted from TRP2 and TRP3 as Td1 and Td2, respectively, with respect to the reception timing of PRS transmitted from TRP1 .
- the reception timing of PRS transmitted from TRP1 may be indicated as Tp (e.g., the reception timing of PRS respect to the timing when the WTRU receives the request from the network).
- the WTRU may receive a request from the network (e.g., LMF, gNB) to transmit SRSp or receive PRS at scheduled timing.
- the transmission or reception timing may be expressed in terms of absolute time or relative time with respect to a reference point/timing.
- the WTRU may receive the request in RRC/LPP message, MAC-CE or DCI.
- the WTRU may receive the request to transmit SRSp or receive PRS, where the indication may include one or more of the following: transmission and/or reception timing(s) from the WTRU perspective (e.g., absolute time, relative time (e.g., expressed in terms of slots, symbols, frames)) with respect to a reference point; transmission and/or reception timing(s) from the network perspective; PRS or SRSp configs associated with reception or transmission, respectively; validity condition(s) of the request; and/or flexibility in transmission/reception timing.
- transmission and/or reception timing(s) from the WTRU perspective e.g., absolute time, relative time (e.g., expressed in terms of slots, symbols, frames)
- PRS or SRSp configs associated with reception or transmission respectively
- validity condition(s) of the request and/or flexibility in transmission/reception timing.
- the WTRU may receive the request to transmit SRSp or receive PRS, where the indication may include transmission and/or reception timing(s) from the WTRU perspective (e.g., absolute time, relative time (e g., expressed in terms of slots, symbols, frames)) with respect to a reference point.
- the WTRU may be requested to receive PRS at specific time (e.g., 3PM UTC).
- the WTRU may receive a request to receive PRS at a relative time (e.g., 10 seconds from a reference timing, N slots from a reference timing where N is the preconfigured parameter, etc.).
- the WTRU may be requested to transmit SRSp at a relative time (e.g., N slots from the timing when the WTRU transmitted ACK to the network after the WTRU obtained the UL grant for SRSp transmission).
- the WTRU may be indicated with a reference transmission timing and relative timing(s) at which SRSp resource(s) or PRS resource(s) are to be transmitted.
- the request may indicate transmission timing(s) of SRSp if the WTRU is configured with UL positioning method(s) (e.g., UL-AoA or UL-TDOA).
- the request may indicate reception timing(s) of PRS if the WTRU is configured with DL positioning method(s) (e.g., DL-AoD or DL-TDOA).
- the transmission timing or reception timing of PRS or SRSp, respectively, may be indicated by the network.
- FIG. 4 illustrates an example of scheduled transmission of PRS.
- the network may indicate transmission timing of PRS with respect to the timing of transmission of the request from the network.
- the WTRU may determine the reception timing of PRS based on distance between the WTRU and network (e.g., timing advance, GNSS location, round-trip time measurement).
- the network may indicate reception timing of SRSp.
- FIG. 5 illustrates an example of scheduled reception of SRSp.
- the WTRU may receive a request indicating a time difference between the timing the network sent the request to the WTRU and the time at which the network receives SRSp.
- the WTRU may determine the transmission timing of SRSp based on distance between the WTRU and network (e.g., timing advance, GNSS location, round-trip time measurement).
- the request may indicate, and/or the WTRU may determine, the reference point/timing when transmission/reception timing is a relative time.
- the reference point may be the timing when the WTRU receives the request from the network and/or the timing when the WTRU sent ACK to the network after transmission/reception resources are granted from the network.
- the reference timing may be when the WTRU sent ACK to the network for the request, sent from the network, for scheduled transmission or reception.
- the WTRU may receive the request to transmit SRSp or receive PRS, where the indication may include PRS or SRSp configs associated with reception or transmission, respectively.
- the request may indicate PRS resource(s) ID, TRP ID or SRSp resource ID, spatial information (e.g., spatial direction the WTRU should transmit SRSp toward) or RX information (e.g., reception I D/panel ID the WTRU should use to receive PRS).
- the WTRU may receive the request to transmit SRSp or receive PRS, where the indication may include validity condition(s) of the request. Examples of validity conditions may be area validity and/or time validity.
- the request may indicate cell ID(s) in which the request is valid. The request may be valid until a preconfigured time (e.g., N slots) before the requested transmission timing of SRSp or reception timing of PRS.
- the WTRU may receive the request to transmit SRSp or receive PRS, where the indication may include flexibility in transmission/reception timing.
- the WTRU may determine from the request flexibility in transmission timing of SRSp or reception timing of PRS.
- the request may indicate a tolerable limit in timing (e.g., plus or minus M slots/seconds from the indicated timing), indicating the WTRU may transmit SRSp or receive PRS within the tolerable limit.
- the priority level associated with PRS, SRSp or window may be indicated as, for example, “high”, “low”, or “medium”. Additionally or alternatively, the priority level may be indicated numerically (e.g., 0,0.1, ...,0.9,1 , where 0 indicates a lowest priority level and 1 indicates a highest priority level).
- the WTRU may determine to prioritize SRSp transmission over UL channels (e.g., PUSCH, PUCCH) or reception of PRS over DL channels (e.g., PDCCH, PDSCH). For example, if the priority level of reception of PRS is relatively low, then the WTRU may prioritize reception of SSB or PDSCH or PDCCH.
- the WTRU may determine to transmit SR or PDCCH instead of SRSp.
- SR may be associated with a priority level of “high” or 0.8
- PUCCH may be associated with a priority level of 0.5
- the priority level of SRSp may be set at 0.9 via configuration, for example.
- the WTRU may determine whether to prioritize PRS reception over reception of DL channels, when time and/or frequency resources of PRS and other DL channels overlap.
- the WTRU may determine whether to prioritize SRSp transmission over transmission of UL channels (e.g., PUCCH, PUSCH, SR), when time and/or frequency resources of SRSp and other UL channels overlap.
- UL channels e.g., PUCCH, PUSCH, SR
- the WTRU may determine the priority level of SRSp based on its transmission characteristic. For example, the WTRU may determine that the highest priority level compared to other UL channels is associated with aperiodic SRSp. For semi-persistent or periodic SRSp, the WTRU may determine to associate the SRSp with the lowest priority level.
- a WTRU may be configured to transmit SRSp or receive PRS at an absolute/relative time.
- Examples of the absolute time may include one or more of the following: Coordinated Universal Time (UTC) time; GNSS time; and/or network time (e.g , in terms of cell ID, system frame number, frame number, slot number, etc.).
- UTC Coordinated Universal Time
- GNSS GNSS time
- network time e.g , in terms of cell ID, system frame number, frame number, slot number, etc.
- the WTRU may determine to translate a relative time to absolute time and report the translated time to the network.
- the WTRU may report the determined absolute time to the network.
- a measurement gap and/or PRS prioritization window may be used.
- the WTRU may be configured to receive PRS during a PRS processing window or measurement gap.
- the measurement gap or PRS processing window may be configured by the network (e.g., LMF, gNB).
- FIG. 6 illustrates examples of the parameters of a measurement gap or PRS processing window. Similar parameters (e.g., periodicity, length of the window, window offset, offset) as in the measurement gap may be defined for a PRS processing window.
- Similar parameters e.g., periodicity, length of the window, window offset, offset
- the WTRU may receive an indication/configuration to make measurements on PRS during the gap length and process the measurements.
- a (e.g., each) measurement gap pattern or PRS processing window patter may be characterized by a set of gap length, gap periodicity and/or offset.
- a priority level may be associated with a PRS prioritization window.
- the WTRU may receive a message from the network (e.g., gNB, LMF) indicating the priority level of the PRS prioritization window.
- the network e.g., gNB, LMF
- Periodic, semi-persistent, and/or aperiodic transmission may be performed.
- the WTRU may receive/transmit PRS or SRSp periodically (e.g., at a configured periodicity).
- the WTRU may be preconfigured with an offset (e.g., in subframes, slots, symbols) to the periodic transmission.
- the WTRU may receive a semi-static message (e.g., LPP, RRC) from the network to enable periodic transmission via semi-static message.
- the WTRU may receive a semi-static message from the network to disable the periodic reception/transmission.
- the WTRU may receive an activation command via MAC-CE to activate semi-persistent PRS/SRSp reception/transmission.
- Semi- persistent transmission/reception may be defined by periodic transmission or reception during a time window which may be activated or deactivated (e.g., or activated via MAC-CE and deactivated by a termination condition such as timer expiration).
- the WTRU may be preconfigured with the duration of the timer or duration of the window expressed in terms of number of slots/frames, for example.
- the WTRU may be preconfigured with PRS or SRSp configurations during the semi-persistent reception/transmission.
- the WTRU may receive a DCI to trigger aperiodic PRS reception or SRSp transmission.
- the DCI command may indicate an index which refers to at least one of the preconfigured PRS or SRSp configurations.
- a DCI or MAC-CE may include contents.
- the DCI or MAC-CE message the WTRU receives from the network may contain one or more of the following: PRS/SRSp configuration(s) (e.g., PRS/SRSp resource index/indices, PRS/SRSp resource set index/indices, etc.); PRS reception and/or SRSp transmission timing; a difference between PRS reception timing and SRSp transmission timing; a periodicity of PRS reception and/or SRSp transmission; an offset of subsequent reception of PRS and/or transmission of SRSp (e.g., T1 and T2 in FIG.
- PRS/SRSp configuration(s) e.g., PRS/SRSp resource index/indices, PRS/SRSp resource set index/indices, etc.
- PRS reception and/or SRSp transmission timing e.g., PRS/SRSp resource index/indices, PRS/SRSp resource set index/indices, etc.
- the WTRU may receive a groupcast or broadcast command, sent from the network, to transmit SRS or receive PRS at specified timing.
- the WTRU may determine resources to use for transmission of SRSp or reception of PRS based on a preconfigured SRSp or PRS resources.
- the WTRU may determine to apply the indication or configurations in the groupcast/broadcast message based on the WTRU ID or WTRU specific parameters (e.g., RNTI) included in the broadcast/groupcast message.
- Tx-Rx prioritization window and/or Tx prioritization window may allow for reliable reception of PRS and/or transmission of SRSp, guaranteeing conditions for calibration or differential processing of measurements.
- the WTRU may be configured with a transmission window during which SRSp is associated with a priority level, and the WTRU may determine to prioritize transmission of UL channels (e.g., PUCCH, PUSCH) over SRSp.
- the parameters of the window e.g., duration, start/end time
- the WTRU may be configured to determine the priority of SRSp and uplink channels (e.g., PUSCH, PUCCH) if both transmissions are scheduled within the active BWP.
- the WTRU may be configured with a window (e.g., Tx prioritization window) during which the WTRU determines whether to prioritize transmission of SRSp or uplink channels.
- the WTRU may determine that the priority level is associated with the Tx prioritization window.
- the WTRU may determine that the priority level is associated with SRSp symbols.
- FIG. 7 illustrates an example of a Tx prioritization window. As shown in FIG.
- the WTRU may be configured to compare the priority of SRSp against other UL channels (e.g., PUSCH, PUCCH) during the Tx prioritization window. If a higher priority level is associated with the UL channel compared to the priority level of the window, the WTRU may determine to prioritize transmission of the UL channel and cancel one or more (e.g., all) SRSp transmissions in the window if resources of the UL channel overlap with resources of the Tx prioritization window. For example, using the example illustrated in FIG. 7, the WTRU may determine that PUCCH is scheduled to be transmitted in uplink slot #1 . Time/frequency resources of PUCCH may not collide with SRSp resources.
- the WTRU may determine to transmit PUCCH and may cancel transmission of the SRSp transmissions (e.g., SRSp transmissions scheduled in uplink slots #1 through slot #4).
- the WTRU may be scheduled to transmit SRSp at symbols #6 through #10 in slot #1 If the WTRU is scheduled to transmit PUCCH at symbol #1 through #5, the WTRU may determine to transmit PUCCH and SRSp at the respective scheduled symbols.
- the WTRU may be scheduled to transmit SRSp at symbols #6 through #10 in slot #1 . If the WTRU is scheduled to transmit PUCCH at symbols #3 through #9, and the priority level associated with PUCCH is higher than that of SRSp, the WTRU may be configured to transmit PUCCH instead of SRSp. Thus, the WTRU may determine to cancel (e.g., drop, not transmit) SRSp transmission at symbol #6 through #10, and may transmit PUCCH at symbol #3 through #9 instead
- the WTRU may determine that UL resources or DL resources that the WTRU requested have a higher priority than the scheduled SRSp transmission or Tx prioritization window. For example, the WTRU may determine to send an SR to the network. The WTRU may determine that the Tx prioritization window is invalid, or may determine to cancel the Tx prioritization window if the WTRU receives a UL grant (e.g., for PUSCH transmission) from the network, corresponding to the SR, which overlaps in time and/or frequency domain with the Tx prioritization window.
- a UL grant e.g., for PUSCH transmission
- the WTRU may be configured to determine to prioritize the transmission for the grant (e.g., prioritize PUSCH transmission) over the scheduled SRSp transmission. Thus, the WTRU may determine to retain the Tx prioritization window.
- Activation/deactivation of the Tx prioritization window may be performed.
- the WTRU may receive a list of Tx prioritization windows with different patterns.
- a pattern of Tx prioritization may be characterized by the parameters shown in FIG. 6 (e.g., periodicity, window duration and/or offset). For example, one pattern may have periodicity of 30ms, window duration (e.g., corresponding to "Measurement gap length” in FIG. 6) of 5ms and offset of 1ms. In another example, one pattern may have periodicity of 10ms, window duration (e.g., corresponding to “Measurement gap length” in FIG. 6) of 5ms and offset of 2ms.
- a (e.g., each) pattern may be associated with an index.
- the WTRU may receive an activation command (e.g., via DCI or MAC-CE) which activates the window.
- the activation command may include an index of the window pattern.
- the window may be deactivated by the deactivation command sent from the network.
- the WTRU may send a request to the network to activate or deactivate the window.
- the request may contain the index of the window the WTRU wants to activate or deactivate.
- the WTRU may determine that the window is deactivated after a timer expires.
- the timer may start when the WTRU receives the activation command from the network or when the WTRU sends an ACK to the configuration/activation command sent from the network.
- FIG. 8 illustrates an example of parameters for a Tx prioritization window.
- the window may be active from the beginning of a first uplink slot (e.g., uplink slot #1) till the end of a second uplink slot (e.g., uplink slot #4).
- the duration of the window may be defined as the difference between the end time and start time of the window.
- the WTRU may transmit SRSp.
- One of the parameters for the Tx prioritization window may be the periodicity of the “on” duration.
- the “on” duration may be determined based on the duration of SRSp and/or the WTRU capability (e.g., the time it takes for the WTRU to prepare transmission of SRSp).
- the “on” duration may correspond to the duration during which the SRSp symbols are scheduled (e.g., symbol #3 to symbol #8 in a slot corresponding to SRSp symbols) or to be transmitted.
- a priority level may be associated with “On” duration or window (e.g., the same priority level is applied across the window).
- the WTRU may be expected to transmit SRSp during the window (e.g., the WTRU does not expect to receive grants for UL channel transmissions during the transmission window).
- the WTRU may transmit a scheduling request (SR) during the window.
- SR scheduling request
- a time limit for configuration of a Tx prioritization window may be disclosed herein.
- the WTRU may receive an activation or request to activate the Tx prioritization window.
- the WTRU may determine to send a reply (e.g., “yes” or “no”) to the network (e.g., LMF, gNB) if the request to activate the Tx prioritization is received at least a preconfigured time (e.g., N slots, N symbols, N subframes, N frames) before the requested activation time of the Tx prioritization window.
- a reply e.g., “yes” or “no”
- the network e.g., LMF, gNB
- the WTRU may send a first reply (e.g., “yes”) for the request (e.g., accepting the request) to the network. If the WTRU receives the request after the preconfigured time, the WTRU may send a second reply (e.g., “no”) for the request to the network. The WTRU may determine to activate the Tx prioritization window after a preconfigured time after the WTRU sent the first reply (e.g., “yes”) for the request.
- a first reply e.g., “yes”
- the WTRU may send a second reply (e.g., “no”) for the request to the network.
- the WTRU may determine to activate the Tx prioritization window after a preconfigured time after the WTRU sent the first reply (e.g., “yes”) for the request.
- Determination of prioritization based on the parameters of the window may be performed.
- the WTRU may determine the priority level of the Tx window based on the parameters of the window and one or more threshold(s).
- the WTRU may be configured with thresholds and/or rules for determining the priority of the window.
- the WTRU may determine that the priority level of the Tx window is high when the duration of the window is shorter than the preconfigured threshold.
- the WTRU may determine that the priority level of Tx window is low when the duration of the window is longer than the preconfigured threshold.
- the WTRU may use the determined priority level to prioritize transmission of UL channels (e.g., PUSCH) or SRSp.
- a WTRU may be preconfigured with one or more SRS configurations.
- the WTRU may receive a TA command from the network (e.g., symbol level adjustment).
- the WTRU may receive an update config for SRS (e.g., spatial information).
- the WTRU may receive grant(s) for uplink transmission from the network.
- the WTRU may receive an activation command for semi-persistent SRS.
- the WTRU may determine the priority of the SRS (e.g., if the priority level for the transmission is not configured by the network). For example, if the duration is below a threshold, the WTRU may prioritize the transmission.
- the WTRU may prioritize other SR or scheduling PUSCH/PUCCH transmission.
- the WTRU may receive an offset command from the network, and may determine to apply the offset at the M ,h occasion from the timing at which the WTRU received the command.
- the WTRU may transmit SRS at the preconfigured periodicity.
- the WTRU may receive a deactivation command for the semi- persistent SRS.
- the WTRU may determine to set the window based on the WTRU capability (e.g., whether the WTRU is a positioning reference unit (PRU) or normal WTRU).
- PRU positioning reference unit
- NW-initiated simultaneous PRS reception may be performed.
- the network may initiate simultaneous PRS reception.
- the WTRU may receive a message from the network indicating the PRS resource index that the WTRU should receive.
- the WTRU may be preconfigured with more than one PRS resources/configurations, and a (e.g., each) resource/configuration may be associated with an index.
- the WTRU may also be preconfigured with a list of measurement gaps or PRS processing windows where a (e.g., each) measurement gap pattern is associated with an index.
- the WTRU may receive an indication of transmission/reception timing from the gNB if the WTRU is configured to transmit SRSp to TRPs or receive PRS from TRPs in the serving gNB.
- the WTRU may determine to use the measurement gap when the WTRU is configured to receive PRS outside of the active BWP.
- the WTRU may determine to use the PRS configuration window when the WTRU is configured to receive PRS (e.g., only) inside of the active BWP.
- the WTRU may receive a message from the network (e.g., gNB, LMF) via DCI, MAC-CE, RRC or LPP message indicating reception time (e.g., absolute or relative time) of PRS, indicating PRS resource/configuration index.
- the message may also contain an index for the measurement gap pattern or PRS processing windows the WTRU shall use to receive PRS.
- the PRS config/resource index may be associated with the index of measurement gap or PRS processing window.
- the WTRU may determine the index of the measurement gap or PRS processing window based on the index of PRS resource or configuration that the WTRU is configured to receive.
- a WTRU may be preconfigured with PRS configurations via a semi-static message (e.g., LPP), where a (e.g., each) PRS config is associated with an index.
- the WTRU may be preconfigured with a list of measurement gaps via a semi-static message (e.g., RRC), where a (e.g., each) gap is associated with an index.
- a semi-static message e.g., RRC
- the WTRU may receive a message from the network (e.g., gNB), via DCI/MAC-CE, indicating PRS reception with indicated time (e.g., relative time) and PRS index.
- the message may also contain the index of the measurement gap patten the WTRU should use.
- the WTRU may determine which measurement gap pattern to use based on the index included in the message.
- the WTRU may receive PRS at the indicated timing.
- the WTRU may make measurements on the received PRS and may report the measurement results to the LMF.
- FIG. 9 illustrates an example of PRS measurement trigger via DCI.
- FIG. 10 shows an example of an indication of reception or transmission timing from a network.
- a WTRU may receive PRS and/or SRSp configurations from the network.
- the WTRU may receive a message (e.g., DCI) from the network, indicating reception and transmission time of PRS and SRSp, respectively.
- the message may also include the PRS and SRSp resource index the WTRU should use to receive or transmit PRS and SRSp, respectively
- FIG. 11 illustrates an example of DCI-triggering PRS reception and SRSp transmission. As shown in FIG.
- the WTRU may be configured with an RTT positioning method, where the WTRU may be expected to receive PRS and transmit SRSp.
- the WTRU may be configured with PRS configurations and SRSp configurations via LMF and gNB, respectively.
- the WTRU may receive a measurement gap configuration from the network.
- FIG. 10 further illustrates an example of an indication of transmission or reception timing from a network.
- the DCI may indicate the transmission timing of SRSp (e.g., Ts) and reception timing of PRS (e.g., Tp) where the timing may be defined with respect to the timing of reception of the DCI message from the network.
- SRSp e.g., Ts
- PRS e.g., Tp
- the DCI or MAC-CE may be contained in PDCCH or PDSCH.
- the DCI or MAC-CE message may indicate a priority level associated with PRS and/or SRSp.
- the WTRU may determine to prioritize reception of DL channels (e.g., PDCCH, PDSCH) with higher priority level over PRS and/or transmission of UL channels (e.g., PUCCH, PUSCH) over SRSp transmission.
- the priority level may be associated with the Tx-Rx window and the WTRU may determine to prioritize PRS reception or SRSp transmission over DL or UL channels, respectively, based on the priority level of the window and DL/UL channels.
- a WTRU may determine Tp and/or Ts.
- FIG. 12 illustrates an example of a Tx and Rx prioritization window.
- the WTRU may be preconfigured with reception timing of PRS (Tp) and transmission timing of SRSp (Ts), where Tp may indicate the relative time with respect to a reference timing, and Ts may indicate the relative transmission timing with respect to the reference timing, where the reference timing may be the timing that the WTRU received the request.
- the WTRU may be preconfigured with a list of reception timings of PRS and transmission timings of SRSp, where a (e.g., each) timing may be associated with an index.
- the request received from the network for the scheduled transmission or reception may include the index of preconfigured reception timing(s) or transmission timing(s).
- the WTRU may determine the transmission timing or reception timing based on the timings indicated in the request.
- a Tx and Rx prioritization window (e.g., “TxRx window”) may be used.
- the WTRU may receive a TxRx window configuration from the network, indicating priority of PRS reception and SRSp transmission inside the window.
- the details of the TxRx window may be as described herein.
- the WTRU may be configured with a UL&DL positioning method (e.g., RTT positioning method) where the WTRU may be configured to receive PRS and transmit SRSp.
- the WTRU may receive the request from the network (e.g., LMF, gNB) to receive PRS and transmit SRSp at a specific timing.
- the network e.g., LMF, gNB
- the WTRU may receive PRS and SRSp config(s) from the network.
- the WTRU may be preconfigured with PRS and SRSp config(s), and the request may indicate an index for a config.
- the WTRU may report the WTRU Rx-Tx time to the network after the WTRU transmits SRSp.
- Tx and/or Rx timings may be determined.
- the WTRU may be configured to determine timing(s) of reception of PRS and/or transmission of SRSp based on one or more of the following methods.
- the WTRU may be preconfigured with timings or a pair of timings (e.g., a pair of Tp and Ts) via a semi-static message (e.g., LPP, RRC) where timings or a pair of timings may be associated with an index.
- a message from the network e.g., DCI, MAC-CE
- the WTRU may receive one or more (e.g., two) separate messages (e.g., DCI, MAC-CE) where a (e.g., each) message may indicate the reception timing of PRS or transmission timing SRSp.
- the WTRU may be preconfigured with timings (e.g. , Tp or Ts shown in FIG. 11) or a pair of timings (e.g. , a pair of Tp and Ts shown in FIG 11) via a semi-static message (e.g., LPP, RRC) where the timings or pair of timings may be associated with an index (e.g., timing index).
- a semi-static message e.g., LPP, RRC
- the WTRU may be preconfigured an association rule between the timing indices and configuration (e.g., PRS configuration, measurement gap pattern, PRS processing window).
- the WTRU may be preconfigured with the association rule (e.g., or table) via a semi-static message by the network (e.g., LMF, gNB).
- the WTRU may determine associated timings. For example, if the WTRU is configured with PRS resources requiring 2 symbols, 6 symbols and 12 symbols, each resource may be associated with 1 slot, 2 slots, or 3 slots for Tp, respectively
- Timings may be defined as the reference timing and subsequent timings with respect to the reference timing.
- the WTRU may be configured to transmit more than one SRSp.
- the WTRU may be preconfigured with more than one SRSp resource, where a (e.g., each) resource may be associated with a different SRSp configuration (e.g., spatial relationship, Tx spatial filter).
- the WTRU may determine to transmit the preconfigured SRSps based on preconfigured timings. Examples of the preconfigured Tx timings for a (e.g., each) SRSp are shown in FIG. 13, where SRSp1 is transmitted after Ts slots after the reception of the DCI.
- FIG. 13 illustrates an example of transmission of more than one SRSp.
- the WTRU may determine to transmit SRSp2 and SRSp3 at T1 slots and T2 slots after the transmission timing of SRSp1 , respectively
- the WTRU may be preconfigured with the default timing. For example, the WTRU may determine that the WTRU may receive PRS N slots after the WTRU receives the DCI/MAC-CE.
- the WTRU may be configured to receive more than one message, where a (e.g., each) message may indicate different granularities (e.g., frame/subframe/slot/symbol-level) of Rx or Tx timings.
- a (e.g., each) message may indicate different granularities (e.g., frame/subframe/slot/symbol-level) of Rx or Tx timings.
- the WTRU may be preconfigured by the network subframe(s) of resources for PRS reception and/or SRSp transmission.
- the WTRU may be preconfigured, via a semi-static message (e.g., LPP, RRC), with subframe/frame indices to transmit SRSp.
- the WTRU may receive DCI or MAC-CE from the network indicating a group of resources within one or plural of subframe indices at which the WTRU may transmit SRSp.
- the DCI or MAC-CE message may indicate an index (or indices) of SRSp resource(s)/configuration(s).
- An example of SRS transmission timing with respect to subframes or slots is shown in FIG. 14.
- the WTRU may receive an indication from the network via a semi-static message that one or more uplink subframes (e.g., uplink subframe #1 through #3 shown in FIG. 14) will contain SRS transmission timings.
- the WTRU may receive a DCI/MAC-CE message indicating a slot (e g., slot #2) in a (e.g., each) subframe are activated for SRS transmission.
- the WTRU may receive an additional DCI/MAC-CE message indicating symbols to be used for SRSp transmission (e.g., symbol #5 through # 9 in slot #2). It may be assumed that there are 14 OFDM symbols in a slot.
- MAC-CE activation/deactivation may be performed.
- the WTRU may be configured to receive MAC-CE from the network (e.g., gNB) to activate semi-persistent transmission of a pair of PRS and SRSp.
- the MAC-CE may include an index for a pair of PRS and SRSp configuration index.
- the WTRU may determine which configuration to use for PRS reception or SRSp reception based on the index.
- the WTRU may determine which pair of PRS and SRSp resources is activated based on the configuration pair index indicated in the MAC-CE command. Based on the activation command, the WTRU may determine to receive PRS periodically and transmit SRS periodically, following the same periodicity.
- the Rx-Tx time difference determined by the difference between reception timing of PRS and transmission timing of PRS, may be preconfigured and indicated in the MAC-CE.
- the WTRU may determine to terminate the periodic reception of PRS and transmission of SRSp based on the deactivation command received from the network (e.g., gNB, LMF).
- FIG. 15 illustrates an example of an activation MAC-CE and a deactivation MAC- CE. As shown in FIG. 15, the WTRU may receive an activation MAC-CE from the network.
- the activation command may also indicate Tp and/or Ts, which are the timing at which PRS and SRSp are received and transmitted, respectively.
- the command may also indicate T1 and/or T2, which are PRS reception and SRSp transmission timing with respect to a reference point, which is the previous SRSp transmission occasion.
- the WTRU may receive PRS and/or transmit SRSp periodically at indicated timings, T1 and T2.
- the WTRU may receive the deactivation MAC-CE message from the network and may terminate reception of PRS and transmission of SRSp.
- cycling through more than one PRS/SRSp resource may be performed. If the WTRU is preconfigured with more than one PRS and/or SRSp resource, the WTRU may determine to transmit SRSp at the configured resources.
- the DCI/MAC-CE/RRC/LPP message may indicate the PRS reception pattern or SRSp transmission pattern. For example, the WTRU may determined, from the indicated or configured pattern, to transmit SRSp following the ascending order of index numbers (e.g., the WTRU transmits SRSp1, SRSp2 and/or SRSp3 in FIG. 13).
- the WTRU may receive configuration(s) for prioritized SRSp transmission and/or PRS reception.
- the WTRU may receive configuration(s) for SRSp transmission and/or PRS reception from the network (e.g., from LMF via LPP message, from gNB via RRC message).
- the WTRU may receive one or more priorities associated with the SRSp transmission and/or PRS reception.
- the WTRU may be indicated with one or more resources for prioritized transmission/reception.
- Such resources may be one or more of the following: a resource for SRSp transmission and/or PRS reception, a set of resources for SRSp transmission and/or PRS reception, a window of resources for SRSp transmission and/or PRS reception, a periodic resource for SRSp transmission and/or PRS reception, and/or a periodic window of resources for SRSp transmission and PRS reception, etc.
- the WTRU may perform one or more of the following for the indicated prioritized transmission/reception resources.
- the WTRU may increase the priority associated with the indicated resources.
- the WTRU may increase the priority of the indicated resources by an offset compared to the other SRSp transmission and/or PRS reception resources in the configuration. The offset may be indicated in the configuration.
- the WTRU may increase the priority of the indicated resources by a predefined level (e.g., the WTRU may increase the priority of the indicated resources from low to medium, or from medium to high).
- the WTRU may set the priority of the indicated resource to be higher and/or lower than a certain physical channel
- the WTRU may set the priority of the indicated SRSp transmission resource to be higher than any PUSCH.
- the WTRU may set the priority of the indicated PRS reception resource to be higher than any PDSCH.
- the WTRU may set the priority of the indicated PRS reception resource to be higher than any PDCCH.
- the WTRU may set the PRS reception resource to be lower than SSB (e.g., only) and higher than any other DL channel except SSB.
- the WTRU may measure and/or report the prioritized PRS.
- the WTRU may perform measurement reporting for the prioritized PRS.
- the WTRU may measure one or more PRS measurement parameters (e.g , RSTD, RSRP, AoA, AoD) within the prioritized PRS.
- the WTRU may not filter measurement of the prioritized and nonprioritized PRS reception resource, the WTRU may perform measurement and reporting of a (e.g., each) prioritized PRS reception resource or a (e.g., each) pair of PRS reception resources (e.g., for RSTD measurement).
- the WTRU may perform measurement and reporting of a set of the prioritized PRS reception resources.
- the WTRU may filter the measurement of multiple prioritized PRS reception resource and report the filtered value to the network. These approaches may be motivated to help the network differentiate the measurement(s) from prioritized resources.
- the WTRU may prioritize reporting the measurement of the prioritized PRS reception. For example, the WTRU may prioritize the measurement report of the prioritized PRS. Specifically, the WTRU may have multiple measurement resources to report. The WTRU may then prioritize reporting the prioritized PRS reception resources compared to the non-prioritized PRS reception resource. The WTRU may prioritize multiplexing the measurement associated with the prioritized reception resource first in a measurement report massage to transmit to the network.
- a scheduling request for SRSp may be used. For example, a trigger for simultaneous SRSp transmission may be used.
- a WTRU may receive a request from the network (e.g., LMF, gNB) to transmit SRSp at scheduled time (e.g., absolute, relative time).
- the network e.g., LMF, gNB
- scheduled time e.g., absolute, relative time
- the WTRU may determine to send a request to the network to initiate simultaneous SRSp transmission among one or more WTRUs (e.g., including the first WTRU). For example, the WTRU may determine to send a request to the network if one or more of the following conditions is satisfied: a measurement error (e.g., RSRP, RSTD, phase) or measurement uncertainty is above a preconfigured threshold; a location estimation error is above a preconfigured threshold; and/or discovery of a PRU within a preconfigured distance threshold, where the WTRU may determine its location based on RAT dependent positioning methods (e.g., DL- TDOA, DO-AoD) and/or RAT independent positioning methods (e.g., GNSS).
- the WTRU may receive location information of PRUs via broadcast.
- a PRU may be a type of WTRU whose location is known by the PRU itself or the network (e.g., LMF,
- a scheduling request for SRSp may be used.
- the WTRU may send a request to the network (e.g., gNB, LMF) to transmit SRSp at a scheduled time (e.g., absolute or relative time).
- the WTRU may indicate the requested SRSp transmission characteristics by including one or more of the following in the scheduling request: a relative time with respect to a reference time; an absolute time (e.g., 3PM UTC); a duration of SRSp transmission (e.g., repetition factor, periodicity of SRSp, a window of periodic transmission of SRSp, time, etc.); and/or SRSp information (e.g., SRSp resource ID, SRSp resource set ID, TRP ID, spatial information of SRSp, etc.).
- a trigger to transmit SRSp may be determined.
- the WTRU may determine to transmit SRSp if the WTRU receives an uplink grant (e.g., time and frequency resources) to transmit SRSp.
- the WTRU may receive an activation command from the network (e.g., via MAC-CE) to transmit SRSp at indicated timing (e.g., N slots from the timing the WTRU receives the MAC-CE activation command).
- the WTRU may receive more than one resource for SRSp (e.g., SRSp resource indices) from the network.
- the WTRU may receive a DCI or MAC-CE indication command from the network, indicating the activated SRSp resource index. Based on the activation command, the WTRU may determine to transmit the activated SRSp using the resources associated with SRSp resource index.
- the WTRU may determine to send the scheduling request until the WTRU receives an acknowledgement message (e.g., “yes” for the WTRU's request) or grant for UL resources for the requested SRSp transmission.
- the WTRU may determine to keep sending the scheduling requests until M slots before the requested transmission timing, where M may be configured by the network.
- the WTRU may determine to send the scheduling request again if the WTRU does not receive a response from the network during a configured response time (e.g., N slots since when the WTRU sent the request to the network).
- the WTRU may be configured with the maximum number of requests that the WTRU can make.
- the WTRU may be configured with transmission occasions (e.g., periodic timing) at which the WTRU can send the scheduling request for SRSp.
- the WTRU may determine that the request failed.
- the WTRU may determine that the request failed when one or more of the following conditions is satisfied: the WTRU does not receive a grant for SRSp transmission from the network (e.g., indication of time and/or frequency resources to transmit SRSp) after sending N requests, where N may be the maximum number of requests; and/or the WTRU does not receive a grant for SRSp transmission within a preconfigured time window from the network (e.g., a request time window), where the time window may start when the WTRU sends the first request to the network.
- the WTRU may report to the network (e.g., LMF, gNB) that the request procedure has failed.
- the WTRU may determine to stop transmission of SRSp once the WTRU receives a deactivation command from the network (e.g., via MAC-CE, RRC, LPP).
- the WTRU may be configured with periodic or semi-persistent SRSp transmission, where the WTRU may be expected to transmit SRSp at a configured periodicity and/or with repetition factors.
- the WTRU may be configured to start a timer when the WTRU receives the grant or activation command for one of the SRSp resources.
- the WTRU may be configured with the time limit for the timer.
- the WTRU may determine to stop transmission of SRSp when the timer expires (e.g., the timer reaches the time limit).
- the WTRU may be configured with a time window with indicated start and end time (e.g., SFN, subframe, frame, slot, symbol number, absolute time, relative time, etc.) for the window.
- the WTRU may determine to stop transmission of SRSp when the WTRU determines that the end time of the time window is reached.
- a WTRU may send a request for scheduled SRS transmission.
- the WTRU may keep sending the request until the request is fulfilled or until the time limit of the request window (e.g., M slots prior to the scheduled transmission timing).
- the WTRU may receive a configuration of Ts (SRSp transmission timing) (e.g., from a first network entity such as an LMF).
- the WTRU may receive SRS configuration(s) (e.g., from the first network entity or a second network entity such as a gNB), where a (e.g., each) SRS configuration may be associated with an index.
- the WTRU may receive a request (e.g., timing) for SRSp transmission at the configured timing (e.g., Ts slots from when the WTRU receives the request, absolute time, etc.) from the network (e g., LMF).
- the configured timing e.g., Ts slots from when the WTRU receives the request, absolute time, etc.
- the WTRU may send a SRSp scheduling request to the gNB indicating at least the transmission timing and/or the SRS config index. If the WTRU does not receive a first reply (e.g., a "Yes”) from the gNB for the request within a preconfigured response time since the WTRU sent the request, the WTRU may determine to send the request until the WTRU receives an ACK from the gNB, or M slots prior to the requested transmission timing. If the WTRU receives the first reply from the gNB for the request, the WTRU may transmit SRSp at the scheduled transmission time.
- a first reply e.g., a "Yes”
- the WTRU may transmit SRSp at the scheduled transmission time.
- the WTRU may receive a configuration of Ts (SRSp transmission timing) from a network (e.g., from a first network entity such as an LMF).
- a configuration of Ts may be referred to as a “time value.”
- the WTRU may receive an SRSp configuration from the network (e.g., from the first network node or a second network node such as a gNB), where the SRSp configuration may include periodic transmission parameters (e.g., periodicity, repetition factor).
- the WTRU may send a request to the network (e.g., to the second network entity) for uplink resources for transmitting the SRSp (e.g., via a SRSp scheduling request) indicating the start time determined by Ts and a duration of SRSp transmission (e g., repetition factor, periodicity, window of transmission).
- the WTRU may receive a grant for more than one uplink resource (e.g., time and frequency resources) from the second network node, where a (e.g., each) resource may be associated with an index.
- the WTRU may receive a command (e.g., via RRC/MAC-CE) from the network (e.g., the second network entity) indicating the index of the resource to be activated for SRSp transmission from the network.
- the WTRU may determine the resource to be activated based on the indicated index and the UL resource indexes received in the grant.
- the WTRU may transmit SRSp at the configured timing.
- the WTRU may terminate SRSp transmission once a termination condition (e.g., time is expired, the WTRU receives the MAC-CE deactivation command, etc.) is met.
- a WTRU may determine to send a request to the network for a measurement report sent by another WTRU(s).
- the WTRU may be configured with a WTRU-based positioning method or WTRU-assisted positioning method.
- the WTRU may be configured to send a request to the network for simultaneous reception of PRS if one or more of the following conditions is satisfied: measurement error (e.g., RSRP, RSTD, phase, etc.) or measurement uncertainty is above a preconfigured threshold; WTRU location estimation error is above a preconfigured threshold; the distance between the PRU and the WTRU is less than a preconfigured distance threshold, where the WTRU may determine its location based on RAT dependent positioning methods (e.g., DL-TDOA, DO-AoD) and/or RAT independent positioning methods (e.g., GNSS); and/or the WTRU receives a request from the network (e.g., LMF) to perform simultaneous PRS reception and report correction or differential measurement results.
- the WTRU may receive location information of PRUs via broadcast, groupcast or unicast.
- a PRU may be a type of WTRU whose location is known by the PRU itself or network (e.g., LMF,
- the request for simultaneous reception may have contents.
- the WTRU may include one or more of the following: reception timings (e.g., absolute, relative) of PRS; WTRU location (e.g., determined based on a RAT dependent positioning method or RAT independent positioning method) and/or indication of the positioning method used to determine the WTRU location; information about the PRS (e.g., PRS resource index, PRS resource set index) the WTRU requests to receive; a type of measurement (e.g., RSTD, phase, RSRP, phase difference, RSRP per path (RSRPP)) the WTRU requests; PRS information (e.g., PRS resource indices) associated with measurement reports requested; PRU IDs or any identification information associated (e.g., RNTI) with PRU, where the term “PRU’’ may be used interchangeably with “reference WTRU" and/or “WTRU”; and/or a time (e.g., absolute, relative) of PRS; WT
- the WTRU may receive a session index in a message (e.g., LPP, RRC) for simultaneous reception as a reply from the network for the WTRU's request.
- the WTRU may determine from the message that the session index is associated with one or more PRS config(s).
- the message may contain the reception timing(s) of PRS associated with the session ID.
- the WTRU may send an acknowledgement message (e.g., in UCI, UL MAC-CE, PUSCH, PUCCH) for the message received from the network.
- a request for other measurements may have contents.
- the WTRU may send a request to the network for measurements made by PRUs or other WTRUs who received the PRS in the same session as the WTRU.
- the WTRU may send the request if one or more of the following conditions is satisfied: measurement error (e.g., RSRP, RSTD, phase) or measurement uncertainty is above a preconfigured threshold; and/or WTRU location estimation error is above a preconfigured threshold.
- the WTRU may indicate one or more of the following: a measurement type (e.g., RSTD, RSRP, phase, phase difference); a measurement volume (e.g., in terms of number of measurement instances, duration of measurements); timing(s) at which the measurements are made; PRS information (e.g., PRS resource index, PRS resource set index, target PRS resource index, reference PRS resource index, target TRP/PRS ID, reference TRP/PRS ID, etc.) associated with the requested measurement; PRU/WTRU IDs or any identification information associated (e.g., RNTI) with the PRU/WTRU; and/or a session index.
- a measurement type e.g., RSTD, RSRP, phase, phase difference
- a measurement volume e.g., in terms of number of measurement instances, duration of measurements
- timing(s) at which the measurements are made e.g., PRS information (e.g., PRS resource index, PRS resource set index, target PRS
- the WTRU may indicate a measurement volume in the request.
- Another WTRU or PRU may make accumulated measurements of repetitions and make an (e.g., one) instance of measurement (e.g., RSTD).
- the WTRU may determine the average, minimum or maximum value of N instances of measurements (e.g., RSRP, RSTD) and make one instance of the N instances of measurements.
- the WTRU may request N instances of measurements.
- the WTRU may indicate timing(s) at which the measurements are made in the request.
- the WTRU may indicate relative timing(s), absolute timing(s) and/or time stamps at which measurements are made.
- the relative time may be defined with respect to a reference timing (e.g., the reference time may be the timing the WTRU received PRS).
- the WTRU may request for measurements made on the indicated PRS resource indices at measurement periodicity of 5 seconds.
- the WTRU may indicate PRS information (e.g., PRS resource index, PRS resource set index, target PRS resource index, reference PRS resource index, target TRP/PRS ID, reference TRP/PRS ID, etc.) associated with the requested measurement in the request.
- PRS information e.g., PRS resource index, PRS resource set index, target PRS resource index, reference PRS resource index, target TRP/PRS ID, reference TRP/PRS ID, etc.
- PRS information e.g., PRS resource index, PRS resource set index, target PRS resource index, reference PRS resource index, target TRP/PRS ID, reference TRP/PRS ID, etc.
- PRS information e.g., PRS resource index, PRS resource set index, target PRS resource index, reference PRS resource index, target TRP/PRS ID, reference TRP/PRS ID, etc.
- the WTRU may request for measurements made on PRS resource #1 in PRS resource set #2 for frequency layer #1 from another WTRU/
- the WTRU may determine that the request procedure failed.
- the WTRU may determine that the request failed when one or more of the following conditions is satisfied: the WTRU does not receive a grant for the request from the network after sending N requests, where N may be the maximum number of requests; and/or the WTRU does not receive a grant for the request within a preconfigured time window from the network (e.g., a request time window), where the time window may start when the WTRU sends the first request to the network.
- the WTRU may report to the network (e.g., LMF, gNB) that the request procedure has failed.
- the network e.g., LMF, gNB
- the WTRU may obtain the measurements reported by PRUs or other WTRUs.
- the WTRU may be configured to perform differential processing.
- differential processing may be a difference between RSTD/RSRP/RSRPP/phase measurements made on the same PRS resource.
- RSTD_p and RSTDJJ are the RSTD measurements made by the PRU and the WTRU, respectively, the difference in RSTD may be computed by RSTD_p - RSTDJJ.
- the WTRU may report the outcome of differential processing to the network (e.g., LMF, gNB) and associate the outcome with the session index and/or time stamp associated with the measurements.
- the network e.g., LMF, gNB
- the WTRU may be configured or requested to determine and report a correction factor based on the measurements received from another WTRU/PRU.
- the correction may relate to Rx power, phase or timing offset or Tx power, phase, and/or timing offset.
- the WTRU may determine to report the correction factor (e.g., power/phase/timing offset determined based on measurements made by another WTRU/PRU and/or WTRU) to the network if the WTRU receives a request from the network to report the correction factor.
- the correction factor e.g., power/phase/timing offset determined based on measurements made by another WTRU/PRU and/or WTRU
- FIG. 16 illustrates an example of on-demand simultaneous PRS reception for differential processing.
- On-demand measurement report may be performed.
- the WTRU may be configured with a WTRU-based positioning method by the network (e.g., LMF, gNB).
- the WTRU may be configured with a distance threshold.
- the WTRU may receive a message (e.g., a broadcast) from the network, indicating locations of PRUs.
- the WTRU may send a request to the network for a simultaneous transmission session, for example if the WTRU determines that a distance between the broadcasted location of PRU(s) and the determined location of the WTRU (e.g., based on a positioning method (e.g., DL-TDOA)) is smaller than the preconfigured distance threshold.
- a positioning method e.g., DL-TDOA
- the WTRU may be configured with a value T (e.g., T slots, T frames) by the network (e.g., LMF) (e.g., via LPP message).
- the WTRU may receive a session index and/or a PRS configuration (e.g., PRS resource indices) associated with the session index from the network.
- the WTRU may receive a request (e.g., from the network) to perform PRS measurement at the configured timing (e.g., T slots from when the WTRU receives the request).
- the WTRU may receive PRS (e.g., T slots from when the WTRU receives the request) according to the PRS configuration, and may make a measurement on the received PRS.
- the WTRU may send a request to the LMF for measurements (e.g., made by PRU) associated with the PRS resource index and/or session index.
- the WTRU may receive the measurements associated with the session index from the network (e.g., LMF) (e.g., via an LPP message).
- the WTRU may report (e.g., an indication of) the WTRU location to the network (e.g., LMF).
- the processes and instrumentalities described herein may apply in any combination, may apply to other wireless technologies, and for other services.
- a WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc.
- WTRU may refer to application-based identities, e.g., user names that may be used per application.
- the processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor.
- Examples of computer- readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
- Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs).
- 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, and/or any host computer.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Une unité de transmission/réception sans fil (WTRU) peut recevoir une configuration de Ts (synchronisation de transmission SRSp). La WTRU peut recevoir une configuration SRSp qui peut comprendre des paramètres de transmission périodiques. La WTRU peut recevoir une requête de transmission de SRSp au moment configuré (par exemple, Ts intervalles à partir du moment où la WTRU reçoit la requête) ou à un moment absolu. La WTRU peut envoyer une requête de ressources de liaison montante pour transmettre le SRSp indiquant le temps de début déterminé par Ts et la durée de la transmission SRSp. La WTRU peut recevoir plus d'une ressource de liaison montante (par exemple, des ressources de temps et de fréquence), chaque ressource pouvant être associée à un indice. La WTRU peut recevoir une commande par l'intermédiaire d'un RRC/MAC-CE indiquant l'indice de la ressource à activer pour une transmission SRSp à partir du réseau. La WTRU peut transmettre un SRSp au moment configuré. La WTRU peut mettre fin à une transmission SRSp une fois qu'une condition de terminaison est satisfaite.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US202363456973P | 2023-04-04 | 2023-04-04 | |
| US63/456,973 | 2023-04-04 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024211545A1 true WO2024211545A1 (fr) | 2024-10-10 |
Family
ID=90923944
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2024/023038 Pending WO2024211545A1 (fr) | 2023-04-04 | 2024-04-04 | Requête de planification pour srs |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2024211545A1 (fr) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022031974A1 (fr) * | 2020-08-05 | 2022-02-10 | Idac Holdings, Inc. | Procédés de configuration de signal de référence dans des systèmes sans fil |
| WO2022031889A1 (fr) * | 2020-08-05 | 2022-02-10 | Idac Holdings, Inc. | Gestion de signaux de référence de positionnement dans des systèmes sans fil |
| WO2023014795A1 (fr) * | 2021-08-03 | 2023-02-09 | Interdigital Patent Holdings, Inc. | Procédés et appareil pour la prise en charge d'un positionnement collaboratif |
-
2024
- 2024-04-04 WO PCT/US2024/023038 patent/WO2024211545A1/fr active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022031974A1 (fr) * | 2020-08-05 | 2022-02-10 | Idac Holdings, Inc. | Procédés de configuration de signal de référence dans des systèmes sans fil |
| WO2022031889A1 (fr) * | 2020-08-05 | 2022-02-10 | Idac Holdings, Inc. | Gestion de signaux de référence de positionnement dans des systèmes sans fil |
| WO2023014795A1 (fr) * | 2021-08-03 | 2023-02-09 | Interdigital Patent Holdings, Inc. | Procédés et appareil pour la prise en charge d'un positionnement collaboratif |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240188153A1 (en) | Nr positioning - methods for resource provision in sidelink positioning | |
| JP7723085B2 (ja) | 無線システムにおける測位 | |
| KR102871859B1 (ko) | 연관된 파라미터들이 미리 결정된 범위 내에 있는 조건에서 sl-prs의 송신 | |
| US20250151010A1 (en) | METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR NEW RADIO (NR) Uu PHASE-BASED POSITIONING | |
| US20250004090A1 (en) | Estimation of obstacle location | |
| WO2023014566A1 (fr) | Activation de positionnement dans un spectre sans licence | |
| WO2025034644A1 (fr) | Motifs de blocage de prs pour sbfd | |
| EP4548529A1 (fr) | Procédés et appareils de sélection de ressources et de régulation de congestion pour sl-prs | |
| WO2024211545A1 (fr) | Requête de planification pour srs | |
| WO2024211548A1 (fr) | Requête de rapport de mesure d'une autre unité d'émission/réception sans fil | |
| WO2024211543A1 (fr) | Réception de prs et transmission de srsp planifiées | |
| WO2024211333A1 (fr) | Détermination de l'inclusion d'une mesure pru dans rapport de positionnement de liaison latérale | |
| WO2025034823A1 (fr) | Acquisition de canal sl-u avec une fenêtre multi-priorité | |
| WO2024186442A2 (fr) | Saut de fréquence de liaison montante adaptatif | |
| WO2025080289A2 (fr) | Évitement de collision pour saut de fréquence de liaison montante adaptatif | |
| EP4666528A2 (fr) | Saut de fréquence de liaison montante adaptatif | |
| WO2024211342A1 (fr) | Sélection d'une pru sur la base d'états de canal | |
| WO2024173141A1 (fr) | Sélection de motif de saut pour saut de fréquence de liaison montante adaptatif | |
| WO2024211337A1 (fr) | Détermination d'une mesure de positionnement pour calcul de positionnement | |
| WO2024211399A1 (fr) | Commande de puissance de transmission de prach sur la base d'une différence de temps entre des ordres de pdcch | |
| WO2025034734A1 (fr) | Procédés et appareils de mesure et de rapport de positions d'obstacles | |
| WO2025034850A1 (fr) | Procédés pour activer/désactiver une transmission par téléversement dans des symboles en duplex intégral de sous-bande avec des signaux de référence de téléchargement sur la base d'un état de protection de symboles de référence | |
| WO2024211401A1 (fr) | Commande de puissance de transmission de prach avec un indice de transmission dans un ordre de pdcch | |
| WO2025034839A1 (fr) | Procédés pour activer/désactiver une transmission par téléversement dans des symboles en duplex intégral de sous-bande avec des signaux de référence de téléchargement sur la base d'une relation spatiale | |
| KR20250048455A (ko) | 사이드링크 포지셔닝을 위한 오류 전파 방지 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 24722930 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |