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 apparatus for use in a wireless communication system. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. Generally, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (such as bandwidth and transmission power). Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, and Single Carrier Frequency Division Multiple Access (SC-FDMA) systems. Summary of the Invention [Problem to be solved by the invention]

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

[0004] The technical object of the present invention is not limited to the above-mentioned technical object, and other technical objects can be inferred from the embodiments of the present invention. [Means for solving the problem]

[0005] The present invention provides a method and apparatus for receiving signals in a wireless communication system.

[0006] As one embodiment of the present invention, there is provided a method for a terminal (UE) to receive a signal in a wireless communication system, the method including: receiving downlink control information (DCI) for scheduling physical downlink shared channels (PDSCHs) on different cells; and receiving the PDSCHs on the different cells based on the DCI, wherein the DCI includes one transmission configuration indication (TCI) field for cells belonging to the same group among the different cells, and one codepoint in the TCI field is mapped to as many TCI states as the number of cells belonging to the group.

[0007] As one embodiment of the present invention, there is provided a signal transmission method in which a base station (BS) transmits a signal in a wireless communication system, the signal transmission method including the steps of: transmitting downlink control information (DCI) for scheduling physical downlink shared channels (PDSCHs) on different cells; and transmitting the PDSCHs on the different cells based on the DCI, wherein the DCI includes one transmission configuration indication (TCI) field for cells belonging to the same group among the different cells, and one codepoint in the TCI field is mapped to TCI states as many as the number of cells belonging to the group.

[0008] As another embodiment of the present invention, there is provided a signal transmission method for a terminal (UE) in a wireless communication system, the signal transmission 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 the first cell, the TPMI for the first cell being determined based on the precoding information and number of layers field; one second precoding information and number of layers field per first cell is configured for DCI for scheduling PUSCHs in one cell; and the number of bits of the precoding information and number of layers field is determined based on a maximum value among the number of bits of the configured second precoding information and number of layers field.

[0009] As one embodiment of the present invention, there is provided a signal reception method in which a base station (BS) transmits a signal in a wireless communication system, the signal reception 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 the first cell, the TPMI for the first cell being determined based on the precoding information and number of layers field; one second precoding information and number of layers field per first cell is configured for DCI for scheduling PUSCHs in one cell; and the number of bits of the precoding information and number of layers field is determined based on the maximum number of bits of the configured second precoding information and number of layers field.

[0010] Another embodiment of the present invention provides an apparatus, a processor, and a storage medium for performing the signal reception method. Also, another embodiment of the present invention provides an apparatus, a processor, and a storage medium for performing the signal transmission method.

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

[0012] The above-described aspects of the present invention are merely some of the preferred embodiments of the present invention, and various embodiments reflecting the technical features of the present invention will be apparent to those skilled in the art based on the detailed description of the present invention below. [Effects of the Invention]

[0013] According to one 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 achieved through operations differentiated from conventional inventions.

[0014] The technical effects of the present invention are not limited to the above-mentioned technical effects, and other technical effects may be inferred from the embodiments of the present invention. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram illustrating the structure of a radio frame. [Figure 2] FIG. 1 illustrates a resource grid of slots. [Figure 3] FIG. 10 is a diagram showing an example of mapping physical channels within a slot. [Figure 4] 1 is a diagram illustrating a method for transmitting and receiving signals according to an embodiment of the present invention. [Figure 5] 1 is a diagram illustrating a method for transmitting and receiving signals according to an embodiment of the present invention. [Figure 6] 1 is a diagram illustrating a method for transmitting and receiving signals according to an embodiment of the present invention. [Figure 7] 1 is a diagram illustrating a method for transmitting and receiving signals according to an embodiment of the present invention. [Figure 8] 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 9] 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 10] 1 illustrates an apparatus according to one embodiment of the present invention. [Figure 11] 1 illustrates an apparatus according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0016] The following technologies can be used for various wireless access 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), and 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 a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A / LTE-A pro are evolved versions 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 clarity, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical concept of the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR can also be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is also referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, please refer to the matters described in standard documents published before the present invention. For example, the following documents may be referenced:

