RU2791282C1 - Terminal and radio communication method - Google Patents

Abstract

FIELD: radio communication.

SUBSTANCE: terminal in accordance with one aspect of the present disclosure includes a transmission section configured to transmit an uplink common channel and a control section configured to determine, when transmitting an uplink common channel, whether a phase tracking reference signal (PTRS) transmission exists based on a type of radio network temporary identifier (RNTI) used for the downlink control information that schedules the uplink common channel.

EFFECT: transmission of a phase tracking reference signal (PTRS).

8 cl, 16 dwg

Description

The field of technology to which the invention belongs

[0001] The present invention relates to a radio communication terminal and method in next generation mobile communication systems.

State of the art

[0002] In the Universal Mobile Telecommunications System (UMTS) network, a Long Term Evolution (LTE) scheme specification has been proposed to further increase the data rate, provide lower latency, etc. .d. (see non-patent document 1). In addition, in order to further increase the capacity, and further improve over LTE (Third Generation Partnership Project (3GPP) versions 8 and 9), the LTE Advanced Scheme Specification: LTE-Advanced (3GPP versions 10-14) has been developed.

[0003] LTE successor systems are also being studied (also called, for example, "5th generation mobile communication system (5G)", "5G+ (plus)", "new radio (NR, from New Radio)", " 3GPP version 15 (or later)", etc.).

[0004] In the existing LTE system (for example, 3GPP versions 8-14), the user terminal (user equipment (UE, from English. User Equipment)) controls the reception of a downlink common channel (for example, a physical downlink shared channel (PDSCH, from English. Physical Downlink Shared Channel) based on downlink control information (DCI) (also called downlink assignment or the like) from the base station. , from Physical Uplink Shared Channel)) based on DCI (also called an uplink grant or the like).

List of cited literature

Non-Patent Documents

[0005] Non-Patent Document 1: 3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010 ("Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General Description; Phase 2 (Release 8)", April 2010)

Disclosure of the essence of the invention

Technical problem

[0006] The uplink and downlink transmission of a phase tracking reference signal (PTRS) in a radio communication system (eg, NR) in the future is currently being discussed. For example, when transmitting an uplink shared channel (eg, PUSCH), the UE controls PTRS transmission based on configurations from the network (eg, base station).

[0007] In NR, a random access procedure is supported. In the random access procedure, when an uplink indication (eg, uplink grant) is included in the response signal transmitted in response to the random access preamble, the UE performs PUSCH transmission based on the uplink grant. However, there is not enough discussion about how to control the transmission of PTRS in such a case.

[0008] Thus, the purpose of the present disclosure is to provide a terminal and a radio communication method that can properly transmit a phase tracking reference signal (PTRS).

Solution

[0009] A terminal according to one aspect of the present disclosure includes: a transmission section configured to transmit an uplink common channel; and a control section configured to determine, when transmitting an uplink common channel, the existence of a phase tracking reference signal (PTRS) transmission based on a type of Radio Network Temporary Identifier (RNTI) used for downlink control information that schedules uplink common channel.

Beneficial Effects of the Invention

[0010] In accordance with one aspect of the present disclosure, it is possible to appropriately transmit a phase tracking reference signal (PTRS).

Brief description of the drawings

[0011]

In FIG. 1 is a diagram showing an example of a contention based random access procedure (with collisions);

In FIG. 2 is a diagram showing an example of a contention-free (no collision) random access procedure;

In FIG. 3 is a diagram showing an example of RAR reported by MAC CE;

In FIG. 4A and 4B are diagrams showing an example of PUSCH transmission control according to the first aspect;

In FIG. 5A and 5B are diagrams showing an example of PUSCH transmission control according to the second aspect;

In FIG. 6A and 6B are diagrams showing another example of PUSCH transmission control according to the third aspect;

In FIG. 7 is a diagram showing an example of a modulation and coding scheme (MCS) table;

In FIG. 8 is a diagram showing an example of a two-stage random access procedure;

In FIG. 9 is a diagram showing another example of a two-stage random access procedure;

In FIG. 10 is a diagram showing an example of a schematic structure of a radio communication system according to one embodiment;

In FIG. 11 is a diagram showing an example of the structure of a base station according to one embodiment;

In FIG. 12 is a diagram showing an example of a structure of a user terminal according to one embodiment; And

In FIG. 13 is a diagram showing an example of a hardware structure of a base station and a user terminal according to one embodiment.

Implementation of the invention

<Random access procedure>

[0012] In an existing LTE system (eg, LTE releases 8 to 13), a random access procedure is supported to establish uplink synchronization. The random access procedure includes contention-based random access (or contention-based random access, or the like) and contention-based random access (or non-contention, also called Non-CBRA). , CFRA, from contention-free random access, etc.).

[0013] In the contention-based random access (CBRA) mode, a terminal (hereinafter also referred to as a user terminal or UE, from the English User Terminal) transmits a preamble selected randomly from a plurality of preambles (also referred to as a random access preamble, a random access channel (physical random access channel (PRACH, from the English Physical Random Access Channel)), RACH preamble, or the like) defined for each cell. Contention-based random access is a random access procedure initiated by the UE, and may be used, for example, at initial access, start or restart of uplink transmission, or the like.

[0014] In the contention-free random access (Non-CBRA, CFRA) mode, the base station uniquely allocates a preamble to the UE via a downlink (DL) control channel (PDCCH), and the UE transmits the preamble allocated by the base station. The contention-free random access is a network-initiated random access procedure, and may be used, for example, in handover (handover), downlink start or restart (uplink start or restart of the downlink retransmission indication information), or the like.

[0015] FIG. 1 is a diagram showing an example of contention-based random access. In FIG. 1, the UE receives in advance information (PRACH configuration information) indicating a random access channel (PRACH) configuration (PRACH configuration, RACH configuration) via system information (for example, a Master Information Block (MIB) and/or a system information (SIB, from the English System Information Block), or signaling of a higher level (for example, signaling control of radio resources (RRC, from the English Radio Resource Control)).

[0016] The PRACH configuration information may indicate, for example, a plurality of preambles (e.g., preamble formats) defined for each cell, a time resource (e.g., a system frame number or a subframe number), and a frequency resource (e.g., an offset (prach-FrequencyOffset parameter) , indicating the starting position of the six resource blocks (Physical Resource Blocks (PRBs)) used to transmit the PRACH.

[0017] As shown in FIG. 1, in the case where the UE transitions from the idle state (RRC_IDLE) to the RRC connected state (RRC_CONNECTED) (for example, at initial access), in the case when uplink synchronization is not established even in the RRC connected state (for example, starting or restarting uplink transmission) or the like, the UE randomly selects one of the plurality of preambles indicated by the PRACH configuration information and transmits the selected preamble via the PRACH (message 1).

[0018] Having detected the preamble, the base station transmits a random access response (RAR, from the English random access response) in response to the preamble (message 2). When RAR reception fails for a certain period (RAR window) after the transmission of the preamble, the UE transmits (retransmits) the preamble again with increased PRACH transmission power. It should be noted that the increase in transmit power during retransmission is also called power ramping.

[0019] Upon receiving the RAR, the UE establishes uplink timing by adjusting the uplink transmission time based on the timing advance (TA) included in the RAR. In addition, the UE transmits a higher layer control message (L2/L3: Layer 2/Layer 3) with an uplink resource indicated by an uplink grant included in the RAR (message 3). The control message contains a UE identifier (UE-ID). The UE identifier may be, for example, a higher layer UE identifier such as a Cell-Radio Network Temporary Identifier (C-RNTI) in the case of an RRC connection state, or a System Architecture Evolution Mobile Subscriber Temporary Identifier (S -TMSI, from System Architecture Evolution - Temporary Mobile Subscriber Identity) in the case of a pending state.

[0020] The base station transmits a collision resolution message in accordance with the higher layer control message (message 4). The contention resolution message is transmitted based on the assignment of the UE ID included in the control message described above. After successfully detecting the contention resolution message, the UE sends an acknowledgment (ACK) for a Hybrid Automatic Repeat ReQuest (HARQ) to the base station. Accordingly, the UE in the idle state transitions to the RRC connected state.

[0021] In the event of a failure to detect a collision resolution message, the UE determines that a collision has occurred, reselects the preamble, and repeats the random access procedure according to messages 1-4. Upon detecting contention resolution with an ACK from the UE, the base station transmits an uplink grant to the UE. The UE starts uplink data using the uplink resource allocated by the uplink grant.

[0022] FIG. 2 is a diagram showing an example of random access without contention. In the case of contention-free random access, the base station first transmits to the UE a physical downlink control channel (PDCCH order) that indicates PRACH transmission (message 0). The UE transmits a random access preamble (PRACH) at the time indicated by the PDCCH (message 1). Upon detecting the random access preamble, the base station transmits a random access response (RAR), which is response information in response to the random access preamble (message 2).

[0023] The UE terminates contention-free random access processing by receiving message 2. When message 2 reception fails, as in contention-based random access, the UE transmits message 1 again with increased PRACH transmission power. Upon receiving message 2, the UE may transmit uplink data (eg, PUSCH) based on the uplink indication (uplink grant) included in message 2.

[0024] In each of the contention-based random access procedure and the contention-free random access procedure, information (e.g., an upstream grant) that instructs an upstream transmission may be included in a random access response (RAR) (see FIG. 3) . In FIG. 3 shows an example of MAC control information (MAC RAR) corresponding to RAR. The UE performs an Uplink Shared Channel (PUSCH) transmission based on a delay time command, an uplink grant, or the like included in the RAR.

[0025] In the contention-based random access procedure, the UE transmits the PUSCH corresponding to message 3 based on the uplink grant included in the RAR. In the contention-free random access procedure, the UE transmits the PUSCH based on the uplink grant included in the RAR. The PUSCH may include, for example, a power headroom or buffer status report.

<Phase tracking reference>

[0026] In NR, a base station (eg, gNB) transmits a phase tracking reference signal (PTRS) on the downlink. For example, the base station may continuously or intermittently display PTRS in the time direction by one subcarrier. The base station may transmit PTRS for at least a portion of a period (eg, slot or symbol) in which a downlink common channel (PDSCH) is transmitted. The PTRS transmitted by the base station may be referred to as downlink PTRS.

[0027] The UE transmits a phase tracking reference signal (PTRS) in the uplink. For example, the UE may continuously or intermittently display PTRS in the time direction by one subcarrier. The UE may transmit PTRS in at least a portion of a period (eg, per slot or symbol) in which an uplink shared channel (Physical Uplink Shared Channel, PUSCH: Physical Uplink Shared Channel) is transmitted. The PTRS transmitted by the UE may be referred to as the uplink PTRS. In the following, upstream PTRS is simply referred to as PTRS.

[0028] The UE may determine if a PTRS exists on the uplink (eg, the existence of a PTRS transmission) based on a higher layer signaling configuration (eg, a PTRS-UplinkConfig parameter). The UE may assume that the PTRS exists in the resource block used to transmit the PUSCH when higher layer PTRS-related signaling is configured (eg, the PTRS-UplinkConfig parameter). The base station may determine the phase noise based on the PTRS transmitted from the UE and correct the phase error of the received signal.

[0029] Here, for example, the higher layer signaling can be any one or combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information and the like.

[0030] For example, MAC signaling can use MAC control elements (MAC CE, from the English. MAC control elements), blocks of data protocol MAC (PDUs, from the English. Protocol Data Units), and the like. The broadcast information can be, for example, a master information block (MIB), a system information block (SIB, System Information Block), minimum system information (remaining minimum system information (RMSI). Remaining Minimum System Information)), other system information (OSI, from the English. Other System Information) or the like.

[0031] In the case of PUSCH transmission as well as PTRS, the UE may perform control (eg, rate negotiation) not to apply the resource to which PTRS is mapped to the PUSCH transmission.

[0032] In the existing system (eg, current version 15), PTRS transmission control based on the type or kind of Radio Network Temporary Identifier (RNTI) used, even when higher layer PTRS-related signaling (eg, PTRS-UplinkConfig) is configured. For example, it has been discussed that the existence of PTRS in PUSCH is allowed or supported when the RNTI is MCS-C-RNTI, C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0033] The RNTI applies to multiple signals or channels (eg, PDSCH, PUSCH, or PDCCH), but the current definition does not clearly define which signal or channel the RNTI applies to.

