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

Abstract

A method and apparatus for monitoring a signal in a wireless communication system, disclosed in the present specification, comprise receiving DCI for scheduling PDSCHs or PUSCHs on different cells. In detail, the DCI includes one or more DCI fields for the PDSCHs or PUSCHs on the different cells.

Description

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

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

[0002] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). Examples of multiple access systems include Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA).

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

[0004] The technical problems of the present invention are not limited to the technical problems described above, and other technical problems can be inferred from the embodiments of the present invention.

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

[0006] As one aspect of the present invention, a method for transmitting a signal by a terminal (UE) in a wireless communication system is provided, comprising: receiving downlink control information (DCI) for scheduling physical uplink shared channels (PUSCHs) on different cells; and transmitting PUSCHs on the different cells based on the DCI; wherein the DCI includes a demodulation reference signal sequence initialization (DMRS) sequence initialization field including common information for the PUSCHs, and a sequence of a DMRS associated with each PUSCH of the cells is generated based on the DMRS sequence initialization field.

[0007] As one aspect of the present invention, a method for receiving a signal by a base station (BS) in a wireless communication system is provided, comprising: transmitting downlink control information (DCI) for scheduling physical uplink shared channels (PUSCHs) on different cells; and receiving PUSCHs on the different cells based on the DCI; wherein the DCI includes a demodulation reference signal sequence initialization (DMRS) sequence initialization field including common information for the PUSCHs, and a sequence of a DMRS associated with each PUSCH of the cells is generated based on the DMRS sequence initialization field.

[0008] As another aspect of the present invention, a device, a processor, and a storage medium for performing the signal receiving method are provided. In addition, as another aspect of the present invention, a device, a processor, and a storage medium for performing the signal transmitting method are provided.

[0009] The above devices may include at least a terminal, a network, and an autonomous vehicle capable of communicating with other autonomous vehicles other than the above devices.

[0010] The above-described aspects of the present invention are only some of the preferred embodiments of the present invention, and various embodiments reflecting the technical features of the present invention can be derived and understood by a person having ordinary skill in the art based on the detailed description of the present invention described below.

[0011] According to one embodiment of the present invention, when control signals and data signals are transmitted and received between communication devices, there is an advantage in that more efficient signal reception can be performed through operations differentiated from those of the prior art.

[0012] The technical effects of the present invention are not limited to the technical effects described above, and other technical effects can be inferred from the embodiments of the present invention.

[0013] Figure 1 illustrates the structure of a radio frame.

[0014] Figure 2 illustrates a resource grid of slots.

[0015] Figure 3 shows an example of physical channels being mapped within a slot.

[0016] Figures 4 to 7 are drawings for explaining a signal transmission and reception method according to an embodiment of the present invention.

[0017] Figures 8 to 11 illustrate devices according to embodiments of the present invention.

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

[0019] For clarity, the description is based on a 3GPP communication system (e.g., LTE, NR), but the technical idea of ​​the present invention is not limited thereto. LTE refers to technology after 3GPP TS 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be referred to as a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, reference may be made to matters described in standard documents published prior to the present invention. For example, reference may be made to the following documents.

[0020] 3GPP NR

[0021] - 38.211: Physical channels and modulation

[0022] - 38.212: Multiplexing and channel coding

[0023] - 38.213: Physical layer procedures for control

[0024] - 38.214: Physical layer procedures for data

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

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

[0027] Figure 1 illustrates the structure of a radio frame used in NR.

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

[0029] Table 1 illustrates that when CP is normally used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0030] [Table 1]

[0031]

[0032] Table 2 illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0033] [Table 2]

[0034]

[0035] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single user equipment (UE). Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as a TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

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

[0037] The NR frequency band is defined by two types of frequency ranges (FR) (FR1 / FR2). FR1 / FR2 can be configured as shown in Table 3 below. FR2 can also refer to millimeter wave (mmW).

[0038] [Table 3]

[0039]

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

[0041] A slot contains multiple symbols in the time domain. For example, for a normal CP, one slot contains 14 symbols, and for an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlaces (simply, interlaces) can be defined in the frequency domain. An interlace m ∈ {0, 1, ..., M-1} can be composed of (common) RBs {m, M+m, 2M+m, 3M+m, ...}. M represents the number of interlaces. A BWP (Bandwidth Part) is defined as multiple consecutive RBs (e.g., physical RBs, PRBs) in the frequency domain, and can correspond to one OFDM numerology (e.g., SCS(u), CP length, etc.). A carrier can contain up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated per terminal within a single cell / carrier. Each element in the resource grid is referred to as a Resource Element (RE), to which a single modulation symbol can be mapped.

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

