WO2020153210A1 - User terminal and wireless communication method - Google Patents

Abstract

The present invention appropriately controls at least one of the reception of a downlink shared channel and the transmission of an uplink shared channel in a time unit shorter than a slot. A user terminal according to one aspect of the present disclosure is provided with: a reception unit that receives downlink control information; and a control unit that determines, on the basis of the value of a prescribed field in the downlink control information, a time domain resource to be assigned to a downlink shared channel or an uplink shared channel in a time unit shorter than a slot.

Description

User terminal and wireless communication method

The present disclosure relates to a user terminal and a wireless communication method in a next-generation mobile communication system.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of further high data rate, low delay, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

A successor system to LTE (for example, 5th generation mobile communication system (5G), 5G+(plus), New Radio (NR), 3GPP Rel.15 or later) is also under consideration.

In the existing LTE system (for example, 3GPP Rel. 8-14), the user terminal (User Equipment (UE)) uses an uplink shared channel (for example, Physical Uplink) based on downlink control information (Downlink Control Information (DCI)). Controls transmission of Shared Channel (PUSCH) and reception of downlink shared channel (for example, Physical Downlink Control Channel (PDSCH)).

3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA)” and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8), April 2010

In a future wireless communication system (hereinafter referred to as NR), a downlink shared channel (for example, Physical Downlink Control Channel (PDSCH)) within a slot based on the value of a predetermined field in downlink control information (Downlink Control Information (DCI)). ) Or determining a time domain resource (eg, symbol) allocated to an uplink shared channel (eg, Physical Uplink Shared Channel (PUSCH)).

Also, in NR, since it satisfies the requirements of ultra-high reliability and low-delay service (for example, Ultra Reliable and Low Latency Communications (URLLC) related service (URLLC service)), it is shorter than the slot (finer) Supporting (introduce) a time unit is also being considered.

However, when a time unit shorter than the slot is introduced, there is a risk that at least one of reception of the downlink shared channel and transmission of the uplink shared channel within the time unit cannot be controlled appropriately.

Therefore, it is an object of the present disclosure to provide a user terminal and a wireless communication method capable of appropriately controlling at least one of reception of a downlink shared channel and transmission of an uplink shared channel within a time unit shorter than a slot. ..

A user terminal according to an aspect of the present disclosure includes a receiving unit that receives downlink control information, and a downlink shared channel or an uplink shared channel within a time unit shorter than a slot based on a value of a predetermined field in the downlink control information. And a control unit that determines a time domain resource allocated to the.

According to an aspect of the present disclosure, it is possible to appropriately control at least one of reception of a downlink shared channel and transmission of an uplink shared channel within a time unit shorter than a slot.

1A and 1B are diagrams illustrating an example of a PDSCH time domain allocation list and a PUSCH time domain allocation list. FIG. 2 is a diagram showing an example of the sub-slot pattern according to the first aspect. 3A and 3B are diagrams showing an example of the offsets K0 and K2 according to the second mode. 4A and 4B are diagrams illustrating an example of a PDSCH time domain allocation list and a PUSCH time domain allocation list according to the second aspect. 5A and 5B are diagrams illustrating an example of determination of a PDSCH time domain allocation list and a PUSCH time domain allocation list according to the third aspect. FIG. 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 7 is a diagram illustrating an example of the configuration of the base station according to the embodiment. FIG. 8 is a diagram showing an example of the configuration of the user terminal according to the embodiment. FIG. 9 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment.

In NR, the value of a predetermined field (for example, Time Domain Resource Assignment or allocation (TDRA) field) in the downlink control information (Downlink Control Information (DCI)) of the user terminal (UE: User Equipment) Time domain resources (for example, one or more symbols) allocated to a downlink shared channel (also called Physical Downlink Shared Channel (PDSCH)) or an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on The decision is being considered.

<PDSCH time domain resource allocation>
The size (the number of bits) of the TDRA field in the DCI (DL assignment, for example, DCI format 1_0 or 1_1) used for PDSCH scheduling may be fixed or variable.

For example, the size of the TDRA field in the DCI format 1_0 may be fixed to a predetermined number of bits (for example, 4 bits). On the other hand, the size of the TDRA field in the DCI format 1_1 may be the number of bits (for example, 0 to 4 bits) that changes according to a predetermined parameter.

The predetermined parameter used to determine the size of the TDRA field may be, for example, the number of entries in the time domain allocation list (PDSCH time domain allocation list) for PDSCH (or downlink data).

For example, the PDSCH time domain allocation list may be, for example, the RRC control element “pdsch-TimeDomainAllocationList” or “PDSCH-TimeDomainResourceAllocationList”. Also, the PDSCH time domain allocation list may be used to set the time domain relationship between the PDCCH and PDSCH. Further, each entry in the PDSCH time domain allocation list may be referred to as time domain resource allocation information for PDSCH (PDSCH time domain allocation information) or the like, and is, for example, “PDSCH-TimeDomainResourceAllocation” of the RRC control element. Good.

Further, the PDSCH time domain allocation list may be included in the cell-specific PDSCH parameter (for example, RRC control element “pdsch-ConfigCommon”), or UE-specific (UE-specific UE-specific applied to a specific BWP). ) It may be included in the parameter (for example, the RRC control element “pdsch-Config”). As such, the PDSCH time domain allocation list may be cell-specific or UE-specific.

FIG. 1A is a diagram showing an example of a PDSCH time domain allocation list. As shown in Figure 1A, each PDSCH time region allocation information of the PDSCH time domain allocation in the list, information indicating a DCI, offset K0 between the PDSCH scheduled by the DCI and (k0, also referred to as _{K 0,} etc.) At least one of (an offset information, K0 information, etc.), information indicating a mapping type of PDSCH (mapping type information), and an index (Start and Length Indicator (SLIV)) that gives a combination of the PDSCH start symbol S and the time length L. May be included.

Alternatively, the predetermined parameter used to determine the size of the TDRA field may be the number of entries in the default table for time domain allocation for upstream data (for example, default PDSCH time domain allocation A). The default table may be determined in advance by specifications. In each row of the default table, a row index, information indicating the position of DMRS, the above mapping type information, the above K0 information, information indicating the start symbol S of PDSCH, and information indicating the number L of symbols allocated to PDSCH At least one may be associated.

The UE may determine the row index (entry number or entry index) of a given table based on the value of the TDRA field in DCI (eg DCI format 1_0 or 1_1). The predetermined table may be a table based on the PDSCH time domain allocation list or the default table.

The UE is in a predetermined slot (one or a plurality of slots) based on at least one of K0 information, SLIV, start symbol S, and time length L defined in the row (or entry) corresponding to the row index. May determine time domain resources (eg, a predetermined number of symbols) assigned to the PDSCH.

