Terminal and wireless communication method

Abstract

This terminal allocates, across a plurality of slots, a physical uplink shared channel, and transmits a data series over the physical uplink shared channel The terminal executes rate matching on each data series transmitted in a prescribed time region.

Description

Terminal and wireless communication method

[0001] The present disclosure relates to a terminal and a wireless communication method that support coverage extension.

[0002] The 3rd Generation Partnership Project (3GPP) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, in 3GPP Release-17, it has been agreed to consider Coverage Enhancement (CE) in NR (Non-Patent Document 1).

[0004] Furthermore, regarding coverage extension, it has been agreed to study a method for determining time resources of a physical uplink shared channel (PUSCH) allocated to multiple slots, specifically, TB processing over multi-slot PUSCH (TBoMS), which processes transport blocks (TBs) via a PUSCH (Physical Uplink Shared Channel) (Non-Patent Document 2).

[0005] "New WID on NR coverage enhancements", RP-202928, 3GPP TSG RAN meeting #90e, 3GPP, December 2020 "RAN1 Chairman's Notes", 3GPP TSG RAN WG1 Meeting #104-ee-Meeting, 3GPP, February 2021

[0006] However, in 3GPP Release-15 and 16, the transport block size (TBS) is specified based on a single slot, and applying this TBS directly to TBoMS may not necessarily be efficient.

[0007] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a terminal and a wireless communication method that can more efficiently realize TBoMS that processes transport blocks (TBs) via a physical uplink shared channel (PUSCH) allocated to multiple slots.

[0008] One aspect of the present disclosure is a terminal (UE 200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives control information indicating allocation of a physical uplink shared channel in the time domain, and a control unit (control unit 270) that allocates the physical uplink shared channel across multiple slots, and the control unit determines a transport block to be transmitted via the physical uplink shared channel based on the control information.

[0009] One aspect of the present disclosure is a terminal (UE) (200) that includes a control unit (control unit 270) that allocates a physical uplink shared channel across multiple slots, and a transmission unit (radio signal transceiver unit 210) that transmits a data sequence via the physical uplink shared channel, and the transmission unit repeatedly transmits the data sequence, which is obtained by concatenating multiple code blocks, via the physical uplink shared channel.

[0010] One aspect of the present disclosure is a terminal (UE) that includes a control unit (control unit 270) that allocates a physical uplink shared channel across multiple slots, and a transmission unit (radio signal transceiver unit 210) that transmits the physical uplink shared channel, wherein the control unit determines a size of a transport block to be transmitted via the physical uplink shared channel based on configuration information of the physical uplink shared channel in a serving cell.

[0011] One aspect of the present disclosure is a terminal (UE) that includes a control unit (control unit 270) that allocates a physical uplink shared channel across multiple slots, and a transmission unit (radio signal transceiver unit 210) that transmits the physical uplink shared channel, and the control unit determines how to divide a transport block to be transmitted via the physical uplink shared channel into multiple code blocks, based on whether or not to allocate the physical uplink shared channel across multiple slots.

[0012] One aspect of the present disclosure is a terminal (UE) (200) that includes a control unit (control unit 270) that allocates a physical uplink shared channel across multiple slots, and a transmission unit (radio signal transceiver unit 210) that transmits the physical uplink shared channel, and the control unit determines a modulation and coding scheme to be applied to the physical uplink shared channel based on whether or not the physical uplink shared channel is allocated across multiple slots.

[0013] One aspect of the present disclosure includes a control unit (control unit 270) that allocates a physical uplink shared channel across multiple slots, and a transmission unit (radio signal transceiver unit 210) that transmits a data sequence via the physical uplink shared channel, and the control unit performs rate matching for each of the data sequences transmitted in a specific time domain (UE 200).

[0014] One aspect of the present disclosure is a wireless communication method comprising: receiving control information indicating a time domain allocation of a physical uplink shared channel; and allocating the physical uplink shared channel across a plurality of slots, wherein in the allocating the physical uplink shared channel, a transport block to be transmitted via the physical uplink shared channel is determined based on the control information.

[0015] One aspect of the present disclosure is a wireless communication method including a step of allocating a physical uplink shared channel across a plurality of slots and a step of transmitting a data sequence via the physical uplink shared channel, wherein in the allocating step, rate matching is performed for each of the data sequences transmitted in a specific time domain.

[0016] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram showing an example of the configuration of radio frames, subframes, and slots used in the wireless communication system 10. FIG. 3 is a functional block configuration diagram of a gNB 100 and a UE 200. FIG. 4 is a diagram showing an example of PUSCH allocation by TBoMS. FIG. 5 is a diagram explaining problems in an example of PUSCH allocation by TBoMS (Type A repetition like TDRA). FIG. 6 is a diagram showing an example of PUSCH time domain allocation according to operation example 1 (Opt 1, 2). FIG. 7 is a diagram showing an example of PUSCH (TB) allocation according to operation example 2 (Alt 1-1-1). FIG. 8 is a diagram showing an example of the configuration of a redundancy version (RV) according to operation example 2 (Alt 2-2). FIG. 9 is a diagram showing N according to operation example 3-1 (Opt 1). sh symbFIG. 10 is a diagram showing an example of TB allocation according to Operation Example 4 (Alt 2). FIG. 11 is a diagram showing an example of TB allocation according to Operation Example 4 (Alt 4-1). FIG. 12 is a diagram showing an example of UL channel repetition according to Operation Example 6 (Opt 3). FIG. 13 is a diagram showing an example of UL channel repetition according to Operation Example 6-1 (Opt 4). FIG. 14 is a diagram showing an example of UL channel repetition according to Operation Example 6-2 (Opt 3, 4). FIG. 15 is a diagram showing an example of UL channel repetition according to Operation Example 6-2 (Opt 5). FIG. 16 is a diagram showing an example of UL channel repetition according to Operation Example 6-3 (Alt 1, 2). FIG. 17 is a diagram showing an example of UL channel repetition according to Operation Example 6-3 (Alt 3, 4). FIG. 18 is a diagram showing an example of the configuration of MAC RAR according to Operation Example 7. 19 is a diagram illustrating an example of a configuration of slot allocation and a redundancy version (RV) according to operation example 8. FIG. 20 is a diagram illustrating an example of a hardware configuration of the gNB100 and the UE200.

[0017] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0018] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

[0019] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0020] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1 .

[0021] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0022] The gNB100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO, which generates highly directional beams by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and multiple NG-RAN nodes.

[0023] The wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR (Frequency Range) are as follows:

[0024] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

[0025] Furthermore, the wireless communication system 10 may also support frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz up to 114.25 GHz.

[0026] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied, and DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0027] FIG. 2 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10.

[0028] As shown in Figure 2, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 (e.g., 28 or 56 symbols). The number of slots per subframe may also vary depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz or 960 kHz, as shown in Figure 2).

[0029] The time direction (t) shown in Fig. 2 may be called a time domain, a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a resource block group, a subcarrier, a BWP (Bandwidth Part), a subchannel, a common frequency resource, etc.

