Phase-tracking reference signal pattern configuration and signaling in wireless communication systems

Abstract

The present disclosure relates to a Phase Tracking Reference Signal (PTRS) resource pattern configuration and signaling. Multiple PTRS resource pattern types may be predefined. Various methods are disclosed in which the PTRS resource pattern configuration for a particular PTRS resource pattern type is communicated and signaled. The disclosed PTRS resource pattern configuration and signaling may facilitate more efficient and flexible PTRS implementation for phase noise compensation in high frequency radio bands.

Description

[Technical Field]

[0001] This disclosure generally relates to wireless access communication networks, and more particularly to phase-tracking reference signal resource pattern configuration and signaling. [Background technology]

[0002] background Radio access communication networks are expanding to radio interfaces that support higher frequency bands. Conventional methods for mitigating phase noise may not be suitable in these higher frequency bands. Phase-tracking reference signals (PTRS) can be used and distributed across radio communication resource patterns in these higher frequency bands and measured. Such measurements can be used for more effective compensation of phase noise. Multiple coexisting PTRS resource patterns can be designed for selection based on a specific channel. The design of a system utilizing these PTRS resource patterns must include the configuration of these multiple coexisting PTRS patterns and a mechanism for signaling a specific configured PTRS resource pattern among the multiple coexisting PTRS resource patterns. [Overview of the project] [Means for solving the problem]

[0003] overview This disclosure relates to methods, systems, and devices for PTRS resource pattern configuration and signaling. Multiple PTRS resource pattern types may be predefined. Various methods are disclosed for communicating and signaling PTRS resource pattern configurations of a particular PTRS resource pattern type. The disclosed PTRS resource pattern configuration and signaling can facilitate more efficient and flexible PTRS implementations for phase noise compensation in the high-frequency radio band.

[0004] In one embodiment, a method performed by a wireless terminal device is disclosed. This method includes receiving a control message, the control message including PTRS resource configuration parameters; obtaining signaling information, the signaling information indicating a particular PTRS resource pattern type among a plurality of predefined PTRS resource pattern types; decoding the control message to extract one or more of a set of PTRS resource configuration parameters based on the particular PTRS resource pattern type; and receiving or transmitting a PTRS signal over a wireless resource specified by one or more of the set of PTRS resource configuration parameters.

[0005] In another embodiment, a method performed by a wireless access network node is disclosed. This method includes selecting a specific PTRS resource pattern type from a plurality of predefined PTRS resource pattern types, constructing a control message the control message includes a set of phase-tracking reference signal (PTRS) resource configuration parameters, determining one or more parameter values ​​from the set of PTRS resource configuration parameters to specify a PTRS resource pattern having a specific PTRS resource pattern type, transmitting the control message to a wireless terminal device, and providing signaling information to the wireless terminal device to indicate a specific PTRS resource pattern type.

[0006] In another embodiment, a wireless device comprising a processor and memory is disclosed. The processor may be configured to read computer code from memory in order to carry out any of the methods described above.

[0007] In yet another embodiment, a computer program product is disclosed comprising a non-temporary computer-readable program medium in which computer code is stored. When the computer code is executed by a processor, it can cause the processor to perform any one of the methods described above.

[0008] Other aspects and alternative forms of the above-described embodiments and their implementations are described in more detail in the following drawings, description, and claims. The present invention provides, for example, the following: (Item 1) A method performed by a wireless terminal device, Receiving a control message, wherein the control message includes a set of phase-tracking reference signal (PTRS) resource configuration parameters, The method involves obtaining signaling information, wherein the signaling information indicates a specific PTRS resource pattern type among a plurality of predefined PTRS resource pattern types. Decoding the control message in order to extract one or more of the set of PTRS resource configuration parameters based on the specified PTRS resource pattern type, Receiving or transmitting a PTRS signal via a radio resource specified by one or more of the set of PTRS resource configuration parameters. Methods that include... (Item 2) The aforementioned multiple predefined PTRS resource pattern types are: Distributed PTRS resource pattern types and Block PTRS resource pattern type, Block PTRS resource pattern types that do not have cyclic sequences or zero-power tones. Block PTRS resource pattern types that have a cyclic sequence and do not have zero-power tones, or Block PTRS resource pattern type without a cyclic sequence and with zero-power tones. A block PTRS resource pattern type that includes one of the following, Ladder PTRS resource pattern types and The method described in item 1, comprising at least two of the following. (Item 3) The aforementioned specific PTRS resource pattern type is a block PTRS resource pattern type that includes a block of consecutive resource elements in the frequency domain, One or more of the set of PTRS resource configuration parameters includes at least the block size for the block of the contiguous resource elements. The method described in item 2. (Item 4) The method according to item 3, wherein one or more of the set of PTRS resource configuration parameters further include a length configuration parameter that specifies the length of a cyclic reference signal sequence within each block of consecutive resource elements in the frequency domain. (Item 5) The method according to item 3, wherein one or more of the set of PTRS resource configuration parameters further include a configuration parameter that specifies the number of zero-power tones in each block of consecutive resource elements in the frequency domain. (Item 6) The aforementioned specific PTRS resource pattern type is the ladder PTRS resource pattern type, One or more of the set of PTRS resource configuration parameters includes at least an offset configuration parameter that specifies resource element offsets between adjacent symbols for the particular PTRS resource pattern type. The method described in item 2. (Item 7) The method according to item 1, wherein the control message belongs to a set of predefined control messages in distinct formats corresponding to the plurality of predefined PTRS resource pattern types. (Item 8) The method according to item 7, wherein obtaining the signaling information includes extracting the format information of the control message from the header of the control message. (Item 9) Acquiring the aforementioned signal information means In addition to the aforementioned control message, a signaling message is received, Extracting the signaling information from the signaling message and The method described in item 7, including the method described in item 7. (Item 10) The method according to item 9, wherein the control message is a radio resource control (RRC) message and the signaling message is a downlink control information (DCI) message. (Item 11) Obtaining the aforementioned signaling information means Extract the value of at least one other independent system configuration parameter, Deriving the signaling information based on the value of at least one other independent system configuration parameter. The method described in item 7, including the method described in item 7. (Item 12) The aforementioned at least one other independent system configuration parameter is: Number of scheduled resource blocks, Scheduled MCS, Number of scheduled resource blocks, frequency range, or Subcarrier spacing The method described in item 11, which includes at least one of the following. (Item 13) The method according to item 1, wherein the set of PTRS resource configuration parameters includes a set of configuration parameters for all of the multiple predefined PTRS resource pattern types. (Item 14) The method according to item 13, wherein one or more of the set of PTRS resource configuration parameters include a subset of the set of PTRS resource configuration parameters that are activated for the particular PTRS resource pattern type. (Item 15) The remaining configuration parameters in the set of PTRS resource configuration parameters are ignored, as described in item 14. (Item 16) Obtaining the aforementioned signaling information means In addition to the aforementioned control message, a signaling message is received, Extracting the signaling information from separate signaling messages and The method described in item 14, including the method described in item 14. (Item 17) The method according to item 16, wherein the control message is a radio resource control (RRC) message and the signaling message is a downlink control information (DCI) message. (Item 18) Obtaining the aforementioned signaling information means Extract the value of at least one other independent system configuration parameter, Deriving the signaling information based on the value of at least one other independent system configuration parameter. The method described in item 14, including the method described in item 14. (Item 19) The aforementioned at least one other independent system configuration parameter is: Number of scheduled resource blocks, Scheduled MCS, Number of scheduled resource blocks, frequency range, or Subcarrier spacing The method described in item 18, which includes at least one of the following. (Item 20) Acquiring the aforementioned signal information means Extracting the value of the signature configuration parameter from the set of PTRS resource configuration parameters, Determining whether the value of the signature configuration parameter falls within a predefined valid range, The signal information is determined based on whether the value of the signature configuration parameter falls within the predefined valid range. The method described in item 14, including the method described in item 14. (Item 21) The plurality of predefined PTRS resource pattern types include at least two of the distributed PTRS resource pattern type, block PTRS resource pattern type, and ladder PTRS resource pattern type. The aforementioned signature configuration parameters are: The block size for a block of consecutive resource elements in the frequency domain for the aforementioned block PTRS resource pattern type, A length configuration parameter that specifies the length of the cyclic reference signal sequence in each block of consecutive resource elements in the frequency domain for the aforementioned block PTRS resource pattern type, A zero-power tone parameter that specifies the number of zero-power tones within each block of consecutive resource elements in the frequency domain for the aforementioned block PTRS resource pattern type, or Offset configuration parameter that specifies the resource element offset between adjacent symbols for the aforementioned specific PTRS resource pattern type. The method described in item 20, including one of the following. (Item 22) A method performed by a wireless access network node, Selecting a specific PTRS resource pattern type from several predefined PTRS resource pattern types, Constructing a control message, wherein the control message includes a set of phase-tracking reference signal (PTRS) resource configuration parameters, In order to specify a PTRS resource pattern having the aforementioned specific PTRS resource pattern type, one or more parameter values ​​from the set of PTRS resource configuration parameters are determined, The control message is transmitted to the wireless terminal device, To provide the wireless terminal device with signaling information to indicate the specific PTRS resource pattern type mentioned above. Methods that include... (Item 23) A wireless device comprising a processor and memory, wherein the processor is configured to read computer code from the memory in order to carry out the method described in any one of items 1 to 22. (Item 24) A computer program product comprising a non-temporary computer-readable program medium storing computer code, wherein the computer code, when executed by a processor, causes the processor to perform the method described in any one of items 1 to 22. [Brief explanation of the drawing]

