Terminals and communication methods

Abstract

To perform multi-carrier scheduling using single control information in a wireless communication system.SOLUTION: A terminal includes a receiving unit that receives RRC (Radio Resource Control) signaling from a base station, and a control unit that acquires from the RRC signaling a combination of settings for each of a plurality of cells that are scheduled by control information that performs multi-carrier scheduling. The receiving unit receives the control information from the base station. The control unit identifies one of the combinations of settings based on a field included in the control information. The receiving unit receives each of the plurality of cells based on the identified setting.SELECTED DRAWING: Figure 5

Description

Technical Field

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

Background Art

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

[0003] Furthermore, research on 6G as the next-generation wireless communication method after 5G has been started, and the realization of wireless quality exceeding 5G is expected. For example, in 6G, research is being advanced toward the realization of further increased capacity, use of new frequency bands, further reduced latency, further increased reliability, further reduction of power consumption, and expansion of coverage in new areas (high altitude, sea, space) by non-terrestrial networks (for example, Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0005] Studies are underway to enhance multi-carrier operation. These studies explore a method for scheduling PDSCH or PUSCH in a multi-cell environment using a single DCI (Downlink Control Information). However, it remains unclear which fields in the DCI should be common across carriers and which should be configured on a carrier-by-carrier basis.

[0006] The present invention has been made in view of the above points, and enables multi-carrier scheduling to be performed with a single control information in a wireless communication system. [Means for solving the problem]

[0007] According to the disclosed technology, a terminal is provided comprising a receiving unit that receives RRC (Radio Resource Control) signaling from a base station, and a control unit that obtains from the RRC signaling a combination of settings for each of a plurality of cells scheduled by control information that performs multi-carrier scheduling, wherein the receiving unit receives the control information from the base station, the control unit identifies one of the combinations of settings based on the fields included in the control information, and the receiving unit receives each of the plurality of cells based on the identified setting. [Effects of the Invention]

[0008] According to the disclosed technology, multi-carrier scheduling can be performed in a wireless communication system using a single control information. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. [Figure 2] This figure shows an example configuration (2) of a wireless communication system in an embodiment of the present invention. [Figure 3] This figure shows an example of scheduling operation (1). [Figure 4] This figure shows an example of scheduling operation (2). [Figure 5] This figure shows an example of scheduling operation (3). [Figure 6] This is a sequence diagram showing an example (1) of scheduling operation in an embodiment of the present invention. [Figure 7] This is a flowchart showing an example of scheduling operation (2) in an embodiment of the present invention. [Figure 8] This flowchart shows an example (3) of scheduling operation in an embodiment of the present invention. [Figure 9] This figure shows an example of the functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 10] This figure shows an example of the functional configuration of terminal 20 according to an embodiment of the present invention. [Figure 11] This figure shows an example of the hardware configuration of a base station 10 or terminal 20 according to an embodiment of the present invention. [Figure 12] This figure shows an example of the configuration of a vehicle 2001 in an embodiment of the present invention. [Modes for carrying out the invention]

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later methods (e.g., NR), unless otherwise specified.

[0012] In addition, in the embodiments of the present invention described below, terms 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), PUSCH (Physical Uplink Shared Channel), etc., which are used in existing LTE, are used. This is for convenience of description, and signals, functions, etc. similar to these may be called by other names. Also, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even for signals used in NR, the "NR-" may not necessarily be explicitly stated.

[0013] In addition, in the embodiments of the present invention, the duplex mode may be a TDD (Time Division Duplex) mode, an FDD (Frequency Division Duplex) mode, or another mode (e.g., Flexible Duplex, etc.).

[0014] In addition, in the embodiments of the present invention, the phrase "configured" for radio parameters, etc. may mean that predetermined values are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are configured.

