WO2022264428A1

WO2022264428A1 - Terminal, and radio communication method

Info

Publication number: WO2022264428A1
Application number: PCT/JP2021/023273
Authority: WO
Inventors: 春陽越後; 浩樹原田; 大輔栗田
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2021-06-18
Filing date: 2021-06-18
Publication date: 2022-12-22
Also published as: EP4358612A1; JPWO2022264428A1; CN117501774A

Abstract

This terminal is provided with: a control unit which multiplies a second size of an information block to be transmitted over a physical uplink shared channel in one time resource unit by a factor, to determine a first size of an information block to be transmitted using a transmission method for transmitting information via a physical uplink shared channel straddling a plurality of time resource units; and a transmitting unit for transmitting an information block having the first size in a plurality of time resource units.

Description

Terminal and wireless communication method

The present disclosure relates to terminals and wireless communication methods.

In the Universal Mobile Telecommunication System (UMTS) network, Long Term Evolution (LTE) has been specified with the aim of achieving even higher data rates and lower delays. In addition, a successor system to LTE is also being considered for the purpose of further widening the bandwidth and speeding up from LTE. LTE successor systems include, for example, LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), New There is a system called Radio (NR).

For example, NR considers how to handle blocks of information (e.g., transport blocks (TB)) that are transmitted over multiple radio resources (e.g., physical uplink shared channels assigned to multiple slots). (Non-Patent Document 2).

　There is room for discussion on how to determine the appropriate size of blocks of information to be transmitted over multiple radio resources.

One aspect of the present disclosure provides a terminal and wireless communication method capable of determining an appropriate size for blocks of information to be transmitted over multiple wireless resources.

A terminal according to an aspect of the present disclosure multiplies a second size of an information block to be transmitted in a physical uplink shared channel in one time resource unit by a coefficient, and the physical a control unit for determining a first size of an information block to be transmitted in a transmission scheme for transmitting information via an uplink shared channel; and transmitting an information block having the first size in units of the plurality of time resources. and a transmission unit for

A wireless communication method according to an aspect of the present disclosure spans a plurality of time resource units by multiplying a second size of an information block transmitted in a physical uplink shared channel in one time resource unit by a coefficient. determining a first size of an information block to be transmitted in a transmission scheme for transmitting information over the physical uplink shared channel, and transmitting the information block having the first size in the plurality of time resource units; .

FIG. 4 is a diagram showing an example of PUSCH allocation by TBoMS; 1 is a diagram showing an example of a radio communication system according to an embodiment; FIG. 2 is a block diagram showing an example of the configuration of a base station according to one embodiment; FIG. 1 is a block diagram showing an example of a configuration of a terminal according to one embodiment; FIG. FIG. 10 is a diagram showing an example of determination method 1; FIG. 4 is a diagram illustrating an example of repeated transmission of TBoMS; FIG. 10 is a diagram showing an example of bit selection in selection method 1 of transmission method 2; FIG. 10 is a diagram showing an example of bit selection in selection method 1 of transmission method 2; FIG. 4 is a diagram showing an example of the relationship between RV ids and TBoMS transmission opportunities; FIG. 11 is a diagram showing an example of bit selection in transmission method 3; FIG. 11 is a diagram showing an example of bit selection in transmission method 3; It is a figure which shows an example of the hardware configuration of the base station and terminal which concern on one Embodiment.

<Knowledge leading to this disclosure>
For example, in 3GPP Release-17, it is agreed to study coverage enhancement (CE: Coverage Enhancement) in NR (Non-Patent Document 1).

Also, regarding coverage extension, physical uplink shared channels allocated to multiple slots, specifically, TB processing over multi-slot PUSCH (PUSCH (Physical Uplink Shared Channel) for processing transport blocks (TB) via PUSCH (Physical Uplink Shared Channel) It has been agreed to study a method for determining time resources for TBoMS (Non-Patent Document 2).

TBoMS can be interpreted as a technique for transmitting one transport block using multiple slots.

Fig. 1 is a diagram showing an example of PUSCH allocation by TBoMS. Specifically, FIG. 1 shows an example of PUSCH allocation by TBoMS according to Type A repetition like TDRA (Time Domain Resource Allocation) and Type B repetition like TDRA. Note that Type A, B may mean Repetition type A, B.

　TBoMS can have the following advantages.

- Since resources are allocated across multiple slots, the coding rate (code rate) decreases.
• The gain of channel coding is improved by lengthening the code sequence.
・Compared to the case of transmitting multiple TB, the amount of upper layer headers can be reduced.

Also, in 3GPP Release-15, etc., when determining the size of TB (TBS) transmitted via PUSCH (PDSCH as well), first the number of REs (N _RE ) is calculated, and then The number of information bits (N _info ) is calculated using the N _REs . TBS is then determined based on the calculated N _info . Here, determination of TBS is based on the assumption that PUSCH is allocated to one slot.

However, in the case of TBoMS, it is desirable to determine the TBS corresponding to PUSCH allocated across multiple slots (which may be consecutive). For example, by determining the appropriate TBS, it is possible to achieve the specified target code rate even when transmitting TBoMS. In other words, by determining the appropriate TBS, the actual code rate during TBoMS transmission can be brought closer to the specified target code rate. Also, by determining an appropriate TBS, the efficiency of coverage extension by TBoMS can be improved.

Therefore, in the present embodiment, as an example, determination of a TBS corresponding to TBoMS using PUSCH allocated across multiple slots will be described.

<Example of wireless communication system>
FIG. 2 is a diagram showing an example of the radio communication system 10 according to the embodiment. The radio communication system 10 may be a radio communication system according to New Radio (NR). The radio communication system 10 includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN 20) and a terminal 200.

Note that the wireless communication system 10 may be a wireless communication system conforming to a scheme called 5G, Beyond 5G, 5G Evolution, or 6G.

NG-RAN 20 includes base stations 100 (base station 100A and base station 100B). Note that the number of base stations 100 and the number of terminals 200 are not limited to the example shown in FIG.

The NG-RAN 20 includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that the NG-RAN 20 and 5GC may simply be referred to as a "network".

The base station 100 may also be called an NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). Terminal 200 may be called User Equipment (UE). Also, base station 100 may be regarded as a device included in a network to which terminal 200 connects.

The base station 100 performs wireless communication with the terminal 200. For example, the wireless communication performed complies with NR. At least one of the base station 100 and the terminal 200 uses Massive MIMO (Multiple-Input Multiple-Output) to generate beams (BM) with higher directivity by controlling radio signals transmitted from a plurality of antenna elements. You can respond. Also, at least one of base station 100 and terminal 200 may support carrier aggregation (CA) in which multiple component carriers (CC) are bundled and used. Also, at least one of the base station 100 and the terminal 200 may support dual connectivity (DC), etc., in which communication is performed between the terminal 200 and each of the plurality of base stations 100 .

The wireless communication system 10 may support multiple frequency bands. For example, wireless communication system 10 supports Frequency Ranges (FR) 1 and FR2. The frequency bands of each FR are, for example, as follows.
・FR1: 410MHz to 7.125GHz
・FR2: 24.25GHz to 52.6GHz