[0009] [Figure 1]Figure 1 shows an exemplary wireless communication network comprising a wireless access network, a core network, and a data network.

[0010] [Figure 2] Figure 2 shows an exemplary radio access network including multiple mobile stations and radio access network nodes communicating with each other via a radio communication interface.

[0011] [Figure 3] Figure 3 shows an exemplary wireless communication resource grid in both the time domain and the frequency domain.

[0012] [Figure 4] Figure 4 shows an exemplary distributed resource pattern allocated to PTRS in both the time domain and the frequency domain.

[0013] [Figure 5] Figure 5 shows an exemplary block resource pattern allocated to PTRS in both the time domain and the frequency domain.

[0014] [Figure 6] Figure 6 shows an exemplary ladder resource pattern allocated to PTRS in both the time domain and the frequency domain.

[0015] [Figure 7] Figure 7 shows an exemplary cyclic sequence implementation for the block resource pattern allocated to PTRS in the frequency domain.

[0016] [Figure 8] Figure 8 shows an exemplary implementation of a block resource pattern allocated to a PTRS in the frequency domain with zero-power resource elements. [Modes for carrying out the invention]

[0017] Detailed explanation The technologies and examples of the implementations and / or embodiments described herein can be used to facilitate wireless resource allocation, configuration, and signaling in wireless access networks. The term “exemplary” is used to mean “an example of” and does not mean an ideal or preferred example, implementation, or embodiment unless otherwise specified. Section headers are used in this disclosure to facilitate understanding of the disclosed implementations and are not intended to limit the disclosed technologies of a section to the corresponding section only. The disclosed implementations may be further embodied in various different forms, and therefore the scope of the subject matter of this disclosure or claims is intended to be construed as not being limited to any of the embodiments described below. Various implementations may be embodied as methods, devices, components, systems, or non-temporary computer-readable media. Thus, embodiments of this disclosure may take the form of, for example, hardware, software, firmware, or any combination thereof.

[0018] This disclosure relates to methods, systems, and devices related to wireless access networks, and more specifically to phase-tracking reference signal (PTRS) resource pattern configuration and signaling. While this disclosure provides exemplary implementations in several specific generations of cellular network systems, the underlying principles are applicable to other generations of cellular network systems and other general non-cellular wireless network systems. Overview of Wireless Networks

[0019] The exemplary wireless communication network shown as 100 in Figure 1 may include user equipment (UEs) 110, 111, and 112, a carrier network 102, various service applications 140, and other data networks 150. The carrier network 102 may include, for example, access networks 120 and 121, and a core network 130. The carrier network 110 may be configured to transmit voice, data, and other information (collectively referred to as data traffic) between UE 110, between UE 111 and UE 112, between the UEs and service applications 140, or between the UEs and other data networks 150. Access networks 120 and 121 may be configured as various wireless access network nodes (WANNs, also called base stations) for interacting with the UEs on one side of a communication session and the core network 130 on the other side. The core network 130 may include various network nodes configured to control the communication session and perform network access management and traffic routing. Service applications 140 may be hosted by various application servers located outside but connected to the core network 130. Similarly, other data networks 150 can also be connected to the core network 130.

[0020] In the wireless communication network 100 in Figure 1, UEs can communicate with each other via a wireless access network. For example, UE110 and UE112 can be connected to the same access network 120 and communicate with each other via it. UEs can communicate with each other via both the access network and the core network. For example, UE110 may be connected to access network 120, while UE111 may be connected to access network 121, and therefore UE110 and UE111 can communicate with each other via access networks 120 and 121, as well as the core network 130. UEs can further communicate with service applications 140 and data networks 150 via the core network 130. Furthermore, UEs can communicate directly with each other via sidelink communication, as shown by 113.

[0021] Figure 2 further illustrates an exemplary system diagram of a wireless access network 120, including a WANN 202 that services UE110 and UE112 via a wireless interface 204. Each of UE110 and UE112 may be a mobile or fixed terminal device with a mobile access unit, such as a SIM / USIM module, installed for accessing the wireless communication network 100. UE110 and UE112 may be implemented as terminal devices, including but not limited to mobile phones, smartphones, tablets, laptop computers, in-vehicle communication equipment, roadside communication equipment, sensor devices, smart appliances (such as televisions, refrigerators, ovens), or other devices that can communicate wirelessly over the network. As shown in Figure 2, each of the UEs, such as UE112, may include a transceiver circuit 206 coupled to one or more antennas 208 to enable wireless communication with another UE, such as WANN120 or UE110. The transceiver circuit 206 may also be coupled to a processor 210, which may also be coupled to a memory 212 or other storage device. Memory 212 may be temporary or non-temporary and, when read and executed by processor 210, may store computer instructions or code that cause processor 210 to perform various methods described herein.

