WO2021064957A1 - Terminal and wireless communication method - Google Patents

Abstract

A terminal according to one embodiment of the present disclosure comprises: a reception unit that receives first downlink control information for scheduling a first physical shared channel and second downlink control information for scheduling a second physical shared channel; and a control unit that controls cross-carrier scheduling on the basis of the first downlink control information and the second downlink control information. If the first physical shared channel and the second physical shared channel are transmitted via the same cell, the cells to which the first downlink control information and the second downlink control information are transmitted are commonly or individually set.

Description

Terminal and wireless communication method

The present disclosure relates to terminals and wireless communication methods in next-generation mobile communication systems.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of further high-speed data rate, low latency, 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, etc.) is also being considered.

In an existing LTE system (for example, LTE Rel.8-15), the uplink signal is mapped to an appropriate radio resource and transmitted from the UE to the base station. Uplink user data (for example, UL-SCH) is transmitted using an uplink shared channel (Physical Uplink Shared Channel (PUSCH)). In addition, uplink control information (UPLINK Control Information (UCI)) uses PUSCH when transmitted together with uplink user data, and uplink control channel (Physical Uplink Control Channel (PUCCH)) when transmitted independently. Is transmitted using.

In future wireless communication systems (for example, 5G (5th generation mobile communication system), NR (New Radio)), further advancement of mobile broadband (eMBB: enhanced Mobile Broadband) and machine type communication (mMTC) that realizes multiple simultaneous connections. : Massive Machine Type Communications), high reliability and low latency communication (URLLC: Ultra-Reliable and Low-Latency Communications) are expected to support multiple traffic types. For example, URLLC requires higher delay reduction than eMBB and higher reliability than eMBB.

As described above, in future wireless communication systems, it is expected that a plurality of services or traffic types having different requirements (for example, requirements for delay reduction) will coexist. For example, it is assumed that different traffic types are supported within the same carrier (also called CC or cell) or with different carriers.

Further, in NR, as in the existing system (for example, before Rel.15), cross-carrier scheduling (or cross-CC scheduling) that schedules data of other cells by using the downlink control information of a predetermined cell is used. It is also possible to support. However, how to control cross-carrier scheduling when different traffic types are supported has not yet been fully explored.

Therefore, one of the purposes of the present disclosure is to provide a terminal and a wireless communication method capable of appropriately controlling cross-carrier scheduling in a future wireless communication system in which a plurality of traffic types and the like are supported.

The terminal according to one aspect of the present disclosure includes a receiving unit that receives the first downlink control information that schedules the first physical shared channel, the second downlink control information that schedules the second physical shared channel, and the above. It has a first downlink control information and a control unit that controls cross-carrier scheduling based on the second downlink control information, and the first physical shared channel and the second physical shared channel are in the same cell. When transmitted, the first downlink control information and the cell to which the second downlink control information is transmitted are set in common or separately.

According to one aspect of the present disclosure, cross-carrier scheduling can be appropriately controlled in a future wireless communication system in which a plurality of traffic types and the like are supported.

FIG. 1 is a diagram showing an example of cross-carrier scheduling in an existing system. FIG. 2 is a diagram showing an example of cross-carrier scheduling setting information in an existing system. FIG. 3 is a diagram showing an example of cross-carrier scheduling according to the first aspect. FIG. 4 is a diagram showing another example of cross-carrier scheduling according to the first aspect. FIG. 5 is a diagram showing an example of cross-carrier scheduling setting information according to the first aspect. FIG. 6 is a diagram showing another example of the cross-carrier scheduling setting information according to the first aspect. FIG. 7 is a diagram showing an example of cross-carrier scheduling according to the second aspect. FIG. 8 is a diagram showing another example of cross-carrier scheduling according to the second aspect. FIG. 9 is a diagram showing an example of cross-carrier scheduling setting information according to the second aspect. FIG. 10 is a diagram showing another example of the cross-carrier scheduling setting information according to the second aspect. FIG. 11 is a diagram showing another example of the cross-carrier scheduling setting information according to the second aspect. FIG. 12 is a diagram showing another example of the cross-carrier scheduling setting information according to the second aspect. FIG. 13 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 14 is a diagram showing an example of the configuration of the base station according to the embodiment. FIG. 15 is a diagram showing an example of the configuration of the user terminal according to the embodiment. FIG. 16 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.

<Traffic type>
In future wireless communication systems (eg, NR), further sophistication of mobile broadband (eg enhanced Mobile Broadband (eMBB)), machine type communication that realizes multiple simultaneous connections (eg massive Machine Type Communications (mMTC), Internet) Of Things (IoT)), high-reliability and low-latency communication (eg, Ultra-Reliable and Low-Latency Communications (URLLC)) and other traffic types (also called services, service types, communication types, use cases, etc.) are assumed. Will be done. For example, URLLC requires less delay and higher reliability than eMBB.

The traffic type may be identified at the physical layer based on at least one of the following:
-Logical channels with different priorities-Modulation and Coding Scheme (MCS) table (MCS index table)
-Channel Quality Indication (CQI) table-DCI format-Used for scramble (mask) of Cyclic Redundancy Check (CRC) bits included (added) in the DCI (DCI format). (Radio Network Temporary Identifier (RNTI))
-RRC (Radio Resource Control) parameters-Specific RNTI (for example, RNTI for URLLC, MCS-C-RNTI, etc.)
-Search space-A predetermined field in DCI (for example, reuse of a newly added field or an existing field)

Specifically, the traffic type of HARQ-ACK for PDSCH may be determined based on at least one of the following:
An MCS index table (for example, MCS index table 3) used to determine at least one of the PDSCH modulation order, target code rate, and transport block size (TBS). Whether or not to use)
-RNTI used for CRC scrambling of DCI used for scheduling the PDSCH (for example, whether CRC scrambled by C-RNTI or MCS-C-RNTI).