[0043] 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 RS (DM-RS), Phase-tracking RS (PT-RS), and Channel-state information RS (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 RS (SRS).

[0044] In the present invention, the base station may be, for example, a gNodeB.

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

[0046] The contents discussed above can be applied in combination with the methods proposed in the present invention described below, or can be supplemented to clarify the technical features of the methods proposed in the present invention.

[0047] In addition, the methods described below can be equally applied to the NR system (licensed band) or shared spectrum described above, and the technical ideas proposed in this specification can be modified or replaced to fit the terms, expressions, structures, etc. defined in each system so that they can be implemented in the corresponding systems.

[0048] In a CA situation where multiple cells are configured, a multi-cell scheduling (multi-CC scheduling) method that schedules multiple serving cells / CCs simultaneously through a single DCI (based on the Justification as in Table 4) may be considered for the purpose of reducing the DCI overhead required for PDSCH / PUSCH scheduling. In this specification, the expression "scheduling multiple cells" may be understood as "scheduling a PDSCH or PUSCH to be transmitted in each of the multiple cells." In other words, a multi-cell DCI is a DCI for scheduling PDSCHs or PUSCHs on multiple different cells.

[0049] Table 4 is a justification for supporting DCI for this purpose, and can be understood as one of the motivations for introducing such DCI (PDCCH).

[0050] NR supports a wide range of spectrum in different frequency ranges. It is expected that there will be increasing availability of spectrum in the market for 5G Advanced possibly due to re-farming from the bands originally used for previous cellular generation networks. Especially for low frequency FR1 bands, the available spectrum blocks tend to be more fragmented and scattered with narrower bandwidth. For FR2 bands and some FR1 bands, the available spectrum can be wider such that intra-band multi-carrier operation is necessary. To meet different spectrum needs, it is important to ensure that these scattered spectrum bands or wider bandwidth spectrum can be utilized in a more spectral / power efficient and flexible manner, thus providing higher throughput and decent coverage in the network.One motivation is to increase flexibility and spectral / power efficiency on scheduling data over multiple cells including intra-band cells and inter-band cells.The current scheduling mechanism only allows scheduling of single cell PUSCH / PDSCH per a scheduling DCI. With more available scattered spectrum bands or wider bandwidth spectrum, the need of simultaneous scheduling of multiple cells is expected to be increasing. To reduce the control overhead, it is beneficial to extend from single-cell scheduling to multi-cell PUSCH / PDSCH scheduling with a single scheduling DCI. Meanwhile, trade-off between overhead saving and scheduling restriction has to be taken into account.

[0051] In this regard, discussions are underway on 'multi-carrier enhancement', which aims to specify a method for scheduling PUSCHs or PDSCHs on multiple serving cells through a single DCI.

[0052] In this specification, we propose a scheduling method that utilizes a DCI field with a modified structure compared to the conventional DCI field to more efficiently schedule PUSCHs or PDSCHs on multiple serving cells through a single DCI. More specifically, more efficient scheduling methods are proposed through modifications to DCI fields related to MIMO (multiple-input and multiple-output).

[0053] In this specification, a DCI that schedules PUSCHs (or PDSCHs) on (one or) multiple serving cells simultaneously is referred to as 'm-CC DCI or multi-cell DCI'. A DCI that has a conventional DCI format and schedules PUSCHs (or PDSCHs) on a single serving cell is referred to as 's-CC DCI or single-cell DCI'. The m-CC DCI can be distinguished from the conventional s-CC DCI by a different DCI format, RNTI, or indicator field within the DCI.

[0054] A single m-CC DCI can schedule PUSCH (or PDSCH) for different numbers / combinations of serving cells. For example, only serving cell #1 can be scheduled through m-CC DCI, serving cells #1 / 2 can be scheduled, or serving cells #1 / 2 / 3 can be scheduled. These numbers / combinations can be distinguished by specific fields in the DCI or RNTI, etc.

[0055] A case where only PUSCH (or PDSCH) on a single cell is scheduled via m-CC DCI may be referred to as an 's-CC scheduling case'. A case where PUSCH (or PDSCH) on multiple cells are scheduled may be referred to as an 'm-CC scheduling case'.

[0056] Even for a single terminal, since the channel conditions for each cell may differ, the number of (MIMO transmission) layers to be applied to each PDSCH or PUSCH may differ. However, in order to provide maximum flexibility, if all DCI fields indicating information for each cell are included in the DCI, the payload size of the m-CC DCI may increase significantly. In particular, a compact configuration of DCI fields may be essential for simultaneous scheduling of three or more cells. Therefore, configuration methods for the following fields related to MIMO operation among the fields included in the m-CC DCI (to reduce the DCI payload size) are proposed.

[0057] - 'Antenna ports' field

[0058] - 'DMRS sequence initialization' field

[0059] - Fields indicating the association between PTRS and DMRS (e.g., 'PTRS-DMRS association' field, 'Second PTRS-DMRS association' field)

[0060] Multiple CCs that are simultaneously scheduled through m-CC DCI (or multiple CCs that can be scheduled through the m-CC DCI) are defined as co-scheduled CCs. The co-scheduled CCs (CCs belonging thereto) can be grouped into one or more subgroups. In addition, a separate field can be configured for each subgroup. Which CCs belong to each subgroup can be set in advance by higher layer signaling. Each field (the value indicated by it) can be commonly applied to the CC(s) belonging to the subgroup. The subgroup can be referred to as a shared CC group. When the CCs belonging to the shared CC group have different attributes, we propose a method for commonly applying the DCI field to the CCs.

[0061] Table 5 shows how each field constituting the m-CC DCI (i.e., DCI format 0_X / 1_X) is classified into three types. DCI format 0_X is a DCI format for scheduling PUSCHs on multiple cells, and DCI format 1_X is a DCI format for scheduling PDSCHs on multiple cells. Type-1 is classified into three sub-types.

[0062] For discussing field design of DCI format 0_X / 1_X which schedules more than one cell, reformulate the types of DCI fields as below:- Type-1 field:-- Type-1A field: A single field indicating common information to all the co-scheduled cells-- Type-1B field: A single field indicating separate information to each of co-scheduled cells via joint indication-- Type-1C field: A single field indicating an information to only one of co-scheduled cells- Type-2 field: Separate field for each of the co-scheduled cells- Type-3 field: Common or separate to each of the co-scheduled cells, or separate to each sub-group, dependent on explicit configuration.Note: One sub-group comprises a subset of co-scheduled cells where a single field is commonly applied to the co-scheduled cell(s) belonging to a same sub-group.

[0063] 표 5의 각 타입들과 대응하여, 본 명세서에 기재된 용어들은 방법 1 내지 4와 같다.

[0064] 방법 1: 공유-셀-공통(shared-cell-common)

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

[0066] Method 2: Shared-State-Extension

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

[0068] Method 3: Separate

[0069] A method in which a number of fields (within the DCI) equal to the number of cells scheduled through a multi-cell DCI (with actions set according to the corresponding DCI field instructions) are configured, and an individual field corresponds to each scheduled cell, and the value indicated by the corresponding field is applied to the corresponding cell.

[0070] Method 4: Shared-reference-cell

[0071] A method in which only one field is configured within the multi-cell DCI, and the value indicated by the DCI field is applied only to a specific reference cell (e.g., the cell to which the DCI was transmitted, the cell with the lowest or highest cell index, or the cell indicated by the CIF field value) among the cells scheduled through the multi-cell DCI and set to operate according to the DCI field indication, and a specific default value defined / set in advance is applied to the remaining cells.

[0072] Basically, a field to which the shared-cell common method is applied may correspond to a Type-1A field. A field to which the shared-state-extension method is applied may correspond to a Type-1B field. A field to which the shared-reference-cell method is applied may correspond to a Type-1C field. A field to which the separation method is applied may correspond to a Type-2 field. A field to which either Methods 1 to 4 are applied may be explicitly configured to correspond to a Type-3 field.

[0073] The multi-cell scheduling described herein for PDSCH can be equally applied to multi-cell scheduling for PUSCH. Furthermore, the multi-cell scheduling operation described herein for PUSCH can also be equally applied to multi-cell scheduling for PDSCH. Furthermore, the term "cell" in this specification may be interpreted as the (active) BWP configured / instructed for the corresponding cell.

[0074] Meanwhile, a reference cell may mean (i) a cell with the lowest (or highest) cell index within a set of cells (i.e., co-scheduled cell set) simultaneously scheduled through the same multi-cell DCI (or within each cell subgroup described below), or (ii) a cell with the earliest (or latest) indicated PDSCH / PUSCH transmission starting symbol time, or (iii) a cell with the earliest (or latest) indicated PDSCH / PUSCH transmission ending symbol time, or (iv) a cell indicated by a CIF field value, or (v) a cell designated in advance via RRC.

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

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

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

[0078] Alternatively, in the case of fields to which the shared-reference-cell method, the shared-cell-common method, and / or the shared-state-extension method are applied, all cells belonging to the co-scheduled cell combination may be grouped into one or more (or multiple) sub-groups, and one (commonly applied) field may be configured for each sub-group. Accordingly, individual / independent fields may be configured between each sub-group. Through this, the shared-reference-cell method, the shared-cell-common method, and / or the shared-state-extension method and the field / information configuration / instruction method based thereon may be applied to each sub-group.

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

[0080] A subgroup may also be referred to as a cell subgroup. A cell subgroup may be composed / configured of one or more specific cells belonging to the co-scheduled cell combination or the schedulable cell combination. For example, a cell subgroup may be composed / configured of some or all of the cells belonging to the co-scheduled cell combination or the schedulable cell combination.

[0081] In the conventional case, the DCI field to which the shared-cell common method is applied may have a structure in which a table consisting of one or more states for each cell is set in advance with RRC or MAC-CE, and one of the states in the table is indicated through the DCI field. The conventional case refers to single-cell DCI-based scheduling. One or more states may be composed of different parameters / values ​​or a combination thereof, and may correspond to the row index of each table. Therefore, 'state' may be replaced with 'index'. 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 may operate based on one or more of the following three options. In the options below, the cell set may refer to a schedulable cell combination, a co-scheduled cell combination, or a cell subgroup.

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

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

[0084] Opt Z) A specific state indicated through a DCI field that is commonly configured for a set of cells to which the shared-cell-common method is applied can be commonly applied to cells belonging to the set of cells by being interpreted as a parameter / value or a combination thereof corresponding to the state in the common table, when a separate common table to be commonly applied to the set of cells is set in advance with RRC / MAC-CE.

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

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

[0087] First, in the existing s-CC DCI-based scheduling, for a specific DCI field (such as Antenna ports), N parameters / values ​​or a combination thereof are set in advance by RRC or MAC-CE for each of N states that can be indicated by the DCI field, and when one of the N states is indicated through the DCI field, the terminal performs PDSCH / PUSCH transmission / reception operations by applying the parameters / values ​​or a combination thereof set 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 set to a different (or the same) value for each cell.

[0088] Meanwhile, in the case of the specific DCI field in m-CC DCI-based scheduling, when parameters / values ​​or a combination thereof are set in advance for each state (applicable to s-CC DCI-based scheduling) for each cell as above, and a specific state is indicated through the DCI field, the terminal can perform transmission / reception operations for the PDSCH / PUSCH scheduled for each cell by interpreting / applying the parameters / values ​​or a combination thereof set for each cell for the indicated state, respectively.

[0089] Meanwhile, in m-CC DCI-based scheduling, the size of the specific DCI field can be determined in one of the following three ways, using N_max, which is the maximum value, and N_min, which is the minimum value, among the N values ​​set for each cell belonging to the set of all schedulable cells (or each co-scheduled cell set).

[0090] Alt-A) Determined by ceil {log2(N_max)} bits based on the maximum value N_max (in this case, it can be a structure that indicates up to (the first) N_max states / indexes through the corresponding DCI field)

[0091] Alt-B) Determined by ceil {log2(N_min)} bits based on the minimum value N_min (in this case, it may be a structure that indicates only up to (the first) N_min states / indexes through the corresponding DCI field)