[0034] For example, a PUSCH scheduled by an uplink grant (uplink RAR grant) included in a response signal (RAR) corresponding to a random access preamble is scrambled with a TC-RNTI in the case of a CBRA or scrambled with a C-RNTI in the case of a CFRA. Alternatively, when an uplink common channel is scheduled via a downlink control channel (or DCI), the RNTI applied to the downlink control channel is configured differently.

[0035] Thus, when the signal or channel corresponding to the RNTI that determines the existence of a PTRS transmission is unclear, the PTRS transmission potentially cannot be performed properly. For example, there may be a case in which the RNTI applied to the PDCCH that schedules the PUSCH may be different from the RNTI applied to the PUSCH, in which case it is problematic to control the PTRS transmission.

[0036] Thus, as an aspect of the present invention, the present inventors have focused on the unclear correspondence between a signal or channel and an RNTI that governs the existence of a PTRS transmission, and came up with the idea of appropriately determining the existence of a PTRS transmission by refining the signal or channel corresponding to the RNTI. Alternatively, the present inventors came up with the idea of clearly defining the existence of a PTRS transmission on a PUSCH scheduled by an uplink RAR grant.

[0037] Consider the case in which the signal or channel corresponding to the RNTI is downstream control information (or DCI). In this case, the upstream grant (upstream RAR grant) included in the RAR is transmitted and reported by the MAC and therefore is not subject to CRC scrambling (from the English cyclic redundancy check - cyclic redundancy check) by a specific (given) RNTI (for example, MCS -C-RNTI, C-RNTI, CS-RNTI or SP-CSI-RNTI). Thus, no PTRS is basically included (does not exist) in the PUSCH scheduled by the RAR upstream grant.

[0038] If the base station has not performed reception processing (eg, decoding) of the PUSCH scheduled by the uplink RAR grant, the base station triggers or indicates retransmission of the PUSCH. For example, in contention-free random access, retransmission may be scheduled using CRC-scrambled DCI by C-RNTI.

[0039] In this case, when the PTRS is configured with higher layer signaling (eg, PTRS-UplinkConfig), it is assumed that the PTRS exists on PUSCH retransmission (eg, the UE transmits PTRS on PUSCH transmission). When there is no PTRS in the initial transmission of the PUSCH, the transport block size potentially cannot be the same for the initial transmission PUSCH and the retransmission PUSCH.

[0040] As another aspect of the present invention, the present inventors have considered PTRS transmission (or mapping) control in at least one of initial transmission of a PUSCH transmitted based on an uplink RAR grant and retransmission of a PUSCH, and have arrived at an embodiment of the present invention.

[0041] Embodiments in accordance with the present disclosure will be described in detail below with reference to the drawings. It should be noted that the first to fifth aspects described below may be applied individually or may be used in combination of at least two. In the following description, the existence of a PTRS transmission and the existence of a PTRS may be interpreted interchangeably.

[0042] The following description concerns, by way of example, the existence of a PTRS transmission in a PUSCH transmission indicated by an upstream RAR grant in a Contention Free Random Access (CFRA) procedure, but the present invention is not limited to this. The present invention can be applied to PTRS in a PUSCH transmission indicated by an upstream RAR grant in a Contention Based Random Access (CBRA) procedure. Alternatively, the present invention may be applied to PTRS with initial transmission and retransmission of a PUSCH (eg, PUSCH based on a configured grant) other than that used in the random access procedure.

[0043] It should be noted that in the present description, retransmission may mean the first transmission as a retransmission (or retransmission) after the initial transmission, or may mean multiple retransmissions (multiple retransmissions after the first retransmission).

(First aspect)

[0044] In a first aspect, a description will be given of the case in which the RNTI that determines the existence of a PTRS transmission is an RNTI applied to a particular signal or channel (or an RNTI used to scramble a particular signal or channel). The following description will be made for a case (case 1) in which a specific signal or channel is a downlink common channel (or DCI) and a case (case 2) in which a specific signal or channel is an uplink common channel.

[0045] In the following description, the RNTI applied to the PDCCH may be the RNTI applied to the CRC scrambling of the PDCCH. The RNTI applied to the PUSCH may be the RNTI applied to the PUSCH scrambling. The RNTI applied to the PUSCH may be used to map RS such as PTRS and generate a sequence.

<Case 1>

[0046] When transmitting a PUSCH scheduled by a PDCCH (or DCI) subjected to CRC scrambling by a specific (given) RNTI, a PTRS may be transmitted (or mapped). A particular RNTI may be, for example, MCS-C-RNTI, C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0047] For example, when a PDCCH that is scheduling a PUSCH (or a DCI) is CRC-scrambled by a particular RNTI, the UE may control transmission processing (e.g., mapping) assuming that a PTRS exists on the resource block used to transmit the PUSCH (see Fig.4A). The DCI may be in a DCI format (eg, at least one of DCI formats 0_0 and 0_1) corresponding to the upstream grant.

[0048] When a PDCCH (or DCI) that schedules a PUSCH is CRC-scrambled by a PDCCH other than a particular RNTI, the UE may control transmission processing (eg, mapping) assuming that no PTRS.

[0049] For example, when the RNTI used to scramble the PUSCH is a specific RNTI, but the downlink signal or channel (eg, PDCCH) that indicates (eg, schedules) the PUSCH transmission is not scrambled by the specific RNTI, the UE may control as to not transmit PTRS. In other words, the UE may control not to transmit PTRS regardless of the type of RNTI used to scramble the PUSCH scheduled by the uplink RAR grant.

[0050] Thus, it is possible to appropriately manage the existence of a PTRS transmission along with the PUSCH by clearly defining a signal or channel corresponding to the RNTI that determines the existence of a PTRS transmission, thereby simplifying the operation of the UE.

[Modification]

[0051] Alternatively, a configuration may be provided such that PTRS does not exist in a PUSCH scheduled by an uplink RAR grant without a clear definition of the signal or channel corresponding to the RNTI (see FIG. 4B). Accordingly, the UE may control not to transmit PTRS regardless of the RNTI used for PUSCH (eg, initial transmission) scheduled by the uplink RAR grant. As a result, the operation of the UE can be simplified.

<Case 2>

[0052] It may be configured that the PTRS is transmitted (mapped) when transmitting a PUSCH scrambled by a particular RNTI. A particular RNTI may be, for example, MCS-C-RNTI, C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0053] For example, when the PUSCH is CRC scrambled by a particular RNTI, the UE may control transmission processing (eg, mapping) assuming that a PTRS exists on the resource block used to transmit the PUSCH.

[0054] In this case, the UE may transmit PTRS when transmitting a PUSCH not scheduled by the PDCCH. For example, a PUSCH based on a configured grant is scrambled by the CS-RNTI but not scheduled by the PDCCH. When case 2 is applied, it is possible to transmit PTRS when transmitting a PUSCH based on a configured grant (eg, PUSCH scrambled by CS-RNTI) not scheduled by the PDCCH. Type 1 and type 2 are defined for PUSCH based on the configured grant, and the present aspect can be applied to either or both of the specified types.

[0055] When case 2 is applied, the PUSCH scheduled by the RAR uplink grant is scheduled by the C-RNTI in contention-free random access (CFRA), and thus the existence of PTRS can be enabled or maintained when transmitting the PUSCH. However, in contention-based random access (CBRA), a PUSCH scheduled by an uplink RAR grant is scheduled by a TC-RNTI, and therefore, it can be configured such that the existence of a PTRS in PUSCH transmission is not allowed or supported.

