Terminal, base station, wireless communication system, and wireless communication method

Abstract

This terminal comprises: a reception unit that executes repeated reception of a downlink channel; and a control unit that assumes the number of times of expansion as the number of times of repetition of the downlink channel.

Description

Terminal, base station, wireless communication system, and wireless communication method

[0001] The present disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method that support repeated transmission of a downlink channel.

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

[0003] In 3GPP Release 18, an extension of downlink coverage is being considered, assuming a non-terrestrial network (NTN) (see, for example, Non-Patent Document 1).

[0004] “Revised WID: NR NTN (Non-Terrestrial Networks) enhancements”, RP-221819, 3GPP TSG RAN Meeting #96, 3GPP, June 6-9, 2022

[0005] Under the above-mentioned background, the inventors have conducted extensive research and found that it is necessary to extend the number of repeated transmissions of the downlink channel in order to extend the downlink coverage assuming NTN.

[0006] Therefore, the present disclosure has been made to solve the above-mentioned problems, and aims to provide a terminal, a base station, a wireless communication system, and a wireless communication method that can appropriately realize the expansion of downlink coverage even when NTN is assumed.

[0007] The disclosed aspect is a terminal including a receiver that performs repeated reception of a downlink channel, and a controller that assumes an extended number of times as the number of times the downlink channel is repeated.

[0008] The disclosed aspect is a base station including a transmitter that performs repeated transmission of a downlink channel, and a controller that assumes an extended number of times as the number of times the downlink channel is repeated.

[0009] The disclosed aspect is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises a receiving unit that performs repeated reception of a downlink channel and a control unit that assumes an extended number of times as the number of repetitions of the downlink channel.

[0010] The disclosed aspect is a wireless communication method including: a step A of performing repeated reception of a downlink channel; and a step B of assuming an extended number of times as the number of times of repetition of the downlink channel.

[0011] FIG. 1 is a diagram illustrating an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram illustrating a frequency range used in the wireless communication system 10. FIG. 3 is a diagram illustrating an example configuration of a radio frame, a subframe, and a slot used in the wireless communication system 10. FIG. 4 is a functional block configuration diagram of a UE 200. FIG. 5 is a functional block configuration diagram of a gNB 100. FIG. 6 is a diagram illustrating an overview of operation examples. FIG. 7 is a diagram illustrating operation example 1. FIG. 8 is a diagram illustrating operation example 2. FIG. 9 is a diagram illustrating operation example 3. FIG. 10 is a diagram illustrating operation example 3. FIG. 11 is a diagram illustrating operation example 4. FIG. 12 is a diagram illustrating operation example 4. FIG. 13 is a diagram illustrating operation example 6. FIG. 14 is a diagram illustrating an example of the hardware configuration of a gNB 100 and a UE 200. FIG. 15 is a diagram illustrating an example configuration of a vehicle 2001.

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

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

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

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

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

[0017] The gNB100 is a radio base station conforming to 5G, and performs 5G radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates on two or more transport blocks between the UE and each of two NG-RAN nodes.

[0018] In the embodiment, a non-terrestrial network (hereinafter, NTN) may be assumed. In the NTN, a non-terrestrial network such as an artificial satellite 150 (hereinafter, satellite 150) is used to provide services to areas that cannot be covered by a terrestrial network (hereinafter, TN) due to cost or other reasons. The NTN can provide more reliable services. For example, the NTN is expected to be applied to IoT (Internet of Things), ships, buses, trains, and critical communications. The NTN also has scalability through efficient multicast or broadcast.

[0019] The satellite 150 may have the function of a relay station device, and the relay method may be either a transparent type or a regenerative type.

[0020] A network including the gNB 100 and the UE 200 without including a non-terrestrial network may be referred to as a terrestrial network (TN) in contrast to an NTN. The UE 200 may communicate with the NG-RAN 20 via the NTN, or may communicate with the NG-RAN 20 via the TN (i.e., without going through the satellite 150).

[0021] The satellite 150 may also have the functionality of a gNB (radio base station). The type of satellite 150 is not particularly limited, and may be, for example, a geostationary orbit satellite (GEO) or a low earth orbit satellite (LEO). Alternatively, a high-altitude platform station (HAPS) may be used. The satellite 150 is not necessarily limited to these satellites, and may be interpreted as including spaceborne / airborne.