Further, the SR traffic type may be determined based on the upper layer parameter used as the SR identifier (SR-ID). The upper layer parameter may indicate whether the SR traffic type is eMBB or URLLC.

Further, the CSI traffic type may be determined based on the configuration information (CSIreportSetting) related to the CSI report, the DCI type used for the trigger, the DCI transmission parameter, and the like. The setting information, DCI type, etc. may indicate whether the traffic type of the CSI is eMBB or URLLC. Further, the setting information may be an upper layer parameter.

Further, the traffic type of PUSCH may be determined based on at least one of the following.
-The MCS index table used to determine at least one of the modulation order, target coding rate, and TBS of the PUSCH (for example, whether or not to use the MCS index table 3).
-RNTI used for CRC scrambling of DCI used for scheduling the PUSCH (for example, whether CRC scrambled by C-RNTI or MCS-C-RNTI).

The traffic type may be associated with communication requirements (requirements such as delay and error rate, requirements), data type (voice, data, etc.) and the like.

The difference between the URLLC requirement and the eMBB requirement may be that the URLLC latency is smaller than the eMBB delay, or that the URLLC requirement includes a reliability requirement.

For example, the eMBB user (U) plane delay requirement may include that the downlink U-plane delay is 4 ms and the uplink U-plane delay is 4 ms. On the other hand, the URLLC U-plane delay requirement may include that the downlink U-plane delay is 0.5 ms and the uplink U-plane delay is 0.5 ms. The reliability requirement of URLLC may also include a 32-byte error rate of ^{10-5 at a U-plane delay of 1 ms.}

In addition, as enhanced Ultra Reliable and Low Latency Communications (eURLLC), improvement of traffic reliability mainly for unicast data is being considered. In the following, when URLLC and eURLLC are not distinguished, they are simply referred to as URLLC.

<Cross-carrier scheduling>
In the existing LTE system, cross-carrier scheduling (CCS) is supported in which a UE in which a plurality of cells (CC) are set is notified of the allocation of PDSCH in another cell by using the PDCCH of a predetermined cell. In this case, the base station can specify a cell for detecting PDSCH by using a 3-bit CIF (Carrier Indicator Field).

In cross-carrier scheduling in DL, when applying CA, the downlink shared channel (PDSCH) and / or uplink shared channel (PUSCH) of one CC is assigned by using the downlink control channel (or DCI) of another CC. (See Fig. 1).

In FIG. 1, the downlink control information (DCI # 1) instructing the allocation of PDSCH and / or PUSCH transmitted by CC # 1 (for example, S-Cell) is set to another CC # 0 (for example, P-Cell). Multiplexed to PDCCH of. At this time, in order to identify which CC (CC0 or CC1) PDSCH and / or PUSCH allocation instruction is used for the downlink control information (DCI # 1) multiplexed on the PDCCH of CC # 1, the carrier A DCI configuration with an identifier (CI: Carrier Indicator) is applied.

In the existing system, a field (CIF: Carrier Indicator Field) for a 3-bit carrier identifier is set in the downlink control information, and the CC corresponding to the downlink control information is notified to the user terminal. The user terminal performs PDSCH reception processing and / or PUSCH transmission processing in a predetermined CC based on the CIF included in the downlink control information.

In addition, when cross-carrier scheduling is applied to a certain cell (CC), the UE is notified of information that cross-carrier scheduling is applied to the cell and information about which cell (CC) the schedule is scheduled from. Will be done. Such information regarding whether or not cross-carrier scheduling is applied and information regarding the scheduling cell (which transmits the CIF) are used as upper layer control information (for example, RRC control information) of the scheduled cell from the base station to the UE. You can notify.

Here, a cell that controls the allocation of PDSCH and / or PUSCH of another cell (CC) (transmits DCI including CIF) can be called a scheduling cell (Scheduling Cell). Further, a cell in which cross-carrier scheduling is set (a cell scheduled based on CIF) can be called a scheduled cell (Scheduled Cell).

In the cross-carrier scheduling shown in FIG. 1, the case where the scheduling cell corresponds to Cell # 0 (CC # 0) and the scheduled cell (also referred to as scheduled cell) corresponds to Cell # 1 (corresponding to CIF = 1) Shown. The scheduling cell (CC) may also instruct the UE to allocate the PDSCH and / or PUSCH of the scheduling cell (self-schedule) using the CIF.

The UE determines the scheduled cell based on the index (for example, ServeCellIndex) corresponding to the 3-bit CIF value included in the PDCCH (or DCI) transmitted in the scheduling cell, and receives the PDSCH assigned in the scheduled cell. To do.

The correspondence between the CIF value and the ServeCellIndex value may be set by higher layer signaling or the like. In this case, the CIF is set for the PDCCH (or DCI) of the scheduling cell (CC), and the upper layer signaling is set so that the value of each CIF corresponds to the value of the ServeCellIndex of the corresponding scheduled cell (CC). To.

FIG. 2 is a diagram showing an example of cross-carrier scheduling setting information. The name of IE shown in FIG. 2 is merely an example, and is not limited to the one shown in the figure. As shown in FIG. 2, the cross-carrier scheduling setting information (CrossCarrierSchedulingConfig) may include either information regarding scheduling of the own cell (own) or information regarding scheduling by another cell (cross-carrier scheduling) (other). Good.

The information (own) regarding the scheduling of the own cell may include information (cif-Presence) indicating the presence or absence of CIF. When cif-Presence is true, the CIF value of the cell (scheduling cell) may be set to 0. If the CIF value of DCI transmitted in the scheduling cell is 0, the UE may determine that it is self-scheduled.

The information (other) related to scheduling by other cells may include a cell identifier (cell index, scheduling cell ID, schedulingCellId) that signals DCI. For example, schedulingCellId tells the UE which cell signals DL allocation and UL grant. Further, the CIF value (cif-InSchedulingCell) of the cell (scheduled cell) used in the scheduling cell may be included in other.

When decoding the PDCCH (or DCI) of the common search space (CSS: Common Search Space), the UE may perform the decoding on the assumption that there is no CIF. That is, when the CIF is set, the UE decodes the control channel in which the CIF is set in the UE specific search space (USS: UE specific Search Space), and decodes the control channel in which the CIF is not set in the common search space.

It is expected that cross-carrier scheduling will be supported in future wireless communication systems as well. For example, it is assumed that different traffic types are supported within the same carrier or with different carriers. However, how to control cross-carrier scheduling when different traffic types are supported has not yet been fully explored.

For example, a scheduling cell (also called a scheduling carrier or a scheduling CC) that schedules different traffic types (for example, eMBB and URLLC) is commonly set for a scheduled cell (also called a scheduled carrier or a scheduled CC). The question is whether they are set separately.

For example, when different DCI types or DCI transmission parameters are applied depending on the traffic type, it is assumed that the size of a predetermined DCI field (for example, CIF field) for scheduling each traffic type is different. In such a case, how to control the cross-carrier scheduling becomes a problem.

Alternatively, the problem is whether the scheduling cells that schedule different transmission directions (for example, UL and DL) are set in common or separately for the scheduled cells. For example, when the scheduled cell is an unlicensed carrier, or when the traffic type of the scheduled cell is URLLC, how to control cross-carrier scheduling becomes a problem.

Therefore, the present inventors examined a cross-carrier schedule control method in consideration of at least one of a traffic type, a transmission direction, and a cell type (for example, unlicensed or licensed), and conceived the present invention.

Hereinafter, embodiments according to the present invention will be described in detail with reference to the drawings. The configurations according to each embodiment may be applied individually or in combination. Further, in the following description, a case where a plurality of shared channels (for example, a first physical shared channel and a second physical shared channel) are transmitted or assigned in the same cell will be described as an example, but the description is limited to this. I can't. The same may be applied when a plurality of shared channels are transmitted in different cells.

(First aspect)
A first aspect describes a scheduling cell that schedules data corresponding to each traffic type when physical shared channels (or data) corresponding to different traffic types are scheduled in a scheduled cell.

The cells that schedule data of different traffic types transmitted in a certain scheduled cell may be set to be common (for example, the same cell) (option 1-1). Alternatively, the cells that schedule the data of different traffic types transmitted in a scheduled cell may be set separately (for example, different cells) (option 1-2).

<Option 1-1>
A cell (for example, a scheduled cell) in which a first DCI and a second DCI that schedule a first physical shared channel and a second physical shared channel transmitted in the same cell (for example, a scheduled cell) are transmitted, respectively. ) May be set to the same (see FIG. 3). The scheduling unit, time interval, allocation, etc. shown in FIG. 3 are examples and are not limited thereto.