In FR1, Sub-Carrier Spacing (SCS) of 15 kHz, 30 kHz or 60 kHz may be used, and a bandwidth (BW) of 5 MHz to 100 MHz may be used. FR2 is, for example, a higher frequency than FR1. FR2 may use an SCS of 60 kHz or 120 kHz and a bandwidth (BW) of 50 MHz to 400 MHz. Also, FR2 may include a 240 kHz SCS.

The wireless communication system 10 according to the present embodiment may support a frequency band higher than the FR2 frequency band. For example, the wireless communication system 10 in this embodiment can support frequency bands exceeding 52.6 GHz and up to 114.25 GHz.

Also, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) than the above example is applied. may Also, DFT-S-OFDM may be applied to both uplink and downlink, or may be applied to either one.

The wireless communication system may support CE (Coverage Enhancement) that expands the coverage of the cells (or physical channels) formed by the base station 100 . Coverage enhancement may provide mechanisms for increasing the success rate of reception of various physical channels.

For example, the base station 100 supports repeated transmission of downlink signals (for example, signals using PDSCH (Physical Downlink Shared Channel)). For example, terminal 200 supports repeated transmission of an uplink signal (eg, PUSCH (Physical Uplink Shared Channel)).

In a wireless communication system, a time division duplex (TDD) slot configuration pattern may be set. For example, DDDSU (D: downlink (DL) symbol, S: DL/uplink (UL) or guard symbol, U: UL symbol) may be specified (see 3GPP TS38.101-4).

Also, in a wireless communication system, channel estimation of PUSCH (or PUCCH (Physical Uplink Control Channel)) can be performed using a demodulation reference signal (DMRS) for each slot. can be used to perform channel estimation for PUSCH (or PUCCH). Such channel estimation may be called joint channel estimation. Alternatively, it may be called by another name such as cross-slot channel estimation.

Terminal 200 may transmit DMRS assigned to (spanning over) multiple slots so that base station 100 can perform joint channel estimation using DMRS.

Also, in a wireless communication system, TB processing over multi-slot PUSCH (TBoMS), which processes transport blocks (TB) via PUSCHs assigned to multiple slots, may be applied for coverage extension.

In TBoMS, the number of allocated symbols can be the same in each slot, as in Time Domain Resource Allocation (TDRA) for PUSCH Repetition type A, or as in TDRA for PUSCH Repetition type B (details below). Additionally, the number of symbols assigned to each slot may be different.

TDRA may be interpreted as resource allocation in the PUSCH time domain specified in 3GPP TS38.214. The PUSCH TDRA may be interpreted as defined by a radio resource control layer (RRC) information element (IE), specifically PDSCH-Config or PDSCH-ConfigCommon.

　TDRA may also be interpreted as resource allocation in the time domain of PUSCH specified by Downlink Control Information (DCI).

The configurations of base station 100 and terminal 200 described below are examples of functions related to the present embodiment. Base station 100 and terminal 200 may have functions not shown. Also, the functional division and/or the name of the functional unit are not limited as long as the function executes the operation according to the present embodiment.

<Configuration of base station>
FIG. 3 is a block diagram showing an example of the configuration of base station 100 according to this embodiment. Base station 100 includes, for example, transmitter 101 , receiver 102 , and controller 103 . Base station 100 wirelessly communicates with terminal 200 (see FIG. 4).

The transmission section 101 transmits a downlink (DL) signal to the terminal 200 . For example, the transmitter 101 transmits a DL signal under the control of the controller 103 .

A DL signal may include, for example, a downlink data signal and control information (eg, Downlink Control Information (DCI)). Also, the DL signal may include information (for example, UL grant) indicating scheduling regarding signal transmission of terminal 200 . Also, the DL signal may include higher layer control information (for example, Radio Resource Control control information). Also, the DL signal may include a reference signal.

Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, base station 100 transmits control information to terminal 200 using PDCCH, and transmits downlink data signals using PDSCH.

Examples of reference signals included in DL signals include demodulation reference signals (DMRS), phase tracking reference signals (PTRS), channel state information-reference signals (CSI-RS), sounding reference signals (SRS ), and Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulation of downlink data signals and transmitted using PDSCH.

The receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 200. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

The control unit 103 controls the communication operation of the base station 100, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102.

For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101 . Control section 103 also outputs the data received from receiving section 102, control information, and the like to an upper layer.

For example, when the control unit 103 determines that the terminal 200 applies TBoMS, the control unit 103 controls transmission of control information regarding TBoMS application to the terminal 200 .

For example, when the terminal 200 transmits an uplink signal to which TBoMS is applied, the control section 103 controls reception of the uplink signal to which TBoMS is applied. For example, the control unit 103 receives PUSCH signals of a plurality of slots and configures a transport block.

<Device configuration>
FIG. 4 is a block diagram showing an example of the configuration of terminal 200 according to this embodiment. Terminal 200 includes, for example, receiver 201 , transmitter 202 , and controller 203 . The terminal 200 wirelessly communicates with the base station 100, for example.

The receiving unit 201 receives the DL signal transmitted from the base station 100. For example, the receiver 201 receives a DL signal under the control of the controller 203 .

The transmission unit 202 transmits the UL signal to the base station 100. For example, the transmitter 202 transmits UL signals under the control of the controller 203 .

The UL signal may include, for example, an uplink data signal and control information. For example, information about the processing capability of terminal 200 (eg, UE capability) may be included. Also, the UL signal may include a reference signal.

Channels used to transmit UL signals include, for example, data channels and control channels. For example, the data channel includes PUSCH (Physical Uplink Shared Channel), and the control channel includes PUCCH (Physical Uplink Control Channel). For example, terminal 200 receives control information from base station 100 using PUCCH, and transmits uplink data signals using PUSCH.

The reference signal included in the UL signal may include at least one of DMRS, PTRS, CSI-RS, SRS, and PRS, for example. For example, reference signals such as DMRS and PTRS are used for demodulation of uplink data signals and transmitted using PUSCH.

The control unit 203 controls communication operations of the terminal 200, including reception processing in the reception unit 201 and transmission processing in the transmission unit 202.

For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202 . Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

For example, when the terminal 200 applies TBoMS, the control unit 203 controls transmission of uplink signals to which TBoMS is applied. In this case, the control unit 203 may control signal transmission to which TBoMS is applied based on control information acquired from the base station 100 . For example, the control unit 203 determines a transport block size (TBS) to be transmitted in TBoMS, and controls transmission of a TB having the determined TBS using PUSCH of a plurality of slots.

Note that the channels used for DL signal transmission and the channels used for UL signal transmission are not limited to the above examples. For example, the channel used for DL signal transmission and the channel used for UL signal transmission may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). RACH may be used, for example, to transmit Downlink Control Information (DCI) containing Random Access Radio Network Temporary Identifier (RA-RNTI).

<Regarding the decision of TBS>
Determination of a TBS corresponding to a TB spanning multiple slots will be described below. For example, for determination of TBS, at least one of the following three TBS calculation methods may be applied.

