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

Abstract

According to at least one of the embodiments disclosed in the present invention, in a wireless communication system, a method for a terminal to receive a signal includes: receiving information regarding one or more CC lists for configuring one or more CC (component carrier) groups; receiving DCI (downlink control information) including TCI (transmission configuration indication) information on a first CC; and simultaneously updating at least one TCI (transmission configuration indication) state for each of all CCs belonging to a first CC group identical to the first CC based on the TCI information included in the DCI, wherein the correspondence between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling.

Description

[Technical Field]

[0001] The present invention relates to wireless communication systems, and more particularly to a method and apparatus for transmitting or receiving uplink / downlink radio signals in a wireless communication system. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. Generally, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems. Summary of the Invention [Problem to be solved by the invention]

[0003] A technical problem of the present disclosure is to provide a method and apparatus for efficiently performing a process of transmitting and receiving a wireless signal.

[0004] Other technical problems of the present disclosure can be inferred from the detailed description. [Means for solving the problem]

[0005] In one aspect of a wireless communication system, a method for a terminal to receive a signal includes receiving information regarding one or more CC lists for configuring one or more CC (component carrier) groups; receiving downlink control information (DCI) including transmission configuration indication (TCI) information on a first CC; and simultaneously updating (comprising; configuring; establishing; setting; including; containing; containing) at least one transmission configuration indication (TCI) state for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI, wherein the correspondence between a value for the TCI information and a TCI state applied to the first CC group is set by network signaling.

[0006] Based on the TCI information of the DCI being set to a first value for updating the jth TCI state, the terminal updates the jth TCI state indicated for each CC of the first CC group to the TCI state associated with the first value.

[0007] The TCI state associated with the first value is set independently for each CC.

[0008] For the first CC, the TCI state "A" set in the first CC is associated with the first value, and for the second CC in the first CC group, the TCI state "B" set in the second CC is associated with the first value. The TCI state "A" and the TCI state "B" are different from each other.

[0009] All CCs in the first CC group are simultaneously activated by the network signaling.

[0010] The at least one TCI state to be updated may be a joint TCI state of the downlink and the uplink, or a separate TCI state of each of the downlink and the uplink.

[0011] The number of downlink TCI states (M1) and the number of uplink TCI states (N1) indicated for the first CC are independent of the number of downlink TCI states (M2) and the number of uplink TCI states (N2) indicated for the second CC of the CC group, respectively.

[0012] The terminal receives, via the network signaling, information specifying a correspondence between a value for the TCI information and a TCI state applied to a CC of the first CC group.

[0013] The value for the TCI information is the codepoint of the TCI field included in the DCI.

[0014] According to another aspect, there is provided a processor-readable recording medium having a program recorded thereon for performing the above-described signal reception.

[0015] According to another aspect, there is provided a terminal that receives the above-described signals.

[0016] According to another aspect, there is provided a signal processing device for controlling a terminal that receives the above-mentioned signals.

[0017] In another aspect of the wireless communication system, a method for transmitting a signal by a network node includes transmitting, to a terminal, information regarding one or more CC lists for configuring one or more CC (component carrier) groups; transmitting, to the terminal, downlink control information (DCI) including transmission configuration indication (TCI) information on a first CC; and simultaneously updating, based on the TCI information included in the DCI, at least one transmission configuration indication (TCI) state for each of all CCs belonging to the same first CC group as the first CC, wherein the correspondence between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling provided to the terminal by the network node.

[0018] According to another aspect, there is provided a network node that performs the above-described signaling. [Effects of the Invention]

[0019] According to the present disclosure, it is possible to efficiently transmit and receive radio signals in a radio communication system.

[0020] Other technical advantages of the present disclosure can be inferred from the detailed description. [Brief explanation of the drawings]

[0021] [Figure 1] 1 is a diagram illustrating physical channels used in a 3GPP (registered trademark: the same applies hereinafter) system, which is an example of a wireless communication system, and a general signal transmission method using these channels. [Figure 2] FIG. 1 is a diagram illustrating the structure of a radio frame. [Figure 3]FIG. 1 illustrates a resource grid of slots. [Figure 4] FIG. 10 is a diagram showing an example of mapping physical channels within a slot. [Figure 5] FIG. 1 illustrates a PDSCH and ACK / NACK transmission process. [Figure 6] FIG. 1 illustrates a PUSCH transmission process. [Figure 7] FIG. 1 illustrates an example of a procedure related to CSI. [Figure 8] FIG. 1 is a diagram illustrating the concept of a unified TCI framework. [Figure 9] 1 is a diagram for explaining determination / maintenance / update of indicated TCI status in a wireless communication system supporting a unified TCI framework according to one embodiment. [Figure 10-11] FIG. 10 is a diagram for explaining the association of TCI states within a CC group for simultaneous TCI updates. [Figure 12] 1 is a diagram illustrating the operation of a network and a terminal in a wireless communication system according to an embodiment. [Figure 13] A diagram for explaining network signaling for TCI status association within a CC group according to one embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of TCI state mapping based on network signaling according to one embodiment. [Figure 15-16] FIG. 10 is a diagram for explaining the TCI status ID and TCI configuration set for each CC. [Figure 17] FIG. 10 is a diagram for explaining the operation of a terminal according to an embodiment. [Figure 18] FIG. 10 is a diagram for explaining the operation of a network node according to one embodiment. [Figure 19-22] 1 is a diagram illustrating a communication system 1 and a wireless device applicable to the present disclosure. [Figure 23] FIG. 1 is a diagram illustrating a DRX (Discontinuous Reception) operation applicable to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0023] As more communication devices require larger communication capacities, there is an emerging need for improved mobile broadband (eMBB) communication compared to existing radio access technologies (RATs). Furthermore, massive machine-type communications (MTC), which connects multiple devices and objects to provide various services anytime, anywhere, is one of the important issues to be considered in next-generation communications. Furthermore, system designs that take into account reliability- and latency-sensitive services / terminals are being discussed. Thus, the introduction of next-generation RATs that take into account enhanced mobile broadband communication (eMBB), massive MTC, and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, the present invention refers to these technologies as new radio or new RATs (NR).

[0024] For clarity of explanation, the description will be focused on 3GPP NR, but the technical idea of ​​the present invention is not limited thereto.

[0025] In this specification, the term "setting" may be replaced with the term "configure / configuration," and the two terms may be used interchangeably. Conditional expressions (e.g., "if," "in a case," or "when") may be replaced with expressions such as "based on that" or "in a state / status." The operation or SW / HW configuration of a terminal / base station based on the satisfaction of a corresponding condition may be inferred or understood by analogy. In signal transmission and reception between wireless communication devices (e.g., base station, terminal), if the process on the receiving (or transmitting) side can be inferred or understood from the process on the transmitting (or receiving) side, the explanation may be omitted. For example, the signal determination / generation / encoding / transmission on the transmitting side may be understood as the signal monitoring / reception / decoding / decision on the receiving side. An expression that a terminal performs (or does not perform) a specific operation may also be interpreted as the base station operating by expecting / assuming (or expecting / assuming not) that the terminal will perform the specific operation. The expression that a base station performs (or does not perform) a specific operation can also be interpreted as the terminal operating under the expectation / assuming (or expecting / assuming not to perform) the execution of a specific operation of the base station. Furthermore, in the following description, the divisions and indexes of each section, embodiment, example, option, method, solution, etc. are for the convenience of explanation and should not be interpreted as meaning that each necessarily constitutes an independent invention or that each necessarily must be implemented individually. Furthermore, in describing each section, embodiment, example, option, method, solution, etc., unless there is explicitly conflicting / opposing technology, it is inferred / interpreted that at least some of them may be combined and implemented together, or at least some may be omitted and implemented.

[0026] In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and transmits information from the base station via an uplink (UL). The information transmitted between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0027] FIG. 1 illustrates physical channels used in a 3GPP NR system and a typical signal transmission method using these channels.

[0028] A terminal that has been powered on in a powered-off state or that has newly entered a cell performs an initial cell search, such as establishing synchronization with a base station, in step S101. To this end, the terminal receives a synchronization signal block (SSB) from the base station. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The terminal establishes synchronization with the base station based on the PSS / SSS and obtains information such as a cell identity. The terminal also obtains broadcast information within the cell based on the PBCH. In addition, the terminal can receive a downlink reference signal (DL RS) during the initial cell search to check the status of the downlink channel.

[0029] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information from the physical downlink control channel in step S102 to obtain more specific system information.

[0030] Thereafter, the terminal performs a random access procedure, such as steps S103 to S106, to complete connection to the base station. To this end, the terminal transmits a preamble over a physical random access channel (PRACH) (S103) and receives a response message to the preamble over a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, the terminal performs a contention resolution procedure, such as transmitting a further physical random access channel (S105) and receiving a physical downlink control channel and a corresponding physical downlink shared channel (S106).

[0031] After performing this procedure, the terminal then receives a physical downlink control channel / physical downlink shared channel (S107) and transmits a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) as a general uplink / downlink signal transmission procedure (S108). The control information transmitted by the terminal to the base station is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted via PUCCH, but when control information and traffic data need to be transmitted simultaneously, it is transmitted via PUSCH. In addition, UCI can be transmitted aperiodically via PUSCH at the request / instruction of the network.

[0032] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are organized into frames. A radio frame has a length of 10 ms and is divided into two 5 ms half-frames (HF). A half-frame is divided into five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots within a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM (Optogonal Frequency Division Multiplexing) symbols depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 OFDM symbols. When an extended CP is used, each slot contains 12 symbols.

[0033] Table 1 shows an example in which the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when a general CP is used.

[0034] [Table 1]

[0035] *N slot symb : Number of symbols in the slot

[0036] *N frame,u slot : Number of slots in the frame

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

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

[0039] [Table 2]

[0040] The frame structure is illustrative only, and the number of subframes, slots, and symbols in a frame can vary.

[0041] In an NR system, OFDM numerology (e.g., SCS) can be configured to be different among multiple cells merged into one terminal. Accordingly, the (absolute time) duration of time resources (e.g., SFs, slots, or TTIs) (commonly referred to as TUs (Time Units) for convenience) consisting of the same number of symbols can be configured to be different among the merged cells. Here, the symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

[0042] FIG. 3 illustrates a resource grid of a slot. A slot includes multiple symbols in the time domain. For example, in the case of a general CP, one slot includes 14 symbols, while in the case of an extended CP, one slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier includes up to N (e.g., 5) BWPs. Data communication is performed using activated BWPs, and only one BWP can be activated for one UE. Each element in the resource grid is called a resource element (RE), and one complex symbol can be mapped to it.