The K0 information may indicate the offset K0 between the DCI and the PDSCH scheduled by the DCI by the number of slots. The UE may determine the slot for receiving the PDSCH by the offset K0. For example, when the UE receives DCI for scheduling PDSCH in slot #n, the slot number n, PDSCH subcarrier interval μ _PDSCH , PDCCH subcarrier interval μ _PDCCH , and at least one of the offsets K0 are set. Based on the above, the slot for receiving the PDSCH (assigned to the PDSCH) may be determined.

<PUSCH time domain resource allocation>
The size (bit number) of the TDRA field in the DCI (UL grant, for example, DCI format 0_0 or 0_1) used for PUSCH scheduling may be fixed or variable.

For example, the size of the TDRA field in the DCI format 0_0 may be fixed to a predetermined number of bits (for example, 4 bits). On the other hand, the size of the TDRA field in the DCI format 0_1 may be the number of bits (for example, 0 to 4 bits) that changes according to a predetermined parameter.

The predetermined parameter used to determine the size of the TDRA field may be, for example, the number of entries in the time domain allocation list (PUSCH time domain allocation list) for PUSCH (or uplink data).

For example, the PUSCH time domain allocation list may be, for example, an RRC control element “pusch-TimeDomainAllocationList” or “PUSCH-TimeDomainResourceAllocationList”. Each entry in the PUSCH time domain allocation list may also be called time domain resource allocation information for PUSCH (PUSCH time domain allocation information), and is, for example, “PUSCH-TimeDomainResourceAllocation” of the RRC control element. Good.

In addition, the PUSCH time domain allocation list may be included in the cell-specific PUSCH parameter (for example, the RRC control element “pusch-ConfigCommon”), or may be specified for each UE (specific bandwidth part (Bandwidth Part (BWP UE)-specific parameters applied to )) (for example, RRC control element “pusch-Config”). As such, the PUSCH time domain allocation list may be cell-specific or UE-specific.

FIG. 1B is a diagram showing an example of a PUSCH time domain allocation list. As shown in FIG. 1B, the PUSCH time region allocation information of the PUSCH time domain allocation in the list, DCI offset K2 (k2, also referred to as _{K 2,} etc.) information (offset indicating a between the PUSCH to be scheduled by the DCI Information, K2 information), information indicating a mapping type of PUSCH (mapping type information), and an index (Start and Length Indicator (SLIV)) that gives a combination of a start symbol of PUSCH and a time length may be included.

Alternatively, the above-mentioned predetermined parameter used for determining the size of the TDRA field may be the number of entries in the default table (eg, default PUSCH time domain allocation A) for time domain allocation for upstream data. The default table may be determined in advance by specifications. Each row of the default table is associated with at least one of a row index, the mapping type information, the K2 information, information indicating the start symbol S of PUSCH, and information indicating the number L of symbols allocated to PUSCH. Good.

The UE may determine the row index (entry number or entry index) of a given table based on the value of the TDRA field in the DCI (eg DCI format 0_0 or 0_1). The predetermined table may be a table based on the PUSCH time domain allocation list or the default table.

The UE is in a predetermined slot (one or more slots) based on at least one of K2 information, SLIV, start symbol S, and time length L defined in the row (or entry) corresponding to the row index. May determine the time domain resources (eg, a predetermined number of symbols) assigned to the PUSCH.

The K2 information may indicate the offset K2 between the DCI and the PUSCH scheduled by the DCI by the number of slots. The UE may determine the slot for transmitting the PUSCH according to the offset K2. For example, when the UE receives the DCI for scheduling the PUSCH in the slot #n, the slot number n, the PUSCH subcarrier interval μ _PUSCH , the PDCCH subcarrier interval μ _PDCCH , and at least one of the offsets K2. The slot for transmitting the PUSCH (assigned to the PUSCH) may be determined based on the above.

As shown in FIGS. 1A and 1B, the Start and Length Indicator (SLIV) in the PUSCH time range allocation list and the PDSCH time domain allocation list may be indicated by a predetermined number of bits (for example, 7 bits). The number of bits of SLIV may be derived based on the number of symbols in a slot (slot length). For example, a 7-bit SLIV may be derived using Equation 1 below based on 14 symbols in a slot.
(Equation 1)
Log2{14*(14+1)/2}=6.71

In this way, in NR, controlling the PDSCH reception and PUSCH transmission on a slot basis is being considered. On the other hand, NR is shorter than a slot (finer) because it satisfies the requirements of ultra-reliable and low-delay services (for example, Ultra Reliable and Low Latency Communications (URLLC) related services (URLLC services)). Supporting (introduce) a time unit is also being considered.

However, if a time unit shorter than the slot is introduced, at least one of PDSCH reception and PUSCH transmission within the time unit may not be controlled appropriately. Therefore, the present inventors have studied a method for appropriately controlling PDSCH reception and PUSCH transmission in a time unit shorter than a slot, and arrived at the present invention.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. In the present embodiment, the time unit shorter than the slot is composed of a smaller number of symbols (eg, 2, 3, 4 or 7 symbols) than the number of symbols (eg, 14 symbols) forming the slot. Further, the time unit may be called, for example, a sub slot, a half slot, a mini slot, or the like. In the following, the time unit is referred to as a subslot, but it goes without saying that it is not limited to this.

Further, in the present embodiment, the PDSCH time domain allocation list may be rephrased as a table in which the PDSCH time domain allocation information in the PDSCH time domain allocation list is an entry (row). Further, the PUSCH time domain allocation list may be rephrased as a table in which the PUSCH time domain allocation information in the PUSCH time domain allocation list is an entry (row).

(First mode)
In the first aspect, the configuration of the sub-slot pattern (sub-slot pattern) in the slot in the UE will be described. The subslot pattern may be paraphrased as a configuration of subslots in a slot.

Specifically, the UE may be configured with a subslot pattern in at least one of downlink (Downlink (DL)) and uplink (Uplink (UL)). The sub-slot pattern may be set in DL and UL respectively, or may be set commonly in DL and UL.

FIG. 2 is a diagram showing an example of a subslot pattern according to the first aspect. Multiple sub-slot patterns may be supported, as shown in FIG. The number of subslots in a slot and the number of symbols in each subslot may be different between the plurality of subslot patterns.

