User terminal and wireless communication method

Abstract

In order to properly control the reception of downlink control information, a user terminal involved in one embodiment of the present invention is characterized in that it has: a receiving unit that receives one or more downlink control information with different purposes in a specific cell; and a control unit that stores the downlink control information so that the downlink control information for a specific purpose in the received downlink control information does not exceed a specific number.

Description

Technical Field

[0001] The present disclosure relates to a user terminal and a wireless communication method in a next generation mobile communication system. Background Art

[0002] In the UMTS (Universal Mobile Telecommunications System) network, Long Term Evolution (LTE) is standardized for the purpose of further high-speed data rate, low latency, etc. (Non-Patent Document 1). In addition, LTE-A (LTE-Advanced, LTE Rel. 10, 11, 12, 13) is standardized for the purpose of further increasing capacity and sophistication from LTE (LTE Rel. 8, 9).

[0003] Subsequent systems of LTE (for example, also called FRA (Future Radio Access), 5G (5th generation mobile communication system), 5G+ (5G plus), NR (New Radio), NX (New radio access), FX (Future generation radio access), LTE Rel.14 or 15 and later, etc.) are also being studied.

[0004] In the existing LTE system (e.g., LTE Rel.8-14), the user terminal (user equipment (UE: User Equipment)) controls the reception of the downlink shared channel (e.g., Physical Downlink Shared Channel (PDSCH)) based on the downlink control information (also called downlink control information (DCI: Downlink Control Information), DL allocation, etc.) transmitted via the downlink control channel (e.g., Physical Downlink Control Channel (PDCCH: Physical Downlink Control Channel)). In addition, the user terminal controls the transmission of the uplink shared channel (e.g., Physical Uplink Shared Channel (PUSCH: Physical Uplink Shared Channel)) based on the DCI (also called UL grant, etc.).

[0005] Prior art literature

[0006] Non-patent document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the invention

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (hereinafter referred to as NR), a study is being conducted on a UE storing (store) received DCI and controlling the transmission and reception of a physical shared channel scheduled by the DCI. For example, a study is being conducted on a UE storing (store) the DCI received until a specific time slot when the UE receives DCI at a specific timing (e.g., a specific time slot).

[0009] Since the load of the UE increases as the number of DCIs stored by the UE increases, it is considered to limit the number of DCIs to be stored. On the other hand, in NR, DCI is not only used for scheduling of physical shared channels, but also used for indication of other purposes (for example, activation or deactivation of specific signals, etc.). In this way, how to control the reception operation of DCI (for example, storage of DCI, etc.) when DCI is used for different purposes has not been fully studied.

[0010] The present disclosure has been made in view of the above problems, and one of its objects is to provide a user terminal and a wireless communication method that can appropriately control reception of downlink control information.

[0011] Means for solving problems

[0012] A user terminal involved in one embodiment of the present disclosure is characterized by comprising: a receiving unit for receiving one or more downlink control information with different purposes in a specific cell; and a control unit for storing so that the downlink control information for a specific purpose in the received downlink control information does not exceed a specific number.

[0013] Effects of the Invention

[0014] According to one aspect of the present disclosure, it is possible to appropriately control the reception of downlink control information. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a diagram for explaining the storage of DCI in UE.

[0016] Figure 2 This is a diagram showing an example of DCI storage control in the first embodiment.

[0017] Figure 3 This is a diagram showing another example of DCI storage control in the first embodiment.

[0018] Figure 4 This is a diagram showing another example of DCI storage control in the first embodiment.

[0019] Figure 5 This is a diagram showing an example of DCI storage control in the third aspect.

[0020] Figure 6 This is a diagram showing another example of DCI storage control in the third embodiment.

[0021] Figure 7 This is a diagram showing an example of DCI storage control in the fourth aspect.

[0022] Figure 8 This is a diagram showing an example of DCI storage control in the fifth aspect.

[0023] Fig. 9 This is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.

[0024] Fig.10 This is a diagram showing an example of the configuration of a base station according to an embodiment.

[0025] Fig.11 This is a diagram showing an example of a configuration of a user terminal according to an embodiment.

[0026] Fig.12 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION

[0027] In NR, the UE is studying to store the received DCI and control the transmission and reception of the physical shared channel (e.g., PDSCH or PUSCH) scheduled by the DCI. For example, when DCI is received in a specific time slot, the UE stores the DCI received until that time slot that is used to schedule the PDSCH that is not received or the PUSCH that is not transmitted (see Figure 1 ). In addition, in this specification, "storage" can also be replaced by "accumulation", "maintaining", "memory" or "saving".

[0028] exist Figure 1, it is shown that the UE stores DCI#3-#5 of the previously received DCI but has not received the corresponding PDSCH at the stage of time slot #5. Thus, even if the DCI and the PDSCH scheduled by the DCI are sent in different time slots, the UE can properly receive the PDSCH based on the DCI.

[0029] On the other hand, as the number of DCIs stored in the UE increases, the load of the UE's reception processing (e.g., baseband or RF processing, memory size for storage, etc.) becomes higher, so it is considered to limit the number of DCIs to be stored. Assuming that the number of DCIs to be stored on the UE side is not limited, there is a concern that the UE's load will increase due to the UE preparing for PDSCH reception or PUSCH transmission of the DCI that is continuously stored.

[0030] Therefore, it is considered to set the number of DCIs stored by the UE to be less than a specific value. The specific value may be set to, for example, 16, or may be set to other values.

[0031] In addition, in NR, it is assumed that downlink control information (DCI) is used for different purposes to control communications. For example, it is assumed that DCI is used for the following purposes. Of course, the purposes of applying DCI are not limited to the following.

[0032]

[0033] · DCI for broadcast PDSCH

[0034] DCI for unicast PDSCH

[0035] DCI used for activation of semi-persistently scheduled PDSCH (SPS PDSCH)

[0036] DCI for deactivation of the semi-persistently scheduled PDSCH (SPS PDSCH)

[0037]

[0038] DCI of the PUSCH (Msg3 PUSCH) message 3 used in the random access process

[0039] DCI for unicast PUSCH

[0040] DCI used for activation of PUSCH configured grant type 2 (PUSCH configured grant Type 2)

[0041] DCI for deactivation of PUSCH configured grant type 2 (PUSCH configured grant Type 2)

[0042] DCI used for activation of semi-persistent CSI (SP-CSI on PUSCH) using PUSCH

[0043] DCI used for deactivation of semi-persistent CSI (SP-CSI on PUSCH) using PUSCH

[0044] In this way, when DCI is used for different purposes, how to control the DCI reception operation (for example, storage of DCI, etc.) becomes a problem. If the DCI reception operation is not properly completed, there is a concern that the communication quality may be degraded.

[0045] The inventors of the present invention focused on the fact that UE receives DCI used for different purposes, and conceived of controlling the reception process of DCI (for example, limiting the number of DCIs to be stored, etc.) according to the type of DCI or regardless of the type of DCI.

[0046] Hereinafter, the present embodiment will be described in detail with reference to the accompanying drawings. Each of the following modes can be applied independently or in combination as appropriate.

[0047] (First method)

[0048] In the first mode, the storage quantity in the UE is limited for DCI of a specific purpose among DCIs used for receiving a DL signal or channel. In addition, in the following description, "storage quantity" may also be replaced by "accumulation quantity", "retention quantity", "memory quantity", "save quantity", or "reception quantity".

[0049] In the following description, the following DCI types are described as DCI used for reception of a DL signal or channel, but the DCI types applicable to the present embodiment are not limited thereto.

[0050] DCI used for broadcast PDSCH (e.g., scheduling PDSCH)

[0051] DCI used for unicast PDSCH (e.g., scheduling PDSCH)

[0052] DCI for activation of PDSCH for SPS

[0053] DCI for deactivation of SPS PDSCH (SPS PDSCH) (or release of SPS)

[0054] The broadcast PDSCH may also be a PDSCH scheduled by a DCI scrambled by a CRC using a specific RNTI (eg, at least one of SI-RNTI, P-RNTI, RA-RNTI, and TC-RNTI).

[0055] The unicast PDSCH may be a PDSCH scheduled by a DCI scrambled by a CRC using a specific RNTI (for example, at least one of a C-RNTI and an MCS-C-RNTI).

[0056] The DCI used for activation or deactivation of the PDSCH of the SPS may be a DCI scrambled by the CRC using a specific RNTI (for example, CS-RNTI).

[0057] The UE performs reception processing so that the number of DCIs stored for a specific purpose becomes less than a specific value. For example, the UE is not required to store a number of DCIs greater than a specific value (e.g., X1). In this case, the UE may also perform reception processing by assuming that a maximum of X1 DCIs are stored in a specific timing (or any timing) of a certain serving cell, or the total number of DCIs stored for a specific purpose becomes less than X1.

[0058] Alternatively, the UE may also be assumed to not receive more than X1 PDCCHs used in the transmission of at least one of the DCI for scheduling a specific channel and the DCI for indicating activation / deactivation of a specific channel at a specific timing. In addition, X1 may be a value pre-set by the specification, or a value set from the base station to the UE using high-layer signaling, etc.

