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

Abstract

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

Description

Technical Field

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

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

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

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

[0005] Technical Solution

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

[0007] According to one aspect of the present disclosure, a method for transmitting a signal by a user equipment (UE) in a wireless communication system includes: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; and transmitting the PUSCH on the different cells based on the DCI, wherein the DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, wherein a sequence of the DMRS associated with each PUSCH of the cell is generated based on the DMRS sequence initialization field.

[0008] According to one aspect of the present disclosure, a method for receiving a signal by a base station (BS) in a wireless communication system includes: sending downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on different cells; and receiving the PUSCH on the different cells based on the DCI, wherein the DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and wherein a sequence of the DMRS associated with each PUSCH of the cell is generated based on the DMRS sequence initialization field.

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

[0010] The apparatus may include an autonomously driven vehicle that communicates with at least a UE, a network, and another autonomously driven vehicle other than the communication apparatus.

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

[0012] Technical Effects

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

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

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

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

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

[0018] Figures 4 to 7 A method for transmitting and receiving a signal according to an embodiment of the present disclosure is illustrated.

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

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

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

[0022] 3GPP NR

[0023] -38.211: Physical channels and modulation

[0024] -38.212: Multiplexing and channel coding

[0025] -38.213: Physical layer procedures for control

[0026] -38.214: Physical layer procedures for data

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

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

[0029] Figure 1 The radio frame structure for NR is shown.

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

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

[0032] [Table 1]

[0033]

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

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

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

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

[0038] [Table 2]

[0039]

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

[0041] NR can support various parameter sets (or subcarrier spacing (SCS)) to provide various 5G services. For example, with an SCS of 15 kHz, NR can support wide areas in traditional cellular bands, and with an SCS of 30 or 60 kHz, it can support dense urban areas and wide carrier bandwidths with lower latency. For an SCS of 60 kHz or higher, NR can support bandwidths above 24.25 GHz to overcome phase noise.

[0042] The NR frequency band may be divided into two frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). FR1 and FR2 may be configured as shown in the following Table 3. FR 2 may mean millimeter wave (mmW).

[0043] [Table 3]

[0044]

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

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

[0047] In a wireless communication system, a UE receives information from a BS in a downlink (DL), and the UE transmits information to the BS in an uplink (UL). Information exchanged between the BS and the UE includes data and various control information, and there are various physical channels / signals according to the type / purpose of the information exchanged therebetween. A physical channel corresponds to a set of resource elements (REs) that carry information originating from a higher layer. A physical signal corresponds to a set of REs that are used by the physical layer but do not carry information originating from a higher layer. The higher layer includes a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and the like.

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

[0049] In the present disclosure, a base station (BS) may be, for example, a gNode B (gNB).

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

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

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

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

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

[0055] [Table 4]

[0056]

[0057] In this regard, discussions are ongoing on what is known as "multi-carrier enhancement," which will specify a method for scheduling PUSCH or PDSCH on multiple serving cells through a single DCI.

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

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

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

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

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

[0063] - Antenna Port field

[0064] - "DMRS sequence initialization" field

[0065] - A field indicating the association between the PTRS and the DMRS (eg, a "PTRS-DMRS Association" field, a "Second PTRS-DMRS Association" field)

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

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

[0068] [Table 5]

[0069]

[0070] Corresponding to the respective types in Table 5, the terms described in the present disclosure are the same as those of Methods 1 to 4.

[0071] Method 1: Shared-Community-Public

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

[0073] Method 2: Shared-State-Extension

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

[0075] Method 3: Single

[0076] A method in which a number of fields (within a DCI) equal to the number of cells scheduled by a multi-cell DCI is configured (with operations configured according to corresponding DCI field instructions), a separate field corresponds to each scheduled cell, and a value indicated by the corresponding field is applied to the corresponding cell.

[0077] Method 4: Shared-Reference-Cell

[0078] A method in which only one field is configured within a multi-cell DCI, the value indicated by the corresponding DCI field is applied only to a specific reference cell (e.g., the cell to which the corresponding DCI is sent, the cell with the lowest or highest cell index, or the cell indicated by the CIF field value) (among the cells scheduled by the multi-cell DCI and configured to operate according to the indication of the corresponding DCI field), and a predefined / configured specific default value is applied to the remaining cells.

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

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

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

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

[0083] Alternatively, the reference cell may refer to (i) a cell having the lowest (or highest) cell index within a set of all cells schedulable via any multi-cell DCI (i.e., a schedulable cell set), (ii) a cell indicated by a CIF field value, (iii) a cell to which the multi-cell DCI is sent, or (iv) a cell reserved via RRC.

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

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

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

[0087] A subgroup may also be referred to as a cell subgroup. A cell subgroup may be configured / set with a specific one or multiple specific cells belonging to a common scheduling cell group or a schedulable cell group. For example, a cell subgroup may be configured / set with some or all cells belonging to a common scheduling cell group or a schedulable cell group.

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

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

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

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

[0092] [Public-T1A: Invalid state handling]

[0093] First, the Type 1A field or shared-cell-common method (particularly the Option X method) is presented in more detail below.

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

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

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

[0097] Alt-A) is determined by ceil {log2(N_max)} bits based on a maximum value N_max (in this case it can be a structure indicating up to (first) N_max states / indexes via a DCI field)

