Terminals and wireless communication methods

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

[Technical Field]

[0001] This disclosure relates to a terminal and wireless communication method that support coverage extension. [Background technology]

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

[0003] For example, 3GPP Release-17 includes an agreement to consider coverage enhancement (CE) in NR (Non-Patent Document 1).

[0004] Furthermore, regarding coverage expansion, it has been agreed to consider methods for determining the time resources of TB processing over multi-slot PUSCH (TBoMS), which processes transport blocks (TBs) via physical uplink shared channels assigned to multiple slots, specifically PUSCH (Physical Uplink Shared Channel) (Non-Patent Literature 2). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "New WID on NR coverage enhancements", RP-202928, 3GPP TSG RAN meeting #90e, 3GPP, December 2020 [Non-Patent Document 2] "RAN1 Chairman's Notes", 3GPP TSG RAN WG1 Meeting #104-ee-Meeting, 3GPP, February 2021 [Overview of the Initiative]

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

[0007] Therefore, the following disclosure is made in view of these circumstances and aims to provide a terminal and wireless communication method that can more efficiently realize a TBoMS that processes transport blocks (TB) via physical uplink sharing channels (PUSCH) assigned to multiple slots.

[0008] One aspect of the present disclosure is a terminal (UE200) comprising a receiving unit (control signal / reference signal processing unit 240) that receives control information indicating the 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 a plurality of slots, wherein 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 (UE200) comprising a control unit (control unit 270) that allocates a physical uplink sharing channel across a plurality of slots, and a transmission unit (wireless signal transmission / reception unit 210) that transmits a data sequence via the physical uplink sharing channel, wherein the transmission unit repeatedly transmits the data sequence, after a plurality of code blocks have been linked together, via the physical uplink sharing channel.

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

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

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

[0013] One aspect of the present disclosure is a terminal (UE200) including a control unit (control unit 270) that allocates a physical uplink shared channel across a plurality of slots, and a transmission unit (radio signal transceiver 210) that transmits a data sequence via the physical uplink shared channel, wherein the control unit performs rate matching for each of the data sequences transmitted in a specific time region.

[0014] One aspect of the present disclosure includes receiving control information indicating an allocation in a time domain of a physical uplink shared channel, and allocating the physical uplink shared channel across a plurality of slots. In the step of allocating the physical uplink shared channel, a wireless communication method is used to determine a transport block transmitted via the physical uplink shared channel based on the control information.

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

Brief Description of Drawings

[0016] [Figure 1] FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10. [Figure 2] FIG. 2 is a diagram showing a configuration example of a wireless frame, subframe, and slot used in the wireless communication system 10. [Figure 3] FIG. 3 is a functional block configuration diagram of gNB 100 and UE 200. [Figure 4] FIG. 4 is a diagram showing an allocation example of PUSCH by TBoMS. [Figure 5] FIG. 5 is an explanatory diagram of problems in an allocation example of PUSCH (Type A repetition like TDRA) by TBoMS. [Figure 6] FIG. 6 is a diagram showing an allocation example of the PUSCH time domain according to Operation Example 1 (Opt 1, 2). [Figure 7] FIG. 7 is a diagram showing an allocation example of PUSCH (TB) according to Operation Example 2 (Alt 1-1-1). [Figure 8] FIG. 8 is a diagram showing a configuration example of a redundancy version (RV) according to Operation Example 2 (Alt 2-2). [Figure 9] Figure 9 shows an example of the calculation of Nsh symb related to operation example 3-1 (Opt 1). [Figure 10] Figure 10 shows an example of TB allocation related to operation example 4 (Alt 2). [Figure 11] Figure 11 shows an example of TB allocation related to operation example 4 (Alt 4-1). [Figure 12] Figure 12 shows an example of UL channel repetition related to operation example 6 (Opt 3). [Figure 13] Figure 13 shows an example of UL channel repetition related to operation example 6-1 (Opt 4). [Figure 14] Figure 14 shows an example of UL channel repetition related to operation example 6-2 (Opt 3, 4). [Figure 15] Figure 15 shows an example of UL channel repetition related to operation example 6-2 (Opt 5). [Figure 16] Figure 16 shows an example of UL channel repetition related to operation example 6-3 (Alt 1, 2). [Figure 17] Figure 17 shows an example of UL channel repetition related to operation example 6-3 (Alt 3, 4). [Figure 18] Figure 18 shows an example of the MAC RAR configuration related to Operation Example 7. [Figure 19] Figure 19 shows an example of slot allocation and redundancy version (RV) configuration related to operation example 8. [Figure 20] Figure 20 shows an example of the hardware configuration of the gNB100 and UE200. [Modes for carrying out the invention]

[0017] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0018] (1) Overall outline of the wireless communication system Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system in accordance with 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN20) and a terminal 200 (User Equipment 200, hereinafter referred to as UE200).

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

[0020] NG-RAN20 includes a wireless base station 100 (hereinafter referred to as gNB100). The specific configuration of the wireless communication system 10, including the number of gNBs and UEs, is not limited to the example shown in Figure 1.

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

[0022] The gNB100 is a radio base station compliant with NR standards and performs NR-compliant wireless communication with the UE200. The gNB100 and UE200 can support Massive MIMO, which generates a more directional beam by controlling radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication between the UE and multiple NG-RAN Nodes.

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

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

[0025] Furthermore, the wireless communication system 10 may also support higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands exceeding 52.6 GHz and 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. Furthermore, DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0027] Figure 2 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless 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 duration (and slot duration). Note that the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Also, the number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (for example, 480 kHz or 960 kHz, as shown in Figure 2).