[0043] Figure 4 shows an example of physical channel mapping within a slot. PDCCH is transmitted in the DL control region, and PDSCH is transmitted in the DL data region. PUCCH is transmitted in the UL control region, and PUSCH is transmitted in the UL data region. GP provides a time gap when the base station and terminal switch from transmission mode to reception mode or from reception mode to transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0044] Each physical channel is described in more detail below.

[0045] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the Paging Channel (PCH), system information on the DL-SCH, resource allocation information for higher layer control messages such as voluntary access responses transmitted on the PDSCH, transmit power control commands, and activation / deactivation of configured scheduling (CS). The DCI includes a cyclic redundancy check (CRC), which is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with a terminal identifier (e.g., cell-RNTI, C-RNTI). If the PDCCH is related to paging, the CRC is masked with a Paging-RNTI (P-RNTI). If the PDCCH is related to system information (e.g., System Information Block, SIB), the CRC is masked with a System Information RNTI (SI-RNTI). If the PDCCH is related to an voluntary access response, the CRC is masked with a Random Access RNTI (RA-RNTI).

[0046] The PDCCH consists of 1, 2, 4, 8, or 16 Control Channel Elements (CCEs) depending on the Aggregation Level (AL). A CCE is a logical allocation unit used to provide a PDCCH with a predetermined code rate according to the radio channel condition. A CCE consists of 6 Resource Element Groups (REGs). A REG is defined by one OFDM symbol and one (P)RB. The PDCCH is transmitted using a Control Resource Set (CORESET). A CORESET is defined by a set of REGs with a given pneumatic system (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can be overlapped in the time / frequency domain. A CORESET is configured by system information (e.g., Master Information Block, MIB) or UE-specific signaling via higher layer (e.g., Radio Resource Control, RRC, layer). Specifically, the number of RBs and the number of OFDM symbols (maximum 3) that make up a CORESET are configured via higher layer signaling.

[0047] To receive / detect PDCCH, the UE monitors PDCCH candidates. PDCCH candidates indicate the CCEs that the UE monitors for PDCCH detection. Each PDCCH candidate is defined by 1, 2, 4, 8, or 16 CCEs depending on the AL. Monitoring includes (blind) decoding of PDCCH candidates. The set of PDCCH candidates that the UE monitors is defined as the PDCCH search space (SS). The search space includes a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more search spaces configured by MIB or higher layer signaling. Each CORESET is associated with one or more search spaces, and each search space is associated with one COREST. The search space is defined based on the following parameters:

[0048] - controlResourceSetId: Indicates the CORESET associated with the search space.

[0049] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period (in slot units) and the PDCCH monitoring period offset (in slot units).

[0050] - monitoringSymbolsWithinSlot: indicates the PDCCH monitoring symbols within the slot (for example, indicates the first symbol of CORESET).

[0051] - nrofCandidates: indicates the number of PDCCH candidates (one of 0, 1, 2, 3, 4, 5, 6, 8) for each AL={1, 2, 4, 8, 16}.

[0052] *An opportunity (e.g., time / frequency resource) for monitoring a PDCCH candidate is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured within a slot.

[0053] Table 3 illustrates the characteristics of each search space type.

[0054] [Table 3]

[0055] Table 4 illustrates an example of a DCI format transmitted via the PDCCH.

[0056] [Table 4]

[0057] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​is used to schedule a TB-based (or TB-level) PUSCH or a Code Block Group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 is used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI formats 0_0 / 0_1 are referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 are referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic SFI) to a UE, and DCI format 2_1 is used to transmit downlink pre-emption information to a UE. DCI format 2_0 and / or DCI format 2_1 are transmitted to terminals in a corresponding group via a group common PDCCH, which is a PDCCH transmitted to terminals defined in one group.

[0058] DCI format 0_0 and DCI format 1_0 are called fallback DCI formats, and DCI format 0_1 ​​and DCI format 1_1 are called non-fallback DCI formats. The fallback DCI format maintains the same DCI size / field configuration regardless of the terminal settings. On the other hand, the non-fallback DCI format has different DCI size / field configurations depending on the terminal settings.

[0059] The PDSCH carries downlink data (e.g., DL-SCH transport block, DL-SCH TB) and uses modulation methods such as QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM. The TB is encoded to generate a codeword. The PDSCH carries up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword are mapped to one or more layers. Each layer is mapped to resources along with a Demodulation Reference Signal (DMRS) to generate an OFDM symbol signal, which is then transmitted from the corresponding antenna port.

[0060] The PUCCH carries Uplink Control Information (UCI), which includes:

[0061] - SR (Scheduling Request): Information used to request UL-SCH resources.

[0062] - HARQ (Hybrid Automatic Repeat reQuest)-ACK (Acknowledgement): A response to a downlink data packet (e.g., a codeword) on the PDSCH. It indicates whether the downlink data packet has been successfully received. One HARQ-ACK bit is transmitted in response to a single codeword, and two HARQ-ACK bits are transmitted in response to two codewords. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK), DTX (Discontinuous Transmission), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0063] CSI (Channel State Information): Feedback information for downlink channels. MIMO (Multiple Input Multiple Output)-related feedback information includes RI (Rank Indicator) and PMI (Precoding Matrix Indicator).

[0064] Table 5 shows an example of a PUCCH format, which can be divided into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3, and 4) according to the PUCCH transmission length.

[0065] [Table 5]

[0066] PUCCH format 0 carries UCI with a maximum size of 2 bits and is mapped and transmitted based on a sequence. Specifically, the terminal transmits one of multiple sequences over a PUCCH with PUCCH format 0 to transmit specific UCI to the base station. The terminal transmits a PUCCH with PUCCH format 0 within the PUCCH resource for the corresponding SR setting only when transmitting a positive SR.

[0067] PUCCH format 1 carries UCI with a maximum size of 2 bits, and modulation symbols are spread in the time domain by an orthogonal cover code (OCC) (the setting varies depending on whether frequency hopping is enabled or disabled). DMRS is transmitted in symbols without modulation symbols (i.e., transmitted using TDM (Time Division Multiplexing)).

[0068] PUCCH format 2 carries UCI with a bit size greater than 2 bits, and modulation symbols are transmitted using frequency division multiplexing (FDM) with DM-RS. DM-RS is located at symbol indices #1, #4, #7, and #10 within a 1 / 3 density resource block. A pseudo noise (PN) sequence is used for the DM-RS sequence. Frequency hopping can be enabled for the 2-symbol PUCCH format 2.

[0069] PUCCH format 3 does not multiplex terminals within the same physical resource block and carries UCI with a bit size greater than 2 bits. That is, the PUCCH resources of PUCCH format 3 do not include orthogonal cover codes. Modulation symbols are transmitted using DMRS and TDM (Time Division Multiplexing).

[0070] PUCCH format 4 supports multiplexing of up to four UEs in the same physical resource block and carries UCI with a bit size greater than 2. That is, the PUCCH resource of PUCCH format 3 includes an orthogonal cover code. Modulation symbols are transmitted using DMRS and TDM (Time Division Multiplexing).

[0071] At least one of one or more configured cells in the terminal is configured for PUCCH transmission. At least the primary cell is configured as a cell for PUCCH transmission. At least one PUCCH cell group is configured in the terminal based on the at least one cell configured for PUCCH transmission, and each PUCCH cell group includes one or more cells. A PUCCH cell group is also simply referred to as a PUCCH group. PUCCH transmission is configured not only for the primary cell but also for SCells, and the primary cell belongs to the primary PUCCH group, and the PUCCH-SCell configured for PUCCH transmission belongs to the secondary PUCCH group. The PUCCH on the primary cell is used for cells belonging to the primary PUCCH group, and the PUCCH on the PUCCH-SCell is used for cells belonging to the secondary PUCCH group.

[0072] The PUSCH carries uplink data (e.g., UL-SCH transport block, UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the terminal applies transform precoding to transmit the PUSCH. For example, if transform precoding is not possible (e.g., transform precoding is disabled), the terminal transmits the PUSCH based on the CP-OFDM waveform, and if transform precoding is possible (e.g., transform precoding is enabled), the terminal transmits the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions are dynamically scheduled by UL grants in DCI or semi-statically scheduled (configured grant) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmissions can be codebook-based or non-codebook-based.

[0073] 5 is a diagram illustrating an ACK / NACK transmission process. Referring to FIG. 5, a UE detects a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and indicates a DL allocation-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 include the following information:

[0074] - Frequency domain resource assignment: Indicates the RB set assigned to the PDSCH.

[0075] - Time domain resource assignment: Indicates K0 (e.g., slot offset), the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index) and the length of the PDSCH (e.g., number of OFDM symbols).

[0076] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1.

[0077] - HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB).

[0078] - PUCCH resource indicator (PRI): Indicates the PUCCH resource used for UCI transmission from among multiple PUCCH resources in a PUCCH resource set.

[0079] Thereafter, the UE receives the PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via the PUCCH in slot #(n1+K1) after finishing receiving the PDSCH in slot #n1 (where n+K0≦n1). Here, the UCI includes a HARQ-ACK response to the PDSCH. For convenience, in FIG. 5, it is assumed that the SCS for the PDSCH and the SCS for the PUCCH are the same and that slot #n1 = slot #n+K0, but the present invention is not limited to this. If the SCSs are different, K1 is indicated / interpreted based on the SCS of the PUCCH.

[0080] If the PDSCH is configured to transmit a maximum of one TB, the HARQ-ACK response consists of 1 bit. If the PDSCH is configured to transmit a maximum of two TBs, the HARQ-ACK response consists of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the transmission time of the HARQ-ACK for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes the HARQ-ACK responses for multiple PDSCHs.

[0081] Whether a UE should perform spatial bundling for HARQ-ACK responses is configured for each cell group (e.g., RRC / higher layer signaling). For example, spatial bundling is configured individually for each HARQ-ACK response transmitted via a PUCCH and / or a HARQ-ACK response transmitted via a PUSCH.

[0082] Spatial bundling is supported when the maximum number of TBs (or codewords) that can be received at one time (or scheduled by 1 DCI) in a corresponding serving cell is two (or more than two) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). On the other hand, for 2-TB transmission, more than four layers are used, and for 1-TB transmission, up to four layers are used. As a result, when spatial bundling is configured for a corresponding cell group, spatial bundling is performed on serving cells in the corresponding cell group that can schedule more than four layers. A UE that wishes to transmit a HARQ-ACK response via spatial bundling in the corresponding serving cell can generate a HARQ-ACK response by performing a bit-wise logical AND operation on A / N bits for multiple TBs.

[0083] For example, assuming that a terminal receives DCI scheduling 2-TB and receives 2-TB via PDSCH based on the DCI, a terminal performing spatial bundling can generate a single A / N bit by logically ANDing a first A / N bit for the first TB and a second A / N bit for the second TB. As a result, if both the first TB and the second TB are ACK, the terminal reports an ACK bit value to the base station, and if any one of the TBs is NACK, the terminal reports a NACK bit value to the base station.