For example, in FIG. 2, three subslot patterns are shown. In the first sub-slot pattern (sub-slot pattern #1), 2 sub-slots are included in each slot, and each sub-slot may include 7 symbols. It should be noted that the sub-slot composed of 7 symbols may be called a half slot or the like.

In the second sub-slot pattern (sub-slot pattern #2), 4 sub-slots are included in each slot, and each sub-slot may include 4 or 3 symbols. For example, in subslot pattern #2 of FIG. 2, the number of symbols in each of the four subslots in the time direction is defined as {4, 3, 3, 4}, but the number is not limited to this. For example, in subslot pattern #2, the number of symbols in each of the 4 subslots is specified by {4, 3, 4, 3}, {3, 4, 3, 4} or {3, 4, 4, 3}. May be. Also, a plurality of sub-slot patterns having different configurations of the 4-symbol sub-slot and the 3-symbol sub-slot in the slot may be supported.

In the third sub-slot pattern (sub-slot pattern #3), 7 sub-slots are included in each slot, and each sub-slot may include 2 symbols.

As described above, when one or more sub-slot patterns are supported, the UE receives information indicating the sub-slot pattern (or used for derivation (determination) of the sub-slot pattern) and based on the information, the sub A slot pattern (or subslot) may be set. The information may be called, for example, subslot pattern information, subslot configuration information, or the like.

UE may receive sub-slot pattern information in each of DL and UL (separately or independently). In this case, the UE may set a subslot pattern (or subslot) used for DL communication (for example, PDSCH reception) based on the DL subslot pattern information. Further, the subslot pattern used for UL communication (for example, PUSCH transmission) may be set based on the subslot pattern information for UL.

Alternatively, the UE may receive sub-slot pattern information common to DL and UL. In this case, the UE sets the subslot pattern (or subslot) used for at least one of DL communication (for example, PDSCH reception) and UL communication (for example, PUSCH transmission) based on the subslot pattern information. Good.

The above sub-slot pattern information may be set in the UE by upper layer parameters.

In the first aspect, since the UE receives the subslot pattern information, the subslot used for PDSCH reception or PUSCH transmission can be appropriately configured (configured) in the UE based on the subslot pattern information.

(Second mode)
In the second mode, allocation of time domain resources to at least one of PDSCH and PUSCH in a set subslot will be described.

<Offset K0/K2>
In the second aspect, the K0 information may indicate the offset K0 between the DCI and the PDSCH scheduled by the DCI in the number of sub-slots instead of the number of slots. The UE may determine a subslot for receiving the PDSCH based on the offset K0. The K0 information may be included in each PDSCH time domain allocation information in the PDSCH time domain allocation list.

For example, when the UE receives DCI (for example, DCI format 1_0 or 1_1) for scheduling PDSCH in subslot #n, the number n of the subslot and the subcarrier interval for _PDSCH μ _PDSCH , sub for PDCCH The subslot for transmitting PDSCH may be determined based on at least one of the carrier interval μ _PDCCH and the offset K0.

The UE may also determine the offset K0 based on the value of a predetermined field (for example, the TDRA field) in the DCI. For example, the UE may determine the offset K0 indicated by the K0 information corresponding to the TDRA field value in the PDSCH time domain allocation list. Alternatively, the UE may determine the offset K0 indicated by the K0 information corresponding to the TDRA field value in the default table.

Also, the K2 information may indicate the offset K2 between DCI and PUSCH scheduled by DCI by the number of sub-slots instead of the number of slots. The UE may determine the subslot for transmitting the PUSCH based on the offset K2. The K2 information may be included in each PUSCH time domain allocation information in the PUSCH time domain allocation list.

For example, when the UE receives DCI (for example, DCI format 0_0 or 0_1) that schedules PUSCH in subslot #n, the number n of the subslot and the subcarrier interval μ _PUSCH for _PUSCH , the sub for PDCCH The sub-slot for transmitting the PUSCH may be determined based on at least one of the carrier interval μ _PDCCH and the offset K2.

Also, the UE may determine the offset K2 based on the value of a predetermined field (for example, the TDRA field) in the DCI. For example, the UE may determine the offset K2 indicated by the K2 information corresponding to the TDRA field value in the PUSCH time domain allocation list. Alternatively, the UE may determine the offset K2 indicated by the K2 information corresponding to the TDRA field value in the default table.

3A and 3B are diagrams showing an example of the offsets K0 and K2 according to the second mode. In FIGS. 3A and 3B, the subcarrier interval μ _PDSCH for _PDSCH or the subcarrier interval μ _PUSCH for _PUSCH and the subcarrier interval μ _PDCCH for _PDCCH are the same, but the present invention is not limited to this. ..

Also, in FIGS. 3A and 3B, the case where the subslot pattern #1 of FIG. 2 is set in the UE is shown as an example, but it goes without saying that other subslot patterns may be set. Further, the DL and UL configurations shown in FIGS. 3A and 3B are merely examples, and the configurations are not limited thereto.

As shown in FIG. 3A, when receiving DCI in subslot #n, the UE may receive PDSCH scheduled by the DCI in subslot #n+K0 (PDSCH is allocated in subslot #n+K0). May be). As described above, the UE may determine the offset K0 (eg, K0=3 in FIG. 3A) based on the TDRA field value in the DCI received in subslot #n.

As shown in FIG. 3B, when receiving DCI in subslot #n, the UE may transmit PUSCH scheduled by the DCI in subslot #n+K2 (PUSCH is allocated in subslot #n+K2). May be). As described above, the UE may determine the offset K2 (eg, K2=3 in FIG. 3B) based on the TDRA field value in the DCI received in subslot #n.

<PDSCH/PUSCH time domain allocation list>
In the second aspect, the predetermined parameter in each PDSCH time domain allocation information of the PDSCH time domain allocation list or the predetermined parameter in each PUSCH time domain allocation information of the PUSCH time domain allocation list is on a subslot basis. It may be set. The predetermined parameter may be at least one of SLIV, start symbol S, and time length L, for example.

For example, the size (bit number) of SLIV in each PDSCH time domain allocation information or each PUSCH time domain allocation information may be derived based on the number of symbols of subslots (subslot length). For example, when the sub-slot length is 7 symbols (sub-slot pattern #1 in FIG. 2), the number of bits of SLIV may be derived based on sub-slot length 7 using the following equation 2.
(Formula 2)
Log2{7*(7+1)/2}=4.8

The start symbol (index or number) S of the PDSCH or PUSCH may be the start symbol in the subslot instead of in the slot. That is, the maximum value of the start symbol S of PDSCH or PUSCH may be (the index or number of) the last symbol of the subslot.

Also, the PDSCH or PUSCH time length (or the number of consecutive symbols) L may be the time length in a subslot instead of in the slot. That is, the maximum value of the time length L of PDSCH or PUSCH may be the time length of the subslot (the number of symbols).

If the sub-slot time lengths are not uniform (eg, sub-slot pattern #2 in FIG. 2), the maximum sub-slot time length (eg, 4 symbols in sub-slot pattern #2 in FIG. 2) is used. Based on the above, the start symbol S and the time length L may be determined.

4A and 4B are diagrams showing an example of a PDSCH time domain allocation list and a PUSCH time domain allocation list according to the second mode. Predetermined in the PDSCH time domain allocation information (eg, “PDSCH-TimeDomainResourceAllocation” of the RRC control element) shown in FIG. 4A and the PUSCH time domain allocation information (eg, “PUSCH-TimeDomainResourceAllocation” of the RRC control element) shown in FIG. 4B. The parameters differ from those of FIGS. 1A and 1B in that they are defined on a sub-slot basis.

Note that the sub-slot-based PDSCH time domain allocation information may be selectively (choice) defined using the RRC control element having the same name as the slot-based PDSCH time domain allocation information. It may be defined using an RRC control element different from (independent of) the PDSCH time domain allocation information. The same applies to a list including PDSCH time domain allocation information on a subslot basis (PDSCH time domain allocation list).

The sub-slot-based PUSCH time domain allocation information may be selectively (choice) defined using the RRC control element having the same name as the slot-based PUSCH time domain allocation information. It may be defined using an RRC control element different from (independent of) the PUSCH time domain allocation information. The same applies to a list (PUSCH time domain allocation list) including sub-slot-based PUSCH time domain allocation information.

The UE may determine at least one of the SLIV for PDSCH, the start symbol S, or the time length L, which is allocated in the sub-slot, based on the value of a predetermined field (for example, the TDRA field) in the DCI. .. For example, the UE may determine the start symbol S and the time length L of the PDSCH to be assigned in the sub-slot based on the SLIV corresponding to the TDRA field value in the PDSCH time domain assignment list.

The UE may determine at least one of the SLIV for PUSCH, the start symbol S, or the time length L, which is allocated in the sub-slot, based on the value of a predetermined field (for example, the TDRA field) in the DCI. .. For example, the UE may determine the start symbol S and the time length L of the PUSCH assigned in the subslot, based on the SLIV corresponding to the TDRA field value in the PUSCH time domain assignment list.

Also, the TDRA field value in the DCI that schedules the PDSCH or PUSCH in the sub-slot is the entry (index of the PDSCH time domain allocation information in the PDSCH time domain allocation list (eg, FIG. 4A) set on a sub-slot basis. , Number) or an entry (index, number) of PUSCH time domain allocation information in the PUSCH time domain allocation list (eg, FIG. 4B).

Note that the predetermined parameter in the default table used when the PDSCH time domain allocation list or the PUSCH time domain allocation list is not set may be set on a subslot basis. For example, in the PDSCH default table, at least one of the information indicating the DMRS position, the K0 information, the start symbol S, and the time length L may be defined on a sub-slot basis. Further, in the PUSCH default table, at least one of the K2 information, the start symbol S, and the time length L may be determined on a subslot basis.

The UE may determine the time domain resource allocated to the PUSCH or PDSCH in the default table based on the row corresponding to the TDRA field value.

In the second aspect, at least one of the K2 information, the K0 information, the predetermined parameter in the PDSCH time domain allocation information, and the predetermined parameter in the PUSCH time domain allocation information is set on a sub-slot basis. A time domain resource assigned to at least one of PDSCH and PUSCH in a slot can be appropriately determined.

(Third aspect)
In the third aspect, capability information regarding whether or not at least one of a plurality of PDSCH time domain allocation lists and a plurality of PUSCH time domain allocation lists can be set will be described.

The plurality of PDSCH time domain allocation lists may include, for example, a slot-based (for example, 14 symbol slots) PDSCH time domain allocation list and a sub-slot-based PDSCH time domain allocation list. The subslot-based PDSCH time domain allocation list may be for subslots configured in the UE (see, eg, FIG. 2).

The plurality of PUSCH time domain allocation lists may include, for example, a slot-based (for example, 14 symbol slots) PUSCH time domain allocation list and a sub-slot-based PUSCH time domain allocation list. The subslot-based PDSCH time domain allocation list may be for subslots configured in the UE (see, eg, FIG. 2).

The UE may send (report) capability information indicating whether or not it is possible to set the plurality of PDSCH time domain allocation lists to a network (for example, a base station). Alternatively, the UE may transmit (report) capability information indicating that the plurality of PDSCH time domain allocation lists can be set.

Also, the UE may send (report) capability information indicating whether or not the plurality of PUSCH time domain allocation lists can be set to a network (for example, a base station). Alternatively, the UE may transmit (report) capability information indicating that the plurality of PUSCH time domain allocation lists can be set.

When a plurality of PDSCH time domain allocation lists are set, the UE uses the radio network temporary identifier (Radio Network Temporary Identifier (RNTI)) used for CRC scrambling of DCI, DCI format, predetermined field value in DCI and transmission ( The PDSCH time domain allocation list used to determine the time domain resources allocated to the PDSCH may be determined based on at least one of the carried data.

In addition, when the plurality of PUSCH time domain allocation lists are set, the UE uses at least one of RNTI used for CRC scrambling of DCI, DCI format, predetermined field value in DCI, and data to be carried. Based on this, the PUSCH time domain allocation list used to determine the time domain resources allocated to the PUSCH may be determined.

Note that the type of data to be transmitted (for example, whether it is URLLC data or not) may be recognized in the physical layer by at least one of RNTI, DCI format and the like.

5A and 5B are diagrams showing an example of determination of the PDSCH time domain allocation list and the PUSCH time domain allocation list according to the third aspect. 5A and 5B show an example of determining the PDSCH time domain allocation list and the PUSCH time domain allocation list based on the RNTI used for the DCI CRC scrambling, but the present invention is not limited to this as described above.

As shown in FIG. 5A, when the slot-based PDSCH time domain allocation list and the sub-slot-based PDSCH time domain allocation list are set in the UE, the UE may use the first RNTI (eg, System Information (SI)-RNTI). Table based on slot-based PDSCH time domain allocation list when PDSCH is scheduled by DCI (for example, DCI format 1_0 or 1_1) that is CRC scrambled by Paging (P)-RNTI or Random Access (RA)-RNTI The time domain resource assigned to the PDSCH may be determined based on (also referred to as the first PDSCH-TDRA list table).

On the other hand, the UE uses the PDSCH with the DCI (eg, DCI format 1_0 or 1_1) CRC-scrambled by the second RNTI (eg, Cell(C)-RNTI, MCS-C-RNTI or Configured Scheduling (CS)-RNTI). When the PDSCH is scheduled, the time domain resource allocated to the PDSCH may be determined based on a table (also referred to as a second PDSCH-TDRA list table or the like) based on the subslot-based PDSCH time domain allocation list. The UE may use the table when the URLLC data is transmitted.

As shown in FIG. 5B, when the slot-based PUSCH time domain allocation list and the sub-slot-based PUSCH time domain allocation list are set in the UE, the UE may perform the first RNTI (eg, Temporary Cell (TC)-RNTI). When a PUSCH is scheduled by DCI (for example, DCI format 1_0 or 1_1) that is CRC scrambled by )), based on a table based on a slot-based PUSCH time domain allocation list (also referred to as a first PUSCH-TDRA list table or the like). Then, the time domain resource assigned to the PDSCH may be determined.

On the other hand, if the UE is PUSCH scheduled by a DCI (eg DCI format 1_0 or 1_1) that is CRC scrambled by a second RNTI (eg C-RNTI, MCS-C-RNTI or CS-RNTI), The time domain resource allocated to the PUSCH may be determined based on a table based on the slot-based PDSCH time domain allocation list (also referred to as a second PUSCH-TDRA list table or the like). The UE may use the table when the URLLC data is transmitted.

Note that, in FIGS. 5A and 5B, the determination of the slot-based and sub-slot-based PDSCH time domain allocation list and the PUSCH time domain allocation list may be performed in reverse to the illustrated one.

(Fourth aspect)
In the fourth mode, at least one applicable range of the first to third modes will be described.

At least one of the first to third aspects, in the case of carrier aggregation (CA) or dual connectivity (DC), a specific serving cell (for example, a primary cell (PCell), a primary secondary cell (PSCell) or a PUCCH secondary cell ( PUCCH-SCell)). The serving cell may be called a cell, a carrier, a component carrier, or the like.

Also, at least one of the first to third aspects may be applied to each serving cell in the case of CA or DC.

Also, at least one of the first to third aspects may be applied to each group (eg, cell group or PUCCH group) in the case of CA or DC. Alternatively, at least one of the first to third aspects may be applied to a specific group (eg, master cell group or secondary cell group) in the case of CA or DC.

Also, at least one of the first to third aspects may be applied to each BWP in the serving cell in the case of CA or DC. Further, at least one of the first to third aspects may be applied to a specific BWP in the case of CA or DC.

(Wireless communication system)
Hereinafter, the configuration of the wireless communication system according to an embodiment of the present disclosure will be described. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.

FIG. 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication by using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by Third Generation Partnership Project (3GPP). ..

Also, the wireless communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple Radio Access Technologies (RATs). MR-DC has dual connectivity (E-UTRA-NR Dual Connectivity (EN-DC)) with LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, and dual connectivity (NR-E) with NR and LTE. -UTRA Dual Connectivity (NE-DC)) etc. may be included.

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

The wireless communication system 1 has dual connectivity between a plurality of base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both MN and SN are NR base stations (gNB). )) may be supported.

The wireless communication system 1 includes a base station 11 forming a macro cell C1 having a relatively wide coverage and a base station 12 (12a-12c) arranged in the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. You may prepare. The user terminal 20 may be located in at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to those shown in the figure. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.

The user terminal 20 may be connected to at least one of the plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (Carrier Aggregation (CA)) using multiple component carriers (Component Carrier (CC)) and dual connectivity (DC).

Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1 and the small cell C2 may be included in FR2. For example, FR1 may be in a frequency band of 6 GHz or less (sub-6 GHz (sub-6 GHz)), and FR2 may be in a frequency band higher than 24 GHz (above-24 GHz). The frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

Also, the user terminal 20 may perform communication in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

The plurality of base stations 10 may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station is the Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) is the IAB. It may be called a node.