[0030] The wireless communication system 10 can support coverage enhancement (CE) that expands the coverage of a cell (or physical channel) formed by the gNB 100. Coverage enhancement may provide a mechanism for improving the success rate of reception of various physical channels.

[0031] For example, gNB100 can support repeated transmission of PDSCH (Physical Downlink Shared Channel), and UE200 can support repeated transmission of PUSCH (Physical Uplink Shared Channel).

[0032] A slot configuration pattern for time division duplexing (TDD) may be set in the wireless communication system 10. 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).

[0033] "D" indicates a slot that contains only DL symbols, "S" indicates a slot that contains a mixture of DL, UL, and guard symbols (G), and "U" indicates a slot that contains only UL symbols. For example, if the S slot is 10D+2G+2U, two consecutive symbols (2U) and one slot (14 symbols) in the time direction can be used for UL, that is, multiple consecutive slots can be used for UL.

[0034] Furthermore, in the wireless communication system 10, channel estimation of the PUSCH (or PUCCH (Physical Uplink Control Channel)) can be performed using a demodulation reference signal (DMRS) for each slot, and further, channel estimation of the PUSCH (or PUCCH) can be performed using DMRSs allocated to multiple slots, respectively. Such channel estimation may be called joint channel estimation, or may be called by another name such as cross-slot channel estimation.

[0035] UE200 can transmit DMRS allocated to (spanning) multiple slots so that gNB100 can perform joint channel estimation using DMRS.

[0036] Furthermore, in the wireless communication system 10, for coverage extension, TB processing over multi-slot PUSCH (TBoMS) may be applied, which processes a transport block (TB) via a PUSCH allocated to multiple slots.

[0037] In TBoMS, the number of allocated symbols may be the same in each slot, as in Time Domain Resource Allocation (TDRA) with PUSCH Repetition type A (described in detail below), or the number of allocated symbols in each slot may be different, as in TDRA with PUSCH Repetition type B (described in detail below).

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

[0039] TDRA may also be interpreted as a time domain resource allocation for PUSCH specified by Downlink Control Information (DCI).

[0040] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described. Fig. 3 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0041] As shown in FIG. 3 , the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0042] It should be noted that Fig. 3 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (e.g., a power supply unit, etc.). Fig. 3 shows the functional block configuration of the UE 200, and for the hardware configuration, please refer to Fig. 19.

[0043] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.

[0044] Furthermore, the radio signal transceiver 210 may transmit a physical uplink shared channel. In this embodiment, the radio signal transceiver 210 may constitute a transmitter.

[0045] Specifically, the radio signal transmission / reception unit 210 may transmit the PUSCH to the network (gNB 100). The radio signal transmission / reception unit 210 may support repeated transmission of the PUSCH.

[0046] A plurality of types of repeated transmission of the PUSCH may be defined. Specifically, Repetition type A and Repetition type B may be defined. Repetition type A may be interpreted as a form in which the PUSCH allocated within a slot is repeatedly transmitted. In other words, the PUSCH is 14 symbols or less and cannot be allocated across multiple slots (adjacent slots).

[0047] On the other hand, Repetition type B may be interpreted as repeated transmission of a PUSCH in which a PUSCH of 15 symbols or more may be allocated. In this embodiment, it may be permitted to allocate such a PUSCH across multiple slots.

[0048] Furthermore, the radio signal transceiver 210 may repeatedly transmit uplink channels (UL channels) during a specific period of at least a plurality of slots. The uplink channels may include a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH).

[0049] The shared channel may also be called a data channel.

[0050] The specific period of more than one slot may be interpreted as a period related to the repetition of the PUSCH (or PUCCH). For example, the specific period may be indicated by the number of repetitions, or may be the time during which a specified number of repetitions are performed.

[0051] Alternatively, the radio signal transmitting and receiving unit 210 may repeatedly transmit the UL channel a specific number of times. Specifically, the radio signal transmitting and receiving unit 210 may repeatedly transmit the PUSCH (or PUCCH) a plurality of times.

[0052] The specific period and / or the specific number of times may be indicated by signaling from the network (which may be a higher layer of RRC or a lower layer such as DCI, same below), or may be pre-configured in UE200.

[0053] Furthermore, the radio signal transceiver 210 may repeatedly transmit a data sequence obtained by concatenating multiple code blocks (CBs) via a PUSCH. The data sequence may be interpreted as a data block, a bit sequence, a bit string, or other equivalent terms. The CB may be a CB after Cyclic Redundancy Checksum (CRC) processing, CB division, channel coding, and rate matching.

[0054] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0055] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0056] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0057] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0058] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0059] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0060] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0061] The channels include a control channel and a data channel. The control channels may include a Physical Downlink Control Channel (PDCCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0062] Furthermore, the data channel includes a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), etc. Data may refer to data transmitted via a data channel.

[0063] Furthermore, the control signal and reference signal processor 240 may transmit capability information of the UE 200 regarding allocation of the Physical Uplink Shared Channel (PUSCH) to the network. In this embodiment, the control signal and reference signal processor 240 may constitute a transmitter that transmits the capability information.

[0064] Specifically, the control signal and reference signal processing unit 240 can transmit UE capability information related to PUSCH allocation (which may include repetition) to the gNB 100. Details of the UE capability information will be described later.

[0065] Furthermore, the control signal and reference signal processor 240 can receive control information indicating allocation of PUSCH in the time domain. In this embodiment, the control signal and reference signal processor 240 may constitute a receiver.

[0066] Specifically, the control signal and reference signal processor 240 may receive downlink control information (DCI) indicating allocation of PUSCH in the time domain.

[0067] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).

[0068] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0069] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0070] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 controls transmission of the UL channel, specifically, the PUSCH and PUCCH.

[0071] Specifically, the control unit 270 can hop the UL channel in the frequency direction in units of a specific period of multiple slots or more. Hopping the UL channel in the frequency direction may be called frequency hopping, and frequency hopping in units of a specific period of multiple slots or more may be called inter-slot frequency hopping. Note that hopping may mean changing the frequency resources used. In short, it may mean changing the subcarriers, resource blocks, resource block groups, BWPs, etc.

[0072] Furthermore, the control unit 270 may hop the UL channel in the frequency direction in units of a specific number of times indicating the number of repeated transmissions of the UL channel. Specifically, the control unit 270 may perform frequency hopping in units of the specified number of repeated transmissions (repetition number) of the UL channel, in other words, for each predetermined number of repetitions.

[0073] When joint channel estimation is applied in gNB100, if transmissions of UL channels (PUSCH and PUCCH) overlap (which may also be expressed as collision), the control unit 270 may determine a frequency hopping pattern using allocatable resources that avoid overlap when allocating resources for the UL channel (which may also be repetition), specifically at the timing of receiving DCI.