[0059] In the case of receiving a PDSCH scheduled by DCI, the UE may also discard the DCI corresponding to the received PDSCH. In addition, in the case of activating a PDSCH indicated by DCI, the UE may also discard the DCI corresponding to the activated SPS PDSCH. Similarly, in the case of deactivating a PDSCH indicated by DCI, the UE may also discard the DCI corresponding to the deactivated SPS PDSCH.

[0060] In addition, when the number of stored DCIs becomes greater than X1, the UE may also discard specific DCIs in the stored DCIs. The discarded DCI may also be the DCI with the earliest reception timing. Alternatively, priorities may be set for the uses of the DCIs, and when the number of stored DCIs becomes greater than X1, DCIs with lower priorities may be discarded. When the DCI is discarded before performing control based on a specific DCI, the UE may not receive the broadcast PDSCH, receive the unicast PDSCH, activate the SPS PDSCH, or deactivate the SPS PDSCH indicated by the discarded DCI.

[0061] In addition, when the DCI is discarded, the HARQ-ACK bit may be set to NACK based on the DCI and sent. Alternatively, when the DCI indicating the activation of the SPS PDSCH or the deactivation of the SPS PDSCH is discarded, the SPS PDSCH may be activated or the SPS PDSCH may be deactivated at the timing of the discard (e.g., time slot or symbol).

[0062] The DCI for a specific purpose with a limited storage quantity in the UE may also apply any of the following structures 1-1 to 1-3. In each of the following structures, the storage quantity of DCI received in a specific time slot of a cell (for example, the current time slot in which the UE performs reception) up to the specific time slot is described.

[0063] In addition, it is assumed that the DCI stored by the UE is a DCI in the received DCI for which an operation associated with the DCI (e.g., reception, activation, or deactivation of PDSCH) has not been performed, but it is not limited to this. In addition, the DCI shown in the following structures 1-1 to 1-3 may also be a specific DCI format (e.g., at least one of DCI format 1_0 and DCI format 1_1).

[0064] <Structure 1-1>

[0065] The DCI for a specific purpose may include DCI used for scheduling the PDSCH, DCI used for activating the PDSCH, and DCI used for deactivating the PDSCH.