[0029] The time direction (t) shown in Figure 2 may also be called the time domain, time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, frequency domain, resource block, resource block group, subcarrier, BWP (Band width part), subchannel, common frequency resource, etc.

[0030] The wireless communication system 10 can support coverage enhancement (CE) to broaden the coverage of the cells (or physical channels) formed by the gNB100. Coverage enhancement may provide mechanisms to increase the success rate of reception for various physical channels.

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

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

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

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

[0035] The UE200 can transmit DMRS signals that are assigned to (spanning) multiple slots, enabling the gNB100 to perform joint channel estimation using DMRS.

[0036] Furthermore, in the wireless communication system 10, TB processing over multi-slot PUSCH (TBoMS) may be applied for coverage expansion, which processes transport blocks (TBs) via PUSCHs assigned to multiple slots.

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

[0038] TDRA may be interpreted as resource allocation in the time domain of PUSCH as defined in 3GPP TS38.214. PUSCH's TDRA may also be interpreted as being defined by information elements (IE) of the Radio Resource Control Layer (RRC), specifically PDSCH-Config or PDSCH-ConfigCommon.

[0039] Furthermore, TDRA may be interpreted as resource allocation in the time domain of PUSCH as specified by Downlink Control Information (DCI).

[0040] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configuration of the UE200 will be described. Figure 3 is a functional block configuration diagram of the gNB100 and UE200.

[0041] As shown in Figure 3, the UE200 comprises a wireless signal transmission / reception 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 transmission / reception unit 260, and a control unit 270.

[0042] Note that Figure 3 shows only the main functional blocks relevant to the description of the embodiment, and the UE200 (gNB100) has other functional blocks (e.g., a power supply unit). Also, Figure 3 shows the functional block configuration of the UE200; please refer to Figure 19 for the hardware configuration.

[0043] The wireless signal transceiver 210 transmits and receives wireless signals in accordance with NR. By controlling the radio frequency (RF) signals transmitted from multiple antenna elements, the wireless signal transceiver 210 can support Massive MIMO, which generates a more directional beam; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication between the UE and each of the two NG-RAN Nodes.

[0044] Furthermore, the wireless signal transceiver 210 may transmit on the physical uplink shared channel. In this embodiment, the wireless signal transceiver 210 may constitute a transmission unit.

[0045] Specifically, the wireless signal transceiver 210 may transmit PUSCH to the network (gNB100). The wireless signal transceiver 210 may support repeated transmission of PUSCH.

[0046] Multiple types of repeated transmissions of 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 a PUSCH assigned within a slot is repeatedly transmitted. In other words, a PUSCH must consist of 14 symbols or less and cannot be assigned across multiple slots (adjacent slots).

[0047] On the other hand, Repetition type B may be interpreted as repeated transmission of a PUSCH that may be assigned 15 or more PUSCH symbols. In this embodiment, it is permissible to assign such a PUSCH across multiple slots.

[0048] Furthermore, the wireless signal transceiver 210 may repeatedly transmit uplink channels (UL channels) over a specific period of multiple slots or more. The uplink channels may include physical uplink sharing channels (PUSCH) and physical uplink control channels (PUCCH).

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

[0050] A specific period of multiple slots or more may be interpreted as a period relating to the repetition of PUSCH (or PUCCH). For example, a specific period may be indicated by the number of repetitions, or it may be the time during which a specified number of repetitions are performed.

[0051] Alternatively, the wireless signal transceiver 210 may repeatedly transmit the UL channel a specific number of times. Specifically, the wireless signal transceiver 210 may repeatedly transmit PUSCH (or PUCCH) multiple times.

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

[0053] Furthermore, the wireless signal transceiver 210 may repeatedly transmit the data sequence after multiple code blocks (CBs) have been concatenated via PUSCH. The term "data sequence" may be replaced with other synonymous terms such as "data block," "bit sequence," or "bit string." The CB may be a CB after Cyclic Redundancy Checksum (CRC) processing, CB splitting, channel coding, and rate matching.

[0054] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0055] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (such as gNB100). The modulation / demodulation 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 / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0057] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

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

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

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

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

[0062] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" can refer to data transmitted through a data channel.

[0063] Furthermore, the control signal / reference signal processing unit 240 may transmit capability information of the UE200 regarding the allocation of physical uplink shared channels (PUSCH) to the network. In this embodiment, the control signal / reference signal processing unit 240 may constitute a transmitting unit for transmitting capability information.

[0064] Specifically, the control signal / reference signal processing unit 240 can send UE Capability Information regarding the assignment of PUSCH (which may include Repetition) to the gNB100. Further details about the information will be provided later.

[0065] Furthermore, the control signal / reference signal processing unit 240 can receive control information indicating the allocation of PUSCH in the time domain. In this embodiment, the control signal / reference signal processing unit 240 may constitute a receiving unit.

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

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

[0068] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0069] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on Hybrid ARQ (Hybrid automatic repeat request).

[0070] The control unit 270 controls each functional block that constitutes the UE200. In particular, in this embodiment, the control unit 270 controls the transmission of UL channels, specifically PUSCH and PUCCH.

[0071] Specifically, the control unit 270 can hop the UL channel in the frequency direction in units of specific periods of multiple slots or more. Frequency hopping of the UL channel may also be called frequency hopping, and frequency hopping in units of specific periods of multiple slots or more may be called inter-slot frequency hopping. Hopping may mean that the frequency resources used change. In short, it may mean that the subcarrier, resource block, resource block group, or BWP changes.