[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 (Half-Frame, HF). A half-frame is defined as five 1 ms subframes (Subframe, 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 depending on the cyclic prefix (CP). If a regular CP is used, each slot contains 14 symbols. If an extended CP is used, each slot contains 12 symbols. Here, a symbol can include an OFDM symbol (or a CP-OFDM symbol) or an SC-FDMA symbol (or a DFT-s-OFDM symbol).

[0027] Table 1 illustrates that when a general CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS.

[0028] [Table 1]

[0029] Table 2 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when an extended CP is used.

[0030] [Table 2]

[0031] In an NR system, multiple cells merged to one user equipment (UE) are configured to have different OFDM(A) pneumatics (e.g., SCS, CP length, etc.), which results in different (absolute time) durations of time resources (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) consisting of the same number of symbols.

[0032] NR supports multiple Orthogonal Frequency Division Multiplexing (OFDM) pneumonologies (e.g., subcarrier spacing, SCS) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths.

[0033] The NR frequency band is defined by two types of frequency ranges (FR) (FR1 / FR2). FR1 / FR2 are configured as shown in Table 3 below. FR2 also stands for millimeter wave (mmW).

[0034] [Table 3]

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

[0036] A slot contains multiple symbols in the time domain. For example, in the case of a general CP, one slot contains 14 symbols, while in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlaces (or simply, interlaces) are defined in the frequency domain. Interlace m ∈ {0, 1, ..., M-1} consists of (common) RBs {m, M+m, 2M+m, 3M+m, ...}, where M represents the number of interlaces. A bandwidth part (BWP) is defined as multiple consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier contains up to N BWPs (e.g., 5). Data communication is performed using activated BWPs, and only one BWP can be 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 a downlink (DL), and the terminal transmits information to the base station via an uplink (UL). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels / signals exist depending on the type / purpose of the information exchanged. A physical channel corresponds to a set of resource elements (RE) that carry information derived from a higher layer. A physical signal corresponds to a set of resource elements (RE) used by a physical layer (PHY), but does not carry information derived from a higher layer. Higher layers include a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, etc.

[0038] DL physical channels include PBCH (Physical Broadcast channel), PDSCH (Physical Downlink Shared channel), and PDCCH (Physical Downlink Control channel). DL physical signals include DL RS (Reference Signal), PSS (Primary synchronization signal), and SSS (Secondary synchronization signal). DL RSs include DM-RS (Demodulation RS), PT-RS (Phase-tracking RS), and CSI-RS (Channel-state information RS). UL physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel). UL physical signals include UL RSs. UL RSs include 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 content can be applied in combination with the method proposed in the present invention to be described later, or is supplemented to clarify the technical features of the method proposed in the present invention.

[0042] Furthermore, the method described below can be similarly applied to the aforementioned NR system (licensed band) or shared spectrum, and it goes without saying that it can be modified or substituted to suit the terms, expressions, structures, etc. defined in each system so that the technical ideas proposed in the present invention can be embodied in the relevant system.

[0043] In a CA situation where multiple cells are configured, in order to reduce the DCI overhead required for PDSCH / PUSCH scheduling (based on justification such as in Table 4), a multi-cell scheduling (multi-CC scheduling) scheme can be considered, in which multiple serving cells / CCs are simultaneously scheduled by a single DCI. In the present invention, the expression "scheduling multiple cells" is understood to mean "scheduling PDSCHs or PUSCHs transmitted from each of multiple cells." In other words, multi-cell DCI is DCI for scheduling PDSCHs or PUSCHs on multiple different cells.

[0044] Table 4 is a justification for supporting DCI for the above-mentioned purposes, and can be understood as one of the motivations for the need to introduce such DCI (PDCCH).

[0045] [Table 4]

[0046] In this regard, "multi-carrier enhancement" is being discussed, which aims to specify a method for scheduling PUSCH or PDSCH on multiple serving cells using one DCI.

[0047] In this specification, in order to more efficiently schedule PUSCHs or PDSCHs on multiple serving cells using one DCI, a scheduling method using a DCI field with a modified structure compared to conventional DCI fields is proposed. More specifically, a more efficient scheduling method is proposed by modifying a MIMO (multiple-input and multiple-output) related DCI field.

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

[0049] A single m-CC DCI can schedule different numbers / combinations of PUSCHs (or PDSCHs) for serving cells. For example, only serving cell #1 may be scheduled, or serving cells #1 / 2 may be scheduled, or serving cells #1 / 2 / 3 may be scheduled, depending on the m-CC DCI. Such numbers / combinations may be distinguished by a specific field in the DCI, RNTI, etc.

[0050] The case where only PUSCH (or PDSCH) on one cell is scheduled by m-CC DCI is called the "s-CC scheduling case." The case where PUSCH (or PDSCH) on multiple cells is scheduled is called the "m-CC scheduling case."

[0051] Even for one UE, the number of (MIMO transmission) layers applied to each PDSCH or PUSCH varies depending on the channel conditions of each cell. However, if all DCI fields indicating information for each cell are included in the DCI to maximize such flexibility, the payload size of the m-CC DCI may increase significantly. In particular, a compact DCI field configuration is essential for simultaneous scheduling of three or more cells. Therefore, a configuration method (to reduce the DCI payload size) for the following fields related to MIMO operation among the fields included in the m-CC DCI is proposed.

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

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

[0054] - "Transmission configuration indication" field

[0055] Multiple CCs that are scheduled simultaneously by an m-CC DCI (or multiple CCs scheduled by the m-CC DCI) are defined as co-scheduled CCs. The co-scheduled CCs (CCs belonging to them) are grouped into one or more sub-groups. A separate field is configured for each sub-group. Which CCs belong to each sub-group is set in advance by higher layer signaling. Each field (the value indicated by this field) is commonly applied to CCs that belong to the sub-group. A sub-group is called a shared CC group. When the attributes of CCs that belong to a shared CC group are different, we propose a method for commonly applying DCI fields to the CCs.

[0056] Table 5 shows the 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 PUSCHs on multiple cells, and DCI format 1_X is a DCI format for scheduling PDSCHs on multiple cells. Type-1 is classified into three sub-types.

[0057] [Table 5]

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

[0059] Method 1: shared-cell-common

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

[0061] Method 2: shared-state-extension

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

[0063] Method 3: Separate

[0064] A method in which the same number of fields are configured (within the DCI) as the number of cells scheduled by the multi-cell DCI (with operation set according to the DCI field indication), an individual field corresponds to each scheduled cell, and the value indicated in the field is applied to that cell.

[0065] Method 4: shared-reference-cell (shared-reference-cell)

[0066] A method in which only one field is configured in a multi-cell DCI, and the value indicated in that DCI field is applied only to one specific reference cell (e.g., the cell from which 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 configured to operate according to the DCI field), and a specific pre-defined / configured default value is applied to other cells.

[0067] Basically, fields to which the Shared-Cell-Common method is applied correspond to Type-1A fields. Fields to which the Shared-State-Extended method is applied correspond to Type-1B fields. Fields to which the Shared-Reference-Cell method is applied correspond to Type-1C fields. Fields to which the Separation method is applied correspond to Type-2 fields. Fields to which it is possible to change whether one of Methods 1 to 4 is applied by explicit configuration correspond to Type-3 fields.

[0068] In this specification, the description of multi-cell scheduling for PDSCH also applies to multi-cell scheduling for PUSCH. Furthermore, the description of the operation of multi-cell scheduling for PUSCH also applies to multi-cell scheduling for PDSCH. Furthermore, in this specification, the word "cell" can also be interpreted as a BWP configured / indicated (active) for the cell.

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

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

[0071] Alternatively, the reference cell may refer to (i) the cell with the lowest (or highest) cell index within the set of all cells that can be scheduled by any multi-cell DCI (i.e., the schedulable cell set), (ii) the cell indicated by the CIF field value, (iii) the cell from which the multi-cell DCI is transmitted, or (iv) a cell pre-specified by RRC.

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

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

[0074] Alternatively, in the case of a field to which the shared-reference-cell method, the shared-cell-common method, and / or the 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 (commonly applied) is configured for each sub-group. Thus, individual / independent fields are configured between each sub-group. As a result, the shared-reference-cell method, the shared-cell-common method, and / or the shared-state-extension method and the field / information configuration / indication method based thereon are applied to each sub-group.

[0075] The sub-group is also referred to as a cell subgroup. A cell subgroup is configured / set by a specific one or a specific number of cells belonging to the co-scheduled cell combination or the schedulable cell combination. For example, a cell subgroup is configured / set by 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 field to which the shared-cell-common method is applied has a structure in which a table consisting of one or more states for each cell is pre-configured by RRC or MAC-CE, and the DCI field indicates one of the one or more states in the table. The conventional case refers to a case in which scheduling is performed based on single-cell DCI. The one or more states are configured with different parameters / values ​​or a combination thereof, and correspond to the row index of each table. Therefore, "state" is replaced with "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 field corresponding to this structure operates based on one or more of the following three options. In the following options, cell set refers to a schedulable cell combination, a co-scheduled cell combination, or a cell subgroup.

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

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

[0079] Opt Z) Shared-Cell - A specific state indicated by a DCI field configured commonly for a cell set to which the common method is applied is interpreted as a parameter / value or a combination thereof corresponding to the state in another common table that is pre-configured in the RRC / MAC-CE and is applied commonly to the cells belonging to the cell set.

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

[0081] First, the Type-1A field or the shared-cell-common method (specifically, the Opt X method) will be more specifically proposed as follows.

[0082] First, in conventional s-CC DCI-based scheduling, for a specific DCI field (SRS resource indicator, Precoding information, and number of layers, etc.), N parameters / values ​​or combinations thereof are pre-configured by RRC or MAC-CE for each of N states that can be indicated by the DCI field, and if one of the N states is indicated by the DCI field, the UE performs PDSCH / PUSCH transmission / reception operations by applying the parameter / value or combination thereof set for the indicated state. In this case, the size of the DCI field is determined to be ceil{log2(N)} bits (or K bits). Here, the value of N (or K) is set to a different (or the same) value for each cell.

[0083] Meanwhile, in the case of the specific DCI field in m-CC DCI-based scheduling, as described above, when a parameter / value or a combination thereof is pre-configured for each state (applied to s-CC DCI-based scheduling) for each cell and a specific state is indicated by the DCI field, the UE interprets / applies the parameter / value or a combination thereof set for each cell for the indicated state, respectively, and performs transmission / reception operations for the PDSCH / PUSCH scheduled for each cell.

[0084] On the other hand, in m-CC DCI-based scheduling, the size of the specific DCI field is determined for the entire set of schedulable cells (or each co-scheduled cell set) in one of the following three ways using N_max, which is the maximum value, and N_min, which is the minimum value, among the N values ​​set for each cell belonging to the set:

[0085] Alt-A) Determined as ceil{log2(N_max)} bits based on the maximum value N_max (in this case, the DCI field indicates up to the (first) N_max states / indexes)

[0086] Alt-B) Determine ceil{log2(N_min)} bits based on the minimum value N_min (in this case, the DCI field indicates up to the (first) N_min states / indexes)

[0087] Alt-C) Determined as ceil{log2(N_exp)} bits based on a specific value (=N_exp) set separately (in this case, the DCI field indicates up to the (first) N_exp states / indexes)

[0088] When the Alt-A or Alt-C scheme is applied, if a specific DCI field indicates a specific state (e.g., a state higher than {N_low-1}) for a specific cell (e.g., cell X, where N is set to N_low, where N is a value less than N_max), the parameter / value or combination thereof set for the state may not exist for cell X. In consideration of this case, the following operation is proposed. For convenience, M=ceil{log2(N_max)} and K=ceil{log2(N_low)} (M≧K) are defined. Specifically, for 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. In addition, hereinafter, it is assumed that the values ​​of the DCI fields corresponding to N states / indexes are 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 the K bits indicate a state / index higher than {N_low-1}, then the actions of Alt 3 or Alt 6 apply.

