RU2795831C1 - Terminal and radio communication method - Google Patents

Abstract

FIELD: mobile communication system.

SUBSTANCE: to achieve the result, the terminal includes a section for receiving information about the number of repetitions of the physical uplink common channel (PUSCH); and a control section configured so that when the physical uplink common channel (PUSCH) to which the retransmission is applied is divided into a plurality of physical uplink common channels (PUSCHs) and transmitted, a determination based on the first redundancy version that is applied to the physical uplink common channel (PUSCH) prior to division, of the second redundancy version that applies to each of the plurality of physical uplink common channels (PUSCHs) is enabled. A part of the second redundancy version is the same as the first redundancy version. The control section is configured to apply a portion of the second redundancy version to the first PUSCH among the plurality of separated PUSCHs.

EFFECT: provision of ability to manage a common channel when the common channel is divided into segments for transmission or reception.

5 cl, 19 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 improve 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 existing LTE systems (for example, 3GPP versions 8-14), a 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] It is currently under study that a future radio communication system (eg, NR) will support scheduling at least one of a given channel and signal (also referred to as "channel/signal") across a slot boundary on a given transmission event. The channel/signal may be, for example, a common channel (eg, an uplink common channel (eg, PUSCH) or a downlink common channel (eg, PDSCH)).

[0007] In this case, UE transmission or reception control is learned by dividing a common channel that is scheduled across a slot boundary (or across a slot boundary) into a plurality of segments. However, the problem is how to manage the common channel when the common channel is divided into segments for transmission or reception.

[0008] It is an object of the present disclosure to provide a radio communication terminal and method that is capable of properly communicating even when a given channel/signal is split for transmission or reception.

Solution

[0009] A terminal according to an aspect of the present disclosure includes: a receiving section, configured to receive information for indicating transmission of an uplink common channel; and a control section configured to control, when dividing the uplink common channel into a plurality of segments and transmitting the segments, to apply at least one segment to at least one of the redundancy version different from the redundancy version configured for the uplink common channel, and a value different from the value of the parameter related to the system cost, which is configured for the uplink common channel.

Beneficial Effects of the Invention

[0010] According to one aspect of the present disclosure, communication can be properly performed even when a given channel/signal is split for transmission or reception.

Brief description of the drawings

[0011]

In FIG. 1 is a diagram showing an allocation example of common channels (eg, PUSCHs);

In FIG. 2 is a diagram showing examples of multi-segment transmissions;

In FIG. 3 is a diagram showing an example of an MCS table;

In FIG. 4 is a diagram showing examples of redundancy versions applied to multiple PUSCH transmissions (eg, PUSCH retransmission);

In FIG. 5A-5E are diagrams showing examples of transmission conditions or transmission parameters that are applied to a plurality of segments;

In FIG. 6 is a diagram showing other examples of transmission conditions or transmission parameters that are applied to a plurality of segments;

In FIG. 7 is a diagram showing other examples of transmission conditions or transmission parameters that are applied to a plurality of segments;

In FIG. 8 is a diagram illustrating self-decodable redundancy versions;

In FIG. 9 is a diagram showing examples of RV versions that apply to a plurality of segments;

In FIG. 10 is a diagram showing other examples of RV versions that apply to multiple segments;

In FIG. 11 is a diagram showing another example of RV versions that apply to multiple segments;

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

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

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

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

Implementation of the invention

(Multi-segment transmission)

[0012] In an existing system (eg, 3GPP Release 15), it has been learned that a UE allocates a time domain resource (eg, a given number of symbols) for an uplink common channel (eg, PUSCH) or a downlink common channel (eg, PDSCH) at a specific a transmission event (also called a period, opportunity, etc.) within the same slot.

[0013] A UE may transmit one or multiple transport blocks (TB) using a PUSCH allocated for a given number of consecutive symbols in a slot on a particular transmission event. The UE may also transmit one or multiple TVs using the PDSCH allocated for a given number of consecutive symbols in a slot on a particular transmission event.

[0014] On the other hand, in a future radio communication system (eg, release 16 or later), it is contemplated that a time domain resource may be allocated to a PUSCH or PDSCH across a slot boundary (or across multiple slots) on a particular transmission event (see Fig. 1). In FIG. 1 shows the case where some PUSCHs are assigned to given sequence numbers (7 symbols in this case) within the same slot, while other PUSCHs are assigned across a slot boundary (or across a slot boundary).

[0015] In particular, a PUSCH is transmitted across the slot boundary, which is allocated to symbols #10 to #13 in slot #n and to symbols #0 to #3 in slot #n+1. Furthermore, it is assumed that when the PUSCH is retransmitted in a plurality of transmission events, as shown in FIG. 1, at least a portion of transmission events or retransmissions may be transmitted across a slot boundary.

[0016] Channel/signal transmission using a time domain resource allocated across a slot boundary (across multiple slots), also referred to as multi-slot transmission, 2-slot transmission, slot boundary transmission, discontinuous transmission, multiple division transmission, or the like. . Similarly, reception of a channel/signal transmitted across a slot boundary is also called multi-segment reception, two-segment reception, over-slot reception, discontinuous reception, multiple division reception, or the like.

[0017] FIG. 2 is a diagram showing examples of multi-segment transmissions. It should be noted that although multi-segment PUSCH transmissions are shown in FIG. 2, they may be replaced by other signals/channels (eg, PDSCHs, etc.). Although the following description illustrates the case where division into each segment is performed based on the slot boundary, the criterion for division into segments is not limited to the slot boundary. In addition, the following description illustrates the case where the symbol length of the PUSCH is 7 symbols, but without limitation, any symbols longer than 2 symbols can be similarly applied.

[0018] FIG. 2, the UE may control the transmission of a PUSCH allocated (or scheduled) within one slot, or a PUSCH allocated across multiple slots, based on a given number of slots. When a time domain resource in one or more slots is allocated to the PUSCH on a particular transmission event, the UE may split (or divide, split) the PUSCH into multiple segments to control the transmission process. For example, the UE may map each segment that is partitioned based on a slot boundary to a predetermined number of allocated symbols in a corresponding slot of each segment.

[0019] Here, a "segment" may be a predetermined number of symbols in each slot allocated to one transmission event, or data transmitted over a predetermined number of symbols. For example, if the initial PUSCH symbol that is allocated for one transmission event is in the first slot and the last PUSCH symbol is in the second slot, one or more of the symbols included in the first slot may be defined as the first segment, and one or more of the symbols included in the second slot may be defined as the second slot with respect to PUSCH.

[0020] It should be noted that a "segment" is a predetermined unit of data and may be at least part of one or multiple TVs. For example, each segment can be formed by one or multiple TVs, one or multiple code blocks (CB, from the English code block) or one or multiple groups of code blocks (CBG, from the English code block group). It should be noted that 1 CB is a unit for encoding a TV, and 1 CB can be a block obtained by dividing a TV into one or a plurality of blocks (CB segmentation). In addition, 1 CBG may include a predetermined number of CBs. It should be noted that the separated segment may also be referred to as a short segment.

[0021] The size (number of bits) of each segment may be determined based on, for example, at least one of: the number of slots assigned to the PUSCH; the number of symbols allocated in each slot; and the ratio of the number of symbols allocated in each slot. In addition, the number of slots may be determined based on the number of slots to which the PUSCH is allocated.

[0022] For example, PUSCH, which is allocated to symbols #5 to #11 in slot #n, is transmitted within one slot (one slot) without crossing a slot boundary. As such, a PUSCH transmission without slot boundary crossing (PUSCH transmission using a given number of symbols allocated within one slot) may also be referred to as a single segment transmission, a single segment transmission, an unsegmented transmission, or the like.