The base station 10 may be connected to the core network 30 via another base station 10 or directly. The core network 30 may include at least one of, for example, Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

In the wireless communication system 1, an orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing (OFDM)) based wireless access method may be used. For example, in at least one of the downlink (Downlink (DL)) and the uplink (Uplink (UL)), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

-The wireless access method may be called a waveform. In the wireless communication system 1, other wireless access methods such as another single carrier transmission method and another multicarrier transmission method may be used as the UL and DL wireless access methods.

In the wireless communication system 1, as downlink channels, downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), and downlink control channels (Physical Downlink Control) shared by each user terminal 20 are used. Channel (PDCCH) etc. may be used.

Further, in the wireless communication system 1, as uplink channels, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), an uplink control channel (Physical Uplink Control Channel (PUCCH)), and a random access channel that are shared by each user terminal 20. (Physical Random Access Channel (PRACH)) or the like may be used.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted by PDSCH. User data, upper layer control information, and the like may be transmitted by the PUSCH. Also, the Master Information Block (MIB) may be transmitted by the PBCH.

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

DCI for scheduling PDSCH may be referred to as DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be referred to as UL grant, UL DCI, etc. Note that PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may be used to detect the PDCCH. CORESET corresponds to a resource for searching DCI. The search space corresponds to the search area and the search method of the PDCCH candidates. A CORESET may be associated with one or more search spaces. The UE may monitor CORESET associated with a search space based on the search space settings.