[0022] Similarly, WANN120 may include a base station or other radio network access point that can communicate radio with one or more UEs via a radio interface 204 and communicate with the core network 130. For example, WANN120 may be implemented in the form of a 2G base station, 3G nodeB, LTE eNB, 4G LTE base station, 5G NR base station, 5G central unit base station, or 5G distributed unit base station, without limitation. Each of these types of WANNs may be configured to perform a corresponding set of radio network functions. WANN202 may include a transceiver circuit 214 coupled to one or more antennas 216, which may include various forms of antenna towers 218, to enable radio communication with UE110 and UE112. The transceiver circuit 214 may be coupled to one or more processors 220, which may be further coupled to memory 222 or other storage devices. Memory 222 may be temporary or non-temporary and may store instructions or code that, when read and executed by the processor 220, cause the processor 220 to perform various functions of WANN120 as described herein.

[0023] The radio transmission resources for the radio interface 204 include frequency, time, and spatial resources. For example, the available frequency and time resources (also called radio resources or radio transmission resources) available for radio communication are shown as 300 in Figure 3. The transmission resources 300 include time-domain and frequency-domain resources that can be allocated to carry DL or UL data or control information. The transmission resources 300 can be further divided into multiple divisions to support more flexible scheduling, configuration, and allocation of transmission resources. For example, in the time domain, the transmission resources 300 may be divided into M divisions, and in the frequency domain, the transmission resources 300 may be divided into N divisions. Thus, the transmission resources 300 can be thought of as a resource grid containing M × N resource divisions, where M and N are both positive integers. In Figure 3, 312 and 314 are shown as two exemplary divisions. Organizing the transmission resources 300 into the resource divisions in Figure 3 facilitates more efficient resource allocation, configuration, and utilization.

[0024] The time and frequency division of the radio resource 300 can be performed at various hierarchical levels. Figure 3 shows only an exemplary division at a particular level. The configuration and identification of time and frequency resources can be performed at any level. For example, the radio resource 300 can be divided into resource blocks (RBs) representing the smallest units of radio resources that can be allocated to a UE for communication with the WANN. Each RB can be further divided into separately identifiable and configurable subunits in both time and frequency. For example, in the frequency domain, an RB can be divided into a configurable number of subcarriers with configurable subcarrier spacing. In the time domain, an RB can occupy time slots having configurable time lengths that can be further divided into several time units, each corresponding to a symbol in, for example, orthogonal frequency division multiplexing (OFDM) or other modulation schemes. Each unit, including subcarriers in the frequency domain and symbols in the time domain, is sometimes called a resource element (RE) representing the smallest identifiable and configurable unit of the radio resource 300. The radio resource 300 can be allocated and configured at higher levels. For example, in the time domain, a subframe may contain a predetermined number (e.g., 7) time slots, and a frame may contain a predetermined number (e.g., 2) subframes. In another example, blocks of subcarriers in several RBs in the frequency domain may be organized as various frequency channels, each assigned for different purposes in transmitting data and control information. These frequency channels may include, but are not limited to, uplink frequency channels (e.g., physical uplink shared channels (PUSCH), physical uplink control channels (PUCCH), etc.) and downlink frequency channels (e.g., physical downlink shared channels (PDSCH), physical uplink control channels (PDCCH), etc.). The term “frequency channel” is used to refer to a set of subcarriers in a particular frequency range, but the term “channel” itself may be used to refer to a broader concept of resource units that is not limited to the frequency domain.

[0025] While the above description focuses on time and frequency resources 300, it may be combined with spatial multiplexing based on the use of multiple antennas and beamforming in wireless transmission. Such spatial resource allocation and configuration may be part of the overall wireless resource allocation and configuration. The principles underlying the various implementations included in this disclosure are intended to be applicable to wireless resource allocation and configuration encompassing all time, frequency, and spatial dimensions. Phase-Tracking Reference Signal (PTRS) Pattern

[0026] In mobile environments, the signal transmission quality and characteristics between the WANN and UE at the various levels of wireless resource units mentioned above can be significantly influenced by many factors. Such quality / characteristics can be tracked and measured in order to allocate / configure these resource units more efficiently and adaptively for various communication purposes. Such tracking can be performed at the receiving wireless network node by measuring various types of reference signals that have known characteristics and are transmitted from one wireless network node to another.

[0027] Among various types of reference signals, a phase-tracking reference signal (PTRS) can be used to track phase noise within a channel so that detected phase noise can be compensated for. In different frequency ranges of the electromagnetic spectrum available for wireless communication, the preferred PTRS configuration may differ to provide a sufficiently accurate phase noise estimate for various channels within a given frequency range. The design of a PTRS may include, for example, the frequency and time patterns of the radio resource elements on which the PTRS signal is carried.

[0028] In some implementations, different types of PTRS resource patterns may be designed and used to achieve phase noise reduction under different circumstances (e.g., different frequency bands). PTRS patterns can be characterized by various PTRS pattern configuration parameters, as will be described in more detail below.

[0029] An example of a PTRS pattern is shown as 400 in Figure 4. In the exemplary PTRS pattern 400, resource elements carrying the phase-tracking reference signal can be uniformly and periodically distributed across the allocated frequency bandwidth by an RE frequency period shown as 420. In the example in Figure 4, the RE period 420 for PTRS is exemplified as 4 subcarriers, but any other number of subcarriers can be used as the PRTS frequency period. In Figure 4, the shaded areas such as 402-410 represent REs carrying the phase-tracking reference signal, while the other open areas represent REs carrying data and / or other information.

[0030] Another example of a PTRS pattern is shown as 500 in Figure 5. In Figure 5, again, the shaded area represents the RE carrying the phase-tracking reference signal, while the other open area represents the RE carrying data and / or other information. In the exemplary PTRS pattern 500, called a block PTRS pattern, the resource elements carrying the phase-tracking reference signal can also be distributed uniformly and periodically across the allocated frequency bandwidth by the RE period shown as 504. However, in the block PTRS pattern 500, the PTRS can be distributed as subcarrier blocks, each containing a consecutive number of subcarriers in the frequency domain. In the example in Figure 5, the RE frequency period 504 for the PTRS is shown as 8 subcarriers in the frequency domain, but any other number of subcarriers can be used as the PRTS frequency period. Similarly, in the example in Figure 5, the consecutive subcarriers of each PTRS block 502 are shown as having 5 subcarriers, but any other number of subcarriers can be used as the respective size of the PRTS subcarrier blocks in the frequency domain.

[0031] In the exemplary PTRS patterns 400 and 500 above, the PTRS signal is shown as occupying all symbols in the time domain for each assigned PTRS subcarrier; however, actual implementations are not limited to this. In some implementations, subgroups rather than entire symbols may be assigned to PTRS. For example, PTRS REs may be allocated periodically in the time domain, and PTS REs may occupy a constitutable proportion of symbols in the time domain.