[0084] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with a bit value of 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0085] A base station / UE has multiple parallel DL HARQ processes for DL ​​transmission. Multiple parallel HARQ processes enable continuous DL transmission while waiting for HARQ feedback for successful or unsuccessful reception of previous DL transmission. Each HARQ process is associated with a HARQ buffer in the Medium Access Control (MAC) layer. Each DL HARQ process manages state variables related to the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, the current redundancy version, etc. Each HARQ process is distinguished by a HARQ process ID.

[0086] 6 illustrates a PUSCH transmission process. Referring to FIG. 6, a UE detects a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). DCI formats 0_0 and 0_1 include the following information:

[0087] - Frequency domain resource assignment: Indicates the RB set assigned to the PUSCH.

[0088] - Time domain resource assignment: Indicates the slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length are indicated by the SLIV (Start and Length Indicator Value) or are indicated separately.

[0089] Thereafter, the terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information of slot #n, where the PUSCH includes a UL-SCH TB.

[0090] CSI-related actions

[0091] FIG. 7 is a diagram showing an example of a procedure related to CSI.

[0092] The terminal receives configuration information related to CSI from the base station via RRC signaling 710. The configuration information related to CSI includes at least one of information on a CSI-IM (interference management) resource, information on a CSI measurement configuration, information on a CSI resource configuration, information on a CSI-RS resource, or information on a CSI report configuration.

[0093] - CSI-IM resources are configured for interference measurement (IM) of the terminal. In the time domain, the CSI-IM resource set is configured periodically, semi-persistently, or aperiodically. The CSI-IM resources are configured as zero power (ZP)-CSI-RS for the terminal. ZP-CSI-RS is configured separately from non-zero power (NZP)-CSI-RS.

[0094] - The UE may assume that the CSI-RS resources for channel measurement configured for one CSI report and the CSI-IM / NZP CSI-RS resources for interference measurement (when the NZP CSI-RS resources are used for interference measurement) have a QCL relationship per resource with respect to "QCL-Type D".

[0095] - The CSI resource configuration includes at least one of a CSI-IM resource for interference measurement, an NZP CSI-RS resource for interference measurement, and an NZP CSI-RS resource for channel measurement, where a CMR (channel measurement resource) is an NZP CSI-RS for CSI acquisition, and an IMR (Interference measurement resource) is an NZP CSI-RS for CSI-IM and IM.

[0096] CSI-RS may be configured for one or more terminals. A different CSI-RS configuration may be provided for each terminal, or the same CSI-RS configuration may be provided for multiple terminals. CSI-RS can support up to 32 antenna ports. CSI-RS corresponding to N (N is 1 or greater) antenna ports are mapped to N RE locations within a time-frequency unit corresponding to one slot and one RB. If N is 2 or greater, the N-port CSI-RS are multiplexed using CDM, FDM, and / or TDM. CSI-RS is mapped to REs other than the REs to which CORESET, DMRS, and SSB are mapped. In the frequency domain, CSI-RS is configured for the entire bandwidth, a partial bandwidth portion (BWP), or a portion of the bandwidth. CSI-RS is transmitted in every RB within the bandwidth where CSI-RS is configured (i.e., density = 1) or every second RB (e.g., even- or odd-numbered RBs) (i.e., density = 1 / 2). When the CSI-RS is used as a Tracking Reference Signal (TRS), a single-port CSI-RS may be mapped onto three subcarriers in each resource block (i.e., density = 3). One or more CSI-RS resource sets are configured for a terminal in the time domain. Each CSI-RS resource set includes one or more CSI-RS configurations. Each CSI-RS resource set may be configured periodically, semi-persistently, or aperiodically.

[0097] - The CSI reporting configuration includes configurations for feedback type, measurement resource, report type, etc. The NZP-CSI-RS resource set is used for the CSI reporting configuration of the terminal. The NZP-CSI-RS resource set is associated with CSI-RS or SSB. In addition, multiple periodic NZP-CSI-RS resource sets are configured by the TRS resource set. (i) The feedback type includes a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS Resource Indicator (CRI), an SSB Resource Block Indicator (SSBRI), a Layer Indicator (LI), a Rank Indicator (RI), a Layer 1-Reference Signal Received Strength (RSRP), etc. (ii) The measurement resource includes configurations for downlink signals and / or downlink resources on which the terminal performs measurements to determine feedback information. The measurement resources are configured as ZP and / or NZP CSI-RS resource sets associated with the CSI reporting configuration. The NZP CSI-RS resource set includes a CSI-RS set or an SSB set. For example, L1-RSRP is measured for a CSI-RS set or an SSB set. (iii) The report type includes settings for the time when the UE reports and the uplink channel. The reporting time is configured as periodic, semi-persistent, or aperiodic. Periodic CSI reporting is transmitted on the PUCCH. Semi-persistent CSI reporting is transmitted on the PUCCH or PUSCH based on the MAC CE indicating activation / deactivation. Aperiodic CSI reporting is indicated by DCI signaling. For example, the CSI request field of the uplink grant indicates one of various report trigger sizes. Aperiodic CSI reporting is transmitted on the PUSCH.

[0098] The terminal measures the CSI based on configuration information related to the CSI. The CSI measurement includes receiving a CSI-RS (720), computing the received CSI-RS, and acquiring the CSI (730).

[0099] The terminal transmits a CSI report to the base station (740). The time and frequency resources available to the UE for CSI reporting are controlled by the base station. The channel state information (CSI) includes at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), an L1-RSRP, and / or an L-SINR.

[0100] The time domain behavior of CSI reporting supports periodic, semi-persistent, and aperiodic modes. i) Periodic CSI reporting is performed on short PUCCH or long PUCCH. The periodicity and slot offset of periodic CSI reporting are configured by RRC and refer to the CSI-ReportConfig IE. ii) Semi-periodic (SP) CSI reporting is performed on short PUCCH, long PUCCH, or PUSCH. For SP CSI on short / long PUCCH, the periodicity and slot offset are configured by RRC, and CSI reporting is activated / deactivated by a separate MAC CE / DCI. For SP CSI on PUSCH, the periodicity of SP CSI reporting is configured by RRC, but the slot offset is not configured by RRC, and SP CSI reporting is activated / deactivated by DCI (format 0_1). A separate RNTI (SP-CSI C-RNTI) is used for SP CSI reporting on the PUSCH. The timing of the first CSI report follows the PUSCH time domain allocation value indicated by the DCI, and the timing of subsequent CSI reports follows the period set by the RRC. DCI format 0_1 ​​includes a CSI request field to activate / deactivate a specific configured SP-CSI trigger state. SP CSI reporting has the same or similar activation / deactivation mechanism as that for data transmission on the SPS PUSCH. iii) Aperiodic CSI reporting is performed on the PUSCH and is triggered by the DCI. In this case, information regarding the trigger of aperiodic CSI reporting is conveyed / indicated / configured by the MAC-CE. In the case of AP CSI with AP CSI-RS, the AP CSI-RS timing is configured by the RRC, and the timing for AP CSI reporting is dynamically controlled by the DCI.

[0101] QCL (quasi-co location)

[0102] Two antenna ports are quasi-colocated if the channel properties of one antenna port can be inferred from the channel of the other antenna port. The channel properties include one or more of the following: Delay spread, Doppler spread, Frequency / Doppler shift, Average received power, Received Timing / average delay, and Spatial RX parameters.

[0103] In relation to the PDCCH / PDSCH QCL, multiple TCI (Transmission Configuration Indication) states are configured in the terminal via higher layer signaling. Up to 64 TCI states are RRC configured for the PDCCH QCL, and up to 128 TCI states are RRC configured for the PDSCH QCL. For the PDSCH QCL, the higher layer parameter PDSCH-Config provides a list for configuring multiple TCI-States.

[0104] Each TCI-State is associated with QCL configuration parameters between one or two DL reference signals and the DM-RS port of the PDSCH / PDSCH. The QCL configuration parameters include qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS. The QCL type corresponds to one of the following:

[0105] - 'QCL-TypeA':{Doppler shift, Doppler spread, average delay, delay spread}

[0106] - 'QCL-TypeB':{Doppler shift, Doppler spread}

[0107] -'QCL-TypeC':{Doppler shift, average delay}

[0108] -'QCL-TypeD':{Spatial Rx parameter}

[0109] The TCI state set via RRC signaling is deactivated by default.

[0110] In the case of the PDSCH QCL, up to eight TCI states among the RRC-configured TCI states are activated by the MAC CE. The TCI field included in the DCI scheduling the PDSCH indicates one of the activated TCI states (e.g., when the provision of the TCI field in the DCI is activated by RRC signaling), and the UE receives the PDSCH based on the QCL information corresponding to the indicated TCI state.

[0111] In the case of PDCCH QCL, one TCI state among the RRC configured TCI states is activated for the corresponding CORESET by the MAC CE. To receive the PDCCH in the corresponding CORESET, the UE receives the PDCCH based on QCL information corresponding to the activated TCI state.

[0112] Operations related to M-TRP (multiple-transmission / reception point)

[0113] The M-TRP transmission method, in which M TRPs transmit data to one terminal, can be broadly divided into eMBB M-TRP transmission, which is a method for increasing the transmission rate, and URLLC M-TRP transmission, which is a method for increasing the reception success rate and reducing latency.

[0114] Meanwhile, the DL M-TRP URLLC transmission scheme refers to a scheme in which multiple TRPs transmit the same data / DCI using different spatial (e.g., layer / port) / time / frequency resources. For example, TRP 1 transmits specific data / DCI in resource 1, and TRP 2 transmits the specific data / DCI (i.e., the same data / DCI) in resource 2.

[0115] That is, when the DL M-TRP URLLC transmission method is configured, the UE receives the same data / DCI using different space / time / frequency resources. In this case, the UE receives an instruction from the base station regarding the QCL RS / type (i.e., DL TCI state) to be used in the space / time / frequency resource for receiving the data / DCI.

[0116] For example, when the data / DCI is received on resource 1 and resource 2, the base station instructs the terminal on the DL TCI state used on resource 1 and the DL TCI state used on resource 2. The terminal can achieve high reliability by receiving the data / DCI via resource 1 and resource 2. This M-TRP URLLC transmission scheme is applied to PDSCH / PDCCH.

[0117] The UL M-TRP URLLC transmission scheme refers to a scheme in which multiple TRPs receive the same data / UCI from one UE using different space / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE in resource 1, and TRP 2 receives the same data / UCI from the UE in resource 2. In addition, TRP 1 and TRP 2 share the data / UCI received from the UE via a backhaul link (connected between the TRPs).