[0072] Furthermore, the control unit 270 may hop the UL channel in the frequency direction using a specific number of repetitions of the UL channel as the unit. Specifically, the control unit 270 may perform frequency hopping using the number of repetitions of the specified UL channel as the unit, in other words, every predetermined number of repetitions.

[0073] When joint channel estimation in gNB100 is applied, if transmissions of UL channels (PUSCH and PUCCH) overlap (or collide), the control unit 270 may determine a frequency hopping pattern using available resources that avoid overlap when allocating resources to the UL channel (or its repetition), specifically at the timing of DCI reception.

[0074] Alternatively, if transmissions on UL channels (PUSCH and PUCCH) overlap, the control unit 270 may determine a hopping pattern using available resources that avoid 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] The control unit 270 may determine the assignment of DMRS transmitted on the UL channel, specifically on PUSCH, based on the repetition status of PUSCH, i.e., the number of repetitions, the repetition period, etc.

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

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

[0079] Note that "spanning multiple slots" may mean that PUSCH is assigned to two or more consecutive slots. Furthermore, symbols or subframes may be used as units instead of slots.

[0080] The control unit 270 may determine the size of the transport block (TB) transmitted via PUSCH based on the PUSCH configuration information 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, other information elements of the RRC layer may be used as long as they are related to the PUSCH configuration information, and the control unit 270 is not necessarily limited to the serving cell. The control unit 270 may also determine the size of the TB based on PUSCH configuration information from layers other than the RRC layer.

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

[0082] For example, the control unit 270 may divide one TB into multiple CBs (up to eight), similar to 3GPP Release-15, 16. Alternatively, the control unit 270 may change the maximum number of divisions to CBs depending on the number of slots (or symbols) to which PUSCH is assigned.

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

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

[0085] Alternatively, the control unit 270 may perform rate matching for each data sequence transmitted in a specific slot. Specifically, the 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 data sequences transmitted using resources to which a transport block (which may be a TBoMS) is allocated. Specifically, the control unit 270 may perform rate matching on sequences transmitted using all resources to which a TBoMS is allocated.

[0087] Furthermore, the DMRS transmission / reception and TBoMS functions described above may also be provided in the gNB100. For example, the gNB100 (wireless signal transmission / reception unit 210) may be configured as a receiver that receives UL channels repeatedly transmitted from the UE200 within a specific period. The wireless signal transmission / reception unit 210 of the gNB100 may receive UL channels that have hopped in the frequency direction, with the specific period as the unit.

[0088] Furthermore, the gNB100 (wireless signal transceiver 210) may receive a UL channel (e.g., PUSCH) from the UE200 that is repeatedly transmitted, i.e., Repetition is performed, a specific number of times. In this case, the gNB100 (wireless signal transceiver 210) may receive UL channels that have hopped in the frequency direction, with the specific number of transmissions as the unit.

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

[0090] Furthermore, the gNB100 (control unit 270) may perform TBoMS, which processes TB via UL channels allocated to multiple slots, that is, control related to the reception of UL channels such as PUSCH allocated across multiple slots.

[0091] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. The operation related to channel estimation of the uplink channel for the purpose of coverage expansion performance will be described.

[0092] (3.1) Premise As mentioned above, TBoMS can be interpreted as a technique for transmitting a single transport block using multiple slots.

[0093] Figure 4 shows an example of PUSCH allocation by TBoMS. Specifically, Figure 4 shows an example of PUSCH allocation by TBoMS according to Type A repetition like TDRA and Type B repetition like TDRA. Note that Type A and B may refer to the repetition types A and B described above.

[0094] TBoMS may have the following advantages:

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

[0096] • A longer code sequence improves the channel coding gain.

[0097] • Compared to sending multiple TBs, the amount of header data in the upper layers can be reduced.

[0098] Furthermore, in 3GPP Release-15 and similar standards, when determining the size of the TB (TBS) transmitted via PUSCH (and PDSCH), the number of REs (N) is first considered. RE ) is calculated, and then the calculated N RE Using the number of information bits (N info ) is calculated. Then, TBS is calculated N info The decision is based on the following: Here, TBS's decision assumes that PUSCH will be allocated to only one slot.

[0099] Figure 5 illustrates the problems in an example of PUSCH allocation using TBoMS (Type A repetition like TDRA). As shown in Figure 5, in the case of TBoMS, the TBS size corresponding to PUSCH allocated across multiple slots (which may be consecutive) needs to be determined.

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

[0101] • (Example 1): Method for allocating time domains in PUSCH when TBoMS is applied • (Example 2): How to send 1TB data using multiple slots • (Operation Example 3): Method for determining TBS when TBoMS is applied • (Example of operation 3-1): N RE When calculating, expand the RE count to include multiple slots instead of just one. • (Example of operation 3-2): Based on the SLIV (Start and Length Indicator Value) of TDRA, N RE Calculate and N according to TDRA info Calculate • (Example of operation 4): Method for determining the number of code blocks during TBoMS • (Example 5): How to select an MCS table when using TBoMS • (Operation Example 6): Frequency hopping when using TBoMS • (Example of operation 6-1): frequency hopping (Type A repetition like TDRA) • (Example of operation 6-2): frequency hopping (Type B repetition like TDRA) • (Example 6-3): Hopping frame when dropping a Repetition resource • (Operation Example 6-4): Method for receiving frequency hopping-related information • (Example of operation 7): Application to Msg3 PUSCH • (Example 7-1): Applicability of Joint channel estimation in Msg3 • (Example of operation 8): Notification of UE capability

