Terminal and communication method

Abstract

Provided is a terminal comprising a reception unit that receives, from a base station, information indicating whether a field included in control information for multi-carrier scheduling is set for each scheduled carrier or for scheduled carriers in common, and a control unit that interprets the control information on the basis of the information, wherein the reception unit receives the control information from the base station, wherein the control unit determines whether the field included in the control information is set for each scheduled carrier or for scheduled carriers in common, and wherein the reception unit receives each carrier scheduled in the control information on the basis of the determination.

Description

[Technical Field]

[0001] The present invention relates to a terminal and a communication method in a wireless communication system. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

[0003] Furthermore, studies on 6G have begun as the next-generation wireless communication system after 5G, and it is expected to achieve wireless quality that exceeds that of 5G. For example, studies are underway for 6G to achieve even higher capacity, the use of new frequency bands, even lower latency, even higher reliability, even lower power consumption, and the expansion of coverage to new areas (high altitude, sea, and space) using non-terrestrial networks (e.g., Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V16.8.0 (2021-12) [Non-patent document 2] 3GPP TR 38.821 V16.1.0 (2021-05) [Non-patent document 3] 3GPP TS 38.212 V16.8.0 (2021-12) Summary of the Invention [Problem to be solved by the invention]

[0005] Studies are being conducted to enhance operation in multi-carrier systems. In this study, a method of scheduling PDSCH or PUSCH using a single Downlink Control Information (DCI) in multi-cell systems is being considered. However, it was unclear which fields in the DCI should be common across carriers and which fields should be configured for each carrier.

[0006] The present invention has been made in view of the above points, and makes it possible to perform multi-carrier scheduling using single control information in a wireless communication system. [Means for solving the problem]

[0007] According to the disclosed technology, a receiving unit that receives RRC (Radio Resource Control) signaling from a base station; and a control unit that specifies, based on the RRC signaling, whether a first field included in control information for scheduling a plurality of cells is to be notified for each cell included in the plurality of cells or to be notified commonly to all cells included in the plurality of cells, wherein the receiving unit receives the control information from the base station, and the control unit interprets the first field included in the control information, a second field included in the control information that is always notified for each cell included in the plurality of cells, and a third field included in the control information that is always notified commonly to all cells included in the plurality of cells. is provided. [Effects of the Invention]

[0008] According to the disclosed technology, it is possible to perform multi-carrier scheduling in a wireless communication system using single control information. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating a configuration example (1) of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating a configuration example (2) of a wireless communication system according to an embodiment of the present invention. [Figure 3] FIG. 10 is a diagram illustrating an example (1) of a scheduling operation. [Figure 4] FIG. 10 is a diagram illustrating an example (2) of a scheduling operation. [Figure 5] FIG. 10 is a diagram illustrating an example (3) of a scheduling operation. [Figure 6] FIG. 10 is a sequence diagram showing an example (1) of a scheduling operation according to an embodiment of the present invention. [Figure 7]10 is a flowchart showing an example (2) of a scheduling operation in the embodiment of the present invention. [Figure 8] 10 is a flowchart showing an example (3) of a scheduling operation in the embodiment of the present invention. [Figure 9] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. [Figure 11] 1 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 12] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0013] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0015] Fig. 1 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0016] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, transmitted via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in the downlink (DL) and receives control signals or data from the terminal 20 in the uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0017] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0018] Terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0019] Fig. 2 is a diagram illustrating an example (2) of a wireless communication system according to an embodiment of the present invention. Fig. 2 shows a configuration example of a wireless communication system in which DC (Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 can communicate with both the base station 10A and the base station 10B.

[0020] A cell group provided by base station 10A, which is an MN, is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN, is called an SCG (Secondary Cell Group). In addition, in a DC, an MCG is composed of one PCell and one or more SCells, and an SCG is composed of one PSCell (Primary SCG Cell) and one or more SCells.

[0021] The processing operations in this embodiment may be executed in the system configuration shown in FIG. 1, in the system configuration shown in FIG. 2, or in any other system configuration.

[0022] Studies are being conducted to enhance operation in multi-carrier systems. In these studies, a method of scheduling PDSCH or PUSCH using a single DCI (Downlink Control Information) in multi-cell systems is being considered. Hereinafter, "PDSCH or PUSCH" is also referred to as "PDSCH / PUSCH."

[0023] When scheduling PDSCH / PUSCH for multiple CCs using a single DCI, compared to a method in which a DCI is prepared for each CC and scheduling is performed one CC at a time, the advantage is that the load due to monitoring the DCI (PDCCH) (e.g., the number of blind decodes) can be reduced. Also, the smaller the size of the single DCI is compared to the size of the conventional DCI multiplied by the number of CCs, the more the total PDCCH overhead can be reduced. On the other hand, the disadvantage is that the instruction content cannot be flexibly changed for each CC. If the instruction content could be flexibly changed, the size of the single DCI would increase, resulting in a worsening of the PDCCH error rate and an increase in overhead. Also, if the PDCCH is decoded incorrectly, data reception for all multiple CCs would fail.

[0024] Fig. 3 is a diagram showing an example (1) of a scheduling operation. As shown in Fig. 3, in conventional self-carrier scheduling, a PDCCH and DCI are transmitted for each CC, and a PDSCH / PUSCH is scheduled for that CC.

[0025] 4 is a diagram showing an example (2) of a scheduling operation. As shown in FIG. 4, in conventional cross-carrier scheduling, PDSCH / PUSCH are scheduled to each CC by PDCCH and DCI in other CCs.

[0026] 5 is a diagram showing an example (3) of a scheduling operation. As shown in FIG. 5, in multi-carrier scheduling, a single DCI schedules a PDSCH / PUSCH for each CC.

[0027] Here, in a single DCI that performs multi-carrier scheduling, it was unclear which fields should be common between CCs and which fields should be set for each CC.

[0028] Therefore, to take advantage of the advantages of single DCI multi-carrier scheduling, a DCI design suitable for more applications or environments may be realized. For example, the following options 1) to 3) may be applied.