[0118] That is, when the UL M-TRP URLLC transmission method is configured, the terminal transmits the same data / UCI to each TRP using different space / time / frequency resources. In this case, the base station instructs the terminal on the Tx beam and Tx power (i.e., UL TCI state) to be used in the space / time / frequency resources that transmit the same data / UCI. For example, when the same data / UCI is transmitted in resource 1 and resource 2, the base station instructs the terminal on the UL TCI state to be used in resource 1 and the UL TCI state to be used in resource 2. Such UL M-TRP URLLC is applied to PUSCH / PUCCH.

[0119] In addition, from the viewpoint of DCI transmission, the M-TRP transmission method can be divided into i) an M-DCI (multiple DCI)-based M-TRP transmission method in which each TRP transmits different DCI, and ii) an S-DCI (single DCI)-based M-TRP transmission method in which one TRP transmits DCI. For example, in the case of S-DCI, all scheduling information for data transmitted by the M-TRP needs to be transmitted via one DCI, and therefore, it is used in an ideal BH (ideal BackHaul) environment in which dynamic cooperation between two TRPs is possible.

[0120] Regarding M-TRP transmission and reception in the Rel-16 NR standardization, PDSCH transmission and reception using the S-DCI-based M-TRP transmission method and the M-DCI-based M-TRP transmission method are supported.

[0121] First, the S-DCI-based M-TRP PDSCH transmission method will be described.

[0122] S-DCI-based M-TRP PDSCH transmission uses one of the SDM, FDM, or TDM methods. In the case of SDM, the base station transmits one TB using multiple layers, and layers belonging to different DMRS CDM groups are transmitted using different Tx beams (i.e., QCL RS or TCI states). This increases the number of layers compared to the conventional S-TRP transmission method, thereby improving transmission capacity. In addition, when one TB is transmitted using multiple layers, some layers are transmitted to TRP 1 and other layers are transmitted to TRP 2, thereby improving channel reliability through diversity gain.

[0123] In the case of FDM, two schemes, Schemes 2a and 2b, are supported. Here, Scheme 2a is a scheme in which one TB is transmitted to multiple RBs, but RBs belonging to different RB groups are transmitted in different Tx beams (i.e., QCL RS or TCI states). Scheme 2b is a scheme in which the same TB is transmitted to different RB groups, but RBs belonging to different RB groups are transmitted in different Tx beams (i.e., QCL RS or TCI states). In the case of TDM, two schemes, Schemes 3 and 4, are supported. Here, Scheme 4 (i.e., inter-slot TDM) is a scheme in which the same TB is repeatedly transmitted in multiple slots, but slots belonging to different slot groups are transmitted in different Tx beams (i.e., QCL RS or TCI states). On the other hand, Scheme 3 (i.e., intra-slot TDM) is a scheme in which the same TB is repeatedly transmitted from multiple OFDM symbol groups, but some OFDM symbol groups are transmitted in different Tx beams (i.e., QCL RS or TCI states) from other OFDM symbol groups.

[0124] Next, the M-DCI-based M-TRP PDSCH transmission method will be described.

[0125] In M-DCI-based MTRP PDSCH transmission, each TRP schedules and transmits a PDSCH via DCI. That is, TRP 1 transmits PDSCH 1 via DCI 1, and TRP 2 transmits PDSCH 2 via DCI 2. When PDSCH 1 and PDSCH 2 are superimposed on the same frequency-time resource, two PDSCHs are received for the same RE, improving resource efficiency and increasing transmission capacity. For this purpose, the concept of a CORESET pool, which refers to a group of multiple CORESETs, has been introduced. For example, TRP 1 transmits a PDCCH via a CORESET belonging to CORESET pool 0 and also transmits a PDSCH scheduled by the PDCCH. TRP 2 transmits a PDCCH via a CORESET belonging to CORESET pool 1 and also transmits a PDSCH scheduled by the PDCCH.

[0126] In the case of PUSCH, a specific TRP also schedules PUSCH transmission to a terminal via a CORESET belonging to each COERSET pool. For example, some PUCCH resources are scheduled by TRP 1, and other PUCCH resources are scheduled by TRP 2. The terminal transmits independent PUSCH / PUCCH to each of TRP 1 and 2.

[0127] In addition, the UE recognizes PUSCHs (or PUCCHs) scheduled by DCIs received based on different CORESETs (or CORESETs belonging to different CORESET groups) as PUSCHs (or PUCCHs) to be transmitted to different TRPs, or as PUSCHs (or PUCCHs) of different TRPs. In addition, the scheme for UL transmissions (e.g., PUSCHs / PUCCHs) to be transmitted to different TRPs is similarly applied to UL transmissions to different panels belonging to the same TRP.

[0128] Hereinafter, a CORESET group ID (or COERSET pool index with the same meaning) refers to an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel. Also, a CORESET group refers to a group / union of CORESETs distinguished by an index / identification information (e.g., ID) / CORESET group ID for distinguishing a CORESET for each TRP / panel. For example, a CORESET group ID is specific index information defined in a CORESET configuration. That is, a CORESET group is set / indicated / defined by an index defined in a CORESET configuration for each CORESET. And / or, a CORESET group ID refers to an index / identification information / designator for distinguishing / identifying CORESETs set in / associated with each TRP / panel.

[0129] Hereinafter, the CORESET group ID may be expressed as a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs configured for / associated with each TRP / panel. This information is configured / indicated through higher layer signaling (e.g., RRC signaling, MAC-CE, etc.) and / or physical layer signaling (e.g., DCI). For example, it is configured / instructed to perform PDCCH detection for each TRP / panel in units of the CORESET group, and it is configured / instructed to separately manage / control UCI (e.g., CSI, HARQ-ACK / NACK, SR, etc.) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) for each TRP / panel in units of the CORESET group. And / or HARQ ACK / NACK (process / retransmission) for PDSCH / PUSCH, etc. scheduled for each TRP / panel in units of the CORESET group is managed.

[0130] For example, the ControlResourceSet IE (information element), which is an upper layer parameter, includes a CORESET-related ID (e.g., controlResourceSetID), a CORESET pool index for the CORESET (e.g., CORESETPoolIndex), time / frequency resource configuration of the CORESET, TCI information related to the CORESET, etc. As an example, the index of the CORESET pool (e.g., CORESETPoolIndex) is set to 0 or 1. The CORESET group described above in the present invention corresponds to the CORESET pool, and the CORESET group ID corresponds to the CORESET pool index (e.g., CORESETPoolIndex).

[0131] Furthermore, with regard to M-TRP transmission and reception in the Rel-17 NR standard, M-TRP PDCCH / PDSCH SFN transmission, S-DCI-based M-TRP PUSCH repeat transmission, and single PUCCH resource-based M-TRP PUCCH repeat transmission are supported. These transmission methods repeatedly transmit the same contents (i.e., DCI / UL TB / UCI, etc.) in accordance with URLLC target improvement for increased reliability. Here, M-TRP PDCCH repeat transmission is performed based on TDM or FDM, M-TRP PDCCH / PDSCH SFN transmission is performed on the same time / frequency / layer, S-DCI-based M-TRP PUSCH repeat transmission is performed based on TDM, and single PUCCH resource-based M-TRP PUCCH repeat transmission is performed based on TDM.

[0132] First, the S-DCI-based M-TRP PDCCH repetitive transmission method will be described.

[0133] In the NR Rel-17 standard, for M-TRP PDCCH repeat transmission, multiple CORESETs with different TCI states (i.e., different QCL RSs) are configured in a terminal, and multiple SS (Search Space) sets connected to the CORESETs are configured. The base station instructs / configures the terminal that the SS set connected to one CORESET and the SS set connected to the other CORESET are linked for repeat transmission. As a result, the terminal knows that the PDCCH candidates of the SS set will be repeatedly transmitted.

[0134] For example, two CORESETs, CORESET 0 and CORESET 1, are configured in a UE, and CORESET 0 and CORESET 1 are connected to SS set 0 and SS set 1, respectively, so that SS set 0 and SS set 1 are linked. The UE can determine that the same DCI is repeatedly transmitted in the PDCCH candidate of SS set 0 and the PDCCH candidate of SS set 1, and that a specific PDCCH candidate of SS set 0 and a specific PDCCH candidate of SS set 1 are a pair configured to repeatedly transmit the same DCI according to a specific rule. The two PDCCH candidates are referred to as linked PDCCH candidates, and the UE can successfully decode the DCI if it properly receives any one of the two PDCCH candidates. However, when receiving PDCCH candidates for SS set 0, the UE uses the QCL RS (i.e., DL beam) in the TCI state of COERSET 0 connected to SS set 0, and when receiving PDCCH candidates for SS set 1, the UE uses the QCL RS (i.e., DL beam) in the TCI state of COERSET 1 connected to SS set 1. As a result, the UE receives the linked PDCCH candidates using different beams.

[0135] Next, the transmission method of the M-TRP SFN PDCCH / PDSCH will be described.

[0136] In one M-TRP PDCCH repeat transmission scheme, multiple TRPs repeatedly transmit the same DCI through the same time / frequency / DMRS port. This transmission scheme is called SFN PDCCH transmission. However, for SFN PDCCH transmission, the base station configures multiple TCI states in one CORESET instead of configuring multiple CORESETs with different TCI states. When the terminal receives PDCCH candidates through the SS set connected to the single CORESET, it performs channel estimation and attempts decoding of the PDCCH DMRS using all of the multiple TCI states.

[0137] Also, during the aforementioned M-TRP PDSCH repeated transmission, the two TRPs repeatedly transmit the corresponding channel on different resources. However, even when the two TRPs use the same resources, i.e., when the same channel is repeatedly transmitted via the same frequency / time / layer (i.e., DMRS port), the reliability of the channel can be improved. In this case, the repeatedly transmitted same channel cannot be separated into resources and is received by combining during transmission (i.e., air), so it is recognized as a single channel (e.g., a composite channel) from the perspective of the receiving end (e.g., UE). For SFN PDSCH transmission, two DL TCI states for PDSCH DMRS reception are configured in the UE.

[0138] Next, the S-DCI-based M-TRP PUSCH repetitive transmission method will be described.