[Modification]

[0056] Alternatively, in case 2, PTRS may not exist in the PUSCH scheduled by the uplink RAR grant. In other words, the PUSCH scheduled by the uplink RAR grant can be controlled not to transmit PTRS regardless of the type of RNTI used.

[0057] Accordingly, in both contention-free random access (CFRA) and contention-based random access (CBRA), a configuration may be provided such that the existence of a PTRS in a PUSCH transmission scheduled by an uplink RAR grant is not allowed and is not supported. As a result, the operation of the UE and the base station can be unified regardless of the type of random access.

(second aspect)

[0058] In a second aspect, when an uplink common channel (eg, PUSCH) is transmitted based on a random access response (eg, RAR), the existence of a PTRS in the PUSCH is controlled to be common to initial transmission and retransmission of the PUSCH.

[0059] Specifically, when PTRS transmission (or mapping) is performed on the initial transmission PUSCH, the UE also performs PTRS transmission on the retransmission PUSCH (see FIG. 5A). However, when PTRS transmission (or mapping) is not performed on the initial transmission PUSCH, the UE may control not to perform PTRS transmission on the retransmission PUSCH (see FIG. 5B).

[0060] For example, the UE may control PTRS transmission on the PUSCH using at least one of 1-1 to 1-3 described below.

<Option 1-1>

[0061] The UE controls not to perform PTRS transmission (or mapping) on initial PUSCH transmission and not to perform PTRS transmission on PUSCH retransmission (see FIG. 5A). When PTRS configuration is performed with higher layer signaling, the UE may ignore the configuration with higher layer signaling and perform control not to perform PTRS transmission.

[0062] When PTRS transmission is performed in each of initial transmission and retransmission of PUSCH, the transport block size (TBS) can be easily controlled to be the same for initial transmission and retransmission.

<Option 1-2>

[0063] The UE performs control to perform PTRS transmission (or mapping) in the initial PUSCH transmission and perform PTRS transmission in the PUSCH retransmission (see FIG. 5A).

[0064] Option 1-2 can be applied to the case in which the PTRS configuration is performed by higher layer signaling (eg, a UE-specific parameter). It may be configured such that option 1-1 applies when PTRS configuration is not performed by higher layer signaling.

[0065] Alternatively, option 1-2 may be applied to the case in which the PTRS configuration is not performed by higher layer signaling. In this case, the UE may perform PTRS transmission regardless of the configuration with higher layer signaling.

[0066] Alternatively, the PTRS corresponding to the initial transmission and the PTRS corresponding to the retransmission may each be configured with separate higher layer signaling. In this case, when the PTRS corresponding to the initial transmission is configured, option 1-2 may be applied regardless of whether the PTRS corresponding to the retransmission is configured (for example, even if the PTRS is not configured).

[0067] The transport block size can be easily controlled to be the same for initial transmission and retransmission by transmitting the PTRS in each of the initial transmission and retransmission of the PUSCH. In each of the initial transmission and retransmission, the base station may determine the phase noise based on the PTRS transmitted from the UE and correct the phase error of the received signal accordingly.

<Option 1-3>

[0068] The UE may perform control to perform PTRS transmission (or mapping) in PUSCH initial transmission and retransmission regardless of whether PTRS configuration is performed with higher layer signaling (a UE-specific parameter).

[0069] In such a case, the UE may perform PTRS transmission using a specific value (eg, a default value) as a PTRS configuration parameter. The PTRS configuration parameter may be at least one of time density (timeDensity) and frequency density (frequencyDensity).

[0070] For example, when a higher layer parameter (timeDensity) associated with time density is not reported, or when the timeDensity field does not exist, the UE may apply a specific time density (eg, L_PTRS=1). Alternatively, when a higher layer parameter (frequencyDensity) associated with frequency density is not reported, or when the frequencyDensity field does not exist, the UE may apply a specific frequency density (eg, K_PT-RS=2).

[0071] The UE may apply the specific PTRS configuration parameter only when PTRS configuration is not performed by higher layer signaling, or may apply the specific PTRS configuration parameter even when PTRS configuration is performed by higher layer signaling.

[0072] Thus, it is possible to appropriately control the transmission of the PTRS in the PUSCH scheduled by the uplink RAR grant by controlling the transmission of the PTRS in the initial transmission of the PUSCH and the retransmission regardless of the configuration of the PTRS with the higher layer parameter.

<Modification>

[0073] The UE may determine whether to include the PTRS in the retransmission based on whether the PTRS is included in the initial transmission (or the previous retransmission) regardless of the PTRS configuration with higher layer signaling and RNTI type.

(Third aspect)

[0074] In a third aspect, in the case of uplink common channel transmission based on random access response, the existence of PTRS in PUSCH is separately (eg, differently) controlled for PUSCH initial transmission and PUSCH retransmission.

[0075] In particular, the UE independently controls the PTRS transmission (or mapping) in the PUSCH transmission as the initial transmission and the PTRS transmission in the PUSCH transmission as the retransmission.

[0076] For example, the UE may control PTRS transmission on the PUSCH using at least one of 2-1 to 2-4 described below.

<Option 2-1>

[0077] The UE controls not to perform PTRS transmission (or mapping) on initial PUSCH transmission. The UE may control not to perform PTRS transmission regardless of the PTRS configuration with higher layer signaling.

[0078] The UE may manage the existence of a PTRS transmission depending on the existence of a PTRS configuration with higher layer signaling on PUSCH retransmission. For example, when PTRS configuration is performed with higher layer signaling, the UE performs control to perform PTRS transmission in PUSCH retransmission (see FIG. 6A).

[0079] Alternatively, the UE may perform control to perform PTRS transmission in the PUSCH retransmission even if PTRS configuration is not performed by higher layer signaling. In this case, the UE can perform PTRS transmission regardless of the non-PTRS configuration with higher layer signaling.

[0080] Thus, when the PTRS transmission is not performed in the initial transmission of the PUSCH, but is performed in the retransmission of the PUSCH, it is possible to appropriately perform phase noise correction with the PTRS in the retransmitted PUSCH. Accordingly, a reduction in the error rate during PUSCH retransmission can be expected.

<Option 2-2>

[0081] The UE may control the existence of a PTRS transmission depending on the existence of a PTRS configuration with higher layer signaling on initial PUSCH transmission. For example, when PTRS configuration is performed with higher layer signaling, the UE performs control to perform PTRS transmission in PUSCH retransmission.

[0082] The UE may control not to perform PTRS transmission regardless of the PTRS configuration with higher layer signaling on PUSCH retransmission (see FIG. 6B). For example, when PTRS configuration is performed with higher layer signaling, the UE may control not to perform PTRS transmission regardless of the configuration with higher layer signaling.

[0083] Thus, when PTRS transmission is performed on initial PUSCH transmission but not performed on PUSCH retransmission, it is possible to reduce the error rate of the retransmitted PUSCH when retransmitted at a lower data rate than initial transmission. Moreover, it is possible to reduce the amount of resources used by the retransmitted PUSCH when retransmitted at the same data rate as the original transmission compared to the original transmission, and thus the frequency utilization efficiency of the retransmitted PUSCH can be expected to improve.

<Option 2-3>

[0084] The UE may separately manage the existence of a PTRS transmission in the initial PUSCH transmission and the existence of a PTRS transmission in the PUSCH retransmission, regardless of the PTRS configuration, with higher layer signaling (a UE-specific parameter).

[0085] For example, the UE may control for PTRS transmission in the initial PUSCH transmission, but not for PTRS transmission in the PUSCH retransmission regardless of the PTRS configuration with higher layer signaling (a UE-specific parameter).

[0086] The PTRS configuration parameter applied to the PTRS transmission on initial PUSCH transmission may be a specific value (eg, a default value). The PTRS configuration parameter applied to the PTRS transmission may be provided in the manner described in option 1-3 above.

<Option 2-4>

[0087] The UE may separately manage the existence of a PTRS transmission in the initial PUSCH transmission and the existence of a PTRS transmission in the PUSCH retransmission, regardless of the PTRS configuration, with higher layer signaling (a UE-specific parameter).

[0088] For example, the UE may control not to transmit PTRS on initial PUSCH transmission, but to transmit PTRS on PUSCH retransmission, regardless of the PTRS configuration with higher layer signaling (a UE-specific parameter).

[0089] The PTRS configuration parameter applied to PTRS transmission on PUSCH retransmission may be a specific value (eg, a default value). The PTRS configuration parameter applied to the PTRS transmission may be provided in the manner described in option 1-3 above.

[0090] Thus, when the existence of a PTRS transmission in each of the initial transmission and the PUSCH retransmission is controlled separately regardless of the PTRS configuration by the higher layer parameter, the effects of phase noise correction and error rate reduction due to PTRS insertion, and the effect of reducing the coding rate data or reduction of resources used by the PUSCH due to the lack of PTRS insertion can be appropriately managed in both initial transmission and retransmission. As a result, it becomes possible to more flexibly and appropriately manage the increase in network usage efficiency and communication quality.

(Fourth aspect)

[0091] In a fourth aspect, in the case of transmitting an uplink common channel based on a random access response, the UE autonomously determines the existence of a PTRS in at least one of the initial PUSCH transmission and the PUSCH retransmission (UE implementation).

[0092] For example, the UE may control the transmission of PTRS on PUSCH using at least one of options 3-1 to 3-5 described below.

<Option 3-1>

[0093] The UE controls not to perform PTRS transmission (or mapping) on initial PUSCH transmission. The UE may control not to perform PTRS transmission regardless of the PTRS configuration with higher layer signaling.

[0094] However, the UE may autonomously determine the existence of a PTRS transmission upon retransmission of the PUSCH.

<Option 3-2>

[0095] The UE may control the existence of a PTRS transmission depending on the existence of a PTRS configuration with higher layer signaling on initial PUSCH transmission. For example, when PTRS configuration is performed with higher layer signaling, the UE performs control to perform PTRS transmission in the initial PUSCH transmission.