[0015] FIG. 1 is a diagram showing a configuration example (1) of a wireless communication system in the embodiments of the present invention. As shown in FIG. 1, the wireless communication system in the embodiments of the present invention includes a base station 10 and a terminal 20. In FIG. 1, one base station 10 and one terminal 20 are shown, but 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 the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits the synchronization signal and the system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, by NR-PBCH and is also referred to as notification information. The synchronization signal and the system information may be called SSB (SS / PBCH block). As shown in FIG. 1, the base station 10 transmits the control signal or data to the terminal 20 in the DL (Downlink) and receives the control signal or data from the terminal 20 in the UL (Uplink). Both the base station 10 and the terminal 20 are capable of performing beamforming for signal transmission and reception. Also, both the base station 10 and the terminal 20 are capable of applying communication by MIMO (Multiple Input Multiple Output) to the DL or UL. Also, 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) by CA (Carrier Aggregation). Further, the terminal 20 may communicate via the primary cell of the base station 10 and the primary SCG cell (PSCell: Primary SCG Cell) of another base station 10 by DC (Dual Connectivity).

[0017] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, 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. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurements based on the reception results of these reference signals.

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

[0019] Figure 2 is a diagram illustrating an example (2) of a wireless communication system in an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A that acts as an MN (Master Node) and a base station 10B that acts as an SN (Secondary Node) are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B.

[0020] A cell group provided by base station 10A, which is the MN (Mobile Network Unit), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is the SN (Stationary Network Unit), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells.

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

[0022] Studies are underway to enhance multi-carrier operation. These studies explore a method for scheduling PDSCH or PUSCH in a multi-cell environment using a single DCI (Downlink Control Information). Hereafter, "PDSCH or PUSCH" will also be referred to as "PDSCH / PUSCH".

[0023] When scheduling PDSCH / PUSCH for multiple CCs using a single DCI, compared to preparing a separate DCI for each CC and scheduling each CC individually, the advantage is that it reduces the monitoring load (e.g., the number of blind decodes) associated with the DCI (PDCCH). Furthermore, the smaller the size of the single DCI (compared to the size of the conventional DCI multiplied by the number of CCs), the lower the total PDCCH overhead becomes. On the other hand, a disadvantage is that the instructions cannot be flexibly changed for each CC. If the instructions need to be flexibly changed, the size of the single DCI increases, leading to a worsening of the PDCCH error rate and increased overhead. Also, if the PDCCH is decoded incorrectly, data reception for all CCs will fail.

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

[0025] Figure 4 shows an example of scheduling operation (2). As shown in Figure 4, in conventional cross-carrier scheduling, PDCCH and DCI in other CCs schedule PDSCH / PUSCH to each CC.

[0026] Figure 5 shows an example of scheduling operation (3). As shown in Figure 5, in multi-carrier scheduling, a single DCI schedules PDSCH / PUSCH to each CC.

[0027] In a single DCI performing multi-carrier scheduling, it was unclear which fields should be common across CCs and which should be configured for each CC.

[0028] Therefore, to take advantage of the benefits of single DCI multi-carrier scheduling, a DCI design more suitable for a wider range of applications or environments may be implemented. For example, options 1) to 3) shown below may be applied.

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

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

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

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

[0033] For example, terminal 20 may assume a DCI size depending on the settings from base station 10.

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

[0035] For example, the specification may define fields that always notify a value for each CC, and / or fields that always notify a value common to all CCs. For example, fields that always notify a value for each CC may be HPN (HARQ process number), RV (Redundancy version), NDI (New data indicator), etc. For example, fields that always notify a value common to all CCs may be CIF (Carrier indicator field), PRI(), PDSCH-to-HARQ feedback timing indicator, etc. (See Non-Patent Literature 3).

[0036] Option 2) In the DCI used for multi-carrier scheduling, whether a value is notified for each CC to be scheduled, or whether a common value is notified among the CCs to be scheduled, may be determined by specific conditions. These specific conditions may be, for example, conditions related to intraband, interband, FR1, FR2, number of CCs, SCS, etc.

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

[0038] For example, whether the scheduled CCs include intraband only or interband may determine whether at least one field is common to all CCs or specific to each CC. The intraband only case may have more common fields or a smaller DCI size than the interband case.

[0039] For example, whether the scheduled CC consists only of intra-FRs or includes inter-FRs may determine whether at least one field is common to all CCs or specific to each CC. The case with only intra-FRs may have more common fields or a smaller DCI size than the case with inter-FRs.

[0040] For example, whether a predetermined FR is included in the scheduled CC may determine whether at least one field is common to all CCs or specific to each CC.

[0041] For example, whether at least one field is common to all CCs or specific to each CC may be determined by whether the number of CCs scheduled (the number dynamically notified or the maximum number set quasi-statically) is greater than or less than a predetermined value.