[0102] (3.3) Example of operation 1 This example demonstrates the operation of allocating the PUSCH time domain when TBoMS is applied.

[0103] When the UE200 performs TDRA of TBoMS, it may notify the network (wireless base station) of the PUSCH time domain allocation method by one of the following means:

[0104] (Opt 1): Notify the system to consolidate multiple assigned Repetitions into a single Repetition in TBoMS PUSCH. (Opt 2): Independent of Repetition, the number of slots (or number of repetitions) to which a PUSCH used for transmitting one TB (1TB) will be allocated will be notified (or the network may notify the UE200 and the UE200 may operate based on that notification (the same applies below)).

[0105] Figure 6 shows an example of PUSCH time domain allocation related to Operation Example 1 (Opt 1, 2). As shown in Figure 6, multiple repetitions may be integrated into a single repetition (Opt 1), and a 1TB PUSCH may be allocated to multiple slots regardless of the number of repetitions.

[0106] • (Opt 2-1): The number of slots (or repetitions) is notified by signaling from the upper layer. In this case, the Repetition count may be the actual number of Repetitions to be allocated, or the number of Repetitions before the Repetition resource is dropped. For this signaling, for example, the RRC layer's PUSCH-Config IE or ConfiguredGrantConfig IE may be used.

[0107] • (Opt 2-2): Notify the number of slots (or repetitions) using DCI. In this case, the number of slots may be either the number of slots that can actually be allocated or the number of consecutive slots before the Repetition resource was dropped.

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

[0109] (Opt 2-2-2): Implicitly notify using DCI For example, TBoMS-related information may be linked to a DCI field and notified. Alternatively, TBoMS-related information may be linked to the 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 it may be determined by a predetermined rule.

[0110] (3.4) Example of operation 2 This example describes the operation of transmitting 1TB using multiple slots. The UE200 may transmit 1TB using multiple slots in one of the following ways:

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

[0112] (Alt 1-1): Send a 1-bit sequence via multiple pushers. • (Alt 1-2): Assign one PUSCH to multiple slots. (Alt 2): Repeatedly transmit the sequence after CB concatenation. Multiple sequences may be allocated using the specified resources across multiple slots (similar to Repetition). In this case, the same sequence may be sent repeatedly, or different sequences may be sent.

[0113] The processes 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): Sends a bit sequence divided equally through each PUSCH. (Alt 1-1-2): Determine the bit length to send according to the symbol length of each PUSCH. For example, if segmentation occurs in a Type B repetition like TDRA, bit sequences of different bit lengths may be transmitted in each repetition.

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

[0116] · (Alt 2-1): Use the conventional bit selection during rate matching · (Alt 2-2): Apply the new bit selection during 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 to which the existing starting point is allocated, add RVs to which different starting points are allocated · (Opt B): Allocate a new starting point to each RV FIG. 8 shows a configuration example of redundancy version (RV) according to Operation Example 2 (Alt 2-2). As shown in FIG. 8, RVs (RV0 to 3) to which the existing starting point is allocated and RVs (RV4, 5) to which different starting points are allocated may be used (Opt A), or a new starting point may be allocated to each RV (Opt B).

[0118] (3.5) Operation Example 3 In this operation example, the operation regarding the determination of TBS when applying TBoMS will be described. Specifically, the determination of TBS corresponding to TBs spanning multiple slots will be described.