[0029] Option 1) In DCI used for multi-carrier scheduling, the base station 10 may be able to set whether to notify a value for at least one field for each CC to be scheduled, or to notify a common value for CCs to be scheduled.

[0030] 6 is a sequence diagram showing an example (1) of a scheduling operation in an embodiment of the present invention. In step S11, base station 10 transmits to terminal 20 information that sets whether, for at least one field in DCI used for multicarrier scheduling, a value is to be notified for each CC to be scheduled, or a value is to be notified commonly between CCs to be scheduled. In the following step S12, base station 10 performs multicarrier scheduling for terminal 20 using DCI to which this setting has been applied.

[0031] For example, the setting transmitted from the base station 10 to the terminal 20 may be notified by any of RRC (Radio Resource Control) signaling, SIB (System Information Block), MAC-CE (Medium Access Control - Control Element) and DCI, or may be notified by a combination of multiple signalings.

[0032] The setting transmitted from the base station 10 to the terminal 20 may be notified for each field, or may be notified for multiple fields at once.

[0033] For example, the terminal 20 may assume the DCI size according to the setting from the base station 10.

[0034] For example, a UE capability indicating whether or not the above-described configuration by base station 10 is possible may be defined. The UE capability may be defined separately for each field or for each of multiple fields. The UE capability may be defined separately for intraband and interband. The UE capability may be defined separately for each maximum number of configurable CCs. The UE capability may be defined for each UE, for each FR (Frequency Range), for each band, for each band combination, for each feature set, or for each CC of a feature set.

[0035] For example, a specification may define a field whose value is always reported for each CC and / or a field whose value is always reported commonly across CCs. For example, a field whose value is always reported for each CC may be an HPN (HARQ process number), an RV (Redundancy version), an NDI (New data indicator), etc. For example, a field whose value is always reported commonly across CCs may be a CIF (Carrier indicator field), a PRI (PUCCH Resource Indicator), a PDSCH-to-HARQ feedback timing indicator, etc. (see Non-Patent Document 3).

[0036] Option 2) In DCI used for multi-carrier scheduling, whether to notify a value for at least one field for each CC to be scheduled or to notify a common value for CCs to be scheduled may be determined based on a specific condition. The specific condition may be, for example, a condition related to intraband, interband, FR1, FR2, the number of CCs, SCS, etc.

[0037] 7 is a flowchart showing an example (2) of a scheduling operation in an embodiment of the present invention. In step S21, base station 10 and terminal 20 determine, based on specific conditions, whether to notify a value for at least one field in DCI used for multicarrier scheduling for each CC to be scheduled, or to notify a value common to all CCs to be scheduled. In the following step S22, base station 10 performs multicarrier scheduling for terminal 20 using the determined DCI.

