Method and apparatus for transmitting and receiving signals in a wireless communication system

Abstract

A method and apparatus for monitoring signals in a wireless communication system according to the present invention includes receiving DCI for scheduling PDSCH or PUSCH on different cells. Specifically, the DCI includes one or more DCI fields for PDSCH or PUSCH on different cells.

Description

Technical Field

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

Background Art

[0002] Wireless communication systems are widely deployed to provide various communication services such as voice and data. Generally, a wireless communication system is a multiple access system that can share available system resources (such as bandwidth and transmission power) to assist communication with multiple users. Examples of multiple access systems include CDMA (Code Division Multiple Access) systems, FDMA (Frequency Division Multiple Access) systems, TDMA (Time Division Multiple Access) systems, OFDMA (Orthogonal Frequency Division Multiple Access) systems, SC-FDMA (Single Carrier Frequency Division Multiple Access) systems, and the like.

Summary of the Invention

Problems to be Solved by the Invention

[0003] The technical problem to be achieved by the present invention is to provide a method and an apparatus therefor for efficiently transmitting and receiving control signals and data signals in a wireless communication system.

[0004] The technical problem of the present invention is not limited to the above-described technical problem, and other technical problems will be analogizable from the embodiments of the present invention.

Means for Solving the Problems

[0005] The present invention provides a signal reception method and an apparatus in a wireless communication system.

[0006] As one embodiment of the present invention, a method for a terminal (UE) to receive a signal in a wireless communication system includes receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on different cells, and receiving the PDSCH on the different cells based on the DCI. The DCI includes one transmission configuration indication (TCI) field for cells belonging to the same group among the different cells, and one code point of the TCI field is mapped to the same number of TCI states as the number of cells belonging to the group. A signal receiving method is provided.

[0007] As one embodiment of the present invention, a method for a base station (BS) to transmit a signal in a wireless communication system includes transmitting downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on different cells, and transmitting the PDSCH on the different cells based on the DCI. The DCI includes one transmission configuration indication (TCI) field for cells belonging to the same group among the different cells, and one code point of the TCI field is mapped to the same number of TCI states as the number of cells belonging to the group. A signal transmitting method is provided.

[0008] As another embodiment of the present invention, a method for a terminal (UE) to transmit a signal in a wireless communication system, comprising: receiving downlink control information (DCI) for scheduling physical downlink shared channels (PUSCHs) on different cells; and transmitting the PUSCHs on the different cells based on the DCI, wherein the DCI includes one precoding information and number of layers field for a first cell belonging to a first group among the different cells, each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each first cell, the TPMI for each first cell is determined based on the precoding information and number of layers field, one second precoding information and number of layers field per first cell is set for DCI for scheduling PUSCHs within a cell, and the number of bits of the precoding information and number of layers field is determined based on the maximum value among the number of bits of the set second precoding information and number of layers fields. A signal transmission method is provided.

[0009] As one embodiment of the present invention, a method for a base station (BS) to transmit a signal in a wireless communication system, the method including: receiving downlink control information (DCI) for scheduling physical downlink shared channels (PUSCHs) on different cells; and transmitting the PUSCHs on the different cells based on the DCI, wherein the DCI includes one precoding information and number of layers field for a first cell belonging to a first group among the different cells, each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each first cell, the TPMI for each first cell is determined based on the precoding information and number of layers field, one second precoding information and number of layers field per first cell is set for DCI for scheduling PUSCHs within a cell, and the number of bits of the precoding information and number of layers field is determined based on the maximum value among the number of bits of the set second precoding information and number of layers fields. A signal reception method is provided.

[0010] As another embodiment of the present invention, an apparatus, a processor, and a storage medium for performing the signal reception method are provided. Further, as another embodiment of the present invention, an apparatus, a processor, and a storage medium for performing the signal transmission method are provided.

[0011] The above apparatus includes at least a terminal, a network, and an autonomous vehicle capable of communicating with other autonomous vehicles other than communication devices.

[0012] The above-described embodiments of the present invention are only a part of the preferred embodiments of the present invention, and various embodiments reflecting the technical features of the present invention can be derived and understood by those with ordinary knowledge in the technical field based on the detailed description of the present invention described below.

Advantages of the Invention

[0013] According to an embodiment of the present invention, when control signals and data signals are transmitted and received between communication devices, there is an advantage that more efficient signal transmission and reception can be performed by an operation differentiated from the conventional invention.

[0014] The technical effects of the present invention are not limited to the above-described technical effects, and other technical effects will be conceivable from the embodiments of the present invention.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Modes for Carrying Out the Invention

[0016] The following technologies can be used in various wireless connection systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented by radio technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented by radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (registered trademark) (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0017] For the sake of clearer explanation, the description will be based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the present invention is not limited thereto. LTE means the technology after 3GPP TS 36.xxx Release 8. Specifically, the LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and the LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR means the technology after TS 38.xxx Release 15. LTE / NR can also be referred to as the 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR is referred to as the 3GPP system. For the background technology, terms, abbreviations, etc. used in the description of the present invention, reference can be made to the matters described in the standard documents published before the present invention. For example, the following documents can be referred to.

[0018] 3GPP NR

[0019] - 38.211: Physical channels and modulation

[0020] - 38.212: Multiplexing and channel coding

[0021] - 38.213: Physical layer procedures for control

[0022] - 38.214: Physical layer procedures for data

[0023] - 38.300: NR and NG-RAN Overall Description

[0024] - 38.331: Radio Resource Control(RRC) protocol specification

[0025] FIG. 1 illustrates the structure of a radio frame used in NR.

[0026] In NR, uplink and downlink transmissions are composed of frames. A radio frame has a length of 10 ms and is defined as two 5-ms half-frames (HF). A half-frame is defined as five 1-ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols with a cyclic prefix (CP). When normal CP is used, each slot contains 14 symbols. When extended CP is used, each slot contains 12 symbols. Here, the symbol can include an OFDM symbol (or a CP-OFDM symbol), an SC-FDMA symbol (or a DFT-s-OFDM symbol).

[0027] Table 1 illustrates that when normal CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change according to the SCS.

[0028] [Table 1]

[0029] Table 2 illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change according to the SCS.

[0030] [Table 2]

[0031] In the NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) is set to be different among multiple cells merged into one terminal (User Equipment; UE). As a result, the (absolute time) intervals of time resources (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) composed of the same number of symbols are different among the merged cells.

[0032] NR supports a number of OFDM (Orthogonal Frequency Division Multiplexing) numerologies (e.g., subcarrier spacing, SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth.

[0033] The NR frequency band is defined by two types of frequency ranges (FR1 / FR2). FR1 / FR2 is configured as shown in Table 3 below. Also, FR2 means millimeter wave (mmW).

[0034]

Table 3

[0035] Figure 2 illustrates the slot structure of the NR frame.

[0036] A slot contains a plurality of symbols in the time domain. For example, in the case of normal CP, one slot contains 14 symbols, while in the case of extended CP, one slot contains 12 symbols. A carrier contains a plurality of subcarriers in the frequency domain. An RB (Resource Block) is defined as a plurality (e.g., 12) of consecutive subcarriers in the frequency domain. In the frequency domain, a plurality of RB interleaves (simply, interleaves) are defined. An interleave m ∈ {0, 1,..., M - 1} is composed of (common) RBs {m, M + m, 2M + m, 3M + m,...}. M indicates the number of interleaves. A BWP (Bandwidth Part) is defined as a plurality of consecutive PRBs (Physical RBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier contains a maximum of N (e.g., 5) BWPs. Data communication is performed on the activated BWP, and only one BWP is activated for one terminal. Each element in the resource grid is called a resource element (RE), and one modulation symbol can be mapped to it.

[0037] In a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received by the base station and the terminal includes data and various control information, and there are various physical channels / signals depending on the type / usage of the information they transmit and receive. A physical channel corresponds to a set of resource elements (REs) that carry information derived from the upper layer. A physical signal corresponds to a set of resource elements (REs) used by the physical layer (PHY) but does not carry information derived from the upper layer. The upper layer includes the MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP (Packet Data Convergence Protocol) layer, RRC (Radio Resource Control) layer, etc.

[0038] The DL physical channels include PBCH (Physical Broadcast channel), PDSCH (Physical Downlink Shared channel), and PDCCH (Physical Downlink Control channel). The DL physical signals include DL RS (Reference Signal), PSS (Primary synchronization signal), and SSS (Secondary synchronization signal). The DL RS includes DM-RS (Demodulation RS), PT-RS (Phase-tracking RS), and CSI-RS (channel-state information RS). The UL physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel). The UL physical signals include UL RS. The UL RS includes DM-RS, PT-RS, and SRS (Sounding RS).

[0039] The base station is, for example, a gNodeB.

[0040] DCI for scheduling PDSCHs or PUSCHs on multiple serving cells

[0041] The above-described content can be applied in combination with the method proposed in the present invention described below, or supplemented to clarify the technical features of the method proposed in the present invention.

[0042] Also, the method described below can be similarly applied to the above-described NR system (licensed band) or shared spectrum, and it goes without saying that it can be deformed or substituted in accordance with the terms, expressions, structures, etc. defined in each system so that the technical idea proposed in the present invention is also embodied in the corresponding system.

[0043] In a CA situation where multiple cells are configured, in order to reduce the DCI overhead related to PDSCH / PUSCH scheduling (based on the justification as shown in Table 4), a multi-cell scheduling (multi-CC scheduling) method of simultaneously scheduling multiple serving cells / CCs with a single DCI is considered. In the present invention, the expression "scheduling multiple cells" is understood to mean "scheduling PDSCH or PUSCH transmitted from each of the multiple cells". In other words, a multi-cell DCI is a DCI for scheduling PDSCH or PUSCH on multiple cells that are different from each other.

[0044] Table 4, which is a justification for supporting the DCI for the aforementioned purpose and is understood as one of the motivations for the necessity of introducing such DCI (PDCCH).

[0045]

Table 4

[0046] In this regard, "multi-carrier enhancement" is being discussed with the aim of specifying a method for scheduling PUSCH or PDSCH on multiple serving cells with a single DCI.

[0047] In this specification, in order to more efficiently perform the operation of scheduling PUSCH or PDSCH on multiple serving cells with a single DCI, a scheduling method using a DCI field with a modified structure compared to the conventional DCI field is proposed. More specifically, a more efficient scheduling method is proposed by modifying the DCI field related to MIMO (multiple-input and multiple-output).

[0048] In this specification, one DCI that simultaneously schedules PUSCH (or PDSCH) on one or more serving cells is referred to as "m-CC DCI or multi-cell DCI". One DCI that has a conventional DCI format and schedules PUSCH (or PDSCH) on a single serving cell is referred to as "s-CC DCI or single-cell DCI". The m-CC DCI is distinguished by a DCI format, RNTI, an indicator field in the DCI, etc., which are different from the conventional s-CC DCI.

[0049] PUSCH (or PDSCH) for different numbers / combinations of serving cells can be scheduled by one m-CC DCI. As an example, only serving cell #1, serving cells #1 / 2, or serving cells #1 / 2 / 3 can be scheduled by the m-CC DCI. Such numbers / combinations are distinguished by a specific field in the DCI or RNTI, etc.

[0050] When only PUSCH (or PDSCH) on one cell is scheduled by the m-CC DCI, it is referred to as the "s-CC scheduling case". When PUSCH (or PDSCH) on multiple cells is scheduled, it is referred to as the "m-CC scheduling case".

[0051] Even for a single terminal, since the channel conditions etc. are different for each cell, the number of layers (for MIMO transmission) applied to each PDSCH or PUSCH is different. However, in order to provide such flexibility to the maximum extent, if all DCI fields indicating information for each cell are included in DCI, the payload size of m-CC DCI can increase significantly. In particular, in order for three or more cells to be scheduled simultaneously, a compact DCI field configuration is essential. Therefore, a configuration method (for reducing the DCI payload size) for the following fields related to MIMO operation among the fields included in m-CC DCI is proposed.

[0052] - Fields related to SRS resource indication (e.g., "SRS resource set indicator" field, "SRS resource indicator" field, "Second SRS resource indicator" field)

[0053] - Fields related to TPMI and layer number setting (e.g., "Precoding information and number of layers" field, "Second Precoding information" field)

[0054] - "Transmission configuration indication" field

[0055] Multiple CCs scheduled simultaneously by m-CC DCI (or multiple CCs scheduled by the m-CC DCI) are defined as co-scheduled CCs. The co-scheduled CCs (CCs belonging thereto) are grouped into one or more sub-groups. Also, a separate field is configured for each sub-group. Which CCs belong to each sub-group is preset by higher layer signaling. Each field (the value indicated thereby) is commonly applied to the CCs belonging within the sub-group. The sub-group is referred to as a shared CC group. When the attributes of the CCs belonging to the shared CC group are different, an attempt is made to propose a method in which a DCI field is commonly applied to the CCs.

[0056] Table 5 shows a classification of each field constituting m-CC DCI (i.e., DCI format 0_X / 1_X) into three types. DCI format 0_X is a DCI format for scheduling PUSCH on multiple cells, and DCI format 1_X is a DCI format for scheduling PDSCH on multiple cells. Type-1 is classified into three sub-types.

[0057]

Table 5

[0058] Corresponding to each type in Table 5, the terms described in this specification are as in Methods 1 to 4.

[0059] Method 1: shared-cell-common

[0060] Only one field is configured in the multi-cell DCI, and the value indicated by the DCI field is applied commonly to all cells (scheduled by the multi-cell DCI).

[0061] Method 2: shared-state-extension

[0062] Only one field is configured in the multi-cell DCI, and each of the multiple states that can be indicated by the DCI field is configured / set with a combination of multiple pieces of information regarding multiple cells (not information regarding a single cell).

[0063] Method 3: separate

[0064] The same number of fields as the number of cells (scheduled by the multi-cell DCI and with operations set according to the DCI field instructions) are configured (in the DCI), and each of the scheduled cells corresponds to an individual field, and the value indicated by the field is applied to the cell.

[0065] Method 4: shared-reference-cell

[0066] Only one field is configured in the multi-cell DCI, and the value indicated by the DCI field is applied only to a specific one of the reference cells (e.g., the cell where the DCI is transmitted or the cell with the lowest or highest cell index or the cell indicated by the CIF field value) among the cells (scheduled by the multi-cell DCI and with operations set according to the DCI field instructions), and a specific default value defined / set in advance is applied to the other cells.

[0067] Basically, the field to which the shared-cell-common method is applied corresponds to a type-1A field. The field to which the shared-state-extension method is applied corresponds to a type-1B field. The field to which the shared-reference-cell method is applied corresponds to a type-1C field. The field to which the separation method is applied corresponds to a type-2 field. The field whose method to be applied, among methods 1 to 4, can be changed by an explicit setting corresponds to a type-3 field.

[0068] In this specification, the content described for multi-cell scheduling for PDSCH is equally applicable to multi-cell scheduling for PUSCH. Also, the content described for the operation of multi-cell scheduling for PUSCH is equally applicable to multi-cell scheduling for PDSCH. Also, the places described as "cell" in this specification are also interpreted as the (active) BWP set / indicated for the cell.

[0069] On the other hand, the reference cell means a cell that has (i) the lowest (or highest) cell index, (ii) the earliest (or latest) indicated PDSCH / PUSCH transmission starting symbol time point, (iii) the earliest (or latest) indicated PDSCH / PUSCH transmission ending symbol time point, (iv) the cell indicated by the CIF field value, or (v) the cell pre-specified by RRC within the cell combination (i.e., co-scheduled cell set) simultaneously scheduled by the same multi-cell DCI (or within each cell subgroup described later).

[0070] If there are multiple cells with the earliest (or latest) PDSCH / PUSCH start symbol time, among those multiple cells, the cell with the lowest (or highest) cell index becomes the reference cell. If there are multiple cells with the earliest (or latest) PDSCH / PUSCH end symbol time, among those multiple cells, the cell with the lowest (or highest) cell index becomes the reference cell.

[0071] Alternatively, the reference cell means (i) the cell with the lowest (or highest) cell index, (ii) the cell indicated by the CIF field value, (iii) the cell where the multi-cell DCI is transmitted, or (iv) the cell pre-specified by the RRC within the set of all cells schedulable by any multi-cell DCI (i.e., schedulable cell set).

[0072] On the other hand, for the fields to which the shared-reference-cell method, shared-cell-common method, and / or shared-state-extension method are applied, only one field is configured within the multi-cell DCI (i.e., commonly applied to all cells belonging to the co-scheduled cell set).

[0073] Alternatively, for the fields to which the shared-reference-cell method, shared-cell-common method, and / or shared-state-extension method are applied, in a state where all cells belonging to the co-scheduled cell combination are grouped into one or more (or multiple) sub-groups, one field (commonly applied) is configured for each sub-group. Thus, individual / independent fields are configured between each sub-group. Thereby, the shared-reference-cell method, shared-cell-common method, and / or shared-state-extension method and the field / information configuration / indication method based thereon are applied for each sub-group.

[0074] Alternatively, in the case of a field to which a shared-reference-cell method, a shared-cell-common method, and / or a shared-state-extension method is applied, all cells belonging to the schedulable cell set are grouped into one or more (or multiple) sub-groups, and one field (applied commonly) is configured for each sub-group. Thus, individual / independent fields are configured between each sub-group. Thereby, the shared-reference-cell method, the shared-cell-common method, and / or the shared-state-extension method and the field / information configuration / instruction method based thereon are applied for each sub-group.

[0075] A sub-group is also referred to as a cell subgroup. A cell subgroup is composed / set of one specific or a specific plurality of cells belonging to the co-scheduled cell combination or the schedulable cell combination. For example, a cell subgroup is composed / set of some or all of the cells belonging to the co-scheduled cell combination or the schedulable cell combination.

[0076] In the conventional case, the DCI fields to which the shared-cell-common method is applied are structured such that a table composed of one or more states for each cell is preset in RRC or MAC-CE, and one of the one or more states within that table is indicated by that DCI field. The conventional case means when performing scheduling based on single-cell DCI. The one or more states are composed of different parameters / values or combinations thereof and correspond to the row indices of each table. Thus, "state" can be replaced by "index". Among the DCI fields, the PRB bundling size indicator, Rate matching (RM) indicator, ZP CSI-RS trigger, and SRS request fields correspond to this structure. The DCI fields corresponding to this structure operate based on one or more of the following three options. In the following options, the cell set refers to a schedulable cell combination, a co-scheduled cell combination, or a cell subgroup.

[0077] Opt X) The specific state indicated by the DCI field configured commonly for the cell set to which the shared-cell-common method is applied is interpreted / applied (for each cell) by the parameter / value or combination thereof corresponding to that state in the table set for each cell belonging to that cell set.