[0066] For example, the UE may schedule a PDSCH for unicast (eg, Figure 2 DCI #5), DCI used for scheduling of broadcast PDSCH (for example, Figure 2 DCI#4), DCI for activating the PDSCH used for SPS, and DCI for deactivating the PDSCH used for SPS (for example, Figure 2 DCI#3) is controlled so that the storage quantity (the total storage quantity of DCIs with different purposes) does not exceed a specific value (for example, X1).

[0067] As a result, since the number of DCIs held in the memory can be set to a specific value or less, an increase in the load on the UE due to preparation for PDSCH reception and the like can be suppressed.

[0068] <Structure 1-2>

[0069] The DCI for a specific purpose may include DCI used for scheduling the PDSCH and DCI used for activating the PDSCH. On the other hand, the DCI used for deactivating the PDSCH may be configured such that the storage quantity is not limited (or not included in the storage quantity).

[0070] For example, the UE may schedule a PDSCH for unicast (eg, Figure 3 DCI #5), DCI used for scheduling of broadcast PDSCH (for example, Figure 3 DCI#4) and the DCI used for activation of the PDSCH of SPS are controlled so that the storage quantity does not exceed a specific value (e.g., X1).

[0071] When receiving a DCI indicating deactivation of the PDSCH for SPS, the UE does not need to perform a PDSCH reception operation (e.g., PDSCH reception preparation). Therefore, even if the DCI for deactivation of the PDSCH used for SPS is not counted in the storage quantity, the impact on the UE load can be reduced. In addition, by setting a structure in which the DCI for deactivation of the PDSCH used for SPS is not counted in the storage quantity, the storage quantity of other DCIs can be ensured.

[0072] <Structure 1-3>

[0073] The DCI for a specific purpose may also be a DCI for scheduling or activating a PDSCH that indicates the need for a delivery confirmation signal (also called HARQ-ACK, A / N or ACK / NACK) corresponding to the PDSCH. For example, as a DCI for a specific purpose, it may also include a DCI for scheduling a PDSCH used for unicast and a DCI for activating or deactivating the PDSCH. On the other hand, the DCI for scheduling a PDSCH used for broadcasting may also be set to a structure in which the storage quantity is not limited (or not counted in the storage quantity).

[0074] For example, the UE may schedule a PDSCH for unicast (eg, Figure 4 DCI#5) used for activation of PDSCH of SPS and deactivation of PDSCH of SPS are controlled so that the storage quantity does not exceed a specific value (for example, X1).

[0075] When receiving the DCI of the PDSCH for scheduling broadcast, the UE does not need to perform the HARQ-ACK transmission operation (e.g., HARQ-ACK operation) corresponding to the PDSCH. Therefore, even if the DCI of the PDSCH for scheduling broadcast is not counted in the storage quantity, the impact on the UE load can be reduced to a certain extent.

[0076] Furthermore, by adopting a configuration in which at least one of the DCI for scheduling broadcast PDSCH and the DCI for deactivating PDSCH used for SPS is not counted in the storage quantity, it is possible to ensure the storage quantity of the other DCI.

[0077] <Modification>

[0078] In addition, in the above-mentioned structures 1-1 to 1-3, a structure is set to aggregate DCIs for different purposes and limit the storage quantity, but it is not limited to this. It can also be set to a structure in which the upper limit of the storage quantity is separately limited according to the DCI for different purposes. For example, the storage quantity of DCI used for scheduling PDSCH used for unicast and the storage quantity of DCI used for scheduling PDSCH used for broadcast can be set to less than Y1, and the storage quantity of DCI used for activating PDSCH used for SPS and the storage quantity of DCI used for deactivating PDSCH used for SPS can be set to less than Y2. In this way, the storage quantity of DCI can be flexibly controlled according to the purpose of DCI.

[0079] (Second method)

[0080] In the second aspect, the amount of DCI used for receiving a UL signal or channel and stored in the UE is limited for DCI for a specific purpose.

[0081] In the following description, the following DCI types are described as DCI used for reception of a UL signal or channel, but the DCI types applicable to the present embodiment are not limited thereto.

[0082] · PUSCH DCI of message 3 used in random access procedure

[0083] · DCI for PUSCH in unicast

[0084] DCI used to configure the activation of PUSCH of grant type 2

[0085] · Used to configure the DCI for deactivation of the PUSCH of grant type 2

[0086] DCI used for activation of SP-CSI using PUSCH

[0087] DCI used for deactivation of SP-CSI using PUSCH

[0088] The PUSCH of message 3 may also be a PUSCH scheduled by a DCI scrambled by a CRC using a specific RNTI (eg, TC-RNTI).

[0089] The unicast PUSCH may also be a PUSCH scheduled by a DCI scrambled by a CRC using a specific RNTI (for example, at least one of a C-RNTI and an MCS-C-RNTI).

[0090] The DCI used to set activation or deactivation of the PUSCH of grant type 2 may be a DCI scrambled by CRC using a specific RNTI (eg, CS-RNTI).

[0091] The DCI used for activation or deactivation of SP-CSI using PUSCH may be DCI scrambled by CRC using a specific RNTI (eg, SP-CSI-RNTI).

[0092] The UE performs reception processing so that the number of DCIs stored for a specific purpose becomes less than a specific value. For example, the UE is not required to store a number of DCIs greater than a specific value (e.g., X2). In this case, the UE may also perform reception processing by assuming that a maximum of X2 DCIs are stored in a specific timing (or any timing) of a certain serving cell, or the total number of DCIs stored for a specific purpose becomes less than X2.

[0093] Alternatively, the UE may also assume that, at a specific timing, it does not receive more than X2 PDCCHs used in the transmission of at least one of the DCIs for scheduling a specific channel and the DCIs for indicating activation / deactivation of a specific channel / signal. In addition, X2 may be a value pre-set by the specification, or a value set from the base station to the UE using high-layer signaling, etc. In addition, X2 may be set to the same value as X1 shown in the first embodiment, or X1 and X2 may be set separately.

[0094] In the case of sending a PUSCH scheduled by DCI, the UE may also discard the DCI corresponding to the sent PUSCH. In addition, in the case of activating a PUSCH or SP-CSI indicated by DCI, the UE may also discard the DCI corresponding to the activated PUSCH or SP-CSI. Similarly, in the case of deactivating a PUSCH or SP-CSI indicated by DCI, the UE may also discard the DCI corresponding to the deactivated PUSCH or SP-CSI.

[0095] In the case where the DCI is discarded before performing control based on a specific DCI, the UE may not perform PUSCH transmission of message 3 in the random access process indicated by the discarded DCI, unicast PUSCH transmission, activation of PUSCH with grant type 2, deactivation of PUSCH with grant type 2, activation of SP-CSI using PUSCH, or deactivation of SP-CSI using PUSCH in the random access process indicated by the discarded DCI. Regarding setting type 2, in the case where the DCI used to indicate activation or deactivation is discarded, a PUSCH that reports a configured grant confirmation in a specific LCID (Logical Channel Identifier) ​​of the MAC PDU sub-header based on the DCI may also be sent.

[0096] Alternatively, in the case where the DCI indicating the activation or deactivation of setting type 2 or SP-CSI is discarded, the activation or deactivation of setting type 2 or SP-CSI may be performed at the timing of the discard (e.g., time slot or codeword).

[0097] In addition, when the number of stored DCIs becomes greater than X2, the UE may also discard specific DCIs in the stored DCIs. The discarded DCI may also be the DCI with the earliest reception timing. Alternatively, priorities may be set for the uses of the DCIs, and when the number of stored DCIs becomes greater than X2, the DCIs with lower priorities may be discarded.

[0098] DCI for specific purposes that limits the storage quantity in the UE can also apply any of the following structures 2-1 to 2-3. In addition, in each of the following structures, the storage quantity of DCI received in a specific time slot of a cell (for example, the current time slot in which the UE performs reception) until the specific time slot is described. In addition, it is assumed that the DCI stored by the UE is the DCI in the received DCI in which the operation associated with the DCI (for example, transmission, activation or deactivation of PUSCH) has not been performed, but it is not limited to this.

[0099] <Structure 2-1>

[0100] The DCI for specific purposes may include DCI used for scheduling of PUSCH, DCI used for activating / deactivating PUSCH for setting grant type 2, and DCI used for activating / deactivating SP-CSI using PUSCH.

[0101] For example, the UE controls the DCI used for PUSCH used for unicast, the DCI used for PUSCH used for message 3, the DCI used for activation of PUSCH for setting license type 2, the DCI used for deactivation of PUSCH for setting license type 2, the DCI used for activation of SP-CSI utilizing PUSCH, and the DCI used for deactivation of SP-CSI utilizing PUSCH so that the storage quantity (the total storage quantity of DCIs for different purposes) does not exceed a specific value (for example, X2).

[0102] As a result, since the number of DCIs held in the memory can be set to a specific value or less, an increase in the load on the UE due to preparation for PUSCH transmission and the like can be suppressed.

[0103] <Structure 2-2>

[0104] DCI for specific purposes may also include DCI used for scheduling of PUSCH, DCI used for activating PUSCH for setting grant type 2, and DCI used for activating SP-CSI using PUSCH. On the other hand, at least one of DCI used for deactivating PUSCH for setting grant type 2 and DCI used for deactivating SP-CSI using PUSCH may also be set to a structure in which the storage quantity is not limited (or not counted in the storage quantity).

[0105] For example, the UE controls the DCI used for PUSCH used for unicast, the DCI used for PUSCH used for message 3, the DCI used for activation of PUSCH for setting permission type 2, and the DCI used for activation of SP-CSI utilizing PUSCH so that the storage quantity does not exceed a specific value (e.g., X2).

[0106] Upon receiving at least one of the DCI for indicating the deactivation of the PUSCH for setting the grant type 2 or the DCI for indicating the deactivation of the SP-CSI using the PUSCH, the UE does not need to perform a PUSCH transmission operation (e.g., PUSCH transmission preparation). Therefore, even if a structure is set such that at least one of the DCI for indicating the deactivation of the PUSCH for setting the grant type 2 and the DCI for indicating the deactivation of the SP-CSI using the PUSCH is not counted in the storage quantity, the impact on the UE load can be reduced. In addition, by setting a structure such that the DCI used for deactivation is not counted in the storage quantity, the storage quantity of other DCIs can be ensured.

[0107] <Structure 2-3>

[0108] DCI for specific purposes may also include DCI for scheduling PUSCH used for unicast and DCI for activating PUSCH used to set license type 2. On the other hand, at least one of DCI for scheduling PUSCH used for message 3, DCI for deactivating PUSCH used to set license type 2, DCI for activating SP-CSI using PUSCH, and DCI for deactivating SP-CSI using PUSCH may also be set to a structure in which the storage quantity is not limited (or not counted in the storage quantity).

[0109] For example, the UE controls the DCI used for the unicast PUSCH and the DCI used for setting activation of the PUSCH of grant type 2 so that the storage quantity does not exceed a specific value (for example, X2).

[0110] When receiving DCI for scheduling of PUSCH used in message 3, DCI for indicating deactivation of PUSCH for setting grant type 2, or DCI for indicating activation / deactivation of SP-CSI using PUSCH, the UE does not need to send unicast data other than control information of the upper layer or physical layer. Therefore, even if at least one of these DCIs is not counted in the storage quantity, the impact on the UE load can be reduced. In addition, by setting a structure in which these DCIs are not counted in the storage quantity, the storage quantity of other DCIs can be ensured.

[0111] <Modification>

[0112] In addition, in the above-mentioned structures 2-1 to 2-3, a structure is set to aggregate DCIs for different purposes and limit the storage quantity, but it is not limited to this. It can also be set to a structure in which the upper limit of the storage quantity is separately limited according to the DCI with different purposes. For example, the storage quantity of DCI used for scheduling of unicast PUSCH and DCI used for scheduling of PUSCH of message 3 can be set to less than Y1, and the storage quantity of DCI used for activation / deactivation of PUSCH for setting permission type 2 and DCI used for activation / deactivation of SP-CSI using PUSCH can be set to less than Y2. In this way, the storage quantity of DCI can be flexibly controlled according to the purpose of DCI.

[0113] (Third Method)

[0114] In the third example, the number of stored DCI formats different from the DCI format used for scheduling of the physical shared channel will be described.

[0115] The DCI format used for scheduling the physical shared channel may be, for example, any one of DCI formats 0_0, 0_1, 1_0, and 1_1. A DCI format different from the DCI format used for scheduling the physical shared channel may be, for example, a DCI format 2 series (at least one of DCI formats 2_0, 2_1, 2_2, and 2_3).

[0116] DCI format 2_0 can also be used to notify the time slot format. DCI format 2_1 can also be used to notify resource blocks (PRBs) and symbols (OFDM symbols) that are not transmitted. DCI format 2_2 can also be used to transmit power control commands (TPC commands) for PUCCH and PUSCH. DCI format 2_3 can also be used to transmit group TPC commands for SRS transmission.

[0117] <Option 1>

[0118] The DCI format 2 series can also be set to a structure in which the storage quantity in the UE is not limited (or not counted in the storage quantity). When receiving the DCI format 2 series, the UE does not need to perform a PDSCH reception operation or a PUSCH transmission operation. Therefore, even if the structure is set to not count the DCI format 2 series in the storage quantity, the impact on the UE load can be reduced.

[0119] <Option 2>

[0120] The DCI format 2 series may also be configured such that the storage quantity in the UE is limited (or counted in the storage quantity). For example, when the UE receives DCI corresponding to the DCI format 2 series, it may be counted in the storage quantity as DCI in the DL.

[0121] DCI format 2 series DCI can also be combined with DCI for other purposes to limit the storage quantity. In a specific time slot of a cell (for example, the current time slot in which the UE is receiving), the UE can also control so that the storage quantity of DCI received until the specific time slot does not exceed a specific value (for example, X1). For example, the UE can also be considered as a DCI for scheduling PDSCH (at least one of unicast PDSCH and broadcast PDSCH) (for example, Figure 5 DCI #4, #5), and DCI format 2 series DCI (for example, Figure 5 The storage quantity of DCI#3) does not exceed a specific value, and reception processing is performed.

[0122] Furthermore, in any of the configurations 1-1 to 1-3 of the first embodiment, DCI of the DCI format 2 series may be included in the DCI for a specific purpose (DCI counted in the number of storage).

[0123] <Option 3>

[0124] The DCI format 2 series may also be configured such that the number of stored data in the UE is limited (or counted in the number of stored data). For example, when the UE receives DCI corresponding to the DCI format 2 series, the DCI may be counted in the number of stored data as DCI in the DL.

[0125] The number of DCIs in the DCI format 2 series can also be limited independently from the number of DCIs for other purposes. For example, an upper limit value (e.g., X3) can be set for the number of DCIs in the DCI format 2 series to be stored. In this case, in a specific time slot of a cell (e.g., the current time slot in which the UE is receiving), the UE can also control so that the DCIs in the DCI format 2 series (e.g., Figure 6 The storage quantity of DCI#3) does not exceed a specific value (for example, X3) (refer to Figure 6 ).

[0126] X3 may be a value preset in the specification or a value set from the base station to the UE using higher layer signaling, etc. In addition, X3 may be set to the same value as X1 shown in the first embodiment, or X1 and X3 may be set separately (for example, X1 ≥ X3).

[0127] In this way, by setting the storage quantity of DCI of the DCI format 2 series separately from DCI for other purposes, the storage quantity can be flexibly set according to the purpose of DCI.

[0128] (Fourth Method)

[0129] In the fourth aspect, the number of DCIs stored for each cell when communicating using multiple cells (for example, applying carrier aggregation) is described. In the following description, the cell may be replaced by a CC. In addition, the cell may be replaced by a broadband part (BWP) set in the cell.

[0130] The UE may also determine the number of DCIs to be stored based on the number of cells. The cell may also be the number of cells (CA application cells) set from the base station to the UE, or the number of activated cells in the set cells. The UE may also control so that the number of DCIs to be stored does not exceed a specific value for each cell. As for the upper limit value of the number of DCIs to be stored (e.g., the limit number), different values ​​may be set separately for each cell, or the same value may be set for each cell.

[0131] <Option 1>

[0132] The upper limit of the number of DL or UL DCIs to be stored in the UE may also increase (eg, scale up linearly) according to the number of cells.

[0133] For example, suppose that each cell performs self-scheduling. In self-scheduling, the PDSCH or PUSCH of a specific cell is scheduled by DCI transmitted in the specific cell. In this case, an upper limit value of the number of DCIs to be stored is set in each cell.

[0134] For example, an upper limit value (for example, X1) of the number of DCIs to be stored in each cell may be set in common. The DCI counted as the number of DCIs to be stored may be applied to any of the first to third aspects described above.

[0135] Next, assume that cross-carrier scheduling is set. When cross-carrier scheduling is set, a DCI for indicating the scheduling of the PDSCH in the second cell #2 is sent in the first cell #1. The first cell may also be referred to as a scheduling cell or a scheduling cell, and the second cell may also be referred to as a scheduled cell or a scheduled cell.

[0136] In cross-carrier scheduling, the upper limit of the number of DCIs stored in the scheduling cell may also be determined based on the number of scheduled cells that are controlled and scheduled by the scheduling cell. Figure 7 The number of cells scheduled by the cell #1) is M (in Figure 7 In the case where there are 2 DCIs in total, namely, cell #1 and cell #2, the upper limit of the number of DCIs to be stored in the scheduled cell may be determined based on M (for example, X1×M).

[0137] In this case, the upper limit value of the number of DCIs stored in the scheduled cell may not be set. Alternatively, the upper limit value of the number of DCIs stored in the scheduled cell may be ignored by the UE.

[0138] In this way, by setting the upper limit value of the number of DCIs to be stored in a plurality of specific cells (eg, scheduling cells), it is possible to appropriately control the storage of DCI even when cross-carrier scheduling is set.

[0139] <Option 2>

[0140] An upper limit value of the number of DCIs to be stored in the DL or UL of the UE may be set according to the number of cells and the UE capability.

[0141] For example, until the number of cells that are set (or activated) reaches a specific number, the upper limit of the number of DCIs to be stored is increased according to the number of cells (for example, linearly increased) in the same manner as option 1. When the number of cells that are set becomes greater than a specific number (for example, 4), the upper limit of the number of DCIs to be stored is determined based on the UE capability. The UE capability may also be a capability related to blind decoding of PDCCH in CA (for example, pdcch-BlindDetectionCA).

[0142] The capability information related to blind decoding of PDCCH in CA is information related to the number of blind decoding of PDCCH in CA (or the number of PDCCH candidates or the number of CCEs that the UE can monitor), and can also be reported from the UE to the base station. In CA, the UE can also determine the upper limit of the number of DCIs that can be stored based on the capability related to blind decoding of PDCCH.

[0143] For example, suppose that self-scheduling is performed in each cell. In self-scheduling, the scheduling of PDSCH or PUSCH of a specific cell is performed through DCI transmitted in the specific cell. In this case, the upper limit of the number of DCIs to be stored may be set in each cell. In addition, option 1 may also be applied when the number of cells to be set is less than a specific number.

[0144] For example, an upper limit value (for example, X1×y / N) for the number of DCIs stored in each cell may also be set publicly. X1 may also be an upper limit value for the number of DCIs that can be stored in a cell when CA is not applied. y may also be a value determined based on a specific UE capability (for example, pdcch-BlindDetectionCA). N may also be the number of cells that are set. In addition, a different upper limit value for the number of storages may be set for each cell. The DCI counted as the number of storages may also apply any of the first method to the third method described above.

[0145] Next, let us assume that cross-carrier scheduling is set. In cross-carrier scheduling, the upper limit of the number of DCIs to be stored in the scheduling cell may be determined based on the number of scheduled cells whose scheduling is controlled by the scheduling cell.

[0146] For example, when the number of cells scheduled by a certain scheduling cell is M, the upper limit of the number of DCIs to be stored in the scheduling cell may be determined based on M and a value (y) corresponding to a specific UE capability (for example, X1×M×y / N).

[0147] In this case, the upper limit value of the number of DCIs stored in the scheduled cell may not be set. Alternatively, the upper limit value of the number of DCIs stored in the scheduled cell may be ignored by the UE.

[0148] In this way, by setting the upper limit value of the number of DCIs to be stored in a plurality of specific cells (eg, scheduling cells), it is possible to appropriately control the storage of DCI even when cross-carrier scheduling is set.

[0149] In addition, in the case of CA between cells (or between BWPs) with different subcarrier spacings, the upper limit of the storage quantity of DCI per cell can be determined by using the ratio of the number of cells with the subcarrier spacing set to the number of all cells with CA set, and further, the determined storage upper limit is allocated to the one or more cells with the subcarrier spacings set, thereby determining the storage upper limit in each cell.

[0150] (Fifth Method)

[0151] In the fifth example, a case where the UE controls the number of DCIs that can be stored according to the type of communication service will be described.

[0152] In NR, use cases such as further advancement of mobile broadband (Enhanced Mobile Broadband (eMBB)), enabling multiple simultaneous connections for machine-type communications (Massive Machine Type Communications (mMTC)), and Ultra-Reliable and Low-Latency Communications (URLLC) are envisioned. For example, in URLLC, lower latency and higher reliability than eMBB are required.

[0153] For example, the difference between the requirements of URLLC and those of eMBB can be that the latency of URLLC is less than that of eMBB, or that the requirements of URLLC include requirements for reliability. For example, the requirements for the user plane latency of eMBB can also include that the user plane latency of the downlink is 4 ms and the user plane latency of the uplink is 4 ms. On the other hand, the requirements for the user plane latency of URLLC can also include that the user plane latency of the downlink is 0.5 ms and the user plane latency of the uplink is 0.5 ms. In addition, the requirements for the reliability of URLLC can also include that in a user plane latency of 1 ms, the error rate for 32 bytes is 10 -5 .

[0154] Thus, the requirements are different between URLLC and eMBB. Therefore, in the fifth mode, the operations in the case where a UE stores the DCI for the first communication service with different requirements (for example, URLLC) and the DCI for the second communication service (for example, eMBB) are described. In the following description, URLLC and eMBB are used as examples, but the applicable communication services (for example, communication services with different requirements) are not limited to these.

[0155] The DCI used for URLLC and the DCI used for eMBB can also be distinguished based on at least one of the set parameters, the applied RNTI, and the conditions specified by the DCI (such as a table, etc.).

[0156] <DCI for URLLC>

[0157] For example, the DCI used for URLLC can also be the DCI that is CRC scrambled by the first RNTI (for example, MCS-C-RSNT).

[0158] Alternatively, the DCI used for URLLC may also be, for example, a new Modulation and Coding Scheme (MCS) table and a new CQI (Channel Quality Indicator) table that can specify a spectral efficiency m less than a specific value (e.g., 0.2 or 0.18) or an R value less than a specific value (e.g., 120 or 100) (where the target coding rate is set to Rx

[1024] ), or at least one of the DCIs in the table.

[0159] The new MCS table may also be referred to as MCS table 3, the new MCS table, or qam64LowSE. MCS table 3 may also be a table that specifies a coding rate lower than the minimum coding rate specified by other MCS tables (e.g., MCS table 1 and MCS table 2, which may also be referred to). Alternatively, MCS table 3 may be a table that sets the coding rate in the same MCS index lower when compared with MCS table 1 or MCS table 2.

[0160] Alternatively, the DCI used for URLLC may also be a DCI that applies a first transmission condition (or transmission parameter) to at least one of the DCI and the corresponding physical shared channel. For example, when the number of symbols used for transmission in at least one of the DCI and the physical shared channel scheduled by the DCI becomes less than a specific value, it can be assumed that this DCI is for URLLC.

[0161] Alternatively, the DCI used for URLLC may also be a DCI that is set according to a range or transmission condition preset by a higher layer signaling (e.g., RRC signaling or broadcast signal, etc.) from the base station.

[0162] <DCI for eMBB>

[0163] For example, the DCI used for eMBB may also be a DCI that is CRC scrambled by a second RNTI (e.g., an RNTI other than MCS-C-RNTI, such as C-RNTI, etc.).

[0164] Alternatively, the DCI used for eMBB may be, for example, a table capable of setting modulation based on 256QAM, or may be a DCI for specifying at least one of a modulation and coding scheme (MCS) table and a CQI (Channel Quality Indicator) table that cannot specify a frequency utilization efficiency (Spectralefficiency) m that is less than a specific value (e.g., 0.2 or 0.18) or a value of R that is less than a specific value (e.g., 120 or 100) (here, the target coding rate is assumed to be Rx

[1024] ).

[0165] It can also be a table that can set modulation based on 256QAM. The MCS table that cannot specify a frequency utilization efficiency (Spectral efficiency) m that is less than a specific value (for example, 0.2 or 0.18) or a value of R that is less than a specific value (for example, 120 or 100) (here, the target coding rate is assumed to be Rx

[1024] ) can also be called MCS table 1 or 2.

[0166] Alternatively, the DCI used for eMBB may be a DCI in which a second transmission condition (or transmission parameter) is applied to at least one of the DCI and the corresponding physical shared channel. For example, when the number of symbols used for transmission of at least one of the DCI and the physical shared channel scheduled by the DCI becomes greater than a specific value, it may be assumed that the DCI is a DCI for eMBB.

[0167] Alternatively, the DCI used for eMBB may be DCI that is set according to a range or a transmission condition that is set in advance by a base station through higher-layer signaling (for example, RRC signaling or a broadcast signal, etc.).

[0168] <When using URLLC only>

[0169] When the UE communicates only using URLLC, an upper limit value (or limit value) of the storage quantity in the UE may be set for the DCI used for URLLC.

[0170] For example, the UE performs reception processing so that the storage quantity of DCI for URLLC is less than a specific value. The specific value may also be any one of 16, 32 or 64, or another value. The upper limit value may also be reported by the UE as terminal capability information (UE capability). In addition, as the type (or purpose) of DCI counted as the storage quantity by the UE, the structures shown in the first method to the third method may also be applied in combination as appropriate. In addition, when CA is applied, the structures shown in the fourth method may also be applied in combination as appropriate.

[0171] The network (eg, base station) may also control scheduling so as not to exceed the upper limit of the number of DCIs stored in the UE. In this case, the UE may also perform reception processing assuming that the DCI will not be sent and exceeds the upper limit of the number of DCIs stored.

[0172] Alternatively, for the DCI for URLLC, a structure in which an upper limit value (or a limit value) of the storage quantity in the UE is not set can also be set. Generally, it can be considered that the indication based on the DCI for URLLC (for example, at least one of scheduling and activation / deactivation) is specified in a short period of time compared with eMBB, etc. Therefore, even if the upper limit value of the storage quantity of the DCI for URLLC is not set, the increase in the processing load in the UE can be suppressed compared with other communication services.

[0173] <Using URLLC and eMBB>

[0174] In the case where the UE uses URLLC and eMBB for communication, the upper limit value of the storage number of DCI for URLLC and the upper limit value of the storage number of DCI for eMBB may also be set separately. In this case, the upper limit value of the storage number of DCI for URLLC and the upper limit value of the storage number of DCI for eMBB may also be set separately. In addition, an upper limit value may be set for the total storage number of DCI for URLLC and the storage number of DCI for eMBB.

[0175] [Option 1]

[0176] Consider a situation where an upper limit value (e.g., z) for the DCI storage quantity is set for the total of URLLC and eMBB traffic (e.g., the total of the storage quantity allowed by DCI for URLLC (e.g., x1) and the storage quantity allowed by DCI for eMBB (e.g., y1)).

[0177] The network (eg, base station) may also control scheduling so as not to exceed the upper limit of the number of storages in the UE (see Figure 8 ).exist Figure 8 In the example, the total of DCI#3 and #4 for eMBB and DCI#5 for URLLC accumulated in a specific time slot (for example, time slot #5) is controlled to be less than z.

[0178] When the upper limit of the number of DCIs stored in the UE is exceeded by scheduling (for example, DCI transmission in a certain time slot), the UE may also control not to perform reception or transmission processing of the DCI and the physical shared channel scheduled by the DCI. That is, when the upper limit of the number of DCIs stored is exceeded, the UE may also skip the reception or transmission processing of the transmitted DCI and the physical shared channel scheduled by the DCI.

[0179] Alternatively, the UE may perform control to drop or discard specific DCI among the stored DCIs based on at least one of the type of communication service corresponding to the DCI and the purpose of the DCI.

[0180] For example, it is assumed that the scheduling of URLLC traffic (for example, DCI transmission for URLLC in a certain time slot) exceeds the upper limit of the storage quantity of DCI in the UE. In this case, the UE may also control the scheduled URLLC traffic (DCI for URLLC and physical shared channels scheduled by the DCI, etc.) so as not to skip the operation and receive the DCI for storage.

[0181] On the other hand, control may be performed so that any DCI (or PDCCH) scheduled for eMBB is discarded. The discarded DCI (or PDCCH) for eMBB may be the earliest received DCI for eMBB or the latest received DCI for eMBB. Alternatively, the discarded DCI (or PDCCH) for eMBB may be the DCI with the largest size (e.g., transport block size (TBS)) among the stored DCIs for eMBB.

[0182] In this way, when the storage quantity of DCI in the UE exceeds the upper limit value, the DCI for URLLC is received and processed (for example, stored) with priority, thereby suppressing the delay of URLLC requiring low delay and suppressing the degradation of communication quality.

[0183] [Option 2]

[0184] For the traffic volume of URLLC and eMBB, the total number of DCIs stored in the UE may also be considered to set the upper limit of the number of DCIs stored for URLLC and the upper limit of the number of DCIs stored for eMBB. In this case, the upper limit of the number of DCIs stored may also be set so that the upper limit of the number of DCIs stored for URLLC and the upper limit of the number of DCIs stored for eMBB meet a specific ratio.

[0185] For example, when a specific ratio is set for the upper limit of the storage quantity of DCI for URLLC and the upper limit of the storage quantity of DCI for eMBB, information related to the ratio may be notified from the base station to the UE using high-layer signaling or the like. For example, when the upper limit of the total storage quantity of DCI in the UE is represented by z, the storage quantity (upper limit of the storage quantity) allowed for DCI for URLLC is represented by x1, and the storage quantity allowed for DCI for eMBB is represented by y1, the storage quantity of each DCI is set so that R eMBB (y1 / z)+R URLLC (x1 / z)≤1. Information on at least one of z, x1, and y1 may be notified from the base station to the UE.

[0186] For example, the storage quantity may be set using the same mechanism as the power control operation in dual connection (DC) (setting mechanism for power allocation to MCG and SCG).

[0187] It is also possible to set the total number of stored URLLC DCI and eMBB DCI to not reach the upper limit value z. In this case, the remaining storage quantity (1-R eMBB (y1 / z)-R URLLC (x1 / z)) can also be preferentially allocated to URLLC traffic (for example, DCI for URLLC). That is, a minimum storage quantity (also referred to as a guaranteed storage quantity) is set for DCI for URLLC and DCI for eMBB, and for the portion exceeding the guaranteed storage quantity, the upper limit of the DCI storage quantity can also be considered to control the allocation.

[0188] Alternatively, the storage quantity allowed for each DCI may be set so that the sum of the storage quantity x1 allowed for the URLLC DCI and the storage quantity y1 allowed for the eMBB DCI exceeds the upper limit z of the storage quantity of the DCI in the UE (for example, R eMBB (y1 / z)+R URLLC (x1 / z)>1). In this case, when the number of DCIs to be stored in the UE exceeds the upper limit, the stored DCIs may be discarded to prioritize URLLC traffic (e.g., DCI for URLLC).

[0189] In this way, by setting the storage quantity x1 allowed for DCI for URLLC and the storage quantity y1 allowed for DCI for eMBB for the UE, the storage quantity of each DCI can be flexibly controlled.

[0190] (Wireless Communication System)

[0191] Hereinafter, a configuration of a wireless communication system according to an embodiment of the present disclosure will be described. In the wireless communication system, communication is performed using any one of the wireless communication methods according to the above-mentioned embodiments of the present disclosure or a combination thereof.

[0192] Fig. 9 1 is a diagram showing an example of a schematic structure of a wireless communication system involved in one embodiment. The wireless communication system 1 may also be a system that implements communication using LTE (Long Term Evolution) standardized by 3GPP (Third Generation Partnership Project), 5G NR (5th generation mobile communication system New Radio), etc.

[0193] In addition, the wireless communication system 1 can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple RATs (Radio Access Technology). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

[0195] The wireless communication system 1 can also support dual connections between multiple base stations within the same RAT (for example, dual connections (NR-NR dual connection (NN-DC: NR-NR Dual Connectivity)) where both MN and SN are NR base stations (gNB)).

[0196] The wireless communication system 1 may also include a base station 11 that forms a macro cell C1 with 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. The user terminal 20 may also be located in at least one cell. The arrangement and number of each cell and the user terminal 20 are not limited to the illustrated method. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.

[0197] 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) using a plurality of component carriers (CCs) and dual connectivity (DC).

[0198] Each CC may also be included in at least one of the first frequency band (frequency range 1 (FR1: Frequency Range 1)) and the second frequency band (frequency range 2 (FR2: Frequency Range 2)). The macro cell C1 may also be included in FR1, and the small cell C2 may also be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these. For example, FR1 may also be equivalent to a frequency band higher than FR2.

[0199] Furthermore, the user terminal 20 may perform communication in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).

[0200] Multiple base stations 10 can also be connected by wire (for example, optical fiber, X2 interface, etc. in accordance with CPRI (Common Public Radio Interface)) or wireless (for example, NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, the base station 11 equivalent to the upper station can also be called an IAB (Integrated Access Backhaul) donor, and the base station 12 equivalent to a relay station can also be called an IAB node.

[0201] The base station 10 may also be connected to the core network 30 via other base stations 10 or directly. The core network 30 may also include at least one of EPC (Evolved Packet Core), 5GCN (5G Core Network), NGC (Next Generation Core), etc.

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

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

[0204] The radio access scheme may also be referred to as a waveform. In the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the radio access schemes for UL and DL.

[0205] In the wireless communication system 1, as downlink channels, a downlink shared channel (physical downlink shared channel (PDSCH: Physical Downlink Shared Channel)), a broadcast channel (physical broadcast channel (PBCH: Physical Broadcast Channel)), a downlink control channel (physical downlink control channel (PDCCH: Physical Downlink Control Channel)), etc. shared by each user terminal 20 can also be used.

[0206] In addition, in the wireless communication system 1, as uplink channels, an uplink shared channel (physical uplink shared channel (PUSCH: Physical Uplink Shared Channel)), an uplink control channel (physical uplink control channel (PUCCH: Physical Uplink Control Channel)), a random access channel (physical random access channel (PRACH: Physical Random Access Channel)), etc. shared by each user terminal 20 can also be used.

[0207] User data, high-layer control information, SIB (System Information Block), etc. are transmitted through PDSCH. User data, high-layer control information, etc. can also be transmitted through PUSCH. In addition, MIB (Master Information Block) can also be transmitted through PBCH.

[0208] Lower layer control information may also be transmitted via the 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 the PDSCH and the PUSCH.

[0209] In addition, the DCI for scheduling the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI for scheduling the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be replaced by DL data, and the PUSCH may also be replaced by UL data.

[0210] The detection of PDCCH can also utilize the control resource set (CORESET: COntrol REsource SET) and the search space. CORESET corresponds to the resources for searching DCI. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a search space based on the search space setting.

[0211] One SS may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as search space sets. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" and the like in the present disclosure may also be interchangeable.

[0212] Through PUCCH, channel state information (CSI: Channel State Information), delivery confirmation information (for example, also known as HARQ-ACK (Hybrid Automatic Repeat reQuest), ACK / NACK, etc.), scheduling request (SR: Scheduling Request), etc. can also be transmitted. Through PRACH, the random access preamble used to establish a connection with the cell can also be transmitted.

[0213] In addition, in the present disclosure, downlink, uplink, etc. may be expressed without adding “link”. In addition, the beginning of various channels may be expressed without adding “Physical”.

[0214] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may also be transmitted. In the wireless communication system 1, as DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may also be transmitted.

[0215] The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS: Primary Synchronization Signal) and a secondary synchronization signal (SSS: Secondary Synchronization Signal). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may also be referred to as an SS / PBCH block, SSB (SS block), etc. In addition, SS, SSB, etc. may also be referred to as a reference signal.

[0216] In addition, in the wireless communication system 1, as an uplink reference signal (UL-RS: Uplink Reference Signal), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may also be transmitted. In addition, DMRS may also be called a user terminal specific reference signal (UE-specific Reference Signal).

[0217] (Base Station)

[0218] Fig.10 1 is a diagram showing an example of a structure of a base station involved in one embodiment. The base station 10 includes a control unit 110, a transmitting and receiving unit 120, a transmitting and receiving antenna 130, and a transmission line interface 140. In addition, the control unit 110, the transmitting and receiving unit 120, the transmitting and receiving antenna 130, and the transmission line interface 140 may each be provided with more than one.

[0219] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also assumed that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0220] 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 that are described based on common knowledge in the technical field to which the present disclosure relates.

[0221] The control unit 110 may also control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission, reception, measurement, etc. using the transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140. The control unit 110 may also generate data, control information, sequences, etc. to be sent as signals, and forward them to the transmission and reception unit 120. The control unit 110 may also perform call processing (setting, release, etc.) of communication channels, state management of the base station 10, management of wireless resources, etc.

[0222] The transmitting and receiving unit 120 may also include a baseband unit 121, an RF (Radio Frequency) unit 122, and a measuring unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting and receiving unit 120 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting and receiving circuit, etc., which are explained based on the common knowledge in the technical field involved in the present disclosure.

[0223] The transmitting and receiving unit 120 may also be configured as an integrated transmitting and receiving unit, or may be configured by a transmitting unit and a receiving unit. The transmitting unit may also be configured by a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured by a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0224] The transmitting / receiving antenna 130 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0225] The transmitting and receiving unit 120 may also transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the above-mentioned uplink channel, uplink reference signal, etc.

