RU2785054C1 - User terminal - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: to realise the technical result, the terminal comprises: a reception section configured to receive information related to the number of repeats of the physical ascending common channel (PUSCH); a transmission section configured to transmit PUSCH in the number of transmission intervals equal to the number of repeats indicated by said information; and a control section configured to apply frequency hopping for PUSCH in the transmission intervals based on the slot boundary within the transmission intervals.

EFFECT: provided control of frequency hopping when repeating a multi-segment transmission.

4 cl, 22 dwg

Description

The field of technology to which the invention belongs

The present invention relates to a user terminal in next generation mobile communication systems.

State of the art

For the Universal Mobile Telecommunications System (UMTS) network, a Long-Term Evolution (LTE) specification project was proposed, the purpose of which is to further increase the data rate, reduce latency, etc. (see non-patent document 1). In addition, in order to further increase the capacity, for improvement, etc. of the LTE system (version 8 and version 9 of the Third Generation Partnership Project, 3GPP), the specifications of the LTE-Advanced system (versions 10-14 3GPP).

LTE successor systems are also being developed (for example, the fifth generation mobile communication system (5G, 5G +), the New Radio System (English New Radio, NR), the 3GPP version 15 system and later, etc.).

In existing LTE systems (e.g., 3GPP release 8-14 systems), the user terminal (User Equipment, UE) controls the transmission of an uplink shared channel (e.g., the Physical Uplink Shared Channel (PUSCH)) and the reception a downlink shared channel (eg, a Physical Downlink Shared Channel (PDSCH)) based on Downlink Control Information (DCI).

List of Cited Materials

Non-Patent Documents

Non-Patent Document 1: 3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrsestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)," April, 2010.

Disclosure of the invention Technical task