[0078] Opt Y) The specific state indicated by the DCI field configured commonly for the cell set to which the shared-cell-common method is applied is interpreted by the parameter / value or combination thereof corresponding to that state in the table set for a specific reference cell within that cell set and is applied commonly to the cells belonging to that cell set.

[0079] For a set of cells to which a common method is applied, the specific state indicated by a DCI field that is commonly configured is interpreted in a state where another common table applied commonly to that set of cells is preset in RRC / MAC-CE, with the parameter / value corresponding to that state in the common table or a combination thereof, and is applied commonly to the cells belonging to that set of cells.

[0080] [Common-T1A: Invalid state handling]

[0081] First, for the type-1A field or the aforementioned shared-cell-common method (specifically, the Opt X method), a more specific proposal is made as follows.

[0082] First, in the conventional s-CC DCI-based scheduling, for a specific DCI field (such as SRS resource indicator, Precoding information and number of layers), for each of the N states that can be indicated by the DCI field, N parameters / values or combinations thereof are preset in RRC or MAC-CE in a preset state. When one of the N states is indicated by the DCI field, the terminal applies the parameter / value or combination thereof set for the indicated state to perform the operation of PDSCH / PUSCH transmission and reception. In this case, the size of the DCI field is determined to be ceil{log 2 (N)} bits (or, K bits). Here, the N (or, K) value is set to a different (or, the same) value for each cell.

[0083] On one hand, in the scheduling of the m-CC DCI basis, for the case of the specific DCI field, as described above, when parameters / values or combinations thereof are preset for each cell for each state (applied to the scheduling of the s-CC DCI basis), and a specific state is indicated by that DCI field, the terminal interprets / applies for each cell the parameters / values or combinations thereof set for each cell for the indicated state, and performs the transmission / reception operations for the PDSCH / PUSCH scheduled for each cell.

[0084] On the other hand, in the scheduling of the m-CC DCI basis, the size of the specific DCI field is determined by any one of the following three methods using the maximum value N_max and the minimum value N_min of the N values set for each cell belonging to the set of all schedulable cells (or each co-scheduled cell set).

[0085] Alt-A) Based on the maximum value N_max, it is determined to be ceil{log 2 (N_max)} bits (in this case, the structure in which up to N_max states / indexes are indicated by the DCI field initially)

[0086] Alt-B) Based on the minimum value N_min, it is determined to be ceil{log 2 (N_min)} bits (in this case, the structure in which up to N_min states / indexes are indicated by the DCI field initially)

[0087] Alt-C) Based on a specific value (=N_exp) set separately, it is determined to be ceil{log 2 (N_exp)} bits (in this case, the structure in which up to N_exp states / indexes are indicated by the DCI field initially)

[0088] When applying the Alt-A mode or Alt-C mode, for a specific cell (cell X, for example, the cell set to N_low where N is a value less than N_max), when a specific state (for example, a state higher than {N_low - 1}) is indicated by a specific DCI field, there may be no parameter / value or combination thereof set to that state for cell X. Considering this case, the following operations are proposed. For convenience, define M = ceil{log2(N_max)} and K = ceil{log2(N_low)} (M ≥ K). Specifically, in the case of the Precoding information and number of layers field, the state corresponding to the Reserved value may or may not be included in N_max / N_low. Also, in the following, the values of the DCI field corresponding to N states / indexes are assumed to be 0,..., N - 1.

[0089] 1) Alt 1: For cell X, only the first K (MSB) bits or the last K (LSB) bits of the M bits in the DCI field are interpreted and applied.

[0090] A. On the other hand, if a state / index with a value higher than {N_low - 1} is indicated by the K bits, the operations of Alt 3 or Alt 6 are applied.

[0091] B. For example, in the case of the SRI (SRS resource indicator) field, when M = 3 and K = 2 assigned to cell X, only the first or last 2 bits of the 3 bits are utilized to interpret the SRI field.

[0092] C. For example, in the case of the Precoding information and number of layers field, when M = 5 and K = 4 assigned to cell X, only the first or last 4 bits out of 5 bits are utilized to interpret the precoding information and number of layers field.

[0093] 2) Alt 2: When a state with a value higher than {N_low - 1} is indicated by the DCI field, apply a specific parameter / value or a combination thereof that is separately set / defined in advance for cell X.

[0094] A. The specific parameter / value or a combination thereof is set / defined as a specific parameter / value or a combination thereof associated with a specific one (e.g., the lowest or highest) value among the N_low states preset for cell X.

[0095] B. For example, in the case of the SRI field, the specific parameter / value or a combination thereof is set / defined as an SRS resource index associated with a specific one (e.g., the lowest or highest) value among the N_low states preset for cell X, or as a specific SRS resource index (e.g., the lowest / highest index) associated with a specific L_max value (e.g., the lowest / highest L_max).

[0096] C. For example, in the case of the Precoding information and number of layers field, the specific parameter / value or a combination thereof is set / defined as a specific state (e.g., the lowest or highest state / index not associated with the Reserved value) among the N_low states preset for cell X.

[0097] 3) Alt 3: If a state with a value higher than {N_low - 1} is indicated by the DCI field, it is considered that there is no PDSCH / PUSCH scheduling for cell X.

[0098] A. As a result, the terminal omits the transmission and reception operations of PDSCH / PUSCH on cell X (in the case of PDSCH, feedbacks the corresponding HARQ-ACK as NACK).

[0099] B. For example, if a state with a value higher than {N_low - 1} is indicated for the SRI field, the terminal considers that there is no PUSCH / SRS scheduling for cell X and omits the transmission and reception operations of PUSCH / SRS on cell X.

[0100] C. For example, if a state with a value higher than {N_low - 1} is indicated for the precoding information and layer number field, the terminal considers that there is no PDSCH / PUSCH scheduling for cell X and omits the transmission and reception operations of PDSCH / PUSCH on cell X (in the case of PDSCH, feedbacks the corresponding HARQ-ACK as NACK).

[0101] 4) Alt 4: For cell X, an additional {N_max - N_low} = N_gap parameters / values or combinations thereof corresponding to each state from state N_low to N_max - 1 are additionally set and applied.

[0102] A. The additional parameters / values or combinations thereof are set with additional parameters / values or combinations thereof linked to specific N_gap states among the N_low states preset for cell X.

[0103] B. For example, in the case of the SRI field, SRS resources linked to a specific state among the N_low preset states are mapped to N_gap states.

[0104] C. For example, in the case of the precoding information and the layer number field, it is set with parameters / values or combinations thereof that are linked to specific N_gap states out of the N_low states (excluding the state / index corresponding to the Reserved value).

