Method performed by UE or base station in wireless communication system, and apparatus therefor

Abstract

A method performed by a UE, according to at least one of embodiments disclosed in the present specification, may comprise: receiving configuration information including a plurality of physical cell IDs (PCIs) related to inter-cell beam management (ICBM); performing first measurement on the basis of a plurality of signals related to the plurality of PCIs; on the basis of the first measurement, transmitting a first report related to preference / non-preference of the UE for each of the plurality of PCIs; performing second measurement on the basis of signals for preferred PCIs, excluding non-preferred PCIs from among the plurality of PCIs; and on the basis that the second measurement satisfies a UE-initiated beam reporting condition, transmitting a second report on the second measurement.

Description

Method performed by a terminal or base station in a wireless communication system and device therefor

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for transmitting or receiving uplink / downlink wireless signals by a terminal or base station in a wireless communication system.

[0002] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single-carrier frequency division multiple access (SC-FDMA).

[0003] The existing NR standard defines that base stations provide terminals with configuration information for beam measurement / reporting for beam management. This configuration information explicitly indicates the beams that the terminal should measure / report.

[0004] Depending on the channel environment, for example, in an environment where the terminal has high mobility, the terminal must frequently perform beam measurement reports to find the optimal beam. In this case, problems such as reference signal overhead, terminal measurement / reporting overhead, and increased power consumption arise.

[0005] The technical task of the present disclosure is to provide a method and a device for efficiently performing a wireless signal transmission and reception process. For example, a method and a device for more efficiently transmitting and receiving beam measurement reports between a terminal and a base station through a UE-initiated measurement report can be provided.

[0006] Other technical challenges can be inferred from the detailed description.

[0007] According to one aspect of the present disclosure, a method performed by a terminal may include receiving configuration information including a plurality of physical cell IDs (PCIs) related to inter-cell beam management (ICBM); performing a first measurement based on a plurality of signals related to the plurality of PCIs; transmitting a first report related to a preference / non-preference of the terminal for each of the plurality of PCIs based on the first measurement; performing a second measurement based on signals for preferred PCIs, excluding non-preferred PCIs among the plurality of PCIs; and transmitting a second report for the second measurement based on whether the second measurement satisfies a terminal-initiated beam reporting condition.

[0008] The above second report may be a terminal-initiated beam report for inter-cell beam management.

[0009] A PCI subset may be configured based on the preferred PCIs of the terminal. The PCI subset may be updated based on the second measurement reported through the second report.

[0010] The second report may include measurement values ​​of up to N beams for each of the preferred PCIs.

[0011] The number of beams for each preferred PCI may be determined differently depending on the preference of each of the above preferred PCIs.

[0012] The number of preferred PCIs, M and N, can be determined based on upper layer signaling.

[0013] The number of preferred PCIs, M and N, can be determined by the terminal. The second report can include at least one of information about M and N.

[0014] The second report may include information on whether a timing advance (TA) measurement was performed for each of the preferred PCIs.

[0015] The terminal-initiated beam reporting condition may include at least one of: a case where there is a PCI having a higher beam quality than a beam quality for a PCI associated with a specific CORESET (control resource set) pool index; and a case where there is a PCI having a higher beam quality than a beam quality of a serving cell.

[0016] According to another aspect of the present disclosure, a non-transitory computer-readable recording medium having recorded thereon a program for performing the method described above may be provided.

[0017] According to another aspect of the present disclosure, a device includes a memory storing instructions; and a processor configured to perform operations by executing the instructions, wherein the operations of the processor may include receiving configuration information including a plurality of physical cell IDs (PCIs) related to inter-cell beam management (ICBM); performing a first measurement based on a plurality of signals related to the plurality of PCIs; transmitting a first report related to a preference / non-preference of the device for each of the plurality of PCIs based on the first measurement; performing a second measurement based on signals for preferred PCIs, excluding non-preferred PCIs among the plurality of PCIs; and transmitting a second report for the second measurement based on whether the second measurement satisfies a device-initiated beam reporting condition.

[0018] The device may further include a transceiver for transmitting or receiving a wireless signal under the control of the processor.

[0019] The above device may be a terminal in a wireless communication system.

[0020] The above device may be a processing device configured to control a terminal in a wireless communication system.

[0021] According to another aspect of the present disclosure, a method performed by at least one network node may include transmitting configuration information including a plurality of physical cell IDs (PCIs) related to inter-cell beam management (ICBM) to a terminal; transmitting a plurality of signals related to the plurality of PCIs; receiving a first measurement report related to preference / non-preference of the terminal for each of the plurality of PCIs; transmitting signals for preferred PCIs to the terminal, excluding non-preferred PCIs among the plurality of PCIs; and receiving a second measurement report for signals for the preferred PCIs based on satisfaction of a terminal-initiated beam reporting condition at the terminal.

[0022] According to another aspect of the present disclosure, at least one network node comprises at least one memory storing commands; and at least one processor performing operations by executing the commands, wherein the operations of the at least one processor may include transmitting configuration information including a plurality of physical cell IDs (PCIs) related to inter-cell beam management (ICBM) to a terminal; transmitting a plurality of signals related to the plurality of PCIs; receiving a first measurement report related to preference / non-preference of the terminal for each of the plurality of PCIs; transmitting signals for preferred PCIs, excluding non-preferred PCIs among the plurality of PCIs, to the terminal; and receiving a second measurement report for signals for the preferred PCIs based on satisfaction of a terminal-initiated beam reporting condition at the terminal.

[0023] According to the present disclosure, wireless signal transmission and reception can be efficiently performed in a wireless communication system. For example, information regarding a UE's preferred / non-preferred cell and / or related reference signal resource set is provided to the network through UE-initiated inter-cell beam management (ICBM) beam reporting, thereby enabling the UE and the network to operate more efficiently.

[0024] Other technical effects can be inferred from the detailed description.

[0025] Figure 1 illustrates physical channels used in a 3GPP system, which is an example of a wireless communication system, and a general signal transmission method using the channels.

[0026] Figure 2 illustrates the structure of a radio frame.

[0027] Figure 3 illustrates a resource grid of slots.

[0028] Figure 4 illustrates an example of physical channels being mapped within a slot.

[0029] Figure 5 illustrates the PDSCH and ACK / NACK transmission process.

[0030] Figure 6 illustrates a PUSCH transmission process.

[0031] Figure 7 shows an example of a CSI-related procedure.

[0032] FIGS. 8 and 9 each illustrate a beam measurement reporting process according to one embodiment.

[0033] FIG. 10 illustrates a flow of a method performed by a terminal according to one embodiment.

[0034] FIG. 11 illustrates a flow of a method performed by at least one network node according to one embodiment.

[0035] Figures 12 to 15 illustrate a communication system (1) and a wireless device applicable to the present disclosure.

[0036] The following technologies can be 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 with radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented with radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented with radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) 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.

[0037] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing RAT (Radio Access Technology) is emerging. Furthermore, massive MTC (Machine Type Communications), which connects multiple devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced Mobile BroadBand Communication (eMBB), massive MTC, and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. For convenience, this technology is referred to as NR (New Radio or New RAT) in the present invention.

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

[0039] In this specification, the expression "setting" can be replaced with the expression "configure / configuration", and the two can be used interchangeably. In addition, conditional expressions (e.g., "if", "in a case", or "when", etc.) can be replaced with the expression "based on that ~~" or "in a state / status". In addition, the operation of the terminal / base station or the SW / HW configuration according to the satisfaction of the condition can be inferred / understood. In addition, if the process of the receiving (or transmitting) side can be inferred / understood from the process of the transmitting (or receiving) side in signal transmission / reception between wireless communication devices (e.g., base stations, terminals), the description thereof can be omitted. For example, signal determination / generation / encoding / transmission, etc. of the transmitting side can be understood as signal monitoring reception / decoding / determination, etc. of the receiving side. In addition, the expression that the terminal performs (or does not perform) a specific operation can also be interpreted as meaning that the base station operates while expecting / assuming (or expecting / assuming that the terminal does not perform) the specific operation. In addition, the expression that the base station performs (or does not perform) a specific operation can also be interpreted as meaning that the terminal operates while expecting / assuming (or expecting / assuming that the base station does not perform) the specific operation. In addition, the division and index of each section, embodiment, example, option, method, plan, etc. in the following description are for the convenience of explanation and should not be interpreted as meaning that each constitutes an independent invention or that each must be implemented only individually. In addition, in describing each section, embodiment, example, option, method, plan, etc., if there is no explicitly conflicting / opposing description, it can be inferred / interpreted that at least some of them can be combined and implemented together, or at least some can be implemented with the omission of each.

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

[0041] Figure 1 is a drawing for explaining physical channels used in a 3GPP NR system and a general signal transmission method using them.

[0042] When a terminal is powered on again from a powered-off state or enters a new cell, it performs an initial cell search operation, such as synchronizing with the 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). Based on the PSS / SSS, the terminal synchronizes with the base station and obtains information such as a cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell based on the PBCH. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

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

[0044] Thereafter, the terminal may perform a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal may transmit a preamble through a physical random access channel (PRACH) (S103) and receive a response message to the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, a contention resolution procedure such as transmission of an additional physical random access channel (S105) and reception of a physical downlink control channel and a corresponding physical downlink shared channel (S106) may be performed.

[0045] The terminal that has performed the procedure as described above can then perform the general uplink / downlink signal transmission procedure, such as receiving a physical downlink control channel / physical downlink shared channel (S107) and transmitting a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108). The control information that the terminal transmits 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 through PUCCH, but can be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, UCI can be transmitted aperiodically via PUSCH upon request / instruction from the network.

[0046] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are organized into frames. Each radio frame is 10 ms long and is divided into two 5 ms half-frames (HF). Each half-frame is divided into five 1 ms sub-frames (SF). A sub-frame is divided into one or more slots, and the number of slots within a sub-frame depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM (Orthogonal 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 OFDM symbols.

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

[0048] SCS (15*2^u)N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

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

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

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

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

[0053] SCS (15*2^u)N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0054] The structure of the frame is only an example, and the number of subframes, number of slots, and number of symbols in the frame can be varied.

[0055] In an NR system, OFDM numerology (e.g., SCS) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbol).