[0032] A third example of a PTRS pattern is shown as 600 in Figure 6. In Figure 6, again, the shaded area represents REs that carry the phase-tracking reference signal, while the other open area represents REs that carry data and / or other information. In the exemplary PTRS pattern 600, the resource elements that carry the phase-tracking reference signal can be distributed as a ladder in the frequency and time domains. In the ladder PTRS pattern 600, the number of PTRS carrier REs is periodically distributed across the bandwidth allocated as a ladder. In the example in Figure 6, the frequency position of a PTRS RE from one symbol to the next shifts by one subcarrier. Similarly, the position of a PTRS RE from one subcarrier to the next shifts by one symbol. A PTRS RE at each symbol position along the frequency dimension can be characterized by its frequency period. In the example in Figure 6, the frequency period is 4 subcarriers. Similarly, a PTRS RE at each subcarrier position along the time dimension can be characterized by its time period. In the example in Figure 6, the time period is 4 symbols. The frequency offset between symbols in PTRS RE is shown as one subcarrier, but any other subcarrier offset may be used. Similarly, the symbol offset from subcarrier to subcarrier for PTRS RE is exemplified as one symbol, but other symbol offsets may be used. Furthermore, the ladder pattern in Figure 6 is illustrated as going from the bottom left to the top right (upward ladder), but it may also be implemented as going from the top left to the bottom right (downward ladder).

[0033] In the case of the block PTRS pattern shown at 500 in Figure 5, the intra-block reference signal sequence used within each block in the frequency domain can be implemented in various exemplary options. In one of the sequence options, as shown by 700 in Figure 7, the subcarriers within each block of the PTRS 703 may be configured to carry a cyclic sequence 701. For example, the cyclic sequence 700 may include a basic sequence 702 and cyclic sequences 704 and 706. The basic sequence 702 is S1...,S p ,...S q ,...,S N It may include a reference signal sequence. The cyclic sequence 704 is the leading cyclic portion (S1...,S) of the basic cyclic sequence 702. p ) can be implemented as the tail cycle portion (S) of the basic cycle sequence 702. q ,...,S N It can be implemented as follows:

[0034] In another exemplary in-block PTRS reference signal configuration, as shown in 800 in Figure 8, the subcarriers within the PTRS block 802 in the frequency domain may be configured to carry the PTRS signal by distributing the reference signal power to a subgroup of subcarriers (called non-zero power, i.e., NZP subcarriers) and leaving the remaining subcarriers in the block as zero-power subcarriers (called zero-power or ZP subcarriers). Distributing the reference signal power in this way within the PTRS block may, in some situations, help improve the accuracy and efficiency of the reference signal sounding. The NZP subcarriers may be cladded by ZP subcarriers, where the ZP subcarriers may function as guard tones. In the particular example in Figure 8, the PTRS signal is concentrated on a single NZP subcarrier 810 within the PTRS block, while all other subcarriers 820, 822, 824, 830, 832, and 834 are ZP subcarriers or guard tones. In some other implementations, two or more central subcarriers in a PTRS subcarrier block may be configured as NZP subcarriers, while the remaining subcarriers within the PTRS block may be configured as ZP subcarriers.

[0035] The three PTRS resource patterns described above are merely examples. Other different PTRS resource patterns may be designed as additional PTRS configuration options. In different electromagnetic spectrum ranges and different mobile application scenarios, one of these patterns may be more appropriate than the others.

[0036] The current standardized spectrum for cellular radio communications is generally lower than 52.6 GHz. With the rapid growth of user data, the demand for a broader electromagnetic spectrum for cellular radio communications continues to accelerate. As the radio spectrum expands to higher frequency bands, including some resource-rich licensed spectra and free licensed spectra (such as the 52.6 GHz to 71 GHz frequency spectrum), phase noise increases, thereby requiring more advanced phase noise mitigation methods, such as De-ICI technology, and higher-order modulation at the receiver side. As bandwidth expands and subcarrier spacing increases (e.g., from 480 kHz to 960 kHz), receiver-side ICI mitigation methods may become insufficient due to their complexity, potentially necessitating the implementation of more flexible and versatile PTRS patterns. Block PTRS, for example, could be considered to reduce the complexity of phase noise mitigation. Individual definitions of PTRS pattern types

[0037] In some implementations, multiple types of PTRS patterns may be defined by separate PTRS pattern configuration data structures. Each PTRS pattern type (including, but not limited to, distributed PTRS pattern types, block PTRS pattern types with various reference signal sequence options, and ladder PTRS pattern types described above in relation to Figures 4-8) may be associated with a corresponding set of PTRS pattern configuration parameters. The PTRS pattern configuration data structure for a particular type of PTRS pattern may include data elements or data items that represent values ​​for the corresponding set of PTRS pattern configuration parameters. Values ​​in such a data structure can uniquely specify a PTRS pattern of that particular PTRS pattern type and thus identify the location of the RE carrying the PTRS signal within the allocated resource grid. In some implementations, PTRS pattern configuration data structures for uplink PTRS patterns and downlink PTRS patterns may be further defined separately for each PTRS pattern type.

[0038] As a simple example, the uplink and downlink PTRS patterns of the distributed PTRS pattern type can be defined by the following PTRS pattern configuration data structure: [ka] [ka]

[0039] More specifically, the uplink PTRS configuration data structure and downlink PTRS configuration data structure described above specify six exemplary PTRS pattern configuration parameters for PTRS patterns of the distributed PTRS pattern type. These exemplary pattern configuration parameters include: For example, the uplink and downlink PTRS pattern configuration parameter "frequencyDensity" represents the PTRS frequency density of a cyclic prefix orthogonal frequency division multiplexed waveform as a function of the scheduled bandwidth. This essentially specifies the density of PTRS REs in the frequency domain. In some exemplary implementations, the "frequencyDensity" parameter may be specified as an integer representing the number of REs in each RB assigned to the PTRS. In some implementations, the frequency density of PTRS REs may be indirectly specified by the scheduled bandwidth via a predefined mapping between the scheduled bandwidth range and the frequency density of the PTRS. This configuration parameter may, for example, specify a PTRS frequency domain period of 420 in Figure 4 above. For example, the uplink and downlink PTRS pattern configuration parameter "timeDensity" represents the PTRS time density of a cyclic prefix quadrature frequency division multiplexed waveform as a function of the MCS. This essentially specifies the density of PTRS REs in the time domain. In some exemplary implementations, the "timeDensity" parameter may indicate the number of symbols within each time slot assigned to the PTRS. In some implementations, the time density of PTRS symbols may be indirectly specified by the scheduled modulation coding scheme (MCS) or its index, via a predefined mapping between the range of the scheduled MCS or its index and the time density of the PTRS. This parameter represents the time-domain PTRS period described above in relation to Figure 4. • Downlink PTRS pattern configuration parameter "epre-Ratio" for specifying the power ratio between the PTRS signal and the data signal. For example, the uplink and downlink PTRS pattern configuration parameter "resourceElementOffset" is used to specify the subcarrier offset for PTRS for cyclic prefix orthogonal frequency division multiplexing. • The uplink and downlink PTRS pattern configuration parameter "maxNrofPorts" specifies the maximum number of PTRS ports for cyclic prefix orthogonal frequency division multiplexing. • Uplink PTRS pattern configuration parameter "ptrs-Power" for specifying the output boost coefficient for each PTRS port. The uplink PTRS pattern configuration parameter "sampleDensity" specifies the sample density of the PTRS for DFT-s-OFDM, pre-DFT (DFT stands for Discrete Fourier Transform), associated with a set of thresholds indicating the dependency between the presence of PTRS and the scheduled bandwidth, and specific parameters that the UE should use depending on the scheduled bandwidth. • Uplink PTRS pattern configuration parameter "timeDensityTransformPrecoding" for specifying the time density (at the OFDM symbol level) of the PTRS for DFT-s-OFDM waveforms.