[0105] 5) Alt 5: For the cell X, it is interpreted and applied to the state corresponding to the value obtained by taking the modulo-N_low operation with respect to the state indicated by the DCI field.

[0106] A. As an example, when N_low = 5 and N_max = 8, each state {0, 1, 2, 3, 4, 5, 6, 7} indicated by the DCI field is interpreted / applied to the state {0, 1, 2, 3, 4, 0, 1, 2} for the cell X, respectively.

[0107] B. For example, in the case of the SRI field, when N_low = 5 and N_max = 8, each state {0, 1, 2, 3, 4, 5, 6, 7} indicated by the field is interpreted / applied to the respective SRS resource index #0 / 1 / 2 / 3 / 4 / 0 / 1 / 2 for the cell X.

[0108] C. For example, in the case of the precoding information and the layer number field, when N_low = 5 and N_max = 8, each state {0, 1, 2, 3, 4, 5, 6, 7} indicated by the DCI field is interpreted / applied to the state {0, 1, 2, 3, 4, 0, 1, 2} for the cell X, respectively.

[0109] 6) Alt 6: When a state with a value higher than {N_low - 1} is indicated by the DCI field, the most recently indicated state is directly applied / maintained for the cell X.

[0110] A. Thereby, the terminal directly applies / maintains the most recently indicated state for the cell X and performs the transmission / reception operation of PDSCH / PUSCH on the cell X.

[0111] B. For example, in the case of the SRI field, the terminal applies / maintains the SRI value most recently indicated for the cell X (by the SRI field on the same DCI format or a different DCI format) as it is, and performs the transmission / reception operation of PUSCH / SRS on the cell X.

[0112] C. For example, in the case of the precoding information and the layer number field, the terminal applies / maintains the state most recently indicated for the cell X (by the field on the same DCI format or a different DCI format) as it is, and performs the transmission / reception operation of PDSCH / PUSCH on the cell X.

[0113] [Common-T2:Field size determination]

[0114] Furthermore, regarding the method for determining the DCI field size for the type-2 field or the field to which the separation method is applied, the following specific proposal is made.

[0115] In the conventional s-CC DCI, for a specific DCI field, in a state where N states can be indicated by the DCI field, the size of the DCI field is set to L = ceil{log 2 (N)} bits. L is set to a different (or the same) value for each cell. The specific DCI field includes the SRI field, the precoding information, the layer number field, etc.

[0116] On one hand, in the m-CC DCI, when the specific DCI field is configured based on the method of the type-2 field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations set for the overall schedulable cell combinations, the sum L_sum of the L values set for each of the cells belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values calculated for each of the N_co co-scheduled cell combinations is determined as the size of the specific DCI field (configured within the m-CC DCI).

[0117] For example, in the case of the SRI field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations set for the overall schedulable cell combinations, the sum L_sum of the L values (for the SRI field) set for each of the cells belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values calculated for each of the N_co co-scheduled cell combinations is determined as the size of the SRI field (configured within the m-CC DCI).

[0118] For example, in the case of the precoding information and layer number field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations (particularly, cells with CB-based UL set) set for the overall schedulable cell combinations, the sum L_sum of the L values (for the precoding information and layer number field) set for each of the cells (particularly, cells with CB-based UL set) belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values calculated for each of the N_co co-scheduled cell combinations is determined as the size of the precoding information and layer number field (configured within the m-CC DCI).

[0119] [Configure table size for m-CC DCI (reduced than s-CC DCI)]

[0120] On the other hand, for a specific DCI field (such as SRI, Precoding information and number of layers, etc.) to which the following type-2 field design method is applied, N_cfg states that can be indicated by the DCI field in the m-CC DCI and the corresponding field size L_cfg = ceil{log2(N_cfg)} are set separately. In this case, it is set in the form of N_cfg < N and / or L_cfg < L. The type-2 field design method includes a method for determining the size of the DCI field for this purpose and / or a shared-cell-common method based on the Opt X method. N_cfg states and the corresponding field size L_cfg are set for each cell.

[0121] Specifically, as described above, when N_cfg states and a field size L_cfg are set separately for a specific DCI field in the m-CC DCI for a specific cell, for this cell, based on the number / set of the states and the field size, the following type-2 field design method is applied. If there is no other setting, based on the N states and the field size L set in the s-CC DCI, the following type-2 field design method is applied.

[0122] For example, in the case of the SRI field, for a specific cell X, a reference cell for the m-CC DCI usage, L_max, N_srs, and / or the number of SRS resources, etc. are defined / set / indicated. When configuring the SRI field in the m-CC DCI and / or when performing multiple CC schedulings by the m-CC DCI, for the said cell, based on the given reference cell, L_max, N_srs, and / or the number of SRS resources, N_cfg states and a field size L_cfg are determined. When configuring the SRI field in the m-CC DCI and / or when performing multiple CC schedulings by the m-CC DCI, for cells where the reference cell, L_max, N_srs, and / or the number of SRS resources, etc. are not defined / set / indicated, based on the N states and the field size L set in the s-CC DCI, the SRI field in the m-CC DCI for the said cell is configured.

[0123] For example, in the case of the Precoding information and number of layers field, for a specific cell X, constraints on the reference cell for m-CC DCI use, the maximum rank number, the valid / invalid row index among the rows of the table corresponding to the cell, and / or the codebookSubset parameter are defined / set / instructed as follows. When configuring the Precoding information and number of layers field in the m-CC DCI and / or when performing multiple CC scheduling using the m-CC DCI, for the cell, based on the given reference cell, the maximum rank number, the valid / invalid row index among the rows of the table corresponding to the cell, and / or the constraints on the codebookSubset parameter, N_cfg states and the field size L_cfg are determined. When configuring the Precoding information and number of layers field in the m-CC DCI and / or when performing multiple CC scheduling using the m-CC DCI, for cells where constraints on the reference cell, the maximum rank number, the valid / invalid row index among the rows of the table corresponding to the cell, and / or the codebookSubset parameter are not defined / set / instructed, based on the N states and the field size L set for the s-CC DCI, the Precoding information and number of layers field in the m-CC DCI for the cell is configured.

[0124] [1] Field related to SRS resource indication

[0125] Table 6 shows the DCI fields related to the indication of SRS resources described in 3GPP TS 38.212.

[0126]

Table 6-1

Table 6-2

[0127] <"SRS resource set indicator" field>

[0128] When multiple TRPs (Transmission and Reception Points) are configured for UL transmission of the terminal, this field indicates a single TRP among the TRPs that is used by the scheduled PUSCH, or this field indicates the transmission procedure of multiple TRPs used by the scheduled PUSCH. When the PUSCH is transmitted by a single TRP, it is called single-TRP operation, and when it is transmitted by multiple TRPs, it is called multi-TRP operation.

[0129] Table 7 is Table 7.3.1.1.2-36 described in 3GPP TS 38.212, and shows the fields and SRS resource sets configured for each value of the SRS resource set indicator field.

[0130]

Table 7

[0131] Considering the payload size of the m-CC DCI, in the m-CC DCI, this SRS resource set indicator field may not exist. Or, the SRS resource set indicator field exists in the DCI only in the case of s-CC scheduling, and does not exist in the DCI in the case of m-CC scheduling. Or, even in the case of s-CC scheduling, when multi-TRP UL operation is not configured for the scheduled cell, this field is defined not to exist. Therefore, the SRS resource set indicator field exists in the DCI only when scheduling in a cell that is in the s-CC scheduling case and for which multi-TRP UL operation is configured.

[0132] Alternatively, if the multi-TRP UL operation is set on a cell scheduled by the m-CC scheduling case or the s-CC scheduling case, but the field does not exist, it is predefined / set which single-TRP operation or multi-TRP operation corresponding to any code point is applied to the cell, or it is updated by a MAC CE (control element) or the like. As an example, when the multi-TRP UL operation is set for CC#1 and PUSCH is scheduled on a plurality of cells including CC#1 by the m-CC DCI, even if the SRS resource set indicator field does not exist, the terminal can interpret the SRS resource indicator field, the precoding information, and the layer number field based on the first SRS resource set information according to a preset rule (as if the "00" code point is indicated by the field). For example, the terminal assumes that the field corresponds to the code point "00" and is preset to operate in the mode. As a specific example, the preset method is a method of receiving an indication by the MAC CE in advance.

[0133] The following Options 1-1 and 1-2 disclose the application method of the "SRS resource set indicator" field when the CCs with the multi-TRP UL operation set and the CCs without the multi-TRP UL operation set are grouped into a shared CC group.

[0134] (Opt 1-1) When the CCs with the multi-TRP UL operation set and the CCs without the multi-TRP UL operation set are set in a shared CC group, the configuration of the SRS resource set indicator field is omitted, and the operations related to the SRS resource (or the SRS resource set) of the CC with the multi-TRP UL operation set are predefined or indicated by the MAC CE. For example, the terminal assumes that the field corresponds to the code point "00" and is predefined / set to operate in the mode.

[0135] (Opt 1-2) When the CCs with multi-TRP UL operation set and the CCs without multi-TRP UL operation set are configured in the shared CC group, the SRS resource set indicator field is present or configured in the DCI, and for the CCs without multi-TRP UL operation set, this field is ignored, and for the CCs with multi-TRP UL operation set, the index indicated by this field may be commonly applied.

[0136] <The "SRS resource indicator" field>

[0137] For the scheduled cell, the SRI indication method is different depending on whether the transmission scheme set in the terminal is codebook-based transmission or non-codebook-based transmission. Codebook-based transmission means that txConfig in PUSCH-Config, which is an RRC parameter, is set to "codebook". Codebook-based transmission is also called CB-based UL. Non-codebook-based transmission means that txConfig in PUSCH-Config, which is an RRC parameter, is set to "nonCodebook". Non-codebook-based transmission is also called NCB-based UL.

[0138] Specifically, in the case of NCB-based UL, the number of layers is determined according to how many SRS resources out of the number of SRS resources in the SRS resource set (= N_srs) are indicated. Therefore, the required number of bits of the SRI field is JPEG2025516215000010.jpg15146 (Here, L_max is the maximum number of PUSCH layers that the terminal can support). In the case of CB-based UL, one of the N_srs SRS resources is selected, and the number of layers is finally determined by the SRS resource and TPMI. Therefore, the required number of bits in the SRI field is JPEG2025516215000011.jpg10146 or the like.

[0139] In the case of cells with NCB-based UL scheduled by the same m-CC DCI, if there is a constraint that the number of layers is the same between these cells, the number of bits can be saved. Also, in the case of the "Second SRS resource indicator" field, when the number of layers is the same between two TRP transmissions, JPEG2025516215000012.jpg14146 bits are not required, but JPEG2025516215000013.jpg13146 bits are sufficient. Among multiple scheduled cells scheduled by the same m-CC DCI, if a specific cell is set as the reference cell, for the smallest cell, JPEG2025516215000014.jpg15146 bits are used to indicate the SRI, and for the other scheduled cells excluding the reference cell, JPEG2025516215000015.jpg14146 bits are used to indicate the SRI.

[0140] Among the plurality of scheduled cells, a rule for determining which cell is the reference cell is required. For example, the reference cell is defined and / or set to the cell with the lowest cell index, the cell with the highest cell index, the cell with the lowest SCS set, the cell with the highest SCS set, the scheduling cell where m-CC DCI is transmitted, the cell with the minimum number of SRS resources in the SRS resource set, or the cell with the maximum number of resources in the SRS resource set. Alternatively, the reference cell is defined and / or set to a specific (one) cell within each combination of scheduled cells based on the combination of cells scheduled by the m-CC DCI.

[0141] The constraint on the number of layers is only applicable to the m-CC scheduling case, and for the s-CC scheduling case, there may be no constraint on the number of layers. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (the operation according to the DCI field indication is set) are configured in the DCI. Also, each of the scheduled cells corresponds to an individual field, and the SRI field is configured in such a way that the value indicated by the field is applied to the cell. Such a method of configuring the field is referred to as the "Type-2 field design method".

[0142] In the case of cells with NCB-based UL configured, different L_max values are configured / applied according to the number of cells that m-CC DCI schedules (simultaneously). As an example, in the s-CC scheduling case, the L_max value follows a value predefined / configured for each cell, while in the m-CC scheduling case, the L_max value is restricted by K. The K value is predefined or configured. As an example, K = 1. Alternatively, in the scheduling case based on m-CC DCI, the L_max value is always restricted by K. The K value is predefined or configured. As an example, K = 1. At this time, the same number of fields as the number of cells scheduled by m-CC DCI (with the operation according to the DCI field indication configured) are configured in the DCI. Also, individual fields correspond to each of the scheduled cells, and the SRI field is configured in such a way that the value indicated by the field is applied to the cell. Such a method of configuring fields is referred to as the "Type-2 field design method".

