Terminal and wireless communication method

Abstract

A terminal receives single downlink control information indicating a schedule for a combination of a plurality of cells. The terminal envisages that the scheduling is applied to at least one of a scheduling cell in which the downlink control information is received and a scheduled cell indicated by the downlink control information.

Description

Technical Field

[0001] This disclosure relates to terminals and wireless communication methods corresponding to a mechanism that uses a single downlink control information transmitted by a specific carrier to schedule a data channel transmitted by multiple carriers. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP, registered trademark) standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)) and also standardized the next generation known as Beyond 5G, 5G Evolution, or 6G.

[0003] In 3GPP Release 18, the function of scheduling PDSCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted by multiple component carriers (CCs) using a single downlink control information (DCI) was investigated (Non-Patent Document 1). Such a function is referred to as Single DCI Multi-carrier PDSCH / PUSCH scheduling or Single DCI Multi-Cell PDSCH / PUSCH scheduling, etc. (hereinafter referred to as Single DCI Multi-Cell PDSCH / PUSCH scheduling)

[0004] In addition, in order to support such Single DCI Multi-Cell PDSCH / PUSCH scheduling, a single DCI format that can schedule PDSCH / PUSCH of multiple cells is agreed upon (which may be called DCI format 0_X / 1_X, etc.) (Non-Patent Document 2).

[0005] By using a DCI that follows this DCI format, multiple cells contained in a set of cells can be scheduled simultaneously.

[0006] Existing technical documents

[0007] Non-patent literature

[0008] Non-patent literature 1: "New WID on Multi-carrier enhancements", RP-213577, 3GPPTSG RAN Meeting #94e, 3GPP, December 2021

[0009] Non-patent document 2: "RAN1 Chair's Notes", 3GPP TSG RAN WG1 #109-e, 3GPP, May 2022 Summary of the Invention

[0010] When supporting Single DCI Multi-Cell PDSCH / PUSCH scheduling as described above, consider the following issues. Specifically, there is concern that even if the User Equipment (UE) directly applies existing cell and carrier-related settings, it may be unable to configure appropriate cells and carriers.

[0011] Therefore, the following disclosure is made in view of the following situation, and its purpose is to provide a terminal and wireless communication method that can perform appropriate settings even when multiple cells are simultaneously scheduled using Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0012] One aspect of this disclosure is a terminal (UE 200) comprising: a receiving unit (control signal / reference signal processing unit 240) that receives a single downlink control information indicating scheduling of a combination of multiple cells; and a control unit (control unit 270) that assumes the scheduling cell receiving the downlink control information and the scheduled cell indicated by the downlink control information are the multiple cells to be scheduled.

[0013] One aspect of this disclosure is a terminal (UE 200) comprising: a receiving unit (control signal / reference signal processing unit 240) that receives a single downlink control information indicating scheduling for a combination of multiple cells; and a control unit (control unit 270) that envisions applying the scheduling to at least one of the scheduling cell receiving the downlink control information and the scheduled cell indicated by the downlink control information. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10.

[0015] Figure 2 This is a diagram showing the frequency bands used in the wireless communication system 10.

[0016] Figure 3 This is a diagram illustrating an example of the structure of wireless frames, subframes, and time slots used in the wireless communication system 10.

[0017] Figure 4 This is the function block structure diagram of gNB 100 and UE 200.

[0018] Figure 5 This is a diagram illustrating an example of a scheduling method that can be supported by the wireless communication system 10.

[0019] Figure 6 This is a diagram illustrating a PDSCH scheduling example based on Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0020] Figure 7 This is a diagram illustrating a notification example of the parameters for carrier indication in Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0021] Figure 8 This is a diagram illustrating a configuration example of Single DCI Multi-Cell PDSCH / PUSCH scheduling using the RRC parameters involved in Opt.1, which uses the action example.

[0022] Figure 9 This is a diagram illustrating a configuration example of Single DCI Multi-Cell PDSCH / PUSCH scheduling using the RRC parameters involved in Opt.2, which uses the action example.

[0023] Figure 10 This is a diagram illustrating an example of the joint coding / encoding / indication table configuration (Opt.1) in the case of Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0024] Figure 11 This is a diagram illustrating an example of the joint coding / encoding / indication table configuration (Opt.2) in the case of Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0025] Figure 12 This is a diagram illustrating an example of the hardware structure of gNB 100 and UE 200.

[0026] Figure 13 This is a diagram showing a structural example of vehicle 2001. Detailed Implementation

[0027] The embodiments are described below based on the accompanying drawings. Furthermore, the same or similar reference numerals are used to denote the same function or structure, and their descriptions are omitted where appropriate.

[0028] (1) Overall general structure of wireless communication system

[0029] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10 involved in this embodiment. The wireless communication system 10 is a wireless communication system that follows 5G New Radio (NR) and includes a Next Generation Radio Access Network (NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter referred to as UE 200).

[0030] Alternatively, the wireless communication system 10 can also be a wireless communication system that follows the methods referred to as Beyond 5G, 5G Evolution, or 6G.

[0031] NG-RAN 20 includes a radio base station 100 (hereinafter referred to as gNB 100). Furthermore, the specific structure of the wireless communication system 10, including the number of gNBs and UEs, is not limited to... Figure 1 The example shown.

[0032] NG-RAN 20 actually contains multiple NG-RAN nodes, specifically multiple gNBs (or ng-eNBs), connected to a 5G-compliant core network (5GC, not shown). Additionally, NG-RAN 20 and 5GC can be simply referred to as a "network".

[0033] The gNB 100 is an NR-compliant radio base station that performs NR-compliant wireless communication with the UE 200. The gNB 100 and UE 200 can support Massive MIMO, which generates more directional beams by controlling radio signals transmitted from multiple antenna elements; Carrier aggregation (CA), which uses multiple component carriers (CC); and Dual connectivity (DC), which allows simultaneous communication between the UE and multiple NG-RAN nodes.

[0034] DCs can be of various types, including Multi-RAT Dual Connectivity (MR-DC) which utilizes multiple radio access technologies, and NR-NR Dual Connectivity which utilizes only NR. Furthermore, MR-DC can be E-UTRA-NR Dual Connectivity (EN-DC) where eNBs form the master node (MN) and gNBs form the slave node (SN), or it can be the opposite: NR-E-UTRA Dual Connectivity (NE-DC).

[0035] In addition, the wireless communication system 10 can support multiple frequency ranges (FRs). Figure 2 The frequency band used in the wireless communication system 10 is shown.

[0036] FR1: 410MHz~7.125GHz

[0037] FR2:

[0038] FR2-1: 24.25GHz~52.6GHz

[0039] FR2-2: Over 52.6GHz to 71GHz