[0096] However, the UE may autonomously determine the existence of a PTRS transmission on PUSCH retransmission (UE implementation).

<Option 3-3>

[0097] The UE may autonomously determine the existence of a PTRS transmission upon initial PUSCH transmission.

[0098] However, the UE controls not to perform PTRS transmission (or mapping) when retransmitting the PUSCH. The UE may control not to perform PTRS transmission regardless of the PTRS configuration with higher layer signaling.

<Option 3-4>

[0099] The UE may autonomously determine the existence of a PTRS transmission upon initial PUSCH transmission.

[0100] The UE may manage the existence of a PTRS transmission, depending on the existence of a PTRS configuration, with higher layer signaling on PUSCH retransmission. For example, when PTRS configuration is performed with higher layer signaling, the UE performs control to perform PTRS transmission in PUSCH retransmission.

<Option 3-5>

[0101] The UE may autonomously determine the existence of a PTRS transmission in each of the initial PUSCH transmission and the PUSCH retransmission.

[0102] Thus, the UE autonomously determines the existence of a PTRS transmission, thereby properly performing a PUSCH transmission based on the uplink RAR grant even if the PTRS configuration is not specified from the base station.

(Fifth aspect)

[0103] In a fifth aspect, the transport block size (TBS) used in the initial transmission and retransmission of the PUSCH will be described below. The fifth aspect is preferably applicable to the case (for example, the third aspect) in which the PTRS transmission is applied to only one of the initial transmission and retransmission. The configuration to which the fifth aspect is applicable is not limited to this case.

[0104] In NR, based on a particular field (eg, modulation and coding scheme (MCS) field) included in the downstream control information (eg, upstream grant), at least one of a modulation scheme (or modulation order) and a coding rate PUSCH scheduled by DCI.

[0105] In particular, it has been discussed that the UE determines for the PUSCH the modulation order and/or coding rate corresponding to the MCS index indicated by the MCS field in the DCI using a table (MCS table) that links the MCS index, the modulation order, and the TBS index.

[0106] Each modulation order is a value corresponding to a modulation scheme. For example, the modulation orders QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM and 256QAM are "2", "4", "6", and "8", respectively.

[0107] In FIG. 7 is a diagram showing an example of an MCS table. Note that the values in the MCS table shown in FIG. 7 are only examples and the present invention is not limited to them. Some elements (eg spectrum efficiency) associated with the MCS index (I _MCS ) may be omitted and any other element may be added.

[0108] In FIG. 7 shows an exemplary table applied when transform precoding is enabled and the MCS table information described above does not indicate 256QAM. It should be noted that the table applied when transform precoding is disabled and the table used when transform precoding is enabled and the MCS table information indicates 256QAM may be defined separately.

[0109] The UE may determine the modulation order and/or coding rate corresponding to the MCS index (I _MCS ) in the DCI using the table in FIG. 7. For example, in FIG. 7, when the UE satisfies a specific condition (eg, BPSK support), the modulation order q corresponding to the specific MCS index (eg, "0" or "1") may be "1" (BPSK). When the above specific condition is not met, the modulation order q may be "2" (QPSK).

[0110] Thus, the UE determines the modulation scheme to be applied to the PUSCH (initial transmission or retransmission) based on the MCS index included in the uplink grant.

[0111] In the table in FIG. 7, MCS indices 28 to 31 correspond to reserved bits. In a fifth aspect, the transport block size (TBS) applied to the PUSCH is signaled using reserved bits.

[0112] For example, when an MCS field included in the DCI (eg, uplink grant) that indicates a PUSCH retransmission indicates a specific MCS index, the UE applies the TBS applied in the initial transmission (or previous retransmission) when retransmitting the PUSCH. In other words, when any of the MCS indexes 28 to 31 is set by the MCS field, the UE performs control such that TBS is the same for initial transmission and retransmission.

[0113] In this example, it is assumed that the specific MCS index is at least one of the MCS indexes 28 to 31 corresponding to the reserved bits, but the value of the specific MCS index is not limited to this.

[0114] Thus, even when PTRS is included in only one of the initial transmission and retransmission of the PUSCH, TBS can be made the same for these transmissions by setting TBS with a bit of a specific field included in the downlink control information (eg, uplink grant), which indicates retransmission.

(Modification)

[0115] The implementation of the random access procedure using steps less than four steps of the existing random access procedure in NR has been discussed. An example is the random access procedure, which consists of two stages. A random access procedure using two stages is also called a two-stage random access procedure, a two-stage RACH, or a 2-stage RACH. The first through fifth aspects described above can be applied in a two-stage RACH.

[0116] An example of a two-stage RACH is shown in FIG. 8. The two-stage RACH may include a first stage of performing a transmission from the UE to a base station and a second stage of performing a transmission from the base station to the UE.

[0117] For example, in the first step, at least one of an uplink and an uplink (hereinafter also referred to as uplink/uplink) in which a preamble and a message are included can be transmitted by the UE to the base station. The preamble may have a function similar to message 1 (PRACH) in the existing random access procedure. The message may have a function similar to that of message 3 (PUSCH) in the existing random access procedure. It should be noted that the preamble and the message transmitted in the first stage may be referred to as message A (Msg. A) or the first message.

[0118] In the second step, at least one of a downlink signal and a downlink (hereinafter also referred to as downlink/downlink) in which response and collision resolution are included can be transmitted from the base station to the UE. The response may have a function similar to that of message 2 (Random Access Response (RAR) sent on the PDSCH) in the existing random access procedure. Collision resolution may have a function similar to message 4 (PDSCH) in the existing random access procedure. It should be noted that the messages transmitted in the second stage may be referred to as message B (Msg. B) or the second message.

[0119] It is assumed that in a two-stage RACH, for example, the transmission of a message (equivalent to the existing message 3) in the first stage is performed using an uplink common channel (eg, PUSCH) (see Fig. 9). In such a case, at least one of the first through fifth aspects described above may be applied to the initial transmission and retransmission of the PUSCH included in message A.

(Radio communication system)

[0120] Next, the structure of a radio communication system according to one embodiment of the present disclosure will be described. In this radio communication system, the radio communication method according to each embodiment of the present disclosure described above can be used for communication alone or in combination.

[0121] In FIG. 10 is a diagram showing an example of a schematic structure of a radio communication system according to one embodiment. The radio communication system 1 may be a system implementing communication using a Long Term Evolution (LTE) system, a 5th generation New Radio (5G NR) mobile communication system, etc. ., the specifications of which have been developed by the 3rd Generation Partnership Project (3GPP).

[0122] The radio communication system 1 can support dual connectivity (MR-DC, multi-RAT dual connectivity) between a plurality of radio access technologies (RAT, Radio Access Technology). MR-DC may include dual connection (E-UTRA-NR (EN-DC) dual connection) between LTE (Evolved Universal Terrestrial Radio Access) and NR, dual connection (NR-E-UTRA (NE-DC) dual connection) between NR and LTE, etc.

[0123] In EN-DC, the LTE Base Station (eNB) (E-UTRA) is the Master Node (MN) and the NR Base Station (gNB) is the Secondary Node (SN). node). In the NE-DC, the NR base station (gNB) is the MN and the LTE (E-UTRA) base station (eNB) is the SN.

[0124] The radio communication system 1 can support dual connection between multiple base stations in the same RAT (e.g., dual connection (NR-NR dual connection (NN-DC)), where both MN and SN are base stations (gNB )NR).

[0125] The radio communication system 1 may include a base station 11, which forms a macro cell C1 with a relatively wide coverage area, and base stations 12 (12a-12c), which form small cells C2, which are located inside the macro cell C1 and which are narrower, than macro cell C1. The user terminal 20 may be located in at least one cell. The location, number, and the like of each cell and user terminal 20 is in no way limited to the aspect shown in the diagram. Hereinafter, base stations 11 and 12 will be collectively referred to as "base stations 10" unless otherwise noted.

[0126] The user terminal 20 may be connected to at least one of a plurality of base stations 10. The user terminal 20 may use at least one of the following: carrier aggregation (CA) and dual connection (DC) using a plurality of component carriers (CC ).

[0127] Each CC may be included in at least one of the first frequency band (frequency band 1 (FR1)) and the second frequency band (frequency band 2 (FR2)). Macro cell C1 may be included in FR1 and small cells C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (below 6 GHz), and FR2 may be a frequency band that is greater than 24 GHz (above 24 GHz). It should be noted that frequency bands, definitions, etc. FR1 and FR2 are not limited in any way, and, for example, FR1 may correspond to a frequency band that is higher than FR2.

[0128] The user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0129] A plurality of base stations 10 may be connected via a wired connection (for example, an optical fiber in accordance with the Common Public Radio Interface (CPRI), X2 interface, etc.) or a wireless connection (for example , NR connection). For example, if the NR link is used as a backhaul link between base stations 11 and 12, base station 11 corresponding to the upstream station may be referred to as "Integrated Access Backhaul (IAB) backhaul donor", and the base station 12 corresponding to the relay station (relay) may be referred to as an "IAB node".

[0130] The base station 10 may be connected to the core network 30 through another base station 10 or directly. For example, core network 30 may include at least one of: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC). English Next Generation Core), etc.

[0131] The user terminal 20 may be a terminal supporting at least one of the communication schemes such as LTE, LTE-A, 5G, etc.

[0132] In the radio communication system 1, a wireless access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, at least one of the downlink (DL) and uplink (UL) can use a cyclic OFDM prefix (CP-OFDM, from the English Cyclic Prefix OFDM), distributed OFDM with discrete Fourier transform (DFT-s-OFDM, Discrete Fourier Transform Spread OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA) Multiple Access), etc.

[0133] The wireless access scheme may be referred to as a "waveform". It should be noted that the radio communication system 1 may use a different wireless access scheme (eg, different single carrier transmission scheme, different multi-carrier transmission scheme) for the uplink and downlink wireless access scheme.

