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

Abstract

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

Description

[Technical Field]

[0001] The present invention relates to a method and apparatus for use in a wireless communication system. [Background technology]

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

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

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

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

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

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

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

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

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

[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 that more efficient signal transmission and reception can be achieved through operations differentiated from conventional inventions.

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

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

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

[0015] For clarity, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical concept of the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR can also be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is also referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, please refer to the matters described in standard documents published before the present invention. For example, the following documents may be referenced:

[0016] 3GPP NR

[0017] - 38.211: Physical channels and modulation

[0018] - 38.212: Multiplexing and channel coding

[0019] - 38.213: Physical layer procedures for control

[0020] - 38.214: Physical layer procedures for data

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

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

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

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

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

[0026] [Table 1]

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

[0028] [Table 2]

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

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

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

[0032] [Table 3]

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

[0034] A slot contains multiple symbols in the time domain. For example, in the case of a general CP, one slot contains 14 symbols, while in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlaces (or simply, interlaces) are defined in the frequency domain. Interlace m ∈ {0, 1, ..., M-1} consists of (common) RBs {m, M+m, 2M+m, 3M+m, ...}, where M represents the number of interlaces. A bandwidth part (BWP) is defined as multiple consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier contains up to N BWPs (e.g., 5). Data communication is performed using activated BWPs, and only one BWP can be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one modulation symbol can be mapped to it.

[0035] In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and the terminal transmits information to the base station via an uplink (UL). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels / signals exist depending on the type / purpose of the information exchanged. A physical channel corresponds to a set of resource elements (RE) that carry information derived from a higher layer. A physical signal corresponds to a set of resource elements (RE) used by a physical layer (PHY), but does not carry information derived from a higher layer. Higher layers include a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, etc.

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

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

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

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

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

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

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

[0043] [Table 4]

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

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

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

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

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

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

[0050] - "Antenna ports" field

[0051] - 'DMRS sequence initialization' field

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

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

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

[0055] [Table 5]

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

[0057] Method 1: shared-cell-common

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

[0059] Method 2: shared-state-extension

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

[0061] Method 3: Separate

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

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

[0064] A method in which only one field is configured in a multi-cell DCI, and the value indicated in that DCI field is applied only to one specific reference cell (e.g., the cell from which the DCI is transmitted, or the cell with the lowest or highest cell index, or the cell indicated by the CIF field value) (among the cells scheduled by the multi-cell DCI and configured to operate according to the DCI field), and a specific pre-defined / configured default value is applied to other cells.

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

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

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

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

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

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

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

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

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

[0074] In the conventional case, the DCI field to which the shared-cell-common method is applied has a structure in which a table consisting of one or more states for each cell is pre-configured by RRC or MAC-CE, and the DCI field indicates one of the one or more states in the table. The conventional case refers to a case in which scheduling is performed based on single-cell DCI. The one or more states are configured with different parameters / values ​​or a combination thereof, and correspond to the row index of each table. Therefore, "state" is replaced with "index." Among the DCI fields, the PRB bundling size indicator, Rate matching (RM) indicator, ZP CSI-RS trigger, and SRS request fields correspond to this structure. The DCI field corresponding to this structure operates based on one or more of the following three options. In the following options, cell set refers to a schedulable cell combination, a co-scheduled cell combination, or a cell subgroup.

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

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

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

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

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

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

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

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

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

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

[0085] When the Alt-A scheme is applied, when a specific state (e.g., a state higher than {N_low-1}) is indicated by a specific DCI field for a specific cell (e.g., a cell set to N_low, where N is a value less than N_max), there may be no parameter / value or combination thereof set for the state for cell X. In consideration of this case, the following operation is proposed. For convenience, M=ceil{log2(N_max)} and K=ceil{log2(N_low)} (M≧K) are defined. Specifically, in the case of a precoding information and number of layers field, a state corresponding to a reserved value may or may not be included in N_max / N_low. In addition, hereinafter, it is assumed that the values ​​of DCI fields corresponding to N states / indexes are 0, ..., N-1.

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

[0087] A. On the other hand, if the K bits indicate a state / index higher than {N_low-1}, then the actions of Alt 3 or Alt 6 apply.

[0088] B. For example, in the case of the antenna port field, if M=5 and K assigned to cell X is K=4, the SRI field is interpreted using only the first or last 4 bits of the 5 bits.

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

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

[0091] B. For example, in the case of an antenna port field, the specific parameter / value or a combination thereof is set / defined to a specific state (e.g., the lowest or highest state / index that is not linked to a reserved value) among N_low states pre-set for the cell X.

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

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

[0094] B. For example, if a value higher than {N_low-1} is indicated for the antenna port field, the terminal assumes that there is no PDSCH / PUSCH scheduling for cell X and omits the transmission and reception operations of PDSCH / PUSCH on cell X (in the case of PDSCH, feeds back the corresponding HARQ-ACK to NACK).

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

[0096] A. The additional parameters / values ​​or combinations thereof are set as additional parameters / values ​​or combinations thereof linked to specific N_gap states among the N_low states preset in the cell X.

[0097] B. For example, in the case of the antenna port field, among the N_low states (excluding states / indexes for reserved values), the parameters / values ​​associated with specific N_gap states or a combination thereof are set.

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

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

[0100] B. For example, in the case of the antenna port field, if N_low=5 and N_max=8, each of the states indicated in the DCI field, {0, 1, 2, 3, 4, 5, 6, 7}, is interpreted / applied to the states {0, 1, 2, 3, 4, 0, 1, 2} for cell X.

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

[0102] A. As a result, the terminal applies / maintains the state most recently instructed to the cell X and performs transmission / reception of the PDSCH / PUSCH on the cell X.

[0103] B. For example, in the case of the antenna port field, the terminal applies / maintains the state most recently indicated for the cell X (by the corresponding field on the same DCI format or a different DCI format) and performs PDSCH / PUSCH transmission / reception operations on the cell X.

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

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

[0106] In the conventional s-CC DCI, for a specific DCI field, the size of the DCI field is set to L=ceil{log2(N)} bits, with N states being set to be indicative by the DCI field. L is set to a different (or the same) value for each cell. The specific DCI field includes an antenna ports field, a PTRS-DMRS association field, etc.

[0107] On the other hand, in the case of an m-CC DCI, if the specific DCI field is configured based on the method of the Type-2 field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations configured in the entire schedulable cell combinations, a sum L_sum of the L values ​​configured for each of the cells belonging to the co-scheduled cell combination is calculated. The maximum value of the N_co L_sum values ​​calculated for each of the N_co co-scheduled cell combinations is determined as the size of the specific DCI field (configured in the m-CC DCI).

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

[0109] For example, in the case of the PTRS-DMRS related field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations (especially, cells configured with CB-based UL) configured in the entire schedulable cell combinations, a sum L_sum of the L values ​​(for the PTRS-DMRS related field) configured in each of the cells (especially, cells configured with CB-based UL) belonging to the co-scheduled cell combination is calculated. The maximum value of the N_co L_sum values ​​calculated for each of the N_co co-scheduled cell combinations is determined as the size of the PTRS-DMRS related field (configured in the m-CC DCI).

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

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

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

[0113] For example, in the case of the antenna port field, for a specific cell X, the number of DM-RS symbols for m-CC DCI, the maximum number of ranks / layers, or valid / invalid row indices among the table rows corresponding to the cell are defined / set / indicated. When configuring the antenna port field in the m-CC DCI and / or when scheduling multiple CCs using the m-CC DCI, N_cfg states and a field size L_cfg are determined for the cell based on the given number of DM-RS symbols, the maximum number of ranks / layers, or valid / invalid row indices among the table rows corresponding to the cell. When configuring the antenna port field in the m-CC DCI and / or when scheduling multiple CCs using the m-CC DCI, for cells for which the number of DM-RS symbols, the maximum number of ranks / layers, or valid / invalid row indices among the table rows corresponding to the cell are not defined / set / indicated, the antenna port field in the m-CC DCI for the cell is configured based on the N states and field size L set in the s-CC DCI.

[0114] [1] "Antenna port" field

[0115] Table 6 shows the antenna port field for each DCI format as disclosed in 3GPP TS 38.212.

[0116] [Table 6-1] [Table 6-2]

[0117] For the rank / number of layers determined by the SRI and / or precoding information and number of layers field, a corresponding DM-RS port index is determined for each layer according to the field.

[0118] As a method for reducing the field size, the number of DM-RS symbols is configured / applied differently depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the s-CC scheduling case, even if the maxLength value follows a value predefined / configured for each cell, the m-CC scheduling case is constrained to schedule only a single-symbol DM-RS. Alternatively, in the scheduling case based on the m-CC DCI, only a single-symbol DM-RS is constrained to be scheduled at any time. Alternatively, a configuration constraint is imposed so that the maxLength value is always set to 1 for cells configured as targets for m-CC DCI scheduling. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (i.e., configured to operate according to the DCI field indication) are configured in the DCI. Furthermore, an individual field corresponds to each scheduled cell, and the antenna port field is configured in such a manner that the value indicated in the field is applied to the cell. This field configuration method is called the "Type-2 field design method."

[0119] If the number of DM-RS symbols for each cell is constrained to match, the CDM capacity will be reduced. In consideration of this, a separate table for each cell and a corresponding individual field for each cell are configured, and the DM-RS port index for each layer is indicated for each cell by the individual field. By adjusting the number of rows in the table for each cell, it is possible to reduce the overall number of bits required to indicate the DM-RS port index for each layer.

[0120] For example, as shown in Table 7 below, when certain conditions (if transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=1) are met, signaling for 28 combinations is required. However, if the cell is scheduled by 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 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 cell.

[0121] In this case, for each cell, which row indexes to select from the rows of the conventional table to reduce the table size and the number of bits is set separately or predefined. For example, only even indexes may be selected from the row indexes, only indexes corresponding to multiples of a specific N value may be selected, only a specific number of lowest indexes may be selected, or only a specific number of highest indexes may be selected. Specifically, a specific cell may be configured to be assigned a 0 bit to indicate the DM-RS port index for each layer. In this case, a specific DM-RS port index is applied to that cell. For example, a rule may be set in advance so that the DM-RS port index is set to 0 for that cell, or it may be predefined which DM-RS port index to use.

[0122] Meanwhile, the application of the above method varies depending on which cell is actually scheduled (the table size varies), and it may be applicable only to the m-CC scheduling case and not to the s-CC scheduling case. As an example, in the s-CC scheduling case, when a cell to which the following Table 7 applies is scheduled, a 5-bit antenna port field is assigned to the cell. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (cells for which an operation according to the indication of the DCI field is set) are configured in the DCI. Furthermore, an individual field corresponds to each scheduled cell, and the antenna port field is configured in such a manner that the value indicated in the field is applied to the cell. This field configuration method is called a "Type-2 field design method."

[0123] [Table 7]

[0124] Alternatively, the setting / application of the maximum rank / number of layers may differ depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the s-CC scheduling case, the maxRank value may follow a predefined / configured value for each cell, but in the m-CC scheduling case, the maxRank value is constrained to K. Alternatively, in the scheduling case based on the m-CC DCI, the maxRank value is always constrained to K. Alternatively, a configuration constraint is imposed on cells configured as targets for m-CC DCI scheduling so that the maxRank value is always set to K only. The value of K is pre-configured or defined. For example, K=1. In the case of PDSCH, specifically, the constraint on the maxRank value is applied only when only 1-TB is scheduled. For cells scheduled with 2-TB, the constraint on the rank value may not be applied. This is because, as shown in Table 8 below, in the case of 2-TB (i.e., when both two codewords are enabled), there are only four corresponding row indexes, and in the case of 1-TB, even if the corresponding row index becomes four or more due to the constraint of the number of ranks, the number of bits of the antenna port field does not change. In this case, the same number of fields as the number of cells scheduled by the m-CC DCI (for which an operation according to the indication of the DCI field is set) are configured in the DCI. Furthermore, an individual field corresponds to each scheduled cell, and the antenna port field is configured in such a manner that the value indicated in the field is applied to the cell. This field configuration method is called the "Type-2 field design method."

[0125] [Table 8]

[0126] The method of configuring m-CC DCI for the "antenna ports" field proposed in the present invention is such that, when different mapping types (i.e., PDSCH / PUSCH mapping type A and B) are configured for a scheduled cell and at least one parameter setting of dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is different for each mapping type, each method is applied to mapping type A and mapping type B. 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 is |X_A-X_B| or (X_A+X_B).

[0127] Options 1-1 to 2-2C disclose how to apply the "Antenna ports" field when CCs that refer to different tables to interpret the "Antenna ports" field are grouped into a shared CC group.

[0128] First, a setting constraint is imposed so that only CCs of the same type belong to a shared CC group. That is, a common table is referenced to interpret the "Antenna ports" field for all CCs belonging to the shared CC group. In this case, "CCs of the same type" means that the settings of transform precoding and / or the settings for the dmrs-Type parameter and / or the settings for the tp-pi2BPSK parameter and / or the settings for the maxLength parameter are the same (or at least one of these settings). Which settings should be the same differs depending on, for example, the case of PDSCH or PUSCH. In the case of PUSCH, a constraint is added so that CCs grouped in a shared CC group have the same transmission rank value, so that a common table is referenced to interpret the "Antenna ports" field. In the case of PDSCH, even if the settings for the dmrs-Type parameter and the settings for the maxLength parameter are the same, different tables are referenced for each CC depending on whether spatial domain multiplexing (SDM) reception from multi-TRP is configured.

[0129] (Opt 1-1) Specifically, only cells with the same setting for whether or not to receive multi-TRP DL are restricted to belong to the shared CC group.

[0130] (Opt 1-2) Alternatively, CCs with different settings for whether or not to receive multi-TRP DL are allowed to belong to one shared CC group. In Opt 1-2, when the table referred to by a cell configured for multi-TRP DL reception operation is X (for example, Table 7.3.1.2.2-1A in the TS 38.212 specifications) and the table referred to by a cell not configured for multi-TRP DL reception operation is Table Y (for example, Table 7.3.1.2.2-1 in the TS 38.212 specifications), a rule is defined so that table X or table Y is commonly referred to for the shared CC group in the m-CC scheduling case. In this case, even if different codepoints exist between table X and table Y, when the specific codepoint is indicated, a cell not configured for multi-TRP DL reception operation performs PDSCH reception as if it were not configured for PDSCH scheduling or as if a pre-configured / defined antenna port is indicated. Alternatively, in Opt 1-2, a rule is 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), and only single-TRP transmission is allowed for cells where multi-TRP DL reception operation is configured but scheduled with m-CC DCI (or when multiple cells are scheduled simultaneously with m-CC DCI).