[0040] In FR1, a sub-carrier spacing (SCS) of 15, 30, or 60 kHz can be used, with a bandwidth (BW) of 5–100 MHz. FR2 operates at a higher frequency than FR1, and can use an SCS of 60 or 120 kHz (or even 240 kHz), with a bandwidth (BW) of 50–400 MHz.

[0041] Furthermore, the wireless communication system 10 can also support frequency bands higher than FR2. Specifically, the wireless communication system 10 can support frequency bands exceeding 52.6 GHz up to 114.25 GHz.

[0042] Furthermore, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread OFDM (DFT-S-OFDM) with larger sub-carrier spacing (SCS) can be applied. Moreover, DFT-S-OFDM can be applied not only to the uplink (UL) but also to the downlink (DL).

[0043] Figure 3 An example of the structure of wireless frames, subframes, and time slots used in wireless communication system 10 is shown.

[0044] like Figure 3 As shown, one time slot consists of 14 symbols. The larger (wider) the SCS, the shorter the symbol period (and time slot period). Furthermore, the number of symbols constituting one time slot does not necessarily have to be 14 symbols (e.g., 28, 56 symbols). Additionally, the number of time slots per subframe can vary depending on the SCS. Moreover, the SCS can also be wider than 240kHz (e.g., ...). Figure 3 As shown, 480kHz and 960kHz).

[0045] in addition, Figure 2 The time direction (t) shown can also be referred to as the time domain, symbol period, or symbol time, etc. Furthermore, the frequency direction can also be referred to as the frequency domain, resource block (RB), resource block group (RBG), subcarrier, BWP (Bandwidth part), etc.

[0046] In the wireless communication system 10, functions related to multiple carriers (specifically, CCs) can be extended as described above. Specifically, in the wireless communication system 10, the function of scheduling PDSCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted by multiple time slots using a single downlink control information (DCI) can be supported (single DCI multi-slot PDSCH / PUSCH scheduling).

[0047] Specifically, in the wireless communication system 10, it can support a scheduling method in which the DCI and the channel to be scheduled are the same CC (self-carrier scheduling), a cross-carrier scheduling method that applies scheduling of channels across multiple CCs, and a multi-carrier scheduling method that uses a single DCI (Single DCI), i.e., one DCI, to allocate channels to multiple different CCs.

[0048] More specifically, in the wireless communication system 10, the function of scheduling PDSCH / PUSCH transmitted by multiple CCs using a single DCI can be supported (Single DCI Multi-carrier PDSCH / PUSCH scheduling or Single DCI Multi-Cell PDSCH / PUSCH scheduling). Hereinafter, it will be referred to as Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0049] Single DCI multi-slot PDSCH / PUSCH scheduling and single DCI multi-cell PDSCH / PUSCH scheduling can only utilize one of them and cannot utilize both at the same time. However, in the wireless communication system 10, simultaneous utilization of both can be supported.

[0050] Furthermore, in the wireless communication system 10, to support such Single DCI Multi-Cell PDSCH / PUSCH scheduling, a single DCI format capable of scheduling PDSCH / PUSCH for multiple cells can be used (which may be called DCI format 0_X / 1_X or DCI format 0_3 / 1_3, etc.). By using a DCI conforming to this DCI format, multiple cells contained in a set of cells can be scheduled simultaneously.

[0051] (2) Functional block structure of wireless communication system

[0052] Next, the functional block structure of the wireless communication system 10 will be described. Specifically, the functional block structure of the UE 200 will be described. Figure 4 This is the function block structure diagram of gNB 100 and UE 200.

[0053] like Figure 4 As shown, the UE 200 includes a wireless signal transceiver unit 210, an amplifier unit 220, a modem unit 230, a control signal and reference signal processing unit 240, an encoding / decoding unit 250, a data transceiver unit 260, and a control unit 270.

[0054] In addition, Figure 4 Only the main functional blocks relevant to the description of the implementation method are shown in the diagram. It should be noted that the UE 200 (gNB100) has other functional blocks (e.g., power supply section, etc.). Furthermore, Figure 4 This shows the functional block structure of UE 200. For information on the hardware structure, please refer to [reference needed]. Figure 12 .

[0055] The radio transceiver unit 210 transmits and receives radio signals that comply with NR. The radio transceiver unit 210 can support massive MIMO (Massive MIMO) that generates beams with higher directionality by controlling radio (RF) signals transmitted from multiple antenna elements, carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that enables simultaneous communication between the UE and two NG-RAN nodes.

[0056] The amplifier section 220 comprises a power amplifier (PA) and a low-noise amplifier (LNA). The amplifier section 220 amplifies the signal output from the modem 230 to a predetermined power level. Furthermore, the amplifier section 220 amplifies the RF signal output from the wireless transceiver 210.

[0057] The modem 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication target (gNB 100, etc.). Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) can also be applied in the modem 230. Furthermore, DFT-S-OFDM can be used not only for the uplink (UL) but also for the downlink (DL).

[0058] The control signal and reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE 200, as well as processing related to various reference signals transmitted and received by the UE 200.

[0059] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, such as control signals from the Radio Resource Control (RRC) layer. Furthermore, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via the predetermined control channel.

[0060] The control signal and reference signal processing unit 240 performs processing using reference signals (RS) such as demodulation reference signal (DMRS) and phase tracking reference signal (PTRS).

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

[0062] In addition to DMRS and PTRS, the reference signal may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

[0063] In addition, channels include control channels and data channels. Control channels may include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, including Downlink Control Information (DCI) containing Random Access Radio Network Temporary Identifier (RA-RNTI)), and Physical Broadcast Channel (PBCH), etc.

[0064] In addition, data channels include PDSCH and PUSCH, etc. Data can refer to data transmitted via data channels.

[0065] The control signal and reference signal processing unit 240 is capable of receiving downlink control information (DCI) transmitted from the network. Specifically, the control signal and reference signal processing unit 240 is capable of receiving DCI conforming to the DCI format specified in 3GPP TS38.212. In particular, in this embodiment, it is capable of receiving scheduling DCI for both UL and DL. More specifically, the control signal and reference signal processing unit 240 can receive DCI conforming to DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, 1_2.

[0066] Furthermore, in this embodiment, the control signal / reference signal processing unit 240 can receive DCIs in DCI formats 0_3 and 1_3 that follow Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0067] DCI formats 0_0, 0_1, 0_2, 0_3 can be interpreted as UL's scheduling grant. DCI formats 1_0, 1_1, 1_2, 1_3 can be interpreted as DL's scheduling assignment.

[0068] The control signal and reference signal processing unit 240 can receive DCIs corresponding to single DCI multi-slot PDSCH / PUSCH scheduling and DCIs corresponding to single DCI multi-cell PDSCH / PUSCH scheduling.

