WO2022239081A1

WO2022239081A1 - Terminal and wireless communication method

Info

Publication number: WO2022239081A1
Application number: PCT/JP2021/017760
Authority: WO
Inventors: 春陽越後; 大輔栗田; 浩樹原田
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2021-05-10
Filing date: 2021-05-10
Publication date: 2022-11-17

Abstract

A terminal according to the present invention comprises: a transmission unit that repeatedly transmits an uplink channel in a specific period of not less than a plurality of slots; and a control unit that controls transmission of the uplink channel, wherein the control unit uses the specific period as an interval at which the transmission power of the uplink channel is determined.

Description

Terminal and wireless communication method

The present disclosure relates to a terminal and wireless communication method compatible with coverage extension.

The 3rd Generation Partnership Project (3GPP) has specified the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and the next generation specification called Beyond 5G, 5G Evolution or 6G We are also proceeding with

For example, in 3GPP Release-17, it was agreed to consider coverage enhancement (CE: Coverage Enhancement) in NR (Non-Patent Document 1).

DDDSU (D: downlink (DL) symbol, S: DL/uplink (UL) or guard symbol, U: UL symbol) is specified as a slot configuration pattern for time division duplex (TDD). If the S slot is 10D+2G+2U, 2 consecutive symbols (2U) and 1 slot (14 symbols) are used for UL in the time direction, that is, multiple consecutive slots are used for UL. can be done.

Therefore, in such a case, channel estimation of an uplink channel (UL channel) such as PUSCH (Physical Uplink Shared Channel) using a demodulation reference signal (DMRS) that can exist in multiple slots is called joint channel estimation. ) are being considered.

However, when such joint channel estimation is applied, there is room for improvement in the uplink channel transmission method.

Therefore, the following disclosure is made in view of this situation, and a terminal and a radio that can more efficiently perform channel estimation of uplink channels such as PUSCH using DMRS that can exist in multiple slots The purpose is to provide a base station.

One aspect of the disclosure is a terminal, comprising: a transmission unit that repeatedly transmits an uplink channel in a specific period of a plurality of slots or more; and a control unit that controls transmission of the uplink channel, wherein the control unit comprises and using the specific period as an interval for determining the transmission power of the uplink channel.

One aspect of the disclosure is a terminal, comprising: a transmission unit that repeatedly transmits an uplink channel in a specific period of a plurality of slots or more; and a control unit that controls transmission of the uplink channel, wherein the control unit comprises and determining a timing to apply timing information received from a network based on the specific time period.

One aspect of the disclosure is a terminal, comprising: a transmission unit that repeatedly transmits an uplink channel in a specific period of a plurality of slots or more; and a control unit that controls transmission of the uplink channel, wherein the control unit comprises and determining an interval for hopping the uplink channel in the frequency direction based on whether or not all repeated transmissions of the uplink channel are included in the specific period.

One aspect of the disclosure is a wireless communication method, comprising: repeatedly transmitting an uplink channel in a specific period of a plurality of slots or more; and using the specific period as an interval for determining the transmission power of the uplink channel. The gist is that it comprises:

One aspect of the disclosure is a wireless communication method, comprising: repeatedly transmitting an uplink channel in a specific period of a plurality of slots or more; and determining a timing to apply timing information received from a network based on the specific period. and the step of:

An aspect of the disclosure is a wireless communication method, comprising: repeatedly transmitting an uplink channel in a specific period of a plurality of slots or more; and determining whether all repeated transmissions of the uplink channel are included in the specific period. and determining an interval for hopping the uplink channel in the frequency direction based on.

FIG. 1 is an overall schematic configuration diagram of a radio communication system 10. As shown in FIG. FIG. 2 is a diagram illustrating frequency ranges used in wireless communication system 10. As shown in FIG. FIG. 3 is a diagram showing a configuration example of radio frames, subframes and slots used in the radio communication system 10. As shown in FIG. FIG. 4 is a functional block configuration diagram of UE200. FIG. 5 is a functional block configuration diagram of gNB100. FIG. 6 is a diagram for explaining joint channel estimation. FIG. 7 is a diagram for explaining Operation Example 4. FIG. FIG. 8 is a diagram for explaining Operation Example 5. FIG. FIG. 9 is a diagram for explaining Operation Example 5. FIG. FIG. 10 is a diagram for explaining Operation Example 6. FIG. FIG. 11 is a diagram for explaining Operation Example 6. FIG. FIG. 12 is a diagram for explaining Operation Example 6. FIG. FIG. 13 is a diagram for explaining Operation Example 6. FIG. FIG. 14 is a diagram for explaining Operation Example 7. FIG. FIG. 15 is a diagram for explaining Operation Example 8. FIG. FIG. 16 is a diagram showing an example of the hardware configuration of gNB100 and UE200.

Hereinafter, embodiments will be described based on the drawings. Note that the same or similar reference numerals are given to the same functions and configurations, and the description thereof will be omitted as appropriate.

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

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

NG-RAN 20 includes a radio base station 100A (hereinafter gNB100A) and a radio base station 100B (hereinafter gNB100B). Note that the specific configuration of the radio communication system 10 including the number of gNBs and UEs is not limited to the example shown in FIG.

NG-RAN 20 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-RAN 20 and 5GC may simply be referred to as a "network".