[0143] In the case of cells with CB-based UL and / or NCB-based UL configured, different N_srs values are configured / applied according to the number of cells that m-CC DCI schedules (simultaneously). As an example, in the s-CC scheduling case, the N_srs value follows a value predefined / configured for each cell, while in the m-CC scheduling case, the N_srs value is restricted by K. The K value is predefined or configured. As an example, K = 1. Alternatively, in the scheduling case based on m-CC DCI, the N_srs value is always restricted by K. The K value is predefined or configured. As an example, K = 1.

[0144] On one hand, even if the number of SRS resources in the SRS resource set configured for a specific cell (in the case scheduled by s-CC DCI) is N1, in the scheduling case based on m-CC DCI or the m-CC scheduling case, only a smaller number (= N2) of SRS resources than N1 are allowed. In this case, a rule for which N2 SRS resources to select is needed. As an example, N2 SRS resources (or SRIs) corresponding to the lowest index, the highest index, or the index corresponding to a multiple of a specific N value in the SRS resource set are selected. Among the SRS resources in the SRS resource set, specific N2 SRIs may be separately preconfigured for the scheduling case based on m-CC DCI or the m-CC scheduling case.

[0145] As an example, in the s-CC scheduling case, the SRI field / information is configured / indicated based on N1 SRIs. In the m-CC scheduling case, for each cell, the SRI field / information is (individually) configured / indicated based on (less than N1) N2 SRIs. Alternatively, for the cell configured as the target of m-CC DCI scheduling, a setting constraint may be given such that only one SRS resource is always configured in the SRS resource set. At this time, the same number of fields as the number of cells scheduled by m-CC DCI (with the operation indicated by the DCI field configured) are configured in the DCI. Also, each scheduled cell corresponds to an individual field, and the SRI field is configured in such a way that the value indicated by the field is applied to the cell. Such a field configuration method is referred to as the "Type-2 field design method".

[0146] For multiple cells scheduled by the same m-CC DCI, if there is a required number of SRI code points for each cell, when an SRI field is configured in the m-CC DCI with only the number of bits obtained by converting the product of the required number of code points for each cell instead of the sum of the number of bits obtained by converting the required number of code points for each cell, the required number of bits can be minimized. For example, when PUSCH on cell #1 / 2 / 3 is scheduled by the m-CC DCI, 10 code points are required for cell #1, 10 code points for cell #2, and 10 code points for cell #3. When an SRI field is configured in the m-CC DCI with only the number of bits obtained by converting the product of the required code points for each cell, the SRI field is configured with ceil{log2(10x10x10)} = 10 bits instead of 4 + 4 + 4 = 12 bits.

[0147] As another method, a combination of multiple SRI information for multiple cells may be indicated by one code point. One code point is indicated by one SRI field configured in the m-CC DCI. As an example, when PUSCH on cell #1 / 2 / 3 is scheduled, the SRI field is configured with 1 bit. Specifically, when '0' is indicated by the 1-bit SRI field, the terminal recognizes that SRI = 0 for cell #1, SRI = 1 for cell #2, and SRI = 0, 1 for cell #3, and when '1' is indicated, the terminal recognizes that SRI = 1 for cell #1, SRI = 0 for cell #2, and SRI = 1, 2 for cell #3. In this way, the SRI value for each cell corresponding to each code point is preset and / or indicated by MAC CE. The final number of bits of SRI is determined according to how many code points' values are set and / or indicated by MAC CE. For example, when values for K code points are set, ceil{log2(K)} bits are allocated to one SRI field.

[0148] Furthermore, for each of the CB-based UL-configured cell and the NCB-based UL-configured cell scheduled by the same m-CC DCI, a method of instructing a combination of a plurality of SRI information for a plurality of cells by one code point is applied. For example, with two SRI fields configured in the m-CC DCI, the first SRI field instructs a combination of a plurality of SRI information for a plurality of cells with CB-based UL configured, and the second SRI field instructs a combination of a plurality of SRI information for a plurality of cells with NCB-based UL configured.

[0149] Options 2-1 to 2-3 disclose the application method of the "SRS resource indicator" field when the CC with NCB-based UL operation configured and the CC with CB-based UL operation configured are grouped into a shared CC group.

[0150] In Options 2-1 to 2-3, a constraint can be considered such that only the same type of CCs belong to the shared CC group. According to this constraint, all CCs belonging to the shared CC group are either configured only for NCB-based UL or only for CB-based UL.

[0151] (Opt 2-1) The number of code points indicated by the "SRS resource indicator" field required for each CC belonging to the same shared CC group is set to be the same. For example, the SRI field is configured based on the minimum value among the number of code points set for single-cell scheduling for each CC. In this case, for a CC with more code points set than that minimum value (e.g., N), only the code points corresponding to the lowest or highest N indices are indicated.

[0152] (Opt 2-2) The SRI field is configured based on the maximum value among the number of code points set for single-cell scheduling for each CC. If the code point indicated by the field is invalid for a specific CC, scheduling for that CC is considered not to exist.

[0153] (Opt 2-3) Basically, the SRI field is configured in the same manner as described in Opt 2-2 above. However, if the indicated code point is invalid for a specific CC, the terminal may operate to assume / apply a specific pre-defined / set code point for that CC.

[0154] Alternatively, it is allowed that different types of CCs belong to a shared CC group. That is, it is allowed that for a certain CC within the shared CC group, NCB-based UL is set, and for another certain CC, CB-based UL is set. Option A and Option B disclose the application method of the "SRS resource indicator" field when different types of CCs belong to a shared CC group.

[0155] (OptA) In this case, the number of code points required for each CC within the shared CC group is restricted to one, and that code point is pre-set or indicated by MAC CE. The SRI field configuration in DCI may be omitted.

[0156] (OptB) According to a specific type (for example, CB-based UL), the SRI field and / or the corresponding table are configured. For other types (for example, NCB-based UL), the default code point is applied. The default code point is pre-set or indicated by MAC CE. As a method for configuring the SRI field that suits a specific type in OptB, the above Opt 2-1 / 2-2 / 2-3 is applied.

[0157] When among the scheduled CCs, a certain CC has an NCB-based UL set and another certain CC has a CB-based UL set, (when there is no other setting for Type-1A or Type-2), the Type-2 method is applied to the SRI field. In other words, when there are different settings for the NCB-based UL or the CB-based UL among the CCs belonging within the scheduled CCs, the terminal does not expect a Type-1A setting in the SRI field. When all CCs are commonly set to the NCB-based UL or the CB-based UL, (when there is no other setting for Type-1A or Type-2), the Type-1A method is applied to the SRI field.

[0158] If, for a specific cell, multiple SRS resource sets are set (for m-TRP operation), when PUSCH / SRS on that specific cell is scheduled by m-CC DCI, it is necessary to determine which SRI within which SRS resource set is indicated by the SRI field. As one method, the SRS resource set corresponding to the highest or lowest SRS resource set index set for that specific cell is applied (or used / set) when scheduling PUSCH / SRS on that specific cell by m-CC DCI. As another method, the SRS resource set corresponding to a specific SRS resource set index is applied (or, used / set) when scheduling PUSCH / SRS on that specific cell by m-CC DCI according to the setting / indication of another base station.

[0159] <“Second SRS resource indicator” field>

[0160] This field is activated only when there is an indication by the SRS resource set indicator field that the second SRS resource set is valid, and otherwise is considered in a reserved state.

[0161] This field may not be present in m-CC DCI. Alternatively, it may be present only in the case of s-CC scheduling and not in the m-CC scheduling case. Even in the case of s-CC scheduling, if multi-TRP UL operation is not configured for the scheduled cell, this field may be defined as not present. For example, when scheduling is performed only for a cell that is in the s-CC scheduling case and for which multi-TRP UL operation is configured, a second SRS resource indicator field exists.

[0162] Alternatively, if it is indicated (e.g., by the method described above) that a second SRS resource set is valid on a cell scheduled by an m-CC scheduling case or an s-CC scheduling case, but this field is not present, it is predefined / set or updated (e.g., by MAC CE) which SRI corresponding to which code point is applicable to the cell. As one method, the terminal may consider that the same SRI as that indicated by the "SRS resource indicator" field is indicated for the cell. Alternatively, it is preset / defined which SRI on the second SRS resource set is used. As an example, the SRS resource with the lowest or highest index in the SRS resource set may be selected and a specific SRI may be preset. Alternatively, for a cell for which m-CC DCI is configured, a setting constraint is given such that only one SRS resource is always configured in the second SRS resource set.

[0163] For reference, according to the 3GPP agreement, if a CB-based SRS resource set or an NCB-based SRS resource set is configured for the UE, the PUSCH scheduled by multi-cell DCI is always associated with the first SRS resource set (If the UE is configured with two SRS resource sets with ‘codebook’ or ‘non-codebook’, a PUSCH scheduled by DCI format 0_X is always associated with the first SRS resource set with ‘codebook’ or ‘non-codebook’). Also, referring to Table 7, the first and second SRS resource sets correspond to the one with a lower ResourceSetId and the one with a higher ResourceSetId among the two SRS resource sets configured by the RRC parameter ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 (NOTE 1 in Table 7: The first and the second SRS resource sets are respectively the ones with lower and higher srs-ResourceSetId of the two SRS resources sets configured by higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2). srs-ResourceSetId is the ID of the SRS resource set and is indicated by an integer value from 0 to maxNrofSRS-ResourceSets - 1. maxNrofSRS-ResourceSets is, for example, 16.The first SRS resource set corresponds to the one with a lower index (a resource set with a lower index compared to the second SRS resource set), and the second SRS resource set corresponds to the one with a higher index (a resource set with a higher index compared to the index of the first SRS resource set). As a conclusion, if a CB-based SRS resource set or an NCB-based SRS resource set is configured for a terminal, the PUSCH scheduled by multi-cell DCI is always associated with the SRS resource set with a lower index.

[0164] As a specific example, when two NCB-based SRS resource sets are configured and an SRI value is given by the m-CC DCI field, the terminal applies the indicated SRI to the PUSCH repetition by the first SRS resource set.

[0165] In Options 3-1 and 3-2, a method for applying the "second SRS resource indicator" field when a CC with multi-TRP UL operation configured and a CC without such configuration are grouped into a shared CC group is proposed.

[0166] (Opt 3-1) When a CC with multi-TRP UL operation configured and a CC without such configuration are grouped into a shared CC group, the configuration of the "second SRS resource indicator" field is omitted, and the (SRS resource related) operation of the CC with multi-TRP UL operation configured is defined in advance, indicated by a MAC CE, or the value indicated by the SRI field is similarly applied to the second SRI.

[0167] (Opt 3-2) The "second SRS resource indicator" field exists or is configured, but for a CC without multi-TRP UL operation configured, the field is ignored. For a CC with multi-TRP UL operation configured, the index indicated by the field is commonly applied.

[0168] [2] Field related to TPMI and layer number setting

[0169] Table 8 shows the DCI fields related to the TPMI and the number of layers disclosed in 3GPP TS 38.212.

[0170]

Table 8-1

Table 8-2

Table 8-3

Table 8-4

[0171] <「Precoding information and number of layers」 field>

[0172] This field is required only for CB-based UL, particularly when the number of ports of the indicated SRS resource is two or more, and the TPMI (transmit precoding matrix information) and the number of layers are finally determined by this field.

[0173] In the case of a cell with CB-based UL scheduled by the same m-CC DCI, if there is a constraint that the number of layers is the same among those cells, the number of bits can be saved. This is similar to the principle that in the case of the "Second Precoding information" field, when the number of layers is the same between two TRP transmissions, up to about 1 to 2 bits can be saved. At this time, among the multiple scheduled cells scheduled by the same m-CC DCI, a specific one of the cells is set as the reference cell, and for the reference cell, the TPMI and the number of layers are indicated by only the necessary bits in the "Precoding information and number of layers" field. For the other scheduled cells except the reference cell, the TPMI and the number of layers are indicated by only the necessary bits in the "Second Precoding information" field.

[0174] A rule is required for which cell among the multiple scheduled cells is determined as the reference cell. A rule for determining the reference cell is predefined. For example, the reference cell is the cell with the lowest index, the cell with the highest index, the cell with the lowest SCS set, the cell with the highest SCS set, the scheduling cell where the m-CC DCI is transmitted, the cell with the minimum maxRank value set, or the cell with the maximum maxRank value set. Alternatively, the reference cell is defined and / or set to a specific (one) cell within each combination of scheduled cells based on the combination of cells scheduled by the m-CC DCI.