Version 15 assumes that a time domain resource (e.g., a given number of symbols) for at least one of a given channel and signal (channel/signal) (e.g., uplink common channel (PUSCH) or downlink common channel (PDSCH) from a given transmission interval (also called a period, an act, or the like) is allocated by a user terminal (UE) within one slot.

At the same time, in future radio communication systems (for example, version 16 or later, also referred to as NR hereinafter), it is assumed that the time domain resources (for example, a given number of symbols) for a given channel/signal (for example, PUSCH or PDSCH) from a given interval, transmissions may be allocated across a slot boundary (ie, in multiple slots).

Channel/signal transmission using a time domain resource allocated in a given slot crossing transmission interval (in a plurality of slots) is also called multi-segment transmission, two-segment transmission, slot boundary crossing transmission, or the like. Similarly, channel/signal reception at a slot boundary is also referred to as multi-segment reception, two-segment reception, slot boundary crossing reception, or the like.

However, in version 15, control related to the transmission and/or reception (transmission/reception) of a signal/channel (e.g., at least one of time domain resource determination, repetitive transmission or repetitive reception, and frequency hopping) is performed assuming that in a given transmission interval, a time domain resource is allocated without crossing a slot boundary (within one slot). Thus, proper control related to multi-segment signal/channel transmission/reception is not possible in NR.

In light of the above, one of the objectives of the present invention is to provide a user terminal that can properly control multi-segment signal/channel transmission/reception.

The solution of the problem

A user terminal in accordance with one aspect of the present invention comprises: a receiving section configured to receive information related to the number of repetitions of an uplink common channel or a downlink common channel; and a control section configured to control the transmission of an uplink common channel or the reception of a downlink common channel in a slot after successive slots, the number of which is equal to the specified number of repetitions, when the uplink common channel or the downlink common channel is transmitted or received in transmission intervals, the number of which is equal to the number repetitions.

Beneficial Effects of the Invention

According to one aspect of the present invention, it is possible to properly control multi-segment signal/channel transmission/reception.

Brief description of the drawings

Fig. 1 illustrates an example of a multi-segment transmission.

Fig. 2A and 2B illustrate an example time domain resource allocation for PUSCH.

Fig. 3A and 3B illustrate an example of frequency hopping.

Fig. 4 illustrates an example of time domain resource determination according to the first aspect.

Fig. 5 illustrates an example of a first option for determining a time domain resource according to the first aspect.

Fig. 6A and 6B illustrate an example of a second time domain resource determination option according to the first aspect.

Fig. 7A and 7B illustrate examples of the first and second repetitive transmission options according to the second aspect.

Fig. 8 illustrates an example of the first version of the frequency hopping operation according to the third aspect.

Fig. 9 illustrates another example of the first version of the frequency hopping operation according to the third aspect.

Fig. 10 illustrates an example of the second version of the frequency hopping operation according to the third aspect.

Fig. 11A and 11B illustrate an example of the first option for determining the boundary at which the frequency hops, according to the fourth aspect.

Fig. 12A and 12B illustrate an example of the second determination of the boundary at which the frequency hops, according to the fourth aspect.

Fig. 13 illustrates an example of a generalized configuration of a radio communication system in accordance with one implementation.

Fig. 14 illustrates an example of a base station configuration according to one implementation.

Fig. 15 illustrates an example of a user terminal configuration according to one implementation.

16 illustrates an example of a base station and user terminal hardware configuration in accordance with one implementation.

Carrying out the Invention (Multi-segment transmission)

Version 15 assumes that a time domain resource (e.g., a given number of symbols) for at least one of a given channel and signal (channel/signal) (e.g., uplink common channel (PUSCH) or downlink common channel (PDSCH) from a given transmission interval (also called a period, an act, or the like) is allocated by a user terminal (UE) within one slot.

For example, in a given transmission interval, a UE may transmit one or more Transport Blocks (TB) using a PUSCH that is allocated a given number of consecutive symbols in a slot. In a given transmission interval, the UE may transmit one or multiple transport blocks using a PDSCH allocated a given number of consecutive symbols in a slot.

At the same time, NR (e.g., version 16 or later) assumes that time domain resources (e.g., a given number of symbols) for a given channel/signal (e.g., PUSCH or PDSCH) from a given transmission interval can be allocated with boundary crossing slots (i.e., in a plurality of slots).

Channel/signal transmission using a time domain resource allocated in a given slot crossing transmission interval (in a plurality of slots) is also called multi-segment transmission, two-segment transmission, slot boundary crossing transmission, or the like. Similarly, channel/signal reception at a slot boundary is also referred to as multi-segment reception, two-segment reception, slot boundary crossing reception, or the like.

Fig. 1 illustrates an example of a multi-segment transmission. In FIG. 1 shows an example of a multi-segment PUSCH transmission. Of course, the present invention can also be applied to other signals/channels (eg, PDSCH, etc.).

In FIG. 1, the UE is configured to control the transmission of a PUSCH placed in one slot or multiple slots based on a predetermined number of slots. More specifically, when a time domain resource for PUSCH is allocated in one or more slots in a given transmission interval, the UE may map each segment to a given number of symbols to be allocated in the corresponding slot.

Here, a segment is understood to mean a given data element, it is only necessary that it be at least part of one or more transport blocks. For example, each segment may contain one or more transport blocks, one or more coding blocks (English Code Blocks, CB), or one or more groups of coding blocks (English Code Block Groups, CBG). Note that one coding block is an element for coding a transport block, which can be obtained by dividing the transport block into one or a plurality of parts (coding block segmentation). One coding block group may contain a predetermined number of coding blocks.

The size (number of bits) in each segment may be determined, for example, based on at least one of the number of slots in which the PUSCH is allocated, the number of symbols to be allocated in each slot, and the ratio of the number of symbols to be allocated in each slot. . The number of segments need only be determined based on the number of slots in which the PUSCH is placed.

Alternatively, a segment may refer to a given number of symbols in each slot allocated in one transmission interval, or data transmitted using that given number of symbols. For example, if the start symbol of a PUSCH allocated in one transmission interval is in the first slot and the end symbol is in the second slot, then for that PUSCH, one or more of the symbols contained in the first slot may be the first segment, and one or more of the symbols contained in the second slot may be the second segment.

For example, PUSCHs #0 and #4 are each allocated a predetermined number of consecutive symbols within one slot. In this case, UΕ may map the entire segment to the allocated symbols, which are all in the same slot. It is only necessary that this segment contains, for example, one or a plurality of transport blocks. The transmission of an entire segment in one slot as described above may be referred to as a single segment transmission, a single segment transmission, or the like.

At the same time, each of the PUSCHs #1, #2, and #3 is placed in a predetermined number of consecutive symbols mapped to a plurality of slots (in this case, two slots) across a slot boundary. In this case, the UE may map a plurality of segments (eg, two segments) to different symbols to be allocated in different slots. It is only necessary that each segment contains, for example, a data element obtained by segmenting one or more transport blocks, for example, one transport block, a given number of coding blocks, or a given number of groups of coding blocks.

As mentioned above, the transmission of a plurality of segments mapped to a plurality of slots may be referred to as a multi-segment transmission, a two-segment transmission, a slot crossing transmission, or the like. It should be noted that each slot may correspond to one segment or multiple segments.

(Time domain resource allocation)

For NR, the UE's determination of a time domain resource (e.g., one or more symbols) to be allocated for PUSCH or PDSCH based on the value of a given field (e.g., Time Domain Resource Assignment or allocation, TDRA) is learned. ) in downstream control information (DCI).

For example, the UE learns to determine the start symbol S and the number (time duration or length) L of PUSCH symbols in a slot based on the value of the TDRA field in the DCI (eg, in DCI format 0_0 or 0_1).

Fig. 2A and 2B illustrate an example time domain resource allocation for PUSCH. As shown in FIG. 2A, a time domain resource allocated to PUSCH may be determined using a symbol start S relative to slot start (start symbol S relative to slot start) and a number L of consecutive symbols. It should be noted that the start symbol S may alternatively be called, for example, the index S or the position S of the start symbol.

For example, based on the value m of the TDRA field in the DCI, the UE may determine the row index (entry number or entry index), eg, m+1, in a given table. This row index may indicate a parameter (PUSCH time domain allocation parameter) related to time domain resource allocation for PUSCH (may define the specified parameter or may be associated with the specified parameter).

The time domain placement parameter of the PUSCH may comprise, for example, at least one of the following:

- information (offset information, K2 information) indicating the time offset K2 (also referred to as k2, K ₂ or the like) between the DCI and the PUSCH scheduled using this DCI;

- information (mapping type information) indicating the PUSCH mapping type and an identifier (Start and Length Indicator (SLIV)) indicating a combination of the start symbol S and the number L of symbols (or the start symbol S and the number of L characters).

The PUSCH time domain allocation parameter corresponding to each row index may be specified by an upper level via a predetermined list (for example, Information Elements (IE) pusch-TimeDomainAllocationList or PUSCH-

TimeDomainResourceAllocationList of the Radio Resource Control (RRC) layer or may be defined in advance in the specification.

For example, the UE, upon detecting a PUSCH scheduling DCI slot #n, may determine the slot for PUSCH transmission based on the K2 information indicated by the row index (eg, m+1) which is specified by the value m of the TDRA field in the DCI.

The UE may determine the start symbol S and the number L of symbols allocated for PUSCH in the slot as defined, based on the SLIV indicated by the row index (eg, m+1) which is specified by the value m of the TDRA field in the DCI.

More specifically, the UE may determine the start symbol S and the number L of symbols over SLIV based on a predetermined rule. For example, when (L-1) is less than or equal to 7, this predetermined rule may be the following formula 1, and when (L-1) is greater than 7, this predetermined rule may be the following formula 2.

Alternatively, the UE may determine the start symbol S and the number L of symbols allocated for PUSCH in the slot, which is defined as such, based on the start symbol S and the number V of symbols directly indicated by the row index (eg, m+1), which is given by the value m of the TDRA field in DCI.

The UE may determine the mapping type of the PUSCH based on the mapping type information indicated by the row index (eg, m+1) which is specified by the value m of the TDRA field in the DCI.

Fig. 2B shows an example of a start symbol S and a number L of symbols recognized by the UE as a permitted PUSCH allocation. As shown in FIG. 2B, the values of the start symbol S and the number L of symbols recognized as the allowed PUSCH allocation may be indicated for the PUSCH mapping type and for the cyclic prefix (CPU) length.

As shown in FIG. 2B, in NR version 15 or earlier, the largest value of the start symbol S and the number of symbols L is 14. The reason for this is that the above-described multi-segment transmission is not provided; more specifically, the PUSCH is assumed to be located in one slot, and the fixed value S=0 corresponding to the start symbol (symbol #0) of the slot is set.

Note that the above description illustrates the case where SLIV is indicated by the value of the TDRA field in the DCI (eg, the case where the PUSCH is scheduled using DCI (Upstream Grant, Dynamic Grant) or the case of a type 2 configuration grant). However, the present invention is not limited to these cases. SLIV may be set using an upper layer parameter (eg, in the case of a type 1 configuration grant).

The above description illustrates the time domain resource allocation for PUSCH. However, time domain resource allocation for the PDSCH can be done in a similar manner. The description of time domain resource allocation for PDSCH can be obtained by replacing PUSCH in the above description with PDSCH.

In the case of PDSCH, it is only necessary to replace the K2 information with information (also referred to as offset information, K0 information or the like) indicating the offset K0 (also referred to as k0, K ₀ or the like) between the DCI and the PDSCH scheduled using this DCI. Note that formulas (1) and (2) above or another formula may be used to calculate the start symbol S and the number L of symbols for the PDSCH. In the case of the PDSCH, the DCI may have, for example, the format 1_0 or 1_1 DCI.

(Repeat transmission)

For NR, PUSCH or PDSCH transmission with repetition is being studied. More specifically, NR studies the transmission of a transport block generated from the same data in one or more transmission intervals. Each of the transmission intervals is located within one slot, and the specified transport block can be transmitted N times in N consecutive slots. In this case, the terms "transmission interval", "slot" and "repetition" can be used interchangeably.

The repeated transmission may be referred to as slot pooling transmission, multi-slot transmission, or the like. The number N of repetitions (number of aggregations, aggregation factor) may be indicated to the UE using at least one of the upper layer parameter (eg, pusch-Aggregation Factor or pdsch-AggregationFactor from RRC layer information elements) and DCI.

N consecutive slots may use the same symbol arrangement. This uniform symbol allocation across slots may be determined in the same manner as described for time domain resource allocation. For example, the UE may determine the placement of symbols in each slot based on the start symbol S and the number L of symbols, which are determined based on the value m of a given field (eg, TDRA field) in the DCI. Note that the UE may determine the start slot based on the K2 information determined based on the value m of a given field (eg, TDRA field) in DCI.

In these N successive slots, the Redundancy Version (RV) applied to the transport block generated from the same data may be the same, or at least part of the RV may be different. For example, the RV applied to the transport block in the nth slot (transmission interval, repetition) may be determined based on the value of a given field (eg, RV field) in the DCI.

When a resource allocated to N consecutive slots has a link direction (which may be uplink, downlink, or soft redirect) indicated using at least one of the uplink and downlink indication information (e.g., TDD -UL-DL-ConfigCommon or TDD-UL-DL-ConfigDedicated from RRC layer information elements) for Time Division Duplex (TDD) control and slot format indicator from DCI (e.g. DCI format 2_0), different for each slot in at least one symbol, transmission (or reception) in the slot resource containing the specified symbol may not be possible.

(Frequency hopping)

In NR, frequency hopping (FH) can be applied to a signal/channel. This is described next. For example, inter-slot hopping or intra-slot hopping may be applied to PUSCH.

Intra-slot hopping can be applied to both PUSCH transmitted with repetition and PUSCH transmitted without repetition (once). Inter-slot hopping may be applied to the PUSCH transmitted repeatedly.

The frequency offset (also referred to simply as offset) between frequency hopping levels (also referred to simply as frequency levels) (e.g., the offset between the first frequency level and the second frequency level) may be determined based on at least one of the upper layer parameter and the value specified field in DCI. For example, for a grant (dynamic grant) in a DCI or a configuration grant (configuration grant type 2) whose activation is controlled by that DCI, a plurality of shifts (e.g., two or four shifts) can be specified using an upstream parameter, and one of the specified set of shifts may be specified using the value of the specified field in the DCI.

Fig. 3A and 3B illustrate an example of frequency hopping. In FIG. 3A shows how inter-slot frequency hopping is applied in repetitive transmission, which can be controlled for each slot. The resource block (eng. Resource Block, RB) of the start of application of each frequency level may be determined based on at least one of the index RB _start of the initial RB resource of the frequency domain allocated for this PUSCH, the offset RB _offset given by at least -something one of the upper layer parameter and the value of the given field in DCI, and the size (number of resource blocks) N _Bwp in the given band (for example, in BWP).

For example, as shown in FIG. 3A, the even slot number start RB slot index may be RB _start , and the odd slot number start RB slot index may be calculated using RB _start , RB _offset and N _Bwp (for example, according to the following formula (3)).

UΕ may define a frequency domain resource (e.g., a resource block or a Physical Resource Block (PRB)) allocated to each slot (repetition, transmission interval) that is determined based on the value of a given field (e.g., resource allocation field frequency domain (Frequency Domain Resource Allocation, FDRA) in DCI. UΕ may determine RB _start based on the value of the FDRA field.

It should be noted that when, as shown in FIG. 3A, inter-slot frequency hopping is applied, intra-slot frequency hopping shall not be applied.

As shown in FIG. 3B, intra-slot frequency hopping may be applied to non-repetition transmission. Alternatively, although not shown, intra-slot hopping may be applied in each slot (transmission interval) of a repetitive transmission. RB start applying each frequency level in FIG. 3B may be determined similarly to the inter-slot hopping case described with reference to FIG. 3A.

In intra-slot frequency hopping in FIG. 3B, the number of symbols at each frequency level (the boundary of each frequency level or the boundary at which the frequency changes) may be determined based on the number N _symb of symbols allocated to the PUSCH in a given transmission interval.

The above-described time domain resource allocation, repetitive transmission, and frequency hopping are designed for a configuration in which the time domain resource allocated to a signal/channel in a given transmission interval is in one slot (does not cross a slot boundary).

At the same time, as described above, in NR (for example, version 16 or later), the introduction of multisegment transmission, in which a time domain resource is located in a plurality of slots (slot border crossing) in a given transmission interval, is being studied. In this situation, it is not clear how to manage the multi-segment transmission.

In light of this, the present inventors have explored the definition of a time domain resource that can be applied to multi-segment transmission (first aspect), repetitive transmission (second aspect), frequency hopping in repetitive transmission (third aspect), and frequency hopping within a single transmission interval ( the fourth aspect), resulting in the idea of properly controlling the transmission or reception of a signal/channel using a time domain resource allocated in a given transmission interval in one or more slots.

Next, with reference to the drawings, implementations of the present invention are described in detail. It should be appreciated that the first through fourth aspects described below may be used alone, or a combination of at least two of these aspects may be used.

(First aspect)

In the first aspect, the definition of a time domain resource is described, which can also be applied to multi-segment transmission. As described above, version 15 assumes that the time domain resource allocated for PUSCH or PDSCH in a given transmission interval fits entirely in one slot (does not cross a slot boundary), and when defining the start symbol S and the number L of symbols as the reference (base) the beginning of the slot is used. Thus, the UE may not be able to properly determine a time domain resource for a PUSCH or PDSCH when that resource is allocated in a given transmission interval in multiple slots (slot boundary crossing).

In light of the above, in a first aspect, it is proposed to report a time slot used as a base for determining a PUSCH or PDSCH start symbol in a given transmission interval (first time domain resource definition). Another suggestion is to assign an index to each element containing a plurality of characters in a plurality of consecutive slots (a first variant of the definition of a time domain resource). Such a configuration makes it possible to properly determine the time domain resource allocated in a given transmission interval in multiple slots (slot boundary crossing).

In the following described first aspect, it is mainly about PUSCH. However, the present invention is applicable to other channels (eg PUSCH). The following describes PUSCH based on a dynamic grant. However, the present invention is also applicable to PUSCH based on a Type 2 Configuration Grant or a Type 1 Configuration Grant.

<First Time Domain Resource Definition>

In the first embodiment of time domain resource determination, the UE is configured to receive information related to a time interval from which a PUSCH start symbol is determined (also called a base time slot, base start time slot, symbol time slot, start symbol time slot, or the like). P.).

The information relating to the base time interval may be, for example, information indicating the value S' of the base time interval. The base slot value S' may be represented by, for example, an offset value from the start of a slot, a number of symbols from the start of a slot, or the like.

The base slot value S' may be indicated using at least one of an upper layer parameter and a predetermined field value in the DCI (eg, DCI for PUSCH scheduling). This given field may be different from the TDRA field used to determine SLIV and may be referred to as a base slot field or the like. The value of this given field may indicate one value of one or more possible values S' of the base time interval. These possible values may be predetermined in the specification or specified using an upper layer parameter (eg, an RRC layer information element).

UΕ may determine the base slot value S' based on at least one of the overlay parameter and the value of the predetermined field in the DCI. Based on the base slot value S' and SLIV (or the start symbol S and the number L of symbols), the UE may determine the time domain resource allocated for the PUSCH.

For example, the UE, when determining the time domain resource allocated to PUSCH, which is performed based on SLIV (or the start symbol S and the number of L symbols), may base not the slot start, but the symbol indicated by the base slot value S' with respect to to the beginning of the slot.

As stated above, the UE may determine SLIV based on the value m of the TDRA field in the DCI for PUSCH scheduling. More specifically, the UE may select an SLIV (or an initial S symbol and an L symbol) which is indicated by the index of the string specified by the value m of the TDRA field in a given table. Based on the SLIV thus selected, the UE may determine the start symbol S and the number of symbols.

It is also possible for the UE to determine the base slot value S' based on the m value of the TDRA field. More specifically, the UE may select a base slot value S', which is indicated by an index of the row specified by the value m of the TDRA field, in a given table. In this case, the PUSCH placement parameter in the time domain may contain the specified base time slot value S'. In such a configuration, the addition of a new field to the DCI is not required to indicate the value S' of the base timeslot.

UΕ, as the time domain resource allocated to the PUSCH, may determine L consecutive symbols starting from the start symbol S counted from the symbol indicated by the base slot value S' defined as described above.

Fig. 4 illustrates an example of time domain resource determination according to the first aspect. For example, in FIG. 4, for the UE, based on the SLIV determined based on the value m of the TDRA field in the DCI, the symbol S=0 is determined as the start symbol. The value S' of the base time interval is determined based on the value of the given field in the DCI.

In a given slot (e.g., a slot determined based on the K2 information), the UE, as the time domain resource allocated for PUSCH, may determine L consecutive symbols starting from the #S'+S symbol followed by the #S' symbol by starting character S, (in other words, from character #S'+S to character #S'+S+L).

Thus, the start symbol S may be indicated by an offset value (also called a relative value indicating a start symbol, a value indicating a relative start time interval, a value indicating a relative start position, or the like) with respect to a base time interval (for example, from a symbol, which is assigned the index S' (symbol #S')) determined by the value S' of the base time interval.

Fig. 5 illustrates an example of a first option for determining a time domain resource according to the first aspect. In FIG. 5, by way of example, the possible values S' of the base time interval are 0, 3, 7, and 10. It should be noted that these possible values are only examples, and their number, the values themselves, and the like. are not limited to those shown in the figure.

In the example in FIG. 5, the start symbol S determined based on the value m of the TDRA field in the DCI is 0, and the number L of symbols is 14. However, the values of S and L are not limited to this example. The UE determines the K2 information based on the value of m of the TDRA field, and as the time domain resource allocated to the PUSCH, determines L consecutive symbols from the #S'+S symbol of the slot determined based on the indicated K2 information.

As shown in FIG. 5, when the base slot value S' is greater than 0 (3, 7, and 10 in FIG. 5), the PUSCH is allocated to successive symbols in the plurality of slots across a slot boundary. The UE is configured to segment the PUSCH (one or multiple transport blocks) to match the specified plurality of slots, and to transmit the segmented PUSCH.

In this manner, by informing the UE of the base offset value S', it is possible to determine the time domain resource allocated for the PUSCH based on the value m of the TDRA field in the DCI on a symbol-by-symbol basis. In this case, the time domain resource may be allocated on a symbol-by-symbol basis in both single-segment transmission (eg, with S'=0 in FIG. 5) and multi-segment transmission (eg, with S'=3, 7, or 10 in FIG. 5). ).

Note that the size (number of bits) of a given field in the DCI indicating the base slot value S' may be predefined in the specification, or may be determined based on the number X _S' of possible base slot values S' given using the upper layer parameter (eg, RRC layer information element). For example, the size of this given field may be determined by the formula ceil{log ₂ (X _S' )}.

The DCI information containing the predetermined field indicating the base slot value S' is the DCI used for scheduling the specified PUSCH, and its format may be, for example, DCI format 0_0 or 0_1, or a DCI format other than the specified formats. Such a different DCI format can be, for example, the DCI format for scheduling PUSCH for a special type of transmitted data (eg, in Ultra Reliable and Low Latency Communications (URLC) technology).

The UE may determine whether a predetermined field indicating the base slot value S' is included in the DCI based on at least one of the following items (1) to (4).

(1) Radio Network Temporary Identifier (RNTI) used in the radio network to scramble DCI information bits with cyclic redundancy check (CRC scrambling);

(2) DCI format size;

(3) the configuration of the search space in which DCI is monitored;

(4) the frequency band (eg, elementary carrier (EC, also called cell, serving cell, carrier, or the like) or Bandwidth Part (BWP)) in which a given DCI is detected.

When a PUSCH is scheduled using a 0_0 format DCI, the UE may assume or assume that a given field indicating the base slot value S' is not contained in that 0_0 format DCI, or may assume or assume that the value of S' is 0. The UE may consider that in a given transmission interval the PUSCH is located in one slot (without crossing a slot boundary).

In the first embodiment of time domain resource determination, reporting the base offset value S' to the UE enables proper determination of the PUSCH time domain resource for multi-segment transmission, using a known method for determining the time domain resource for a given SLIV (or start symbol S and number L of symbols).

<Second Time Domain Resource Definition>

In a second embodiment of the time domain resource definition, the time domain resource for the PUSCH may be allocated on an element-by-element basis using a non-character temporal element (eg, a temporal element containing multiple consecutive symbols).

In the second embodiment of the time domain resource definition, slot boundary crossing time domain resource allocation (in other words, multisegment transmission) can be implemented by allocating a time domain resource for PUSCH on an element-by-element basis using a time element containing a plurality of consecutive symbols.

More specifically, each temporary element contained in the plurality of consecutive slots may be assigned an index (also called an element index, a temporary element index, or the like). For example, a plurality of slots may contain 14 temporary elements, and these 14 temporary elements, in ascending order in the time direction, may be assigned indexes #0 through #13.

The number of symbols constituting each time element may be determined based on the number of inter-symbol boundaries crossed when placing a PUSCH (in other words, based on the number of slots in which one PUSCH (one repetition) is placed). For example, when a PUSCH is placed in two slots with a single inter-symbol boundary crossing, each time element may contain two consecutive symbols. The number of symbols constituting each time element need not be the same, and, for example, three and four symbol time elements may coexist in a plurality of consecutive slots.

The number of symbols constituting each temporal element (also referred to as an element schema, element configuration, or the like) may be predetermined in the specification, or may be determined using a higher layer parameter.

Instead of indicating to the UE a combination of the start symbol S and the number L of symbols, SLIV can be used as an identifier indicating the combination of the first time element (initial element) S allocated for PUSCH and the number L of time elements in a row starting from the time element S, SLIV can be used. , determined based on the value m of the TDRA field in DCI.

More specifically, the UE may select SLIV (or S and L), which is indicated by the index of the row specified by the value m of the TDRA field in DCI, in a given table. Based on the SLIV, the UE may determine the initial element S and the number L of elements. Alternatively, the UE may select an initial element S and the number L of elements, which are indicated by the row index determined by the value m of the TDRA field in the DCI, in a given table.

Fig. 6A and 6B illustrate an example of a second time domain resource determination option according to the first aspect. As an example, in FIG. 6A and 6B, S=3 and L=7 are determined from SLIV, which is determined based on the m value of the TDRA field in DCI. However, the values of S and L are not limited to those shown in the figures.

In FIG. 6A shows a case in which L consecutive symbols (L=7) are allocated to the PUSCH on a symbol-by-symbol basis, starting from the start symbol #S (in this case, S=3). In FIG. 6B shows a case in which L successive elements (L=7) are allocated to the PUSCH on an element-by-element basis, starting from the leading element #S (in this case, S=3).

In the shown in FIG. 6In the case of using a time element, the SLIV value (or the S and L values) is interpreted as a value indicating the time element allocated for PUSCH, and not as a value indicating the symbol allocated for PUSCH.

In the case of using a time element, the smallest value of the time domain resource allocated for PUSCH is equal to the length of one time element (eg, two symbols in FIG. 6B). The largest time domain resource value is obtained by multiplying the length of one time chip by the number of time chips (=14) (eg, in FIG. 6B, this is 28 symbols).

In the shown in FIG. 6In a variant of interpreting SLIV (or S and L) as a value indicating the time chips allocated to the PUSCH, it is possible to allocate a time domain resource to the PUSCH in a plurality of slots using a known method.

The UE may determine which basis, per symbol or per element, is used when indicating by means of the SLIV value (or the S and L values) the time domain resource for the PUSCH based on at least one of the following items (1) through ( four).

(1) RNTI used for DCI CRC scrambling;

(2) DCI format size;

(3) the configuration of the search space in which DCI is monitored;

(4) the frequency band (eg EH or BWP) in which the DCI is detected.

Alternatively, when indicating by means of the SLIV value (or the S and L value) the time domain resource for the PUSCH, the basis, per symbol or per element, can be reported to the UE using an upper layer parameter (eg, an RRC layer information element).

When PUSCH is scheduled using DCI format 0_0, the UE may assume or assume that the basis for the SLIV determined based on the value of the TDRA field in DCI format 0_0 (or for S and L) is per symbol.

The second option for determining the time domain resource makes it possible to properly determine the PUSCH time domain resource for a multi-segment transmission, using the known method for determining the time domain resource for a given SLIV (or the initial symbol S and the number L of symbols), and it is not even necessary to report the value S' of the base time interval, as in the first variant of the time domain resource definition.

As described above, in a first aspect, a time domain resource allocated in a multi-segment transmission can be determined using a known method designed to allocate a time domain resource in a given transmission interval within one slot. This makes it possible to implement multi-segment transmission without increasing implementation costs.

(second aspect)

In the second aspect, repetition of a multi-segment transmission is described. The UE, upon receiving information indicating the number of repetitions X (also referred to as a combining factor, number of combining, repetition factor, or the like), may consider that the multi-hop transmission is repeated X times (in X transmission intervals).

UΕ may consider that the time domain resource in each repetition (transmission interval) is allocated using the same scheme. The specified scheme may contain at least one of the start position and time duration in a given transmission interval.

For example, the schema may contain a start symbol relative to a base time interval (eg, symbol #S') indicated by the value S' of the base time interval and the number of symbols (a first time domain resource definition), or may contain a start element relative to the beginning of the slot, and the number of elements (the second option for determining the time domain resource). Thus, the second aspect may be used in combination with the first aspect.

In a multi-segment transmission with X repetitions, X' consecutive slots may be used for the UE, where X' is a number greater than X, for example, X'=X+1 (first repetition transmission option), or X consecutive slots (second repetition transmission option). transmission).

In the following, the second aspect described is mainly about PUSCH. However, the present invention is applicable to other channels (eg PUSCH). The following describes PUSCH based on a dynamic grant. However, the present invention is also applicable to PUSCH based on a Type 2 Configuration Grant or a Type 1 Configuration Grant.

<First Repeat Transmission Variant>

In the first variant of the repeated transmission, the UE may consider that the multi-hop transmission is repeated X times in X' consecutive slots, where X' is a number greater than X repetitions of the multi-hop transmission.

Fig. 7A is a diagram of an example of the first repetitive transmission option according to the second aspect. In the example in FIG. 7A, all X (in this case X=4) PUSCH repetitions are scheduled using one DCI. It is only necessary for the UE to indicate the number X of repetitions using at least one of the upper layer parameter and the DCI. In FIG. 7A shows the time domain resource allocated for PUSCH in the j-th (eg, 1≤j≤X) repetition (transmission interval).

As shown in FIG. 7A, when multi-hop transmission is not used, the number of slots equal to the number of X repetitions can be used for PUSCH transmission (for example, in FIG. 7A, it is four slots). At the same time, when using multi-hop transmission, X' slots may be used for PUSCH transmission, where X is a number greater than X repetitions (for example, in FIG. 7A, it is five slots).

In X repetitions (transmission intervals) of a multi-segment transmission, different redundancy versions (RV) may be applied to transport blocks generated from the same data. The RV applied to each of the X repetitions may be specified using a value of a predetermined field in the DCI (eg, an RV field), or may be specified using an RRC (upper layer parameter) signaling or the like.

As shown in FIG. 7A, a time domain resource allocated using the same scheme can be used in all X repetitions (transmission intervals), regardless of whether the transmission is a multi-hop transmission. In this case, the repetition gain can be appropriately obtained in multi-segment transmission as well.

<Second Recurring Transmission Option>

In the second case of repeated transmission, the UE may consider that in a transmission interval containing a symbol that goes beyond consecutive slots equal to the number of X repetitions of the multi-hop transmission, at least a portion of the multi-hop transmission is canceled.

Fig. 7B illustrates an example of a second repetitive transmission option according to the second aspect. For FIG. 7B will mainly describe the difference from FIG. 7A. In FIG. 7B shows how, when using multi-segment transmission, a portion of the time domain resource for multi-segment transmission in a given transmission interval (eg, in a transmission interval with j=X) falls outside of X successive slots. In this case, in this part of the time domain resource, the UE may cancel transmission (transmission of part of one segment).

In FIG. 7B, for repetition in multi-segment transmission, only consecutive slots are used, the number of which is equal to the number of X repetitions (in FIG. 7B, these are four slots). This makes it possible to avoid the complexity of scheduling that occurs in multisegment repetition transmission due to the mismatch between the number of X repetitions and the number of consecutive slots.

As mentioned above, according to the second aspect, the UE can keep proper control when performing multi-segment transmission with repetition.

By setting the number of slots in which multi-hop transmission is performed to a predetermined number of repetitions, the base station can properly manage resources.

(Third aspect)

In a third aspect, frequency hopping is described when a multi-segment transmission is repeated. In the case of repeating a one-seg transmission as described above, inter-slot frequency hopping may be applied (eg, FIG. 3A). At the same time, in the case of repetition of multi-segment transmission, the question arises of how to control frequency hopping.

In a third aspect, frequency hopping control in case of repetition of multi-segment transmission may be performed for each slot (first variant of frequency hopping operation) or for each repetition (transmission interval) (second variant of frequency hopping operation).

In the following third aspect, we are talking mainly about PUSCH. However, the present invention is applicable to other channels (eg PUSCH). The following describes PUSCH based on a dynamic grant. However, the present invention is also applicable to PUSCH based on a Type 2 Configuration Grant or a Type 1 Configuration Grant.

<First Variant of Frequency Hopping Operation>

In the first variation of the frequency hopping operation in repetition of multi-hop transmission, frequency hopping within one transmission interval (one repetition, one multi-hop transmission) can be applied using a slot boundary as a boundary at which frequency hops.

Fig. 8 is a diagram of an example of the first frequency hopping operation according to the third aspect. For FIG. 8 mainly describes the difference from FIG. 3A. For the case in FIG. 8, the RB _offset between frequency levels may be indicated using at least one of the upper layer parameter and the DCI.

The UE may determine the index of the initial resource block (RB) allocated for multi-hop transmission with X repetitions based on the value of a specified field in the DCI (for example, the value of the FDRA field) or an upper layer parameter (for example, frequencyDomainAllocation in the rrc-ConfiguredUplinkGrant information element of the RRC layer) .

As shown in FIG. 8, when a multi-segment transmission is repeated, a frequency resource may hop within one transmission interval (one repetition), while a slot boundary is used as a frequency hopping boundary.

For example, in the case not of FIG. 8 in the jth transmission interval, the index of the initial RB segment before the slot boundary (first segment) may be RB _start , and the index of the initial RB segment after the slot boundary (second segment) in the specified transmission interval may be calculated using at least one from RB _start , RB _offset and N _Bwp (for example, according to the above formula (3)).

Of course, although not shown, the initial RB of the first segment may be determined using at least one of RB _start , RB _offset and N _BWP and the initial RB of the second segment may be RB _start .

In FIG. 8, the frequency hopping patterns in different transmission intervals are the same, but the present invention is not limited to this. For example, as shown in FIG. 9, frequency hopping patterns in different transmission spans may change. More specifically, in FIG. 9 shows that the initial RB index of the first slot and the initial RB index of the second slot in adjacent transmission intervals (the jth transmission interval and the (j+1)th transmission interval) may change from one to the other.

For example, the initial RB index of the first slot in the jth (e.g., j is an odd number) transmission interval may be RB _start , and the initial RB index of the second segment in the specified transmission interval may be computed based on at least one of the RB _start , RB _offset , and N _BWP (for example, according to formula (3)) as shown in FIG. 9. In this case, as shown in FIG. 9, a non-hopping scheme can be used within a slot (in other words, one frequency resource can be used).

Alternatively, the start RB index of the first slot in the (j+1)th (e.g., (j+1) is an even number) transmission interval may be a value computed based on at least one of RB _start , RB _offset and N _BWP (for example, according to formula (3)), and the start RB index of the second segment that belongs to slot #n+2 in the specified transmission interval may be RB _start . It should be noted that Fig. 8 and 9 are just examples, and the initial RB of each frequency level is not limited to that shown in these figures.

As stated above, the initial RBs of the first slot and the second slot may be determined based on what number those slots have in the transmission spans.

Alternatively, the initial RBs of the first slot and the second slot may be determined based on the slot number in which the transmission interval starts. For example, if the initial RB index of the first segment in a transmission interval starting in an even slot number slot is RB _start , then the initial RB index of the first segment in a transmission interval starting in an odd slot number slot may be calculated based on at least - one of RB _start , RB _offset and N _BWP (for example, according to formula (3)).

In the case of FIG. 9, the same frequency resource is used to transmit segments contained within the same slot but belonging to different likely transmission intervals (eg, the second segment in the jth transmission interval and the first segment in the (j+1)th transmission interval). Therefore, it is possible to use the channel estimation results obtained in the previous transmission interval for the second segment, and perform the channel estimation for the first segment in the following transmission interval.

In the first variation of the frequency hopping operation, when frequency hopping between slots is set using an upper layer parameter, frequency hopping within each transmission interval can be applied in multi-segment transmission using a slot boundary as the boundary at which frequency hops (also called intra-segment multisegment transmission, intra-segment frequency hopping, or the like).

Alternatively, when intra-slot frequency hopping is specified using an upper layer parameter, intra-slot frequency hopping may be applied in a multi-segment transmission. Alternatively, if intra-segment frequency hopping is specified in multi-segment transmission in addition to inter-slot frequency hopping or inter-slot and intra-slot frequency hopping in multi-segment transmission, multi-segment transmission may apply intra-segment frequency hopping in multiple segments .

The first version of the frequency hopping operation, and in the case of multi-segment transmission, enables frequency hopping control using the slot boundary as a base.

<Second version of frequency hopping operation>

In the second variant of the frequency hopping operation, the frequency resource hopping when the multi-segment transmission is repeated can be controlled in each transmission interval.

Fig. 10 illustrates an example of the second version of the frequency hopping operation according to the third aspect. For FIG. 10 will mainly describe the difference from FIG. 8. As shown in FIG. 10, when repeating a multi-hop transmission, frequency resource hopping can be performed between transmission intervals (repetitions), similar to single-hop transmission.

For example, in FIG. 10 shows that the start RB index in the jth (eg, j is an odd number) transmission interval may be RB _start , and the value of the start RB index of the first slot in the (j+1)th (eg, (j+1)) is an odd number) transmission interval may be calculated based on at least one of RB _start , RB _offset , and N _BWP (eg, formula (3)). It should be noted that Fig. 10 is just an example, and the initial RB of each frequency level is not limited to that shown in this figure.

As indicated above, the initial RB of each transmission interval may be determined based on the number of that transmission interval in the transmission intervals.

Alternatively, the initial RB of each transmission interval may be determined based on the slot number in which that transmission interval begins. For example, if the start RB index in a transmission interval starting in an even slot number slot is RB _start , then the start RB index in a transmission interval starting in an odd slot number slot can be computed based on at least one of the RBs. _start , RB _offset and N _BWP (for example, according to formula (3)).

In the second version of the frequency hopping operation, when frequency hopping between slots is set using an upper layer parameter, frequency hopping between transmission intervals (repetitions) can be applied in multi-segment transmission (which is also called multi-segment transmission with frequency hopping between slots, hopping frequency between transmission intervals, or the like).

Alternatively, when intra-slot frequency hopping is specified using an upper layer parameter, intersegment frequency hopping may be applied in a multi-segment transmission. Alternatively, if inter-segment frequency hopping in multi-segment transmission is specified in addition to inter-slot frequency hopping or inter-slot and intra-slot frequency hopping using the higher layer parameter, inter-segment frequency hopping in a plurality of segments can be applied in multi-segment transmission. .

In the second version of the frequency hopping operation, frequency hopping can be performed between transmission intervals in both multi-segment transmission and single-segment transmission.

<Modification Examples>

In the first and second variations of the frequency hopping operation, the first variation and the second repetition transmission variation according to the second aspect may be combined. More specifically, as described in the first embodiment of the repeated transmission according to the second aspect (eg, with reference to FIG. 7A), the above-described FIGS. 8-10 illustrate a case in which UΕ considers that the multi-seg transmission is repeated X times in X' successive slots, where X' is a number greater than X repetitions of the multi-seg transmission. However, the present invention is not limited to this case.

As described in the second variant of the repeated transmission according to the second aspect (eg, with reference to FIG. 7B), the UE in multi-hop transmission may cancel at least a portion of the transmission by doing so in a slot after slots equal to the number of X repetitions of the multi-hop transmission.

For example, in the one shown in FIG. 8 in the case of multi-segment transmission, the second segment in the fourth transmission interval (the transmission interval indicated by the index j=4) belongs to the slot after the slots whose number is equal to the number of repetitions (=4) (the fifth slot, counting from the slot in which the first transmission interval began ). Thus, the UE may cancel the transmission of the second segment in the fourth transmission interval (may not perform this transmission). Similarly, the transmission of the second segment in the fourth transmission interval may also be canceled by the UE in the multi-segment transmission shown in FIG. 9 and FIG. 10 (may not perform this transfer).

Of course, the time domain resource allocated to the PUSCH in each transmission interval in FIG. 8-10 may be determined using the first or second time domain resource determination options described in the first aspect.

As described above, according to the third aspect, appropriate frequency hopping control is also possible in multi-segment repetition transmission.

(Fourth aspect)

In the fourth aspect, frequency hopping within a transmission interval is described. In single-seg transmission, intra-slot frequency hopping (eg, as in FIG. 3B) can be applied to both the repetition case and the single non-repetition case. At the same time, in multi-segment transmission, the question arises of how to control frequency hopping within a transmission interval (also called intra-slot frequency hopping, intra-segment multi-segment transmission, or the like).

In the fourth aspect, a frequency hopping boundary when frequency hopping within a transmission interval may be determined based on the number N _symb of symbols allocated for PUSCH (the first option for determining a frequency hopping boundary) or based on a slot boundary (the second option determining the boundary at which the frequency changes abruptly).

Note that frequency hopping within a transmission interval can apply to both single-segment transmission and multi-segment transmission. Frequency hopping within a transmission interval may be applied to at least one case of a repetition case and a single transmission case without repetition in a single-segment transmission or a multi-segment transmission.

In the fourth aspect described below, it is mainly about PUSCH. However, the present invention is applicable to other channels (eg PUSCH). The following describes PUSCH based on a dynamic grant. However, the present invention is also applicable to PUSCH based on a Type 2 Configuration Grant or a Type 1 Configuration Grant.

<The first option to determine the boundary at which the frequency hops>

In the first option of determining the boundary at which the frequency hops, the UE may determine the boundary at which the frequency hops (the number of symbols in each frequency level) based on the number N _symb of symbols allocated for the PUSCH.

Fig. 11A and 11B illustrate an example of the first option for determining the boundary at which the frequency hops, according to the fourth aspect. For FIG. 11A and 11B will mainly describe the difference from FIG. 3B. The RB _offset may be determined based on at least one of the upper layer parameter and the value of a given field in the DCI. It should be noted that Fig. 11A and 11B are just examples, and the initial RB of each frequency level is not limited to that shown in these figures.

As shown in FIG. 11A, in the case of a one-seg transmission, the UE may determine the boundary at which the frequency hops in a given transmission interval based on the number N _symb of symbols allocated for the PUSCH.

As shown in FIG. 11B, in the case of multi-hop transmission, the UE may determine a boundary at which frequency hops in a given transmission interval based on the number N _symb of symbols allocated for PUSCH.

For example, in FIG. 11A and 11B show that the UE determines the number of first hop symbols according to the formula floor(N _symb /2), and the number of second hop symbols according to the formula N _symb -floor(N _symb /2). It should be noted that the number of symbols in each frequency level is not limited to the number determined by the above formulas.

In FIG. 11A and 11B show that the UE can determine the PUSCH start symbol index based on the base slot value S' (first time domain resource definition option) or based on the index of the consecutive plurality element (second time domain resource definition option). As mentioned above, the first option for determining the boundary at which the frequency hops can be used in combination with the first aspect.

In the first variant of determining the boundary at which the frequency hops, as shown in FIG. 11A and 11B, the number of symbols at each frequency level (in other words, the boundary at which the frequency hops) can be determined such that the number is the same for both single-segment transmission and multi-segment transmission.

<Second option for determining the boundary at which the frequency hops>

In the second option for determining the boundary at which the frequency hops, the UE may determine the boundary in the PUSCH transmission interval at which the frequency hops (the number of symbols in each frequency level) based on the slot boundary.

Fig. 12A and 12B illustrate an example of the second option for determining the boundary at which the frequency hops, according to the fourth aspect. For FIG. 12A and 12B will mainly describe the difference from FIG. 11B. It should be noted that Fig. 12A and 12B are just examples, and the initial RB of each frequency level is not limited to that shown in these figures.

As shown in FIG. 12A, in the case of multi-hop transmission, the UE may define a slot boundary within the specified transmission interval as a boundary at which the frequency hops in a given transmission interval.

As shown in FIG. 12B, in the case of multi-hop transmission, the UE may determine a boundary at which frequency hops in a given transmission interval based on a slot boundary in a given transmission interval and the number of symbols in each slot.

More specifically, in FIG. 12B shows that the UE can determine the boundary at which the frequency hops in the first slot based on the number A _symb of symbols in the first slot. For example, in FIG. 12B, the UE determines the number of symbols in the first frequency level in the first slot according to the formula floor(A _symb /2), and the number of symbols in the second frequency level in the first slot is determined according to the formula A _symb -floor(A _symb /2).

In FIG. 12B shows that the UE can determine the boundary at which the frequency hops in the second slot based on the symbol number B _symb of the second slot. For example, in FIG. 12B, the UE determines the number of symbols in the first frequency level in the second slot according to the formula floor(B _symb /2), and the number of symbols in the second frequency level in the first slot is determined according to the formula B _symb -floor(B _symb /2). It should be noted that the number of symbols in each frequency level of each segment is not limited to the number determined by the above formulas.

As shown in FIG. 12B, the RB _offset between frequency levels in different segments may be the same or different. In the latter case, the RB _offset may be determined based on the upper layer parameter and the value of a given field in the DCI for each individual segment.

For the cases in FIG. 12A and 12B, the UE may determine a PUSCH start symbol index based on the base slot value S' (first time domain resource definition) or based on an index of an element containing a plurality of consecutive symbols (second time domain resource definition). As mentioned above, the second option for determining the boundary at which the frequency hops can be used in combination with the first aspect.

In the second variant of determining the boundary at which the frequency hops, shown in FIG. 12A and 12B, it is possible to appropriately determine the number of symbols in each frequency level (in other words, the boundary at which the frequency hops) based on the slot boundary within the transmission interval.

According to the above, according to the fourth aspect, frequency hopping within a transmission interval can be properly controlled.

(Radio communication system)

The following describes the configuration of a radio communication system in accordance with one implementation of the present invention. In this radio communication system, the radio communication method according to each of the above-described implementations of the present invention may be used for communication individually or in combination.

Fig. 13 illustrates an example of a generalized configuration of a radio communication system in accordance with one implementation. The radio communication system 1 may be a system capable of communicating using LTE, a new 5G radio system (5G NR) and the like, the specifications of which are proposed by the 3GPP consortium.

The radio communication system 1 is configured to support dual connectivity between multiple Radio Access Technologies (RAT) (Multi-RAT Dual Connectivity, MR-DC). The MR-DC may include a dual connection between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, a dual connection between NR and LTE, and the like. (Dual connection E-UTRA-NR is referred to as EN-DC, double connection NR-E-UTRA is referred to as NE-DC).

In EN-DC, the LTE Base Station (eNB) (E-UTRA) is the Master Node (MN) and the NR Base Station (gNB) is the Secondary Node (SN). In the NE-DC, the NR base station (gNB) is the primary node (MN) and the LTE base station (eNB) (E-UTRA) is the secondary node (SN).

The radio communication system 1 is configured to support a dual connection between a plurality of base stations in one RAT (for example, a dual connection in which both MNs and SNs are base stations (gNBs) of the NR system (NR-NR dual connection, referred to as NN-DC) ).

The radio communication system 1 may include a base station 11 forming a macro cell C1 with a relatively wide coverage, and base stations 12 (12a-12c) located in the macro cell C1 and forming small cells C2 with less coverage than that of the macro cell C1. The user terminal 20 may be located in at least one cell. Placement, quantity, etc. cells and user terminal 20 is not limited in any way to the aspect shown in the diagram. Hereinafter, base stations 11 and 12 are collectively referred to as base stations 10 unless otherwise indicated.

The user terminal 20 may be connected to at least one base station from a plurality of base stations 10. The user terminal 20 is configured to use at least one of carrier aggregation (AH) and dual connection (DC) using a plurality of elementary carriers (EN).

Each EN can be included in at least one of the first frequency range (eng. Frequency Range 1, FR1)) and the second frequency range (FR2). Macro cell C1 may refer to FR1 and small cells C2 may refer to FR2. For example, the FR1 band may be 6 GHz and below, and the FR2 band may be above 24 GHz. Please note that frequency ranges, definitions, etc. FR1 and FR2 are not limited in any way, and, for example, FR1 may correspond to a frequency range above FR2.