[0091] B. For example, in the case of an SRI (SRS resource indicator) field, if M=3 and K assigned to cell X is K=2, the SRI field is interpreted using only the first or last two bits of the three bits.

[0092] C. For example, in the case of a precoding information and number of layers field, if M=5 and K assigned to cell X is K=4, the precoding information and number of layers field is interpreted using only the first or last 4 bits of the 5 bits.

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

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

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

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

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

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

[0099] B. For example, if 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 of PUSCH / SRS on cell X.

[0100] C. For example, if the precoding information and layer number fields indicate a state higher than {N_low-1}, the terminal assumes 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, feeds back the corresponding HARQ-ACK to NACK).

[0101] 4) Alt 4: For the cell X, {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 as additional parameters / values ​​or combinations thereof linked to specific N_gap states among the N_low states preset in the cell X.

[0103] B. For example, in the case of the SRI field, an SRS resource connected to a specific state among the preset N_low states is mapped to N_gap states.

[0104] C. For example, in the case of the precoding information and layer number fields, the parameters / values ​​or combinations thereof associated with specific N_gap states (excluding states / indexes corresponding to reserved values) among the N_low states are set.

[0105] 5) Alt 5: For the cell X, interpret the state indicated by the DCI field as the state corresponding to the value obtained by modulo-N_low operation and apply it.

[0106] A. As an example, if N_low=5 and N_max=8, the states indicated in the DCI field {0, 1, 2, 3, 4, 5, 6, 7} are interpreted / applied to states {0, 1, 2, 3, 4, 0, 1, 2} for cell X.

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

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

[0109] 6) Alt 6: If the DCI field indicates a state higher than {N_low-1}, apply / maintain the most recently indicated state for cell X as is.

[0110] A. As a result, the terminal applies / maintains the state most recently instructed to the cell X and performs transmission / reception of the 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 cell X (by the SRI field on the same DCI format or a different DCI format) and performs PUSCH / SRS transmission / reception operations on cell X.

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

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

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

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

[0116] On the other hand, in the case of an m-CC DCI, if 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 configured in the entire schedulable cell combinations, a sum L_sum of the L values ​​configured for each of the cells belonging to the co-scheduled cell combination is calculated. The maximum value of 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 in the m-CC DCI).

[0117] For example, in the case of the SRI field, for each of a plurality of (e.g., N_co) co-scheduled cell combinations configured in the entire schedulable cell combinations, the sum L_sum of the L values ​​(for the SRI field) configured for each of the cells belonging to the co-scheduled cell combination is calculated. The maximum value of 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 in the m-CC DCI).