[0175] The restriction on the number of layers is only applied to m-CC scheduled cells, and for the s-CC scheduling case, there may be no such restriction on the number of layers as described above. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (with the operation according to the DCI field instruction set) are configured in the DCI. Also, each of the scheduled cells corresponds to an individual field, and the precoding information and the number-of-layers field are configured in such a way that the value indicated by the field is applied to the cell. Such a method of configuring fields is referred to as the "Type-2 field design method".

[0176] In the case of cells with CB-based UL configured, different maximum rank / number-of-layers are set / applied according to the number of cells scheduled by the m-CC DCI (simultaneously). As an example, in the s-CC scheduling case, the maxRank value follows a pre-defined / set value for each cell, while in the m-CC scheduling case, the maxRank value is restricted to K. Alternatively, in the scheduling case based on the m-CC DCI, the maxRank value is always restricted to K. Alternatively, for the cells set as the target of m-CC DCI scheduling, setting restrictions are given so that the maxRank value is always set only to K. The K value is set or defined in advance. As an example, K = 1. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (with the operation according to the DCI field instruction set) are configured in the DCI. Also, each of the scheduled cells corresponds to an individual field, and the precoding information and the number-of-layers field are configured in such a way that the value indicated by the field is applied to the cell. Such a method of configuring fields is referred to as the "Type-2 field design method".

[0177] It is not actually easy to match the precoder or the number of layers for each cell. Also, imposing a constraint on the number of layers has the drawback of reducing the data rate. Considering this, a separate table for each cell and an individual field for each corresponding cell are configured, and the TPMI and the number of layers are indicated for each cell by the individual field. A method of reducing the total number of bits required for the indication of the TPMI and the number of layers can be considered by adjusting the number of rows in the table for each cell.

[0178] As an example, as shown in Table 9 below, for 4 antenna port SRSs (Precoding information and number of layers for 4 antenna ports), when specific conditions (if transform precoder is disabled, maxRank = 2, and ul - FullPowerTransmission = fullpowerMode1, codebookSubset = partialAndNonCoherent) are met, signaling for 30 combinations of TPMI and the number of layers is required. However, when the cell is scheduled by m - CC DCI, the table can be configured with only some of the 30 rows corresponding to the 30 combinations. This can save the number of bits required to configure / indicate the "precoding information and number of layers" field / indication for the cell. As an example, if only 8 out of 30 rows are selected, only 3 bits instead of 5 bits are required for the indication of the TPMI and the number of layers for the cell.

[0179] At this time, for each cell (where the UL of the CB-base is set), whether to select only a specific row index from the conventional codebook to reduce the codebook size is set separately or predefined. For example, among the row indexes, only even indexes are selected, only indexes corresponding to multiples of a specific N value are selected, only the lowest specific number of indexes are selected, or only the highest specific number of indexes are selected.

[0180] The method is applied differently according to which cells are actually scheduled (the codebook sizes are different), and may not be applied to the s-CC scheduling case. As an example, in the s-CC scheduling case, based on Table 9 below, fields / information related to the TPMI and the number of layers are configured / indicated. In the m-CC scheduling case, fields / information related to the TPMI and the number of layers are configured / indicated based on only a specific part (e.g., 8 rows) of Table 9 below. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (where the operation according to the DCI field instruction is set) are configured in the DCI. Also, each of the scheduled cells corresponds to an individual field, and the precoding information and the number-of-layers field are configured in such a way that the value indicated by the field is applied to the cell. Such a method of configuring fields is referred to as the "Type-2 field design method".

[0181] As a method similar to this, the number of bits assigned to the field can be reduced by imposing constraints on the codebookSubset parameter. As an example, in the case scheduled by m-CC DCI, by not allowing the full-partial-and-non-coherent mode, 1-bit information can be saved. Alternatively, the constraints on this codebookSubset parameter may not be applied to the case scheduled by s-CC, and may be applied only to the case scheduled by m-CC. At this time, the same number of fields as the number of cells scheduled by m-CC DCI (where the operation according to the DCI field instruction is set) are configured in the DCI. Also, each of the scheduled cells corresponds to an individual field, and the precoding information and the number of layers field are configured in such a way that the value indicated by the field is applied to the cell. Such a method of configuring the field is referred to as the "Type-2 field design method".

[0182] Table 9 is Table 7.3.1.1.2-2A of 3GPP TS 38.212, and shows the table used when "Precoding information and number of layers for 4 antenna ports, if transform precoder is disabled, maxRank=2, and ul-FullPowerTransmission=fullpowerMode1".

[0183]

Table 9

[0184] Options 4-1 to 4-3 disclose the application method of the "precoding information and number of layers" field when the NCB-based UL operations configured CCs and the CB-based UL operations configured CCs are grouped into a shared CC group, or even when the shared CC group is grouped only for the CB-based UL operations configured CCs, but the table configurations referred to for each CC are different.

[0185] First, since the field itself is only necessary for the CCs with CB-based UL operations configured, when the CCs with NCB-based UL operations configured are included in the shared CC group (and also in the case of CCs with CB-based UL operations configured and the number of ports of the SRS resource being 1), the indication in the field for such CCs is ignored.

[0186] (Opt 4-1) The number of code points required for each CB-based UL operation configured CC within the same shared CC group is set in the same way. For example, the TPMI field is configured based on the minimum value among the number of code points set for each CC for single-cell scheduling. In this case, for the CCs with more code points set than the minimum value (e.g., N), only the code points corresponding to the lowest or highest N indexes are indicated.

[0187] (Opt 4-2) Alternatively, the TPMI field is configured based on the maximum value among the number of code points set for each CC for single-cell scheduling. If the code points indicated by the field are not valid for a specific CC, then for that CC, it is considered that there is no scheduling.

[0188] (Opt 4-3) If the TPMI field is configured in a similar manner to the above-mentioned Opt 4-3, or if the indicated code points are invalid for a specific CC, the terminal may operate to assume / apply specific predefined / set code points for that CC.

[0189] <「Second Precoding information」field>

[0190] This field is activated only when the SRS resource set indicator field indicates that a second SRS resource set is valid; otherwise, it is considered to be in a reserved state.

[0191] This field may not exist in m-CC DCI. Alternatively, it may exist only in the s-CC scheduling case and not in the m-CC scheduling case. Even in the s-CC scheduling case, if multi-TRP UL operation is not configured for the scheduled cell, this field may be defined as not existing. For example, when scheduling is performed only for a cell in the s-CC scheduling case and with multi-TRP UL operation configured, the second precoding information field exists.

[0192] Alternatively, if it is indicated (by the method etc.) that a second SRS resource set is valid on a cell scheduled by the m-CC scheduling case or the s-CC scheduling case, but this field does not exist, it is predefined / set or updated by a MAC CE etc. which TPMI / layer number corresponding to which code point is applied to the cell. As one method, the terminal may consider that the same TPMI / layer number as indicated by the "Precoding information and layer number" field (for the cell) is indicated. Alternatively, which TPMI / layer number is applied to the second SRS resource set is preset / defined.

[0193] Options 5-1 and 5-2 propose how the "second precoding information" field is applied when CCs with multi-TRP UL operation configured and those without such configuration are grouped into a shared CC group.

[0194] (Opt 5-1) When a CC with multi-TRP UL configured and a CC without such configuration are grouped into a shared CC group, the configuration of the "second precoding information" field is omitted, and the operation (related to precoding) of the CC with multi-TRP UL configured is either predefined, indicated by a MAC CE, or the value indicated by the "precoding information and number of layers" field is similarly applied to the second TRP as well.

[0195] (Opt 5-2) The "second precoding information" field exists or is configured, but for a CC without multi-TRP UL operation configured, the field is ignored.

[0196] [3] 「Transmission configuration indication」 field

[0197] Table 10 shows the TCI (Transmission configuration indication) field disclosed in 3GPP TS 38.212.

[0198]

Table 10

[0199] Depending on the per-cell configuration, the indication for the TCI state sets the operation of one of the following two modes as follows.

[0200] TCI mode #1: By upper layer signaling, TCI (or, in the case of UL, spatial relation RS and / or RS for path-loss setting) is individually set for each cell (or BWP). The upper layer signaling is, for example, RRC signaling.

[0201] TCI mode #2: By upper layer signaling, a list of cells (e.g., CC#1 / 2) that share TCI (or, in the case of UL, spatial relation RS and / or RS for path-loss setting) is set. When the TCI state is changed in one of the cells in the list (e.g., CC#1), the states of the other cells (e.g., CC#2) belonging to the list of cells are also commonly changed. The upper layer signaling is, for example, RRC signaling.

[0202] As one method to reduce the size of the TCI field, an independent TCI field is configured for each cell scheduled (simultaneously) by m-CC DCI, and the number of bits of the TCI field configured for each cell is less than 3 bits. As an example, when CC#1 and CC#2 are scheduled by m-CC DCI, a 2-bit TCI field corresponding to CC#1 and a 2-bit TCI field corresponding to CC#2 are individually configured, and the TCI field in the DCI is configured with a total of 4 bits.

[0203] At this time, the TCI states corresponding to the four code points for CC#1 and the four code points for CC#2 are set / indicated separately from the case scheduled by s-CC DCI. Alternatively, the TCI states corresponding to the four code points for CC#1 and the four code points for CC#2 are preset to a part of the TCI states preset / indicated in the case scheduled by s-CC DCI, or are defined by some code points with specific rules. For example, the TCI state corresponding to the code point having the lowest or highest index among the TCI states preset / indicated in the case scheduled by s-CC DCI is inherited (or used). Specifically, when a 2-bit TCI field is configured for each cell, the TCI states corresponding to code points 0 to 3 are used. Alternatively, the TCI state corresponding to some code points having an index corresponding to a multiple of a specific N value is inherited (or used).

[0204] An independent TCI field is configured for each cell scheduled (simultaneously) by m-CC DCI, and the number of bits of the TCI field configured for each cell is set to less than 3 bits, and the method is called a "separate reduced table".

[0205] If all the cells schedulable by the m-CC DCI are configured to operate in TCI mode #2 and are included in the cell list, instead of configuring a separate TCI field for each cell, only a common (single) TCI field is configured. Alternatively, if all the cells schedulable by the m-CC DCI (e.g., CC #1 / 2 / 3 / 4) are configured to operate in TCI mode #2 but are not included in a common cell list (Case 1: CC#1 / 2 belong to cell list #1, but CC#3 / 4 belong to cell list #2) or the TCI modes configured for each cell are different (Case 2: CC#1 / 2 belong to cell list #1, but CC#3 and CC#4 are configured with TCI mode #1), separate TCI fields are configured for each cell and / or for each cell list. In Case 1, one common TCI field / information is configured / indicated for CC#1 / 2, and another common TCI field / information is configured / indicated for CC#3 / 4. In this case, a total of two TCI fields are configured. In Case 2, one common TCI field / information is configured / indicated for CC#1 / 2, and individual TCI fields are configured for each of CC#3 and CC#4. In this case, a total of three TCI fields are configured. Between the cells included in the common cell list, only a common TCI field is configured, and when an independent TCI field is configured for each cell (or for each cell list), the number of bits assigned to each cell (or for each cell list) is set to less than 3 bits (by the method as described above).

[0206] As another method of reducing the size for the TCI field, one TCI field that is commonly used for cells scheduled (simultaneously) by m-CC DCI is configured, and for one code point indicated by the TCI field, the TCI states for each CC are interlocked. In other words, for one code point, combinations of multiple TCI states for multiple cells are set. As an example, when CC#1 and CC#2 are scheduled by m-CC DCI, one TCI field for CC#1 and CC#2 is configured. One TCI field indicates combinations of multiple TCI states corresponding to both of the two CCs for each code point. As an example, by code point 0, TCI state #1 for CC#1 and TCI state #2 for CC#2 are set / indicated simultaneously. At this time, the TCI states corresponding to each code point of one TCI field for CC#1 and CC#2 are set / indicated separately from the case scheduled by s-CC DCI. The method by which the TCI states for each CC are interlocked for one code point indicated by one TCI field is referred to as "code point extension".

[0207] Suppose that all the cells schedulable (simultaneously) by the m-CC DCI are configured to operate in TCI mode #2, and if they are included in the cell list, instead of the TCI states for each CC being associated with one code point, only one TCI state commonly applied to multiple cells is associated. Alternatively, all the cells schedulable by the m-CC DCI (e.g., CC #1 / 2 / 3 / 4) are configured to operate in TCI mode #2, but if they are not included in a common cell list (case A: CC#1 / 2 belong to cell list #1, while CC#3 / 4 belong to cell list #2), or if the TCI modes set for each cell are different (case B: CC#1 / 2 belong to cell list #1, while CC#3 and CC#4 are set to TCI mode #1), code points with different TCI states associated for each cell and / or for each cell list are configured. In case A, the TCI states for CC#1 / 2 and the TCI states for CC#3 / 4 are both associated with one code point, and the TCI field is configured at this code point. In case B, the TCI states for CC#1 / 2, the TCI state for CC#3, and the TCI state for CC#4 are all associated with one code point, and the TCI field is configured at this code point. For the cells included in the common cell list, only one TCI state commonly applied to the cell is associated with one code point.