[0056] Figure 3 illustrates a resource grid of a slot. A slot contains multiple symbols in the time domain. For example, in the case of a regular CP, one slot contains 14 symbols, but in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) is defined as multiple consecutive Physical RBs (PRBs) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can contain up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0057] Figure 4 illustrates an example of how physical channels are mapped within a slot. A PDCCH can be transmitted in the DL control region, and a PDSCH can be transmitted in the DL data region. A PUCCH can be transmitted in the UL control region, and a PUSCH can be transmitted in the UL data region. GP provides a time gap between the base station and the terminal when switching from transmission mode to reception mode or from reception mode to transmission mode. Some symbols within a subframe at the time of transition from DL to UL can be set as GP.

[0058] Below, each physical channel is described in more detail.

[0059] 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 upper layer control messages such as random access responses transmitted on the PDSCH, transmission power control commands, activation / deactivation of Configured Scheduling (CS), etc. 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 usage 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 for paging, the CRC is masked with the Paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a System Information Block, SIB), the CRC is masked with the System Information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the Random Access-RNTI (RA-RNTI).

[0060] 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 depending on the radio channel status. A CCE consists of six Resource Element Groups (REGs). A REG is defined as one OFDM symbol and one (P)RB. The PDCCH is transmitted through a Control Resource Set (CORESET). A CORESET is defined as a set of REGs with a given numerology (e.g., SCS, CP length, etc.). Multiple CORESETs for a single UE can overlap in the time / frequency domain. A CORESET can be configured through system information (e.g., Master Information Block, MIB) or UE-specific upper layer (e.g., Radio Resource Control, RRC, layer) signaling. Specifically, the number of RBs and the number of OFDM symbols (up to 3) that constitute the CORESET can be set by upper layer signaling.

[0061] To receive / detect PDCCH, the UE monitors PDCCH candidates. PDCCH candidates represent the CCE(s) that the UE should monitor for PDCCH detection. Each PDCCH candidate is defined as 1, 2, 4, 8, or 16 CCEs depending on the AL. Monitoring involves (blind) decoding the PDCCH candidates. The set of PDCCH candidates that the UE monitors is defined as a PDCCH Search Space (SS). The search space includes a Common Search Space (CSS) or a UE-specific search space (USS). The UE can acquire DCI by monitoring PDCCH candidates in one or more search spaces configured by the 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 can be defined based on the following parameters.

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

[0063] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period (in slots) and the PDCCH monitoring interval offset (in slots).

[0064] - monitoringSymbolsWithinSlot: Indicates the PDCCH monitoring symbols within the slot (e.g., the first symbol(s) of the CORESET).

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

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

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

[0068] TypeSearch SpaceRNTIUse CaseType0-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType0A-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType1-PDCCHCommonRA-RNTI or TC-RNTI on a primary cellMsg2, Msg4 decoding in RACHType2-PDCCHCommonP-RNTI on a primary cellPaging DecodingType3-PDCCHCommonINT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI(s)UE SpecificUE SpecificC-RNTI, or MCS-C-RNTI, or CS-RNTI(s)User specific PDSCH decoding

[0069] Table 4 illustrates DCI formats transmitted via PDCCH.

[0070] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

[0071] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule a TB-based (or TB-level) PUSCH or a CBG (Code Block Group)-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 can be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 may be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to the terminal, and DCI format 2_1 is used to convey downlink pre-emption information to the terminal. DCI format 2_0 and / or DCI format 2_1 can be conveyed to the terminals within a group through the group common PDCCH, which is a PDCCH conveyed to the terminals defined as a group.

[0072] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI format, the DCI size / field configuration remains the same regardless of the terminal configuration. On the other hand, in the non-fallback DCI format, the DCI size / field configuration varies depending on the terminal configuration.

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

[0074] PUCCH carries Uplink Control Information (UCI). UCI includes:

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

[0076] - HARQ(Hybrid Automatic Repeat reQuest)-ACK(Acknowledgement): This is a response to a downlink data packet (e.g., codeword) on the PDSCH. It indicates whether the downlink data packet was successfully received. One HARQ-ACK bit can be transmitted in response to a single codeword, and two HARQ-ACK bits can be transmitted in response to two codewords. The HARQ-ACK response includes a positive ACK (simply, ACK), a negative ACK (NACK), a DTX, or a NACK / DTX. Here, HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

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

[0078] Table 5 illustrates PUCCH formats. Depending on the PUCCH transmission length, they can be classified into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3, and 4).

[0079] PUCCH formatLength in OFDM symbols N PUCCH symb Number of bitsUsageEtc01 - 2≤2HARQ, SRSequence selection14 - 14≤2HARQ, [SR]Sequence modulation21 - 2>2HARQ, CSI, [SR]CP-OFDM34 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(no UE multiplexing)44 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(Pre DFT OCC)

[0080] PUCCH format 0 carries UCI of up to 2 bits in size and is mapped and transmitted based on sequence. Specifically, the terminal transmits a specific UCI to the base station by transmitting one of multiple sequences through the PUCCH of PUCCH format 0. The terminal transmits the PUCCH of PUCCH format 0 within the PUCCH resources for the corresponding SR configuration only when transmitting a positive SR.

[0081] PUCCH format 1 carries UCI of up to 2 bits in size, and modulation symbols are spread in the time domain using an orthogonal cover code (OCC) (which is set differently depending on whether frequency hopping is used). DMRS are transmitted in symbols where modulation symbols are not transmitted (i.e., transmitted using Time Division Multiplexing (TDM).

[0082] PUCCH format 2 carries UCI with a bit size greater than 2 bits, and modulation symbols are transmitted by frequency division multiplexing (FDM) with DMRS. DM-RSs are located at symbol indices #1, #4, #7, and #10 within a given resource block with a density of 1 / 3. Pseudo Noise (PN) sequences are used for DM_RS sequences. Frequency hopping can be enabled for 2-symbol PUCCH format 2.

[0083] PUCCH format 3 does not multiplex terminals within the same physical resource blocks and carries UCI with a bit size greater than 2 bits. In other words, PUCCH resources in PUCCH format 3 do not include orthogonal cover codes. Modulation symbols are transmitted through time division multiplexing (TDM) with DMRS.

[0084] PUCCH format 4 supports multiplexing of up to four terminals within the same physical resource blocks and carries UCI with a bit size greater than 2 bits. In other words, PUCCH resources in PUCCH format 3 include orthogonal cover codes. Modulation symbols are transmitted through time division multiplexing (TDM) with DMRS.

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

[0086] 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 CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplexing) waveform or a DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplexing) waveform. When the PUSCH is transmitted based on a DFT-s-OFDM waveform, the UE transmits the PUSCH by applying transform precoding. For example, when transform precoding is disabled (e.g., transform precoding is disabled), the UE transmits the PUSCH based on the CP-OFDM waveform, and when transform precoding is enabled (e.g., transform precoding is enabled), the UE can transmit the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions can be 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 performed in a codebook-based or non-codebook-based manner.

[0087] Figure 5 illustrates an ACK / NACK transmission process. Referring to Figure 5, a terminal can detect a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0, 1_1), and the PDCCH indicates a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 can include the following information:

[0088] - Frequency domain resource assignment: Indicates the set of RBs allocated to the PDSCH.

[0089] - Time domain resource assignment: K0 (e.g., slot offset), indicates 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).

[0090] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1

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

[0092] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources within the PUCCH resource set.

[0093] Afterwards, the terminal receives PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and when reception of PDSCH is finished in slot #n1 (where, n+K0≤n1), UCI can be transmitted through PUCCH in slot #(n1+K1). Here, UCI may include HARQ-ACK response for PDSCH. In Fig. 5, for convenience, it is assumed that SCS for PDSCH and SCS for PUCCH are the same and slot # n1 = slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 can be indicated / interpreted based on the SCS of PUCCH.

[0094] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and may consist of 1 bit if spatial bundling is configured. When the HARQ-ACK transmission timing for multiple PDSCHs is designated as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

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

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

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

[0098] 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 bit value 1. Consequently, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0099] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. These multiple parallel HARQ processes allow DL transmissions to be performed continuously while waiting for HARQ feedback regarding the success or failure of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables such as the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0100] Figure 6 illustrates a PUSCH transmission process. Referring to Figure 6, a terminal can detect 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 can include the following information.

[0101] - Frequency domain resource assignment: Indicates the set of RBs allocated to PUSCH.

[0102] - Time domain resource assignment: Slot offset K2 indicates 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 can be indicated through SLIV (Start and Length Indicator Value) or can be indicated separately.

[0103] Thereafter, the terminal can transmit a PUSCH in slot #(n+K2) according to the scheduling information of slot #n. Here, the PUSCH includes a UL-SCH TB.

[0104] CSI-related actions

[0105] Figure 7 shows an example of a CSI-related procedure.

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

[0107] - CSI-IM resources can be configured for interference measurement (IM) of the terminal. In the time domain, the CSI-IM resource set can be configured periodically, semi-persistently, or aperiodicly. The CSI-IM resources can be configured as Zero Power (ZP)-CSI-RS for the terminal. The ZP-CSI-RS can be configured separately from the Non-Zero Power (NZP)-CSI-RS.

[0108] - The UE may assume that the CSI-RS resource(s) for channel measurement configured for one CSI reporting and the CSI-IM / NZP CSI-RS resource(s) for interference measurement (when NZP CSI-RS resource(s) are used for interference measurement) are in a QCL relationship with respect to 'QCL-TypeD' per resource.

[0109] - The CSI resource configuration may include 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. The CMR (channel measurement resource) may be an NZP CSI-RS for CSI acquisition, and the IMR (Interference measurement resource) may be an NZP CSI-RS for CSI-IM and IM.

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