gNB100A and gNB100B are 5G-compliant radio base stations and perform 5G-compliant radio communication with UE200. gNB100A, gNB100B and UE200 generate BM beams with higher directivity by controlling radio signals transmitted from multiple antenna elements Massive MIMO (Multiple-Input Multiple-Output), multiple component carriers (CC ), and dual connectivity (DC) that simultaneously communicates with two or more transport blocks between the UE and each of the two NG-RAN Nodes.

Also, the wireless communication system 10 supports multiple frequency ranges (FR). FIG. 2 shows the frequency ranges used in wireless communication system 10. As shown in FIG.

As shown in FIG. 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows.

・FR1: 410MHz to 7.125GHz
・FR2: 24.25 GHz to 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-100 MHz may be used. FR2 is higher frequency than FR1 and may use an SCS of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50-400 MHz.

It should be noted that SCS may be interpreted as numerology. numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands above 52.6 GHz and up to 71 GHz or 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x".

Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/ Discrete Fourier Transform - Spread (DFT-S-OFDM) may be applied.

FIG. 3 shows a configuration example of radio frames, subframes and slots used in the radio communication system 10. FIG.

As shown in FIG. 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 intervals (frequencies) shown in FIG. For example, 480 kHz, 960 kHz, etc. may be used.

Also, the number of symbols forming one slot does not necessarily have to be 14 symbols (for example, 28 or 56 symbols). Furthermore, the number of slots per subframe may vary between SCSs.

Note that the time direction (t) shown in FIG. 3 may be called the time domain, symbol period, symbol time, or the like. Also, the frequency direction may be called a frequency domain, resource block, subcarrier, bandwidth part (BWP), or the like.

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

DMRS can be used for channel estimation in devices, eg, UE 200, as part of coherent demodulation. DMRS may reside only in resource blocks (RBs) used for PDSCH transmission.

A DMRS may have multiple mapping types. Specifically, DMRS has mapping type A and mapping type B. For mapping type A, the first DMRS is placed in the 2nd or 3rd symbol of the slot. In mapping type A, the DMRS may be mapped relative to slot boundaries, regardless of where in the slot the actual data transmission begins. The reason the first DMRS is placed in the second or third symbol of the slot may be interpreted as to place the first DMRS after the control resource sets (CORESET).

In mapping type B, the first DMRS may be placed in the first symbol of data allocation. That is, the position of the DMRS may be given relative to where the data is located rather than relative to slot boundaries.

In addition, DMRS may have multiple types (Type). Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in mapping in the frequency domain and the maximum number of orthogonal reference signals. Type 1 can output up to 4 orthogonal signals with single-symbol DMRS, and Type 2 can output up to 8 orthogonal signals with double-symbol DMRS.

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

For example, gNB 100 can support repeated transmission of PDSCH (Physical Downlink Shared Channel), and UE 200 can support repeated transmission of PUSCH (Physical Uplink Shared Channel).

In the radio 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).

"D" indicates a slot containing all DL symbols, and "S" indicates a slot containing a mixture of DL, UL, and guard symbols (G). "U" indicates a slot containing all UL symbols.

Further, in the radio 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. can be used to perform channel estimation for PUSCH (or PUCCH). Such channel estimation may be called joint channel estimation. Alternatively, it may be called by another name such as cross-slot channel estimation.

The UE 200 can transmit DMRS assigned to (spanning) multiple slots so that the gNB 100 can perform joint channel estimation using DMRS.

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

In TBoMS, the number of allocated symbols can be the same in each slot as in PUSCH Repetition type A Time Domain Resource Allocation (TDRA), or it can be the same in each slot as in PUSCH Repetition type B TDRA. The number of assigned symbols can be different.

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

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

(2) Functional Block Configuration of Radio Communication System Next, the functional block configuration of the radio communication system 10 will be described.

First, the functional block configuration of the UE200 will be explained.

FIG. 4 is a functional block diagram of the UE200. As shown in FIG. 4, the UE 200 includes a radio signal transmission/reception unit 210, an amplifier unit 220, a modem 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. .

The radio signal transmitting/receiving unit 210 transmits/receives radio signals according to NR. The radio signal transmitting/receiving unit 210 supports Massive MIMO, CA that bundles multiple CCs, and DC that simultaneously communicates between the UE and each of the two NG-RAN Nodes.

Here, the radio signal transmitting/receiving unit 210 may transmit a physical uplink shared channel. In the embodiment, the radio signal transceiver 210 may constitute a transmitter.

Specifically, the radio signal transmitting/receiving unit 210 may transmit PUSCH toward the network (gNB 100). The radio signal transmitting/receiving unit 210 may support repeated transmission (Repetition) of PUSCH. The uplink channel may include a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH). A shared channel may also be referred to as a data channel.

Multiple types of repeated transmission 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 the PUSCH allocated within the slot is repeatedly transmitted. That is, PUSCH is 14 symbols or less, and there is no possibility of being allocated across multiple slots (adjacent slots).

On the other hand, Repetition type B may be interpreted as repeated transmission of PUSCH to which 15 or more PUSCH symbols may be allocated. In the present embodiment, allocation of such PUSCH across multiple slots may be allowed.

A specific period of multiple slots or more may be interpreted as a period related to PUSCH (or PUCCH) repetition. For example, the specific period may be indicated by the number of Repetitions, or may be the time during which a specified number of Repetitions are executed. In embodiments, the specified time period may be interpreted as the time period over which the joint channel estimation is applied. The UE 200 may not be able to receive a downlink channel (DL channel) during a specific period.