[0208] Based on the proposed method described above (for cells scheduled by the same m-CC DCI), the following configurations are possible.

[0209] - Between the cells with TCI mode #1 set, the separate reduced table method or the code point extension method (based on a single field) is applied.

[0210] - For different cell lists with TCI mode #2 set, a separate reduction table method (based on a method of constructing one (common) TCI table for each cell list) or a code point extension method (based on a method of setting one (common) TCI state for each cell list) is applied.

[0211] - When a cell with TCI mode #1 set and a cell with TCI mode #2 set are scheduled simultaneously, the above method is applied for each TCI mode. Alternatively, in this case as well, the code point extension method is applied to all cells. In this case, for cells with TCI mode #2 set, one (common) TCI state is set for each cell list.

[0212] On the other hand, the proposed method described above is applied only to the m-CC scheduling case. In the s-CC scheduling case, exceptionally, TCI information is indicated based on the TCI field (and the TCI state associated with each code point) set for s-CC DCI.

[0213] Options 6-1 to 6-3 propose a method for applying the TCI field when a CC with the TCI field set and a CC without the TCI field set are grouped into a shared CC group.

[0214] (Opt 6-1) When a CC with the TCI field set and a CC without the TCI field set are grouped into a shared CC group, the TCI field configuration is omitted in the m-CC DCI for the shared CC group, and a specific default TCI is always assumed / applied.

[0215] (Opt 6-2) If a TCI field is configured in the m-CC DCI and a specific code point or index (e.g., 0 or state 0) is indicated, for the unconfigured CC, a specific default TCI is assumed / applied. If a code point other than the specific code point is indicated, the terminal considers that there is no scheduling for the unconfigured CC.

[0216] (Opt 6-3) If a TCI field is configured in the m-CC DCI, a specific default TCI is applied to the unconfigured CC.

[0217] Here, the specific default TCI is a specific index among the TCI state IDs set (for single-cell scheduling of the CC) (preset / defined in advance or indicated by MAC CE). Alternatively, the specific default TCI is the TCI information corresponding to a specific CORESET (e.g., the lowest-index CORESET of the latest slot from the indicated data).