[0226] The transmitting and receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0227] The sending and receiving unit 120 (sending processing unit 1211), for example, may also perform PDCP (Packet Data Convergence Protocol) layer processing, RLC (Radio Link Control) layer processing (for example, RLC retransmission control), MAC (Medium Access Control) layer processing (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 110 to generate a bit string to be sent.

[0228] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, discrete Fourier transform (DFT: Discrete Fourier Transform) processing (as needed), inverse fast Fourier transform (IFFT: Inverse Fast Fourier Transform) processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0229] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal in the radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0230] On the other hand, the transmission and reception unit 120 (RF unit 122) performs amplification, filter processing, and baseband signal demodulation on the signal in the radio frequency band received by the transmission and reception antenna 130.

[0231] The sending and receiving unit 120 (receiving processing unit 1212) applies receiving processing such as analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0232] The transmitting and receiving unit 120 (measuring unit 123) may also implement measurements related to the received signal. For example, the measuring unit 123 may also perform RRM (Radio Resource Management) measurement, CSI (Channel State Information) measurement, etc. based on the received signal. The measuring unit 123 may also measure the received power (e.g., RSRP (Reference Signal Received Power)), received quality (e.g., RSRQ (Reference Signal Received Quality), SINR (Signal to Interference plus Noise Ratio), SNR (Signal to Noise Ratio)), signal strength (e.g., RSSI (Received Signal Strength Indicator), propagation path information (e.g., CSI), etc. The measurement result may also be output to the control unit 110.

[0233] The transmission path interface 140 can also send and receive signals between devices included in the core network 30, other base stations 10, etc. (return signaling notification), and obtain and transmit user data (user plane data) and control plane data for the user terminal 20.

[0234] In addition, the transmission unit and the reception unit of the base station 10 in the present disclosure may also be constituted by at least one of the transmission and reception unit 120 , the transmission and reception antenna 130 , and the transmission path interface 140 .

[0235] In addition, the transmitting and receiving unit 120 transmits one or more downlink control information for different purposes in a specific cell.

[0236] The control unit 110 may also control scheduling so that the downlink control information stored in the UE does not exceed a specific amount.

[0237] The downlink control information for a specific purpose may also include downlink control information used for scheduling of a physical shared channel, downlink control information used for activating a physical shared channel, and downlink control information used for deactivating a physical shared channel.

[0238] Alternatively, the downlink control information for a specific purpose may include downlink control information used for scheduling of a physical shared channel and downlink control information used for activating a physical shared channel. On the other hand, downlink control information used for deactivating a physical shared channel may not be included.

[0239] Alternatively, the downlink control information for a specific purpose may also include downlink control information used for scheduling a physical shared channel for unicast and downlink control information used for activating a physical shared channel. On the other hand, it may not include downlink control information used for deactivating a physical shared channel and downlink control information used for scheduling a physical shared channel for broadcast.

[0240] In addition, the transmitting and receiving unit 120 may also transmit the first downlink control information and the second downlink control information using at least one of different RNTIs (Radio Network Temporary Identifiers), different modulation and coding tables, and different transmission parameters.

[0241] The control unit 110 may also control scheduling for at least one of the first downlink control information and the second downlink control information so that the storage quantity in the UE does not exceed a specific quantity.

[0242] An upper limit value of the amount of first downlink control information to be stored and an upper limit value of the amount of second downlink control information to be stored may be set separately.

[0243] (User Terminal)

[0244] Fig.11 2 is a diagram showing an example of a configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. In addition, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided with one or more.

[0245] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it is also conceivable that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0246] 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 that are described based on common knowledge in the technical field to which the present disclosure relates.