In FIG. 3, when the first DCI that schedules the first physical shared channel transmitted by CC # 2 and the second DCI that schedules the second physical shared channel are transmitted by the same CC # 1. Is shown. Here, CC # 1 corresponds to the scheduling cell and CC # 2 corresponds to the scheduled cell. That is, the scheduling cell for scheduling the first traffic type and the second traffic type is the same for the scheduled cell (CC # 2).

The first physical shared channel may be at least one of PUSCH and PDSCH corresponding to the first traffic type (eg, URLLC). The second physical shared channel may be at least one of the PUSCH and PDSCH corresponding to the second traffic type (eg, eMBB). Of course, the traffic type and number are not limited to this.

In this way, the control of cross-carrier scheduling is simplified by making the scheduling cell that schedules the first traffic type transmitted by CC # 2 the same as the scheduling cell that schedules the second traffic type. Can be done.

The first DCI and the second DCI may differ from each other in at least one of the DCI format, the RNTI type, the control resource set to be used, the search space, the field type included in the DCI, and the field size of the DCI. Alternatively, the first DCI and the second DCI may have different information (for example, MCS) to be notified to the UE in the same field.

Further, the size of the field for notifying the scheduled cell included in the first DCI (for example, the first CIF) and the field for notifying the scheduled cell included in the second DCI (for example, the second CIF) are the same. It may be.

Alternatively, the size of the field notifying the scheduled cell contained in the first DCI (for example, the first CIF) and the field notifying the scheduled cell contained in the second DCI (for example, the second CIF) are different. It may be set to (for example, set differently). For example, the size of the first CIF may be changed and the size of the second CIF may be fixed. Alternatively, the size changeable range of the first CIF may be larger (or smaller) than the changeable range of the size of the second CIF.

By configuring the size of the first CIF and the second CIF to be set separately, the number of CCs that support (or set) the first traffic type and the second traffic type are supported (or set). , The CIF of each DCI can be flexibly set when the number of CCs to be set is different. As a result, an increase in DCI overhead can be suppressed.

<Option 1-2>
A cell (for example, a scheduled cell) in which a first DCI and a second DCI that schedule a first physical shared channel and a second physical shared channel transmitted in the same cell (for example, a scheduled cell) are transmitted, respectively. ) May be set separately (see FIG. 4). The scheduling unit, time interval, allocation, etc. shown in FIG. 3 are examples and are not limited thereto.

FIG. 4 shows a case where the first DCI that schedules the first physical shared channel transmitted by CC # 2 and the second DCI that schedules the second physical shared channel are transmitted by different CCs. ing. Here, the case where the first DCI is transmitted in CC # 1 and the second DCI is transmitted in a cell other than CC # 1 (for example, CC # 2 or CC # 3) is shown.

Also, CC # 1 and CC # 3 correspond to scheduling cells, and CC # 2 corresponds to scheduled cells. That is, the scheduling cell that schedules the first traffic type and the scheduling cell that schedules the second traffic type are different from the scheduled cell (CC # 2). When the second DCI is transmitted by CC # 2, it has a self-scheduling configuration.