[0118] For example, in the case of the precoding information and number of layers field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations (e.g., cells configured with CB-based UL) configured in the entire schedulable cell combination, a sum L_sum of L values ​​(for the precoding information and number of layers field) configured in each of the cells (e.g., cells configured with CB-based UL) belonging to the co-scheduled cell combination is calculated. The maximum value of 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 number of layers field (configured in 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 the method for determining the size of the DCI field for this purpose and / or the shared-cell-common method based on the Opt X method. The 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, a reference cell, L_max, N_srs, and / or the number of SRS resources, etc. for use in the m-CC DCI are defined / configured / indicated for a specific cell X. When configuring the SRI field in the m-CC DCI and / or when multiple CCs are scheduled by the m-CC DCI, N_cfg states and a field size L_cfg are determined for the cell based on the given reference cell, L_max, N_srs, and / or the number of SRS resources. When configuring the SRI field in the m-CC DCI and / or when multiple CCs are scheduled by the m-CC DCI, for a cell for which a reference cell, L_max, N_srs, and / or the number of SRS resources, etc. are not defined / configured / indicated, the SRI field in the m-CC DCI for the cell is configured based on the N states and field size L set in the s-CC DCI.

[0123] For example, in the case of a precoding information and number of layers field, for a specific cell X, a reference cell for m-CC DCI use, a maximum rank number, valid / invalid row indices among the table rows corresponding to the cell, and / or constraints on the codebookSubset parameter are defined / configured / indicated as proposed below. When configuring the precoding information and number of layers field in the m-CC DCI and / or when scheduling multiple CCs using the m-CC DCI, N_cfg states and a field size L_cfg are determined for the cell based on the given reference cell, maximum rank number, valid / invalid row indices among the table rows corresponding to the cell, and / or constraints on the codebookSubset parameter. When configuring the precoding information and number of layers fields in the m-CC DCI and / or when scheduling multiple CCs using the m-CC DCI, for cells for which the reference cell, maximum rank number, valid / invalid row indexes of the table rows corresponding to the cell, and / or constraints on the codebookSubset parameters are not defined / set / indicated, the precoding information and number of layers fields in the m-CC DCI for the cell are configured based on the N states and field size L set in the s-CC DCI.

[0124] [1] SRS resource indication related fields

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

[0126] [Table 6-1] [Table 6-2]

[0127] <“SRS resource set indicator” field>

[0128] If multiple Transmission and Reception Points (TRPs) for UL transmission of the UE are configured, this field indicates a single TRP used by the scheduled PUSCH among the TRPs, or indicates the transmission procedure of multiple TRPs used by the scheduled PUSCH. When a PUSCH is transmitted by a single TRP, this is called single-TRP operation, and when it is transmitted by multiple TRPs, this 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 that are set for each value of the SRS resource set indicator field.

[0130] [Table 7]

[0131] Considering the payload size of the m-CC DCI, the SRS resource set indicator field may not be present in the m-CC DCI. Alternatively, the SRS resource set indicator field is present in the DCI only in the s-CC scheduling case, and is not present in the DCI in the m-CC scheduling case. Alternatively, even in the s-CC scheduling case, if multi-TRP UL operation is not configured for the scheduled cell, the field is specified not to be present. Therefore, the SRS resource set indicator field is present in the DCI only in the s-CC scheduling case and when scheduling is performed in a cell with multi-TRP UL operation configured.

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

[0133] Options 1-1 and 1-2 below disclose how to apply the "SRS Resource Set Indicator" field when CCs with and without multi-TRP UL operation configured are grouped into a shared CC group.

[0134] (Opt 1-1) When a CC configured with multi-TRP UL operation and a CC not configured with multi-TRP UL operation are configured in a shared CC group, the configuration of the SRS resource set indicator field is omitted, and the operation related to the SRS resource (or SRS resource set) of the CC configured with multi-TRP UL operation is predefined or indicated by the MAC CE. For example, the UE considers this field to correspond to codepoint "00" and is predefined / configured to operate in this mode.

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

[0136] <“SRS resource indicator” field>

[0137] The SRI indication method differs depending on whether the transmission scheme configured in the UE for the scheduled cell is codebook-based transmission or non-codebook-based transmission. Codebook-based transmission means that txConfig in the RRC parameter PUSCH-Config is set to 'codebook'. Codebook-based transmission is also called CB-based UL. Non-codebook-based transmission means that txConfig in the RRC parameter PUSCH-Config 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 are specified among the number of SRS resources (=N_srs) in the SRS resource set. Therefore, the number of bits required for the SRI field is JPEG0007827886000009.jpg15146 (where L_max is the maximum number of PUSCH layers that the terminal can support). In the case of CB-based UL, one of N_srs SRS resources is selected, and the number of layers is finally determined by the selected SRS resource and TPMI. Therefore, the number of bits required for the SRI field is It looks like JPEG0007827886000010.jpg10146.

[0139] For cells with NCB-based UL scheduled by the same m-CC DCI, the number of layers must be the same between the cells, which can save bits. In the case of the "Second SRS resource indicator" field, if the number of layers between two TRP transmissions is the same, JPEG0007827886000011.jpg14146 bits, not JPEG0007827886000012.jpg13146 bits are required. When a specific cell among multiple scheduled cells scheduled by the same m-CC DCI is set as the reference cell, for that smallest cell, JPEG0007827886000013.jpg15146 bits indicate SRI, and for other scheduled cells other than the reference cell, JPEG0007827886000014.jpgSRI is indicated by 14146 bits.

[0140] A rule is needed as to which cell among multiple scheduled cells is set as the reference cell. For example, the reference cell may be 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 configured, the cell with the highest SCS configured, the scheduling cell where the m-CC DCI is transmitted, the cell with the smallest number of SRS resources in the SRS resource set, or the cell with the largest number of resources in the SRS resource set. Alternatively, the reference cell may be defined and / or set to a specific cell (one) in each scheduled cell combination based on the combination of cells scheduled by the m-CC DCI.

[0141] The constraint on the number of layers applies only to the m-CC scheduling case, and there may be no constraint on the number of layers for the s-CC scheduling case. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (with the operation specified by the DCI field configured) are configured in the DCI. In addition, each scheduled cell is assigned to a separate field, and the SRI field is configured in such a way that the value specified in the field is applied to the cell. This field configuration method is called the "Type-2 field design method."

[0142] For a cell configured with an NCB-based UL, a different L_max value is configured / applied depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For 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 constrained to K. The value of K is predefined or configured. For example, K=1. Alternatively, in the scheduling case based on the m-CC DCI, the L_max value is always constrained to K. The value of K is predefined or configured. For example, K=1. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (for which an operation according to the DCI field indication is configured) are configured in the DCI. Furthermore, an individual field corresponds to each scheduled cell, and the SRI field is configured in such a manner that the value indicated in the field is applied to the cell. This field configuration method is called a "Type-2 field design method."

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

[0144] On the other hand, even if the number of SRS resources in the SRS resource set configured for a specific cell (in the case of scheduling using s-CC DCI) is N1, only a number (=N2) of SRS resources less than N1 are allowed in the case of scheduling based on m-CC DCI or the m-CC scheduling case. In this case, a rule is required for selecting the N2 SRS resources. As an example, the N2 SRS resources (or SRIs) with the lowest index, the highest index, or an index corresponding to a multiple of a specific N value in the SRS resource set are selected. Of the SRS resources in the SRS resource set, specific N2 SRIs may be preset separately for the case of scheduling based on m-CC DCI or the m-CC scheduling case.

[0145] For example, in the s-CC scheduling case, the SRI field / information is configured / indicated based on N1 SRIs. In the m-CC scheduling case, the SRI field / information is configured / indicated (individually) for each cell based on N2 SRIs (less than N1). Alternatively, a configuration constraint may be imposed so that only one SRS resource is always configured in the SRS resource set for a cell configured as a target for m-CC DCI scheduling. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (i.e., configured to operate according to the instruction of the DCI field) are configured in the DCI. Furthermore, each field corresponds to each scheduled cell, and the SRI field is configured in a manner in which the value indicated in the field is applied to the cell. This field configuration method is called the "Type-2 field design method."

[0146] When multiple cells scheduled by the same m-CC DCI require a certain number of SRI code points for each cell, the number of required bits can be minimized by configuring an SRI field in the m-CC DCI with the number of bits obtained by converting the product of the number of code points required for each cell, rather than the sum of the number of bits obtained by converting the number of code points required for each cell. 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 with the number of bits obtained by converting the product of the code points required for each cell is configured in the m-CC DCI, the SRI field is configured with ceil{log2(10x10x10)}=10 bits, rather than 4+4+4=12 bits.

[0147] Alternatively, 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. For example, when PUSCH is scheduled on cell #1 / 2 / 3, the SRI field is configured with one bit. Specifically, if the one-bit SRI field indicates '0', the UE recognizes that SRI=0 for cell #1, SRI=1 for cell #2, and SRI=0, 1 for cell #3. If the one-bit SRI field indicates '1', the UE 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 pre-configured and / or indicated by the MAC CE. The final number of SRI bits is determined depending on how many code points have values ​​configured and / or indicated by the MAC CE. For example, if values ​​for K code points are configured, ceil{log2(K)} bits are allocated to one SRI field.

[0148] Furthermore, a method is applied in which a single codepoint indicates a combination of multiple SRI information for multiple cells, each of which is scheduled by the same m-CC DCI and has a CB-based UL configured and an NCB-based UL configured. For example, when two SRI fields are configured in the m-CC DCI, the first SRI field indicates a combination of multiple SRI information for multiple cells with a CB-based UL configured, and the second SRI field indicates a combination of multiple SRI information for multiple cells with an NCB-based UL configured.

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

[0150] In options 2-1 to 2-3, a constraint can be considered that only CCs of the same type belong to a shared CC group, where all CCs in a shared CC group are set only to NCB-based ULs, or all CCs are set only to CB-based ULs.

[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 of the number of code points configured for single-cell scheduling for each CC. In this case, for a CC configured with more code points than the minimum value (e.g., N), only the code points corresponding to the lowest or highest N indexes are indicated.

[0152] (Opt 2-2) The SRI field is configured based on the maximum number of code points configured for single cell scheduling for each CC. If the code point indicated by this field is invalid for a specific CC, it is considered that there is no scheduling for that CC.

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

[0154] Alternatively, different types of CCs may belong to a shared CC group. That is, an NCB-based UL may be configured for some CCs in the shared CC group, and a CB-based UL may be configured for other CCs. Option A and Option B disclose how to apply 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 in the shared CC group is limited to one, and the code point is configured in advance or indicated by the MAC CE. The SRI field configuration in the DCI may be omitted.

[0156] (OptB) The SRI field and / or corresponding table are configured for a specific type (e.g., CB-based UL). For other types (e.g., NCB-based UL), a default codepoint is applied. The default codepoint is preset or indicated by the MAC CE. Opt 2-1 / 2-2 / 2-3 are applied as a method for configuring the SRI field for a specific type in OptB.

[0157] If one of the co-scheduled CCs is configured with an NCB-based UL and the other is configured with a CB-based UL, the Type-2 method is applied to the SRI field (unless there is another configuration for Type-1A or Type-2). In other words, if the configurations for NCB-based UL or CB-based UL differ between CCs in a co-scheduled CC, the UE does not expect a Type-1A configuration for the SRI field. If all CCs are commonly configured with an NCB-based UL or CB-based UL, the Type-1A method is applied to the SRI field (unless there is another configuration for Type-1A or Type-2).

[0158] If multiple SRS resource sets are configured for a specific cell (due to m-TRP operation), it is necessary to determine which SRS resource set's SRI is indicated by the SRI field when scheduling PUSCH / SRS on that specific cell by m-CC DCI. One method is to apply (or use / configure) the SRS resource set corresponding to the highest or lowest SRS resource set index configured for that specific cell when scheduling PUSCH / SRS on that specific cell by m-CC DCI. Another method is to apply (or use / configure) the SRS resource set corresponding to a specific SRS resource set index configured / instructed by another base station when scheduling PUSCH / SRS on that specific cell by m-CC DCI.

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

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

[0161] This field may not be present in the m-CC DCI. Alternatively, it may be present only in the s-CC scheduling case and not present 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 specified not to be present. For example, in the s-CC scheduling case, when scheduling is performed only for a cell configured for multi-TRP UL operation, the second SRS resource indicator field is present.

[0162] Alternatively, if it is indicated (by the above-described method or the like) that a second SRS resource set is valid on a cell scheduled in the m-CC scheduling case or the s-CC scheduling case, but the field does not exist, the SRI corresponding to which codepoint is to be applied to the cell is predefined / configured or updated by a MAC CE or the like. As one method, the terminal considers that an SRI similar to that indicated by the "SRS resource indicator" field (for the cell) is indicated. Alternatively, which SRI on the second SRS resource set to be used is preconfigured / defined. 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 preconfigured. Alternatively, a configuration constraint may be imposed so that only one SRS resource is always configured in the second SRS resource set for a cell in which an m-CC DCI is configured.

[0163] For reference, according to the 3GPP agreement, if a UE is configured with a CB-based SRS resource set or an NCB-based SRS resource set, a 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 ones with lower and higher srs-ResourceSetIds of the two SRS resource sets configured by the RRC parameter ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 (NOTE 1 in Table 7: The first and second SRS resource sets are respectively the ones with lower and higher srs-ResourceSetIds of the two SRS resource sets configured by higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2). srs-ResourceSetId is an ID of the SRS resource set and is indicated by an integer ranging from 0 to maxNrofSRS-ResourceSets-1. maxNrofSRS-ResourceSets is, for example, 16.The first SRS resource set corresponds to a lower one (a resource set with a lower index than the second SRS resource set), and the second SRS resource set corresponds to a higher one (a resource set with a higher index than the index of the first SRS resource set). In conclusion, if a CB-based SRS resource set or an NCB-based SRS resource set is configured in a UE, a PUSCH scheduled by multi-cell DCI is always associated with an SRS resource set with a lower index.

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

[0165] Options 3-1 and 3-2 propose how to apply the "Second SRS Resource Indicator" field when CCs with and without multi-TRP UL operation configured are grouped into a shared CC group.

[0166] (Opt 3-1) When a CC with multi-TRP UL configured and a CC without multi-TRP UL configured 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 predefined, indicated by the MAC CE, or the value indicated by the SRI field is also applied to the second SRI.

[0167] (Opt 3-2) The "Second SRS Resource Indicator" field is present or configured, but is ignored for CCs that do not have multi-TRP UL operation configured. For CCs that do have multi-TRP UL operation configured, the index indicated by this field is commonly applied.

[0168] [2] Fields related to TPMI and layer number settings

[0169] Table 8 shows the DCI fields related to the TPMI and layer number as 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 only required in the case of CB-based UL, especially 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 ultimately determined by this field.

[0173] For cells scheduled by the same m-CC DCI and configured with CB-based UL, if the number of layers is the same between the cells, the number of bits can be saved. This is similar to the principle that, in the case of the "Second Precoding Information" field, if the number of layers between two TRP transmissions is the same, up to 1 to 2 bits can be saved. In this case, a specific cell among multiple scheduled cells scheduled by the same m-CC DCI is set as a reference cell, and the TPMI and the number of layers for the reference cell are indicated by as many bits as necessary in the "Precoding Information and Number of Layers" field. For other scheduled cells other than the reference cell, the TPMI and the number of layers are indicated by as many bits as necessary in the "Second Precoding Information" field.

[0174] A rule is required for determining which cell among multiple scheduled cells is set as the reference cell. The 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 smallest maxRank value, or the cell with the largest maxRank value. Alternatively, the reference cell is defined and / or set to a specific cell (one) in each scheduled cell combination based on the combination of cells scheduled by the m-CC DCI.

[0175] The constraint on the number of layers applies only to m-CC scheduled cells, and the above-mentioned constraint on the number of layers may not be necessary for s-CC scheduling cases. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (i.e., configured with the operation indicated by the DCI field) are configured in the DCI. In addition, each scheduled cell corresponds to an individual field, and the precoding information and number of layers fields are configured in a manner in which the value indicated in the field is applied to the cell. This field configuration method is called the "Type-2 field design method."

[0176] For a cell configured with CB-based UL, a different maximum rank / layer number is set / applied depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the s-CC scheduling case, the maxRank value follows a value predefined / configured for each cell, but in the m-CC scheduling case, the maxRank value is constrained to K. Alternatively, in the scheduling case based on the m-CC DCI, the maxRank value is always constrained to K. Alternatively, a configuration constraint is imposed so that the maxRank value is always set to K for cells configured as targets for m-CC DCI scheduling. The value of K is predefined or defined. For example, K=1. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (for which an operation according to the DCI field indication is configured) are configured in the DCI. Furthermore, each scheduled cell is assigned a separate field, and the precoding information and layer number fields are configured in a manner in which the value indicated in the field is applied to the cell. This field configuration method is called a "Type-2 field design method."

[0177] In practice, it is not easy to match the precoder or the number of layers for each cell. Furthermore, restricting the number of layers has the disadvantage of reducing the data rate. In consideration of this, a separate table and corresponding individual fields for each cell are configured, and the TPMI and the number of layers are indicated for each cell by the individual fields. A method of reducing the overall number of bits required to indicate the TPMI and the number of layers can be considered by adjusting the number of rows in the table for each cell.

[0178] For example, as shown in Table 9 below, for a four-antenna port SRS (Precoding information and number of layers for 4 antenna ports), when certain conditions (if transform precoder is disabled, maxRank=2, and ul-FullPowerTransmission=fullpowerMode1, codebookSubset=partialAndNonCoherent) are met, signaling for 30 combinations of TPMI and 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 reduces the number of bits required to configure / indicate the "Precoding Information and Number of Layers" field / indication for the cell. For example, if only eight rows out of 30 are selected, only three bits are required instead of five bits to indicate the TPMI and number of layers for the cell.

[0179] In this case, for each cell (for which CB-based UL is set), which row indexes are selected from the conventional codebook to reduce the codebook size can be set separately or predefined. For example, only even indexes, only indexes corresponding to multiples of a specific N value, only a specific number of lowest indexes, or only a specific number of highest indexes can be selected from the row indexes.

[0180] The application of this method varies depending on which cell is actually scheduled (the codebook size varies), and may not be applicable to the s-CC scheduling case. As an example, in the s-CC scheduling case, fields / information related to the TPMI and the number of layers are configured / indicated based on Table 9 below. 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 portion (e.g., eight) of rows in Table 9 below. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (for which an operation according to the DCI field indication is set) are configured in the DCI. In addition, each field corresponds to each scheduled cell, and the precoding information and number of layers fields are configured in a manner in which the value indicated in the field is applied to the cell. This field configuration method is called a "Type-2 field design method."

[0181] In a similar manner, the number of bits allocated to the field can be reduced by restricting the codebookSubset parameter. As an example, in the case of m-CC DCI scheduling, the full-partial-and-non-coherent mode is not allowed, thereby saving one bit of information. Alternatively, this restriction on the codebookSubset parameter may not be applied to the case of s-CC scheduling, but may be applied only to the case of m-CC scheduling. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (i.e., configured with the operation indicated by the DCI field) are configured in the DCI. Furthermore, each field corresponds to each scheduled cell, and the precoding information and layer number fields are configured in a manner in which the value indicated in the field is applied to the cell. This field configuration method is called the "Type-2 field design method."

[0182] Table 9 shows Table 7.3.1.1.2-2A of 3GPP TS 38.212, which is 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 how to apply the "Precoding Information and Number of Layers" field when a CC configured for NCB-based UL operation and a CC configured for CB-based UL operation are grouped into a shared CC group, or when a shared CC group is grouped only with CCs configured for CB-based UL operation but the table configuration referenced for each CC is different.

[0185] First, since this field itself is only required for CCs configured with CB-based UL operation, if a CC configured with NCB-based UL operation is included in a shared CC group (and also if the CC is configured with CB-based UL operation and has one port in the SRS resource), the instructions in this field will be ignored for that CC.

[0186] (Opt 4-1) The number of code points required for each CC configured with CB-based UL operation in the same shared CC group is set in the same way. For example, the TPMI field is configured based on the minimum number of code points configured for single-cell scheduling for each CC. In this case, for CCs configured with more code points 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 number of code points configured for scheduling of a single cell for each CC. If the code point indicated by this field is not valid for a particular CC, it is considered that there is no scheduling for that CC.

[0188] (Opt 4-3) The TPMI field may be configured in the same manner as Opt 4-3 described above, or if the indicated code point is invalid for a specific CC, the terminal may operate to assume / apply a specific code point that is predefined / configured for the CC.

[0189] <“Second Precoding information” field>

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

[0191] This field may not be present in the m-CC DCI. Alternatively, it may be present 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 specified not to be present. For example, in the s-CC scheduling case, when scheduling is performed only for a cell configured for multi-TRP UL operation, the second precoding information field is present.

[0192] Alternatively, if it is indicated (by the above method or the like) that a second SRS resource set is valid on a cell scheduled in the m-CC scheduling case or the s-CC scheduling case, but the field does not exist, the TPMI / number of layers corresponding to which codepoint is to be applied to the cell is predefined / configured or updated by a MAC CE or the like. As one method, the terminal considers that the same TPMI / number of layers as that indicated (for the cell) by the "precoding information and number of layers" field is indicated. Alternatively, the TPMI / number of layers to be applied to the second SRS resource set is predefined / configured.

[0193] Options 5-1 and 5-2 propose how to apply the "Secondary Precoding Information" field when CCs with and without multi-TRP UL operation configured are grouped into a shared CC group.

[0194] (Opt 5-1) If a CC with multi-TRP UL configured and a CC without multi-TRP UL configured are grouped into a shared CC group, the configuration of the "Second Precoding Information" field is omitted, and the (precoding-related) operation of the CC with multi-TRP UL operation configured is pre-defined, indicated by the MAC CE, or the value indicated by the "Precoding Information and Number of Layers" field is applied to the second TRP as well.

[0195] (Opt 5-2) This “Second Precoding Information” field is present or configured, but for CCs where multi-TRP UL operation is not configured, this 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 cell-specific settings, the TCI status indication is set to operate in one of two modes:

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

[0201] TCI mode #2: A list of cells (e.g., CC#1 / 2) that share the TCI (or, in the case of UL, the spatially related RS and / or the RS for path-loss configuration) is configured by higher layer signaling. If the TCI state is changed in one of the cells (e.g., CC#1), the states of the other cells (e.g., CC#2) belonging to the list of cells are also changed in common. The higher layer signaling is, for example, RRC signaling.

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

[0203] In this case, 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 the 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 some of the TCI states preset / indicated for the case scheduled by the s-CC DCI, or are defined by some code points with a specific rule. For example, the TCI state corresponding to the code point with the lowest or highest index among the TCI states preset / indicated for the case scheduled by the 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 states corresponding to some code points with indexes corresponding to multiples of a specific N value are inherited (or used).

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

[0205] If all cells schedulable by m-CC DCI are configured to operate in TCI mode #2 and are included in the cell list, a separate TCI field is not configured for each cell, but only a common (single) TCI field is configured. Alternatively, if all cells schedulable by m-CC DCI (e.g., CC #1 / 2 / 3 / 4) are configured to operate in TCI mode #2 but are not included in the common cell list (case 1: CC #1 / 2 belong to cell list #1, but CC #3 / 4 belong to cell list #2), or if 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), a separate TCI field is configured for each cell and / or 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. When only a common TCI field is configured between cells included in a common cell list and an independent TCI field is configured for each cell (or for each cell list), the number of bits allocated for each cell (or for each cell list) is set to less than 3 bits (using the method described above).

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

[0207] If all cells that can be (simultaneously) scheduled by m-CC DCI are configured to operate in TCI mode #2 and are included in a cell list, only one TCI state that is commonly applied to multiple cells is linked, instead of one code point linking the TCI state for each CC. Alternatively, if all cells that can be scheduled by 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 A: CC #1 / 2 belong to cell list #1, but CC #3 / 4 belong to cell list #2), or if the TCI mode configured for each cell is different (Case B: CC #1 / 2 belong to cell list #1, but CC #3 and CC #4 are set to TCI mode #1), a code point linked to a different TCI state is configured for each cell and / or each cell list. In case A, the TCI status for CC#1 / 2 and the TCI status for CC#3 / 4 are all linked to one code point, and this code point constitutes the TCI field. In case B, the TCI status for CC#1 / 2, the TCI status for CC#3, and the TCI status for CC#4 are all linked to one code point, and this code point constitutes the TCI field. For cells included in the common cell list, only one TCI status that is commonly applied to the cells is linked to one code point.

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

[0209] Between 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] - Between different cell lists configured with TCI mode #2, the separated reduction table method (based on configuring one (common) TCI table for each cell list) or the code point extension method (based on configuring one (common) TCI state for each cell list) is applied.

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

[0212] On the other hand, the above-mentioned proposed method is applied only to the m-CC scheduling case, and for the s-CC scheduling case, exceptionally, TCI information is indicated based on the TCI field configured for the s-CC DCI (and the TCI status linked to each code point).

[0213] Options 6-1 to 6-3 propose how the TCI field should be applied when CCs with and without the TCI field set are grouped into a shared CC group.

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

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

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

[0217] Here, the specific default TCI is a specific index (pre-configured / defined or indicated by the MAC CE) among the TCI state IDs set (for single-cell scheduling of the CC), or the specific default TCI is 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 TCI fields set are grouped into a shared CC group, but different TCI modes are set between each CC (when a CC with TCI mode #1 set and a CC with TCI mode #2 set are grouped into a shared CC group).

[0219] Unlike options 7-1 and 7-2, a setting constraint is imposed so that only CCs configured with the same TCI mode belong to the same shared CC group. In particular, when a shared CC group is grouped with only CCs configured with TCI mode #2, a setting constraint is imposed so that only CCs that belong to the same cell list belong to the group.

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

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

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

[0223] - Alt-1: The mapping relationship between each codepoint in the TCI field in the m-CC DCI and the TCI status index for multiple cells is constrained to be updated only by RRC signaling (or RRC reconfiguration) and not by the MAC CE (for s-CC DCI). For example, a conventional (e.g., Rel-15 / 16 / 17) MAC CE updates only the TCI status linked to the s-CC DCI, but not the TCI status linked to the m-CC DCI.

[0224] - Alt-2: The mapping relationship between each codepoint in the TCI field in the m-CC DCI and the TCI status index for multiple cells is updated by the MAC CE (for s-CC DCI), and rules and / or constraints on the update method are defined. One method is that only the same number of TCI status indexes (or fewer) as the number of TCI status indexes set in the TCI field of the m-CC DCI for a specific CC are updated by the MAC CE. For example, in the table for the TCI field in the m-CC DCI shown in Table 11 below, a (maximum) three (one) constraint is given for TCI updates by the MAC CE for CC1 (or CC3). If the MAC CE for CC1 signals that the list of TCI indexes is updated from {1, 2, 3} to {2, 3, 4}, 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"} in Table 11. If the MAC CE for CC3 signals that the list of TCI indexes is updated from {4} to {1}, the terminal recognizes that the code point mapping for CC3 is updated to {1 for "00" / "01" / "10" / "11"} in Table 11.

[0225] As another example, in a table for the TCI field in an m-CC DCI such as Table 11, a TCI update by a MAC CE for CC1 is restricted to three or less. If the MAC CE for CC1 signals that the list of TCI indices is updated to a smaller number, from {1, 2, 3} to {3, 4}, the UE recognizes that the code point mapping for CC1 in Table 11 below 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 indices {T_old.0, ... T_old.N-1} and the latest TCI state is composed of K TCI state indices {T_new.0, ... T_new.K-1}, where N>K, the UE recognizes that the previous N TCI states (corresponding code points) are replaced / updated / mapped to the N latest TCI state indices. For example, the TCI state index is updated to {T_new.0, ... T_new.K-1, T_new.0, ...} based on modulo-K arithmetic, or the TCI state index is updated to {T_new.0, ... T_new.K-1, T_new.K-1, T_new.K-1, ...} where the last T_new.K-1 is then repeated.

[0226] [Table 11]

[0227] - Alt-3: Regarding the mapping relationship between each codepoint in the TCI field in the m-CC DCI and the TCI state index, a separate MAC CE (for m-CC DCI) is defined to update the relationship, or the conventional MAC CE (for s-CC DCI) is extended. The separate MAC CE or conventional MAC CE indicates the TCI state index for each codepoint in the TCI field (in m-CC DCI) for a specific CC. As an example, for CC1 in Table 11, the separate MAC CE or conventional MAC CE signals that the TCI state index for each codepoint in the TCI field (in m-CC DCI) for CC1 is updated from {1, 2, 2, 3} to {2, 2, 4, 5}. Alternatively, the separate MAC CE indicates the TCI state index for each CC corresponding to a specific codepoint in the TCI field (in m-CC DCI). As an example, for code-point #01 in Table 11, another MAC CE signals that the TCI state index for each CC is updated from {1, 2, 4, 5} to {2, 3, 3, 4}.

[0228] On the other hand, the contents of the present invention are not limited to uplink and / or downlink signal transmission and reception. For example, the contents of the present invention can also be applied to direct communication between terminals. Furthermore, 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 or by a relay node.

[0229] The above-mentioned example of the proposed method is also included as one of the methods of implementing the present invention, and therefore can be regarded as a kind of proposed method. In addition, the above-mentioned proposed methods may be implemented independently, or may be implemented in the form of a combination (or merging) of some of the proposed methods. Information regarding whether or not the above-mentioned proposed method is applied (or information regarding the rules of the proposed method) can be specified so that the base station notifies the terminal or the transmitting terminal notifies the receiving terminal by a predetermined signal (e.g., a physical layer signal or a higher layer signal).

[0230] Example

[0231] 4 and 5 show flowcharts of a signal transmission and reception method according to an embodiment of the present invention.

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

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

[0234] In addition to the operations of Figures 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 Section [3], DCI for scheduling PDSCHs in 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, one common TCI table is configured for cells belonging to the same cell list among different cells configured with TCI mode #2, so the DCI includes one TCI field for one cell list. A cell list is made up 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, a code point in one TCI field is configured with a combination of multiple TCI states for multiple cells. For example, when CC#1 and CC#2 are scheduled by m-CC DCI, one TCI field is configured for CC#1 and CC#2. One code point value in one TCI field indicates a combination of multiple TCI states corresponding to both of the two CCs. Even 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 in one TCI field included in the single DCI indicates a combination of all of the corresponding multiple TCI states of the three or more CCs. The mapping relationship between code points and TCI states is configured by MAC CE (TCI States Activation / Deactivation for UE-specific PDSCH MAC CE). In general, one code point in one TCI field included in DCI for scheduling PDSCHs on different cells is mapped to as many TCI states as the number of cells belonging to one group.

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

[0238] Furthermore, according to the code point extension method, when the TCI modes set for cells that can be scheduled by the m-CC DCI are different for each cell, a different TCI field is configured for each TCI mode. Thus, when some of the different cells scheduled by the 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, the DCI includes one first TCI field for cells belonging to a first group and one second TCI field for each specific cell. One code point in the first TCI field is mapped to as many TCI states as the number of cells belonging to the first group, and one second code point in the second TCI field is mapped to one TCI state.

[0239] Therefore, if the cells scheduled by the m-CC DCI consist of cells belonging to different cell lists set to TCI mode #2 and multiple cells set to TCI mode #1, the m-CC DCI includes TCI fields equal to 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 higher layer signaling, a specific cell is set not to belong to any cell list (cell group) based on higher layer signaling, and a cell that belongs to a specific cell list is also set based on higher layer signaling.

[0241] Meanwhile, the code point extension method may be applied only to the m-CC scheduling case and not to the s-CC scheduling case. Accordingly, when only one PDSCH is scheduled by DCIs for scheduling PDSCHs in different cells, the code point extension method is not used, and the m-CC DCI includes one TCI field configured for the s-CC DCI. If the TCI field when multiple cells are scheduled by the m-CC DCI is referred to as a 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 in the first TCI field is mapped to TCI states for the same number of m-CC DCIs as the number of cells belonging to the first group, and one second code point in the second TCI field is mapped to a TCI state for one s-CC DCI.

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

[0243] 6 and 7 show flowcharts of a signal transmission / reception method according to another embodiment of the present invention.

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

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

[0246] In addition to the operations of Figures 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, DCI for scheduling PUSCHs on different cells may include 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 a combination of any one or more of the methods disclosed in Sections [1] and [2].

[0249] Specifically, referring to Section [2], the table configuration referenced by each CC belonging to the same shared CC group is different. In this case, when Opt 4-2 is applied, one TPMI field for a shared CC group is configured based on the maximum number of code points configured for DCI for single-cell scheduling (PUSCH scheduling in one cell). The TPMI field refers to a "precoding information and number of layers" field for indicating the TPMI. The TPMI is used to determine a transmission precoder when a UE transmits a PUSCH. The number of code points is related to the number of bits in the precoding information and number of layers field. When the number of code points is N, the number of bits in the precoding information and number of layers field is determined as ceil{log2(N)}. Therefore, the "number of bits in the precoding information and number of layers field for single-cell scheduling (second precoding information and number of layers field)" for each first cell is determined based on the number of code points configured for single-cell scheduling for each cell.

[0250] In summary, one precoding information and number of layers field is included for each first cell belonging to the same shared CC group (first group) among different cells that can be scheduled by the m-CC DCI. Each PUSCH of the first cell is transmitted based on a transmit precoder determined by the TPMI for each first cell. The TPMI for each first cell is given by one precoding information and number of layers field for the first group. Furthermore, the number of bits of one precoding information and number of layers field is determined based on the maximum value of the number of bits of the precoding information and number of layers field set for single-cell scheduling for each first cell. Furthermore, the one precoding information and number of layers field for the first group also indicates 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 configured 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 second precoding information and number of layers 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 configured for single-cell scheduling in each first cell.

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

[0253] In other words, the precoding information and number of layers field is determined to be the maximum value of M bits associated with N different cells when the field is set to Type 1A. For the 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 an independently configured table is used for each first cell, even if the same row index is indicated in each table by one value in the precoding information and number of layers field, the TPMI value corresponding to the row index in each table corresponds to an independent value for each cell.

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

[0256] Since one precoding information and number of layers field is set per shared CC group, for a second cell that belongs to a second group other than the first group among different cells that can be scheduled by DCI, a precoding information and number of layers field (third precoding information and number of layers field) separate from the precoding information and number of layers field for the first group is included in the DCI.

[0257] In addition, the shared CC group includes both a CC configured for CB-based UL operation and a CC configured for NCB-based UL operation, but the UE ignores the precoding information and number of layers fields for the CC configured for NCB-based UL operation. Therefore, when non-codebook-based transmission is configured for the PUSCH of a specific cell among the first cells, the UE transmits the PUSCH on the specific cell without using the values ​​of the precoding information and number of layers fields.

[0258] Furthermore, referring to Section [1], the UE transmits PUSCHs in different cells based on SRS resource sets configured for each cell. If multiple SRS resource sets are configured for a specific cell, the UE transmits PUSCHs in the specific cell based on the resource set with the highest or lowest index among the SRS resource sets configured for the specific cell.

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

[0260] In other words, when the SRI field is configured as Type 1A, the maximum value of the M bits associated with N different cells is determined. Referring to Table 6, when the cell is configured as an NCB-based UL (txConfig=nonCodebook), the M bits for each of the N cells 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 transmission in all UL BWPs of the serving cell. Also, when the cell is configured as a CB-based UL (txConfig=Codebook), the M bits for each of the N cells are determined based on the number of configured SRS resources N_SRS. Furthermore, when multiple SRS resource sets are configured in one cell, the first SRS resource set with a lower index is used, so 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 the PUSCH on different cells is referred to as DCI format 0_X, where X is a natural number equal to or greater than 3. For example, the DCI format of the DCI for scheduling the PUSCH on different cells is DCI format 0_3.

[0262] Furthermore, in addition to the operations described in Figures 4 to 7, any one or more of the operations described in Figures 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 performed in combination.

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

[0264] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or flow charts of the present invention disclosed in this specification may be applied to various fields requiring wireless communication / connectivity between devices (e.g., 5G).

[0265] Hereinafter, a more detailed description will be given with reference to the drawings. In the following drawings / description, the same reference numerals indicate the same or corresponding hardware blocks, software blocks or function blocks unless otherwise specified.

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

[0267] Referring to FIG. 8, a communication system 1 applicable to the present invention includes wireless devices, base stations, and a network. Here, the wireless devices refer to devices that communicate using wireless connection technologies (e.g., 5G NR, LTE), and are also referred to as communication / wireless / 5G devices. The wireless devices include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication capabilities, autonomous vehicles, vehicles capable of vehicle-to-vehicle communication, etc. Here, the vehicles include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices include Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, base stations and networks may also be embodied as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0268] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. The wireless devices 100a to 100f are equipped with AI (Artificial Intelligence) technology, and are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the 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). IoT devices (e.g., sensors) can also communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0269] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f and the base stations 200, and between the base stations 200. Here, the wireless communication / connections are performed using various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication), and communication between base stations 150c (e.g., relay, Integrated Access Backhaul (IAB)) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and the base stations, and the base stations, can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, according to various proposals of the present invention, any one of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / 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 to which the present invention can be applied.