[0134] In the radio communication system 1, downlink common channels (Physical Downlink Shared Channel (PDSCH)) shared by the user terminal 20, broadcast channel (Physical Broadcast Channel (PBCH)), downlink control channel (Physical Downlink control channel (PDCCH)) etc.

[0135] In the radio communication system 1, uplink common channels (Physical Uplink Common Channel (PUSCH)) shared by the user terminal 20, uplink control channel (Physical Uplink Control Channel (PUCCH)), random access channel ( physical random access channel (PRACH)) etc.

[0136] User data, higher-level control information, System Information Blocks (SIBs), etc. transmitted over the PDSCH. User data, higher level management information, etc. may be transmitted on the PUSCH channel. Blocks of basic information (MIB, from the English. Master Information Block) can be transmitted over the Strategic Missile Forces.

[0137] Lower layer control information may be transmitted on the PDCCH. For example, the lower layer control information may include downlink control information (DCI) including scheduling information on at least one of the PDSCHs and PUSCHs.

[0138] It should be noted that the DCI for PDSCH scheduling may be referred to as "downstream assignment", "downstream DCI", etc., and the DCI for PUSCH scheduling may be referred to as "upstream grant", "upstream DCI", etc. It should be noted that PDSCH may be interpreted as "downstream data" and PUSCH may be interpreted as "upstream data".

[0139] For PDCCH detection, a control resource set (CORESET) and a search space can be used. CORESET corresponds to a resource for DCI lookup. The search space corresponds to the search area and the search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may track the CORESET associated with a particular search space based on the search space configuration.

[0140] One search space may correspond to a PDCCH candidate corresponding to one or more levels of aggregation. One or more search spaces may be referred to as a "set of search spaces". It should be noted that "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. of the present disclosure may be interpreted interchangeably.

[0141] Uplink control information (UCI), including at least one of: channel state information (CSI), transmission acknowledgment information (e.g., which may also be referred to as hybrid automatic repeat request (HARQ-ACK) acknowledgment), ACK/NACK, etc.) and a scheduling request (SR) may be transmitted via the PUCCH. Random access preambles can be sent over the PRACH to establish connections with cells.

[0142] It should be noted that downstream, upstream, etc. in the present disclosure may be used without the term "communication". Also, different channels can be mentioned without adding "physical" to the name.

[0143] In the radio communication system 1, a synchronization signal (SS, from synchronization signal), a downlink reference signal (DL-RS, from English. downlink reference signal), etc. can be transmitted. In the radio communication system 1, a cell-specific Reference Signal (CRS), a Channel State Information Reference Signal (CSI-RS), a Demodulation Reference Signal (DMRS). DeModulation Reference Signal), positioning reference signal (PRS, from Positioning Reference Signal), phase tracking reference signal (PTRS, from Phase Tracking Reference Signal), etc. may be transmitted as DL-RS.

[0144] For example, the synchronization signal may be at least one of a primary synchronization signal (PSS, from the English primary synchronization signal) and a secondary synchronization signal (SSS, from the English secondary synchronization signal). A signaling block including SS (PSS, SSS) and Strategic Missile Forces (and DMRS for Strategic Missile Forces) may be referred to as "SS block/RVSN", "SS block (SSB)", etc. It should be noted that SS, SSB, etc. may also be referred to as a "reference signal".

[0145] Sounding reference signal (SRS), demodulation reference signal (DMRS), etc. may be transmitted as the uplink reference signal (UL-RS) in the radio communication system 1. It should be noted that DMRS may be referred to as "user terminal-specific reference signal (UE-specific reference signal)".

(Base station)

[0146] FIG. 11 is a diagram showing an example of the structure of a base station according to one embodiment. The base station 10 includes a control section 110, a transmission/reception section 120, a transmission/reception antenna 130, and a communication channel interface (transmission line interface) 140 . It should be noted that base station 10 may include one or more control sections 110, one or more transmit/receive sections 120, one or more transmit/receive antennas 130, and one or more communication channel interfaces 140.

[0147] It should be noted that the present example mainly shows functional blocks that relate to the characteristic parts of the present embodiment, and it is assumed that the base station 10 may include other functional blocks that are also necessary for radio communication. Part of the processes of each section described below can be omitted.

[0148] The control section 110 controls the entire base station 10. The control section 110 may be formed by a controller, control circuit, or the like described based on a general understanding of the technical field to which the present disclosure pertains.

[0149] The control section 110 may control signal generation, scheduling (eg, resource allocation, display), and so on. The control section 110 can control transmission and reception, measurement, etc. using the transmission/reception section 120, the transmission/reception antennas 130, and the communication channel interface 140. The control section 110 may generate data, control information, a sequence, and so on. to be transmitted as a signal, and forward the generated elements to the transmit/receive section 120. The control section 110 can perform call processing (setup, release) for communication channels, manage the state of the base station 10, and manage radio resources.

[0150] The transmission/reception section 120 may include a baseband section 121, a radio frequency (RF) section 122, and a measurement section 123. The baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212. The transmit/receive section 120 may be formed by a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmit/receive circuit, or the like described based on a general understanding of the technical field to which the present disclosure pertains.

[0151] The transmit/receive section 120 may be structured as a transmit/receive section in one entity, or may be composed of a transmit section and a receive section separately. The transmission section may be formed by the transmission processing section 1211 and the RF section 122. The reception section may be formed by the reception processing section 1212, the RF section 122, and the measurement section 123.

[0152] The transmit/receive antennas 130 may be formed by antennas, such as an antenna array, or the like, described based on a general understanding of the technical field to which the present disclosure pertains.

[0153] The transmit/receive section 120 may transmit the above-described downlink, synchronization signal, downlink reference signal, and so on. The transmit/receive section 120 may receive the above-described uplink, uplink reference signal, and so on.

[0154] The transmit/receive section 120 may generate at least one of a transmit beam and a receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), and so on.

[0155] The transmission/reception section 120 (transmission processing section 1211) can perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), medium access control (MAC) layer processing (for example, HARQ retransmission control), etc., such as data and control information, etc. obtained from control section 110, and may generate a bit string for transmission.

[0156] The transmission/reception section 120 (transmission processing section 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing. discrete Fourier transform) (if necessary), inverse fast Fourier transform (IFFT), precoding, digital-to-analog conversion, etc. bit string to transmit and output the baseband signal.

[0157] The transmit/receive section 120 (RF section 122) may perform RF band modulation, filtering, amplification, and so on. baseband signal and transmit the radio frequency band signal through the transmit/receive antennas 130.

[0158] On the other hand, the transmit/receive section 120 (RF section 122) may perform amplification, filtering, demodulation of the baseband signal, and so on. for the radio frequency band signal received by the transmit/receive antennas 130.

[0159] The transmission/reception section 120 (reception processing section 1212) may apply reception processing such as A/D conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing. , from English inverse discrete Fourier transform) (if necessary), filtering, inverse mapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing, etc. to the received baseband signal and receive user data, etc.

[0160] The transmission/reception section 120 (measurement section 123) may perform measurement related to the received signal. For example, the measurement section 123 can perform a Radio Resource Management (RRM) measurement, a Channel State Information (CSI) measurement, and so on. based on the received signal. The measurement section 123 can measure the received power (for example, the power of the received reference signal (RSRP, from the English. Reference Signal Received Power)), the reception quality (for example, the quality of the received reference signal (RSRQ, from the English. Reference Signal Received Quality), signal ratio / interference plus noise (SINR, from the English Signal to Interference plus Noise Ratio), signal-to-noise ratio (SNR, from the English Signal to Noise Ratio)), signal level (for example, the received signal strength indicator (RSSI, from the English. Received Signal Strength Indicator)), channel information (such as CSI), etc. The measurement results may be output to the control section 110 .

[0161] The link interface 140 can perform transmission/reception (backhaul signaling) of a signal with a device included in the core network 30 or other base stations 10, etc., and receive or transmit user data (user plane data) control plane data, etc. for user terminal 20.

[0162] It should be noted that the transmission section and the reception section of the base station 10 in the present disclosure may be formed by at least one of the following: the transmission/reception section 120, the transmission/reception antennas 130, and the communication channel interface 140.

[0163] It should be noted that the transmission/reception section 120 may receive an uplink common channel. The transmit/receive section 120 may transmit control information (eg, PDCCH order) that indicates transmission of the random access preamble. The transmit/receive section 120 may transmit a response signal corresponding to the random access preamble. The transmit/receive section 120 may transmit information related to the PTRS configuration (eg, higher layer signaling).

[0164] When receiving an uplink shared channel, control section 110 may determine the existence of a phase tracking reference signal (PTRS) based on the type of radio network temporary identifier (RNTI) used for the downlink control information that schedules the uplink common channel. When receiving the uplink common channel, control section 110 may determine the existence of a phase tracking reference signal (PTRS) based on the type of radio network temporary identifier (RNTI) used for the uplink common channel.

[0165] The control section 110 may control the reception based on the assumption that the existence of a phase tracking reference signal (PTRS) transmission on initial transmission and the existence of PTRS transmission on retransmission are generally configured. Alternatively, control section 110 may control reception based on the assumption that the existence of a phase tracking reference signal (PTRS) transmission on initial transmission and the existence of PTRS transmission on retransmission are configured independently (eg, differently).

[0166] The control section 110 may indicate the downlink control information such that the same transport block size is used for the initial transmission PUSCH and the retransmission PUSCH.

(User terminal)

[0167] FIG. 12 is a diagram showing an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control section 210, a transmit/receive section 220, and a transmit/receive antenna 230. It should be noted that the user terminal 20 may include one or more control sections 210, one or more transmit/receive sections 220, and one or more transmit/receive antennas 230.

[0168] It should be noted that the present example mainly shows functional blocks that relate to the characteristic parts of the present embodiment, and it is assumed that the user terminal 20 may include other functional blocks that are also necessary for radio communication. Part of the processes of each section described below can be omitted.