[0074] Alternatively, when transmission of UL channels (PUSCH and PUCCH) overlaps, the control unit 270 may determine a hopping pattern using allocatable resources that avoids overlap at the time of the first repetition of the UL channel, specifically, at the transmission timing of the first repetition.

[0075] Furthermore, the control unit 270 may set a hopping pattern for the repetition of the UL channel as described above based on signaling from the network.

[0076] Control unit 270 may determine the allocation of the UL channel, specifically, the DMRS to be transmitted on the PUSCH, based on the repetition state of the PUSCH, that is, the number of repetitions, the repetition period, and the like.

[0077] Specifically, control unit 270 may transmit the same DMRS symbol (OFDM symbol) for each predetermined number of repetitions. Furthermore, control unit 270 may set the DMRS symbol (OFDM symbol) to be used for each predetermined number of repetitions.

[0078] As described above, the control unit 270 may allocate the PUSCH across multiple slots, that is, may support TBoMS. When supporting TBoMS, the control unit 270 may determine a transport block (TB) to be transmitted via the PUSCH based on DCI (control information) received by the control signal / reference signal processing unit 240.

[0079] Note that spanning multiple slots may mean that the PUSCH is allocated to two or more consecutive slots. Also, the unit may be a symbol or a subframe, instead of a slot.

[0080] The control unit 270 may determine the size of a transport block (TB) transmitted via a PUSCH based on configuration information of the PUSCH in the serving cell. For example, the control unit 270 may determine the size of the TB based on PDSCH-ServingCellConfig, which is an information element (IE) of the RRC layer. However, as long as it is related to the configuration information of the PUSCH, other information elements of the RRC layer may be used, and the size may not necessarily be limited to the serving cell. Furthermore, the control unit 270 may determine the size of the TB based on configuration information related to the PUSCH of a layer other than the RRC layer.

[0081] Furthermore, the control unit 270 may determine how to divide the TB transmitted via the PUSCH into multiple code blocks (CBs) based on whether or not the PUSCH is allocated across multiple slots.

[0082] For example, control unit 270 may divide one TB into a plurality of CBs (maximum of eight) as in 3GPP Release-15 and 16. Alternatively, control unit 270 may change the maximum number of divisions into CBs depending on the number of slots (or number of symbols) to which PUSCHs are allocated.

[0083] Furthermore, the control unit 270 may determine the modulation and coding scheme to be applied to the PUSCH based on whether or not the PUSCH is allocated across multiple slots. Specifically, in the case of allocating the PUSCH across multiple slots, that is, TBoMS, the control unit 270 may apply a specific Quadrature Amplitude Modulation (QAM) as the modulation scheme, or a specific Modulation and Coding Scheme (MCS).

[0084] Furthermore, the control unit 270 may perform rate matching for each data sequence transmitted in a specific time domain (for example, a slot). The slots to which rate matching is applied may be only slots in which the PUSCH is actually transmitted, or may be resources specified in resource allocation.

[0085] Alternatively, control unit 270 may perform rate matching for each data sequence transmitted in a specific slot. Specifically, control unit 270 may perform rate matching for each sequence transmitted in each slot during TBoMS transmission.

[0086] Alternatively, the control unit 270 may perform rate matching on a data sequence transmitted using resources to which a transport block (which may be TBoMS) is allocated. Specifically, the control unit 270 may perform rate matching on a sequence transmitted using all resources to which TBoMS is allocated.

[0087] The gNB 100 may also have the above-mentioned functions related to DMRS transmission / reception and TBoMS. For example, the gNB 100 (radio signal transmission / reception unit 210) may configure a reception unit that receives an UL channel repeatedly transmitted within a specific period from the UE 200. The radio signal transmission / reception unit 210 of the gNB 100 may receive an UL channel hopped in the frequency direction in units of the specific period.

[0088] Furthermore, the gNB100 (radio signal transmitting / receiving unit 210) may receive a UL channel (e.g., PUSCH) that is repeatedly transmitted, i.e., that undergoes repetition, a specific number of times from the UE 200. In this case, the gNB100 (radio signal transmitting / receiving unit 210) may receive the UL channel that has hopped in the frequency direction in units of the specific number of times.

[0089] The gNB100 (control unit 270) may be configured as a control unit that performs channel estimation (joint channel estimation) of an UL channel, for example, a PUSCH, assigned to multiple slots using DMRSs assigned to multiple slots.

[0090] In addition, the gNB100 (control unit 270) may perform TBoMS, which processes TB via an UL channel allocated to multiple slots, i.e., control related to the reception of an UL channel such as a PUSCH allocated across multiple slots.

[0091] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. The following describes the operation related to channel estimation of the uplink channel for the purpose of coverage extension performance.

[0092] (3.1) Assumptions As mentioned above, TBoMS may be interpreted as a technology for transmitting one transport block using multiple slots.

[0093] Fig. 4 shows an example of PUSCH allocation by TBoMS. Specifically, Fig. 4 shows an example of PUSCH allocation by TBoMS in accordance with Type A repetition like TDRA and Type B repetition like TDRA. Note that Types A and B are as described above and may mean Repetition types A and B.

[0094] TBoMS may have the following advantages:

[0095] - Because resources are allocated across multiple slots, the coding rate (code rate) decreases.

[0096] - The longer the code sequence, the higher the gain of channel coding.

[0097] - The amount of headers in the upper layer can be reduced compared to when sending multiple TB.

[0098] In addition, in 3GPP Release-15 and the like, when determining the size of TB (TBS) transmitted via PUSCH (as well as PDSCH), the number of REs (N RE ) is calculated, and then the calculated N RE Using the number of information bits (N info ) is calculated. Then, TBS is calculated as N info Here, the TBS is determined on the assumption that the PUSCH is allocated to only one slot.

[0099] Fig. 5 is a diagram illustrating an example of PUSCH allocation (Type A repetition like TDRA) using TBoMS. As shown in Fig. 5, in the case of TBoMS, it is necessary to determine a TBS size corresponding to a PUSCH allocated across multiple slots (which may be consecutive).

[0100] (3.2) Overview of Operation The following operation example will be described below.

[0101] (Operation example 1): PUSCH time domain allocation method when TBoMS is applied. (Operation example 2): Method of transmitting 1TB in multiple slots. (Operation example 3): Method of determining TBS when TBoMS is applied. (Operation example 3-1): N RE When calculating N, the number of REs is expanded to multiple slots instead of one slot. (Example 3-2): Based on the SLIV (Start and Length Indicator Value) of TDRA, N RE Calculate N according to TDRA info ・(Operation Example 4): Method for determining the number of code blocks when using TBoMS ・(Operation Example 5): Method for selecting an MCS table when using TBoMS ・(Operation Example 6): Frequency hopping when using TBoMS ・(Operation Example 6-1): Frequency hopping (Type A repetition like TDRA) ・(Operation Example 6-2): Frequency hopping (Type B repetition like TDRA) ・(Operation Example 6-3): Hopping pattern when dropping Repetition resources ・(Operation Example 6-4): Method for receiving information related to frequency hopping ・(Operation Example 7): Application to Msg3 PUSCH ・(Operation Example 7-1): Applicability of Joint channel estimation in Msg3 ・(Operation Example 8): Notification of UE capability