[0272] 9, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR). Here, {first wireless device 100, second wireless device 200} corresponds to {wireless devices 100a to 100f, base station 200} and / or {wireless devices 100a to 100f, 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 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 102 processes information in the memory 104 to generate first information / signals and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106 and then stores information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is coupled 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 some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In the present invention, a wireless device may also refer to 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 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0275] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed herein and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and derive the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein.

[0276] The one or more processors 102, 202 may also be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. For example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be included in the one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed in this specification may be embodied using firmware or software in the form of code, instructions and / or sets of instructions.

[0277] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0278] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or flowcharts herein to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or flowcharts herein from one or more other devices. For example, one or more transceivers 106, 206 can be coupled 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. Furthermore, one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and are configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein via the one or more antennas 108, 208. In this specification, one or more antennas may refer to multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0279] Examples of use of wireless devices to which this invention is applied

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

[0281] 10, wireless devices 100, 200 correspond to the wireless devices 100, 200 of FIG. 9 and are composed of various elements, components, units / parts, and / or modules. For example, the wireless devices 100, 200 include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit 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 unit 120 is electrically coupled to the communication unit 110, the memory unit 130, and the additional element 140, and controls the overall operation of the wireless device. For example, the control unit 120 controls the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0282] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Wireless devices may be embodied in the form of, but are not limited to, a robot (FIG. 8, 100a), a vehicle (FIG. 8, 100b-1, 100b-2), an XR device (FIG. 8, 100c), a mobile device (FIG. 8, 100d), a home appliance (FIG. 8, 100e), an IoT device (FIG. 8, 100f), a digital broadcasting 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 (FIG. 8, 400), a base station (FIG. 8, 200), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0283] In FIG. 10, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all connected to each other by wired interfaces or at least some are connected wirelessly by a communication section 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Furthermore, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is configured with a set of one or more processors. For example, the control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 is configured with 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] 11 is a diagram illustrating an example of a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be embodied as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, etc.

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