[0098] Alt-B) is determined by ceil {log2(N_min)} bits based on the minimum value N_min (in this case it can be a structure where only up to the (first) N_min states / indexes are indicated via the DCI field)

[0099] When the Alt-A method or the Alt-C method is applied, if a specific state (e.g., a state higher than {N_low-1}) is indicated by a specific DCI field for a specific cell (e.g., a cell in which N is set to N_low, where N_low is a value less than N_max), there may not be a parameter / value or a combination thereof configured for the corresponding state for cell X. In view of this situation, the following operation is proposed. For convenience, M = ceil {log2 (N_max)} and K = ceil {log2(N_low)} (M≥ K) are defined. Specifically, for the antenna port field and the number of layers of the precoding information, the state corresponding to the reserved value may or may not be included in N_max / N_low. In the following description, it is assumed that the values ​​of the DCI fields corresponding to N states / indexes are 0, ..., N-1.

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

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

[0102] B. For example, for the antenna port field, when M=5 and K allocated to cell X is K=4, only the first 4 bits or the last 4 bits of the 5 bits may be used to interpret the SRI field.

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

[0104] A. A specific parameter / value or combination thereof may be configured / defined as a specific parameter / value or combination thereof linked to a specific one (eg, the lowest or highest) value of the N_low states pre-configured for cellX.

[0105] B. For example, for the antenna port field, a specific parameter / value or a combination thereof may be configured / defined as a specific SRS resource index linked to a specific state (e.g., lowest or highest) among the N_low states pre-configured for cell X, or a specific SRS resource index (e.g., lowest / highest index) linked to a specific L_max value (e.g., lowest / highest L_max).

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

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

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

[0109] 4) Alt 4: For cell X, {N_max – N_low} = N_gap parameters / values ​​corresponding to each state from N_low to N_max-1 or a combination thereof may be additionally configured and applied.

[0110] A. Additional parameters / values ​​or combinations thereof may be configured to be linked to a specific N_gap state among the N_low states pre-configured for cell X.

[0111] B. For example, for the antenna port field, (multiple) SRS resources linked to a specific state among the preset N_low states may be mapped to N_gap states.

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

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

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

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

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

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

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

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

[0120] In the case of a specific DCI field in an existing s-CC DCI field, when N states are to be indicated by the DCI field, the size of the DCI field may be configured as L = ceil {log2(N)} bits. For each cell, L may be configured as a different (or the same) value. The specific DCI field may include an antenna port field and a PTRS-DMRS association field.

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

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

[0123] For example, for the PTRS-DMRS association field, for each of the multiple (e.g., N_co) common scheduling cell combinations (particularly cells with CB-based UL sets) configured in the entire fully schedulable cell combination, a sum L_sum of L values ​​(for the PTRS-DMRS association field) configured for each of the cells (particularly cells with CB-based UL sets) belonging to the corresponding common scheduling cell combination is calculated. For each of the N_co common scheduling cell combinations, the maximum value of the calculated N_co L_sum values ​​can be determined as the size of the PTRS-DMRS association field (configured in the m-CC DCI).

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

[0125] For a specific DCI field (antenna port, PTRS-DMRS associated field, etc.) to which the type 2 field design method is applied, the N_cfg state indicated by the corresponding DCI field in the m-CC DCI and the corresponding field size L_cfg = ceil {log2(N_cfg)} can be configured separately. In this case, it can be configured in the form of N_cfg < N and / or L_cfg < L. The type 2 field design method may include a shared-cell-common method based on DCI field size determination and / or an option X method. The N_cfg state and the corresponding field size L_cfg may be configured for each cell.

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

[0127] For example, for the antenna port field, the number of DM-RS symbols for m-CC DCI purposes, the maximum number of ranks / layers, or the valid / invalid row index from the row of the table corresponding to the corresponding cell may be defined / configured / indicated for a specific cell X. When the antenna port field in the m-CC DCI is configured and / or multiple CCs are scheduled through the m-CC DCI, N_cfg states and a field size L_cfg are determined for the corresponding cell based on a given number of DM-RS symbols, the maximum number of ranks / layers, or the valid / invalid row index from the row of the table corresponding to the corresponding cell. When the antenna port field in the m-CC DCI is configured and / or multiple CCs are scheduled through the m-CC DCI, for cells that do not define / configure / indicate the number of DM-RS symbols, the maximum number of ranks / layers, or the valid / invalid row index from the row of the table corresponding to the corresponding cell, the antenna port field in the m-CC DCI for the cell may be configured based on the N states and field size L configured in the s-CC DCI.

[0128] [1] Antenna Port field

[0129] Table 6 shows the antenna port field of each DCI format disclosed in the 3GPP TS 38.212 document.

[0130] [Table 6]

[0131]

[0132]

[0133]

[0134] For the rank / number of layers determined by the SRI and / or precoding information field and the number of layers, the corresponding DM-RS port index of each layer can be determined by the corresponding field.

