Method and apparatus for transmitting / receiving signal in wireless communication system

By introducing TCI fields into the DCI of the wireless communication system and adopting the code point expansion method, the problem of large DCI payload size in multi-cell carrier aggregation scenario is solved, and more efficient signal transmission, reception and scheduling efficiency is achieved.

CN119014104APending Publication Date: 2024-11-22LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036361.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-02-16
Filing Date
2023-04-27
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In wireless communication systems, it is difficult for the prior art to effectively transmit and receive control and data signals, especially in multi-cell carrier aggregation scenarios, the payload size of DCI is large, resulting in low scheduling efficiency.

Method used

By introducing a transmission configuration indicator (TCI) field in DCI and mapping its code points to the state of multiple cells, the code point expansion method is used to reduce the number of bits of DCI and improve the efficiency of multi-cell scheduling.

Benefits of technology

It realizes more efficient transmission and reception of signals in wireless communication systems, reduces the payload size of DCI, and improves the efficiency and flexibility of multi-cell scheduling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014104A_ABST
    Figure CN119014104A_ABST
Patent Text Reader

Abstract

Disclosed in the present specification is a method and apparatus for monitoring a signal in a wireless communication system, comprising receiving DCI for scheduling a PDSCH or a PUSCH on a different cell. In particular, the DCI includes one or more DCI fields for a PDSCH or a PUSCH on a different cell.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method and an apparatus for use in a wireless communication system. Background Art

[0002] In general, wireless communication systems are being developed to diversely cover a wide range to provide communication services such as audio communication services, data communication services, etc. Wireless communication is a multiple access system capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, the multiple access system may include one of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and the like. Summary of the invention

[0003] Technical issues

[0004] An object of the present disclosure is to provide a signal transmission and reception method and apparatus thereof for efficiently transmitting and receiving control and data signals in a wireless communication system.

[0005] Those skilled in the art will understand that the objectives that can be achieved by the present disclosure are not limited to those specifically described above, and the above and other objectives that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] The present disclosure provides a method and apparatus for transmitting and receiving signals in a wireless communication system.

[0008] In one aspect of the present disclosure, a method for receiving a signal by a user equipment (UE) in a wireless communication system includes: receiving downlink control information (DCI) scheduled for a physical downlink shared channel (PUSCH) on different cells, and receiving a PDSCH on different cells based on the DCI, wherein the DCI includes a transmission configuration indication (TCI) field for cells belonging to the same group among the different cells, and a code point of the TCI field is mapped to a plurality of TCI states equal to the number of cells belonging to the group.

[0009] In one aspect of the present disclosure, a method for a base station (BS) to send a signal in a wireless communication system includes: sending downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on different cells, and sending the PDSCH on different cells based on the DCI; wherein the DCI includes a transmission configuration indication (TCI) field for cells belonging to the same group among the different cells, and a code point of the TCI field is mapped to a plurality of TCI states equal to the number of cells belonging to the group.

[0010] In another aspect of the present disclosure, a method for transmitting a signal by a user equipment (UE) in a wireless communication system includes: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells, and transmitting the PUSCH on the different cells based on the DCI, wherein the DCI includes a field of precoding information and a number of layers of a first cell belonging to a first group among the different cells, transmitting each PUSCH of the first cell based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and determining a TPMI for each of the first cells based on the field of the precoding information and the number of layers, configuring a field of second precoding information and the number of layers for each of the first cells for the DCI for scheduling the PUSCH in one cell, and determining bits in the field of the precoding information and the number of layers based on a maximum value among bits in the field of the configuration of the second precoding information and the number of layers.

[0011] In one aspect of the present disclosure, a method for a base station (BS) to transmit a signal in a wireless communication system includes: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells, and transmitting the PUSCH on the different cells based on the DCI, wherein the DCI includes a field of precoding information and a number of layers of a first cell belonging to a first group among the different cells, transmitting each PUSCH of the first cell based on a transmit precoding matrix indicator (TPMI) for each of the first cells, determining a TPMI for each of the first cells based on the field of the precoding information and the number of layers, and for the DCI for scheduling the PUSCH in one cell, configuring a field of second precoding information and the number of layers for each first cell, and determining bits of the field of the precoding information and the number of layers based on a maximum value among bits of the configured field of the second precoding information and the number of layers.

[0012] In another aspect of the present disclosure, a device, a processor, and a storage medium for executing a signal receiving method are provided. In addition, in another aspect of the present disclosure, a device, a processor, and a storage medium for executing a signal sending method are provided.

[0013] The device may include an autonomous driving vehicle that communicates with at least a UE, a network, and another autonomous driving vehicle other than the communication device.

[0014] The above-mentioned aspects of the present disclosure are only some preferred embodiments of the present disclosure, and those skilled in the art can derive and understand various embodiments reflecting the technical features of the present disclosure from the following detailed description of the present disclosure.

[0015] Beneficial Effects

[0016] According to one embodiment of the present disclosure, when control and data signals are transmitted and received between communication devices, the signals can be transmitted and received more efficiently based on an operation different from that of the prior art.

[0017] Those skilled in the art will recognize that the effects that can be achieved using the present disclosure are not limited to the contents specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 The radio frame structure is shown.

[0019] Figure 2 The resource grid during the duration of a time slot is illustrated.

[0020] Figure 3 Figure 1 shows a self-contained time slot structure.

[0021] Figures 4 to 7 is a diagram illustrating a method for transmitting and receiving a signal according to an embodiment of the present disclosure.

[0022] Figures 8 to 11 An apparatus according to an embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

[0023] The following technologies may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (WiFi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP New Radio or New Radio Access Technology (NR) is an evolved version of 3GPP LTE / LTE-A.

[0024] For clarity of description, the present disclosure will be described in the context of 3GPP communication systems (e.g., LTE and NR), which should not be construed as limiting the spirit of the present disclosure. LTE refers to technology beyond 3GPP TS 36.xxx version 8. Specifically, LTE technology beyond 3GPP TS 36.xxx version 10 is called LTE-A, and LTE technology beyond 3GPP TS 36.xxx version 13 is called LTE-A pro. 3GPP NR is a technology beyond 3GPP TS 38.xxx version 15. LTE / NR may be referred to as a 3GPP system. "xxx" specifies a technical specification number. LTE / NR may be collectively referred to as a 3GPP system. Background technology, terms, abbreviations, etc. as used herein refer to technical specifications published prior to the present disclosure. For example, the following documents may be referenced.

[0025] 3GPP NR

[0026] - 38.211: Physical channels and modulation

[0027] - 38.212: Multiplexing and channel coding

[0028] - 38.213: Physical layer procedures for control

[0029] - 38.214: Physical layer procedures for data

[0030] - 38.300: NR and NG-RAN general description

[0031] - 38.331: Radio Resource Control (RRC) Protocol Specification

[0032] Figure 1 The radio frame structure for NR is illustrated.

[0033] In NR, UL and DL transmissions are configured on a frame basis. Each radio frame has a length of 10ms and is divided into two 5ms half-frames. Each half-frame is divided into five 1ms subframes. A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each slot includes 12 or 14 OFDM (A) symbols. When a normal CP is used, each slot includes 14 OFDM symbols. When an extended CP is used, each slot includes 12 OFDM symbols. Symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform-extended-OFDM (DFT-s-OFDM) symbols).

[0034] Table 1 exemplarily illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS in the normal CP case.

[0035] [Table 1]

[0036]

[0037] *N slot symb : The number of symbols in a time slot

[0038] *N frame, u slot : Number of time slots in a frame

[0039] *N subframe, u slot : Number of time slots in a subframe

[0040] Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS in the case of extended CP.

[0041] [Table 2]

[0042]

[0043] In the NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., a subframe, a time slot, or a transmission time interval (TTI)) consisting of the same number of symbols (referred to as a time unit (TU) for convenience) may be configured differently between the aggregated cells.

[0044] In NR, various parameter sets (or SCS) can be supported to support various fifth generation (5G) services. For example, with an SCS of 15 kHz, wide areas in traditional cellular bands can be supported, while with an SCS of 30 kHz or 60 kHz, dense urban areas, lower latency, and wide carrier bandwidth can be supported. For an SCS of 60 kHz or higher, bandwidths above 24.25 kHz can be supported to overcome phase noise.

[0045] The NR frequency band may be defined by two types of frequency ranges FR1 and FR2. FR1 and FR2 may be configured as described in Table 3 below. FR2 may be millimeter wave (mmW).

[0046] [Table 3]

[0047]

[0048] Figure 2 The resource grid during the duration of one time slot is illustrated.

[0049] A slot includes multiple symbols in the time domain. For example, a slot includes 14 symbols in the normal CP case and 12 symbols in the extended CP case. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) may be defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interleavings (referred to as interleavings) may be defined in the frequency domain. Interleaving m∈{0, 1, ..., M-1} may be composed of (common) RBs{m, M+m, 2M+m, 3M+m,...}. M represents the number of interleavings. A bandwidth part (BWP) may be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed in an active BWP, and only one BWP may be activated for a UE. Each element in a resource grid may be referred to as a resource element (RE), to which a complex symbol may be mapped.

[0050] In a wireless communication system, a UE receives information from a BS in a downlink (DL), and the UE transmits information to the BS in an uplink (UL). Information exchanged between the BS and the UE includes data and various control information, and there are various physical channels / signals according to the type / purpose of the information exchanged therebetween. A physical channel corresponds to a set of resource elements (REs) that carry information originating from a higher layer. A physical signal corresponds to a set of REs that are used by the physical layer but do not carry information originating from a higher layer. The higher layer includes 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, and the like.

[0051] DL physical channels include physical broadcast channel (PBCH), physical downlink shared channel (PDSCH) and physical downlink control channel (PDCCH). DL physical signals include DL reference signal (RS), primary synchronization signal (PSS) and secondary synchronization signal (SSS). DL RS includes demodulation reference signal (DM-RS), phase tracking reference signal (PT-RS) and channel state information reference signal (CSI-RS). UL physical channels include physical random access channel (PRACH), physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH). UL physical signals include UL RS. UL RS includes DM-RS, PT-RS and sounding reference signal (SRS).

[0052] In the present disclosure, a base station (BS) may be, for example, a gNodeB (gNB).

[0053] DCI for scheduling PDSCH or PUSCH on multiple serving cells

[0054] The above content can be used in combination with the method proposed in the present disclosure, which will be described later. Alternatively, the content can illustrate the technical features of the method proposed in the present disclosure.

[0055] In addition, the following method can also be applied to the above-mentioned NR system (licensed band) or shared spectrum. Therefore, it is obvious that the terms, expressions and structures in this document can be modified to be suitable for the system so as to implement the technical ideas of the present disclosure in the corresponding system.

[0056] In the case of carrier aggregation (CA) in which multiple cells are configured, a multi-cell scheduling (multi-CC scheduling) method of simultaneously scheduling multiple serving cells / CCs through a single DCI may be considered (based on the reasons in Table 4) to reduce the DCI overhead required for PDSCH / PUSCH scheduling. In the present disclosure, the expression "scheduling multiple cells" may be understood as "scheduling PDSCH or PUSCH to be transmitted in each of multiple cells". In other words, the multi-cell DCI is a DCI for scheduling PDSCH or PUSCH on multiple different cells.

[0057] Table 4 shows the reasons for supporting DCI for this purpose and can be understood as one of the motivations for introducing such DCI (PDCCH).

[0058] [Table 4]

[0059]

