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 used in a wireless communication system.

Background Art

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

Summary of the Invention

Problems to be Solved by the Invention

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

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

Means for Solving the Problems

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

[0006] As an embodiment of the present invention, there is provided a method for a terminal (UE) to transmit a signal in a wireless communication system, 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. The DCI includes one demodulation reference signal sequence initialization field including common information for the PUSCH, and the sequence of the DMRS related to each PUSCH of the cell is generated based on the DMRS sequence initialization field.

[0007] As an embodiment of the present invention, there is provided a method for a base station (BS) to receive a signal in a wireless communication system, including 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. The DCI includes one demodulation reference signal sequence initialization field including common information for the PUSCH, and the sequence of the DMRS related to each PUSCH of the cell is generated based on the DMRS sequence initialization field.

[0008] As another embodiment of the present invention, there are provided an apparatus, a processor, and a storage medium for performing the signal receiving method. Also, as another embodiment of the present invention, there are provided an apparatus, a processor, and a storage medium for performing the signal transmitting method.

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

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

Effects of the Invention

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

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

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Best Mode for Carrying Out the Invention

[0014] The following technologies can be used in various wireless connection systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented by radio technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented by radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (registered trademark) (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) using 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 clearer explanation, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the present invention is not limited thereto. LTE means the technology after 3GPP TS 36.xxx Release 8. Specifically, the LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and the LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR means the technology after TS 38.xxx Release 15. LTE / NR can also be referred to as the 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR is referred to as the 3GPP system. For the background technology, terms, abbreviations, etc. used in the description of the present invention, reference can be made to the matters described in the standard documents published before the present invention. For example, the following documents can be referred to.