[0022] The gNB 100 may include an NTN gateway (not shown), which transmits downlink (DL) signals to the satellite 150. The NTN gateway receives uplink (UL) signals from the satellite 150.

[0023] The satellite 150 relays downlink signals received from the NTN gateway to the UE 200. The satellite 150 relays uplink signals received from the UE 200 to the NTN gateway. The satellite 150 may be interpreted as a TRP (Transmission-Reception Point), a repeater, or a relay.

[0024] The wireless communication system 10 also supports a plurality of frequency ranges (FR).

[0025] 2, the wireless communication system 10 corresponds to FR1, FR2-1, and FR2-2. The frequency bands of each FR are as follows.

[0026] FR1: 410 MHz to 7.125 GHz; FR2-1: 24.25 GHz to 52.6 GHz; FR2-2: 52.6 GHz to 71 GHz. FR1 may use a sub-carrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2-1 is a higher frequency than FR1 and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz. FR2-2 is a higher frequency than FR2-1 and may use an SCS of 120, 480 kHz, or 960 kHz and a bandwidth (BW) of 400 to 2000 MHz.

[0027] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0028] Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2-2 frequency band. Specifically, the wireless communication system 10 supports frequency bands above 52.6 GHz up to 71 GHz or 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x."

[0029] To solve the problem of increased phase noise in high frequency bands, when using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.

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

[0031] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used.

[0032] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0033] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0034] DMRS is a type of reference signal and is prepared for various channels. Here, unless otherwise specified, it may refer to a downlink data channel, specifically, a DMRS for a PDSCH (Physical Downlink Shared Channel). However, a DMRS for an uplink data channel, specifically, a PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as a DMRS for a PDSCH.

[0035] The DMRS may be used for channel estimation at the device, for example, as part of coherent demodulation at the UE 200. The DMRS may only be present in resource blocks (RBs) used for PDSCH transmission.

[0036] A DMRS may have multiple mapping types. Specifically, a DMRS has mapping type A and mapping type B. In mapping type A, the first DMRS is placed in the second or third symbol of a slot. In mapping type A, the DMRS may be mapped based on a slot boundary, regardless of where in the slot actual data transmission starts. The reason why the first DMRS is placed in the second or third symbol of a slot may be interpreted as being to place the first DMRS after a control resource set (CORESET).

[0037] In mapping type B, the first DMRS may be placed in the first symbol of the data allocation, i.e., the position of the DMRS may be given relative to where the data is placed, rather than relative to the slot boundary.

[0038] Furthermore, DMRS may have multiple types. Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

[0039] (2) Functional Block Configuration of Wireless Communication System Next, the functional block configuration of the wireless communication system 10 will be described.

[0040] First, the functional block configuration of the UE 200 will be described.

[0041] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.

[0042] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0043] In the embodiment, the radio signal transceiver 210 configures a receiver that performs repeated reception of a downlink channel. The downlink channel may include a PDSCH. The downlink channel may include Msg2 and / or Msg4 in a 4-step RA procedure. The downlink channel may include MsgB in a 2-step RA procedure.

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

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

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

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

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

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

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

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

[0052] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.

[0053] Here, the control signal and reference signal processor 240 may receive downlink control information (DCI). The DCI includes existing fields for storing DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), RV (Redundancy Version), and the like.

[0054] The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by an RRC message or may be determined by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI field is an information element for specifying whether the data to which the DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

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

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

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

[0058] The control unit 270 controls each functional block constituting the UE 200. In the embodiment, the control unit 270 constitutes a control unit that assumes an extended number of times as the number of repetitions of the downlink channel.

[0059] Here, the extended number of repetitions may be a number greater than the existing number of repetitions. The existing number of repetitions may be considered to be the number of repetitions specified up to 3GPP Release 16. The extended number of repetitions may be considered to be the number of repetitions introduced in 3GPP Release 19 or later.

[0060] Secondly, we will explain the functional block configuration of gNB100.

[0061] Fig. 5 is a functional block diagram of the gNB 100. As shown in Fig. 5, the gNB 100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0062] The receiving unit 110 receives various signals from the UE 200. The receiving unit 110 may receive an UL signal via a PUCCH or a PUSCH.

[0063] The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit DL signals via a PDCCH or a PDSCH. In the embodiment, the transmitter 120 configures a transmitter that performs repeated transmission of a downlink channel.

[0064] The control unit 130 controls the gNB 100. In the embodiment, the control unit 130 configures a control unit that assumes an extended number of times as the number of repetitions of the downlink channel.