The user terminal 20 is configured to communicate using at least one of Time Division Duplex (TDD) and/or Frequency Division Duplex (FDD) on each EN.

The plurality of base stations 10 may be connected by a wired connection (for example, a fiber optic cable in accordance with the Common Public Interface (CPRI) standard, an X2 interface, etc.) or a wireless connection (for example, NR communication) . For example, if an NR link is used as a reverse connection between base stations 11 and 12, then the base station 11 corresponding to the older station may be called the donor of the integrated access and reverse connection (Eng. Integrated Access and Backhaul, IAB), and the base station 12, the corresponding relay station may be called an IAB node.

Base station 10 may be connected to core network 30 through another base station 10 or directly. The core network 30 may comprise at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core Network (Next). Generation Core, NGC), etc.

The user terminal 20 may be a terminal supporting at least one of the communication schemes such as LTE, LTE-A, 5G, and the like.

The radio communication system 1 may use a wireless access scheme based on orthogonal frequency division multiplexing (OFDM). For example, in at least one of the downlink (downlink, DL) and uplink (uplink, UL), OFDM with a cyclic prefix (eng. Cyclic Prefix OFDM, CP-OFDM), OFDM with spread spectrum based on the discrete Fourier transform (Eng. Discrete Fourier Transform Spread OFDM, DFT-s-OFDM), multiple access with orthogonal frequency division multiple access (Eng. Orthogonal Frequency Division Multiple Access, OFDMA), multiple access on one carrier with division frequency (English Single Carrier Frequency Division Multiple Access, SC-FDMA), etc.