[0040] The values ​​of these parameters uniquely identify the signal power level and position of the RE in both the frequency and time domains, which is configured to carry the PTRS signal for the configured PTRS pattern of the distributed PTRS pattern type.

[0041] As another example, uplink and downlink PTRS patterns of a block PTRS pattern type that do not have cyclic sequences and ZP tones can be defined by the following PTRS pattern configuration data structure: [ka] [ka]

[0042] More specifically, the PTRS configuration data structure described above specifies eight exemplary PTRS pattern configuration parameters for PTRS patterns of block PTRS pattern types that do not have cyclic sequences and ZP tones. Compared to the exemplary PTRS data structure for distributed PTRS pattern types described above, the additional PTRS pattern configuration parameters include: The uplink and downlink PTRS pattern configuration parameter "sizeofBlock" specifies the number of consecutive PTRS REs within each PTRS block in the frequency domain. This parameter can specify, for example, a block size of 502 in Figure 5. • Uplink and downlink PTRS pattern configuration parameter "nrofBlock" for specifying the number of PTRS blocks in the frequency domain.

[0043] In this example of a PTRS pattern configuration data structure for a block PTRS pattern type PTRS pattern, the parameter "frequencyDensity" in the distributed PTRS pattern configuration data structure definition is unnecessary and can therefore be removed, as the PTRS RE count can be calculated via the "sizeofBlock" and "nrofBlock" parameters. Specifically, the PTRS RE count can be calculated by multiplying "sizeofBlock" (the number of REs in each PTRS block) by "nrofBlock" (the number of PTRS blocks). The PTRS position can be further determined in conjunction with the parameter "resourceElementOffset".

[0044] The values ​​of these configuration parameters described above uniquely identify the signal power level and position of the RE in both the frequency and time domains configured to carry the PTRS signal for a configured PTRS pattern of a block PTRS pattern type that does not have a cyclic sequence and ZP tone.

[0045] As a further example, uplink and downlink PTRS patterns of a block PTRS pattern type that have a cyclic sequence and do not have ZP tones can be defined by the following PTRS pattern configuration data structure: [ka]

[0046] More specifically, the PTRS configuration data structure described above specifies nine exemplary PTRS pattern configuration parameters for a PTRS pattern of a block PTRS pattern type that has a cyclic sequence but does not have a ZP tone. Compared to the exemplary data structure described above for a block PTRS pattern type that does not have a cyclic sequence and a ZP tone, additional PTRS pattern configuration parameters include: • Uplink and downlink PTRS pattern configuration parameter "lengthofCircular" for specifying the length of the circular sequence within each PTRS block in the frequency domain.

[0047] The values ​​of these parameters uniquely identify the signal power level and position of the RE in both the frequency and time domains, configured to carry PTRS signals for a configured PTRS pattern of a block PTRS pattern type that has a cyclic sequence and does not have ZP tones.

[0048] As a further example, uplink and downlink PTRS patterns of a block PTRS pattern type that have ZP tones and no cyclic sequences can be defined by the following PTRS pattern configuration data structure: [ka] [ka]

[0049] More specifically, the PTRS configuration data structure described above specifies nine exemplary PTRS pattern configuration parameters for a PTRS pattern of a block PTRS pattern type that has ZP tones but no cyclic sequences. Compared to the exemplary data structure described above for block PTRS pattern types without cyclic sequences and ZP tones, the additional PTRS pattern configuration parameters include: • Uplink and downlink PTRS pattern configuration parameter "nrofZPtones" for specifying the number of ZP tones within each PTRS block in the frequency domain.

[0050] The values ​​of these parameters uniquely identify the signal power level and position of the RE in both the frequency and time domains, configured to carry PTRS signals for a PTRS pattern of a block PTRS pattern type that has ZP tones and no cyclic sequences.

[0051] As yet another example, uplink and downlink PTRS patterns of a ladder PTRS pattern type can be defined by the following PTRS pattern configuration data structure: [ka]

[0052] More specifically, the PTRS configuration data structure described above specifies seven exemplary PTRS pattern configuration parameters for a ladder PTRS pattern type. Compared to the exemplary data structure for the distributed PTRS pattern type described above, the additional PTRS pattern configuration parameters include: • Uplink and downlink PTRS pattern configuration parameter "adjacentSymbolREOffset" for specifying the PTRS RE offset (frequency) between adjacent PTRS symbols.

[0053] Furthermore, the uplink and downlink PTRS pattern configuration parameter "resourceElementOffset" used in other patterns can be reinterpreted as the PTRS RE offset of the first PTRS symbol.

[0054] The values ​​of these parameters uniquely identify the signal power level and position of the RE in both the frequency and time domains, which is configured to carry the PTRS signal for the configured PTRS pattern of the ladder PTRS pattern type. Messaging and signaling of separately defined PTRS pattern configurations

[0055] Any of the above PTRS pattern configuration data structures can be implemented as a PTRS configuration message (or PTRS pattern configuration message) communicated from the WANN to the UE. The UE can receive the PTRS configuration message, decode the message, and determine various PTRS pattern configuration parameters. The values ​​of these PTRS pattern configuration parameters specify the power level of the PTRS signal and the position of the RE in the allocated resources that carry the PTRS signal. Thus, the UE can determine how to receive the actual downlink PTRS reference signal and how to transmit the actual uplink PTRS reference signal.

[0056] PTRS configuration messages can be implemented as part of or as a component of control messages, such as radio resource control (RRC) messages. However, the implementation of PTRS configuration messages is not limited to this. PTRS configuration messages can be carried by any other type of message that can be communicated from the WANN to the UE.

[0057] In some implementations, a single specific PTRS pattern type may be adopted from among the various PTRS pattern types described above. The format of the PTRS pattern configuration message for a single PTRS pattern type may be predetermined, stored, and followed by the WANN and UE. The WANN may follow such a format to construct the PTRS pattern configuration message and send it to the UE, while the UE may follow such a format to parse and decode the PTRS pattern configuration message received from the WANN in order to correctly obtain the PTRS pattern configuration parameters.

[0058] In some other implementations, multiple coexisting PTRS pattern types, such as those described above, may be employed and defined independently. Multiple corresponding message formats for these PTRS pattern types may be predetermined and stored by the WANN and UE. Before transmitting the actual PTRS reference signal, the WANN may select a downlink PTRS pattern type from multiple coexisting PTRS pattern types according to the communication conditions (e.g., frequency range, subcarrier spacing), construct a downlink PTRS pattern configuration message according to the corresponding message format, and send it to the UE for the UE to determine the configured downlink PTRS pattern. Similarly, the WANN may determine the PTRS pattern type for the UE to transmit the uplink PTRS signal, construct an uplink PTRS configuration message according to the corresponding message format, and send it to the UE for the UE to determine the configured uplink PTRS pattern.