[0065] (3) Problems After careful consideration, the inventors have found that it is necessary to increase the number of repeated transmissions of the downlink channel when expanding downlink coverage assuming NTN. For example, when satellite 150 communicates using multiple beams simultaneously, there is a possibility that the transmission power per beam may be insufficient.

[0066] To solve this problem, the UE 200 and the gNB 100 assume an extended number of times as the number of repetitions of the downlink channel. The extended number of times may be a number defined for the NTN, or may be a number defined without distinguishing between the TN and the NTN.

[0067] (4) Example of Operation (4.1) Overview of Example of Operation Below, an overview of an example of operation will be explained. In the overview of the example of operation, repeated transmission of Msg2 and / or Msg4 in the 4-step RA procedure will be illustrated.

[0068] As shown in Fig. 6, in step S10, the UE 200 receives a system information block (SIB) from the gNB 100. The SIB may include a PDSCH-ConfigCommon. The PDSCH-ConfigCommon may or may not include a pdsch-TimeDomainAllocationList.

[0069] In step S11, UE200 transmits a random access preamble to gNB100 as a first message (hereinafter, Msg1).

[0070] In step S12, the gNB 100 transmits a second message (hereinafter, Msg2) as a response message to the Msg1 to the UE 200. The gNB 100 may repeatedly transmit the Msg2. The Msg2 may be transmitted via the PDSCH.

[0071] In step S13, after receiving Msg2, the UE 200 transmits a third message (hereinafter, Msg3) to the gNB 100. Msg3 may be transmitted via the PUSCH.

[0072] In step S14, the gNB 100 transmits a fourth message (hereinafter, Msg4) as a response message to the Msg3 to the UE 200. The gNB 100 may repeatedly transmit the Msg4. The Msg4 may be transmitted via the PDSCH.

[0073] 6 illustrates a 4-step RA procedure, the embodiment may be applied to a 2-step RA procedure. In such a case, the gNB 100 performs repeated transmission of the MsgB.

[0074] (4.2) Operation Example 1 Operation example 1 will be described below. In operation example 1, a case where dsch-TimeDomainAllocationList is set will be described. It may be included in PDSCH-Config or PDSCH-ConfigCommon. PDSCH-Config is an information element for setting parameters for each UE 200, and PDSCH-ConfigCommon may be an information element for setting parameters common to a cell.

[0075] As shown in FIG. 7 , pdsch-TimeDomainAllocationList may include pdsch-AggregationFactor-r19. pdsch-AggregationFactor-r19 may be defined separately from the existing parameter (pdsch-AggregationFactor). pdsch-AggregationFactor-r19 may be a parameter that can specify an extended number of times. The extended number of times may include a number (e.g., n16, n20) that is greater than the number (e.g., n2, n4, n8) that can be specified by pdsch-AggregationFactor. pdsch-AggregationFactor and pdsch-AggregationFactor-r19 may be parameters for determining the number of PDSCH repetitions without being based on DCI notification.

[0076] In the first operation example, the UE 200 receives a higher layer parameter (pdsch-AggregationFactor-r19) that can specify the extended number of times. With this configuration, assuming NTN, the number of times of repeated transmission of the downlink channel can be appropriately extended.

[0077] In the first operational example, pdsch-AggregationFactor-r19 may be a parameter defined for NTN, or may be a parameter defined without distinguishing between TN and NTN. pdsch-AggregationFactor-r19 may be applied to PDSCH, Msg2, Msg4, or MsgB.

[0078] In the first operational example, the UE 200 may report UE capability related to the number of downlink repetitions to the gNB 100. The UE capability may be reported as a parameter for the NTN separate from the TN, or may be reported as a parameter common to the TN and the NTN. However, the UE capability may be reported for each band.

[0079] (4.3) Operation Example 2 Operation example 2 will be described below. In operation example 2, a case where dsch-TimeDomainAllocationList is set will be described. It may be included in PDSCH-Config or PDSCH-ConfigCommon. PDSCH-Config is an information element for setting parameters for each UE 200, and PDSCH-ConfigCommon may be an information element for setting parameters common to the cell.