[0023] On the other hand, PUSCH, which is allocated for symbols #10 to #13 in slot #n and for symbols #0 to #2 in slot #n+1, is transmitted across the slot boundary. As such, a PUSCH transmission across a slot boundary (transmission of a PUSCH using a predetermined number of symbols allocated to a plurality of slots) may also be referred to as a multi-segment transmission, a two-segment transmission, a transmission across a slot boundary, or the like.

[0024] In addition, as shown in FIG. 2, when the PUSCH is retransmitted in a plurality of transmission events, multi-hop transmission can be applied to at least a portion of the transmission events. For example, in FIG. 2, the PUSCH is repeated twice, a single-hop transmission is applied to the first PUSCH transmission, and a multi-hop transmission is applied to the second PUSCH transmission.

[0025] In addition, retransmissions may be performed in one or more units of time. Each transmission event may be provided in each unit of time. Each time unit may be, for example, a slot, or a time unit shorter than a slot (eg, also referred to as a mini-slot, sub-slot, half-slot, or the like). For example, in FIG. 2 shows repeated transmissions using 7-character mini-slots, but the retransmission unit (eg, symbol length) is not limited to that shown in FIG. 2.

[0026] In addition, the number of repetitions equal to 1 may indicate that the PUSCH or PDSCH is transmitted once (not repeated).

[0027] Retransmission may also be referred to as slot aggregation transmission, multi-slot transmission, or the like. The number of repetitions (number of aggregation, aggregation factor) N may be given to the UE by at least one of a higher layer parameter (e.g. "pusch-AggregationFactor" or "pdsch-AggregationFactor" of the radio resource control information element (RRC IE). .Radio Resource Control Information Element)) and DCI. In addition, a transmission event, repetition, slot or mini-slot, and the like. can be interpreted interchangeably.

[0028] Thus, cases are contemplated where a PUSCH (also referred to as a nominal PUSCH) for which allocation (or scheduling) is indicated crosses a slot boundary, or a symbol that cannot be used to transmit the PUSCH (for example, a downlink or a flexible symbol), exists within the range of a single transmission (eg 7 symbols). In such cases, it is possible that the UE divides the PUSCH into multiple slots (or repetitions) for transmission control.

[0029] However, when the PUSCH is divided into a plurality of segments for transmission, the problem is how to control the transmission. For example, when the UE transmits a PUSCH, transmission is performed using a given transmission condition or transmission parameter, but the problem is how to control the transmission condition or transmission parameter of separated segments. As an example of a transmission condition, at least one of transport block size (TBS) and redundancy version (RV) can be considered.

<Transport block size>

[0030] FIG. 3 is a diagram showing an example of a Modulation and Coding Scheme table (MCS tables) in the aforementioned future radio communication system. It should be noted that FIG. 3 is just an example and the values shown are not a limitation, and some elements (fields) may be removed, or elements may be added that are not shown.

[0031] As shown in FIG. 3, in a future radio communication system, a table (MCS table) can be defined that relates a modulation order, a coding rate (also called an assumed coding rate, a target annual rate, or the like), and an index (eg, MCS index) indicating the modulation order. and encoding rate (may be stored in the user terminal). It should be noted that in the MCS table a link for spectral efficiency can also be established in addition to the above three items.

[0032] The user terminal may receive DCI for PDSCH scheduling (at least one of the downlink assignment and DCI formats 1_0 and 1_1) and may determine the modulation order (Q _m ) and coding rate (R) used for the PDSCH based on the MCS table (FIG. 3) and the MCS index included in the DCI.

[0033] In addition, the user terminal may receive the DCI for PUSCH scheduling (at least one of the uplink grant and DCI formats 0_0 and 0_1) and may determine the modulation order (Q _m ) and coding rate (R) used for the PUSCH on based on the MCS table (FIG. 3) and the MCS index included in the DCI.

[0034] In a future radio communication system, the user terminal may determine the TBS using at least one of the following steps 1)-4). It should be noted that although the definition of TBS for PDSCH will be described in the following steps 1)-4) as an example, "PDSCH" in the following steps 1)-4) may be replaced by "PUSCH" for proper application to the definition of TBS for PUSCH .

(Stage 1)

[0035] The user terminal determines the number of REs (N _RE ) in the slot.

[0036] Specifically, the user terminal may determine the number of REs ( _N'REs ) allocated for the PDSCH within 1 PRB. For example, the user terminal may determine the number of REs ( _N'REs ) allocated for the PDSCH within 1 PRB based on at least one parameter represented by the following equation (1).

[0037] Here, N ^RB _SC is the number of subcarriers per RB, and may be, for example, N ^RB _SC = 12. N ^sh _symb is the number of symbols (eg, OFDM symbols) scheduled within a slot.

[0038] N ^PRB _DMRS is the number of REs for DMRS per PRB within the scheduled period. The number of REs for the DMRS may include a group system cost related to code division multiplexing (CDM) of the DMRS indicated by the DCI (e.g., at least one of the 1_0, 1_1, 0_0, and 0_1 DCI formats ).

[0039] N ^PRB _oh may be a value configured by a higher layer parameter. For example, N ^PRB _oh is the system cost indicated by the higher layer parameter (Xoh-PDSCH) and can be any of 0, 6, 12, or 18. If the Xoh-PDSCH is not configured in the user terminal (reported to the user terminal), Xoh-PDSCH may be configured to be 0. In addition, Xoh-PUSCH is configured to be 0 in message 3 (msg3) in the random access procedure.