[0131] (Opt 2-1) Alternatively, CCs of different types (i.e., not the same type as described above) are allowed to belong to a shared CC group. In this case, the "Antenna ports" field configuration is omitted in the m-CC DCI (i.e., the field does not exist), and the number of codepoints required / applied to each CC in the group (in the "Antenna ports" table) is restricted to one. The codepoint is either pre-configured or indicated by the MAC.

[0132] (Opt 2-2) The field and / or the corresponding table are configured to match a specific CC of a specific type (such as the parameters and codepoint number set for single-cell scheduling of the CC) belonging to the shared CC group. A default codepoint is applied to CCs of a type different from the specific type. The default codepoint is set in advance or indicated by the MAC.

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

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

[0135] (Opt 2-2C) If the 'Antenna ports' field is configured in the same manner as Opt 2-2B, or if the specified code point is invalid for a specific CC, the terminal operates to assume / apply a specific code point that is predefined / configured for the CC.

[0136] [2] "DMRS sequence initialization" field

[0137] If a 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. Alternatively, if a 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 a PDSCH is scheduled by s-CC DCI, 1 bit is always assigned to this field.

[0138] The DMRS sequence initialization field is a Type 1A field, and one bit is assigned in common to cells that are (simultaneously) scheduled by m-CC DCI. In the case of PUSCH, specifically, one bit is assigned in common to cells to which CP-OFDM is applied among the cells. That is, a value of "0" or "1" indicated for all scheduled cells (in the case of PUSCH, all cells to which CP-OFDM is applied) is applied.