[0080] As shown in FIG. 8 , pdsch-TimeDomainAllocationList may include repetitionNumber-r19. RepetitionNumber-r19 may be defined separately from the existing parameter (repetitionNumber-r16). RepetitionNumber-r19 may be a parameter that can specify an extended number of times. The extended number of times may include a number (e.g., n20) greater than the numbers (e.g., n2, n3, n4, n5, n6, n7, n8, n16) that can be specified by repetitionNumber-r16. RepetitionNumber-r16 and repetitionNumber-r19 may be parameters related to the number of repetitions notified by DCI for PDSCH reception.

[0081] In the second example of operation, the UE 200 receives a higher layer parameter (repetitionNumber-r19) that can specify the extended number of times. With this configuration, assuming NTN, the number of times of repeated transmission of the downlink channel can be appropriately extended.

[0082] In the second operational example, repetitionNumber-r19 may be a parameter defined for NTN, or may be a parameter defined without distinguishing between TN and NTN. RepetitionNumber-r19 may be applied to PDSCH, Msg2, Msg4, or MsgB.

[0083] In the second operation example, the UE 200 may report the UE capability related to the number of downlink repetitions to the gNB 100. The UE capability may be reported as a parameter for the NTN separate from the TN, or may be reported as a parameter common to the TN and the NTN. However, the UE capability may be reported for each band.

[0084] (4.4) Operation Example 3 Operation Example 3 will be described below. In Operation Example 3, a case where dsch-TimeDomainAllocationList is not set will be described. In such a case, the Default PDSCH time domain resource allocation table is used. In Operation Example 3, repeated transmission of Msg2 / Msg4 may be mainly assumed.

[0085] As shown in Fig. 9, a column for repetition factors may be added to the default PDSCH time domain resource allocation table for normal CP (cyclic prefix). Similarly, a column for repetition factors may be added to the default PDSCH time domain resource allocation table for extended CP.

[0086] In the existing Default PDSCH time domain resource allocation table, there is no column for Repetition factors, so the Repetition factors correspond to the extended number of times.

[0087] In the third operation example, the UE 200 assumes a table (the table shown in FIGS. 9 and 10) that can specify an extended number of times as a table defining time domain resources of the downlink channel. With this configuration, when NTN is assumed, the number of times of repeated transmission of the downlink channel can be appropriately extended.

[0088] In the third example operation, whether to apply the sequence of repetition factors may be indicated by the SIB or may be specified by the Scheduling DCI that schedules the PDSCH. UE 200 may apply the sequence of repetition factors if there is an instruction, and may not apply the sequence of repetition factors if there is no instruction. Instructions may be given separately for Msg2 and Msg4, or an instruction for Msg2 may be reapplied to Msg4.

[0089] In the third operational example, whether or not to apply the sequence of repetition factors may be based on a request from the UE 200. The UE 200 may apply the sequence of repetition factors when repetition of Msg2 / Msg4 is requested, and may not apply the sequence of repetition factors when repetition of Msg2 / Msg4 is not requested.

[0090] In the third exemplary operation, whether or not to apply the sequence of repetition factors may be determined based on the UE capability. When the UE 200 reports that it supports the repetition of Msg2 / Msg4, the UE 200 may apply the sequence of repetition factors, and when the UE 200 does not report that it supports the repetition of Msg2 / Msg4, the UE 200 may not apply the sequence of repetition factors.

[0091] Although the third operation example has been mainly described with reference to Msg2 / Msg4, the third operation example may also be applied to MsgB.

[0092] (4.5) Operation Example 4 Operation Example 4 will be described below. In Operation Example 4, a case where dsch-TimeDomainAllocationList is not set will be described. In such a case, the Default PDSCH time domain resource allocation table is used. In Operation Example 4, repeated transmission of Msg2 / Msg4 may be mainly assumed.

[0093] As shown in Fig. 11, the existing default PDSCH time domain resource allocation table does not have a column for repetition factors. As shown in Fig. 12, the new default PDSCH time domain resource allocation table adds a column for repetition factors.

[0094] Although Figures 11 and 12 illustrate examples of the default PDSCH time domain resource allocation table for normal CP, a new table with an additional column for repetition factors may also be introduced for the default PDSCH time domain resource allocation table for extended CP.

[0095] That is, in the third operation example, the existing Default PDSCH time domain resource allocation table is updated, whereas in the fourth operation example, a new Default PDSCH time domain resource allocation table is introduced to which a column for Repetition factors has been added.

[0096] In the existing Default PDSCH time domain resource allocation table, there is no column for Repetition factors, so the Repetition factors correspond to the extended number of times.