[0060] In this regard, a discussion called "multi-carrier enhancement" is ongoing, which is to specify a method to schedule PUSCH or PDSCH on multiple serving cells through a single DCI.

[0061] The present disclosure proposes a scheduling method using a DCI field having a changed structure compared to a conventional DCI field to more efficiently perform an operation of scheduling a PUSCH or PDSCH on multiple serving cells through a single DCI. In more detail, a more efficient scheduling method is proposed by changing a DCI field related to multiple input and multiple output (MIMO).

[0062] In the present disclosure, DCI that schedules PUSCH (or PDSCH) on (one or) multiple serving cells at the same time is referred to as "m-CC DCI or multi-cell DCI". DCI that has a conventional DCI format and schedules PUSCH (or PDSCH) on a single serving cell is referred to as "s-CC DCI or single-cell DCI". m-CC DCI can be distinguished from the existing s-CC DCI by the DCI format, RNTI, or indicator field within the DCI.

[0063] PUSCH (or PDSCH) of different numbers / combinations of serving cells may be scheduled through one m-CC DCI. For example, only serving cell #1 may be scheduled through m-CC DCI, serving cells #1 / 2 may be scheduled, or serving cells #1 / 2 / 3 may be scheduled. These numbers / combinations may be distinguished through a specific field in the DCI or through the RNTI.

[0064] The case where PUSCH (or PDSCH) on one cell is scheduled only via m-CC DCI may be referred to as an “s-CC scheduling case.” The case where PUSCH (or PDSCH) on multiple cells is scheduled may be referred to as an “m-CC scheduling case.”

[0065] Even for one UE, the channel conditions of individual cells may be different from each other, so the number of (MIMO transmission) layers applied to each PDSCH or PUSCH may be different. However, in order to provide maximum flexibility, the payload size of the m-CC DCI may increase significantly when all DCI fields indicating information for each cell are included in the DCI. In particular, a compact DCI field configuration may be required to schedule three or more cells simultaneously. Therefore, a method for configuring the following fields related to MIMO operation in the fields included in the m-CCDCI (to reduce the DCI payload size) is proposed.

[0066] - SRS resource indication related fields (e.g., "SRS resource set indicator" field, "SRS resource indicator" field, or "second SRS resource indicator" field)

[0067] - Fields related to TPMI and layer number settings (e.g., "Precoding information and layer number" field or "Second precoding information" field)

[0068] - "Transmission Configuration Indication" field

[0069] Multiple CCs scheduled simultaneously via m-CC DCI (or multiple CCs to be scheduled via m-CC DCI) are defined as co-scheduled CCs. The corresponding co-scheduled CCs (and CCs belonging thereto) can be grouped into one or more subgroups. A separate field can be configured for each subgroup. The CCs belonging to each subgroup can be pre-configured by higher layer signaling. Each field (by the value indicated by it) can be applied in common to the CCs belonging to the subgroup. The subgroup can be referred to as a shared CC group. A method for applying DCI fields in common to corresponding CCs belonging to a shared CC group when the attributes of the CCs are different is proposed.

[0070] Table 5 shows that each field constituting m-CC DCI (ie, DCI format 0_X / 1_X) is divided into three types. DCI format 0_X is a DCI format for scheduling PUSCH on multiple cells, and DCI format 1_X is a DCI format for scheduling PDSCH on multiple cells. Type 1 is divided into three subtypes.

[0071] [Table 5]

[0072]

[0073] Corresponding to each type in Table 5, the terms described in the present disclosure are the same as those of Methods 1 to 4.

[0074] Method 1: Shared Cell - Public

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

[0076] Method 2: Shared State - Extension

[0077] A method in which only one field is configured within a multi-cell DCI, and each of a plurality of states to be indicated by the DCI field is configured / set by a combination of a plurality of pieces of information on a plurality of cells, rather than information on a single cell.

[0078] Method 3: Alone

[0079] A method of configuring a number of fields equal to the number of cells scheduled by multi-cell DCI (using operations configured according to corresponding DCI field instructions), a separate field corresponds to each scheduled cell, and applying the value indicated by the corresponding field to the corresponding cell.

[0080] Method 4: Shared Reference Cell

[0081] The following method: only one field is configured in a multi-cell DCI, the value indicated by the corresponding DCI field is applied only to a specific reference cell (e.g., the cell to which the corresponding DCI is transmitted, the cell with the lowest or highest cell index, or the cell indicated by the CIF field value) (from the cells scheduled by the multi-cell DCI and for which operation is configured according to the indication of the corresponding DCI field), and a predefined / configured specific default value is applied to the remaining cells.

[0082] Basically, the field for applying the shared cell-common method may correspond to a type 1A field. The field for applying the shared state-extended method may correspond to a type 1B field. The field for applying the shared reference cell method may correspond to a type 1C field. The field for applying the separate method may correspond to a type 2 field. The field in which whether method 1, 2, 3, or 4 is applied can be changed by explicit setting may correspond to a type 3 field.

[0083] The description of multi-cell scheduling of PDSCH in this disclosure may also apply to multi-cell scheduling of PUSCH. The description of multi-cell scheduling operation of PUSCH may also apply to multi-cell scheduling of PDSCH. The part described as "cell" in this disclosure may also be interpreted as the (active) BWP set / indicated in the corresponding cell.

[0084] The reference cell may represent (i) a cell with the lowest (or highest) cell index, (ii) a cell with the earliest (or latest) indicated PDSCH / PUSCH transmission start symbol time, (iii) a cell with the earliest (or latest) indicated PDSCH / PUSCH transmission end symbol time, (iv) a cell indicated by a CIF field value, or (v) a cell predetermined via RRC within a combination of cells (a co-scheduled set of cells or each cell subgroup) simultaneously scheduled by the same multi-cell DCI.

[0085] When there are multiple cells with the earliest (or latest) PDSCH / PUSCH start symbol time, the cell with the lowest (or highest) cell index among the multiple cells can be the reference cell. When there are multiple cells with the earliest (or latest) PDSCH / PUSCH end symbol time, the cell with the lowest (or highest) cell index among the multiple cells can be the reference cell.

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

[0087] For fields for applying the shared reference cell method, shared cell-common method and / or shared state-extended method, only one field may be configured in the multi-cell DCI (ie, commonly applied to all cells belonging to the co-scheduled cell set).

[0088] Alternatively, for fields to which the shared reference cell method, shared cell-common method, and / or shared state-extended method are applied, all cells belonging to the co-scheduled cell combination may be grouped into one or more (or more) subgroups, and a (commonly applied) field may be configured for each subgroup. Thus, separate / independent fields may be configured between the subgroups. Thus, the shared reference cell method, shared cell-common method, and / or shared state-extended method and field / information configuration / instruction methods based thereon may be applied to each subgroup.

[0089] Alternatively, for fields to which the shared reference cell method, the shared cell-common method, and / or the shared state-extended method are applied, all cells belonging to the schedulable cell set may be grouped into one or more (or more) subgroups, and a (commonly applied) field may be configured for each subgroup. Thus, separate / independent fields may be configured between the subgroups. Thus, the shared reference cell method, the shared cell-common method, and / or the shared state-extended method and the field / information configuration / instruction methods based thereon may be applied to each subgroup.

[0090] The subgroup may also be referred to as a cell subgroup. The cell subgroup may be configured / set to belong to a specific one or more specific cells of a co-scheduled cell combination or a schedulable cell combination. For example, the cell subgroup may be configured / set to belong to part or all of the cells of a co-scheduled cell combination or a schedulable cell combination.

[0091] In the existing situation, the DCI field to which the shared cell-common method is applied can be constructed so that a table including one or more states of each cell is pre-configured via RRC or MAC-CE, and one of the states in the table is indicated by the DCI field. The conventional case refers to scheduling based on a single-cell DCI. One or more states may include different parameters / values ​​or a combination thereof, and may correspond to a row index in each table. Therefore, "index" can be used instead of "state". Among the DCI fields, the PRB bundling size indicator, the rate matching (RM) indicator, the ZP CSI-RS trigger, and the SRS request field correspond to this structure. The DCI field corresponding to this structure can operate based on one or more of the following three options. In the following options, a cell set may refer to a schedulable cell set, a co-scheduled cell set, or a cell subgroup.

[0092] Option X): A specific state indicated by a DCI field commonly configured for a set of cells to which the shared cell-common method is applied may be interpreted / applied (for each cell) as a parameter / value or a combination thereof corresponding to a state in a table configured for each cell belonging to the set of cells.

[0093] Option Y): A specific state indicated by a DCI field commonly configured for a set of cells applying the shared cell-common method may be interpreted as a parameter / value or a combination thereof corresponding to a state in a table configured for a specific reference cell within the set of cells, and may be commonly applied to cells belonging to the set of cells.

[0094] Option Z): In a state where a separate common table to be applied commonly to a cell set is pre-configured via RRC / MAC-CE, a specific state indicated by a DCI field commonly configured for a cell set to apply the shared cell-common method can be commonly applied to the cells belonging to the cell set by being interpreted as a parameter / value or a combination thereof corresponding to the state in the common table.

[0095] [Public-T1A: Invalid state disposition]

[0096] First, the Type 1A field or Shared Cell-Common method (specifically, Option X method) is presented in more detail below.

[0097] First, in the existing s-CC DCI-based scheduling, for a specific DCI field (such as an SRS resource indicator, precoding information, and the number of layers), when one of the N states is indicated by the corresponding DCI field in a state in which N parameters / values ​​or a combination thereof are preconfigured via RRC or MAC-CE for each of the N states to be indicated by the corresponding DCI field, the UE performs a PDSCH / PUSCH transmission / reception operation by applying the parameter / value or a combination thereof configured for the indicated state. In this case, the size of the DCI field can be determined as ceil{log2(N)} bits (or K bits). Here, the N (or K) value can be configured as a different (or the same) value for each cell.

[0098] For a specific DCI field in the m-CC DCI-based scheduling, when a parameter / value or a combination thereof is pre-configured for each state of each cell (applicable to the s-CC DCI-based scheduling) as described above, if a specific state is indicated through the DCI field, the UE can perform a transmission / reception operation of the PDSCH / PUSCH scheduled for each cell by interpreting / applying the parameter / value or a combination thereof set for each cell respectively for the indicated state.

[0099] In m-CC DCI-based scheduling, by using the maximum value N_max and the minimum value N_min among N values ​​set for each cell belonging to all schedulable cell sets (or each co-scheduled cell set), the size of a specific DCI field can be determined by one of the following three methods.

[0100] Alt-A) Determined by the maximum value N_max, by ceil{log2(N_max)} bits (in this case, it can be a structure indicating up to the (first) N_max states / indexes via the DCI field)

[0101] Alt-B) Determine from the minimum value N_min by ceil{log2(N_min)} bits (in this case, it can be a structure where only the (first) N_min states / indexes are indicated by the DCI field)

[0102] Alt-C) is determined by ceil{log2(N_exp)} bits (in this case, it can be a structure that indicates only up to the (first) N_exp states / indexes via the DCI field) according to a specific value (=N_exp) configured separately

[0103] When the Alt-A method or the Alt-C method is applied, if a specific state (e.g., a state higher than {N_low-1}) is indicated by a specific DCI field of a specific cell (e.g., a cell in which N is set to N_low, where N_low is a value less than N_max), then for cell X, there may not be a parameter / value or a combination thereof configured for the corresponding state. In view of this situation, 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 fields of precoding information and the number of layers, the state corresponding to the Reserved value may or may not be included in N_max / N_low. In the following description, it is assumed that the values ​​of the DCI fields corresponding to the N states / indexes are 0,..., N-1.

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