[0111] - The CSI report configuration may include configurations for feedback type, measurement resources, report type, etc. The NZP-CSI-RS resource set may be used for the CSI report configuration of the corresponding terminal. The NZP-CSI-RS resource set may be associated with CSI-RS or SSB. In addition, multiple periodic NZP-CSI-RS resource sets may be configured as TRS resource sets. (i) The feedback type may include 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) Measurement resources may include configurations for downlink signals and / or downlink resources on which the terminal performs measurements to determine feedback information. The measurement resources may be configured as ZP and / or NZP CSI-RS resource sets associated with CSI reporting configurations. The NZP CSI-RS resource set may include a CSI-RS set or an SSB set. For example, L1-RSRP may be measured for a CSI-RS set or an SSB set. (iii) Reporting types may include configurations for a time point at which the terminal performs reporting and an uplink channel, etc. The reporting time point may be configured as periodic, semi-persistent, or aperiodic. Periodic CSI reporting may be transmitted on PUCCH. Semi-persistent CSI reporting may be transmitted on PUCCH or PUSCH based on a MAC CE indicating activation / deactivation. Aperiodic CSI reporting may be indicated by DCI signaling.For example, the CSI request field of an uplink grant may indicate one of several report trigger sizes. Aperiodic CSI reports may be transmitted on the PUSCH.

[0112] The terminal measures CSI based on configuration information related to CSI. CSI measurement may include a procedure of receiving a CSI-RS (720) and computing the received CSI-RS to acquire CSI (730).

[0113] The UE can transmit a CSI report to the base station (740). For the CSI report, the time and frequency resources that the UE can use are controlled by the base station. The CSI (channel state information) can include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), L1-RSRP, and / or L-SINR.

[0114] The time domain behavior of CSI reporting supports periodic, semi-persistent, and aperiodic. i) Periodic CSI reporting is performed on short PUCCH and long PUCCH. The periodicity and slot offset of periodic CSI reporting can be configured by RRC, and refer to the CSI-ReportConfig IE. ii) SP (semi-periodic) CSI reporting is performed on short PUCCH, long PUCCH, or PUSCH. In case of SP CSI on short / long PUCCH, the periodicity and slot offset are configured by RRC, and CSI reporting is activated / deactivated by separate MAC CE / DCI. In case of 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). For SP CSI reporting on PUSCH, a separate RNTI (SP-CSI C-RNTI) is used. The initial CSI reporting timing follows the PUSCH time domain allocation value indicated in the DCI, and subsequent CSI reporting timings follow the cycle set by RRC. DCI format 0_1 ​​includes a CSI request field and can activate / deactivate a specific configured SP-CSI trigger state. SP CSI reporting has the same or similar activation / deactivation mechanism as the data transmission mechanism on the SPS PUSCH.iii) Aperiodic CSI reporting is performed on PUSCH and is triggered by DCI. In this case, information related to the triggering of aperiodic CSI reporting can be transmitted / indicated / configured via MAC-CE. For AP CSI with AP CSI-RS, the AP CSI-RS timing is configured by RRC, and the timing for AP CSI reporting is dynamically controlled by DCI.

[0115] Beam Management (BM)

[0116] BM procedures are L1 (layer 1) / L2 (layer 2) procedures for acquiring and maintaining a set of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams that can be used for downlink (DL) and uplink (UL) transmission / reception, and may include the following procedures and terminology.

[0117] - Beam measurement: An operation in which a base station or UE measures the characteristics of a received beam-forming signal.

[0118] - Beam determination: An operation in which a base station or UE selects its own transmit beam (Tx beam) / receive beam (Rx beam).

[0119] - Beam sweeping: The operation of covering a spatial area using a transmit and / or receive beam over a predetermined time interval in a predetermined manner.

[0120] - Beam report: An operation in which a UE reports information about a beam-formed signal based on beam measurement.

[0121] The BM procedure can be divided into (1) a DL BM procedure using SS (synchronization signal) / PBCH (physical broadcast channel) Block or CSI-RS, and (2) a UL BM procedure using SRS (sounding reference signal).

[0122] Additionally, each BM procedure may include Tx beam sweeping to determine the Tx beam and Rx beam sweeping to determine the Rx beam.

[0123] DL BM

[0124] The DL BM procedure may include transmission of beamformed DL RSs (reference signals) (e.g., CSI-RS or SS Block (SSB)) of the base station and beam reporting of the terminal.

[0125] Here, beam reporting may include preferred DL RS ID(identifier)(s) and corresponding L1-RSRP (Reference Signal Received Power).

[0126] The above DL RS ID may be an SSBRI (SSB Resource Indicator) or a CRI (CSI-RS Resource Indicator).

[0127] Both SSB and CSI-RS beams can be used for beam measurement. The measurement metric is L1-RSRP per resource / block. SSB is used for coarse beam measurement, and CSI-RS can be used for fine beam measurement. SSB can be used for both Tx beam sweeping and Rx beam sweeping.

[0128] (1) SSB beam

[0129] Rx beam sweeping using SSB can be performed by the UE changing the Rx beam for the same SSBRI across multiple SSB bursts, where one SS burst contains one or more SSBs, and one SS burst set contains one or more SSB bursts.

[0130] The configuration for beam reporting using SSB is performed during CSI / beam configuration in the RRC connected state (or RRC connected mode). The terminal receives a CSI-ResourceConfig IE containing a CSI-SSB-ResourceSetList containing SSB resources used for BM from the base station.

[0131] (2) CSI-RS beam

[0132] Looking at the usage of CSI-RS, i) if the repetition parameter is set to a specific CSI-RS resource set and trs-Info is not set, CSI-RS is used for beam management. ii) if the repetition parameter is not set and trs-Info is set, CSI-RS is used for TRS (tracking reference signal). iii) if the repetition parameter is not set and trs-Info is not set, CSI-RS is used for CSI acquisition.

[0133] This repetition parameter can only be set for CSI-RS resource sets associated with a CSI-ReportConfig that is set to report L1 RSRP or 'No Report (or None)'.

[0134] If the terminal receives a CSI-ReportConfig with reportQuantity set to 'cri-RSRP', 'cri-SINR' or 'none', and if the CSI-ResourceConfig for channel measurement (higher layer parameter resourcesForChannelMeasurement) includes an NZP-CSI-RS-ResourceSet with higher layer parameter 'repetition' set but without higher layer parameter 'trs-Info', the terminal may only configure all CSI-RS resources in the NZP-CSI-RS-ResourceSet with the same number of ports (1-port or 2-port) with the higher layer parameter 'nrofPorts'.

[0135] (higher layer parameter) When repetition is set to 'ON', it is related to the Rx beam sweeping procedure of the terminal. In this case, when the terminal receives an NZP-CSI-RS-ResourceSet with repetition set to 'ON', the terminal can assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same Tx beam. Here, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet can be transmitted in a different OFDM symbol. In addition, the terminal does not expect to receive different periods in periodicityAndOffset among all CSI-RS resources in the NZP-CSI-RS-Resourceset.

[0136] On the other hand, when Repetition is set to 'OFF', it is related to the Tx beam sweeping procedure of the base station. In this case, when repetition is set to 'OFF', the terminal does not assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through a different Tx beam.

[0137] - The terminal receives an NZP CSI-RS resource set IE including a higher layer parameter repetition from the base station via RRC signaling. Here, the repetition parameter is set to 'ON'.

[0138] - The terminal repeatedly receives CSI-RS resource(s) within the NZP CSI-RS resource set with repetition 'ON' in different OFDM symbols through the same Tx beam (or DL ​​spatial domain transmission filter) of the base station.

[0139] - The terminal determines its own Rx beam.

[0140] - The terminal omits the CSI report. In this case, the reportQuantity of the CSI report config can be set to 'No report (or None)'.

[0141] That is, the terminal can omit the CSI report when repetition is set to 'ON'.

[0142] DL BM related beam indication

[0143] A UE may receive an RRC configuration list of at most M candidate Transmission Configuration Indication (TCI) states for the purpose of at least a Quasi Co-location (QCL) indication. Here, M may vary depending on the capability of the UE and may be, for example, 64.

[0144] Each TCI state can be configured with one RS set. At least each ID of a DL RS for spatial QCL purposes (QCL Type D) within an RS set can refer to one of the DL RS types, such as SSB, P-CSI RS, SP-CSI RS, or A-CSI RS.

[0145] At least the initialization / update of the IDs of DL RS(s) within the RS set used for spatial QCL purposes can be performed at least through explicit signaling.

[0146] Rel-16 / 17 enhancement

[0147] In Rel-16, enhancements were made not only for beam / PL RS indication but also for beam reporting. Rel-15 supports a mode in which the terminal measures / reports the L1-RSRP for each beam RS. However, in an environment with high inter-beam interference, it is difficult to guarantee that the RS has good quality as a serving beam just because the L1-RSRP of a specific beam RS is high, i.e., the reception intensity is high. In other words, the terminal may select a beam with high reception intensity but also high beam interference and report it to the base station. To overcome this drawback, Rel-16 newly supports a beam reporting mode in which the base station sets resources for interference measurement as well as RS for channel measurement, and the terminal measures the L1-SINR for the corresponding channel resource and interference resource based on this and reports several RSs with high L1-SINR values.

[0148] In this way, various BM enhancements were made in Rel-16. In particular, features were created that can significantly reduce signaling overhead / latency related to beam indication methods. However, beams were still not configured / indicated in an integrated channel / RS manner for terminals operating with a single serving beam. Based on this motivation, Rel-17 standardized a method for integrated channel / RS beam configuration / indication. In NR, DL beams are indicated through the transmit configuration indicator (TCI), so this is called the unified TCI state. While the existing TCI state was configured / indicated separately for each DL RS / channel, the unified TCI state is characterized by integrated configuration / indication. Basically, the DL unified TCI state indicates QCL type-D RS that is integrated and applied to (some) PDCCH, PDSCH, and (some) CSI-RS resources, and the UL unified TCI state indicates spatial relation RS (and PL RS) that is integrated and applied to (some) PUCCH, PUSCH, and (some) SRS resources. In addition, similar to the Rel-16 default spatial relation / PL RS feature, the UL spatial relation and PL RS can also be aligned with the DL beam RS for UEs that establish beam correspondence, so the channels / RSs to which the unified TCI state is applied can encompass both DL and UL channels / RSs. This is called a joint DL / UL TCI state. That is, the following two modes are supported.

[0149] - Joint DL / UL TCI Setting / Instruction Mode: The DL RS set / instructed as the Joint TCI state is applied not only as the QCL type-D source RS for the DL channel / RS, but also as the spatial relation RS (and PL RS) for the UL channel / RS. That is, when the joint TCI state is instructed to update, the beam RS (and PL RS) for the corresponding DL channel / RS and UL channel / RS are changed together.