[0102] (3.3) Operation Example 1 In this operation example, an operation relating to allocation of the PUSCH time region when TBoMS is applied will be described.

[0103] When performing TDRA for TBoMS, the UE 200 may notify the network (radio base station) of the PUSCH time region allocation method by any of the following methods.

[0104] (Opt 1): Notify to combine multiple repetitions to be allocated into one repetition of TBoMS PUSCH. (Opt 2): Notify the number of slots (or the number of repeated transmissions (repetitions)) to which PUSCH used for transmitting one TB (1 TB) is allocated, independent of the repetition (alternatively, the network may notify the UE 200, and the UE 200 may operate based on the notification (same below).

[0105] Fig. 6 shows an example of allocation of the PUSCH time domain according to operation example 1 (Opt 1, 2). As shown in Fig. 6, multiple repetitions may be combined into one repetition (Opt 1), or a PUSCH for 1 TB may be allocated to multiple slots regardless of the number of repetitions.

[0106] (Opt 2-1): The number of slots (or the number of repetitions) is notified by higher layer signaling. In this case, the number of repetitions may be the number of repetitions actually allocated or the number of repetitions before the repetition resources are dropped. For example, the PUSCH-Config IE or ConfiguredGrantConfig IE of the RRC layer may be used for this signaling.

[0107] (Opt 2-2): The number of slots (or the number of repetitions) is notified using DCI. In this case, the number of slots may be the number of slots that can actually be allocated or the number of consecutive slots before dropping the repetition resource.

[0108] (Opt 2-2-1): Explicitly notify using DCI For example, TBoMS-related information may be added as an element of the TDRA table in the RRC layer.

[0109] (Opt 2-2-2): Implicit notification using DCI For example, the TBoMS-related information may be linked to a DCI field and notified. Alternatively, the TBoMS-related information may be linked to a CCE (Control channel element) index where the DCI for resource allocation is located and notified. In this case, the linking method may be notification by signaling from a higher layer or may be determined according to a predetermined rule.

[0110] (3.4) Operation Example 2 In this operation example, an operation of transmitting 1 TB using multiple slots will be described. The UE 200 may transmit 1 TB using multiple slots by any of the following methods.

[0111] (Alt 1): Transmitting a 1-bit sequence after code block (CB) concatenation across multiple slots. Specifically, a 1-bit sequence may be divided and transmitted across multiple slots using designated resources.

[0112] (Alt 1-1): Transmit a 1-bit sequence via multiple PUSCHs (Alt 1-2): Allocate one PUSCH to multiple slots (Alt 2): Repeatedly transmit a CB-concatenated sequence Multiple sequences may be allocated using resources specified across multiple slots (similar to Repetition). In this case, the same sequence may be repeatedly transmitted, or different sequences may be transmitted.

[0113] Note that processing may be performed in the following order: CRC attachment, CB segmentation, CRC attachment per CB, channel coding, rate matching, and CB concatenation.

[0114] (Alt 1-1-1): Transmit an equally divided bit sequence via each PUSCH. (Alt 1-1-2): Determine the bit length to be transmitted according to the symbol length of each PUSCH. For example, if segmentation occurs in Type B repetition like TDRA, bit sequences of different bit lengths may be transmitted in each repetition.

[0115] FIG. 7 shows an example of PUSCH (TB) allocation according to operation example 2 (Alt 1-1-1).

[0116] ・(Alt 2-1): Use conventional bit selection when rate matching. ・(Alt 2-2): Apply new bit selection when rate matching. For example, five or more redundancy versions (RVs) may be provided, and one may be selected during bit selection.

[0117] (Opt A): In addition to the RVs with existing starting points assigned, add RVs with different starting points assigned. (Opt B): Assign a new starting point to each RV. Figure 8 shows a configuration example of the redundancy version (RV) related to operation example 2 (Alt 2-2). As shown in Figure 8, RVs with existing starting points assigned (RV0-3) and RVs with different starting points assigned (RV4, 5) may be used (Opt A), or a new starting point may be assigned to each RV (Opt B).

[0118] (3.5) Operation Example 3 In this operation example, an operation relating to the determination of a TBS when TBoMS is applied will be described. Specifically, the determination of a TBS corresponding to a TB spanning multiple slots will be described.

[0119] ・(Opt 1): N RE When calculating, the number of REs is expanded to multiple slots instead of one slot (Example 3-1). Specifically, N RE(N' RE ) may be calculated.

[0120]

[0121] Here, each variable may be changed to the number of REs spanning multiple slots.

[0122] (Opt 2): Based on the SLIV of TDRA, RE Calculate N according to TDRA info (Operation example 3-2) ・(Alt 1): In the case of Type A repetition like TDRA, N of one slot RE Calculate the number of repeated transmissions and info Multiply when calculating In this case, the number of slots may be calculated taking into account the slots to be dropped (multiplying by the number of allocatable slots). If a TDD pattern, SFI (Slot Format Indication) / CI (Cancel Indication), etc. are present, the value may be changed from the value notified by the TBS to be transmitted or received.

[0123] ・(Alt 2): In the case of Type B repetition like TDRA, N of one Repetition RE Calculate the number of repeated transmissions and info Multiply during calculation (Opt 1): Multiply the actual number of repetitions. In this case, the actual number of repetitions that is not segmented may be multiplied.

[0124] ・(Opt 2): Multiply the nominal repetition number.

[0125] Note that the actual repetition is the repetition finally transmitted, and the nominal repetition may be interpreted as the repetition notified / assigned by the gNB to the UE. For example, the actual repetition and the nominal repetition may change depending on the following factors.

[0126] (i) If no nominal repetition is placed in the UL symbol, the nominal repetition may be omitted.

[0127] (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.

[0128] (Alt 3): Add a specific parameter (the parameter may be signaled using DCI or higher layer signaling). For example, N info A predetermined parameter (K) may be added when calculating the value of N. For example, K may be info It may be a value that multiplies the value by K (scaling factor), but the purpose is not necessarily limited to this.

[0129]

[0130] (3.5.1) Operation Example 3-1 In this operation example, N RE When calculating, the number of REs may be expanded to multiple slots instead of one slot.

[0131] In this case, N PRB oh may be calculated by either:

[0132] ・(Opt 1): Same N for all slots PRB oh ・(Opt 1-1): The xOverhead set by PDSCH-ServingCellConfig is allocated to each slot. ・(Opt 1-2): The xOverhead set by PDSCH-ServingCellConfig is divided by the number of slots to which TBoMS is applied, and the value is allocated to each slot. PRB oh In this case, the quotient may be rounded to an integer by ceil or floor.

[0133] (Opt 1-3): Add new parameters and, when using TBoMS, calculate N based on the parameters. PRB oh (Opt 1-4): Add a new parameter and determine N based on the parameter and xOverhead when TBoMS is used. PRB oh (Opt 2): Determine N based on the number of slots and symbols to which TBoMS is applied. PRB oh Set: (Opt 2-1): Multiply xOverhead by the number of slots to which resources are allocated (Type A repetition like TDRA) (Opt 2-2): Multiply xOverhead by the number of repeated transmissions (Type B repetition like TDRA) (Opt 2-2-1): Multiply by the actual repetition number.

[0134] In this case, the number of actual repetitions that are not divided may be multiplied.

[0135] ・(Opt 2-2-2): Multiply the nominal repetition number.

[0136] (Opt 2-3): Calculated according to the SLIV of TDRA, the number of symbols to be allocated, the total number of allocated symbols, and xOverhead. For example, it may be calculated by (xOverhead) × (total number of symbols) / (SLIV of TDRA and number of symbols to be allocated).

[0137] In Opt 2-1, 2-2, and 2-3, a different parameter set by PDSCH-ServingCellConfig may be used instead of xOverhead. For example, N is set based on the added parameter, xOverhead, and the number of slots and symbols. PRB oh In this case, different parameters may be set when TBoMS is applied and when it is not applied.

[0138] Also, N shsymb Calculation of (N PRB DMRS ), any of the following may apply:

[0139] (Alt 1): Change to the number of symbols (RE) of all resources to which resources are assigned. In this case, the number of symbols (RE) may be calculated taking into account the TDD pattern, SFI, and CI.

[0140] ・(Alt 2): Multiply by the number of slots to which resources can be allocated (Type A repetition like TDRA) ・(Alt 3): Multiply by the number of repeated transmissions (Type B repetition like TDRA) ・(Opt 1): Multiply by the actual repetition number.

[0141] In this case, the number of actual repetitions that are not divided may be multiplied.

[0142] ・(Opt 2): Multiply the nominal repetition number.

[0143] FIG. 9 shows the N sh symb As shown in Figure 9, the number of symbols in multiple slots (18) may be calculated.

[0144] (3.6) Operation Example 4 In this operation example, an operation relating to the determination of the number of code blocks in TBoMS will be described.

[0145] The 1 TB for TBoMS may be divided into CBs in any of the following ways:

[0146] (Alt 1): When TBoMS is used, CBs are not divided. Regardless of the maxCodeBlockGroupsPerTransportBlock set by RRC, CBs are not divided. (Alt 2): As in 3GPP Releases 15 and 16, 1 TB is divided into multiple CBs (up to 8 CBs). In this case, the maximum number of maxCodeBlockGroupsPerTransportBlock may be increased. Also, the maximum number of CBs when TBoMS is used may be set individually.

[0147] (Alt 3): Change the division number of the maximum CB according to the number of slots (number of symbols). In this case, the maximum number of CBs may be changed appropriately according to the number of slots (number of symbols) to which 1 TB is allocated. For example, the number of slots to which 1 TB is allocated may be multiplied by the maximum number of CBs set by RRC.

[0148] (Alt 4): Set the number of CBs according to the number of repetitions when allocating resources. Fig. 10 shows an example of TB allocation according to operation example 4 (Alt 2). As shown in Fig. 10, when maxCodeBlockGroupsPerTransportBlock = 4, one TB spanning three slots may be divided into four CBs.

[0149] ・(Alt 4-1): Multiply the number of repeat placements by the maximum number of CBs ・(Alt 4-2): Set the number of repeat placements = maximum number of CBs Note that Alt 3 and Alt 4 may have the maximum number of CBs limited to 8 so that they can be handled by the conventional DCI.

[0150] 11 shows an example of TB allocation according to Operation Example 4 (Alt 4-1). As shown in FIG. 11, when 1 TB spans three slots, the maximum number of CBs may be set to six, and when it spans two slots, the maximum number of CBs may be set to four.

[0151] (3.7) Operation Example 5 In this operation example, an operation related to MCS table selection when TBoMS is used will be described. Regarding the MCS table when TBoMS is used, any of the following operations may be applied.

[0152] (Alt 1): When TBoMS is used, the qam 64 low SE MCS table is fixed. Specifically, when TBoMS is used, the qam 64 low SE MCS table may be fixed, regardless of whether MCS-C (Cell)-RNTI is used. This operation may also be applied to Msg 3. Msg 3 is a message for the Random Access Channel (RACH) procedure, and PUSCH may be used to transmit Msg 3.

[0153] (Alt 2): When TBoMS is used, a new low SE MCS table can be used. Specifically, when TBoMS is used, a new MCS table may be used. When C-RNTI is used, one of the following MCS tables may be specified by a predetermined rule, higher layer signaling, or DCI.

[0154] - Existing MCS table - qam 64 low SE MCS table - New MCS table Furthermore, when MCS-C-RNTI is used, any of the following MCS tables may be specified by a predetermined rule, higher layer signaling, or DCI.

[0155] qam 64 low SE MCS table New MCS table Note that an MCS table may be selected implicitly depending on the MCS index, TDRA, or transmission power.

[0156] (3.8) Operation Example 6 (3.8.1) Operation Example 6-1 In this operation example, an operation relating to frequency hopping when TBoMS is used will be described.

[0157] When TBoMS is applied, UE 200 may determine the hopping pattern of the UL channel from the following hopping patterns according to a rule (setting) specified by the network (radio base station) or a predefined rule. The UL channel may refer to either a PUSCH or a PUCCH (same applies below). The UL channel may also include a repeated PUSCH or PUCCH.

[0158] Specifically, when Type A repetition like TDRA is applied or PUCCH is used, UE 200 may determine one of the following hopping patterns.

[0159] (Opt 1): Frequency hopping for each slot (Opt 2): Frequency hopping within a slot (Opt 3): Frequency hopping only once within a repetition transmission (Opt 3-1): Calculating a unique hop duration based on the number of repetition transmissions. In this case, frequency hopping may not be performed based on the number of repetition transmissions of the UL channel. The number of repetitions may be the number of repetitions actually assigned, or the number of repetitions before the repetition resource is dropped. Dropping a repetition resource may be interpreted as a resource (time resource and / or frequency resource) that cannot be assigned due to a collision (overlapping assignment) between the repetition resource and a resource of another UL channel.

[0160] For example, the hopping duration may be determined by first hopping duration = floor(repetition number / 2) or ceil(repetition number / 2).

[0161] (Opt 3-2): Notify slot position for frequency hopping For example, UE 200 may notify the network of duration per hop = X slot number (X repetition number) and perform frequency hopping after X repetition transmission (X repetition transmission, same below). Alternatively, the network may notify UE 200, and UE 200 may operate based on the notification (same below).

[0162] The number of slots may be the number of slots actually allocated by Repetition, or may be the number of slots before the Repetition resource is dropped.

[0163] Fig. 12 shows an example of UL channel repetition according to operation example 6 (Opt 3). As shown in Fig. 12, the hop period may be determined as floor (number of repetitions (Rep) (6) / 2) = 3. In Fig. 12, each frame in the time (t) direction may be interpreted as corresponding to a slot (or symbol, etc.) (same below).

[0164] The hop duration may be expressed as a term such as duration hop, hopping duration, or duration per hop, and may be indicated by a time length or the number of repetitions.

[0165] (Opt 4): Frequency hopping every X slots (Opt 4-1): Duration per hop is notified from the network. For example, it may be notified that duration per hop = X number of slots, and frequency hopping may be performed every X slots.

[0166] (Opt 4-2): Determine the hopping pattern based on the number of slots (or the number of symbols) to which joint channel estimation is applied. For example, if the time window size is three slots, frequency hopping may be performed every three slots. The time window size may be in units of slots or other time domain units such as symbols (same below).

[0167] (Opt 4-3): Determine duration per hop based on the number of repeated transmissions. (Opt 4-4): Determine hopping pattern based on the number of repeated transmissions and the number of slots (or the number of symbols) to which joint channel estimation is applied. Figure 13 shows an example of UL channel repetition related to operation example 6-1 (Opt 4). As shown in Figure 13, frequency hopping (X = 2) may be performed every two slots.

[0168] (3.8.2) Operation Example 6-2 In this operation example, an operation relating to frequency hopping (Type B repetition like TDRA) when TBoMS is applied will be described.

[0169] The UE 200 may determine the hopping pattern of the UL channel from among the following hopping patterns according to a rule specified by the network (radio base station) or defined in advance.

[0170] Specifically, when Type B repetition like TDRA is applied, the UE 200 may determine one of the following hopping patterns.

[0171] (Opt 1): Frequency hopping every slot (Opt 2): Frequency hopping every repetition (Opt 3): Frequency hopping only once within a repetition transmission (Opt 4): Frequency hopping every X slots Figure 14 shows an example of UL channel repetition according to operational example 6-2 (Opt 3, 4). Specifically, the upper part of Figure 14 shows an example of UL channel repetition according to Opt 3, and the lower part of Figure 14 shows an example of UL channel repetition according to Opt 4.

[0172] As shown in Fig. 14, the hop period may be determined as floor (number of repetitions (10) / 2) = 5, or frequency hopping (X = 2) may be performed every two slots. Also, as shown in Fig. 14, in the case of Type B repetition like TDRA, multiple repetitions (Rep) may be repeated within a slot, or multiple repetitions may be assigned within the same slot.

[0173] (Opt 5): Frequency hopping every X repetitions (Opt 5-1): duration per hop is notified from the network For example, the UE 200 may notify that duration per hop = X number of repetitions, and perform frequency hopping every X repetitions.

[0174] (Opt 5-2): Determine the hopping pattern based on the number of slots (or the number of symbols) to which joint channel estimation is applied. For example, if the time window size is three slots, frequency hopping may be performed every three slots. The time window size may be a time domain to which joint channel estimation is applicable, and may be in units of slots or other time domain units such as symbols.

[0175] Figure 15 shows an example of UL channel repetition according to Operation Example 6-2 (Opt 5). As shown in Figure 15, frequency hopping may be performed every three slots. Also, as shown in Figure 15, the hopping timing may be within a slot (in the middle) rather than at a slot boundary.

[0176] (3.8.3) Operation Example 6-3 In this operation example, an operation related to a hopping pattern when a repetition resource is dropped when TBoMS is applied will be described. Fig. 16 shows an example of repetition of the UL channel according to operation example 6-3 (Alt 1, 2).

[0177] When joint channel estimation is applied (at the radio base station side) and the repetition resource of the UL channel (e.g., PUSCH) collides (may also be called overlapping) with a different resource (e.g., resource for PUCCH), UE200 may apply one of the following hopping patterns:

[0178] (Alt 1): Apply hopping pattern without considering resource collisions. In this case, the hopping pattern may be applied on a slot-by-slot basis without considering whether a resource will be dropped. For example, even if a second Repetition resource is dropped, the same hopping pattern may be maintained (see the upper part of Figure 16, where the dropped Repetition resource is indicated by a dotted frame).

[0179] (Alt. 2): Applying a hopping pattern based on the resources actually transmitted. In this case, the hopping pattern may be applied based on the resources used for transmitting each repetition. For example, if the second repetition resource is dropped, the hopping pattern may be applied excluding the dropped resource (see the bottom of Figure 10; since the dropped repetition resource (dotted frame) is excluded, the frequency direction resources from slot #3 onwards are different from Alt. 1).

[0180] When a hopping pattern as described below is applied, or when the number of repeated transmissions is specified based on the number of allocatable resources, Alt 1 and 2 may be set separately.

[0181] FIG. 17 shows an example of UL channel repetition according to operation example 6-3 (Alt 3, 4).

[0182] (Alt 3): When allocating resources, a hopping pattern is applied based on allocable repetition resources. In this case, allocable resources may be determined depending on the collision reason. For example, the symbols of the TDD pattern and SS / PBCH block (Synchronization Signal / Physical Broadcast Channel blocks) may be taken into consideration, but collisions with repetitive transmissions of SFI (Slot Format Indication) / CI (Control Information) / PUCCH may not be taken into consideration. Alternatively, dropping of repetition resources known to the radio base station (gNB100) may be taken into consideration, but dropping of resources that the radio base station cannot determine may not be taken into consideration.

[0183] (Alt 4): When transmitting the first repetition, a hopping pattern is applied to allocatable repetition resources. In this case, allocatable resources may be determined depending on the collision reason. As with Alt 3, for example, TDD pattern and SS / PBCH block symbols may be taken into consideration, but collision with repetitive transmission of SFI / CI / PUCCH may not be taken into consideration. Alternatively, dropping of repetition resources known to the radio base station may be taken into consideration, but dropping of resources that the radio base station cannot determine may not be taken into consideration.

[0184] (3.8.4) Operation Example 6-4 In this operation example, the UE 200 may receive frequency hopping-related information by any of the following methods.

[0185] (Opt 1): DCI (Opt 1-1): Explicit frequency hopping related information by DCI fields In this case, the linking (association) between the frequency hopping related information and the DCI fields may be performed using higher layer signaling or may follow predefined rules (settings).

[0186] (Opt 1-2): In a higher layer, an information element for frequency hopping-related information is added to the TDRA table and determined by DCI. (Opt 1-3): Implicit frequency hopping-related information according to a DCI field. For example, frequency hopping-related information may be linked to a DCI field. Alternatively, frequency hopping-related information may be linked to a CCE (Control channel element) index where the DCI for resource allocation is located.

[0187] (Opt 2): Higher layer signaling For example, the hopping pattern may be selected based on frequency hopping related information received in the RRC.

[0188] (Opt 3): Determine a hopping pattern based on a predetermined rule. For example, in the case of channel estimation using multiple slots, any of the hopping pattern options may be specified.

[0189] Furthermore, the UE 200 may set the hopping pattern by any of the following methods.

[0190] The number of slots to which joint channel estimation is applied and the hop duration parameters are set separately or in common. The parameters are set separately or in common for Type A like repetition TDRA and Type B like repetition TDRA. The hop duration for Type B like repetition TDRA is set separately or in common for the number of slots and the number of repetitions.

[0191] (3.9) Operation Example 7 In this operation example, an operation relating to application of TBoMS to Msg3 PUSCH will be described.

[0192] The UE 200 may receive information related to the TBoMS for Msg3initial transmission based on any one or a combination of the following methods: In this case, the settings related to the TBoMS may differ depending on the frequency (band) used by the UE.

[0193] Notification to UE 200 by signaling of higher layers For example, a PUSCH-ConfigCommon IE (Information Element) or a RACH-ConfigCommon IE defined in the RRC layer may be used. Note that Msg3 is a message of a random access channel (RACH (Random Access Channel) procedure, and PUSCH may be used to transmit Msg3.

[0194] Furthermore, Msg1 may be transmitted via a PRACH (Physical Random Access Channel). Msg1 may be referred to as a PRACH Preamble. Msg2 may be transmitted via a PDSCH. Msg2 may be referred to as an RAR (Random Access Response). Msg3 may be referred to as an RRC Connection Request. Msg4 may be referred to as an RRC Connection Setup.

[0195] Notification to UE 200 via Msg2 RAR Any of the following methods may be applied:

[0196] (Alt 1): Notification to Enhanced UE by sending RAR with a different MAC configuration than that of normal UE. Enhanced UE may mean a UE that supports TBoMS.

[0197] (Alt 2): Notification of UL grant using TDRA. For example, an information element regarding channel estimation across multiple slots may be added to the TDRA table configured in RRC, and the information may be selected by DCI.

[0198] (Alt 3): Implicit notification using UL grant information. For example, it may be linked to a TPC (Transmit Power Control) command or MCS (Modulation and Coding Scheme). In this case, the linking method may be set by a predetermined rule or by the network (radio base station).

[0199] (Alt 4): Notification using reserved bit Fig. 18 shows a configuration example of MAC RAR according to operation example 7. As shown in Fig. 18, a reserved bit (R) included in MAC RAR may be used for the above-mentioned notification. For example, only whether TBoMS is in use or not may be notified using the reserved bit.

[0200] Furthermore, in the notification by higher layer signaling, TBoMS-related information may be added to the PUSCH-ConfigCommon information element TDRA table.

[0201] Alternatively, for notification via DCI format 0_0 with CRC scrambled by TC-RNTI (Temporary C (Cell)-RNTI), one of the following may be applied:

[0202] (Alt 1): TBoMS-related information is implicitly notified according to the CCE index where the DCI is placed. (Alt 2): TBoMS-related information is notified using reserved bits of the HARQ process number and New data indicator. (Alt 3): TBoMS-related information is implicitly notified by information notified by the DCI. For example, the related information may be linked to the TDRA, TPC command, or MCS. In this case, the linking method may be set by a predetermined rule or by the network (radio base station).

[0203] Alternatively, DCI with CRC scrambled by an RNTI for Enhanced UE may be used. The RNTI for Enhanced UE may be assigned by the RAR. Furthermore, TBoMS-related information may be reported by the DCI for Enhanced UE.

[0204] Furthermore, the UE 200 may report (notify) to the network (radio base station) whether or not to apply TBoMS when transmitting Msg3, or whether or not it can be applied, based on any of the following methods.

[0205] (Opt 1): Report together with applicability (or request) of repeated transmission of Msg3. When repeated transmission of Msg3 is performed, it may include whether TBoMS is applicable.

[0206] ・(Opt 2): Report independently of whether repeated transmission of Msg3 is applicable (or requested) ・(Opt 2-1): Allocate different initial bandwidth depending on whether it is applicable (or requested) ・(Opt 2-2): Use different RACH preamble depending on whether it is applicable (or requested) ・(Opt 2-3): Use different RACH occasion depending on whether it is applicable (or requested) ・(Opt 2-4): Use a specific OCC (Orthogonal Cover Code) pattern for Msg1 that is repeatedly transmitted depending on whether it is applicable (or requested)

[0207] (3.10) Operation Example 8 In this operation example, an operation relating to rate matching during TBoMS transmission will be described. Specifically, rate matching may be applied to each sequence transmitted in each slot.

[0208] UE 200 may perform rate matching for each sequence transmitted in each slot during TBoMS transmission. In this case, the slot may be only the slot in which the PUSCH is actually transmitted, or may be a resource designated by resource allocation.

[0209] Fig. 19 shows an example of slot allocation and a configuration of a redundancy version (RV) according to operation example 8. Fig. 19 shows an example in which UCI is multiplexed in slot 1 and the bit selection sequence is shortened.

[0210] The UE 200 may determine the starting point of bit selection of the sequence transmitted in each slot according to one of the following methods.

[0211] (Opt 1): Determine the starting point of bit selection so that it is a continuous sequence. For example, the first slot may be determined according to the RV. For subsequent slots, the last bit (or the bit next to the last bit) of the circular buffer extracted by bit selection in the previous slot may be used as the starting point.

[0212] (Opt 2): Determine the starting points of bit selection in each slot so that they are evenly spaced. For example, the first slot is determined according to the RV, and the starting points of other slots may be shifted from the starting point of the previous slot by the length of the sequence extracted by bit selection of a specific slot. In this case, the specific slot may be the first slot or the sequence with the shortest length extracted by bit selection.

[0213] (Opt 3): Bit selection based on the RV corresponding to each slot. In this case, a starting point different from that in 3GPP Releases 15 and 16 may be applied. For example, the mapping between each RV and the starting point may be changed only when applying to TBoMS. As an example of changing the mapping between each RV and the starting point, the starting point may be determined using the same method as in Opts 1 and 2. In this case, as described above, five or more RVs may be applied (see Opts A and B in Fig. 8).

[0214] (3.11) Operation Example 9 In this operation example, similar to Operation Example 8, rate matching during TBoMS transmission will be described. Specifically, rate matching may be applied to each sequence transmitted in X slots, which are specific slots (which may be single or multiple).

[0215] UE 200 may perform rate matching for each sequence transmitted in X slots during TBoMS transmission. In this case, the slots may be only slots in which PUSCHs are actually transmitted, or may be resources designated by resource allocation.

[0216] "X" may be determined based on a predetermined rule, an RRC parameter, or a combination of a predetermined rule and an RRC parameter. For example, X may be the number of consecutive UL slots based on the TDD pattern.

[0217] (Operation Example 9-1): Bit selection (Opt 1): Determine the starting point of bit selection so that it becomes a continuous series. The slot-by-slot approach in Opt 1 of Operation Example 8 may be changed to every X slots and applied.

[0218] (Opt 2): Determine the starting points of bit selection so that they are spaced equally in each slot. The slot-by-slot approach in Opt 2 of Operation Example 8 may be changed to every X slots and applied.

[0219] (Opt 3): A starting point is determined based on the RV corresponding to each X slot. In this case, a starting point different from that in 3GPP Releases 15 and 16 may be applied. For example, the mapping between each RV and the starting point may be changed only when applying to TBoMS. In this case, as mentioned above, five or more RVs may be applied (see Opts A and B in Fig. 8).

[0220] (Operation Example 9-2): Bit Interleaving When performing bit interleaving, the UE 200 may apply it to each sequence transmitted in each slot.

[0221] (3.12) Operation Example 10 In this operation example, as in Operation Example 8, an operation related to rate matching during TBoMS transmission will be described. Specifically, in this operation example, rate matching may be applied to all sequences transmitted by TBoMS.

[0222] During transmission by TBoMS, UE 200 may perform rate matching on sequences transmitted in all resources allocated to TBoMS. In this case, the slots may be only slots in which PUSCHs are actually transmitted, or may be resources designated by resource allocation.

[0223] When performing bit interleaving, UE 200 may apply rate matching to each sequence transmitted in each slot.

[0224] Alternatively, when performing bit interleaving, UE 200 may apply rate matching to each sequence transmitted in X slots.

[0225] "X" may be determined based on a predetermined rule, an RRC parameter, or a combination of a predetermined rule and an RRC parameter. For example, X may be the number of consecutive UL slots based on the TDD pattern.

[0226] (3.13) Operation Example 11 In this operation example, an operation related to notification of UE capability will be described.

[0227] Regarding TBoMS, the UE 200 may report the following information to the network as UE Capability Information.

[0228] -Whether repeated transmission of TBoMS PUSCH can be applied -Whether each RV extension can be applied when TBoMS is applied -Whether the new low SE MCS table can be applied when TBoMS is applied -Whether each frequency hopping pattern can be applied when TBoMS is applied -Whether TBoMS can be applied to Msg 3 PUSCH Furthermore, UE200 may report the following information to the network as UE Capability Information regarding rate matching in TBoMS.

[0229] - Applicability of options (Opt) for each operation example (operation examples 8 to 10) Applicability for each operation example may be reported individually, or applicability for multiple operations may be reported together. - Maximum number of slots in operation examples 8 and 9 - Maximum number of X slots in operation examples 9 and 10 Furthermore, UE200 may report the frequencies (which may be FR or bands) that it supports using one of the following methods.

[0230] - Supportability for all frequencies at once (supportability as a mobile station) - Supportability for each frequency - Supportability for each FR1 / FR2 - Supportability for each SCS Furthermore, UE200 may report the supported duplex method using any of the following methods.

[0231] ・Supportability as UE ・Supportability of each duplex method (TDD / FDD)

[0232] (4) Actions and Effects According to the above-described embodiment, the following actions and effects can be obtained. Specifically, according to the UE 200 (and the gNB 100) according to the above-described Operation Examples 1 to 8, it is possible to more efficiently realize TBoMS, which processes transport blocks (TBs) via a physical uplink shared channel (PUSCH) allocated to multiple slots.

[0233] In particular, according to the above-described operation example, it is possible to realize appropriate PUSCH allocation, TBS determination, code block determination, MCS table selection, frequency hopping, transmission of Msg3, and transmission of UE Capability Information, taking TBoMS into consideration.

[0234] (5) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

[0235] For example, in the above-described embodiment, the term transport block (TB) is used, but as will be described later, this refers to a block of predetermined data and may be replaced with another synonymous term, such as a data packet.

[0236] In the above-described embodiment, a demodulation reference signal (DMRS) used for channel estimation of a PUSCH (or a PUCCH) has been described, but any other reference signal may be used for channel estimation of a physical channel such as a PUSCH (or a PUCCH).

[0237] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0238] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0239] The block diagram ( FIG. 3 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., via wire, wireless, etc.) and these multiple devices. The functional block may be realized by combining the single device or multiple devices with software.

[0240] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0241] Furthermore, the above-described gNB100 and UE200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 20 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 20, the devices may be 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, etc.

[0242] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0243] Each functional block of the device (see FIG. 3) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0244] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0245] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0246] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0247] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

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