[0097] In the fourth operation example, the UE 200 assumes a table (the table shown in FIG. 12) that can specify an extended number of times as a table defining time domain resources of the downlink channel. With this configuration, when NTN is assumed, the number of times of repeated transmission of the downlink channel can be appropriately extended.

[0098] In the fourth operation example, whether to apply the new Default PDSCH time domain resource allocation table may be indicated by the SIB or may be specified by the Scheduling DCI that schedules the PDSCH. UE 200 may apply the new Default PDSCH time domain resource allocation table if there is an indication, and may apply the existing Default PDSCH time domain resource allocation table if there is no indication. The indication may be given separately for Msg2 and Msg4, or the indication for Msg2 may be reapplied to Msg4.

[0099] In the fourth operation example, whether to apply the new Default PDSCH time domain resource allocation table may be based on a request from the UE 200. When the UE 200 requests repetition of Msg2 / Msg4, the UE 200 may apply the new Default PDSCH time domain resource allocation table, and when the UE 200 does not request repetition of Msg2 / Msg4, the UE 200 may apply the existing Default PDSCH time domain resource allocation table.

[0100] In the fourth operational example, whether to apply the new Default PDSCH time domain resource allocation table may be determined based on the UE capability. When the UE 200 reports that it supports Msg2 / Msg4 repetition, the UE 200 may apply the new Default PDSCH time domain resource allocation table, and when the UE 200 does not report that it supports Msg2 / Msg4 repetition, the UE 200 may not apply the existing Default PDSCH time domain resource allocation table.

[0101] Although the fourth operational example has been mainly described with respect to Msg2 / Msg4, the fourth operational example may also be applied to MsgB.

[0102] (4.6) Operational Example 5 In operational example 5, possible values ​​of the repetition factors of each row will be explained in the above-mentioned operational examples 3 and 4. The possible values ​​of the repetition factors of each row are the following options:

[0103] In option 5-1, the repetition factors for each row may have only one possible value.

[0104] The possible values ​​for the repetition factors for each row are the following options:

[0105] In option 5-1-1, the value of the repetition factor may be different for each row of the Default PDSCH time domain resource allocation table. In such a case, the value of the repetition factor may be the same for some of the rows of the Default PDSCH time domain resource allocation table.

[0106] In option 5-1-2, the value of the Repetition factor may be the same for all rows in the Default PDSCH time domain resource allocation table.

[0107] The repetition factor for each line can have the following options:

[0108] In option 5-1-2-1, the repetition factor of each row may be the same as the existing repetition number (e.g., n1, n2, n4, n8). The existing repetition number may be considered to be the repetition number specified before 3GPP Release 18.

[0109] In Option 5-1-2-2, the repetition factor of each row may be a number greater than the existing number of repetitions (e.g., n1, n2, n4, n8, n16, n20). A number greater than the existing number of repetitions may be considered to be a number of repetitions specified in 3GPP Release 19 or later.

[0110] Option 5-1 allows for a single possible value for the repetition factors in each row, reducing the signaling load.

[0111] In option 5-2, the repetition factors for each row may have more than one possible value.

[0112] The repetition factor that UE 200 actually applies from the candidate repetition factors in each row may be indicated by gNB 100 to UE 200. For example, the repetition factor that UE 200 actually applies may be specified by Scheduling DCI that schedules the PDSCH. The repetition factor that UE 200 actually applies may be specified by a new field included in Scheduling DCI, or may be specified by interpreting an existing field included in Scheduling DCI.

[0113] The repetition factor for each line can have the following options:

[0114] In option 5-2-1, the repetition factor of each row may be the same as the existing repetition count (e.g., n1, n2, n4, n8). The existing repetition count may be considered to be the repetition count specified before 3GPP Release 18.

[0115] In Option 5-2-2, the repetition factor of each row may be a number greater than the existing repetition number (e.g., n1, n2, n4, n8, n16, n20). A number greater than the existing repetition number may be considered to be a repetition number specified in 3GPP Release 19 or later.

[0116] Option 5-2 allows flexibility in setting repetition factors, as there are two possible values ​​for each row.

[0117] (4.7) Operation Example 6 In Operation Example 6, the number of repetitions applied to Msg2 / Msg4 will be described. The number of repetitions applied to Msg2 / Msg4 may be specified by SIB or PDSCH-ConfigCommon.