[0150] - Separate DL and UL TCI configuration / indication mode: QCL type-D source RS for DL ​​channels / RSs are integrated and configured / indicated as DL TCI state, and spatial relation RS (and PL RS) for UL channels / RSs are integrated and configured / indicated as UL TCI state. Here, DL TCI state and UL TCI state are separately configured / indicated.

[0151] The above DL / UL / joint TCI states will be indicated / updated via MAC-CE and / or DCI. More specifically, one or more TCI states will be activated via MAC-CE among multiple TCI states configured via RRC (called TCI state pool). If multiple TCI states are activated via MAC-CE, one of the TCI states will be indicated via DCI. This DCI indication will be supported via downlink DCI formats (DCI1-1 / 1-2) that support the TCI field, and can be supported both with and without PDSCH scheduling. In the latter case, since PDSCH scheduling is omitted (similar to the DCI-based semi-persistent scheduling (SPS) release method), ACK transmission by the terminal for the corresponding DCI can be supported.

[0152] The Rel-17 beam report mode can support a mode in which the terminal measures / reports the optimal beam RS for each TRP, targeting a multi-TRP environment. To this end, the beam measurement RS set / group can be divided into two subsets / sub-groups, which the base station configures, and the terminal can then select RS(es) for each subset / sub-group and report them along with the quality value (L1-RSRP, [L1-SINR]) of the corresponding RS.

[0153] QCL (quasi-co location)

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

[0155] Regarding PDCCH / PDSCH QCL, multiple Transmission Configuration Indication (TCI) states can be configured to the terminal via higher layer signaling. Up to 64 TCI states can be configured via RRC for PDCCH QCL, and up to 128 TCI states can be configured via RRC for PDSCH QCL. For PDSCH QCL, a list for configuring multiple TCI-States can be provided via the higher layer parameter PDSCH-Config.

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

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

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

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

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

[0161] TCI states set through RRC signaling are deactivated by default.

[0162] For PDSCH QCL, up to eight TCI states can be activated through MAC CE among the RRC configured TCI states. The TCI field included in the DCI scheduling the PDSCH can indicate one of the activated TCI states (e.g., if the provision of the TCI field in the corresponding DCI is activated via RRC signaling), and the UE can receive the PDSCH based on the QCL information corresponding to the indicated TCI state.

[0163] For PDCCH QCL, one TCI state can be activated for the corresponding CORESET through MAC CE among the RRC configured TCI states. To receive the PDCCH in the corresponding CORESET, the UE can receive the PDCCH based on the QCL information corresponding to the activated TCI state.

[0164] M-TRP (multiple-transmission / reception point) related operations

[0165] The M-TRP transmission method, in which M TRPs transmit data to one terminal, can be broadly divided into two types: 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.

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

[0167] That is, when the DL M-TRP URLLC transmission method is set, the terminal can receive the same data / DCI using different space / time / frequency resources. At this time, the terminal can receive an indication from the base station about the QCL RS / type (i.e., DL TCI state) used in the space / time / frequency resources for receiving the corresponding data / DCI.

[0168] For example, if the corresponding data / DCI is received from resource 1 and resource 2, the terminal can be instructed by the base station about the DL TCI state used in resource 1 and the DL TCI state used in resource 2. By receiving the corresponding data / DCI through resource 1 and resource 2, high reliability can be achieved. This M-TRP URLLC transmission method can be applied to PDSCH / PDCCH.

[0169] UL M-TRP URLLC transmission method refers to a method in which multiple TRPs receive the same data / UCI from a terminal using different space / time / frequency resources. For example, TRP 1 can receive the same data / UCI from a terminal on resource 1, and TRP 2 can receive the same data / UCI from a terminal on resource 2. In addition, TRP 1 and TRP 2 can share the data / UCI received from the terminal through a backhaul link (connected between TRPs).

[0170] That is, when the UL M-TRP URLLC transmission method is set, the terminal can transmit the same data / UCI to each TRP using different space / time / frequency resources. At this time, the terminal can be instructed by the base station about the Tx beam and Tx power (i.e., UL TCI state) to be used in the space / time / frequency resources for transmitting the same data / UCI. For example, when the same data / UCI is transmitted in resource 1 and resource 2, the terminal can be instructed by the base station about the UL TCI state used in resource 1 and the UL TCI state used in resource 2. This UL M-TRP URLLC can be applied to PUSCH / PUCCH.

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

[0172] In relation to M-TRP transmission and reception in Rel-16 NR standardization, PDSCH transmission and reception according to S-DCI-based M-TRP transmission method and M-DCI-based M-TRP transmission method are supported.

[0173] First, we will look at the S-DCI-based M-TRP PDSCH transmission method.

[0174] S-DCI-based M-TRP PDSCH transmission can use one of SDM / FDM / TDM methods. In the case of SDM, the base station transmits one TB using multiple layers, and transmits layers belonging to different DMRS CDM groups using different transmit beams (i.e., QCL RS or TCI states). This can increase the number of layers compared to the existing 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 the remaining layers are transmitted to TRP 2, which can improve channel reliability due to diversity gain.

[0175] For FDM, two schemes, scheme 2a and 2b, are supported. Here, scheme 2a transmits one TB to multi-RBs, but transmits RBs belonging to different RB groups with different Tx beams (i.e., QCL RS or TCI states). Scheme 2b transmits the same TB to different RB groups, but transmits RBs belonging to different RB groups with different Tx beams (i.e., QCL RS or TCI states). For TDM, two schemes, scheme 3 and 4, are supported. Here, scheme 4 (i.e., inter-slot TDM) repeatedly transmits the same TB in multiple slots, but transmits slots belonging to different slot groups with different Tx beams (i.e., QCL RS or TCI states). On the other hand, Scheme 3 (i.e., intra-slot TDM) repeatedly transmits the same TB in multiple OFDM symbol groups, but transmits some OFDM symbol groups and the remaining OFDM symbol groups with different Tx beams (i.e., QCL RS or TCI state).

[0176] Next, we will look at the M-DCI-based M-TRP PDSCH transmission method.

[0177] M-DCI based MTRP PDSCH transmission is a method in which each TRP schedules and transmits PDSCH through DCI. That is, TRP 1 transmits PDSCH 1 through DCI 1, and TRP 2 transmits PDSCH 2 through DCI 2. When PDSCH 1 and PDSCH 2 overlap in the same frequency / time resource, two PDSCHs are received for the same RE, which increases resource efficiency and increases transmission capacity. To this end, the concept of a CORESET pool, which refers to a group of multiple CORESETs, was introduced. For example, TRP 1 transmits a PDCCH through a CORESET belonging to CORESET pool 0, and also transmits the PDSCH scheduled by the PDCCH. TRP 2 transmits a PDCCH through a CORESET belonging to CORESET pool 1, and also transmits the PDSCH scheduled by the PDCCH.

[0178] Even for PUSCH, specific TRPs can schedule PUSCH transmissions to UEs via CORESETs within each COERSET pool. For example, some PUCCH resources may be scheduled by TRP 1, while the remaining PUCCH resources may be scheduled by TRP 2. UEs can transmit independent PUSCH / PUCCHs for each of TRPs 1 and 2.

[0179] In addition, the terminal may recognize the PUSCH (or PUCCH) scheduled by the DCI received based on different CORESETs (or CORESETs belonging to different CORESET groups) as a PUSCH (or PUCCH) transmitted to different TRPs or as a PUSCH (or PUCCH) of different TRPs. In addition, the method for UL transmission (e.g., PUSCH / PUCCH) transmitted to different TRPs can be equally applied to UL transmission transmitted to different panels belonging to the same TRP.

[0180] Hereinafter, the CORESET group ID (or COERSET pool index having the same meaning) may mean an index / identification information (e.g., ID) for distinguishing the CORESET for each TRP / panel. And the CORESET group may mean a group / union of CORESETs distinguished by an index / identification information (e.g., ID) / CORESET group ID for distinguishing the CORESET for each TRP / panel. For example, the CORESET group ID may be specific index information defined in the CORESET configuration. That is, the CORESET group may be set / indicated / defined by an index defined in the CORESET configuration for each CORESET. And / or, the CORESET group ID may mean an index / identification information / indicator for distinguishing / identifying between the CORESETs set / associated in each TRP / panel.

[0181] Hereinafter, the CORESET group ID may be replaced with a specific index / specific identification information / specific indicator for distinguishing / identifying the CORESETs set / associated with each TRP / panel. The information may be set / indicated via higher layer signaling (e.g., RRC signaling, MAC-CE, etc.) and / or physical layer signaling (e.g., DCI). For example, PDCCH detection may be set / indicated to be performed for each TRP / panel in units of the corresponding CORESET group, and UCI (e.g., CSI, HARQ-ACK / NACK, SR, etc.) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) may be set / indicated to be managed / controlled separately for each TRP / panel in units of the corresponding CORESET group. And / or, HARQ ACK / NACK (process / retransmission) for PDSCH / PUSCH, etc. scheduled for each TRP / panel by CORESET group unit can be managed.

[0182] For example, the upper layer parameter ControlResourceSet IE (information element) may include a CORESET related ID (e.g., controlResourceSetID) / CORESET pool index for CORESET (e.g., CORESETPoolIndex) / time / frequency resource settings of CORESET / TCI information related to CORESET, etc. For example, the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1. In the description above in the present disclosure, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex).

[0183] Additionally, with respect to M-TRP transmission and reception in Rel-17 NR standardization, M-TRP PDCCH / PDSCH SFN transmission, S-DCI-based M-TRP PUSCH repeated transmission, and single PUCCH resource-based M-TRP PUCCH repeated transmission are supported. These transmission techniques repeatedly transmit the same contents (i.e., DCI / UL TB / UCI, etc.) with improved URLLC target for increased reliability. Here, M-TRP PDCCH repeated transmission is performed based on TDM or FDM, M-TRP PDCCH / PDSCH SFN transmission is performed in the same time / frequency / layer, S-DCI-based M-TRP PUSCH repeated transmission is performed based on TDM, and single PUCCH resource-based M-TRP PUCCH repeated transmission is performed based on TDM.

[0184] First, we will look at the S-DCI-based M-TRP PDCCH repetition transmission method.