[0105] A. When a state / index with a value higher than {N_low-1} is indicated by K bits, the operation of Alt 3 or Alt 6 may be applied.

[0106] B. For example, for the SRI (SRS Resource Indicator) field, when M=3 and K allocated to cell X is K=2, only the first 2 bits or the last 2 bits of the 3 bits may be used to interpret the SRI field.

[0107] C. For example, for the field of precoding information and the number of layers, when M=5 and K allocated to cell X is K=4, only the first 4 bits or the last 4 bits of the 5 bits may be used to interpret the field of precoding information and the number of layers.

[0108] 2) Alt 2: When a state higher than {N_low-1} is indicated by the above DCI field, specific parameters / values ​​or a combination thereof individually preconfigured / predefined for cell X are applied.

[0109] A. A specific parameter / value or combination thereof may be configured / defined as being associated with a specific one of the N_low states preconfigured for cell X (eg, the lowest or highest value).

[0110] B. For example, for the SRI field, a specific parameter / value or a combination thereof may be configured / defined as a specific SRS resource index associated with a specific one of the N_low states preconfigured for cell X (e.g., lowest or highest), or a specific SRS resource index (e.g., lowest / highest index) associated with a specific L_max value (e.g., lowest / highest L_max).

[0111] C. For example, for the fields of precoding information and number of layers, a specific parameter / value or a combination thereof may be configured / defined as a specific one of the N_low states preset for the corresponding cell X (eg, the lowest or highest state / index not associated with a reserved value).

[0112] Alt 3: When a state / index having a value higher than {N_low-1} is indicated by a DCI field, cell X is considered to have no PDSCH / PUSCH scheduling.

[0113] A. Therefore, the UE can omit the PDSCH / PUSCH transmission and reception operation on the corresponding cell X (in the case of PDSCH, the corresponding HARQ-ACK is fed back as NACK).

[0114] B. For example, when the SRI field indicates a state higher than {N_low-1}, the UE may consider that there is no PUSCH / SRS scheduling for cell X and may omit the PUSCH / SRS transmission / reception operation on cell X.

[0115] C. For example, when the field indicating the precoding information and the number of layers indicates a value higher than {N_low-1}, the UE may consider that there is no PDSCH / PUSCH scheduling for cell X and may omit the PDSCH / PUSCH transmission / reception operation on cell X (in the case of PDSCH, the corresponding HARQ-ACK may be fed back as NACK).

[0116] 4) Alt 4: For cell X, {N_max-N_low}=N_gap parameters / values ​​or combinations thereof corresponding to various states from N_low to N_max-1 may be additionally configured and applied.

[0117] A. Additional parameters / values ​​or combinations thereof may be configured as being associated with a specific N_gap state in the N_low state pre-configured for cell X.

[0118] B. For example, for the SRI field, an SRS resource associated with a specific state in the preset N_low state may be mapped to the N_gap state.

[0119] C. For example, for the fields of precoding information and the number of layers, parameters / values ​​or a combination thereof associated with a specific N_gap state in the N_low state (excluding the state / index corresponding to the reserved value) may be configured.

[0120] 5) Alt 5: For cell X, it can be interpreted and applied as a state corresponding to a value obtained by performing a modulo N_low operation on the state indicated by the DCI field.

[0121] A. For example, when N_low=5 and N_max=8, each state {0,1,2,3,4,5,6,7} indicated by the DCI field can be interpreted / applied as the state {0,1,2,3,4,0,1,2} of cell X, respectively.

[0122] B. For example, for the SRI field, when N_low=5 and N_max=8, each state {0,1,2,3,4,5,6,7} indicated by the field can be interpreted / applied as the SRS resource index #0 / 1 / 2 / 3 / 4 / 0 / 1 / 2 of cell X, respectively.

[0123] C. For example, for the fields of precoding information and number of layers, if N_low=5 and N_max=8, each state {0,1,2,3,4,5,6,7} indicated by the DCI field can be interpreted / applied as the state {0,1,2,3,4,0,1,2} of cell X, respectively.

[0124] Alt 6: When a state / index having a value higher than {N_low-1} is indicated by a DCI field, the most recently indicated state of cell X may be applied / maintained.

[0125] A. Accordingly, the UE may perform PDSCH / PUSCH transmission / reception operations on cell X by applying / maintaining the most recently indicated state to cell X.

[0126] B. For example, in the case of the SRI field, the UE may perform PUSCH / SRS transmission / reception operations on cell X by applying / maintaining the most recently indicated SRI value (via the SRI field of the same DCI format or a different DCI format) to cell X.

[0127] C. For example, in the case of the fields of precoding information and the number of layers, the UE may perform PDSCH / PUSCH transmission / reception operations on the corresponding cell X by applying / maintaining the most recently indicated state (via the corresponding fields of the same DCI format or a different DCI format) to the corresponding cell X.

[0128] [Public-T2: Field size determination]

[0129] The following are specific recommendations for methods of determining the DCI field size for Type 2 fields or fields to which a separate method is applied.

[0130] In the case of a specific DCI field in an existing s-CC DCI, when N states are to be indicated by a DCI field, the size of the DCI field can be configured as L = ceil{log2(N)} bits. L can be configured to a different (or the same) value for each cell. A specific DCI field can include multiple SRI fields as well as fields for precoding information and the number of layers.

[0131] When a specific DCI field in an m-CC DCI is configured based on the type 2 field method, for each of a plurality of (e.g., N_co) co-scheduled cell combinations configured in the entire schedulable cell combination, the sum L_sum of L values ​​configured for each cell belonging to the co-scheduled cell combination is calculated. For each of the N_co co-scheduled cell combinations, the maximum value of the calculated N_co L_sum values ​​may be determined as the size of the corresponding specific DCI field (configured in the m-CC DCI).

[0132] For example, for the SRI field, for each of the multiple (e.g., N_co) co-scheduled cell combinations configured in the entire schedulable cell combination, the sum L_sum of the L values ​​(for the SRI field) configured in each cell belonging to the co-scheduled cell combination is calculated. For each of the N_co co-scheduled cell combinations, the maximum value of the calculated N_co L_sum values ​​can be determined as the size of the corresponding SRI field (configured in the m-CC DCI).

[0133] For example, for the field of precoding information and the number of layers, for each of a plurality of (e.g., N_co) co-scheduled cell combinations (particularly cells with CB-based UL sets) configured in the entire fully schedulable cell combination, a sum L_sum of L values ​​(for the field of precoding information and the number of layers) of each cell configuration belonging to the corresponding co-scheduled cell combination (particularly cells with CB-based UL sets) is calculated. For each of the N_co co-scheduled cell combinations, the maximum value of the calculated N_co L_sum values ​​may be determined as the size of the field of precoding information and the number of layers (configured in the m-CC DCI).

[0134] [Configure table size for m-CC DCI (reduced compared to s-CC DCI)]

[0135] For specific DCI fields (such as SRI, precoding information, and number of layers, etc.) that adopt the type 2 field design method, the N_cfg status to be indicated by the corresponding DCI field in the m-CC DCI and the corresponding field size L_cfg = ceil{log2(N_cfg)} can be configured separately. In this case, it can be configured in the form of N_cfg < N and / or L_cfg < L. The type 2 field design method can include a shared cell common method based on the DCI field size determination method and / or option X method. The N_cfg status and the corresponding field size L_cfg can be configured for each cell.

[0136] Specifically, for the specific DCI field in the m-CC DCI as described above, when the N_cfg status and the field size L_cfg are configured separately for a specific cell, the type 2 field design method is applied to this cell based on the number / set of statuses and the field size. When there is no separate setting, the type 2 field design method can be applied based on the N statuses and the field size L configured in the s-CC DCI.

[0137] For example, for the SRI field, the reference cell, L_max, N_srs, and / or the number of SRS resources of a specific cell X used for the m-CC DCI can be defined / configured / indicated. When the SRI field in the m-CC DCI is configured and / or multiple CCs are scheduled via the m-CC DCI, the N_cfg status and the field size L_cfg can be determined for this cell based on the given reference cell, L_max, N_srs, and / or the number of SRS resources. When the SRI field in the m-CC DCI is configured and / or multiple CCs are scheduled via the m-CC DCI, for a cell for which the reference cell, L_max, N_srs, and / or the number of SRS resources are not defined / configured / indicated, the SRI field in the m-CC DCI of this cell can be configured based on the N statuses and the field size L configured in the s-CC DCI.

[0138] For example, for the fields of precoding information and number of layers, for a specific cell X, a reference cell for m-CC DCI purposes, a maximum rank number, a valid / invalid row index in a row of a table corresponding to the cell, and / or a constraint on a codebookSubset parameter may be defined / configured / indicated, as described in the following proposal. When the fields of precoding information and number of layers in the m-CC DCI are configured and / or multiple CCs are scheduled via the m-CC DCI, the N_cfg state and field size L_cfg may be determined for the cell based on the constraints on a given reference cell, the maximum rank number, a valid / invalid row index in a row of a table corresponding to the cell, and / or a codebookSubset parameter. When the fields for precoding information and the number of layers in the m-CC DCI are configured and / or multiple CCs through the m-CC DCI are scheduled, for cells that do not define / configure / indicate the reference cell, the maximum rank number, the valid / invalid row index in the row of the table corresponding to the cell, and / or the constraints on the codebookSubset parameter, the fields for precoding information and the number of layers in the m-CC DCI of the cell can be configured based on the N states and field size L configured in the s-CCDCI.

[0139] SRS resource indication related fields

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

[0141] [Table 6]

[0142]

[0143]

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

[0145] When multiple transmission and reception points (TRPs) are configured for UL transmission of the UE, this field indicates a single TRP among the TRPs to be used by the scheduled PUSCH, or this field indicates the transmission order of multiple TRPs to be used by the scheduled PUSCH. When PUSCH is transmitted through a single TRP, it can be referred to as single-TRP operation, and when PUSCH is transmitted through multiple TRPs, it can be referred to as multi-TRP operation.

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

[0147] [Table 7]

[0148]

[0149] 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 may be present in the DCI only in the s-CC scheduling case, while the SRS resource set indicator field may not be 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 corresponding scheduling cell, the corresponding field may be defined as not present. Therefore, the SRS resource set indicator field may be present in the DCI only when scheduling is performed in a cell in which multi-TRP UL operation is configured and it is an s-CC scheduling case.

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

[0151] Options 1-1 and 1-2 below disclose methods of applying the "SRS Resource Indicator" field when CCs with and without multi-TRP UL operation are grouped into a shared CC group.

[0152] (Option 1-1) When a CC configured with multi-TRP UL operation and a CC not configured with multi-TRP UL operation are configured as a shared CC group, the SRS resource set indicator field configuration is omitted, and the SRS resource (or SRS resource set) related operation of the CC with multi-TRP UL operation set may be predefined or indicated via MAC CE. For example, the UE may be predefined / configured to consider this field as corresponding to code point "00" and operate in the corresponding mode.

[0153] (Option 1-2) CCs configured with multi-TRP UL operation and CCs not configured with multi-TRP UL operation are shared CCs. When configured as a group, the SRS resource set indicator field is present or configured in the DCI. For CCs not configured with multi-TRP UL operation, this field is ignored. For CCs configured with multi-TRP UL operation, the index indicated by this field can be universal.

[0154] <"SRS Resource Indicator" field>