[0038] For example, whether at least one field is common between CCs or per CC may be determined depending on whether the scheduled CC is intraband only or includes interband. In the case of intraband only, the number of fields common between CCs may be increased compared to the case of including interband, and the DCI size may be reduced.

[0039] For example, whether at least one field is common between CCs or per CC may be determined depending on whether the scheduled CC contains only intra FRs or inter FRs. In the case of only intra FRs, the number of fields common between CCs may be increased compared to the case of containing inter FRs, and the DCI size may be reduced.

[0040] For example, whether at least one field is common to CCs or per CC may be determined depending on whether a predetermined FR is included in the scheduled CC.

[0041] For example, whether at least one field is common across CCs or per CC may be determined depending on whether the number of scheduled CCs (a number that is dynamically notified or a maximum number that is semi-statically set) is greater or less than a predetermined value.

[0042] For example, whether at least one field is common between CCs or per CC may be determined depending on whether the scheduled CC has only a single SCS or includes multiple different SCSs. In the case of a single SCS, the number of fields common between CCs may be increased compared to the case of a CC including multiple SCSs, and the DCI size may be reduced.

[0043] For example, whether at least one field is common to all CCs or per CC may be determined depending on whether a specific combination of SCSs is included in the CC to be scheduled.

[0044] For example, whether at least one field is common to all CCs or is per CC may be determined depending on whether the CC to be scheduled includes only licensed CCs or unlicensed CCs.

[0045] Note that the above-mentioned option 1) and option 2) may be combined. For example, whether the base station 10 can set a field common to CCs or for each CC may be determined depending on the relationship between CCs to be scheduled.

[0046] Option 3) The applicability of the multi-carrier scheduling DCI may be determined according to at least one of the conditions 1) and 2) below.

[0047] 1) The multi-carrier scheduling DCI may be applicable to only some of the fallback DCI (0_0, 1_0), non-fallback DCI (0_1, 1_1), and compact DCI (0_2, 1_2).

[0048] For example, multi-carrier scheduling may be applicable only to non-fallback DCI, or multi-carrier scheduling may be applicable only to non-fallback DCI and compact DCI.

[0049] 2) Multi-carrier scheduling DCI may be applicable only in cases where only a specific CC is included in the scheduled CC.

[0050] For example, the specific CC may be a CC that does not include a specific FR (e.g., FR2-2). The specific CC may be a CC that does not include a different specific combination of FRs (e.g., FR1 and FR2). The specific CC may be a CC that does not include an unlicensed frequency. The specific CC may be a CC that does not include both a licensed frequency and an unlicensed frequency. The specific CC may be a CC that does not include a specific SCS (e.g., 480 kHz or 960 kHz). The specific CC may be a CC that does not include a different specific combination of SCSs (e.g., 15 kHz and 30 kHz, or 480 kHz and 960 kHz).

[0051] 8 is a flowchart showing an example (3) of a scheduling operation according to an embodiment of the present invention. In step S31, the base station 10 and the terminal 20 determine whether or not DCI is applicable to multicarrier scheduling based on predetermined conditions. In the following step S32, the base station 10 performs multicarrier scheduling on the terminal 20 using applicable DCI.

[0052] An example of each field in the DL grant will be described below. For details of each field, see Non-Patent Document 3.

[0053] DCI format identifier: May always be assumed to be common across CCs, i.e., a single field.

[0054] Carrier indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying one or multiple scheduled cells. It may also be assumed to be per CC, or may be defined as a field that specifies the presence or absence of each of multiple scheduled cells, for example. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, the size (total) of this field may be larger than before.

[0055] BWP indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be a notification for a specific cell or for all scheduled cells. It may also be assumed to be per CC, or, for example, defined so that each field specifies the BWP of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0056] TDRA (Time Domain Resource Allocation): TDRA may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying the TDRA for each of multiple scheduled cells. Also, it may be assumed to be per CC, or, for example, may be defined such that each field specifies each of multiple scheduled cells. Depending on specific conditions, for example, whether the SCS is common to the scheduled cells, switching between CC-common and CC-per-CC may be performed. Also, a combination of candidate TDRA values ​​for each of multiple cells may be configured by RRC signaling. Restrictions may be specified, such as requiring all scheduled cells to have a common SCS.