The wireless access scheme may be referred to as a "signal type". Note that in the radio communication system 1, a different wireless access scheme (eg, different single carrier transmission scheme, different multi-carrier transmission scheme) may be used as the wireless access scheme in the uplink and downlink.

In the radio communication system 1, a downlink shared channel (Physical Downlink Shared Channel, PDSCH) shared by all user terminals 20, a broadcast channel (Physical Broadcast Channel, PBCH) can be used as downlinks. ), downlink control channel (Physical Downlink Control Channel, PDCCH), etc.

In the radio communication system 1, uplink channels can be used as an uplink shared channel (Physical Uplink Shared Channel, PUSCH) shared by all user terminals 20, an uplink control channel (Physical Uplink Control Channel, Eng. Physical Uplink Control Channel, PUCCH), random access channel (Physical Random Access Channel, PRACH), etc.

The PDSCH carries user data, higher layer control information, System Information Blocks (SIBs), and so on. User data, higher level control information, etc. may be transmitted on the PUSCH. Master Information Blocks (MIBs) can be transmitted on the Strategic Missile Forces.

The lower layer control information may be transmitted on the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) containing scheduling information of at least one of the PDSCH and PUSCH.

Note that the DCI for PDSCH scheduling may be referred to as downstream allocation, downstream DCI, and the like, and the DCI for PUSCH scheduling may be referred to as upstream grant, upstream DCI, and the like. Note that PDSCH may be interpreted as downstream data and PUSCH may be interpreted as upstream data.