[0155] For the scheduled cell, the SRI indication method may be different depending on whether the transmission scheme configured for the UE is codebook-based transmission or non-codebook-based transmission. Codebook-based transmission means that txConfig in the RRC parameter PUSCH-Config is configured as "codebook". Codebook-based transmission is also called CB-based UL. Codebook-based transmission means that txConfig in the RRC parameter PUSCH-Config is configured as "non-codebook". Non-codebook-based transmission is also called NCB-based UL.

[0156] Specifically, for NCB-based UL, the number of layers is determined based on the number of SRS resources indicated in the number of SRS resources in the SRS resource set (= N_srs). Therefore, the number of bits required in the SRI field is equal to (Where L_max is the maximum number of PUSCH layers that the UE can support). For CB-based UL, one of the N_srs SRS resources is selected, and the number of layers is ultimately determined by the SRS resource and TPMI. Therefore, the number of bits required in the SRI field is .

[0157] For cells with NCB-based UL scheduled via the same m-CC DCI, if there is a constraint that the number of layers between cells can be the same, the number of bits can be saved. Even for the 'Second SRS Resource Indicator' field, only 1 bit is needed if the number of layers between two TRP transmissions is the same. bits, instead of When a specific cell among multiple scheduled cells scheduled by the same m-CC DCI is configured as a reference cell, for the corresponding reference cell, bits to indicate SRI, and for other scheduling cells except the corresponding reference cell, bits to indicate SRI.

[0158] Rules may be needed regarding which of the multiple scheduled cells is designated as the reference cell. For example, the reference cell may be defined and / or configured as the cell with the lowest cell index, the cell with the highest cell index, the cell with the lowest SCS set, the cell with the highest SCS set, the scheduled cell in which the m-CC DCI is sent, 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 configured as a specific (one) cell within each scheduled cell combination based on the cell combination scheduled by the m-CC DCI.

[0159] The constraint on the number of layers may only apply to the m-CC scheduling case, while there may be no constraint on the number of layers for the s-CC scheduling case. In this case, a number of fields equal to the number of cells scheduled via the m-CC DCI is configured in the corresponding DCI (configuration operations are performed for them according to the corresponding DCI field instructions). The SRI field can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the corresponding field is applied to the corresponding cell. This method of configuring the field is called "Type 2 field design method".

[0160] For cells configured with NCB-based UL, the L_max value can be configured / applied in different ways depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the case of s-CC scheduling, even if the L_max value follows the predefined / configured value of each cell, in the case of m-CC scheduling, the L_max value may be limited to K. The K value can be configured or predefined. For example, K=1. Alternatively, in the case of m-CC DCI-based scheduling, the value of L_max can always be limited to K. The K value can be configured or predefined. For example, K=1. In this case, a number of fields equal to the number of cells scheduled via the m-CC DCI are configured in the corresponding DCI (operations are configured for them according to the corresponding DCI field instructions). The SRI field can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the corresponding field is applied to the corresponding cell. This method of configuring fields is called "Type 2 field design method".

[0161] For cells configured with CB-based UL and / or NCB-based UL, the N_srs value may be configured / applied in different ways depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the case of s-CC scheduling, even if the N_srs value follows the predefined / preconfigured value of each cell, in the case of m-CC scheduling, the N_srs value may be limited to K. The K value may be configured or predefined. For example, K=1. Alternatively, in the case of m-CC DCI-based scheduling, the N_srs value may always be limited to K. The K value may be configured or predefined. For example, K=1.

[0162] Even if the number of SRS resources in the SRS resources configured for a specific cell (when using s-CC DCI scheduling) is N1, in the case of m-CC DCI-based scheduling or m-CC scheduling, only a number of SRS resources less than N1 (= N2) may be allowed. In this case, rules may be required as to which N2 SRS resources are selected. For example, N2 SRS resources (or SRIs) within an SRS resource set may be selected, whose index is a multiple of the lowest index, the highest index, or a specific N value. Among the SRS resources in the SRS resource set, specific N2 SRIs may be pre-configured separately for the m-CC DCI-based scheduling or the m-CC scheduling.

[0163] For example, in the case of s-CC scheduling, the SRI field / information is configured / indicated based on the N1 SRI. In the case of m-CC scheduling, the SRI field / information of each cell can be (individually) configured / indicated based on the N2 SRI (less than N1). Alternatively, a constraint can be imposed on the cell configured as the m-CC DCI scheduling target so that only one SRS resource is always configured in the SRS resource set. In this case, a number of fields equal to the number of cells scheduled via the m-CC DCI are configured in the corresponding DCI (and their actions are configured according to the corresponding DCI field instructions). The SRI field can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the corresponding field is applied to the corresponding cell. This method of configuring fields is called "Type 2 field design method".

[0164] For multiple cells scheduled by the same m-CC DCI, when there are multiple SRI code points required by each cell, the number of bits required can be minimized if the number of bits of the SRI field configured in the m-CC DCI is equal to the product of the number of code points required by each cell, rather than converted to the sum of the number of bits of the number of code points required by each cell. For example, when scheduling PUSCH on cells #1 / 2 / 3 via m-CCDCI, cell #1 may require 10 code points, cell #2 may require 10 code points, and cell #3 may require 10 code points. When the number of bits of the SRI field configured in the m-CC DCI is equal to the product of the number of code points required by each cell, the SRI field can be configured with ceil{log2(10x10x10)}=10 bits instead of 4+4+4=12 bits.

[0165] Alternatively, a combination of multiple SRI information of multiple cells may be indicated via a single code point. A single code point may be indicated by a single SRI field configured within the m-CC DCI. For example, when PUSCH is scheduled on cell #1 / 2 / 3, the SRI field is configured with 1 bit. In detail, when the 1-bit SRI field indicates "0", the UE can recognize that SRI=0 for cell #1, SRI=1 for cell #2, and SRI=0,1 for cell #3, and when indicating "1", the UE can recognize that SRI=1 for cell #1, SRI=0 for cell #2, and SRI=1, 2 for cell #3. Therefore, the SRI value of each cell corresponding to each code point may be pre-configured and / or indicated via MAC CE. Based on the number of code points configured and / or indicated via MAC CE, the final bit in the SRI may be determined. For example, when values ​​are configured for K code points, ceil{log2(K)} bits may be allocated to one SRI field.

[0166] For each cell configured with CB-based UL and each cell configured with NCB-based UL scheduled by the same m-CC DCI, a method of indicating a combination of multiple SRI information of multiple cells through one code point may be applied. For example, in a state where two SRI fields are configured in the m-CC DCI, a combination of multiple SRI information of multiple cells configured with CB-based UL may be indicated by the first SRI field, and a combination of multiple SRI information of multiple cells configured with NCB-based UL may be indicated by the second SRI field.

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

[0168] In options 2-1 to 2-3, a constraint may be considered to ensure that only CCs of the same type belong to a shared CC group. This constraint requires that all CCs belonging to a shared CC group be configured as either NCB-based UL only or CB-based UL only.