[0169] The control section 210 controls the entire user terminal 20. The control section 210 may be formed by a controller, control scheme, or the like described based on a general understanding of the technical field to which the present disclosure pertains.

[0170] The control section 210 can control signal generation, display, and so on. The control section 210 can control transmission/reception, measurement, etc. using the transmission/reception section 220 and the transmission/reception antenna 230. The control section 210 generates data, control information, sequence, and so on. to be transmitted as a signal, and may forward the generated elements to the transmit/receive section 220.

[0171] The transmit/receive section 220 may include a baseband section 221, an RF section 222, and a measurement section 223. The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212. The transmit/receive section 220 may be formed by a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmit/receive circuit, or the like described based on a general understanding of the technical field to which the present disclosure pertains.

[0172] The transmit/receive section 220 may be structured as a transmit/receive section in one entity, or may be composed of a transmit section and a receive section separately. The transmission section may be formed by the transmission processing section 2211 and the RF section 222. The reception section may be formed by the reception processing section 2212, the RF section 222, and the measurement section 223.

[0173] The transmit/receive antennas 230 may be formed by antennas, such as an antenna array, or the like, described based on a general understanding of the technical field to which the present disclosure pertains.

[0174] The transmit/receive section 220 may receive the above-described downlink, synchronization signal, downlink reference signal, and so on. The transmit/receive section 220 may transmit the above-described uplink, uplink reference signal, and so on.

[0175] The transmit/receive section 220 may generate at least one of a transmit beam and a receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), and so on.

[0176] The transmission/reception section 220 (transmission processing section 2211) may perform Packet Data Downmix Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Media Access Control (MAC) layer processing ) (eg, HARQ retransmission control), etc., such as data and control information, etc. obtained from the control section 210, and may generate a bit string for transmission.

[0177] The transmission/reception section 220 (transmission processing section 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary). ), inverse fast Fourier transform (IFFT) processing, precoding, digital-to-analogue conversion, etc. bit string to transmit and output the baseband signal.

[0178] It should be noted that the decision to apply DFT processing or not may be based on the transform precoding configuration. The transmit/receive section 220 (transmit processing section 2211) may perform per-channel (eg, PUSCH) DFT processing as the above-described transmit processing for channel transmission using a DFT-s-OFDM waveform if transform precoding is enabled, and otherwise case, it is not necessary to perform DFT processing as the above transmission process.

[0179] The transmit/receive section 220 (RF section 222) may perform RF band modulation, filtering, amplification, and so on. baseband signal and transmit the radio frequency band signal through the transmit/receive antennas 230.

[0180] On the other hand, the transmit/receive section 220 (RF section 222) may perform amplification, filtering, demodulation of the baseband signal, and so on. for the radio frequency band signal received by the transmit/receive antennas 230.

[0181] The transmit/receive section 220 (receive processing section 2212) may apply receive processing such as A/D conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering , demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, etc. to the received baseband signal and receive user data, etc.

[0182] The transmit/receive section 220 (measurement section 223) may perform measurement related to the received signal. For example, the measurement section 223 may perform a radio resource management (RRM) measurement, a channel state information (CSI) measurement, and so on. based on the received signal. Measurement section 223 may measure received power (eg, RSRP), reception quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and so on. The measurement results may be output to the control section 210 .

[0183] It should be noted that the transmission section and the reception section of the user terminal 20 in the present disclosure may be formed by at least one of the following: the transmission/reception section 220 and the transmission/reception antenna 230.

[0184] It should be noted that the transmit/receive section 220 may transmit an uplink common channel. The transmit/receive section 220 may receive control information (eg, PDCCH order) that indicates transmission of the random access preamble. The transmit/receive section 120 may transmit the random access preamble. The transmit/receive section 120 may receive a response signal corresponding to the random access preamble. The transmit/receive section 120 may receive information related to the PTRS configuration (eg, higher layer signaling).

[0185] When transmitting an uplink common channel, control section 210 may determine the existence of a phase tracking reference signal (PTRS) transmission based on the type of Radio Network Temporary Identifier (RNTI) used for downlink control information that schedules an uplink common channel. Alternatively, when transmitting an uplink common channel, control section 210 may determine the existence of a phase tracking reference signal (PTRS) transmission based on the type of radio network temporary identifier (RNTI) used for the uplink common channel. The control section 210 may control not to perform PTRS transmission in uplink common channel transmission based on the uplink indication included in the response signal corresponding to the random access preamble.

[0186] When transmitting the uplink common channel based on the response signal, the control section 210 may perform control such that the existence of a phase tracking reference signal (PTRS) transmission on initial transmission and the existence of PTRS transmission on retransmission are common. Even when receiving information related to the PTRS configuration, the control section 210 can control the existence of a PTRS transmission in each of the initial transmission and retransmission regardless of the specified information.

[0187] Alternatively, when transmitting the uplink common channel based on the response signal, the control section 210 may separately control the existence of a phase tracking reference signal (PTRS) transmission on initial transmission and the existence of a PTRS transmission on retransmission. Even when receiving information related to the PTRS configuration, the control section 210 may perform control to perform PTRS transmission in one of initial transmission and retransmission regardless of the specified information, but not to perform PTRS transmission in the other.

[0188] The control section 210 may perform retransmission using the same transport block size as the initial transmission when the index of the modulation and coding scheme that is included in the downlink control information that schedules the retransmission of the uplink common channel is a specific value.

(Hardware structure)

[0189] It should be noted that in the functional diagrams used to describe the above embodiments, blocks are shown in the functional modules. These functional blocks (components) can be implemented by arbitrary combinations of at least one hardware and software. Here, the implementation method of each functional block is not specifically limited. In other words, each functional block may be implemented by one physically or logically single part of the device, or may be implemented by directly or indirectly connecting two or more physically and/or logically separated parts of the device (via, for example, a wired, wireless connection, or the like) and use of this plurality of device parts. The functional blocks may be implemented by combining software into a device as described above, or a plurality of devices as described above.

[0190] Here, the functions include judgment, determination, decision, calculation, calculation, processing, inference, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, assignment, establishment, comparison, guess, expectation, consideration, broadcast, notification, communication, routing, configuration, reconfiguration, distribution (display), assignment, and the like, but the functions are by no means limited to these. For example, the functional block(s) for realizing the transmission function may be called "transmission section (transmission block)", "transmitter" and the like. The implementation method of each component is not specifically limited as described above.

[0191] For example, base station, user terminal, etc. according to one embodiment of the present disclosure, may function as a computer executing the operations of the radio communication method of the present disclosure. In FIG. 13 is a diagram showing an example of a hardware structure of a base station and a user terminal according to one embodiment. Physically, the base station 10 and user terminal 20 described above may be implemented as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007, etc.

[0192] It should be noted that in the present disclosure, words such as apparatus, circuit, device, section, unit, etc. can be interpreted interchangeably. The hardware structure of base station 10 and user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured not to include some of these devices.

[0193] For example, although only one processor 1001 is shown, multiple processors may be provided. In addition, operations may be performed by a single processor or by two or more processors simultaneously, sequentially, or in other ways. It should be noted that processor 1001 may be implemented with one or more integrated circuits.

[0194] Each function of base station 10 and user terminals 20 is implemented, for example, by allowing predetermined software(s) to be read by hardware such as processor 1001 and memory 1002, and by allowing processor 1001 to perform calculations to control communication through the device 1004 communication and control of at least one of reading and writing data to memory 1002 and storage 1003.

[0195] The processor 1001 controls the entire computer by, for example, executing an operating system. The processor 1001 may be configured with a central processing unit (CPU) having interfaces with a peripheral device, a control device, a computing device, a recorder, and so on. For example, at least a portion of the control section 110 (210) described above, the transmit/receive section 120 (220), etc. may be implemented by the processor 1001.

[0196] In addition, the processor 1001 reads programs (program codes), program modules, data, and so on. from at least one of the storage 1003 and the communication device 1004 to the memory 1002 and performs various operations in accordance therewith. With regard to these programs, programs that enable the computer to perform at least part of the operations of the above-described embodiments of the invention can be used. For example, control section 110 (210) may be implemented by program codes stored in memory 1002 and executed by processor 1001; other functional blocks can be implemented similarly.

[0197] Memory 1002 is a computer-readable, writable storage medium and may be formed, for example, by at least one of the following: Read Only Memory (ROM), Erasable and Programmable Read Only Memory (EPROM), Electrically Erasable and Programmable Read Only Memory (EEPROM), Random Access Memory (RAM) and other suitable media for storing information. Memory 1002 may be referred to as a register, cache, main memory (main storage), and so on. The memory 1002 is configured to store executable programs (program codes), program modules, and the like. for implementing a radio communication method according to an embodiment of the present disclosure.

[0198] The storage 1003 is a machine-readable writable medium and can be formed, for example, by at least one of a floppy disk, a floppy disk (a registered trademark of floppy disk), a magneto-optical disk (for example, a Compact Disc ROM, CD-ROM), etc.), Digital Versatile Disc, Blu-ray Disc (registered trademark), removable disk, hard disk, smart card, flash memory device (such as , memory card, removable storage, removable disk), magnetic stripe, database, server, and other suitable storage media. Storage 1003 may be referred to as auxiliary storage.

[0199] The communication device 1004 is a hardware (transmitter/receiver) for computer-to-computer communication via at least wired and wireless networks, and may be called, for example, a network device, a network controller, a network card, a communication module, etc. . The communication device 1004 may be configured to include a high frequency switch, an antenna switch, a filter, a frequency synthesizer, and so on. in order to implement, for example, at least duplex frequency division (FDD, from the English. Frequency Division Duplex) and duplex time division (TDD, from the English. Time Division Duplex). For example, the transmit/receive section 120 (220) described above, transmit/receive antennas 130 (230), etc. may be implemented by the communications device 1004. In the transmit/receive section 120 (220), the transmit section 120a (220a) and the receive section 120b (220b) may be implemented in physical or logical separation.