[0139] In the NR Rel-17 standard, a base station configures two SRS sets in a terminal for S-DCI-based M-TRP PUSCH transmission, and each of these sets is used to indicate the UL Tx port and UL beam / QCL information for TRP 1 and TRP 2, respectively. Furthermore, the base station may indicate SRS resources for each SRS resource set via two SRI fields included in one DCI, and indicate up to two PC parameter sets. For example, the first SRI field indicates the SRS resources and PC parameter set defined in SRS resource set 0, and the second SRI field indicates the SRS resources and PC parameter set defined in SRS resource set 1. The terminal receives indication of the UL Tx port, PC parameter set, and UL beam / QCL information for TRP 1 via the first SRI field, and accordingly, the terminal transmits a PUSCH via a TO corresponding to SRS resource set 0. Similarly, the UE receives indication of the UL Tx port, PC parameter set, and UL beam / QCL information for TRP 2 via the second SRI field, and accordingly, the UE transmits a PUSCH using a TO corresponding to SRS resource set 1. The conventional single field is expanded to two fields so that the TPMI, PTRS, TPC, and other fields can be indicated for each TRP in addition to the SRI field. A 2-bit SRS resource set indication field is also introduced to select one of two SRS sets to perform STRP PUSCH repetitive transmission, or select both sets to perform MTRP PUSCH repetitive transmission. That is, when this field is 00 or 01, it indicates SRS set 0 or SRS set 1, respectively, and STRP PUSCH transmission corresponding to each set is performed. When this field is 10, it indicates (SRS set 0, SRS set 1), and MTRP PUSCH transmission is performed in the order in which the set pairs are indicated. That is, set 0 corresponds to the first PUSCH TO. If the set pair is 11 (SRS set 1, SRS set 0), the MTRP PUSCH transmission is performed in the specified order.That is, set 1 corresponds to the first PUSCH TO.

[0140] Next, the M-TRP PUCCH repetition transmission method based on a single PUCCH resource will be described.

[0141] In the NR Rel-17 standard, for single-PUCCH resource-based M-TRP PUCCH transmission, the base station activates / configures two pieces of spatial relation information (spatial relation info) for a single PUCCH resource in the UE (for FR1, two PC parameter sets are activated / configured). When UL UCI is transmitted via the PUCCH resource, each piece of spatial relation info is used to indicate spatial relation information for TRP1 and TRP2 to the UE. For example, the value indicated in the first piece of spatial relation info indicates the Tx beam / PC parameters for TRP1, and the UE uses the information to transmit the PUCCH in the TO corresponding to TRP1. Similarly, the value indicated in the second piece of spatial relation info indicates the Tx beam / PC parameters for TRP2, and the UE uses the information to transmit the PUCCH in the TO corresponding to TRP2.

[0142] In addition, for the M-TRP PUCCH repeated transmission, the configuration method has been improved so that two pieces of spatial relation information are configured in the PUCCH resource. That is, when a power control (PC) parameter such as PLRS, Alpha, P0, or closed loop index is configured in each piece of spatial relation information, a spatial relation RS is configured. As a result, PC information and spatial relation RS information corresponding to two TRPs are configured based on the two pieces of spatial relation information. As a result, the UE transmits a UCI (i.e., CSI, ACK / NACK, SR, etc.) PUCCH using the first spatial relation information in the first TO, and transmits the same UCI PUCCH using the second spatial relation information in the second TO. In the present invention, a PUCCH resource configured with two pieces of spatial relation information is referred to as an M-TRP PUCCH resource, and a PUCCH resource configured with one piece of spatial relation information is referred to as an S-TRP PUCCH resource.

[0143] TCI (transmission configuration indication) status / beam indication

[0144] Furthermore, in describing the present disclosure, when receiving / transmitting data / DCI / UCI via a specific space / time / frequency resource, using (or mapping) a specific TCI state (or TCI) means, in the case of DL, estimating a channel from a DMRS using a QCL type and QCL RS indicated by the specific TCI state in the specific space / time / frequency resource, and receiving / demodulating the data / DCI / UCI using the estimated channel.

[0145] Furthermore, when receiving / transmitting data / DCI / UCI via a specific space / time / frequency resource, using (or mapping) a specific TCI state (or TCI) means, in the UL case, transmitting / modulating DMRS and data / UCI using a Tx beam and / or Tx power indicated by the specific TCI state in the specific space / time / frequency resource.

[0146] The UL TCI state also includes Tx beam or Tx power information of the UE. The base station also sets spatial relation information, etc., to the UE through other parameters instead of the TCI state.

[0147] For example, the UL TCI state may be directly indicated to the UE via an UL grant DCI, or may refer to spatial relationship information of SRS resources indicated via an SRS resource indicator (SRI) field of the UL grant DCI, or may refer to an open loop (OP) Tx power control parameter linked to a value indicated via the SRI field of the UL grant DCI.

[0148] Here, the OL Tx power control parameters include, for example, j (index for OP parameter Po and alpha (maximum 32 parameter value sets per cell), q_d (index of DL RS resource for PL (path loss) measurement (maximum 4 measurements per cell)), and / or I (closed loop power control process index (maximum 2 processes per cell)).

[0149] For convenience of explanation, the present disclosure assumes that two TRPs cooperate with each other to perform transmission / reception operations, but is not limited thereto. That is, the present disclosure can be extended to a multi-TRP environment of three or more, and can also be extended to an environment in which the same TRP transmits / receives using different panels or beams. A terminal recognizes different TRPs as different TCI states. When a terminal transmits / receives data / DCI / UCI using TCI state 1, it means transmitting / receiving data / DCI / UCI from (or to) TRP1.

[0150] TO (Transmission Occasion) refers to each channel transmitted at a different time when multiple channels are TDMed, each channel transmitted to a different frequency / RB when multiple channels are FDMed, and each channel transmitted to a different layer / beam / DMRS port when multiple channels are SDMed. One TCI state is mapped to each TO. When the same channel is transmitted repeatedly, complete data / DCI / UCI is transmitted to one TO, and the receiving end can receive multiple TOs to increase the success rate of reception.

[0151] Single DCI-based multi-TB PUSCH / PDSCH scheduling

[0152] Rel. 17 NR supports a scheme in which one DCI simultaneously schedules multiple PUSCHs / PDSCHs in the ultra-high frequency band (beyond 5.26 GHz). For example, multiple TDRAs (=TOs) can be indicated at once via the TDRA field of the PUSCH scheduling DCI, and different TBs are transmitted via the PUSCH for each TO. The FDRA, MCS, TPMI, and SRI values ​​of the DCI are commonly applied to multiple scheduled TBs. In addition, the DCI indicates NDI and RV for each TB, and a single HARQ number is indicated, but the HARQ number increases sequentially in the order of the TOs based on the initial TO.

[0153] STxMP(simultaneous transmission across multiple panels)

[0154] Recently, for the Rel. 18 NR standard, there has been discussion about whether a UE can simultaneously transmit multiple channels / RSs of the same type or multiple channels / RSs of different types. While conventional UEs are limited in their ability to simultaneously transmit multiple channels / RSs (e.g., for UL beam measurement, multiple SRS resources from different SRS sets can be simultaneously transmitted, but multiple PUSCHs cannot be simultaneously transmitted), advanced UEs will be able to relax this limitation and simultaneously transmit multiple channels or RSs using multiple transmission panels. This UE is called a STxMP UE. For example, two PUSCHs corresponding to two UL TBs are scheduled in the same RE, and spatial relation RS 1 and PC parameter Set 1 (i.e., UL TCI state 1) and spatial relation RS 2 and PC parameter Set 2 (i.e., UL TCI state 2) are configured for PUSCH 1 and PUSCH 2 transmission, respectively. The UE transmits PUSCH 1 using panel 1 corresponding to UL TCI state 1, and simultaneously transmits PUSCH 2 using panel 2 corresponding to UL TCI state 2.

[0155] When a base station schedules a PUSCH via DCI, it indicates whether the PUSCH should be transmitted in STxMP, in a single panel, or repeatedly transmitted in MTRP PUSCH. Of course, the UE must be STxMP capable, and the STxMP mode must be enabled in advance by RRC signaling, etc. For this purpose, the conventional SRS resource set indication field is redefined and used, or a new DCI field is introduced.

[0156] Unified TCI Framework

[0157] 8 is a diagram illustrating the concept of a unified TCI framework introduced in NR Rel. 17. In the unified TCI framework of Rel. 17, not only the DL TCI status but also the UL TCI status may be indicated via DL DCI (e.g., DCI format 1-1 or 1-2), or only the UL TCI status may be indicated via DL DCI without indicating the DL TCI status. In this way, Rel. 17 can support dynamic beam update operations using joint DL / UL TCI status indication or separate DL / UL TCI status indication.

[0158] Such dynamic beam update operations include common beam updates, for example, in which the base station instructs the terminal to use one common beam for multiple specific channel / RS combinations via DCI and / or MAC-CE, causing the terminal to perform a common beam update operation.

[0159] Rel-17 introduced dynamic beam update operations using joint DL / UL TCI states and separate DL / UL TCI states, and standardized common beam update operations for terminals, in which a base station uses DCI and / or MAC-CE to instruct / update a terminal using a single beam common to multiple specific channel / RS combinations. Regarding the target channel / RS for common beam update, in DL, common beam update is applied to UE-dedicated CORESET and UE-dedicated reception on PDSCH. In UL, common beam update is applied to all or a subset of dynamic grant (DG) / configured grant (CG)-PUSCH and dedicated PUCCH. Furthermore, aperiodic CSI-RS / BM and SRS for tracking may be configured as target channel / RS for common beam update.

[0160] For such common beam applicability, Rel-17 beam pointing operations are primarily related to single-TRP operations. In the unified TCI framework, where the number of DL TCI states is M and the number of UL TCI states is N, the number of DL / UL TCI states for NR Rel-17 common beam update is M=1 / N=1, respectively.

[0161] In NR Rel-18, in relation to MIMO standardization, discussions are underway on extensions to the unified TCI framework configuration (M>1 and / or N>1) and multi-TRP operation under such configuration.

[0162] The contents of the integrated TCI framework extensions in Rel-18 that have been discussed so far are summarized in Table 6.

[0163] [Table 6]

[0164] In Table 6, 3) J / J in combination means "first DL+UL joint TCI state / second DL+UL joint TCI state," and S / S means "first separate TCI state and / or first UL separate TCI state / second separate TCI state and / or second UL separate TCI state." However, it is not necessary that both the first and second TCI states are mapped to one code point, as in J / J or S / S, and J / -, - / J, S / -, or - / S are also possible. More specifically, in the case of joint TCI, each code point in the TCI field included in the DCI is either (i) mapped to only one joint (=DL+UL) TCI state, or (ii) mapped to two joint (=DL+UL) TCI states, as in {first joint (=DL+UL) TCI state, second joint (=DL+UL) TCI state}. The number of mapped joint (=DL+UL) TCI states may vary for each codepoint.

[0165] In the case of separate TCI, each code point in the TCI field is either mapped to (i) one DL TCI state (e.g., the first or second DL TCI state) and / or one UL TCI state (e.g., the first or second UL TCI state), or (ii) two separate (= DL and / or UL) TCI states, such as {first DL state and / or first UL TCI state, second DL state and / or second UL TCI state}. The number of mapped separate (= DL and / or UL) TCI states may vary for each code point. For example, in case (i), the total number of DL TCI states and the number of UL TCI states mapped to one code point is a maximum of two. In case (ii), the total number of DL TCI states and the number of UL TCI states mapped to one code point is a maximum of four.