[0092] When applying the above Alt-A method, if a specific state (e.g., a state higher than {N_low - 1}) is indicated through a specific DCI field for a specific cell (e.g., a cell where N is set to N_low, which is a value less than N_max), the parameters / values ​​or combinations thereof set for the corresponding state may not exist for cell X. Considering this case, the following operation is proposed. For convenience, we define M = ceil {log2(N_max)} and K = ceil {log2(N_low)} (M ≥ K). Specifically, for the Antenna ports field, the state corresponding to the Reserved value may or may not be included in N_max / N_low. In addition, in the description below, the values ​​of the DCI fields corresponding to N states / indexes are assumed to be 0, ..., N-1.

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

[0094] A. On the other hand, if a state / index with a value higher than {N_low - 1} is indicated through the above K bits, the operation of Alt 3 or Alt 6 can be applied.

[0095] B. For example, for the Antenna ports field, if M=5 and the K assigned to cell X is K=4, the SRI field can be interpreted using only the first or last 4 bits out of 5 bits.

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

[0097] A. The above specific parameter / value or combination thereof may be set / defined as a specific parameter / value or combination thereof linked to a specific one (e.g. lowest or highest) value among the N_low states preset for the corresponding cell X.

[0098] B. For example, for the Antenna ports field, the above specific specific parameter / value or combination thereof may be set / defined as a specific one of the N_low states preset for the corresponding cell X (e.g. lowest or highest state / index not linked to the Reserved value).

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

[0100] A. Accordingly, the terminal can omit PDSCH / PUSCH transmission / reception operations on the corresponding cell X (in the case of PDSCH, the corresponding HARQ-ACK is fed back as NACK).

[0101] B. For example, if a state higher than {N_low - 1} is indicated for the Antenna ports field, the terminal may consider that there is no PDSCH / PUSCH scheduling for the cell X, and may omit the PDSCH / PUSCH transmission / reception operation on the cell X (in the case of PDSCH, the corresponding HARQ-ACK may be fed back as NACK).

[0102] 4) Alt 4: For the above cell X, additionally set {N_max - N_low} = N_gap parameters / values ​​or a combination thereof corresponding to each state from state N_low to N_max - 1 and apply.

[0103] A. The above additional parameters / values ​​or combinations thereof may be set as additional parameters / values ​​or combinations thereof linked to specific N_gap states among the N_low states preset for the corresponding cell X.

[0104] B. For example, for the Antenna ports field, it can be set to a parameter / value associated with a specific N_gap state among the N_low states (excluding the state / index corresponding to the Reserved value) or a combination thereof.

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

[0106] A. For example, 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 state {0,1,2,3,4,0,1,2} for the cell X, respectively.

[0107] B. For example, for the Antenna ports field, 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} for the cell X, respectively.

[0108] 6) Alt 6: If a state higher than {N_low - 1} is indicated through the DCI field above, the most recently indicated state is applied / maintained for the cell X.

[0109] A. Accordingly, the terminal can perform PDSCH / PUSCH transmission / reception operations on the cell X by applying / maintaining the recently instructed state to the cell X.

[0110] B. For example, in the case of the Antenna ports field, the terminal can perform PDSCH / PUSCH transmission / reception operations on the corresponding cell X by applying / maintaining the recently indicated state (via the corresponding field in the same DCI format or a different DCI format) to the corresponding cell X.

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

[0112] Additionally, the following is a specific proposal for a method of determining the DCI field size for the above type-2 field or field to which the separation method is applied.

[0113] In the existing s-CC DCI, for a specific DCI field, the size of the DCI field can be set to L = ceil {log2(N)} bits, while N states can be indicated through the DCI field. L can be set to a different (or the same) value for each cell. The specific DCI field can include an Antenna ports field, a PTRS-DMRS association field, etc.

[0114] Meanwhile, when the specific DCI field in the 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 set in the entire schedulable cell combination, the sum L_sum of the L values ​​set for each cell belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values ​​calculated for each of the N_co co-scheduled cell combinations can be determined as the size of the specific DCI field (configured in the m-CC DCI).

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

[0116] For example, in the case of the PTRS-DMRS association field, for each of multiple (e.g., N_co) co-scheduled cell combinations (in particular, cells configured with CB-based UL) set in the entire fully schedulable cell combination, the sum L_sum of the L values ​​(for the PTRS-DMRS association field) set in each of the cells (in particular, cells configured with CB-based UL) belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values ​​calculated for each of the N_co co-scheduled cell combinations can be determined as the size of the corresponding PTRS-DMRS association field (configured in the m-CC DCI).

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

[0118] Meanwhile, for a specific DCI field (such as Antenna ports, PTRS-DMRS association field, etc.) to which the Type-2 field design method is applied, N_cfg states and the corresponding field size L_cfg = ceil {log2(N_cfg)} that can be indicated through the corresponding DCI field in the m-CC DCI can be separately set. In this case, they can be set in the form of N_cfg < N and / or L_cfg < L. The Type-2 field design method can include the DCI field size determination method and / or the shared-cell common method based on the Opt X method for this purpose. The N_cfg states and the corresponding field size L_cfg can be set for each cell.

[0119] Specifically, for a specific DCI field within the m-CC DCI as described above, if N_cfg states and field size L_cfg are separately set for a specific cell, the Type-2 field design method below is applied to the cell based on the number / set of states and field size. If there is no separate setting, the Type-2 field design method below can be applied based on the N states and field size L set in the s-CC DCI.

[0120] For example, for the Antenna ports field, the number of DM-RS symbols for m-CC DCI purposes, the maximum number of ranks / layers, or the valid / invalid row index(es) among the rows of the table corresponding to the cell may be defined / set / indicated for a specific cell X. When configuring the Antenna ports field in the m-CC DCI and / or scheduling multiple CCs through the m-CC DCI, N_cfg states and field size L_cfg may be determined for the cell based on the given number of DM-RS symbols, the maximum number of ranks / layers, or the valid / invalid row index(es) among the rows of the table corresponding to the cell. When configuring the Antenna ports field in m-CC DCI and / or scheduling multiple CCs through m-CC DCI, for a cell for which the number of DM-RS symbols, the maximum number of ranks / layers, or valid / invalid row index(es) among the rows of the table corresponding to the cell are not defined / set / indicated, the Antenna ports field in m-CC DCI for the cell can be configured based on the N states and field size L set in the s-CC DCI.

[0121] [1] 'Antenna port' field

[0122] Table 6 shows the Antenna ports fields for each DCI format disclosed in the 3GPP TS 38.212 document.

[0123] For DCI format 0_1,- Antenna ports - number of bits determined by the following- 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled,dmrs-Type=1, andmaxLength=1, except thatdmrs-UplinkTransformPrecodingandtp-pi2BPSKare both configured and ð / 2 BPSK modulation is used;- 2 bits as defined by Tables 7.3.1.1.2-6A, if transform precoder is enabled anddmrs-UplinkTransformPrecodingandtp-pi2BPSKare both configured, ð / 2 BPSK modulation is used,dmrs-Type=1, andmaxLength=1, where n SCIDis the scrambling identity for antenna ports defined in [Clause 6.4.1.1.1.2, TS38.211];- 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled,dmrs-Type=1, andmaxLength=2, except thatdmrs-UplinkTransformPrecodingandtp-pi2BPSKare both configured and ð / 2 BPSK modulation is used;- 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled anddmrs-UplinkTransformPrecodingandtp-pi2BPSKare both configured, ð / 2 BPSK modulation is used,dmrs-Type=1, andmaxLength=2, where n SCIDis the scrambling identity for antenna ports defined in [Clause 6.4.1.1.1.2, TS38.211];- 3 bits as defined by Tables 7.3.1.1.2-8 / 9 / 10 / 11, if transform precoder is disabled,dmrs-Type=1, andmaxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parametertxConfig = nonCodebookand according to the Precoding information and number of layers field if the higher layer parametertxConfig = codebook;- 4 bits as defined by Tables 7.3.1.1.2-12 / 13 / 14 / 15, if transform precoder is disabled,dmrs-Type=1, andmaxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parametertxConfig = nonCodebookand according to the Precoding information and number of layers field if the higher layer parametertxConfig = codebook;- 4 bits as defined by Tables 7.3.1.1.2-16 / 17 / 18 / 19, if transform precoder is disabled,dmrs-Type=2, andmaxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parametertxConfig = nonCodebookand according to the Precoding information and number of layers field if the higher layer parametertxConfig = codebook;- 5 bits as defined by Tables 7.3.1.1.2-20 / 21 / 22 / 23, if transform precoder is disabled,dmrs-Type=2, andmaxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parametertxConfig = nonCodebookand according to the Precoding information and number of layers field if the higher layer parametertxConfig = codebook.where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively.If a UE is configured with bothdmrs-UplinkForPUSCH-MappingTypeAanddmrs-UplinkForPUSCH-MappingTypeB, the bitwidth of this field equals max {x. A , x B } where x A ,is the "Antenna ports" bitwidth derived according todmrs-UplinkForPUSCH-MappingTypeAand x B is the "Antenna ports" bitwidthderived according todmrs-UplinkForPUSCH-MappingTypeB. A number of zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of x A and x B For DCI format 1_1,- Antenna port(s) - 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1 / 2 / 3 / 4 and Tables 7.3.1.2.2-1A / 2A / 3A / 4A, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports {p0, ...p v-1 } shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1 / 2 / 3 / 4 or Tables 7.3.1.2.2-1A / 2A / 3A / 4A. When a UE receives an activation command that maps at least one codepoint of DCI field 'Transmission Configuration Indication' to two TCI states, the UE shall use Table 7.3.1.2.2-1A / 2A / 3A / 4A; otherwise, it shall use Tables 7.3.1.2.2-1 / 2 / 3 / 4. The UE can receive an entry with DMRS ports equals to 1000, 1002, 1003 when two TCI states are indicated in a codepoint of DCI field 'Transmission Configuration Indication'.If a UE is configured with bothdmrs-DownlinkForPDSCH-MappingTypeAanddmrs-DownlinkForPDSCH-MappingTypeB, the bitwidth of this field equals max {x A , x B } where x A ,is the "Antenna ports" bitwidth derived according todmrs-UplinkForPUSCH-MappingTypeAand x B is the "Antenna ports" bitwidthderived according todmrs-UplinkForPUSCH-MappingTypeB. A number of zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of x A and x B

