Terminal and wireless communication method
The proposed terminal and wireless communication method addresses the challenge of monitoring and scheduling DCI across multiple cells by reporting UE capability, optimizing DCI monitoring and reducing load, thereby enhancing data transmission reliability in Single DCI Multi-Cell PDSCH/PUSCH scheduling.
Patent Information
- Application Number
- PCT/JP2024/018180
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-16
- Publication Date
- 2024-11-28
AI Technical Summary
The existing wireless communication systems face challenges in efficiently monitoring and scheduling Downlink Control Information (DCI) across multiple cells using Single DCI Multi-Cell PDSCH/PUSCH scheduling, particularly due to limitations in UE capability reporting and potential increased DCI load, which can impact data reception across multiple component carriers.
A terminal and wireless communication method that transmits terminal capability information regarding scheduling for multiple cells using a single downlink control information, allowing for appropriate DCI monitoring by reporting whether existing DCI formats can be simultaneously monitored, depending on whether the scheduled cell is a reference cell or not, thereby optimizing DCI monitoring and scheduling.
Enables efficient DCI monitoring and scheduling even when Single DCI Multi-Cell PDSCH/PUSCH scheduling is introduced, ensuring appropriate channel allocation and reducing DCI load, thus improving data transmission reliability across multiple cells.
Smart Images