[0135] As a method of reducing the size of the corresponding field, the number of DM-RS symbols may be configured / applied differently depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the case of s-CC scheduling, even if the maxLength value follows a predefined / configured value for each cell, only single-symbol DM-RS may be constrained for scheduling in the case of m-CC scheduling. Alternatively, in the case of m-CC DCI-based scheduling, only single-symbol DM-RS may be constrained to always be scheduled. Alternatively, a configuration constraint may be imposed such that the maxLength value is always configured to 1 for cells configured as m-CC DCI scheduling targets. In this case, a number of fields equal to the number of cells scheduled by the m-CC DCI is configured within the corresponding DCI (configuration operations are performed for it according to the corresponding DCI field instructions). The antenna port field can be configured in such a way that each scheduled cell corresponds to a separate field, and the value indicated by the corresponding field is applied to the corresponding cell. This method of configuring fields is referred to as a "type 2 field design method".

[0136] If the number of DM-RS symbols per cell is limited, there may be a disadvantage of reduced CDM capacity. In view of this, a separate table and a separate field corresponding to each cell may be configured for each cell, and the DM-RS port index of each layer may be indicated for each cell through a separate field. A method of reducing the total number of bits required for the DM-RS port index indication of each layer by adjusting the number of rows of the table for each cell may be considered.

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

[0138] In this case, for each cell, only which row indexes are selected from the rows of the existing table to reduce the table size, and the bits can be individually or predefined. For example, only even row indexes can be selected, only indexes that are multiples of a specific value N can be selected, only a specific number of lowest indexes can be selected, or only a specific number of highest indexes can be selected. Specifically, for a specific cell, the 0 bit can be configured to be allocated for a layer-specific DM-RS port index indication. In this case, a specific DM-RS port index can be applied to the corresponding cell. For example, a rule can be preconfigured so that the DM-RS port index is applied as 0 for the corresponding cell, or which DM-RS port index to use can be preconfigured.

[0139] This method may be applied differently depending on which cells are actually scheduled (the size of the table may be different), and may be applied only to the m-CC scheduling case and not to the s-CC scheduling case. For example, in the s-CC scheduling case, when scheduling a cell to which the following Table 7 is applied, a 5-bit antenna port field may be allocated to the corresponding cell. In this case, a number of fields equal to the number of cells scheduled by the m-CC DCI is configured within the corresponding DCI (configuration operations are performed for it according to the corresponding DCI field instructions). The antenna port field can be configured in such a way that each scheduled cell corresponds to a separate field, and the value indicated by the field is applied to the corresponding cell, and this field configuration method is referred to as a "Type 2 field design method".

[0140] [Table 7]

[0141]

[0142] As another example, the maximum number of ranks / layers may be configured / applied differently depending on the number of cells scheduled (simultaneously) by the m-CC DCI. For example, in the case of s-CC scheduling, even if the maxRank value follows a predefined / configured value for each cell, in the case of m-CC scheduling, the maxRank value may be constrained to K. Alternatively, in the case of m-CC DCI-based scheduling, the maxRank value may always be constrained to K. Alternatively, a configuration constraint may be imposed so that for cells configured as m-CC DCI scheduling targets, the maxRank value is always configured to K. The K value may be configured or predefined. For example, K=1. For PDSCH, constraints on the maxRank value may be applied only when only 1-TB is scheduled. For cells scheduled with 2-TB, constraints on the rank value may not be applied. This is because, as shown in Table 8 below, in the case of 2-TB (i.e., both codewords are enabled), there are only 4 corresponding row indices, and therefore even if the corresponding row index is greater than 4 due to the rank count constraint in the case of 1-TB, the number of bits in the corresponding antenna port field may not change. In this case, the number of fields equal to the number of cells scheduled by the m-CC DCI is configured within the corresponding DCI (for which the configuration operation is performed according to the corresponding DCI field instruction). The antenna port field can be configured in such a way that each scheduled cell corresponds to a separate field, and the value indicated by the corresponding field is applied to the corresponding cell. This method of configuring the field is called a "type 2 field design method".

[0143] [Table 8]

[0144]

[0145]

[0146] When different mapping types (ie, PDSCH / PUSCH mapping types A and B) are configured for the scheduling cell and at least one parameter from dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is configured differently for each mapping type, the m-CC DCI configuration method for the "antenna port" field proposed in the present disclosure can be applied to each of 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 port" field can be |X_A-X_B| or (X_A+X_B).

[0147] Options 1-1 to 2-2C disclose a method of applying the "antenna port" field when different CCs that refer to different tables are grouped into a shared CC group when interpreting the "antenna port" field.

[0148] First, constraints can be imposed on the settings so that only CCs of the same type belong to a shared CC group. That is, for all CCs belonging to a shared CC group, a common table is referenced when the "antenna port" field is interpreted. In this case, CCs of the same type mean that the transform precoding configuration and / or the configuration of the dmrs-Type parameter and / or the configuration of the tp-pi2BPSK parameter and / or the configuration of the maxLength parameter (or at least one of these configurations) are the same. Which configurations need to be the same may differ depending on the situation, such as PDSCH and PUSCH. In the case of PUSCH, constraints are added to ensure that the CCs grouped into a shared CC group have the same transmission rank value, and therefore the tables referenced when interpreting the "antenna port" field can be publicly aligned. In the case of PDSCH, even if the configurations of the dmrs-Type parameter and the maxLength parameter are the same, the table configured to be referenced by each CC may be different depending on whether spatial domain multiplexing (SDM) reception from multiple TRPs is configured.