[0118] For example, as shown in Fig. 13, PDSCH-ConfigCommon may include pdsch-AggregationFactor-r18. pdsch-AggregationFactor-r18 may be a parameter specifying one value (ENUMERATED {n1, n2, n4, n8, n16, n32...}). pdsch-AggregationFactor-r18 may be a parameter specifying two or more values ​​(SEQUENCE (SIZE(1...MaxResourceAllocation) OF ENUMERATED {n1, n2, n4, n8, n16, n32...}). Msg2 and Msg4 may be indicated separately, and an indication for Msg2 may be reapplied to Msg4.

[0119] When a parameter specifying a value of 2 or greater is configured, the repetition factor actually applied by UE 200 may be indicated by gNB 100 to UE 200. For example, the repetition factor actually applied by UE 200 may be specified by Scheduling DCI that schedules the PDSCH. The repetition factor actually applied by UE 200 may be specified by a new field included in Scheduling DCI, or may be specified by interpreting an existing field included in Scheduling DCI.

[0120] Although the sixth operational example has been mainly described with respect to Msg2 / Msg4, the fourth operational example may also be applied to MsgB.

[0121] (4.8) Operation Example 7 In Operation Example 7, the repetition count applied to Msg2 / Msg4 will be described. The repetition count applied to Msg2 / Msg4 may be specified by the Scheduling DCI that schedules the PDSCH. The repetition count may be specified by a new field included in the Scheduling DCI, or may be specified by interpreting an existing field included in the Scheduling DCI. The repetition count may be indicated separately for each of Msg2 and Msg4, or the indication for Msg2 may be reapplied to Msg4.

[0122] Although the seventh operational example has been mainly described with respect to Msg2 / Msg4, the seventh operational example may also be applied to MsgB.

[0123] (4.9) Operation Example 8 In Operation Example 8, a case will be described in which the UE 200 requests whether or not to apply the Repetition factors column (or a new Default PDSCH time domain resource allocation table, the same applies below) in the above-described Operation Examples 3 and 4.

[0124] The UE 200 transmits a request for repetition and / or the number of repetitions by Msg1 / Msg3 based on the implementation of the UE 200 or a predetermined rule.

[0125] For example, if UE 200 is a mobile terminal in an NTN scenario, UE 200 may always send a request.

[0126] For example, if the SS-RSRP / CSI-RSRP measured by the UE 200 is lower than a specific RSRP threshold, the UE 200 may transmit the request. The specific RSRP threshold may be indicated to the UE 200 by the SIB. The specific RSRP threshold may be the same as the threshold used for repeated transmission of Msg3 introduced in 3GPP Release 17, the same as the threshold used for repeated transmission of Msg.4 (PUCCH) introduced in 3GPP Release 18, or a newly introduced threshold.

[0127] The UE 200 may transmit, by Msg1 / Msg3, assistant information for the gNB 100 to determine repeated transmission. The assistant information may include CSI, UE type, service type, and the like.

[0128] According to the eighth operational example, in the case where the UE 200 requests whether or not to apply the sequence of repetition factors, the signaling regarding the request of the UE 200 is clarified.

[0129] Although the operation example 8 has been mainly described with respect to Msg2 / Msg4, the operation example 8 may also be applied to MsgB. In such a case, Msg1 / 3 may be read as MsgA.

[0130] (4.10) Operation Example 9 In Operation Example 9, a case will be described in which a UE capability indicating whether or not to apply the Repetition factors column (or the new Default PDSCH time domain resource allocation table, the same applies below) is transmitted in the above-mentioned Operation Examples 3 and 4. The following options are possible for transmitting the UE capability.

[0131] In option 9-1, the UE 200 may always transmit the UE capability via Msg1 / Msg3.

[0132] In option 9-2, the UE 200 may transmit the UE capability in response to receiving Msg2 / Msg4 including information requesting the UE capability.

[0133] In option 9-3, the UE 200 may transmit the UE capability based on the implementation of the UE 200. For example, the UE 200 may transmit the UE capability when it detects that it is necessary to repeat Msg2 / Msg4.

[0134] In the ninth operation example, the UE capability may be transmitted together with the request described in the eighth operation example, or may be transmitted separately from the request described in the eighth operation example.

[0135] According to the ninth operational example, in the case where the UE capability indicating whether or not to apply the sequence of repetition factors is transmitted, the signaling related to the UE capability is clarified.

[0136] Although the operation example 9 has been mainly described with respect to Msg2 / Msg4, the operation example 9 may also be applied to MsgB. In such a case, Msg1 / 3 may be read as MsgA.

[0137] (4.11) Others The above-described operation examples 1-9 may be applied to reception of PDSCH after reception of Msg2 / 4 when an individual PDSCH Config is not set in UE 200. The number of repetitions of PDSCH after reception of Msg2 / 4 may be the same as the number of repetitions of Msg2 / 4, or may be specified separately from the number of repetitions of Msg2 / 4.

[0138] (5) Actions and Effects In the embodiment, the UE 200 and the gNB 100 assume an extended number of times as the number of repetitions of the downlink channel. With this configuration, when NTN is assumed, the number of repetitions of the downlink channel can be appropriately extended.

[0139] (6) Other Embodiments The contents of the present invention have been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0140] In the above disclosure, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

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