Figure JP2024018180_28112024_PF_FP_ABST
Abstract
Description
Terminal and wireless communication method
[0001] The present disclosure relates to a terminal and a wireless communication method that support a mechanism for scheduling data channels transmitted by multiple carriers using single downlink control information transmitted by a specific carrier.
[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.
[0003] In 3GPP Release 18, the introduction of a function for scheduling PDSCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted by multiple component carriers (CCs) using single downlink control information (DCI) is being considered (see Non-Patent Document 1). Such a function is called single DCI multi-carrier PDSCH / PUSCH scheduling or single DCI multi-cell PDSCH / PUSCH scheduling (hereinafter referred to as single DCI multi-cell PDSCH / PUSCH scheduling).
[0004] Furthermore, in order to support such single DCI multi-cell PDSCH / PUSCH scheduling, a single DCI format (which may be called DCI format 0_3 / 1_3, etc.) capable of scheduling PDSCH / PUSCH for multiple cells has been agreed upon (Non-Patent Document 2).
[0005] Furthermore, a method of reporting the capability of a terminal (User Equipment, UE) regarding Single DCI Multi-Cell PDSCH / PUSCH scheduling to a network has also been studied (Non-Patent Document 3).
[0006] "New WID on Multi-carrier enhancements", RP-213577, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 "RAN1 Chair's Notes", RAN1 Chair's Notes, 3GPP, May 2022 "Initial RAN1 UE features list for Rel-18 NR after RAN1#112bis-e", R1-2304282, 3GPP TSG RAN WG1 #112bis-e, 3GPP, April 2023
[0007] In single DCI multi-cell PDSCH / PUSCH scheduling, one cell is configured to count the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH that schedules the cells of each set of cells for each combination of multiple cells by the DCI. The cell that counts the DCI size / PDCCH candidate (BD) / number of CCEs is called a reference cell, and the reference cell is notified by a higher layer parameter (search space) configuration.
[0008] However, in a cell that monitors DCI formats 0_3 / 1_3, whether or not existing DCI formats can be simultaneously monitored may vary depending on the UE capability.
[0009] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a terminal and a radio communication method that can realize appropriate DCI monitoring even when Single DCI Multi-Cell PDSCH / PUSCH scheduling is introduced.
[0010] One aspect of the present disclosure is a terminal (UE200) that includes a transmitter (control signal / reference signal processor 240) that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information, and a controller (controller 270) that causes the transmission of the terminal capability information including whether or not the downlink control information and existing downlink control information other than the downlink control information can be simultaneously monitored.
[0011] The terminal (UE200) includes a transmitter (control signal / reference signal processor 240) that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information, and a controller (controller 270) that transmits the terminal capability information including whether or not simultaneous monitoring of the downlink control information and the existing downlink control information is possible, depending on whether or not a cell scheduled by existing downlink control information other than the downlink control information is a reference cell.
[0012] FIG. 1 is a diagram illustrating an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram illustrating frequency bands used in the wireless communication system 10. FIG. 3 is a diagram illustrating an example configuration of radio frames, subframes, and slots used in the wireless communication system 10. FIG. 4 is a functional block configuration diagram of a gNB 100 and a UE 200. FIG. 5 is a diagram illustrating an example of a scheduling method that can be supported by the wireless communication system 10. FIG. 6 is a diagram illustrating an example of PDSCH scheduling according to Single DCI Multi-Cell PDSCH / PUSCH scheduling. FIG. 7 is a diagram illustrating an example (part 1) of a relationship between a cell scheduled by DCI and a reference cell according to an operation example 2. FIG. 8 is a diagram illustrating an example (part 1) of a relationship between a cell scheduled by DCI and a reference cell according to an operation example 2. FIG. 9 is a diagram illustrating an example of the hardware configuration of a gNB 100 and a UE 200. FIG. 10 is a diagram illustrating an example of the configuration of a vehicle 2001.
[0013] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.
[0014] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).
[0015] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.
[0016] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1 .
[0017] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."
[0018] The gNB100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO, which generates highly directional beams by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and multiple NG-RAN nodes.
[0019] The type of DC may be Multi-RAT Dual Connectivity (MR-DC) that uses multiple radio access technologies, or NR-NR Dual Connectivity (NR-DC) that uses only NR. MR-DC may also be E-UTRA-NR Dual Connectivity (EN-DC) in which the eNB constitutes the master node (MN) and the gNB constitutes the secondary node (SN), or vice versa, NR-E-UTRA Dual Connectivity (NE-DC).
[0020] The wireless communication system 10 may also support multiple frequency ranges (FR).
[0021] FR1: 410 MHz to 7.125 GHz FR2: FR2-1: 24.25 GHz to 52.6 GHz FR2-2: Over 52.6 GHz to 71 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1 and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.
[0022] Furthermore, the wireless communication system 10 may also support frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz up to 114.25 GHz.
[0023] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied, and DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).
[0024] FIG. 3 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10.
[0025] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 (e.g., 28 or 56 symbols). The number of slots per subframe may also vary depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz or 960 kHz, as shown in Figure 3).
[0026] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block (RB), a resource block group (RBG), a subcarrier, a BWP (Bandwidth part), etc.
[0027] As described above, the wireless communication system 10 may have an extended function related to multiple carriers (specifically, CCs). Specifically, the wireless communication system 10 may support a function (single DCI multi-slot PDSCH / PUSCH scheduling) for scheduling PDSCHs (Physical Downlink Shared Channels) / PUSCHs (Physical Uplink Shared Channels) transmitted in multiple slots using single DCI (Downlink Control Information).
[0028] Specifically, the wireless communication system 10 may support a scheduling method (self-carrier scheduling) in which the scheduling DCI and the channel to be scheduled are the same CC, a cross-carrier scheduling method (cross carrier scheduling) in which scheduling of channels spanning multiple CCs is applied, and a single DCI (single DCI), i.e., a scheduling method (multi-carrier scheduling) in which channels are assigned to multiple different CCs by one DCI.
[0029] More specifically, the wireless communication system 10 may support a function of scheduling PDSCH / PUSCHs transmitted by multiple CCs using a single DCI (single DCI multi-carrier PDSCH / PUSCH scheduling or single DCI multi-cell PDSCH / PUSCH scheduling). Hereinafter, this function will be referred to as single DCI multi-cell PDSCH / PUSCH scheduling.
[0030] Only one of single DCI multi-slot PDSCH / PUSCH scheduling and single DCI multi-cell PDSCH / PUSCH scheduling can be used, and both do not necessarily have to be used simultaneously, but the wireless communication system 10 may support simultaneous use of both.
[0031] Furthermore, in order to support such Single DCI Multi-Cell PDSCH / PUSCH scheduling, the wireless communication system 10 may use a single DCI format (which may be called DCI format 0_3 / 1_3, etc.) that can schedule the PDSCH / PUSCH of multiple cells. By using DCI conforming to this DCI format, it becomes possible to simultaneously schedule multiple cells included in a set of multiple cells (set of cells).
[0032] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described. Fig. 4 is a functional block configuration diagram of the gNB 100 and the UE 200.
[0033] As shown in FIG. 4 , the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.
[0034] It should be noted that Fig. 4 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the UE 200, and for the hardware configuration, please refer to Fig. 11.
[0035] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.
[0036] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.
[0037] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).
[0038] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .
[0039] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.
[0040] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).
[0041] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.
[0042] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.
[0043] The channels include a control channel and a data channel. The control channels may include a Physical Downlink Control Channel (PDCCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.
[0044] Furthermore, the data channel includes a PDSCH, a PUSCH, etc. Data may refer to data transmitted via a data channel.
[0045] The control signal and reference signal processor 240 can receive downlink control information (DCI) transmitted from the network. Specifically, the control signal and reference signal processor 240 can receive DCI according to the DCI format defined in 3GPP TS38.212. In particular, in this embodiment, it can receive UL and DL scheduling DCI. More specifically, the control signal and reference signal processor 240 may receive DCI according to DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2.
[0046] Furthermore, in this embodiment, the control signal and reference signal processing unit 240 may receive DCI in accordance with DCI formats 0_3 and 1_3 for Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0047] DCI formats 0_0, 0_1, 0_2, and 0_3 may be interpreted as UL scheduling grants, and DCI formats 1_0, 1_1, 1_2, and 1_3 may be interpreted as DL scheduling assignments.
[0048] Control signal and reference signal processing unit 240 may receive DCI corresponding to single DCI multi-slot PDSCH / PUSCH scheduling and DCI corresponding to single DCI multi-cell PDSCH / PUSCH scheduling.
[0049] Specifically, for single DCI multi-slot PDSCH / PUSCH scheduling, the control signal and reference signal processor 240 can receive a single DCI that schedules channels transmitted by multiple slots. Also, for single DCI multi-cell PDSCH / PUSCH scheduling, the control signal and reference signal processor 240 can receive a single DCI that schedules channels transmitted by multiple carriers.
[0050] Here, the channel may include the above-mentioned control channel and data channel, and may not be particularly limited to the uplink and downlink directions, but may typically mean at least one of PDSCH and PUSCH. The carrier may mean a component carrier (CC), but may also be simply interpreted as a carrier or subcarrier.
[0051] Furthermore, the control signal and reference signal processor 240 may transmit to the network capability information of the UE 200. In particular, in this embodiment, the control signal and reference signal processor 240 can transmit UE capability information (terminal capability information, see FIG. 1 ) related to scheduling to the gNB 100.
[0052] The control signal and reference signal processor 240 may transmit terminal capability information including terminal capability (UE Capability) related to scheduling of the UE 200. In this embodiment, the control signal and reference signal processor 240 may constitute a transmitter.
[0053] The control signal and reference signal processing unit 240 can transmit terminal capability information related to scheduling for a combination of multiple cells (Set of cells) using DCI (format 0_3 / 1_3) for Single DCI Multi-Cell PDSCH / PUSCH scheduling. Details of the terminal capability included in the terminal capability information will be described later, and the information may include terminal capabilities related to the number of scheduling cells to which the DCI is transmitted and / or the number of scheduled cells to be scheduled by the DCI.
[0054] Furthermore, control signal and reference signal processor 240 may report the terminal capability information each time it is used in a scheduling cell and a scheduled cell.
[0055] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).
[0056] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.
[0057] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).
[0058] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 controls transmission or reception of a channel (for example, PDSCH / PUSCH, the same applies hereinafter) based on DCI for single DCI multi-slot PDSCH / PUSCH scheduling.
[0059] Furthermore, control unit 270 controls transmission or reception of channels based on DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0060] In this way, control unit 270 may control transmission or reception of channels based on at least one of DCI for single DCI multi-slot PDSCH / PUSCH scheduling and DCI for single DCI multi-cell PDSCH / PUSCH scheduling. Furthermore, single DCI multi-slot PDSCH / PUSCH scheduling and single DCI multi-cell PDSCH / PUSCH scheduling may be used simultaneously, and control unit 270 may perform control based on both scheduling DCIs simultaneously in parallel.
[0061] The control unit 270 may apply different settings to at least one of the cell, slot, or channel scheduled by the DCI for single DCI multi-slot PDSCH / PUSCH scheduling and the DCI for single DCI multi-cell PDSCH / PUSCH scheduling. The cell type (primary cell (PCell), primary / secondary cell (PSCell), and secondary cell (SCell)) may not be particularly limited, and a cell group (master or secondary) may be targeted. The channel type is also not particularly limited, and may be either the uplink or downlink direction, but the PDSCH / PUSCH may be targeted here.
[0062] Note that multiple cells that are simultaneously scheduled by the DCI may be called co-scheduled cells.
[0063] Furthermore, control unit 270 can transmit terminal capability information including whether or not DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling and existing downlink control information (DCI) other than the DCI can be simultaneously monitored. As described above, DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling may be interpreted as DCI format 0_3 / 1_3. Existing DCI may be interpreted as DCI of DCI format 0_3 / 1_3, for example, at least one of DCI 0_0 / 1_0 / 1_0 / 1_1 / 0_2 / 1_2.
[0064] Alternatively, control unit 270 may cause the terminal capability information including whether or not the DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling and the existing DCI can be simultaneously monitored, depending on whether or not a cell scheduled by existing downlink control information (DCI) other than the DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling is a reference cell.
[0065] The control unit 270 may transmit terminal capability information including whether or not existing DCI set in a common search space (CSS) or a search space (USS) specific to the UE 200 and DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling can be simultaneously monitored.
[0066] Furthermore, the gNB 100 may have a function corresponding to the above-mentioned UE 200. Specifically, the gNB 100 (control signal / reference signal processing unit 240) may be configured with a transmitter that transmits downlink control information instructing scheduling for a combination of multiple cells, and a receiver that receives terminal capability information related to scheduling from the UE 200.
[0067] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to efficient UE capability reporting even when Single DCI Multi-Cell PDSCH / PUSCH scheduling is introduced.
[0068] (3.1) Assumptions and Issues As described above, the wireless communication system 10 may support a function of scheduling PDSCH / PUSCH of multiple CCs using a single (one) DCI (Single DCI Multi-Cell PDSCH / PUSCH scheduling).
[0069] 5 shows an example of a scheduling method that can be supported by the wireless communication system 10. Single DCI Multi-Cell PDSCH / PUSCH scheduling (Single DCI Multi-carrier PDSCH / PUSCH scheduling) has the following features compared to a conventional method in which DCI is prepared for each CC and scheduled one by one.
[0070] ・(Advantages): The load (number of blind decodes (BD)) caused by monitoring DCI (PDCCH) can be reduced. Also, the total PDCCH overhead can be reduced (the smaller the size of the single DCI is compared to the conventional DCI x number of CCs, the more effective it is). ・(Disadvantages): The instructions cannot be changed in detail for each CC (if this were possible, the size of the single DCI would increase, and the PDCCH error rate and overhead would increase). If there is an error in the PDCCH, data reception across multiple CCs will fail.
[0071] 6 shows an example of PDSCH scheduling using single DCI multi-cell PDSCH / PUSCH scheduling. As described above, DCI that schedules PUSCH / PDSCH for multiple cells using a single DCI may be referred to as DCI format 0_3 / 1_3, respectively.
[0072] DCI formats 0_3 / 1_3 can be simultaneously scheduled for a combination of cells included in a set of cells to be scheduled (Set of cells). The following requirements may be applied to the Set of cells.
[0073] - One set of cells consists of a maximum of four cells - Any cell is included in only one set of cells Figure 6 shows an example where Set of cells 1 includes CC#1 / 2 / 3 / 4, and Set of cells 2 includes CC#5 / 6 / 7. The DCI formats of Set of cells 1 and 2 may each be included in a different PDCCH.
[0074] A cell that counts the DCI size / PDCCH candidate (BD) / number of CCEs may be called a reference cell. For each set of cells, one cell may be configured that counts the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH that schedules the cells included in each set of cells. In FIG. 6, for example, the reference cell for set of cells 1 may be CC#1, and the reference cell for set of cells 2 may be CC#5. Here, cell and CC may be interpreted interchangeably.
[0075] In this case, the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH (DCI for set of cells 1) may be counted in CC #1. Also, the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH (DCI for set of cells 2) may be counted in CC #5.
[0076] One cell may be configured for each set of cells to count the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH that schedules the cells of each set of cells. The cell that counts the DCI size / PDCCH candidate (BD) / number of CCEs may be called a reference cell. The reference cell may be notified by the upper layer parameter search space configuration.
[0077] FIG. 6 shows an example in which the reference cell of the cell in Set of cells 1 is CC#1, and the reference cell of Set of cells 2 is CC#5.
[0078] When DCI format 0_3 / 1_3 for Single DCI Multi-Cell PDSCH / PUSCH scheduling is applied, whether or not existing DCI formats can be simultaneously monitored may vary depending on UE capability in a cell that monitors DCI format 0_3 / 1_3. Specifically, UE 200 needs to be able to appropriately report to the network which DCI formats can be simultaneously monitored in which cells.
[0079] (3.2) Operational Example The following describes an operational example related to reporting of DCI monitoring capabilities supported by UE 200 in Single DCI Multi-Cell PDSCH / PUSCH scheduling. This makes it possible to realize appropriate Single DCI Multi-Cell PDSCH / PUSCH scheduling according to UE Capability.
[0080] The following operation example regarding UE Capability reporting will be described below.
[0081] (Operation Example 1): Reporting according to a cell that simultaneously monitors the existing DCI and DCI format 0_3 / 1_3 (Operation Example 2): Reporting according to a scheduling cell that the existing DCI schedules (Operation Example 3): Reporting according to the type of existing DCI format Note that "simultaneous monitoring" may be interpreted as monitoring the corresponding DCI format in the same cell, or as monitoring the corresponding DCI format in PDCCH monitoring occasions of at least partially overlapping time resources, or as monitoring the corresponding DCI format in the same slot.
[0082] (3.2.1) Operation Example 1 In this operation example, UE 200 may be able to report whether or not it can support simultaneous monitoring of existing DCI formats, depending on whether the cell monitoring DCI formats 0_3 / 1_3 is a P(S)Cell or an SCell.
[0083] The UE 200 does not need to explicitly report the support of Single DCI Multi-Cell PDSCH / PUSCH scheduling as a mandatory capability of the UE 200, or may report it as (a part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0084] For example, UE200 may be required to have simultaneous monitoring of the existing DCI and DCI format 0_3 / 1_3 in the P(S)Cell as a required function for UE200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling, and may be able to report by separate UE capability signaling whether it supports simultaneous monitoring of the existing DCI and DCI format 0_3 / 1_3 in the P(S)Cell.
[0085] UE 200 may be capable of reporting at least one of {none, P(S)Cell, Scell, P(S)Cell and SCell} in which cells simultaneous monitoring of the legacy DCI format and DCI format 0_3 / 1_3 is possible. For example, UE 200 may be capable of reporting in which cells {P(S)Cell, Scell, P(S)Cell and SCell} monitoring of DCI format 0_3 / 1_3 is supported, and may be capable of reporting whether monitoring of the legacy DCI is supported (separately for P(S)Cell and SCell) for cells that have reported supporting monitoring of DCI format 0_3 / 1_3.
[0086] The UE 200 may be able to report whether it can support simultaneous monitoring of existing DCI formats, depending on whether the cell monitoring DCI format 0_3 / 1_3 is a reference cell of the set of cells scheduled by the DCI, or may not explicitly report this as a required capability of the UE 200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling. Alternatively, the UE 200 may report this as (a part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0087] For example, UE200 may set simultaneous monitoring of the existing DCI and DCI format 0_3 / 1_3 in the reference cell as a required function for UE200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling, and may be able to report by separate UE capability signaling whether or not UE200 supports simultaneous monitoring of the existing DCI and DCI format 0_3 / 1_3 in cells other than the reference cell.
[0088] UE200 may be able to report at least one of {none (not possible in any cell), reference cell, non-reference cell, reference cell and non-reference cell} in which cells simultaneous monitoring of the existing DCI format and DCI format 0_3 / 1_3 is possible.
[0089] UE200 may be capable of reporting whether or not monitoring of DCI format 0_3 / 1_3 is supported in any of the cells {reference cell, non-reference cell, reference cell, and non-reference cell}, and may be capable of reporting whether or not monitoring of existing DCI is supported for cells that have reported that they support monitoring of DCI format 0_3 / 1_3 (separately for reference cell and non-reference cell).
[0090] Furthermore, the UE 200 may be able to report whether or not simultaneous monitoring of existing DCI formats is supported, depending on whether or not a cell monitoring DCI format 0_3 / 1_3 is included in the set of cells scheduled by the DCI, and may not explicitly report this as a required capability of the UE 200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling. Alternatively, the UE 200 may report this as (a part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0091] For example, UE200 may be capable of reporting whether or not it supports monitoring of DCI format 0_3 / 1_3 depending on whether or not a cell that monitors DCI format 0_3 / 1_3 is included in the set of cells, and when it reports that it supports monitoring of DCI format 0_3 / 1_3, it may be capable of reporting whether or not it supports monitoring of an existing DCI (separately for when the cell is included in the set of cells and when it is not included).
[0092] (3.2.2) Operation Example 2 In this operation example, the UE 200 may be able to report whether or not simultaneous monitoring with DCI format 0_3 / 1_3 is supported, depending on whether or not the cell scheduled by the existing DCI is a reference cell, and may not explicitly report this as a required capability of the UE 200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling. Alternatively, the UE 200 may report this as (a part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0093] For example, when the cell scheduled by the existing DCI is a reference cell, simultaneous monitoring of DCI formats 0_3 / 1_3 may be a required function for UE200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling, and when the cell scheduled by the existing DCI is a cell other than the reference cell, UE200 may be able to report whether or not simultaneous monitoring of DCI formats 0_3 / 1_3 is supported by another UE capability signaling.
[0094] Fig. 7 shows an example (part 1) of the relationship between a cell scheduled by DCI and a reference cell according to operation example 2. Fig. 8 shows an example (part 1) of the relationship between a cell scheduled by DCI and a reference cell according to operation example 2. In Figs. 7 and 8, PDSCH / PUSCH are collectively referred to as PXSCH (the same applies hereinafter).
[0095] 7 shows an example in which a cell scheduled by an existing DCI is a reference cell (CC#1). BDs / CCEs of DCI format 0_3 / 1_3 are counted in reference cell=CC#1, and BDs / CCEs of the existing DCI may also be counted in CC#1.
[0096] 8 shows an example in which a cell scheduled by an existing DCI is a non-reference cell. BDs / CCEs of DCI format 0_3 / 1_3 may be counted in reference cell=CC#1, and BDs / CCEs of the existing DCI may be counted in CC#2. In this case, there is a concern that the load on the DCI monitor of UE 200 may increase.
[0097] (3.2.3) Operation Example 3 In this operation example, the existing DCI format that the UE 200 simultaneously monitors may be at least one of DCI formats 0_0 / 1_0 / 1_0 / 1_1 / 0_2 / 1_2. Alternatively, the UE 200 may separately report whether or not it can simultaneously monitor DCI formats 0_3 / 1_3 depending on the DCI format. The UE 200 does not need to explicitly report support for Single DCI Multi-Cell PDSCH / PUSCH scheduling as a required capability of the UE 200, or may report it as (part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0098] For example, UE200 may set simultaneous monitoring of DCI format 0_0 / 1_0 and DCI format 0_3 / 1_3 as a required function for UE200 supporting Single DCI Multi-Cell PDSCH / PUSCH scheduling, and may be able to report whether or not UE200 supports simultaneous monitoring of DCI format 1_0 / 1_1 / 0_2 / 1_2 and DCI format 0_3 / 1_3 by separate UE capability signaling.
[0099] UE200 may be able to report (combinations of) DCI formats that can be monitored simultaneously with DCI format 0_3 / 1_3 by at least one of {none, DCI 0_0, DCI 1_0, DCI 0_1, DCI 1_1, DCI 0_2, DCI 1_2}.
[0100] Furthermore, the existing DCI format simultaneously monitored by UE 200 may be a DCI set in common SS (CSS) or a DCI set in UE specific SS (USS). UE 200 may separately report whether simultaneous monitoring with DCI format 0_3 / 1_3 is possible depending on whether the DCI is set in CSS or USS, or may not explicitly report this as a required capability of UE 200 supporting Single DCI Multi-Cell PDSCH / PUSCH scheduling. Alternatively, UE 200 may report this as (part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0101] UE200 may set simultaneous monitoring of the existing DCI format set in the CSS and DCI format 0_3 / 1_3 as a required function for UE200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling, and may be able to report whether or not simultaneous monitoring of the existing DCI format set in the USS and DCI format 0_3 / 1_3 is supported by separate UE capability signaling.
[0102] UE200 may be able to report (combinations of) DCI formats that can be monitored simultaneously with DCI format 0_3 / 1_3 by at least one of {none, legacy DCI in CSS, legacy DCI in USS, legacy DCI in CSS and USS}.
[0103] Furthermore, the existing DCI format that UE200 simultaneously monitors may be (but is not limited to) DCI scrambled with at least one of SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, MsgB-RNTI, PEI-RNTI, MCCH-RNTI, G-RNTI, C-RNTI, CS-RNTI, MCS-C-RNTI, SFI-RNTI, and INT-RNTI.
[0104] The UE 200 may be able to separately report whether simultaneous monitoring with DCI format 0_3 / 1_3 is possible depending on which RNTI the DCI is scrambled by, or may not explicitly report this as a required capability of the UE 200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling. Alternatively, the UE 200 may report this as (a part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0105] UE200 may set simultaneous monitoring of existing DCI scrambled with at least one of SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, and MsgB-RNTI and DCI format 0_3 / 1_3 as a required function for UE200 supporting Single DCI Multi-Cell PDSCH / PUSCH scheduling, and may be capable of reporting, by separate UE capability signaling, whether or not simultaneous monitoring of existing DCI format scrambled with at least one of C-RNTI, CS-RNTI, and MCS-C-RNTI and DCI format 0_3 / 1_3 is supported.
[0106] (3.2.4) Others The above-described operation examples 1 to 3 may be combined in plural. For example, the monitoring of existing DCI (at least DCI format 0_0 / 1_0) that performs scheduling for a reference cell and the simultaneous monitoring of DCI format 0_3 / 1_3 may be considered as a required function of UE 200 that supports multi-carrier (MC) scheduling in a P(S)Cell, and may not be explicitly reported as a required function of UE 200 that supports Single DCI Multi-Cell PDSCH / PUSCH scheduling. Alternatively, UE 200 may report this as (part of) the basic capability of Single DCI Multi-Cell PDSCH / PUSCH scheduling.
[0107] UE200 may be able to report whether it supports simultaneous monitoring of existing DCI (at least DCI format 0_0 / 1_0) that schedules cells other than the reference cell in the P(S)Cell and DCI format 0_3 / 1_3 according to UE Capability.
[0108] UE200 may be able to report whether or not it supports simultaneous monitoring of DCI format 0_1 / 1_1 / 0_2 / 1_2 and DCI format 0_3 / 1_3 in the P(S)Cell (for scheduling to a reference cell and / or a non-reference cell) according to UE Capability.
[0109] UE 200 may be able to report whether or not it supports simultaneous monitoring of DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 and DCI format 0_3 / 1_3 in the SCell (for scheduling to a reference cell and / or a non-reference cell) according to UE Capability.
[0110] Furthermore, the UE Capability in the above-described operation example may be defined so that it can be reported separately depending on whether it is UL operation (monitoring DCI format 0_3) or DL operation (monitoring DCI format 1_3).
[0111] The reporting granularity of UE Capability in the above-described operation example may be at least one of per carrier type (FR1 / FR2-1 / FR2-2, licensed / unlicensed, TDD / FDD), per band, per BC, per UE, Per-FS (Feature Set), and Per-FSPC (Feature Set Per CC).
[0112] The UE Capability in the above-described operation example may be defined separately for the case where the number of cells scheduled by DCI format 0_3 / 1_3 is one and the case where the number of cells scheduled by DCI format 0_3 / 1_3 is two or more.
[0113] (4) Actions and Effects According to the above-described embodiment, the following actions and effects can be obtained. Specifically, according to the above-described operation example, the UE 200 can report, to the network, UE Capability Information including whether or not the UE 200 can simultaneously monitor DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling (DCI format 0_3 / 1_3) and existing DCI (DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, etc.). Furthermore, depending on whether a cell scheduled by an existing DCI (DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, etc.) other than the DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling (DCI format 0_3 / 1_3) is a reference cell or not, UE 200 can report UE Capability Information to the network, including whether or not the DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling (DCI format 0_3 / 1_3) and the existing DCI (DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, etc.) can be simultaneously monitored.
[0114] Therefore, even when single DCI multi-cell PDSCH / PUSCH scheduling is introduced, the UE 200 can monitor DCI appropriately, thereby realizing appropriate single DCI multi-cell PDSCH / PUSCH scheduling according to the UE capability.
[0115] In this embodiment, the UE 200 can report to the network UE Capability Information including whether or not the UE 200 can simultaneously monitor the existing DCI (DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, etc.) set in the common search space (CSS) or the UE 200-specific search space (USS) and the DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling (DCI format 0_3 / 1_3). This makes it possible to realize more appropriate Single DCI Multi-Cell PDSCH / PUSCH scheduling according to the UE capabilities.
[0116] (5) Other Embodiments The contents of the present proposal have been explained above using examples, but it will be obvious to those skilled in the art that the present proposal is not limited to these descriptions and that various modifications and improvements are possible.
[0117] For example, in the above-described embodiment, the terms "single DCI multi-slot PDSCH / PUSCH scheduling" and "single DCI multi-cell PDSCH / PUSCH scheduling" are used in the description, but these terms may be called by other names as long as they refer to a function of scheduling PDSCH / PUSCHs of multiple slots using one DCI or a function of scheduling PDSCHs / PUSCHs of multiple CCs using a single (one) DCI. Also, as described above, the channel is not limited to the PDSCH / PUSCH, and may include a control channel and / or other data channels.
[0118] In addition, in the above-described embodiment, UE capability signaling may be per UE, per FR, per TDD / FDD, per band, per BC (Band Combination), per FS (Feature Set), or per FSPC (Feature Set Per CC).
[0119] The UE 200 may report the UE capability to the scheduling CC, or may report the UE capability to the scheduled CC, or may report the UE capability to the CC that transmits the PUCCH.
[0120] In addition, in the above-described embodiments, the terms scheduled cell and co-scheduled cell(s) are used in the description, where a scheduled cell means any one cell and a co-scheduled cell(s) may be interpreted as meaning multiple cells that are scheduled simultaneously, but scheduled cell and co-scheduled cell(s) may be used interchangeably.
[0121] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.
[0122] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.
[0123] The block diagram ( FIG. 4 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., via wire, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.
[0124] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.
[0125] Furthermore, the above-described gNB100 and UE200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 9 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 9, the devices may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0126] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0127] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.
[0128] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.
[0129] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.
[0130] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.
[0131] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.
[0132] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0133] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.
[0134] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
[0135] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0136] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0137] Furthermore, the device may 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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0138] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by 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 a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0139] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, 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 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.
[0140] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0141] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.
[0142] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.
[0143] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.
[0144] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0145] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).
[0146] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0147] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0148] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0149] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0150] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0151] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0152] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0153] In this disclosure, terms such as "base station (BS)," "radio 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" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0154] 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 be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0155] The terms "cell" or "sector" refer to part or all of the coverage area of a base station and / or base station subsystem that provides communication services within that coverage area.
[0156] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
[0157] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0158] A mobile station may also be referred to by those skilled in the art 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, handset, user agent, mobile client, client, or some other suitable terminology.
[0159] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
[0160] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).
[0161] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.
[0162] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0163] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.
[0164] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based time unit.
[0165] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0166] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[0167] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
[0168] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.
[0169] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0170] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0171] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0172] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0173] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
[0174] The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may also be determined based on the numerology.
[0175] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.
[0176] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
[0177] Furthermore, 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.
[0178] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0179] 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.
[0180] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0181] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.
[0182] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0183] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.
[0184] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0185] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0186] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.
[0187] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.
[0188] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0189] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0190] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."
[0191] 10 shows an example of the configuration of a vehicle 2001. As shown in Fig. 10, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a 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.
[0192] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0193] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0194] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.
[0195] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0196] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.
[0197] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.
[0198] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.
[0199] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0200] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.
[0201] Although the present disclosure has been described in detail above, it is 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 in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0202] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transceiver 220 Amplifier 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transceiver 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port
Claims
1. A terminal comprising: a transmitter that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information; and a control unit that transmits the terminal capability information including whether or not the downlink control information and existing downlink control information other than the downlink control information can be simultaneously monitored.
2. A terminal as described in claim 1, wherein the control unit transmits the existing downlink control information set in a common search space or a search space specific to the terminal, and the terminal capability information including whether or not the downlink control information can be simultaneously monitored.
3. A terminal comprising: a transmitting unit that transmits terminal capability information related to scheduling targeting a combination of multiple cells using a single downlink control information; and a control unit that transmits the terminal capability information including whether or not the downlink control information and the existing downlink control information can be simultaneously monitored depending on whether or not a cell scheduled by existing downlink control information other than the downlink control information is a reference cell.
4. A terminal as described in claim 3, wherein the control unit transmits the existing downlink control information set in a common search space or a search space specific to the terminal, and the terminal capability information including whether or not the downlink control information can be simultaneously monitored.
5. A wireless communication method in a terminal, comprising: a step of transmitting terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information; and a step of transmitting the terminal capability information including whether or not the downlink control information and existing downlink control information other than the downlink control information can be simultaneously monitored.
6. A wireless communication method in a terminal, comprising: a step of transmitting terminal capability information regarding scheduling targeting a combination of multiple cells using single downlink control information; and a step of transmitting the terminal capability information including whether or not the downlink control information and the existing downlink control information can be simultaneously monitored depending on whether or not a cell scheduled by existing downlink control information other than the downlink control information is a reference cell.
Citation Information
Patent Citations
Terminal apparatus, base station apparatus, communication method, and integrated circuit
WO2016163464A1