The first physical shared channel may be at least one of PUSCH and PDSCH corresponding to the first traffic type (eg, URLLC). The second physical shared channel may be at least one of the PUSCH and PDSCH corresponding to the second traffic type (eg, eMBB). Of course, the traffic type and number are not limited to this.

In this way, cross-carrier scheduling can be flexibly set by making it possible to separately set the scheduling cell that schedules the first traffic type transmitted by CC # 2 and the scheduling cell that schedules the second traffic type. it can.

The configuration described in option 1-1 may be applied to the configuration of the first DCI and the second DCI, the size of the CIF included in the first DCI and the second DCI, and the like.

<Cross-career schedule setting>
The cross-carrier scheduling setting information applied to the data corresponding to the predetermined (for example, the first) traffic type may be set from the base station to the UE by using the upper layer signaling.

FIG. 5 is a diagram showing an example of cross-carrier scheduling setting information. FIG. 5 shows a case where the cross-carrier scheduling setting (for example, CrossCarrierSchedulingConfig-r16) corresponding to the first traffic type (for example, URLLC) is provided separately from the existing cross-carrier scheduling setting (for example, CrossCarrierSchedulingConfig). There is.

In this case, the network can set the application of cross-carrier scheduling separately for each traffic type. The names of IE shown in FIG. 5 are merely examples, and are not limited to those shown in the drawings. For example, the size of the information (cif-InSchedulingCell) regarding the CIF value may be set separately.

FIG. 5 shows a case where the cross-carrier scheduling settings are set separately, but the present invention is not limited to this. For example, as shown in FIG. 6, cross-carrier scheduling information (eg, schedulingCellInfo-r16) to be applied to a predetermined traffic type may be included in the existing cross-carrier scheduling settings (for example, CrossCarrierSchedulingConfig).

(Second aspect)
In the second aspect, when the physical shared channels (or data) corresponding to different transmission directions are scheduled in a certain scheduled cell, the scheduling cell that schedules the data corresponding to each transmission direction will be described.

The cells that schedule data in different transmission directions transmitted in a certain scheduled cell may be set to be common (for example, the same cell) (option 2-1). Alternatively, the cells that schedule the data in different transmission directions transmitted in a certain scheduled cell may be set separately (for example, different cells) (option 2-2).

<Option 2-1>
A first that schedules a physical shared channel for DL transmission (eg, DL data or PDSCH) transmitted in the same cell (eg, scheduled cell) and a physical shared channel for UL transmission (eg, UL data or PUSCH), respectively. The cell to which the DCI and the second DCI are transmitted (eg, the scheduled cell) may be set to be the same (see FIG. 7). The scheduling unit, time interval, allocation, etc. shown in FIG. 7 are examples and are not limited thereto.

FIG. 7 shows a case where the first DCI that schedules DL data transmitted by CC # 2 and the second DCI that schedules UL data are transmitted by the same CC # 1. Here, CC # 1 corresponds to the scheduling cell and CC # 2 corresponds to the scheduled cell. That is, the scheduling cell for scheduling DL transmission and UL transmission is the same for the scheduled cell (CC # 2).

The physical shared channel for DL transmission may be a PDSCH corresponding to a first traffic type (eg, URLLC) or a second traffic type (eg, eMBB). The physical shared channel of UL transmission may be a PUSCH corresponding to a first traffic type (eg, URLLC) or a second traffic type (eg, eMBB). Of course, the traffic type and number are not limited to this.

In this way, by making the scheduling cell for scheduling DL data transmitted by CC # 2 the same as the scheduling cell for scheduling UL data, it is possible to simplify the control of cross-carrier scheduling.

The first DCI and the second DCI may differ from each other in at least one of the DCI format, the RNTI type, the control resource set to be used, the search space, the field type included in the DCI, and the field size of the DCI.

Further, the size of the field for notifying the scheduled cell included in the first DCI (for example, the first CIF) and the field for notifying the scheduled cell included in the second DCI (for example, the second CIF) are the same. It may be.

Alternatively, the size of the field notifying the scheduled cell contained in the first DCI (for example, the first CIF) and the field notifying the scheduled cell contained in the second DCI (for example, the second CIF) are different. It may be set to (for example, set differently).

The number of CCs that support (or set) DL transmission and the number of CCs that support (or set) UL transmission by configuring the size of the first CIF and the second CIF to be set separately. Can be flexibly set for each DCI when As a result, an increase in DCI overhead can be suppressed.

<Option 2-2>
A first that schedules a physical shared channel for DL transmission (eg, DL data or PDSCH) transmitted in the same cell (eg, scheduled cell) and a physical shared channel for UL transmission (eg, UL data or PUSCH), respectively. The cell to which the DCI and the second DCI are transmitted (eg, the scheduled cell) may be set separately (see FIG. 8). The scheduling unit, time interval, allocation, etc. shown in FIG. 8 are examples and are not limited thereto.

FIG. 8 shows a case where the first DCI that schedules DL data transmitted by CC # 2 and the second DCI that schedules UL data are transmitted by different CCs. Here, the case where the first DCI is transmitted in CC # 1 and the second DCI is transmitted in a cell other than CC # 1 (for example, CC # 2 or CC # 3) is shown.

Also, CC # 1 and CC # 3 correspond to scheduling cells, and CC # 2 corresponds to scheduled cells. That is, the scheduling cell for scheduling DL data and the scheduling cell for scheduling UL data are different from the scheduled cell (CC # 2). When the second DCI is transmitted by CC # 2, it has a self-scheduling configuration.

The physical shared channel for DL transmission may be a PDSCH corresponding to a first traffic type (eg, URLLC) or a second traffic type (eg, eMBB). The physical shared channel of UL transmission may be a PUSCH corresponding to a first traffic type (eg, URLLC) or a second traffic type (eg, eMBB). Of course, the traffic type and number are not limited to this.