[0218] Options 7-1 and 7-2 propose a method for applying the TCI field when CCs with the TCI field set are grouped into a shared CC group but different TCI modes are set between each CC (when a CC with TCI mode #1 and a CC with TCI mode #2 are grouped into a shared CC group).

[0219] Different from Options 7-1 and 7-2, setting constraints are given so that only CCs configured with the same TCI mode belong to the same shared CC group. In particular, when only CCs configured with TCI mode #2 are grouped into a shared CC group, setting constraints are given so that only CCs belonging to the same cell list belong to the group.

[0220] (Opt 7-1) If CCS (even if the CCS are in the same TCI mode #2 but belong to different lists) configured with different TCI modes belong to one shared CC group, the TCI field configuration in the m-CC DCI is omitted, and for each CC, the specific default TCI is assumed / applied.

[0221] (Opt 7-2) A TCI field / table is configured according to a specific CC (for example, a CC configured with TCI mode #2). For other CCs (for example, a CC configured with TCI mode #1), the specific default TCI is applied. Here, the specific default TCI is a specific index among the TCI state IDs set (for single-cell scheduling of the CC) (preset / defined in advance or indicated by a MAC CE). Alternatively, the specific default TCI is TCI information corresponding to a specific CORESET (for example, the lowest-index CORESET in the latest slot from the indicated data).

[0222] When the TCI field in the conventional s-CC DCI is set, 3 bits are allocated, and the mapping relationship between each code point and the TCI state index is updated by a MAC CE. However, when the TCI field in the m-CC DCI is configured by a code point extension method (based on a single field), it becomes difficult to simply update it by the conventional MAC CE. As a method to solve this,

[0223] - Alt-1: The mapping relationship between each code point of the TCI field in the m-CC DCI and the TCI state index for a plurality of cells is restricted to be updated only by RRC signaling (or RRC reconfiguration) and not by MAC CE (for s-CC DCI). For example, in conventional (e.g., Rel-15 / 16 / 17) MAC CE, only the TCI state associated with s-CC DCI is updated, and the TCI state associated with m-CC DCI is not updated.

[0224] - Alt-2: The mapping relationship between each code point of the TCI field in the m-CC DCI and the TCI state index for a plurality of cells is updated by MAC CE (for s-CC DCI), and rules and / or constraints for the update method are defined. As one method, only the same number (or less) of TCI state indexes as the number of TCI state indexes set in the TCI field of the m-CC DCI for a specific CC are updated by MAC CE. For example, in the table for the TCI field in the m-CC DCI as shown in Table 11 below, in the case of TCI update by MAC CE for CC1 (or CC3), a constraint of (maximum) 3 (1) is given. If it is signaled that the list of TCI indexes is updated from {1, 2, 3} to {2, 3, 4} by MAC CE for CC1, in Table 11, the terminal recognizes that the code point mapping for CC1 is updated to {2 for "00", 3 for "01", 3 for "10", 4 for "11"}. If it is signaled that the list of TCI indexes is updated from {4} to {1} by MAC CE for CC3, in Table 11, the terminal recognizes that the code point mapping for CC3 is updated to {1 for "00" / "01" / "10" / "11"}.

[0225] As another example, in the table for the TCI field in the m-CC DCI as shown in Table 11, in the case of TCI update by MAC CE for CC1, a constraint of three or less is given. If it is signaled that the list of TCI indexes is updated to a smaller number from {1, 2, 3} to {3, 4} by the MAC CE for the CC1, in Table 11 below, the terminal recognizes that the code point mapping for CC1 is updated to {3 for "00", 4 for "01", 4 for "10", 3 for "11"}. That is, if the previous TCI state is composed of N TCI state indexes {T_old.0, … T_old.N-1}, the latest TCI state is composed of K TCI state indexes {T_new.0, … T_new.K-1}, and N > K, the terminal recognizes that the previous N TCI states (and the corresponding code points) are replaced / updated / mapped to N of the latest TCI state indexes. For example, the TCI state index is updated to {T_new.0, … T_new.K-1, T_new.0, …} based on modulo-K operation. Alternatively, the TCI state index is updated to {T_new.0, … T_new.K-1, T_new.K-1, T_new.K-1, …} in a form where the last T_new.K-1 is repeated thereafter.

[0226]

Table 11

[0227] - Alt-3: The mapping relationship between each code point of the TCI field in the m-CC DCI and the TCI state index is such that either another MAC CE (for m-CC DCI) for updating the relationship is defined, or the conventional MAC CE (for s-CC DCI) is extended. The TCI state index for each code point of the TCI field (in m-CC DCI) for a specific CC is indicated by the other MAC CE or the conventional MAC CE. As an example, in the case of CC1 in Table 11 above, it is signaled that the TCI state index for each code point of the TCI field (in m-CC DCI) for CC1 is updated from {1, 2, 2, 3} to {2, 2, 4, 5} by the other MAC CE or the conventional MAC CE. As another method, the TCI state index for each CC corresponding to a specific code point of the TCI field (in m-CC DCI) is indicated by the other MAC CE. As an example, for code-point #01 in Table 11 above, it is signaled that the TCI state index for each CC is updated from {1, 2, 4, 5} to {2, 3, 3, 4} by the other MAC CE.

[0228] On the other hand, the content of the present invention is not limited to signal transmission and reception in the uplink and / or downlink. For example, the content of the present invention can also be applied to direct communication between terminals. Also, the base station in the present invention is a concept that includes not only a Base Station but also a relay node. For example, the operation of the base station in the present invention may be performed by the base station (Base Station) or by the relay node.

[0229] Since an example of the above-described proposed method is also included as one of the implementation methods of the present invention, it can be regarded as a kind of proposed method. Also, the above-described proposed method may be implemented independently, or may be implemented in the form of a combination (or merger) of some proposed methods. Information regarding the application or non-application of the above-described proposed method (or information regarding the rules of the proposed method) can be defined such that the base station notifies the terminal or the transmitting terminal notifies the receiving terminal by a predetermined signal (for example, a physical layer signal or a higher layer signal).

[0230] Embodiment

[0231] FIG. 4 and FIG. 5 show flowcharts of signal transmission and reception methods according to embodiments of the present invention.

[0232] Referring to FIG. 4, one embodiment of the present invention includes a step (S401) of receiving, by a terminal, DCI for scheduling PDSCHs on different cells from each other, and a step (S403) of receiving the PDSCHs on the different cells from each other based on the DCI.

[0233] Referring to FIG. 5, another embodiment of the present invention includes a step (S501) of transmitting, by a base station, DCI for scheduling PDSCHs on different cells from each other, and a step (S503) of transmitting the PDSCHs on the different cells from each other based on the DCI.

[0234] In addition to the operations of FIGS. 4 and / or 5, any one or more of the operations described in "DCI for scheduling PDSCHs or PUSCHs on multiple serving cells" and Sections [1] to [3] may be further performed.

[0235] For example, referring to [3], the DCI for scheduling PDSCH on different cells includes a TCI field. This TCI field is configured by the "code point extension" method. When the TCI field is configured by the code point extension method, since one common TCI table is configured for cells belonging to the same cell list among different cells with TCI mode #2 set, the DCI includes one TCI field for one cell list. A cell list is composed of a set of multiple cells and is expressed as a group, cell group, or sub-group. In other words, the DCI includes one TCI field for cells belonging to the same group among different cells.

[0236] Also, according to the code point extension method, combinations of multiple TCI states for multiple cells are set for the code point of one TCI field. For example, when CC#1 and CC#2 are scheduled by m-CC DCI, one TCI field for CC#1 and CC#2 is configured. One code point value of one TCI field indicates combinations of multiple TCI states corresponding to both of the two CCs. When three or more CCs are scheduled by a single DCI, if the three or more CCs belong to the same cell list (or cell group), one code point value of one TCI field included in the single DCI indicates combinations of multiple TCI states corresponding to all of the three or more CCs. The mapping relationship between the code point and the TCI state is set by the MAC CE (TCI States Activation / Deactivation for UE-specific PDSCH MAC CE). Generally speaking, one code point of one TCI field included in the DCI for scheduling PDSCH on different cells is mapped to the same number of TCI states as the number of cells belonging to one group.

[0237] According to the code point extension method, all cells schedulable by m-CC DCI are set to operate in TCI mode #2. When included in the cell list, m-CC DCI contains only one TCI field. Although all cells schedulable by m-CC DCI are set to operate in TCI mode #2, when included in different cell lists, different TCI fields are configured for each cell list. Therefore, when different cells scheduled by DCI belong to different cell lists, DCI includes one TCI field per cell list. If there are two cell lists (cell groups), DCI includes a first TCI field for the first cell group and a second TCI field for the second cell group. Thus, one code point of the first TCI field is mapped to the same number of TCI states as the number of cells belonging to the first group, and one second code point of the second TCI field is mapped to the same number of TCI states as the number of cells belonging to the second group.

[0238] Also, according to the code point extension method, when the TCI modes set for each cell of the cells schedulable by m-CC DCI are different, different TCI fields are configured for each TCI mode. Therefore, when some of the different cells scheduled by DCI are set to TCI mode #2 and belong to one cell list, and one or more specific cells are set to TCI mode #1 and do not belong to the cell list, DCI includes one first TCI field for the cells belonging to the first group and one second TCI field per specific cell. One code point of the first TCI field is mapped to the same number of TCI states as the number of cells belonging to the first group, and one second code point of the second TCI field is mapped to one TCI state.

[0239] Therefore, when the cells scheduled by the m-CC DCI are composed of cells belonging to different cell lists set to TCI mode #2 and a plurality of cells set to TCI mode #1, the m-CC DCI includes TCI fields only in the sum of the number of cell lists and the number of cells set to TCI mode #1.

[0240] Since the TCI mode is set based on upper layer signaling, a specific cell is set not to belong to any cell list (cell group) based on upper layer signaling. Cells belonging to a specific cell list are also set based on upper layer signaling.

[0241] On the other hand, the code point extension method is applied only to the m-CC scheduling case and may not be applied to the s-CC scheduling case. According to this, when only one PDSCH is scheduled by DCI for scheduling PDSCHs on different cells, the code point extension method is not used, and the m-CC DCI includes one TCI field set for the s-CC DCI. When the TCI field in the case where a plurality of cells are scheduled by the m-CC DCI is defined as the first TCI field, when one cell is scheduled by the m-CC DCI, the m-CC DCI includes a second TCI field different from the first TCI field. One code point of the first TCI field is mapped to the same number of TCI states for the m-CC DCI as the number of cells belonging to the first group, and one second code point of the second TCI field is mapped to the TCI state for one s-CC DCI.

[0242] The DCI format of the DCI for scheduling PDSCHs on different cells is referred to as DCI format 1_X, where X is a natural number of 3 or more. For example, the DCI format of the DCI for scheduling PDSCHs on different cells is DCI format 1_3.

[0243] FIG. 6 and FIG. 7 show flowcharts for signal transmission and reception methods according to other embodiments of the present invention.

[0244] Referring to FIG. 6, one embodiment of the present invention includes a step (S601) of receiving, by a terminal, DCI for scheduling PUSCHs on different cells from each other, and a step (S603) of transmitting PUSCHs on the different cells from each other based on the DCI.

[0245] Referring to FIG. 7, another embodiment of the present invention includes a step (S701) of transmitting, by a base station, DCI for scheduling PUSCHs on different cells from each other, and a step (S703) of receiving PUSCHs on the different cells from each other based on the DCI.

[0246] In addition to the operations of FIGS. 6 and / or 7, any one or more of the operations described in "DCI for scheduling PDSCHs or PUSCHs on multiple serving cells" and Sections [1] to [3] may be further performed.

[0247] For example, the DCI for scheduling PUSCHs on different cells from each other includes any one or more fields of an SRS resource set indicator, an SRS resource indicator, a second SRS resource indicator, precoding information and the number of layers, and second precoding information.

[0248] Each DCI field is configured based on any one or more combinations of the methods disclosed in Sections [1] and [2].

[0249] Specifically, referring to section [2], each CC belonging to the same shared CC group also has a different table configuration to be referred to. At this time, when Opt 4-2 is applied, one TPMI field for the shared CC group is configured based on the maximum value among the number of code points set for DCI for single-cell scheduling (scheduling of PUSCH within one cell). The TPMI field means the "Precoding information and number of layers" field for indicating the TPMI. The TPMI is used to determine the transmission precoder when the terminal transmits the PUSCH. The number of code points is related to the number of bits of the precoding information and number of layers field. If the number of code points is N, the number of bits of the precoding information and number of layers field is determined as ceil{log 2 (N)}. Therefore, for each first cell, the "number of bits of the precoding information and number of layers field (second precoding information and number of layers field) for single-cell scheduling" is determined based on the number of code points set for single-cell scheduling for each cell.

[0250] In summary, for the first cell belonging to the same shared CC group (the first group) among different cells schedulable by m-CC DCI, one precoding information and layer number field are included. Each PUSCH of the first cell is transmitted based on the transmission precoder determined by the TPMI for each first cell. The TPMI for each first cell is given by one precoding information and layer number field for the first group. Also, the number of bits of one precoding information and layer number field is determined based on the maximum value among the number of bits of the precoding information and layer number field set for single cell scheduling for each first cell. Furthermore, one precoding information and layer number field for the first group also indicate the number of layers for each first cell.

[0251] The number of code points for each first cell is determined based on the number of row indexes of the table set for single cell scheduling for each first cell. Referring to Tables 8 and 9, the table for single cell scheduling is determined based on the number of antenna ports, codebook-based transmission, full power transmission mode, transform precoder, maximum rank, and codebook subset. Therefore, the number of bits for each of the second precoding information and layer number field of the first cell is determined based on the number of antenna ports, codebook-based transmission, full power transmission mode, transform precoder, maximum rank, and codebook subset set for single cell scheduling in each of the first cells.

[0252] For reference, the number of antenna ports is 1, 2, or 4. Codebook-based transmission is determined based on the RRC parameter txConfig regarding whether the UE uses codebook-based or non-codebook-based transmission. If there is no txConfig parameter, the UE transmits the PUSCH on one antenna port. The full power transmission mode is set based on the RRC parameter ul-FullPowerTransmission regarding whether the UE is configured with the UL full power transmission mode. Specifically, the ul-FullPowerTransmission parameter includes three mode settings: fullpower, fullpowerMode1, and fullpowerMode2, and the specific operations for each mode follow the operations in Section 7.1 of 3GPP TS 38.213. The transform precoder is determined based on the RRC parameter transformPrecoder regarding the UE specific selection of the transform precoder for the PUSCH. If there is no transformPrecoder parameter, the UE uses the transform precoder value of Msg3 used in the random access procedure. The maximum rank is a subset of the PMIs (precoding matrix indicators) processed by the TRI (transmission rank indicator) and is set to one value from 1 to 4 by the RRC parameter maxRank.The codebook subset is a subset of PMIs processed by the TPMI (Subset of PMIs addressed by TPMI) and is set to one of the values of fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent by the codebookSubset, which is an RRC parameter.

[0253] In other words, the precoding information and the layer number field are determined to be the maximum value among the M bits related to N different cells when the field is set to type 1A. For N cells, the M bits for each cell are determined based on the number of antenna ports, codebook-based transmission, full power transmission mode, transform precoder, maximum rank, and codebook subset.

[0254] Since a table independently set for each first cell is used, even if the same row index is indicated in each table by one value of one precoding information and layer number field, the TPMI value corresponding to the row index of each table corresponds to an independent value for each cell.

[0255] Here, since the precoding information and the layer number field are set based on the maximum number of bits among the second precoding information and the layer number field, there may be a case where there is no row index corresponding to a specific value of the precoding information and the layer number field for a specific cell. According to Opt 4-2, for a specific cell without a TPMI value corresponding to one value of the precoding information and the layer number field, the terminal considers that the PUSCH is not scheduled. Alternatively, according to Opt 4-3, for a specific cell without a TPMI value corresponding to one value of the precoding information and the layer number field, the terminal transmits the PUSCH based on a predefined specific TPMI value.

[0256] Since one precoding information and layer number field is set per shared CC group, for a second cell belonging to a second group that is not the first group among different cells schedulable by DCI, precoding information and layer number fields (third precoding information and layer number fields) separated from the precoding information and layer number fields for the first group are included in the DCI.

[0257] Also, the shared CC group includes both a CC with CB-based UL operation set and a CC with NCB-based UL operation set. However, the terminal ignores the precoding information and layer number fields for the CC with NCB-based UL operation set. Thus, when non-codebook-based transmission is set for the PUSCH of a specific cell among the first cells, the terminal does not use the values of the precoding information and layer number fields and transmits the PUSCH on the specific cell.

[0258] Furthermore, referring to section [1], the terminal transmits PUSCHs on different cells based on the SRS resource set set for each cell. When multiple SRS resource sets are set for a specific cell, the terminal transmits the PUSCH on the specific cell based on the resource set with the highest or lowest index among the SRS resource sets set for the specific cell.

[0259] Also, referring to Opt 2-1 to 2-3, one SRI field is included for a first cell belonging to the same shared CC group (first group) among different cells schedulable by m-CC DCI. The number of bits of one SRI field is determined based on the maximum value among the number of bits of the SRI fields set for single cell scheduling for each first cell.

[0260] In other words, the SRI field is determined to be the maximum value among the M bits related to N mutually different cells when the field is set to Type 1A. Referring to Table 6, for N cells, the M bits for each cell are set based on (i) the number of configured SRS resources N_SRS and (ii) L_max, which is the maximum number of MIMO layers to be used for PUSCH in all UL BWPs of the serving cell, when the UL of the cell is set to NCB-based (txConfig = nonCodebook). Also, for N cells, the M bits for each cell are determined based on the number of configured SRS resources N_SRS when the UL of the cell is set to CB-based (txConfig = Codebook). Furthermore, when multiple SRS resource sets are configured for one cell, since the first SRS resource set with a lower index is used, the number of configured SRS resources N_SRS is the number of SRS resources configured in the first SRS resource set among the first SRS resource set and the second SRS resource set.

[0261] The DCI format of the DCI for scheduling PUSCHs on mutually different cells is referred to as DCI format 0_X, where X is a natural number of 3 or more. For example, the DCI format of the DCI for scheduling PUSCHs on mutually different cells is DCI format 0_3.

[0262] Furthermore, in addition to the operations described in FIGS. 4 to 7, any one or more of the operations described in FIGS. 1 to 3 and / or the operations described in "DCI for scheduling PDSCHs or PUSCHs on multiple serving cells" and Sections [1] to [3] may be combined and performed.

[0263] Communication system and apparatus to which the proposal of the present invention is applied

[0264] Without being limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of the present invention disclosed in this specification can be applied to various fields that require wireless communication / connection between devices (e.g., 5G).

[0265] The following will be described more specifically with reference to the drawings. In the following figures / descriptions, the same reference numerals exemplify the same or corresponding hardware blocks, software blocks, or functional blocks unless otherwise specifically mentioned.

[0266] FIG. 8 illustrates a communication system 1 applied to the present invention.

[0267] Referring to FIG. 8, the communication system 1 applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device means a device that communicates using a wireless connection technology (e.g., 5G NR, LTE), and is also referred to as a communication / wireless / 5G device. Without being limited thereto, the wireless devices include a robot 100a, vehicles 100b-1, 100b-2, an XR (Extended Reality) device 100c, a hand-held device 100d, a home appliance 100e, an IoT (Internet of Thing) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with a wireless communication function, autonomous driving vehicles, vehicles capable of performing vehicle-to-vehicle communication, etc. Here, the vehicles include UAVs (Unmanned Aerial Vehicles) (e.g., drones). The XR device includes AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and is embodied in the form of an HMD (Head-Mounted Device), a HUD (Head-Up Display) equipped on a vehicle, a TV, a smartphone, a computer, a wearable device, a home appliance, a digital signboard, a vehicle, a robot, etc. The hand-held devices include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., notebook computers, etc.). The home appliances include TVs, refrigerators, washing machines, etc. The IoT devices include sensors, smart meters, etc. For example, the base station and the network are also embodied in the wireless device, and a specific wireless device 200a can also operate as a base station / network node for other wireless devices.

[0268] Wireless devices 100a to 100f are connected to network 300 via base station 200. AI (Artificial Intelligence) technology is applied to wireless devices 100a to 100f, and wireless devices 100a to 100f are connected to AI server 400 via network 300. Network 300 is configured using a 3G network, 4G (e.g., LTE) network, or 5G (e.g., NR) network, etc. Wireless devices 100a to 100f can communicate with each other via base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0269] Wireless communications / connections 150a, 150b, and 150c are performed between wireless devices 100a to 100f / base station 200 and between base stations 200 / 200. Here, the wireless communications / connections are uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and communication 150c between base stations (e.g., performed by various wireless connection technologies such as relay, IAB (Integrated Access Backhaul) (e.g., 5G NR)). Through wireless communications / connections 150a, 150b, and 150c, wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communications / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. For this purpose, based on various proposals of the present invention, any one of the setting processes of various configuration information for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes is performed.

[0270] Examples of wireless devices to which the present invention is applied

[0271] FIG. 9 illustrates a wireless device applicable to the present invention.

[0272] Referring to FIG. 9, the first wireless device 100 and the second wireless device 200 transmit and receive wireless signals by various wireless connection technologies (e.g., LTE, NR). Here, {the first wireless device 100, the second wireless device 200} corresponds to {the wireless devices 100a to 100f, the base station 200} and / or {the wireless devices 100a to 100f, the wireless devices 100a to 100f} in FIG. 8.

[0273] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceiver 106, and is configured to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. For example, after the processor 102 processes the information in the memory 104 to generate a first information / signal, the transceiver 106 transmits a wireless signal including the first information / signal. Also, after the processor 102 receives a wireless signal including a second information / signal by the transceiver 106, the information obtained from the signal processing of the second information / signal is stored in the memory 104. The memory 104 is connected to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing part or all of the processes controlled by the processor 102, or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. Here, the processor 102 and the memory 104 are part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). The transceiver 106 is connected to the processor 102 and transmits and / or receives wireless signals through one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 can also be used interchangeably with an RF (radio Frequency) unit. In the present invention, the wireless device can also mean a communication modem / circuit / chip.