Alternatively, the radio signal transmitting/receiving unit 210 may repeatedly transmit the UL channel a specific number of times. Specifically, radio signal transmitting/receiving section 210 may repeatedly transmit PUSCH (or PUCCH) multiple times.

The specific period and/or the specific number of times may be indicated by signaling from the network (the upper layer of RRC or the lower layer such as DCI, the same applies hereinafter), or may be preset in the UE 200. .

The amplifier section 220 is configured by a PA (Power Amplifier)/LNA (Low Noise Amplifier) and the like. Amplifier section 220 amplifies the signal output from modem section 230 to a predetermined power level. In addition, amplifier section 220 amplifies the RF signal output from radio signal transmission/reception section 210 .

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

The control signal/reference signal processing unit 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.

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

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

A DMRS is a known reference signal (pilot signal) between a terminal-specific base station and a terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is a problem in high frequency bands.

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

Also, the channel includes a control channel and a data channel. Control channels include Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Random Access Channel (RACH), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH) etc. are included.

In addition, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data means data transmitted over a data channel. A data channel may be read as a shared channel.

Here, the control signal/reference signal processing unit 240 may receive downlink control information (DCI). DCI has existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Allocation), TDRA (Time Domain Resource Allocation), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number) , NDI (New Data Indicator), RV (Redundancy Version), etc.

The value stored in the DCI Format field is an information element that specifies the DCI format. The value stored in the CI field is an information element that specifies the CC to which DCI is applied. The value stored in the BWP indicator field is an information element that specifies the BWP to which DCI applies. The BWP that can be specified by the BWP indicator is configured 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 DCI is applied. A frequency domain resource is identified by a 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 DCI applies. The time domain resource is specified by the value stored in the TDRA field and information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. A time-domain resource may be identified by a 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 DCI applies. The MCS is specified by the values stored in the MCS and the MCS table. The MCS table may be specified by RRC messages or identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which DCI is applied. The value stored in NDI is an information element for specifying whether data to which DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the data redundancy to which DCI is applied.

The encoding/decoding unit 250 performs data segmentation/concatenation, channel coding/decoding, etc. for each predetermined communication destination (gNB 100 or other gNB).

Specifically, the encoding/decoding unit 250 divides the data output from the data transmission/reception unit 260 into pieces of a predetermined size, and performs channel coding on the divided data. Also, encoding/decoding section 250 decodes the data output from modem section 230 and concatenates the decoded data.

The data transmission/reception unit 260 executes transmission/reception of Protocol Data Unit (PDU) and Service Data Unit (SDU). Specifically, the data transmitting/receiving unit 260 performs PDU/SDU in multiple layers (medium access control layer (MAC), radio link control layer (RLC), packet data convergence protocol layer (PDCP), etc.). Assemble/disassemble etc. The data transmission/reception unit 260 also performs data error correction and retransmission control based on HARQ (Hybrid Automatic Repeat Request).

The control unit 270 controls each functional block that configures the UE200. In embodiments, the controller 270 may constitute a controller that controls transmission of UL channels (eg, PUSCH and PUCCH).

For example, when two or more specifying methods for setting a specific period are defined, the control unit 270 may set the specific period based on two or more specific methods. A specific time period may be referred to as a Time domain window. How to set the time domain window will be described later.

The control unit 270 may determine the allocation of DMRS transmitted on the UL channel, specifically the PUSCH, based on the PUSCH repetition state, that is, the number of repetitions, the repetition period, and the like.

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

Second, the functional block configuration of gNB100 will be explained.

FIG. 5 is a functional block configuration diagram of gNB100. As shown in FIG. 5, the gNB 100 has a receiver 110, a transmitter 120 and a controller .

The receiving unit 110 receives various signals from the UE200. The receiver 110 may receive UL signals via UL channels such as PUCCH or PUSCH.

The transmission unit 120 transmits various signals to the UE200. Transmitter 120 may transmit a DL signal via a DL channel such as PDCCH or PDSCH.

The control unit 130 controls the gNB100. The control unit 130 may perform joint channel estimation of UL channels allocated to multiple slots, eg, PUSCH, using DMRS allocated to multiple slots. Control section 130 may perform initial access of UE 200, specifically, joint channel estimation of the UL channel in a random access procedure, using DMRSs assigned to multiple slots.

(3) Joint channel estimation
Joint channel estimation will be described below. As described above, joint channel estimation may be interpreted as a technique of performing channel estimation based on (assigned) DMRS present in multiple slots.

As shown in FIG. 6, the UE 200 may transmit DMRS symbols between specific PUSCHs, between PUCCHs, or between PUSCHs and PUCCHs so that the gNB 100 can perform joint channel estimation. The UE 200 may transmit DMRS symbols whose transmission power, phase, and transmission timing do not change between slots.

For example, DMRSs may be arranged in DMRS resources allocated to each PUSCH before the PUSCHs are integrated. DMRSs may be transmitted (arranged) at equal intervals within resources to which channel estimation using multiple slots is applied.

(4) Operation example (4.1) Operation example 1
Operation example 1 will be described below. In operation example 1, a method for setting a specific period (Time domain window) will be described.