[0057] FDRA (Frequency Domain Resource Allocation): This field may always be common across CCs, i.e., a single field, or may be defined as a single field for specifying the FDRA of each of multiple scheduled cells. It may also be assumed to be per CC, or, for example, defined such that each field specifies a separate field for each of multiple scheduled cells. It may switch between being common across CCs or per CC depending on specific conditions, for example, whether the scheduled cell is intraband or not. Furthermore, a combination of candidate FDRA values ​​for each of multiple cells may be set by RRC signaling. The interpretation of the FDRA field common across CCs may differ from conventional interpretations. For example, it may be interpreted as a wideband FDRA including multiple intraband CCs, or the interpretation may change for each scheduled cell.

[0058] Rate matching indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or, for example, defined such that each field specifies rate matching for multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed. A combination of rate matching patterns for each of multiple cells may be set by RRC signaling.

[0059] ZP-CSI-RS trigger: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or all scheduled cells. It may also be assumed to be per CC, or, for example, may be defined such that each field specifies a ZP-CSI-RS trigger for multiple scheduled cells. It may switch between being common across CCs or per CC depending on a specific condition, for example, the maximum number of scheduled CCs configured by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed. A combination of aperiodic ZP-CSI-RS resource sets for each of multiple cells may be configured by RRC signaling.

[0060] MCS (Modulation and Coding Scheme): It may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying an MCS common to multiple scheduled cells. It may also be assumed to be per CC, or may be defined, for example, as a field specifying each of multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling.

[0061] NDI / RV (New Data Indicator / Redundancy Version): May always be assumed to be per CC. The RV size is smaller than before, and it may be specified that 0 or 2, or 0 or 1, can be specified in 1 bit for multi-carrier scheduling.

[0062] 2ndTB: The presence or absence of 2ndTB may be determined commonly between CCs, or it may be possible to enable or disable it for each CC, or either of the above may be switched depending on specific conditions.

[0063] HPN (HARQ process number): May always be assumed to be per CC.

[0064] DAI (Downlink assignment index): This may be assumed to be always common between CCs, or may be assumed to be a single field and value.

[0065] PRI: May always be assumed to be common across CCs, or may be assumed to be a single field and value.

[0066] PDSCH-to-HARQ feedback timing indicator: This may be assumed to be always common between CCs, or a single field and value may be assumed. The specifications may define which PDSCH the value of this field is to be interpreted as based on. For example, the PDSCH of the cell that transmits the PUCCH may be set as the reference, or the PDSCH with the latest timing may be set as the reference, or the PDSCH that is to be set as the reference may be set by the base station 10.

[0067] One-shot HARQ-ACK request: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0068] Enhanced Type 2 codebook indicator: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0069] PDSCH group index: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0070] New feedback indicator: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0071] Number of requested PDSCH groups (Number of requested PDSCH group(s)): This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0072] HARQ-ACK retransmission indicator: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0073] Antenna port(s): This may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying the antenna port of each of multiple scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies each of multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, whether the scheduled cell is intraband or not.

[0074] Transmission configuration indication: This may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying the TCI of each of multiple scheduled cells. It may also be assumed to be per CC, or may be defined, for example, as a field specifying each of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, whether the scheduled cell is intraband or not.

[0075] SRS request: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be a notification for a specific cell or a notification for all scheduled cells. It may also be assumed to be per CC, or, for example, may be defined such that each field specifies an SRS request for multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0076] SRS offset indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or, for example, may be defined such that each field specifies the SRS offset of multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed. A combination of SRS offset candidate values ​​for each of multiple cells may be set by RRC signaling.

[0077] CBG transmission information (CBGTI): This may always be assumed per CC, or may be defined, for example, with one field specifying each of multiple scheduled cells. In case of multi-carrier scheduling DCI, this field may not be assumed.

[0078] CBG flushing out information (CBGFI): May always be assumed per CC or may be defined, for example, with one field specifying each of multiple scheduled cells. In case of multi-carrier scheduling DCI, this field may not be assumed.

[0079] DMRS sequence initialization: This may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying common settings for multiple scheduled cells. It may also be assumed to be per CC, or defined, for example, as a field specifying each of multiple scheduled cells. It may be switched between common and per CC depending on specific conditions, for example, the maximum number of scheduled CCs configured by RRC signaling.