[0249] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0250] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0251] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0252] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0253] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0254] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0255] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

[0256] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0257] In the present disclosure, a specific operation described 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 having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0258] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.

[0259] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

[0260] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0261] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0262] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0263] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0264] The 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 be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0265] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0266] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0267] Furthermore, 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. For example, a radio resource may be indicated by an index.

[0268] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0269] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0270] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0271] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0272] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0273] A mobile station may also be referred to 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 terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0274] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include 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 Internet of Things (IoT) device such as a sensor.

[0275] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0276] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0277] A radio frame may consist of one or more frames in the time domain.

[0278] Each of the one or more frames in the time domain may be called a subframe, and the subframe may further be made up of one or more slots in the time domain.

[0279] A subframe may be of fixed time length (e.g., 1 ms) that is independent of numerology.

[0280] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

[0282] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0283] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0284] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0285] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0286] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0287] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0288] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0289] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0290] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.

[0291] The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may also be determined based on the numerology.

[0292] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

[0293] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0294] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0295] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0296] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0297] 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 the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0298] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.

[0299] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0300] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

[0301] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0302] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0303] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0304] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

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

[0306] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0307] 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 "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0308] 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 herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0309] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitting / receiving unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transmitting / receiving unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims

1. A transmitter for transmitting a transport block via a physical uplink shared channel spanning a plurality of slots; a control unit that performs rate matching for each sequence of the transport block transmitted in each of the plurality of slots, The control unit determines the start position of bit selection of the sequence transmitted in the first slot of the plurality of slots in accordance with a redundancy version of a circular buffer, and determines the start position of bit selection of the sequence transmitted in the slot following the first slot or later in accordance with the last bit extracted in the previous slot.

2. A terminal as described in claim 1, wherein the number of slots of the plurality of slots is received from the network via higher layer signaling.

3. A transmission step of transmitting a transport block via a physical uplink shared channel spanning a plurality of slots; a control step of performing rate matching for each sequence of the transport blocks transmitted in each of the plurality of slots; The control step determines a start position of bit selection of the sequence transmitted in a first slot of the plurality of slots in accordance with a redundancy version of a circular buffer, and determines a start position of bit selection of the sequence transmitted in a slot subsequent to the first slot in accordance with a last bit extracted in a previous slot. The wireless communication method of the terminal.

4. The terminal comprises: The transmission is carried out via a physical uplink shared channel spanning multiple slots. a transmitter for transmitting the port block to a base station; The transport block transmitted in each of the plurality of slots. a control unit that executes rate matching for each lock sequence; The control unit is configured to control the system The starting position of the column bit selection is determined according to the redundancy version of the circular buffer. and determining the sequence to be transmitted in the slot following the first slot and thereafter. The start position of the bit selection is determined based on the last bit extracted in the previous slot. The decision is based on The base station, via the physical uplink shared channel spanning the plurality of slots A receiving unit that receives the transport block from the terminal. system.