[0149] (Option 1-1) In detail, whether to configure multi-TRP DL reception can be limited to cells belonging to a shared CC group.

[0150] (Option 1-2) Alternatively, CCs with different configurations for multi-TRP DL reception may be allowed to belong to a single shared CC group. In Option 1-2, when the table referenced by a cell configured with multi-TRP DL reception operation is referred to as Table X (e.g., Table 7.3.1.2.2-1A of the TS 38.212 specification) and the table referenced by a cell not configured with multi-TRP DL reception operation is referred to as Table Y (e.g., Table 7.3.1.2.2-1 of the TS 38.212 specification), a rule may be established in the case of m-CC scheduling to commonly reference Table X or Table Y for the corresponding shared CC group. In this case, when there are different code points between Table X or Table Y, and when a specific code point is indicated, the cell not configured with multi-TRP DL reception operation performs PDSCH reception as if there is no PDSCH scheduling or as if a pre-configured / defined antenna port is indicated. Alternatively, in option 1-2, rules can be defined to refer only to Table Y (not only for cells in which multi-TRP DL reception operation is not configured, but also for cells in which multi-TRP DL reception operation is configured), so that when scheduled with m-CC DCI (or when multiple cells are simultaneously scheduled via m-CC DCI), the cell in which multi-TRP DL reception operation is configured may allow only a single TRP transmission.

[0151] (Option 2-1) As another method, CCs of different types (ie, not the same type as described above) may be allowed to belong to a shared CC group. In this case, the "antenna port" field configuration in the m-CC DCI is omitted (ie, the field does not exist), and the required / applied code point for each CC in the group (in the "antenna port" table) is limited to 1. The corresponding code point may be pre-configured or indicated via MAC.

[0152] (Option 2-2) The corresponding field and / or the corresponding table are configured according to a specific CC of a specific type belonging to a shared CC group (parameters configured for single-cell scheduling of the CC and the number of code points, etc.). A CC of a type different from the corresponding type may apply a default code point. The default code point may be pre-configured or indicated via MAC.

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

[0154] (Option 2-2B) The "Antenna Port" field may be configured based on the maximum number of code points configured for single-cell scheduling of each CC. If the code point indicated by this field is invalid for a specific CC, scheduling for that CC is not considered.

[0155] (Option 2-2C) The "Antenna Port" field is configured in the same manner as Option 2-2B above, but if the indicated code point is not valid for a specific CC, the UE may operate to assume / apply a specific code point predefined / configured for the CC.

[0156] [2] "DMRS Sequence Initialization" field

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

[0158] The DMRS sequence initialization field is a type 1A field, which usually allocates 1 bit for the cell scheduled by m-CC DCI (simultaneously), and in the case of PUSCH, usually 1 bit can be allocated for the cell applying CP-OFDM in the corresponding cell. That is to say, the indicated value of "0" or "1" can be applied to all cells being scheduled (all cells applying CP-OFDM in the case of PUSCH).

[0159] For PUSCH, if DFT-s-OFDM is applied to all cells to be scheduled by m-CC DCI, 0 bit can be allocated to the corresponding field. When CP-OFDM is applied to some cells to be scheduled via m-CC DCI and DFT-s-OFDM is applied to the remaining cells, 1 bit can be allocated to the corresponding field. When DFT-s-OFDM is applied to all actually scheduled cells, there may be no corresponding field. Alternatively, if DFT-s-OFDM is applied to all actually scheduled cells, 1 bit is allocated to the corresponding field, but the corresponding bit can be regarded as a reserved bit. Alternatively, configuration constraints can be imposed such that all cells configured with m-CC DCI apply DFT-s-OFDM.

[0160] When M cells are to be scheduled (which can refer to M CP-OFDM cells in the case of PUSCH), and the corresponding field is configured with less than K (<M) bits, 2^K (or less than 2^K) combinations of the DM-RS sequence initialization methods for the M cells are pre-configured, and one of the combinations can be indicated by m-CC DCI. For example, in the case of PDSCH, when M = 4 and K = 2, for each of the cases of "00" / "01" / "10" / "11", the DM-RS sequence initialization methods for the four cells are pre-configured. When m-CC DCI indicates "00", the DM-RS sequence initialization method corresponding to the corresponding code point can be applied to each of the M cells.

[0161] As another method, for m-CC DCI, there may be no corresponding field. In this case, the pre-defined / configured DM-RS sequence initialization method can be applied to each scheduled cell. This method (without configuring / indicating the field / information within m-CCDCI) can be applied only to the m-CC scheduling case. In the s-CC scheduling case (or when CP-OFDM is applied to a single scheduled cell), 1-bit field / information can be configured / indicated in the DMRS sequence initialization field.

[0162] Alternatively, in the case where only one field is configured in the m-CC DCI, the DM-RS sequence initialization information may be indicated only for a specific reference cell among the cells scheduled by the corresponding DCI (through this field). For the remaining cells that are not reference cells, a predefined / configured DM-RS sequence initialization method may be applied.

[0163] Options 3-1 to 3-3 disclose a method of applying the “DMRS sequence initialization” field when a CC configured with the “DMRS sequence initialization” field and a CC not configured with the “DMRS sequence initialization” field are grouped into a shared CC group.