[0124] For the number of ranks / layers determined through the above SRI and / or Precoding information and number of layers fields, the corresponding DM-RS port index for each layer can be determined through the corresponding fields.

[0125] As one way to reduce the field size, the number of DM-RS symbols can be set / applied differently depending on the number of cells (simultaneously) scheduled by the m-CC DCI. For example, in the s-CC scheduling case, even if the maxLength value follows a value predefined / set for each cell, the m-CC scheduling case can be constrained to schedule only single-symbol DM-RS. Alternatively, the scheduling case based on the m-CC DCI can be constrained to always schedule only single-symbol DM-RS. Alternatively, the maxLength value can be configured to always be set to 1 for cells designated as m-CC DCI scheduling targets. In this case, the number of fields equal to the number of cells scheduled through the m-CC DCI (those for which actions are set according to the corresponding DCI field instructions) is configured within the DCI. Additionally, the Antenna ports field can be configured such that each scheduled cell is assigned a separate field and the value indicated by the field is applied to the corresponding cell. This field configuration method is referred to as the "Type-2 field design method."

[0126] Restricting the number of DM-RS symbols per cell may have the disadvantage of reducing CDM capacity. Considering this, a separate table and corresponding individual fields for each cell are configured, and the DM-RS port index for each layer can be indicated for each cell through the individual fields. A method can be considered to reduce the total number of bits required to indicate the DM-RS port index for each layer by adjusting the number of rows in the table for each cell.

[0127] For example, if certain conditions (if transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=1) are satisfied as shown in Table 7 below, signaling for 28 combinations is required. However, if the corresponding cell is scheduled via m-CC DCI, the table can be configured with only some of the 28 rows corresponding to the 28 combinations. This reduces the number of bits required to configure / indicate the 'Antenna ports' field / information for the corresponding cell. For example, if only 8 rows out of 27 are selected, only 3 bits instead of 5 bits are required to indicate the DM-RS port index per layer for the corresponding cell.

[0128] At this time, for each cell, which row indices among the rows of the existing table are selected to reduce the table size and bit count can be separately set or defined in advance. For example, only even indices among the row indices can be selected, only indices corresponding to a multiple of a specific N value can be selected, only a specific number of the lowest indices can be selected, or only a specific number of the highest indices can be selected. Specifically, for a specific cell, a 0 bit can be set to be allocated to indicate a DM-RS port index per layer. In this case, a specific DM-RS port index can be applied to the cell. For example, a rule can be set in advance so that the DM-RS port index is applied as 0 for the cell, or the DM-RS port index to be used can be set in advance.

[0129] Meanwhile, the above method may be applied differently (the size of the table may be different) depending on which cells are actually scheduled, and may be applied only to the m-CC scheduling case and not to the s-CC scheduling case. For example, in the s-CC scheduling case, if a cell to which Table 7 below applies is scheduled, a 5-bit Antenna ports field may be allocated to the cell. At this time, the same number of fields as the number of cells scheduled through the m-CC DCI (for which an operation is set according to the corresponding DCI field instruction) are configured within the corresponding DCI. In addition, the Antenna ports field may be configured in such a way that an individual field corresponds to each scheduled cell and the value indicated by the corresponding field is applied to the corresponding cell, and this field configuration method is referred to as a "Type-2 field design method."

[0130] ValueNumber of DMRS CDM group(s) without dataDMRS port(s)Number of front-load symbols01011111220132114221523163017311832193311034111351123021331214322153321634217352183621937220382213922231022331122410225112261622717228-31ReservedReservedReserved

[0131] Alternatively, the maximum number of ranks / layers can be set / applied differently depending on the number of cells that m-CC DCI schedules (simultaneously). For example, in the s-CC scheduling case, even if the maxRank value follows a predefined / configured value for each cell, the maxRank value can be constrained to K in the m-CC scheduling case. Alternatively, in the scheduling case based on m-CC DCI, the maxRank value can always be constrained to K. Alternatively, a configuration constraint can be applied so that the maxRank value is always set to K for cells that are scheduled as m-CC DCI scheduling targets. The K value can be set or predefined. For example, K=1. In the case of PDSCH, the constraint on the maxRank value can be applied only when only 1-TB is scheduled. The constraint on the rank value may not be applied for cells scheduled with 2-TB. This is because, as shown in Table 8 below, in the case of 2-TB (i.e., when both codewords are enabled), there are only 4 corresponding row indices, so in the case of 1-TB, even if the corresponding row indices become more than 4 due to the rank count constraint, the number of bits of the corresponding Antenna ports field may not change. At this time, the number of fields equal to the number of cells scheduled through m-CC DCI (for which an operation is set according to the corresponding DCI field instruction) is configured within the corresponding DCI. In addition, the Antenna ports field can be configured in such a way that an individual field corresponds to each scheduled cell, and the value indicated by the corresponding field is applied to the corresponding cell. This field configuration method is referred to as the "Type-2 field design method."

[0132] One Codeword:Codeword 0 enabled,Codeword 1 disabledTwo Codewords:Codeword 0 enabled,Codeword 1 enabledValueNumber of DMRS CDM group(s) without dataDMRS port(s)Number of front-load symbolsValueNumber of DMRS CDM group(s) without dataDMRS port(s)Number of front-load symbols0101020-421111120,1,2,3,4,62210,11220,1,2,3,4,5,623201320,1,2,3,4,5,6, 7242114-31reservedreservedreserved52216231720,11822,31920-211020-311120,211220 2132121422215232162421725218262192722020,122122,322224,522326,722420,422522,6 22620,1,422722,3,622820,1,4,522922,3,6,723020,2,4,6231ReservedReservedReserved

[0133] The m-CC DCI configuration method for the 'antenna ports' field proposed in the present invention can be applied to mapping type A and mapping type B, respectively, when different mapping types (i.e., PDSCH / PUSCH mapping type A and B) are set for scheduled cells and at least one parameter of dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is set differently for each mapping type. When the payload size corresponding to mapping type A is X_A and the payload size corresponding to mapping type B is X_B, the payload size of the final 'antenna ports' field can be |X_A-X_B| or (X_A+X_B).

[0134] Options 1-1 to 2-2C describe how to apply the 'Antenna ports' field when different CCs referencing different tables are grouped into a shared CC group.