[0247] The control unit 210 may also control signal generation, mapping, etc. The control unit 210 may also control transmission, reception, measurement, etc. using the transmission and reception unit 220 and the transmission and reception antenna 230. The control unit 210 may also generate data, control information, sequences, etc. to be sent as signals and forward them to the transmission and reception unit 220.

[0248] The transmitting and receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measuring unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting and receiving unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting and receiving circuit, etc., which are described based on the common knowledge in the technical field involved in the present disclosure.

[0249] The transmitting and receiving unit 220 may also be configured as an integrated transmitting and receiving unit, or may be configured by a transmitting unit and a receiving unit. The transmitting unit may also be configured by a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be configured by a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0250] The transmitting / receiving antenna 230 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0251] The transmitting and receiving unit 220 may also receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0252] The transmitting and receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0253] The sending and receiving unit 220 (sending processing unit 2211), for example, can also perform PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 210 to generate a bit string to be sent.

[0254] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0255] In addition, whether to apply DFT processing may also be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transmitting and receiving unit 220 (transmitting processing unit 2211) may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, DFT processing may not be performed as the above-mentioned transmission processing.

[0256] The transmitting and receiving unit 220 (RF unit 222 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal in the radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 230 .

[0257] On the other hand, the transmitting and receiving unit 220 (RF unit 222) may also perform amplification, filter processing, and baseband signal demodulation on the signal in the radio frequency band received through the transmitting and receiving antenna 230.

[0258] The sending and receiving unit 220 (receiving processing unit 2212) can also apply receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0259] The transmitting and receiving unit 220 (measuring unit 223) may also perform measurements related to the received signal. For example, the measuring unit 223 may also perform RRM measurements, CSI measurements, etc. based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may also be output to the control unit 210.