[0042] For example, whether the scheduled CC consists of only a single SCS or includes multiple different SCSs may determine whether at least one field is common to all CCs or specific to each CC. A single SCS may have more common fields or a smaller DCI size than one with multiple SCSs.

[0043] For example, whether a particular combination of SCS is included in the scheduled CC may determine whether at least one field is common to all CCs or specific to each CC.

[0044] For example, whether the scheduled CC consists only of licensed CCs or includes unlicensed CCs may determine whether at least one field is common to all CCs or specific to each CC.

[0045] Furthermore, options 1) and 2) above may be combined. For example, for a given field, whether the base station 10 can set a common CC or a CC-specific setting may be determined by the relationship between the CCs being scheduled.

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

[0047] 1) Multi-carrier scheduling DCI may be applicable to only a portion 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. For example, multi-carrier scheduling may be applicable only to non-fallback DCI and compact DCI.

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

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

[0051] Figure 8 is a flowchart showing an example (3) of scheduling operation in an embodiment of the present invention. In step S31, the base station 10 and the terminal 20 determine whether the DCI is applicable to multi-carrier scheduling based on predetermined conditions. In the subsequent step S32, the base station 10 performs multi-carrier scheduling on the terminal 20 using the applicable DCI.

[0052] Examples of implementations for each field in the DL grant are described below. For details on each field, please refer to Non-Patent Document 3.

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

[0054] Carrier indicator: This may always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field for specifying one or more scheduled cells. It may also be assumed to be per CC, or defined so that each field specifies the presence or absence of each of multiple scheduled cells, for example. It may switch between being common across CCs or per CC depending on specific conditions, such as 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 always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each field specifies the BWP for multiple scheduled cells, for example. It may switch between being common across CCs or per CC depending on certain conditions, for example, the maximum number of scheduled CCs set in RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0056] TDRA (Time Domain Resource Allocation): It may always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field to specify the TDRA for each of the multiple scheduled cells. It may also be assumed to be per CC, or it may be defined so that each of the multiple scheduled cells is specified by a separate field. Depending on specific conditions, for example, whether the SCS is common among the scheduled cells, it may switch between being common across CCs or per CC. In addition, combinations of candidate values ​​for the TDRA of each of the multiple cells may be set by RRC signaling. Constraints may be specified, such as all scheduled cells needing to have a common SCS.

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

[0058] Rate matching indicator: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells. It may also be assumed to be per CC; for example, each field may specify the rate matching 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 set by the RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed. The RRC signaling may set combinations of rate matching patterns for multiple cells.

[0059] ZP-CSI-RS trigger: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or, for example, each field may specify a ZP-CSI-RS trigger for multiple scheduled cells. Depending on certain conditions, for example, the maximum number of scheduled CCs set by RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduled DCI, this field may not be assumed. RRC signaling may set combinations of aperiodic ZP-CSI-RS resource sets for each of multiple cells.

[0060] MCS (Modulation and Coding Scheme): It may always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field for specifying an MCS common to multiple scheduled cells. Alternatively, it may be assumed to be per CC, or it may be defined so that each of the multiple scheduled cells has its own field. Depending on certain conditions, for example, the maximum number of scheduled CCs set by RRC signaling, it may switch between being common to CCs or per CCs.

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

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

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

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

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

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

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

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

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

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

[0071] Number of requested PDSCH group(s): This may always 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 always be assumed to be common across CCs, or it may be assumed to be a single field and value. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0073] Antenna port(s): May always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field specifying the antenna port for each of the multiple scheduled cells. Alternatively, it may be assumed to be per CC, or it may be defined so that each of the multiple scheduled cells is specified by a separate field. Depending on certain conditions, such as whether the scheduled cell is intraband or not, it may switch between being common across CCs or per CC.

[0074] Transmission configuration indication: This may always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field for specifying the TCI for each of the multiple scheduled cells. Alternatively, it may be assumed to be per CC, or it may be defined so that each of the multiple scheduled cells is specified by a separate field. Depending on specific conditions, such as whether the scheduled cell is intraband or not, it may switch between being common across CCs or per CC.