[0200] The input device 1005 is a device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) for receiving information from outside. The output device 1006 is an output device (eg, display, acoustic emitter, LED indicator, etc.) for outputting information. It should be noted that the input device 1005 and the output device 1006 may be combined into a single structure (eg, a touch panel).

[0201] In addition, these types of devices, including the processor 1001, the memory 1002, etc., are connected by a bus 1007 to exchange information. Bus 1007 may be formed by a single bus, or may be formed by buses that are different for different parts of the device.

[0202] In addition, the structure of the radio base station 10 and user terminals 20 may contain such hardware as a microprocessor, a digital signal processor (DSP, from the English Digital Signal Processor), an application-specific integrated circuit (ASIC, from the English Application-Specific Integrated Circuit), programmable logic device (PLD, from the English Programmable Logic Device), programmable logic element matrix (FPGA, from the English Field Programmable Gate Array), etc., and all or part of the functional blocks can be implemented through the specified hardware. For example, processor 1001 may be implemented by at least one of these hardware.

(Modifications)

[0203] It should be noted that the terms described in this disclosure, and the terms necessary for understanding this disclosure, can be replaced by other terms that have the same or similar meaning. For example, the terms "channel", "symbol" and "signal" (or signaling) can be interpreted interchangeably. In addition, "signals" can be "messages". The reference signal may be abbreviated "RS" (from the English. Reference Signal) and may be called pilot, pilot signal, etc., depending on the applicable standard. In addition, a component carrier (CC) may be referred to as a cell, a frequency carrier, a frequency carrier, and so on.

[0204] A radio frame in the time domain may consist of one or multiple periods (frames). Each of one or more periods (frames) constituting a radio frame may be referred to as a subframe. In addition, a subframe in the time domain may consist of one or multiple slots. The subframe may have a fixed time duration (eg, 1 ms) independent of numerology.

[0205] Here, the numerology may be a communication parameter applied to at least one of the following: the transmission and reception of a particular signal or channel. For example, the numerology may indicate at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering process performed by the transceiver in frequency domain, specific windowing performed by the transceiver in the time domain, and so on.

[0206] A slot may consist of one or multiple symbols in the time domain (orthogonal frequency division multiplexing (OFDM) symbols), single carrier frequency division multiple access (SC-FDMA) symbols, English Single-Carrier Frequency Division Multiple Access), etc.). In addition, the slot can be a temporary element depending on numerology.

[0207] A slot may include a plurality of mini-slots. Each mini-slot may consist of one or more symbols in the time domain. A mini-slot may be referred to as a "sub-slot". A mini-slot can consist of symbols smaller than the number of slots. A PDSCH (or PUSCH) transmitted per unit of time larger than a mini-slot may be referred to as "Type A PDSCH (PUSCH) Mapping." The PDSCH (or PUSCH) transmitted using the mini-slot may be referred to as "Type B PDSCH (PUSCH) Mapping."

[0208] The radio frame, subframe, slot, mini-slot, and symbol are temporary elements in signaling. Radio frame, subframe, slot, mini-slot, and symbol may be referred to by other equivalent terms. It should be noted that temporal elements such as frame, subframe, slot, mini-slot, and symbol in the present disclosure can be interpreted interchangeably.

[0209] For example, one subframe, multiple consecutive subframes, one slot, or one mini-slot may be referred to as a TTI. Thus, at least one of the subframe and/or TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms. It should be noted that an element representing a TTI may not be called a subframe, but a slot, mini-slot, or the like.

[0210] In this document, TTI refers to, for example, the smallest scheduling time element in radio communication. For example, in LTE systems, a base station schedules allocation of RF resources for each user terminal (eg, frequency bands and transmit power values that can be used by each user terminal), in units of TTI. It should be noted that the definition of TTI is not limited to this.

[0211] TTIs may be elementary units of time in the transmission of channel-encoded data packets (transport blocks), code blocks, or codewords, or may serve as elementary units of processing in scheduling, link adaptation, etc. It should be noted that even when TTIs are determined, the time period (eg, number of symbols) for which transport blocks, code blocks, or code words or the like are actually mapped may be shorter than this TTI.

[0212] It should be noted that in the case where TTI is understood to mean one slot or one mini-slot, the minimum elementary unit of time in scheduling can be one or more TTIs (i.e. one or more slots or one or more mini-slots ). In addition, the number of slots (number of mini-slots) constituting this minimum elementary unit of time in scheduling can be adjusted.

[0213] A TTI with a time duration of 1 ms may be called a normal TTI (TTI in 3GPP versions 8-12), a long TTI, a normal subframe, a long subframe, a slot, and so on. A TTI that is shorter than a regular TTI may be referred to as a short TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-slot, a sub-slot, and the like.

[0214] It should be noted that a long TTI (eg, normal TTI, subframe, etc.) may be interpreted by a TTI with a time duration greater than 1 ms, and a short TTI (eg, short TTI, etc.) may be interpreted A TTI with a duration shorter than the long TTI and equal to or greater than 1 ms.

[0215] Resource block (RB, from the English. Resource Block), which is a resource allocation element in the time domain and in the frequency domain, may contain one subcarrier or multiple subcarriers following continuously in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers included in the RB may be determined based on the numerology.

[0216] In the time domain, a resource block may contain one or multiple symbols and may be one slot, one mini-slot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may consist of a single resource block or multiple resource blocks.

[0217] It should be noted that one or more resource blocks can be called a physical resource block (PRB, from the English. Physical RB), a group of subcarriers (SCG, from the English. Subcarrier Group), a group of resource elements (REG, from the English. Resource Element Group), PRB pair, RB pair, etc.

[0218] In addition, the resource block may contain one resource element (RE, from the English. Resource Element) or multiple resource elements.

For example, one RE may correspond to a radio resource area formed by one subcarrier and one symbol.

[0219] The Bandwidth Part (BWP) (which may be referred to as "partial bandwidth", etc.) may represent a subset of contiguous common resource blocks (common RBs) for a particular numerology on a particular carrier. Here, the common RB may be indicated by the RB index based on the common carrier reference point. The PRB may be defined by a particular BWP and may be numbered within the BWP.

[0220] The BWP may include an uplink BWP (UL BWP, uplink BWP) and a downlink BWP (DL BWP, downlink BWP). One or multiple BWPs may be configured on a single carrier for a UE.

[0221] At least one of the configured BWPs may be active, and the UE need not assume the transmission/reception of a particular signal/channel outside of the active BWPs. It should be noted that "cell", "carrier", etc. in the present disclosure may be interpreted as "BWP".

[0222] It should be noted that the above structures of radio frames, subframes, slots, mini-slots, symbols, etc. are just examples. For example, structures such as the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of subcarriers included in composition of RB, number of characters in TTI, character length and length of the cyclic prefix (CP, from the English Cyclic Prefix), etc. can be changed in various ways.

[0223] Also, the information, parameters, etc. described in the present disclosure may be represented by absolute values or relative values with respect to specific values, or may be represented by other relevant information. For example, radio resources may be designated by specific indexes.

[0224] Names used for parameters, etc. in the present disclosure are not limiting in any respect. In addition, the mathematical expressions that use these parameters, etc., may differ from those expressly disclosed in the present disclosure. For example, since the various channels (Physical Uplink Control Channel (PUCCH), Physical Downlink Control Channel (PDCCH), etc.) and information items can be identified by any suitable names, the different names assigned to these individual channels and information items are neither in what respect are not limiting.

[0225] The information, signals, etc. described in the present disclosure may be represented using any of a variety of different methods. For example, data, instructions, commands, information, signals, bits, symbols and code sequences (chips), etc. that may be encountered in this disclosure may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination of the above.

[0226] In addition, information, signals, etc. can be output at least from higher levels to lower levels and from lower levels to higher levels. Information, signals, etc. may be input and/or output via a plurality of network nodes.

[0227] Received and/or transmitted information, signals, etc. may be stored in a specific location (eg, memory) or may be stored using a control table. Information, signals, etc. to be input and/or output can be overwritten, updated or supplemented. Information, signals, etc. output can be removed. Information, signals, etc. input can be transferred to other devices.

[0228] The communication of information is in no way limited to the aspects/embodiments described in this disclosure, and other methods may be used. For example, reporting information in the present disclosure may be performed by using physical layer signaling (eg, downlink control information (DCI), uplink control information (UCI)), higher layer signaling (eg, radio resource control (RRC) layer signaling), broadcast information ( Basic Information Block (MIB), System Information Blocks (SIB), etc.), Media Access Layer (MAC) signaling, other signals, or combinations thereof.

[0229] It should be noted that physical layer signaling may be referred to as L1/L2 control information (L1/L2 control signals) (Layer 1/Layer 2, layer 1/layer 2), L1 control information (L1 control signal), etc. .d. In addition, the RRC layer signaling may be referred to as RRC messages, and the signaling may be, for example, an RRC connection establishment message, an RRC connection reconfiguration message, and so on. Also, MAC layer signaling can be transmitted using, for example, MAC control elements (MAC CE).

[0230] In addition, reporting specific information (eg, reporting that "X does not change") need not be reported explicitly, and may be reported implicitly (eg, by not reporting that specific information or by reporting a different piece of information).

[0231] Definitions may be made based on values represented by a single bit (0 or 1), boolean values representing true or false, or based on comparisons of numeric values (eg, comparisons with a specific value).

[0232] Software, whether called "program", "internal program", "middleware", "microcode", "hardware description language" or otherwise, should be understood in a broad sense, covering instructions, instruction sets, code, code segments, program codes, programs, subroutines, program modules, applications, software applications, software packages, objects, executables, threads of execution, procedures, functions, etc.