[0166] As mentioned above, for convenience of explanation, the (maximum) number of DL or joint TCI states that can be mapped to one code point in the TCI field is denoted as M, and the (maximum) number of UL or joint TCI states that can be mapped to one code point in the TCI field is denoted as N.

[0167] As an example, if the total number of codepoints in the TCI field is L, i.e., if the size of the TCI field is assumed to be a ceiling function of log2L, then in the joint TCI mode, M = N = Max{# of joint TCI states of 1st codepoint, # of joint TCI states of 2nd codepoint, ..., # of joint TCI states of L-th codepoint}. In the separate TCI mode, M and N may be the same or different depending on the configuration. Specifically, (i) M = Max{# of DL TCI states of 1st codepoint, # of DL TCI states of 2nd codepoint, ..., # of DL TCI states of S-th codepoint}, and (ii) N = Max{# of UL TCI states of 1st codepoint, # of UL TCI states of 2nd codepoint, ..., # of UL TCI states of L-th codepoint}.

[0168] M may denote the number of indicated DL or joint TCI states (e.g., the maximum number per code point), and N may denote the number of indicated UL or joint TCI states (e.g., the maximum number per code point).

[0169] The terminal can maintain / update M indicated TCI states for DL ​​and N indicated TCI states for UL.

[0170] FIG. 9 shows an example of updating / maintaining the indicated TCI state of the terminal.

[0171] For ease of explanation, in Figure 9, the following is assumed: (i) the terminal receives a DL or joint TCI state list via RRC signaling, (ii) the number of TCI states indicated for the downlink, M = 2, (iii) the terminal receives an RRC parameter indicating that a TCI field is provided in the DCI (TCI-present in DCI: enabled), (iv) code point A of the TCI field indicates TCI state #3 as the first TCI state for DL ​​and a second TCI state for DL ​​is not provided, and code point B of the TCI field indicates that a first TCI state for DL ​​is not provided and a second TCI state for DL ​​is TCI state #4, (v) although the TCI field can be used for both non-scheduling DCI and scheduling DCI, Figure 9 assumes the TCI field included in the PDSCH scheduling DCI, and (vi) at the beginning of Figure 9, the two indicated TCI states currently held by the terminal are assumed to be {TCI state #1, TCI state #2}. (vii) Although Figure 9 illustrates DL, it is also applicable to UL, in which case the DCI is a UL scheduling DCI that schedules PUSCH, or a non-scheduling DCI, and the PDSCH reception of the terminal is replaced by a PUSCH transmission, and the HARQ-ACK transmission of the terminal is replaced by a HARQ-ACK transmission of the base station.

[0172] 9, the terminal receives a first DCI (A05), where the TCI field of the first DCI is set to code point A, and the first DCI schedules a first PDSCH.

[0173] The UE receives the first PDSCH based on the first DCI (A10). At this time, the UE has not yet applied / updated TCI state #3 indicated by code point A of the TCI field to the first indicated TCI state, so the UE can receive the first PDSCH based on at least one of the UE's current two indicated TCI states {TCI state #1, TCI state #2}. Also, if RRC configuration is such that the first DCI further includes a TCI selection field, at least one of {TCI state #1, TCI state #2} is selected based on the TCI selection field, thereby allowing the UE to receive the first PDSCH.

[0174] The terminal transmits a first HARQ-ACK for the first PDSCH (A15).

[0175] If the first HARQ-ACK is ACK (positive), the terminal updates the indicated TCI state held by the terminal to {TCI state #3, TCI state #2} based on the TCI field of the first DCI when BAT (Beam Application Time) has elapsed since the end (last symbol) of the transmission of the first HARQ-ACK. That is, since code point A does not provide a TCI state for the second indicated TCI state held by the terminal, the second indicated TCI state held by the terminal is continuously held in TCI state #2.

[0176] Meanwhile, in the example of Figure 9, it is assumed that the first DCI is a scheduling DCI, so the first HARQ-ACK is related to the first PDSCH, but in contrast, if the first DCI is not a scheduling DCI, the first HARQ-ACK may be HARQ-ACK information for reception of the first DCI. In the latter case, if the HARQ-ACK for reception of the first DCI is ACK (positive), BAT is applied, and the start point of BAT may be the point at which HARQ-ACK transmission for reception of the first DCI ends.

[0177] After this, the terminal receives a second DCI (A20), in which the TCI field is set to code point B, and the second DCI schedules a second PDSCH.

[0178] The terminal receives the second PDSCH based on the second DCI (A25). At this time, the terminal has applied / updated TCI state #3 indicated by code point A of the TCI field to the first indicated TCI state, so the terminal can receive the second PDSCH based on at least one of the terminal's current two indicated TCI states, {TCI state #3, TCI state #2}. Also, if the RRC is configured to further include a TCI selection field in the second DCI, at least one of {TCI state #3, TCI state #2} is selected based on the TCI selection field, thereby allowing the terminal to receive the second PDSCH.

[0179] The terminal transmits a second HARQ-ACK for the second PDSCH (A15).

[0180] If the second HARQ-ACK is ACK (positive), the terminal updates the indicated TCI state held by the terminal to {TCI state #3, TCI state #4} based on the TCI field of the second DCI when BAT (Beam Application Time) has elapsed since the end (last symbol) of the transmission of the second HARQ-ACK. That is, since code point B does not provide a TCI state for the first indicated TCI state held by the terminal, the first indicated TCI state held by the terminal continues to be held in TCI state #3.

[0181] Meanwhile, in the example of Figure 9, it is assumed that the second DCI is a scheduling DCI, so the second HARQ-ACK is related to the second PDSCH, but in contrast, if the second DCI is not a scheduling DCI, the second HARQ-ACK may be HARQ-ACK information for the reception of the second DCI. In the latter case, BAT is also applied when the HARQ-ACK for the reception of the second DCI is ACK (positive), and the start point of BAT may be the point at which the transmission of the HARQ-ACK for the reception of the second DCI ends.

[0182] On the other hand, Rel-17 introduces the simultaneous TCI state update / activation operation for the specified TCI state, not only for the specific target CC but also for multiple CCs included in the CC list, and the related details are shown in Table 7.

[0183] [Table 7]

[0184] As shown in Table 7, the unified TCI framework in Rel-17 only considers the M=N=1 situation, allowing for common updates to DL / UL beams with a single directed TCI state even for multiple CCs.

[0185] The Rel-18 unified TCI framework, which takes into account the MTRP extension, also allows for simultaneous TCI state updates for multiple CCs in addition to the target CC. The main consideration here is that each CC may have the same or different M / N configuration (by RRC). This can lead to problems when applying the indicated TCI state for a specific CC to other CCs in the list if the CCs have different M / N configurations in the list for simultaneous TCI updates.

[0186] A simple way to prevent this problem is to include CCs with the same M / N setting in a list, or to update only CCs with the same M / N setting for CCs with different M / N settings in a CC list. In this case, there is no problem in itself with performing simultaneous TCI updates for multiple CCs based on the TCI status indicated by a specific CC, but another problem arises in that multiple CC lists must be set for each case and beam instructions must be performed for each case. Therefore, this increases the control signaling overhead for common beam instructions, which weakens the original purpose of simultaneous TCI updates.

[0187] To solve this problem, this specification proposes a method for performing simultaneous TCI update / activation when CCs with different M / N settings are included in the CC list.

[0188] 1. Proposal 1

[0189] When configuring a CC list for simultaneous TCI update / activation, CCs with the same or different M / N settings can be set to the same CC list, and the number of indicated TCI states to be applied to the CC is determined based on the (maximum) M / N value in the CC list (e.g., CC1 is {M=2, N=1} and CC2 is {M=1, N=2} → S_DL=2, S_UL=2). S_DL and S_UL can respectively mean the number of DL or joint TCI states and the number of UL or joint TCI states to be applied to the CC list during simultaneous TCI update / activation.

[0190] Proposal 1 is a method for allowing the same or different M / N settings within a CC list when multiple CCs to be applied for simultaneous TCI updates are configured in one CC list, and a method for determining the indicated TCI state to be applied to multiple CCs based on this. For example, in Table 8, the CC list is made up of {CC1, CC2, CC3}, and the M / N settings for each CC are assumed to be as follows:

[0191] [Table 8]

[0192] In this case, when a TCI instruction is made in a specific CC, it is necessary to use this to simultaneously update the TCI of other CCs in the CC list using the updated TCI status, so it is necessary to determine the number of instructed TCI statuses to apply to multiple CCs based on the maximum values ​​of M and N in the CC list.

[0193] In the example of Table 8, the maximum values ​​of M and N in the CC list are each 2, and the indicated TCI states (i.e., S_DL, S_UL) for applying simultaneous TCI states (for DL / UL) are each determined to be 2. The two indicated TCI states for S_DL in the CC list are shown as s_DL0 and s_DL1, and the two indicated TCI states for S_UL in the CC list are shown as s_UL0 and s_UL1. Depending on the joint / separate TCI mode, the pairs {s_DL0, s_UL0} and {s_DL1, s_UL1} can be indicated as the same or different TCI states.

[0194] To express the above example more generally, the CC list of the CC group is [CC1,CC2,...,CC k ], and for DL, the M values ​​of each of the k CCs are expressed as [M1,M2,...,M k ] and for UL, let the N values ​​of each of the k CCs be [N1,N2,...,N k ], then S_DL=Max[M1,M2,...,M k ] and S_UL=Max[N1,N2,...,N k ]. Code points in the TCI field of the DCI provided for the CC group can be mapped to (up to) S_DL designated DL or joint TCI states and (up to) S_UL designated UL or joint TCI states. Here, the fact that code points in the TCI field can be mapped to "X" (e.g., S_DL or S_UL) TCI states does not necessarily mean that all code points must be mapped to "X" TCI states. For example, code point #1 is mapped to X TCI states, while code point #2 is mapped to XY TCI states, where Y is a positive integer not exceeding X.

[0195] 2. Proposal 2

[0196] Based on the explanation of Proposal 1, we propose below a method in which, in a situation where TCI status indication information is provided for a specific CC, (i) the indicated TCI status information for the specific CC is associated with (ii) indicated TCI status (i.e., S_DL and / or S_UL) information that applies to multiple CCs, and the TCI status of other CCs is updated simultaneously based on such association.

[0197] The terminal may be provided with a CC list configuration, allowing the terminal to perform simultaneous TCI state updates by (implicit / explicit) associating (i) the indicated TCI state for each CC with (ii) the indicated TCI state that applies to the CCs in the CC list. To avoid confusion between (i) the indicated TCI state for each CC and (ii) the indicated TCI state for the entire CC list, these are denoted as "(i) Per_CC_indicated TCI state" and "(ii) Per CC group_indicated TCI state", respectively.

[0198] For ease of explanation, the M indicated TCI states for the DL of the CC are denoted as m=0, m=1 (m=1 corresponds to the case where M=2), and the N indicated TCI states for the UL of the CC are denoted as n=0, n=1 (n=1 corresponds to the case where N=2).

[0199] 1) Rule-Based Mapping

[0200] For example, Per CC group_indicated TCI state s_DL=0 / s_UL=0 is mapped to the first Per CC_DL / UL indicated TCI state of each CC, and Per CC group_indicated TCI state s_DL=1 / s_UL=1 is mapped to the second per CC DL / UL indicated state TCI of each CC. For M=N=1 CCs, Per CC group_indicated TCI state is always mapped to the first Per CC DL TCI state where m=0 and the first Per CC UL indicated TCI state where n=0.

[0201] 2) Network configuration / instruction-based mapping

[0202] For example, information regarding which m / n value to apply for each CC is set by network signaling (for example, RRC / MAC CE, etc.).

[0203] This section explains how to associate the Per CC group_indicated TCI state that applies to multiple CCs with the TCI indication in a specific CC (e.g., the TCI field of the DCI received on a specific CC) for CCs with various M / N settings in a CC list, and explains the TCI update behavior based on this. This can be indicated by implicit / explicit mapping with the Per CC group_indicated TCI state that applies to multiple CCs when a TCI indication is made in each CC.

[0204] Figure 10 shows an example of TCI indication association for DL, assuming the CC list and M setting in Table 8. Referring to Figure 10, assume that m=0 for M=1 in CC1 is mapped to s_DL0, m=0, m=1 for M=2 in CC2 are mapped to s_DL0, s_DL1, and m=0, m=1 for M=2 in CC3 are mapped to s_DL0, s_DL1.

[0205] In this case, if the DL TCI state is indicated by the DCI received on CC1, the indicated TCI state is s_DL0 (because m=1 is not set on CC1). Based on the mapping of s_DL0 indicated on CC1 to s_DL0 on CC2 and CC3, the TCI state of m=0 on each CC can be updated.

[0206] Instead of following such a predefined mapping method, a different mapping method may be set for each CC. For example, referring to FIG. 11, CC2 and CC3 both have M=2, and the TCI state mapping of CC2 is set to s_DL0 for m=0 and s_DL1 for m=1, while the TCI state mapping of CC3 is set to s_DL1 for m=0 and s_DL0 for m=1. In this way, it is possible to simultaneously apply the designated TCI state of a specific CC to CCs in a CC group, while the ordered pairs are reversely mapped and applied. Alternatively, for the method shown in FIG. 11, a 1-bit swapping instruction may be used to swap the ordered pairs based on the m=0 / 1 mapping for s_DL0 / s_DL1.

[0207] Based on the above description, an example of a co-integrated TCI activation / update procedure will now be described with reference to FIG.

[0208] The terminal receives a CC list constituting a CC group from the network via RRC signaling in order to activate / update the simultaneous integrated TCI of CCs belonging to the CC group (B05). One CC group can be configured in the terminal, but multiple CC groups may also be configured depending on the network configuration. A CC list is provided for each CC group. CC groups can be configured without any constraint on the same M / N value between CCs.

[0209] The UE receives network signaling for a designated DL / UL TCI state (i.e., s_DL, s_UL) applied to the CC group (B10). The network signaling may be received via any one CC in the CC group or may be commonly applied to all CCs in the CC group. The network signaling may include at least one of MAC CE or RRC signaling. Hereinafter, for convenience of explanation, a separate designated DL / UL TCI state is assumed, but the scope of the invention is not limited thereto and may also be applied to a jointly designated DL / UL TCI state.

[0210] FIG. 13 is a diagram for explaining an example of network signaling (B10). FIG. 13 is based on the example of Table 8. Referring to FIG. 13, since S_DL=2, a first indicated DL TCI status ID for s_DL0 and a second indicated DL TCI status ID for s_DL1 are set for each code point. Also, since S_UL=2, a first indicated UL TCI status ID for s_UL0 and a second indicated UL TCI status ID for s_UL1 are set for each code point. For example, when the code point of the TCI field for a CC group (i.e., the TCI indication information) is 000, the indicated TCI status for the CC group is [first indicated DL TCI status ID=A, second indicated DL TCI status ID=G, first indicated UL TCI status ID=B, second indicated UL TCI status ID=F]. For ease of explanation, Figure 13 illustrates that the first / second DL / UL indicated TCI states (a total of four states) are provided, but depending on the embodiment, some TCI states may not be mapped.

[0211] Returning to FIG. 12, based on the network signaling (B10), the association between s_DL(s) / s_UL(s) (e.g., FIG. 13) for the provided CC group and the TCI status for each CC is determined (B15). FIG. 14 shows an example of the association between (i) s_DL(s) / s_UL(s) for the CC group shown in FIG. 13 and (ii) the M / N value for each CC in Table 8. For CC1, since M=1, the first instructed DL TCI status ID=A is mapped only to m=0, and since N=1, the first instructed UL TCI status ID=B is mapped only to n=0. For CC2, since M=2 and N=2, [first instructed DL TCI status ID=A, second instructed DL TCI status ID=G, first instructed UL TCI status ID=B, second instructed UL TCI status ID=F] are all mapped.

[0212] When a DCI including a TCI field of 000 is received, the ID of the first indicated DL TCI state is DL TCI state ID=A for all of CC1, CC2, and CC3, but the actual parameters of the TCI state setting indicated by DL TCI state ID=A may differ for each CC. For example, referring to Figures 15 and 16, in Figure 15, the TCI field ID=A indicates TCI state setting (i) for CC1, TCI state setting (ii) for CC2, and TCI state setting (iii) for CC3. In other words, in TCI state settings (i) to (iii), parameter 1601 shown in Figure 16 has the same value, but the other parameters 1602 are not necessarily the same. This is because the TCI state setting and ID are RRC settings provided for each CC.

[0213] Returning to FIG. 12, the terminal receives DCI including the TCI field via (any one of) the CCs in the CC group (B20).

[0214] The UE simultaneously updates the TCI status for all CCs belonging to the CC group based on the TCI indication information in the TCI field (B25). For example, referring to Figure 14, when DCI including TCI field = 001 is received on CC1, the UE updates the first indicated DL / UL status for CC1 with M = 1 / N = 1 to [first indicated DL TCI status of ID = C, first indicated UL TCI status of ID = D], and for CC2 and CC3 with M = 2 / N = 2, it can update the first indicated DL TCI status of ID = C, second indicated DL TCI status of ID = H, first indicated UL TCI status of ID = D, second indicated UL TCI status of ID = I]. For the BAT and update process according to the TCI indication, please refer to the description of Figure 9 above.