[0075] SRS request: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or, for example, each SRS request for multiple scheduled cells may be specified by a separate field. Depending on certain conditions, such as the maximum number of scheduled CCs set in the RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0076] SRS offset indicator: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each field specifies the SRS offset for each of multiple scheduled cells, for example. Depending on certain conditions, for example, the maximum number of scheduled CCs set in the RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed. The RRC signaling may set combinations of candidate SRS offset values ​​for each of multiple cells.

[0077] CBG transmission information (CBGTI): This may always be assumed to be per CC, or it may be defined so that each of the multiple scheduled cells is specified by a separate field. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0078] CBG flushing out information (CBGFI): This may always be assumed to be per CC, or it may be defined so that each of the multiple scheduled cells is specified by a separate field. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0079] DMRS sequence initialization: This may always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field specifying settings common to multiple scheduled cells. Alternatively, it may be assumed to be per CC, or defined as each of multiple scheduled cells having its own individual field. Depending on certain conditions, such as the maximum number of scheduled CCs set by RRC signaling, it may switch between common to CCs and per CCs.

[0080] Priority indicator: This may always be assumed to be common across CCs, i.e., a single field, or it may be defined as a single field specifying a setting common to multiple scheduled cells. It may also be assumed to be per CC, or defined as each of multiple scheduled cells having its own separate field. It may switch between common to CCs or per CCs depending on specific conditions, such as the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0081] ChannelAccess-CPext: This can always be assumed to be common across CCs, or it can be assumed to be 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 always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. Depending on certain conditions, such as the maximum number of scheduled CCs set by the RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0083] SCell dormancy indication: This may always 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 always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells. It may also be assumed to be per CC; for example, each of multiple scheduled cells may be specified by a separate field. It may switch between being common across CCs or per CC depending on certain conditions, such as the maximum number of scheduled CCs set in the RRC signaling. In the case of multi-carrier scheduled DCI, this field may not be assumed.

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

[0086] Examples of applications for each field in the UL grant are described below. For details on each field, please refer to Non-Patent Document 3.

[0087] DFI flag: This can always be assumed to be common across CCs, i.e., a single field; it can be assumed to be a notification for a specific cell; or it can be assumed to be a notification for all scheduled cells. It can also be assumed to be per CC; for example, each of multiple scheduled cells may be specified by a separate field. It may switch between being common across CCs or per CC depending on certain conditions, such as the maximum number of scheduled CCs set in the RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0088] TPC command (TPC command for scheduled PUSCH): This can always be assumed to be common across CCs, i.e., a single field; it can be assumed to be a notification for a specific cell; or it can be assumed to be a notification for all scheduled cells. It can also be assumed to be per CC; for example, each of multiple scheduled cells may be specified by a separate field. Depending on certain conditions, such as the maximum number of scheduled CCs set by RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduled DCI, this field may not be assumed.

[0089] UL / SUL indicator: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. Depending on certain conditions, for example, the maximum number of scheduled CCs set in the RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0090] SRS resource set indicator: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. It may switch between being common across CCs or per CC depending on certain conditions, such as the maximum number of scheduled CCs set by RRC signaling. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0091] SRS resource indicator: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. Depending on certain conditions, such as the maximum number of scheduled CCs set by RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0092] PTRS-DMRS association: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. Depending on certain conditions, for example, the maximum number of scheduled CCs set in the RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0093] The beta offset indicator (beta_offset_indicator) may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. Depending on certain conditions, such as the maximum number of scheduled CCs set by the RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduled DCI, this field may not be assumed.

[0094] UL-SCH indicator: This may always be assumed to be common across CCs, i.e., a single field; it may be assumed to be a notification for a specific cell; or it may be assumed to be a notification for all scheduled cells; or it may be assumed to be per CC; or it may be defined so that each of multiple scheduled cells is specified by a separate field. Depending on certain conditions, for example, the maximum number of scheduled CCs set by RRC signaling, it may switch between being common across CCs and per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0095] ChannelAccess-CPext-CAPC: This can always be assumed to be common across CCs, i.e., a single field; it can be assumed to be a notification for a specific cell; or it can be assumed to be a notification for all scheduled cells. It can also be assumed to be per CC; for example, each of multiple scheduled cells may be specified by a separate field. Depending on specific conditions, such as intraband or interband, it may switch between being common across CCs or per CC. In the case of multi-carrier scheduling DCI, this field may not be assumed.