[0139] In the case of PUSCH, if DFT-s-OFDM is applied to all cells scheduled by m-CC DCI, 0 bit is assigned to this field. On the other hand, if CP-OFDM is applied to some of the cells scheduled by m-CC DCI and DFT-s-OFDM is applied to the others, 1 bit is assigned to this field. If DFT-s-OFDM is applied to all actually scheduled cells, this field may not exist. Alternatively, if DFT-s-OFDM is applied to all actually scheduled cells, 1 bit is assigned to this field, and this bit is considered a reserved bit. Alternatively, a configuration constraint is imposed that DFT-s-OFDM is applied to all cells for which m-CC DCI is configured.

[0140] When M cells (in the case of PUSCH, it means the cells to which M CP-OFDMs are applied) are scheduled, if the field is configured with fewer than K (<M) bits, 2^K (or less than 2^K) combinations of DM-RS sequence initializations for the M cells are preset, and one of those combinations is indicated by the m-CC DCI. As an example, in the case of PDSCH, when M = 4 and K = 2, for each of the cases of "00" / "01" / "10" / "11", the methods of initializing the DM-RS sequences for the four cells are preset. When the m-CC DCI indicates "00", the method of initializing the DM-RS sequence corresponding to the code point is applied to each of the M cells.

[0141] As another method, in the case of m-CC DCI, the field does not exist. In this case, the predefined / set method of initializing the DM-RS sequence is applied to each scheduled cell. That method (the method of not configuring / indicating a field / information in the m-CC DCI) is only applicable 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 is configured / indicated in the DMRS sequence initialization field.