One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. The “search space”, “search space set”, “search space setting”, “search space set setting”, “CORESET”, “CORESET setting” and the like of the present disclosure may be read as each other.

Depending on the PUCCH, channel state information (Channel State Information (CSI)), delivery confirmation information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.) and scheduling request (Scheduling Request (Scheduling Request ( Uplink Control Information (UCI) including at least one of (SR)) may be transmitted. A random access preamble for establishing a connection with a cell may be transmitted by the PRACH.

Note that in the present disclosure, downlink, uplink, etc. may be expressed without adding “link”. Further, it may be expressed without adding “Physical” to the head of each channel.

In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may be transmitted. In the wireless communication system 1, as a DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), and a demodulation reference signal (DeModulation) Reference Signal (DMRS), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc. may be transmitted.

The synchronization signal may be, for example, at least one of a primary synchronization signal (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be referred to as an SS/PBCH block, SS Block (SSB), or the like. Note that SS and SSB may also be referred to as reference signals.

Further, in the wireless communication system 1, even if the measurement reference signal (Sounding Reference Signal (SRS)), the demodulation reference signal (DMRS), etc. are transmitted as the uplink reference signal (Uplink Reference Signal (UL-RS)). Good. The DMRS may be called a user terminal specific reference signal (UE-specific Reference Signal).

(base station)
FIG. 7 is a diagram illustrating an example of the configuration of the base station according to the embodiment. The base station 10 includes a control unit 110, a transmission/reception unit 120, a transmission/reception antenna 130, and a transmission line interface 140. It should be noted that the control unit 110, the transmission/reception unit 120, the transmission/reception antenna 130, and the transmission path interface 140 may each be provided with one or more.

Note that, in this example, the functional blocks of the characteristic part in the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be configured by a controller, a control circuit, and the like described based on common recognition in the technical field of the present disclosure.

The control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping) and the like. The control unit 110 may control transmission/reception using the transmission/reception unit 120, the transmission/reception antenna 130, and the transmission path interface 140, measurement, and the like. The control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer the generated data to the transmission/reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of the communication channel, state management of the base station 10, radio resource management, and the like.

The transmission/reception unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmission/reception unit 120 includes a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission/reception circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.

The transmission/reception unit 120 may be configured as an integrated transmission/reception unit, or may be configured by a transmission unit and a reception unit. The transmitting unit may include a transmission processing unit 1211 and an RF unit 122. The receiving unit may include a reception processing unit 1212, an RF unit 122, and a measuring unit 123.

The transmission/reception antenna 130 can be configured by an antenna described based on common recognition in the technical field according to the present disclosure, for example, an array antenna or the like.

The transmitting/receiving unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like. The transmitter/receiver 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.

The transmission/reception unit 120 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

The transmission/reception unit 120 (transmission processing unit 1211) processes the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer (for example, for data and control information acquired from the control unit 110) (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.

The transmission/reception unit 120 (transmission processing unit 1211) performs channel coding (may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (Discrete Fourier Transform (DFT)) on the bit string to be transmitted. Processing (as necessary), inverse fast Fourier transform (Inverse Fast Fourier Transform (IFFT)) processing, precoding, digital-analog conversion, and other transmission processing may be performed to output the baseband signal.

The transmitter/receiver 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal in a radio frequency band, and transmit the radio frequency band signal via the transmission/reception antenna 130. ..

On the other hand, the transmission/reception unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the signal in the radio frequency band received by the transmission/reception antenna 130.

The transmission/reception unit 120 (reception processing unit 1212) performs analog-digital conversion, fast Fourier transform (Fast Fourier Transform (FFT)) processing, and inverse discrete Fourier transform (Inverse Discrete Fourier Transform (IDFT) on the acquired baseband signal. )) Apply reception processing such as processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, User data and the like may be acquired.

The transmission/reception unit 120 (measurement unit 123) may perform measurement on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. The measurement unit 123 receives power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)). , Signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), etc. may be measured. The measurement result may be output to the control unit 110.