[0096] In the embodiment described above, the base station 10 and terminal 20 can determine whether each field of the DCI used for multi-carrier scheduling is common to all carriers (CCs) or specific to each CC, thereby adjusting the trade-off between flexibility and performance.

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

[0098] (Device configuration) Next, we will describe an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above. The base station 10 and terminal 20 include functions to implement the embodiments described above. However, the base station 10 and terminal 20 may each have only some of the functions in the embodiments.

[0099] <Base station 10> Figure 9 shows an example of the functional configuration of a base station 10 in an embodiment of the present invention. As shown in Figure 9, the 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 Figure 9 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention.

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

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

[0102] The control unit 140 performs control related to multi-carrier scheduling, as described in the embodiment. The signal transmission function of the control unit 140 may be included in the transmission unit 110, and the signal reception function of the control unit 140 may be included in the reception unit 120.

[0103] <Terminal 20> Figure 10 shows an example of the functional configuration of a terminal 20 in an embodiment of the present invention. As shown in Figure 10, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 10 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

[0104] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. For example, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to other terminals 20 as D2D communication, and the receiving unit 220 receives PSCCH, PSSCH, PSDCH or PSBCH, etc. from other terminals 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 pre-configured setting information. The content of the setting information includes, for example, information related to multi-carrier scheduling.

[0106] The control unit 240 performs control related to multi-carrier scheduling, as described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0107] (Hardware configuration) The block diagrams (Figures 9 and 10) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of 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 it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0108] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0109] For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 11 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 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 explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0111] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0112] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0113] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 9 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 10 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line.

[0114] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0115] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0116] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

[0117] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., 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 different buses may be configured for each device.

[0119] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0120] Figure 12 shows an example of the configuration of vehicle 2001. As shown in Figure 12, vehicle 2001 comprises 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-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0121] The drive unit 2002 consists 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, which is operated by the user.

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

[0123] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0124] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0125] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), 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 driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0126] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 to the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 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 external devices. For example, it can send and receive various types of information to and from external devices 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 or a mobile station.

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

[0129] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle 2001. The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in 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, axles 2009, sensors 2021-2029, etc., installed in the vehicle 2001.

[0130] (Summary of the embodiments) As described above, according to an embodiment of the present invention, a terminal is provided which has a control unit that determines, based on certain conditions, whether a field included in the control information for performing multi-carrier scheduling is set for each scheduled carrier or set for all scheduled carriers, and a receiving unit that receives the control information from a base station, and the receiving unit receives each carrier scheduled by the control information based on the determination.

[0131] With the above configuration, the base station 10 and terminal 20 can decide whether each field of the DCI used for multi-carrier scheduling is common to all carriers (CCs) or specific to each CC, thereby adjusting the trade-off between flexibility and performance. In other words, multi-carrier scheduling can be performed in a wireless communication system using a single control information.

[0132] The aforementioned conditions may relate to at least one of the following: that the scheduled carrier is intraband, that the scheduled carrier is interband, the frequency range of the scheduled carrier, the number of carriers in the scheduled carrier, and the subcarrier spacing of the scheduled carrier. With this configuration, the base station 10 and the terminal 20 can decide whether each field of the DCI performing multicarrier scheduling is common to all CCs or per CC, and adjust the trade-off between flexibility and performance.

[0133] The aforementioned condition may be that the scheduled carrier is a single subcarrier interval, or that the scheduled carrier includes multiple subcarrier intervals. With this configuration, the base station 10 and terminal 20 can decide whether each field of the DCI performing multicarrier scheduling is common to all CCs or per CC, and adjust the trade-off between flexibility and performance.

[0134] The aforementioned condition may be whether or not the scheduled carrier includes a specific subcarrier interval. With this configuration, the base station 10 and terminal 20 can decide whether each field of the DCI performing multicarrier scheduling is common to all carriers (CCs) or per carrier, and adjust the trade-off between flexibility and performance.

[0135] The aforementioned condition may be that the scheduled carriers consist only of licensed carriers, or that the scheduled carriers include unlicensed carriers. With this configuration, the base station 10 and terminal 20 can decide whether each field of the DCI performing multi-carrier scheduling is common to all CCs or per CC, and adjust the trade-off between flexibility and performance.