[0142] As yet another method, with only one field configured in the m-CC DCI, the DM-RS sequence initialization information is indicated (by the field) only for a specific one of the cells scheduled by the DCI, which is the reference cell. For the other cells that are not the reference cell, the predefined / set method of initializing the DM-RS sequence is applied.

[0143] Options 3-1 to 3-3 disclose the application method of the "DMRS sequence initialization" field when the CCs with the "DMRS sequence initialization" field set and those without are grouped into a shared CC group.

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

[0145] (Opt 3-2) If the "DMRS sequence initialization" field is configured in the m-CC DCI and indicated as n_SCID=1, it is assumed that there is no scheduling for CCs where the "DMRS sequence initialization" field is not set.

[0146] (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 is always applied (even if the field indicates n_SCID=1).

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

[0148] [3] A field indicating the association between the PTRS and the DMRS.

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

[0150] [Table 9]

[0151] <“PTRS-DMRS association” field>

[0152] If the condition for allocating 0 bit to this field is met for all cells that can be (simultaneously) scheduled by 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) (for convenience, this condition is referred to as condition #A), 0 bit is allocated to this field. On the other hand, if some of the cells that can be scheduled by m-CC DCI satisfy condition #A and the others do not, 2 bits (or 1 bit by combining the following method) are allocated to this field. If the actually scheduled cell satisfies condition #A, this field may not exist. Alternatively, if the actually scheduled cell satisfies condition #A, 2 bits (or 1 bit by combining the following method) are allocated to this field, but these 2 bits are considered to be reserved bits. Alternatively, a configuration constraint is imposed that all cells configured with m-CC DCI are configured to satisfy condition #A. Alternatively, the s-CC scheduling case does not impose a constraint that condition #A be satisfied, and only the m-CC scheduling case imposes a constraint on scheduled cells that condition #A be satisfied (e.g., maxRank=1).

[0153] Alternatively, in the case of scheduling with m-CC DCI, the field size can be reduced by reducing the number of candidates for the DM-RS port index associated with the PT-RS compared to the conventional s-CC DCI. As an example, as shown in Table 10 below, PT-RS port 0 is indicated by this field to be associated with one of four DM-RS ports. However, in the case of m-CC DCI (or in the case of m-CC scheduling), PT-RS port 0 is designated as one of two specific DM-RS ports (e.g., 1 st scheduled DMRS port or 2 nd In this case, for each cell scheduled by the same m-CC DCI, only one bit is required in the "PTRS-DMRS association" field for that cell, instead of two bits. Alternatively, to further reduce the number of bits in this field, in the case of scheduling by m-CC DCI (or in the case of m-CC scheduling), which DM-RS port is associated with the PT-RS port is pre-configured / defined, and the "PTRS-DMRS association" field for that cell is not assigned.

[0154] In the case of scheduling by m-CC DCI (or in the case of m-CC scheduling), the number of bits in the "PTRS-DMRS association" field corresponding to each cell is set to be the same by commonly applying any one of the above methods to cells scheduled by the same m-CC DCI. Alternatively, the number of bits in the "PTRS-DMRS association" field may be different for each cell by applying a different one of the above methods to cells scheduled by the same m-CC DCI. As an example, in the m-CC scheduling case, 2 bits are assigned to this field as in the conventional case, and 0 bits are assigned to this field for other scheduled cells. The reference cell is defined and / or configured to the cell with the lowest cell index, the cell with the highest cell index, the cell with the lowest SCS configured, the cell with the highest SCS configured, the scheduling cell from which the m-CC DCI is transmitted, the cell with the smallest number of SRS resources in the SRS resource set, or the cell with the largest number of resources in the SRS resource set. For cells to which 0 bit is assigned in this field, it is either preset / defined which DM-RS port is associated with the PT-RS port, or a restriction is set that condition #A must be satisfied. As another example, in the s-CC scheduling case, 2 bits are assigned to this field as in the past, and in the m-CC scheduling case, the above-proposed method (including the 0 bit assignment method) is applied commonly or differently to multiple cells.

[0155] [Table 10]

[0156] Options 4-1 to 4-3 disclose how the "PTRS-DMRS association" field is applied when CCs with and without the "PTRS-DMRS association" field set are grouped into a shared CC group.

[0157] (Opt 4-1) When a CC with the "PTRS-DMRS association" field set and a CC without the "PTRS-DMRS association" field set 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 scheduled DMRS port.

[0158] (Opt 4-2) When the "PTRS-DMRS association" field is configured in the m-CC DCI and indicates a state of 0 (or only bit "0"), the specific default DMRS port is assumed / applied to CCs for which the "PTRS-DMRS association" field is not configured. If a state other than 0 (or at least one bit "1") is indicated, it is assumed that there is no scheduling for the unconfigured CCs.

[0159] (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 by the configuration, regardless of the state (or bit) indicated by the field. The default DMRS port is, for example, "0 or 1". st scheduled DMRS port.

[0160] As another example, in Options 5-1 and 5-2, CCs with the "PTRS-DMRS association" field set are grouped into a shared CC group, but we propose a method for applying the "PTRS-DMRS association" field when a CC with one PTRS port set and a CC with two PTRS ports set are grouped into a shared CC group.

[0161] (Opt 5-1) Specifically, for a CC configured with one PTRS port, the terminal only refers to the most significant bit (MSB) of the "PTRS-DMRS association" field and interprets / applies the "PTRS-DMRS association" field to only state 0 / 1. Alternatively, for a CC configured with one PTRS port, the specific default DMRS port is always fixed and used.

[0162] (Opt 5-2) Two PTRS ports are set for CC. nd (or 1 st )PTRS port is fixed to a specific DMRS port. st (or 2 nd For a PTRS port, the MSB or LSB (least significant bit) of the "PTRS-DMRS association" field is referred to and interpreted / applied to the DMRS port associated with the "PTRS-DMRS association" field. st (or 2 nd For the PTRS port, the specific default DMRS port is always fixed and used. In Opt 5-2, one of the CCs with two PTRS ports set st (or 2 nd ) The remaining bits not used to indicate the PTRS port are used for PTRS configuration of CCs with one PTRS port configured.

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

[0164] <“Second PTRS-DMRS association” field>

[0165] This field may not be present in the m-CC DCI. Alternatively, it may be present only in the s-CC scheduling case and not in the m-CC scheduling case. Even in the s-CC scheduling case, if multi-TRP UL operation is not configured for the scheduled cell, this field is specified to be absent. For example, in the s-CC scheduling case, this field is specified to be present when the DCI schedules only cells with multi-TRP UL operation configured.

[0166] Alternatively, if it is indicated (by the above-described method or the like) that a second SRS resource set is valid on a cell scheduled in the m-CC scheduling case or the s-CC scheduling case, but this field does not exist, the association between the PT-RS and the DM-RS port for this cell is predefined / configured or updated by the MAC CE or the like. As one method, the terminal considers that the same association between the PT-RS port and the DM-RS port as indicated (for this cell) in the "PTRS-DMRS association" field has been indicated. Alternatively, the association between the PT-RS port and the DM-RS port to be applied to the second SRS resource set is predefined / configured.

[0167] The m-CC DCI configuration method for the field indicating the association between a PTRS and a DMRS proposed in the present invention is applied to mapping type A and mapping type B when different mapping types (i.e., PDSCH / PUSCH mapping type A and B) are configured for a scheduled cell and at least one parameter setting of dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is different 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 the association between a PTRS and a DMRS is |X_A-x_B| or (X_A+X_B).

[0168] Options 6-1 and 6-2 propose how to apply the "Second PTRS-DMRS association" field when CCs with and without multi-TRP UL operation configured are grouped into a shared CC group.

[0169] (Opt 6-1) If a CC with and without multi-TRP UL operation configured is grouped into a shared CC group, the configuration of this field in the m-CC DCI is omitted, and the operation (PTRS and DMRS association) for the CC with multi-TRP UL operation configured is predefined or indicated by the MAC CE. Alternatively, the value indicated by the "PTRS-DMRS association" field applies to the second TRP as well.

[0170] (Opt 6-2) This field is present or configured in the m-CC DCI, but is ignored for CCs that are not configured for multi-TRP UL operation.

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

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

[0173] Example

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

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

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

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

[0178] For example, DCI for scheduling PDSCHs on different cells includes one or more of an antenna port field and a DMRS sequence initialization field.

[0179] Referring to Opt 2-2A to 2-2C, one antenna port 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 of one antenna port field is determined based on the maximum value of the number of bits of the antenna port field set for single-cell scheduling for each cell.

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

[0181] Also, referring to Section [2], the DMRS sequence initialization field is determined to be 1 bit for the m-CC DCI that schedules the PDSCH.

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

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

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

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

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

[0187] For example, DCI for scheduling PUSCHs on different cells may include one or more of the following fields: antenna port, DMRS sequence initialization, PTRS-DMRS association, and second PTRS-DMRS association fields.

[0188] Each DCI field is configured based on a combination of one or more of the methods disclosed in Sections [1] through [3].

[0189] For example, referring to Section [2], the DMRS sequence initialization field is a Type 1A field, and is therefore included in the m-CC DCI as a single field containing common information for cells scheduled by the m-CC DCI. Since scheduling is for a PUSCH, the DCI includes a DMRS sequence initialization field containing common information for the PUSCH. Referring to previous standards, the DMRS sequence transmitted for the PUSCH is 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.

[0190] In the case of PUSCH, if DFT-s-OFDM is applied to all cells that can be scheduled by m-CC DCI, 0 bits are assigned to this field. Therefore, if a transform precoder is activated for all PUSCHs that can be scheduled by DCI, the DMRS sequence initialization field is determined to be 0 bits.

[0191] Furthermore, when CP-OFDM is applied to some of the cells that can be scheduled by m-CC DCI and DFT-s-OFDM is applied to the other cells, 1 bit is assigned to this field. Therefore, when a transform precoder is deactivated for at least one of all PUSCHs that can be scheduled by DCI, the DMRS sequence initialization field is determined to be 1 bit.

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

[0193] Conversely, even if DFT-s-OFDM is applied to all actually scheduled cells, one bit may be allocated to this field. However, since no actually scheduled cells use this one bit, this bit is considered a reserved bit. Therefore, if transform precoders for PUSCHs of different cells that are not actually scheduled simultaneously at a particular time are deactivated, the DMRS sequence initialization field is configured with one bit even if transform precoders for all PUSCHs of cells that are actually scheduled simultaneously at a particular time are activated.

[0194] Referring to Opt 3-1, etc., if the DMRS sequence initialization field is 0 bit, the terminal assumes / considers or sets n_SCID, which is a scrambling ID for generating a DMRS sequence, to 0.

[0195] According to Section [2], in the case of DCI for PUSCH scheduling, which waveform, CP-OFDM or DFT-s-OFDM, is applied to the corresponding PUSCH is dynamically indicated. For example, m-CC DCI includes one 1-bit indicator field containing common information for multiple scheduled cells (or PUSCHs scheduled in the cells). Thus, the 1-bit indicator field corresponds to Type-1A. One 1-bit indicator field indicates dynamic waveform switching to one of CP-OFDM or DFT-s-OFDM for multiple scheduled cells (or PUSCHs scheduled in the cells). Since CP-OFDM or DFT-s-OFDM is determined depending on whether a transform precoder is activated, one 1-bit indicator field can be understood to dynamically indicate the activation of a transform precoder for multiple scheduled cells (or PUSCHs scheduled in the cells).

[0196] Also, referring to Opt 2-2A to 2-2C in Section [1], the antenna port field related to the PUSCH also includes one antenna port field 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 port field is determined based on the maximum value of the number of bits in the antenna port field set for single-cell scheduling for each cell.

[0197] In other words, when the antenna port field is set to Type 1A, it is determined to be the maximum value of M bits associated with N different cells. Referring to Table 6, for N cells, M bits for each cell are determined according to the corresponding table. The conditions for each corresponding table correspond to the conditions listed for each bit number of DCI format 0_1 ​​in Table 6. For example, for a cell where "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 port field is set to 2 bits. For cells where "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 port field is set to 5 bits.

[0198] Here, since the antenna port field is set based on the maximum number of bits of the second antenna port field, there may be a case where a row index corresponding to a specific value of the antenna port field does not exist for a specific cell. According to Opt 2-2B, for a specific cell that does not have a DMRS port value corresponding to a value of the antenna port field, the terminal assumes that a PUSCH is not scheduled. Alternatively, according to Opt 2-2C, for a specific cell that does not have a DMRS port value corresponding to a value of the antenna port field, the terminal transmits a PUSCH based on a predefined specific DMRS port value.

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

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

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

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

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

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

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

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

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

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

[0209] FIG. 9 illustrates a wireless device to which the present invention can be applied.

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

[0211] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 102 processes information in the memory 104 to generate first information / signals and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106 and then stores information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0212] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

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

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

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

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

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

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

[0219] 10, wireless devices 100, 200 correspond to the wireless devices 100, 200 of FIG. 9 and are composed of various elements, components, units / parts, and / or modules. For example, the wireless devices 100, 200 include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102, 202 and / or one or more memories 104, 204 in FIG. 9. For example, the transceiver 114 includes one or more transceivers 106, 206 and / or one or more antennas 108, 208 in FIG. 9. The control unit 120 is electrically coupled to the communication unit 110, the memory unit 130, and the additional element 140, and controls the overall operation of the wireless device. For example, the control unit 120 controls the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0220] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Wireless devices may be embodied in the form of, but are not limited to, a robot (FIG. 8, 100a), a vehicle (FIG. 8, 100b-1, 100b-2), an XR device (FIG. 8, 100c), a mobile device (FIG. 8, 100d), a home appliance (FIG. 8, 100e), an IoT device (FIG. 8, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or financial device), a security device, a climate / environment device, an AI server / device (FIG. 8, 400), a base station (FIG. 8, 200), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0221] In FIG. 10, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all connected to each other by wired interfaces or at least some are connected wirelessly by a communication section 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Furthermore, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is configured with a set of one or more processors. For example, the control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 is configured with a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

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

[0223] 11 is a diagram illustrating an example of a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be embodied as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, etc.

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

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

[0226] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a driving plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. The communication unit 110 aperiodically obtains the latest traffic information data from an external server during autonomous driving and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server can predict traffic information data using AI technology based on information collected from the vehicle or autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0227] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the characteristics of the present invention. Therefore, the above detailed description should not be construed as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention. [Industrial Applicability]

[0228] As mentioned above, the present invention can be applied to a variety of wireless communication systems.

Claims

1. A method for providing a mobile station with a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells; transmitting the PUSCH on the plurality of cells based on the DCI; The DCI includes one demodulation reference signal (DMRS) sequence initialization field containing information for the PUSCH, The DMRS sequence initialization field is set to a 0 bit based on the transform precoder not being disabled for all of the plurality of cells; The DMRS sequence initialization field is set to 1 bit based on the transform precoder being disabled for at least one cell among the plurality of cells; A method, wherein a sequence of DMRSs associated with each of the PUSCHs is generated based on the DMRS sequence initialization field.

2. the DCI includes an antenna port field for the plurality of cells; a DMRS port value of the DMRS associated with each of the PUSCHs is determined based on the antenna port field; the number of bits in the antenna port field is determined based on a maximum number of bits for antenna ports; The method of claim 1 , wherein each of the number of bits for the antenna port is defined for a corresponding cell of the plurality of cells.

3. 3. The method of claim 2, wherein the PUSCH for a particular cell from the plurality of cells is deemed not to be scheduled based on the absence of a DMRS port value corresponding to one of the values ​​for the particular cell.

4. 3. The method of claim 2, wherein, based on the absence of a DMRS port value corresponding to one of the values ​​for a particular cell from the plurality of cells, the PUSCH for the particular cell is transmitted based on a predefined particular DMRS port value.

5. The DCI includes one 1-bit indicator field containing common information for the PUSCH; The method of claim 1 , wherein the 1-bit indicator field indicates whether the transform precoder is disabled.

6. At least one processor; at least one memory configured to store instructions; The instructions, when executed, cause the at least one processor to: receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells; transmitting the PUSCH on the plurality of cells based on the DCI; The DCI includes one demodulation reference signal (DMRS) sequence initialization field containing information for the PUSCH, The DMRS sequence initialization field is set to a 0 bit based on the transform precoder not being disabled for all of the plurality of cells; The DMRS sequence initialization field is set to 1 bit based on the transform precoder being disabled for at least one cell among the plurality of cells; A UE (user equipment) generates a sequence of DMRSs associated with each of the PUSCHs based on the DMRS sequence initialization field.

7. The DCI includes an antenna port field for each of the plurality of cells; a DMRS port value of the DMRS associated with each of the PUSCHs is determined based on the antenna port field; the number of bits in the antenna port field is determined based on a maximum number of bits for antenna ports; The UE of claim 6 , wherein each of the number of bits for the antenna port is defined for a corresponding cell of the plurality of cells.

8. An apparatus for a UE (user equipment), comprising: at least one processor; at least one computer memory configured, when executed, to cause said at least one processor to perform operations; The operation is receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells; transmitting the PUSCH on the plurality of cells based on the DCI; The DCI includes one demodulation reference signal (DMRS) sequence initialization field containing information for the PUSCH, The DMRS sequence initialization field is set to a 0 bit based on the transform precoder not being disabled for all of the plurality of cells; The DMRS sequence initialization field is set to 1 bit based on the transform precoder being disabled for at least one cell among the plurality of cells; A sequence of DMRSs associated with each of the PUSCHs is generated based on the DMRS sequence initialization field.

9. The DCI includes an antenna port field for each of the plurality of cells; a DMRS port value of the DMRS associated with each of the PUSCHs is determined based on the antenna port field; the number of bits in the antenna port field is determined based on a maximum number of bits for antenna ports; The apparatus of claim 8 , wherein each of the number of bits for the antenna port is defined for a corresponding cell of the plurality of cells.

10. A computer-readable non-transitory storage medium containing at least one computer program for causing at least one processor to perform operations, comprising: The operation is receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells; transmitting the PUSCH on the plurality of cells based on the DCI; The DCI includes one demodulation reference signal (DMRS) sequence initialization field containing information for the PUSCH, The DMRS sequence initialization field is set to a 0 bit based on the transform precoder not being disabled for all of the plurality of cells; The DMRS sequence initialization field is set to 1 bit based on the transform precoder being disabled for at least one cell among the plurality of cells; A computer-readable non-transitory storage medium, wherein a sequence of DMRSs associated with each of the PUSCHs is generated based on the DMRS sequence initialization field.

11. The DCI includes one antenna port field for the plurality of cells; a DMRS port value of the DMRS associated with each of the PUSCHs is determined based on the antenna port field; the number of bits in the antenna port field is determined based on a maximum number of bits for antenna ports; The computer-readable non-transitory storage medium of claim 10 , wherein each of the number of bits for the antenna port is defined for a corresponding cell of the plurality of cells.

12. A method for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells, comprising: transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells; receiving the PUSCH on the plurality of cells based on the DCI; The DCI includes one demodulation reference signal (DMRS) sequence initialization field containing information for the PUSCH, The DMRS sequence initialization field is set to a 0 bit based on the transform precoder not being disabled for all of the plurality of cells; The DMRS sequence initialization field is set to 1 bit based on the transform precoder being disabled for at least one cell among the plurality of cells; A method, wherein a sequence of DMRSs associated with each of the PUSCHs is generated based on the DMRS sequence initialization field.

13. The DCI includes one antenna port field for the plurality of cells; a DMRS port value of the DMRS associated with each of the PUSCHs is determined based on the antenna port field; the number of bits in the antenna port field is determined based on a maximum number of bits for antenna ports; The method of claim 12 , wherein each of the number of bits for the antenna port is defined for a corresponding cell of the plurality of cells.

14. At least one processor; at least one memory configured to store instructions; The instructions, when executed, cause the at least one processor to: transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) on a plurality of cells; receiving the PUSCH on the plurality of cells based on the DCI; The DCI includes one demodulation reference signal (DMRS) sequence initialization field containing information for the PUSCH, The DMRS sequence initialization field is set to a 0 bit based on the transform precoder not being disabled for all of the plurality of cells; The DMRS sequence initialization field is set to 1 bit based on the transform precoder being disabled for at least one cell among the plurality of cells; A base station (BS) generates a sequence of DMRSs associated with each of the PUSCHs based on the DMRS sequence initialization field.

15. The DCI includes an antenna port field for each of the plurality of cells; a DMRS port value of the DMRS associated with each of the PUSCHs is determined based on the antenna port field; the number of bits in the antenna port field is determined based on a maximum number of bits for antenna ports; The BS of claim 14 , wherein each of the number of bits for the antenna port is defined for a corresponding cell of the plurality of cells.

Images