[0135] First, a configuration constraint can be applied so that only CCs of the same type belong to a shared CC group. That is, a common table is referenced when interpreting the 'Antenna ports' field for all CCs belonging to the shared CC group. In this case, CCs of the same type mean that the transform precoding configuration and / or the configuration for the dmrs-Type parameter and / or the configuration for the tp-pi2BPSK parameter and / or the configuration for the maxLength parameter (or at least one of these configurations) are the same. Which configurations must be the same may differ depending on the case of PDSCH and PUSCH. In the case of PUSCH, a constraint is added so that CCs grouped into a shared CC group have the same transmission rank value, so that the table referenced when interpreting the 'Antenna ports' field can be commonly aligned. In the case of PDSCH, even if the settings for the dmrs-Type parameter and the maxLength parameter are the same, the tables set to be referenced by each CC may be different depending on whether SDM (spatial domain multiplexing) reception from multi-TRP is set.

[0136] (Opt 1-1) Specifically, the multi-TRP DL reception setting can be restricted to only cells belonging to the shared CC group.

[0137] (Opt 1-2) Alternatively, CCs with different settings for multi-TRP DL reception may be allowed to belong to a single shared CC group. In Opt 1-2, when the table referenced by a cell with multi-TRP DL reception operation set is Table X (e.g., Table 7.3.1.2.2-1A of TS 38.212 specification) and the table referenced by a cell without multi-TRP DL reception operation set is Table Y (e.g., Table 7.3.1.2.2-1 of TS 38.212 specification), a rule may be established in the m-CC scheduling case to commonly reference Table X or Table Y for the shared CC group. At this time, if there is a different code point between Table X or Table Y, and if the specific code point is indicated, the cell without multi-TRP DL reception operation is regarded as having no PDSCH scheduling or performing PDSCH reception as if the pre-configured / defined antenna port(s) are indicated. Alternatively, in Opt 1-2, a rule may be defined to refer only to Table Y (not only for cells where multi-TRP DL reception operation is not configured, but also for cells where multi-TRP DL reception operation is configured), so that cells where multi-TRP DL reception operation is configured may only allow single-TRP transmission when scheduling with m-CC DCI (or when multiple cells are scheduled simultaneously via m-CC DCI).

[0138] (Opt 2-1) Alternatively, CCs of different types (i.e. not of the same type as above) may be allowed to belong to a shared CC group. In this case, the 'Antenna ports' field configuration in the m-CC DCI is omitted (i.e. the field does not exist) and the number of code points required / applied to each CC in the group (in the 'Antenna ports' table) is limited to 1. The code point may be preset or indicated via MAC.

[0139] (Opt 2-2) The corresponding fields and / or corresponding tables are configured according to a specific CC of a specific type belonging to the above shared CC group (such as parameters set for single-cell scheduling of the CC and number of code points). A default code point may be applied to CC(s) of a different type from the corresponding type. The default code point may be preset or indicated via MAC.

[0140] (Opt 2-2A) For Opt 2-2, the number of code points that can be indicated by the 'Antenna ports' field, which are required for the above specific type of CCs, is set to be the same. For example, the 'Antenna ports' field can be configured based on the minimum number of code points set for single cell scheduling for each CC. In this case, for a CC that has more code points set than the minimum value (e.g. N), only the code points corresponding to the lowest or highest N indices can be indicated.

[0141] (Opt 2-2B) The 'Antenna ports' field may be configured based on the maximum number of code points set for single-cell scheduling for each CC. If the code point indicated by this field is not valid for a particular CC, scheduling is considered non-existent for that CC.

[0142] (Opt 2-2C) The 'Antenna ports' field is configured in the same manner as Opt 2-2B above, but if the indicated code point is not valid for a specific CC, the terminal may operate to assume / apply a specific code point defined / set in advance for that CC.

[0143] [2] ‘DMRS sequence initialization’ field

[0144] If PUSCH is scheduled by s-CC DCI and CP-OFDM is applied (i.e., if transform precoder is disabled), 1 bit is assigned to this field. Or, if PUSCH is scheduled by s-CC DCI and DFT-s-OFDM is applied (i.e., if transform precoder is enabled), 0 bit is assigned to this field. On the other hand, if PDSCH is scheduled by s-CC DCI, 1 bit is always assigned to this field.

[0145] The DMRS sequence initialization field is a Type-1A field, and 1 bit is commonly allocated to cells that are (simultaneously) scheduled through m-CC DCI. In the case of PUSCH, 1 bit can be commonly allocated to cell(s) to which CP-OFDM is applied among the cells. That is, the value of '0' or '1' indicated for all scheduled cells (all cells to which CP-OFDM is applied in the case of PUSCH) can be applied.

[0146] For PUSCH, if DFT-s-OFDM is applied to all cells that can be scheduled via m-CC DCI, 0 bits may be allocated to this field. On the other hand, if CP-OFDM is applied to some of the cells that can be scheduled via m-CC DCI and DFT-s-OFDM is applied to the rest, 1 bit may be allocated to this field. If DFT-s-OFDM is applied to all of the actually scheduled cells, this field may not exist. Alternatively, if DFT-s-OFDM is applied to all of the actually scheduled cells, 1 bit may be allocated to this field, but this bit may be regarded as a reserved bit. Alternatively, a configuration restriction may be imposed that DFT-s-OFDM is applied to all cells for which m-CC DCI is configured.

[0147] When M cells (in case of PUSCH, this may mean M cells to which CP-OFDM is applied) can be scheduled, less than K ( <M) 비트로 해당 필드가 구성되면, M 개 셀들의 DM-RS sequence initialization 조합 방법 2^K 개(혹은 2^K 개 이하)가 사전에 설정되고, m-CC DCI 를 통해 그 중 하나의 조합이 지시될 수 있다. 일 예로, PDSCH 의 경우 M=4 이고 K=2 일 때, '00' / '01' / '10' / '11' 각 경우에 대해 4 개 셀들의 DM-RS sequence initialization 방법이 사전에 설정된다. m-CC DCI가 '00'을 지시하면, 해당 코드포인트에 대응되는 DM-RS sequence initialization 방법이 M 개 셀 각각에 대해 적용될 수 있다.

[0148] Alternatively, the field may not exist for m-CC DCI. In this case, a predefined / configured DM-RS sequence initialization method may be applied to each scheduled cell(s). This method (not configuring / indicating fields / information within m-CC DCI) may only be applied to the m-CC scheduling case. For the s-CC scheduling case (or when CP-OFDM is applied to a single scheduled cell), a 1-bit field / information may be configured / indicated in the DMRS sequence initialization field.

[0149] Alternatively, with only one field configured within the m-CC DCI, DM-RS sequence initialization information can be indicated (via that field) only for a specific reference cell among the cells scheduled through that DCI. For the remaining cells that are not reference cells, a predefined / configured DM-RS sequence initialization method can be applied.

[0150] Options 3-1 to 3-3 disclose how to apply the 'DMRS sequence initialization' field when a CC with the 'DMRS sequence initialization' field set and a CC(s) without the 'DMRS sequence initialization' field are grouped into a shared CC group.

[0151] (Opt 3-1) When a CC with the 'DMRS sequence initialization' field set and a CC without the 'DMRS sequence initialization' field are grouped into a shared CC group, the 'DMRS sequence initialization' field is omitted in the m-CC DCI (for the shared CC group) and n_SCID = 0 is always assumed / applied.

[0152] (Opt 3-2) If the 'DMRS sequence initialization' field is configured in the m-CC DCI and n_SCID = 1 is indicated, no scheduling is considered for CCs for which the 'DMRS sequence initialization' field is not configured.

[0153] (Opt 3-3) For CCs where the 'DMRS sequence initialization' field is configured in the m-CC DCI and the 'DMRS sequence initialization' field is not set, n_SCID = 0 may always be applied (even if n_SCID = 1 is indicated through that field).

[0154] In the case of DCI for PUSCH scheduling, which waveform among CP-OFDM or DFT-s-OFDM is to be applied to the corresponding PUSCH can be dynamically indicated. For example, one of the two waveforms can be indicated by introducing a separate 1-bit indicator. One of the two waveforms can also be indicated by utilizing some bits or some code points of an existing field. If the 1-bit indicator is introduced in the m-CC DCI, the indication for the dynamic waveform switching (DWS) can be commonly applied to all co-scheduled CCs (or CC(s) among co-scheduled CCs for which DWS is set). Alternatively, the indication for the dynamic waveform switching can be applied only to a specific reference cell, and a specific waveform can be applied to cells other than the reference cell by a predefined / set method. The reference cell can be the cell with the lowest index, the cell with the highest index, the cell with the lowest SCS set, the cell with the highest SCS set, or the scheduling cell where m-CC DCI is transmitted. In the case of m-CC DCI, the corresponding DWS indication field is omitted, and a specific waveform for each cell may be applied in a predefined / set manner. In this way, when the DWS indication can be applied to only all or some of the co-scheduled CCs, the corresponding 'DMRS sequence initialization' field is interpreted only for the cells where CP-OFDM is indicated / applied, and the corresponding 'DMRS sequence initialization' field may be ignored for other cells.