[0080] Priority indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be defined as one field for specifying settings common to multiple scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a different one for each of multiple scheduled cells. It may be switched between common and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0081] ChannelAccess-CPext: May always be assumed to be common across CCs, i.e., a single field, or a single field and value. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0082] Minimum applicable scheduling offset indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between common across CCs and per CC depending on a specific condition, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0083] SCell dormancy indication: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0084] PDCCH monitoring adaptation indication: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be a notification for a specific cell, or may be assumed to be a notification for all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0085] PUCCH Cell Indicator: This may be assumed to be common across CCs, or a single field and value may be assumed. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0086] An example of each field in the UL grant will be described below. For details of each field, please refer to Non-Patent Document 3.

[0087] DFI flag: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or, for example, defined so that each field specifies a respective one of multiple scheduled cells. It may be switched between being common across CCs or per CC depending on a specific condition, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0088] TPC command (TPC command for scheduled PUSCH): This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be a notification for a specific cell, or may be assumed to be a notification for all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0089] UL / SUL indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a separate one of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0090] SRS resource set indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0091] SRS resource indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0092] PTRS-DMRS association: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or, for example, defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0093] Beta offset indicator (beta_offset_indicator): This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be notified to a specific cell or to all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a separate field for multiple scheduled cells. It may be switched between being common across CCs or per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0094] UL-SCH indicator: This may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be a notification for a specific cell or for all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a separate one of multiple scheduled cells. It may be switched between common across CCs and per CC depending on specific conditions, for example, the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0095] ChannelAccess-CPext-CAPC: This field may be assumed to be always common across CCs, i.e., a single field, or may be assumed to be a notification for a specific cell or for all scheduled cells. It may also be assumed to be per CC, or may be defined such that each field specifies a respective one of multiple scheduled cells. It may be switched between common across CCs or per CC depending on specific conditions, for example, intraband or interband. In the case of multi-carrier scheduling DCI, this field need not be assumed.

[0096] According to the above-described embodiment, the base station 10 and the terminal 20 can determine whether each field of DCI for which multi-carrier scheduling is performed is common to all CCs or for each CC, and can adjust the trade-off between flexibility and performance.

[0097] That is, in a wireless communication system, multi-carrier scheduling can be performed using single control information.

[0098] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0099] <Base station 10> Fig. 9 is a diagram showing an example of the functional configuration of base station 10 in the embodiment of the present invention. As shown in Fig. 9, base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 9 is merely an example. The functional divisions and names of the functional units may be any names as long as they can perform the operations related to the embodiment of the present invention.

[0100] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0101] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to multi-carrier scheduling.

[0102] As described in the embodiments, the control unit 140 performs control related to multi-carrier scheduling. The functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0103] <Terminal 20> Fig. 10 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 10, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 10 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0104] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, the PSSCH, the PSDCH, the PSBCH, and the like from the other terminal 20.

[0105] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The setting information includes, for example, information related to multicarrier scheduling.

[0106] As described in the embodiments, the control unit 240 performs control related to multi-carrier scheduling. The functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0107] (Hardware configuration) The block diagrams (FIGS. 9 and 10) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and connected directly or indirectly (for example, by wire, wirelessly, etc.). The functional block may be realized by combining software with the one device or the multiple devices.

[0108] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, 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 these functions are implemented.

[0109] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0110] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 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.

[0111] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0112] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0113] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also 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.

[0114] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0115] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc 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. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0116] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may 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). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0117] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0118] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by 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.

[0119] Furthermore, base station 10 and terminal 20 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, processor 1001 may be implemented using at least one of these pieces of hardware.

[0120] Fig. 12 shows an example configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, 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. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0121] The drive unit 2002 is configured, for example, by 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.

[0122] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0123] The signals from the various sensors 2021 to 2029 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.

[0124] 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 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 obtained 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 2001.

[0125] 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 a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, 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 the driving assistance function or the autonomous driving function.

[0126] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0127] 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.

[0128] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, which are input to the electronic control unit 2010.

[0129] The communication module 2013 receives various information (traffic information, traffic signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the 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, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0130] (Summary of the embodiment) As described above, according to an embodiment of the present invention, a terminal is provided which includes a receiver that receives from a base station information indicating whether a field included in control information for performing multicarrier scheduling is set for each scheduled carrier or set commonly for all scheduled carriers, and a controller that interprets the control information based on the information, wherein the receiver receives the control information from the base station, the controller determines whether a field included in the control information is set for each scheduled carrier or set commonly for all scheduled carriers, and the receiver receives each carrier scheduled by the control information based on the determination.