[0169] (Option 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 may be configured to be the same number. For example, the SRI field may be configured based on the minimum number of code points configured for single-cell scheduling of 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 index may be indicated.

[0170] (Option 2-2) The SRI field may be configured based on the maximum number of codepoints configured for single-cell scheduling of each CC. When the codepoint indicated by this field is invalid for a specific CC, scheduling for the corresponding CC is not considered.

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

[0172] Alternatively, different types of CCs may be allowed to belong to a shared CC group. That is, some CCs within a shared CC group may be allowed to configure NCB-based UL and other CCs may be allowed to configure CB-based UL. Option A and Option B disclose methods of applying the "SRS resource indicator" field when different types of CCs belong to a shared CC group.

[0173] (Option A) In this case, the number of codepoints required per CC in the shared CC group is limited to 1, and the codepoints may be preconfigured or indicated via the MAC CE. The SRI field configuration in the DCI may be omitted.

[0174] (Option B) Configure the SRI field and / or corresponding table for a specific type (e.g., CB-based UL). For other types (e.g., NCB-based UL), a default code point may be applied. The default code point may be pre-configured or indicated via MAC CE. Option 2-1 / 2-2 / 2-3 above may be applied as a method for configuring the SRI field for a specific type in Option B.

[0175] When NCB-based UL is configured for some co-scheduled CCs and CB-based UL is configured for other CCs, the Type 2 method may be applied to the SRI field (when there is no separate configuration for Type 1A or Type 2). In other words, when the configuration of NCB-based UL or CB-based UL is different from CCs within the co-scheduled CCs, the UE may not expect a Type 1A configuration in the SRI field. When all CCs are co-configured as NCB-based UL or CB-based UL, the Type 1A method may be applied to the SRI field (when there is no separate Type 1A or Type 2 configuration).

[0176] When multiple SRS resource sets are configured for a specific cell (for m-TRP operation), if PUSCH / SRS on the corresponding specific cell is scheduled via m-CC DCI, it may be necessary to determine which SRI within which SRS resource set is indicated via the SRI field. As one method, when PUSCH / SRS on the corresponding specific cell is scheduled via m-CC DCI, the SRS resource set corresponding to the highest or lowest SRS resource set index configured for the corresponding specific cell may be applied (or used / configured). As another method, when PUSCH / SRS on the corresponding specific cell is scheduled via m-CC DCI, the SRS resource set corresponding to the specific SRS resource set index may be applied (or used / configured) via separate configuration / indication of the BS.

[0177] <"Second SRS Resource Indicator" field>

[0178] Only when the SRS resource set indicator field indicates that the second SRS resource set is valid, the corresponding field is activated, otherwise it is considered to be reserved.

[0179] The corresponding field may not exist in the m-CC DCI. Alternatively, the corresponding field may exist only in the s-CC scheduling case and not in the m-CC scheduling case. Even in the s-CC scheduling case, if multi-TRP UL operation is not configured for the corresponding scheduling cell, the corresponding field may be defined as not existing. For example, when scheduling is performed only for cells configured with multi-TRP UL operation and in the s-CC scheduling case, the second SRS resource indicator field may exist.

[0180] Alternatively, when the second SRS resource set is indicated to be valid on a cell scheduled by an m-CC scheduling case or an s-CC scheduling case (by the above method) but the field does not exist, one or more SRIs corresponding to the code points to be applied to the cell may be predefined / configured or updated by the MAC CE. As one method, the UE may consider that the same SRI (for the corresponding cell) is indicated via the 'SRS resource indicator' field. Alternatively, which SRI to use on the second SRS resource set may be preconfigured / defined. For example, the SRS resource with the lowest or highest index within the SRS resource set may be selected, and a specific SRI may be preconfigured. Alternatively, a configuration constraint may be imposed so that for a cell configured with an m-CC DCI, only one SRS resource is always configured in the second SRS resource set.

[0181] For reference, according to the 3GPP protocol, when the UE is configured with a CB-based SRS resource set or an NCB-based SRS resource set, the PUSCH scheduled by the 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', the PUSCH scheduled by the DCI format 0_X is always associated with the first SRS resource set with 'codebook' or 'non-codebook'). Referring to Table 7, the first and second SRS resource sets are respectively the resource sets with lower and higher ResourceSetId in the two SRS resource sets configured by the RRC parameter ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 (Note 1 of Table 7: The first and second SRS resource sets are respectively the resource sets with lower and higher srs-ResourceSetId in the two SRS resource sets configured by the higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2). srs-ResourceSetId can be the ID of the SRS resource set, indicated by an integer between 0 and maxNrofSRS-ResourceSets-1. maxNrofSRS-ResourceSets can be, for example, 16. The first SRS resource set corresponds to a lower SRS resource set (a resource set with a lower index than the second SRS resource set), and the second SRS resource set corresponds to a higher SRS resource set (a resource set with a higher index than the first SRS resource set). In summary, when a CB-based SRS resource set or an NCB-based SRS resource set is configured in the UE, the PUSCH scheduled by the multi-cell DCI is always associated with the SRS resource set with a lower index.

[0182] For example, when two NCB-based SRS resource sets are configured and the SRI value is given by the m-CC DCI field, the UE may apply the indicated SRI to the PUSCH repetition according to the first SRS resource set.

[0183] Options 3-1 and 3-2 propose a method of applying the "second SRS resource indicator" field when CCs configured and not configured with multi-TRP UL operation are grouped into a shared CC group.

[0184] (Option 3-1) When a CC configured with multi-TRP UL and a CC not configured with multi-TRP UL 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 configured with multi-TRP UL operation can be applied to the second SRI in the same manner as predefined, indicated by MAC CE, or indicated by the SRI field.

[0185] (Option 3-2) The "Second SRS Resource Indicator" field exists or is configured, but is not considered for CCs that do not configure multi-TRP UL operation. For CCs that configure multi-TRP UL operation, the index indicated by the corresponding field may be commonly applied.

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

[0187] Table 8 shows DCI fields related to TPMI and layer number disclosed in 3GPP TS 38.212 document.

[0188] [Table 8]

[0189]

[0190]

[0191]

[0192]

[0193]

[0194] <“Precoding information and number of layers” field>

[0195] The corresponding field is required only for CB-based UL, especially when the port number of the indicated SRS resource is 2 or more, and the transmit precoding matrix information (TPMI) and the number of layers are ultimately determined by the corresponding field.

[0196] For cells with CB-based UL scheduled via the same m-CC DCI, bits can be saved if there is a constraint that the number of layers can be the same between cells. This corresponds to the same principle as saving up to 1 to 2 bits by having the same number of layers between two TRP transmissions in the case of the "second precoding information" field. In this case, among multiple scheduled cells scheduled by the same m-CC DCI, one specific cell is configured as a reference cell, and for the reference cell, the TPMI and number of layers are indicated by the required bits in the "Precoding information and number of layers" field. For other scheduled cells other than the reference cell, the TPMI and number of layers can be indicated by as many bits as possible in the "second precoding information" field.

[0197] Rules may be required as to which of the multiple scheduled cells is designated as the reference cell. Rules for determining the reference cell may be predefined. For example, the reference cell may be the cell with the lowest index, the cell with the highest index, the cell with the lowest SCS setting, the cell with the highest SCS setting, the scheduled cell in which the m-CC DCI is sent, the cell with the minimum maxRank value set, or the cell with the maximum maxRank value configured. Alternatively, the reference cell may be defined and / or configured as a specific (one) cell within each scheduled cell combination based on the combination of cells scheduled by the m-CCDCI.

[0198] The constraint on the number of layers may only apply to m-CC scheduled cells, and there may be no constraint on the number of layers for s-CC scheduling. In this case, multiple fields equal to the number of cells scheduled via m-CC DCI are configured in the corresponding DCI (configuration operations are performed for them according to the corresponding DCI field instructions). The fields for precoding information and the number of layers can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the field is applied to the corresponding cell. This method of configuring fields is called "Type 2 field design method".

[0199] For cells configured with CB-based UL, the maximum number of ranks / layers may be configured / applied in different ways depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the case of s-CC scheduling, even if the maxRank value follows the predefined / preconfigured value of each cell, in the case of m-CC scheduling, the maxRank value may be limited to K. Alternatively, in the case of m-CC DCI-based scheduling, the value of maxRank may always be limited to K. Alternatively, a configuration constraint may be imposed so that for cells configured as m-CC DCI scheduling targets, the maxRank value is always configured to K. The K value may be configured or predefined. For example, K=1. In this case, a number of fields equal to the number of cells scheduled via the m-CC DCI are configured in the corresponding DCI (configuration operations are performed for them according to the corresponding DCI field instructions). The fields for precoding information and number of layers can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the field is applied to the corresponding cell. This method of configuring fields is called "Type 2 field design method".

[0200] In practice, it may not be easy to match the number of precoders or layers for each cell. When the number of layers is limited, there is a disadvantage of reduced data rate. With this in mind, a separate table and separate fields corresponding to each cell may be configured for each cell, and the TPMI and number of layers may be indicated for each cell through separate fields. A method of reducing the total number of bits required for TPMI and number of layers instructions by adjusting the number of rows in the table for each cell may be considered.

[0201] For example, for 4 antenna port SRS (precoding information and number of layers for 4 antenna ports) as shown in Table 9 below, when certain conditions are met (if transform precoder is disabled, maxRank=2 and ul-FullPowerTransmission=fullpowerMode1, codebookSubset=partialAndNonCoherent), signaling is required for 30 combinations of TPMI and number of layers. However, when the corresponding cell is scheduled via m-CC DCI, the table may include only some of the 30 rows corresponding to the 30 combinations. This allows reducing the bits required to configure / indicate the "precoding information and number of layers" field / instruction for the corresponding cell. For example, when only 8 rows are selected from 30 rows, only 3 bits instead of 5 bits are required to indicate the TPMI and number of layers of the corresponding cell.

[0202] In this case, for each cell (in which CB-based UL is configured), only which row indexes are selected from the existing codebook to reduce the codebook size may be individually configured or predefined. For example, only even row indexes may be selected, only indexes that are multiples of a specific N value may be selected, only a specific number of lowest indexes may be selected, or only a specific number of highest indexes may be selected.

[0203] The corresponding method may be applied differently depending on the actual scheduled cell (the codebook size may be different), and may not be applicable to the s-CC scheduling case. For example, in the s-CC scheduling case, the TPMI and layer number related fields / information are configured / indicated based on Table 9 below. In the m-CC scheduling case, the TPMI and layer number related fields / information may be configured / indicated based only on certain (e.g., 8) rows in Table 9 below. In this case, a number of fields equal to the number of cells scheduled via the m-CC DCI are configured in the corresponding DCI (configuration operations are performed for them according to the corresponding DCI field instructions). The fields for precoding information and the number of layers can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the field is applied to the corresponding cell. This method of configuring fields is called "Type 2 field design method".

[0204] In a similar manner, constraints on the codebookSubset parameters can reduce the bits allocated to the corresponding fields. For example, in the case of m-CC DCI scheduling, 1 bit of information can be saved by not allowing the full-partial-incoherent mode. Alternatively, when the case is s-CC scheduling, the constraints on these codebookSubset parameters may not apply, but only apply to the case of m-CC scheduling. In this case, a number of fields equal to the number of cells scheduled via the m-CC DCI are configured in the corresponding DCI (operations are configured for them according to the corresponding DCI field instructions). The fields for precoding information and the number of layers can be configured in the following manner: each scheduled cell corresponds to a separate field, and the value indicated by the field is applied to the corresponding cell. This method of configuring fields is called "Type 2 field design method".

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

[0206] [Table 9]

[0207]

[0208] Options 4-1 to 4-3 disclose a method of applying the "precoding information and number of layers" field when CCs configured with NCB-based UL operation and CCs configured with CB-based UL operation are grouped into a shared CC group, or when the table configuration referenced by each CC is different even when the shared CC group is grouped only with CCs configured with CB-based UL operation.

[0209] First, this field itself is only required for CCs with CB-based UL operation set, so when a CC with NCB-based UL operation configured is included in a shared CC group (and the same is true for a CC with CB-based UL operation configured and the port number of SRS resources is 1), the indication in the field can be ignored for the CC.

[0210] (Option 4-1) The number of code points required for each CB-based UL operation configured in the same shared CC group can be configured to be the same. For example, the TPMI field can be 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 index can be indicated.

[0211] (Option 4-2) Alternatively, the TPMI field may be configured based on the maximum number of code points configured for single-cell scheduling of each CC. When the code point indicated by this field is invalid for a specific CC, scheduling for the corresponding CC is not considered.

[0212] (Option 4-3) The TPMI field is configured in the same manner as Option 4-3 above, but if the indicated codepoint is invalid for a specific CC, the UE may operate to assume / apply a specific codepoint predefined / configured for the corresponding CC.

[0213] <"Second Precoding Information" Field>

[0214] Only when the SRS resource set indicator field indicates that the second SRS resource set is valid, the corresponding field is activated, otherwise it is considered to be reserved.

[0215] The corresponding field may not exist in the m-CC DCI. Alternatively, the corresponding field may exist only in the s-CC scheduling case and not in the m-CC scheduling case. Even in the s-CC scheduling case, if multi-TRP UL operation is not configured for the corresponding scheduling cell, the corresponding field may be defined as not existing. For example, when scheduling is performed only for cells configured with multi-TRP UL operation and in the s-CC scheduling case, the second precoding information field may exist.

[0216] Alternatively, when it is indicated that the second SRS resource set is valid on a cell scheduled by an m-CC scheduling case or an s-CC scheduling case (by the above method) but this field does not exist, the TPMI / number of layers corresponding to the code point applied to the cell may be predefined / configured or updated by the MAC CE. As a method, the UE may consider that the same number of TPMI / layers (for the corresponding cell) is indicated via the "precoding information and number of layers" field. Alternatively, which TPMI / number of layers to apply to the second SRS resource set may be preconfigured / defined.

[0217] Options 5-1 and 5-2 propose a method of applying the "second precoding information" field when CCs configured with and without multi-TRP UL operation are grouped into a shared CC group.

[0218] (Option 5-1) When a CC configured with multi-TRP UL and a CC not configured with multi-TRP UL are grouped into a shared CC group, the "second precoding information" field configuration is omitted, and the (precoding-related) operation of the CC configured with multi-TRP UL operation can be predefined or indicated by the MAC CE, or the value indicated by the "Precoding information and number of layers" field can also be applied to the second TRP.

[0219] (Option 5-2) The "Second Precoding Information" field is present or configured, but is not considered for CCs that are not configured for multi-TRP UL operation.

[0220] “ Transport Configuration Indicator ” Fields

[0221] Table 10 shows a transmission configuration indication (TCI) field disclosed in the 3GPP TS 38.212 document.

[0222] [Table 10]

[0223]

[0224] Depending on the cell-specific configuration, the instruction of the TCI state can be configured in one of the following two modes.

[0225] TCI mode #1: TCI (or spatial relation RS and / or path loss setting RS in the UL case) is configured individually for each cell (or BWP) through higher layer signaling. The higher layer signaling may be, for example, RRC signaling.

[0226] TCI mode #2: A list of cells (e.g., CC#1 / 2) that share TCI (or spatial relationship RS and / or path loss setting RS in the UL case) is configured via higher layer signaling. When the TCI state of one of the cells (e.g., CC#1) changes, the states of the other cells (e.g., CC#2) belonging to the cell list also change together. The higher layer signaling may be, for example, RRC signaling.

[0227] As a method of reducing the size of the TCI field, an independent TCI field may be configured for each cell scheduled (simultaneously) via m-CC DCI, and the number of bits of the TCI field configured for each cell may be less than 3 bits. For example, when CC#1 and CC#2 are to be scheduled via m-CC DCI, 2 bits of the TCI field corresponding to CC#1 and 2 bits of the TCI field corresponding to CC#2 may be configured respectively, so that a total of 4 bits of the TCI field in the DCI may be configured.

[0228] In this case, unlike the case of using s-CC DCI scheduling, the TCI states corresponding to the four code points of CC#1 and the four code points of CC#2 may be separately configured / indicated. Alternatively, the TCI states corresponding to the four code points of CC#1 and the four code points of CC#2 may be preconfigured as some of the TCI states preconfigured / indicated in the case of using s-CC DCI scheduling, or defined by some code points using specific rules. For example, in the case of using s-CC DCI scheduling, the TCI state corresponding to the code point with the lowest or highest index in the configured / indicated TCI state may be inherited (or used). In detail, when each cell is configured with a 2-bit TCI field, the TCI states corresponding to code points 0 to 3 may be used. Alternatively, the TCI states corresponding to some code points having an index that is a multiple of a specific N value may be inherited (or used).

[0229] A method of configuring an independent TCI field for each cell to be (simultaneously) scheduled via m-CC DCI and configuring the number of bits of the TCI field configured for each cell to be less than 3 bits may be referred to as a “separate reduced table”.

[0230] When all cells schedulable via m-CC DCI are configured to operate in TCI mode #2 and are provided in the cell list, only a common (single) TCI field may be configured without configuring a separate TCI field for each cell. Alternatively, when all cells schedulable via 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 belongs to cell list #1, but CC#3 / 4 belongs to cell list #2) or a different TCI mode is set for each cell (case 2: CC#1 / 2 belongs to cell list #1, but CC#3 and CC#4 are set with TCI mode #1), a separate TCI field may be configured for each cell and / or each cell list. For case 1, one common TCI field / information may be configured / indicated for CC#1 / 2, and another common TCI field / information may be configured / indicated for CC#3 / 4. In this case, a total of two TCI fields are configured. For case 2, one common TCI field / information is configured / indicated for CC#1 / 2, and separate TCI fields are configured for CC#3 and CC#4, respectively. In this case, a total of three TCI fields can be configured. Only a common TCI field can be configured between cells included in the common cell list, and when an independent TCI field is configured for each cell (or each cell list), the bits allocated for each cell (or each cell list) can be configured to be less than 3 bits (in the same manner as described above).

[0231] As another method of reducing the size of the corresponding TCI field, one TCI field commonly used for cells scheduled (simultaneously) via m-CC DCI may be configured, and the TCI state for each CC may be linked for one code point indicated by the corresponding TCI field. In other words, a combination of multiple TCI states for multiple cells may be configured for a single code point. For example, when CC#1 and CC#2 are scheduled via m-CC DCI, one TCI field is configured for CC#1 and CC#2. A combination of multiple TCI states corresponding to two CCs for each code point may be indicated by a single TCI field. For example, TCI state #1 of CC#1 and TCI state #2 of CC#2 may be configured / indicated simultaneously via code point 0. In this case, the TCI state corresponding to each code point of one TCI field of CC#1 and CC#2 may be configured / indicated separately from the case of using s-CC DCI scheduling. The method in which the TCI state for each CC is linked to a single code point indicated by a single TCI field may be referred to as "code point extension".

[0232] When all cells scheduled via m-CC DCI (simultaneously) are configured to operate in TCI mode #2 and are included in the cell list, only one TCI state to be commonly applied to multiple cells may be linked instead of linking the TCI state for each CC to one code point. Alternatively, when all cells scheduled via 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 A: CC#1 / 2 belongs to cell list #1, but CC#3 / 4 belongs to cell list #2) or a different TCI mode is set for each cell (case B: CC#1 / 2 belongs to cell list #1, but CC#3 and CC#4 are set with TCI mode #1), a code point linked to a separate TCI state may be configured for each cell and / or each cell list. For case A, the TCI state of CC#1 / 2 and the TCI state of CC#3 / 4 are linked together in one code point, and the TCI field contains the code point. For case B, the TCI status of CC#1 / 2, the TCI status of CC#3, and the TCI status of CC#4 are linked together in one code point, and the TCI field may contain code points. For cells included in the common cell list, only one TCI status to be commonly applied to the corresponding cells can be linked to one code point.

[0233] Based on the proposed approach, the following configurations may be possible (for cells scheduled via the same m-CC DCI).

[0234] - Between cells where TCI mode #1 is configured, either the single simplified table method or the codepoint extension method (based on a single field) can be applied.

[0235] - Between different cell lists in which TCI mode #2 is configured, either the separate simplified table approach (one (common) TCI table is configured on a per-cell list basis) or the codepoint extension approach (one (common) TCI state is configured on a per-cell list basis) may be applied.

[0236] - When cells configured with TCI pattern #1 and cells configured with TCI pattern #2 are scheduled simultaneously, these methods can be applied to each TCI pattern. Alternatively, in this case, the code point extension method can be applied to all cells. In this case, for cells configured with TCI pattern #2, one (common) TCI state can be configured per cell list.

[0237] The proposed method may only be applicable to the m-CC scheduling case, and in the s-CC scheduling case, TCI information may be exceptionally indicated based on the TCI field configured for the s-CC DCI (and the linked TCI status for each codepoint).

[0238] Options 6-1 to 6-3 propose methods of applying the TCI field when CCs configured with the TCI field and CCs not configured with the TCI field are grouped into a shared CC group.

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

[0240] (Option 6-2) When 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 for the unconfigured CC. When a codepoint other than the specified codepoint is indicated, the UE considers that there is no scheduling for the unconfigured CC.

[0241] (Option 6-3) Configure the TCI field in the m-CC DCI and apply a specific default TCI to unconfigured CCs.

[0242] Here, the specific default TCI may be a specific index (pre-configured / defined or indicated via MAC CE) in the configured TCI state ID (for single-cell scheduling of the corresponding CC). Alternatively, the specific default TCI may be TCI information corresponding to a specific CORESET (e.g., the lowest index CORESET from the latest timeslot indicating data).

[0243] In the case where CCs configured with the TCI field are grouped into a shared CC group, but the TCI mode is configured differently between each CC (CCs configured with TCI mode #1 and CCs configured with TCI mode #2 are grouped into a shared CC group), options 7-1 and 7-2 are proposed for the TCI field application method.

[0244] Unlike options 7-1 and 7-2, configuration constraints can be imposed so that only CCs configured with the same TCI mode belong to the same shared CC group. Specifically, when a shared CC group is grouped together only with CCs configured with TCI mode #2, configuration constraints can be imposed so that only CCs belonging to the same cell list belong to the group.

[0245] (Option 7-1) When CCs configured with different TCI patterns (CCs configured with the same TCI pattern #2 but belonging to different lists) belong to one shared CC group, the TCI field configuration in the m-CC DCI may be omitted and a specific default TCI may be assumed / applied for each CC.

[0246] (Option 7-2) The TCI field / table of a specific CC (e.g., a CC configured with TCI mode #2) may be configured. A specific default TCI may be applied to other CCs (e.g., a CC configured with TCI mode #1). Here, the specific default TCI may be a specific index (pre-configured / defined or indicated via MAC CE) in the configured TCI state ID (for single-cell scheduling of the corresponding CC). Alternatively, the specific default TCI may be TCI information corresponding to a specific CORESET (e.g., the lowest index CORESET from the latest timeslot indicating data).

[0247] When configuring the TCI field in the existing s-CC DCI, 3 bits are allocated, and the mapping relationship between each code point and the TCI state index can be updated through the MAC CE. However, when configuring the TCI field in the m-CCDCI through the code point extension method (based on a single field), it may be difficult to simply update through the existing MAC CE. As a solution to this problem,

[0248] - Alt-1: The mapping relationship between each code point of the TCI field in the m-CC DCI and the TCI state index of multiple cells may be restricted to be updated only through RRC signaling (or RRC reconfiguration) and not through MAC CE (for s-CC DCI). For example, only the TCI state connected to the s-CC DCI can be updated through the existing (e.g. Rel-15 / 16 / 17) MAC CE, while the TCI state connected to the m-CC DCI may not be updated.

[0249] - Alt-2: The mapping relationship between each code point of the TCI field in the m-CC DCI and the TCI state indexes of multiple cells may be updated via MAC CE (for s-CC DCI), and rules and / or constraints on the update method may be defined. As one method, only multiple TCI state indexes equal to (or less than) the number of TCI state indexes configured in the TCI field of the m-CC DCI of a specific CC may be updated via MAC CE. For example, in the table of the TCI field in the m-CC DCI in Table 11 below, a constraint of (up to) 3 (1) TCI updates for CC1 (or CC3) via MAC CE may be imposed. If the TCI index list is updated from {1,2,3} to {2,3,4} via MAC CE for CC1, the UE may recognize that the code point mapping for CC1 in Table 11 has been updated to {2 for '00', 3 for '01', 3 for '10', 4 for '11'}. If the TCI index list is updated from {4} to {1} through the MAC CE corresponding to CC3, the UE can recognize that the code point mapping for CC3 in Table 11 has been updated to {1 for '00' / '01' / '10' / '11'}.

[0250] For another example, in a table for the TCI field in the m-CC DCI as in Table 11, a constraint of 3 or less may be imposed on the TCI update performed via the MAC CE for CC1. If the TCI index list is updated from {1,2,3} to {3,4} via the MAC CE for CC1, the UE may recognize that the code point mapping for CC1 in Table 11 has been updated to {3 for '00', 4 for '01', 4 for '10', 3 for '11'}. That is, when the previous TCI state includes N TCI state indexes {T_old.0, …T_old.N-1}, and the latest TCI state includes K TCI state indexes {T_new.0, …T_new.K-1}, and N>K, the UE may recognize that the previous N TCI states (corresponding code points) have been replaced / updated / mapped by the latest N TCI state indexes. For example, the TCI state index may be updated to {T_new.0, ...T_new.K-1, T_new.0, ...} based on a modulo K operation. Alternatively, the TCI state index may be 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 repeated thereafter.

[0251] [Table 11]

[0252]

[0253] - Alt-3: The mapping relationship between each code point of the TCI field in the m-CC DCI and the TCI state index may be defined by a separate MAC CE (for m-CC DCI) to update the relationship, or the existing MAC CE (for s-CCDCI) may be extended. The TCI state index of each code point of the TCI field (in the m-CC DCI) of a specific CC may be indicated by a separate MAC CE or an existing MAC CE. For example, in the case of CC1 in Table 11 above, the TCI state index of each code point of the TCI field (in the m-CC DCI) of CC1 may be updated from {1, 2, 2, 3} to {2, 2, 4, 5} by notifying the TCI state index of each code point of the TCI field (in the m-CC DCI) of CC1 through a separate MAC CE or an existing MAC CE. Alternatively, a CC-specific TCI state index corresponding to a specific code point in the TCI field (in the m-CC DCI) may be indicated via a separate MAC CE. For example, for code point #01 in Table 11 above, the CC-specific TCI state index may be updated from {1, 2, 4, 5} to {2, 3, 3, 4} via a separate MAC CE.

[0254] The content of the present disclosure is not limited to the transmission and reception of uplink and / or downlink signals. For example, the content of the present disclosure can also be used for direct communication between UEs. The BS according to the present disclosure can be a concept that includes not only a BS but also a relay node. For example, the operation of the BS according to the present disclosure can be performed by the BS, but can also be performed by a relay node.

[0255] Obviously, the example of the method proposed above can also be included as one of the implementation methods of the present disclosure, and therefore can be considered as a proposed method. The method proposed above can be implemented independently, but can also be implemented in the form of a combination (or merger) of some proposed methods. The information on whether the proposed method is applicable (or the information on the rules of the proposed method) can be defined by a rule, so that the BS notifies the UE through a predefined signal (e.g., a physical layer signal or a higher layer signal) or the sending UE notifies the receiving UE.

[0256] Implementation Example

[0257] Figure 4 and Figure 5 is a flowchart of a signal sending and receiving method according to an embodiment of the present disclosure.

[0258] refer to Figure 4 The method according to one embodiment of the present disclosure may be performed by a UE and may include receiving a DCI for scheduling a PDSCH on a different cell ( S401 ) and receiving a PDSCH on a different cell based on the DCI ( S403 ).

[0259] refer to Figure 5 , a method according to another embodiment of the present disclosure may be performed by a BS, and may include transmitting a DCI for scheduling a PDSCH on a different cell ( S501 ) and transmitting the PDSCH on the different cell based on the DCI ( S503 ).

[0260] Apart from Figure 4 and / or Figure 5 In addition to the operations of 'DCI for scheduling PDSCH or PUSCH on multiple serving cells' and one or more operations described in Sections [1] to [3] may also be performed.

[0261] For example, referring to Section [3], the DCI for scheduling PDSCH on different cells may include a TCI field. The TCI field may be configured by the 'code point extension' method. When the TCI field is configured by the code point extension method, a common TCI table is configured for cells belonging to the same cell list among different cells in which TCI mode #2 is configured, so the DCI includes one TCI field for one cell list. The cell list may include a set of multiple cells and may be expressed as a group, a cell group, or a subgroup. In other words, the DCI includes one TCI field for cells belonging to the same group among different cells.

[0262] According to the code point extension method, a combination of multiple TCI states of multiple cells is configured for the code point of one TCI field. For example, when CC#1 and CC#2 are scheduled via m-CC DCI, one TCI field is configured for CC#1 and CC#2. A combination of multiple TCI states corresponding to two CCs can be indicated by a single code point value of one TCI field. Even when three or more CCs are scheduled via a single DCI, if the three or more CCs belong to the same cell list (or cell group), a code point value of one TCI field contained in a single DCI indicates a combination of multiple TCI states corresponding to all three or more CCs. The mapping relationship between code points and TCI states can be established by TCI state activation / deactivation of the UE-specific PDSCH MAC CE (MAC CE). Typically, one code point of a TCI field contained in a DCI for scheduling PDSCHs on different cells is mapped to multiple TCI states equal to the number of cells belonging to a group.

[0263] According to the code point extension method, when all cells that can be scheduled via m-CC DCI are configured to operate in TCI mode #2 and are included in the cell list, the m-CC DCI contains only one TCI field. All cells that can be scheduled via m-CC DCI are configured to operate in TCI mode #2, but if the cells are included in different cell lists, different TCI fields are configured for each cell list. Therefore, if different cells scheduled by the DCI belong to different cell lists, the DCI contains 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 of the first TCI field is mapped to a number of TCI states equal to the number of cells belonging to the first group, and one second code point of the second TCI field is mapped to a number of TCI states equal to the number of cells belonging to the second group.

[0264] According to the code point extension method, if the cells scheduled via the m-CC DCI have different TCI modes configured for each cell, different TCI fields are configured for each TCI mode. Therefore, if some different cells scheduled by the DCI are configured as TCI mode #2 and belong to a cell list, and one or more specific cells are configured as TCI mode #1 and do not belong to the cell list, the DCI includes a first TCI field for the cells belonging to the first group and a second TCI field for each specific cell. One code point of the first TCI field is mapped to a number of TCI states equal to the number of cells belonging to the first group, and one second code point of the second TCI field is mapped to one TCI state.

[0265] Therefore, if the cells scheduled by the m-CC DCI include cells belonging to different cell lists configured as TCI mode #2 and multiple cells configured as TCI mode #1, the m-CC DCI includes as many TCI fields as the number of cell lists plus the number of cells configured as TCI mode #1.

[0266] The TCI mode is configured based on higher layer signaling, so a specific cell is configured based on higher layer signaling as not belonging to any cell list (cell group). Cells belonging to a specific cell list are also configured based on higher layer signaling.

[0267] The code point extension method may be applied only to the m-CC scheduling case and may not be applied to the s-CC scheduling case. Therefore, when only one PDSCH is scheduled through the DCI for scheduling PDSCHs on different cells, the code point extension method is not used, and the m-CC DCI includes a TCI field configured for the s-CC DCI. When multiple cells are scheduled through the m-CC DCI, the TCI field is the first TCI field, and when one cell is scheduled through the m-CC DCI, the m-CC DCI includes a second TCI field separated from the first TCI field. One code point of the first TCI field is mapped to multiple TCI states of the m-CC DCI equal to the number of cells belonging to the first group, and one second code point of the second TCI field is mapped to one TCI state of one s-CC DCI.

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

[0269] Figure 6 and Figure 7 is a flowchart of a signal sending and receiving method according to other embodiments of the present invention.

[0270] See also Figure 6 , the method according to one embodiment of the present disclosure may be performed by a UE, and may include: receiving a DCI for scheduling a PUSCH on a different cell ( S601 ) and transmitting a PUSCH on a different cell based on the DCI ( S603 ).

[0271] refer to Figure 7 , a method according to another embodiment of the present disclosure may be performed by a BS, and may include: transmitting a DCI for scheduling a PUSCH on a different cell ( S701 ) and receiving a PUSCH on a different cell based on the DCI ( S703 ).

[0272] Apart from Figure 6 and / or Figure 7 In addition to the operation of 'DCI for scheduling PDSCH or PUSCH on multiple serving cells' and one or more operations described in Sections [1] to [3] may also be performed.

[0273] For example, the DCI for scheduling the PUSCH 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.

[0274] Each DCI field may be configured based on a combination of one or more of the methods disclosed in Sections [1] and [2].

[0275] In detail, referring to Section [2], CCs belonging to the same shared CC group may also have different CC-referenced table configurations. In this case, when Option 4-2 is applied, a TPMI field of the shared CC group is configured based on the maximum number of code points configured for DCI for single-cell scheduling (PUSCH scheduling within one cell). The TPMI field refers to the 'precoding information and number of layers' field used to indicate the TPMI. The TPMI is used to determine the transmission precoder when the UE sends a PUSCH. The number of code points is related to the number of bits in the field of precoding information and number of layers. When the number of code points is N, the number of bits in the field of precoding information and number of layers is determined by ceil{log2(N)}. Therefore, the number of bits of the 'precoding information and number of layers for single-cell scheduling' field (the second precoding information and number of layers field) of each of the first cells is determined based on the number of code points set for single-cell scheduling for each cell.

[0276] In summary, for the first cell belonging to the same shared CC group (first group) among the different cells scheduled by the m-CC DCI, a field for precoding information and the number of layers is included. The PUSCH of each of the first cells is transmitted based on the transmission precoder determined by the TPMI used for each of the first cells. The TPMI used for each of the first cells is given by a field for the precoding information and the number of layers of the first group. The number of bits in a field for the precoding information and the number of layers is determined based on the maximum value of the number of bits in a field for the precoding information and the number of layers configured for single-cell scheduling of each of the first cells. A field for the precoding information and the number of layers of the first group may also indicate the number of layers used for each of the first cells.

[0277] The number of code points for each of the first cells is determined based on the number of row indices of the table configured for single-cell scheduling for each of the first cells. 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 in each field of the second precoding information and the number of layers of the first cell is determined based on the number of antenna ports configured for single-cell scheduling for each of the first cells, codebook-based transmission, full-power transmission mode, transform precoder, maximum rank, and codebook subset.

[0278] For reference, the number of antenna ports can be 1, 2, or 4. Codebook-based transmission may refer to whether the UE uses codebook-based transmission or non-codebook-based transmission, and may be determined according to the RRC parameter txConfig. If the txConfig parameter does not exist, the UE sends the PUSCH on one antenna port. The full-power transmission mode refers to whether the UL full-power transmission mode is configured in the UE, and is configured according to the RRC parameter ul-FullPowerTransmission. In detail, the ul-FullPowerTransmission parameter includes three mode settings including fullpower, fullpowerMode1, and fullpowerMode2, and the specific operations for each mode follow the operations in Section 7.1 of the 3GPP TS 38.213 document. The transform precoder may be a specific selection of the transform precoder for the PUSCH by the UE, and is determined according to the RRC parameter transformPrecoder. If the transformPrecoder parameter does not exist, the UE may use the transform precoder value of Msg3 used in the random access process. The maximum rank may be a subset of the precoding matrix indicator (PMI) addressed by the transmission rank indicator (TRI) and configured by the RRC parameter maxRank to a value of 1 to 4. The codebook subset is a subset of the PMI addressed by the TPMI and is set by the RRC parameter codebookSubset to one of the values ​​fullyAndPartialAndNonCoherent, partialAndNonCoherent, or nonCoherent.

[0279] In other words, when the field is configured as type 1A, the field of precoding information and number of layers is determined as the maximum value of M bits associated with N different cells. For N cells, the M bits for each cell are determined based on the number of antenna ports, codebook-based transmission, full power transmission mode, transform precoder, maximum rank, and codebook subset.

[0280] Each independently configured table for the first cell is used, so even if the same row index is indicated by a value of a field of precoding information and the number of layers in each table, the TPMI value corresponding to the row index of each table is an independent value for each cell.

[0281] Here, the field of precoding information and the number of layers is configured based on the maximum number of bits in the field of second precoding information and the number of layers, so there may be a situation where a specific cell does not have a row index corresponding to a specific value of the field of precoding information and the number of layers. According to option 4-2, for a specific cell that does not have a TPMI value corresponding to one of the values ​​in the field of precoding information and the number of layers, the UE may consider that the PUSCH is not scheduled. Alternatively, according to option 4-3, for a specific cell that does not have a TPMI value corresponding to the value of the field of precoding information and the number of layers, the UE may send the PUSCH based on a predefined specific TPMI value.

[0282] The fields of precoding information and the number of layers are configured one for each shared CC group, so for a second cell belonging to the second group instead of the first group among different cells to be scheduled by DCI, the fields of precoding information and the number of layers separate from the fields of precoding information and the number of layers of the first group (the fields of third precoding information and the number of layers) may be included in the DCI.

[0283] The shared CC group may include a CC configured with CB-based UL operation and a CC configured with NCB-based UL operation, and the UE ignores the fields of precoding information and the number of layers of the CC configured with NCB-based UL operation. Therefore, when non-codebook-based transmission is configured for the PUSCH of a specific cell in the first cell, the UE sends the PUSCH on the specific cell without using the value of the field of precoding information and the number of layers.

[0284] Referring to Section [1], the UE may send PUSCH on different cells according to the SRS resource set configured for each cell. When multiple SRS resource sets are configured for a specific cell, the UE may send PUSCH on the specific cell according to the resource with the highest or lowest index configured in the SRS resource set configured for the specific cell.

[0285] Referring to options 2-1 to 2-3, among different cells schedulable by m-CC DCI, a first cell belonging to the same shared CC group (first group) includes one SRI field. The number of bits in one SRI field is determined according to the maximum value of the number of bits in the SRI field configured for each single cell scheduling of the first cell.

[0286] In other words, when the field is configured as type 1A, the SRI field is determined as the maximum value of the M bits associated with N different cells. Referring to Table 6, for N cells, when the cell is configured with NCB-based UL (txConfig=nonCodebook), the M bits of each cell are configured based on (i) the configured number of SRS resources N_SRS, and (ii) L_max (the maximum MIMO layer for PUSCH in all BWPs of the corresponding UL of the serving cell). For N cells, when the cell is configured with CB-based UL (txConfig=Codebook), the M bits of each cell are determined based on the configured number of SRS resources N_SRS. When multiple SRS resource sets are configured in one cell, the first SRS resource set with a lower index can be used, so the number of SRS resources N_SRS set can be the number of SRS resources configured in the first SRS resource set and the second SRS resource set.

[0287] The DCI format of the DCI for scheduling PUSCH on different cells may be referred to as DCI format 0_X, where X may be a natural number greater than or equal to 3. For example, the DCI format of the DCI for scheduling PUSCH on different cells may be DCI format 0_3.

[0288] In addition to reference Figures 4 to 7 In addition to the operations described, you can also combine and execute reference Figures 1 to 3 The operations described and / or one or more of the operations described in 'DCI for scheduling PDSCH or PUSCH on multiple serving cells' and sections [1] to [3].

[0289] Example of a communication system to which the present disclosure is applied

[0290] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure described herein may be applied to (but not limited to) various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0291] More specific examples will be described below with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, similar reference numerals represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0292] Figure 8 A communication system 1 applied to the present disclosure is shown.

[0293] Reference Figure 8, the communication system 1 applied to the present disclosure includes a wireless device, a BS, and a network. The wireless device is a device that performs communication using a radio access technology (RAT) (e.g., 5G NR (or new RAT) or LTE), also referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television (TV), a smart phone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptop computers). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node for other wireless devices.

[0294] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without the intervention of the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., V2V / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0295] Wireless communication / connection 150a, 150b, and 150c may be established between wireless devices 100a to 100f / BS 200 and between BSs 200. Herein, wireless communication / connection may be established through various RATs (e.g., 5G NR) such as UL / DL communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay or integrated access backhaul (IAB)). Wireless signals may be sent and received between wireless devices, between wireless devices and BSs, and between BSs through wireless communication / connection 150a, 150b, and 150c. For example, signals may be sent and received via various physical channels through wireless communication / connection 150a, 150b, and 150c. To this end, at least a portion of various configuration information for configuring a process for sending / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and a resource allocation process may be performed based on various proposals of the present disclosure.