[0069] Specifically, regarding single DCI multi-slot PDSCH / PUSCH scheduling, the control signal and reference signal processing unit 240 can receive a single (1) DCI for scheduling channels transmitted from multiple time slots. Furthermore, regarding single DCI multi-cell PDSCH / PUSCH scheduling, the control signal and reference signal processing unit 240 can receive a single (1) DCI for scheduling channels transmitted from multiple carriers.

[0070] Here, the channel may include the control channel and data channel mentioned above, and may not be specifically limited to the uplink and downlink directions. Typically, it may refer to at least one of PDSCH or PUSCH. The carrier may refer to the component carrier (CC), but may also be interpreted simply as the carrier or subcarrier, etc.

[0071] Furthermore, the control signal / reference signal processing unit 240 can send UE 200 capability information to the network. In particular, in this embodiment, the control signal / reference signal processing unit 240 can send scheduling-related UE capability information (refer to...) to the gNB 100. Figure 1 ).

[0072] The control signal / reference signal processing unit 240 can send scheduling-related UE capability information based on the control unit 270's assumption about the UE 200's scheduling-related terminal capabilities.

[0073] As described above, the control signal / reference signal processing unit 240 is capable of performing processing related to the Radio Resource Control (RRC) layer and can transmit or receive RRC layer messages. The control signal / reference signal processing unit 240 can receive a single downlink control information (DCI) instructing scheduling for a set of cells. In this embodiment, the control signal / reference signal processing unit 240 can be configured as a receiving unit.

[0074] Specifically, the control signal / reference signal processing unit 240 can receive DCI (DCI following DCI format 0_X / 1_X) that indicates scheduling of a set of cells based on Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0075] The encoding / decoding unit 250 performs data segmentation / linking and channel encoding / decoding for each predetermined communication target (gNB 100 or other gNB).

[0076] Specifically, the encoding / decoding unit 250 divides the data output from the data transceiver unit 260 into predetermined sizes and performs channel coding on the divided data. Furthermore, the encoding / decoding unit 250 decodes the data output from the modem unit 230 and concatenates the decoded data.

[0077] The data transceiver unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transceiver unit 260 performs the assembly / disassembly of PDUs / SDUs at multiple layers (Media Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP), etc.). Furthermore, the data transceiver unit 260 performs error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ).

[0078] The control unit 270 controls the functional blocks constituting the UE 200. In particular, in this embodiment, the control unit 270 controls the transmission or reception of channels (e.g., PDSCH / PUSCH, hereinafter the same) based on the DCI used for single DCI multi-slot PDSCH / PUSCH scheduling.

[0079] In addition, the control unit 270 controls the transmission or reception of the channel based on the DCI used for Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0080] Thus, the control unit 270 can control the transmission or reception of the channel based on at least one of the DCI used for single DCI multi-slot PDSCH / PUSCH scheduling and the DCI used for single DCI multi-cell PDSCH / PUSCH scheduling. Furthermore, both single DCI multi-slot PDSCH / PUSCH scheduling and single DCI multi-cell PDSCH / PUSCH scheduling can be used simultaneously, allowing the control unit 270 to execute control based on both scheduling DCIs concurrently.

[0081] The control unit 270 can apply different settings to at least one of the cells, time slots, or channels scheduled using the DCI used for single DCI multi-slot PDSCH / PUSCH scheduling and the DCI used for single DCI multi-cell PDSCH / PUSCH scheduling. The cell type (primary cell (PCell), primary / secondary cell (PSCell), and secondary cell (SCell)) is not particularly limited, and cell groups (primary or secondary) can be used. The channel type is also not particularly limited; it can be UL direction or DL ​​direction, and PDSCH / PUSCH can be used as the target.

[0082] Furthermore, in the case of scheduling a set of cells (a collection of cells) indicated by Single DCI Multi-Cell PDSCH / PUSCH scheduling, the control unit 270 can envision multiple cells as the scheduling targets as follows. Specifically, the control unit 270 can envision that the scheduling cell receiving the DCI (DCI format 0_X / 1_X) used for Single DCI Multi-Cell PDSCH / PUSCH scheduling and the scheduled cells indicated by the DCI are multiple cells as the scheduling targets.

[0083] Thus, the cell that receives the DCI can be called the scheduling cell, and the cell indicated by the DCI can be called the scheduled cell. Furthermore, multiple cells that are simultaneously scheduled using the DCI can be called co-scheduled cells.

[0084] More specifically, the control unit 270 can envision the objects of the multiple cells based on the information elements (IEs) related to the configuration of the serving cell contained in the RRC message. Examples of IEs related to the configuration of the serving cell include servingCellConfig or servingCellConfigCommon (see 3GPP TS38.331). However, it is not limited to such IEs; any IE related to the serving cell can be used, or other IEs.

[0085] The control unit 270 can perform settings related to multiple cells based on the identification information (ID) of the set of cells contained in the RRC message. For example, the MultiCellScheduling-SetId field (which can be a temporary name) can be set as the ID of the set of cells. Specific examples of this field will be described later.

[0086] The control unit 270 can perform settings related to multiple cells based on RRC messages that have the above-mentioned fields set for both the scheduling cell and the scheduled cell. That is, the field can also be set separately in the scheduling cell and the scheduled cell.

[0087] Alternatively, the control unit 270 may perform settings related to multiple cells based on the carrier indication (CI) field contained in the DCI and / or RRC message that is associated with a combination of multiple cells. For example, the notification nCI-Value (which may be a temporary name) may be set as a field of the value of n_CI associated with a set of cells.

[0088] Furthermore, the control unit 270 can envision applying Single DCI Multi-Cell PDSCH / PUSCH scheduling to at least one of the scheduling cell (DCI format 0_X / 1_X) used for receiving Single DCI Multi-Cell PDSCH / PUSCH scheduling and the scheduled cell indicated by that DCI. In other words, the control unit 270 can envision applying Single DCI Multi-Cell PDSCH / PUSCH scheduling only to cells of any one type, rather than to both the scheduling cell and the scheduled cell.

[0089] In this case, the control unit 270 may envision applying Single DCI Multi-Cell PDSCH / PUSCH scheduling to the scheduling cell or a reference cell that is set to monitor the search space of the DCI.

[0090] Additionally, a reference cell can be interpreted as a cell that counts the DCI size, PDCCH candidate (BD), and CCE number for DCI format 0_X / 1_X. For each set of cells, a cell can be set up to count the DCI size, PDCCH candidate (BD), and CCE number for the cells included in the set of cells.

[0091] Furthermore, the control unit 270 can also perform cell-related settings for application scheduling based on the information elements (IEs) related to the serving cell settings contained in the RRC message. For example, in the servingCellConfig, fields related to the settings of cells included in the set of cells for Single DCI Multi-Cell PDSCH / PUSCH scheduling can be set.