[0136] Furthermore, according to an embodiment of the present invention, a communication method is provided in which a terminal performs the following steps: a control procedure for determining, based on certain conditions, whether a field included in control information for performing multi-carrier scheduling is set for each scheduled carrier or set for all scheduled carriers; a reception procedure for receiving the control information from a base station; 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 terminal 20 can decide whether each field of the DCI used for multi-carrier scheduling is common to all carriers (CCs) or specific to each CC, thereby adjusting the trade-off between flexibility and performance. In other words, multi-carrier scheduling can be performed in a wireless communication system using a single control information.

[0138] (Supplement to the embodiment) While 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, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but 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, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may 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 embodiments / models described herein and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0140] Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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 (where x is, for example, an integer or decimal)), 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)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

[0141] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

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

[0143] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0144] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0145] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0146] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0147] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0148] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0149] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

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

[0151] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0152] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0153] In this disclosure, terms such as "base station (BS)", "wireless base station", "base station equipment", "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 house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0155] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" 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 several other appropriate terms.

[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, the mobile body itself, etc. 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 be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0158] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0159] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0160] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0161] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0163] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0164] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0166] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0167] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist 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] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

[0170] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots 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] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[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 mini-slot may be called a TTI. In other words, at least one of a subframe and a 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, mini-slot, etc., instead of a subframe.

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

[0174] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0175] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0176] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0177] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0179] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0180] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

[0182] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology system in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. A Bandwidth Part (PRB) may be defined and numbered within a given BWP.

[0183] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0184] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0185] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0186] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0187] In this 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 "combine" may be interpreted similarly to "different."

[0188] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0189] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0190] <Note> The embodiments described above can also be further described as follows (see addendum).

[0191] (Note 1) A control unit that determines, based on certain conditions, whether a field included in the control information for multi-carrier scheduling is set for each scheduled carrier or set for all scheduled carriers, It has a receiving unit that receives the aforementioned control information from a base station, The receiving unit is a terminal that receives each carrier scheduled according to the control information based on the decision.

[0192] (Note 2) The terminal described in Appendix 1, wherein the aforementioned condition relates to at least one of the following: the scheduled carrier is intraband, the scheduled carrier is interband, the frequency range of the scheduled carrier, the number of carriers of the scheduled carrier, and the subcarrier interval of the scheduled carrier.

[0193] (Note 3) The terminal as described in Appendix 2, wherein the aforementioned condition is that the scheduled carrier is a single subcarrier interval or the scheduled carrier includes multiple subcarrier intervals.

[0194] (Note 4) The terminal described in Appendix 2, wherein the aforementioned condition is whether or not a specific subcarrier interval is included in the scheduled carrier.

[0195] (Note 5) The terminal as described in Appendix 2, wherein the aforementioned condition is that the scheduled carriers are either licensed carriers only or that the scheduled carriers include unlicensed carriers.

[0196] (Note 6) A control procedure that determines, based on certain conditions, whether a field included in the control information for multi-carrier scheduling is set for each scheduled carrier or set for all scheduled carriers, A receiving procedure for receiving the aforementioned control information from a base station, A communication method in which a terminal performs the procedure of receiving each carrier scheduled by the control information based on the aforementioned decision. [Explanation of symbols]

[0197] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive Unit 2003 Steering Department 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 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A receiving unit that receives RRC (Radio Resource Control) signaling from a base station, The system includes a control unit that obtains combinations of settings for each of the multiple cells scheduled by control information for multi-carrier scheduling from the RRC signaling, The receiving unit receives the control information from the base station, The control unit identifies one of the combinations of settings based on the fields included in the control information, The receiving unit is a terminal that receives each of the multiple cells based on the specified settings.

2. The terminal according to claim 1, wherein the control unit identifies a Time Domain Resource Allocation (TDRA), a rate matching indicator, a ZP-CSI-RS trigger, an SRS request, and an SRS offset indicator based on the field.

3. The procedure for receiving RRC (Radio Resource Control) signaling from a base station, A procedure for obtaining the combination of settings for each of the multiple cells scheduled by the control information for multi-carrier scheduling from the RRC signaling, A procedure for receiving the aforementioned control information from the base station, A procedure for identifying one of the combinations of settings based on the fields included in the control information, A communication method in which a terminal performs a procedure for receiving each of the multiple cells based on the specified settings.

Images