[0296] Example of wireless device to which the present disclosure is applied

[0297] Fig. 9 A wireless device suitable for use with the present disclosure is shown.

[0298] Reference Fig. 9 , the first wireless device 100 and the second wireless device 200 may transmit wireless signals through various RATs (eg, LTE and NR). {The first wireless device 100 and the second wireless device 200} may correspond to Figure 8 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0299] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and also include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a wireless signal including the first information / signals through the transceiver 106. The processor 102 may receive a wireless signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102, and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including instructions for executing all or part of the processing controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. The processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive wireless signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may be a communication modem / circuit / chip.

[0300] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and also include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a wireless signal including the third information / signals through the transceiver 206. The processor 202 may receive a wireless signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing all or part of the processing controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. The processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive wireless signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may be a communication modem / circuit / chip.

[0301] Now, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document, and provide these messages, control information, data, or information to one or more transceivers 106 and 206. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0302] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, 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) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be included in one or more processors 102 and 202 or may be stored in one or more memories 104 and 204 and driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, instructions and / or instruction sets using firmware or software.

[0303] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured to include read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0304] One or more transceivers 106 and 206 may send user data, control information and / or wireless signals / channels mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information and / or wireless signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive wireless signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or wireless signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or wireless signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information, and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods, and / or operation flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert the received wireless signals / channels from RF band signals to baseband signals so as to process the received user data, control information, and wireless signals / channels using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert the user data, control information, and wireless signals / channels processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0305] Example of use of wireless device to which the present disclosure is applied