[0092] For example, the control unit 270 can perform settings related to the cell applying Single DCI Multi-Cell PDSCH / PUSCH scheduling based on the carrier indication (CI) field included in the information element. Specifically, the setting field (MultiCellScheduling-Set-Config, which may be a temporary name) for notifying the set of cells for multi-cell scheduling can be specified in servingCellConfig. In this field, the value of n_CI can be used to notify nCI-Value (which may also be a temporary name).

[0093] The control unit 270 can execute cell-related settings for Single DCI Multi-Cell PDSCH / PUSCH scheduling based on RRC messages that configure fields for multiple cells. For example, the control unit 270 can specify fields for notifying joint coding table settings in MultiCellScheduling-Set-Config and execute settings according to those fields.

[0094] Furthermore, gNB 100 may have functions corresponding to UE 200 described above. Specifically, gNB 100 (control signal / reference signal processing unit 240) may be configured as a transmitting unit that transmits downlink control information indicating scheduling of combinations of multiple cells, and gNB 100 (control unit 270) may be configured as a control unit that executes the settings of downlink control information.

[0095] (3) Operation of wireless communication system

[0096] Next, the operation of the wireless communication system 10 will be explained. Specifically, the operation related to the framework of the RRC layer setting for Single DCI Multi-Cell PDSCH / PUSCH scheduling will be explained.

[0097] (3.1) Prerequisites and topics

[0098] As described above, in the wireless communication system 10, the function of scheduling PDSCH / PUSCH of multiple CCs using a single (1) DCI can be supported (Single DCI Multi-Cell PDSCH / PUSCH scheduling).

[0099] Figure 5 An example of a scheduling method that can be supported by the wireless communication system 10 is shown. Compared with the conventional method of preparing DCIs for each CC and scheduling them one by one, the single DCI multi-cell PDSCH / PUSCH scheduling (single DCI multi-carrier PDSCH / PUSCH scheduling) has the following characteristics.

[0100] • (Advantages): It can reduce the load (number of blind decodings (BD)) caused by DCI (PDCCH) monitoring. In addition, it can reduce the total PDCCH overhead (the smaller the size of a single DCI (Single DCI) is compared to the previous method of DCI×CC number, the more effective it is).

[0101] • (Disadvantages): It is impossible to modify the indication content for each CC in detail (if it were possible, the size of a single DCI would increase, and the error rate and overhead of the PDCCH would increase). If the PDCCH is faulty, the data reception of multiple CCs would fail.

[0102] Figure 6 This illustrates a PDSCH scheduling example based on Single DCI Multi-Cell PDSCH / PUSCH scheduling. As mentioned above, the DCI that uses a single (1) DCI to schedule PUSCH / PDSCH for multiple cells can be referred to as DCI format 0_X / 1_X (or DCI format 0_3 / 1_3).

[0103] DCI format 0_X / 1_X enables simultaneous scheduling of combinations of cells contained in a set of cells. The following requirements can be applied to the set of cells.

[0104] A set of cells consists of a maximum of 4 cells.

[0105] • Any cell is contained in a set of only one cell.

[0106] exist Figure 6 The example shown illustrates a set of cells 1 containing CC#1 / 2 / 3 / 4 and a set of cells 2 containing CC#5 / 6 / 7. The DCI formats of sets of cells 1 and 2 can be contained in different PDCCHs.

[0107] A cell that counts the DCI size, PDCCH candidate (BD) ratio, and CCE count can be called a reference cell. For each set of cells, a cell can be designated to count the DCI size, PDCCH candidate (BD) ratio, and CCE count for the PDCCHs of all cells included in that set. Figure 6 For example, the reference cell of set 1 can be set as CC#1, and the reference cell of set 2 can be set as CC#5. Here, the cell and CC can be interchanged.

[0108] In this case, the DCI size / PDCCH candidate (BD) / CCE number of the PDCCH (for set of cells 1) can be counted in CC#1. Furthermore, the DCI size / PDCCH candidate (BD) / CCE number of the PDCCH (for set of cells 2) can be counted in CC#5.

[0109] Figure 7 This example illustrates a notification of carrier indication parameters in Single DCI Multi-Cell PDSCH / PUSCH scheduling. For instance... Figure 7 As shown, the value of parameter n_CI (carrier indicator) used to determine the CCE index of the PDCCH can be set differently for each set of cells. Figure 7 The example shown is an example of setting n_CI = X in the initial PDCCH and setting n_CI = Y in the next PDCCH.

[0110] Regarding the framework of Single DCI Multi-Cell PDSCH / PUSCH scheduling as described above, it is necessary to study the configuration methods of the cells contained in the set of cells, the configuration methods and interpretations of the n_CI value of each set of cells, the configuration methods of the joint coding / encoding / indication table, the configuration methods of the fields contained in DCI format 0_X / 1_X (including the Configurable field), and the configuration of the search space (SS) for monitoring DCI format 0_X / 1_X, as well as other configurations related to the set of cells.

[0111] (3.2) Action Summary

[0112] The following action examples illustrate the framework of Single DCI Multi-Cell PDSCH / PUSCH scheduling, particularly the actions and regulations involved in the framework related to RRC settings.

[0113] The following action examples may include the following options.

[0114] •Opt.1: Set up Single DCI Multi-Cell PDSCH / PUSCH scheduling (a set of cells) for the scheduling cell and each scheduled cell.

[0115] Opt.2: Set up Single DCI Multi-Cell PDSCH / PUSCH scheduling (a set of cells) for at least one cell in the scheduling cell or the scheduled cell.

[0116] Specifically, it can include application examples that take parameters as objects, such as those described below.

[0117] • Application Example 1: Cells contained in a Set of cells

[0118] • Application Example 2: The value of n_CI for each set of cells

[0119] • Application Example 3: Joint coding / encoding / indication table for each set of cells

[0120] • Application Example 4: Configurable fields contained in the DCI format 0_X / 1_X of each set of cells

[0121] • Application Example 5: Presence of fields contained in the DCI format 0_X / 1_X of each cell set.

[0122] • Application Example 6: Monitoring the search space of DCI format 0_X / 1_X

[0123] Additionally, as mentioned above, DCI format 0_X / 1_X can also be replaced with DCI format 0_3 / 1_3. Furthermore, the name of the RRC parameter (IE, field) includes a temporary name and can also be referred to by other names.

[0124] (3.3) Example of an action

[0125] Figure 8 This example demonstrates a configuration example for Single DCI Multi-Cell PDSCH / PUSCH scheduling using the RRC parameters involved in Opt.1 of the action example.

[0126] like Figure 8As shown, information elements related to serving cell settings can be used. Specifically, settings related to Single DCI Multi-Cell PDSCH / PUSCH scheduling can be included in servingCellConfig / servingCellConfigCommon / PhysicalCellGroupConfig.