A control resource set (CORESET) and a search space may be used for PDCCH discovery. CORESET corresponds to a resource for DCI lookup. The search space corresponds to the search area and the search method for candidate PDCCHs. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with the given search space based on the search space configuration.

One search space may correspond to a candidate PDCCH corresponding to one or more levels of aggregation. One or more search spaces may be referred to as a "multiple search spaces". It should be appreciated that "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration" and the like can be interpreted interchangeably in the present disclosure.

Uplink Control Information (UCI) containing at least one of the link state information (CSI), transmission acknowledgment information (which may also be called, for example, an acknowledgment in a hybrid automatic retransmission request (eng. Random access preambles for establishing connections with honeycombs.

It should be appreciated that in the present disclosure, downlink, uplink, etc. can be named without using the term "line". In addition, different channels can be named without adding the word "physical" at the beginning.

In the radio communication system 1, a Synchronization Signal (SS), a Downlink Reference Signal (DL-RS), and the like can be transmitted. In the radio communication system 1, as a downlink reference signal (English Downlink Reference Signal, DL-RS), an individual cell-specific reference signal (English Cell-Specific Reference Signal, CRS), a reference signal of information about the channel state (English Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS) etc.

Said synchronization signal may be at least one of, for example, a primary synchronization signal (Primary SS, PSS) and a secondary synchronization signal (Secondary SS, SSS). A signal block containing an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS/PBCH block, an SS block (SSB), and so on. Please note that SS, SSB, etc. may also be referred to as a reference signal.

Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. can be transmitted as the uplink reference signal (UL-RS) in the radio communication system 1. Note that DMRS may be referred to as a user terminal-specific reference signal (UE-specific reference signal).

(Base station)

Fig. 14 illustrates an example of a base station configuration according to one implementation. The base station 10 includes a control section 110, a transmit/receive section 120, transmit/receive antennas 130, and a transmission line interface 140. Note that base station 10 may include one or more control sections 110, one or more transmit/receive sections 120, one or more transmit/receive antennas 130, and one or more transmission line interfaces 140.

It should be noted that the base station 10, in addition to the functional blocks presented in this example, related to parts important for this implementation, may contain other functional blocks that are also necessary for radio communication. Part of the operations of each of the sections described below may be omitted.

The control section 110 is configured to control the base station 10 as a whole. The control section 110 may be formed by a controller, a control circuit, or the like, well known in the art to which the present invention pertains.

The control section 110 is configured to control signal generation, scheduling (eg, resource allocation, mapping), and the like. The control section 110 is configured to control transmission and reception, measurement, and the like, which are performed using the transmission/reception section 120, the transmit/receive antennas 130, and the transmission line interface 140. The control section 110 is configured to generate data, control information, sequence, and the like. to transmit as a signal, and transmit the formed elements to the transmission/reception section 120. The control section 110 is configured to call processing (set up, release) for communication channels, control the state of the base station 10, and control radio resources.

The transmission/reception section 120 may include a baseband section 121, a radio frequency (RF) section 122, and a measurement section 123. Section 121 of the base band may contain section 1211 processing for transmission and section 1212 receiving processing. The transmit/receive section 120 may be formed by a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmit/receive circuit, or the like, well known in the art to which the present invention pertains.

The transmit/receive section 120 may be organized as a single transmit/receive section, or may contain a transmit section and a receive section. The transmission section may be formed by the transmission processing section 1211 and the RF section 122. The reception section may be formed by the reception processing section 1212, the RF section 122, and the measurement section 123.

The transmit/receive antennas 130 may be formed by antennas, such as a multi-element antenna or the like, well known in the art to which the present invention pertains.

The transmission/reception section 120 is configured to transmit the above-described downlink, synchronization signal, downlink reference signal, and the like. The transmission/reception section 120 is configured to receive the above-described uplink, uplink reference signal, and the like.

The transmit/receive section 120 is configured to generate at least one of a transmit beam and a receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), and the like.

The transmission/reception section 120 (transmission processing section 1211) is configured to perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing, such as control retransmission at the RLC layer), media access layer (MAC) processing, such as HARQ retransmission control), etc., for example, on data and control information, etc. obtained from the control section 110, and with the possibility of forming a sequence of bits for transmission.

The transmission/reception section 120 (transmission processing section 1211) is configured to perform processing for transmission, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary). ), inverse fast Fourier transform (IFFT), precoding, digital-to-analog conversion, and the like. over the specified sequence of bits to transmit, and with the possibility of issuing a baseband signal.

The transmit/receive section 120 (RF section 122) is configured to perform RF modulation, filtering, amplification, and so on. above the baseband signal and with the possibility of transmitting an RF signal through the transmit/receive antennas 130.

In addition, the transmit/receive section 120 (RF section 122) is configured to perform amplification, filtering, demodulation to baseband signal, etc., on the RF signal received by the transmit/receive antennas 130.

The transmit/receive section 120 (receive processing section 1212) is configured to apply receive processing such as A/D conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, inverse mapping , demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, etc., to the received baseband signal, and with the possibility of obtaining user data, etc.