[0059] When multiple PTRS pattern types are employed and coexist, the WANN may need to signal to the UE which type of PTRS pattern configuration is included in the PTRS configuration message in order for the UE to correctly decode the PTRS configuration message it receives. Such signaling may be provided by the WANN, either explicitly or implicitly, as described below.

[0060] In some implementations of explicit signaling of PTRS pattern types when multiple PTRS pattern types coexist, each PTRS pattern type may be associated with a distinct type or format of PTRS configuration messages. The message format or type may be included in the header of the PTRS configuration message to indicate the type of PTRS pattern. The UE can determine the PTRS pattern type by parsing the message header and then decode the received PTRS configuration message using a predetermined message format for a particular PTRS pattern. For example, RRC message types or formats may be defined corresponding to the coexisting PTRS pattern types adopted and their configuration parameter sets.

[0061] In some alternative implementations for explicit signaling of PTRS pattern types when multiple PTRS pattern types coexist, a single message type may be used in the message header to indicate that the message is for PTRS pattern configuration. Additional signaling information may be provided from the WANN to the UE to specify the PTRS pattern type selected from among multiple PTRS pattern types. Such signaling may be provided, for example, via DCI signaling or other signaling paths. Based on such signaling information, the UE can determine the PTRS pattern type corresponding to the received PTRS configuration message and, based on the determined PTRS pattern type, decode the PTRS configuration parameters contained in the PTRS configuration message.

[0062] In some implementations for implicit signaling of PTRS pattern types when multiple PTRS pattern types coexist, dedicated signaling information to indicate the PTRS pattern type may not be provided. Instead, such signaling may be implicitly embedded in other existing system configuration parameters included in other system configuration messages.

[0063] For example, a PTRS pattern type may be associated with and indicated by at least one of the parameters, including but not limited to the scheduled number of RBs, frequency range, scheduled MCS, and subcarrier intervals within various RRC messages. The UE may determine a PTRS pattern type from among several coexisting PTRS pattern types according to the values ​​of these other configuration parameters, and then decode the received PTRS configuration message using a known message format corresponding to the determined PTRS pattern type to correctly extract the corresponding PTRS configuration parameters for identifying the power level and location of the uplink or downlink PTRS reference signal.

[0064] The following is a non-limiting detailed example of using one or a combination of any number of other system configuration parameters, such as the scheduled RB number (bandwidth), scheduled MCS, subcarrier spacing, and frequency range, to implicitly signal and indicate the PTRS pattern type: [ka] [ka] [ka]

[0065] In the example above, N is an integer, and N > N RB0 Therefore, M is an integer and M > ptrs - MCS1. RB0 And ptrs-MCS1 can be a predefined value.

[0066] PTRS pattern type 1 may refer to, for example, a distributed PTRS pattern type. PTRS pattern type 2 may refer to one of the following PTRS pattern types: block PTRS without cyclic sequences and ZP tones, block PTRS with cyclic sequences, block PTRS with ZP tones, and ladder PTRS.

[0067] The above example uses various system configuration parameters to implicitly signal one of two PTRS types. In some implementations, these and other system configuration parameters may be used individually or in any combination to implicitly indicate three or more types of PTRS patterns. For example, any one of the distributed PTRS pattern type, the block PTRS pattern type without a cyclic sequence, the block PTRS pattern type with a cyclic sequence, the block PTRS pattern type with a ZP tone, and the ladder PTRS pattern type may form multiple types of PTRS patterns adopted by the system, and the signaling or indication of a particular pattern may be provided by any individual or combination of the above configuration parameters. Aggregated definition of PTRS pattern type

[0068] In some alternative implementations, when multiple types of PTRS patterns coexist, they may be defined not by separately defined and independently defined PTRS configuration data structures, but by an aggregated PTRS configuration data structure. Exemplary aggregated uplink PTRS configuration data structures and exemplary aggregated downlink PTRS configuration data structures are shown below: [ka] [ka]

[0069] Each of the above PTRS configuration data structures essentially aggregates all the PTRS configuration parameters required for all coexisting PTRS pattern types into a single data structure. The exemplary parameters included in the above aggregated PTRS data structures are similar to those described above for separately defined PTRS data structures, using distributed PTRS pattern types, block PTRS pattern types (with cyclic sequences or ZP tones), and ladder PTRS pattern types as examples. Aggregated PTRS pattern configuration messaging and signaling

[0070] The aggregated PTRS pattern configuration data structure described above may be implemented as a PTRS pattern configuration message communicated from the WANN to the UE. The UE may receive the PTRS pattern configuration message. The UE may further receive signaling information indicating the PTRS pattern type among several coexisting PTRS pattern types selected by the WANN. Based on both the received PTRS pattern configuration message and the PTRS pattern signaling information, the UE may decode the PTRS pattern configuration message and selectively extract various relevant PTRS pattern configuration parameters from the PTRS pattern configuration message according to the signaled PTRS pattern type. The values ​​of these selectively extracted PTRS pattern configuration parameters specify the power level of the PTRS signal and the position of the RE among the allocated resources carrying the PTRS signal. Thus, the UE can determine how to receive the actual downlink PTRS reference signal and how to transmit the actual uplink PTRS reference signal.

[0071] PTRS pattern configuration messages can be implemented as part of or as a component of control messages, such as radio resource control (RRC) messages. However, the implementation of PTRS pattern configuration messages is not limited to this. PTRS pattern configuration messages can be carried by any other type of message that can be communicated from the WANN to the UE.

[0072] Only a subset of the PTRS pattern configuration parameters from all the parameters defined in the aggregated PTRS pattern configuration message above may be applicable to a particular PTRS pattern type among several coexisting PTRS pattern types. The association between the parameter subset and the corresponding PTRS pattern type may be stored by the UE and WANN. Before transmitting the actual PTRS reference signal, the WANN may select a downlink PTRS pattern type from several coexisting PTRS pattern types depending on the communication conditions (e.g., frequency range, subcarrier spacing, etc.) and construct a downlink aggregated PTRS configuration message with the set of PTRS configuration parameters corresponding to the specified selected PTRS pattern type. The WANN may provide the WANN with any further signaling information necessary to indicate the selected PTRS pattern type. The UE can then correctly decode the PTRS pattern configuration parameters by considering only the relevant subset of parameters as activated. Similarly, the WANN may determine the PTRS pattern type for the UE to transmit uplink PTRS signals, construct an uplink aggregated PTRS configuration message with the specified associated PTRS pattern configuration parameters, and send it to the UE along with PTRS pattern type signaling information for decoding the received PTRS pattern configuration message and extracting a set of activated PTRS pattern configuration parameters to identify the power level and resource location of the RE for carrying uplink PTRS reference signals.