[0119] · (Opt 1): When calculating N RE extend it to the number of REs in multiple slots instead of one slot (Operation Example 3-1) Specifically, as follows, N RE (N' RE ) may be calculated.

[0120] [Equation]

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

[0122] (Opt 2): Based on SLIV of TDRA, N RE Calculate N according to TDRA info Calculate (Example 3-2) • (Alt 1): Type A repetition like TDRA, N in 1 slot RE Calculate the number of repeated transmissions, and N info Multiply during calculation In this case, the number of slots may be calculated taking into account the slots to be dropped (by multiplying by the number of assignable slots). If a TDD pattern, SFI (Slot Format Indication) / CI (Cancel Indication) exists, it may be changed from the value notified by the TBS being sent or received.

[0123] • (Alt 2): In the case of Type B repetition like TDRA, there are N repetitions of one. RE Calculate the number of repeated transmissions, and N info Multiply during calculation (Opt 1): Multiply by the actual repetition count. In this case, the number of actual repetitions that have not been segmented may also be multiplied.

[0124] (Opt 2): Multiply by the nominal repetition count.

[0125] Note that "actual repetition" refers to the final repetition sent, while "nominal repetition" can be interpreted as the repetition notified / assigned by the gNB to the UE. For example, the actual repetition and nominal repetition may change due to the following factors:

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

[0127] (ii) If a nominal repetition is located at a slot boundary, the nominal repetition may be split at the slot boundary and transformed into two actual repetitions.

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

[0129]

number

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

[0131] In this case, N PRB oh It may be calculated by any of the following methods:

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

[0133] (Opt 1-3): Add a new parameter, and when using TBoMS, N will be based on that parameter. PRB oh Decided (Opt 1-4): Add a new parameter, and when using TBoMS, N will be calculated based on that parameter and xOverhead. PRB oh Decided (Opt 2): N based on the number of slot symbols to which TBoMS applies. PRB oh Setting (Opt 2-1): Multiply xOverhead by the number of slots to which resources are allocated (Type A repetition like TDRA) • (Opt 2-2): Multiply the number of repeated transmissions by xOverhead (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 have not been divided may be multiplied.

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

[0136] (Opt 2-3): Calculated based on TDRA's SLIV, the number of symbols to assign, the total number of assigned symbols, and xOverhead. For example, it may be calculated as (xOverhead) × (total number of symbols) / (SLIV of TDRA and the number of symbols to be assigned).

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

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

[0139] • (Alt 1): Changes the number of symbols (REs) for all resources to which the resource is allocated. In this case, the number of symbols (REs) may be calculated considering the TDD pattern, SFI, and CI.

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

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

[0142] (Opt 2): Multiply by the nominal repetition count.

[0143] Figure 9 shows N related to Operation Example 3-1 (Opt 1). sh symb An example of the calculation is shown below. As shown in Figure 9, the number of symbols in multiple slots (18) may be calculated.

[0144] (3.6) Example of operation 4 This example demonstrates the process of determining the number of code blocks during TBoMS.

[0145] The 1TB related to TBoMS may be partitioned into CBs by one of the following methods:

[0146] • (Alt 1): When using TBoMS, do not split the CB. Regardless of maxCodeBlockGroupsPerTransportBlock set by RRC, do not split into CBs. (Alt 2): Similar to 3GPP Release 15 and 16, if 1TB is to be divided into multiple CBs (up to 8 CBs), the maximum number of maxCodeBlockGroupsPerTransportBlock may be increased. Also, the maximum number of CBs when using TBoMS may be set individually.

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

[0148] • (Alt 4): Set the number of CBs according to the number of Repetitions when allocating resources. Figure 10 shows an example of TB allocation related to Operation Example 4 (Alt 2). As shown in Figure 10, when maxCodeBlockGroupsPerTransportBlock = 4, one TB spanning 3 slots may be divided into 4 CBs.

[0149] • (Alt 4-1): Multiply the number of repeating placements by the maximum number of counterbonds. • (Alt 4-2): Set the number of repeating placements to the maximum number of counterbores. Furthermore, Alt 3 and Alt 4 may be limited to a maximum of 8 CBs so that they can be handled by conventional DCI.

[0150] Figure 11 shows an example of TB allocation related to Operation Example 4 (Alt 4-1). As shown in Figure 11, if 1TB spans 3 slots, the maximum number of CBs may be set to 6, and if it spans 2 slots, the maximum number of CBs may be set to 4.

[0151] (3.7) Example of operation 5 This example describes the operation related to MCS table selection when using TBoMS. Regarding the MCS table when using TBoMS, one of the following operations may apply.

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

[0153] • (Alt 2): When using TBoMS, enable the use of a new low SE MCS table. Specifically, when using TBoMS, a new MCS table may be used. When using C-RNTI, 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 using MCS-C-RNTI, any of the following MCS tables may be specified by predetermined rules, higher-layer signaling, or DCI.

[0155] • qam 64 low SE MCS table • New MCS table Furthermore, the MCS table may be implicitly selected depending on the MCS index, TDRA, or transmit power.

[0156] (3.8) Example of operation 6 (3.8.1) Example of operation 6-1 This example demonstrates the operation of frequency hopping when using TBoMS.

[0157] When TBoMS is applied, the UE200 may determine the hopping pattern for the UL channel from the following hopping patterns, according to the network (wireless base station) or predefined rules (settings). Note that the UL channel may mean either PUSCH or PUCCH (the same applies hereinafter). The UL channel may also include repeated PUSCH or PUCCH.

[0158] Specifically, when UE200 applies Type A repetition like TDRA or uses PUCCH, it may determine one of the following hopping patterns:

[0159] (Opt 1): Frequency hopping per slot (Opt 2): Frequency hopping within the slot (Opt 3): Frequency hopping only once within a Repeat transmission. (Opt 3-1): Calculate a unique hop duration based on the number of repeated transmissions. In this case, frequency hopping may be disabled based on the number of repeated transmissions on the UL channel. The number of repetitions may be the actual number of repetitions to be allocated, or the number of repetitions before the drop of the repetition resource. Note that the drop of a repetition resource may be interpreted as a resource (time resource and / or frequency resource) that cannot be allocated due to a conflict (overlapping allocation) with a resource on another UL channel.

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

[0161] • (Opt 3-2): Notify the slot position where frequency hopping will be performed. For example, UE200 may notify the network of duration per hop = X slots (X repetitions), and after sending X repetitions (X repetitions, the same applies hereafter), it may perform frequency hopping. Alternatively, the network may notify UE200 of this, and UE200 may operate based on this notification (the same applies hereafter).

[0162] Furthermore, the number of slots can be either the actual number of slots allocated by Repetition, or the number of slots before the Repetition resource is dropped.

[0163] Figure 12 shows an example of a UL channel repetition related to Operation Example 6 (Opt 3). As shown in Figure 12, the hop period may be determined as floor(Repetition (Rep) count (6) / 2)=3. In Figure 12, each frame in the time (t) direction may be interpreted as corresponding to a slot (however, symbols may also be used) (the same applies below).

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

[0165] (Opt 4): Frequency hopping per X slot • (Opt 4-1): Duration per hop is notified from the network. For example, if the duration per hop is specified as "X slots", then frequency hopping may be performed for every X slots.

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

[0167] (Opt 4-3): Determine duration per hop based on the number of repeated transmissions. (Opt 4-4): Determine the hopping pattern based on the number of repetitions and the number of slots (or 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) Example of operation 6-2 This example demonstrates the behavior of frequency hopping (Type B repetition like TDRA) when TBoMS is applied.

[0169] The UE200 may determine the hopping pattern for the UL channel from the following hopping patterns, according to the network (wireless base station) or predefined rules.

[0170] Specifically, when applying Type B repetition like TDRA, UE200 may determine one of the following hopping patterns:

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

[0172] As shown in Figure 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 Figure 14, in the case of Type B repetition like TDRA, multiple repetitions (Rep) may be repeated within a slot, and multiple repetitions may be assigned to the same slot.

[0173] (Opt 5): X Frequency hopping with each repetition • (Opt 5-1): Duration per hop is notified from the network. For example, the UE200 can notify the duration per hop = X repetitions and perform frequency hopping for every X repetitions.

[0174] (Opt 5-2): Determine the hopping pattern based on the number of slots (or symbols) to which joint channel estimation is applied. For example, if the time window size is 3 slots, frequency hopping may be performed every 3 slots. The time window size may be the 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 related to operation example 6-2 (Opt 5). As shown in Figure 15, frequency hopping may occur every 3 slots. Also, as shown in Figure 15, the hopping timing may be within (midway through) a slot, rather than at the slot boundary.

[0176] (3.8.3) Example of operation 6-3 This example describes the behavior regarding the hopping pattern when a Repetition resource is dropped when TBoMS is applied. Figure 16 shows an example of a Repetition for a UL channel related to example 6-3 (Alt 1, 2).

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

[0178] • (Alt 1): Apply hopping pattern without considering resource conflicts. In this case, the hopping pattern may be applied on a slot-by-slot basis without considering the possibility of resources being dropped. For example, even if the 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 line).

[0179] (Alt 2): Apply hopping pattern based on the resources actually being sent. In this case, a hopping pattern may be applied based on the resources used to transmit 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; the dropped Repetition resource (dotted box) is excluded, so the resources in the frequency direction from slot #3 onwards are different from Alt. 1).

[0180] Furthermore, when applying a hopping pattern as described later, or when specifying the number of repeated transmissions based on the number of available resources, Alt 1 and 2 may be set separately.

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

[0182] • (Alt 3): When allocating resources, apply the hopping pattern based on the available Repetition resources. In this case, the resources that can be allocated may be determined according to the reason for the collision. For example, symbols for TDD patterns and SS / PBCH blocks (Synchronization Signal / Physical Broadcast Channel blocks) may be considered, but collisions with repeated transmissions of SFI (Slot Format Indication) / CI (Control Information) / PUCCH may not be considered. Alternatively, drops of Repetition resources known to the radio base station (gNB100) may be considered, but drops that the radio base station cannot determine may not be considered.

[0183] • (Alt 4): When sending the first Repetition, apply the hopping pattern to the assignable Repetition resource. In this case, the resources that can be allocated may be determined according to the reason for the time collision. Similar to Alt 3, for example, symbols of the TDD pattern and SS / PBCH block may be considered, but collisions with repeated transmissions of SFI / CI / PUCCH may not be considered. Alternatively, drops of Repetition resources known to the radio base station may be considered, but drops that the radio base station cannot determine may not be considered.

[0184] (3.8.4) Example of operation 6-4 In this example, the UE200 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 field In this case, the linking (correspondence) between frequency hopping-related information and DCI fields may be done using signaling at a higher layer, or it may follow predefined rules (settings).

[0186] (Opt 1-2): In the upper layer, add frequency hopping-related information elements to the TDRA table and determine them using DCI. • (Opt 1-3): Information related to implicit frequency hopping by DCI fields For example, frequency hopping-related information may be associated with a DCI field. Alternatively, frequency hopping-related information may be associated with the CCE (Control channel element) index where the DCI for resource allocation is located.

[0187] (Opt 2): Upper layer signal For example, a hopping pattern may be selected based on frequency hopping-related information received at RRC.

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

[0189] The UE200 may also set the hopping pattern by one of the following methods.

[0190] • The number of slots to which joint channel estimation is applied and the hop duration parameter can be set separately or together. • Set separate or common parameters for Type A like repetition TDRA and Type B like repetition TDRA. • Type B like repetition: Set the hop duration of the TDRA separately or using a common parameter for the number of slots and the number of repetitions.

[0191] (3.9) Example of operation 7 This example demonstrates the operation of applying TBoMS to Msg3 PUSCH.

[0192] The UE200 may receive relevant information for the TBoMS for Msg3 initial transmission based on any of the following methods or combinations. In this case, the TBoMS settings may differ depending on the frequency (bandwidth) used by the UE.

[0193] • Notification to UE200 via signaling in the upper layer For example, PUSCH-ConfigCommon IE (Information Element) or RACH-ConfigCommon IE, as defined in the RRC layer, may be used. Note that Msg3 is a message for the Random Access Channel (RACH) procedure, and PUSCH may be used to send Msg3.

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

[0195] • Notification to UE200 via Msg2 RAR Any of the following methods may be applied.

[0196] (Alt 1): Enhanced UEs are notified by sending RARs with a different MAC configuration than regular UEs. Enhanced UE can be defined as a UE that supports TBoMS.

[0197] • (Alt 2): Notification of UL grant using TDRA For example, information elements related to channel estimation spanning multiple slots may be added to the TDRA table set up in RRC, and this information may be selected by DCI.

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

[0199] • (Alt 4): Notification using reserved bits Figure 18 shows an example of the MAC RAR configuration related to Operation Example 7. As shown in Figure 18, the reserved bits (R) included in the MAC RAR may be used for the notification described above. For example, only the presence or absence of TBoMS may be notified using the reserved bits.

[0200] Additionally, in notifications via signaling at higher layers, TBoMS-related information may be added to the PUSCH-ConfigCommon information element TDRA table.

[0201] Alternatively, in notifications via DCI format 0_0 with CRC scrambled by TC-RNTI (Temporary C (Cell)-RNTI), either of the following may apply:

[0202] • (Alt 1): Implicitly notifies TBoMS-related information depending on the CCE index where DCI is located. • (Alt 2): TBoMS-related information is notified using the reserved bits of the HARQ process number and New data indicator. • (Alt 3): Implicitly notified by information provided by DCI For example, relevant information may be linked to TDRA, TPC command, or MCS. In this case, the method of linking may be set by predetermined rules or a network (wireless base station).

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

[0204] Furthermore, the UE200 may report (notify) the network (wireless base station) whether or not TBoMS is applied when transmitting Msg3, or whether or not it is applicable, based on one of the following methods.

[0205] • (Opt 1): Report whether (or request) repeated transmission of Msg3 is applicable. When repeatedly sending Msg3, it may be possible to include the application of TBoMS.

[0206] • (Opt 2): Report independently of whether or not repeated transmission of Msg3 is applicable (or requested). (Opt 2-1): Allocate different initial bandwidths depending on applicability (or requirements). (Opt 2-2): Use different RACH preambles depending on applicability (or requirements). (Opt 2-3): Use different RACH occasions depending on applicability (or requirements). • (Opt 2-4): Use a specific OCC (Orthogonal Cover Code) pattern in Msg1, which is sent repeatedly depending on its applicability (or request).

[0207] (3.10) Example of operation 8 This example describes the operation of rate matching during TBoMS transmission. Specifically, rate matching may be applied to each sequence transmitted in each slot.

[0208] The UE200 may perform rate matching for each sequence transmitted in each slot during TBoMS transmission. In this case, the slots may be only those slots on which PUSCH is actually transmitted, or they may be resources specified by resource allocation.

[0209] Figure 19 shows an example of slot allocation and redundancy version (RV) configuration related to operation example 8. In Figure 19, an example is shown where UCI multiplexing occurs in Slot 1, resulting in a shorter bit selection sequence.

[0210] The UE200 may determine the starting point for bit selection of the sequence transmitted in each slot according to one of the following methods:

[0211] (Opt 1): Determine the starting point of the bit selection so that it forms a continuous sequence. For example, the first slot may be determined according to the RV. For subsequent slots, the last bit (or the bit after 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 so that the bit selection starting points are evenly spaced in each slot. For example, the first slot may be determined according to the RV, and the starting point of the other slots may be shifted from the starting point of the previous slot by the length of the sequence extracted by the bit selection of that particular slot. In this case, the particular slot may be the first slot or the sequence with the shortest sequence length extracted by the bit selection.

[0213] (Opt 3): Bit selection based on RV corresponding to each slot In this case, a different starting point than that used 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 it to TBoMS. As an example of changing the mapping between each RV and the starting point, the starting point may be determined in the same way as in Opts 1 and 2. In this case, as mentioned above, five or more RVs may be applied (see Opts A and B in Figure 8).

[0214] (3.11) Example of operation 9 In this example, as in Example 8, we will explain the operation related to rate matching during TBoMS transmission. Specifically, rate matching may be applied to each sequence transmitted in a specific slot (one or more) called slot X.

[0215] The UE200 may perform rate matching for each sequence transmitted in the X slot during TBoMS transmission. In this case, the slots may be only those slots on which PUSCH is actually transmitted, or they may be resources specified by resource allocation.

[0216] "X" may be determined based on a predetermined rule / RRC parameter / a combination of a predetermined rule and 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 as to form a continuous series Each slot in Opt 1 of Operation Example 8 may be changed to each X slot and applied.

[0218] ·(Opt 2): Determine the starting point so that the starting points of bit selection are equally spaced in each slot Each slot in Opt 2 of Operation Example 8 may be changed to each X slot and applied.

[0219] ·(Opt 3): Determine the starting point based on the RV corresponding to each X slot. At this time, a starting point different from that in 3GPP Release 15 and 16 may be applied. For example, the mapping between each RV and the starting point may be changed only when applied to TBoMS. Note that, at this time, as described above, five or more RVs may be applied (see Opt A and B in Figure 8).

[0220] ·(Operation Example 9-2): Bit Interleaving When performing bit interleaving, UE200 may apply it to each series transmitted in each slot.

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

[0222] When transmitting by TBoMS, UE200 may perform rate matching for the sequences transmitted in all the resources allocated by TBoMS. At this time, the slot may be only the slot in which PUSCH is actually transmitted, or may be the resources specified by the resource allocation.

[0223] When performing bit interleaving, UE200 may apply rate matching for each sequence transmitted in each slot.

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

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

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

[0227] Regarding TBoMS, UE200 may report the following content 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 a 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 Also, regarding rate matching in TBoMS, UE200 may report the following content to the network as UE Capability Information.

[0229] • Whether the options (Opt) can be applied to each operation example (Operation Examples 8-10) You may report the applicability of each operation example individually, or you may report the applicability of multiple operations together. • Maximum number of slots in operation examples 8 and 9 • Maximum number of X slots in operation examples 9 and 10 Furthermore, the UE200 may report the supported frequencies (FR or band) in one of the following ways:

[0230] • Whether all frequencies can be used simultaneously (whether it can be used as a mobile station) • Availability of support for each frequency • Availability of support for FR1 / FR2 • Availability of support for each SCS Furthermore, the UE200 may report the corresponding duplex scheme by any of the following methods:

[0231] • Whether UE can handle it • Compatibility with each duplexing method (TDD / FDD)

[0232] (4) Action and Effects According to the embodiments described above, the following effects can be obtained. Specifically, the UE200 (and gNB100) according to the operation examples 1 to 8 described above can more efficiently realize a TBoMS that processes transport blocks (TB) via physical uplink sharing channels (PUSCH) assigned to multiple slots.

[0233] In particular, the above-mentioned example of operation makes it possible to achieve appropriate placement of PUSCHs considering TBoMS, TBS determination, code block determination, MCS table selection, frequency hopping, transmission of Msg3, and transmission of UE CapabilityInformation.

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

[0235] For example, in the above-described embodiments, the term "transport block (TB)" has been used. However, as will be described later, it is a block of predetermined data and may be replaced with another synonymous term such as a data packet.

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

[0237] In addition, in the above description, "configure", "activate", "update", "indicate", "enable", "specify", "select" may be mutually interchanged. Similarly, "link", "associate", "correspond", "map" may be mutually interchanged, and "allocate", "assign", "monitor", "map" may also be mutually interchanged.

[0238] Furthermore, "specific", "dedicated", "UE-specific", "UE-dedicated" may be mutually interchanged. Similarly, "common", "shared", "group-common", "UE-common", "UE-shared" may be mutually interchanged.

[0239] Furthermore, the block diagram (Figure 3) used in the description of the embodiments above shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Moreover, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0240] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0241] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 20 shows an example of the hardware configuration of the device. As shown in Figure 20, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0242] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

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

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