The transmission/reception section 120 (measurement section 123) is configured to perform a measurement related to the received signal. For example, the measurement section 123 may, based on the received signal, perform a measurement in Radio Resource Management (RRM), a measurement to obtain Channel State Information (CSI), and so on. The measurement section 123 can measure reception power (for example, Reference Signal Received Power, RSRP), reception quality (for example, Reference Signal Received Quality, RSRQ), signal-to-sum ratio interference and noise (Signal to Interference plus Noise Ratio, SINR), signal to noise ratio (Signal to Noise Ratio, SNR), signal strength (for example, Received Signal Strength Indicator, RSSI) ), channel information (eg, CSI), and the like. The measurement results may be transmitted to the control section 110 .

The transmission line interface 140 is configured to perform signal transmission/reception (reverse connection signaling) with a device included in the core network 30 or other base stations 10, etc., and capable of receiving or transmitting user data (user plane data) , control plane data, etc. for user terminal 20.

Note that the transmission section and the reception section of the base station 10 in the present invention may be formed by at least one of the transmission/reception section 120, the transmission/reception antennas 130, and the transmission line interface 140.

The transmission/reception section 120 is configured to transmit information related to a time slot used as a base for determining an uplink common channel start symbol or a downlink common channel symbol in a given transmission interval (first time domain resource determination option according to the first aspect).

Said time slot related information may be a value of a given field in the downlink control information used for scheduling said uplink common channel or said downlink common channel. The value of the given field may indicate a value indicating the named time interval.

Using the upper layer parameter, a plurality of possible values indicating the time interval may be set, or the plurality may be predefined in the specification. The value of the given field in the downstream control information may indicate one value from this set of possible values.

The control section 110 is configured to determine, in one or more slots, a time domain resource allocated to an uplink common channel or a downlink common channel based on a start symbol determined using a time slot used as a base and the number of consecutive symbols starting from a specified start symbol (the first time domain resource determination option according to the first aspect). The control section 110 is configured to control the transmission of downstream control information containing a predetermined field, the value of which is used to determine the start character and the number of characters.

The transmit/receive section 120 is configured to transmit information related to the index of the initial element and the number of consecutive elements in a given transmission interval, counted from the initial element of the uplink common channel or the downlink common channel, when each element containing a plurality of symbols in the plurality of consecutive slots is assigned index (the second time domain resource definition option according to the first aspect).

Said information related to the start element index and the number of elements may be the value of a predetermined field in the downlink control information used for scheduling an uplink common channel or a downlink common channel.

The control section 110 is configured to determine a time domain resource in one slot or a plurality of slots allocated to an uplink common channel or a downlink common channel based on the start element and the number of elements (a second time domain resource determination option according to the first aspect).

The transmit/receive section 120 is configured to transmit information related to the number of repetitions of the uplink common channel or the downlink common channel (second aspect).

The control section 110 is configured to control the uplink common channel reception or the downlink common channel transmission in a slot after successive slots equal to the number of repetitions when the uplink common channel or the downlink common channel is transmitted or received in transmission intervals equal to the number of repetitions ( second aspect).

The control section 110 is configured to continue receiving the uplink common channel or transmitting the downlink common channel and in a slot after said successive slots (the first repeating transmission option according to the second aspect).

The control section 110 is configured to cancel the uplink common channel reception or the downlink common channel transmission in a slot after said successive slots (second repetitive transmission option according to the second aspect).

The control section 110 is configured to control the frequency hopping of the uplink common channel or the downlink common channel in each of the transmission intervals based on the slot boundary in each of said transmission intervals (the first frequency hopping operation according to the third aspect).

The frequency hopping pattern in said transmission intervals, the number of which is equal to the number of repetitions, may be the same (eg, FIG. 8), or at least part of said transmission intervals may be different (eg, FIG. 9).

The control section 210 is configured to control uplink common channel or downlink common channel frequency hopping between transmission intervals equal to the number of repetitions (the second frequency hopping operation according to the third aspect).

The transmission/reception section 120 is configured to transmit an uplink common channel or transmit a downlink common channel in a given transmission interval (fourth aspect).

The control section 110 is configured to determine a boundary at which a frequency hops in a given transmission interval (number of symbols at each frequency level in a given transmission interval) based on the number of symbols allocated to an uplink common channel or a downlink common channel (the first boundary determination option , at which the frequency hops, according to the fourth aspect). The control section 110 is configured to determine a boundary at which the frequency hops without regard to a slot boundary in a given transmission interval.

The control section 110 is configured to determine a boundary at which a frequency hops in a given transmission interval based on a slot boundary in that given transmission interval (the second option for determining a boundary at which a frequency hops according to the fourth aspect). The control section 110 is configured to control frequency hopping in a predetermined transmission interval between slots (eg, FIG. 12A).

The control section 110 is configured to control frequency hopping in a given transmission interval within each slot (eg, FIG. 12B). The control section 210 is configured to determine the boundary at which the frequency hops in each slot (determining the number of symbols at each frequency level per predetermined transmission interval per slot) based on the number of symbols per predetermined transmission interval per slot. .

(User terminal)

Fig. 15 illustrates an example of a user terminal configuration according to one implementation. The user terminal 20 includes a control section 210, a transmit/receive section 220, and transmit/receive antennas 230. It should be noted that the user terminal 20 may include one or more control sections 210, one or more transmit/receive sections 220, and one or more transmit/receive antennas. receiving antennas 230.

It should be noted that the user terminal 20, in addition to the functional blocks presented in this example, related to parts important for this implementation, may contain other functional blocks that are also necessary for radio communication. Part of the operations of each of the sections described below may be omitted.

The control section 210 is configured to control the user terminal 20 as a whole. The control section 210 may be formed by a controller, control circuit, or the like, well known in the art to which the present invention pertains.

The control section 210 is configured to control signal generation, display, and so on. The control section 210 is configured to control transmission/reception, measurement, and the like. using the transmit/receive section 220 and the transmit/receive antennas 230. The control section 210 generates data, control information, sequences, and the like. for transmission as a signal, and is configured to transmit the formed elements to the transmission/reception section 220.

The transmit/receive section 220 may include a baseband section 221, an RF section 222, and a measurement section 223. Section 221 of the base band may contain section 2211 processing for transmission and section 2212 receiving processing. The transmit/receive section 220 may be formed by a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmit/receive circuit, or the like, well known in the art to which the present invention pertains.

The transmit/receive section 220 may be organized as a single transmit/receive section, or may contain a transmit section and a receive section. The transmission section may be formed by the transmission processing section 2211 and the RF section 222. The reception section may be formed by the reception processing section 2212, the RF section 222, and the measurement section 223.

The transmit/receive antennas 230 may be formed by antennas, such as a multi-element antenna or the like, well known in the art to which the present invention pertains.

The transmission/reception section 220 is configured to receive the above-described downlink, synchronization signal, downlink reference signal, and the like. The transmission/reception section 220 is configured to transmit the above-described uplink, uplink reference signal, and the like.

The transmit/receive section 220 is configured to generate at least one of a transmit beam and a receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), and the like.

The transmission/reception section 220 (transmission processing section 2211) is configured to perform PDCP layer processing, RLC layer processing such as RLC layer retransmission control, MAC layer processing (for example, HARQ retransmission control), and so on. , for example, on the data and control information, etc. obtained from the control section 210, and with the possibility of generating a bit sequence for transmission.

The transmission/reception section 220 (transmission processing section 2211) is configured to perform processing for transmission, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, digital-to-analogue conversion, etc. over the specified sequence of bits to transmit, and with the possibility of issuing a baseband signal.

It should be appreciated that the decision to apply or not to apply DFT processing may be made based on the transform precoding configuration. The transmit/receive section 220 (transmit processing section 2211) is configured to perform DFT processing for a specific channel (eg, PUSCH) as the above-described transmit processing to transmit said channel using a DFT-s-OFDM scheme if precoding is enabled. with the transformation, and with the possibility of not performing the DFT processing as the above processing for transmission otherwise.

The transmit/receive section 220 (RF section 222) is configured to perform RF modulation, filtering, amplification, and so on. above the baseband signal and capable of transmitting the RF signal through the transmit/receive antennas 230.

In addition, the transmit/receive section 220 (RF section 222) is configured to perform amplification, filtering, demodulation to baseband signal, etc., on the RF signal received by the transmit/receive antennas 230.

The transmit/receive section 220 (receive processing section 2212) is configured to apply receive processing such as A/D conversion, FFT processing, ODFT (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding) , MAC layer processing, RLC layer processing, and PDCP layer processing, etc., to the received baseband signal, and with the possibility of obtaining user data, etc.

The transmission/reception section 220 (measurement section 223) is configured to perform a measurement related to the received signal. For example, the measurement section 223 may, based on the received signal, perform measurements in radio resource management (RRM), CSI measurement, and the like. Measurement section 223 may measure receive power (eg, RSRP), reception quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel state information (eg, CSI), and the like. The measurement results may be transmitted to the control section 210 .

Note that the transmission section and the reception section of the user terminal 20 in the present invention may be formed by at least one of the transmission/reception section 220, the transmission/reception antennas 230, and the transmission line interface 240.

Note that the transmit/receive section 220 is configured to receive information related to a time interval used as a base for determining an uplink common channel start symbol or a downlink common channel symbol in a given transmission interval (first time domain resource determination option according to the first aspect) .

Said time slot related information may be a value of a given field in the downlink control information used for scheduling said uplink common channel or said downlink common channel. The value of the given field may indicate a value indicating the named time interval.

Using the upper layer parameter, a plurality of possible values indicating the time interval may be set, or the plurality may be predefined in the specification. The value of the given field in the downstream control information may indicate one value from this set of possible values.

The control section 210 is configured to determine, in one or more slots, a time domain resource allocated to an uplink common channel or a downlink common channel based on a start symbol determined using a time slot used as a base and the number of consecutive symbols starting from a specified start symbol (the first time domain resource determination option according to the first aspect). The control section 210 is configured to determine the start character and the number of consecutive characters based on the value of the predetermined field in the downstream control information.

The transmit/receive section 220 is configured to receive information related to the start element index and the number of successive elements in a given transmission interval, counted from the start element of the uplink common channel or the downlink common channel, when each multi-character element in the plurality of consecutive slots is assigned index (the second time domain resource definition option according to the first aspect).

Said information related to the start element index and the number of elements may be the value of a predetermined field in the downlink control information used for scheduling an uplink common channel or a downlink common channel.

The control section 210 is configured to determine a time domain resource in one slot or a plurality of slots allocated to an uplink common channel or a downlink common channel based on the start element and the number of elements (a second time domain resource determination option according to the first aspect).

The transmit/receive section 220 is configured to receive information related to the number of repetitions of the uplink common channel or the downlink common channel (second aspect).

The control section 210 is configured to control the transmission of the uplink common channel or the reception of the downlink common channel in a slot after successive slots equal to the number of repetitions when the uplink common channel or the downlink common channel is transmitted or received in transmission intervals equal to the number of repetitions ( second aspect).

The control section 210 is configured to continue transmitting the uplink common channel or receiving the downlink common channel and in a slot after said successive slots (the first repeating transmission option according to the second aspect).

The control section 210 is configured to cancel the transmission of the uplink common channel or the reception of the downlink common channel in a slot after said successive slots (a second repetitive transmission option according to the second aspect).

The control section 210 is configured to control the frequency hopping of the uplink common channel or the downlink common channel in each of the transmission intervals based on the slot boundary in each of said transmission intervals (the first frequency hopping operation according to the third aspect).

The frequency hopping pattern in said transmission intervals, the number of which is equal to the number of repetitions, may be the same (eg, FIG. 8), or at least part of said transmission intervals may be different (eg, FIG. 9).

The control section 210 is configured to control the frequency hopping of the uplink common channel or the downlink common channel in transmission intervals equal to the number of repetitions (the second frequency hopping operation according to the third aspect).