The transmission path interface 140 transmits/receives signals (backhaul signaling) to/from devices included in the core network 30, other base stations 10, and the like, and user data (user plane data) for the user terminal 20 and a control plane. Data or the like may be acquired or transmitted.

Note that the transmission unit and the reception unit of the base station 10 according to the present disclosure may be configured by at least one of the transmission/reception unit 120, the transmission/reception antenna 130, and the transmission path interface 140.

Note that the transmission/reception unit 120 may transmit the downlink control information.

The transmission/reception unit 120 may receive the transmission indicating the time unit pattern in the slot (first mode). The control unit 110 may set the time unit based on the information.

The transmitting/receiving unit 120 may transmit information indicating the offset using the time unit (second mode).

The transmitting/receiving unit 120 may transmit a list including time domain resource information using the time unit (second mode). The control unit 110 may control the generation of the list using the time unit.

The transmitter/receiver 120 may receive information regarding support for setting a first list including time domain resource information using slots and a second list including time domain resource information using the time units (the first list). 3 aspect). The transceiver 120 may transmit a plurality of lists generated using different time units (for example, slots and time units shorter than slots).

(User terminal)
FIG. 8 is a diagram showing an example of the configuration of the user terminal according to the embodiment. The user terminal 20 includes a control unit 210, a transmission/reception unit 220, and a transmission/reception antenna 230. Note that each of the control unit 210, the transmission/reception unit 220, and the transmission/reception antenna 230 may be provided with one or more.

Note that, in this example, the functional blocks of the characteristic part in the present embodiment are mainly shown, and the user terminal 20 may be assumed to also have other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured by a controller, a control circuit, and the like that are described based on common recognition in the technical field according to the present disclosure.

The control unit 210 may control signal generation, mapping, and the like. The control unit 210 may control transmission/reception, measurement, and the like using the transmission/reception unit 220 and the transmission/reception antenna 230. The control unit 210 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer the data to the transmission/reception unit 220.

The transmitter/receiver 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitter/receiver 220 may include a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitter/receiver circuit, and the like, which are described based on common knowledge in the technical field of the present disclosure.

The transmission/reception unit 220 may be configured as an integrated transmission/reception unit, or may be configured by a transmission unit and a reception unit. The transmission unit may include a transmission processing unit 2211 and an RF unit 222. The reception unit may include a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

The transmission/reception antenna 230 can be configured by an antenna described based on common recognition in the technical field according to the present disclosure, for example, an array antenna or the like.

The transmitter/receiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.

The transmission/reception unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

The transmission/reception unit 220 (transmission processing unit 2211) processes the PDCP layer, the RLC layer (for example, RLC retransmission control), and the MAC layer (for example, for the data and control information acquired from the control unit 210). , HARQ retransmission control) or the like to generate a bit string to be transmitted.

The transmission/reception unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (if necessary), and IFFT processing on the bit string to be transmitted. The baseband signal may be output by performing transmission processing such as precoding and digital-analog conversion.

Note that whether or not to apply DFT processing may be based on the settings of transform precoding. The transmission/reception unit 220 (transmission processing unit 2211) is configured to transmit the channel using a DFT-s-OFDM waveform when transform precoding is enabled for the channel (for example, PUSCH). The DFT process may be performed as the transmission process, or otherwise, the DFT process may not be performed as the transmission process.

The transmitter/receiver 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal in the radio frequency band, and transmit the radio frequency band signal via the transmission/reception antenna 230. ..

On the other hand, the transmission/reception unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on a signal in the radio frequency band received by the transmission/reception antenna 230.

The transmission/reception unit 220 (reception processing unit 2212) performs analog-digital conversion, FFT processing, IDFT processing (if necessary), filter processing, demapping, demodulation, decoding (error correction) on the acquired baseband signal. User data and the like may be acquired by applying reception processing such as MAC layer processing, RLC layer processing, and PDCP layer processing.

The transmission/reception unit 220 (measurement unit 223) may perform measurement on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), channel information (for example, CSI), and the like. The measurement result may be output to the control unit 210.

Note that the transmission unit and the reception unit of the user terminal 20 according to the present disclosure may be configured by at least one of the transmission/reception unit 220, the transmission/reception antenna 230, and the transmission path interface 240.

The transmitter/receiver 220 may receive the downlink control information. The control unit 210 may determine a time domain resource allocated to the downlink shared channel or the uplink shared channel within a time unit shorter than the slot, based on the value of the predetermined field in the downlink control information.

The transmitter/receiver 220 may receive information indicating the pattern of the time unit in the slot (first mode). The control unit 210 may set the time unit based on the information.

The transmitter/receiver 220 may receive information indicating the offset using the time unit (second mode). The controller 210 may determine the time unit to which the downlink shared channel or the uplink shared channel is assigned based on the information.