[0155] [3] Fields indicating the association between PTRS and DMRS

[0156] Table 9 shows the fields that indicate the association between PTRS and DMRS as disclosed in the 3GPP TS 38.212 document.

[0157] - PTRS-DMRS association - number of bits determined as follows- 0 bit ifPTRS-UplinkConfig is not configured in eitherdmrs-UplinkForPUSCH-MappingTypeAordmrs-UplinkForPUSCH-MappingTypeBand transform precoder is disabled, or if transform precoder is enabled, or ifmaxRank=1;- 2 bits otherwise, where Table 7.3.1.1.2-25 / 7.3.1.1.2-25A and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured bymaxNrofPortsinPTRS-UplinkConfigrespectively, and the DMRS ports are indicated by the Antenna ports field. When the SRS resource set indicator field is present andmaxRank>2, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and / or Precoding information and number of layers field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26.When the SRS resource set indicator field is present and equals "10" and "11" andmaxRank=2, the MSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator and / or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and / or Second Precoding information field, according to Table 7.3.1.1.2-25A.If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part.- Second PTRS-DMRS association - 2 bits if PTRS-DMRS association field and SRS resource set indicator field are present andmaxRank>2; 0 bit otherwise. Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and / or Second precoding information field when one PT-RS port and two PT-RS ports are configured bymaxNrofPortsinPTRS-UplinkConfigrespectively, and the DMRS ports are indicated by the Antenna ports field.

[0158] <'PTRS-DMRS association' field>

[0159] If the condition that 0 bits are allocated to the corresponding field for all cells that can be scheduled (simultaneously) via m-CC DCI (if PTRS-UplinkConfig is not configured in either dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and transform precoder is disabled, or if transform precoder is enabled, or if maxRank=1) (let's call this condition Condition #A for convenience) is satisfied, 0 bits may be allocated to the corresponding field. On the other hand, if some of the cells that can be scheduled via m-CC DCI satisfy Condition #A and the rest do not satisfy Condition #A, 2 bits (or 1 bit in combination with the method below) may be allocated to the corresponding field. If the cells that are actually scheduled satisfy Condition #A, the corresponding field may not exist. Alternatively, if the actual scheduled cells satisfy condition #A, 2 bits (or 1 bit in combination with the method below) may be allocated to the field, but the 2 bits may be considered reserved bits. Alternatively, a constraint may be imposed on the configuration such that all cells with m-CC DCI configured are configured to satisfy condition #A. Alternatively, the s-CC scheduling case may not impose a constraint on whether condition #A is satisfied, but may impose a constraint (e.g., maxRank=1) on cells scheduled only in the m-CC scheduling case to satisfy condition #A.

[0160] Alternatively, in the case of scheduling with m-CC DCI, the field size can be reduced by reducing the number of candidates for DM-RS port indices that can be linked to PT-RS compared to the existing s-CC DCI. For example, as shown in Table 10 below, PT-RS port 0 could be indicated by the field to be linked to one of the four DM-RS ports. However, in m-CC DCI (or in the case of m-CC scheduling case), PT-RS port 0 can be linked to one of the two specific DM-RS ports (e.g., 1 st scheduled DMRS port or 2 nd scheduled DMRS port) may be indicated by the field. In this case, for each cell scheduled through the same m-CC DCI, only 1 bit instead of 2 bits may be required for the 'PTRS-DMRS association' field for the corresponding cell. Alternatively, to further reduce the number of bits in the field, in the case of being scheduled through m-CC DCI (or in the case of m-CC scheduling case), which DM-RS port is associated with which PT-RS port may be preset or defined, and the 'PTRS-DMRS association' field for the corresponding cell may not be allocated.

[0161] In the case of scheduling with m-CC DCI (or in the case of m-CC scheduling case), the number of bits of the 'PTRS-DMRS association' field corresponding to each cell can be set to be the same by commonly applying one of the above methods to cells scheduled through the same m-CC DCI. Alternatively, the number of bits of the 'PTRS-DMRS association' field can be different for each cell by applying a different method for each cell among the above methods to cells scheduled through the same m-CC DCI. For example, in the m-CC scheduling case, 2 bits may be allocated to the field for a specific reference cell as before, and 0 bits may be allocated to the field for other scheduled cell(s). A reference cell may be defined and / or set as a cell with the lowest cell index, a cell with the highest cell index, a cell with the lowest SCS set, a cell with the highest SCS set, a scheduling cell where m-CC DCI is transmitted, a cell with the minimum number of SRS resources in an SRS resource set, or a cell with the maximum number of resources in an SRS resource set. For a cell with 0 bits allocated to the field, a constraint may be set in advance that which DM-RS port is associated with the PT-RS port, or that condition #A is satisfied. As another example, in the s-CC scheduling case, 2 bits are allocated to the field as before, and in the m-CC scheduling case, the proposed methods (including the 0 bit allocation method) may be applied commonly or differently to multiple cells.

[0162] ValueDMRS port01 st scheduled DMRS port12 nd scheduled DMRS port23 rd scheduled DMRS port34 th scheduled DMRS port

[0163] Options 4-1 to 4-3 disclose how to apply the 'PTRS-DMRS association' field when a CC with the 'PTRS-DMRS association' field set and a CC(s) without the 'PTRS-DMRS association' field are grouped into a shared CC group.

[0164] (Opt 4-1) When a CC with the 'PTRS-DMRS association' field set and a CC without it are grouped into a shared CC group, the 'PTRS-DMRS association' field is omitted in the m-CC DCI (for the shared CC group) and a specific default DMRS port (index) is always assumed / applied. The default DMRS port is, for example, '0 or 1'. st It may be a 'scheduled DMRS port'.

[0165] (Opt 4-2) If the 'PTRS-DMRS association' field is configured in the m-CC DCI and a 0 state (or only bit '0') is indicated through the field, the specific default DMRS port is assumed / applied for the CC for which the 'PTRS-DMRS association' field is not configured. If a non-0 state (or at least one bit '1') is indicated, it is considered that there is no scheduling for the non-configured CC.

[0166] (Opt 4-3) For CCs where the 'PTRS-DMRS association' field is configured in the m-CC DCI and the 'PTRS-DMRS association' field is not set, a specific DMRS port (index) is always assumed / applied according to the setting, regardless of the state (or bit) indicated through the field. The default DMRS port is, for example, '0 or 1'. st It may be a 'scheduled DMRS port'.

[0167] As another example, in options 5-1 and 5-2, only CCs with the 'PTRS-DMRS association' field set are grouped into a shared CC group, but we would like to propose a method for applying the 'PTRS-DMRS association' field in a case where a CC with one PTRS port set and a CC with two PTRS ports set are grouped into a shared CC group.

[0168] (Opt 5-1) Specifically, for a CC with one PTRS port configured, the terminal may interpret / apply the 'PTRS-DMRS association' field only as state 0 / 1 by referring only to the MSB (most significant bit) of the 'PTRS-DMRS association' field. Alternatively, for a CC with one PTRS port configured, the specific default DMRS port may always be fixed and used.

[0169] (Opt 5-2) 2 of CC with two PTRS ports set nd (or vice versa 1 st ) PTRS port is fixed to a specific DMRS port. Terminal 1 st (or vice versa 2 nd ) For PTRS ports, the 'PTRS-DMRS association' field can be interpreted / applied to the associated DMRS port by referring to the MSB or LSB (least significant bit) of the 'PTRS-DMRS association' field. Or 1 st (or vice versa 2 nd ) For PTRS ports, the above specific default DMRS port can always be fixed and used. In Opt 5-2, 1 of the CC with two PTRS ports set st (or 2 nd ) The remaining bits not used in the PTRS port indication can be used for PTRS configuration of the CC where one PTRS port is configured.

[0170] Alternatively, the configuration can be restricted so that only CCs with the same number of PTRS ports configured are grouped into a shared CC group (i.e., CCs with different numbers of PTRS ports configured are not grouped into a shared CC group).

[0171] <'Second PTRS-DMRS association' field>

[0172] This field may not exist in m-CC DCI. Or, it may exist only in s-CC scheduling cases and not in m-CC scheduling cases. Even in s-CC scheduling cases, this field may be defined not to exist if multi-TRP UL operation is not configured for the scheduled cell. For example, in s-CC scheduling cases, this field may be defined to exist when the DCI schedules only cells for which multi-TRP UL operation is configured.

[0173] Alternatively, if the second SRS resource set is indicated to be valid on a cell scheduled through an m-CC scheduling case or an s-CC scheduling case (e.g., by the above method) but the corresponding field does not exist, the association between the PT-RS and DM-RS ports for the corresponding cell may be defined / configured in advance or updated through a MAC CE, etc. In one way, the UE may consider that the same PT-RS port and DM-RS port association as that indicated (for the corresponding cell) in the 'PTRS-DMRS association' field is indicated. Alternatively, the association between a PT-RS port and a DM-RS port to be applied to the second SRS resource set may be configured / defined in advance.

[0174] The m-CC DCI configuration method for fields indicating association between PTRS and DMRS proposed in the present invention can be applied to mapping type A and mapping type B, respectively, when different mapping types (i.e., PDSCH / PUSCH mapping type A and B) are set for scheduled cells and at least one parameter among dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is set differently for each mapping type. When the payload size corresponding to mapping type A is X_A and the payload size corresponding to mapping type B is X_B, the final payload size of the field indicating association between PTRS and DMRS can be |X_A-X_B| or (X_A+X_B).

[0175] In options 6-1 and 6-2, it is proposed how to apply the 'Second PTRS-DMRS association' field when CCs with and without multi-TRP UL operation are grouped into a shared CC group.

[0176] (Opt 6-1) When a CC with multi-TRP UL operation set and a CC without multi-TRP UL operation are grouped into a shared CC group, the corresponding field configuration in the m-CC DCI is omitted, and the operation (related to the association between PTRS and DMRS) for the CC(s) with multi-TRP UL operation set can be predefined or indicated by MAC CE. Alternatively, the value indicated through the 'PTRS-DMRS association' field can be applied to the second TRP as well.

[0177] (Opt 6-2) The field may be present or configured in the m-CC DCI, but may be ignored for CCs for which multi-TRP UL operation is not configured.

[0178] Meanwhile, the present invention is not limited to the transmission and reception of uplink and / or downlink signals. For example, the present invention can also be used in direct communication between terminals. Furthermore, the base station in the present invention may include not only a base station but also a relay node. For example, the base station operations in the present invention may be performed by the base station, but may also be performed by a relay node.

[0179] It is clear that the examples of the proposed methods described above can also be considered as a type of proposed methods, as they can be included as one of the implementation methods of the present invention. In addition, the proposed methods described above can be implemented independently, but can also be implemented in the form of a combination (or merge) of some of the proposed methods. Information on whether the proposed methods are applicable (or information on the rules of the proposed methods) can be defined as a rule so that the base station notifies the terminal or the transmitting terminal notifies the receiving terminal through a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0180] Implementation example