[0164] (Option 3-1) When CCs configured with the "DMRS sequence initialization" field and CCs not configured with this field are grouped into a shared CC group, the "DMRS sequence initialization" field is omitted in the m-CC DCI (for the shared CC group) and n_scid=0 is always assumed / applied.

[0165] (Option 3-2) When the "DMRS sequence initialization" field is configured in the m-CC DCI and n_SCID=1 is indicated, it is considered that there is no scheduling for the CC for which the "DMRS sequence initialization" field is not configured.

[0166] (Option 3-3) When the "DMRS sequence initialization" field is configured in the m-CC DCI, n_SCID=0 may always be applied to CCs for which the "DMRS sequence initialization" field is not configured (even if n_SCID=1 is indicated by the corresponding field).

[0167] In the case of DCI for PUSCH scheduling, it is possible to dynamically indicate which waveform among CP-OFDM or DFT-s-OFDM will be applied to the corresponding PUSCH. For example, one of the two waveforms can be indicated by introducing a separate 1-bit indicator. One of the two waveforms can be indicated by utilizing some bits or some code points of the existing field. If a 1-bit indicator is introduced in the m-CC DCI, the indication for dynamic waveform switching (DWS) can be commonly applied to all publicly scheduled CCs (or CCs configured with DWS among publicly scheduled CCs). Alternatively, the instruction for dynamic waveform switching can be applied only to a specific reference cell, and a specific waveform can be applied to a non-reference cell in a predefined / configured manner. The reference cell can be a cell with the lowest index, a cell with the highest index, a cell configured with the lowest SCS, a cell configured with the highest SCS, or a scheduling cell that sends the m-CC DCI. For the m-CC DCI, the corresponding DWS instruction field can be omitted, and a specific waveform for each cell can be applied by a predefined / configured method. Therefore, when the DWS command applies only to all or some commonly scheduled CCs, the "DMRS sequence initialization" field is interpreted only for cells indicating / applying CP-OFDM, and can be ignored for other cells.

[0168] [3] Field indicating the association between PTRS and DMRS

[0169] Table 9 shows fields indicating association between PTRS and DMRS disclosed in 3GPP TS 38.212 document.

[0170] [Table 9]

[0171]

[0172] <PTRS-DMRS Association field>