[0306] Fig.10 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be based on the use case / service (refer to Figure 8 ) are implemented in various forms.

[0307] Reference Fig.10 , the wireless devices 100 and 200 may correspond to Fig. 9The wireless devices 100 and 200 may be configured to include various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig. 9 The one or more processors 102 and 202 and / or the one or more memories 104 and 204 of the present invention. For example, the transceiver 114 may include Fig. 9 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and provides overall control of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / instruction / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0308] The additional component 140 may be configured in various ways depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in (but not limited to) a robot ( Figure 8 100a), vehicles ( Figure 8 100b-1 and 100b-2), XR devices ( Figure 8 100c), handheld device ( Figure 8 100d), household appliances ( Figure 8 100e), IoT devices ( Figure 8 100f), digital broadcast terminals, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices ( Figure 8 400), BS ( Figure 8 200), network node, etc. Depending on the use case / service, the wireless device can be mobile or fixed.

[0309] exist Fig.10In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. The various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured using a collection of one or more processors. For example, the control unit 120 may be configured using a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. In another example, the memory 130 may be configured using RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0310] Examples of vehicles or autonomous driving vehicles to which the present disclosure is applied

[0311] Fig.11 A vehicle or an autonomous vehicle applied to the present disclosure is shown. The vehicle or the autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0312] Reference Fig.11 The vehicle or autonomous driving vehicle 100 may include 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 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Fig.10 Block 110 / 130 / 140.