In this way, the cross-carrier scheduling can be flexibly set by making it possible to separately set the scheduling cell for scheduling the DL data transmitted by CC # 2 and the scheduling cell for scheduling the UL data.

The configuration described in option 2-1 may be applied to the configuration of the first DCI and the second DCI, the size of the CIF included in the first DCI and the second DCI, and the like.

<Cross-career schedule setting>
The cross-carrier scheduling setting information applied to the data corresponding to at least one of the first transmission direction (for example, DL) and the second transmission direction (for example, UL) is obtained from the base station to the UE by using the upper layer signaling. May be set to.

FIG. 9 is a diagram showing an example of cross-carrier scheduling setting information. In FIG. 9, the cross-carrier scheduling setting corresponding to the first transmission direction (for example, DL) (for example, CrossCarrierSchedulingConfig-DL-r16) and the cross-carrier scheduling corresponding to the second transmission direction (for example, UL) are set. The case where the setting (for example, CrossCarrierSchedulingConfig-UL-r16) is provided separately from the existing cross-carrier scheduling setting (for example, CrossCarrierSchedulingConfig) is shown.

In this case, the network can separately set the application of cross-carrier scheduling (for example, the cell to be applied) for each transmission direction. The name of IE shown in FIG. 9 is merely an example, and is not limited to the one shown in the figure. For example, the size of the information (cif-InSchedulingCell) regarding the CIF value may be set separately.

FIG. 9 shows a case where the cross-carrier scheduling setting is set separately for each transmission direction, but the present invention is not limited to this. For example, as shown in FIG. 10, cross-carrier scheduling information (eg, schedulingCellInfo-UL-r16 and schedulingCellInfo-DL-r16) applied in a predetermined transmission direction in an existing cross-carrier scheduling setting (for example, CrossCarrierSchedulingConfig). At least one of) may be included.

Alternatively, in the cross-carrier scheduling information applied to a predetermined traffic type (for example, schedulingCellInfo-r16), the information about the scheduled cell (for example, other) may include the information about the scheduled cell corresponding to each transmission direction. (See FIG. 11). Thereby, the transmission direction to which the cross-carrier scheduling is applied can be set for each cell (for example, a scheduled cell).

Alternatively, the information about the scheduling cell (eg, own) may include information about the scheduling cell that performs cross-carrier scheduling for each transmission direction (eg, at least one of cif-Presence-UL and cif-Presence-DL). It may be good (see FIG. 12).

This makes it possible to separately set a cell for self-scheduling (scheduling cell) and a cell for cross-carrier scheduling (scheduled cell) for each transmission direction. For example, it is possible to flexibly set a pattern such as a scheduling cell that self-schedules only in one transmission direction and a scheduled cell that performs cross-carrier scheduling only in one transmission direction.

(Third aspect)
In the third aspect, the control of cross-carrier scheduling when the unlicensed band is used will be described.

<Unlicensed band>
In the unlicensed band (for example, 2.4 GHz band, 5 GHz band, 6 GHz band), it is assumed that a plurality of systems such as a Wi-Fi system and a system supporting LAA (LAA system) coexist. It is considered that collision avoidance and / or interference control of transmission between the plurality of systems is required.

In the LAA of the existing LTE system, the data transmission device listens to confirm the presence or absence of transmission of other devices (for example, base station, user terminal, Wi-Fi device, etc.) before transmitting data in the unlicensed band. (Also called Listen Before Talk (LBT), Clear Channel Assessment (CCA), carrier sense, channel sensing, channel access operation, etc.).

The transmitting device may be, for example, a base station (for example, gNodeB (gNB)) for downlink (DL) and a user terminal (for example, User Equipment (UE)) for uplink (UL). Further, the receiving device that receives the data from the transmitting device may be, for example, a UE in DL and a base station in UL.

In the LAA of the existing LTE system, the transmitting device starts data transmission after a predetermined period (for example, immediately after or during the backoff period) after the LBT detects that there is no transmission of another device (idle state). ..

An NR system that uses an unlicensed band may be called an NR-Unlicensed (U) system, an NR LAA system, or the like. Dual Connectivity (DC) between the licensed band and the unlicensed band, Stand-Alone (SA) of the unlicensed band, etc. may also be included in the NR-U.

The node (for example, base station, UE) in NR-U starts transmission after confirming that the channel is free (idle) by LBT for coexistence with other systems or other operators.

In the NR-U system, when the LBT result is idle (LBT-idle), the base station or UE acquires a transmission opportunity (Transmission Opportunity (TxOP)) and transmits. The base station or UE does not transmit when the LBT result is busy (LBT-busy). The time of transmission opportunity is also called Channel Occupancy Time (COT).

Note that LBT-idle may be read as LBT success. LBT-busy may be read as LBT failure.

In this way, in the unlicensed band, it is necessary to apply the listening operation before transmission. In such a case, how to apply cross-carrier scheduling becomes a problem. In the third aspect, cross-carrier scheduling may be controlled by utilizing at least one of the following options 3-1 to 3-4.

<Option 3-1>
In cross-carrier scheduling, the scheduling cell (or scheduling carrier) may be limited to the license cell (or license carrier). That is, the unlicensed cell may be configured not to be set as a scheduling cell (for example, only a scheduled cell is set).

As a result, even if transmission is restricted due to LBT failure in the unlicensed band, the communication delay in cross-carrier scheduling can be reduced by configuring the unlicensed band not to schedule other cells. Can be suppressed.

<Option 3-2>
In cross-carrier scheduling, the scheduling cell may be set to a licensed cell or an unlicensed cell. That is, the unlicensed cell may be configured to allow the scheduling cell to be set. In this case, the network (for example, a base station) may notify the UE of information about the scheduling cell by using upper layer signaling or the like.

The base station may switch the scheduling cell from the unlicensed cell to the licensed cell according to the communication status. As a result, even when the unlicensed cell is set as the scheduling cell, the communication delay in cross-carrier scheduling can be reduced.