The transmission/reception section 220 is configured to transmit an uplink common channel and receive a downlink common channel in a given transmission interval (fourth aspect).

The control section 210 is configured to determine a boundary at which a frequency hops in a given transmission interval (number of symbols at each frequency level in a given transmission interval) based on the number of symbols allocated to an uplink common channel or a downlink common channel (the first boundary determination option , at which the frequency hops, according to the fourth aspect). The control section 210 is configured to determine a boundary at which the frequency hops without regard to a slot boundary in a given transmission interval.

The control section 210 is configured to determine a boundary at which a frequency hops in a given transmission interval based on a boundary of a slot in that specified transmission interval (the second option for determining a boundary at which a frequency hops according to the fourth aspect). The control section 210 is configured to control frequency hopping in a predetermined transmission interval between slots (eg, FIG. 12A).

The control section 210 is configured to control frequency hopping in a given transmission interval within each slot (eg, FIG. 12B). The control section 210 is configured to determine the boundary at which the frequency hops in each slot (determining the number of symbols at each frequency level per predetermined transmission interval per slot) based on the number of symbols per predetermined transmission interval per slot. .

(Hardware configuration)

In the functional diagrams used to describe the above implementations, blocks are shown in functional modules. These functional blocks (components) may be implemented by arbitrary combinations of at least one of the hardware and/or software. Here, the implementation method of each function block is not specifically limited. In other words, each functional block may be implemented by a single physically or logically connected device, or may be implemented by directly or indirectly connecting two or more physically or logically separate devices (via, for example, a wired, wireless connection, or the like) and using this set of devices. These functional blocks can be implemented by combining the above described software with one or more of the above devices.

Here, the functions include analysis, definition, decision making, calculation, calculation, processing, inference, research, search, confirmation, reception, transmission, output, access, disambiguation, selection, indication, establishment, comparison, assumption, assumption, consideration, broadcast, notification, message, forwarding, setting, reconfiguring, hosting (display), assigning, etc., but these functions are by no means limited to the above list. For example, the functional block(s) for realizing the transmission function may be called a transmission section (transmission unit), a transmitter, or the like. The implementation method of each component is not specifically limited to the above.

For example, base station, user terminal, etc. according to one implementation of the present invention may function as a computer executing the operations of the radio communication method of the present invention. Fig. 16 illustrates an example of a base station and user terminal hardware configuration according to one implementation. Physically, the base station 10 and user terminal 20 described above may be implemented 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 so on.

In this disclosure, words such as "hardware", "circuit", "device", "section", "module", etc. can be interpreted interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may contain one or more of each of the devices shown in the drawings, or may not contain a part of these devices.

For example, although only one processor 1001 is shown, multiple processors may be provided. The operations may be performed by a single processor or by two or more processors simultaneously, sequentially, or otherwise. It should be appreciated that processor 1001 may be implemented using one or more integrated circuit chips.

Each functional module of base station 10 and user terminals 20 is implemented, for example, by enabling certain software(s) to be read into hardware, for example, into processor 1001 and into memory 1002, and by enabling processor 1001 to perform calculations to control communication through the communication device 1004 and the ability to control the reading and/or writing of data to the memory 1002 and the storage device 1003.

The processor 1001 is configured to control the entire computer by, for example, executing an operating system. The processor 1001 may be configured to include a central processing unit (CPU) including interfaces with a peripheral device, a control device, a computing device, a register, and so on. The processor 1001 may implement, for example, at least a portion of the above-described control section 110 (210), transmit/receive section 120 (220), and the like.

Further, the processor 1001 reads programs (program codes), program modules, data, and so on. from the storage 1003 and/or the communication device 1004 to the memory 1002 and performs various operations in accordance therewith. With regard to these programs, programs that implement the ability of a computer to perform at least part of the operations of the above implementations can be used. For example, control section 110 (210) may be implemented by program codes stored in memory 1002 and executed by processor 1001; other functional blocks can be implemented similarly.

Memory 1002 is a machine-readable, writable storage medium and may be formed, for example, by at least one of Read Only Memory, ROM, Erasable Programmable ROM, EPROM ), electrically erasable read-only memory (English Electrically Erasable Programmable ROM, EEPROM), random access memory (English Random Access Memory, RAM) and other suitable storage media. Memory 1002 may be referred to as a register, cache, main memory (main storage), and so on. The memory 1002 is configured to store executable programs (program codes), program modules, and the like. to implement a radio communication method according to an embodiment of the present invention.

The storage 1003 is a computer-readable writable medium and can be implemented using, for example, at least one of a floppy disk, a floppy disk (a registered trademark of floppy disk), a magneto-optical disk (for example, a Compact Disc ROM , CD-ROM), etc.), Digital Versatile Disc, Blu-ray Disc (registered trademark), Removable Disk, Hard Disk, Smart Card, Flash Memory ( e.g. memory card, removable storage, removable disk, etc.), magnetic tape, database, server, and other suitable media. Storage 1003 may be referred to as an additional storage device.

Communication device 1004 is a hardware (transmitter/receiver) for computer-to-computer communication via wired and/or wireless networks, and may be referred to as a network device, network controller, network card, communication module, etc., for example. The communication device 1004 may be configured to include a high frequency switch, an antenna switch, a filter, a frequency synthesizer, and so on. in order to implement, for example, frequency division duplex (FDD) and/or time division duplex (TDD). For example, the above-described transmit/receive sections 120 (220), transmit/receive antennas 130 (230), etc., may be implemented by the communication device 1004. In the transmit/receive section 120 (220), the transmit section 120a (220a) and the receive section 120b (220b) may be implemented with physical or logical separation.

The input device 1005 is a device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) for receiving information from outside. The output device 1006 is an output device (eg, display, acoustic emitter, LED indicator, etc.) for outputting information. It should be noted that the input device 1005 and the output device 1006 may be combined into a single structure (eg, a touch panel).

Devices of these types, including processor 1001, memory 1002, etc., are connected by bus 1007 to exchange information. Bus 1007 may be formed by a single bus or buses that differ from device to device.

Base station 10 and user terminals 20 may be configured to include hardware such as a microprocessor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (ASIC), a programmable logic device (English Programmable Logic Device, PLD), programmable matrix of logical elements (English Programmable Gate Array, FPGA), etc., and all or part of the functional blocks can be implemented by the specified hardware. For example, processor 1001 may be implemented using at least one of these hardware.

(Modifications)

It should be appreciated that the terms described in the disclosure of the present invention and the terms necessary for understanding the present invention may be replaced by other terms conveying the same or similar meaning. For example, "channel", "symbol", and "signal" (or signaling) can be interpreted interchangeably. In addition, "signals" can be "messages". The reference signal can be abbreviated as RS (Reference Signal) and called pilot, pilot signal, etc. depending on the applicable standard. A Elementary Carrier (EC) may be referred to as a cell, a frequency carrier, a frequency carrier, and so on.

A radio frame may be formed from one or more periods (frames) in the time domain. Each of one or more periods (frames) constituting a radio frame may be referred to as a subframe. Further, a subframe in the time domain may be formed from one or more slots. A subframe may be a time slot of a fixed duration (eg, 1 ms) independent of numerology.

In this context, numerology may refer to a communication parameter applied to at least one of the transmission and reception of a given signal or channel. For example, numerology may indicate at least one of Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, and so on.

A slot in the time domain may be formed by one or more symbols (OFDM symbols, SC-FDMA symbols, etc.). The slot can be a temporary element depending on numerology.

A slot may contain a plurality of mini-slots. Each mini-slot in the time domain may be formed from one or more symbols. A mini-slot may be referred to as a sub-slot. A mini-slot may be formed from symbols that are less than the number of slots. PDSCH (or PUSCH) transmission in a tile larger than a mini-slot may be referred to as PDSCH Mapping Type A (PUSCH). PDSCH (or PUSCH) transmission using a mini-slot may be referred to as PDSCH Map Type B (PUSCH).

The radio frame, subframe, slot, mini-slot, and symbol are temporary elements in signaling. The radio frame, subframe, slot, mini-slot, and symbol may be referred to by other suitable names. It should be appreciated that temporal elements such as frame, subframe, slot, mini-slot, and symbol may be interpreted interchangeably in the present disclosure.

For example, one subframe, multiple consecutive subframes, one slot, or one mini-slot may be referred to as a transmission time interval (TTI). Thus, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1 to 13 symbols), or a period longer than 1 ms. Note that an element representing a TTI may not be referred to as a subframe, but as a slot, mini-slot, or the like.

In this document, TTI is understood to mean, for example, the smallest scheduling time element in a radio communication. For example, in LTE systems, a base station schedules the allocation of radio resources (eg, bandwidth and transmit power allowed for use by each user terminal) for each user terminal in units of TTI. The definition of TTI intervals is not limited to this.

The TTIs may be time units for transmitting channel-encoded data packets (transport blocks), code blocks, or codewords, or the TTI may be a processing time unit in scheduling, link adaptation, and so on. It should be appreciated that even with given TTIs, the time interval (eg, number of symbols) for which transport blocks, code blocks and/or codewords are actually mapped may be shorter than these TTIs.

Note that when a TTI is referred to as one slot or one mini-slot, the minimum time element in scheduling may be one or more such TTIs (ie, one or more slots or one or more mini-slots). Moreover, the number of slots (number of mini-slots) constituting this minimum scheduling time element can be controllable.

A TTI with a time duration of 1 ms may be called a regular TTI (TTI in 3GPP Releases 8-12), long TTI, regular subframe, long subframe, slot, and so on. A TTI that is shorter than a regular TTI may be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-slot, a subslot, a slot, and the like.

Note that a long TTI (e.g., regular TTI, subframe, etc.) may be interpreted as a TTI with a time duration greater than 1 ms, and a short TTI (e.g., shortened TTI) may be interpreted as a TTI with a duration shorter than the duration of the long TTI and not less than 1 ms.

Resource block (English Resource Block, RB), which is a resource allocation element in the time domain and in the frequency domain, may contain one subcarrier or multiple subcarriers in succession in the frequency domain. The number of subcarriers in a resource block may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers in resource blocks may be determined based on the numerology.

In the time domain, a resource block may contain one symbol or multiple symbols, and may be one slot, one mini-slot, one subframe, or one TTI in length. One TTI, one subframe, etc. may be formed by a single resource block or multiple resource blocks.

It should be noted that one or more resource blocks (RB) can be called a physical resource block (English Physical RB, PRB), sub-carrier group (English Sub-Carrier Group, SCG), group of resource elements (English Resource Element Group, REG ), a pair of PRBs, a pair of RBs, and the like.

Further, a resource block can be formed by a single resource element (English Resource Elements, RE) or multiple REs. For example, one RE may correspond to a radio resource region consisting of one subcarrier and one symbol.

The Bandwidth Part (BWP; may also be referred to as a partial band, etc.) may be a subset of consecutive uninterrupted common resource blocks (RB) for a given numerology on a given carrier. In this case, the common RB may be indicated by the RB index with respect to the common reference point on that carrier. The PRB may be defined by a given BWP and may be numbered in that BWP.

A BWP may contain an uplink BWP (uplink BWP) and a downlink BWP (downlink BWP). One or multiple BWPs may be configured for a UE on a single carrier.

At least one of the configured BWPs may be active and UΕ should not assume that a given signal/channel is being transmitted/received outside of the active BWPs. It should be noted that the terms "cell", "carrier", etc. in this disclosure may be interpreted as "BWP".

It should be appreciated that the above-described configurations of radio frames, subframes, slots, mini-slots, symbols, etc. are only examples. For example, various changes are possible with respect to the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots contained in a slot, the number of symbols and RBs contained in a slot or mini-slot, the number of subcarriers contained in a RB, number of symbols in TTI, symbol duration, cyclic prefix (CPU) length, etc.