[0185] In the NR Rel-17 standardization, multiple CORESETs with different TCI states (i.e., different QCL RSs) are configured for the UE for repeated M-TRP PDCCH transmission, and multiple SS (Search Space) sets are configured, each linked to the corresponding CORESETs. The base station can instruct / configure the UE that the SS set connected to one CORESET and the SS set connected to another CORESET are linked for repeated transmission. Through this, the UE can be informed that the PDCCH candidates of the corresponding SS set are being repeatedly transmitted.

[0186] For example, two CORESETs, CORESET 0 and CORESET 1, may be set for a terminal, CORESET 0 and CORESET 1 may be connected to SS set 0 and SS set 1, respectively, and SS set 0 and SS set 1 may be linked. The terminal may recognize that the same DCI has been repeatedly transmitted in the PDCCH candidate of SS set 0 and the PDCCH candidate of SS set 1, and may recognize that a specific PDCCH candidate of SS set 0 and a specific PDCCH candidate of SS set 1 are a pair set for repeatedly transmitting the same DCI based on a specific rule. The two PDCCH candidates are referred to as linked PDCCH candidates, and the terminal may successfully decode the corresponding DCI if it properly receives either of the two PDCCH candidates. However, when receiving a PDCCH candidate of SS set 0, the terminal may use the QCL RS (i.e., DL beam) of the TCI state of COERSET 0 connected to SS set 0, and when receiving a PDCCH candidate of SS set 1, the terminal may use the QCL RS (i.e., DL beam) of the TCI state of COERSET 1 connected to SS set 1. Accordingly, the terminal receives linked PDCCH candidates using different beams.

[0187] Next, we will look at the M-TRP SFN PDCCH / PDSCH transmission method.

[0188] M-TRP is a type of PDCCH repetition transmission, in which multiple TRPs can repeatedly transmit the same DCI through the same time / frequency / DMRS port. This transmission method can be referred to as SFN PDCCH transmission. However, for SFN PDCCH transmission, instead of configuring multiple CORESETs with different TCI states, the base station configures multiple TCI states in a single CORESET. When a terminal receives a PDCCH candidate through an SS set connected to a single CORESET, it can perform channel estimation of the PDCCH DMRS using all of the multiple TCI states and attempt decoding.

[0189] In addition, when the above-described M-TRP PDSCH is repeatedly transmitted, the two TRPs repeatedly transmit the corresponding channel on different resources. However, if the two TRPs use the same resource, that is, if the same channel is repeatedly transmitted through the same frequency / time / layer (i.e., DMRS port), the reliability of the corresponding channel can be improved. In this case, the repeatedly transmitted same channel is not distinguished in terms of resources, so it is received by being combined during transmission (i.e., over the air), and thus can be recognized as a single channel (e.g., a composite channel) from the perspective of the receiving end (e.g., a terminal). For SFN PDSCH transmission, two DL TCI states for PDSCH DMRS reception can be set for the terminal.

[0190] Next, we will look at the S-DCI-based M-TRP PUSCH repetitive transmission scheme.

[0191] In NR Rel-17 standardization, the base station configures two SRS sets for the UE for S-DCI-based M-TRP PUSCH transmission, and each set is used to indicate the UL Tx port and UL beam / QCL information for TRP 1 and TRP 2, respectively. In addition, the base station can indicate SRS resources for each SRS resource set through two SRI fields included in one DCI, and can indicate up to two PC parameter sets. For example, the first SRI field can indicate the SRS resources and PC parameter set defined in SRS resource set 0, and the second SRI field can indicate the SRS resources and PC parameter set defined in SRS resource set 1. The UE can be indicated the UL Tx port, PC parameter set, and UL beam / QCL information for TRP 1 through the first SRI field, and through this, the UE performs PUSCH transmission in the TO corresponding to SRS resource set 0. Similarly, the terminal can be instructed about the UL Tx port, PC parameter set, and UL beam / QCL information for TRP 2 through the second SRI field, and through this, the terminal performs PUSCH transmission in the TO corresponding to SRS resource set 1. In addition to the SRI field, the TPMI, PTRS, and TPC fields can also be instructed for each TRP, so that the existing single field is expanded into two fields. In addition, by introducing a 2-bit SRS resource set indication field, STRP PUSCH repeated transmission can be performed by selecting a specific one of the two SRS sets, and MTRP PUSCH repeated transmission can be performed by selecting both.That is, if the field is 00, 01, SRS set 0 and SRS set 1 are indicated respectively, and STRP PUSCH transmission corresponding to each set is performed. If it is 10, (SRS set 0, SRS set 1) is indicated, and MTRP PUSCH transmission is performed in the indicated order of set pairs. That is, set 0 corresponds to the first PUSCH TO. If it is 11, (SRS set 1, SRS set 0) is indicated, and MTRP PUSCH transmission is performed in the indicated order of set pairs. That is, set 1 corresponds to the first PUSCH TO.

[0192] Next, we examine a single PUCCH resource-based M-TRP PUCCH repetition transmission scheme.

[0193] In NR Rel-17 standardization, for M-TRP PUCCH transmission based on a single PUCCH resource, a base station can activate / configure two spatial relation info (if FR1, activate / configure two PC parameter sets) for a single PUCCH resource to a UE. When UL UCI is transmitted through the PUCCH resource, each spatial relation info is used to indicate spatial relation info toward TRP 1 and TRP 2 to the UE. For example, through the value indicated in the first spatial relation info, the UE is instructed with Tx beam / PC parameter(s) toward TRP 1, and the UE performs PUCCH transmission at the TO corresponding to TRP 1 using the information. Similarly, through the value indicated in the second spatial relation info, the UE is instructed with Tx beam / PC parameter(s) toward TRP 2, and the UE performs PUCCH transmission at the TO corresponding to TRP 2 using the information.

[0194] In addition, for M-TRP PUCCH repeated transmission, the configuration method has been improved so that two new spatial relation info can be configured for a PUCCH resource. That is, if PC (power control) parameters such as PLRS, Alpha, P0, and Closed loop index are configured for each spatial relation info, a spatial relation RS can be configured. Consequently, PC information and spatial relation RS information corresponding to two TRPs can be configured through two spatial relation info. Through this, the terminal transmits a UCI (i.e., CSI, ACK / NACK, SR, etc.) PUCCH using the first spatial relation info in the first TO, and transmits the same UCI PUCCH using the second spatial relation info in the second TO. In the present disclosure, a PUCCH resource with two spatial relation info configured is referred to as an M-TRP PUCCH resource, and a PUCCH resource with one spatial relation info configured is referred to as an S-TRP PUCCH resource.

[0195] TCI (transmission configuration indication) state / beam indication

[0196] In addition, in describing the present disclosure, when receiving / transmitting data / DCI / UCI through specific space / time / frequency resources, using (or mapping) a specific TCI state (or TCI) may mean, 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 resources, and receiving / demodulating data / DCI / UCI with the estimated channel.

[0197] And, when receiving / transmitting data / DCI / UCI through specific space / time / frequency resources, using (or mapping) a specific TCI state (or TCI) may mean, in the case of UL, transmitting / modulating DMRS and data / UCI using a Tx beam and / or Tx power indicated by a specific TCI state in a specific space / time / frequency resource.

[0198] In addition, the UL TCI state may include Tx beam or Tx power information of the terminal. In addition, the base station may set other parameters, such as spatial relation information, to the terminal instead of the TCI state.

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

[0200] Here, the OL Tx power control parameters may include, for example, j (index for OP parameter(s) Po and alpha (set of up to 32 parameter values ​​per cell), q_d (index of DL RS resources for path loss (PL) measurement (up to 4 measurements per cell), or / and I (closed-loop power control process index (up to 2 processes per cell)).

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

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

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

[0204] In Rel.17 NR, a single DCI can schedule multiple PUSCH / PDSCHs simultaneously in ultra-high frequency bands (beyond 5.26 GHz). For example, multiple TDRAs (=TOs) can be indicated at once through the TDRA field of the PUSCH scheduling DCI, and a different TB is 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 NDI and RV for each TB are individually indicated through the DCI, and a single HARQ number is indicated, but they sequentially increase in the order of the TOs based on the initial TO.

[0205] STxMP (simultaneous transmission across multiple panels)

[0206] Recently, for the Rel. 18 NR standardization, methods for UEs to simultaneously transmit multiple channels / RSs of the same type or multiple channels / RSs of different types are being discussed. In the case of existing UEs, the operation of transmitting multiple channels / RSs at a time is restricted (e.g., simultaneous transmission of multiple SRS resources of different SRS sets is possible for UL beam measurement, but simultaneous transmission of multiple PUSCHs is not possible). However, in the future, advanced UEs will be able to relax these restrictions and transmit multiple channels or RSs simultaneously using multiple transmission panels. Such UEs are called STxMP UEs. For example, two PUSCHs corresponding to two UL TBs are scheduled on 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 set for PUSCH 1 and 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.

[0207] When a base station schedules a PUSCH through DCI, it can indicate whether the PUSCH will be transmitted as STxMP, as a single panel, or as MTRP PUSCH repetitions. Of course, the UE must have STxMP capability, and the STxMP mode must be enabled in advance, such as through RRC signaling. To achieve this, the existing SRS resource set indication field can be redefined and used, or a new DCI field can be introduced.

[0208] UE-initiated beam report for inter-cell beam management / MTRP

[0209] We propose terminal / network operations and required events for UE-initiated beam reports considering inter-cell beam management (ICBM) and inter-cell Multi-TRP (MTRP).

[0210] In the following description, 'beam' can mean source RS for 'spatial filter' or 'spatial relation', and can be interpreted as QCL (type-D) RS or (DL / UL / joint) TCI state or (in case of uplink) spatial relation RS. Beam measurement can mean measurement of a signal (e.g., reference signal) transmitted and received through the beam / beamforming. In addition, for convenience, a cell having a specific PCI can be simply referred to as PCI.

[0211] Currently, in NR, beam measurement / reporting methods and beam activation / indication of the base station are defined for beam management (BM). For example, the beam measurement / reporting of a terminal is set / instructed by the base station, and the base station can perform beam activation and beam indication instructions to the terminal based on the beam measurement / reporting of the terminal.

[0212] In NR Rel-17, beam measurement reporting for ICBM and inter-cell MTRP operations was agreed upon as shown in Table 6.

[0213] Regarding Rel.17 multi-beam measurement / reporting enhancements for L1 / L2-centric inter-cell mobility and inter-cell mTRP:- The quality of up to Kmax beams associated with non-serving cells can be reported in a single CSI reporting instance.- For each beam, the UE can report at least (1) the measured RS indicator and (2) the beam metrics associated with the measured RS indicator:- The network can mix beams associated with non-serving cells with beams associated with serving cells in a single reporting instance.- Supports at least K=4, where K is defined as the number of beams associated with non-serving cells reported in a single CSI reporting instance.- The maximum value of K, Kmax, is UE capability.- K is configured by the network according to UE capability.- For K>4, the maximum number of beams associated with a cell is 4. *Note: The above may also apply if beam metrics other than L1-RSRP are supported. Beam indication enhancements for ICBM for Rel.17, supported Rel-17 MAC-CE-based and / or DCI-based beam direction (using at least DCI format 1_1 / 1_2 with or without DL allocation, including relevant MAC-CE-based TCI state activation):- Applies to both joint TCI and separate DL / UL TCI.- Both MAC-CE-based and MAC-CE+DCI-based beam direction schemes are supported. Regarding Rel-17 enhancements for ICBM and inter-cell mTRP:- L1-RSRP reporting reuses the Rel-15 L1-RSRP table.- N MAX (The maximum number of PCIs that can be RRC configured differently from the serving cell for measurement / reporting) may vary depending on the UE capability, and its candidate values ​​include at least 1 and X. - N MAXWhen is set to X, the UE may be RRC configured to measure L1-RSRP for up to X different PCIs from the serving cell PCI. - The Rel-15 L1-RSRP reporting format is reused for all SSBRI-RSRP pairs in one L1-RSRP reporting instance, i.e., for K>1, (K-1) 4-bit differential L1-RSRP are computed for the reference (absolute) 7-bit L1-RSRP. - The CSI-SSB-ResourceSet configured for L1-RSRP measurement / reporting contains at least one set of SSB indices, each of which is associated with a PCI index. A PCI index refers to a PCI within a PCI set configured for ICBM or inter-cell multi-TRP.

[0214] Based on Table 6, beam measurements / reports to support ICBMs can be summarized as follows.

[0215] Multi-beam measurement report for L1 / L2-centered ICBM / MTRP

[0216] (1) Measurement reference signal

[0217] 1) SSB is supported, and L1-RSRP is used as the reporting quantity.

[0218] 2) The CSI-SSB-ResourceSet configured for L1-RSRP measurement / reporting includes a set of at least one SSB indices.

