Phase tracking reference signal transmission
By maintaining consistent PT-RS density through RB offset determination, the solution addresses high propagation losses in advanced wireless systems, ensuring reliable phase tracking and signal integrity in high-frequency communications.
Patent Information
- Application Number
- JP2023173834
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-08-21
- Filing Date
- 2023-10-05
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2038-11-14
AI Technical Summary
Advanced wireless systems face challenges with high propagation losses at frequencies above 6GHz, especially in outdoor environments, necessitating effective phase tracking reference signals (PT-RS) to maintain consistent performance.
The number of phase tracking reference signals (PT-RS) is maintained constant across multiple slots by determining the RB offset value based on WTRU-ID modulo the maximum RB offset value, ensuring consistent PT-RS density and distribution.
This approach ensures reliable phase tracking across varying bandwidths and environments, mitigating propagation losses and maintaining signal integrity in high-frequency wireless communications.
Smart Images

Figure 0007583138000085 
Figure 0007583138000086 
Figure 0007583138000087
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 62,586,642, filed November 15, 2017, and U.S. Patent Application No. 62 / 720,614, filed August 21, 2018, the contents of which are incorporated herein by reference. [Background technology]
[0002] In advanced wireless systems, there may be high data requirements for spectrum above 6 GHz frequencies to take advantage of the wide bandwidth available. One challenge of using these frequencies is that there may be large propagation losses, especially in outdoor environments, due to the higher free space path loss at higher frequencies. Systems, methods, and devices may be used to address these issues. Summary of the Invention [Problem to be solved by the invention]
[0003] A system, method and device are provided that ensures that the number of phase tracking reference signals (PT-RS) is the same for multiple slots.
[0004] Systems, methods and devices are provided for ensuring that the number of Phase Tracking Reference Signals (PT-RS) is the same for multiple slots. A wireless transmit / receive unit (WTRU) can receive control information including a number of scheduled resource blocks (RBs) and then determine a PT-RS density based on the number of scheduled RBs. The WTRU can determine an RB offset value for the WTRU based on a WTRU-ID modulo a maximum RB offset value, where the maximum value of the RB offset value can be based on at least one of the number of scheduled RBs and the PT-RS density. The WTRU can then transmit or receive a signal with a PT-RS based on the RB offset value. Effect of the Invention
[0005] A system, method and device are provided that ensures that the number of phase tracking reference signals is the same for multiple slots. [Brief description of the drawings]
[0006] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numbers refer to similar elements and in which: [Figure 1A] FIG. 1 illustrates an example communication system in which one or more embodiments may be implemented. [Figure 1B] 1A illustrates an exemplary wireless transmit / receive unit (WTRU) for use within the communications system of FIG. 1A, according to an embodiment. [Figure 1C] FIG. 1B illustrates an exemplary Radio Access Network (RAN) and Core Network (CN) for use within the communications system of FIG. 1A, according to an embodiment. [Figure 1D] FIG. 1B is a system diagram illustrating a further example RAN and CN for use within the communication system of FIG. 1A, according to an embodiment. [Diagram 2] FIG. 1 is an exemplary PT-RS time density diagram. [Diagram 3] FIG. 13 is a diagram of an example chunk-based pre-DFT PT-RS for DFT-s-OFDM with N chunks. [Figure 4] FIG. 1 is a diagram of an exemplary normal cyclic prefix (CP). [Diagram 5] FIG. 1 is a diagram of an exemplary extended CP (virtual CP). [Figure 6] 1 is a set of diagrams of exemplary simple UW and CW combinations. [Figure 7] FIG. 1 illustrates an example perturbation technique. [Figure 8] FIG. 1 is a diagram of an example dynamic approach for DFT-s-OFDM. [Figure 9] FIG. 1 is a diagram of an example dynamic approach for DFT-s-OFDM. [Figure 10] FIG. 1 is a diagram of an example of PT-RS frequency density. [Figure 11A] FIG. 13 is a diagram showing an example of an RB offset value. [Figure 11B] FIG. 13 illustrates an example process for maintaining the same number of PT-RS for a scheduled bandwidth. [Figure 12] FIG. 13 is a diagram of an example cyclic shift of an RB including a PT-RS. [Figure 13] A diagram of an example of PT-RS mapping for seven RBs with different RB offset values. [Figure 14] A diagram of an example PT-RS mapping for 7 RB and 13 RB width scheduling. [Figure 15] A diagram of an example PT-RS mapping for seven RBs with dynamic RB offset values. [Figure 16] A diagram of an example of PT-RS mapping for 13 RB transmission with dynamic RB offset value. [Figure 17] FIG. 13 is a diagram of an example PT-RS frequency location based on symbol location. [Figure 18] FIG. 13 is a diagram of an example PT-RS frequency density based on RBG. [Figure 19]FIG. 13 is a diagram of an example PT-RS generation for pi / 2 BPSK data modulation. [Figure 20] FIG. 13 is a diagram of an example PT-RS generation for pi / 2 BPSK data modulation and OCC. [Figure 21] FIG. 13 is an example of a loop through the OCC. [Figure 22] FIG. 1 shows an example constellation for a pi / 2 BPSK and QPSK constellation. [Figure 23] FIG. 1 is a diagram of an example of a common PT-RS design. [Figure 24] FIG. 1 is a diagram of an exemplary OCC application. [Diagram 25] FIG. 1 is a diagram of an exemplary OCC application. [Figure 26] FIG. 2 shows an example constellation of an alternative pi / 2 BPSK constellation. [Figure 27] 1 is a diagram of an example generation of a CP extended RS based on a pre-determined RS using a CP extender block. [Figure 28] FIG. 13 is a diagram of an example signal structure for implementing a virtual CP using a CP extender block. [Figure 29] 13 is a diagram of an example division of a waveform matrix to derive a CP extender block. [Diagram 30] FIG. 1 is a transmission diagram of an example NR numerology with a virtual CP. [Diagram 31] FIG. 1 is a signal diagram of an example NR numerology with a virtual CP. [Diagram 32] FIG. 13 illustrates an exemplary doubling of CP extension using a CP extension RS. [Diagram 33] FIG. 1 is a diagram of an exemplary CP-enhanced PT-RS design. [Diagram 34] FIG. 13 is a diagram of an example signal structure for a virtual CP using a CP extender block. [Diagram 35] A diagram of an example of a division of a waveform matrix to derive a CP extender block for a complete PT-RS. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0007] 1A illustrates an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tailed unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, and filter bank multicarrier (FBMC).
[0008] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals, and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, IoT devices, watches or other wearables, head mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, and devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as UEs.
[0009] The communication system 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 other networks 112. For example, 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, an NR NodeB, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0010] As discussed herein, a wireless device may be any node on a network that performs wireless communication, such as a WTRU or a base station as discussed herein.
[0011] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or 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 cells (not shown). These frequencies may be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectrum. A cell may provide coverage for wireless services in a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ MIMO technology and utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.
[0012] 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).
[0013] More specifically, as noted above, the communication 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, etc. For example, the base stations 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).
[0014] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE Advanced (LTE-A) and / or LTE Advanced Pro (LTE-A Pro).
[0015] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology, such as New Radio (NR) radio access, capable of establishing the air interface 116 using NR.
[0016] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE and NR radio access together, e.g., using a dual connectivity (DC) principle. Thus, the air interface utilized by the 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., eNBs and gNBs).
[0017] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.
[0018] The base station 114b of FIG. 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT for facilitating wireless connectivity within a localized area, such as an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use with drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.11, to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.15, to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.
[0019] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, 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 different throughput requirements, latency requirements, error resilience requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, charging services, mobile location services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high level security functions such as user authentication. Although not shown in FIG. 1A, it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.
[0020] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as TCP, UDP, and / or IP in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs that may employ the same RAT as the RAN 104 / 113 or a different RAT.
[0021] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a that may employ a cellular-based wireless technology and a base station 114b that may employ an IEEE 802 wireless technology.
[0022] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include, among other things, 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 GPS chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the above elements while remaining consistent with an embodiment.
[0023] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. 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. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be incorporated together in an electronic package or chip.
[0024] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0025] 1B as a single element, 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.
[0026] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.
[0027] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an 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 in and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include RAM, 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, or the like. In other embodiments, the processor 118 may access information in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and may store data in those memories.
[0028] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0029] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding a current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by way of any suitable location determination method while remaining consistent with an embodiment.
[0030] The processor 118 may be further 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. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a USB port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (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, etc. The peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, 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.
[0031] 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 a particular subframe for both the UL (e.g., for transmission) and the downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing by a processor (e.g., by a separate processor (not shown) or by the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio, for which transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or the downlink (e.g., for reception)) may be parallel and / or simultaneous.
[0032] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As mentioned above, the RAN 104 may employ E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with the CN 106.
[0033] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0034] 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, etc. As shown in FIG 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0035] 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (i.e., PGW) 166. Although each of the above elements is shown as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.
[0036] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, etc. 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.
[0037] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an 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 the user plane during inter-eNode B handover, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.
[0038] The SGW 164 may be connected to a PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0039] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. The CN 106 may also provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.
[0040] Although the WTRU is described in Figures 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications network.
[0041] In an exemplary embodiment, the other network 112 may be a WLAN.
[0042] 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 access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic to the STA originating from outside the BSS may arrive through the AP and be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP to be delivered to the respective destination. Traffic between STAs in the BSS may be sent through the AP, e.g., a source STA may send traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent (e.g., directly) between a source STA and a destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 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) in or using the IBSS may communicate directly with each other. IBSS mode communication is sometimes referred to herein as an "ad-hoc" mode of communication.
[0043] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, 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 bandwidth) or may be dynamically set by signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In a particular representative embodiment, for example, in an 802.11 system, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) may be implemented. In CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.
[0044] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, by combining a primary 20 MHz channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.
[0045] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz channels may be formed by combining contiguous 20 MHz channels. The 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, sometimes referred to as an 80+80 configuration. In the 80+80 configuration, the data may be passed through a segment parser that can split the data into two streams after channel encoding. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately for each stream. The streams may be mapped to two 80 MHz channels and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration may be reversed and the combined data may be sent to the Medium Access Control (MAC).
[0046] Sub-1 GHz operation modes are supported by 802.11af and 802.11ah. In 802.11af and 802.11ah, the channel operating bandwidth and carriers are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have specific capabilities, including, for example, specific bandwidths and / or limited bandwidth support (e.g., support of only that bandwidth). MTC devices may include a battery with a battery life above a threshold (e.g., having a very long battery life).
[0047] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA that supports the smallest bandwidth operating mode among all STAs operating in the BSS. In an 802.11ah example, the primary channel may be 1 MHz wide for a STA (e.g., an MTC type device) that supports 1 MHz mode (e.g., only supports 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) setting may depend on the state of the primary channel. If the primary channel is busy, e.g., due to a STA (that only supports 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band may remain idle and available.
[0048] In the United States, the available frequency bands that may be used by 802.11ah are 902MHz to 928MHz. In South Korea, the available frequency bands are 917.5MHz to 923.5MHz. In Japan, the available frequency bands are 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz depending on the country code.
[0049] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As mentioned above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.
[0050] The RAN 113 may include gNBs 180a, 180b, 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may transmit wireless signals to and / or receive wireless signals from the WTRU 102a using, for example, multiple antennas. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, and the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).
[0051] The WTRUs 102a, 102b, 102c may communicate with the 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 the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including varying numbers of OFDM symbols and / or lasting varying lengths of absolute time).
[0052] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing any other RAN (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with other RANs, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0053] 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 for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPFs) 184a, 184b, routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.
[0054] 1D 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. Although each of the above elements is shown as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0055] 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 act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service being utilized by the WTRUs 102a, 102b, 102c. Different network slices may be established for different use cases, such as, for example, services relying on ultra-reliable low-latency (URLLC) access, services relying on enhanced large capacity mobile broadband (eMBB) access, and / or services for machine type communications (MTC) access, etc. 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.
[0056] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0057] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface and 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 UPFs 184a, 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, etc.
[0058] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. The CN 115 may also provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the local DNs 185a, 185b.
[0059] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices 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. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.
[0060] The emulation device may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, the one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. The one or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing and / or may perform testing using wireless wireless communication.
[0061] The emulation device or devices may perform one or more functions, inclusive, without being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation device may be utilized in a test laboratory and / or in a test scenario in a non-deployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. The emulation device or devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation device to transmit and / or receive data.
[0062] Generally, in LTE, Orthogonal Frequency Division Multiplexing (OFDM) may be used for downlink (DL) transmission, while Discrete Fourier Transform (DFT)-s-OFDM may be used for uplink (UL) transmission. In conventional Cyclic Prefix (CP) DFT-s-OFDM (sometimes called Single Carrier Frequency Division Multiple Access with Multiple Access (SC-FDMA)), data symbols may be spread with a DFT block and then mapped to corresponding inputs of an IDFT block. The CP may be prepended to the beginning of a symbol to avoid inter-symbol interference (ISI) and enable one-tap frequency domain equalization (FDE) at the receiver.
[0063] In downlink transmission, reference symbols may be scattered across specific subcarriers (i.e., one OFDM symbol may have subcarriers loaded with data and reference symbols). Common reference symbols may be transmitted on subcarriers distributed across the system bandwidth, and WTRU-specific reference signals may be distributed on subbands assigned to a particular WTRU.
[0064] 3GPP can address an advanced wireless communication system called New Radio (NR). NR applications can be aggregated into several categories: enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Under each category, there can be a broad set of applications that consider different needs and deployment scenarios that call for specific performance requirements. For example, mMTC and URLLC applications range from automotive to health, agriculture, utilities, and logistics industries.
[0065] To meet high data rate requirements, spectrum above 6 GHz frequencies may be used to take advantage of the wide bandwidth of the spectrum. One challenge with using these higher frequencies is that there can be significant propagation losses, especially in outdoor environments, due to the higher free space path loss at higher frequencies.
[0066] Beamforming (e.g., analog beams) can be a solution to address the large path loss at higher frequencies, since the path loss can be compensated for without increasing the transmit power. Since beams are used to compensate for the path loss, all downlink and uplink channels can be based on beams.
[0067] In one scenario, device-to-device (D2D) and / or vehicle-to-everything (V2X) communications may employ LTE. For sidelink transmission and / or reception, one or more of the following physical channels may be used: sidelink primary sync signal (SPSS) and / or sidelink secondary sync signal (SSSS), physical sidelink broadcasting channel (PSBCH), physical sidelink control channel (PSCCH), physical sidelink shared channel (PSSCH), and / or physical sidelink shared channel (PSDCH).
[0068] The sidelink may support one or more modes (e.g., up to four modes). A first and / or a second mode (e.g., mode 1 and / or mode 2) may be used for D2D communication. D2D communication may require a power-efficient and reliable transmission. D2D communication may be delay tolerant and / or may be used for low mobility. Mode 1 may be based on or use eNB scheduling for sidelink transmission, where resources for sidelink transmission may be scheduled by the eNB over DCI. Mode 2 may be based on or use WTRU resource selection (e.g., autonomous resource selection) in a resource pool that may be configured. Mode 1 may be used when WTRUs for sidelink transmission are located under or within eNB coverage such that the WTRUs are able to receive control signals from the eNB. Mode 2 may be used when WTRUs for sidelink transmission are outside eNB coverage and / or when they are within coverage.
[0069] A third and / or fourth mode (e.g., Mode 3 and / or Mode 4) may be used for V2X communications, e.g., to support high mobility and / or low latency. Mode 3 may use eNB scheduling for sidelink resource determination. Mode 4 may use WTRU resource selection (e.g., autonomous resource selection).
[0070] For modes that use scheduling (e.g., Mode 1 and / or Mode 3), a sidelink WTRU may receive a resource grant for sidelink transmissions. The WTRU may monitor (e.g., monitor for) a resource grant in a search space configured for the Uu interface.
[0071] In one or more embodiments, a phase tracking reference signal (PT-RS) may be used to measure, track, and / or estimate phase noise to compensate for phase noise prior to demodulation of a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH). The PT-RS may be used interchangeably with a phase noise reference signal (PNRS) and a reference signal (RS).
[0072] The PT-RS may be transmitted within a scheduled bandwidth for the PDSCH or PUSCH. Transmission of the PT-RS within a scheduled bandwidth for the PDSCH or PUSCH may be turned on / off by a node, such as a gNB, via higher layer signaling. If transmission of PT-RS in the scheduled bandwidth is turned on, the presence of PT-RS and / or density of PT-RS (e.g., time and / or frequency) in the scheduled bandwidth for the PDSCH or PUSCH may be determined based on one or more of the scheduled number of resource blocks (RBs) (e.g., also known as the scheduled bandwidth and / or physical resource blocks (PRBs)), the modulation and coding scheme (MCS) level indicated for the scheduled PDSCH and / or PUSCH, the numerology (e.g., subcarrier spacing, slot length, etc.), the WTRU capabilities (e.g., whether or not it supports PT-RS), the demodulation reference signal (DM-RS) density that may be used for demodulation, the number of scheduled layers (e.g., transmission rank of the PDSCH or PUSCH), and / or the presence of UCI in the PUSCH and its associated UCI type (e.g., HARQ-ACK or CSI).
[0073] When a PT-RS is within a scheduled bandwidth for a PDSCH or PUSCH, a subset of the scheduled RBs may include, contain, or transmit the PT-RS. The subset of PT-RS RBs may be determined based on one or more of an RB offset or the scheduled bandwidth.
[0074] With respect to the RB offset, the subset of RBs with the PT-RS may be located every K RBs in the scheduled bandwidth, where the RBs are indexed from the smallest RB index in the scheduled RBs to an RB with a larger index, regardless of whether the scheduled RBs are contiguous or distributed. The RB offset may be a starting RB index for including the PT-RS. As discussed herein, the RB offset, PRB offset, starting RB offset, and starting RB index may be used interchangeably.
[0075] For a scheduled bandwidth, the number of RBs that may contain, include, or transmit a PT-RS may be determined based on the scheduled bandwidth. If the scheduled bandwidth is less than a first threshold, then a first number of RBs may contain a PT-RS, if the scheduled bandwidth is equal to or greater than the first threshold and less than a second threshold, then a second number of RBs may contain a PT-RS, and so on. The subset may include a situation where all scheduled RBs (or RBs) may contain, include, or transmit a PT-RS.
[0076] When a PT-RS is present within a scheduled bandwidth for a PDSCH or PUSCH, a subset of symbols (e.g., CP-OFDM symbols or DFT-s-OFDM symbols) may include the PT-RS. The presence of the PT-RS in a symbol may be determined based on one or more of the MCS level (or modulation order) of the scheduled PDSCH or PUSCH, the presence of the DM-RS in the symbol (e.g., if the symbol includes a DM-RS, then the PT-RS may not be transmitted in the symbol), and / or a PT-RS density determined based on one or more scheduling parameters. The PT-RS density, time / frequency location, and / or use or non-use of DFT precoding may depend on the waveform used.
[0077] In one scenario, the PT-RS may be used for PDSCH or PUSCH transmission when a CP-OFDM waveform is used. One or more subcarriers in the RB may be used for PT-RS transmission, and the same subcarrier position may be used across consecutive OFDM symbols that may be determined for PT-RS transmission.
[0078] FIG. 2 shows some examples of PT-RS time density. There are three example grids 202, 204, and 206, where the horizontal axis 201 of each grid can be OFDM symbols and the vertical axis 203 is subcarriers. For each example, there is a grid of resource elements (REs), and the shaded blocks can represent REs that contain PT-RSs. Looking from left to right, in example 202, there can be a PT-RS located every symbol (e.g., OFDM symbol), in example 204, there can be a PT-RS every two symbols, and / or in example 206, there can be a PT-RS every four symbols. The PT-RS time density can be determined based on the MCS threshold, for example, as shown in Table 1 below. I MCS may be the MCS level used, determined, or indicated for the PUSCH or PDSCH in the associated DCI. PT-RSthMCS1, PT-RSthMCS2, PT-RSthMCS3, and PT-RSthMCS4 may be configured via higher layer signaling or DCI and may be referred to as thresholds for determining the time density of the PT-RS. In the absence of configuration or indication, a default configuration (e.g., per symbol) may be used.
[0079] [Table 1]
[0080] For CP-OFDM and DFT-s-OFDM, when a PT-RS is present, the PT-RS mapping pattern may start at the first symbol containing a PDSCH / PUSCH in the slot and may be mapped every L_{PT-RS} symbols. The PT-RS mapping pattern may be restarted at each symbol containing a DMRS and may be mapped every L_{PT-RS} symbols for the symbol containing a PT-RS. In the case of two adjacent DMRS symbols, the PT-RS pattern may be restarted using the second of the two DMRS symbols as a reference. When the PT-RS time density is less than 1, the symbol immediately after the frontloaded DMRS and the symbol immediately after the additional DMRS, if present, may not contain a PT-RS. A PT-RS that follows the mapping pattern may not be transmitted in an OFDM symbol containing a PDSCH / PUSCH DMRS. A PT-RS that follows the mapping pattern may not be transmitted in a resource element (RE) that overlaps with a configured control channel resource set (CORESET).
[0081] The PT-RS frequency density may be determined based on the number of scheduled RBs as shown in Table 2 below. RB may be the number of scheduled RBs. PT-RSthRB0, PT-RSthRB1, PT-RSthRB2, PT-RSthRB3, and PT-RSthRB4 may be thresholds for determining the frequency density of the PT-RS, which may be configured via RRC signaling or indicated in the associated DCI. In the absence of configuration or indication, a default configuration (e.g., the second RB) may be used.
[0082] [Table 2]
[0083] 3 illustrates an example process in which chunk-based pre-DFT PT-RS insertion may be used to generate a DFT-s-OFDM waveform. The PT-RS input / output 322 is indicated by an arrow and gray shading, and the data input / output 321 is indicated by a black arrow. In general, in LTE, the process of forming a waveform may include first spreading data symbols 302 in a DFT block 304 and then mapping to corresponding inputs of an IDFT block 306. A CP 308 may be prepended to the beginning of a symbol to avoid inter-symbol interference (ISI) and enable one-tap frequency domain equalization (FDE) at the receiver.
[0084] A PT-RS pattern (e.g., chunk-based pre-DFT PT-RS pattern) may be determined based on a chunk number (X) 310, a chunk size (V) 312, and a chunk position. X PT-RS chunks 310, such as PT-RS chunk #1 311, may be inserted before the DFT block 304. The PT-RS chunks and data will go along the same process as described above to form a waveform. The chunks are composed of tones, and for each chunk, the size may be V PT-RS tones. For each chunk, there may be V PT-RS tones before the DFT input, and in the example of FIG. 3, the chunk size is V=3, as indicated by the three long dotted arrows per PT-RS chunk, which is also shown in the resulting waveform in the DFT-S-OFDM symbol 313, where PT-RS chunk #1 311 is in the first three shaded blocks and PT-RS chunk #X is at the end.
[0085] The location of the chunks in the DFT input may be determined based on the scheduled RBs, the chunk size (V) 312, and / or the chunk number (X) 310. For example, two values of V, V1 and V2, may be used, and the location of the chunks may be determined based on the V value as follows: when V=V1, the samples in the DFT domain may be divided into X intervals, and the chunks may be placed at the Head (first V samples), Middle (middle V samples), or Tail (last V samples) of each interval; when V=V2, the samples in the DFT domain are divided into X intervals, and in the first interval, the chunks are placed at the Head (first V samples), in the last interval, the chunks are placed at the Tail (last V samples), and in the remaining intervals, the chunks are placed at the middle of each of the two intervals.
[0086] The PT-RS pattern defines a threshold N per BWP that indicates the values of X and V that the WTRU should use depending on the scheduled BW according to Table 3 below. RBn The time may be determined based on the scheduled BW having a set of (n=0,1,2,3,4). Y represents an arbitrary value. In one example, the value of Y may be 8.
[0087] [Table 3]
[0088] FIG. 4 shows a diagram of a signal with a normal cyclic prefix (CP). Time 401 is shown on the horizontal axis. In any diagram discussed herein, each portion of any given symbol shown in the time domain signal diagram may be shaded with a pattern to indicate similarity. As shown, there are two symbols of the signal (i.e., DFT-s-OFDM, OFDM), symbol 402 and symbol 403, with CP 406 and CP 407, respectively. In normal CP operation, the size of each CP may be G, and the inverse discrete Fourier transform (IDFT) output may be extended by prepending a replica of the last portion of the IDFT output. CP 406 and CP 407 replicate the ends and continue to N-IDFT output 404 and N-IDFT output 405, respectively, with the last portions being 413 and 415, respectively, indicated by arrows 410 and 411, respectively. At the receiver side, the location of the DFT window may be on the first symbol and may not take samples from subsequent symbols, and each N-IDFT output 404, 405 may be within the receiver (RX) DFT window 408, 409, respectively. However, if the CP size G is not smaller than the number of taps of the multipath channel, the receiver may suffer from ISI. In some cases, the normal CP size may not be sufficient. For example, if the communication environment is outdoors or the link is established on a non-line-of-sight (LOS) path, the maximum excess delay of the multipath channel may increase substantially. In these cases, the duration of the CP may not be large enough to handle the delay spread of the channel, and this insufficient CP size may lead to inter-symbol interference (ISI).
[0089] FIG. 5 shows a diagram of a signal with an extended CP (e.g., a virtual CP). Time 501 is shown on the horizontal axis. As shown, there is a symbol 502 of the signal with a CP 506 that can be extended to a length 523. Note that the N-IDFT output 505 and a second symbol 503 with CP 507 are shown to provide context as to where the extension comes from with respect to the entire signal. CP extension (also known as a virtual CP) can be used to address when the CP size is not long enough. The goal of virtual CP can be to increase the effective CP length of block-based symbols (e.g., DFT-s-OFDM, OFDM) to increase their robustness against multipath channels. In the example shown in FIG. 5, the CP 506 of length G can be extended by H samples to a total extended CP length 523. The N-IDFT output 504 of the IDFT may be extended by prepending a last replica 522 of the N-IDFT output 504, similar to the example shown in Figure 4, but the extended CP region may be forced to be identical due to the special structure of the IDFT output. Note also that the RX DFT window 508 may be shifted by H samples.
[0090] This approach may also be advantageous to maintain receiver-side hardware complexity since the basic receiver operation does not need to be changed. Another advantage of the virtual CP may be reduced out-of-band emissions (OOBE) by forcing two subsequent symbols to be consecutive, since samples in the RX DFT window should be consecutive to decode the symbol without interference.
[0091] FIG. 6 shows an example of a simple unique word (UW) and cyclic prefix (CW) combination. In one approach, the UW and CP may be combined as shown. Looking at the transmit (TX) block diagram 601, PT-RS 602a and 602b are M ) M-DFT604 to output N-IDFT606(
[0092]
number
[0093] where (·) H is a Hermitian operator, and F N 612 and 614. Without any special design in the reference symbols, if the CP 611 of duration G is shorter than the tail 614 of duration T, the depicted portions can be nearly identical and may be considered to be of extended CP duration.
[0094] For example, looking at frame 630 of the resulting time domain signal, e The expanded CP620 is the previous symbol 631 i-1 The tail of the 631 and its current symbol i While this approach appears to achieve the goal of a virtual / extended CP 620, the receiver (RX) may be adversely affected, which may be undesirable, since the RX DFT window 621 size changes from N to N+G and therefore the receiver structure may be affected for the extended CP reception. Also, the receiver may have to re-enter the current symbol 631. i and the next symbol 631 i+1 This can be adversely affected because the transition between CPs may not be continuous without special design, and thus data symbols such as 613 may be interfered with. Thus, the receiver may need to perform extra operations to recover the data, which may not be ideal.
[0095] FIG. 7 shows an example of a perturbation approach. In this approach, each OFDM symbol may be perturbed by some perturbation vector to achieve continuity between adjacent symbols (i.e., also achieving CP extension). In the example shown in FIG. 7, a transmitter diagram 701 of the proposed approach and a corresponding time domain signal 730 are shown on the left and right, respectively. As with other transmission processes discussed herein, the data is transmitted in a time domain (
[0096]
number
[0097] The inputs may enter an IDFT block 716 (represented by N+G), resulting in symbols of length N. The symbols may pass through a Perturbation Vector Generator block 722 and / or a delay may be introduced in block 720. A CP may be added in block 708, resulting in symbols of length N+G.
[0098] The resulting signal 730 may, for example, include the previous symbol 731 i-1 , current symbol 731 i , and the next symbol 731 i+1 It should be noted that each portion of any given symbol shown in the time domain signal 730 may be shaded with a pattern to indicate similarity.
[0099]
number
[0100] exists for each symbol. i is the unperturbed signal X to be manipulated i Element 760 may be a part of b i A i-1 , which may be the output of a perturbation vector generator that replaces the previous perturbed OFDM symbol
[0101]
number
[0102] The first part of the i-1 The previous symbol (i.e.
[0103]
number
[0104] ) and the current symbol (
[0105]
number
[0106] ), the beginning of the CP of the current or i-th perturbed OFDM symbol is also i-1 CP can be expressed as the symbol
[0107]
number
[0108] Since it is a copy of the last part of the vector
[0109]
number
[0110] is the aft tail position of 731b i-1 For this purpose, the IDFT706 output (i.e., X i ) is the a of the i-1-th perturbed OFDM symbol i-1 can be perturbed as a function of
[0111] This approach may work for any CP duration size, but may also present some problems. One problem may be that since it is a dynamic method (i.e., the perturbation is a function of the data), it may need to be calculated for each individual OFDM symbol, which may be processing intensive. Furthermore, since it is a dynamic method, it may not match the reference signal (RS). Another problem may be that the perturbation signal cannot be used as the RS. Another problem may be that since the perturbation vector follows an arbitrary structure, the receiver may need to perform extra operations to remove the effect of interference due to the perturbation vector.
[0112] FIG. 8 shows an example of a dynamic approach for DFT-s-OFDM. An example transmitter diagram 801 and corresponding time domain signal 830 are seen on the left and right of the figure, respectively. In this approach, the single carrier structure of DFT-s-OFDM may be utilized, and CP extension may be achieved by shifting the position of data symbols and reusing them in the previous and next DFT-s-OFDM symbols based on a specific rule for a particular CP length and DFT spreading size. As with the other transmission processes discussed herein, the transmitter diagram 801 includes a block D M (DFT)802, M f 804,
[0113]
number
[0114] The processes including (IDFT) 806 and CP 808 are executed in this order. f 804 is D M 802 output
[0115]
number
[0116] 806. In this approach, the symbol S at the input of the DFT-s-OFDM block 802 may be a subcarrier mapping operation. k is ordered as follows:
[0117]
number
[0118] Where:
[0119]
number
[0120] is a data symbol, k is the DFT-s-OFDM symbol index, and the CP length is
[0121]
number
[0122] should be set to
[0123] In the resulting time domain signal 830, as an example, the previous symbol 831 i-1 , current symbol 831 i , and the next symbol 831 i+1 It should be noted that each portion of any given symbol shown in the time domain signal 830 may be shaded with a pattern to indicate similarity. In the example shown, the symbol 831 i In a where k=2 k In the case of b k-1 f a2 is b1, and so on for the first other input of the transmitter diagram 801. And so on, for each element in the symbol, there can be a corresponding input, e.g., further using the example where k=2, f a2 is the current symbol 831 iAs shown, this method can achieve an extended CP 833, where the CP length (G) plus the tails (T) and (H) is the length of G taken from the other end 832. e (note the similar pattern in the extended CP 833 and the other end 832), which can be realized without complex operations at both the transmitter and the receiver, but may nevertheless also introduce undesirable constraints on the CP size G. Therefore, this approach may only be compatible with certain numerologies. Another possible problem with this approach may be generating the CP extension based on the data symbols. Therefore, this approach may only be compatible with certain PT-RS structures.
[0124] 9 shows an example of a static approach for DFT-s-OFDM. An example transmitter diagram 901 and corresponding time domain signal 930 can be seen on the left and right of the figure, respectively. As with the other transmission processes discussed herein, the transmitter diagram 901 includes a block D M (DFT)902, M f 904, and
[0125]
number
[0126] In this approach, the single carrier structure of DFT-s-OFDM may be utilized, and the CP extension shown in signal diagram 901 uses a CP block in the transmitter to convert the input data symbols into
[0127]
number
[0128] This can be achieved by replacing φ with a fixed RS.
[0129] In the resulting time domain signal 930, as an example, the previous symbol 931i-1 , current symbol 931 i , and the next symbol 931 i+1 Note that each portion of any given symbol shown in the time domain signal 930 may be shaded with a pattern to indicate similarity. Similar to the example shown in FIG. 8, this method can achieve an extended CP 933 and shows that the CP length (G) plus the tails (T) and (H) results in Ge being taken from the other end 932 (note the similar patterns in the extended CP 933 and the other end 932). This static method addresses the PT-RS design, but where the CP length is
[0130]
number
[0131] This can have drawbacks of the dynamic method, such as having to be set to
[0132] FIG. 10 shows an example of how PT-RS frequency density (K) may work with different bandwidth schedules. Specifically, PT-RS frequency density may be based on the number of scheduled RBs when the RB offset is "0" (i.e., starting from the first RB scheduled), and the following thresholds are configured: {PT-RSthRB0=2, PT-RSthRB1=6, PT-RSthRB2=12, PT-RSthRB3=16}. The RB index 1001 at the bottom indicates in which number of RBs the PT-RS 1010 is for any given configuration. Three example scenarios with different PT-RS densities are shown: every RB 1010 (i.e., K=1), every two RBs 1020 (i.e., K=2), and every four RBs 1030 (i.e., K=4). The PT-RS frequency density may not increase linearly as the number of scheduled RBs becomes larger. Also, the PT-RS frequency density may differ based on the RB offset. For example, the total number of PT-RS may be different for a WTRU with RB offset=0 and another WTRU with RB offset=1, but the number of RBs scheduled for both WTRUs may be the same.
[0133] The RB offset (e.g., starting RB index) may be used to randomize PT-RS interference (e.g., due to collisions between PT-RS) from a co-scheduled WTRU. The RB offset may be determined based on one or more WTRU-specific parameters. One such parameter may be WTRU-ID (e.g., temporary C-RNTI, C-RNTI, IMSI), where one or more WTRU-IDs may be used. For example, when the WTRU is in RRC idle mode, IMSI may be used as the WTRU-ID, and when the WTRU is in RRC connected mode, C-RNTI may be used. The temporary C-RNTI may be used to determine the RB offset for RACH msg2, 3, and / or 4 transmission / reception, and / or the C-RNTI may be used after the WTRU receives a C-RNTI configuration.
[0134] Additionally / alternatively, the RB offset may be determined based on a WTRU-specific parameter of a scrambling ID (e.g., a scrambling ID configured or indicated for a DM-RS), which may be configured in WTRU-specific RRC signaling or indicated in an associated DCI for PDSCH or PUSCH scheduling.
[0135] Additionally / alternatively, the RB offset may be determined based on a WTRU-specific parameter of a cell ID (e.g., a physical cell ID), where the physical cell ID may be determined during an initial access procedure or detected from a synchronization signal (SS).
[0136] Additionally / alternatively, the RB offset may be determined based on a WTRU-specific parameter of an SS block time index (e.g., SS / PBCH block index), which may be determined during the initial access procedure, and as discussed herein, SS block index, SS block time index, SS / PBCH block index, and SS / PBCH block time index may be used interchangeably.
[0137] Additionally / alternatively, the RB offset may be determined based on a WTRU-specific parameter of a bandwidth portion (BWP) index, e.g., where a WTRU may be configured with one or more BWPs, and a subset of the configured BWPs may be active simultaneously. An active BWP index, for which a WTRU may be configured or indicated to transmit and / or receive a PDSCH or PUSCH, may be used to determine the RB offset value. As discussed herein, BWP and carrier may be used interchangeably.
[0138] The default RB offset may be used before RRC connection setup or before the WTRU may be configured with WTRU-specific parameters. The default RB offset may be determined by at least one of a fixed RB offset (e.g., RB offset=0) and / or an RB offset determined based on one or more cell-specific parameters (e.g., a physical cell ID).
[0139] To determine the RB offset value, a maximum RB offset value may be determined, used, configured, or predefined. For example, if the WTRU-ID is used for the RB offset value determination, a modulo (mod) operation of the WTRU-ID with the maximum RB offset value (max_RB_offset) may be used (mod represents the modulus after division). As discussed herein, the modulo operation result produces a remainder, and a modulo operation with A and B may have A as the dividend and B as the divisor, and may be expressed interchangeably as A Mod B, (A) mod B, and / or mod(A,B).
[0140] For example, RB offset value = (n RNTI ) mod max_RB_offset, where n RNTI may be a C-RNTI or a temporary C-RNTI, or n RNTI may be the most significant bit (MSB) or least significant bit (LSB) of the C-RNTI or temporary C-RNTI. In either case, max_RB_offset may be a maximum RB offset value. In some cases, the max_RB_offset value may be implicitly determined based on one or more of the scheduled BW (e.g., number of scheduled RBs), PT-RS frequency density (e.g., PT-RS placed every K RBs), and / or WTRU-specific parameters, where K is a number between 0 and 100, as discussed herein.
[0141]
number
[0142] In some cases, the max_RB_offset value, which may be implicitly determined, may be overridden by a max_RB_offset value configured at a higher layer.
[0143] The RB offset value may be limited to a set of RB offsets that may be configured, determined, or used. Further, a subset of the set of RB offsets may be determined or used based on at least one of the scheduled BW, frequency density, and / or WTRU-specific parameters. The RB offsets may be limited to the set / subset, determined, and / or configured in one or more ways discussed herein.
[0144] In one method, a set of RB offsets may be defined, determined, or used based on the max_RB_offset value. For example, the set of RB offsets may be {0, 1, ..., max_RB_offset}, which would constitute a complete set of possible values. In one example, max_RB_offset may be a frequency density K, where max_RB_offset = K, which would constitute a set of RB offsets {0, 1, ..., K}.
[0145] Alternatively, the set and / or subset of RB offsets may be determined based on the scheduled bandwidth N RB and the PT-RS frequency density K. In one example, if a first condition is met, the first subset may be {0}, where the first condition is: (N RB +1) mod K=0. In another example, a second subset {0, 1} may be used if a second condition is met, where the second condition is (N RB +2) mod K=0. In another example, if the third condition is met, then the set (i.e., the entirety) of RB offsets {0, 1, ..., max_RB_offset} may be used, where the third condition is: (N RB) mod K=0.
[0146] In another method, the RB offset value is RB offset value=(n RNTI ) mod max_RB_offset_S, where max_RB_offset_S may be the number of RB offset values in the subset.
[0147] Alternatively, a subset of the set of RB offsets may be configured via higher layer signaling, e.g., a bitmap may be used to indicate the subset of RB offset values.
[0148] In another approach for limiting the RB offset value, the max_RB_offset value for a set of RB offsets where the set of RB offsets is the complete set of values {0,1,...,max_RB_offset} may be determined based on the number of RBs that do not contain a PT-RS after the last RB that contains a PT-RS with RB offset=0. For example, returning to FIG. 10, in scenario 1030, there are 16 RBs scheduled, where the max_RB_offset value can be 3 since all RBs after the last RB 12 (i.e., RBs 13, 14, and 15) do not contain a PT-RS. In another example shown in scenario 1030, when 15 RBs are scheduled, the max_RB_offset value can be 2 since that is the number of RBs after the 12th RB, RBs 13 and 14, that do not contain a PT-RS. In this approach, in one method, max_RB_offset can be determined based on the number of RBs after the 12th RB, RBs 13 and 14, that do not contain a PT-RS. RB mod K-1, where K may be determined based on frequency density (e.g., the PT-RS is placed every K RBs), and / or N RB may be the number of scheduled RBs. Alternatively, the RB offset value = (n RNTI ) mod max_RB_offset.
[0149] FIG. 11A shows an example of max_RB_offset value determination (or limitation / restriction) based on scheduled RBs and PT-RS frequency density. Similar to FIG. 10, the shaded blocks may represent PT-RSs in the RBs. In scenario 1120, there may be 8 RBs and a PT-RS every 2 RBs (i.e., K=2), and the total number of PT-RSs may be 4 when the offset is 0, as shown by line 1121, and the number of PT-RSs may also be 4 when the offset is 1, as shown by line 1122. In scenario 1120, the PT-RS density is divided evenly into the number of scheduled RBs with no remainder (i.e., N RB Note that, mod K=0), so that max_RB_offset is equal to the PT-RS density K=2; in other words, when K=2, the RB offset is the first two possible values, where the value starts at 0 and the set of values is {0,1}. More generally, this is the case for N RB When mod K=0, it can be written that max_RB_offset=K.
[0150] In scenario 1110, there may be seven RBs and a PT-RS density of one every two RBs (i.e., K=2), where the PT-RS density does not divide evenly into the number of scheduled RBs (i.e., N RB mod K≠0). As a result, when the RB offset is 0, the total number of PT-RS can be 4, as shown by line 1111, and when the offset is 1, the total PT-RS is reduced to 3 (i.e., the RB offset value limits the number of PT-RS).
[0151] In some cases, it may be preferable for the number of PT-RS for a scheduled bandwidth to be the same to avoid WTRU performance degradation. Thus, it may be desirable to avoid a situation where there are different numbers of PT-RS for the same scheduled bandwidth as shown in line 1112. To ensure that the number of PT-RS remains the same, the complete possible set of RB offset values, max_RB_offset, may need to be limited. For example, the RB offset may be based on the WTRU-ID (i.e., n RNTI mod max_RB_offset), limiting max_RB_offset can enable the ability to keep the number of PT-RSs the same for a given number of scheduled RBs. As shown in scenario 1120, the PT-RS density may not be evenly divisible into the number of scheduled RBs (i.e., N RB mod K≠0). In the scenario of 1110, max_RB_offset may be limited to a function of the PT-RS density and the number of scheduled RBs, specifically, max_RB_offset may be limited to the remainder of the PT-RS density divided by the number of scheduled RBs, which is 7 mod 2, which equals 1. As discussed above, a numerical value of max_RB_offset, such as 1, results in a limited set (i.e., a subset) of RB offset values, where any RB offset value starts at 0. Then, if max_RB_offset is limited to 1, then the subset of max_RB_offset is {0}, which means that any RB offset greater than 0, such as shown by line 1112 with RB offset values {0,1}, will result in a different total number of PT-RS. More generally, this can be achieved by limiting the number of PT-RSs to N. RB mod K ≠ 0 when max_RB_offset = N RB It can be written as mod K.
[0152] 11B illustrates an example process for sending PT-RS transmissions to ensure that the PT-RS density K remains the same to address the possible issues discussed with respect to FIG. 11A. In a first step 1151, the PT-RS density K and the number of scheduled RBs N RB In one case, a device such as a WTRU may have a specific bandwidth scheduled (i.e., control information is received on a control channel). The WTRU may determine the PT-RS density K based on the scheduled bandwidth. In step 1152, the PT-RS density K is determined as the number of scheduled RBs N RB In step 1152, max_RB_offset may be equal to the PT-RS density if the PT-RS density is evenly divided, or if not, max_RB_offset may be a function of the PT-RS density and the number of scheduled RBs. In step 1154, an RB offset value may be determined according to the result of step 1153. In step 1155, after the RB offset is determined, this information may be used to send and / or receive transmissions with the PT-RS.
[0153] In another approach for limiting the RB offset values, there may be one or more methods applied to randomize interference with a restricted / limited set of RB offset values when the max_RB_offset value is less than K. There may be one or more methods that can follow this approach.
[0154] In one method, the RE location or subframe location of the PT-RS within an RB may be determined based on one or more WTRU-specific parameters. For example, when the RB offset value is restricted / limited, the RE location of the PT-RS within an RB may be determined with WTRU-specific parameters, and when the RB offset value is not restricted / limited (e.g., max_RB_offset=K), the RE location of the PT-RS within an RB may be determined based on a non-WTRU-specific parameter (e.g., a fixed, predefined, cell-specific parameter).
[0155] In another method, the PT-RS scrambling sequence may be determined based on one or more WTRU-specific parameters. For example, when the RB offset value is not restricted, the PT-RS scrambling sequence may be initialized based on one or more non-WTRU-specific parameters, and when the RB offset value is restricted, the PT-RS scrambling sequence may be initialized based on one or more WTRU-specific parameters.
[0156] In another method, the PT-RS time position (e.g., starting symbol index) may be determined based on one or more WTRU-specific parameters. For example, when the RB offset value is not restricted, a first symbol index may be used as the starting symbol of the PT-RS transmission, and when the RB offset value is restricted, a second symbol index may be used as the starting symbol of the PT-RS transmission. The first symbol index may be fixed, configured, and / or predefined, and the second symbol index may be determined based on one or more WTRU-specific parameters.
[0157] FIG. 12 illustrates an example of cyclically shifted RBs containing PT-RS. In this approach, a set of RB offsets may be defined, determined, or used in the set {0, 1, ..., max_RB_offset}, where max_RB_offset may be K (e.g., PT-RS density), and the RBs containing PT-RS may be cyclically shifted based on the RB offset value. Thus, the number of RBs containing PT-RS may be the same regardless of the RB offset value. Scenario 1210 illustrates several examples of a slot including 7 RBs with PT-RS every 2 RBs. In one example 1211, the RBs containing PT-RS may be evenly distributed, where the RB offset is 0, resulting in a PT-RS density of 4. In another example 1212, the RB offset may be 1, and the RBs containing PT-RS may not be evenly distributed, where one PT-RS RB 1202 is shifted and adjacent to another PT-RS RB, but the PT-RS density is still 4. Furthermore, the cyclic shift value may be determined based on one or more WTRU-specific parameters. For example, a PT-RS that is not assigned to an RB by the RB offset value may be placed in one of the RBs that does not contain a PT-RS, where the RB location may be determined based on the WTRU-ID (e.g., C-RNTI).
[0158] In some cases, the reference position of the RB containing the PT-RS may be based on RB offset=0, where the number of RBs containing the PT-RS may be the same as in the case of RB offset=0 regardless of the determined RB offset value, and the PT-RS density may be 4.
[0159] In one approach, a power boosting PT-RS may be used when the number of RBs used for the PT-RS for an RB offset is smaller than that for a reference RB offset. For example, a reference RB offset may be defined, configured, or used with RB offset=0, and the number of RBs used for the PT-RS may be K p The number of RBs used for the PT-RS for a particular RB offset may be Kp If the number of RBs containing the PT-RS is smaller than K for the first RB offset value, power boosting of the PT-RS may be used. p When the first power level is equal to K, the number of RBs containing the PT-RS is equal to K for the second RB offset value. p A second power level (higher than the first power level) may be used for the PT-RS when K is smaller than the number of RBs containing the PT-RS for a particular RB offset value. p The ratio between the
[0160] Also in this approach, the constellation points may be correlated to an offset value, and the number of RBs containing the PT-RS is determined to be K for the first RB offset value. p When the first constellation point (e.g., a QPSK constellation) may be used for the PT-RS sequence, and the number of RBs containing the PT-RS may be K for the second RB offset value. p When the modulation order for the outermost constellation point (e.g., 16QAM, 64QAM, or 256QAM) is smaller than K, a second constellation point (e.g., an outermost constellation point of 16QAM, 64QAM, or 256QAM) may be used. The modulation order for the outermost constellation point (e.g., 16QAM, 64QAM, or 256QAM) depends on the number of RBs containing the PT-RS for a particular RB offset value (K a ) and K p For example, the ratio between K a / K p If K is greater than a predefined threshold, a first modulation order (e.g., 16QAM) may be used, and K a / K p If t is less than a predefined threshold, then a second modulation order (e.g., 64QAM) may be used. The modulation order for the outermost constellation point may be determined based on an indicated, determined, or scheduled modulation order for an associated data channel (e.g., PDSCH or PUSCH).
[0161] In one scenario, the RB offset value may be used to shift the PT-RS from a default RB location to a different RB, such as a fixed number of RBs away from the default RB location, to avoid intra-cell or inter-cell interference sources from other transmitters of PT-RS in the same RB location. If significant PT-RS-based interference exists, the time and frequency of the PT-RS density may be modified or changed to avoid or reduce the interference level. For example, Table 4 below shows possible RB offset and PT-RS frequency density combinations, assuming both transmitters use PT-RS time density=1 (e.g., PT-RS transmitted every symbol).
[0162] [Table 4]
[0163] For this scenario, the frequency density of one or more interference sources (e.g., co-scheduled WTRUs or neighboring cells) may be indicated to the WTRU via higher layer or L1 signaling (e.g., DCI). For this indication to the WTRU, one or more approaches may be applicable.
[0164] In one approach, the WTRU may receive a frequency density of the interfering PT-RS in an associated DCI for data scheduling, and the PT-RS density (e.g., serving PT-RS time and / or frequency density) for the WTRU may be determined based on the frequency density of the interfering PT-RS. If the interfering PT-RS density is increased, the serving PT-RS density may also be increased. Alternatively, if the interfering PT-RS density is increased, the serving PT-RS density may be reduced.
[0165] In another approach, the set of RB offset values may be limited based on the interference PT-RS density. For example, if the interference PT-RS density is lower, a smaller set of RB offset values may be used, and if the interference PT-RS density is higher, a larger set of RB offset values may be used. In a further example, if the interference PT-RS density is low (e.g., 1), a first subset of RB offset values (e.g., {0}) may be used, if the interference PT-RS density is medium (e.g., 2), a second subset of RB offset values (e.g., {0,1}) may be used, and if the interference PT-RS density is high (e.g., 4), a third subset of RB offset values (e.g., {0,1,2,3}) may be used.
[0166] In another approach, the set of RB offset values may be limited based on the interfering PT-RS density and the serving PT-RS density.
[0167] Similar options for RB offset may be possible if any one of the transmitters uses a PT-RS time density < 1 (e.g., OFDM symbol offset). Also, OFDM symbol offset may be needed to handle DM-RS based interference to the PT-RS. Another possibility is to use a subcarrier offset for the PT-RS within the RB.
[0168] Figure 13 shows an example of PT-RS mapping for seven RBs with different RB offset values. In this approach, the RB offset may be determined based on the C-RNTI and / or the subframe / slot number or index. For perspective, returning to Figure 2,
[0169]
number
[0170] , and PT-RS mappings with different PT-RS densities of 4 RBs are shown, and since there is a PT-RS at the scheduled starting RB position, the RB offset can be assumed to be 0 since there is a PT-RS RB at the first index.
[0171]
number
[0172] In any configuration where N, the PT-RS density per slot can vary based on the RB offset value. Now, looking at the example shown in FIG. 13, there is a PT-RS mapping, N RB = 7 RBs, each with a different RB offset value, 0 RB in scenario 1310 and 1 RB in scenario 1320. In scenario 1310, there are RBs every 2 RBs and the RB offset may be 0, resulting in a PT-RS density of 4, and in scenario 1320, there are RBs every 2 RBs and the RB offset may be 1, resulting in a PT-RS density of 3. As shown, in the configuration with RB offset = 1, the total number of PT-RSs will be smaller than in the RB offset = 0 case, which may result in some performance degradation.
[0173] Figure 14 shows examples of PT-RS mapping with different RB width schedules. In scenario 1410, there may be 7 RBs with PT-RS every 2 RBs, resulting in a density of 4. In scenario 1420, there may be 13 RBs with PT-RS every 4 RBs, resulting in a density of 4; such configurations may have a greater impact on performance since the scheduling is so spread out.
[0174] FIG. 15 shows an example PT-RS mapping for seven dynamic RB offset values. In this approach, the RB offset can be dynamically adjusted or determined based on the time index to have an equal average of PT-RS over the duration of the transmission. In scenario 1510, there can be seven RBs with a PT-RS every two RBs. The time index is determined by the frame number (n Frame ), slot number (n Slot ), or symbol number (n Sym For example, the first RB offset may be determined based on the C-RNTI, and the additional RB offset may be at least one of n Slot where n Slot is the slot number corresponding to the current transmission. Scenario 1510 illustrates an example implementation based on setting the offset value based on odd / even slot number, resulting in each increment in slots (i.e., slot n, slot n+1, slot n+2, ..., slot n+k) alternating RB offset values, which also impacts the PT-RS density (i.e., density alternating between 4 and 3 based on offset values of 0 and 1, respectively). The slot number may be a slot number within a radio frame, or an absolute number. In an alternative example, the RB offset value may be jointly defined based on the C-RNTI and a time index, etc. In another example, the RB offset adjustment may be applied only to configurations exhibiting uneven distribution, or may be applied universally to all configurations regardless of the impact of the offset value.
[0175] FIG. 16 shows an example of PT-RS mapping with dynamic RB offset values for 13 PRs per slot. In this case, the RB offset values can be dynamically adjusted based on time index to combat the effects of frequency selective fading. Thus, regardless of the effects of PT-RS density, the RB offsets can be dynamically changed to avoid experiencing long fades for all configurations. Scenario 1610 shows 13 RBs in each slot, with a PT-RS RB every 4 (i.e.,
[0176]
number
[0177] ). The time index is n Frame ,
[0178]
number
[0179] , n Slot , or n Sym For example, an initial RB offset may be determined based on the C-RNTI, and then additional RB offsets may be applied to shift the position of the PT-RS RBs on a slot-by-slot basis or based on slot number. The RB offset may be n Slot and
[0180]
number
[0181] where the additional offset may be determined based on:
[0182]
number
[0183] As shown, the RB offset increases with each slot number, so in slot n, the RB offset is 0, in slot n+1 the offset is 1, in slot n+2 the RB offset is 2, and in slot n+3 the RB offset is 3. Note that after the RB offset is 3, in the next slot n+4, the RB offset will go back to 0 since the PT-RS density is only 4; one cannot have an RB offset of 4 without having a PT-RS density of at least 5, which is not assumed in this example.
[0184] In an embodiment, the PT-RS density may depend on the frequency resource allocation type. In some cases, modulated information symbols may be mapped to time and frequency resources before transmission. Multiple information symbols may be mapped to discrete consecutive time and frequency blocks. In LTE and NR, modulated information symbols may be mapped to time and frequency units called resource elements (REs). An RE may include one subcarrier in one OFDM symbol. A block RE includes 12 consecutive subcarriers (i.e., frequency) by 7 OFDM symbols (i.e., a slot may include RBs). When individual or multiple RBs are mapped contiguously or non-contiguously in time and frequency, they are considered to have a localized or distributed resource allocation type, respectively. Since the PT-RS may be mapped within an assigned RB that may have a localized or distributed resource allocation type, the PT-RS density in time and frequency may depend on its type. Thus, at least in some circumstances, it is necessary to configure the PT-RS time and frequency density, which also depends on whether a localized or distributed resource allocation type is used.
[0185] FIG. 17 shows an example of PT-RS frequency location based on symbol location. As in FIG. 2, horizontal axis 1704 is symbols (i.e., OFDM) and vertical axis 1705 is subcarriers. Regardless of whether NR resource allocation types 0 and 1 indicate that localized or distributed allocation is required, PT-RS time and frequency density may be maintained. If RBs are distributed in time during a transmission interval, PT-RS time density, which may be applicable to localized allocation, may be applied separately to each time region as shown in FIG. 17. If RBs are distributed in frequency during a transmission interval, PT-RS frequency density, which may be applicable to localized allocation, may be applied separately (i.e., for the carrier bandwidth portion used) to each frequency region of consecutively allocated resource blocks or resource block groups (RBGs). In example 1701, there may be a PT-RS per symbol that does not show any change. In example 1702, there may be a PT-RS density of every other symbol (i.e., every two symbols) and may restart when the frequency changes due to different frequency regions starting in the middle 1712. In example 1703, there may be a PT-RS symbol every 4 symbols and may restart when the frequency changes due to different frequency regions beginning in the middle 1713.
[0186] Figure 18 shows an example of PT-RS frequency density based on RBG. The frequency density may be determined based on the configured or determined RBG size, and there may be a different RBG for each scenario in Figure 18. In scenario 1810, there is a PT-RS for every RB and may have a density of every RB. In scenario 1820, there is a different RBG and may have a different density of every 2 RBs. In scenario 1830, there is yet another different RBG and may have a different density of every 4 RBs.
[0187] In an embodiment, the RE location (e.g., subcarrier location, RE offset) of a PT-RS within an RB containing the PT-RS may be determined based on at least one of a physical cell ID, a WTRU-ID (e.g., C-RNTI, temporary C-RNTI, or IMSI), a frequency density of the PT-RS, a time density of the PT-RS, and a max_RB_offset value. For example, if the max_RB_offset value is a first value (e.g., 0), the RE location (or RE offset) may be determined based on the WTRU-ID, and if the max_RB_offset value is a second value (e.g., >0), the RE location (or RE offset) may be determined based on a cell ID. Alternatively, if the max_RB_offset value is a first value, the RE location (or RE offset) may be determined based on a frequency density of the PT-RS, and if the max_RB_offset value is a second value, the RE location (or RE offset) may be determined based on a cell ID.
[0188] 19 shows an example of PT-RS generation for π / 2 BPSK data modulation. For binary phase shift keying (BPSK) modulation 1912, the bit sequence b(n) is
[0189]
number
[0190] , may be mapped to a complex-valued modulation symbol x based on
[0191] For π / 2 BPSK modulation 1914, the bit sequence b(n), where n is the index (i.e., position), is
[0192]
number
[0193] , may be mapped to a complex-valued modulation symbol x based on
[0194] Where:
[0195]
number
[0196] It is.
[0197] As discussed herein, π and pi may be used interchangeably. As seen in FIG. 19, there may be a PT-RS sequence design in which the modulation order of the associated data (e.g., PDSCH or PUSCH) may be pi / 2BPSK. The PT-RS bits, consisting of 0s and 1s, may be multiplexed 1910 with the data bits according to a predefined pattern. The resulting multiplexed bits b 1902 may undergo BPSK modulation 1912 to produce d 1904, and then pi / 2 modulation 1914 to produce c 1906. Separation of BPSK and pi / 2 modulation may be beneficial when an orthogonal cover code (OCC) is applied across the PT-RS bits. After pi / 2 modulation 1914, the resulting symbols may be processed by a DFT block 1916 and optional frequency domain spectral shaping (FDSS) 1918, which may be implemented either before or after the DFT 1916. The shaped symbols are mapped 1920 to the assigned subcarriers and go through an IDFT processing block 1922 before being prepared for transmission in an OFDM symbol.
[0198] FIG. 19 may be further detailed with the following example. Assuming that the DFT size is set to N=12 (e.g., the total number of data and PT-RS bits) based on the allocated resources, that the PT-RS bits are inserted in two chunks at the beginning and end of the sequence b 1902, and that each chunk consists of 2 bits, the multiplexed vector of data and PT-RS bits 1910 may be written as b=[X, X, 8 data bits, Y, Y], where X, Y, and data bits are either 0 or 1. Note that in general, the PT-RS bits in each chunk do not need to be the same, and thus may be values X1, X2, Y1, and Y2 in this example, and there may be different X and Y values. For illustration, there may be values of b=[1,1,0,0,1,1,0,1,0,1,1 1], and after BPSK modulation 1912 of b 1902, the modulated sequence may be d 1904 as shown in Table 5 below, and the following notation is used:
[0199]
number
[0200] [Table 5]
[0201] Then, to perform pi / 2 modulation 1914 to obtain c 1906, the sequence d 1904 is transformed into the vector
[0202]
number
[0203] (n=0,…,N-1) is multiplied element-wise (Hadamard product). Note that p(n) can be written slightly differently, as long as it represents a pi / 2 modulation. Example calculated values of p(n) are given in Table 6 below.
[0204] [Table 6]
[0205] Then, as shown in Table 7 below,
[0206]
number
[0207] get.
[0208] [Table 7]
[0209] FIG. 20 illustrates an example of PT-RS generation for pi / 2 BPSK data modulation and OCC. As discussed herein, some elements may be interpreted as similar if they use the same last two digits, such as in FIG. 19 and FIG. 20. FIG. 20 may also be similar to FIG. 19, except that when PT-RS bits are transmitted in chunks, an orthogonal cover code (OCC) may be applied across the PT-RS bits in the chunk. Note that the bits multiplied with the OCC may be the same. In such a scenario, the OCC may be applied to the PT-RS bits after the BPSK modulation 2012 but before the pi / 2 modulation 2014 (i.e., in sequence d 2004), resulting in an OCC-applied PT-RS bit e 2005 (i.e., vector e). Note that applying the OCC after the pi / 2 modulation may destroy the phase continuity of the signal and result in a signal with a larger peak-to-average power ratio.
[0210] To explain in more detail, assume for example that the chunk size is 2 and the OCCs to be applied are
[0011] and [1 -1]. The two PT-RS bits in each chunk in d 2004 can be multiplied with one of these OCCs 2013. Continuing with the example, if the OCC is
[0011] , the vector e 2005 will be as shown in Table 8 below.
[0211] [Table 8]
[0212] When OCC is [1 -1], vector e2005 is as shown in Table 9 below.
[0213] [Table 9]
[0214] The OCC applied by a given WTRU to each chunk of PT-RS bits may be the same for all chunks or may be different for one or more chunks. For example, in the case of two chunks and two bits, the OCC code applied by the WTRU may be {
[0011] ,
[0011] } or {[1 -1],[1 -1]} or {
[0011] ,[1 -1]} or {[1 -1],
[0011] }.
[0215] If the same OCC is applied across all chunks, the code index may be signaled or determined implicitly using another parameter, e.g., the WTRU ID. For example, mod(WTRU ID,2) may determine one of two OCCs, mod(WTRU ID,4) may determine one of four OCCs, etc. In general, mod(WTRU ID,k) may determine one of k OCCs.
[0216] The index of the OCC to be applied across chunks may be determined by a rule such as code rotation. For example, assume there are four chunks, each with 2PT-RS bits. The WTRU may then apply the following codes to the four chunks in the given order: {
[0011] , [1 -1],
[0011] , [1 -1]} or {[1 -1],
[0011] , [1 -1],
[0011] }. The index of the first code may be signaled or determined implicitly, for example, by the WTRU ID.
[0217] Figure 21 shows an example of cycling through OCCs. The cycling operation can be done clockwise 2101 or counterclockwise 2102, where the indices of the OCCs are arranged on a circle. For example, OCC#1=[1 1 1 1], OCC#2=[1 1 -1 -1], OCC#3=[1 -1 1 -1], OCC#4=[1 -1 -1 1].
[0218] In one approach, an OCC may be used for a reference signal sequence (e.g., within a chunk) based on the modulation order of the reference signal (e.g., PT-RS). For example, if a first modulation order (e.g., pi / 2BPSK) is used for the reference signal, no OCC may be used (e.g., an OCC with all "1" entries may be used), and if a second modulation order (e.g., QPSK) is used for the reference, an OCC may be used, which may be determined based on one or more WTRU-specific parameters (e.g., WTRU-ID (e.g., C-RNTI), scrambling ID, etc.), parameters configured at higher layers, a layer (e.g., transmission layer), number of layers, one or more cell-specific parameters (e.g., cell ID), and / or the use of a particular OCC (e.g., all "1" entries) may be referred to as non-use of an OCC.
[0219] For a common PT-RS design for all modulation types, such as QPSK modulation, the pair of bits b(n) and b(n+1) is
[0220]
number
[0221] The complex-valued modulation symbol x may be mapped to the complex-valued modulation symbol x according to
[0222] FIG. 22 shows examples of pi / 2BPSK and QPSK constellations. Note that both the pi / 2BPSK and QPSK modulations described above can have the same constellations as shown in FIG. 22. The horizontal axis measures real numbers 2201 and the vertical axis measures imaginary numbers 2202. Given that pi / 2BPSK and QPSK have the same constellation, it may be desirable to have a sequence design for PT-RS that is common to all types of data modulation, including pi / 2BPSK, as well as QPSK, 16QAM, and others. For this reason, in general, the number of bits required for PT-RS in one DFT-s-OFDM symbol can be equal to V*X (V multiplied by X), where V is the chunk size and X is the chunk number.
[0223] FIG. 23 shows a common PT-RS design sample. In this example, the PT-RS bits 2310 can have values of p(0), p(1), p(2), and p(3). When processed by BPSK modulation 2302, the PT-RS sequence is
[0224]
number
[0225] It can be generated according to:
[0226] This is shown in 2303, where n is the index (n=0, 1, . . . , N-1) of the DFT 2304 input, and the i-th PT-RS bit p(i) is inserted.
[0227] For example, if the DFT size is 12 and PT-RS is inserted into DFT 2304 inputs n=0,1 (leading) and n=10,11 (tail), the PT-RS inserted into these DFT 2304 inputs may be written as follows:
[0228]
number
[0229] FIG. 24 shows an example of OCC application to a PT-RS design for the smallest n in a group, and FIG. 25 shows the same except for the largest n in a group. Note that, as described with respect to FIG. 21, when OCC is applied across the PT-RS bits in a chunk and the modulation type for the data is pi / 2BPSK, OCC can be applied after the BPSK modulation but before the pi / 2 modulation. The same method can be used when the data modulation type is not pi / 2BPSK. Alternatively, when the data modulation type is not pi / 2BPSK, OCC can be applied across the pi / 2BPSK modulated PT-RS bits as shown in the example of FIG. 24. Also in FIG. 24, O1 and O2 2405 can indicate OCC bits (e.g., [O1 O2]=
[0011] or [1 -1]).
[0230] With OCC, the number of PT-RS bits 2410 required can be (X*V) / L, where L is the length of the OCC. After these bits are BPSK modulated 2402, each bit can be repeated L times and mapped to the corresponding input of the DFT 2404. In the example of FIG. 24, we use L=2. The bits in each L-sized group are assigned the same coefficient e jmπ / 2 2403, where m may be determined based on the index of the DFT 2404 input corresponding to the L-sized group. For example, m may be multiplied by the smallest n (i.e., e jmπ / 2 e j(0)π / 2 and e j(N-1)π / 2), or the largest n in that group (i.e., e jmπ / 2 e j(1)π / 2 and e j(N)π / 2 24 may be similar to FIG. 25 except for the value of n. Alternatively, m may be set equal to i (PT-RS bit index, i=0,1,...,(X*K) / L).
[0231] The PT-RS bits p(i) may be generated using a pseudorandom number generator, such as a Gold sequence generator used in LTE.
[0232] In one scenario, the OCC may depend on the data modulation order: In the case of pi / 2 BPSK modulation of the data bits, a default OCC vector may be applied across the PT-RS chunk (e.g., an all-ones vector such as
[0011] or [1 1 1 1]).
[0233] pi / 2BPSK modulation,
[0234]
number
[0235] If defined as: The constellation becomes as shown in the example of Figure 26, where the horizontal axis shows real numbers 2601 and the vertical axis shows imaginary numbers 2602. In such a case, a pi / 2BPSK modulated PT-RS can be used when the data modulation is QPSK or higher order QAM modulation, after multiplying the PT-RS symbols with e^(jπ / 4) to create the constellation as shown in Figure 26.
[0236] In another scenario, the first RS sequence may be based on pi / 2BPSK, and the second RS sequence may be a phase-shifted version of the first RS sequence. In such a scenario, one or more of the following may apply: the first RS sequence may be used when the modulation order of its associated data channel is a first modulation order (e.g., pi / 2BPSK), and / or the phase-shifted version of the first RS sequence (e.g., the second RS sequence) may be used when the modulation order of its associated data channel is a second modulation order (e.g., a modulation order higher than pi / 2BPSK), where the phase shift value may be predefined, preconfigured, or determined based on the constellations of pi / 2BPSK and QPSK.
[0237] In an embodiment, a PT-RS for a virtual CP (i.e., an extended CP) for NR may be considered, where the waveform and frame structure may be standardized, CP DFT-s-OFDM and CP OFDM may be waveforms in the uplink direction, pre-DFT PT-RS may be used for DFT-s-OFDM, and Δf=2 μ There may be multiple numerologies with subcarrier spacing defined as 15 kHz. For different subcarrier spacings, the CP size can be based on the formula given below:
[0238]
number
[0239] [Table 10]
[0240] Based on these considerations, the CP size may be exponentially reduced for larger subcarrier spacing in NR. This means that OFDM or DFT-s-OFDM symbols may be susceptible to multipath delay spread for higher subcarrier spacing, and the receiver may suffer from ISI for higher subcarrier spacing in certain cases (e.g., outdoor scenarios or with NLOS links). Existing solutions may increase the complexity of both the transmitter and receiver (e.g., UW and CP combinations, perturbation approaches) or may not fit the numerology used for NR (i.e., dynamic and static methods for DFT-s-OFDM). For example, static methods that essentially enable pre-DFT PT-RS require a CP length of 100 ms.
[0241]
number
[0242] However, this may not be feasible with one or more of the possible numerologies for NR. Therefore, it may be useful to consider a hypothetical CP solution that allows for CP expansion while conforming to possible constraints on the size of the CP, such as in the NR case.
[0243] FIG. 27 shows an example technique for generating a CP extended RS based on a pre-determined RS using a CP extender block. In this technique, a CP extended RS can be calculated based on other pre-determined RSs by using the CP extender block 2708 and mapping it to the input of the DFT-s-OFDM to extend the normal CP duration. A detailed transmitter block diagram for this method as well as the corresponding time domain symbols (i.e., three consecutive DFT-s-OFDM symbols 2731) are shown. i-1 , 2731 i , and 2731 i+1 ) can be seen in the example diagram shown in Figure 27. In the TX block diagram 2701,
[0244]
number
[0245] is a data vector containing data symbols,
[0246]
number
[0247] is a vector that may include a predetermined RS or PT-RS,
[0248]
number
[0249] is a vector that can contain the CP extended RS generated through the CP extender block 2708. The inputs of the CP extender block are
[0250]
number
[0251] The size of (i.e., R h and R t ), the amount of expansion in the time domain (i.e., T and H), the predetermined RS or PT-RS (i.e., h and t), the normal CP size G, and / or the symbol mapping matrix
[0252]
number
[0253] and the symbol mapping matrix may be the vectors d, h, t,
[0254]
number
[0255] Let D be the M-point DFT matrix D M The input is mapped to
[0256] 27, the CP extender block 2708 extends the vector φ based on a minimization criterion to achieve the virtual CP.
[0257]
number
[0258] Since the CP extender block 2708 operates with fixed values in this approach, the output of the CP extender block 270 may be calculated offline and stored in a memory of the transmitter (not shown).
[0259]
number
[0260] After ,is generated, ,d, h, ,t,
[0261]
number
[0262] is the symbol mapping matrix M t 2710 to the input of the M-DFT. The mapped vectors d, h, t,
[0263]
number
[0264] In a subsequent step, the M-DFT of D M 2712 yields the output of a DFT of size M (M-DFT), which is
[0265]
number
[0266] 2714, and the N-IDFT of the mapped output of the M-DFT is given by the IDFT matrix
[0267]
number
[0268] 2716, which is the time domain signal vector
[0269]
number
[0270] The last G samples of x can be prepended to a signal vector x and the resulting vector can be transmitted, resulting in the time-domain signal diagram 2730.
[0271] The overall operation to create the vector x is
[0272]
number
[0273] It can be expressed as:
[0274] Where:
[0275]
number
[0276] are vectors d, h, t,
[0277]
number
[0278] is the waveform matrix that generates the vector x from
[0279] FIG. 28 shows an example of a signal structure designed to realize a virtual CP using a CP extender block. For illustrative purposes, the derivation of the CP extension part can be based on a pre-determined RS (e.g., PT-RS). The signal structure with a CP part G is denoted by a data vector M d can be used to realize a virtual CP, denoted when is set to the zero vector. Given the CP length G, h, t, and the mapping matrix M t About CP extender block,
[0280]
number
[0281] may be generated such that the last T samples (denoted by x1) and the first H samples (denoted by x4) of vector x shown in signal diagram 2830 are approximately equal to the T samples up to the (N-G+1)th sample of x (denoted by x2) and the H samples from the (N-G+1)th sample of x (denoted by x3), respectively, where
[0282]
number
[0283] CP is the value
[0284]
number
[0285] To achieve this goal, the waveform matrix A can be divided.
[0286] FIG. 29 shows an example of the division of the waveform matrix A to derive the CP extender blocks. FIG. 29 may be interpreted in the context of the variables as discussed herein, such as in connection with FIG. 27 and FIG. 28. The sub-matrices are: A H11 =A(1:H,[1:M d +M t +M h ]) A H12 =A(1:H,M d +M t +M h +[1:M]) A H21 =A(N-G+[1:H],[1:M d +M t +M h ]) A H22 =A(N-G+[1:H],M d +M t +M h +[1:M]) A T11 =A(NG-T+[1:T],[1:M d +M t +M h ]) A T12 =A(NG-T+[1:T],M d +M t +M h +[1:M]) A T21 =A(N-T+[1:T],[1:M d +M t +M h ]) A T22 =A(N-T+[1:T],M d +M t +M h +[1:M]) It can be defined as:
[0287] Here, A(X+[A1:A 2],Y+[B1:B2]) gives the submatrix in A from row X+A1 to X+A2 and column Y+B1 to Y+B2.
[0288] By using the above submatrices, vectors x1, x2, x3, and x4 are respectively
[0289]
number
[0290] It can be expressed as:
[0291] The objective is
[0292]
number
[0293] Therefore, by rearranging the submatrices, the objective function in the CP extender block can be expressed as follows:
[0294]
number
[0295] which is subject to the following conditions:
[0296]
number
[0297] where α is a non-negative value that constrains the energy of the CP-extended RS. An equivalent approach for a given α can be obtained in closed form in Equation (1) below.
[0298]
number
[0299] where λ is a non-negative internal parameter of the CP extender block.
[0300] 30 shows an example transmit (TX) block diagram with assumptions to further explain concepts related to the CP extender block. FIG. 30 may be interpreted in the context of variables and processes as discussed herein, such as in connection with FIG. 27, FIG. 28, and FIG. 29.
[0301] Figure 31 shows an example signal resulting from assumed values of the transmit blocks shown in Figure 30. Figure 31 may be interpreted in the context of the variables and processes as discussed herein, such as in connection with Figures 27, 28, 29, and 30.
[0302] Referring to FIG. 30, M=96 (i.e., 6 RBs since there can be 96 subcarriers in NR), N=512, G=36, and the CP size is G e = G + 18 = 54 (e.g., H = 18 and T = 0) samples to increase the robustness of the DFT-s-OFDM symbol against multipath channels. In this example, the independent RS length is M h =1 and M t =1, and their values can be assumed to be set to 1 (M h is set to M to avoid leakage from the data symbols. h ≧G / N×M). For mapping, M d1 =86 and M d2 = 1. The size of RS that is depended on can be assumed to be R h =3 and R t = 2. The inner λ may be set to 0.0001. Given these parameters, and referring to Figure 31, the resulting signal in the time domain may be shown, with amplitude shown on the vertical axis 3102 and samples shown on the horizontal axis 3101. With these settings, the CP extender block generates the following CP extended RS:
[0303]
number
[0304] As can be seen from the time domain signal, the extended CP portion 3114 can be almost the same looking at 3110a and 3110b. Therefore, this example shows that the robustness of DFT-s-OFDM to multipath channels can be improved by the techniques disclosed herein.
[0305] FIG. 32 shows an example of doubling the CP extension using the CP extension RS. In this example, H+T can be equal to G. To reduce the error in equation (1), the symbol mapping matrix M t For example, the mapping matrix M t can interface the CP extended RS and the predetermined RS.
[0306] FIG. 33 shows an example of a CP extended PT-RS design. In an embodiment, all RSs or PT-RSs with energy constraints can be calculated and mapped to the input of DFT-s-OFDM by using the CP extender block 3308. As shown, a detailed transmitter block diagram 3301 is shown as well as a corresponding time domain symbol 3330 (i.e., three consecutive DFT-s-OFDM symbols 3331 ). i-1 , 3331 i , and 3331 i+1 ) is possible. The CP extender block 3308 extends the vector
[0307]
number
[0308] The output of the CP extender block may be calculated offline and stored in the memory of the transmitter.
[0309]
number
[0310] After is generated, d,
[0311]
number
[0312] is the symbol mapping matrix M t The overall operation to generate the vector x is
[0313]
number
[0314] It can be expressed as:
[0315] Where:
[0316]
number
[0317] is the vector d,
[0318]
number
[0319] is the waveform matrix that generates the vector x from
[0320] 34 shows an example of a signal structure for implementing a virtual CP using a CP extender block. The signal structure 3430 having a CP extension for implementing a virtual CP is d It can be shown that when is set to the zero vector. Given the CP length G and the mapping matrix M t About CP extender block,
[0321]
number
[0322] to ensure that the last T samples (denoted by x4) and the first H samples (denoted by x1) of vector x are approximately equal to the T samples up to the (N-G+1)th sample of x (denoted by x2) and the H samples from the (N-G+1)th sample of x (denoted by x3), respectively, i.e.,
[0323]
number
[0324] The CP can be
[0325]
number
[0326] To achieve this goal, the waveform matrix A can be divided.
[0327] Figure 35 shows a waveform matrix A for deriving the CP extender block for the complete PT-RS. A H11 =A(1:H,[1:M d ]) A H12 =A(1:H,M d +[1:M]) A H21 =A(N-G+[1:H],[1:M d ]) A H22 =A(N-G+[1:H],M d +[1:M]) A T11 =A(NG-T+[1:T],[1:M d ]) A T12 =A(NG-T+[1:T],Md +[1:M]) A T21 =A(N-T+[1:T],[1:M d ]) A T22 =A(N-T+[1:T],M d +[1:M]) It can be defined as:
[0328] Here, A(X+[A1:A 2] ,Y+[B1:B2]) gives the submatrix in A from row X+A1 to X+A2 and column Y+B1 to Y+B2.
[0329] By using the above submatrices, vectors x1, x2, x3, and x4 are respectively
[0330]
number
[0331] It can be expressed as:
[0332] One purpose is
[0333]
number
[0334] Therefore, by rearranging the submatrices, the operation in the CP extender block can be TIFF0007583138000082.tif1457
[0335] which is subject to the following conditions: TIFF0007583138000083.tif1220
[0336] where α is a non-negative value that avoids trivial solutions, which can be addressed by using any convex optimization toolbox since the problem is convex.
[0337] Another approach is to use the element TIFF0007583138000084.tif923
[0338] Another constraint can be introduced to optimize the value for .
[0339] In an embodiment, the PT-RS may be used for or along with sidelink transmissions or channels, which may be channels used between WTRUs.
[0340] PT-RS is a non-limiting example of an RS that may be used. In the embodiments and examples described herein, other RSs, such as DM-RSs, may be used in place of PT-RSs and still be consistent with the present disclosure. For example, solutions used to determine the presence, density and / or location of PT-RSs may be applicable to determine those of other RSs, such as DM-RSs, for channels, such as sidelink channels.
[0341] Sidelink channels or transmissions are non-limiting examples of channels or transmissions that may be used for communication between WTRUs, which may be of the same or different types. For example, in the examples and embodiments described herein, a backhaul channel or transmission may be used in place of a sidelink channel or transmission and still be consistent with the present disclosure. The backhaul channel or transmission may be between a gNB, a relay and a gNB (e.g., a donor gNB), an integrated access backhaul (IAB) node, a gNB, and / or an IAB node, etc.
[0342] In one approach, the PSCCH and PSSCH may use the same structure (e.g., DM-RS RE location and data RE location within an RB or scheduled RBs). A sidelink transmission may include a PSCCH and its associated PSSCH, where the PSCCH may provide scheduling information for the PSSCH.
[0343] The presence (e.g., transmission) of the PT-RS on the PSCCH may be determined based on the presence of the PT-RS on the PSSCH. For example, the PT-RS may be present (e.g., transmitted) on the PSCCH when the PT-RS is present in an associated PSSCH (e.g., a PSSCH scheduled by the PSCCH).
[0344] The presence of the PT-RS in a PSCCH may be determined based on the presence of the PT-RS in an associated PSSCH and the time position of the associated PSCCH. For example, if a PSCCH and its associated PSSCH (e.g., a PSSCH scheduled by a PSCCH) are located in the same slot or in the same time position and the associated PSSCH includes a PT-RS, then the PSSCH may include a PT-RS. If a PSCCH and its associated PSSCH are located in different slots or in different time positions, then the PSCCH may not include a PT-RS.
[0345] The presence of the PT-RS in the PSSCH may be determined based on at least one of the frequency range (e.g., FR1, FR2) of the carrier or bandwidth portion for sidelink transmission (e.g., for the PSSCH), the subcarrier spacing of the carrier or BWP for the PSSCH transmission or the subcarrier spacing that may be used for the PSSCH transmission, the MCS level and / or scheduling bandwidth indicated or used for the PSSCH, the Doppler frequency (or the relative velocity between the two WTRUs), and / or higher layer configuration.
[0346] The density (e.g., time and / or frequency density) of the PT-RS on the PSCCH may be determined based on the density of the PT-RS on the associated PSSCH. Additionally / alternatively, the density of the PT-RS on the PSCCH may be the same as the density of the PT-RS on the associated PSSCH. Additionally / alternatively, the density of the PT-RS on the associated PSSCH may be determined based on a higher layer configuration. Additionally / alternatively, the density of the PT-RS on the associated PSSCH may be determined based on a distance or proximity between two WTRUs, and the WTRU may be informed of distance or proximity information from a gNB that may grant sidelink resources. Additionally / alternatively, the density of the PT-RS on the associated PSSCH may be determined based on one or more scheduling parameters (e.g., MCS level, scheduling bandwidth).
[0347] One or more scheduling parameters for the PSSCH, which may determine the PT-RS density of the PSSCH and / or the PSCCH, may be configured (e.g., pre-configured) or indicated before the WTRU transmits the PSCCH. For example, a PDCCH (e.g., a PDCCH granting one or more sidelink resources) may provide or indicate one or more scheduling information for the PSSCH, which may determine or may be used to determine the PT-RS density of the PSCCH and / or the PSSCH.
[0348] One or more PSCCHs may be associated with a PSSCH, and sidelink control information (SCI) that schedules the PSSCH may be split into one or more PSCCHs. For example, a first subset of SCIs may be transmitted in a first PSCCH, a second subset of SCIs may be transmitted in a second PSCCH, and so on. The first PSCCH may include a PT-RS. The density and / or location of the PT-RS of the first PSCCH may be configured or pre-determined. Alternatively, the first PSCCH may not include a PT-RS. Additionally / or, the first PSCCH may include one or more scheduling information for the PSSCH, which may determine or may be used to determine the PT-RS density and / or PT-RS location of the PSSCH. One or more scheduling information included in a PSCCH (e.g., a first PSCCH) may determine or may be used to determine PT-RS density and / or PT-RS location of other PSCCHs, such as one or more (e.g., all) of the remaining portions of the PSCCH.
[0349] The presence and / or density of PT-RS on the PSCCH may be determined or pre-determined based on a PSCCH configuration. The presence and / or density of PT-RS on the PSSCH may be determined based on scheduling parameters provided by the associated PSCCH.
[0350] In one scenario, when a PSCCH is used to schedule a PSSCH, the scheduling parameters (e.g., MCS or scheduling bandwidth) of the PSSCH may not be known, e.g., until the PSCCH is received. A maximum or minimum value of the scheduling parameter (e.g., for the PSSCH) may be configured and / or used to determine the presence and / or density of PT-RS on the PSCCH.
[0351] In the approach, the PSCCH and / or PSSCH resources may be determined, indicated, and / or granted by the PDCCH. The presence and / or density of the PT-RS on the PSCCH may be determined based on information provided by the associated PDCCH. The presence and / or density of the PT-RS on the PSSCH may be determined based on information provided by the associated PSCCH.
[0352] A PDCCH (e.g., DCI) for PSCCH resource allocation or grant may include one or more of the following: time / frequency locations of one or more PSCCHs, the number of RBs used for PSCCH transmission, DM-RS configuration information (e.g., DM-RS density of the PSCCH, DM-RS location within the PSCCH, etc.), and / or PT-RS configuration information (e.g., PT-RS presence, PT-RS density, PT-RS location including RB offset and subcarrier location).
[0353] The PSCCH for PSSCH scheduling may include one or more of the following: time / frequency location of the scheduled PSSCH, number of RBs used for the scheduled PSSCH, DM-RS configuration information (e.g., DM-RS density of the PSSCH, DM-RS location within the PSSCH, etc.), PT-RS configuration information (e.g., PT-RS presence, PT-RS density, PT-RS location including RB offset and subcarrier location), and / or if PT-RS configuration information is not provided by the associated PSCCH, the PT-RS configuration may be the same as that of the PSCCH.
[0354] One or more operation modes may be used for the sidelink. In a first sidelink mode (e.g., SL-Mode-1), resources for the PSCCH and / or PSSCH may be dynamically granted by the gNB (e.g., using the PDCCH). In a second sidelink mode (e.g., SL-Mode-2), one or more resources for the PSCCH and / or PSSCH are configured (e.g., pre-configured) and the WTRU may determine and / or use one of the configured resources.
[0355] In the examples and embodiments described herein, the first mode may be a mode with dynamically granted resources (e.g., SL-Mode-1) and the second mode may be a mode with resources selected for the WTRU from a configured pool or set (e.g., SL-Mode-2), or vice versa.
[0356] In the solution, the presence, density and / or location of the PT-RS in a sidelink channel (e.g., PSCCH and / or PSSCH) may be determined based on the sidelink operation mode. For example, the presence of the PT-RS in the sidelink channel may be determined based on the sidelink operation mode. The PT-RS may be able to be present in the sidelink channel in a first sidelink mode and may not be present in the sidelink channel in a second sidelink mode.
[0357] The density and / or location of the PT-RS on the sidelink channel may be configured (e.g., via higher layer signaling) or may be determined as described in the examples herein (e.g., based on one or more transmission parameters, such as a frequency range, subcarrier spacing, MCS level, or scheduling bandwidth).
[0358] A means for determining (e.g., means for using to determine) density and / or location of PT-RS of a sidelink channel may be determined based on the sidelink mode. The means may be explicit means such as configuration or signaling (e.g., of density and / or location). The means may be implicit means such as determination based on one or more parameters (e.g., parameters that are not explicitly density and / or location). For example, the density and / or location of PT-RS of a sidelink channel may be configured (e.g., by higher layer signaling) in the first sidelink mode. In the second sidelink mode, the density and / or location of PT-RS of a sidelink channel may be determined based on one or more transmission parameters such as frequency range, subcarrier spacing, MCS level, scheduling bandwidth, etc.
[0359] In the solution, the presence, density and / or location of the PT-RS in a sidelink channel (e.g., PSCCH and / or PSSCH) may be determined based on one or more of the following transmission parameters: relative speeds between the WTRUs, coverage level (e.g., proximity level) between the WTRUs, geographical location of a WTRU (e.g., Tx WTRU) within a cell, number of symbols used for the sidelink channel, frequency range, time / frequency location or sidelink resource index or identity of the determined sidelink resource, where sidelink resources may be determined based on scheduling, configuration and / or selection, DM-RS density (e.g., number of symbols used for DM-RS), and / or search space used for the channel or associated channel (e.g., search space of the associated PSCCH channel when transmitting a PT-RS in or together with the PSSCH).
[0360] In an example, one or more sidelink resources may be configured (e.g., preconfigured) and (e.g., each) sidelink resource may be associated with a sidelink resource identity (e.g., SL-id). The WTRU may determine the sidelink resources for transmission or reception. The presence, density, and / or location of the PT-RS in a sidelink channel (e.g., PSCCH, PSSCH) may be determined based on the determined sidelink resource identity.
[0361] The location of the PT-RS may include one or more RB locations and / or one or more subcarrier locations.
[0362] In the solution, the presence, density, and / or location of PT-RS in a sidelink channel (e.g., PSCCH and / or PSSCH) may be determined based on DM-RS density (e.g., the number of symbols used for DM-RS). In an example, if the DM-RS density of a sidelink channel is below a threshold, the PT-RS may not be present in the sidelink channel, otherwise the PT-RS may be present in the sidelink channel. In another example, if the DM-RS density of a sidelink channel is below a threshold, a first PT-RS density may be used for the sidelink channel, otherwise a second PT-RS density may be used for the sidelink channel. The DM-RS density of the sidelink channel may be indicated in the associated PDCCH for sidelink channel resource allocation (e.g., SL-Mode_1).
[0363] In the solution, the RB offset of the PT-RS in the sidelink channel may be determined based on a WTRU identity (WTRU-id) of the transmitter WTRU or receiver WTRU. Alternatively, the RB offset of the PT-RS in the sidelink channel may be determined based on a destination identity, which may be a group ID (e.g., ProSe group ID) to which the sidelink channel may be transmitted. The WTRU-id may be an RNTI (e.g., C-RNTI, SL-RNTI) assigned to the WTRU (i.e., the transmitter WTRU or receiver WTRU). The WTRU-id and / or the group ID may be provided within a resource grant (e.g., from the PDCCH) for the sidelink transmission.
[0364] In another solution, the RB offset of a PT-RS in a channel (e.g., a sidelink channel) may be determined based on at least one of a scrambling code or sequence (e.g., an index or identity of the scrambling code or sequence) that may be used for transmission of the channel, a DM-RS (e.g., an index or identity of the DM-RS, such as an index or identity of a DM-RS sequence) that may be transmitted along with the channel, and / or a search space used for the channel or an associated channel (e.g., the search space of an associated PSCCH channel when transmitting a PT-RS in or along with a PSSCH).
[0365] Although features and elements are described above in certain combinations, one skilled in the art will understand that each feature or element may be used alone or in any combination with other features and elements. Also, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). Software and associated processors may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. [Industrial Applicability]
[0366] The present invention can be used in wireless systems.
Claims
1. A method performed by a network node, comprising the steps of: transmitting a first signal including control information indicating a number of scheduled resource blocks (RBs) to a wireless transmit / receive unit (WTRU); transmitting a second signal to the WTRU, the second signal including a phase tracking reference signal (PT-RS), the PT-RS being transmitted via the scheduled resource blocks, a density of the PT-RS being based on the number of scheduled RBs, an RB offset value for the PT-RS being based on a WTRU identity (WTRU-ID) modulo a maximum RB offset value, the maximum RB offset value being based on the density of the PT-RS; A method for providing the above.
2. The method of claim 1 , wherein the density of the PT-RS has a value of 2 or 4.
3. The method of claim 1, wherein the number of scheduled RBs modulo the density of the PT-RS is zero.
4. 2. The method of claim 1, wherein the maximum RB offset value is based on both the number of scheduled resource blocks and the density of the PT-RS, provided that the number of scheduled resource blocks modulo the density of the PT-RS is not zero.
5. The method of claim 1 , wherein the control information is associated with the WTRU-ID.
6. The method of claim 1, wherein the WTRU-ID is a C-RNTI.
7. The method of claim 1 , wherein the RB offset value is a set of numbers starting with zero.
8. The method of claim 1, wherein the density of the PT-RSs is based on a number of RBs that include at least one of the PT-RSs within the scheduled RBs.
9. The method of claim 1, wherein the signal with the PT-RS is transmitted in a scheduled PUSCH or received in a scheduled PDSCH.
10. transmitting a first signal including control information indicating a number of scheduled resource blocks (RBs) to a wireless transmit / receive unit (WTRU); and transmitting a second signal to the WTRU, the second signal including a phase tracking reference signal (PT-RS), the PT-RS being transmitted via the scheduled resource blocks, a density of the PT-RS being based on the number of scheduled RBs, an RB offset value for the PT-RS being based on a WTRU identity (WTRU-ID) modulo a maximum RB offset value, and the maximum RB offset value being based on the density of the PT-RS. A network node comprising:
11. The network node of claim 10, wherein the density of the PT-RS has a value of 2 or 4.
12. The network node of claim 10, wherein the number of scheduled RBs modulo the density of the PT-RS is zero.
13. 11. The network node of claim 10, wherein the maximum RB offset value is based on both the number of scheduled resource blocks and the density of the PT-RS, provided that the number of scheduled resource blocks modulo the density of the PT-RS is not zero.
14. The network node of claim 10, wherein the control information is associated with the WTRU-ID.
15. The network node of claim 10, wherein the WTRU-ID is a C-RNTI.
16. The network node of claim 10, wherein the RB offset value is a set of numbers starting with zero.
17. The network node of claim 10, wherein the density of the PT-RSs is based on a number of RBs that include at least one of the PT-RSs within the scheduled RBs.
18. The network node of claim 10, wherein the signal with the PT-RS is transmitted in a scheduled PUSCH or received in a scheduled PDSCH.