<TBS calculation method 1>
When calculating the number of REs (N _RE ), we expand to the number of REs in multiple slots rather than in one slot.
For example, N _RE (N′ _RE ) may be calculated as in Equation (1) below.

In formula (1), N ^RB _SC indicates the number of subcarriers per resource block, N ^sh _symb indicates the number of symbols in slot units, and N ^PRB _DMRS indicates the number used for DMRS in slot units. , N ^PRB _oh indicate the number of overheads. Here, each variable may be changed to the number of REs spanning multiple slots.

For example, in this case N ^PRB _oh in equation (1) may be calculated by either:

・(Opt 1): Set the same N ^PRB _oh for all slots ・(Opt 1-1): Assign xOverhead set by PDSCH-ServingCellConfig to each slot ・(Opt 1-2): xOverhead set by PDSCH-ServingCellConfig is divided by the number of slots to which TBoMS is applied and set as N ^PRB _oh in each slot. In this case, the quotient may be rounded to an integer by ceil or floor.
・(Opt 1-3): Add a new parameter, and when using TBoMS, determine N ^PRB _oh based on this parameter ・(Opt 1-4): Add a new parameter, and when using TBoMS, this parameter and xOverhead (Opt 2): ^{Set N PRB} ^oh _based on the number of slot symbols where _TBoMS is applied (Opt 2-1): Multiply xOverhead by the number of slots to which resources are allocated (Type A repetition like TDRA)
・(Opt 2-2): Multiply the number of repeated transmissions (number of repetitions) by xOverhead (Type B repetition like TDRA)
• (Opt 2-2-1): Multiply the number of actual repetitions.
In this case, the number of undivided actual repetitions may be multiplied.
・(Opt 2-2-2): Multiply the nominal repetition number.
・(Opt 2-3): Calculated according to SLIV of TDRA and number of symbols to be allocated, total number of symbols to be allocated and xOverhead For example, calculated by (xOverhead) × (total number of symbols) / (SLIV of TDRA and number of symbols to be allocated) may be

Also, in Opts 2-1, 2-2, 2-3, different parameters set by PDSCH-ServingCellConfig may be used instead of xOverhead. For example, N ^PRB _oh may be calculated based on the added parameter and xOverhead, both slot symbol numbers. In this case, different parameters may be set when TBoMS is applied and when not applied.

Also, regarding the calculation of N ^sh _symb (N ^PRB _DMRS ) in equation (1), either of the following may be applied.

(Alt 1): Change to the number of symbols (RE) of all resources to which resources are allocated In this case, the number of symbols (RE) may be calculated in consideration of the TDD pattern, SFI, and CI.
・(Alt 2): Multiply the number of slots allocated for resources (Type A repetition like TDRA)
・(Alt 3): Multiply the number of repetitions (Type B repetition like TDRA)
• (Opt 1): Multiply the actual repetition number.
In this case, the number of undivided actual repetitions may be multiplied.
• (Opt 2): Multiply the nominal repetition number.

<TBS calculation method 2>
Calculate N _RE based on SLIV of TDRA, and calculate N _info according to TDRA. As for calculation method 2, any of the following methods may be applied.

(Alt 1): In the case of Type A repetition like TDRA, calculate N _RE for one slot, and multiply the number of repetitions when calculating N _info . In this case, the number of slots may be calculated taking into account the slots to be dropped (multiplied by the number of slots available for allocation). If there is a TDD pattern, SFI (Slot Format Indication) / CI (Cancel Indication), etc., it may be changed from the value notified by the TBS that transmits or receives.

(Alt 2): In the case of Type B repetition like TDRA, calculate N _RE for one repetition, and multiply the number of repetitions when calculating N _info . Here, the following two Options may be applied.

· (Opt 1): Multiply the number of actual repetitions. In this case, the number of actual repetitions without segmentation may be multiplied.

· (Opt 2): Multiply the number of nominal repetitions.

Note that the actual repetition is the repetition to be finally transmitted, and the nominal repetition may be interpreted as the repetition notified/assigned to the terminal by the base station. For example, the following factors can change actual repetition and nominal repetition:

(i) If the nominal repetition is not placed in the UL symbol, the nominal repetition may be excluded.

(ii) If a nominal repetition is placed on a slot boundary, the nominal repetition may be split at the slot boundary and turned into two actual repetitions.

<TBS calculation method 3>
Add the given parameters. For example, the parameter may be notified using DCI and/or higher layer signaling.

For example, a predetermined parameter (K) may be added when calculating the value of N _info , as shown in Equation (2) below. For example, K may be a value (scaling factor) that multiplies the N _info value by K, but is not necessarily limited to this purpose. A scaling factor may also be referred to as a scaling value.

In equation (2), N _RE indicates the number of REs, R indicates the coding rate, Qm indicates the modulation level, and v indicates the number of MIMO layers. For example, the right-hand side of equation (2) indicates that the size of the TB to be transmitted in the PUSCH of one slot is multiplied by the scaling factor K. In other words, in equation (2), the TBS of the TBoMS transmission is calculated by multiplying the size of the TB to be transmitted in the PUSCH of one slot by the scaling factor K.

For example, in the example of Equation (2), a scaling factor may be added in calculating N _info , but the present disclosure is not limited to this. For example, a scaling factor may be applied to the number of REs allocated within one slot. For example, the number of REs allocated in one slot may be multiplied by K times by a scaling factor. A scaling factor may also be applied to the quantized intermediate variables. For example, the quantized intermediate variable _Ninfo' may be multiplied K times by a scaling factor.

The scaling factor K may be an integer greater than 1. A method of determining the scaling factor will be described below. Note that determination of the scaling factor may be understood as an example of determination of the TBS.

The scaling factor may be determined, for example, based on at least one of the following determination methods.

In determination method 1, the scaling factor is determined based on at least one of the number of slots assigned to the TBoMS and the number of slots that can be assigned by the TBoMS.

In decision method 2, the scaling factor is decided based on RRC and/or MAC CE.

In determination method 3, the scaling factor is determined based on DCI.

In determination method 4, the scaling factor is determined based on the notified information and the number of allocated slots.

In decision method 5, the method to be applied among the above decision methods 1 to 4 is set by control information (eg, RRC).

In determination method 6, terminal capability information (eg, UE capability) regarding the applicability of determination methods 1 to 5 above is notified.

Next, each of the determination methods 1 to 6 described above will be specifically described.

(Determination method 1: Determined from the number of TBoMS slots)
For example, the terminal determines the scaling factor based on at least one of the number of allocated slots for the TBoMS and the number of slots that can be allocated by the TBoMS. For example, the scaling factors are determined based on the following method examples 1-1 to 1-4.

(Method example 1-1)
The terminal determines the number designated for the TBoMS allocation slots indicated by each row index in the TDRA list set by RRC as the scaling factor. Note that the "number of designated slots for TBoMS assignment" may correspond to "the number of (candidate) slots to which the TBoMS is assigned". The “specified number of allocated slots for TBoMS” may correspond to the number of slots configured (specified) by control information (eg, RRC and/or DCI).