[0233] In addition, programs, commands, information, and the like. can be transmitted and received over the communication medium. For example, if a program is transmitted from a website, a server, or other remote sources using at least wired technologies (coaxial cables, fiber optic cables, twisted pair cables, digital subscriber lines (DSL, from English Digital Subscriber Line) etc.) and wireless technologies (infrared radiation, microwaves, etc.), then at least these wired technical means and wireless technical means are also included in the concept of a communication medium.

[0234] The terms "system" and "network" as used in this disclosure may be used interchangeably. "Network" may mean a device (eg, base station) included in the network.

[0235] In the present disclosure, terms such as "pre-coding", "pre-encoder", "weight (pre-coding weight)", "quasi-co-location (QCL)," indication status transmission configuration (TCI status)", "spatial ratio", "spatial domain filter", "transmit power", "phase rotation", "antenna port", "antenna port group", "level", "number of levels", " rank", "resource", "resource set", "resource group", "beam", "beamwidth", "beam angle", "antenna", "antenna element", "panel", etc. can be used interchangeably.

[0236] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point" , "transmission point (TP, from the English transmission point)", "reception point (RP, from the English reception point)", "transmission / reception point (TRP, from the English transmission / reception point)", "panel" , "cell", "sector", "cell group", "carrier", "component carrier", ", etc. may be used interchangeably. A base station may be referred to by terms such as "macro cell", "small cell", "femtocell", "picocell", etc.

[0237] A base station may be configured to serve one or more (e.g., three) cells. When a base station serves a plurality of cells, the entire coverage area of that base station may be divided into a plurality of smaller areas, in each of which communication services may be provided. through base station subsystems, for example, small base stations for premises (remote radio units, eng. Remote Radio Head). The term "cell" or "sector" refers to part or all of the coverage area of at least one base station and the base station subsystem that provides communication services in that coverage area.

[0238] In the present disclosure, the terms "mobile station (MS, from the English mobile station)", "user terminal", "user equipment (UE)" and "terminal" can be used interchangeably.

[0239] A mobile station may be referred to as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a device for wireless communication, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term in some cases.

[0240] At least one of the base station and the mobile station may be called a transmission device, a reception device, a radio communication device, and so on. It should be noted that at least one of the base station and the mobile station may be a device installed on the mobile unit or the mobile unit itself, etc. The movable object may be a vehicle (for example, a car, an airplane, etc.), may be a movable object that moves in an unmanned manner (for example, an unmanned aerial vehicle (drone), a self-driving car, etc.) , or may be a robot (manned type or unmanned type). It should be noted that at least one of the base station and the mobile station also includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor and the like.

[0241] In addition, the base station in the present disclosure can be interpreted as a user terminal. For example, each aspect/embodiment of the present disclosure may be applied to a structure that replaces communications between a base station and a user terminal with communications between multiple user terminals (e.g., which may be referred to as Device-to-Device (D2D). -Device)", "Vehicle-to-Everything (V2X, from English. Vehicle-to-Everything)", etc.). In this case, the user terminals 20 may have the functions of the base stations 10 described above. The words "uplink" and "downlink" can be interpreted as words corresponding to communication between terminals (eg, "referring to the communication side"). For example, uplink, downlink, etc. can be interpreted as a communication side channel.

[0242] Similarly, a user terminal in the present disclosure can be interpreted as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0243] The actions described in this disclosure as being performed by a base station may in some cases be performed by upper nodes. In a network consisting of one or more network nodes with base stations, various operations performed for communication with terminals may be performed by base stations, one or more network nodes other than base stations (for example, mobility management nodes (MME). . Mobility Management Entity), serving gateways (S-GW, from the English Serving-Gateway), etc.) or combinations of the listed nodes.

[0244] Aspects/embodiments illustrated in this disclosure may be used singly or in combination, which may vary depending on the implementation. The order of operations, sequences, block diagrams, etc. used in the present disclosure to describe aspects/embodiments may be changed if this does not lead to inconsistencies. For example, while the various methods are illustrated in the present disclosure with various components of the steps in the order given by way of example, the specific order illustrated herein is in no way limiting.

[0245] The aspects/embodiments illustrated in this disclosure may be applicable to the Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, system 4th generation mobile communications (4G), 5th generation mobile communications system (5G), future radio access (FRA), new radio access technology (New-RAT), new radio access (NX), next generation radio access (FX), global mobile communication system (GSM, from the English Global System for Mobile communications) (registered trademark), CDMA2000, ultra-broadband mobile communications (UMB, from the English Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems that use suitable radio communication methods, and next generation systems that expand based on these systems m. A plurality of systems may be combined (eg, a combination of LTE or LTE-A and 5G, etc.) and applied.

[0246] The expression "based on" (or "based on") as used in this disclosure does not mean "only based on" (or "only based on") unless explicitly stated. In other words, the expression "based on" (or "based on") means both "based on only" and "based on at least" ("based on only" and "based on at least").

[0247] Indication of elements using designations such as "first", "second", etc. in the present disclosure, as a rule, does not limit the number/number or order of these elements. These designations are used in this disclosure for convenience only, as a way to distinguish between two or more elements. Thus, referring to the first and second element does not mean that only two elements can be used, or that the first element must somehow precede the second element.

[0248] The term "decide (determine)" in this disclosure covers a wide variety of actions. For example, the terms "decide (determine)" can be interpreted as meaning making decisions (checks) related to calculation, calculation, processing, inference, research, search, search and query (for example, search in a table, database or some other data structure), fact-finding, etc.

[0249] In addition, the terms "decide (determine)" can be interpreted as meaning making "judgments (determinations)" about reception (for example, receiving information), transmission (for example, transmitting information), input, output, access (for example, access to data in memory), etc.

[0250] In addition, "judgment (determination)", as used here, can be interpreted as meaning making "judgments (determinations)" about resolution, selection, selection, establishment, comparison, etc. In other words, "judgment (determination)" can be interpreted as meaning making "judgments (determinations)" about some action.

[0251] In addition, "judge (determine)" can be interpreted as "guess", "expect", "consider", and the like.

[0252] The terms "connected" and "connected" or any variations of these terms used in this disclosure, mean all direct or indirect connections or communication between two or more elements and may include the presence of one or more intermediate elements between two elements, which are "connected" or "linked" to each other. The relationship or connection between elements can be physical, logical, or a combination of both. For example, "connection" can be interpreted as "access".

[0253] In the present disclosure, when two elements are connected, the two elements may be considered to be "connected" or "connected" to each other by one or more electrical wires, cables, and printed electrical connections, and, as some non-limiting and not including examples, using electromagnetic energy having wavelengths in the radio frequency regions, microwave regions, (both visible and invisible) optical regions, or the like.

[0254] In the present disclosure, the phrase "A and B are different" may mean that "A and B are different from each other." It should be noted that this phrase may mean that "each of A and B is different from C." The terms "separate", "to be connected", etc. can be interpreted similarly to "other".

[0255] When terms such as "include", "including" and variations thereof are used in the present disclosure, these terms are intended to be inclusive, similar to how the term "comprising" is used. In addition, the conjunction "or" used in the present disclosure should not be understood to mean an exclusive disjunction.

[0256] For example, in the present disclosure, when the nouns are used in the singular, the present disclosure may include said nouns in the plural.

[0257] Above, the invention according to the present disclosure has been disclosed in detail, but it should now be apparent to a person skilled in the art that the invention according to the present disclosure is in no way limited to the specific embodiments described in this disclosure. The invention according to the present disclosure can be implemented with various changes and in various modifications without departing from the spirit and scope of the present invention as defined by the claims. Accordingly, the description of the present disclosure is provided for illustrative purposes only and should in no way be construed as limiting the invention in accordance with the present disclosure.

Claims (19)

1. Terminal containing: a transmission section configured to transmit an uplink common channel; And a control section configured to, when scheduling an uplink common channel by a downlink cyclic redundancy code (CRC) control channel scrambled with a predetermined radio network temporary identifier (RNTI), control the transmission of a phase tracking reference signal (PTRS) when transmitting the uplink common channel. 2. The terminal of claim 1, wherein the control section is configured to control not to transmit PTRS when transmitting the uplink common channel based on the uplink indication included in the response signal corresponding to the random access preamble. 3. The terminal of claim 2, wherein the control section is configured to control not to transmit PTRS when retransmitting the uplink common channel that was transmitted based on the uplink indication included in the response signal. 4. The terminal according to any one of paragraphs. 1-3, wherein the control section is configured to control to perform PTRS transmission when transmitting an uplink common channel based on a configured grant. 5. The terminal of claim 1, wherein the control section is configured to determine that a PTRS transmission does not exist in an uplink common channel transmission if an uplink common channel is scheduled via a downlink control channel with a CRC scrambled with an RNTI different from the given RNTI. 6. A radio communication method for a terminal, comprising: uplink common channel transmission; And when scheduling an uplink common channel by a downlink cyclic redundancy control channel (CRC) scrambled by a predetermined radio network temporary identifier (RNTI), controlling the transmission of a phase tracking reference signal (PTRS) when transmitting the uplink common channel. 7. Base station, containing: a transmission section configured to transmit a downlink control channel with a cyclic redundancy code (CRC) scrambled by a predetermined radio network temporary identifier (RNTI); And a receiving section configured to receive an uplink common channel and a phase tracking reference signal (PTRS) corresponding to the uplink common channel; wherein the uplink common channel is scheduled by the downlink control channel. 8. A radio communication system containing a terminal and a base station, in which the terminal contains: a transmission section configured to transmit an uplink common channel; and a control section configured to, when scheduling an uplink common channel by a downlink cyclic redundancy code (CRC) control channel scrambled by a predetermined radio network temporary identifier (RNTI), control the transmission of a phase tracking reference signal (PTRS) when transmitting the uplink common channel; wherein the base station contains: a transmission section configured to transmit a downlink control channel with a cyclic redundancy code (CRC) scrambled by a predetermined radio network temporary identifier (RNTI); And a receiving section configured to receive an uplink common channel and a phase tracking reference signal (PTRS).

Images