[0219] i. A set of SSB indices and PCI indices are linked respectively.

[0220] ii. AdditionalInfo associated with SSB(s) different from the PCI(s) of the serving cell may also be applied to the ICBM.

[0221] 3) Nmax (the number of PCIs RRC configured differently from the serving cell for measurement / reporting) is a UE capability, and candidate values ​​include 1 to 7.

[0222] i. When Nmax is set to X, L1-RSRP measurements for up to X PCIs different from the serving cell PCI can be configured in RRC on the terminal.

[0223] (2) Report content

[0224] 1) Quality and measured RS indicators of up to 4 beams

[0225] 2) In one reporting instance, beams associated with non-serving cells can be mixed with associated serving cell beams.

[0226] 3) L1-RSRP reporting reuses the Rel-15 L1-RSRP table / format.

[0227] Meanwhile, the problem with the current ICBM beam measurement / reporting process is that in environments where the terminal moves a lot or when there is a lot of movement of objects around the terminal, beam measurement / reporting must be performed frequently to find the optimal beam, which causes problems such as RS overhead and power consumption for transmitting the corresponding RSs on the base station side, implementation burden due to terminal measurement / reporting, and increased power consumption.

[0228] N set to RRC as described above max Since the terminal must measure the measurement RSs of non-serving cell(s) according to the value every time, the terminal power consumption may increase depending on the number of measurement RSs. And / or, depending on the configuration of the base station, the terminal may also measure RSs for PCI(s) that do not have a large impact on the terminal in terms of signal strength or channel characteristics according to the distance from the cell / TRP, which may further increase the terminal power consumption. In addition, when the measurement RS configuration includes multiple RSs, the size of the information (e.g., CRI / SSBRI field) for reporting the RS(s) actually measured by the terminal increases, and since this large size of information is fixed according to the measurement RS configuration, there is also an overhead accordingly.

[0229] The Rel-17 ICBM standardization did not introduce a mechanism for activating / deactivating a subset of non-serving cell SSBs that should be measured via MAC-CE. Even if such a mechanism were introduced, additional MAC-CE signaling would still be required, resulting in signaling overhead issues.

[0230] In the Rel-19 standardization discussion, it was agreed to standardize the following to introduce a process in which beam reports are triggered based on changes in beam quality at the terminal level, rather than beam measurement / reporting by the terminal set / instructed by the base station, and beam instructions are performed accordingly:

[0231] Define UE-initiated / event-based beam management to reduce overhead and / or latency, assume unified TCI but leverage the framework of existing CSI measurement reporting settings where possible, and target FR2 and intra-cell / inter-cell STRP.

[0232] - UL signaling content for UE-initiated / event-based beam reporting for rapid beam switching

[0233] - UL signaling means / container considering the UE-initiated / event-driven characteristics of UE transmissions designed primarily for beam reporting purposes.

[0234] Currently supported NR beam / CSI measurements / reporting are performed by base station configuration / instruction. Specifically for ICBMs, the number of RSs for which a terminal must perform measurements increases with the number of non-serving cells configured, exacerbating the problem of terminal power consumption and base station power consumption due to transmitting these RSs in a pre-configured manner.

[0235] Accordingly, according to one embodiment, rather than the terminal performing (ICBM) beam measurement / reporting in a manner and target set by the network as before, if the terminal determines on its own that the quality of measurement beams corresponding to different PCI(s) is degraded or a beam change is required, the terminal can perform (ICBM) beam report, and / or the terminal can effectively determine a candidate for the measurement RS by selecting PCI(s) on its own for the (ICBM) beam report.

[0236] For example, a method for configuring events and reporting contents in which corresponding actions are performed in relation to a UE-initiated beam report, and / or a method for selecting a measurement RS of a (subsequent) terminal through a candidate indication of a measurement RS associated with (serving / non-serving) PCIs are proposed.

[0237] According to the embodiments described below, if a terminal reports information about its preferred / disliked PCI and related resource sets to the network, the network may disable the corresponding measurement RS / cell. In this case, disabling disliked RS / cells is effective in saving network energy. Furthermore, disabling some PCI / RS sets in this way reduces the number of RS candidates, thereby reducing the feedback overhead of the RS indication field (e.g., CRI / SSBRI field) included in the beam report.

[0238] Proposal 1

[0239] In one embodiment, a method is proposed whereby a UE (dynamically) indicates / reports to the network its preferred or non-preferred PCI / and / or PCI-linked measurement RS set(s) / config(s) via UE-initiated ICBM beam report.

[0240] (1) Option 1: A method based on up to K beam information (quality values) included in the ICBM beam report and RS IDs linked to PCI.

[0241] Figure 8 illustrates an example of terminal operation based on option 1.

[0242] 1) First, the terminal can configure a subset of PCI with PCI(s) corresponding to the report quantity (805). The terminal can perform subsequent RS measurements by selecting only the RS(s) corresponding to the PCI(s) included in the PCI subset from among the total preset measurement RSs or by including the RS(s) (810). For example, the PCI subset configuration can be determined through single or multiple reporting instances(s).

[0243] 2) If the RS(s) that are the target of subsequent RS measurement according to the above process 1) meet a 'specific condition', the terminal can perform an ICBM beam report in a terminal-led (initiated) manner (815). In this ICBM beam report process, the PCI subset can be changed / updated. For example, the measurement RSs that are the target of the beam report quantity configuration can be all preset measurement RSs, or RS(s) corresponding to PCI(s) that are not currently included in the PCI subset.

[0244] (2) Option 2: For example, a method in which a terminal selects and / or reports / instructs PCI(s) and configures beam(s) corresponding to the PCI(s) with a report quantity.

[0245] Figure 9 illustrates an example of terminal operation based on option 2.

[0246] The terminal may, based on the total set of measurement RSs, independently select (optimal) M PCI(s) (905). And / or, a resource set or resource config corresponding to the selected M PCIs may be selected, and a report quantity may be configured based on RS IDs corresponding to up to N beam quality values ​​for each PCI.

[0247] Example 1) Report quantity configuration when there are a total of 4 PCIs {PCI#0, PCI#1, PCI#2, PCI#3}:

[0248] - Selected 2 PCIs {PCI#0, PCI#1}

[0249] - 4 CRIs / SSBRIs of 'PCI#0' and corresponding beam quality values ​​(L1-RSRP / L1-SINR)

[0250] - 4 CRIs / SSBRIs of 'PCI#1' and corresponding beam quality values ​​(L1-RSRP / L1-SINR)

[0251] Example 2) When there are a total of 4 resource sets or resource configs, report quantity configuration of {RS_set#0, RS_set#1 RS_set#2, RS_set#3}:

[0252] - 2 resource sets (or config) {RS_set#0, RS_set#1} corresponding to the selected PCIs

[0253] - 4 CRIs / SSBRIs of 'RS_set#0' and corresponding beam quality values ​​(L1-RSRP / L1-SINR)

[0254] - 4 CRIs / SSBRIs of 'RS_set#1' and corresponding beam quality values ​​(L1-RSRP / L1-SINR)

[0255] At this time, the measurement RS and / or resource set(s) / config(s) corresponding to the PCI(s) included in the report can be utilized for subsequent RS measurements.

[0256] The terminal may perform a terminal-driven ICBM beam report as described above (910) when the measurement RS and / or RS(s) of the resource set(s) corresponding to the selected M PCI(s) meet a 'specific condition'.

[0257] For example, the M and N values ​​may be set by the base station. Alternatively, the maximum values ​​for M and N may be set or determined by UE capability, and then the M and N values ​​actually applied to each report instance may be selected and reported by the UE. In this case, the applied M and N values ​​may be included as report content.

[0258] One or more of the following examples may be considered as 'specific conditions' for ICBM beam reports:

[0259] Example 1) If the quality value for the best beam of the serving cell PCI and / or the size (and / or average value) of the quality values ​​of up to K beams is below a certain threshold.

[0260] Example 2) If the quality value of the best beam of the non-serving cell PCI and / or the size (and / or average value) of the quality values ​​of up to K beams is greater than or equal to a specific beam of the serving cell PCI (serving beam or best beam, and / or average value of the quality values ​​of up to N beams corresponding to the PCI).

[0261] Example 3) If the maximum K quality values ​​corresponding to the latest ICBM beam report are below a certain threshold.