In addition, in example 1-1, the number of repetitions (number of repetitions) indicated in the TDRA list may be determined as the number specified for the allocated slots of TBoMS. In other words, the number of repetitions indicated in the TDRA list may be used (or reused) for the number of slots assigned to the TBoMS. In this case, the terminal may determine which of TBoMS and repetition should be applied to perform signal transmission based on information related to communication control. For example, information related to communication control may be set by at least one of RRC, MAC CE, DCI, and UE capability. In this case, the terminal may perform scaling using the scaling factor for TBS determination when applying TBoMS. In this case, the terminal does not need to perform scaling using the scaling factor when TBoMS is not applied (for example, when repetition is applied).

(Method example 1-2)
It is determined that the number of slots to which TBoMS can be allocated, which is determined based on the RRC configuration and/or DCI information for allocating TBoMS, is the scaling factor. The number of slots that can be assigned to TBoMS is the number of slots that cannot be assigned to TBoMS due to overlap with the number of slots specified for TBoMS assignment (the number of slots set by control information) and other resources. and may be determined based on For example, "the number of slots to which TBoMS can be allocated" is a number equal to or less than the number designated as the allocation slots of TBoMS (the number of slots set by control information). The “number of slots to which TBoMS can be allocated” may be the number obtained by subtracting the number of slots that cannot be allocated to TBoMS due to overlapping with other resources, etc. from the number designated as slots to be allocated to TBoMS. For example, if the number of slots allocated for TBoMS is set to be 4 by DCI, and one of the four slots set is designated as DL, the number of slots to which TBoMS can be allocated is , 3.

For example, TDD-UL-DL-Configcommon, TDD-UL-DL-ConfigurationDedicated, etc. The number of slots in which the SRS and PUSCH resources triggered by the same DCI as the DCI that allocates the downlink symbol and/or PUSCH in the TDD pattern does not overlap , is the scaling factor.

(Method example 1-3)
The number of slots to which TBoMS can be assigned, determined based on signals received prior to DCI for assigning TBoMS, is determined to be the scaling factor. For example, signals received before DCI may consider RRC, UL CI (Cancel Indication), and dynamic SFI (Slot Format Indication) in DCI format 2-0.

(Method example 1-4)
The scaling factor is determined to be the number of slots to which the TBoMS can be assigned, determined based on signals received prior to the first slot to transmit the TBoMS. For example, signals received before the first slot to transmit TBoMS may consider RRC, UL CI, and dynamic SFI in DCI format 2-0.

Using FIG. 5 as an example, method example 1-3 and method example 1-4 will be described.

FIG. 5 is a diagram showing an example of determination method 1. FIG. In the example of FIG. 5, slot #1 to slot #6 are shown, DCI is transmitted in slot #1, and TBoMS transmission is performed in slots #3 to slot #6. The DCI for slot #1 contains information to allocate TBoMS. In other words, DCI in slot #1 allocates TBoMS. Also, in the example of FIG. 5, the first slot for transmitting TBoMS is slot #3.

In method example 1-3, the DCI for assigning TBoMS is the DCI for slot #1, so the number of slots to which TBoMS can be assigned is determined based on the signal received before the DCI for slot #1. . The determined number of allocatable slots is then determined to be the scaling factor.

In method example 1-4, the slot in which TBoMS is first transmitted is slot #3, so the number of slots to which TBoMS can be assigned is determined based on the signals received before slot #3. The determined number of allocatable slots is then determined to be the scaling factor.

In Examples 1-1 to 1-4 of the method described above, the number of slots designated for TBoMS allocation or the number of slots to which TBoMS can be allocated is the scaling factor. Not limited. It may be determined that the scaling factor is a value obtained by a predetermined process based on the number of assigned slots for the TBoMS or the number of slots to which the TBoMS can be assigned. For example, the scaling factor may be the number of assigned slots for the TBoMS or the number of slots to which the TBoMS can be assigned divided by X. In this case, X may be set according to a predetermined rule or may be set by RRC.

Also, in Examples 1-2 to 1-4 of the methods described above, scheduling signals for other carriers may be considered. For example, a scheduling signal for CA (Carrier Aggregation) may be considered.

(Decision method 2: Determined based on RRC and/or MAC CE)
For example, the terminal determines the scaling factor based on RRC settings and/or MAC (Media Access Control) CE (Control element).

(Method example 2-1: Decision based on RRC setting)
For example, a parameter for setting the scaling factor may be added to the PUSCH-Config IE of RRC. The terminal may determine the scaling factor based on parameters added to the RRC PUSCH-Config IE. In this case, the scaling factor determined based on the RRC settings may be set according to the number of designated slots for TBoMS allocation and/or the number of slots to which TBoMS can be allocated. For example, a scaling factor may be set when the number of slots assigned to the TBoMS is "1" and when the number of slots assigned to the TBoMS is "2". For example, a parameter added to the PUSCH-Config IE of RRC may be set according to the number of allocated slots of TBoMS. For example, the number assigned to the TBoMS allocation slots may be associated with a scaling factor or a parameter that sets the scaling factor.

(Method example 2-2: Decision based on MAC CE)
For example, it may be determined that the MAC CE specified parameter is the scaling factor used to determine the TBS. In other words, a scaling factor specified in MAC CE may be applied.

Also, the scaling factor specified by MAC CE may be set according to the number specified for TBoMS allocation slots. For example, the MAC CE may specify a scaling factor that is set according to the number of slots assigned to TBoMS. For example, the number assigned to the TBoMS allocation slots may be associated with a scaling factor or a parameter that sets the scaling factor.

The scaling factor set by RRC may be activated or deactivated by MAC CE. In other words, whether to use the scaling factor set by RRC may be set by MAC CE. Alternatively, scaling factor candidates may be configured by RRC, and scaling factors to be applied among the candidates may be configured by MAC CE. In this case, the scaling factor set by RRC and activated or deactivated by MAC CE may be set according to the number of allocated slots of TBoMS.

(Decision method 3: Determined based on DCI)
For example, the terminal determines the scaling factor based on DCI. For example, the scaling factor may be signaled by a field (eg, bit field) storing information included in the DCI.

(Method example 3-1: Determined based on FDRA bit field)
For example, the scaling factor may be notified by an FDRA (Frequency Domain Resource Allocation) bit field. One or more bits of the FDRA field may be used to signal scaling factors. In this case, the number of RBs for transmitting TBoMS may be limited. Bits used for reporting scaling factors may be reserved by limiting RBs. Also, in frequency allocation, only Uplink resource allocation type 1 or/and 2 may be applicable.

(Method example 3-2: Determined based on TDRA bit field)
For example, the TDRA bit field may signal the scaling factor. A scaling factor corresponding to each row index in the TDRA list may be set according to a predetermined rule and/or RRC setting. Then the scaling factor set to the row index specified by the TDRA field may be used. For example, a scaling factor may be set in PUSCH-Allocation of the PUSCH-TimeDomainResourceAllocation IE. In the TDRA bit field, a scaling factor may be set apart from the number specified for the TBoMS allocation slots.