[0173] If the condition that 0 bits are allocated to the field of all cells to be scheduled (simultaneously) via m-CC DCI is met (if PTRS-UplinkConfig is not configured in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and the transform precoder is disabled, or if the transform precoder is enabled, or if maxRank=1) (for convenience, the condition is named condition #A), 0 bits may be allocated to the field. When some cells to be scheduled via m-CC DCI meet condition #A and the remaining cells do not meet condition #A, 2 bits (or 1 bit combined with the following method) may be allocated to the corresponding field. If the actually scheduled cell meets condition #A, the corresponding field may not exist. Alternatively, if the actually scheduled cell meets condition #A, 2 bits (or 1 bit combined with the following method) are allocated to the corresponding field, but these 2 bits may be considered as reserved bits. Alternatively, a configuration constraint may be imposed so that all cells configured with m-CC DCI are configured to meet condition #A. Alternatively, the s-CC scheduling case may be constrained to satisfy condition #A (eg, maxRank=1) only for cells scheduled in the m-CC scheduling case, without imposing any constraint on whether condition #A is satisfied.

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

[0175] In the case of scheduling using 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 can be configured to be the same by applying one of these methods to the cells scheduled by the same m-CC DCI in common. Alternatively, by applying different methods in the method to cells scheduled by the same m-CC DCI, the number of bits in the "PTRS-DMRS association" field can be different for each cell. For example, in the case of m-CC scheduling, 2 bits can be allocated to the corresponding field for a specific reference cell as described above, and 0 bits can be allocated to the corresponding field for other scheduled cells. The reference cell can be defined and / or configured as a cell with the lowest cell index, a cell with the highest cell index, a cell with the lowest SCS set, a cell with the highest SCS set, a scheduling cell that sends m-CC DCI, a cell with the smallest number of SRS resources in an SRS resource set, or a cell with the largest number of resources in an SRS resource set. For cells that allocate 0 bits to the corresponding field, which DM-RS port is associated with which PT-RS port can be pre-configured or the constraints of condition #A can be satisfied. As another example, in the case of s-CC scheduling, 2 bits are allocated to the field as described above, and in the case of m-CC scheduling, the proposed method (including the 0-bit allocation method) can be commonly or differently applied to multiple cells.

[0176] [Table 10]

[0177]

[0178] Options 4-1 to 4-3 disclose a method of applying the “PTRS-DMRS Association” field when a CC configured with the “PTRS-DMRS Association” field and a CC not configured with the “PTRS-DMRS Association” field are grouped into a shared CC group.

[0179] (Option 4-1) When CCs configured with the "PTRS-DMRS Association" field and CCs not configured with this field 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 can be, for example, "0 or the first scheduled DMRS port".

[0180] (Option 4-2) If the "PTRS-DMRS Association" field is configured in the m-CC DCI and indicates state 0 (or only bit "0"), a specific default DMRS port is assumed / applied to CCs for which the "PTRS-DMRS Association" field is not configured. If a non-zero state (or at least one bit "1") is indicated, scheduling for unconfigured CCs is not considered.

[0181] (Option 4-3) For CCs that have the "PTRS-DMRS Association" field configured in the m-CC DCI and the "PTRS-DMRS Association" field not configured, a specific DMRS port (index) is always assumed / applied based on the configuration, regardless of the state (or bit) indicated by the corresponding field. The default DMRS port may be, for example, "0 or the first scheduled DMRS port".

[0182] As another example, in options 5-1 and 5-2, CCs configured only with the "PTRS-DMRS Association" field are grouped into a shared CC group, but a method of applying the "PTRS-DMRS Association" field is proposed when grouping a shared CC group between a CC configured with one PTRS port and a CC configured with two PTRS ports.

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

[0184] (Option 5-2) The second (or conversely, the first) PTRS port of a CC configured with two PTRS ports is fixed to a specific DMRS port. The UE may interpret / apply the "PTRS-DMRS Association" field to the associated DMRS port by referring to the MSB or the least significant bit (LSB) of the "PTRS-DMRS Association" field of the first (or conversely, the second) PTRS port. Alternatively, for the 1st (or conversely, the 2nd) PTRS port, a specific default DMRS port may always be fixed and used. In Option 5-2, the remaining bits not used in the first (or second) PTRS port indication of a CC configured with two PTRS ports may be used for the PTRS configuration of a CC configured with one PTRS port.

[0185] As another method, the configuration may be restricted so that only CCs configured with the same number of PTRS ports are grouped into a shared CC group (ie, CCs configured with different numbers of PTRS ports are not grouped into a shared CC group).

[0186] <"Second PTRS-DMRS Association" field>

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

[0188] Alternatively, when it is indicated (by this method) that the second SRS resource set is valid on a cell scheduled by an m-CC scheduling case or an s-CC scheduling case but there is no corresponding field, the association between the PT-RS and DM-RS ports of the corresponding cell may be predefined / configured or updated by a MAC CE or the like. As a method, the UE may consider that the association between the same PT-RS port and DM-RS port is indicated in the "PTRS-DMRS Association" field (for the corresponding cell). Alternatively, it may be preconfigured / defined which PT-RS port and DM-RS port association will apply to which second SRS resource set.

[0189] When different mapping types (ie, PDSCH / PUSCH mapping types A and B) are configured for the scheduling cell and at least one parameter from dmrs-Type and / or dmrs-AdditionalPosition and / or maxLength is configured differently for each mapping type, the m-CC DCI configuration method for the field indicating the association between PTRS and DMRS proposed in the present disclosure may be applied to each of 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 association between PTRS and DMRS may be |X_A-X_B| or (X_A+X_B).

[0190] In options 6-1 and 6-2, a method of applying the "Second PTRS-DMRS Association" field when a CC configured with multi-TRP UL operation and a CC not configured with multi-TRP UL operation are grouped into a shared CC group is proposed.

[0191] (Option 6-1) When a CC configured with multi-TRP UL operation and a CC not configured with multi-TRP UL operation are grouped into a shared CC group, the corresponding field configuration in the m-CC DCI may be omitted, and the operation (related to the association between PTRS and DMRS) of the CC configured with multi-TRP UL operation may be predefined or indicated by the MAC CE. Alternatively, the value indicated via the "PTRS-DMRS Association" field may be equally applied to the second TRP.

[0192] (Option 6-2) A corresponding field may be present or configured in the m-CC DCI, but may be ignored for CCs that are not configured with multi-TRP UL operation.

[0193] The content of the present disclosure is not limited to being applied only to UL and / or DL ​​signal transmission and reception. For example, the content of the present disclosure can also be used for direct communication between UEs. In this document, the term base station (BS) can be understood as including the concept of a relay node as well as a BS. For example, the operation of the BS described in the present disclosure can be performed by a relay node as well as a BS.

[0194] Obviously, each example of the proposed method may also be included as an implementation method of the present disclosure, and thus each example may be considered as a proposed method. Although the above-mentioned proposed methods may be implemented independently, some of the proposed methods may be combined and implemented. In addition, it may be provided that information on whether to apply the proposed method (or information on rules related to the proposed method) is sent from the BS to the UE in a predefined signal (e.g., physical layer signaling or higher layer signaling).

[0195] Implementation Example

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

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

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

[0199] Apart from Figure 4 and / or Figure 5In addition to the operations of “DCI for scheduling PDSCH or PUSCH on multiple serving cells” and one or more operations described in sections [1] to [3] may be additionally performed.

[0200] For example, DCI for scheduling PDSCH on different cells may include one or more fields of antenna port and DMRS sequence initialization.

[0201] Referring to options 2-2A to 2-2C, for cells belonging to the same shared CC group from among different cells schedulable by m-CC DCI, one antenna port field is included. The bits in one antenna port field are determined based on the maximum number of bits in the antenna port field configured for single-cell scheduling of each cell.

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

[0203] Referring to Section [2], for the m-CC DCI scheduling PDSCH, the DMRS sequence initialization field may be determined to be 1 bit.

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

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

[0206] refer to Figure 6 , the method according to an embodiment of the present disclosure may be performed by a UE, and may include receiving DCI for scheduling a PUSCH on different cells ( S601 ) and transmitting a PUSCH on different cells based on the DCI ( S603 ).

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

[0208] Apart from Figure 6 and / or Figure 7 In addition to the operations of “DCI for scheduling PDSCH or PUSCH on multiple serving cells” and one or more operations described in sections [1] to [3] may be additionally performed.

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

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

[0211] For example, referring to Section [2], the DMRS sequence initialization field is a type 1A field and is therefore included in the m-CC DCI as a field containing common information for the cell scheduled by the m-CC DCI. The scheduling is for PUSCH, and therefore the DCI includes a DMRS sequence initialization field containing common information for PUSCH. Referring to the conventional standard, a DMRS sequence transmitted for PUSCH may be generated based on n_SCID, which is a scrambling ID determined based on the DMRS sequence initialization field. In detail, n_SCID is configured to be 0 or 1 according to the value of the DMRS sequence initialization field.

[0212] For PUSCH, if DFT-s-OFDM is applied to all cells to be scheduled by m-CC DCI, 0 bits may be allocated to the corresponding field. Therefore, when the transform precoder is activated for all PUSCHs to be scheduled by DCI, the DMRS sequence initialization field is determined to be 0 bits.

[0213] When CP-OFDM is applied to some cells to be scheduled by m-CC DCI and DFT-s-OFDM is applied to the remaining cells, 1 bit may be allocated to the corresponding field. Therefore, when the transform precoder is deactivated for at least one of the PUSCHs to be scheduled by DCI, the DMRS sequence initialization field is determined to be 1 bit.

[0214] The size of the DMRS sequence initialization field can be determined based on the cells that are actually scheduled simultaneously at a specific point in time rather than all cells to be scheduled via DCI. For example, when DFT-s-OFDM is applied to all actually scheduled cells, there may be no corresponding field. Therefore, if the transform precoders of all PUSCHs on cells that are actually publicly scheduled from different cells are activated at a certain point in time, the DMRS sequence initialization field can be configured with 0 bits even if the transform precoders of PUSCHs that are not actually publicly scheduled at a certain point in time are deactivated.

[0215] On the contrary, even if DFT-s-OFDM is applied to all actually scheduled cells, 1 bit can be allocated to the corresponding field. However, there is no cell using the corresponding 1 bit in the actually scheduled unit, so the corresponding bit can be considered as a reserved bit. Therefore, if the transform precoder for PUSCH that is not actually scheduled simultaneously from different cells at a specific point in time is deactivated, even if the transform precoder for all PUSCHs on cells that are actually scheduled simultaneously at a specific point in time is activated, the DMRS sequence initialization field is configured as 1 bit.

[0216] Referring to option 3-1 and the like, when the DMRS sequence initialization field is 0 bits, the UE may assume / consider or configure n_SCID, which is a scrambling ID for DMRS sequence generation, to 0.

[0217] According to Section [2], in the case of DCI for PUSCH scheduling, it is possible to dynamically indicate which waveform from CP-OFDM or DFT-s-OFDM will be applied to the corresponding PUSCH. For example, the m-CC DCI includes a 1-bit indicator field that contains common information for multiple scheduled cells (or PUSCH scheduled to the corresponding cell). Therefore, the 1-bit indicator field corresponds to type 1A. A single 1-bit indicator field can indicate a dynamic waveform switching to CP-OFDM or DFT-s-OFDM for multiple scheduled cells (or PUSCH scheduled to the corresponding cell). CP-OFDM or DFT-s-OFDM is determined based on whether the transform precoder is activated, and therefore one 1-bit indicator field can be understood as dynamically indicating whether the transform precoder is activated for multiple scheduled cells (or for PUSCH scheduled to the corresponding cell).

[0218] Referring to options 2-2A to 2-2C in section [1], for the antenna port field related to PUSCH, one antenna port field may be included for cells belonging to the same shared CC group from among different cells schedulable by m-CC DCI. The number of bits in one antenna port field is determined based on the maximum number of bits in the antenna port field configured for single-cell scheduling of each cell.

[0219] In other words, when the corresponding field is configured as type 1A, the antenna port field is determined by the maximum value of M bits associated with N different cells. Referring to Table 6, for N cells, the M bits of each cell are determined according to the corresponding table. The corresponding table-specific conditions correspond to the conditions described for each bit of DCI format 0_1 ​​in Table 6. For example, for a cell with "if the transform precoder is enabled, dmrs-Type=1 and maxLength=1, in addition to configuring both dmrs-UplinkTransformPrecoding and tp-pi2BPSK and using π / 2 BPSK modulation", the antenna port field is configured with 2 bits. For a cell with "if the transform precoder is disabled, dmrs-Type=2 and maxLength=2, and if the higher layer parameter txConfig=nonCodebook, the rank value is determined according to the SRS resource indicator field, and if the higher layer parameter txConfig=codebook, the rank value is determined according to the precoding information and the number of layers field", the antenna port field is configured with 5 bits.

[0220] Here, the antenna port field is configured based on the maximum bit in the second antenna port field, so there may be a case where there is no row index corresponding to a specific value of the antenna port field for a specific cell. According to option 2-2B, for a specific cell where there is no DMRS port value corresponding to one of the values ​​of the antenna port field, the UE may consider that the PUSCH is not scheduled. Alternatively, according to option 2-2C, for a specific cell that does not have a DMRS port value corresponding to one of the values ​​of the antenna port field, the UE may transmit the PUSCH based on a predefined specific DMRS port value.

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

[0222] In addition to reference Figures 4 to 7 In addition to the operations described, you can also perform reference Figures 1 to 3One or more operations described and / or operations described in “DCI for scheduling PDSCH or PUSCH on multiple serving cells” and sections [1] to [3].

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

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

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

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

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

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

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

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

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

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

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

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

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

[0236] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be included in one or more processors 102 and 202 or may be stored in one or more memories 104 and 204 and driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, instructions and / or instruction sets using firmware or software.

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

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

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

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

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

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

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

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

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

[0246] Reference Fig.11 The vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Fig.10 Block 110 / 130 / 140.

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

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

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

[0250] Industrial Applicability

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

Claims

1. A method for transmitting a signal by a user equipment (UE) in a wireless communication system, the method comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; as well as sending the PUSCH on the different cells based on the DCI, The DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and Wherein, based on the DMRS sequence initialization field, a sequence of DMRS associated with each PUSCH of the cell is generated.

2. The method according to claim 1, wherein: Upon activation of the transform precoder for all PUSCHs, the DMRS sequence initialization field is configured with 0 bits, and The DMRS for each of the cells is generated based on a scrambling ID configured as 0.

3. The method according to claim 1, wherein: The DMRS sequence initialization field is configured with 1 bit based on deactivation of a transform precoder for at least one of the PUSCHs.

4. The method according to claim 1, wherein: Based on the transform precoder for all PUSCHs on a cell that is actually commonly scheduled among different cells being activated at a specific time point, even if the transform precoder for a PUSCH that is not actually commonly scheduled at the specific time point is deactivated, the DMRS sequence initialization field is configured with 0 bits, and The DMRS for each of the cells is generated based on a scrambling ID configured as 0.

5. The method according to claim 1, wherein: Based on the fact that the transform precoder for PUSCHs that are not actually scheduled simultaneously among different cells is deactivated at a specific time point, even if the transform precoder for all PUSCHs on the cells that are actually scheduled in common at the specific time point is activated, the DMRS sequence initialization field is configured with 1 bit.

6. The method according to claim 5, wherein: The 1 bit is considered as a reserved bit.

7. The method according to claim 1, wherein: The DCI includes an antenna port field for the different cells, wherein, based on the antenna port field, a DMRS port value of the DMRS for each cell in the cell is determined, Wherein, a second antenna port field of each cell is configured for DCI for scheduling PUSCH in a cell, and The bit of the antenna port field is determined based on a maximum value among the configured bits of the second antenna port field.

8. The method according to claim 7, wherein: Based on the absence of a DMRS port value corresponding to one of the values ​​for a specific cell among the cells, the PUSCH for the specific cell is considered to be unscheduled.

9. The method according to claim 7, wherein: Based on the absence of a DMRS port value corresponding to one of the values ​​for a specific cell among the cells, the PUSCH for the specific cell is transmitted based on a predefined specific DMRS port value.

10. The method according to claim 1, wherein: The DCI includes a 1-bit indicator field, the 1-bit indicator field contains common information for the PUSCH, and The 1-bit indicator field dynamically indicates whether the transform precoder for the PUSCH is activated.

11. A user equipment (UE) for receiving a signal in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as At least one memory, the at least one memory being operably connected to the at least one processor and configured to store instructions, the instructions causing the at least one processor to perform specific operations when executed, the specific operations comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; and sending the PUSCH on the different cells based on the DCI, The DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and Wherein, based on the DMRS sequence initialization field, a sequence of DMRS associated with each PUSCH of the cell is generated.

12. An apparatus for a user equipment (UE), the apparatus comprising: at least one processor; as well as at least one computer memory operably connected to the at least one processor and configured to, when executed, cause the at least one processor to perform operations comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; and sending the PUSCH on the different cells based on the DCI, The DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and Wherein, based on the DMRS sequence initialization field, a sequence of DMRS associated with each PUSCH of the cell is generated.

13. A computer-readable non-volatile storage medium comprising at least one computer program for causing at least one processor to perform operations comprising: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PUSCH) on different cells; as well as sending the PUSCH on the different cells based on the DCI, The DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and Wherein, based on the DMRS sequence initialization field, a sequence of DMRS associated with each PUSCH of the cell is generated.

14. A method for receiving a signal by a base station (BS) in a wireless communication system, the method comprising: Sending downlink control information (DCI) for scheduling the physical downlink shared channel (PDSCH) on different cells; as well as receiving the PUSCH on the different cell based on the DCI, The DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and Wherein, based on the DMRS sequence initialization field, a sequence of DMRS associated with each PUSCH of the cell is generated.

15. A base station (BS) for transmitting a signal in a wireless communication system, the BS comprising: at least one transceiver; at least one processor; as well as At least one memory, the at least one memory being operably connected to the at least one processor and configured to store instructions, the instructions causing the at least one processor to perform specific operations when executed, the specific operations comprising: Sending downlink control information (DCI) for scheduling physical downlink shared channels (PDSCH) on different cells; and receiving the PUSCH on the different cell based on the DCI, The DCI includes a demodulation reference signal (DMRS) sequence initialization field, the DMRS sequence initialization field includes common information for the PUSCH, and Wherein, based on the DMRS sequence initialization field, a sequence of DMRS associated with each PUSCH of the cell is generated.

Images