[0262] At this time, the threshold may be applied equally to up to K beams, or may be applied differently depending on the K-th beam quality value starting from the best beam quality value. The threshold may be set by the base station, and if the terminal changes / indicates the threshold value, the information may be included as report content.

[0263] At this time, the terminal's preferred / non-preferred PCI / RS set information may be encoded and reported together with the CSI / beam report or may be reported through a separate report.

[0264] The above proposal 1 is a method to solve the problem that occurs due to performing RS measurement based on the resource configuration set in advance for performing ICBM beam report. The terminal can configure a subset for PCI with the beam report and reduce the candidates for subsequent RS measurement based on this. In addition, if the beam quality value corresponding to the PCI subset is under a specific condition, the terminal determines that the PCI subset needs to be changed, performs a UE-initiated ICBM beam report, and changes / updates the PCI subset accordingly so that the base station can turn off the preferred / non-preferred PCI and related RS sets, or reduce the size of the indication field for indicating the RS when reporting the beam with the reduced measurement RS candidates.

[0265] Option 1 is a method based on up to K beam quality values ​​included in the existing ICBM beam report and RS IDs associated with each PCI.

[0266] Option 2 is a method for supporting best N beam reports for each TRP(s) with different PCI(s). In this case, a separate report configuration for each TRP and resource configuration for RSs with different PCIs are required. From this perspective, the terminal can perform N beam reports for the best M TRPs / PCIs in a UE-initiated beam report. For example, the terminal can select M TRPs / PCIs and perform reporting, and accordingly, the RS set or resource configuration to be reported can be selected and reported. In addition, detailed embodiments for the following scenarios can be considered when the ICBM beam report is triggered for a 'specific condition'.

[0267] 1) Inter-cell M-DCI based MTRP

[0268] If there is a (best / average) beam quality value associated with one or more PCI(s) that is better than the (best / average) beam quality value associated with the PCI(s) corresponding to a specific CORESET pool index among the multiple CORESET pools set for the purpose of TRP distinction, the terminal can trigger an ICBM beam report.

[0269] 2) Rel-18 L1 / L2 triggered mobility (ie LTM)

[0270] Instead of performing handover (HO) based on L3 measurements as before, the terminal performs L1 measurements on the serving cell / non-serving cell(s) and reports them, and then performs HO through a cell switch command (CSC) via MAC-CE based on these measurements.

[0271] A terminal can trigger an ICBM beam report if there is a (best / average) beam quality value associated with one or more PCI(s) that is better than the (best / average) beam quality value associated with the current serving cell.

[0272] In this case, in UE-based TA measurement, the terminal can measure the TA(s) related to the reported candidate cell PCI(s).

[0273] In Rel-18 LTM, UE-based TA measurements are performed on a specific candidate cell and / or associated DL RS among the established candidate cells, depending on the UE implementation. Therefore, after the base station indicates a CSC, the TA corresponding to the cell may be inaccurate, requiring RACH triggering to be performed in conjunction with the CSC.

[0274] When the terminal measures TA(s) related to the candidate cell PCI(s) reported in this manner, the terminal is measuring TA(s) for the PCI(s) included in the ICBM beam report, so the RACH triggering following the CSC can be omitted, which has an advantage in terms of reducing signaling / delay overhead.

[0275] As part of the confidence information for the TA measurement of the corresponding terminal, a 1-bit indicator may be included in the ICBM beam report contents, which may be used as information to determine whether the TA measurement was performed (i.e., if the indicator value is 1) and / or whether the base station will perform RACH triggering for the corresponding terminal.

[0276] This could be part 1 CSI information in two-part encoding, or a PCI-specific indicator could also be included in part 2 CSI to indicate whether a PCI-specific TA measurement is being performed.

[0277] Since there may be terminals that support the above different operation scenarios simultaneously, events corresponding to different scenarios may coexist.

[0278] As in the operation of the above proposal 1, the terminal performs RS measurement and report using some PCI subset / RS set(s), and based on this, the base station can transmit or not transmit RSs corresponding / not corresponding to the above information. Alternatively, contrary to the configuration / instruction of the PCI subset / RS set(s) by the terminal, the base station can instruct the PCI subset / RS set(s) through signaling (MAC-CE and / or DCI) to transmit or not transmit RSs at the base station's initiative. From the perspective of NW energy saving, this can save power for RS transmission according to the needs of specific base stations(es).

[0279] In this case, since the terminal and base station can know RSs corresponding / not corresponding to specific PCI(s) / RS set(s) based on the preset RS configuration and report configuration through the PCI subset / RS set(s) indicated by the signaling, the terminal can use the codepoint corresponding to the RS subset(s) reduced by the above operation instead of the CRI / SSBRI targeting the entire RSs for the purpose of indicating the RS ID in subsequent RS measurement / reporting.

[0280] For example, if the number of measurement RSs configured by RRC is 4 (i.e. CRI bits = 2 and the corresponding RS IDs = RS#0, RS#1, RS#2, RS#3), and the base station signaling indicates that there is no need to perform measurement reports corresponding to RS#1 and RS#2, the number of RSs actually used for measurement is 2 (i.e. RS#0, RS#3), and the CRI bit to indicate this can be applied as 1 instead of the existing 2, and changed when configuring the beam report content. In this case, if CRI=0, it can be configured to correspond to RS#0, if CRI=1, it can correspond to RS#3, and so on. Alternatively, in the above example, a subset for operation may be set in advance (e.g., set#0={RS#0, RS#1, RS#2, RS#3} / set#1={RS#0, RS#3} / set#2={RS#0, RS#1, RS#2}) and the candidate set of the measurement RS may be signaled by indicating the corresponding set index with MAC-CE and / or DCI.

[0281] Proposal 1-1

[0282] A method for configuring beam report size and / or report quantity according to the number of given beams for configuring PCI subset of Proposal 1 is proposed.

[0283] Option 1) K max Set the value to a value greater than the original 4 (e.g. 6 or 8)

[0284] It works in the same way as the current ICBM beam report, but can be used to configure the PCI subset by increasing the size of the corresponding Kmax value.

[0285] Option 2) Given K max The beam quality values ​​for the quantity to be reported are as follows:

[0286] [Number of PCIs N1] X [Number of beams to report per PCI N2] = K max

[0287] Example) K max If =4, {N1, N2} can be composed of {1,4}, {2,2}, {4,1}.

[0288] For example, since the current behavior depends on the size of the L1-RSRP of the measured RS, only information corresponding to a specific PCI can be included in a single report instance, so by comparing the best beam quality size per PCI, {L1-RSRP and RS ID} pairs corresponding to a total of four PCIs can be reported.

[0289] The above method may be indicated by the base station through RRC settings or MAC-CE. Alternatively, the terminal may select and configure the report quantity and include the corresponding information in the report content.

[0290] Proposal 1-2

[0291] A solution is proposed to address the issue of fluctuations occurring for PCI subsets per report instance in Proposal 1.

[0292] Option 1) Set an offset for the quality value of the measured RS corresponding to each PCI subset.

[0293] At this time, you can set the same / different offset for each beam and / or PCI.

[0294] Option 2) When configuring a PCI subset with quality values ​​for a preset measurement RS, do not judge it as a single instance, but configure a PCI subset based on multiple instances (e.g., 5 times) and apply it to subsequent RS measurements.

[0295] Regarding the method of configuring PCI subsets in the operation of Proposal 1 above, if the PCI included in each beam reporting instance differs, UE-initiated ICBM beam reports may occur frequently. Therefore, to reduce fluctuations in PCI subsets while also reducing signaling overhead associated with UE-initiated beam reports, PCIs can be selected based on quality values ​​for multiple instances.

[0296] Example) Assume that the PCI subsets according to the three instances are 1st instance = {PCI#0, PCI#1}, 2nd instance = {PCI#1, PCI#2, PCI#3}, 3rd instance = {PCI#1, PCI#3, PCI#4}.

[0297] For example, in instance 3, the most numerous PCIs, PCI#1 and PCI#3, can be set as a PCI subset, or it can include PCI(s) that appear more than a specific n times.

[0298] As another example, a PCI subset could be configured targeting all PCIs contained in instances 3.

[0299] The number of instances to be considered [X] and / or the value of n for PCI selection can be set by RRC.

[0300] In addition to the above proposals 1, 1-1, and 1-2, as an additional consideration, in case the terminal selects and reports the optimal M TRP / PCI as in option 2 of the above proposal 1, the reporting payload may vary depending on the number of PCIs selected by the terminal or the number of beams reported for each PCI. One way to address this is to prevent the payload size from changing based on [the number of PCIs to report, A] and [the number of beams reported for each PCI, B] as in proposal 1-2 (e.g., AXB = K max or a specific constant), but in this case, as the number of PCIs increases, the number of beams reported per PCI decreases, so a trade-off may occur in terms of PCI subset configuration or the reliability of beam quality of the corresponding specific PCI.

[0301] Therefore, a method may be needed to enable the terminal to variably set / indicate the above M and N and the base station to decode by reflecting the accompanying increase in payload.

[0302] Proposal 2

[0303] A method for configuring ICBM beam report quantity considering the selection of maximum M PCIs and the number of beams per PCI is proposed.

[0304] Option 1) Two-part encoding method to make beam report payload size variable

[0305] 1) Part 1 Report Content may include one or more of the following information:

[0306] - Number of PCIs reflected in the report m (<=M)

[0307] - Number of beams (per PCI or common to PCI)

[0308] - TA measurement related indicators (applicable to PCI or common to PCI)