First, the Time domain window may be set by an information element included in a radio resource control message (RRC message). An RRC message is an example of a message containing information elements received from NG RAN 20 . The RRC message may be at least one of PUCCH-Config, PUSCH-Config, and PUSCH-Config common. An RRC message may contain information elements that set more than one time domain window. In such cases, for applicable resources such as joint channel estimation between PUSCHs with different TB, channel estimation between PUSCH repetition type A, joint channel estimation between PUSCH repetition type B, joint channel estimation between PUCCH, etc. Information elements that set different time domain windows may be included in the RRC message accordingly.

The RRC message may be interpreted as containing an information element that sets the Time domain window to Semi-static. The information element may include an information element indicating the Time domain window, an information element indicating the Time domain window size, and an information element indicating the unit of the Time domain window size (Repetition, number of slots, etc.). , may contain an information element indicating the use (different TB (Transport Block)s, TBoMS, Repetition, etc.) to which the Time domain window applies.

The UE 200 may apply a Time domain window for each PUCCH resource out of two or more Time domain windows, or may apply a Time domain window for each PUCCH resource format.

When UE200 does not receive an information element specifying a time domain window to be applied to UE200 from among two or more time domain windows, UE200 selects a time domain window (Default time domain window) may be determined.

The predetermined rule may be a rule that applies the Time domain window with the smallest Index as the Default time domain window on the premise that the Time domain window is associated with the Index.

The predetermined rule may be a rule that applies the time domain window specified in the upper layer as the Default time domain window.

The predetermined rule may be a rule that applies the time domain window predetermined in the wireless communication system 10 as the Default time domain window. In such cases, two or more Time domain windows may not be set by RRC messages.

Second, the Time domain window may be set by an information element included in the media access control message (MAC CE message). A MAC CE message is an example of a message containing information elements received from NG RAN 20 .

A MAC CE message may be interpreted as containing an information element that sets the Time domain window to Semi-persistent. The information element may include an information element indicating the Time domain window, may include an information element indicating the start timing of the Time domain window, may include an information element indicating the Time domain window size, and may include an information element indicating the Time domain window size. (Repetition, number of slots, etc.) may be included, and an information element indicating the use (different TBs, TBoMS, Repetition, etc.) to which the Time domain window is applied may be included.

For example, a MAC CE message may include an information element that sets (activates) one or more Time domain windows. The MAC CE message may include an information element specifying one or more time domain windows to be activated from two or more time domain windows set by the RRC message. A MAC CE message may contain an information element that deactivates the Time domain window.

When the UE 200 receives a MAC CE message containing an information element that activates the time domain window, the UE 200 may deactivate the time domain window after applying the time domain window for a certain period of time. A certain period of time may be measured by a timer that is started upon receipt of a MAC CE message. The certain period of time may be set by an RRC message, may be set by a MAC CE message, or may be predetermined in the wireless communication system 10 . If timers are used, the information element that deactivates the Time domain window need not be defined.

Alternatively, the MAC CE message may contain information elements that specify one or more Time domain window sizes. The MAC CE message may contain an information element specifying the Time domain window size for the Time domain window set by the RRC message. A Time domain window applied to the UE 200 may be specified by a Time domain window size. A MAC CE message may contain an information element that activates the Time domain window size. A MAC CE message may contain an information element that deactivates the Time domain window size.

When the UE 200 receives a MAC CE message containing an information element that activates the time domain window size, the UE 200 may deactivate the time domain window size after applying the time domain window size for a certain period of time. A certain period of time may be measured by a timer that is started upon receipt of a MAC CE message. The certain period of time may be set by an RRC message, may be set by a MAC CE message, or may be predetermined in the wireless communication system 10 . If timers are used, the information element deactivating Time domain window size may not be defined.

In such cases, the minimum interval may be defined as the interval from receiving the MAC CE message to starting the Time domain window size. The minimum interval may be predetermined in the wireless communication system 10, configured by an RRC message, or configured by a MAC CE message.

(4.2) Operation example 2
Operation example 1 will be described below. In operation example 1, a method for setting a specific period (Time domain window) will be described.

First, the Time domain window may be set by an information element included in downlink control information (DCI). DCI is an example of a message containing information elements received from NG RAN 20 .

DCI may be interpreted as containing an information element that sets the Time domain window to Dynamic. The information element may include an information element indicating the Time domain window, may include an information element indicating the start timing of the Time domain window, may include an information element indicating the Time domain window size, and may include an information element indicating the Time domain window size. (Repetition, number of slots, etc.) may be included, and an information element indicating the use (different TBs, TBoMS, Repetition, etc.) to which the Time domain window is applied may be included.

For example, DCI may include an information element that specifies a time domain window to apply to UE 200 from among two or more time domain windows set (activated) by an RRC message or MAC CE message.

The UE 200 may apply the time domain window for a certain period of time when receiving DCI including an information element that applies the time domain window. A certain period of time may be measured by a timer that is started upon reception of DCI. The certain period of time may be set by an RRC message, may be set by a MAC CE message, may be set by DCI, or may be predetermined in the wireless communication system 10 .

Alternatively, the DCI may contain information elements that specify one or more Time domain window sizes. The DCI may contain an information element specifying the time domain window size for the time domain window set (activated) by the RRC message or MAC CE message. A Time domain window applied to the UE 200 may be specified by a Time domain window size.