[0073] Some PTRS pattern configuration parameters specified in the aggregated PTRS pattern configuration message are applicable to all pattern types and are therefore always activated. For example, the parameters "timeDensity", "frequencyDensity", "epre-Ratio", and "maxNrofPorts" can always be activated. Some other parameters may only be relevant to specific PTRS pattern types and are therefore only activated when the corresponding PTRS pattern type is indicated. For example, the "sizeofBlock" parameter is activated only when a block PTRS pattern is indicated; the "sizeofBlock" and "lengthofCircular" parameters are activated only when a block PTRS pattern with a circular sequence is indicated; the "sizeofBlock" and "nrofZPtones" parameters are activated only when a block PTRS pattern of ZP tones is indicated; only the "adjacentSymbolREOffset" parameter is activated, and the parameter "resourceElementOffset" can be interpreted as the PTRS RE offset of the first PTRS symbol when a ladder PTRS pattern is indicated. PTRS pattern configuration parameters in aggregated PTRS pattern configuration messages that are not related to the indicated PTRS pattern type may not be activated and are therefore ignored.

[0074] The signaling information indicates which PTRS pattern type was selected by the WANN, allowing the UE to determine the activated or relevant PTRS pattern configuration parameters from all parameters specified in the received PTRS pattern configuration message. PTRS pattern type signaling can be performed explicitly or implicitly by the WANN.

[0075] For example, in some implementations of explicit signaling of PTRS pattern types when multiple PTRS pattern types coexist, the signaling of the PTRS pattern type may be provided via DCI signaling or other signaling paths or interfaces. Based on such signaling information, the UE can determine the PTRS pattern type corresponding to the received aggregated PTRS configuration message and correctly decode the relevant set of PTRS configuration parameters contained in the PTRS configuration message. In some other implementations, the PTRS pattern type may be explicitly indicated to the UE via other control signaling, such as RRC signaling.

[0076] In some implementations for implicit signaling of PTRS pattern types when multiple PTRS pattern types coexist, dedicated signaling information to indicate the PTRS pattern type may not be provided. Instead, such signaling may be implicitly embedded in other existing system configuration parameters included in other system configuration messages.

[0077] For example, a PTRS pattern type may be associated with and indicated by at least one of the parameters, including but not limited to the scheduled number of RBs, frequency range, scheduled MCS, and subcarrier intervals within various RRC messages. The UE may determine a PTRS pattern type from among several coexisting PTRS pattern types according to the values ​​of these other configuration parameters, and then decode the received PTRS configuration message using a known message format corresponding to the determined PTRS pattern to correctly extract the corresponding PTRS configuration parameters for identifying the power level and location of the uplink or downlink PTRS reference signal.

[0078] Non-limiting detailed examples that use a single one or a combination of any number of other system configuration parameters such as the number of scheduled RBs (bandwidth), scheduled MCS, subcarrier spacing, and frequency range to implicitly indicate the PTRS pattern type are similar to those given above for the implementation of implicit signaling of separately defined PTRS pattern configuration data structures and messages, and are repeated below assuming that two types of PTRS patterns (Type 1 and Type 2) are defined and employed:

化

化

化

[0079] In the above example, N is an integer, N>N RB0 and M is an integer, M>ptrs-MCS1. N RB0 and ptrs-MCS1 may be predefined values.

[0080] PTRS pattern type 1 may refer to, for example, a distributed PTRS pattern type. PTRS pattern type 2 may refer to one PTRS pattern type selected from the group consisting of a block PTRS without a cyclic sequence, a block PTRS with a cyclic sequence, a block PTRS with ZP tones, and a ladder PTRS.

[0081] The above example uses various system configuration parameters to implicitly signal one of two PTRS types. In some implementations, these and other system configuration parameters may be used individually or in any combination to implicitly indicate three or more types of PTRS patterns. For example, each of the distributed PTRS pattern type, the block PTRS pattern type without a cyclic sequence, the block PTRS pattern type with a cyclic sequence, the block PTRS pattern type with a ZP tone, and the ladder PTRS pattern type may, individually or in combination, form multiple types of PTRS patterns indicated by system configuration parameters or other system configuration parameters.

[0082] In some other implementations, the PTRS pattern type may be implicitly signaled by the received PTRS pattern configuration data structure and the values ​​of various PTRS pattern parameters within the message.

[0083] For example, if a valid value for the "sizeofBlock" parameter exists in the PTRS pattern configuration message, for example, greater than 1, but there are no valid "lengthofCircular" parameters (e.g., 0 or less) and valid "nrofZPtones" parameters (e.g., 0 or less), it can be used as an indication that the PTRS pattern is a block PTRS pattern type that does not have cyclic sequences and ZP zones.

[0084] In another example, if the valid value of the "sizeofBlock" parameter is greater than, for example, 1, and the valid value of the "lengthofCircular" parameter is greater than, for example, 0, this can be used as an indication that the PTRS pattern is of a block PTRS pattern type that has a cyclic sequence.

[0085] In another example, if the valid value of the "sizeofBlock" parameter is greater than, for example, 1, and the valid value of the "nrofZPtones" parameter is greater than, for example, 0, this can be used as an indication that the PTRS pattern is of a block PTRS pattern type of ZP tones.

[0086] In another example, if a valid value for the "adjacentSymbolREOffset" parameter exists within a PTRS pattern configuration message, for example, if it is greater than 0, it can be used as an indication that the PTRS pattern is of the ladder PTRS pattern type.

[0087] If no valid values ​​exist for the above parameters, this can be used as an indication that the PTRS pattern is of the distributed PTRS pattern type.

[0088] In the various implementations described above that use the PTRS pattern parameter values ​​themselves as implicit PTRS pattern type notifications, the valid parameters "sizeofBlock" and "adjacentSymbolREOffset" do not need to be configured simultaneously, since the configured PTRS pattern cannot be both block type and ladder type (they may be mutually exclusive). Similarly, the valid parameters "lengthofCircular" and "nrofZPtones" do not need to be configured simultaneously, since the configured PTRS pattern cannot be both block type with cyclic sequences and block type with ZP tones (they may be mutually exclusive).

[0089] The above description and accompanying drawings provide specific exemplary embodiments and implementations. However, the subject matter described may be embodied in a variety of different forms, and it is intended that the subject matter included or claimed is not limited to any exemplary embodiments described herein. A reasonably broad range of the subject matter claimed or included is intended. In particular, for example, the subject matter may be embodied as a method, device, component, system, or non-temporary computer-readable medium for storing computer code. Thus, embodiments may take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, an embodiment of the method described above may be carried out by a component, device, or system including memory and a processor by executing computer code stored in memory.

[0090] Throughout this specification and the claims, terms may have nuances implied or suggested in context beyond their expressly stated meanings. Similarly, the phrase “in one embodiment / implementation” as used herein does not necessarily refer to the same embodiment, and the phrase “in another embodiment / implementation” as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include combinations of embodiments that are illustrated whole or partially.

[0091] In general, terms can be understood at least partially from their use in context. For example, terms such as “and,” “or,” or “and / or” as used herein may have various meanings that may at least partially depend on the context in which such terms are used. Typically, when “or” is used to relate a list such as A, B, or C, it is intended to mean A, B, and C, used here in an inclusive sense, as well as A, B, or C, used here in an exclusive sense. Furthermore, the term “one or more” as used herein may be used at least partially, depending on the context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can likewise be understood, at least partially, depending on the context, to convey either a singular or plural usage. Furthermore, the term “based on” may be understood not necessarily to convey an exclusive set of factors, but instead, at least partially, depending on the context, to allow for the presence of additional factors that are not necessarily explicitly described.