<Option 3-3>
In cross-carrier scheduling, the scheduling cells that schedule UL and DL in the unlicensed cell (or unlicensed carrier) may be set to the same cell (or carrier).

The scheduling cell may be limited to the license cell (for example, option 3-1). Alternatively, the scheduling cell may be set as a licensed cell or an unlicensed cell (eg, option 3-2). In this case, the base station may notify the UE of information about the scheduling cell by using higher layer signaling or the like.

<Option 3-4>
In cross-carrier scheduling, the scheduling cells that schedule UL and DL in the unlicensed cell (or unlicensed carrier) may be set separately (for example, different cells). In this case, the base station may notify the UE of information on cells that schedule UL and information on cells that schedule DL by using upper layer signaling or the like.

Scheduling cells that schedule at least one of UL and DL may be limited to license cells (eg, option 3-1). Alternatively, the scheduling cell that schedules at least one of UL and DL may be set to a licensed cell or an unlicensed cell (for example, option 3-2). In this case, the base station may notify the UE of information about the scheduling cell by using higher layer signaling or the like.

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

FIG. 13 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 using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by Third Generation Partnership Project (3GPP). ..

Further, the wireless communication system 1 may support dual connectivity between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC is dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E). -UTRA Dual Connectivity (NE-DC)) may be included.

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

The wireless communication system 1 has dual connectivity between a plurality of base stations in 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 that forms a macro cell C1 having a relatively wide coverage, and a base station 12 (12a-12c) that is arranged in the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. You may prepare. The user terminal 20 may be located in at least one cell. The arrangement, number, and the like of each cell and the user terminal 20 are not limited to the mode 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)) and dual connectivity (DC) using a plurality of component carriers (Component Carrier (CC)).

Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a 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.

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

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 base stations 11 and 12, the base station 11 corresponding to the higher-level station is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to a relay station (relay) is 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 such as Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

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

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, 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, another wireless access system (for example, another single carrier transmission system, another multi-carrier transmission system) may be used as the UL and DL wireless access systems.

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)) and the like may be used.

Further, in the wireless communication system 1, as the uplink channel, the uplink shared channel (Physical Uplink Shared Channel (PUSCH)), the uplink control channel (Physical Uplink Control Channel (PUCCH)), and the random access channel shared by each user terminal 20 are used. (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. Further, the Master Information Block (MIB) may be transmitted by the PBCH.

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

The DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. The PDSCH may be read as DL data, and the PUSCH may be read as UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may be used to detect PDCCH. CORESET corresponds to a resource that searches for DCI. The search space corresponds to the search area and search method of PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the 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", etc. 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, it may be called Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.) and scheduling request (Scheduling Request () Uplink Control Information (UCI) including at least one of SR)) may be transmitted. The PRACH may transmit a random access preamble to establish a connection with the cell.

In this disclosure, downlinks, uplinks, etc. may be expressed without "links". Further, it may be expressed without adding "Physical" at the beginning of various channels.

In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), and the like may be transmitted. In the wireless communication system 1, the DL-RS includes 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 (Positioning Reference Signal (PRS)), phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), and the like 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)). The signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be referred to as SS / PBCH block, SS Block (SSB) and the like. In addition, SS, SSB and the like may also be called a reference signal.

Further, in the wireless communication system 1, even if a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), or the like is transmitted as an 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. 14 is a diagram showing 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. The control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may each be provided with one or more.

Note that this example mainly shows the functional blocks of the feature portion in the present embodiment, 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 part described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to 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, measurement, and the like using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the 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, management of radio resources, 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 transmitter / receiver 120 includes 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 recognition in the technical fields 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 composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

The transmitting / receiving antenna 130 can be composed of an antenna described based on common recognition in the technical field according to the present disclosure, for example, an array antenna.

The transmission / reception unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like. The transmission / reception unit 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), and the like.

The transmission / reception unit 120 (transmission processing unit 1211) processes, for example, Packet Data Convergence Protocol (PDCP) layer processing and Radio Link Control (RLC) layer processing (for example, RLC) for data, control information, etc. acquired from control unit 110. RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), and the like 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)) for the bit string to be transmitted. The base band signal may be output by performing processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, digital-analog transform, and other transmission processing.

The transmission / reception unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band 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, or the like on the radio frequency band signal received by the transmission / reception antenna 130.

The transmission / reception unit 120 (reception processing unit 1212) performs analog-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) Processing (if necessary), filtering, decoding, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing are applied. 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, or the like based on the received signal. The measuring unit 123 has received power (for example, Reference Signal Received Power (RSRP)) and 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)), propagation path information (for example, CSI), and the like may be measured. The measurement result may be output to the control unit 110.

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

The transmission unit and the reception unit of the base station 10 in the present disclosure may be composed of at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140.

The transmission / reception unit 120 includes first downlink control information that schedules a first physical shared channel (for example, at least one of PUSCH and PDSCH) and a second physical shared channel (for example, at least one of PUSCH and PDSCH). The second downlink control information is transmitted.

The control unit 110 transmits (or schedules) a cell to which the first physical shared channel and the second physical shared channel are transmitted, and at least one of the first downlink control information and the second downlink control information is transmitted. The cells may be controlled to be different cells.

(User terminal)
FIG. 15 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. The control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may each be provided with one or more.

Note that this example mainly shows the functional blocks of the feature portion in the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like described based on the 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, and the like, and transfer the data to the transmission / reception unit 220.

The transmission / reception unit 220 may include a baseband unit 221 and 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 can be composed of 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 the common recognition in the technical field according to the present disclosure.

The transmission / reception unit 220 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

The transmitting / receiving antenna 230 can be composed of an antenna described based on common recognition in the technical field according to the present disclosure, for example, an array antenna.

The transmission / reception unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like. The transmission / reception unit 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), and the like.

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