When the UE 200 receives DCI including an information element that activates the time domain window size, the UE 200 may apply the time domain window size for a certain period of time. A certain period of time may be measured by a timer that is started upon reception of DCI. The certain period of time may be set by an RRC message, may be set by a MAC CE message, may be set by DCI, or may be predetermined in the wireless communication system 10 .

Second, the UE200 may identify the DCI addressed to the UE200 based on the RNTI used in DCI scrambling.

The RNTI used for DCI scrambling may be an RNTI (eg, C-RNTI) associated with one UE200.

Alternatively, the RNTI used in DCI scrambling may be an RNTI associated with two or more UEs 200 (for example, a group RNTI). In such a case, the group (two or more UEs 200) to which the group RNTI is applied may be set by RRC, and the UE 200 may identify the DCI addressed to the UE 200 based on the group RNTI. Alternatively, a group (two or more UEs 200) to which DCI is applied may be set for each DCI format, and UE 200 may specify DCI for UE 200 based on DCI format and RNTI.

In such cases, the minimum interval may be defined as the interval from receiving DCI to starting the Time domain window size. The minimum interval may be predetermined in the wireless communication system 10, configured by an RRC message, or configured by a MAC CE message.

(4.3) Operation example 3
Operation example 3 will be described below. In operation example 3, a method for setting a specific period (Time domain window) will be described.

The time domain window is set based on the timing of hopping the UL channel in the frequency direction. As described above, UE 200 may transmit DMRS symbols such that transmission power, phase, and transmission timing do not change between slots.

For example, the time domain window may start/end at the timing of hopping the UL channel in the frequency direction. In other words, the Time domain window may be a period during which the UL channel is not hopped in the frequency direction.

(4.4) Operation example 4
Operation example 4 will be described below. In operation example 4, when two or more specifying methods for setting a specific period (time domain window) are defined, a case will be illustrated in which the time domain window is applied based on two or more specifying methods. The specifying method is one or more methods selected from the operation examples 1 to 3 described above.

For example, consider a case where Time domain window #A and Time domain window #B are set as shown in FIG. Time domain window #A may be the Time domain window set by the RRC message, and Time domain window #B may be the Time domain window set by DCI. Alternatively, Time domain window #A may be the Time domain window set based on the slot format, and Time domain window #B may be the Time domain window set based on the allocated resources. good. In such cases, the following options may be adopted.

In option 1, UE200 applies Time domain window #B as one Time domain window in the section where Time domain window #A overlaps Time domain window #B, and Time domain window #A is Time domain window #B Time domain window #A may be applied as another Time domain window in intervals that do not overlap with .

In option 2, UE200 applies Time domain window #B as one Time domain window in the section where Time domain window #A overlaps Time domain window #B, and Time domain window #A is Time domain window #B Time domain window need not be applied in intervals that do not overlap with .

Options

1 and 2 are options that prioritize Time domain window #B over Time domain window #A. In other words, the time domain window set (designated) by DCI has priority over the time domain window set by the RRC message.

In Option 3, the UE 200 may integrate Time domain window #A and Time domain window #B and apply the integrated section as one Time domain window.

(4.5) Operation example 5
Operation example 5 will be described below. Operation example 5 describes the transmission power of the UL channel transmitted in the Time domain window. The UL channel may include PUCCH and may include PUSCH.

In the conventional technology, the UE 200 determines the transmission power of the UL channel in the slot used for PUSCH Repetition type B or non-nominal repetition for PUSCH Repetition type B for each transmission occasion. On the other hand, in operation example 5, when a time domain window is set, the UE 200 determines the transmission power of UL channels transmitted on transmission occasions within the time domain window for each time domain window. In other words, UE 200 uses the time domain window as the interval for determining the transmission power of the UL channel.

In the following, a case in which PUSCH is repeatedly transmitted twice in the Time domain window will be illustrated. Under this premise, the transmission power of PUSCH transmitted within the time domain window may be determined as follows.

In Option 1, as shown in FIG. 8, PUSCH transmission occurrences included in the Time domain window may be treated as one transmission occurrence. That is, the transmission power of two PUSCHs is determined for each Time domain window. In such cases, the power (terms) dependent on the MCS and TPC of each PUSCH may be calculated based on the MCS and TPC of any one PUSCH included in the Time domain window.

Any one PUSCH included in the Time domain window may be the first PUSCH included in the Time domain window or the last PUSCH included in the Time domain window (option 1-1).

Any one PUSCH included in the time domain window may be the PUSCH that requires the maximum transmission power or the PUSCH that requires the minimum transmission power among the PUSCHs included in the time domain window (option 1- 2).

Any one PUSCH included in the time domain window may be the PUSCH having the maximum symbol length or the PUSCH having the minimum symbol length among the PUSCHs included in the time domain window (option 1- 3).

Any one PUSCH included in the time domain window may be the PUSCH with the maximum TBS or the PUSCH with the minimum TBS among the PUSCHs included in the time domain window (option 1-4) .

In option 2, as shown in FIG. 9, the PUSCH transmission power determined for each time domain window may be the transmission power of any one transmission occurrence (PUSCH) included in the time domain window. The transmission power of any one transmission occurrence included in the time domain window is used as the transmission power of other transmission occurrences.

Any one transmission occurrence included in the time domain window may be the first transmission occurrence included in the time domain window or the last transmission occurrence included in the time domain window (option 2-1 ).