[0181] Figures 4 and 5 are flowcharts of a signal transmission and reception method according to embodiments of the present invention.

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

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

[0184] In addition to the operations of FIGS. 4 and / or 5, one or more of the operations described in 'DCI for scheduling PDSCHs or PUSCHs on multiple serving cells' and sections [1] to [3] may be additionally performed.

[0185] For example, DCI for scheduling PDSCHs on different cells may include one or more fields among Antenna ports and DMRS sequence initialization fields.

[0186] Referring to Opt 2-2A to 2-2C, one Antenna ports field is included for cells belonging to the same shared CC group among different cells that can be scheduled by m-CC DCI. The number of bits in one Antenna ports field is determined based on the maximum value among the number of bits in the Antenna ports field set for single-cell scheduling for each cell.

[0187] In other words, the Antenna ports field is determined as the maximum value among the M bits associated with N different cells when the field is set to Type 1A. Referring to Table 6 and Table 8, for N cells, the M bits for each cell can be determined based on the DMRS type (dmrs-Type) and maximum length (maxLength). The maximum length can be the maximum number of OFDM symbols for DL ​​front-loaded DMRS.

[0188] Additionally, referring to section [2], the DMRS sequence initialization field can be determined as 1 bit for the m-CC DCI that schedules PDSCHs.

[0189] The DCI format of the DCI for scheduling PDSCHs 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 the DCI for scheduling PDSCHs on different cells may be DCI format 1_3.

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

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

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

[0193] In addition to the operations of FIGS. 6 and / or 7, one or more of the operations described in 'DCI for scheduling PDSCHs or PUSCHs on multiple serving cells' and sections [1] to [3] may be additionally performed.

[0194] For example, DCI for scheduling PUSCHs on different cells may include one or more of the following fields: Antenna ports, DMRS sequence initialization, PTRS-DMRS association, and Second PTRS-DMRS association.

[0195] Each DCI field can be configured based on a combination of one or more of the methods disclosed in sections [1] to [3].

[0196] For example, referring to section [2], the DMRS sequence initialization field is a Type 1A field, and thus is included in the m-CC DCI as a field containing common information for cells scheduled through the m-CC DCI. Since the scheduling is for PUSCH, the DCI includes a DMRS sequence initialization field containing common information for PUSCHs. Referring to the conventional standard, the sequence of DMRS transmitted for PUSCH can be generated based on n_SCID, which is a scrambling ID determined based on the DMRS sequence initialization field. Specifically, n_SCID is set to 0 or 1 depending on the value of the DMRS sequence initialization field.

[0197] For PUSCH, if DFT-s-OFDM is applied to all cells that can be scheduled via m-CC DCI, 0 bits can be assigned to the corresponding field. Accordingly, if the transform precoder is activated for all PUSCHs that can be scheduled via DCI, the DMRS sequence initialization field is determined to be 0 bits.

[0198] Additionally, if CP-OFDM is applied to some of the cells that can be scheduled via m-CC DCI and DFT-s-OFDM is applied to the remaining some, 1 bit may be allocated to the field. Accordingly, if the transform precoder is disabled for at least one of all PUSCHs that can be scheduled via DCI, the DMRS sequence initialization field is determined to be 1 bit.

[0199] The size of the DMRS sequence initialization field may be determined based on the cells that are actually scheduled simultaneously at a specific point in time, instead of all cells that can be scheduled via DCI. For example, if DFT-s-OFDM is applied to all of the actually scheduled cells, the field may not exist. Accordingly, if the transform precoder for all PUSCHs on the actually simultaneously scheduled cells among different cells at a specific point in time is activated, the DMRS sequence initialization field may be configured with 0 bits even if the transform precoder for the PUSCHs that are not actually simultaneously scheduled at the specific point in time is deactivated.

[0200] Conversely, even if DFT-s-OFDM is applied to all of the actually scheduled cells, 1 bit may be allocated to the field. However, since no cell among the actually scheduled cells uses the 1 bit, the bit may be regarded as a reserved bit. Therefore, if the transform precoder for the PUSCH that is not actually concurrently scheduled among different cells at a certain point in time is deactivated, even if the transform precoder for all of the PUSCHs on the cells that are actually concurrently scheduled at a certain point in time is activated, the DMRS sequence initialization field is configured with 1 bit.

[0201] Referring to Opt 3-1, etc., if the DMRS sequence initialization field is 0 bit, the terminal may assume / consider or set n_SCID, which is a scrambling ID for DMRS sequence generation, to 0.

[0202] According to [2], in case of DCI for PUSCH scheduling, it can be dynamically indicated which waveform among CP-OFDM or DFT-s-OFDM is to be applied to the corresponding PUSCH. For example, m-CC DCI includes one 1-bit indicator field that includes common information for multiple scheduled cells (or PUSCHs scheduled to the corresponding cells). Therefore, the 1-bit indicator field corresponds to Type-1A. One 1-bit indicator field can indicate dynamic waveform switching to either CP-OFDM or DFT-s-OFDM for multiple scheduled cells (or PUSCHs scheduled to the corresponding cells). Since CP-OFDM or DFT-s-OFDM is determined based on whether the transform precoder is activated, one 1-bit indicator field can be understood as dynamically indicating whether the transform precoder is activated for multiple scheduled cells (or PUSCHs scheduled for the corresponding cells).