[0040] The user terminal may also determine the total number of REs allocated to the PDSCH (N _RE ). The user terminal may determine the total number of REs allocated to the PDSCH (N _RE ) based on the number of REs allocated to the PDSCH per PRB (N' _RE ) and the total number of PRBs allocated to the user terminal (n _PRB ) (eg, following the equation (2)).

[0041] It should be noted that the user terminal may quantize the number of REs allocated to the PDSCH per PRB (N' _RE ) according to a predetermined rule, and may determine the total number of REs allocated to the PDSCH (N _RE ) based on the quantized number of REs and the total number of PRBs allocated to the user terminal (n _PRBs ).

(Stage 2)

[0042] The user terminal determines an intermediate number of information bits (N _info ). Specifically, the user terminal may determine an intermediate amount (N _info ) based on at least one parameter represented by the following equation (3). It should be noted that the intermediate amount (N _info ) may also be referred to as temporary TBS (TBS _temp ) or the like.

[0043] Here, N _RE is the total number of REs allocated to the PDSCH. R is the coding rate associated with the MCS index, which is included in the DCI, in the MCS table (eg, FIG. 3). Q _m is the modulation order associated with the MCS index, which is included in the DCI in the MCS table. v is the number of PDSCH levels.

(Stage 3)

[0044] When the intermediate number of information bits determined in step 2) (N _info ) is less than (or less than) a predetermined threshold value (eg, 3824), the user terminal may quantize the intermediate number and determine the quantized intermediate number (eg, N' _info ). The user terminal may calculate the quantized intermediate amount (N' _info ) using equation (4), for example.

[0045] In addition, the user terminal can find the closest TBS not less than the quantized intermediate number (N' _info ) using a predetermined table (e.g., a table that associates a TBS with an index (also called a quantization table, a TBS table, or the like). P.)).

(Step 4)

[0046] On the other hand, when the intermediate number of information bits determined in step 2) (N _info ) is greater than (or not less than) a predetermined threshold value (eg, 3824), the user terminal may quantize the intermediate number (N _info ) and determine quantized intermediate quantity (N' _info ). The user terminal may calculate the quantized intermediate amount (N' _info ) using equation (5), for example. It should be noted that the round function may round the result.

[0047] Here, when the coding rate (R) associated with the MCS index, which is in the DCI, in the MCS table (for example, Fig. 3), does not exceed (or less than) a predetermined threshold value (for example, 1/4), the user terminal may determine the TBS based on at least one parameter represented by the following equation (6) (eg, using equation (6)).

N' _info is a quantized intermediate amount and can be calculated using, for example, Equation (5) above. In addition, C can be the number of code blocks (CB, from the English code blocks) into which the TV is divided.

[0048] On the other hand, when the encoding rate (R) is greater than (or not less than) a predetermined threshold value (for example, 1/4), as well as the quantized intermediate number of information bits (N' _info ) is greater than (or not less than) a predetermined threshold value (eg, 8424), the user terminal may determine the TBS based on at least one parameter represented by the following equation (7) (eg, using equation (7)).

[0049] In addition, when the encoding rate (R) is less than (or less than) a predetermined threshold value (e.g., 1/4) and the quantized intermediate amount (N' _info ) is less than (or less than) a predetermined threshold value (e.g., 8424), the user terminal may determine the TBS based on at least one parameter represented by the following equation (8) (eg, using equation (8)).

[0050]

[0051] Thus, it is learned that for a future radio communication system, the user terminal determines an intermediate number of information bits (N _info ), based on at least one of the number of REs (N _RE ) available for the PDSCH or PUSCH in the slot, the rate ( R) coding, modulation order (Q _m ), and number of layers, and determines the TBS for PDSCH or PUSCH based on the quantized intermediate number (N' _info ) obtained by quantizing the intermediate number (N' _info ).

<Redundancy version>

[0052] When a plurality of shared channels (eg, PUSCH) is transmitted or a PUSCH is retransmitted, a given redundancy version (RV) is applied to each PUSCH transmission.

[0053] When the PUSCH (or TV) is retransmitted in a plurality of transmission events, the RV applied to the nth TV transmission event may be determined based on a predetermined rule. For example, for a PUSCH retransmission that is scheduled on a PDCCH (or DCI) with a scrambled CRC (cyclic redundancy check) using a given RNTI, the RV can be determined based on the information reported by the DCI and the transmission event index .

[0054] The UE may determine the RV (which may be interchangeably interpreted as an RV index, RV value, or the like) corresponding to the nth repetition based on the value of a given field (eg, RV field) in the DCI that schedules the PDSCH repetition. . It should be noted that in the present disclosure, the nth repetition may be interchangeably interpreted as the n-1th repetition (eg, the first repetition may be expressed as the 0th repetition).

[0055] For example, the UE may determine the RV index to apply to the first repetition based on the 2-bit RV field. For example, an RV field value of "00", "01", "10", or "11" may correspond to the RV index of the first repetition of '0', '1', '2', or '3', respectively.

[0056] FIG. 4 is a diagram showing an example of RV mapping for each transmission event. The leftmost column of the table in Fig. 4 indicates an RV index (rv _id ) indicated by the RV field. The UE may determine the RV index applied to the nth transmission event according to this value.

[0057] For example, the UE may determine that when the rv _id indicated by the RV field is 0, n mod 4 (equivalent to mod (n, 4))=0, 1, 2, 3 correspond to rv _id =0, 2 , 3, 1, respectively. In other words, starting from the RV indicated by the RV field, the UE may apply the right RV to each repetition of the sequence RV{#0, #2, #3, #1}.

[0058] Only a specific RV sequence may be supported for PUSCH repetition. A particular RV sequence may be an RV sequence (eg, an RV sequence {#0, #2, #3, #1}) including different RV indices (and not including the same RV indices). It should be noted that in the present disclosure, an RV sequence may include one or more RV indices.

[0059] In addition, more than one RV sequence may be supported for PUSCH repetition. More than one RV sequence may include, for example, RV sequences {#0, #2, #3, #1}, {#0, #3, #0, #3}, {#0, #0, # 0, #0}. The number of RV sequences to be applied may be configured according to the type of transmission. For example, one RV sequence may be applied to a dynamic PUSCH transmission where the PUSCH is scheduled in DCI, and multiple RV sequences may be applied to a configured grant (ie, grant-based) PUSCH transmission.

[0060] The UE may be configured with at least one of more than one RV sequence to repeat the PUSCH via higher layer signaling. For example, the UE may determine the RV index to be applied to the first repetition of the configured RV sequence based on the 2-bit RV field. The UE may determine the RV index to be applied to the nth repetition (transmission event) based on the RV index applied to the first repetition, as described above with reference to the first mapping.

[0061] For example, in a configured PUSCH grant transmission, at least one of the RV sequences {#0, #2, #3, #1}, {#0, #3, #0, #3}, and {#0, #0, #0, #0} can be configured via higher layer signaling.

[0062] As described above, in PUSCH transmission, transmission is performed using a given transport block size (TBS), but how to manage TBS for separated segments is a problem. Similarly, in PUSCH transmission, transmission is performed using a given redundancy version (RV), but how to control the redundancy version for a plurality of separated segments is a problem.

[0063] The present inventors have learned how to apply a transmission condition, parameter, or the like. to a plurality of common channel segments and arrived at the idea of the present invention.

[0064] Embodiments relating to the present disclosure will be described in detail below with reference to the drawings. It should be noted that the following first through third aspects may be used alone, or at least two of them may be used in combination. The following description will be given on the example of an uplink common channel (eg, PUSCH), but the applicable signal/channel is not limited to this. For example, the present embodiments can also be applied by changing PUSCH to PDSCH and transmitting to receiving.

[0065] In addition, the aspects described below can be applied to at least one of the common channel (PUSCH or PDSCH) to which retransmission is applied (also referred to as repetition or nominal repetition) and to the common channel to which retransmission is applied. transfer is not applied (or the number of repetitions is equal to one).

(First Aspect)

[0066] In a first aspect, a transport block size (TBS) that is applied to each segment when the PUSCH is divided into a plurality of segments and transmitted will be described.

[0067] When the UE divides the PUSCH (also referred to as nominal PUSCH) scheduled or allocated for a given area or a given transmission event into a plurality of segments and transmits the segments, the UE determines the TBS of each segment after division based on a given condition. This condition may be a transmission condition or a transmission parameter including at least one of time, frequency (freq), modulation and coding scheme (MCS) and number of levels (layer). The modulation and coding scheme (MCS) may be at least one of a modulation order and a target code rate.

[0068] The UE may control the TBS of the plurality of separated segments to be the same. In addition, the UE may control that the TBS of the PUSCH before splitting (also referred to as the original TBS) and the TBS of each segment after splitting are the same. By transmitting Transport Blocks (TBs) using the same TBSs among multiple PUSCH transmissions, a receiving side (eg, a base station in the uplink) can combine the multiple TBs appropriately.

[0069] The UE may determine the TBS of each PUSCH transmission (eg, single-segment PUSCH or multi-segment PUSCH) based on conditions such as time, frequency (freq), modulation and coding scheme (MCS), and number of layers (layer). For example, TBS may be determined based on steps 1)-4) described above.

[0070] When the PUSCH is divided into multiple segments, the allocation for each segment in the time direction (eg, the number of symbols) is less than the allocation for the original PUSCH. Therefore, in order to make the TBS of each segment the same as the original TBS, another transmission condition or transmission parameter (eg, at least one of frequency, MCS, and level) may be changed or may be controlled to apply a given MCS index. For example, the UE may change the transmission condition or transmission parameter applied to each segment based on at least one of the following options from 1-1 to 1-5.

<Option 1-1>

[0071] The frequency resource to be allocated (eg, the number of RBs or the number of PRBs) may be increased for at least one of the plurality of segments. In other words, the number of symbols corresponding to the time parameter is reduced by dividing between the parameters to determine the TBS, which makes it possible to increase the frequency resource corresponding to the frequency (freq) parameter (see FIGS. 5A and 6).

[0072] For example, the UE may perform allocation by increasing the number of PRBs allocated to at least one of the plurality of segments more than the number of PRBs allocated to the PUSCH before splitting (also referred to as the initial number of PRBs). The number of PRBs allocated to the PUSCH before splitting may be indicated by the DCI that schedules the PUSCH.

[0073] The number of PRBs allocated to each segment can be adjusted so that they can be increased by the same amount. For example, when the PUSCH is divided into a first slot and a second slot, the number of PRBs allocated to the first slot and the number of PRBs allocated to the second slot can be changed in the usual manner (eg, increased).

[0074] Alternatively, the number of PRBs allocated to each segment can be adjusted to increase separately. For example, the frequency resource to be increased (eg, the number of PR B) may be determined based on the time resource of each segment (eg, the number of symbols). As an example, the number of PRBs in the first segment having fewer symbols can be changed to more than the number of PRBs in the second segment having more symbols than the first segment's symbols (see retransmission in FIG. 6).

[0075] Information about the frequency resource applied to each segment (eg, the number of PRBs to be increased) may be predetermined in the specification, or may be reported from the base station to the UE using at least one of higher layer signaling and DCI .

[0076] By increasing the frequency resource (eg, number of PRBs) allocated to each slot in this way, the same TBS as in the original PUSCH (eg, the originally allocated PUSCH) can be maintained with or without increasing the coding rate.

<Option 1-2>

[0077] The MCS (eg, at least one of the modulation order and the target code rate) may be increased for at least one of the plurality of segments. In other words, the number of symbols corresponding to the time parameter is reduced by dividing between the parameters to determine the TBS, which allows the MCS to be increased (see FIG. 5B). The MCS may be at least one of a modulation order and a target code rate, or may be an MCS index.

[0078] For example, the UE may perform allocation by increasing the MCS of at least one of the plurality of segments more than the pre-split PUSCH MCS (also referred to as the original MCS). The MCS of the PUSCH before splitting may be specified by the DCI that schedules the PUSCH.

[0079] The MCS of each segment can be adjusted so that they can be increased by the same amount. For example, when the PUSCH is divided into a first slot and a second slot, the MCS of the first slot and the MCS of the second slot can be changed in the usual manner (eg, increased).

[0080] Alternatively, the MCS of each segment can be adjusted to increase separately. For example, the MCS to be incremented may be determined based on the time resource of each segment (eg, the number of symbols). As an example, the MCS of a first segment having fewer symbols may be changed to be greater than the MCS of a second segment having more symbols than the first segment's symbols.

[0081] The MCS information applied to each segment (eg, MCS to be incremented) may be pre-specified in the specification, or may be reported from the base station to the UE using at least one of higher layer signaling and DCI.

[0082] By increasing the MCS applied to each segment in this manner, it is possible to maintain the same TBS as in the original PUSCH (eg, the originally assigned PUSCH) with or without increasing the frequency resource allocation. In addition, since the frequency resource does not change, complicated allocation control of slotted PUSCHs can be suppressed.

<Option 1-3>

[0083] A particular MCS index or a particular modulation order may be applied to at least one of the plurality of segments. The particular MCS index may be a reserved MCS index. In addition, the specific modulation order may be a fixed value predetermined in the specification, or a value reported or configured by the base station.

[0084] When using a specific MCS index (eg, reserved MCS index), the UE does not use the above four steps, but instead, the MCS index is determined based on the DCI (MCS index ranges from 0 to 27) transmitted by the last PDCCH. In other words, the original TBS can be maintained without recalculating the TBS by applying a specific MCS index or a specific modulation order.

<Option 1-4>

[0085] The spatial resource (eg, the number of levels) may be increased for at least one of the plurality of segments. In other words, the number of symbols corresponding to the temporal parameter is reduced due to the separation between the parameters to determine the TBS, which allows to increase the spatial resource (see Fig. 5D and 7).

[0086] For example, the UE may perform allocation by increasing at least one spatial resource (eg, the number of layers) of the plurality of segments more than the PUSCH spatial resource before splitting (eg, the original number of layers). The space resource of the PUSCH before splitting (eg, the number of layers) may be specified by the DCI that schedules the PUSCH.

[0087] The number of levels in each segment can be adjusted so that they can be increased by the same number. For example, when the PUSCH is divided into a first slot and a second slot, the number of layers in the first slot and the number of layers in the second slot can be changed in the usual manner (eg, increased).

[0088] Alternatively, the MCS of each segment can be adjusted to increase separately. For example, the number of levels to be increased may be determined based on the time resource of each segment (eg, the number of symbols). As an example, the number of layers in the first segment having fewer symbols can be changed to more than the number of layers in the second segment having more symbols than the first segment's symbols (see retransmission in FIG. 7).

[0089] Information about the number of layers applied to each segment (eg, the number of layers to be increased) may be predefined in the specification or may be reported from the base station to the UE using at least one of higher layer signaling and DCI .

[0090] By increasing the number of layers applied to each segment in this way, the same TBS as in the original PUSCH (eg, the originally assigned PUSCH) can be maintained, with or without increasing frequency resource allocation and MCS. In addition, since the frequency resource does not change, complicated allocation control of slotted PUSCHs can be suppressed.

<Option 1-5>

[0091] Of the above options 1-1 to 1-4, at least two options can be used in combination. For example, frequency resource (eg, number of PRBs) and MCS may be increased for at least one of the plurality of segments. In other words, the number of symbols corresponding to the time parameter is reduced by the separation between the parameters to determine the TBS, which allows to increase the frequency resource and MCS (see Fig. 5E).

[0092] Alternatively, the frequency resource and the space resource may be increased, the MCS and space resource may be increased, or the frequency resource, MCS and space resource may be increased. Moreover, the parameter to be increased may be common to multiple segments. Alternatively, the parameters to be increased can be configured separately for the respective segments.

<UE operation>

[0093] By dividing the PUSCH into multiple segments and transmitting the segments, the UE may autonomously (eg, automatically) adjust the transmission condition or parameter of each segment. For example, when a scheduled or configured PUSCH crosses a slot boundary, the PUSCH may be split based on the slot boundary, and at least one of the above options 1-1 to 1-5 may be applied to the separated segments.

[0094] For example, the UE adjusts the number of PRBs in each segment when applying option 1-1. The UE adjusts the MCS of each segment when applying option 1-2. The UE adjusts the number of layers in each segment when applying option 1-4. The UE adjusts at least two of the number of PRBs, MCS, and the number of layers of each slot when applying option 1-5.

[0095] The UE may apply a given MCS index (eg, MCS=28, 29, 30, or 31) when applying option 1-3. Which MCS index to apply may be configured by the higher layer signaling or may be selected based on the target code rate. When using option 1-3, the modulation order may be applied as the same value as the modulation order specified in the MCS field included in the DCI.

[0096] Alternatively, when dividing the PUSCH into multiple segments and transmitting the segments, the UE may adjust the transmission condition or parameter of each segment based on information reported from the base station. For example, the UE may determine a transmission condition or parameter to apply to each segment based on information explicitly signaled using at least one of the given fields (eg, new field) of DCI and higher layer signaling.

[0097] Alternatively, the transmission condition or parameter applied to each segment may be controlled based on the scheduling status (or communication status). For example, the UE may manage to apply option 1-1 when a resource is available in the frequency direction of each segment. When the frequency resource of the original PUSCH (eg, the number of assigned PRBs) is not less than a predetermined value, the UE may control the application of another method (eg, any of options 1-2 to 1-4) without increasing the frequency resource.

[0098] When the MCS of the original PUSCH does not exceed a predetermined value, the UE may control the application of another method (eg, any of options 1-1,1-3 and 1-4) without increasing the MCS.

[0099] It is possible that the number of PRBs to be increased is not available even if option 1-1 is selected to maintain the same TBS and MCS as in the original PUSCH. In such a case, the MCS index can be changed using option 1-5. In this case, the MCS index may be changed such that the modified MCS is in a range close to the original MCS index.

[0100] When the code rate (eg, effective code rate) applied to each segment exceeds a predetermined value (eg, 0.95), the UE may control not to transmit (eg, ignore) the PUSCH (or each segment). By ignoring the transmission of a PUSCH segment that is unlikely to be decoded, it is possible to suppress the increase in power consumption of the UE (eg, saving battery power) and reduce the effect of interference on other cells.

[0101] It should be noted that if there is a first segment having a coding rate of a given value or less, and a second segment having a coding rate higher than a given value among the plurality of segments, only the first segment can be controlled for transmission (the second segment is not transmitted), or both the first segment and the second segment may be controlled not to be transmitted.

[0102] Alternatively, the UE may control the transmission of the PUSCH (or each segment) regardless of the coding rate applied to each segment. In other words, the UE can control PUSCH transmission even when the coding rate applied to each slot exceeds a predetermined value. In this case, the base station can appropriately decode the PUSCH having a high coding rate by combining (eg, soft combining) with another PUSCH.

<Transmission power control>

[0103] When the PUSCH is divided into multiple segments (slotted PUSCHs) and transmitted, each segment may be transmitted using the same transmission power as the transmission power configured for the PUSCH before splitting (eg, the original PUSCH). In this case, the UE applies the same transmit power to each segment.

[0104] Alternatively, when the PUSCH is divided into multiple segments (slotted PUSCHs) and transmitted, each segment may be transmitted using a different transmission power than that configured for the PUSCH before splitting (eg, the original PUSCH). For example, if the transmit power configured for the original PUSCH does not exceed a predetermined value (eg, when power is not limited), the transmit power of each slot may be increased (or boosted).

[0105] The set value may be the allowable maximum transmit power (P _MAX ). _{and when} the transmit power of the original _PUSCH does not exceed the allowable maximum power _,f,c (i)), the transmit power can be increased.

[0106] The value for increasing the transmission power (increased power value) may be determined autonomously at the UE side (UE implementation), may be determined in the specification, or may be notified from the base station to the UE through higher layer signaling, or the like. For example, when the coding rate of the segmented PUSCH is higher than (eg, twice) the coding rate of the original PUSCH, the transmit power may be increased by a predetermined value (eg, 3 dB). As a result, deterioration in communication quality can be suppressed even if the coding rate of each segment is high.

(second aspect)

[0107] In a second aspect, a redundancy version (RV) that is applied to each segment when the PUSCH is divided into multiple segments and transmitted will be described.

[0108] When the UE divides the PUSCH (also called nominal PUSCH) scheduled or allocated for a given area or a given transmission event into a plurality of segments and transmits the segments, the UE determines an RV to apply to each segment after division based on a given condition. For example, the UE may determine the RV to apply to each segment based on at least one of the following options from 2-1 to 2-4.

<Option 2-1>

[0109] The same RV can be applied to multiple segments. For example, when dividing the PUSCH into multiple segments and transmitting the segments, the UE applies the same RV to each segment. In addition, the RV that is applied to each segment may be an RV (eg, the original RV) that is configured for PUSCH before splitting (eg, the original PUSCH).

[0110] The RV of the original PUSCH may be reported by the DCI that schedules the original PUSCH. For example, when the RV reported by the PDCCH (or DCI) that schedules the PUSCH is 0, the UE applies 0 to the RN/ for a plurality of segments that are separated from the PUSCH for transmission.

[0111] Thus, by determining the RV to be applied to each hop based on the RV that is pre-configured for PUSCH, scheduling complexity can be reduced.

<Option 2-2>

[0112] Different RVs can be applied to multiple segments. For example, when dividing the PUSCH into multiple segments and transmitting the segments, the UE applies different RVs to at least two segments out of the plurality of segments. In addition, the RV that applies to at least one of the plurality of segments may be an RV that is configured for a PUSCH before splitting (eg, the original PUSCH). An RV applied to other segments can be selected based on a predetermined condition.

[0113] For example, when the PUSCH is divided into two segments (the first segment and the second segment), the original RV may be applied to one of the first segment and the second segment, and a different RV than the original RV may be applied to the other segment. An RV different from the original RV may be determined based on a predetermined condition (eg, any of predetermined conditions 1-4 shown below).

[0114] The RV of the original PUSCH may be reported by the DCI that schedules the original PUSCH. For example, when the RV reported by the PDCCH (or DCI) that schedules the PUSCH is 0, the UE may apply RV=0 to at least one of the plurality of segments that are separated from the PUSCH for transmission and apply a different RV (eg, 2 ) to other segments. At least one of the plurality of segments may be the segment transmitted first in the temporal direction (eg, the first segment).

<Option 2-3>

[0115] An RV other than the RV that is configured for PUSCH before splitting (eg, the original PUSCH) may be applied to multiple segments. In this case, the same RV may be applied to multiple segments, or different RVs may be applied.

[0116] For example, when the PUSCH is divided into two segments (a first segment and a second segment), an RV different from the original RV may be applied to both the first segment and the second segment. An RV different from the original RV may be determined based on a predetermined condition (eg, any of predetermined conditions 1-4 shown below).

[0117] When the same RV (an RV other than the RV configured for the original PUSCH) is configured for each segment, the applicable RV may be selected based on a given condition. For example, when the RV reported by the PDCCH (or DCI) that schedules the PUSCH is 0, the UE may apply a RV other than 0 (eg, RV=2) to a plurality of slots that are separated from the PUSCH for transmission.

[0118] When a different RV is configured for each segment, an applicable RV may be selected based on a predetermined condition. For example, when the RV reported by the PDCCH (or DCI) that schedules the PUSCH is 0, the UE may apply a RV other than 0 to each slot. For example, when there are two segments, the RV of the first segment (eg, the segment transmitted first in the time direction) may be 2, and the RV of the second segment may be 3.

<Option 2-4>

[0119] A particular RV sequence may be applied to multiple segments. The RV sequence may be at least one of {#0, #2, #3, #1}, {#0, #3, #0, #3}, and {#0, #0, #0, #0 }.

[0120] As described above, when using an RV other than the RV that is configured for the original PUSCH before splitting into slotted PUSCHs, the UE may determine the modified RV based on a given condition. It should be noted that when splitting some PUSCHs of repeated transmissions or multiple PUSCH transmissions, the UE may only change the RV of the split slotted PUSCHs, or may change the RVs of the slotted PUSCHs and other non-splitted PUSCHs (eg, the PUSCH that is transmitted after the split slotted PUSCH).

<When changing only the segmented PUSCH RV>

[Set condition 1]

[0121] The UE may determine the RV to be applied to the plurality of segments that are separated from the original PUSCH based on the given RV sequence. For example, it is assumed that the RV sequence is {#0, #2, #3, #1} and the number of separated segments is two (first segment and second segment). In this case, the UE may apply the RV reported by the PDCCH (or DCI) that schedules the PUSCH for the first hop and apply the RV to the right of the RV in the RV sequence to the second hop.

[0122] For example, when the RV reported by the PDCCH (or DCI) that schedules the PUSCH is 0, the UE may determine that the RV of the first slot is 0 and the RV of the second slot is 2.

[0123] It should be noted that the RV sequence used is not limited to {#0, #2, #3, #1}. Other RV sequences may also be used, such as {#0, #3, #0, #3} or {#0, #0, #0, #0}. The RV sequence to be used may be predetermined in the specification, or may be notified from the base station to the UE by higher layer signaling or the like.

[0124] Thus, when an RV segment of a divided PUSCH is determined based on a given RV sequence, decoding gain can be obtained by receiving all segments.

[Set condition 2]

The UE may select the RV to be applied to the plurality of slots that are separated from the original PUSCH from the specific RV values. The particular RV value may be a self-decodable RV. The self-decodable RV may be an RV containing a large number of bits related to system information (system bits) (eg, RV=0.3) (see FIG. 8). By receiving the PUSCH to which the self-decodable RV is applied, the probability of decoding based on the PUSCH to which the RV is applied can be increased.

[0125] For example, the number of separated segments is assumed to be 2 (first segment and second segment). In this case, if the RV reported by the PDCCH (or DCI) that schedules the PUSCH is a specific RV, the UE may apply the reported RV (or the reported RV and another specific RV). For example, when the RV reported by the PDCCH (or DCI) that schedules the PUSCH is 0, the UE may determine that the RV of the first slot is 0 and the RV of the second slot is another specific RV equal to 3.

[0126] On the other hand, if the RV reported by the PDCCH (or DCI) that schedules the PUSCH is not a specific RV, the UE may apply the reported RV and the specific RV to two segments, respectively. For example, it is assumed that in PUSCH retransmissions, the second PUSCH transmission is divided into multiple segments. If the RV of the second PUSCH transmission (the PUSCH to be split) is 2 based on the PDCCH (or DCI) that schedules the PUSCH repetition, the UE may determine that the RV of the first slot is 2 and the RV of the second slot is a specific RV equal to 0 or 3 ( see Fig. 9).

[0127] Alternatively, the UE may apply a specific RV to multiple segments without applying the reported RV, unless the RV reported by the PDCCH (or DCI) that schedules the PUSCH is not a specific RV.

[0128] Thus, by applying the self-decodable RV, the probability of decoding the PUSCH to which the RV is applied can be improved, which can improve the communication quality (eg, SNR).

<When changing the RV of a segmented PUSCH and the RV of another PUSCH>

[0129] When dividing some PUSCHs from the retransmitted PUSCHs into multiple segments, the UE may change the RV of the separated segment to be different from the RV configured for the original PUSCH and also change the RV of the PUSCH transmitted subsequently. For example, for a PUSCH transmitted after transmitting a PUSCH divided into a plurality of segments, the RV may be determined in the same way as for the segments.

[Set condition 3]

[0130] The RV applied to the unsplit PUSCH may be determined in view of the RV applied to the split segment. For example, when selecting an RV (e.g., an RV other than the RV of the original PUSCH) to be applied to the split segment based on the given RV sequence, the RV to be applied to the remaining repeated PUSCH after the segmented PUSCH can also be determined based on the given RV sequence.

[0131] For example, the RV sequence is assumed to be {#0, #2, #3, #1} and the number of separated segments is two (first segment and second segment). In this case, the UE may apply the RV reported by the PDCCH (or DCI) that schedules the PUSCH to the first hop, and apply the RV near (eg, to the right of) the reported RV in the RV sequence to the second hop.

[0132] For example, it is assumed that in PUSCH retransmissions, the second PUSCH transmission is divided into multiple segments. If the RV of the second PUSCH transmission is 2 based on the PDCCH (or DCI) that schedules the PUSCH repetition, the UE may determine that the RV of the first slot is 2 and the RV of the second slot is 3. In addition, the UE sets the RV value applied to the PUSCH transmission , following the segment equal to 1. In this case, the UE manages the use of different RVs even if the original RN/for PUSCH is 3 (see FIG. 10).

[0133] It should be noted that the RV sequence used is not limited to {#0, #2, #3, #1}. Other RV sequences may also be used, such as {#0, #3, #0, #3} or {#0, #0, #0, #0}. The RV sequence to be used may be predetermined in the specification, or may be notified from the base station to the UE by higher layer signaling or the like.

[0134] Thus, when an RV segment of a divided PUSCH is determined based on a given RV sequence, decoding gain can be obtained by receiving all segments.

[Set condition 4]

[0135] The RV applied to the unsplit PUSCH may be determined without considering the RV applied to the split segment. In other words, the RV versions are defined separately for the split segmented PUSCH and for the unsplit PUSCH.

[0136] For example, when selecting an RV (e.g., an RV other than the RV of the original PUSCH) to be applied to the separated segment based on the given RV sequence, the RV to be applied may be determined based on the given RV sequence separately for the PUSCH divided into many segments, and for an unshared PUSCH.

[0137] For example, it is assumed that the RV sequence is {#0, #2, #3, #1} and the number of separated segments is two (first segment and second segment). In this case, the UE may apply the RV reported by the PDCCH (or DCI) that schedules the PUSCH to the first slot and the RV near (eg, to the right of) the reported RV in the RV sequence to the second slot. In addition, the RV sequence can be applied to a PUSCH that is not divided into multiple segments (PUSCH excluding PUSCH divided into multiple segments).

[0138] For example, in PUSCH retransmissions, it is assumed that the second PUSCH transmission is divided into multiple segments. When the RV reported by the PDCCH (or DCI) that schedules the PUSCH repetition is 0, the UE sets the RV to be applied to the first PUSCH transmission to 0.

[0139] On the other hand, in the second PUSCH transmission that is divided into a plurality of segments, the RV of the first segment may be determined to be 0, and the RV of the second segment may be determined to be 2. In addition, the UE sets the RV applied to the next PUSCH transmission behind the second segment, equal to 2 (see Fig. 11). In this case, the UE controls the application of the RV sequence (eg, to apply different RVs) except for the second PUSCH, even if the original RV for the third PUSCH is 3.

[0140] It should be noted that the RV sequence used is not limited to {#0, #2, #3, #1}. Other RV sequences may also be used, such as {#0, #3, #0, #3} or {#0, #0, #0, #0}. The RV sequence to be used may be predetermined in the specification, or may be notified from the base station to the UE by higher layer signaling or the like.

<Modification>

[0141] The method for determining the RV to be applied to the PUSCH transmission may be selected based on a given condition. The UE may select the RV determination method based on any of the following options A to D.

[Option A]

[0142] The RV determination method may be configured based on the PUSCH scheduling type. For example, the UE may apply different RV determination methods to a dynamic grant (ie, grant-based) PUSCH that is dynamically scheduled in DCI and a configured grant PUSCH that is not dynamically scheduled to DCI. The RV determination method may be specified in the specification, or may be configured from the base station to the UE with higher layer signaling or the like.

[Option B]

[0143] The RV determination method may be reported from the base station to the UE using L1 signaling. For example, the UE may select a method for determining the RV based on at least one of the given field, the DCI format, and the applied RNTI DCI information transmitted from the base station.

[Option C]

[0144] The RV determination method may be selected based on the TBS determination method (or the TBS determination method and the RV determination method may be related to each other). For example, when using the first TBS determination method (option 1-1), the UE may apply the first RV determination method (eg, predetermined condition 2 of 2-2).

[Option D]

[0145] The RV determination method may be communicated from the base station to the UE using higher layer signaling. Alternatively, the way in which RV is determined may be predetermined in the specification.

(Third aspect)

[0146] In a third aspect, a parameter relating to system overhead (eg, N ^PRB _oh ) applied to each segment when the PUSCH is divided into a plurality of segments for transmission will be described.

[0147] The system cost related parameter (eg, N ^PRB _oh ) indicates the system cost from other signals (eg, CSI-RS, PT-RS, or the like). For example, N ^PRB _oh may indicate the number of resource elements (RE) of other signals in the PRB, and N ^PRB _oh may be a value configured by a higher layer parameter. For example, N ^PRB _oh is the system cost indicated by the higher layer parameter (Xoh-PUSCH) and can be any value of 0, 6, 12, or 18. If Xoh-PUSCH is not configured in the user terminal (reported to the user terminal) , Xoh-PUSCH may be configured as 0. The UE may determine TBS or the like. based on N ^PRB _oh .

[0148] When the UE divides the PUSCH (also referred to as the nominal PUSCH) scheduled or allocated for a given area or a given transmission event into a plurality of segments and transmits the segments, the UE determines N ^PRB _oh to be applied to each segment after the division, based on the given conditions. For example, the UE may determine N ^PRB _oh to apply to each segment based on at least one of the following options from 3-1 to 3-4.

<Option 3-1>

[0149] The same N ^PRB _oh can be applied to multiple segments. For example, it is assumed that when dividing the PUSCH into multiple segments and transmitting the segments, the UE applies the same N ^PRB _oh to each segment. In addition, the N ^PRB _oh applied to each segment may be the N ^PRB _oh that is configured for the PUSCH before splitting (eg, the original PUSCH).

[0150] The N ^PRB _oh of the original PUSCH may be signaled by higher layer signaling (eg, xOverhead). For example, when the NPRB0h reported by higher layer signaling is X equal to 0, the UE applies X as N ^PRB _oh to a plurality of segments that are separated from the PUSCH for transmission.

[0151] Thus, by determining the N ^PRB _oh to be applied to each segment, scheduling complexity can be reduced based on the N ^PRB _oh configured for the PUSCH in advance.

<Option 3-2>

[0152] Different N ^PRB _oh can be applied to multiple segments. For example, it is assumed that when dividing the PUSCH into multiple segments and transmitting the segments, the UE configures different N ^PRB _oh for at least two segments of the multiple segments. In addition, the N ^PRB _oh applied to at least one of the plurality of segments may be the N ^PRB _oh (original N ^PRB _oh ) that is configured for the PUSCH before splitting (eg, the original PUSCH).

[0153] N ^PRB _oh applied to other segments may be NPRB0h>different from the original N ^PRB _oh . N ^PRB _oh different from the original N ^PRB _oh may be selected based on a predetermined condition. For example, the UE may determine N ^PRB _oh different from the original N ^PRB _oh based on at least one of a scheduling condition, a given DCI field, and higher layer signaling.

[0154] For example, when N ^PRB _oh reported by higher layer signaling is 6, the UE may apply N ^PRB _oh =6 to at least one of the plurality of segments that are separated from the PUSCH for transmission, and may apply different N ^PRBs _oh (for example, 0) to other segments. At least one of the plurality of segments (eg, the first segment) may be the segment transmitted first in the time direction.

<Option 3-3>

[0155] N ^PRB _oh other than NPRB0h>which is configured for PUSCH before splitting (eg, the original PUSCH) may be applied to multiple segments. In this case, the same N ^PRB _oh may be applied to multiple segments, or different N ^PRB _oh may be applied.

[0156] When the same N ^PRB _oh is configured for each segment (N ^PRB _oh different from the N ^PRB _oh configured for the original PUSCH), the N ^PRB _oh to be applied may be selected based on a given condition. For example, when N ^PRB _oh reported by higher layer signaling is 0, the UE may apply N ^PRB _oh other than 0 (eg, N ^PRB _oh =6) to a plurality of slots that are separated from the PUSCH for transmission.

[0157] When a different N ^PRB _oh is configured for each segment, the N ^PRB _oh to be applied may be selected based on a predetermined condition. For example, when N ^PRB _oh reported by higher layer signaling is 0, the UE may apply N ^PRB _oh other than 0 to each segment. For example, when there are two segments, the N ^PRB _oh of the first segment (eg, the segment transmitted first in the time direction) may be 6, and the N ^PRB _{oh of} the second segment may be 12.

[0158] Thus, assuming that N ^PRB _oh is higher than the original N ^PRB _oh for the segment after splitting, it is possible to suppress over-allocation caused by N ^PRB _oh mismatch or applying a coding rate higher than the target code rate.

<Option 3-4>

A particular N ^PRB _oh may be applied to multiple segments. Specific N ^PRB _oh may be 0. (Radio communication system)

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

[0160] In FIG. 12 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).

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

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

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

[0164] 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. Location, quantity, etc. each cell and user terminal 20 are not limited in any way 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.

[0165] User terminal 20 may be connected to at least one of a plurality of base stations 10. User terminal 20 may use at least one of carrier aggregation and dual connection (DC) using multiple component carriers (CC).

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

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

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

[0169] The base station 10 may be connected to the core network 30 through another base station 10 or directly. For example, the 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.

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

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

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

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

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

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

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

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

[0178] 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 keep track of the CORESET associated with the given search space based on the search space configuration.

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

[0180] 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 a hybrid automatic repeat request (HARQ-ACK) acknowledgment, ACK/NACK, etc.) and scheduling request (SR) may be transmitted via the PUCCH. Random access preambles can be sent over the PRACH to establish connections with cells.

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

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

[0183] 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 signal block including SS (PSS, SSS) and Strategic Missile Forces (and DMRS for Strategic Missile Forces) may be referred to as "SS block / Strategic Missile Forces", "SS block (SSB)", etc. It should be noted that SS, SSB, etc. may also be referred to as a "reference signal".

[0184] 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)

[0185] FIG. 13 is a diagram showing an example of a structure of a base station according to one embodiment. The base station 10 includes a control section 110, a transmit/receive section 120, transmit/receive antennas 130, and a 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 transmission line interfaces 140.

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

[0187] Control section 110 controls the entire base station 10. 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 relates.

[0188] 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 transmission line interface 140. The control section 110 may generate data, control information, a sequence, and so on. to transmit 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.

[0189] The transmit/receive 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.

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

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

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

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

[0194] 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. received from the control section 110, and may generate a bit string for transmission.

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

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

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

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

[0199] 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, received signal strength indicator (RSSI, from English. Received Signal Strength Indicator)), channel information (such as CSI), etc. The measurement results may be output to the control section 110 .

[0200] The transmission line 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.

[0201] 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 transmission line interface 140.

[0202] It should be noted that the transmission/reception section 120 transmits information for indicating transmission of the uplink common channel. The transmit/receive section 120 may transmit at least one of the number of repetitions, TBS information, RV information, and system cost information.

[0203] The control section 110 may control, when the UE divides the uplink common channel into a plurality of segments and transmits the segments, to apply a transmission condition different from the transmission condition configured for transmitting the uplink common channel to at least one segment.

[0204] The control section 110 may control when the UE divides the uplink common channel into a plurality of segments and transmits the segments to apply a redundancy version different from the redundancy version configured to transmit the uplink common channel, or apply the same redundancy version as the redundancy version , configured to transmit an uplink common channel to at least one segment.

(User terminal)

[0205] In FIG. 14 is a diagram showing an example of a 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.

[0206] It should be noted that the present example mainly shows functional blocks that are related 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.

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

[0208] The control section 210 may 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.

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

[0210] The transmit/receive section 220 may be configured as a transmit/receive section in a single 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.

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

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

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

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

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

[0216] It should be noted that the decision to apply DFT processing or not may be based on the transform precoding configuration. The transmission/reception section 220 (transmission processing section 2211) may perform, for a given channel (eg, PUSCH), DFT processing as the above-described transmission 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.

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

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

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

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

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

[0222] It should be noted that the transmission/reception section 220 receives information for indicating transmission of the uplink common channel. The transmit/receive section 220 may receive at least one of the number of repetitions, TBS information, RV information, and system cost information.

[0223] The control section 210 may control, when dividing the uplink common channel into a plurality of segments and transmitting the segments, to apply to at least one segment a transmission condition different from the transmission condition configured for transmitting the uplink common channel.

[0224] For example, control section 210 may control a frequency resource used to transmit at least one segment to be larger than a frequency resource that is configured to transmit an uplink common channel. Alternatively, control section 210 may control changing at least one modulation and coding scheme and modulation order used to transmit at least one segment from at least one modulation and coding scheme and modulation order that is configured to transmit the uplink common channel. . Alternatively, control section 210 may control the space resource used to transmit at least one segment to be larger than the space resource that is configured to transmit the uplink common channel. A plurality of segments may be located in different slots.

[0225] In addition, the control section 210 can control when dividing the uplink common channel into a plurality of segments and transmitting the segments to apply to at least one segment of at least one of: a redundancy version other than the redundancy version configured for the uplink common channel; and a value different from the value of the parameter related to the system cost, which is configured for the uplink common channel. Alternatively, when dividing the uplink common channel into a plurality of segments and transmitting the segments, control section 210 may control to apply to the plurality of segments at least one of: the same redundancy version as the redundancy version configured for the uplink common channel; and the same value as the system overhead parameter value configured for the uplink common channel.

[0226] For example, control section 210 may apply at least one of a particular redundancy version and a particular system cost parameter value to at least one of the plurality of shards. When dividing some uplink common channels among the plurality of retransmitted uplink common channels into a plurality of segments and transmitting the segments, the control section 210 may apply to the uplink common channel that is transmitted without splitting into multiple segments the same redundancy version as the redundancy version that is configured for uplink common channel transmissions. Alternatively, when dividing some uplink common channels among the plurality of retransmitted uplink common channels into a plurality of segments and transmitting the segments, control section 210 may apply to the uplink common channel that is transmitted without splitting into multiple segments, a redundancy version different from the redundancy version that configured to transmit uplink common channels. (Hardware structure)

[0227] 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 connecting two or more physically or logically separated parts of the device directly or indirectly (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.

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

[0229] For example, a 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. 15 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.

[0230] It should be noted that in the present disclosure, words such as apparatus, circuit, device, section, block, 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.

[0231] 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 the processor 1001 may be implemented with one or more integrated circuits.

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

[0233] 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 part of the control section 110 (210) described above, the transmit/receive section 120 (220), etc. may be implemented by the processor 1001.

[0234] 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 means of program codes stored in memory 1002 and executed by processor 1001; other functional blocks can be implemented similarly.

[0235] The 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.

[0236] 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 medium. Storage 1003 may be referred to as auxiliary storage.

[0237] 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, the transmit/receive antenna 130 (230), etc. may be implemented by communication 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.

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

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

[0240] 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)

[0241] 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 a 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.

[0242] A radio frame in the time domain may consist of one or multiple periods (frames). Each of one or a plurality of 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.

[0243] Here, the numerology may be a communication parameter applied to at least one of the following: transmission and reception of a given 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.

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

[0245] 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 a "Type A PDSCH (PUSCH) Mapping". The PDSCH (or PUSCH) transmitted using the mini-slot may be referred to as "Type B PDSCH (PUSCH) Mapping."

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

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

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

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

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

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

[0252] It should be noted that a long TTI (eg, normal TTI, subframe, etc.) can be interpreted by a TTI with a time duration of more than 1 ms, and a short TTI (eg, shortened TTI, etc.) can be interpreted TTI with a duration less than the duration of the long TTI and equal to or greater than 1 ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0268] In addition, reporting the provided information (eg, reporting that "X does not change") need not be explicitly communicated, and may be communicated implicitly (eg, by not reporting this given information or by reporting another piece of information).

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

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

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

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

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

[0274] 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. can be used interchangeably. A base station may be referred to by terms such as "macro cell", "small cell", "femto cell", "pico cell", etc.

[0275] The base station may be configured to serve one or more (eg, three) cells. When a base station serves many cells, the entire coverage area of that base station can be divided into many smaller areas, in each of which communication services can be provided through subsystems of the base station, for example, small base stations for premises (remote radio units, English 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.

[0276] In the present disclosure, the terms “mobile station (MS)*, “user terminal”, “user equipment (UE)”, and “terminal” may be used interchangeably.

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

[0278] 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 mounted on a moving object, or the moving object itself, etc. The moving object may be a vehicle (for example, a car, an airplane, etc.), may be a moving 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.

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

[0280] Similarly, the 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.

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

[0282] 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, flowcharts, etc. used in this 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.

[0283] The aspects/embodiments illustrated in this disclosure may be applicable to the Long Term Evolution (LTE) scheme, 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 (W1MAX (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. A plurality of systems may be combined (eg, a combination of LTE or LTE-A and 5G, etc.) and applied.

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

[0285] Indication of elements using designations such as "first", "second", etc. in this disclosure, as a rule, does not limit the number / quantity 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.

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

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

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

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

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

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

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

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

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

[0295] Above, the invention according to the present disclosure has been disclosed in detail, but it will 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 (25)

1. Terminal containing: a receiving section, configured to receive information about the number of repetitions of the physical uplink common channel (PUSCH); And a control section configured when the physical uplink common channel (PUSCH) to which the retransmission is applied is divided into a plurality of physical uplink common channels (PUSCHs) and transmitted, determining, based on the first redundancy version that is applied to the physical uplink common channel channel (PUSCH) prior to splitting, a second redundancy version that applies to each of the plurality of physical uplink common channels (PUSCHs), wherein part of the second redundancy version is the same as the first redundancy version, and the control section is configured to apply a portion of the second redundancy version to the first PUSCH among the plurality of separated PUSCHs. 2. The terminal of claim 1, wherein the control section is configured, when the PUSCH is assigned across two slots, to divide the PUSCH into a plurality of PUSCHs based on a slot boundary. 3. A radio communication method for a terminal, comprising: receiving information about the number of repetitions of the physical uplink common channel (PUSCH); And when the Physical Uplink Shared Channel (PUSCH) to which retransmission is applied is divided into a plurality of Physical Uplink Shared Channels (PUSCHs) and transmitted, determining, based on the first version of the redundancy that is applied to the Physical Uplink Shared Channel (PUSCH) before separation, a second redundancy version that applies to each of the plurality of physical uplink common channels (PUSCHs), wherein part of the second redundancy version is the same as the first redundancy version, and at said determination step, apply part of the second redundancy version to the first PUSCH among the plurality of separated PUSCHs. 4. Base station, containing: a transmission section configured to transmit information about the number of repetitions of the physical uplink common channel (PUSCH); And a control section configured, when the physical uplink common channel (PUSCH) to which the retransmission is applied, is divided into a plurality of physical uplink common channels (PUSCHs) and transmitted, controlling the reception of the plurality of physical uplink common channels (PUSCHs), to which the second redundancy version is applied and transmitted, the second redundancy version being determined based on the first redundancy version that is applied to the physical uplink common channel (PUSCH) prior to separation, wherein part of the second redundancy version is the same as the first redundancy version, and a part of the second redundancy version is applied to the first PUSCH among the plurality of separated PUSCHs. 5. A radio communication system comprising a terminal and a base station in which terminal contains: a receiving section, configured to receive information about the number of repetitions of the physical uplink common channel (PUSCH); And a control section configured when the physical uplink common channel (PUSCH) to which the retransmission is applied is divided into a plurality of physical uplink common channels (PUSCHs) and transmitted, determining, based on the first redundancy version that is applied to the physical uplink common channel channel (PUSCH) prior to splitting, a second redundancy version that applies to each of the plurality of physical uplink common channels (PUSCHs), wherein part of the second redundancy version is the same as the first redundancy version, and the terminal control section is configured to apply a portion of the second redundancy version to the first PUSCH among the plurality of separated PUSCHs; And base station contains: a transmission section configured to transmit said information; And a control section configured to control the reception of a plurality of physical uplink common channels (PUSCHs).

Images