[0313] The communication unit 110 may send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an ECU. The drive unit 140a may enable the vehicle or autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100 and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may acquire information about the vehicle status, surrounding environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight 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, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a route if a destination is set, and the like.

[0314] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving route and a driving plan from the obtained data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may aperiodically / periodically obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit 140c may obtain information about the vehicle state and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving route, and / or driving plan to an external server. The external server may predict traffic information data using AI technology based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0315] Those skilled in the art will appreciate that the present disclosure may be implemented in other specific ways than those described herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above embodiments are to be interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents (rather than the above description), and all changes falling within the meaning and equivalent scope of the appended claims are intended to be covered therein.

[0316] Industrial Applicability

[0317] As described above, the present disclosure is applicable to various wireless communication systems.

Claims

1. A method for transmitting a signal by a user equipment (UE) in a wireless communication system, the method comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; as well as sending the PUSCH on the different cell based on the DCI, The DCI includes a field for precoding information and a number of layers for a first cell belonging to a first group among the different cells, wherein each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and the TPMI for each of the first cells is determined based on the precoding information and the field of the number of layers, wherein a DCI for scheduling a PUSCH in a cell is configured with a field for second precoding information and a number of layers for each of the first cells, and The bits in the field of the precoding information and the number of layers are determined based on a maximum value among the bits in the field configured with the second precoding information and the number of layers.

2. The method according to claim 1, wherein: The second precoding information and the bits of the number of layers are determined based on the number of antenna ports, codebook based transmission, full power transmission mode, transform precoder, maxRank and codebookSubset.

3. The method according to claim 1, wherein: The number of layers used for each of the first cells is determined based on the precoding information and the field of the number of layers.

4. The method according to claim 1, wherein: One value of the field of the precoding information and the number of layers corresponds to a TPMI value independently configured for each of the first cells.

5. The method according to claim 4, wherein: Based on the absence of a TPMI value corresponding to the one value for a specific cell among the first cells, a PUSCH for the specific cell is considered to be unscheduled.

6. The method according to claim 4, wherein: Based on the absence of a TPMI value corresponding to the one value for a specific cell among the first cells, a PUSCH for the specific cell is transmitted based on a predefined specific TPMI value.

7. The method according to claim 1, wherein: The DCI includes a field of third precoding information and a number of layers for a second cell belonging to a second group among the different cells, separate from the fields of the precoding information and the number of layers of the first group.

8. The method according to claim 1, wherein: Based on configuring non-codebook based transmission for a PUSCH of a specific cell among the first cells, the fields of the precoding information and the number of layers are ignored for the PUSCH of the specific cell.

9. The method according to claim 1, wherein: Based on configuring a plurality of SRS resource sets for a specific cell among the first cells, the PUSCH of the specific cell is transmitted based on an SRS resource set having a highest index among the plurality of SRS resource sets.

10. The method according to claim 1, wherein: Based on configuring a plurality of SRS resource sets for a specific cell among the first cells, the PUSCH of the specific cell is transmitted based on an SRS resource set having a lowest index among the plurality of SRS resource sets.

11. A user equipment (UE) for receiving a signal in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as At least one memory, the at least one memory being operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform specific operations, the specific operations comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; and sending the PUSCH on the different cell based on the DCI, The DCI includes a field for precoding information and a number of layers of a first cell belonging to a first group among the different cells, wherein each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and the TPMI for each of the first cells is determined based on the precoding information and the field of the number of layers, wherein a DCI for scheduling a PUSCH in a cell is configured with a field for second precoding information and a number of layers for each of the first cells, and The bits in the field of the precoding information and the number of layers are determined based on a maximum value among the bits in the field configured with the second precoding information and the number of layers.

12. A device for a user equipment (UE), the device comprising: at least one processor; receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; as well as sending the PUSCH on the different cell based on the DCI, The DCI includes a field for precoding information and a number of layers of a first cell belonging to a first group among the different cells, wherein each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and the TPMI for each of the first cells is determined based on the precoding information and the field of the number of layers, wherein a DCI for scheduling a PUSCH in a cell is configured with a field for second precoding information and a number of layers for each of the first cells, and The bits in the field of the precoding information and the number of layers are determined based on a maximum value among the bits in the field configured with the second precoding information and the number of layers.

13. A computer-readable non-volatile storage medium, the computer-readable non-volatile storage medium comprising at least one computer program for causing at least one processor to perform operations comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; as well as sending the PUSCH on the different cell based on the DCI, The DCI includes a field for precoding information and a number of layers of a first cell belonging to a first group among the different cells, wherein each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and the TPMI for each of the first cells is determined based on the precoding information and the field of the number of layers, wherein a DCI for scheduling a PUSCH in a cell is configured with a field for second precoding information and a number of layers for each of the first cells, and The bits in the field of the precoding information and the number of layers are determined based on a maximum value among the bits in the field configured with the second precoding information and the number of layers.

14. A method for receiving a signal by a base station (BS) in a wireless communication system, the method comprising: Sending downlink control information (DCI) for scheduling the physical downlink shared channel (PUSCH) on different cells; as well as receiving the PUSCH on the different cell based on the DCI, The DCI includes a field for precoding information and a number of layers of a first cell belonging to a first group among the different cells, wherein each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and the TPMI for each of the first cells is determined based on the precoding information and the field of the number of layers, wherein a DCI for scheduling a PUSCH in a cell is configured with a field for second precoding information and a number of layers for each of the first cells, and The bits in the field of the precoding information and the number of layers are determined based on a maximum value among the bits in the field configured with the second precoding information and the number of layers.

15. A base station (BS) for transmitting a signal in a wireless communication system, the BS comprising: at least one transceiver; at least one processor; as well as At least one memory, the at least one memory being operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform specific operations, the specific operations comprising: Sending downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; and receiving the PUSCH on the different cell based on the DCI, The DCI includes a field for precoding information and a number of layers of a first cell belonging to a first group among the different cells, wherein each PUSCH of the first cell is transmitted based on a transmit precoding matrix indicator (TPMI) for each of the first cells, and the TPMI for each of the first cells is determined based on the precoding information and the field of the number of layers, wherein a DCI for scheduling a PUSCH in a cell is configured with a field for second precoding information and a number of layers for each of the first cells, and The bits in the field of the precoding information and the number of layers are determined based on a maximum value among the bits in the field configured with the second precoding information and the number of layers.