(Method example 3-3: Determined based on MCS bit field)
For example, the scaling factor may be notified based on the MCS (Modulation and Coding Scheme) bit field. For example, one or more bits of the MCS bit field may indicate the MCS and the remaining one or more bits may indicate the scaling factor. For example, the upper one or more bits of the MCS bit field may indicate the MCS, and the remaining lower one or more bits may indicate the scaling factor. For example, the lower one or more bits of the MCS bit field may indicate the MCS, and the upper remaining one or more bits may indicate the scaling factor. For example, the upper (or lower) 3 bits of the MCS bit field may be used for MCS notification, and the lower (or upper) 2 bits may be used for scaling factor notification.

　In addition, if the scaling factor is notified based on the MCS bit field, the MCS that can be selected in TBoMS transmission may be restricted. Bits used for signaling the scaling factor may be reserved by limiting the selectable MCS.

For example, an MCS index with a low index (for example, a low spectral efficiency) may be selectable in a default MCS table that shows the relationship between multiple MCSs and indexes associated with each MCS. In this case, the MCS index with a high index (eg, high spectral efficiency) may be restricted. For example, if 3 bits are used for MCS notification, 8 MCS indices with low indices may be selectable.

However, it is not limited to an example in which a low MCS index (for example, low spectral efficiency) can be selected. For example, a high MCS index (eg, high spectral efficiency) may be selectable, and a low MCS index (eg, low spectral efficiency) may be restricted. Alternatively, in the MCS table, the MCS index with a low index or the MCS index with a high index is not limited to being selectable. may be restricted. Alternatively, in the MCS table, selectable MCS indexes and restrictive MCS indexes may be arranged randomly, or selectable MCS indexes or restrictive MCS indexes may be arranged at regular intervals (for example, alternately). The selectable MCS index and the limiting MCS index may be fixed, statically or dynamically changed.

Note that the above-mentioned default MCS table may be regarded as an MCS table used when no scaling factor is notified, or as an MCS table used when TBoMS transmission is not performed, for example.

　The default MCS table is not limited to an example in which selectable MCS indexes and restricted MCS indexes are set. For example, an MCS table for TBoMS transmission may be set, and the MCS table for TBoMS transmission may be referenced in the TBoMS transmission. In other words, the MCS table when TBoMS transmission is performed may be distinguished from the MCS table when TBoMS is not performed (or when the scaling factor is not notified).

In the above, an example in which the scaling factor is notified by the FDRA bit field, TDRA bit field, or MCS bit field of DCI is shown, but in DCI, the scaling factor is notified by a bit field different from these bit fields. may Also, in the above description, an example in which the scaling factor is notified by one bid field is shown, but the scaling factor may be notified by a plurality of bit fields. For example, a scaling factor may be signaled by a combination of bits in each of multiple bit fields.

(Method Example 3-4: Variation)
Also, in the above example, the scaling factor is notified by the FDRA bit field, TDRA bit field, or MCS bit field specified in DCI, but the bit field for notifying the scaling factor is specified in DCI. may be The scaling factor may be notified by a bit field for notifying the scaling factor (a bit field dedicated to the scaling factor).

The number of bits and the number of bit fields used for notifying the scaling factors described above are examples, and the present disclosure is not limited thereto. For example, the number of bits and the number of bit fields may be fixed, dynamically or statically set. For example, this setting may be performed by higher layer control information.

(Decision method 4: Determined based on the notified information and the number of allocated slots)
For example, the terminal determines the scaling factor based on the notified information and/or the number of allocated slots.

For example, in determining the scaling factor, the terminal may determine the scaling factor by combining the number of slots to be assigned by PUSCH and information set by RRC and/or information notified by DCI.

For example, the number of slots assigned to PUSCH is not particularly limited. The number of slots to allocate for PUSCH may correspond to "the number of slots to which TBoMS can be allocated" indicated by the determination method 1 described above, or to the "number of designated slots for allocation of TBoMS". For example, the number of slots allocated for PUSCH corresponds to the number of slots determined by at least one of the examples 1-1 to 1-4 of the determination method 1 described above.

Also, the information set by RRC is not particularly limited. The information set by RRC may correspond to the information indicated in determination method 2 above.

In addition, the information notified by DCI is not particularly limited. The information notified by DCI may correspond to the information indicated in determination method 3 described above.

For example, the scaling factor is determined by adding (or subtracting) the notified information (eg, value) to the number of slots allocated by PUSCH. Alternatively, the scaling factor may be determined by dividing (or multiplying) the number of slots to allocate for PUSCH with the signaled information (eg, value).

For example, a case where DCI notifies information about scaling factors (for example, scaling factor index) will be described. The following table shows an example of the relationship between information about scaling factors and reference values for the scaling factors.

For example, when information about the scaling factor (e.g., scaling factor index) is notified by the DCI, the terminal refers to Table 1 to determine the scaling reference value (scaling reference value), and the number of slots to allocate for PUSCH and scaling A scaling reference value may be added to determine the scaling factor.

For example, if TBoMS is allocated across 4 slots, the number of slots allocated for PUSCH is 4. Then, when the scaling factor index is 1, referring to Table 1, the scaling reference value is '0' and the scaling factor K is K=4+0. Similarly, when the scaling factor index is 2, referring to Table 1, the scaling reference value is "-1" and the scaling factor K is K = 4 + (-1) = 3. .

(Determination method 5: RRC setting for scaling factor)
For example, in the terminal, among the determination methods 1 to 4 described above, the method applied to determine the scaling factor is set by a predetermined rule and/or RRC. In determination method 5, the terminal determines a method to be applied among determination methods 1 to 4, and determines a scaling factor using the determined method.

(Method example 5-1: Determined according to UE capability)
For example, the method applied to determine the scaling factor may be determined based on the UE capabilities. For example, a terminal reports information indicating a determination method supported by the terminal (for example, a determination method usable by the terminal) using UE capability. If the terminal supports determination method 3, the terminal reports information indicating support for determination method 3 by UE capability. Then, the terminal receives notification of the scaling factor based on the determination method 3 and determines the scaling factor. In this case, a terminal that does not support determination method 3 may determine the scaling factor based on

determination method

1 or 2. Note that a terminal that supports a determination method other than determination method 3 may report information indicating the supported determination method (for example, determination methods 1 and/or 2) using the UE capability.

(Method example 5-2: Determined according to RRC settings)
For example, the method applied to determine the scaling factor may be determined based on RRC configuration. For example, in the PUSCH-Config IE, information (eg, parameters) regarding scaling factors may be configured. Information (eg, parameters) about the scaling factor may indicate at least one of determination methods 1-3. For example, the terminal may identify the determination method to use based on the information about the scaling factor, and determine the scaling factor based on the determined determination method.

(Method Example 5-3: Combination)
For example, the method examples 5-1 and 5-2 described above may be combined. For example, a terminal reports information indicating one or more determination methods supported by the terminal using UE capabilities. The base station that received the report identifies the determination method to be used from one or more determination methods indicated by the UE capability, and configures RRC based on the determined determination method (e.g., notification of information on the scaling factor). I do. Based on the RRC configuration, the terminal may identify a determination method to use from among one or more determination methods supported by the terminal, and determine the scaling factor based on the determined determination method.