[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 (HF). A half - frame is defined as five 1 - ms sub - frames (SF). A sub - frame is divided into one or more slots, and the number of slots in a sub - frame depends on the sub - carrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols by means of a cyclic prefix (CP). When normal CP is used, each slot contains 14 symbols. When extended CP is used, each slot contains 12 symbols. Here, the symbol can include an OFDM symbol (or a CP - OFDM symbol), an SC - FDMA symbol (or a DFT - s - OFDM symbol).

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

[0026] [Table 1]

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

[0028] [Table 2]

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

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

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

[0032]

Table 3

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

[0034] A slot contains a plurality of symbols in the time domain. For example, in the case of normal CP, one slot contains 14 symbols, while in the case of extended CP, one slot contains 12 symbols. A carrier contains a plurality of subcarriers in the frequency domain. An RB (Resource Block) is defined as a plurality (e.g., 12) of consecutive subcarriers in the frequency domain. In the frequency domain, a plurality of RB interleaves (simply, interleaves) are defined. An interleave m ∈ {0, 1,..., M - 1} is composed of (common) RBs {m, M + m, 2M + m, 3M + m,...}. M indicates the number of interleaves. A BWP (Bandwidth Part) is defined as a plurality of consecutive PRBs (Physical RBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier contains a maximum of N (e.g., 5) BWPs. Data communication is performed on the activated BWP, and only one BWP is activated for one terminal. Each element in the resource grid is called a resource element (Resource Element (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 the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received by the base station and the terminal includes data and various control information, and there are various physical channels / signals depending on the type / usage of the information they transmit and receive. A physical channel corresponds to a set of resource elements (REs) that carry information derived from the upper layer. A physical signal corresponds to a set of resource elements (REs) used by the physical layer (PHY) but does not carry information derived from the upper layer. The upper layer includes the MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP (Packet Data Convergence Protocol) layer, RRC (Radio Resource Control) layer, etc.

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

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

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

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

[0040] In addition, the method described hereinafter can be similarly applied to the above-described NR system (licensed band) or shared spectrum. Needless to say, it can be deformed or substituted in accordance with terms, expressions, structures, etc. defined in each system so that the technical idea proposed in the present invention is also embodied in the corresponding system.

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

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

[0043]

Table 4

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

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

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

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

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

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

[0050] - "Antenna ports" field

[0051] - "DMRS sequence initialization" field

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

[0053] A plurality of CCs scheduled simultaneously by m-CC DCI (or a plurality of CCs scheduled by the m-CC DCI) are defined as co-scheduled CCs. The co-scheduled CCs (the CCs belonging to this) are grouped into one or more sub-groups. Also, a separate field is configured for each sub-group. Which CCs belong to each sub-group is preset by higher layer signaling. Each field (the value indicated by this) is commonly applied to the CCs belonging to the sub-group. The sub-group is referred to as a shared CC group. When the attributes of the CCs belonging to the shared CC group are different, a method of commonly applying the DCI field to the CCs will be proposed.

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

[0055]

Table 5

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

[0057] Method 1: shared-cell-common

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

[0059] Method 2: shared-state-extension

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

[0061] Method 3: separate

[0062] The same number of fields as the number of cells (scheduled by the multi-cell DCI and with the operation set by the DCI field instruction) are configured (within the DCI), each individual field corresponds to each of the scheduled cells, and the value indicated by the field is applied to the corresponding cell.

[0063] Method 4: shared-reference-cell

[0064] Only one field is configured within the multi-cell DCI, and the value indicated by the DCI field is applied only to a specific one reference cell (for example, the cell where the DCI is transmitted or the cell with the lowest or highest cell index or the cell indicated by the CIF field value) among the cells (scheduled by the multi-cell DCI and with the operation set by the DCI field instruction), and a specific predefined / default value is applied to the other cells.

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

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

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

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

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

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

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

[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 the cells belonging to the schedulable cell set are grouped into one or more (or a plurality of) sub-groups, and one field (applied commonly) 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 / instruction method based thereon are applied for each sub-group.

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

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

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

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

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

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

[0079] First, the type-1A field or the above-mentioned [shared-cell-common] method (specifically, the [Opt X] method) is proposed more specifically as follows.

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

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

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

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

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

[0085] When applying the Alt-A mode, for a specific cell (cell X, for example, a cell set to N_low where N is a value less than N_max), when a specific state (e.g., a state higher than {N_low - 1}) is indicated by a specific DCI field, there may be no parameter / value or combination thereof set to that state for cell X. Considering this case, the following operations are proposed. For convenience, define M = ceil{log2(N_max)} and K = ceil{log2(N_low)} (M ≥ K). Specifically, in the case of the Precoding information and number of layers field, the state corresponding to the Reserved value may or may not be included in N_max / N_low. Also, hereinafter, the values of the DCI field corresponding to N states / indexes are assumed to be 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 one hand, if a state / index with a value higher than {N_low - 1} is indicated by the K bits, the operations of Alt 3 or Alt 6 are applied.

[0088] B. For example, in the case of the antenna port field, when M = 5 and K = 4 assigned to cell X, only the first or last 4 bits of the 5 bits are utilized to interpret the SRI field.

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

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

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

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

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

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

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

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

[0097] B. For example, in the case of the antenna port field, among the N_low states (excluding the states / indexes for the Reserved values), it is set by a parameter / value or a combination thereof linked to a specific N_gap states.

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

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

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

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

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

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

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

[0105] Furthermore, the method for determining the DCI field size for the type-2 field or the field to which the separation method is applied is specifically proposed as follows.

[0106] In the conventional s-CC DCI, for a specific DCI field, in a state where N states can be indicated by the DCI field, the size of the DCI field is set to L = ceil{log 2 (N)} bits. L is set to a different (or the same) value for each cell. A specific DCI field includes an Antenna ports field, a PTRS-DMRS association field, etc.

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

[0108] For example, in the case of the antenna port field, for each of a plurality (e.g., N_co) of co-scheduled cell combinations set for the entire schedulable cell combination, the sum L_sum of the L values (for the antenna port field) set for each of the cells belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values calculated for each of the N_co co-scheduled cell combinations is determined as the size of the 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 (in particular, cells with CB-based UL set) set for the entire schedulable cell combination, the sum L_sum of the L values (for the PTRS-DMRS related field) set for each of the cells (in particular, cells with CB-based UL set) belonging to the co-scheduled cell combination is calculated. The maximum value among the N_co L_sum values calculated for each of the N_co co-scheduled cell combinations is determined as the size of the 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 cell with respect to a specific DCI field in the m-CC DCI, for this cell, based on the number / set of the states and the field size, the following type-2 field design method is applied. If there is no other setting, based on the N states and the field size L set in the s-CC DCI, the following type-2 field design method is applied.

[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 usage, the maximum rank / layer number, or a valid / invalid row index among the rows of the table corresponding to the cell is defined / set / instructed. When configuring the antenna port field in the m-CC DCI and / or when scheduling multiple CCs by the m-CC DCI, for the cell, based on the given number of DM-RS symbols, the maximum rank / layer number, or a valid / invalid row index among the rows of the table corresponding to the cell, N_cfg states and a field size L_cfg are determined. When configuring the antenna port field in the m-CC DCI and / or when scheduling multiple CCs by the m-CC DCI, for a cell where the number of DM-RS symbols, the maximum rank / layer number, or a valid / invalid row index among the rows of the table corresponding to the cell is not defined / set / instructed, based on the N states and the field size L set in the s-CC DCI, the antenna port field in the m-CC DCI for the cell is configured.

[0114] [1] 「Antenna port」 field

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

[0116]

Table 6-1

Table 6-2

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

[0118] As one way to reduce the field size, the setting / application of the number of DM-RS symbols differs according to the number of cells scheduled by the m-CC DCI (simultaneously). As an example, in the s-CC scheduling case, even if the maxLength value follows a predefined / set value for each cell, in the m-CC scheduling case, only single-symbol DM-RS is restricted to be scheduled. Alternatively, in the scheduling case based on the m-CC DCI, it is always restricted that only single-symbol DM-RS is scheduled. Alternatively, setting constraints are given such that the maxLength value is always set to only 1 for the cells set as the target of the m-CC DCI scheduling. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (the operation according to the DCI field instruction is set) are configured in the DCI. Also, an individual field corresponds to each of the scheduled cells, and the antenna port field is configured in such a way that the value indicated by the field is applied to the cell. Such a field configuration method is called the "Type-2 field design method".

[0119] Constraining to match the number of DM-RS symbols for each cell has the disadvantage of reducing the CDM capacity. Considering this, a separate table for each cell and an individual field corresponding to each cell are configured, and the DM-RS port index for each layer is indicated for each cell by the individual field. A method of reducing the total number of bits required for indicating the DM-RS port index for each layer by adjusting the number of rows in the table for each cell can be considered.

[0120] As an example, as shown in Table 7 below, when specific conditions (if transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=1) are met, signaling for 28 combinations is required. However, when the cell is scheduled by m-CC DCI, only some of the 28 rows corresponding to the 28 combinations can be used to form the table. This can reduce the number of bits required to configure / indicate the "Antenna ports" field / information for the cell. As an example, when only 8 out of 27 rows are selected, only 3 bits instead of 5 bits are required for the DM-RS port index indication for each layer of the cell.

[0121] At this time, for each cell, which row index is selected 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 among the row indexes are selected, only indexes corresponding to multiples of a specific N value are selected, only the lowest indexes of a specific number are selected, or only the highest indexes of a specific number are selected. Specifically, for a specific cell, it is set so that 0 bits are allocated for the indication of the DM-RS port index for each layer. In this case, a specific DM-RS port index is applied to the cell. For example, for the cell, the rule may be predefined so that the DM-RS port index is applied as 0, or which DM-RS port index is used may be predefined.

[0122] On the one hand, the method has different applications (different table sizes) depending on which cell is actually scheduled, and is only applicable to the m-CC scheduling case and may not be applicable to the s-CC scheduling case. As an example, in the s-CC scheduling case, when the cell to which Table 7 below is applied is scheduled, a 5-bit antenna port field is allocated to the cell. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (the operation according to the DCI field instruction is set) are configured in the DCI. Also, each scheduled cell corresponds to an individual field, and the antenna port field is configured in such a way that the value indicated by the field is applied to the cell. Such a method of field configuration is referred to as the "Type-2 field design method".

[0123]

Table 7

[0124] As another method, the setting / application of the maximum rank / layer number varies according to the number of cells scheduled by the m-CC DCI (simultaneously). As an example, in the s-CC scheduling case, even if the maxRank value follows a value predefined / set for each cell, in the m-CC scheduling case, the maxRank value is restricted to K. Alternatively, in the scheduling case based on the m-CC DCI, the maxRank value is always restricted to K. Alternatively, for the cells set as the target of the m-CC DCI scheduling, setting constraints are given so that the maxRank value is always set only to K. The K value is set or defined in advance. As an example, K = 1. In the case of PDSCH, specifically, the constraint on the maxRank value is applied only when only 1-TB is scheduled. For the cells where 2-TB is scheduled, the constraint on the rank value may not be applied. This is because, as shown in Table 8 below, when it is 2-TB (that is, when both two codewords are enabled), there are only 4 corresponding row indexes, so even if the number of row indexes exceeds 4 due to the rank number constraint in the case of 1-TB, the number of bits of the antenna port field does not change. At this time, the same number of fields as the number of cells scheduled by the m-CC DCI (the operation according to the DCI field instruction is set) are configured in the DCI. Also, each of the scheduled cells corresponds to an individual field, and the antenna port field is configured in such a way that the value indicated by the field is applied to the cell. Such a field configuration method is called the "Type-2 field design method".

[0125]

Table 8

[0126] The method for configuring m-CC DCI for the "antenna ports" field proposed in the present invention is that for the scheduled cell, different mapping types (i.e., PDSCH / PUSCH mapping type A and B) are set, and when at least one parameter of dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is set differently for each mapping type, respective methods are 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 the application method of the "Antenna ports" field when different CCs that refer to the table for interpreting the "Antenna ports" field are grouped into a shared CC group.

[0128] First, configuration constraints are imposed such that only CCS of the same type belong to the shared CC group. That is, for all CCS belonging to the shared CC group, a common table is referenced to interpret the "Antenna ports" field. At this time, CCS of the same type means that the settings for 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 (or at least one of such settings) are the same. Which settings should be the same depends on cases such as PDSCH and PUSCH. In the case of PUSCH, constraints are added such that CCS grouped in the shared CC group have the same transmission rank value, so that the tables referenced to interpret the "Antenna ports" field are commonly adjusted. In the case of PDSCH, even if the settings for the dmrs-Type parameter and the settings for the maxLength parameter are the same, the tables referenced for each CC are different depending on whether spatial domain multiplexing (SDM) reception from multi-TRP is configured or not.

[0129] (Opt 1-1) Specifically, only cells with the same setting for the presence or absence of multi-TRP DL reception are constrained to belong to the shared CC group.

[0130] (Opt 1-2) Alternatively, CCS with different settings regarding the reception of multi-TRP DL are also allowed to belong to one shared CC group. In Opt 1-2, when the table referred to by the cell with the multi-TRP DL reception operation set is X (for example, Table 7.3.1.2.2-1A in the TS 38.212 specification), and the table referred to by the cell without the multi-TRP DL reception operation set is Table Y (for example, Table 7.3.1.2.2-1 in the TS 38.212 specification), in the m-CC scheduling case, rules are defined such that for the shared CC group, Table X or Table Y is commonly referred to. At this time, there are different code points between Table X and Table Y, but when the specific code point is indicated, the cell without the multi-TRP DL reception operation set is considered to have no PDSCH scheduling or performs PDSCH reception in a state where a preset / defined antenna port is considered to be indicated. Alternatively, in Opt 1-2, rules are defined to refer only to Table Y (not only for cells without the multi-TRP DL reception operation set but also for cells with the multi-TRP DL reception operation set). For a cell with the multi-TRP DL reception operation set but scheduled by m-CC DCI (or when multiple cells are scheduled simultaneously by m-CC DCI), only single-TRP transmission is allowed.

[0131] (Opt 2-1) As another method, CCS of different types (i.e., not of the same type as described above) are also allowed to belong to the shared CC group. In this case, the configuration of the "Antenna ports" field in the m-CC DCI is omitted (i.e., the field does not exist), and the code point on the "Antenna ports" table required / applied to each CC in the group is restricted to one. The code point is preset or indicated by the MAC.

[0132] (Opt 2-2) In accordance with a specific CC belonging to the shared CC group (parameters and number of code points set for single-cell scheduling of the CC, etc.), for a CC having a type different from the type for which the field and / or the corresponding table are configured, a default code point is applied. The default code point 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, which is required for the CC of the specific type, is set to be the same. For example, the "Antenna ports" field is configured based on the minimum value among the number of code points set for single-cell scheduling for each CC. In this case, for a CC with more code points set than the minimum value (e.g., N), only the code points corresponding to the lowest or highest N indices are indicated.

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

[0135] (Opt 2-2C) When the "Antenna ports" field is configured in the same manner as in Opt 2-2B or when the indicated code points are invalid for a specific CC, the terminal operates to assume / apply a specific code point defined / set in advance for that CC.

[0136] [2] 「DMRS sequence initialization」 field

[0137] When PUSCH is scheduled by s-CC DCI and CP-OFDM is applied (i.e., if transform precoder is disabled), 1 bit is allocated to this field. Alternatively, when PUSCH is scheduled by s-CC DCI and DFT-s-OFDM is applied (i.e., if transform precoder is enabled), 0 bits are allocated to this field. On the other hand, when PDSCH is scheduled by s-CC DCI, 1 bit is always allocated to this field.

[0138] The DMRS sequence initialization field is a Type-1A field, and 1 bit is commonly allocated to cells scheduled by m-CC DCI (simultaneously). In the case of PUSCH, specifically, 1 bit is commonly allocated to cells to which CP-OFDM is applied among these cells. That is, the 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 bits are allocated to this field. On the other hand, when 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 allocated 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 allocated to this field, but this bit is regarded as a reserved bit. Alternatively, a setting constraint is given that DFT-s-OFDM is applied to all cells set by m-CC DCI.

[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 combinations (or 2^K or fewer) of the DM-RS sequence initialization methods for the M cells are preset, and one of these 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 for initializing the DM-RS sequences of the 4 cells are preset. When the m-CC DCI indicates "00", the method for 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 for 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 reference cells among the cells scheduled by the DCI. For the other cells that are not reference cells, the predefined / set method for 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 the field set are grouped into a shared CC group.

[0144] (Opt 3-1) When 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 the said shared CC group), and n_SCID = 0 is always assumed / applied.

[0145] (Opt 3-2) When the "DMRS sequence initialization" field is configured in the m-CC DCI and n_SCID = 1 is indicated, scheduling is considered not to exist for the CC without the "DMRS sequence initialization" field set.

[0146] (Opt 3-3) When the "DMRS sequence initialization" field is configured in the m-CC DCI, n_SCID = 0 is always applied to the CC without the "DMRS sequence initialization" field set (even when n_SCID = 1 is indicated by the said field).

[0147] For the case of DCI for PUSCH scheduling, for the corresponding PUSCH, it is dynamically indicated which of the waveforms of CP-OFDM or DFT-s-OFDM is applied. As an example, by introducing a separate 1-bit indicator, one of the two waveforms is indicated. By utilizing some bits or some code points of an existing field, one of the two waveforms may be indicated. If a 1-bit indicator is introduced into the m-CC DCI, the indication for its dynamic waveform switching (DWS) is commonly applied to all of the co-scheduled CCs (or the CCs among the co-scheduled CCs for which DWS is set). Alternatively, the indication for its dynamic waveform switching is applied only to a specific reference cell, and for cells that are not the reference cell, a specific waveform is applied by a predefined / set method. The reference cell is the cell with the lowest index, the cell with the highest index, the cell with the lowest SCS set, the cell with the highest SCS set, or the scheduling cell where 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 by a predefined / set method. Thus, when the DWS indication is applied to all or some of the co-scheduled CCs, the "DMRS sequence initialization" field is interpreted only for the cells where CP-OFDM is indicated / applied, and for other cells, the "DMRS sequence initialization" field is ignored.

[0148] [3] Field for indicating the association between PTRS and DMRS

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

[0150]

Table 9

[0151] <「PTRS-DMRS association」field>

[0152] If, for all cells that can be (simultaneously) scheduled by m-CC DCI, the condition (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 the sake of convenience, this condition is referred to as condition #A) is satisfied, 0 bits are 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 methods) 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 methods) are allocated to this field, but these 2 bits are regarded as reserved bits. Alternatively, a setting constraint is given such that all cells set by m-CC DCI are set to satisfy condition #A. Alternatively, the s-CC scheduling case does not give the constraint of satisfying condition #A, and only for the m-CC scheduling case, a constraint is given (for example, maxRank = 1) such that the scheduled cells satisfy condition #A.

[0153] As another method, in the case scheduled by m-CC DCI, the field size can be reduced by reducing the number of candidates for the DM-RS port index associated with 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 the field to be associated with one of the four DM-RS ports. However, in m-CC DCI (or in the case of an m-CC scheduling case), PT-RS port 0 is indicated by the corresponding field to be associated with one of the specific two DM-RS ports (e.g., 1 st scheduled DMRS port or 2 nd scheduled DMRS port). In this case, for each cell scheduled by the same m-CC DCI, only 1 bit instead of 2 bits is required for the "PTRS-DMRS association" field for the cell. Alternatively, in order to further reduce the number of bits of the field, in the case scheduled by m-CC DCI (or in the case of an m-CC scheduling case), which DM-RS port is associated with the PT-RS port is preset / defined in advance, and the "PTRS-DMRS association" field for the cell is not allocated.

[0154] In the case scheduled by m-CC DCI (or in the case of m-CC scheduling), the number of bits of the "PTRS-DMRS association" field corresponding to each cell is set in the same way by commonly applying any one of the above methods to the cells scheduled by the same m-CC DCI. Alternatively, the number of bits of the "PTRS-DMRS association" field may be different for each cell by applying different methods for each cell among the above methods to the cells scheduled by the same m-CC DCI. As an example, in the m-CC scheduling case, for a specific reference cell, as in the prior art, 2 bits are assigned to this field, and for other scheduled cells, 0 bits are assigned to this field. The reference cell is defined and / or set as the cell with the lowest cell index, the cell with the highest cell index, the cell with the lowest SCS set, the cell with the highest SCS set, the scheduling cell where the m-CC DCI is transmitted, the cell with the minimum number of SRS resources in the SRS resource set, or the cell with the maximum number of resources in the SRS resource set. For the cell to which 0 bits are assigned to this field, a restriction is set that it should satisfy condition #A or it should be preset / defined which DM-RS port is associated with the PT-RS port. As another example, in the s-CC scheduling case, 2 bits are assigned to this field as in the prior art, and in the m-CC scheduling case (including the 0-bit assignment method), the methods proposed above are 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 a CC with the "PTRS-DMRS association" field set and a CC without the 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 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) If the "PTRS-DMRS association" field is configured in the m-CC DCI and a state of 0 (or only bit "0") is indicated by the field, the specific default DMRS port is assumed / applied for the CC without the "PTRS-DMRS association" field set. If a non-zero state (or at least one bit "1") is indicated, no scheduling is considered for the unconfigured CC.

[0159] (Opt 4-3) If the "PTRS-DMRS association" field is configured in the m-CC DCI, for a CC without the "PTRS-DMRS association" field set, a specific DMRS port (index) is always assumed / applied by 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 to 5-2, CCs with the "PTRS-DMRS association" field set are grouped into a shared CC group. However, a method for applying the "PTRS-DMRS association" field when a CC with one PTRS port and a CC with two PTRS ports are grouped into a shared CC group is proposed.

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

[0162] (Opt 5-2) For the 2 nd (or 1 st ) PTRS ports of a CC with two PTRS ports, they are fixed to a specific DMRS port. The terminal refers to the MSB or LSB (least significant bit) of the "PTRS-DMRS association" field for the 1 st (or 2 nd ) PTRS ports and interprets / applies it to the DMRS port related to the "PTRS-DMRS association" field. Alternatively, for the 1 st (or 2 nd ) PTRS ports, the specific default DMRS port is always fixed and used. In Opt 5-2, the bits remaining unused for the indication of the 1 st (or 2 nd ) PTRS ports of a CC with two PTRS ports are used for the PTRS setting of a CC with one PTRS port.

[0163] As another method, the setting is restricted such that CCS with the same number of PTRS ports are grouped into a shared CC group (i.e., CCS with different numbers of PTRS ports are not grouped into a shared CC group).

[0164] <「Second PTRS-DMRS association」field>

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

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

[0167] The method for configuring m-CC DCI for the field indicating the relationship between PTRS and DMRS proposed in the present invention is that different mapping types (i.e., PDSCH / PUSCH mapping type A and B) are set for the scheduled cells. When at least one parameter of dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is set differently for each mapping type, respective methods are 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 final payload size of the field indicating the relationship between PTRS and DMRS is |X_A - x_B| or (X_A + X_B).

[0168] In Options 6-1 and 6-2, a method for applying the "Second PTRS-DMRS association" field when a CC with multi-TRP UL operation set and a CC without multi-TRP UL operation set are grouped into a shared CC group is proposed.

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

[0170] (Opt 6-2) The field exists or is configured in the m-CC DCI, but the field is ignored for a CC without multi-TRP UL operation set.

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

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

[0173] Embodiment

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

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

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

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

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

[0179] Referring to Opt 2-2A to 2-2C, for cells belonging to the same shared CC group among different cells schedulable by m-CC DCI, one antenna port field is included. The number of bits of one antenna port field is determined based on the maximum value among the number of bits of the antenna port fields set for single cell scheduling for each cell.

[0180] In other words, when the antenna port field is set to Type 1A, it is determined to be the maximum value among M bits associated with N different cells. Referring to Tables 6 and 8, for N cells, the M bits for each cell are determined based on the DMRS type (dmrs-Type) and the 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 PDSCHs on different cells is referred to as DCI format 1_X. X is a natural number of 3 or more. For example, the DCI format of the DCI for scheduling PDSCHs on different cells is DCI format 1_3.

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

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

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

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

[0187] For example, DCI for scheduling PUSCHs on different cells from each other includes any one or more fields of an antenna port, DMRS sequence initialization, PTRS - DMRS related, and a second PTRS - DMRS related field.

[0188] Each DCI field is configured based on any one or more combinations of the methods disclosed in Sections [1] to [3].

[0189] For example, referring to [2], since the DMRS sequence initialization field is a type 1A field, it is included in the m-CC DCI as one field containing common information for the cells scheduled by the m-CC DCI. Since the scheduling is for the PUSCH, the DCI includes one DMRS sequence initialization field containing common information for the PUSCH. Referring to the conventional standard, the sequence of the DMRS transmitted for the PUSCH is generated based on the scrambling ID n_SCID which is determined based on the DMRS sequence initialization field. Specifically, n_SCID is set to 0 or 1 according to the value of the DMRS sequence initialization field.

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

[0191] Also, when CP-OFDM is applied to some of the cells schedulable by the m-CC DCI and DFT-s-OFDM is applied to some others, 1 bit is allocated to this field. Therefore, when the transform precoder is deactivated for at least one of all PUSCHs schedulable by the 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 specific time point, instead of all the cells schedulable by DCI. For example, when DFT-s-OFDM is applied to all the actually scheduled cells, this field may not exist. Thus, when the transform precoders for all the PUSCHs on the cells that are actually scheduled simultaneously among different cells at a specific time point are activated, even if the transform precoders for the PUSCHs that are not actually scheduled simultaneously at a specific time point are deactivated, the DMRS sequence initialization field is composed of 0 bits.

[0193] Conversely, even when DFT-s-OFDM is applied to all the actually scheduled cells, 1 bit may be allocated to this field. However, since there is no cell that uses this 1 bit among the actually scheduled cells, this bit is regarded as a reserved bit. Thus, when the transform precoders for the PUSCHs that are not actually scheduled simultaneously among different cells at a specific time point are deactivated, even if the transform precoders for all the PUSCHs on the cells that are actually scheduled simultaneously at a specific time point are activated, the DMRS sequence initialization field is composed of 1 bit.

[0194] Referring to Opt 3-1 etc., when the DMRS sequence initialization field is 0 bits, the terminal assumes / regards or sets the n_SCID, which is the scrambling ID for DMRS sequence generation, to 0.

[0195] [2] According to the section, in the case of DCI for PUSCH scheduling, for the corresponding PUSCH, it is dynamically indicated which waveform of CP-OFDM or DFT-s-OFDM is applied. For example, the m-CC DCI includes one 1-bit indicator field that contains common information for a plurality of scheduled cells (or PUSCHs scheduled for the cell). Therefore, the 1-bit indicator field corresponds to Type-1A. One 1-bit indicator field indicates dynamic waveform switching with one of CP-OFDM or DFT-s-OFDM for a plurality of scheduled cells (or PUSCHs scheduled for the cell). Since CP-OFDM or DFT-s-OFDM is determined according to the activation or not of the transform precoder, one 1-bit indicator field is understood to dynamically indicate the activation of the transform precoder for a plurality of scheduled cells (or PUSCHs scheduled for the cell).

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

[0197] In other words, the antenna port field is determined to be the maximum value among the M bits related to N different cells when the field is set to Type 1A. Referring to Table 6, for N cells, the M bits for each cell are determined by the corresponding table. The conditions for each corresponding table correspond to the conditions described for each number of bits of DCI format 0_1 in Table 6. For example, for a cell with the condition "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 a cell with the condition "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 among the second antenna port fields, for a specific cell, there may be a case where there is no row index corresponding to a specific value of the antenna port field. According to Opt 2-2B, for a specific cell without a DMRS port value corresponding to one value of the antenna port field, the terminal considers that the PUSCH is not scheduled. Alternatively, according to Opt 2-2C, for a specific cell without a DMRS port value corresponding to one value of the antenna port field, the terminal transmits the PUSCH based on a predefined specific DMRS port value.

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

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

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

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

[0203] Hereinafter, a more specific description will be given with reference to the drawings. In the following figures / descriptions, the same reference numerals exemplify the same or corresponding hardware blocks, software blocks, or functional blocks unless otherwise specifically mentioned.

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

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

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

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

[0208] Example of wireless device to which the present invention is applied

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

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

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

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

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

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

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

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

[0217] Example of utilization of wireless device to which the present invention is applied

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

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

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

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

[0222] Example of vehicle or autonomous driving vehicle to which the present invention is applied

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

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

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

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

[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 features of the present invention. Therefore, the above detailed description should not be construed restrictively in all aspects, but should be considered as exemplary. The scope of the present invention must be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention.

Industrial Applicability

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

Claims

1. A method for a terminal (UE) to transmit a signal in a wireless communication system, comprising: receiving downlink control information (DCI) for scheduling physical downlink shared channels (PUSCHs) on different cells; transmitting the PUSCHs on the different cells based on the DCI, wherein the DCI includes one demodulation reference signal sequence initialization field including common information for the PUSCH, and a sequence of DMRSs associated with each PUSCH of the cell is generated based on the DMRS sequence initialization field; A signal transmission method.

2. Based on activation of a transform precoder for all of the PUSCHs, the DMRS sequence initialization field is composed of 0 bits, and the DMRS for each cell is generated based on a scrambling ID set to 0; The signal transmission method according to claim 1.

3. Based on deactivation of a transform precoder for at least one of the PUSCHs, the DMRS sequence initialization field is composed of 1 bit; The signal transmission method according to claim 1.

4. Based on activation of a transform precoder for all of the PUSCHs on cells actually scheduled simultaneously at a specific time among the different cells, even if the transform precoder for a PUSCH not actually scheduled simultaneously at the specific time is deactivated, the DMRS sequence initialization field is composed of 0 bits, and the DMRS for each cell is generated based on a scrambling ID set to 0; The signal transmission method according to claim 1.

5. Based on deactivation of a transform precoder for a PUSCH not actually scheduled simultaneously at a specific time among the different cells, even if the transform precoder for all of the PUSCHs on cells actually scheduled simultaneously at the specific time is activated, the DMRS sequence initialization field is composed of 1 bit; The signal transmission method according to claim 1.

6. The 1 bit is regarded as a reserved bit. The signal transmission method according to claim 5.

7. The DCI includes one antenna ports field for different cells. The DMRS port value of the DMRS for each cell is determined based on the antenna ports field. One second antenna ports field per cell is set for DCI for PUSCH scheduling within one cell. The number of bits of the antenna ports field is determined based on the maximum value among the number of bits of the set second antenna ports field. The signal transmission method according to claim 1.

8. If there is no DMRS port value corresponding to the one value for a specific cell among the cells, the PUSCH for the specific cell is considered not to be scheduled. The signal transmission method according to claim 7.

9. If there is no DMRS port value corresponding to the one value for a specific cell among the cells, the PUSCH for the specific cell is transmitted based on a predefined specific DMRS port value. The signal transmission method according to claim 7.

10. The DCI includes one 1-bit indicator field including common information for the PUSCH. The 1-bit indicator field dynamically indicates whether a transform precoder for the PUSCH is activated. The signal transmission method according to claim 1.

11. A terminal for receiving a signal in a wireless communication system, comprising: At least one transceiver; At least one processor; At least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform a specific operation. The specific operation includes: Receiving DCI (downlink control information) for scheduling PUSCH (physical downlink shared channel) on different cells; Transmitting PUSCH on the different cells based on the DCI. The DCI includes one DMRS sequence initialization field that contains common information for the PUSCH, and the sequence of DMRSs associated with each PUSCH of the cell is generated based on the DMRS sequence initialization field. Terminal. **Claim 12** An apparatus for a terminal, comprising at least one processor, and at least one computer memory operably connected to the at least one processor and that, when executed, causes the at least one processor to perform operations, the operations including: receiving DCI (downlink control information) for scheduling PUSCH (physical downlink shared channel) on cells that are different from each other; transmitting PUSCH on the cells that are different from each other based on the DCI, wherein the DCI includes one DMRS sequence initialization (demodulation reference signal sequence initialization) field that contains common information for the PUSCH, and the sequence of DMRSs associated with each PUSCH of the cell is generated based on the DMRS sequence initialization field. Apparatus. **Claim 13** A computer-readable non-volatile storage medium including at least one computer program that causes at least one processor to perform operations, the operations including: receiving DCI (downlink control information) for scheduling PUSCH (physical downlink shared channel) on cells that are different from each other; transmitting PUSCH on the cells that are different from each other based on the DCI, wherein the DCI includes one DMRS sequence initialization (demodulation reference signal sequence initialization) field that contains common information for the PUSCH, and the sequence of DMRSs associated with each PUSCH of the cell is generated based on the DMRS sequence initialization field. Storage medium.

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

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

Images