The information and parameters described in this disclosure may be represented by absolute values or relative values with respect to setpoints, or may be represented by other relevant information. For example, the radio resources may be indicated by predetermined indexes.

Names used for parameters, etc. in the present disclosure are not limiting in any respect. Mathematical expressions that use these parameters, etc. may differ from those expressly disclosed in the present disclosure. For example, since the various channels (PUCCH, PDCCH, etc.) and information elements may be referred to by any suitable names, the various names given to these individual channels and information elements are not limiting in any respect.

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, code sequences (chips), etc. that may be encountered in this disclosure may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination of the above.

Information, signals, etc. may be transmitted from higher layers to lower layers and/or from lower layers to higher layers. Information, signals, etc. may be transmitted and/or received through a plurality of network nodes.

Received and/or transmitted information, signals, etc. may be stored in a specific location (eg, in memory), or they may be stored using a control table. Information, signals, etc. to be received and/or transmitted may be overwritten, updated or supplemented. Transmitted information, signals, etc. can be removed. Received information, signals, etc. can be transferred to another device.

The communication of information is in no way limited to the aspects/implementations described in this disclosure, and other methods may be used. For example, the communication of information in the present invention can be performed by using physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI)), upper layer signaling (e.g., radio resource control (RRC) layer signaling), broadcast information (Basic Information Block (MIB), System Information Blocks (SIB), etc.), Media Access Layer (MAC) signaling, other signals, and/or combinations thereof.

The physical layer signaling may be referred to as L1/L2 control information (L1/L2 control signals) (Layer 1/Layer 2, layer 1/layer 2), L1 control information (L1 control signal), etc. The RRC layer signaling may be referred to as an RRC message, and the signaling may be, for example, an RRC connection establishment message, an RRC connection reconfiguration message, and so on. MAC layer signaling can be transmitted using, for example, MAC control elements (MAC CE).

The message of the given information (for example, the message that X does not change) need not be communicated explicitly, but may be conveyed implicitly (by, for example, not reporting this given information or by reporting another piece of information).

Tests can be performed on values represented by a single bit (0 or 1), on boolean values representing true or false, or by comparing numeric values (for example, by comparing with a given value).

Software, whether called "program", "internal program", "middleware", "microcode", "hardware description language" or otherwise, should be understood in a broad sense, covering instructions, sets instructions, code, code segments, program codes, programs, subroutines, program modules, applications, software applications, software packages, objects, executable files, threads of execution, procedures, functions, etc.

Programs, commands, information, etc. can be transmitted and received over the communication medium. For example, if a program is transmitted from a website, server, or other remote source using at least one of the wired technologies (coaxial cables, fiber optic cables, twisted pair cables, Digital Subscriber Lines) , DSL), etc.) and wireless technology (infrared radiation, microwaves, etc.), then at least one of these wired and / or wireless technology is also included in the concept of a communication medium.

The terms "system" and "network" as used in this disclosure may be used interchangeably. "Network" may mean a device (eg, a base station) that is part of a network.

In the present disclosure, terms such as "precoding", "precoding device", "weight (weight in precoding)", "quasi-proximity" (English Quasi-Co-Location, QCL), "indicator status transmission configuration" (TCI status), "spatial relationship", "spatial domain filter", "transmit power", "phase rotation", "antenna port", "antenna port group", "level", "number of levels", " rank, resource, resource set, resource group, beam, beamwidth, beam angle, antenna, antenna element, panel, etc. can be used interchangeably.

In this disclosure, terms such as "base station)" , “access point”, “transmission point” (eng. Transmission Point, TP), “reception point” (eng. Reception Point, RP), “transmitting / receiving point” (eng. Transmission / Reception Point, TRP), “ panel", "cell", "sector", "cell group", "carrier", "unit carrier" may be used interchangeably. Base station may be referred to by terms such as "macro cell", "small cell", "femto cell" ”, “pico cell”, etc.

The base station may be configured to serve one or more (eg, three) cells. When a base station serves many cells, the entire coverage area of that base station can be divided into many smaller areas, in each of which communication services can be provided through subsystems of the base station, for example, small base stations for premises (remote radio units, English Remote Radio Head ). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or a subsystem of a base station providing communication services in that coverage area.

In the present disclosure, the terms "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" may be used interchangeably.

A mobile station may be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote unit, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, telephone handset, user agent, mobile client, client and, in some cases, some other suitable terms.

At least one of a base station and a mobile station may be referred to as a transmitter, a receiver, a radio communication device, and so on. It should be appreciated that at least one of the base station and the mobile station may be a device mounted on a mobile unit, the mobile unit itself, and so on. The specified moving object can be a vehicle (for example, a car, an airplane, etc.), a moving object, the movement of which is carried out without a pilot on board (for example, a drone, a car without a driver, etc.) or a robot (controlled by human type or unmanned type). It should be appreciated that at least one of the base station and the mobile station also includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (ΙοΤ) device, such as a sensor, or the like.

The base station in the present disclosure can be interpreted as a user terminal. For example, each aspect/implementation of the present invention, instead of a configuration in which communication is carried out between a base station and a user terminal, can be applied to a configuration in which communication is carried out between a plurality of user terminals (for example, this type of communication may be called device communication). -to-Device, D2D), communication between a vehicle and a wide range of objects (Vehicle-to-Everything, V2X), etc.). In this case, the user terminals 20 may perform the functions of the base stations 10 described above. The words "upstream" and "downstream" may be interpreted as corresponding to terminal-to-terminal communications (eg, as "referring to direct communications"). For example, uplink, downlink, etc. can be interpreted as a direct channel.

Similarly, in the present disclosure, a user terminal can be interpreted as a base station. In this case, the base station 10 may perform the functions of the user terminal 20 described above.

The actions described herein as being performed by a base station may, in some cases, be performed by older nodes. Obviously, in a network containing one or more network nodes with base stations, various operations performed to communicate with terminals can be performed by base stations, one or more network nodes other than base stations (for example, mobility management nodes (eng. Mobility Management Entity, MME), serving gateways (English Serving-Gateway, S-GW), etc., but this list is not limiting) or combinations of the listed nodes.

The aspects/implementations illustrated in this disclosure may be used singly or in combination, which may vary depending on the preferred implementation. The order of operations, sequences, block diagrams, etc. used in this disclosure to describe aspects/implementations may be changed if this does not lead to inconsistencies. For example, while the various methods are illustrated in the present disclosure with various components of the steps in the order given by way of example, the specific order presented here is in no way limiting.

Aspects/implementations illustrated in this disclosure may apply to LTE, LTE-A, LTE-B, SUPER 3G, IMT-Advanced, fourth generation (4G) mobile communication system, fifth generation (5G) mobile communication system, future Radio Access (FRA), New Radio Access Technology (RAT), New Radio System (New Radio, NR), New Radio Access (NX), Future Generation Radio Access, FX ), to the Global System for Mobile communications (GSM (registered trademark)), to the CDMA2000 system, to the Ultra Mobile Broadband (UMB) system, to the IEEE 802.11 (Wi- Fi (registered trademark)), IEEE 802.16 (Wi-MAX (registered trademark)), IEEE 802.20, to a short range communication system using ultra-low spectral density wideband signals (Ultra-Wide Ba nd, UWB), to the Bluetooth system (registered trademark), to systems using other suitable radio communication methods, and to next-generation systems improved on these systems. Multiple systems can be combined and used (eg combination of LTE or LTE-A and 5G, etc.).

In this disclosure, the phrase "based on" (or "based on") does not mean "only based on" (or "only based on"), unless otherwise indicated. In other words, the phrase "on the basis of" (or "on the basis of") means both "on the basis of" and "on the basis of at least" ("only on the basis of" and "at least on the basis of").

Referencing elements using designations such as "first", "second", etc. the present disclosure does not generally limit the number or order of these elements. These designations may be used in the present disclosure for convenience only, as a way to distinguish between two or more elements. Thus, the mention of the first and second elements does not imply that only two elements can be used, or that the first element must in any way precede the second element.

The term "decision" ("determination") in the present disclosure can cover a wide variety of actions. For example, “decision” (“determining”) can be interpreted as making decisions (carrying out checks) related to judgment, calculation, calculation, processing, inference, research, search, search and query (for example, search in a table, database or some other data structure), establishing a fact, etc.

Further, the term “decision” (“determining”) can be interpreted as meaning making decisions (carrying out checks) related to receiving (for example, receiving information), transmitting (for example, transmitting information), input, output, access (for example, access to data in memory), etc.

In addition, the term "decision" ("determining") in this document can be interpreted as meaning making decisions (carrying out checks) related to disambiguation, selection, selection, establishment, comparison, etc. In other words, "decision" ("determination") can be interpreted as making decisions (carrying out checks) about the performance of some action.

In addition, “decision” (“determination”) can be interpreted as “guess”, “expectation”, “consideration”, etc.

"Highest transmit power" according to the present disclosure may mean the highest transmit power value, may mean the nominal highest transmit power (nominal highest transmit power of the UE), or may mean the normative highest transmit power (the normative highest transmit power of the UE).

In this disclosure, the terms "connected", "connected" and any of their options means all direct or indirect connections or connections between two or more elements, and may allow the presence of one or more intermediate elements between two elements that are "connected" or "connected" between themselves. The relationship or connection between these elements may be physical, logical, or a combination of both. For example, "connection" can be interpreted as "access".

When the present disclosure indicates that two elements are connected, the two elements may be considered to be connected or interconnected using one or more electrical conductors, cables, and printed electrical connections, and, as a few non-limiting and non-exclusive examples, using electromagnetic energy, having wavelengths in radio frequency bands, microwave bands and optical (both visible and invisible) bands, or the like.

In the present disclosure, the expression "A and B are different" may mean "A and B are different from each other." It should be noted that this expression can mean "both A and B are different from C". The terms "separate", "be connected", etc. can be interpreted similarly to the term "various".

When used in the present disclosure, for example, terms such as "include", "comprising" and variations thereof, these terms should be understood in a content sense similar to that in which the term "comprising" is used. The conjunction "or" in this disclosure is not to be understood as meaning an exclusive disjunction.

In the present disclosure, when an article such as "a", "an" and "the" is added in English translation, the noun after the said article can be interpreted as containing the plural value as well.

Now, while the present invention has been described in detail above, it should be apparent to those skilled in the art that the invention according to the present disclosure is in no way limited to the implementations described in this disclosure. The invention in accordance with the present disclosure can be implemented with various changes and in various modifications without deviating from the essence. Accordingly, the description of the present disclosure is given only within the scope of the present invention, defined by the claims, to explain examples and should in no way be taken as limiting the present invention.

Claims (15)

1. Terminal containing: a receiving section, configured to receive information related to the number of repetitions of the physical uplink common channel (PUSCH); a transmission section configured to transmit the PUSCH in the same number of transmission intervals as the number of repetitions indicated by the specified information; and a control section configured to apply frequency hopping for the PUSCH in transmission spans based on a slot boundary within transmission spans. 2. The terminal of claim 1, wherein the frequency hopping scheme differs in at least a portion of said transmission intervals by the same number as the number of repetitions. 3. A radio communication method for a terminal, including: receiving information related to the number of repetitions of the physical uplink common channel (PUSCH); transmitting the PUSCH in the same number of transmission intervals as the number of repetitions indicated by the specified information; and applying frequency hopping for PUSCH in transmission spans based on slot boundary within transmission spans. 4. A radio communication system comprising a terminal and a base station, wherein the terminal contains: a receiving section, configured to receive information related to the number of repetitions of the physical uplink common channel (PUSCH); a transmission section configured to transmit the PUSCH in the same number of transmission intervals as the number of repetitions indicated by the specified information; and a control section configured to apply frequency hopping for PUSCH in transmission intervals based on a slot boundary within transmission intervals, and the base station comprises: a transmission section configured to transmit said information; and a receiving section configured to receive the PUSCH.

Images