(Determination method 6: Notification of UE capability)
A terminal may report information about the TBS determination of TBoMS by UE capability. For example, the information reported by UE capability may be information indicating the terminal's capability for TBS determination in TBoMS.

For example, the terminal may report information related to determination methods 1 to 5 described above by UE capability.

For example, information indicating whether or not the terminal is applicable to at least one of determination methods 1 to 5 described above may be reported by UE capability. In addition, information indicating whether or not at least one of the examples of each method shown in determination method 1 to determination method 5 described above is applicable may be reported by the UE capability. For example, the applicability of each example of determination methods 1 to 5 may be reported, or the applicability of multiple methods (or examples of methods) may be collectively reported. .

Also, the terminal may report the maximum value of the scaling factor by UE capability. For example, the maximum scaling factor value may be the maximum scaling factor value supported by the terminal or the maximum scaling factor value usable by the terminal.

In addition, the terminal may report information about the frequencies supported by the terminal through UE capability. The reporting method is not particularly limited. For example, the terminal may collectively report whether each frequency is compatible. In other words, the terminal may report whether or not it is compatible as a terminal. Alternatively, the terminal may individually report whether it is compatible with each frequency. As an example, the terminal may individually report whether or not it can handle FR1 and FR2. For example, the terminal may report information indicating that FR1 is capable of supporting and FR2 is not capable of supporting through UE capability. Also, the terminal may report whether it can handle each SCS.

Note that the terminal may report whether or not it supports frequencies different from FR1 and FR2. Also, at least one of FR1 and FR2 may be subdivided, and whether or not the terminal is compatible may be reported for each subdivided. For example, if FR2 is subdivided into sub-labeled frequencies such as FR2-1 and FR2-2, even if the device's compatibility with each subdivided FR2-1 and FR2-2 is reported, good.

In addition, the terminal may report information about the duplexing scheme (for example, TDD and/or FDD) that the terminal supports by UE capability. For example, the terminal may collectively report whether or not it supports each of the duplex modes.

As described above, in the present embodiment, the scaling factor used to determine the TBS in TBoMS can be determined to be an appropriate value, so the TB in TBoMS can be determined to have an appropriate size. In addition, since the TB in TBoMS can be determined to be an appropriate size, resource utilization efficiency can be improved.

It should be noted that the determination of the TBS in the TBoMS transmission described above (eg, determination of the scaling factor) is not limited to the example applied to the determination of the TBS in one TBoMS transmission. For example, it may be applied to TBS determination in repeated transmissions of TBoMS. In other words, TBoMS and repeated transmission may be combined as a method of transmitting one TB.

Below, we will explain the repeated transmission of TBoMS.

(Transmission method 1)
For example, the terminal may repeatedly transmit TBoMS. Repeated transmissions of TBoMS may be referred to as "TBoMS with repetitions," for example.

FIG. 6 is a diagram showing an example of repeated transmission of TBoMS. FIG. 6 shows an example of two repeated transmissions of TBoMS in six slots from slot #1 to slot #6. For example, in slot #1 to slot #3 in FIG. 6, one TBoMS transmission (single TBoMS) is performed. Also, one TBoMS transmission is performed in slot #4 to slot #6. In FIG. 6, a TBoMS block in one slot is indicated as a TBoMS unit. TBoMS unit #1 and TBoMS unit #2 indicate different TBoMS transmissions. Note that each TBoMS unit #1 of slot #1 to slot #3 may correspond to different information (for example, sequence). Also, each TBoMS unit #2 of slot #4 to slot #6 may correspond to different information (for example, sequence).

A terminal may repeatedly transmit TBoMS using multiple slots. For example, the terminal may determine whether or not to repeatedly transmit TBoMS according to the following conditions.

(Condition 1)
The terminal supports repeated transmission of TBoMS.

(Condition 2)
Repeated transmission of TBoMS is enabled by RRC settings. Note that this RRC setting may be set by parameters of the PUSCH-Config IE, for example. For example, application of TBoMS, application of repeated transmission, and application of repeated transmission of TBoMS may each be set (designated) by setting RRC.

(Condition 3)
A row index is specified in which both the number of repetitions of the TDRA list and the number of slots assigned to the TBoMS are set. Designation of the row index of the TDRA list is performed by DCI, for example.

(Condition 4)
The number of repetitions is set by RRC, and the row index set to the number of slots allocated for TBoMS in the TDRA list is specified. Designation of the row index of the TDRA list is performed by DCI, for example. Note that the number of repetitions of the TDRA list may not be set for the row index specified here.

(Condition 5)
Both the number of repetitions and the number of allocated slots of TBoMS are set by RRC.

The terminal may decide to repeatedly transmit TBoMS when one of the conditions 1 to 5 described above is satisfied. Alternatively, the terminal may decide to repeatedly transmit TBoMS when two or more of conditions 1 to 5 are satisfied.

(Transmission method 2: Bit selection method 1 for repeated transmission of TBoMS)
The terminal may perform continuous bit selection in bit selection for repeated transmission of TBoMS. For example, the starting point of bit selection may be determined such that the LDPC-encoded bit sequence is continuously bit-selected.

(Selection method 1)
For example, the starting position of bit selection in a certain slot #n may be the position of the bit next to the last bit of bit selection in a slot before slot #n in which PUSCH is transmitted.

7A and 7B are diagrams showing an example of bit selection in selection method 1 of transmission method 2. FIG. Similar to FIG. 6, FIGS. 7A and 7B show an example of two repeated TBoMS transmissions performed in slot #1 to slot #6. 7A and 7B show the relationship between the bits transmitted in each slot and the bit positions in the circular buffer. Note that the circular buffer may store a bit sequence corresponding to one TB.

Note that the example of FIG. 7A shows bit selection when rate matching is performed on a slot-by-slot basis, and the example of FIG. ) shows an example of bit selection.

For example, in FIGS. 7A and 7B, the starting position of bit selection for slot #4 is earlier than slot #4 and is the last position of bit selection in slot #3 where PUSCH is transmitted (TBoMS transmission is performed). The position of the bit following the bit.

(Selection method 2)
For example, the start positions may be determined so that the start positions of bit selection in each repetition transmission (each repetition) are evenly spaced.

For example, the starting position of the first repetition is determined according to the RV (redundancy version). The start positions of repetitions other than the first repetition may be determined based on the sequence length extracted in bit selection of a specific repetition (hereinafter, “specific sequence length”). For example, the bit sequence bit selection start position to be transmitted in the k-th repetition (k is an integer of 2 or more and n or less, n is the number of repetitions, and an integer of 2 or more) is transmitted in the k-1th repetition It may be a position shifted by a specific sequence length from the bit selection start position of the bit sequence. In this case, the bit selection start position is determined at intervals corresponding to a specific sequence length. In this case, the specific repetition may be the first repetition or the repetition for transmitting the transmission bit sequence with the shortest sequence length. Alternatively, the specific repetition in this case may be the repetition of transmitting the transmission bit sequence with the longest sequence length. Also, the specific sequence length may be determined based on sequence lengths extracted in each of a plurality of repetition bit selections. For example, it may be the average, maximum, or minimum sequence length extracted in each of bit selections of a plurality of repetitions.