[0274] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 controls the memory 204 and / or the transceiver 206, and is configured to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. For example, after the processor 202 processes the information in the memory 204 to generate third information / signals, the transceiver 206 transmits a wireless signal including the third information / signals. Also, after the processor 202 receives a wireless signal including fourth information / signals by the transceiver 206, the information obtained from the signal processing of the fourth information / signals is stored in the memory 204. The memory 204 is connected to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code that performs some or all of the processes controlled by the processor 202, or includes instructions for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. Here, the processor 202 and the memory 204 are part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). The transceiver 206 is connected to the processor 202 and transmits and / or receives wireless signals through one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 can also be used interchangeably with an RF unit. In the present invention, the wireless device can also mean a communication modem / circuit / chip.

[0275] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. Although not limited thereto, one or more protocol layers are implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 implement one or more layers (for example, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102 and 202 generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. One or more processors 102 and 202 generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. One or more processors 102 and 202 generate a signal (for example, a baseband signal) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification and provide it to one or more transceivers 106 and 206. One or more processors 102 and 202 receive a signal (for example, a baseband signal) from one or more transceivers 106 and 206 and can obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification.

[0276] One or more processors 102, 202 are also referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors 102, 202 are implemented by hardware, firmware, software, or a combination thereof. As an example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) are included in one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification are implemented using firmware or software, and the firmware or software is implemented to include modules, procedures, functions, and the like. The firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification is included in one or more processors 102, 202, or stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification are implemented using firmware or software in the form of code, instructions, and / or a set of instructions.

[0277] One or more memories 104, 204 are connected to one or more processors 102, 202 and can store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 are composed of ROM, RAM, EPROM, flash memory, hard drive, register, cache memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104, 204 are located inside and / or outside the one or more processors 102, 202. Also, the one or more memories 104, 204 are connected to the one or more processors 102, 202 by various techniques such as wired or wireless connection.

[0278] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc. mentioned in this specification in the form of methods and / or flowcharts, etc. to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts, etc. disclosed in this specification from one or more other devices. For example, one or more transceivers 106, 206 are connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information or wireless signals from one or more other devices. Also, one or more transceivers 106, 206 are connected to one or more antennas 108, 208, and one or more transceivers 106, 206 are configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts, etc. disclosed in this specification by one or more antennas 108, 208. In this specification, one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 convert the received wireless signals / channels, etc. from RF band signals to baseband signals (Convert) in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors 102, 202. One or more transceivers 106, 206 convert the user data, control information, wireless signals / channels, etc. processed using one or more processors 102, 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0279] Examples of utilization of wireless devices to which the present invention is applied

[0280] FIG. 10 shows another example of a wireless device to which the present invention is applied. The wireless device is embodied in various forms depending on the usage example / service (see FIG. 8).

[0281] Referring to FIG. 10, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 in FIG. 9 and are composed of various elements, components (parts), units / sections, and / or modules. For example, the wireless devices 100 and 200 include a communication section 110, a control section 120, a memory section 130, and additional elements 140. The communication section includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102, 202 and / or one or more memories 104, 204 in FIG. 9. For example, the transceiver 114 includes one or more transceivers 106, 206 and / or one or more antennas 108, 208 in FIG. 9. The control section 120 is electrically connected to the communication section 110, the memory section 130, and the additional elements 140 and controls various operations of the wireless device. For example, the control section 120 controls the electrical / mechanical operations of the wireless device based on programs / codes / instructions / information stored in the memory section 130. Also, the control section 120 transmits the information stored in the memory section 130 to the outside (e.g., other communication devices) through a wireless / wired interface by the communication section 110, or stores the information received from the outside (e.g., other communication devices) through a wireless / wired interface by the communication section 110 in the memory section 130.

[0282] The additional element 140 is configured variously depending on the type of wireless device. For example, the additional element 140 includes any one of a power unit / battery, an input / output unit (I / O unit), a drive unit, and a computer unit. Without being limited thereto, the wireless device is embodied in forms such as a robot (Figs. 8, 100a), a vehicle (Figs. 8, 100b-1, 100b-2), an XR device (Figs. 8, 100c), a portable device (Figs. 8, 100d), a home appliance (Figs. 8, 100e), an IoT device (Figs. 8, 100f), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Figs. 8, 400), a base station (Figs. 8, 200), and a network node. The wireless device is movable depending on the usage example / service or is used at a fixed location.

[0283] In Fig. 10, various elements, components, units / parts, and / or modules within the wireless devices 100 and 200 are all connected to each other by a wired interface or at least some of them are wirelessly connected by the communication unit 110. For example, within the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are wired-connected, and the control unit 120 and the first unit (for example, 130, 140) are wirelessly connected by the communication unit 110. Also, each element, component, unit / part, and / or module within the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is composed of a set of one or more processors. For example, the control unit 120 is composed of a set such as a communication control processor, an application processor, an ECU (Electronic control Unit), a graphics processing processor, and a memory control processor. As another example, the memory unit 130 is composed of a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0284] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0285] FIG. 11 is a diagram illustrating a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle is embodied as a mobile robot, a vehicle, a train, an aerial vehicle (AV) with / without a pilot, a ship, or the like.

[0286] Referring to FIG. 11, the vehicle or the autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 is constituted by a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d respectively correspond to blocks 110 / 130 / 140 in FIG. 10.

[0287] The communication unit 110 transmits and receives signals (such as data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 controls elements of the vehicle or the autonomous driving vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a enables the vehicle or the autonomous driving vehicle 100 to travel on the ground. The driving unit 140a includes an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or the autonomous driving vehicle 100 and includes a wired / wireless charging circuit, a battery, etc. The sensor unit 140c can obtain vehicle state, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (Inertial Measurement Unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight sensing sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d implements technologies such as maintaining the lane during driving, automatically adjusting the speed like an adaptive cruise control, automatically driving along a predetermined route, and automatically setting and driving along a route when a destination is set.

[0288] As an example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a drive plan based on the obtained data. The control unit 120 controls the driving unit 140a so that the vehicle or the autonomous driving vehicle 100 moves along the autonomous driving route according to the drive plan (for example, speed / direction adjustment). The communication unit 110 periodically obtains the latest traffic information data from the external server during autonomous driving and also obtains traffic information data of surrounding vehicles from the surrounding vehicles. Further, the sensor unit 140c obtains vehicle state and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and the drive plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, the autonomous driving route, the drive plan, etc. to the external server. The external server can predict traffic information data in advance using AI technology or the like based on the information collected from the vehicle or the autonomous driving vehicle and provide the predicted traffic information data to the vehicle or the autonomous driving vehicle.

[0289] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the features of the present invention. Therefore, the above detailed description should not be construed restrictively in all aspects and should be considered as exemplary. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention.

Industrial Applicability

[0290] As described above, the present invention can be applied to various wireless communication systems.

Claims

1. A method for a terminal (UE) to transmit a signal in a wireless communication system, comprising: receiving downlink control information (DCI) for scheduling physical downlink shared channels (PUSCHs) on different cells; transmitting the PUSCHs on the different cells based on the DCI, wherein the DCI includes one precoding information and number of layers field for a first cell belonging to a first group among the different cells, each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each first cell, and the TPMI for each first cell is determined based on the precoding information and number of layers field, one second precoding information and number of layers field per first cell is set for DCI for scheduling PUSCHs within a cell, the number of bits of the precoding information and number of layers field is determined based on the maximum value among the number of bits of the set second precoding information and number of layers fields, A signal transmission method.

2. The number of bits of the second precoding information and number of layers field is determined based on the number of antenna ports, codebook-based transmission, full power transmission mode, transform precoder, maxRank, and codebook subset. The signal transmission method according to Claim 1.

3. The number of layers for each first cell is determined based on the precoding information and number of layers field. The signal transmission method according to Claim 1.

4. One value of the precoding information and number of layers field corresponds to a TPMI value independently set for each first cell. The signal transmission method according to Claim 1.

5. For a specific cell among the first cells, if there is no TPMI value corresponding to the one value, the PUSCH for the specific cell is considered not to be scheduled. The signal transmission method according to claim 4.

6. When there is no TPMI value corresponding to the one value for a specific cell among the first cells, the PUSCH for the specific cell is transmitted based on a predefined specific TPMI value. The signal transmission method according to claim 4.

7. The DCI includes third precoding information and a layer number field separated from the precoding information and the layer number field for a second cell belonging to a second group different from the first group among the cells different from each other. The signal transmission method according to claim 1.

8. Based on the setting of non-codebook-based transmission for the PUSCH of a specific cell among the first cells, the precoding information and the layer number field are ignored for the PUSCH of the specific cell. The signal transmission method according to claim 1.

9. Based on the setting of a plurality of SRS resource sets for a specific cell among the first cells, the PUSCH of the specific cell is transmitted based on the SRS resource set with the highest index among the plurality of SRS resource sets. The signal transmission method according to claim 1.

10. Based on the setting of a plurality of SRS resource sets for a specific cell among the first cells, the PUSCH of the specific cell is transmitted based on the SRS resource set with the lowest index among the plurality of SRS resource sets. The signal transmission method according to claim 1.

11. A terminal for receiving signals in a wireless communication system, comprising: At least one transceiver; At least one processor; At least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform a specific operation. The specific operation includes: Receiving downlink control information (DCI) for scheduling physical downlink shared channels (PUSCH) on cells different from each other; Transmitting PUSCH on cells different from each other based on the DCI. The DCI includes one precoding information and number of layers field for a first cell belonging to a first group among the cells different from each other. Each PUSCH of the first cell is transmitted based on a TPMI (Transmit Precoding Matrix Indicator) for each first cell, and the TPMI for each first cell is determined based on the precoding information and number of layers field. One second precoding information and number of layers field per first cell is set for DCI for scheduling of PUSCH within one cell. The number of bits of the precoding information and number of layers field is determined based on the maximum value among the number of bits of the set second precoding information and number of layers field. Terminal. **Claim 12** An apparatus for a terminal, including at least one processor, receiving DCI (Downlink Control Information) for scheduling of PUSCH (Physical Downlink Shared Channel) on cells different from each other, transmitting PUSCH on the cells different from each other based on the DCI, and the DCI includes one precoding information and number of layers field for a first cell belonging to a first group among the cells different from each other. Each PUSCH of the first cell is transmitted based on a TPMI (Transmit Precoding Matrix Indicator) for each first cell, and the TPMI for each first cell is determined based on the precoding information and number of layers field. One second precoding information and number of layers field per first cell is set for DCI for scheduling of PUSCH within one cell. The number of bits of the precoding information and number of layers field is determined based on the maximum value among the number of bits of the set second precoding information and number of layers field. Apparatus. **Claim 13** A computer-readable non-volatile storage medium including at least one computer program for causing at least one processor to perform operations, the operations including: Receiving downlink control information (DCI) for scheduling physical downlink shared channels (PUSCHs) on different cells; Transmitting the PUSCHs on the different cells based on the DCI; The DCI includes a precoding information and number of layers field for a first cell belonging to a first group among the different cells; Each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each first cell, and the TPMI for each first cell is determined based on the precoding information and number of layers field; One precoding information and number of layers field per first cell is set for DCI for scheduling PUSCHs within a cell; The number of bits of the precoding information and number of layers field is determined based on the maximum value among the number of bits of the set precoding information and number of layers fields; Storage medium.

14. A method for a base station (BS) to receive signals in a wireless communication system, the method including: Transmitting downlink control information (DCI) for scheduling physical downlink shared channels (PUSCHs) on different cells; Receiving the PUSCHs on the different cells based on the DCI; The DCI includes a precoding information and number of layers field for a first cell belonging to a first group among the different cells; Each PUSCH of the first cell is transmitted based on the TPMI (Transmit Precoding Matrix Indicator) for each first cell, and the TPMI for each first cell is determined based on the precoding information and the number of layers field. One piece of second precoding information per first cell and the number of layers field are set for DCI for scheduling PUSCH within one cell. The number of bits of the precoding information and the number of layers field is determined based on the maximum value among the number of bits of the set second precoding information and the number of layers field. Signal reception method. [

15. ] A base station for transmitting signals in a wireless communication system, At least one transceiver, At least one processor, At least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform a specific operation. The specific operation includes Transmitting DCI (Downlink Control Information) for scheduling PUSCH (Physical Downlink Shared Channel) on cells different from each other, Receiving PUSCH on the cells different from each other based on the DCI. The DCI includes one precoding information and number of layers field for a first cell belonging to a first group among the cells different from each other. Each PUSCH of the first cell is transmitted based on the TPMI (Transmit Precoding Matrix Indicator) for each first cell, and the TPMI for each first cell is determined based on the precoding information and the number of layers field. One piece of second precoding information per first cell and the number of layers field are set for DCI for scheduling PUSCH within one cell. The number of bits of the pre-coding information and the layer number field is determined based on the maximum value among the set number of bits of the second pre-coding information and the layer number field. Base station.

Images