The transmission/reception unit 220 may receive a list including time domain resource information using the time unit (second mode). The control unit 210 may determine the time domain resource based on the list and the value of the predetermined field.

The transmitter/receiver 220 may transmit information regarding support for setting a first list including time domain resource information using slots and a second list including time domain resource information using the time units (the first list). 3 aspect).

When a plurality of lists are set in the user terminal 20, the control unit 210 scrambles (CRC) bits of the redundancy check check (CRC) of downlink control information (DCI), RNTI, DCI format, and a predetermined field in DCI. The list used for determining the time domain resources allocated to the PDSCH or PUSCH may be determined based on at least one of the values.

(Hardware configuration)
Note that the block diagrams used in the description of the above embodiment show blocks of functional units. These functional blocks (components) are realized by an arbitrary combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device physically or logically coupled, or directly or indirectly (for example, two or more devices physically or logically separated). , Wired, wireless, etc.) and may be implemented using these multiple devices. The functional blocks may be realized by combining the one device or the plurality of devices with software.

Here, the functions include judgment, determination, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and deemed. , Broadcasting (notifying), notifying (communicating), forwarding (forwarding), configuring (reconfiguring), allocating (allocating, mapping), allocating (assigning), etc. Not limited. For example, a functional block (configuration unit) that causes transmission to function may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like. In any case, as described above, the implementation method is not particularly limited.

For example, the base station, the user terminal, and the like according to an embodiment of the present disclosure may function as a computer that performs the process of the wireless communication method of the present disclosure. FIG. 9 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. The base station 10 and the user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. ..

Note that in the present disclosure, the terms such as a device, a circuit, a device, a section, and a unit are interchangeable with each other. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or a plurality of each device illustrated in the figure, or may be configured not to include some devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Further, the processing may be executed by one processor, or the processing may be executed by two or more processors simultaneously, sequentially, or by using another method. The processor 1001 may be implemented by one or more chips.

For each function in the base station 10 and the user terminal 20, for example, the processor 1001 performs an arithmetic operation by loading predetermined software (program) on hardware such as the processor 1001, the memory 1002, and the communication via the communication device 1004. Is controlled, and at least one of reading and writing of data in the memory 1002 and the storage 1003 is controlled.

The processor 1001 operates an operating system to control the entire computer, for example. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, at least a part of the control unit 110 (210) and the transmission/reception unit 120 (220) described above may be realized by the processor 1001.

Also, the processor 1001 reads a program (program code), software module, data, and the like from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least part of the operations described in the above-described embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and may be realized similarly for other functional blocks.

The memory 1002 is a computer-readable recording medium, and for example, at least Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other appropriate storage media. It may be configured by one. The memory 1002 may be called a register, a cache, a main memory (main storage device), or the like. The memory 1002 may store an executable program (program code), a software module, etc. for implementing the wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray® disk), removable disk, hard disk drive, smart card, flash memory device (eg, card, stick, key drive), magnetic stripe, database, server, and/or other suitable storage medium May be configured by. The storage 1003 may be called an auxiliary storage device.

The communication device 1004 is hardware (transmission/reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device 1004, for example, realizes at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)), a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. May be included. For example, the transmission/reception unit 120 (220) and the transmission/reception antenna 130 (230) described above may be realized by the communication device 1004. The transmitter/receiver 120 (220) may be physically or logically separated from the transmitter 120a (220a) and the receiver 120b (220b).

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

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

In addition, the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), and the like. It may be configured to include hardware, and part or all of each functional block may be realized by using the hardware. For example, the processor 1001 may be implemented using at least one of these hardware.

(Modification)
Note that the terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be read as each other. The signal may also be a message. The reference signal may be abbreviated as RS, and may be referred to as a pilot, a pilot signal, or the like according to the applied standard. Moreover, a component carrier (Component Carrier (CC)) may be called a cell, a frequency carrier, a carrier frequency, or the like.

A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) forming the radio frame may be referred to as a subframe. Further, a subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The numerology includes, for example, subcarrier spacing (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, and radio frame configuration. , At least one of a specific filtering process performed by the transceiver in the frequency domain and a specific windowing process performed by the transceiver in the time domain.

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

A slot may include multiple minislots. Each minislot may be composed of one or more symbols in the time domain. The minislot may also be called a subslot. Minislots may be configured with a smaller number of symbols than slots. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be referred to as PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (PUSCH) mapping type B.

Radio frame, subframe, slot, minislot, and symbol all represent the time unit for signal transmission. Radio frames, subframes, slots, minislots, and symbols may have different names corresponding to them. It should be noted that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be interchanged with each other.

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

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

The TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, a codeword, or a processing unit such as scheduling or link adaptation. When a TTI is given, the time interval (eg, the number of symbols) in which the transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like. A TTI shorter than the normal TTI may be called a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that a long TTI (eg, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and a short TTI (eg, shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms. It may be read as a TTI having the above TTI length.

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

Also, the RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may be configured by one or a plurality of resource blocks.

One or more RBs are a physical resource block (Physical RB (PRB)), a subcarrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, and an RB. It may be called a pair or the like.

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

Bandwidth Part (BWP) (may be called partial bandwidth etc.) represents a subset of continuous common RBs (common resource blocks) for a certain neurology in a certain carrier. Good. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

At least one of the configured BWPs may be active, and the UE does not have to expect to send and receive a given signal/channel outside the active BWP. Note that “cell”, “carrier”, and the like in the present disclosure may be read as “BWP”.

Note that the structure of the radio frame, subframe, slot, minislot, symbol, etc. described above is merely an example. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, and included in RBs The number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and the like can be variously changed.

Further, the information, parameters, etc. described in the present disclosure may be represented by using an absolute value, may be represented by using a relative value from a predetermined value, or by using other corresponding information. May be represented. For example, the radio resource may be indicated by a predetermined index.

The names used for parameters and the like in the present disclosure are not limited names in any respect. Further, the formulas, etc., that use these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not limiting in any way. ..

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

Information and signals may be output from the upper layer to at least one of the lower layer and the lower layer to the upper layer. Information, signals, etc. may be input and output via a plurality of network nodes.

Input/output information, signals, etc. may be stored in a specific location (for example, memory), or may be managed using a management table. Information, signals, etc. that are input and output can be overwritten, updated or added. The output information, signal, etc. may be deleted. The input information, signal, etc. may be transmitted to another device.

The notification of information is not limited to the aspect/embodiment described in the present disclosure, and may be performed using another method. For example, notification of information in the present disclosure includes physical layer signaling (for example, downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), upper layer signaling (for example, Radio Resource Control). (RRC) signaling, broadcast information (master information block (Master Information Block (MIB)), system information block (System Information Block (SIB)), etc.), Medium Access Control (MAC) signaling), other signals or a combination thereof May be implemented by.

The physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration message, or the like. Further, the MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).

Further, the notification of the predetermined information (for example, the notification of “being X”) is not limited to the explicit notification, and may be implicitly (for example, by not issuing the notification of the predetermined information or another information). May be carried out).