[0215] FIG. 17 is a diagram illustrating the operation of a terminal according to an embodiment.

[0216] Referring to FIG. 17, the terminal receives information about one or more component carrier (CC) lists for setting one or more CC groups (C05).

[0217] The terminal receives downlink control information (DCI) including transmission configuration indication (TCI) information on the first CC (C10).

[0218] Based on the TCI information included in the DCI, the terminal simultaneously updates at least one TCI (transmission configuration indication) status for each of all CCs belonging to the same first CC group as the first CC (C15).

[0219] The association between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling.

[0220] Based on the TCI information of the DCI being set to a first value for updating the jth TCI state, the terminal updates the jth TCI state indicated for each CC of the first CC group to the TCI state associated with the first value.

[0221] The TCI state associated with the first value is set independently for each CC.

[0222] For the first CC, the TCI state "A" set in the first CC is associated with the first value, and for the second CC in the first CC group, the TCI state "B" set in the second CC is associated with the first value. The TCI state "A" and the TCI state "B" are different from each other.

[0223] All CCs in the first CC group are simultaneously activated by the network signaling.

[0224] The at least one TCI state to be updated may be a joint TCI state of the downlink and the uplink, or a separate TCI state of each of the downlink and the uplink.

[0225] The number of downlink TCI states (M1) and the number of uplink TCI states (N1) indicated for the first CC are independent of the number of downlink TCI states (M2) and the number of uplink TCI states (N2) indicated for the second CC of the CC group, respectively.

[0226] The terminal receives, via the network signaling, information specifying a correspondence between a value for the TCI information and a TCI state that applies to the first CC group.

[0227] The value for the TCI information is the codepoint of the TCI field included in the DCI.

[0228] 18 is a diagram illustrating the operation of a network node according to an embodiment. The network node includes / controls one or more TRPs / BSs.

[0229] Referring to FIG. 18, a network node transmits information on one or more component carrier (CC) lists for setting one or more CC groups to a terminal (D05).

[0230] The network node transmits downlink control information (DCI) including transmission configuration indication (TCI) information to the terminal on a first CC (D10).

[0231] Based on the TCI information included in the DCI, the network node simultaneously updates at least one TCI (transmission configuration indication) status for each of all CCs belonging to the same first CC group as the first CC (D15).

[0232] The association between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling provided to the terminal by the network node.

[0233] Based on the TCI information of the DCI being set to a first value for updating the jth TCI state, the network node updates the jth TCI state indicated to each CC of the first CC group to the TCI state associated with the first value.

[0234] The TCI state associated with the first value is set independently for each CC.

[0235] For the first CC, the TCI state "A" set in the first CC is associated with the first value, and for the second CC in the first CC group, the TCI state "B" set in the second CC is associated with the first value. The TCI state "A" and the TCI state "B" are different from each other.

[0236] All CCs in the first CC group are simultaneously activated by the network signaling.

[0237] The at least one TCI state to be updated may be a joint TCI state of the downlink and the uplink, or a separate TCI state of each of the downlink and the uplink.

[0238] The number of downlink TCI states (M1) and the number of uplink TCI states (N1) indicated for the first CC are independent of the number of downlink TCI states (M2) and the number of uplink TCI states (N2) indicated for the second CC of the CC group, respectively.

[0239] The network node transmits, by means of the network signaling, information specifying an association between a value for the TCI information and a TCI state that applies to a CC of the first CC group.

[0240] The value for the TCI information is the codepoint of the TCI field included in the DCI.

[0241] FIG. 19 illustrates a communication system 1 to which the present invention can be applied.

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

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

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

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