[0260] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 , the transmitting and receiving antenna 230 , and the transmission path interface 240 .

[0261] In addition, the transmitting and receiving unit 220 receives one or more downlink control information for different purposes in a specific cell.

[0262] The control unit 210 may also control the storage so that the downlink control information for a specific purpose in the received downlink control information does not exceed a specific amount. In addition, the DCI may also be stored in a storage device (eg, memory) included in the UE.

[0263] The downlink control information for a specific purpose may also include downlink control information used for scheduling of a physical shared channel, downlink control information used for activating a physical shared channel, and downlink control information used for deactivating a physical shared channel.

[0264] Alternatively, the downlink control information for a specific purpose may include downlink control information used for scheduling of a physical shared channel and downlink control information used for activating a physical shared channel. On the other hand, downlink control information used for deactivating a physical shared channel may not be included.

[0265] Alternatively, the downlink control information for a specific purpose may also include downlink control information used for scheduling of a physical shared channel for unicast, downlink control information used for activation of a physical shared channel, and downlink control information used for deactivation of a physical shared channel. On the other hand, the downlink control information used for deactivation of a physical shared channel and downlink control information used for scheduling of a physical shared channel for broadcast may not be included.

[0266] When communication is performed using a plurality of cells, the control unit 210 may determine the amount of downlink control information to be stored for each cell.