Any one transmission occurrence included in the time domain window may be the transmission occurrence requiring the maximum transmission power or the transmission occurrence requiring the minimum transmission power among the transmission occurrences included in the time domain window. (Option 2-2).

Any one transmission occurrence included in the time domain window may be the transmission occurrence with the maximum symbol length or the transmission occurrence with the minimum symbol length among the transmission occurrences included in the time domain window. (Option 2-3).

Any one transmission occurrence included in the time domain window may be the transmission occurrence with the maximum TBS or the transmission occurrence with the minimum TBS among the transmission occurrences included in the time domain window (optional 2-4).

In option 3, the PUSCH transmission power determined for each time domain window may be determined based on the transmission power of each transmission occurrence included in the time domain window. The PUSCH transmission power determined for each time domain window may be the average value, the minimum value, or the maximum value of the transmission power of each transmission occurrence.

(4.6) Operation example 6
Operation example 6 will be described below. In operation example 6, closed-loop power control in a case where a time domain window is set will be described.

As shown in FIG. 10, when the Time domain window is set, the UE 200 cannot receive the DL channel (here, PDCCH#B) within the Time domain window. cannot receive TPC commands (see Figure 11) that

Therefore, UE 200 executes closed-loop power control of the UL channel (here, PUSCH) based on the TPC commands included in PDCCH#A and PDCCH#B. However, since the reception interval of the TPC command is extended, there is a possibility that the existing TPC command shown in FIG. 11 cannot perform the closed-loop power control appropriately. As shown in FIG. 11, the TPC Command Field is associated with Accumulated TPC Command values (eg, _{σPUSCH,b,f,c} , _σSRS,b,f,c ).

Against this background, Operation Example 6 introduces a new Accumulated TPC Command value that is used when a Time domain window is set. The following options are conceivable for the newly introduced Accumulated TPC Command values.

In option 1, as shown in FIG. 12, a new table may be defined for use in cases where a time domain window is set, in addition to the existing table shown in FIG. The number of values that the TPC Command Field shown in FIG. 12 can specify may be the same as the number of values that the existing TPC Command Field shown in FIG. 11 can specify. The maximum Accumulated TPC Command value (eg, 4) shown in FIG. 12 may be greater than the existing maximum Accumulated TPC Command value (eg, 3) shown in FIG. The minimum Accumulated TPC Command value (eg, -4) shown in FIG. 12 may be smaller than the existing minimum Accumulated TPC Command value (eg, -3) shown in FIG.

In option 2, the existing table shown in FIG. 11 may be extended as shown in FIG. The number of values that can be specified by the TPC Command Field shown in FIG. 13 is greater than the number of values that can be specified by the existing TPC Command Field shown in FIG. wider than the range of existing Accumulated TPC Command values shown in . The Accumulated TPC Command values shown in FIG. 13 include the existing Accumulated TPC Command values shown in FIG. 11 (for example, -1, 0, 1, 3) and values other than the existing Accumulated TPC Command values shown in FIG. (e.g. -4, -3, 4, 5).

Here, the conditions for applying the Accumulated TPC Command value related to Option 1 or Option 2 are the following applicable conditions. The applicable conditions may include conditions under which the table shown in FIG. 12 or 13 is set by an RRC message or MAC CE message. Applicability conditions may include conditions under which the Time domain window is set. The application condition may be a condition that the position of the first bit of the TPC Command is a position that refers to the table shown in FIG. 12 or 13 . In other words, the position of the first bit of TPC Command may indicate whether to refer to the table shown in FIG. 12 or 13 . The format of DCI including such TPC commands may be DCI_format 2_2 or DCI_format 2_3.

The table shown in FIG. 12 or 13 may be predetermined in the wireless communication system 10, or may be set by an RRC message. For example, the RRC message may include an information element indicating the correspondence between the TPC Command Field and the Accumulated TPC Command value.

(4.7) Operation example 7
Operation example 7 will be described below. In operation example 7, application of a TA (Timing Advance) Command in a case where a Time domain window is set will be described.

In Operation Example 7, when the Time domain window is set, the UE 200 determines the timing to apply the timing information (TA Command) based on the Time domain window.

Specifically, as shown in FIG. 14, when a TA Command is received at slot #n, if the Time domain window is not set, the timing to apply the TA Command is Defined by start timing. n+k+1 is the existing timing to apply TA Command, defined in 3GPP TS38.213.

In operation example 7, when the Time domain window is set in slot n+k+1 (slot#n+2 in FIG. 14), the UE 200 determines the timing to apply the TA Command based on the Time domain window. decide. In Option 1, the UE 200 may determine the end timing of the Time domain window as the timing to apply the TA Command. In Option 2, the UE 200 may determine the end timing of the slot (slot#n+3 in FIG. 14) including the end timing of the Time domain window as the timing to apply the TA Command.

(4.8) Operation example 8
Operation example 8 will be described below. In operation example 8, the duration per hop at which the UL channel is hopped in the frequency direction when a time domain window is set will be described.

In Operation Example 8, the UE 200 determines the duration per hop of the UL channel in the frequency direction based on whether all repeated transmissions of the UL channel are included in the Time domain window. For example, a case where PUSCH repetition is 6 times will be illustrated.

First, as shown in the upper part of FIG. 15 (Case 1), the case where all PUSCH repetitions are not included in one Time domain window will be described. In such cases, the following options are conceivable as a method of determining the duration per hop.

In option 1, the UE 200 may decide to hop the UL channel in the frequency direction at the start timing or end timing of the time domain window. In Option 2, the Time domain window may be determined as duration per hop.

Second, as shown in the lower part of FIG. 15 (Case 2), the case where all PUSCH repetitions are included in one Time domain window will be described. In such cases, the following options are conceivable as a method of determining the duration per hop.

In Option 1, the UE 200 may determine the duration per hop based on the number of PUSCH repetitions. For example, the first hopping duration may be specified by a function of floor(number of PUSCH repetitions/2) and may be specified by a function of ceil(number of PUSCH repetitions/2). In option 2, the UE 200 may determine the duration per hop based on the number of time resources assigned PUSCH repetition. A time resource may be a slot or a symbol. In Option 2 like this, the UE 200 may determine the duration per hop based on the actually allocatable time resources for the PUSCH repetition. In such cases, the UE 200 may determine the actually allocatable time resources for PUSCH repetition based on the collision reason. For example, the UE 200 considers collision reasons such as TDD pattern, SS/PBCH block symbol, etc., and excludes resources such as TDD pattern, SS/PBCH block symbol from the actually allocatable time resources for PUSCH repetition. may On the other hand, the UE 200 does not consider the collision reasons such as SFI, CI, and PUCCH, and does not exclude resources such as SFI, CI, and PUCCH from the time resources that can actually be allocated for PUSCH repetition. good.

(4.9) Operation example 9
Operation example 9 will be described below. In operation example 9, UE Capability regarding joint channel estimation will be described. UE200 transmits UE Capability to NG RAN20. The UE Capability may be reported separately for each UL channel type (PUSCH/PUCCH), or may be collectively reported as a UL channel regardless of the UL channel type.

　UE Capability may include an information element indicating the number of Time domain windows that the UE 200 can set.

　UE Capability may include an information element indicating whether or not the UE 200 supports Option 3 of Operation Example 4. As described above, option 3 of operation example 4 integrates two or more time domain windows and applies the integrated section as one time domain window when two or more time domain windows are set. Optional.

　UE Capability may include an information element indicating whether or not the UE 200 supports the MAC CE message of operation example 1. As described above, the MAC CE message of Operation Example 1 is a message that activates (or deactivates) one or more Time domain windows.

　UE Capability may include an information element indicating whether or not the UE 200 supports DCI in operation example 2. As described above, the DCI of Operation Example 2 is a message that includes an information element that sets the Time domain window to Dynamic.

　UE Capability may include an information element indicating whether or not the UE 200 supports the Time domain window of operation example 3. As described above, the time domain window of operation example 3 is set based on the timing of hopping the UL channel in the frequency direction.

The E Capability may include an information element indicating whether or not the UE 200 supports the transmission power of the UL channel transmitted in the Time domain window of Operation Example 5. As described above, the transmission power of the UL channel in Operation Example 5 is determined for each Time domain window.

　UE Capability may include an information element indicating whether or not the UE 200 supports the Accumulated TPC Command value of Operation Example 6. As described above, the Accumulated TPC Command value in Operation Example 6 is a value that is used when an applicable condition such as a Time domain window is set is satisfied.

　UE Capability may include an information element indicating whether or not the UE 200 supports the application timing of the TA command in Operation Example 7. As described above, the application timing of the TA command in Operation Example 7 may be the end timing of the Time domain window (option 1) or the end timing of the slot including the end timing of the Time domain window ( Option 2). UE Capability may include an information element indicating whether Option 1 is supported, and may include an information element indicating whether Option 2 is supported.

　UE Capability may include an information element indicating whether or not the UE 200 supports the duration per hop of operation example 8. The duration per hop of Operational Example 8 is determined based on whether all repeated transmissions of the UL channel are included in the Time domain window.

　UE Capability may include an information element indicating whether the UE 200 supports each of the various options described in Operation Example 1 to Operation Example 8.

Here, the UE 200 may report the UE Capability based on the frequency supported by the UE 200. UE200 may report UE Capability as UE200 regardless of the frequency that UE200 supports. UE 200 may report UE Capability for each frequency that UE 200 supports. UE 200 may report UE Capability for each frequency range (for example, FR1/FR2) that UE 200 supports. UE 200 may report UE Capability for each SCS that UE 200 supports.

　UE 200 may report UE Capability based on the duplex scheme (TDD/FDD) that UE 200 supports. UE 200 may report UE Capability as UE 200 regardless of the duplex scheme that UE 200 supports. UE 200 may report UE Capability for each duplex scheme (TDD/FDD) that UE 200 supports.

(5) Functions and effects In the embodiment, when two or more specifying methods for setting the time domain window are defined, the UE 200 may apply the time domain window based on two or more specifying methods. According to such a configuration, when assuming a case where two or more time domain windows are set by two or more identification methods, the time domain window to be applied by the UE 200 can be appropriately determined.

In the embodiment, the UE 200 may use the time domain window as the interval for determining the transmission power of the UL channel. According to such a configuration, assuming joint channel estimation in gNB 100, the transmission power of the UL channel does not change within the time domain window, so joint channel estimation can be performed appropriately.

In the embodiment, the UE 200 may use the newly introduced Accumulated TPC Command value when the Time domain window is set. According to such a configuration, closed-loop power control can be executed appropriately when assuming a case where the TPC command reception interval is extended.

In the embodiment, when the Time domain window is set, the UE 200 may determine the timing of applying the TA Command based on the Time domain window. According to such a configuration, the TA Command can be reflected at appropriate timing.

In an embodiment, the UE 200 may determine the duration per hop for the UL channel based on whether all repeated transmissions of the UL channel are included in the Time domain window. According to such a configuration, assuming joint channel estimation in gNB 100, duration per hop can be determined appropriately, and joint channel estimation can be performed appropriately.

(6) Other Embodiments Although the contents of the present invention have been described in accordance with the embodiments, it should be understood that the present invention is not limited to these descriptions and that various modifications and improvements are possible. self-evident to the trader.

Although PUSCH repetition has been mainly described in the above disclosure, the above disclosure is not limited to this. The above disclosure can be applied to UL channels where joint channel estimation is applied.

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

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

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

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

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

In addition, each function of the device is implemented by causing the processor 1001 to perform calculations, controlling communication by the communication device 1004, and controlling the It is realized by controlling at least one of data reading and writing in 1002 and storage 1003 .

A processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including interfaces with peripheral devices, a control unit, an arithmetic unit, registers, and the like.

Also, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. Furthermore, the above-described various processes may be executed by one processor 1001, or may be executed by two or more processors 1001 simultaneously or sequentially. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

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

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

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like.

The communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc., for realizing at least one of frequency division duplex (FDD) and time division duplex (TDD). may consist of

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

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

In addition, the device includes hardware such as a microprocessor, digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic device (PLD), field programmable gate array (FPGA), etc. A part or all of each functional block may be implemented by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

In addition, 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 include 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, and RRC signaling may also be referred to as RRC messages, e.g., RRC Connection Setup ) message, RRC Connection Reconfiguration message, or the like.

Each aspect/embodiment described in this disclosure includes 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 (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)) , IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, other suitable systems, and/or next-generation systems enhanced therefrom. may be applied to Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).

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

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

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