[0142] The block diagrams (FIGS. 4 and 5) used to explain the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

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

[0144] Furthermore, the above-described gNB 100 and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 14 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 14, the devices may be configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

[0146] Each functional block of the device (see FIGS. 4 and 5) is realized by any hardware element of the computer device or a combination of the hardware elements.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0160] In the present disclosure, a specific operation described as being performed by a base station may, in some cases, be performed by its upper node. It is clear that in a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (such as, but not limited to, an MME or an S-GW). While the above example illustrates a case in which there is one other network node other than the base station, a combination of multiple other network nodes (such as an MME and an S-GW) may also be used.

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

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

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

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

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

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

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

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

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

[0170] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

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

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

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

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

[0175] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0177] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0178] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

[0181] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

[0182] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0183] Numerology may be a communication parameter applied to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation performed by a transceiver in the frequency domain, a particular windowing operation performed by a transceiver in the time domain, etc.

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

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

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

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

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

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

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

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

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

[0193] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0194] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

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

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

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

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

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

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

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

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

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

[0205] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

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

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

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

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

[0210] 15 shows an example of the configuration of a vehicle 2001. As shown in Fig. 15, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0211] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0212] The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0213] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0214] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0215] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0216] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0217] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0218] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0219] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0220] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0221] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0222] (Additional Note) The above disclosure may be expressed as follows.

[0223] The first feature is a terminal including: a receiving unit that executes repeated reception of a downlink channel; and a control unit that assumes an extended number of times as the number of times of repetition of the downlink channel.

[0224] A second feature is the terminal based on the first feature, wherein the receiving unit receives a higher layer parameter capable of specifying the extended number of times.

[0225] A third feature is the terminal according to the first and second features, wherein the control unit assumes a table capable of specifying the extended number of times as a table defining time domain resources of a downlink channel.

[0226] A fourth feature is a base station including: a transmitter that executes repeated transmission of a downlink channel; and a controller that assumes an extended number of times as the number of times of repetition of the downlink channel.

[0227] A fifth feature is a wireless communication system including a terminal and a base station, wherein the terminal includes a receiving unit that performs repeated reception of a downlink channel, and a control unit that assumes an extended number of times as the number of repetitions of the downlink channel.

[0228] A sixth feature is a wireless communication method including: a step A of performing repeated reception of a downlink channel; and a step B of assuming an extended number of times as the number of times of repetition of the downlink channel.

[0229] 10 Wireless communication system 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitting unit 130 Control unit 150 Satellite 200 UE 210 Radio signal transmitting / receiving unit 220 Amplifying unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transmitting / receiving unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a receiving unit that performs repeated reception of a downlink channel; and a control unit that assumes an extended number of times as the number of times the downlink channel is repeated.

2. The terminal according to claim 1, wherein the receiving unit receives a higher layer parameter capable of specifying the extended number of times.

3. The terminal according to claim 1, wherein the control unit assumes a table capable of specifying the extended number of times as a table defining time domain resources of a downlink channel.

4. A base station comprising: a transmitting unit that performs repeated transmission of a downlink channel; and a control unit that assumes an extended number of times as the number of repetitions of the downlink channel.

5. A wireless communication system comprising a terminal and a base station, the terminal comprising: a receiving unit that performs repeated reception of a downlink channel; and a control unit that assumes an extended number of times as the number of repetitions of the downlink channel.

6. A wireless communication method comprising: a step A of performing repeated reception of a downlink channel; and a step B of assuming an extended number of times as the number of repetitions of the downlink channel.

Images