[0267] In addition, the transmitting and receiving unit 220 may also receive the first downlink control information and the second downlink control information to which at least one of different RNTIs (Radio Network Temporary Identifiers), different modulation and coding tables, and different transmission parameters are applied.

[0268] The control unit 210 may also control the storage so that the received first downlink control information and the received second downlink control information do not exceed a specific number.

[0269] An upper limit value of the amount of first downlink control information to be stored and an upper limit value of the amount of second downlink control information to be stored may be set separately.

[0270] When the number of stored first downlink control information and the number of stored second downlink control information exceed a specific number, the control unit 210 may also perform control so as to preferentially discard the downlink control information of one party.

[0271] The upper limit value of the amount of first downlink control information to be stored and the upper limit value of the amount of second downlink control information to be stored may be set at a specific ratio.

[0272] The upper limit value of the amount of first downlink control information to be stored and the upper limit value of the amount of second downlink control information to be stored may be set to exceed a specific amount based on a specific ratio.

[0273] (Hardware Structure)

[0274] In addition, the block diagram used in the description of the above-mentioned embodiment represents a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using one device that is physically or logically combined, or two or more devices that are physically or logically separated can be directly and / or indirectly (for example, using wired, wireless, etc.) connected and implemented using these multiple devices. The functional block can also be implemented by combining software with the above-mentioned one device or the above-mentioned multiple devices.

[0275] Here, the functions include judging, determining, judging, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, the functional block (structural part) that enables the transmission function may also be referred to as a transmitting unit, a transmitter, etc. As described above, the implementation method is not particularly limited to any one of them.

[0276] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig.12 The base station 10 and the user terminal 20 are 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, and a bus 1007.

[0277] In addition, in the present disclosure, the words such as device, circuit, equipment, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or may exclude some of the devices.

[0278] For example, only one processor 1001 is shown, but there may be multiple processors. In addition, the processing may be performed by one processor, or the processing may be performed by two or more processors simultaneously, sequentially, or using other methods. In addition, the processor 1001 may also be implemented by one or more chips.

[0279] The various functions in the wireless base station 10 and the user terminal 20 are implemented, for example, as follows: specific software (program) is read into hardware such as the processor 1001 and the memory 1002, and the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0280] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a computing device, registers, etc. For example, at least a part of the control unit 110 (210), the sending and receiving unit 120 (220), etc., may also be implemented by the processor 1001.

[0281] In addition, 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 performs various processes based on them. As a program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the control unit 110 (210) can be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks can also be implemented in the same way.

[0282] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically EPROM), a RAM (Random Access Memory), or other suitable storage media. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The memory 1002 can store an executable program (program code), a software module, etc. for implementing the wireless communication method of one embodiment of the present disclosure.

[0283] The storage 1003 is a computer-readable recording medium, and may be composed of at least one of a flexible disk, a floopy (registered trademark) disk, an optical disk (e.g., a compact disk (CD-ROM (Compact Disc ROM)), a digital versatile disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0284] The communication device 1004 is hardware (transmitting and receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., for example, in order to realize at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex). For example, the above-mentioned transmitting and receiving unit 120 (220), the transmitting and receiving unit 130 (230), etc. may also be realized by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated by the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0285] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that performs output to the outside (e.g., a display, a speaker, an LED (Light Emitting Diode) lamp, etc.). In addition, the input device 1005 and the output device 1006 may also be an integrated structure (e.g., a touch panel).

[0286] In addition, the processor 1001, the memory 1002 and other devices are connected via a bus 1007 for information communication. The bus 1007 may be configured by a single bus or by different buses between devices.

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

[0288] (Variation Example)

[0289] In addition, the terms described in the present disclosure and / or the terms required for understanding the present disclosure can be replaced with terms having the same or similar meanings. For example, channels, code elements, and signals (signal or signaling) can also be replaced with each other. In addition, the signal can also be a message. The reference signal can also be referred to as RS (Reference Signal), and depending on the applied standard, it can also be referred to as a pilot (Pilot), a pilot signal, etc. In addition, a component carrier (CC) can also be referred to as a cell, a frequency carrier, a carrier frequency, etc.

[0290] A wireless frame may also be composed of one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) constituting a wireless frame may also be referred to as a subframe. Furthermore, a subframe may also be composed of one or more time slots in the time domain. A subframe may be a fixed duration (e.g., 1 ms) that is independent of a parameter set (numerology).

[0291] Here, the parameter set may also refer to a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. The parameter set may also represent, for example, at least one of the subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, wireless frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

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

[0293] A time slot may include multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be called a sub-slot. A mini-slot may also be composed of symbols less than the number of time slots. A PDSCH (or PUSCH) transmitted in a time unit greater than a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type B.

[0294] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols may also be referred to by other names corresponding to each other. In addition, the time units of frames, subframes, time slots, mini-time slots, and symbols in the present disclosure may also be interchangeable.

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

[0296] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) in units of TTI. In addition, the definition of TTI is not limited to this.

[0297] TTI can be a transmission time unit for data packets (transmission blocks), code blocks, code words, etc. after channel coding, and can also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which the transmission block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0298] In addition, when 1 time slot or 1 mini time slot is referred to as TTI, more than 1 TTI (i.e., more than 1 time slot or more than 1 mini time slot) can be the minimum time unit of scheduling. In addition, the number of time slots (number of mini time slots) constituting the minimum time unit of scheduling can be controlled.

[0299] A TTI with a duration of 1 ms may also 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 time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini-time slot, a sub-time slot, a time slot, etc.

[0300] In addition, long TTI (e.g., normal TTI, subframe, etc.) can also be replaced by a TTI with a duration exceeding 1 ms, and short TTI (e.g., shortened TTI, etc.) can also be replaced by a TTI with a TTI length shorter than that of long TTI and longer than 1 ms.

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

[0302] In addition, an RB may include one or more symbols in the time domain, and may be of the length of one slot, one mini slot, one subframe, or one TTI. One TTI and one subframe may also be composed of one or more resource blocks, respectively.

[0303] In addition, one or more RBs may also be referred to as a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, and the like.

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

[0305] A bandwidth part (BWP) (also referred to as a partial bandwidth, etc.) may also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a carrier. Here, the common RBs may also be identified by an index of the RB based on a common reference point of the carrier. PRBs may be defined by a BWP or may be assigned a number within the BWP.

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

[0307] At least one of the set BWPs may also be activated, and the UE may not assume that it sends or receives specific signals / channels outside the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be replaced by "BWP".

[0308] In addition, the structures of the above-mentioned radio frames, subframes, time slots, mini-time slots, and symbols are only examples. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP: Cyclic Prefix) length can be changed in various ways.

[0309] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may also be indicated by specific indexes.

[0310] The names used for parameters, etc. in the present disclosure are not restrictive names at all. Furthermore, the formulas, etc. using these parameters may also be different from the formulas explicitly disclosed in the present disclosure. Various channels (PUCCH (Physical Uplink Control Channel), PDCCH (Physical Downlink Control Channel), etc.) and information elements can be identified by all appropriate names, and therefore the various names assigned to these various channels and information elements are not restrictive names at all.

[0311] Information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, code elements, and chips, etc. that may be mentioned throughout the above description may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0312] In addition, information, signals, etc. may be output to at least one of the following: from a high layer to a low layer, and from a low layer to a high layer. Information, signals, etc. may also be input and output via a plurality of network nodes.

[0313] The input and output information, signals, etc. may be stored in a specific area (e.g., a memory) or managed using a management table. The input and output information, signals, etc. may also be overwritten, updated, or added. The output information, signals, etc. may also be deleted. The input information, signals, etc. may also be sent to other devices.

[0314] The notification of information is not limited to the method / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information in the present disclosure may be implemented through physical layer signaling (e.g., downlink control information (downlink control information (DCI: Downlink Control Information)), uplink control information (uplink control information (UCI: Uplink Control Information))), high-layer signaling (e.g., RRC (Radio Resource Control) signaling, broadcast information (Master Information Block (MIB: Master Information Block), System Information Block (SIB: System Information Block)), MAC (Medium Access Control) signaling), other signals or a combination thereof.