The transmission / reception unit 220 (transmission processing unit 2211) performs channel coding (may include error correction coding), modulation, mapping, filtering processing, DFT processing (if necessary), and IFFT processing for the bit string to be transmitted. , Precoding, digital-to-analog conversion, and other transmission processing may be performed to output the baseband signal.

Whether or not to apply the DFT process may be based on the transform precoding setting. When the transform precoding is enabled for a channel (for example, PUSCH), the transmission / reception unit 220 (transmission processing unit 2211) transmits the channel using the DFT-s-OFDM waveform. The DFT process may be performed as the transmission process, and if not, the DFT process may not be performed as the transmission process.

The transmission / reception unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band 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, or the like on the signal in the radio frequency band received by the transmission / reception antenna 230.

The transmission / reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering processing, demapping, demodulation, and decoding (error correction) for the acquired baseband signal. Decoding may be included), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.

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

The transmitter and receiver of the user terminal 20 in the present disclosure may be composed of at least one of the transmitter / receiver 220 and the transmitter / receiver antenna 230.

The transmission / reception unit 220 includes the first downlink control information that schedules the first physical shared channel (for example, at least one of PUSCH and PDSCH) and at least one of the second physical shared channels (for example, PUSCH and PDSCH). Receives the second downlink control information that schedules one).

Further, the transmission / reception unit 220 may receive the cross-carrier scheduling setting information by higher layer signaling. For example, the transmission / reception unit 220 may receive information regarding the cell to which the first downlink control information is transmitted and the cell to which the second downlink control information is transmitted by higher layer signaling.

The control unit 210 controls cross-carrier scheduling based on the first downlink control information and the second downlink control information.

When the first physical shared channel and the second physical shared channel are transmitted in the same cell, the cell in which the first downlink control information and the second downlink control information are transmitted is set to be common (for example, the same cell). May be done.

Alternatively, when the first physical shared channel and the second physical shared channel are transmitted in the same cell, the cells to which the first downlink control information and the second downlink control information are transmitted are separate (for example, different cells). May be set to.

The first physical shared channel and the second physical shared channel may have different traffic types or may be scheduled with different types of downlink control information. Alternatively, the first physical shared channel and the second physical shared channel may have different transmission directions.

The cell to which the first downlink control information or the second downlink control information is transmitted is limited to the license band, or at least one of the license band and the unlicensed band may be set by higher layer signaling.

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

Here, the functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and deemed. , Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (constituent unit) for functioning transmission may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like. As described above, the method of realizing each of them is not particularly limited.

For example, the base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. FIG. 16 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the 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. ..

In this disclosure, the terms of devices, circuits, devices, sections, units, etc. can be read as each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

For example, although only one processor 1001 is shown, there may be a plurality of processors. Further, the processing may be executed by one processor, or the processing may be executed simultaneously, sequentially, or by using other methods by two or more processors. The processor 1001 may be mounted by one or more chips.

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

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

Further, the processor 1001 reads a program (program code), a software module, data, etc. 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 a part of the operations described in the above-described embodiment 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 in the same manner for other functional blocks.

The memory 1002 is a computer-readable recording medium, for example, at least a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), or any other suitable storage medium. It may be composed of one. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can be executed to implement the wireless communication method according to the embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, and is, for example, a flexible disc, a floppy (registered trademark) disc, an optical magnetic disc (for example, a compact disc (Compact Disc ROM (CD-ROM)), a digital versatile disc, etc.). At least one of Blu-ray® disks, removable disks, optical disc drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers, and other suitable storage media. It may be composed of. The storage 1003 may be referred to as an auxiliary storage device.

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

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a 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 have an integrated configuration (for example, a touch panel).

Further, each device such as the processor 1001 and the memory 1002 is connected by the 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.

Further, the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (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 a part or all of each functional block may be realized by using the hardware. For example, processor 1001 may be implemented using at least one of these hardware.

(Modification example)
The terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channels, symbols and signals (signals or signaling) may be read interchangeably. Also, the signal may 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 depending on the applied standard. Further, the component carrier (Component Carrier (CC)) may be referred to as a cell, a frequency carrier, a carrier frequency, or the like.

The wireless frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the wireless frame may be referred to as a subframe. Further, the 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 is independent of numerology.

Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel. 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 wireless frame configuration. , A specific filtering process performed by the transmitter / receiver in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.

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

The slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain. The mini-slot may also be referred to as a sub-slot. A minislot may consist of a smaller number of symbols than the slot. PDSCH (or PUSCH) transmitted in time units larger than the 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.

The wireless frame, subframe, slot, minislot and symbol all represent the time unit when transmitting a signal. The radio frame, subframe, slot, minislot and symbol may have different names corresponding to each. The time units such as frames, subframes, slots, mini slots, and symbols in the present disclosure may be read as each other.

For example, one subframe may be called TTI, a plurality of consecutive subframes may be called TTI, and one slot or one minislot may be called TTI. That is, 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-13 symbols), or a period longer than 1 ms. It may be. The unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units. 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, or a code word, or may be a processing unit such as scheduling or link adaptation. When a TTI is given, the time interval (for example, the number of symbols) to which the transport block, code block, code word, etc. are actually mapped may be shorter than the TTI.

When one slot or one mini slot is called TTI, one or more TTIs (that is, one or more slots or one or more mini slots) may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be referred to as 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. TTIs shorter than normal TTIs may be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots, and the like.