[0245] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0246] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line.

[0247] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.

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

[0249] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0250] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0251] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

[0254] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0255] Each aspect / embodiment described herein may be applied to at least one of the following: Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0256] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0257] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0258] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0259] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.

[0260] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0261] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0262] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0263] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0264] The information, signals, etc. described in this disclosure may be represented using any of the various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0265] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0266] The terms “system” and “network” as used in this disclosure are interchangeable.

[0267] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

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

[0269] In this disclosure, terms such as "Base Station (BS)," "wireless 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 house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also 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 a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

[0272] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" 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 appropriate term.

[0274] At least one of the base station and the mobile station may be called 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 body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (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 be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0275] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, each aspect / embodiment of this 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), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.

[0276] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0277] A wireless 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. A subframe may further consist of one or more slots in the time domain.

[0279] Subframes may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0280] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes 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 or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may also be a time unit based on neurology.

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

[0283] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0284] For example, one subframe may be called a Transmit Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a 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 unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0286] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0287] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit of scheduling may be controlled.

[0288] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0289] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0291] The number of subcarriers included in the RB may be the same regardless of the neurology, for example, it may be 12. The number of subcarriers included in the RB may be determined based on the neurology.

[0292] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0293] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

[0295] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology on a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0296] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0297] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0298] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0299] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0301] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

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