[0127] For example, such as Figure 8 As shown, MultiCellScheduling-SetId(1, 2) can be set in servingCellConfig. MultiCellScheduling-SetId can correspond to the set of cells(1, 2). Figure 8 As shown, MultiCellScheduling-SetId can be set for each CC (or cell).

[0128] Figure 9 This example demonstrates a configuration example for Single DCI Multi-Cell PDSCH / PUSCH scheduling using the RRC parameters involved in Opt.2 of the action example.

[0129] like Figure 9 As shown, in Opt.2, information elements related to serving cell settings can also be used. Specifically, settings related to Single DCI Multi-Cell PDSCH / PUSCH scheduling can be included in servingCellConfig / servingCellConfigCommon / PhysicalCellGroupConfig.

[0130] For example, such as Figure 9As shown, MultiCellScheduling-SetId(1, 2) can be set in servingCellConfig. MultiCellScheduling-SetId can contain ScheduledCell-ListDCI-0-X = {1, 2, 3, 4} / = {5, 6, 7}, which can correspond to the set of cells (1, 2). MultiCellScheduling-SetId can be set according to the set of cells for each cell.

[0131] exist Figure 9 The example shown illustrates how, in Set of cells 1, the reference cell is CC#1, and how this is configured. In Set of cells 2, the example shown illustrates how, the reference cell is CC#5, and how this is configured. Additionally, it can be configured as a scheduling cell or any other cell.

[0132] Furthermore, in Opt.2, the cell to be configured (which can be replaced by a cell applying Single DCI Multi-Cell PDSCH / PUSCH scheduling, hereinafter the same) can be a scheduling cell or a reference cell (a cell that is configured to monitor the scheduling cell or the DCI SS of DCI format 0_X / 1_X). Alternatively, it can be a scheduled cell other than a scheduling cell or a reference cell. Additionally, if the scheduling cell is included within a scheduled cell, it can also be designated as the scheduling cell.

[0133] Alternatively, you can set only a portion of the fields included in MultiCellScheduling-Set-Config, which are used as RRC parameters, for the scheduling cell / each scheduled cell, and set other fields for at least one of the scheduling cells / scheduled cells.

[0134] For example, MultiCellScheduling-SetId can be set for the scheduling cell / each scheduled cell. Other fields are not set except for specific cells.

[0135] In addition, a value of n_CI (temporary name) associated with the set of cells can be set for the scheduling cell / each scheduled cell, except for specific cells.

[0136] (3.4) Application Examples

[0137] (3.4.1) Application Example 1

[0138] As a method for defining the cells contained in a set of cells, in the case of Opt.1, any of the following can be applied.

[0139] • Opt. 1-1: Alternatively, the notification can be used as the ID of the set of cells, with the field MultiCellScheduling-SetId (temporary name) set for the scheduling cell / each scheduled cell (see [reference]). Figure 10 ).

[0140] Alternatively, other fields can be specified for UL / DL separately and set through these fields.

[0141] •Opt.1-2: Alternatively, the field nCI-Value (temporary name) can be specified to associate the notification with the set of cells. This field can be set for the scheduling cell / each scheduled cell.

[0142] Alternatively, other fields can be specified for UL / DL separately and set through these fields.

[0143] As a method for configuring cells within a set of cells, in Opt.2, the configuration field for the cells included in the set of multi-cell scheduling can be specified in servingCellConfig, and the configuration can be done through this field (see [reference]). Figure 11 ).

[0144] Alternatively, other fields can be specified for UL / DL and set through these fields (e.g., ScheduledCell-ListDCI-0-X / ScheduledCell-ListDCI-1-X).

[0145] The association between the Type-2 fields (FDRA (Frequency Domain Resource Allocation), HPN (HARQ Process Number), MCS (Modulation and Coding Scheme), RV (Redundancy Version), NDI (New-Data Indicator), TPC (Transmit Power Control) command for scheduled PUSCH, and PTRS-DMRS association) contained in DCI format 0_X / 1_X and the cells contained in the set of cells can be in any of the following manner.

[0146] • Alt.1: (Starting from the MSB / LSB of this DCI field) The cell order set by ScheduledCell-ListDCI-0-X / ScheduledCell-ListDCI-1-X, etc., as RRC parameters.

[0147] • Alt.2: (Starting from the MSB / LSB of this DCI field) Sets the order (ascending or descending) of the indexes of cells included in the same set in the RRC.

[0148] • Alt.3: (Starting from the MSB / LSB of this DCI field) Sets the order (ascending or descending) of the indexes of cells simultaneously scheduled using DCI.

[0149] (3.4.2) Application Example 2

[0150] As a method for setting the value of n_CI for each set of cells, in the case of Opt.1, it is possible to specify the field of n_CI-Value (temporary name) associated with the set of cells, and set this field for the scheduling cell / each scheduled cell (same as Alt.2 above).

[0151] As a method for setting the value of n_CI for each set of cells, in the case of Opt.2, the setting of the set of cells for multi-cell scheduling can be specified in the field MultiCellScheduling-Set-Config in servingCellConfig, and the value of n_CI, nCI-Value, can be set in this field.

[0152] Furthermore, the interpretation of the value notified by the RRC parameter nCI-Value can be done according to any of the following methods.

[0153] • Alt.1: This is interpreted as the value used in the CCE index calculation being notified by nCI-Value, specifying and notifying the association between nCI-Value and the value notified by the set of cell indicators contained in DCI format 0_X / 1_X.

[0154] In addition, regarding the range of possible values, any of the following can be applied.

[0155] • Alt.1-1: Notifies any value from 0 to 11 (this is an example, but it can be any other value).

[0156] RRC can be used to set the association with values ​​notified by the set of cell indicators.

[0157] • Alt.1-2: Imagine that in cross-carrier scheduling within a single cell, 0-7 are assigned to n_CI (maximum), and any value from 8-11 (this is an example, but other values ​​could also be used) is notified.

[0158] The value notified by the set of cell indicators can be set to nCI-Value-8.

[0159] • Alt.1-3: In cross-carrier scheduling within a single cell, if the actual value of n_CI is set to be between 0 and X (X≥0), notify any value from X+1 to 11 (this is an example, but other values ​​are also possible).

[0160] The value notified by the set of cell indicators can be set to nCI-Value-(X+1).

[0161] • Alt.2: The difference between the n_CI value and the maximum value of n_CI for cross-carrier scheduling for a single cell is provided by nCI-Value, and this value is directly interpreted as the value provided by the set of cell indicators within DCI format 0_X / 1_X.

[0162] The possible values ​​for nCI-Value can be 0 to 3. Furthermore, the n_CI value used to calculate the CCE index of the set of cells can be any of the following.