The determination may be performed by a value represented by 1 bit (0 or 1), or may be performed by a boolean value represented by true or false. , May be performed by comparison of numerical values (for example, comparison with a predetermined value).

Software, whether called software, firmware, middleware, microcode, hardware description language, or any other name, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules. , Application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc. should be construed broadly.

Also, software, instructions, information, etc. may be sent and received via a transmission medium. For example, the software uses at least one of wired technology (coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) , Servers, or other remote sources, these wired and/or wireless technologies are included within the definition of transmission media.

The terms "system" and "network" used in this disclosure may be used interchangeably. “Network” may mean a device (eg, a base station) included in the network.

In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "pseudo-collocation (Quasi-Co-Location (QCL))", "Transmission Configuration Indication state (TCI state)", "space" "Spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", Terms such as “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, “antenna”, “antenna element”, “panel” are compatible. Can be used for

In the present disclosure, “base station (BS)”, “wireless base station”, “fixed station”, “NodeB”, “eNB (eNodeB)”, “gNB (gNodeB)”, "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel" , "Cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may be referred to by terms such as macro cell, small cell, femto cell, and pico cell.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being defined by a base station subsystem (for example, a small indoor base station (Remote Radio Head (RRH))) to provide communication services. The term "cell" or "sector" refers to part or all of the coverage area of at least one of a base station and a base station subsystem providing communication services in this coverage.

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

A mobile station is a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal. , Handset, user agent, mobile client, client or some other suitable term.

At least one of the base station and the mobile station may be called a transmission device, a reception device, a wireless communication device, or the like. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ). 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 (IoT) device such as a sensor.

Also, the base station in the present disclosure may be replaced by the user terminal. For example, the communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (eg, may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the function of the base station 10 described above. In addition, the words such as “up” and “down” may be replaced with the words corresponding to the communication between terminals (for example, “side”). For example, the uplink channel and the downlink channel may be replaced with the side channel.

Similarly, the user terminal in the present disclosure may be replaced by the base station. In this case, the base station 10 may have the function of the user terminal 20 described above.

In the present disclosure, the operation supposed to be performed by the base station may be performed by its upper node in some cases. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal include a base station and one or more network nodes other than the base station (for example, Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. are conceivable, but not limited to these) or a combination of these is clear.

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be switched according to execution. Further, the order of the processing procedure, sequence, flowchart, etc. of each aspect/embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps in a sample order, and are not limited to the specific order presented.

Each aspect/embodiment described in the present disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global. System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.11 (WiMAX (registered trademark)), IEEE 802. 20, Ultra-WideBand (UWB), Bluetooth (registered trademark), a system using another appropriate wireless communication method, and a next-generation system extended based on these may be applied. Further, a plurality of systems may be combined and applied (for example, a combination of LTE or LTE-A and 5G).

As used in this disclosure, the phrase “based on” does not mean “based only on,” unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using the designations “first,” “second,” etc. as used in this disclosure does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, references to first and second elements do not mean that only two elements may be employed or that the first element must precede the second element in any way.

The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "judgment" means "judging", "calculating", "computing", "processing", "deriving", "investigating", "searching" (looking up, search, inquiry) ( For example, it may be considered to be a “decision” for a search in a table, database or another data structure), ascertaining, etc.

In addition, "decision (decision)" means receiving (eg, receiving information), transmitting (eg, transmitting information), input (input), output (output), access ( Accessing) (eg, accessing data in memory) and the like may be considered to be a "decision."

In addition, "judgment (decision)" is regarded as "decision (decision)" of resolving, selecting, choosing, choosing, establishing, establishing, comparing, etc. Good. That is, "determination (decision)" may be regarded as "determination (decision)" of some operation.

Also, "judgment (decision)" may be read as "assuming," "expecting," "considering," etc.

The “maximum transmission power” described in the present disclosure may mean the maximum value of the transmission power, may mean the nominal maximum transmission power (the nominal UE maximum transmit power), or may be the rated maximum transmission power (the maximum transmission power). It may mean rated UE maximum transmit power).

As used in this disclosure, the term "connected," "coupled," or any variation thereof, refers to any direct or indirect connection or coupling between two or more elements. And may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other. The connections or connections between the elements may be physical, logical, or a combination thereof. For example, “connection” may be read as “access”.

In this disclosure, where two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave Regions, electromagnetic energy having wavelengths in the light (both visible and invisible) region, etc. can be used to be considered "connected" or "coupled" to each other.

In the present disclosure, the term “A and B are different” may mean “A and B are different from each other”. The term may mean that “A and B are different from C”. The terms "remove", "coupled" and the like may be construed similarly as "different".

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

In the present disclosure, if translations add articles, such as a, an, and the in English, the disclosure may include that the noun that follows these articles is in the plural.

Although the invention according to the present disclosure has been described in detail above, it is obvious to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modified and changed modes without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is for the purpose of exemplifying explanation, and does not bring any limiting meaning to the invention according to the present disclosure.

This application is based on Japanese Patent Application No. 2019-021077 filed on January 22, 2019. All of this content is included here.

Claims (6)

A receiver for receiving downlink control information,
Based on the value of the predetermined field in the downlink control information, a control unit that determines the time domain resources allocated to the downlink shared channel or the uplink shared channel in a time unit shorter than the slot,
A user terminal comprising: The receiving unit receives information indicating the time unit pattern in the slot,
The user terminal according to claim 1, wherein the control unit sets the time unit based on the information. The receiving unit receives information indicating an offset using the time unit,
The said control part determines the said time unit to which the said downlink shared channel or the said uplink shared channel is allocated based on the said information, The user terminal of Claim 1 or Claim 2 characterized by the above-mentioned. The receiving unit receives a list including time domain resource information using the time unit,
The said control part determines the said time domain resource based on the said list and the value of the said predetermined field, The user terminal in any one of Claim 1 to 3 characterized by the above-mentioned. The apparatus may further include a transmitter that transmits information regarding support for setting a first list including time domain resource information using the slot and a second list including time domain resource information using the time unit. The user terminal according to any one of claims 1 to 4. Receiving downlink control information,
Based on the value of the predetermined field in the downlink control information, determining a time domain resource allocated to the downlink shared channel or the uplink shared channel in a time unit shorter than the slot,
A wireless communication method for a user terminal, comprising:

Images