[0092] Throughout this specification, references to features, benefits, or similar terms do not imply that all features and benefits that may be realized by the Solution should or will be included in any single implementation thereof. Rather, any terms referring to features and benefits should be understood to mean that certain features, benefits, or characteristics described in relation to an embodiment are included in at least one embodiment of the Solution. Accordingly, descriptions of features and benefits, as well as similar terms, throughout this specification may, but not necessarily, refer to the same embodiment.

[0093] Furthermore, the features, advantages, and characteristics described in this solution can be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that this solution can be implemented without one or more of the specific features or advantages of a particular embodiment. In other examples, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of this solution.

Claims

1. A method performed by a wireless terminal device, wherein the method is Receiving a control message, wherein the control message includes a set of phase-tracking reference signal (PTRS) resource configuration parameters, The method involves obtaining signaling information, wherein the signaling information indicates a specific PTRS resource pattern type among a plurality of predefined PTRS resource pattern types. Decoding the control message in order to extract one or more of the set of PTRS resource configuration parameters based on the specified PTRS resource pattern type, Receiving or transmitting PTRS signals via a radio resource specified by one or more of the set of PTRS resource configuration parameters. Includes, The aforementioned multiple predefined PTRS resource pattern types are: A ladder PTRS resource pattern type having multiple ladders in frequency and time, wherein at least one of the multiple ladders overlaps with another of the multiple ladders in frequency, At least one of the distributed PTRS resource pattern type or the block PTRS resource pattern type and Methods that include...

2. The aforementioned block PTRS resource pattern type is: A block PTRS resource pattern type that does not have a cyclical sequence and does not have a zero-power tone. A block PTRS resource pattern type having a cyclic sequence and no zero-power tone, or Block PTRS resource pattern type that does not have a cyclical sequence and has a zero-power tone. The method according to claim 1, comprising one of the following.

3. The aforementioned specific PTRS resource pattern type is a block PTRS resource pattern type comprising multiple blocks of multiple consecutive resource elements in the frequency domain, The method according to claim 1, wherein one or more of the set of PTRS resource configuration parameters include at least the block size for the plurality of blocks of the plurality of consecutive resource elements.

4. The method according to claim 3, wherein one or more of the set of PTRS resource configuration parameters further include length configuration parameters that specify the length of a cyclic reference signal sequence within each block of a plurality of consecutive resource elements in the frequency domain.

5. The method according to claim 3, wherein one or more of the set of PTRS resource configuration parameters further include a configuration parameter that specifies the number of zero-power tones in each block of a plurality of consecutive resource elements in the frequency domain.

6. The aforementioned specific PTRS resource pattern type is the ladder PTRS resource pattern type, The method according to claim 1, wherein one or more of the set of PTRS resource configuration parameters include at least an offset configuration parameter that specifies resource element offsets between adjacent symbols for the particular PTRS resource pattern type.

7. The control message belongs to a set of multiple predefined control messages in separate formats corresponding to the multiple predefined PTRS resource pattern types. Obtaining the aforementioned signaling information means Extracting the format information of the control message from the header of the control message, or Receiving a signaling message separately from the aforementioned control message, and extracting the signaling information from the signaling message, or, Extracting the value of at least one other independent system configuration parameter, and deriving the signaling information based on the value of the at least one other independent system configuration parameter. The method according to claim 1, including the method described in claim 1.

8. The method according to claim 7, wherein the control message is a radio resource control (RRC) message and the signaling message is a downlink control information (DCI) message.

9. Obtaining the signaling information includes extracting the values ​​of at least one other independent system configuration parameter and deriving the signaling information based on the values ​​of at least one other independent system configuration parameter. The aforementioned at least one other independent system configuration parameter is Number of scheduled resource blocks, Scheduled MCS, Number of scheduled resource elements, Frequency range, or Subcarrier spacing The method according to claim 7, comprising at least one of the following.

10. The set of PTRS resource configuration parameters is the set of multiple predefined PTRS The method according to claim 1, comprising a set of configuration parameters for all resource pattern types.

11. The method according to claim 10, wherein one or more of the set of PTRS resource configuration parameters include a subset of the set of PTRS resource configuration parameters that are activated for the particular PTRS resource pattern type.

12. The method according to claim 11, wherein the remaining configuration parameters in the set of PTRS resource configuration parameters are ignored.

13. Obtaining the aforementioned signaling information means Receiving a signaling message separately from the aforementioned control message, Extracting the signaling information from separate signaling messages and The method according to claim 11, including the method described in claim 11.

14. The method according to claim 13, wherein the control message is a radio resource control (RRC) message and the signaling message is a downlink control information (DCI) message.

15. Obtaining the aforementioned signaling information means Extract the value of at least one other independent system configuration parameter, Deriving the signaling information based on the value of at least one other independent system configuration parameter. The method according to claim 11, including the method described in claim 11.

16. The aforementioned at least one other independent system configuration parameter is Number of scheduled resource blocks, Scheduled MCS, Number of scheduled resource elements, Frequency range, or Subcarrier spacing The method according to claim 15, comprising at least one of the following.

17. Obtaining the aforementioned signaling information means Extracting the values ​​of pattern configuration parameters from the set of PTRS resource configuration parameters, Determining whether the value of the pattern configuration parameter falls within a predefined valid range, The signaling information is determined based on whether the value of the pattern configuration parameter falls within the predefined effective range. The method according to claim 11, including the method described in claim 11.

18. The aforementioned pattern configuration parameters are: The block size for multiple blocks of multiple consecutive resource elements in the frequency domain for the aforementioned block PTRS resource pattern type, A length configuration parameter that specifies the length of the cyclic reference signal sequence in each block of multiple consecutive resource elements in the frequency domain for the aforementioned block PTRS resource pattern type, The number of zero-power tones within each block of multiple consecutive resource elements in the frequency domain for the aforementioned block PTRS resource pattern type. parameter, or, An offset configuration parameter that specifies the resource element offset between adjacent symbols for the aforementioned specific PTRS resource pattern type. The method according to claim 17, comprising one of the following.

19. A method performed by a wireless access network node, the method is Selecting a specific PTRS resource pattern type from several predefined PTRS resource pattern types, Constructing a control message, wherein the control message includes a set of phase-tracking reference signal (PTRS) resource configuration parameters, In order to specify a PTRS resource pattern having the aforementioned specific PTRS resource pattern type, one or more parameter values ​​from the set of PTRS resource configuration parameters are determined. The control message is transmitted to the wireless terminal device, To provide the wireless terminal device with signaling information to indicate the specific PTRS resource pattern type, Includes, The aforementioned multiple predefined PTRS resource pattern types are: A ladder PTRS resource pattern type having multiple ladders in frequency and time, wherein at least one of the multiple ladders overlaps with another of the multiple ladders in frequency, At least one of the distributed PTRS resource pattern type or the block PTRS resource pattern type and Methods that include...

20. A wireless device comprising a processor and memory, wherein the processor is configured to perform the method according to claim 1 by reading computer code from the memory.

Images