[0163] • Alt.2-1: Imagine that in cross-carrier scheduling within a single cell, 0 to 7 are allocated to n_CI (maximum), denoted as 8 + nCI - Value.

[0164] • Alt.2-2: In cross-carrier scheduling within a single cell, if the actual value of n_CI is set to be between 0 and X (X≥0), notify any value from X+1 to 11 (this is an example, but other values ​​are also possible).

[0165] (3.4.3) Application Example 3

[0166] As a method for setting the joint coding / encoding / indication table for each set of cells, the following components included in DCI format 0_X / 1_X—TDRA / rate matching indicator / ZP (Zero Power)-CSI-RS trigger / TCI (Transmission Configuration Indication) / SRS request / SRS offset indicator / co-scheduled cell indicator—can be applied to at least any one of the joint coding tables for notification code points. Figure 10 , Figure 11 Opt.1 / Opt.2 as shown (described later).

[0167] As an RRC field, the following fields can be examples (which can be temporary names).

[0168] ·Joint-TDRA-ListDCI-1-X, Joint-TDRA-ListDCI-0-X, Joint-RateMatchIndication-ListDCI-1-X, Joint-ZP-CSI-RS-Trigger-ListDCI-1-X, Joint-TCI-ListDCI-1-X, Joint-SRS-Request-ListDCI-1-X, Joint-SRS-OffsetIndicator-ListDCI-1-X, Joint-SRS-Request-ListDCI-0-X, Joint-SRS-OffsetIndicator-ListDCI-0-X. ScheduledCellCombo-ListDCI-1-X, ScheduledCellCombo-ListDCI-0-X

[0169] Furthermore, in the absence of a co-scheduled cell combination table, it is conceivable that the co-scheduled cell indicator is not included in the DCI format 0_X / 1_X, and the value notified by the co-scheduled cell indicator can also be ignored.

[0170] Figure 10 This shows an example of the joint coding / encoding / indication table configuration (Opt. 1) for Single DCI Multi-Cell PDSCH / PUSCH scheduling. Figure 10 As shown, in Opt.1, this field can be set for the scheduling cell / each scheduled cell, and an association can be established with the set of cells based on the Set of cells ID and / or n_CI value set for each cell.

[0171] Figure 11 This shows an example of the joint coding / encoding / indication table configuration (Opt. 2) for Single DCI Multi-Cell PDSCH / PUSCH scheduling. Figure 11 As shown, in Opt.2, the fields for setting the joint coding table can be specified in MultiCellScheduling-Set-Config, and the joint coding / encoding / indication table can be set through these fields.

[0172] (3.4.4) Application Example 4

[0173] As a method for setting the configuration field contained in the DCI format 0_X / 1_X of each set of cells, any one of the following can be applied to at least any one of the configuration fields Antenna port, precoding information and number of layers, and SRS resource indicator.

[0174] In Opt.1, the type of the notification configuration field (RRC field) can be set for the scheduling cell / each scheduled cell, and an association can be established with the Set of cells ID based on the Set of cells ID and / or n_CI value set for each cell.

[0175] In Opt.2, the type of the notification configuration field can be set in the RRC field of MultiCellScheduling-Set-Config, and the setting can be done through this field.

[0176] As an RRC field, the following fields can be examples (which can be temporary names).

[0177] ·AntennaPort-TypeDCI-1-X, AntennaPort-TypeDCI-0-X, PrecodingInfo-NrofLayers-TypeDCI-0-X, SRS-ResourceIndicator-TypeDCI-0-X

[0178] (3.4.5) Application Example 5

[0179] As a method for setting the presence of fields included in the DCI format 0_X / 1_X for each set of cells, any one of the following can be applied to at least one of the following fields that can be set to be included in the DCI format 0_X / 1_X: field priority indicator, SCell dormancy, PDCCH monitoring adaptation, minimum applicable offset, enhanced Type-3 codebook indicator, HARQ-ACK retransmission indicator, and PUCCH cell indicator.

[0180] In Opt.1, a set of RRC fields can be set to notify the existence of the DCI field for the scheduling cell / each scheduled cell, and an association can be established with the set of cells based on the Set of cells ID and / or n_CI value set for each cell.

[0181] In Opt.2, the RRC field that notifies the existence of the DCI field can be specified in MultiCellScheduling-Set-Config, and the settings can be configured through this field.

[0182] As an RRC field, the following fields can be examples (which can be temporary names).

[0183] ・PriorityIndicator-PresenseDCI-1-X, PriorityIndicator-PresenseDCI-0-X. ScellDormancy-PresenseDCI-1-X, ScellDormancy-PresenseDCI-0-X, PDCCHMonitorAdaptation_PresenseDCI-1-X, PDCCHMonitorAdaptation_PresenseDCI-0-X, MinApplicableSchedulingOffset_PresenseDCI-1-X,MinApplicableSchedulingOffset_PresenseDCI-0-X

[0184] (3.4.6) Application Example 6

[0185] It specifies the search space (SS) for monitoring DCI format 0_X / 1_X in the scheduling cell, or in both the scheduling cell and the reference cell.

[0186] When the search space is set in the reference cell, all fields included in the search space can be absent except for searchspace Id and norofcandidate (number of PDCCH candidates per aggregation level).

[0187] In addition, cells that also have fields other than searchspace ID and norofcandidate can be interpreted as scheduling cells.

[0188] (4) Functions and Effects

[0189] According to the above implementation method, the following effects can be obtained. As described above, when applying Single DCI Multi-Cell PDSCH / PUSCH scheduling, Single DCI Multi-Cell PDSCH / PUSCH scheduling (a set of cells) can be set for both the scheduling cell and each scheduled cell (Opt.1). Alternatively, Single DCI Multi-Cell PDSCH / PUSCH scheduling (a set of cells) can be set for at least any one of the scheduling cell or scheduled cells (Opt.2). Furthermore, UE 200 can determine which option to apply based on information elements (which may include fields) contained in the RRC message or based on prior settings.

[0190] Therefore, even when using Single DCI Multi-Cell PDSCH / PUSCH scheduling to schedule multiple cells simultaneously, UE 200 can still execute appropriate settings.

[0191] In this embodiment, UE 200 can also perform settings related to multiple cells based on the DCI (DCI format 0_X / 1_X) or the carrier indication (CI) field associated with a combination of multiple cells contained in the RRC message, or the ID of the set of cells. Therefore, efficient cell settings can be achieved using Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0192] (5) Other implementation methods

[0193] The above describes the embodiments, but the present invention is not limited to the embodiments described therein, and various modifications and improvements can be made, which will be obvious to those skilled in the art.