[0315] In addition, physical layer signaling may also be referred to as L1 / L2 (Layer 1 / Layer 2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling may also be referred to as RRC message, for example, RRC connection setup (RRC Connection Setup) message, RRC connection reconstruction (RRC Connection Reconfiguration) message, etc. In addition, MAC signaling may be notified using, for example, a MAC control element (MAC CE (Control Element)).

[0316] In addition, notification of specific information (for example, notification of "it is X") is not limited to explicit notification, and may be performed implicitly (for example, by not notifying the specific information or by notifying other information).

[0317] The determination can be made by a value represented by 1 bit (0 or 1), by a true or false value (Boolean value) represented by true (true) or false (false), or by comparison of numerical values ​​(for example, comparison with a specific value).

[0318] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be construed broadly to mean instructions, instruction sets, codes, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, etc.

[0319] In addition, software, instructions, information, etc. may be sent and received via a transmission medium. For example, when the software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, optical cable, twisted pair, and digital subscriber line (DSL) etc.) and wireless technology (infrared, microwave etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0320] The terms "system" and "network" used in the present disclosure may be used interchangeably. "Network" may also mean a device (eg, a base station) included in the network.

[0321] In the present disclosure, the terms "precoding", "precoder", "weight (precoding weight)", "quasi-co-location (QCL: Quasi-Co-Location)", "TCI state (Transmission Configuration Indication state)", "spatial relation", "spatial domain filter", "transmit power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel", etc. can be used interchangeably.

[0322] In the present disclosure, the terms "base station (BS)," "wireless base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier" and the like are used interchangeably. Base stations are sometimes also referred to as macrocells, small cells, femtocells, picocells and the like.

[0323] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to part or all of the coverage area of ​​at least one of a base station and a base station subsystem that provide communication services within the coverage area.

[0324] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (UE)”, and “terminal” may be used interchangeably.

[0325] A mobile station is also sometimes referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client or some other appropriate terminology.

[0326] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a means of transportation (e.g., a car, an airplane, etc.), a mobile body that moves unmanned (e.g., a drone, an automatic vehicle, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an IoT (Internet of Things) device such as a sensor.

[0327] In addition, the base station in the present disclosure can be replaced by a user terminal. For example, the various methods / implementations of the present disclosure can also be applied to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple user terminals (for example, it can also be called device-to-device (D2D (Device-to-Device)), vehicle-to-everything (V2X (Vehicle-to-Everything)), etc.). In this case, it can be set as a structure in which the user terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, words such as "uplink" and "downlink" can be replaced by words corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can also be replaced by side channels.

[0328] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0329] In the present disclosure, operations are assumed to be performed by a base station, and sometimes, depending on the circumstances, they are also performed by its upper node. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal can obviously be performed by a base station, one or more network nodes other than the base station (for example, consider MME (Mobility Management Entity), S-GW (Serving-Gateway), etc., but not limited to this) or a combination thereof.

[0330] Each method / implementation method described in this disclosure may be used alone, in combination, or switched during execution. In addition, the processing procedures, timings, flow charts, etc. of each method / implementation method described in this disclosure may be swapped in order as long as they are not contradictory. For example, regarding the method described in this disclosure, the elements of various steps are presented in an illustrative order, and are not limited to the specific order presented.

[0331] The various modes and implementation modes described in the present disclosure can be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), LTE-B (LTE-Beyond), SUPER3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), New-RAT (Radio Access Technology), NR (New Radio), NX (New radio access), FX (Future generation radio access), GSM (registered trademark) (Global System for Mobile communications), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), systems using other appropriate wireless communication methods, and next-generation systems expanded based on them. In addition, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G, etc.).

[0332] The phrase “based on” used in the present disclosure does not mean “based only on” unless explicitly described otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on”.

[0333] Any reference to an element using the terms "first", "second", etc. used in this disclosure is not intended to fully define the number or order of these elements. These terms may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first and second element does not mean that only two elements may be used or that the first element must be located before the second element in some form.

[0334] The term "determining" as used in this specification sometimes includes a variety of operations. For example, "determining" can be considered as "judging", calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (for example, searching in a table, database or other data structure), ascertaining, etc.

[0335] In addition, "judgment (decision)" can also be regarded as "judgment (decision)" on receiving (for example, receiving information), sending (for example, transmitting information), input (input), output (output), accessing (for example, accessing data in a memory), etc.

[0336] In addition, "judgment (decision)" can also be regarded as "judgment (decision)" on resolving (resolving), selecting (selecting), choosing (choosing), establishing (establishing), comparing (comparing), etc. In other words, "judgment (decision)" can be regarded as "judgment (decision)" on certain operations.

[0337] In addition, "judge (decide)" can also be replaced by "assuming (assuming)," "expecting (expecting)," "considering (considering)".

[0338] The terms "connected", "coupled", etc., or all their variations used in this disclosure, mean all direct or indirect connections or combinations between two or more elements, and may include situations where there are one or more intermediate elements between the two elements that are "connected" or "coupled" to each other. The combination or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may also be replaced by "access".

[0339] In the present disclosure, when more than two elements are connected, it can be considered that they are "connected" or "combined" with each other using one or more wires, cables, printed electrical connections, etc., and as several non-limiting and non-exhaustive examples, electromagnetic energy with wavelengths in the wireless frequency domain, microwave domain, and light (both visible and invisible light) domain, etc.

[0340] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". Terms such as "separate", "combined", etc. may also be interpreted as "different".

[0341] When the terms "include", "including" and their variations are used in the present disclosure, these terms, like the term "comprising", mean inclusiveness. Furthermore, the term "or" used in the present disclosure does not mean a logical exclusive OR.

[0342] In the present disclosure, when articles such as a, an, and the in English are added by translation, the present disclosure includes the case where the noun following these articles is in plural form.

[0343] The invention involved in the present disclosure is described in detail above, but for those skilled in the art, the invention involved in the present disclosure is obviously not limited to the embodiments described in the present disclosure. The invention involved in the present disclosure can be implemented as a modification and variation without departing from the purpose and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for the purpose of exemplary description and does not bring any restrictive meaning to the invention involved in the present disclosure.

Claims

1. A terminal, characterized in that: have: a receiving unit, receiving a first downlink shared channel scheduled for the first cell, and receiving a second downlink shared channel scheduled for the second cell; and A control unit is assumed to receive at most X downlink control channels for downlink control information, and control reception processing, wherein the downlink control information is used to activate or deactivate an unreceived downlink shared channel and is scrambled by a specific radio network temporary identifier, i.e., a specific RNTI, and is CRC-scrambled, The specific RNTI is a CS-RNTI, The control unit is assumed to receive a maximum of X downlink control channels for each cell including the first cell and the second cell.

2. The terminal according to claim 1, characterized in that The control unit does not include reception of a downlink control channel of downlink control information scrambled by CRC using SI-RNTI in the X number.

3. The terminal according to claim 1, characterized in that The downlink control information is DCI format 1_0 or DCI format 1_1.

4. The terminal according to claim 1, characterized in that The X is 16.

5. The terminal according to claim 1, characterized in that In the case where cross-carrier scheduling is applied, the control unit determines the maximum value of the reception number of the downlink control channel in the scheduling cell based on the number of scheduled cells.

6. A wireless communication method for a terminal, characterized in that: have: The steps of receiving a first downlink shared channel scheduled for the first cell and receiving a second downlink shared channel scheduled for the second cell; and Assuming that at most X downlink control channels for downlink control information are received, the receiving process is controlled, wherein the downlink control information is used to activate or deactivate the unreceived downlink shared channel and is scrambled by a specific radio network temporary identifier, i.e., a specific RNTI, and the like, The specific RNTI is a CS-RNTI, The method further includes a step of assuming that each cell including the first cell and the second cell receives a maximum of X of the downlink control channels.

7. A base station, characterized in that: have: a sending unit, sending a first downlink shared channel scheduled for the first cell, and sending a second downlink shared channel scheduled for the second cell; and A control unit, assuming that the terminal receives at most X downlink control channels for downlink control information, and controls the sending process, wherein the downlink control information is used to activate or deactivate the downlink shared channel not received by the terminal and is CRC-scrambled by a specific radio network temporary identifier, i.e., a specific RNTI, The specific RNTI is a CS-RNTI, The control unit assumes that the terminal receives at most X downlink control channels in each cell including the first cell and the second cell.

8. A system comprising a terminal and a base station, characterized in that: The terminal comprises: a receiving unit, receiving a first downlink shared channel scheduled for the first cell, and receiving a second downlink shared channel scheduled for the second cell; and A control unit is assumed to receive at most X downlink control channels for downlink control information, and control reception processing, wherein the downlink control information is used to activate or deactivate an unreceived downlink shared channel and is scrambled by a specific radio network temporary identifier, i.e., a specific RNTI, and is CRC-scrambled, The specific RNTI is a CS-RNTI, The control unit is assumed to receive at most X downlink control channels for each cell including the first cell and the second cell. The base station comprises: A sending unit, sending the downlink shared channel; and The control unit controls the transmission process assuming that the terminal receives at most X of the downlink control channels, The control unit assumes that the terminal receives at most X downlink control channels in each cell including the first cell and the second cell.

Images