[0287] The communication unit 110 transmits and receives signals (e.g., 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 autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or autonomous vehicle 100 to move on the ground. The driving unit 140a includes an engine, a motor, a powertrain, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, 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 detection sensor, a heading sensor, a position module, a vehicle forward / reverse 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 technology for maintaining a lane while driving, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a predetermined route, technology for automatically setting a route and driving when a destination is set, etc.

[0288] For 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 driving plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. The communication unit 110 aperiodically obtains the latest traffic information data from an external server during autonomous driving and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server can predict traffic information data using AI technology based on information collected from the vehicle or autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous 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 characteristics of the present invention. Therefore, the above detailed description should not be construed as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by 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 mentioned above, the present invention can be applied to a variety of wireless communication systems.

Claims

1. A method of receiving configuration information related to a cell set by radio resource control (RRC) signaling; receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells within a scheduled cell set of the cell set; transmitting the PUSCH based on the DCI; The DCI includes a first field of precoding information and a number of layers for the plurality of cells; The PUSCH is transmitted based on a transmit precoding matrix indicator (TPMI), the TPMI being determined based on the first field; A method, wherein the number of bits in the first field is determined based on a maximum number from numbers of bits defined for possible co-scheduled cells in the scheduled cell set.

2. The method described in claim 1, wherein each of the number of bits is determined based on the number of antenna ports, codebook-based transmission, full power transmission mode, transform precoder, maxRank, and codebookSubset.

3. The method of claim 1 , wherein the number of layers for each of the plurality of cells is determined based on the first field.

4. The method described in claim 1, wherein one value of the first field corresponds to a TPMI value set independently for each of the plurality of cells.

5. The method of claim 4 , wherein, based on the absence of a TPMI value corresponding to the one value for a particular cell from the plurality of cells, a PUSCH for the particular cell is deemed not to be scheduled.

6. 5. The method of claim 4, wherein, based on the absence of a TPMI value corresponding to the one value for a specific cell from the plurality of cells, the PUSCH for the specific cell is transmitted based on a predefined specific TPMI value.

7. 2. The method of claim 1, wherein the DCI includes a second field of layer number and second precoding information for a second plurality of cells in another scheduled cell set of the cell set, separated from the first field.

8. The method of claim 1, wherein the first field is ignored for a PUSCH of a specific cell from among the plurality of cells based on non-codebook-based transmission being configured for the PUSCH of the specific cell.

9. 2. The method of claim 1, wherein a plurality of SRS resource sets are configured for a specific cell from the plurality of cells, and the PUSCH of the specific cell is transmitted based on an SRS resource set having a highest index from the plurality of SRS resource sets.

10. 2. The method of claim 1, wherein, based on multiple SRS resource sets being configured for a specific cell from the multiple cells, the PUSCH of the specific cell is transmitted based on an SRS resource set having a lowest index from the multiple SRS resource sets.

11. The DCI includes a third field of a sounding reference signal (SRS) resource indicator for the plurality of cells; The PUSCH is transmitted based on an SRS resource indicator (SRI), and the SRI is determined based on the third field; 2. The method of claim 1, wherein the number of bits in the third field is determined based on a maximum number of bits defined for the potentially co-scheduled cells in the scheduled cell set.

12. at least one processor; When executed, the at least one processor: receiving configuration information related to a cell set by radio resource control (RRC) signaling; receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells within a scheduled cell set of the cell set; and transmitting the PUSCH based on the DCI. The DCI includes a first field of precoding information and a number of layers for the plurality of cells; The PUSCH is transmitted based on a transmit precoding matrix indicator (TPMI), the TPMI being determined based on the first field; The number of bits of the first field is determined based on a maximum value from the number of bits defined for possible co-scheduled cells in the scheduled cell set, UE (user equipment).

13. An apparatus for a user equipment (UE), comprising: at least one processor; When executed, the at least one processor: receiving configuration information related to a cell set by radio resource control (RRC) signaling; receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells within a scheduled cell set of the cell set; and transmitting the PUSCH based on the DCI. The DCI includes a first field of precoding information and a number of layers for the plurality of cells; The PUSCH is transmitted based on a transmit precoding matrix indicator (TPMI), the TPMI being determined based on the first field; The apparatus, wherein the number of bits in the first field is determined based on a maximum number of bits from numbers of bits defined for possible co-scheduled cells in the scheduled cell set.

14. At least one processor receiving configuration information related to a cell set by radio resource control (RRC) signaling; receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells within a scheduled cell set of the cell set; and transmitting the PUSCH based on the DCI, The DCI includes a first field of precoding information and a number of layers for the plurality of cells; The PUSCH is transmitted based on a transmit precoding matrix indicator (TPMI), the TPMI being determined based on the first field; A storage medium, wherein the number of bits in the first field is determined based on a maximum number from the number of bits defined for possible co-scheduled cells in the scheduled cell set.

15. A method for transmitting configuration information related to a cell set by radio resource control (RRC) signaling; transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells within a scheduled cell set of the cell set; receiving the PUSCH based on the DCI; The DCI includes a first field of precoding information and a number of layers for the plurality of cells; The PUSCH is transmitted based on a transmit precoding matrix indicator (TPMI), the TPMI being determined based on the first field; A method, wherein the number of bits in the first field is determined based on a maximum number from numbers of bits defined for possible co-scheduled cells in the scheduled cell set.

16. at least one processor; When executed, the at least one processor: transmitting configuration information related to a cell set by radio resource control (RRC) signaling; transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells within a scheduled cell set of the cell set; and receiving the PUSCH based on the DCI; The DCI includes a first field of precoding information and a number of layers for the plurality of cells; The PUSCH is transmitted based on a transmit precoding matrix indicator (TPMI), the TPMI being determined based on the first field; The number of bits in the first field is determined based on a maximum value from the number of bits defined for possible co-scheduled cells in the scheduled cell set.

Images