The long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (for example, 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 (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 contained in the RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers contained in the RB may be determined based on numerology.

Further, the RB may include one or more symbols in the time domain, and may have a length of 1 slot, 1 mini slot, 1 subframe or 1 TTI. Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.

One or more RBs are a physical resource block (Physical RB (PRB)), a sub-carrier 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.

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

Bandwidth Part (BWP) (which may also be called partial bandwidth, etc.) represents a subset of consecutive common resource blocks (RBs) for a neurology in a carrier. May be good. Here, the common RB may be specified by the index of the RB with respect to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

At least one of the configured BWPs may be active, and the UE may not expect to send or receive a given signal / channel outside the active BWP. In addition, "cell", "carrier" and the like in this disclosure may be read as "BWP".

Note that the above-mentioned structures such as wireless frames, subframes, slots, mini slots, and symbols are merely examples. For example, the number of subframes contained in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in the RB. The number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

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

The names used for parameters, etc. in this disclosure are not limited in any respect. Further, mathematical formulas and the like using 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 techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.

In addition, information, signals, etc. can be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layers. Information, signals, etc. may be input / 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. Input / output information, signals, etc. can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

The notification of information is not limited to the mode / embodiment described in the present disclosure, and may be performed by using another method. For example, the notification of information in the present disclosure includes physical layer signaling (for example, downlink control information (DCI)), uplink control information (Uplink Control Information (UCI))), and higher layer signaling (for example, Radio Resource Control). (RRC) signaling, broadcast information (master information block (MIB), system information block (SIB), etc.), medium access control (MAC) signaling), other signals or combinations thereof May be carried out by.

Note that the physical layer signaling may be referred to as 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 (RRC Connection Reconfiguration) message, or the like. Further, MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).

In addition, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit notification, but implicitly (for example, by not notifying the predetermined information or another information). May be done (by notification of).

The determination may be made by a value represented by 1 bit (0 or 1), or by a boolean value represented by true or false. , May be done by numerical comparison (eg, comparison with a given value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name, is an instruction, instruction set, code, code segment, program code, program, subprogram, software module. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted.

Further, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, a website where software uses at least one of wired technology (coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.). When transmitted from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.

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

In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "pseudo-colocation (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)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission point (Transmission Point (TP))", "Reception point (Reception Point (RP))", "Transmission / reception point (Transmission / Reception Point (TRP))", "Panel" , "Cell", "sector", "cell group", "carrier", "component carrier" and the like can be used interchangeably. Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.

The base station can accommodate one or more (for example, 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 a base station subsystem (eg, a small indoor base station (Remote Radio)). Communication services can also be provided by Head (RRH))). The term "cell" or "sector" refers to part or all of the coverage area of at least one of the base stations and base station subsystems that provide communication services in this coverage.

In this disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" are used interchangeably. Can be done.

Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , 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 transmitting device, a receiving device, a wireless communication device, or the like. At least one of the base station and the mobile station may be a device mounted on the mobile body, the mobile body itself, or the like. The moving body may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving body (for example, a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned type). ) May be. It should be noted that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

In the present disclosure, the operation performed by the base station may be performed by its upper node (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 are performed by the base station and one or more network nodes other than the base station (for example,). Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. can be considered, but it is not limited to these), or it is clear that it can be performed by a combination thereof.

Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched with execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular 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.16 (WiMAX (registered trademark)), LTE 802. 20, Ultra-WideBand (UWB), Bluetooth®, other systems utilizing appropriate wireless communication methods, next-generation systems extended based on these, and the like may be applied. In addition, a plurality of systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

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

Any reference to elements using designations such as "first", "second", etc. as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted or that the first element must somehow precede the second element.

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

In addition, "judgment (decision)" includes receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access (for example). It may be regarded as "judgment (decision)" such as "accessing" (for example, accessing data in memory).

In addition, "judgment (decision)" is regarded as "judgment (decision)" of solving, selecting, selecting, establishing, comparing, and the like. May be good. That is, "judgment (decision)" may be regarded as "judgment (decision)" of some action.

In addition, "judgment (decision)" may be read as "assuming", "expecting", "considering", and the like.

The terms "connected", "coupled", or any variation thereof, as used herein, are any direct or indirect connection or connection between two or more elements. Means, and can include the presence of one or more intermediate elements between two elements that are "connected" or "joined" to each other. The connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access".

In the present disclosure, when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-comprehensive examples, the radio frequency domain, microwaves. It can be considered to be "connected" or "coupled" to each other using frequency, electromagnetic energy having wavelengths in the light (both visible and invisible) regions, and the like.

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

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

In the present disclosure, if articles are added by translation, for example, a, an and the in English, the disclosure may include that the nouns following these articles are in the plural.

Although the invention according to the present disclosure has been described in detail above, it is clear 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 an amended or modified mode without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for purposes of illustration and does not bring any limiting meaning to the invention according to the present disclosure.

Claims (6)

1. A receiver that receives the first downlink control information that schedules the first physical shared channel and the second downlink control information that schedules the second physical shared channel.
   It has a first downlink control information and a control unit that controls cross-carrier scheduling based on the second downlink control information.
   When the first physical shared channel and the second physical shared channel are transmitted in the same cell, the cell in which the first downlink control information and the second downlink control information are transmitted are set in common or separately. A terminal characterized by being played.
2. The terminal according to claim 1, wherein the first physical shared channel and the second physical shared channel are scheduled with different types of traffic or different types of downlink control information.
3. The terminal according to claim 1 or 2, wherein the first physical shared channel and the second physical shared channel have different transmission directions.
4. Claims 1 to claim 1, wherein the receiving unit receives information about a cell to which the first downlink control information is transmitted and a cell to which the second downlink control information is transmitted by higher layer signaling. The terminal according to any one of 3.
5. The cell to which the first downlink control information or the second downlink control information is transmitted is limited to the license band, or at least one of the license band and the unlicensed band is set by the upper layer signaling. The terminal according to any one of claims 1 to 4, which is characteristic.
6. The process of receiving the first downlink control information for scheduling the first physical shared channel and the second downlink control information for scheduling the second physical shared channel.
   It has a step of controlling cross-carrier scheduling based on the first downlink control information and the second downlink control information.
   When the first physical shared channel and the second physical shared channel are transmitted in the same cell, the cell in which the first downlink control information and the second downlink control information are transmitted are set in common or separately. A wireless communication method characterized by being performed.
   

Images