(Transmission method 3: Bit selection method 2 for repeated transmission of TBoMS)
In TBoMS repeated transmission, the terminal may apply the id of the RV in each TBoMS transmission occasion based on predetermined rules and/or parameters set by RRC.

For example, the terminal may apply the RV id in one TBoMS transmission opportunity.

FIG. 8 is a diagram showing an example of the relationship between RV ids and TBoMS transmission opportunities. FIG. 8 shows an example of each relationship from Option 1 (Opt 1) to Option 4 (Opt 4). Note that examples of the relationship between RV ids and TBoMS transmission opportunities are not limited to these. For example, when Opt 1 in FIG. 8 is applied, each RV id of TBoMS follows in order of 0, 2, 3, 1, 0, 2, . FIG. 9 shows an example in which each RV id of TBoMS is 0 and 2.

9A and 9B are diagrams showing examples of bit selection in transmission method 3. FIG. Similar to FIGS. 7A and 7B, FIGS. 9A and 9B show an example of two repeated TBoMS transmissions performed in slot #1 to slot #6. 9A and 9B show the relationship between the bits transmitted in each slot and the bit positions in the circular buffer. Note that the circular buffer may store a bit sequence corresponding to one TB.

Note that the example of FIG. 9A shows bit selection when rate matching is performed on a slot-by-slot basis, and the example of FIG. ) shows an example of bit selection.

For example, in FIGS. 9A and 9B, for slot #1 to slot #3 corresponding to the first TBoMS repeated transmission, RV id=corresponding to the first TBoMS transmission opportunity (n=0 in FIG. 8) 0 applies. Then, RV id=2 corresponding to the second (n=1 in FIG. 8) TBoMS transmission opportunity is applied to slot #4 to slot #6 corresponding to the second TBoMS repeated transmission.

(Transmission method 4: RRC setting regarding rate matching in repeated transmission of TBoMS)
In repeated transmission of TBoMS, the terminal may determine a method of determining the id of the RV in each transmission occasion of TBoMS based on predetermined rules and/or parameters set by RRC.

For example, the terminal determines which of transmission method 2 and transmission method 3 regarding repeated transmission of TBoMS is to be applied.

(Example 4-1 of how to determine the transmission method: Determined according to UE capability)
For example, the RV id determination method may be determined based on the UE capability. For example, if the terminal supports bit selection indicated by transmission method 2 (eg, continuous bit selection over repetition), the terminal may report information indicating support for bit selection indicated by transmission method 2 using the UE capability. The terminal may then determine the id of the RV based on the bit selection shown in transmission method 2. If the terminal does not support the bit selection shown in transmission method 2, the terminal may apply the bit selection shown in transmission method 3.

(Example 4-2 of how to determine the transmission method: Determined according to RRC settings)
For example, how the RV id is determined may be determined based on the RRC configuration. For example, in the PUSCH-Config IE, information (eg, parameters) regarding how to determine the id of the RV may be set. The information (for example, parameters) on how to determine the id of the RV may indicate at least one of the bit selection shown in transmission method 2 and the method shown in transmission method 3 described above. For example, the terminal may identify the method to use based on information about how to determine the id of the RV, and determine the id of the RV based on the identified method. For example, if the id of the RV used by the method shown in transmission method 3 is set by RRC, the method shown in transmission method 3 is applied, and if the id of the RV is not set by RRC, the method shown in transmission method 2 Bit selection may be applied.

(Example 4-3 of transmission method determination method: combination)
For example, Examples 4-1 and 4-2 described above may be combined. For example, the terminal reports one or more determination methods supported by the terminal through the UE capability. The base station that received the report identifies the determination method to be used from among one or more determination methods indicated in the UE capability, and performs RRC settings based on the determined determination method (for example, regarding the RV id determination method information). Based on the RRC configuration, the terminal may identify the determination method to be used from among one or more determination methods supported by the terminal, and determine the id of the RV based on the determined determination method.

(Transmission method 5: Notification of UE capability)
A terminal may report information about repeated transmission of TBoMS by UE capability. For example, the information reported by UE capability may be information indicating the terminal's capability for repeated transmission of TBoMS.

For example, the terminal may report information related to transmission methods 1 to 5 of the TBoMS repeated transmission described above by UE capability. For example, the following information may be reported by the UE capability.

For example, information indicating whether or not a terminal is applicable to at least one of transmission methods 1 to 4 of repeated TBoMS transmission described above may be reported by UE capability. In addition, information indicating whether or not at least one of the examples of each method shown in TBoMS repeated transmission transmission method 1 to transmission method 4 described above is applicable may be reported by the UE capability. For example, the applicability of each example of TBoMS repeated transmission transmission methods 1 to 4 may be reported, or the applicability of a plurality of methods (or examples of methods) may be summarized, may be reported.

Also, the terminal may report the maximum number of slots to which TBoMS is allocated by the UE capability. For example, the maximum number of slots to allocate TBoMS may be the maximum number of slots to allocate TBoMS supported by the terminal, or the maximum number of slots to allocate TBoMS that the terminal can use.

In addition, when performing repeated transmission of TBoMS, the terminal may report the maximum total number of slots allocated in repeated transmission of TBoMS by UE capability. For example, the maximum total number of slots allocated in repeated transmission of TBoMS may be the maximum total number of slots allocated in repeated transmission of TBoMS supported by the terminal, or the maximum number of slots allocated in repeated transmission of TBoMS supported by the terminal. It may be the maximum total number of slots allocated in repeated transmissions.

Also, when performing TBoMS repeated transmission, the terminal may report the maximum number of repeated transmissions by UE capability. For example, the maximum number of repeat transmissions may be the maximum number of repeat transmissions supported by the terminal, or the maximum number of repeat transmissions available to the terminal.

As described above, in this embodiment, TBoMS can be repeatedly transmitted, so the data transmission efficiency can be improved. In addition, since TBoMS can be repeatedly transmitted, coverage can be extended efficiently.

For example, if the environment in which gain is obtained by TBoMS and the environment in which gain is obtained by repeated transmission are different, in order to obtain each gain efficiently, the number of slots assigned to TBoMS and repetition transmission (repetition ) may be controlled. For example, in environments where the gain provided by TBoMS is relatively large (eg, when the desired data rate is relatively low), the number of iterations may be decreased and the number of assigned slots for TBoMS increased. Also, for example, in an environment where the gain obtained by repeated transmission is relatively large (for example, when the desired data rate is relatively high), the number of repetitions is increased and the number of allocated slots for TBoMS is decreased. good. Through such control, the respective gains of TBoMS and repeated transmission can be obtained efficiently. It should be noted that the adjustment of the number of allocated slots for TBoMS and the number of repetitions may be performed by the base station.