Input/output information may be stored in a specific location (for example, memory) or managed using a management table. Input and output information may be overwritten, updated, or appended. The output information may be deleted. The entered information may be transmitted to other devices.

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

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

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

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

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 refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

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

The terms "system" and "network" used in this disclosure are used interchangeably.

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

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

In the present disclosure, "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", " Terms such as "carrier", "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area corresponding to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head: RRH) can also provide communication services.

The term "cell" or "sector" refers to part or all of the coverage area of at least one of a base station and base station subsystem that provides communication services in this coverage.

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

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

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

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

Similarly, a mobile station in the present disclosure may be read as a base station. In this case, the base station may have the functions that the mobile station has.

A radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe.

A subframe may further consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

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

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

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

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

For example, one subframe may be called a transmission time interval (TTI), a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, may be a period shorter than 1ms (eg, 1-13 symbols), or a period longer than 1ms may be Note that the unit representing the TTI may be called a slot, minislot, or the like instead of a subframe.

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

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

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

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

In addition, long TTI (for example, normal TTI, subframe, etc.) may be read as TTI having a time length exceeding 1 ms, and short TTI (for example, shortened TTI, etc.) is less than the TTI length of long TTI and 1 ms. A TTI having a TTI length greater than or equal to this value may be read as a replacement.

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

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

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

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

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

BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP). One or more BWPs may be configured in one carrier for the UE.

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

The structures such as radio frames, subframes, slots, minislots and symbols described above are only examples. For example, the number of subframes 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 Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.

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

The reference signal can also be abbreviated as Reference Signal (RS), and may also be called Pilot depending on the applicable standard.

The term "based on" as used in this disclosure does not mean "based only on" unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

"Means" in the configuration of each device described above may be replaced with "unit", "circuit", "device", or the like.

Any reference to elements using the "first", "second", etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to 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.

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

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

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

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

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

10 Radio communication system 20 NG-RAN
100 gNB
110 receiver 120 transmitter 130 controller 200 UE
210 radio signal transmission/reception unit 220 amplifier unit 230 modulation/demodulation unit 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

a transmission unit that repeatedly transmits an uplink channel in a specific period of multiple slots or more;
A control unit that controls transmission of the uplink channel,
The terminal, wherein the control unit uses the specific period as an interval for determining the transmission power of the uplink channel.
a transmission unit that repeatedly transmits an uplink channel in a specific period of multiple slots or more;
A control unit that controls transmission of the uplink channel,
The terminal, wherein the control unit determines timing to apply timing information received from a network based on the specific period.
a transmission unit that repeatedly transmits an uplink channel in a specific period of multiple slots or more;
A control unit that controls transmission of the uplink channel,
The terminal, wherein the control unit determines an interval for hopping the uplink channel in the frequency direction based on whether or not all repeated transmissions of the uplink channel are included in the specific period.
a step of repeatedly transmitting an uplink channel in a specific period of a plurality of slots or more;
and using the specific period as an interval for determining the transmission power of the uplink channel.
a step of repeatedly transmitting an uplink channel in a specific period of a plurality of slots or more;
determining when to apply timing information received from a network based on the specified period of time.
a step of repeatedly transmitting an uplink channel in a specific period of a plurality of slots or more;
determining an interval for hopping the uplink channel in the frequency direction based on whether or not all repeated transmissions of the uplink channel are included in the specific period.