[0203] Also, referring to Opt 2-2A to 2-2C in Section [1], for the Antenna ports field related to PUSCH, one Antenna ports field may be included for cells belonging to the same shared CC group among different cells schedulable by m-CC DCI. The number of bits in one Antenna ports field is determined based on the maximum value among the number of bits in the Antenna ports field set for single-cell scheduling for each cell.

[0204] In other words, the Antenna ports field is determined as the maximum value among the M bits associated with N different cells when the field is set to Type 1A. Referring to Table 6, for N cells, the M bits for each cell are determined according to the corresponding table. The conditions for each corresponding table correspond to the conditions described for each number of bits of DCI format 0_1 ​​in Table 6. For example, for a cell with 'if transform precoder is enabled, dmrs-Type=1, and maxLength=1, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and ð / 2 BPSK modulation is used', the Antenna ports field is set to 2 bits. For cells with 'if transform precoder is disabled, dmrs-Type=2, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook', the Antenna ports field is set to 5 bits.

[0205] Here, since the antenna port field is set based on the maximum number of bits among the second antenna port fields, there may be a case where there is no row index corresponding to a specific value of the antenna port field for a specific cell. According to Opt 2-2B, for a specific cell that does not have a DMRS port value corresponding to one value of the antenna port field, the terminal may consider that the PUSCH is not scheduled. Alternatively, according to Opt 2-2C, for a specific cell that does not have a DMRS port value corresponding to one value of the antenna port field, the terminal may transmit the PUSCH based on a specific DMRS port value defined in advance.

[0206] The DCI format of the DCI for scheduling PUSCHs 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 PUSCHs on different cells may be DCI format 0_3.

[0207] In addition to the operations described with respect to FIGS. 4 to 7, one or more of the operations described with respect to FIGS. 1 to 3 and / or the operations described in 'DCI for scheduling PDSCHs or PUSCHs on multiple serving cells' and sections [1] to [3] may be additionally performed in combination.

[0208] Examples of communication systems to which the present invention is applied

[0209] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0210] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0211] Figure 8 illustrates a communication system (1) applied to the present invention.

[0212] Referring to FIG. 8, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

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

[0214] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

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

[0216] Figure 9 illustrates a wireless device applicable to the present invention.

[0217] Referring to FIG. 9, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 8.

[0218] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal 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 perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0219] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

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

[0221] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 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, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0222] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0223] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 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, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

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

[0225] Figure 10 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 8).

[0226] Referring to FIG. 10, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 9 and may be composed of various elements, components, units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 9. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 9. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation 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 / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0227] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 8, 100a), a vehicle (Fig. 8, 100b-1, 100b-2), an XR device (Fig. 8, 100c), a portable device (Fig. 8, 100d), a home appliance (Fig. 8, 100e), an IoT device (Fig. 8, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 8, 400), a base station (Fig. 8, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0228] In FIG. 10, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

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

[0230] Figure 11 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, car, train, manned / unmanned aerial vehicle (AV), ship, etc.

[0231] Referring to FIG. 11, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 10, respectively.

[0232] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0233] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0234] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

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

Claims

1. In a method for transmitting a signal by a terminal (UE) in a wireless communication system, A step of receiving DCI (downlink control information) for scheduling PUSCHs (physical downlink shared channels) on different cells; and A step of transmitting PUSCHs on the different cells based on the DCI; The DCI includes a DMRS sequence initialization (demodulation reference signal sequence initialization) field containing common information for the PUSCHs, The sequence of DMRS associated with each PUSCH of the above cells is generated based on the DMRS sequence initialization field. How to transmit signals.

2. In paragraph 1, Based on the activation of the transform precoder for all of the above PUSCHs, the DMRS sequence initialization field is configured with 0 bits, The DMRS for each of the above cells is generated based on the scrambling ID set to 0. How to transmit signals.

3. In paragraph 1, Based on the deactivation of the transform precoder for at least one of the above PUSCHs, the DMRS sequence initialization field consists of 1 bit. How to transmit signals.

4. In paragraph 1, Based on the activation of the transform precoder for all PUSCHs on cells that are actually concurrently scheduled at a specific point in time among the different cells, even if the transform precoder for a PUSCH that is not actually concurrently scheduled at the specific point in time is deactivated, the DMRS sequence initialization field is configured with 0 bits. The DMRS for each of the above cells is generated based on the scrambling ID set to 0. How to transmit signals.

5. In paragraph 1, The DMRS sequence initialization field is configured with 1 bit, even if the transform precoder for all PUSCHs on the cells that are actually concurrently scheduled at the specific point in time is activated based on the deactivation of the transform precoder for the PUSCHs that are not actually concurrently scheduled at the specific point in time among the different cells. How to transmit signals.

6. In paragraph 5, The above 1 bit is considered a reserved bit, How to transmit signals.

7. In paragraph 1, The above DCI includes one antenna port field for the different cells, The DMRS port value of the DMRS for each of the above cells is determined based on the antenna port field, One second antenna port field per the above cells is set for DCI for scheduling PUSCH within one cell, The number of bits of the above antenna port field is determined based on the maximum value among the number of bits of the set second antenna port fields. How to transmit signals.

8. In paragraph 7, If there is no DMRS port value corresponding to one of the above values ​​for a specific cell among the above cells, the PUSCH for the specific cell is considered as not scheduled. How to transmit signals.

9. In paragraph 7, If there is no DMRS port value corresponding to the one value for a specific cell among the above cells, the PUSCH for the specific cell is transmitted based on a specific DMRS port value defined in advance. How to transmit signals.

10. In paragraph 1, The DCI includes a 1-bit indicator field containing common information for the PUSCHs, The above 1-bit indicator field dynamically indicates whether to enable the transform precoder for the PUSCHs. How to transmit signals.

11. In a terminal for receiving a signal in a wireless communication system, At least one transceiver; at least one processor; and At least one memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform a specific operation; The above specific actions are, A step of receiving DCI (downlink control information) for scheduling PUSCHs (physical downlink shared channels) on different cells; and A step of transmitting PUSCHs on the different cells based on the DCI; The DCI includes a DMRS sequence initialization (demodulation reference signal sequence initialization) field containing common information for the PUSCHs, The sequence of DMRS associated with each PUSCH of the above cells is generated based on the DMRS sequence initialization field. Terminal.

12. In a device for a terminal, at least one processor; and At least one computer memory operably connected to said at least one processor and configured to, when executed, cause said at least one processor to perform operations, said operations comprising: A step of receiving DCI (downlink control information) for scheduling PUSCHs (physical downlink shared channels) on different cells; and A step of transmitting PUSCHs on the different cells based on the DCI; The DCI includes a DMRS sequence initialization (demodulation reference signal sequence initialization) field containing common information for the PUSCHs, The sequence of DMRS associated with each PUSCH of the above cells is generated based on the DMRS sequence initialization field. device.

13. A computer-readable non-volatile storage medium comprising at least one computer program that causes at least one processor to perform an operation, the operation comprising: A step of receiving DCI (downlink control information) for scheduling PUSCHs (physical downlink shared channels) on different cells; and A step of transmitting PUSCHs on the different cells based on the DCI; The DCI includes a DMRS sequence initialization (demodulation reference signal sequence initialization) field containing common information for the PUSCHs, The sequence of DMRS associated with each PUSCH of the above cells is generated based on the DMRS sequence initialization field. Storage media.

14. In a method for a base station (BS) to receive a signal in a wireless communication system, A step of transmitting DCI (downlink control information) for scheduling PDSCHs (physical downlink shared channels) on different cells; and A step of receiving PUSCHs on different cells based on the DCI; The DCI includes a DMRS sequence initialization (demodulation reference signal sequence initialization) field containing common information for the PUSCHs, The sequence of DMRS associated with each PUSCH of the above cells is generated based on the DMRS sequence initialization field. How to receive signals.

15. In a base station for transmitting signals in a wireless communication system, At least one transceiver; at least one processor; and At least one memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform a specific operation; The above specific actions are, A step of transmitting DCI (downlink control information) for scheduling PDSCHs (physical downlink shared channels) on different cells; and A step of receiving PUSCHs on different cells based on the DCI; The DCI includes a DMRS sequence initialization (demodulation reference signal sequence initialization) field containing common information for the PUSCHs, The sequence of DMRS associated with each PUSCH of the above cells is generated based on the DMRS sequence initialization field. Base station.

Images