Although the above-described embodiment shows an example in which TBoMS is applied in PUSCH transmission, the present disclosure is not limited to this. TBoMS may be applied in transmission on a channel different from PUSCH. Alternatively, TBoMS may be applied to a combination of multiple channels. With respect to repeated transmission of TBoMS, similarly, repeated transmission of TBoMS may be applied to transmission on a channel different from PUSCH, or repeated transmission of TBoMS may be applied to transmission on a channel different from PUSCH for a combination of a plurality of channels. may be applied.

Also, in the above-described embodiment, an example in which TBoMS is applied to uplink signals has been shown, but TBoMS may be applied to downlink signals, or repeated transmission of TBoMS may be applied.

Also, in the above-described embodiment, "slot" indicates an example of the time unit of radio resources, but the present disclosure is not limited to this. "Slot" may be read as terms such as "minislot", "frame", "subframe", "interval", or "TTI".

Also, in the above-described embodiment, "transport block (TB)" indicates an example of a block unit of information, but the present disclosure is not limited to this. "Transport block" is interchanged with other terms such as "information block", "packet", "codeword", "code block", "sequence", "encoded sequence", or "subsequence". good too.

(Hardware configuration)
It should be noted that the block diagrams used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, examining, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that makes transmission work is called a transmitting unit or transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 10 is a diagram illustrating an example of hardware configurations of a base station and terminals according to an embodiment of the present disclosure. The base station 100 and terminal 200 described above may be physically configured 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, a bus 1007, and the like.

In the following explanation, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of base station 100 and terminal 200 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

Each function of the base station 100 and the terminal 200 is implemented by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002 so that the processor 1001 performs calculations and controls communication by the communication device 1004. , and controlling at least one of reading and writing of data in the memory 1002 and the storage 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, the control unit 103 and the control unit 203 described above may be implemented by the processor 1001 .

Also, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 103 of the base station 100 or the control unit 203 of the terminal 200 may be implemented by a control program stored in the memory 1002 and operating in the processor 1001, and other functional blocks may be implemented in the same way. good. Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

The memory 1002 is a computer-readable recording medium, and is composed of at least one of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be The memory 1002 may also be called a register, cache, main memory (main storage device), or the like. The memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disc, a magneto-optical disc (for example, a compact disc, a digital versatile disc, a Blu-ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like. Storage 1003 may also be called an auxiliary storage device. The storage medium described above may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003 .

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, the transmitting unit 101, the receiving unit 102, the receiving unit 201, the transmitting unit 202, etc. described above may be realized by the communication device 1004. FIG.

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (eg, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between devices.

In addition, the base station 100 and the terminal 200 include hardware such as microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), and FPGAs (Field Programmable Gate Arrays). , and part or all of each functional block may be implemented by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

(notification of information, signaling)
Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

(Applicable system)
Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other suitable systems and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

(Processing procedure, etc.)
The processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

(Base station operation)
Certain operations that are described in this disclosure as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes with a base station, various operations performed for communication with a terminal may be performed by the base station and other network nodes other than the base station (e.g. MME or S-GW, etc. (including but not limited to). Although the case where there is one network node other than the base station is exemplified above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).

(input/output direction)
Information and the like (*see the item “information, signal”) can be output from the upper layer (or lower layer) to the lower layer (or higher layer). It may be input and output via multiple network nodes.

(Handling of input/output information, etc.)
Input/output information and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

(Determination method)
The determination may be made by a value represented by one bit (0 or 1), by a true/false value (Boolean: true or false), or by numerical comparison (for example, a predetermined value).

(software)
Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) to website, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.

(information, signal)
Information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

The terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

("system", "network")
As used in this disclosure, the terms "system" and "network" are used interchangeably.

(parameter, channel name)
In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indexed.

The names used for the parameters described above are not restrictive names in any respect. Further, the formulas, etc., using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in no way restrictive names. is not.

(Base station (wireless base station))
In the present disclosure, "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", ""accesspoint","transmissionpoint","receptionpoint","transmission/receptionpoint","cell","sector","cellgroup", Terms such as "carrier" and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: Communication services can also be provided by Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.

(terminal)
In this disclosure, terms such as “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” “terminal,” etc. may be used interchangeably. .

A mobile station is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

(base station/mobile station)
At least one of a base station and a mobile station may be called a transmitter, a receiver, a communication device, and the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, terminal 200 may have the functions of base station 100 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, a terminal in the present disclosure may be read as a base station. In this case, the base station 100 may have the functions that the terminal 200 described above has.

(Term meaning and interpretation)
As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Judgement", "determining" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as "judged" or "determined", and the like. Also, "judgment" and "determination" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment" or "decision" has been made. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" may include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are defined using at least one of one or more wires, cables, and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

(reference signal)
The reference signal may be abbreviated as RS (Reference Signal), or may be referred to as Pilot according to the applicable standard.

(meaning "based on")
As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

("first", "second")
Any reference to elements using the "first,""second," etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

(means)
The "unit" in the configuration of each device described above may be replaced with "means", "circuit", "device", or the like.

(open format)
Where "include,""including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

(Time unit such as TTI, frequency unit such as RB, radio frame configuration) A radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

A numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception specific filtering operations performed by the receiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, and/or the like.

A slot may consist of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.

For example, one subframe may be called a Transmission Time Interval (TTI), a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. may That is, at least one of the subframe and 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 may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum scheduling time unit in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

A TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.

When one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like. A TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve. The number of subcarriers included in an RB may be determined based on neumerology.

Also, the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long. One TTI, one subframe, etc. may each consist of one or more resource blocks.

One or more RBs are physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. may be called.

Also, a resource block may be composed of one or more resource elements (RE: Resource Element). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A bandwidth part (BWP) (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a certain numerology in a certain carrier. good. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or multiple BWPs may be configured for a UE within one carrier.

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

The structures such as radio frames, subframes, slots, minislots and symbols described above are only examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. can be varied.

In this disclosure, if articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are plural.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

(Variation of mode, etc.)
Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching according to execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

One aspect of the present disclosure is useful for mobile communication systems.

10 wireless communication system 20 NG-RAN
100 base station 200

terminal

101, 202

transmitter

102, 201

receiver

103, 203 controller

Claims

Transmitting information over said physical uplink shared channel over a plurality of time resource units by multiplying a second size of an information block to be transmitted in said physical uplink shared channel in one time resource unit by a factor. a control unit that determines a first size of an information block to be transmitted in a transmission scheme that
a transmission unit that transmits the information block having the first size in the plurality of time resource units;
terminal with
The control unit determines the number of the time resource units allocated for use in the transmission scheme as the coefficient.
A terminal according to claim 1 .
The control unit determines the number of the time resource units that can be used for the transmission scheme as the coefficient.
A terminal according to claim 1 .
The control unit determines the coefficient based on control information related to the transmission method.
A terminal according to claim 1 .
The control information is included in at least one of Radio Resource Control (RRC), Media Access Control Element (MAC CE), and Downlink Control Information (DCI).
A terminal according to claim 4.
Transmitting information over said physical uplink shared channel over a plurality of time resource units by multiplying a second size of an information block to be transmitted in said physical uplink shared channel in one time resource unit by a factor. determining a first size of an information block to be transmitted in a transmission scheme that
transmitting information blocks having the first size in the plurality of time resource units;
wireless communication method.