[0309] 2) Part 2 report content follows the information in Part 1.

[0310] Option 2) Reporting of fixed payload size based on reduced payload size compared to existing ICBMs.

[0311] A method is proposed to fix the number of PCIs to M, order the PCIs by ‘specific criteria’, and differentiate the number of beam reports corresponding to each PCI.

[0312] Example) For M=4, assume that PCIs are sorted in the order of PCI 1 / 2 / 3 / 4 according to a specific criterion, and N=4. In this case, the following can be considered as a report quantity configuration method.

[0313] - PCI1 and corresponding N {beam quality value, RS ID} pairs

[0314] - PCI2 and corresponding N-1 {beam quality value, RS ID} pairs

[0315] - PCI3 and corresponding N-2 {beam quality value, RS ID} pairs

[0316] - PCI4 and corresponding N-3 {beam quality value, RS ID} pairs

[0317] Here, the 'specific criteria' may be the best and / or average beam quality values ​​of each PCI, or the number of times the PCI is included in multiple instances in the multiple instance-based PCI selection of the above proposal 1-2.

[0318] Option 1 of the above proposal 2 can be configured as a two-part encoding method to provide freedom in PCI selection and the number of beams per PCI. Since the base station can determine the payload size for the subsequent part 2 by checking the fixed payload information of part 1, the ambiguity issue during decoding at the base station can be resolved.

[0319] At this time, the number of PCIs applied to the report is important as part 1 information. This is because the number of RSRP information corresponding to a beam quality value can increase as a product of the number of PCIs. Furthermore, whether the same number of beams will be reported for all PCIs or whether the number of beams to be reported will vary by PCI can also be reflected as part 1 information.

[0320] Also, in relation to the TA measurement of the proposal 1 above, a 1-bit indicator indicating that all TAs for cells corresponding to the PCI subset have been measured may be used, but it may also provide information on the presence / absence of TA measurement for specific PCI(s) (e.g. {1,1,1,0} for 4 PCIs) and, subsequently, based on the indicator value at the time of CSC, for the 4th PCI, the presence / absence of TA measurement may be '0', so RACH triggering may be triggered, but for other PCIs, triggering may not be performed.

[0321] Option 2, unlike Option 1, does not have a variable payload, but it can apply a differential beam report count method, such as reporting multiple beams for PCIs with high frequency or good beam quality by giving priority to PCIs that are included in multiple instances or information about beam quality values ​​for each PCI, and conversely, reducing the number of beam reports according to sort order for PCI(s) with low frequency or relatively poor beam quality.

[0322] FIG. 10 illustrates a flow of a method performed by a terminal according to one embodiment.

[0323] Referring to FIG. 10, a terminal can receive configuration information including multiple physical cell IDs (PCIs) related to ICBM (inter-cell beam management) (1010).

[0324] The terminal can perform a first measurement based on a plurality of signals related to the plurality of PCIs (1015).

[0325] The terminal may transmit a first report related to the terminal's preference / dispreference for each of the plurality of PCIs based on the first measurement (1020).

[0326] The terminal can perform a second measurement based on signals for preferred PCIs, excluding non-preferred PCIs among the plurality of PCIs (1025).

[0327] The terminal may transmit a second report for the second measurement based on the second measurement satisfying a terminal-initiated beam reporting condition (1030).

[0328] The above second report may be a terminal-initiated beam report for inter-cell beam management.

[0329] A PCI subset may be configured based on the preferred PCIs of the terminal. The PCI subset may be updated based on the second measurement reported through the second report.

[0330] The second report may include measurement values ​​of up to N beams for each of the preferred PCIs.

[0331] The number of beams for each preferred PCI may be determined differently depending on the preference of each of the above preferred PCIs.

[0332] The number of preferred PCIs, M and N, can be determined based on upper layer signaling.

[0333] The number of preferred PCIs, M and N, can be determined by the terminal. The second report can include at least one of information about M and N.

[0334] The second report may include information on whether a timing advance (TA) measurement was performed for each of the preferred PCIs.

[0335] The terminal-initiated beam reporting condition may include at least one of: a case where there is a PCI having a higher beam quality than a beam quality for a PCI associated with a specific CORESET (control resource set) pool index; and a case where there is a PCI having a higher beam quality than a beam quality of a serving cell.

[0336] FIG. 11 illustrates a flowchart of a method performed by at least one network node according to one embodiment. In FIG. 11, at least one network node may be at least one base station / TRP.

[0337] Referring to FIG. 11, at least one network node can transmit configuration information including multiple physical cell IDs (PCIs) related to inter-cell beam management (ICBM) to a terminal (1105).

[0338] At least one network node can transmit a plurality of signals related to said plurality of PCIs (1110).

[0339] At least one network node may receive a first measurement report related to the preference / dispreference of the terminal for each of the plurality of PCIs (1115).

[0340] At least one network node can transmit signals for preferred PCIs to the terminal, excluding non-preferred PCIs among the plurality of PCIs (1120).

[0341] At least one network node may receive a second measurement report for signals for the preferred PCIs based on a terminal-initiated beam reporting condition being satisfied at the terminal (1125).

[0342] The above second measurement report may be a terminal-initiated beam report for inter-cell beam management.

[0343] A PCI subset may be configured based on the preferred PCIs of the terminal. The PCI subset may be updated through the second measurement report.

[0344] The second measurement report may include measurement values ​​of up to N beams for each of the preferred PCIs.

[0345] The number of beams for each preferred PCI may be determined differently depending on the preference of each of the above preferred PCIs.

[0346] The number of preferred PCIs, M and N, can be determined based on upper layer signaling.

[0347] The number of preferred PCIs, M and N, can be determined by the terminal. The second measurement report can include at least one of information about M and N.

[0348] The second measurement report may include information on whether a timing advance (TA) measurement was performed for each of the preferred PCIs.

[0349] The terminal-initiated beam reporting condition may include at least one of: a case where there is a PCI having a higher beam quality than a beam quality for a PCI associated with a specific CORESET (control resource set) pool index; and a case where there is a PCI having a higher beam quality than a beam quality of a serving cell.

[0350] Fig. 12 illustrates a communication system (1) applicable to the present disclosure.

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

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

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

[0354] Figure 13 illustrates a wireless device applicable to the present disclosure.

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

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

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

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

[0359] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

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

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

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

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

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

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

[0366] Figure 15 illustrates a vehicle or autonomous vehicle applicable to the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like.

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

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

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

[0370] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

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

[0372] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed by a terminal, Receive configuration information including multiple PCIs (physical cell IDs) related to ICBM (inter-cell beam management); Performing a first measurement based on a plurality of signals related to the plurality of PCIs; Transmitting a first report related to the preference / dispreference of the terminal for each of the plurality of PCIs based on the first measurement; Performing a second measurement based on signals for preferred PCIs, excluding non-preferred PCIs among the plurality of PCIs; and A method comprising transmitting a second report for the second measurement based on the second measurement satisfying a terminal-initiated beam reporting condition.

2. In paragraph 1, The above second report is a method for terminal-initiated beam reporting for inter-cell beam management.

3. In paragraph 1, A PCI subset is formed based on the preferred PCIs of the above terminals, A method wherein the PCI subset is updated based on the second measurement reported through the second report.

4. In paragraph 1, A method wherein the second report comprises measurement values of at most N beams for each of the preferred PCIs.

5. In paragraph 4, A method in which the number of beams for each preferred PCI is determined differently according to the preference of each of the above preferred PCIs.

6. In paragraph 4, A method wherein the number of preferred PCIs, M and N, are determined based on upper layer signaling.

7. In paragraph 4, The number of the above preferred PCIs, M and N, are determined by the terminal, A method wherein the second report includes at least one of information about the M and the N.

8. In paragraph 1, A method wherein the second report includes information on whether a TA (timing advance) measurement was performed for each of the preferred PCIs.

9. In paragraph 1, The above terminal-initiated beam reporting conditions are: If there is a PCI with a higher beam quality than the beam quality for the PCI associated with a particular CORESET (control resource set) pool index; and A method comprising at least one of the following: a PCI having a beam quality higher than a beam quality of a serving cell.

10. A non-transitory computer-readable recording medium having recorded thereon a program for performing the method described in paragraph 1.

11. In the device, memory for storing commands; and A processor for performing operations by executing the above instructions, The operations of the above processor are: Receive configuration information including multiple PCIs (physical cell IDs) related to ICBM (inter-cell beam management); Performing a first measurement based on a plurality of signals related to the plurality of PCIs; Transmitting a first report relating to a preference / dispreference of the device for each of the plurality of PCIs based on the first measurement; Performing a second measurement based on signals for preferred PCIs, excluding non-preferred PCIs among the plurality of PCIs; and A device comprising transmitting a second report for the second measurement based on the second measurement satisfying a device-initiated beam reporting condition.

12. In paragraph 11, Further comprising a transceiver for transmitting or receiving a wireless signal under the control of the processor, The above device is a terminal in a wireless communication system.

13. In paragraph 11, The above device is a processing device configured to control a terminal in a wireless communication system.

14. A method performed by at least one network node, Transmitting configuration information including multiple PCIs (physical cell IDs) related to ICBM (inter-cell beam management) to the terminal; Transmitting a plurality of signals related to the plurality of PCIs; Receive a first measurement report related to the preference / dispreference of the terminal for each of the plurality of PCIs; Transmitting signals for preferred PCIs to the terminal, excluding non-preferred PCIs among the plurality of PCIs; and A method comprising receiving a second measurement report for signals for the preferred PCIs based on satisfaction of a terminal-initiated beam reporting condition at the terminal.

15. In at least one network node, At least one memory for storing instructions; and At least one processor for performing operations by executing the above instructions, The operations of at least one processor, Transmitting configuration information including multiple PCIs (physical cell IDs) related to ICBM (inter-cell beam management) to the terminal; Transmitting a plurality of signals related to the plurality of PCIs; Receive a first measurement report related to the preference / dispreference of the terminal for each of the plurality of PCIs; Transmitting signals for preferred PCIs to the terminal, excluding non-preferred PCIs among the plurality of PCIs; and At least one network node comprising receiving a second measurement report for signals for said preferred PCIs based on satisfaction of a terminal-initiated beam reporting condition at said terminal.

Images