[0131] With the above configuration, the base station 10 and the terminal 20 can determine whether to perform multicarrier scheduling for each field of DCI common to all CCs or for each CC, and can adjust the trade-off between flexibility and performance. In other words, in a wireless communication system, multicarrier scheduling can be performed using single control information.

[0132] The information may be notified for each field of the control information, or may be notified collectively for multiple fields of the control information. With this configuration, the base station 10 and the terminal 20 can determine whether to use common CCs or per CC for each field of DCI for which multi-carrier scheduling is performed, and adjust the trade-off between flexibility and performance.

[0133] The control unit may execute the setting according to the information for each field or for each set of multiple fields. With this configuration, the base station 10 and the terminal 20 can determine whether to perform multi-carrier scheduling for each field of DCI for which multi-carrier scheduling is performed, for both CCs or for each CC, and adjust the trade-off between flexibility and performance.

[0134] The control unit may execute the setting based on the information for each intraband or interband individually. With this configuration, the base station 10 and the terminal 20 can determine whether to perform multi-carrier scheduling for each field of DCI common to all CCs or for each CC, and adjust the trade-off between flexibility and performance.

[0135] The control unit may execute the setting based on the information for each of the maximum number of configurable carriers. With this configuration, the base station 10 and the terminal 20 can determine whether to perform multi-carrier scheduling for each field of DCI common to all CCs or for each CC, and adjust the trade-off between flexibility and performance.

[0136] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the following procedures: a reception procedure for receiving from a base station information indicating whether a field included in control information for performing multi-carrier scheduling is set for each scheduled carrier or set commonly for the scheduled carriers; a control procedure for interpreting the control information based on the information; a procedure for receiving the control information from the base station; a procedure for determining whether a field included in the control information is set for each scheduled carrier or set commonly for the scheduled carriers; and a procedure for receiving each carrier scheduled by the control information based on the determination.

[0137] With the above configuration, the base station 10 and the terminal 20 can determine whether to perform multicarrier scheduling for each field of DCI common to all CCs or for each CC, and can adjust the trade-off between flexibility and performance. In other words, in a wireless communication system, multicarrier scheduling can be performed using single control information.

[0138] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0139] 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., Radio Resource Control (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.

[0140] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0141] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein 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.

[0142] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0143] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0144] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0145] In the present disclosure, 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).

[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 explained 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 the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. 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 service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0155] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0156] 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.

[0157] At least one of the base station and the mobile station may be called 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 body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (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 IoT (Internet of Things) device such as a sensor.

[0158] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. 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.

[0159] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0160] 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.

[0161] 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.

[0162] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0163] 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."

[0164] 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 or that the first element must in some way precede the second element.

[0165] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0166] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0167] 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.

[0168] Numerology may be communication parameters that apply to at least one of transmission and 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.

[0169] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0170] A slot may include multiple minislots. Each minislot may consist of one or multiple 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.

[0171] 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.

[0172] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.

[0173] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0174] 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.

[0175] 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. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0176] A TTI having a time length of 1 ms may be called 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 called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0177] 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.

[0178] 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. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0179] 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. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0180] 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, or the like.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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."

[0185] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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, etc. may be changed in various ways.

[0186] 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.

[0187] 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."

[0188] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0189] 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. [Explanation of symbols]

[0190] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 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 Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A receiver that receives RRC (Radio Resource Control) signaling from a base station; a control unit that specifies, based on the RRC signaling, whether a first field included in control information for scheduling a plurality of cells is notified for each cell included in the plurality of cells or is notified commonly to all cells included in the plurality of cells; the receiving unit receives the control information from the base station; The control unit is a terminal that interprets the first field included in the control information, the second field that is always notified for each cell included in the plurality of cells included in the control information, and the third field that is always notified commonly to all cells included in the plurality of cells included in the control information.

2. A terminal as described in claim 1, wherein the control unit does not assume that the control information will include some fields when the control information schedules multiple cells.

3. A method of receiving RRC (Radio Resource Control) signaling from a base station; a step of determining whether a first field included in control information for scheduling a plurality of cells is notified for each cell included in the plurality of cells or is notified commonly to all cells included in the plurality of cells, based on the RRC signaling; receiving the control information from the base station; A communication method in which a terminal executes a procedure of interpreting the first field included in the control information, a second field included in the control information that is always notified for each cell included in the plurality of cells, and a third field included in the control information that is always notified commonly to all cells included in the plurality of cells.

Images