[0246] 20, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR), where {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

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

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

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

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

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

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

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

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

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

[0256] 21, various elements, components, units / sections, and / or modules in wireless devices 100 and 200 are all connected to each other via a wired interface, or at least some are connected wirelessly via a communication unit 110. For example, in wireless devices 100 and 200, control unit 120 and communication unit 110 are connected via a wire, and control unit 120 and a first unit (e.g., 130, 140) are connected wirelessly via communication unit 110. Each element, component, unit / section, and / or module in wireless devices 100 and 200 further includes one or more elements. For example, control unit 120 is configured with a set of one or more processors. For example, control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

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

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

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

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

[0261] FIG. 23 is a diagram illustrating a DRX (Discontinuous Reception) operation of a terminal according to one embodiment of the present invention.

[0262] A terminal can perform DRX operation while executing the procedures and / or methods described / proposed above. A terminal configured for DRX can reduce power consumption by discontinuously receiving DL signals. DRX is performed in the RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. DRX in the RRC_IDLE state and RRC_INACTIVE state is used to discontinuously receive paging signals. DRX performed in the RRC_CONNECTED state will be described below (RRC_CONNECTED DRX).

[0263] Referring to FIG. 23, a DRX cycle consists of On Duration and Opportunity for DRX. The DRX cycle defines a time interval during which On Duration is periodically repeated. On Duration indicates a time period during which the UE monitors to receive the PDCCH. When DRX is configured, the UE monitors the PDCCH during On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates an inactivity timer and remains awake. On the other hand, if a PDCCH is not successfully detected during PDCCH monitoring, the UE enters a sleep state after the On Duration expires. Therefore, when DRX is configured, PDCCH monitoring / reception is performed discontinuously in the time domain when performing the procedures and / or methods described / proposed above. For example, when DRX is configured, in the present invention, PDCCH reception opportunities (e.g., slots having a PDCCH search space) are configured discontinuously according to the DRX configuration. On the other hand, if DRX is not configured, when the above-described / proposed procedures and / or methods are performed, PDCCH monitoring / reception is performed continuously in the time domain. For example, if DRX is not configured, in the present invention, PDCCH reception opportunities (e.g., slots having PDCCH search spaces) are configured continuously. On the other hand, PDCCH monitoring may be restricted in the time interval configured as the measurement gap, regardless of whether DRX is configured.

[0264] Table 9 shows the process of the UE related to DRX (RRC_CONNECTED state). Referring to Table 13, DRX configuration information is received via higher layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by a DRX command of the MAC layer. When DRX is configured, the UE can perform PDCCH monitoring discontinuously when performing the procedures and / or methods described / proposed in the present invention.

[0265] [Table 9]

[0266] Here, MAC-CellGroupConfig includes configuration information required to set MAC (Medium Access Control) parameters for a cell group. MAC-CellGroupConfig may also include configuration information related to DRX. - Value of drx-OnDurationTimer: defines the length of the start interval of the DRX cycle.

[0267] - Value of drx-InactivityTimer: defines the length of the time interval in which the UE is in an awake state after a PDCCH opportunity in which a PDCCH indicating initial UL or DL ​​data is detected.

[0268] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between the reception of a DL initial transmission and the reception of a DL retransmission.

[0269] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between the reception of a grant for an UL initial transmission and the reception of a grant for an UL retransmission.

[0270] - drx-LongCycleStartOffset: defines the length and start of a DRX cycle

[0271] - drx-ShortCycle(optional): defines the time length of a short DRX cycle

[0272] Here, if any one of the drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is running, the terminal remains awake and performs PDCCH monitoring at every PDCCH opportunity.

[0273] The above-described embodiments are combinations of elements and features of the present invention in a predetermined form. Each element or feature should be considered optional unless otherwise explicitly stated. Each element or feature may be implemented without being combined with other elements or features. It is also possible to combine some elements and / or features to form an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some elements or features of any embodiment may be included in other embodiments, or may be replaced with corresponding elements or features of other embodiments. It is obvious that claims that are not explicitly cited in the claims may be combined to form an embodiment, or may be included as new claims by amendment after filing.

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

[0275] [Industrial Applicability] The present invention can be used in a terminal, a base station or other equipment of a wireless mobile communication system.

[0276] [Claims at the time of international application] [Claim 1] A method for a user equipment (UE) to receive a signal in a wireless communication system, comprising: receiving information regarding one or more component carrier (CC) lists for establishing one or more CC groups; receiving downlink control information (DCI) including transmission configuration indication (TCI) information on a first CC; and simultaneously updating at least one TCI (transmission configuration indication) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; A method wherein the association between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling. [Claim 2] The method of claim 1, wherein, based on the TCI information of the DCI being set to a first value for updating the jth TCI state, the terminal updates the jth TCI state indicated for each CC of the first CC group to the TCI state associated with the first value. [Claim 3] The method of claim 2 , wherein the TCI state associated with the first value is set independently for each CC. [Claim 4] For the first CC, the TCI state "A" set for the first CC is associated with the first value; For a second CC in the first CC group, the TCI state "B" set for the second CC is associated with the first value; The method of claim 2 , wherein the TCI state “A” and the TCI state “B” are different from each other. [Claim 5] The method of claim 1 , wherein the network signaling causes all CCs in the first CC group to be activated simultaneously. [Claim 6] The at least one TCI state that is updated is: A joint downlink and uplink TCI condition exists, or The method of claim 1, wherein the TCI states are separate for the downlink and the uplink. [Claim 7] 2. The method of claim 1, wherein the number of downlink TCI states (M1) and the number of uplink TCI states (N1) indicated for the first CC are independent of the number of downlink TCI states (M2) and the number of uplink TCI states (N2) indicated for the second CC of the CC group, respectively. [Claim 8] The method of claim 1 , further comprising: receiving, via the network signaling, information specifying a mapping between a value for the TCI information and a TCI state to be applied to CCs of the first CC group. [Claim 9] The method of claim 1, wherein the value for the TCI information is a codepoint of a TCI field included in the DCI. [Claim 10] A computer-readable recording medium having a program recorded thereon for carrying out the method according to claim 1. [Claim 11] 1. An apparatus for wireless communication, comprising: a memory for storing instruction words; and a processor that operates by executing the instructions; The operation of the processor is receiving information regarding one or more component carrier (CC) lists for establishing one or more CC groups; receiving downlink control information (DCI) including transmission configuration indication (TCI) information on a first CC; and simultaneously updating at least one TCI (transmission configuration indication) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; The correspondence between the value for the TCI information and the TCI state applied to the CC of the first CC group is set by network signaling, the device. [Claim 12] a transceiver for transmitting or receiving wireless signals under the control of the processor; The device of claim 11 , wherein the device is a terminal in a wireless communication system. [Claim 13] The device according to claim 11, wherein the device is a signal processing device for controlling a terminal. [Claim 14] 1. A method for a network node to transmit a signal in a wireless communication system, comprising: sending information about one or more component carrier (CC) lists to the terminal for configuring one or more CC groups; transmitting downlink control information (DCI) including transmission configuration indication (TCI) information to the terminal on a first CC; and simultaneously updating at least one TCI (transmission configuration indication) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; A method in which the association between the value for the TCI information and the TCI state applied to the CC of the first CC group is set by network signaling given to the terminal by the network node. [Claim 15] A network node for wireless communication, comprising: a memory for storing instruction words; and a processor that operates by executing the instructions; The operation of the processor is sending information about one or more component carrier (CC) lists to the terminal for configuring one or more CC groups; transmitting downlink control information (DCI) including transmission configuration indication (TCI) information to the terminal on a first CC; and simultaneously updating at least one TCI (transmission configuration indication) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; A network node, wherein the association between the value for the TCI information and the TCI state to be applied to the CC of the first CC group is set by network signaling given to the terminal by the network node.

Claims

1. A method for a terminal (user equipment: UE) receiving a signal in a wireless communication system, comprising: receiving information regarding one or more component carrier (CC) lists for establishing one or more CC groups; receiving downlink control information (DCI) including transmission configuration indication (TCI) information on a first CC; and and simultaneously updating at least one transmission configuration indication (TCI) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; A method wherein the association between the value for the TCI information and the TCI state applied to the CCs of the first CC group is configured by network signaling.

2. 2. The method of claim 1, wherein, based on the TCI information of the DCI being set to a first value for updating a j-th TCI state, the terminal updates the j-th TCI state indicated for each CC of the first CC group to a TCI state associated with the first value.

3. The method of claim 2 , wherein the TCI state associated with the first value is set independently for each CC.

4. For the first CC, a TCI state "A" set for the first CC is associated with the first value; For a second CC of the first CC group, a TCI state "B" set for the second CC is associated with the first value; The method of claim 2 , wherein the TCI state “A” and the TCI state “B” are different from each other.

5. The method of claim 1 , wherein the network signaling causes all CCs in the first CC group to be activated simultaneously.

6. The at least one TCI state that is updated is: A joint downlink and uplink TCI condition, or The method of claim 1, wherein the TCI states are separate for the downlink and the uplink.

7. 2. The method of claim 1, wherein the number of downlink TCI states (M1) and the number of uplink TCI states (N1) indicated for the first CC are independent of the number of downlink TCI states (M2) and the number of uplink TCI states (N2) indicated for a second CC of the CC group, respectively.

8. 2. The method of claim 1, further comprising: receiving, via the network signaling, information specifying a correspondence between a value for the TCI information and a TCI state to be applied to CCs of the first CC group.

9. The method of claim 1 , wherein the value for the TCI information is a codepoint of a TCI field included in the DCI.

10. A computer-readable recording medium having a program recorded thereon for carrying out the method according to claim 1.

11. 1. An apparatus for wireless communication, comprising: a memory for storing an instruction word; and a processor that operates by executing the instructions; The operation of the processor is receiving information regarding one or more component carrier (CC) lists for establishing one or more CC groups; receiving downlink control information (DCI) including transmission configuration indication (TCI) information on a first CC; and and simultaneously updating at least one transmission configuration indication (TCI) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; The correspondence between the value for the TCI information and the TCI state applied to the CCs of the first CC group is configured by network signaling.

12. a transceiver for transmitting or receiving wireless signals under the control of the processor; The device of claim 11 , wherein the device is a terminal in a wireless communication system.

13. The device according to claim 11, wherein the device is a signal processing device for controlling a terminal.

14. 1. A method for a network node to transmit a signal in a wireless communication system, comprising: transmitting, to a terminal, information regarding one or more component carrier (CC) lists for setting one or more CC groups; transmitting downlink control information (DCI) including transmission configuration indication (TCI) information to the terminal on a first CC; and and simultaneously updating at least one transmission configuration indication (TCI) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; A method, wherein the association between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling provided to the terminal by the network node.

15. A network node for wireless communication, comprising: a memory for storing an instruction word; and a processor that operates by executing the instructions; The operation of the processor is transmitting, to a terminal, information regarding one or more component carrier (CC) lists for setting one or more CC groups; transmitting downlink control information (DCI) including transmission configuration indication (TCI) information to the terminal on a first CC; and and simultaneously updating at least one transmission configuration indication (TCI) status for each of all CCs belonging to the same first CC group as the first CC based on the TCI information included in the DCI; A network node, wherein the association between the value for the TCI information and the TCI state applied to the CCs of the first CC group is set by network signaling given to the terminal by the network node.

Images