[0303] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

[0304] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0305] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

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

[0307] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." Furthermore, the term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted in the same way as "different."

[0308] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of Symbols]

[0309] 10 Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transmission and reception unit 220 Amplifier section 230 Modulation / Demodulation Section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission / reception 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 unit that transmits transport blocks via a physical uplink sharing channel spanning multiple slots, Each of the plurality of slots includes a control unit that performs rate matching for each sequence of transport blocks transmitted, The control unit determines the starting position of the bit selection sequence transmitted in the first slot of the plurality of slots according to the redundancy version of the circular buffer, determines the starting position of the bit selection sequence transmitted in the slot following the first slot based on the last bit extracted in the previous slot, and hops the physical uplink shared channel in the frequency direction in units of the number of slots notified by signaling of the upper layer.

2. The terminal according to claim 1, wherein the number of slots of the plurality of slots is received from the network via signaling at the upper layer.

3. A transmit step that transmits a transport block over a physical uplink shared channel spanning multiple slots, The control step includes performing rate matching for each sequence of transport blocks transmitted in each of the plurality of slots, A wireless communication method for a terminal, wherein the control step determines the starting position of the bit selection of the sequence transmitted in the first slot of the plurality of slots according to the redundancy version of the circular buffer, determines the starting position of the bit selection of the sequence transmitted in the slot following the first slot based on the last bit extracted in the previous slot, and hops the physical uplink shared channel in the frequency direction in units of the number of slots notified by signaling of the upper layer.

4. The device is, A transmitting unit that transmits transport blocks to the base station via a physical uplink sharing channel spanning multiple slots, Each of the plurality of slots includes a control unit that performs rate matching for each sequence of transport blocks transmitted, The control unit determines the starting position of the bit selection of the sequence transmitted in the first slot of the plurality of slots according to the redundancy version of the circular buffer, determines the starting position of the bit selection of the sequence transmitted in the slot following the first slot based on the last bit extracted in the previous slot, and hops the physical uplink shared channel in the frequency direction in units of the number of slots notified by signaling of the upper layer. The aforementioned base station is A system comprising a receiving unit that receives the transport block from the terminal via the physical uplink sharing channel spanning the plurality of slots.

Images