[0194] For example, in the above embodiments, the terms "single DCI multi-slot PDSCH / PUSCH scheduling" and "single DCI multi-cell PDSCH / PUSCH scheduling" were used in the description. However, these terms can be used as long as they refer to the function of scheduling multiple time slots of PDSCH / PUSCH using one DCI or the function of scheduling multiple CCs of PDSCH / PUSCH using a single (1) DCI. Furthermore, as mentioned above, the channel is not limited to PDSCH / PUSCH; control channels and / or other data channels can also be considered.

[0195] Furthermore, in the above description, the terms configure, activate, update, indicate, enable, specify, and select can be interchanged. Similarly, the terms link, associate, correspond, and map can be interchanged, as can allocate, assign, monitor, and map.

[0196] Furthermore, specific, dedicated, UE specific, and UE dedicated can be used interchangeably. Similarly, common, shared, group-common, UE common, and UE shared can also be used interchangeably.

[0197] The block structure diagram used in the above description of the embodiments ( Figure 4 The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within the aforementioned single or multiple devices.

[0198] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0199] Furthermore, the aforementioned gNB 100 and UE 200 (the device) can also function as a computer for processing the wireless communication method disclosed herein. Figure 12 This is a diagram illustrating an example of the hardware structure of the device. (As shown...) Figure 12 As shown, the device can also be configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0200] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of this device can be configured as either a device comprising one or more of the illustrated components, or a device without any components.

[0201] The functional blocks of the device (refer to) Figure 4 This can be achieved through any hardware element or combination of hardware elements in the computer device.

[0202] Furthermore, the functions of the device are implemented by reading predetermined software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication of communication device 1004 or controls at least one of reading and writing data in memory 1002 and storage device 1003.

[0203] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc.

[0204] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one direction of memory 1002 in the storage device 1003 and the communication device 1004, and performs various processes accordingly. The program is used to cause the computer to perform at least a portion of the actions described in the above embodiments. Moreover, the various processes described above can be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 can also be implemented using one or more chips. Additionally, the program can be transmitted from a network via a telecommunications line.

[0205] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and random access memory (RAM). The memory 1002 may be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 may store programs (program code), software modules, etc., capable of executing the methods according to an embodiment of this disclosure.

[0206] Storage device 1003 is a computer-readable recording medium, and may be composed of at least one of the following: optical discs such as CD-ROM (Compact Disc ROM), hard disk drives, floppy disks, magneto-optical discs (e.g., compact discs, digital multipurpose discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. Storage device 1003 may also be referred to as an auxiliary storage device. The aforementioned recording medium may, for example, be a database, server, or other suitable media that includes at least one of memory 1002 and storage device 1003.

[0207] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network, and is also known as a network device, network controller, network card, communication module, etc.

[0208] The communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0209] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0210] Furthermore, devices such as processor 1001 and memory 1002 are connected via bus 1007 for communicating information. Bus 1007 can be configured as a single bus or as different buses between devices.

[0211] Furthermore, the device can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), which can be used to implement some or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0212] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0213] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (x being, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The system may include at least one of 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on these systems. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0214] The processing procedures, timing, and flow of the various forms / implementations described in this disclosure may be changed in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order in the methods described in this disclosure, but are not limited to the specific order indicated.

[0215] In this disclosure, certain actions performed by the base station are sometimes also performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having a base station, it is obvious that various actions performed to communicate with a terminal can be performed by at least one of the base station and other network nodes besides the base station (e.g., considering an MME or S-GW, but not limited to these). The above illustration depicts a case where there is only one other network node besides the base station, but it can also be a combination of multiple other network nodes (e.g., an MME and an S-GW).

[0216] It can output information and signals (information, etc.) from a higher (or lower) level to a lower (or higher) level. It can also input and output through multiple network nodes.

[0217] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0218] The determination can be made by the value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparing numerical values ​​(e.g., comparing with a predetermined value).

[0219] The various forms / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information (e.g., a "It is X" notification) is not limited to being explicit, but can also be implicit (e.g., not being notified of the predetermined information).

[0220] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0221] Furthermore, software, commands, and information can be sent and received via a transmission medium. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0222] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description as a whole can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0223] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0224] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0225] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may be indicated using indexes.

[0226] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters may sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any appropriate name, and therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0227] In this disclosure, the terms "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0228] A base station can accommodate one or more (e.g., three) cells (also called sectors). 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 the base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0229] Terms such as “cell” or “sector” refer to a portion or the entire coverage area of ​​at least one of the base stations and base station subsystems that provide communication services within that coverage area.

[0230] In this disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal on information-based control / actions.

[0231] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.

[0232] For mobile stations, those skilled in the art sometimes also use the following terms: 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 terms.

[0233] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Additionally, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0234] Furthermore, the base station in this disclosure can also be replaced by a mobile station (user terminal, hereinafter the same). For example, various forms / implementations of this disclosure can also be applied to structures that replace communication between the base station and the mobile station with communication between multiple mobile stations (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the structure can also be configured such that the mobile station has the functions of the base station. In addition, terms such as "uplink" and "downlink" can also be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel (or side link).

[0235] Similarly, the mobile station in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of a mobile station.

[0236] A radio frame can consist of one or more frames in the time domain. In the time domain, one or more frames can be called subframes. A subframe can also consist of one or more time slots in the time domain. A subframe can be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0237] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

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

[0239] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0240] 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 can each be referred to by other corresponding names.

[0241] For example, a single subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a single time slot or a single mini-time slot can also be called a TTI. In other words, at least one of the subframe and TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., symbols 1-13), or a period longer than 1ms. Furthermore, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0242] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0243] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than the TTI.

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

[0245] A TTI with a duration of 1ms can also be called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0246] Additionally, for long TTIs (e.g., normal TTIs, subframes, etc.), a TTI with a duration of more than 1ms can be used as a replacement. For short TTIs (e.g., shortened TTIs, etc.), a TTI with a duration of more than 1ms but shorter than the long TTI can be used as a replacement.

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

[0248] Furthermore, the temporal domain of an RB can contain one or more symbols, which can be a single time slot, a single mini-time slot, a single subframe, or the length of a single TTI. A single TTI, a single subframe, etc., can each be composed of one or more resource blocks.

[0249] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0250] Furthermore, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.

[0251] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a given carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0252] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.

[0253] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive predetermined signals / channels outside of the active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0254] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc., can be varied in many ways.

[0255] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, they are “connected” or “coupled” to each other using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (both visible and invisible) region.

[0256] The reference signal can be simply called the Reference Signal (RS), or, depending on the standard applied, the pilot signal.

[0257] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".

[0258] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0259] Any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to "first" and "second" elements do not imply that only two elements can be used there, or that in some form the first element must precede the second element.

[0260] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0261] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may include cases where the noun following these articles is in a plural form.

[0262] As used in this disclosure, terms such as "determining" and "determining" sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in storage), which are considered as actions of "determining" or "determining." Additionally, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0263] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Additionally, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0264] Figure 13 An example of the structure of vehicle 2001 is shown. For example... Figure 13 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0265] The drive unit 2002 may be composed of, for example, an engine, a motor, or a hybrid powertrain of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel), configured to steer at least one of the front and rear wheels based on user-operated steering wheel movements. The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 present in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be referred to as an ECU (Electronic Control Unit).

[0266] The signals from various sensors 2021 to 2028 include current signals from current sensor 2021 that senses the current of the motor, speed signals of the front and rear wheels obtained by speed sensor 2022, air pressure signals of the front and rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal input signals obtained by accelerator pedal sensor 2029, brake pedal input signals obtained by brake pedal sensor 2026, gear lever operation signals obtained by gear lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0267] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via communication modules 2013, etc., to provide various multimedia information and multimedia services to the occupants of vehicle 1.

[0268] The Information Services Department 2012 may include input devices that accept input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that implement output to external sources (e.g., monitor, speaker, LED light, touch panel, etc.).

[0269] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

[0270] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 1 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2028 in the vehicle 2001 via the communication port 2033.

[0271] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0272] The communication module 2013 can wirelessly transmit to an external device at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2028, information obtained based on those signals, and information obtained via the information service unit 2012 based on input from an external source (user). The electronic control unit 2010, the various sensors 2021-2028, and the information service unit 2012 can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 can contain information based on the aforementioned input.

[0273] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 provided by the vehicle. The information service unit 2012 can also be referred to as an output unit for outputting information (for example, outputting information to devices such as displays and speakers based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH). In addition, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, etc., provided by the vehicle 2001 based on the information stored in the memory 2032.

[0274] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0275] (Postscript)

[0276] The above disclosure can also be expressed as follows. The first feature is a terminal comprising: a receiving unit that receives a single downlink control information indicating scheduling of a combination of multiple cells; and a control unit that assumes that the scheduling cell receiving the downlink control information and the scheduled cell indicated by the downlink control information are the multiple cells to be scheduled.

[0277] The second feature is that, in the first feature, the receiving unit receives a message from the radio resource control layer, and the control unit, based on information elements related to the setting of the serving cell contained in the message, envisions the multiple cells as objects.

[0278] The third feature is that, in the first or second feature, the receiving unit receives a message from the radio resource control layer, and the control unit performs settings related to the multiple cells based on the identification information of the combination of the multiple cells contained in the message.

[0279] The fourth feature is that, in features 1 to 3, the control unit performs settings related to the multiple cells based on a carrier indication field included in the downlink control information that is associated with the combination of the multiple cells.

[0280] The fifth feature is that, in features 1 to 4, the control unit performs settings related to the plurality of cells based on the message that sets fields for the scheduled cell and the scheduled cell respectively.

[0281] The sixth feature is a terminal comprising: a receiving unit that receives a single downlink control information indicating scheduling for a combination of multiple cells; and a control unit that envisions applying the scheduling to at least one of the scheduling cell receiving the downlink control information and the scheduled cell indicated by the downlink control information.

[0282] The seventh feature is that, in the sixth feature, the control unit envisions applying the scheduling to the scheduling cell or a reference cell in a search space configured to monitor the downlink control information.

[0283] The eighth feature is that, in the sixth or seventh feature, the receiving unit receives a message from the radio resource control layer, and the control unit performs settings related to the serving cell settings contained in the message.

[0284] The ninth feature is that, in features 6 to 8, the control unit performs settings related to the cell for which the scheduling is applied, based on the carrier indication field included in the information element.

[0285] The 10th feature is that, in features 6 to 9, the control unit performs settings related to the cells to which the scheduling is applied, based on the message that sets fields for the combination of the plurality of cells.

[0286] Label Explanation

[0287] 10: Wireless Communication System

[0288] 20: NG-RAN

[0289] 100: gNB

[0290] 200:UE

[0291] 210: Wireless Signal Transceiver Unit

[0292] 220: Amplifier Section

[0293] 230: Modulation and Demodulation Section

[0294] 240: Control Signal & Reference Signal Processing Unit

[0295] 250: Encoding / Decoding Section

[0296] 260: Data Transceiver Department

[0297] 270: Control Department

[0298] 1001: Processor

[0299] 1002: Memory

[0300] 1003: Storage device

[0301] 1004: Communication device

[0302] 1005: Input device

[0303] 1006: Output device

[0304] 1007: Bus

[0305] 2001: Vehicles

[0306] 2002: Drive Unit

[0307] 2003: Steering Unit

[0308] 2004: Accelerator Pedal

[0309] 2005: Brake Pedal

[0310] 2006: Gear Shift

[0311] 2007: Left and right front wheels

[0312] 2008: Left and right rear wheels

[0313] 2009: Axle

[0314] 2010: Electronic Control Department

[0315] 2012: Information Services Department

[0316] 2013: Communication Module

[0317] 2021: Current Sensor

[0318] 2022: Speed ​​Sensor

[0319] 2023: Barometric Pressure Sensor

[0320] 2024: Vehicle Speed ​​Sensor

[0321] 2025: Accelerometer

[0322] 2026: Brake Pedal Sensor

[0323] 2027: Gearshift Sensor

[0324] 2028: Object Detection Sensor

[0325] 2029: Accelerator Pedal Sensor

[0326] 2030: Driver Assistance Systems Department

[0327] 2031: Microprocessors

[0328] 2032: Memory (ROM, RAM)

[0329] 2033: Communication Port

Claims

1. A terminal, comprising: The receiving unit receives single downlink control information indicating scheduling of combinations of multiple cells; and The control unit envisions applying the scheduling to at least one of the scheduling cells that receive the downlink control information and the scheduled cells indicated by the downlink control information.

2. The terminal according to claim 1, wherein, The control unit envisions applying the scheduling to the scheduling cell or to a reference cell in a search space configured to monitor the downlink control information.

3. The terminal according to claim 1, wherein, The receiving unit receives messages from the radio resource control layer. The control unit executes settings related to the serving cell that are being scheduled, based on information elements contained in the message.

4. The terminal according to claim 3, wherein, The control unit performs settings related to the cell for which the scheduling is applied, based on the carrier indication field contained in the information element.

5. The terminal according to claim 3, wherein, The control unit executes settings related to the cells to which the scheduling is applied, based on the message that sets fields for the combination of the multiple cells.

6. A wireless communication method in a terminal, comprising the following steps: Receive a single downlink control message indicating scheduling for a combination of multiple cells; and Imagine applying the scheduling to at least one of the scheduling cell that receives the downlink control information and the scheduled cell indicated by the downlink control information.

Images