Method and device for performing UE-initiated beam reporting using pucch

Abstract

A method and a device for performing UE-initiated beam reporting using a physical uplink control channel (PUCCH) are provided. A UE receives UE-initiated beam reporting (UEIBR) configuration information and transmits first uplink control information related to UEIBR through a PUCCH resource on the basis of the received UEIBR configuration information. The UE starts a timer on the basis of the transmission of the first uplink control information and transmits a report corresponding to the first uplink control information while the timer is running. In addition, the UE restarts the timer on the basis of the transmission of the report.

Description

Method and apparatus for performing terminal initiation beam reporting using PUCCH

[0001] This specification relates to wireless communication applicable to 5G NR, 5G-Advanced, and 6G.

[0002] As the times change and more communication devices demand larger communication traffic, there is a demand for next-generation 5G systems, which are wireless broadband communication systems that are improved over existing LTE systems. In these next-generation 5G systems, referred to as NewRAT, communication scenarios are classified into Enhanced Mobile BroadBand (eMBB), Ultra-reliability and low-latency communication (URLLC), and Massive Machine-Type Communications (mMTC).

[0003] Here, eMBB is a next-generation mobile communication scenario characterized by High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate; URLLC is a next-generation mobile communication scenario characterized by Ultra Reliable, Ultra Low Latency, and Ultra High Availability (e.g., V2X, Emergency Service, Remote Control); and mMTC is a next-generation mobile communication scenario characterized by Low Cost, Low Energy, Short Packet, and Massive Connectivity (e.g., IoT).

[0004] One disclosure of this specification is to provide a method and apparatus for efficiently performing terminal initiation beam reporting using a PUCCH in a wireless communication system.

[0005] In one embodiment of the present specification, in a wireless communication system, a terminal receives UE-Initiated Beam Reporting (UEIBR) configuration information and, based on the received UEIBR configuration information, transmits first uplink control information related to the UEIBR through a Physical Uplink Control Channel (PUCCH) resource. Then, based on the transmission of the first uplink control information, the terminal starts a timer and, while the timer is operating, transmits a report corresponding to the first uplink control information. Additionally, the terminal provides a method for restarting the timer based on the transmission of the report.

[0006] Furthermore, one embodiment of the present invention provides a wireless communication system comprising at least one processor and at least one memory that stores instructions and is operablely electrically connected to at least one processor, wherein the operation performed based on the instruction being executed by at least one processor is: receiving UE-Initiated Beam Reporting (UEIBR) configuration information and, based on the received UEIBR configuration information, transmitting first uplink control information related to the UEIBR through a Physical Uplink Control Channel (PUCCH) resource. Then, based on the transmission of the first uplink control information, a timer is started and, while the timer is operating, a report corresponding to the first uplink control information is transmitted. Additionally, a terminal is provided that restarts the timer based on the transmission of the report.

[0007] The above UEIBR configuration information may include information regarding the PUCCH resource and information regarding the timer. Additionally, the above UEIBR configuration information may further include at least one of UEIBR event information, UEIBR event trigger information, and information on the maximum number of transmissions of uplink control information related to the UEIBR.

[0008] When the transmission of the second uplink control information related to the UEIBR is triggered, the transmission of the second uplink control information may be suspended while the timer is operating.

[0009] Meanwhile, when the transmission of the first uplink control information and the second uplink control information reaches the maximum number of transmissions indicated by the maximum number of transmissions information, at least one of triggering a beam failure report, initiating a random access procedure, and canceling all pending UEIBR transmissions may be performed.

[0010] The terminal may receive beam indication information, RS (Reference Signal) reconfiguration information, or RS update information in response to the transmission of the above report.

[0011] If none of the beam indication information, RS (Reference Signal) reconfiguration information, or RS update information is received in response to the transmission of the above report, the above withheld second uplink control information may be transmitted.

[0012] According to the disclosure of this specification, a timer driving condition is provided to prohibit a UEIBR PUCCH transmission that may be additionally triggered after a UEIBR PUCCH transmission, so that a terminal performing UEIBR (UE initiated Beam Reporting) can transmit or retransmit a UCI for requesting UEIBR more timely.

[0013] In addition, even after Channel State Information (CSI) reports are transmitted via PUSCH by the UEIBR, unnecessary repeated transmissions of UEIBR PUCCH may occur until explicit responses, such as Beam Indication information, Transmission Configuration Indicator (TCI) status update information, or RS reconfiguration / update information, are received from the base station; however, the present invention can effectively prevent such unnecessary UEIBR PUCCH transmissions by using the timer.

[0014] Therefore, unnecessary PUCCH transmissions can be reduced to lower uplink control signal overhead, enabling efficient use of uplink resources.

[0015] Additionally, if an expected explicit response from the base station (e.g., Beam Indication / TCI state update / RS reconfiguration or update) is not received within a certain period of time, allowing UEIBR PUCCH retransmission enables the terminal to retry beam switching without delay, thereby ensuring that beam switching is performed in a timely manner and improving link performance and quality of service.

[0016] Figure 1 is a diagram illustrating a wireless communication system.

[0017] Figure 2 illustrates the structure of a wireless frame used in NR.

[0018] FIGS. 3a to 3c are exemplary diagrams illustrating exemplary architectures for wireless communication services.

[0019] Figure 4 illustrates the slot structure of an NR frame.

[0020] Figure 5 illustrates an example of a subframe type in NR.

[0021] Figure 6 illustrates the structure of a self-contained slot.

[0022] Figures 7a through 7c show examples of beam reporting procedures in NR.

[0023] FIG. 8 is a flowchart illustrating a method of operation of a terminal according to one embodiment of the present specification.

[0024] FIGS. 9 to 12 are drawings illustrating procedures of a base station and a terminal according to an embodiment of the present specification.

[0025] FIG. 13 shows an apparatus according to one embodiment of the present specification.

[0026] FIG. 14 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0027] FIG. 15 shows a block diagram of a processor in which the disclosure of the present specification is implemented.

[0028] FIG. 16 is a block diagram showing in detail the transceiver of the first device shown in FIG. 13 or the transceiver of the device shown in FIG. 14.

[0029] It should be noted that technical terms used in this specification are used merely to describe specific embodiments and are not intended to limit the content of this specification. Furthermore, unless specifically defined otherwise in this specification, technical terms used in this specification should be interpreted in the sense generally understood by those skilled in the art to which this disclosure pertains, and should not be interpreted in an overly broad or overly narrow sense. Additionally, if a technical term used in this specification is an incorrect technical term that fails to accurately express the content and concept of this specification, it should be understood as being replaced by a technical term that can be correctly understood by those skilled in the art. Moreover, general terms used in this specification should be interpreted according to their prior definitions or the context, and should not be interpreted in an overly narrow sense.

[0030] Additionally, singular expressions used in this specification include plural expressions unless the context clearly indicates otherwise. In this application, terms such as "composed of" or "have" should not be interpreted as necessarily including all of the various components or steps described in the specification, and should be interpreted as meaning that some of the components or steps may be omitted or additional components or steps may be included.

[0031] Additionally, terms including ordinal numbers, such as first, second, etc., used herein may be used to describe various components, but said components shall not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the rights, the first component may be named the second component, and similarly, the second component may be named the first component.

[0032] When it is stated that a component is connected to or coupled with another component, it may be directly connected to or coupled with that other component, or there may be other components in between. On the other hand, when it is stated that a component is directly connected to or directly coupled with another component, it should be understood that there are no other components in between.

[0033] Hereinafter, embodiments will be described in detail with reference to the attached drawings. Identical or similar components regardless of drawing symbols are assigned the same reference number, and redundant descriptions thereof will be omitted. Furthermore, in describing the contents of this specification, if it is determined that a detailed description of related prior art may obscure the gist of this specification, such detailed description will be omitted. Additionally, it should be noted that the attached drawings are intended only to facilitate understanding of the contents and concepts of this specification, and should not be interpreted as limiting the contents and concepts of this specification. The contents and concepts of this specification should be interpreted as extending to all modifications, equivalents, and substitutions in addition to the attached drawings.

[0034] In this specification, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, in this specification, “A or B” may be interpreted as “A and / or B.” For example, in this specification, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0035] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “A and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B or C.”

[0036] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as synonymous with “at least one of A and B.”

[0037] Additionally, in this specification, “at least one of A, B and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” may mean “at least one of A, B and C.”

[0038] Additionally, parentheses used in this specification may mean “for example.” Specifically, where indicated as “Control Information (PDCCH),” “PDCCH (Physical Downlink Control Channel)” may be proposed as an example of “Control Information.” In other words, “Control Information” in this specification is not limited to “PDCCH,” and “PDDCH” may be proposed as an example of “Control Information.” Furthermore, even when indicated as “Control Information (i.e., PDCCH),” “PDCCH” may be proposed as an example of “Control Information.”

[0039] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0040] In the attached drawings, User Equipment (UE) is illustrated as an example, but the illustrated UE may also be referred to by terms such as Terminal or Mobile Equipment (ME). Furthermore, the UE may be a portable device such as a laptop, mobile phone, PDA, smartphone, multimedia device, etc., or a non-portable device such as a PC or vehicle-mounted device.

[0041] In the following, UE is used as an example of a wireless communication-capable device (e.g., wireless communication device, wireless device, or wireless apparatus). The operations performed by the UE may be performed by any wireless communication-capable device. A wireless communication-capable device may also be referred to as a wireless communication device, wireless device, or wireless apparatus.

[0042] The term "base station" as used below generally refers to a fixed station that communicates with wireless devices, and can be used as a comprehensive term including eNodeB (evolved-NodeB), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point, gNB (Next generation NodeB), RRH (remote radio head), TP (transmission point), RP (reception point), relay, etc.

[0043] This specification describes embodiments using LTE systems, LTE-A systems and NR systems, but these embodiments may be applied to any communication system corresponding to the above definitions.

[0044] Wireless Communication System

[0045] Building on the success of LTE (long term evolution) / LTE-Advanced (LTE-A) for 4th generation mobile communication, commercialization and subsequent research for the next generation, namely 5th generation (so-called 5G) mobile communication, are also continuing.

[0046] Fifth-generation mobile communication, as defined by the International Telecommunication Union (ITU), refers to providing data transmission speeds of up to 20 Gbps and a perceived transmission speed of at least 100 Mbps anywhere. Its official name is 'IMT-2020'.

[0047] The ITU presents three major usage scenarios, such as eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications).

[0048] URLLC concerns use scenarios requiring high reliability and low latency. For example, services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (e.g., latency of 1ms or less). Currently, the latency of 4G (LTE) is statistically 21-43ms (best 10%) and 33-75ms (median). This is insufficient to support services requiring latency of 1ms or less. Next, eMBB use scenarios concern use scenarios requiring mobile ultra-broadband.

[0049] In other words, 5th generation mobile communication systems support higher capacity than current 4G LTE, increase the density of mobile broadband users, and can support D2D (Device to Device), high stability, and MTC (Machine type communication). 5G research and development also aims for lower latency and lower battery consumption than 4G mobile communication systems to better implement the Internet of Things. New radio access technology (New RAT or NR) may be proposed for such 5G mobile communication.

[0050] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change; for example, the two types of frequency ranges (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean the “sub 6GHz range” and FR2 may mean the “above 6GHz range” and may be referred to as millimeter wave (mmW).

[0051] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0052] The numerical values ​​of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 1. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0053] Meanwhile, 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from upper layers. For example, physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), physical multicast channel (PMCH), physical control format indicator channel (PCFICH), physical downlink control channel (PDCCH), and physical hybrid ARQ indicator channel (PHICH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal of a specific waveform that is known to both the gNB and the UE. For example, cell-specific RS, UE-specific RS (UE-RS), positioning RS (PRS), and channel state information RS (CSI-RS) are defined as downlink reference signals. The 3GPP LTE / LTE-A standard defines uplink physical channels corresponding to resource elements that carry information originating from upper layers, and uplink physical signals corresponding to resource elements used by the physical layer but that do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and physical random access channel (PRACH) are defined as uplink physical channels, and the demodulation reference signal (DMRS) for uplink control / data signals and the sounding reference signal (SRS) used for uplink channel measurement are defined.

[0054] In this specification, PDCCH (Physical Downlink Control Channel) / PCFICH (Physical Control Format Indicator Channel) / PHICH (Physical Hybrid automatic retransmit request Indicator Channel) / PDSCH (Physical Downlink Shared Channel) each refers to a set of time-frequency resources or a set of resource elements carrying DCI (Downlink Control Information) / CFI (Control Format Indicator) / downlink ACK / NACK (ACKnowlegement / Negative ACK) / downlink data. Additionally, PUCCH (Physical Uplink Control Channel) / PUSCH (Physical Uplink Shared Channel) / PRACH (Physical Random Access Channel) each refers to a set of time-frequency resources or a set of resource elements carrying UCI (Uplink Control Information) / uplink data / random access signals.

[0055] Figure 1 is a diagram illustrating a wireless communication system.

[0056] As can be seen with reference to FIG. 1, the wireless communication system includes at least one base station (BS). The BS is divided into a gNodeB (or gNB) (20a) and an eNodeB (or eNB) (20b). The gNB (20a) supports 5th generation mobile communication. The eNB (20b) supports 4th generation mobile communication, i.e., LTE (Long Term Evolution).

[0057] Each base station (20a and 20b) provides communication services for a specific geographical area (generally called a cell) (20-1, 20-2, 20-3). A cell can be further divided into multiple areas (called sectors).

[0058] User Equipment (UE) typically belongs to a single cell, and the cell to which the UE belongs is called the serving cell. The base station that provides communication services to the serving cell is called the serving base station (serving BS). Since the wireless communication system is a cellular system, there exists another cell adjacent to the serving cell. The other cell adjacent to the serving cell is called the neighbor cell. The base station that provides communication services to the neighbor cell is called the neighbor base station (neighbor BS). The serving cell and neighbor cells are determined relatively to the UE.

[0059] In the following, the downlink refers to communication from the base station (20) to the UE (10), and the uplink refers to communication from the UE (10) to the base station (20). In the downlink, the transmitter may be part of the base station (20) and the receiver may be part of the UE (10). In the uplink, the transmitter may be part of the UE (10) and the receiver may be part of the base station (20).

[0060] Meanwhile, wireless communication systems can be broadly classified into Frequency Division Duplex (FDD) and Time Division Duplex (TDD) methods. In the FDD method, uplink and downlink transmissions occupy different frequency bands. In the TDD method, uplink and downlink transmissions occupy the same frequency band and occur at different times. The channel response in the TDD method is practically reciprocal. This means that the downlink channel response and the uplink channel response are nearly identical within a given frequency range. Therefore, in a wireless communication system based on TDD, there is an advantage in that the downlink channel response can be derived from the uplink channel response. In the TDD method, since the entire frequency band is time-divided for uplink and downlink transmissions, downlink transmission by the base station and uplink transmission by the UE cannot be performed simultaneously. In a TDD system where uplink and downlink transmissions are separated by subframes, uplink and downlink transmissions are performed in different subframes.

[0061] Figure 2 illustrates the structure of a wireless frame used in NR.

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

[0063] Support for various numerologies

[0064] In NR systems, as wireless communication technology develops, multiple numerologies may be provided to the terminal. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0065] The above numerology can be defined by the cycle prefix (CP) length and the subcarrier spacing (SCS). A single cell can provide multiple numerologies to the terminal. When the index of the numerology is denoted by μ, each subcarrier spacing and the corresponding CP length may be as shown in the table below.

[0066] μ△f=2 μ 15 [kHz]CP015General 130General 260General, Extended 3120General 4240General 5480General 6960General

[0067] For a standard CP, when the numerology index is denoted by μ, the number of OFDM symbols per slot (N slot symb ), number of slots per frame (N frame,μ slot ) And, the number of slots per subframe (N subframe,μ slot ) is as shown in the table below.

[0068] μ△f=2 μ 15 [kHz]N slot symb N frame,μ slot N subframe,μ slot 015141011301420226014404312014808424014160165480143203269601464064

[0069] For extended CP, when the numerology index is denoted by μ, the number of OFDM symbols per slot (N slot symb ), number of slots per frame (N frame,μ slot ) And, the number of slots per subframe (N subframe,μ slot ) is as shown in the table below.

[0070] μSCS (15*2 u )N slot symb N frame,μ slot N subframe,μslot 260KHz (u=2)12404

[0071] In an NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) composed of the same number of symbols can be configured differently among the merged cells.

[0072] FIGS. 3a to 3c are exemplary diagrams illustrating exemplary architectures for wireless communication services.

[0073] Referring to Fig. 3a, the UE is connected to an LTE / LTE-A based cell and an NR based cell in a DC (dual connectivity) manner.

[0074] The above NR-based cell is connected to the core network for existing 4th generation mobile communication, namely the EPC (Evolved Packet Core).

[0075] Referring to Fig. 3b, unlike Fig. 3a, the LTE / LTE-A based cell is connected to a core network for 5th generation mobile communication, that is, a 5G core network.

[0076] A service method based on the architecture as illustrated in Figures 3a and 3b is called NSA (non-standalone).

[0077] Referring to Fig. 3c, the UE is connected only to NR-based cells. A service method based on this architecture is called SA (standalone).

[0078] Meanwhile, in the above NR, it may be considered that reception from the base station utilizes a downlink subframe, and transmission to the base station utilizes an uplink subframe. This method can be applied to paired spectra and unpaired spectra. A paired spectrum means that it includes two carrier spectra for downlink and uplink operations. For example, in a paired spectrum, one carrier may include a downlink band and an uplink band that are paired with each other.

[0079] Figure 4 illustrates the slot structure of an NR frame.

[0080] A slot contains multiple symbols in the time domain. For example, in the case of a standard CP, one slot contains 14 symbols, whereas 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, P)RBs in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A terminal may be configured with up to N (e.g., 4) BWPs in both the downlink and uplink. Downlink or uplink transmission is performed through an active BWP, and at a given time, only one of the BWPs configured for the terminal may be active. In the resource grid, each element is referred to as a Resource Element (RE), and a single complex symbol may be mapped to it.

[0081] Figure 5 illustrates an example of a subframe type in NR.

[0082] The transmission time interval (TTI) illustrated in Fig. 5 can be referred to as a subframe or slot for NR (or new RAT). The subframe (or slot) of Fig. 5 can be used in the TDD system of NR (or new RAT) to minimize data transmission delay. As illustrated in Fig. 5, the subframe (or slot) contains 14 symbols. The symbols at the beginning of the subframe (or slot) can be used for the downlink (DL) control channel, and the symbols at the end of the subframe (or slot) can be used for the uplink (UL) control channel. The remaining symbols can be used for DL ​​data transmission or UL data transmission. According to this subframe (or slot) structure, downlink transmission and uplink transmission can proceed sequentially within a single subframe (or slot). Thus, downlink data can be received within the subframe (or slot), and uplink acknowledgments (ACK / NACK) can be transmitted within that subframe (or slot).

[0083] The structure of such a subframe (or slot) can be called a self-contained subframe (or slot).

[0084] Specifically, the first N symbols within the slot are used to transmit a DL control channel (hereinafter referred to as the DL control area), and the last M symbols within the slot may be used to transmit a UL control channel (hereinafter referred to as the UL control area). N and M are each integers greater than or equal to 0. A resource area (hereinafter referred to as the data area) located between the DL control area and the UL control area may be used for DL ​​data transmission or for UL data transmission. For example, a physical downlink control channel (PDCCH) may be transmitted in the DL control area, and a physical downlink shared channel (PDSCH) may be transmitted in the DL data area. A physical uplink control channel (PUCCH) may be transmitted in the UL control area, and a physical uplink shared channel (PUSCH) may be transmitted in the UL data area.

[0085] Using such a subframe (or slot) structure has the advantage of reducing the time required to retransmit data that has received errors, thereby minimizing the waiting time for final data transmission. In such a self-contained subframe (or slot) structure, a time gap may be required during the transition from transmit mode to receive mode or from receive mode to transmit mode. To this end, some OFDM symbols during the transition from DL to UL in the subframe structure may be set as a Guard Period (GP).

[0086] Figure 6 illustrates the structure of a self-contained slot.

[0087] In an NR system, a frame is characterized by a self-complete structure in which a DL control channel, DL or UL data, a UL control channel, etc., can all be included within a single slot. For example, the first N symbols within the slot are used to transmit a DL control channel (hereinafter referred to as the DL control area), and the last M symbols within the slot may be used to transmit a UL control channel (hereinafter referred to as the UL control area). N and M are each integers greater than or equal to 0. The resource area (hereinafter referred to as the data area) located between the DL control area and the UL control area may be used for transmitting DL data or for transmitting UL data. As an example, the following configuration can be considered. Each section is listed in chronological order.

[0088] 1. DL only configuration

[0089] 2. UL only configuration

[0090] 3. Mixed UL-DL Configuration

[0091] - DL Area + GP (Guard Period) + UL Control Area

[0092] - DL Control Area + GP + UL Area

[0093] DL Area: (i) DL Data Area, (ii) DL Control Area + DL Data Area

[0094] UL Area: (i) UL Data Area, (ii) UL Data Area + UL Control Area

[0095] PDCCH can be transmitted in the DL control area, and PDSCH can be transmitted in the DL data area. PUCCH can be transmitted in the UL control area, and PUSCH can be transmitted in the UL data area. In PDCCH, DCI (Downlink Control Information), such as DL data scheduling information and UL data scheduling information, can be transmitted. In PUCCH, UCI (Uplink Control Information), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, and SR (Scheduling Request), can be transmitted. GP provides a time gap during the process in which the base station and the terminal switch from transmit mode to receive mode or from receive mode to transmit mode. Within a subframe, some symbols at the point of transition from DL to UL can be set as GP.

[0096] <NR에서 빔 측정(beam measurement)>

[0097] One disclosure of the present specification relates to a method involving the transmission and / or retransmission of a Physical Uplink Control Channel (PUCCH) to request the allocation or activation of uplink resources for beam reporting, in order for a terminal to report L1 (Layer 1) CSI (Channel State Information) measurement results via a Physical Uplink Shared Channel (PUSCH) based on events set by a base station.

[0098] Beam measurement in NR is based on the CSI framework and requires L1 measurement results to be reported to the base station according to CSI report settings. To reduce overhead caused by frequent reporting, L3 (Layer 3) measurement is defined to trigger the transmission of RRC (Radio Resource Control) messages from the terminal to the base station based on events configured by the base station. However, L1 measurement is defined so that reporting is performed periodically or only upon the instruction of the base station.

[0099] Figures 7a through 7c show examples of beam reporting procedures in NR.

[0100] Currently, L1 measurement result reporting in NR follows the base station's RRC settings, just like L3, and 3GPP defines that it should be set using one of the following three methods.

[0101] - Periodic reporting

[0102] - Aperioditic reporting

[0103] - Semi-persistent reporting

[0104] FIG. 7a illustrates a periodic CSI reporting method, which is triggered by an RRC configuration. Specifically, the terminal receives an RRC configuration message from the base station, which includes settings for CSI-related RS resources and reporting methods, i.e., CSI resource set information and information that CSI reporting is periodic (S701a). Subsequently, the terminal receives periodically transmitted RS based on the received RRC configuration message (S702a and S705a), and measures the signal strength of the beam based on the received RS (S703a and S706a). Then, the terminal periodically reports the measured result (value) to the base station (S704a and S707a).

[0105] FIG. 7b illustrates a non-periodic CSI reporting method. Even if CSI-related RS resources and reporting methods are configured via an RRC configuration message, beam measurement via RS is not performed without a trigger message (or information) from a lower layer. That is, the terminal receives an RRC configuration message from the base station containing information regarding the configuration of CSI-related RS resources and reporting methods, namely CSI resource set information and information that CSI reporting is non-periodic (S701b). The CSI report trigger is established via a MAC (medium access control) CE (control element) or DCI (downlink control information). The terminal receives CSI report trigger information containing a trigger indication from the base station via the MAC CE or DCI (S702b), and receives RSs transmitted once based on the received trigger indication (S703b). Here, the transmission of RSs for the CSI resource set may be transmitted after a specific time (e.g., X slots) in which the CSI report trigger information was transmitted. Subsequently, the terminal measures the signal strength of the beam based on the received RSs (S704b). Then, the terminal reports the measured result (value) to the base station once (S705b). Here, the CSI report may be transmitted after a specific time (e.g., Y slots) in which the CSI report trigger information was received.

[0106] FIG. 7c illustrates a semi-persistent reporting method, which is an intermediate method between periodic and non-periodic reporting methods. A terminal that receives settings for CSI-related RS resources and reporting methods via an RRC configuration message performs CSI reporting periodically only when activated by MAC CE, until it receives a deactivation message (or information). That is, the terminal receives an RRC configuration message from the base station containing settings for CSI-related RS resources and reporting methods, namely CSI resource set information and information that CSI reporting is semi-persistent (S701c), and CSI report activation is performed via MAC CE. The terminal receives CSI report activation information containing an activation indication from the base station via MAC CE (S702c and S710c), receives RSs periodically transmitted based on the received activation indication (S703c, S706c, S711c and S714c), and measures the signal strength of the beam based on the received RSs (S704c, S707c, S712c and S715c). Then, the terminal periodically reports the measured results (values) to the base station (S705c, S708c, S713c ​​and S716c). After CSI reporting is activated, if the terminal receives CSI report deactivation information containing a deactivation indication from the base station via MAC CE (S709c), the terminal stops CSI reporting.

[0107] The three methods for CSI reporting described above can be configured in relation to the transmission characteristics of the CSI-RS resource. That is, depending on the CSI-RS resource configuration, the RS can be configured to be transmitted periodic, semi-persistent, or aperioditic. In the case of periodic CSI-RS, the transmission periodicity and slot offset are set by the RRC, and accordingly, the CSI-RS is transmitted periodically. In the case of semi-persistent CSI-RS, the transmission periodicity and slot offset are set by the RRC, but the activation or deactivation of CSI-RS transmission is directed by the MAC CE (Control Element). In the case of aperioditic CSI-RS, the slot offset is set by the RRC, and CSI-RS transmission is triggered by the reception of DCI (Downlink Control Information). The characteristics of such CSI-RS transmission in the time domain are associated with the CSI reporting settings, which can determine the periodic, semi-persistent, or aperioditic mode of CSI reporting. Specifically, if CSI-RS transmission is set to periodic, CSI reporting can be set to periodic, semi-persistent, or aperioditic; if CSI-RS transmission is set to semi-persistent, CSI reporting can be set to semi-persistent or aperioditic; and if CSI-RS transmission is set to aperioditic, CSI reporting can be set to aperioditic only.

[0108] NR experiences frequent link failures due to beamforming technology in the high-frequency band. Timely beam reporting can minimize link failures at terminals by enabling rapid switching to the optimal beam before a link is interrupted. However, since current L1 beam reporting methods only support base station instruction-based reporting, CSI reporting must be configured periodically to ensure timely beam reporting. This causes overall system overhead by resulting in unnecessarily frequent beam result reporting. While semi-static or non-periodic CSI reporting can be configured to reduce overhead, this presents a problem where base stations may have difficulty receiving CSI reports at the appropriate time. To address these issues, 3GPP has initiated discussions to define an event-based L1 CSI reporting scheme.

[0109] In other words, 3GPP is introducing the concept of UE-Initiated Beam Reporting (UEIBR), in which a terminal independently detects changes in beam quality, determines the need for beam reporting, and actively initiates it. Generally, since terminals can recognize situations where beam quality changes due to increased mobility or changes in the channel environment more quickly and accurately than the network, it is considered that applying UEIBR will enable the provision of beam-related information in a more timely manner while reducing unnecessary periodic or frequent network-trigger-based beam reporting.

[0110] Currently, 3GPP has decided to support the following three events for UEIBR.

[0111] - Event-1: Quality of the current beam is worse than a certain threshold.

[0112] - Event-2: Quality of at least one new beam, such as L1-RSRP, becomes a threshold value better than the current beam.

[0113] - Event-7: Quality of at least one new beam, such as L1-RSRP, becomes a threshold value better than the RS derived from the activated TCI state with the Q-th best quality.

[0114] For UEIBR triggered based on the above event, it was decided to define UEIBR PUCCH so that the terminal could request PUSCH resources to transmit a CSI report, and UEIBR operation was defined in the following two modes depending on the method of allocating PUSCH.

[0115] Mode A (Dynamic DCI based)

[0116] The terminal sends a UEIBR PUCCH for the DCI request.

[0117] The terminal receives a DCI containing a CSI report request.

[0118] The terminal transmits the CSI report via the PUSCH directed by the DCI.

[0119] Mode B (Configured Grant (CG) based on PUSCH)

[0120] The terminal transmits a UEIBR PUCCH for notification.

[0121] The terminal transmits CSI reports via the PUSCH assigned by the configured grant.

[0122] In addition, it was decided to define a new UCI type for transmitting UEIBR PUCCH, and it is assumed that UEIBR PUCCH resources for this can be periodically allocated to terminals. Currently, discussions are proceeding based on a 1-bit indication, but whether to define a multi-bit indication in cases where a multi-event or multi-report configuration can be set up is left as a matter for further study (FFS).

[0123] In Mode A, dynamic push resources are allocated from the base station only after the UEIBR push transmission is successfully executed. If the base station fails to successfully receive the UEIBR push from the terminal due to poor channel conditions or various other reasons, the terminal may fail to receive the DCI, which allocates push resources for CSI report transmission. Persistent UEIBR push transmission failures result in the failure to transmit CSI reports that should be sent from the terminal; consequently, the base station that fails to receive these reports is unable to switch the terminal's beam to a new beam in a timely manner. This ultimately leads to beam failure or link failure and causes system performance degradation.

[0124] To minimize such beam / link failures, it is necessary to define a method for the terminal to re-request PSUCH resources by retransmitting the UEIBR PUCCH when it fails to receive the DCI from the base station allocating PUSCH resources for CSI reporting. In this regard, discussions are underway regarding the retransmission of the UEIBR PUCCH, the maximum number of transmissions, and methods utilizing a prohibit timer.

[0125] Meanwhile, in the case of conventional SR (Scheduling Request) PUCCH, a prohibit timer is set to avoid frequent transmission of SR PUCCHs triggered for the same purpose, and once an SR PUCCH is transmitted, additional SR PUCCH transmissions for the same purpose triggered by the prohibit timer are suspended. However, if the BSR (Buffer Status Report) transmission fails because the terminal has not been allocated PUSCH resources for BSR transmission despite continuously (re)transmitting SR PUCCHs, the terminal determines that there is a problem with the uplink channel, releases all related uplink resources, cancels all pending SRs, and attempts random access to the SpCell (Special Cell) (using RACH). Retransmission of UEIBR PUCCH also needs to be considered using a method similar to that of SR PUCCH; however, since UEIBR PUCCH has a different function from SR, it is desirable to define a PUCCH retransmission method suitable for it.

[0126] On the other hand, for Event 2, it is decided to define an event instance count to determine the event trigger time, and it is discussed that the terminal transmits a UEIBR PUCCH for transmitting a beam report only when M or more event instances are satisfied within a specific time window.

[0127] As described above, the terminal may start a timer for a time window when at least any new beam satisfies Event 2, and may instruct a UEIBR PUCCH transmission when M events occur within the time window (hereinafter referred to as BR event Instance, BRI). After transmitting the UEIBR PUCCH (or transmitting a CSI report via PUSCH), the terminal starts a prohibition timer, and the BRI, which is increased by additional events occurring while the prohibition timer is running, may continue to be counted until a TCI state update or RS reconfiguration / update for the new beam (or candidate beam) is satisfied. As a result, a situation may occur where an additional UEIBR PUCCH must be transmitted after the prohibition timer expires, i.e., a pending PUCCH transmission may occur.

[0128] However, UEIBR triggers an event when the beam strength / quality of the beam measured by the terminal indicates that a switch to a new beam is necessary. This implies that the terminal expects a beam indication directing the switch to a new beam by transmitting a CSI report regarding the beam results. If the terminal transmits a CSI report but fails to receive a TCI status update or beam indication, this results in a beam / link failure for the terminal. A UEIBR PUCCH retransmission method needs to be defined to resolve this issue.

[0129] FIG. 8 is a flowchart illustrating a method of operation of a terminal according to one embodiment of the present specification.

[0130] Referring to FIG. 8, the terminal receives UE-Initiated Beam Reporting (UEIBR) configuration information (S801) and, based on the received UEIBR configuration information, transmits first uplink control information related to the UEIBR through a Physical Uplink Control Channel (PUCCH) resource (S801). Then, based on the transmission of the first uplink control information, the terminal starts a timer (S803), and while the timer is running, transmits a report corresponding to the first uplink control information (S804). Additionally, based on the transmission of the report, the terminal restarts the timer (S805).

[0131] The above UEIBR configuration information may include information regarding the PUCCH resource and information regarding the timer. Additionally, the above UEIBR configuration information may further include at least one of UEIBR event information, UEIBR event trigger information, and information on the maximum number of transmissions of uplink control information related to the UEIBR.

[0132] When the transmission of the second uplink control information related to the UEIBR is triggered, the transmission of the second uplink control information may be suspended while the timer is operating.

[0133] Meanwhile, when the transmission of the first uplink control information and the second uplink control information reaches the maximum number of transmissions indicated by the maximum number of transmissions information, at least one of triggering a beam failure report, initiating a random access procedure, and canceling all pending UEIBR transmissions may be performed.

[0134] The terminal may receive beam indication information, RS (Reference Signal) reconfiguration information, or RS update information in response to the transmission of the above report.

[0135] If none of the beam indication information, RS (Reference Signal) reconfiguration information, or RS update information is received in response to the transmission of the above report, the above withheld second uplink control information may be transmitted.

[0136] The above timer can be named a prohibit timer.

[0137] The above UEIBR configuration information may be CSI report configuration information. Alternatively, the above UEIBR configuration information may be included within the CSI report configuration information.

[0138] The above description applies to both UEIBR Mode A and Mode B.

[0139] More specifically, the CSI reporting setting for the UEIBR received in the present invention may include, in addition to the prohibition timer, a value M for triggering a BR event (the UEIBR is triggered when the event is satisfied M times within an arbitrary time window) and a "br_TransMax" value representing the maximum number of transmissions for the UEIBR PUCCH. Based on such RRC parameters, the terminal may use the following variables.

[0140] - UEIBR_COUNTER

[0141] - BRI_COUNTER

[0142] When the terminal satisfies a configured event (per CSI report configuration, per event, per beam, or per UE), it increments BRI_COUNTER by 1. The BRI_COUNTER is counted within an arbitrary time window, and if BRI_COUNTER is reset, the timer for the time window is also stopped / reset. If a BRI is received from a lower layer, it is desirable for the time window to be restarted by sliding. However, the operating conditions for the time window and BRI counting described herein may operate independently of the present invention, and it is obvious that various methods may be applied, as such content is described by reference only for the purpose of explaining the present invention.

[0143] FIGS. 9 to 12 are drawings illustrating procedures of a base station and a terminal according to an embodiment of the present specification.

[0144] If the terminal satisfies the following conditions, it instructs the lower layer to transmit UEIBR PUCCH.

[0145] - If the BR event instance (i.e., BR_COUNTER) is greater than or equal to M;

[0146] - If the prohibition timer is not running;

[0147] - If UEIBR_COUNTER is less than the ueibr_TransMax value,

[0148] The terminal transmits UEIBR PUCCH.

[0149] The terminal starts a prohibition timer.

[0150] The terminal increments UEIBR_COUNTER by 1.

[0151] That is, the terminal that sent the UEIBR PUCCH starts the prohibit timer. While the prohibit timer is running, the BRI_COUNTER may be incremented by 1 due to additional BR event instances, and the UEIBR PUCCH may be triggered again accordingly, but because the prohibit timer is running, the PUCCH triggered at this time remains as a pending UEIBR.

[0152] If the terminal transmits a CSI report to the base station via PUSCH while the prohibition timer is running, the prohibition timer is restarted. If a PUCCH is triggered by a BRI occurring while the prohibition timer is running, the terminal holds it as a pending UEIBR. This is to prevent unnecessary transmission of a UEIBR PUCCH in cases where the BRI is not reset by the CSI report, but the BRI is subsequently counted and incremented due to additional satisfied events after the CSI report, thereby generating an additional UEIBR PUCCH. In other words, the present invention enables the generated pending PUCCH to be quickly transmitted to the base station after the prohibition timer expires, provided that the terminal does not receive a beam indication, TCI status update, or RS reconfiguration / update for the CSI report. That is, even if the terminal transmits a CSI report via PUSCH, if it does not receive the above information (i.e., beam indication, TCI status update, or RS reconfiguration / update), the terminal can understand that the CSI report it reported was not successfully transmitted to the base station. FIGS. 10 and 11 are examples of cases where the terminal retransmits the UEIBR PUCCH.

[0153] If there is a pending PUCCH, the terminal checks the conditions for transmitting the UEIBR PUCCH and, if the conditions are satisfied, retransmits the pending PUCCH. In Mode-A, if the terminal fails to transmit the CSI report associated with the transmitted UEIBR PUCCH after transmitting the pending UEIBR PUCCH, and all of the above conditions are satisfied, the terminal may consider that it has not received the DCI. Alternatively, if the terminal fails to receive a beam indication, TCI status update, or RS reconfiguration / update from the base station while the prohibition timer is running after transmitting the CSI report via PUSCH, and all of the above conditions are satisfied, the terminal may consider that the base station has not successfully received the CSI report.

[0154] The present invention causes the terminal to retransmit the UEIBR PUCCH in both of the above cases. Mode-B can operate in the same way as Mode-A. A terminal operating in Mode-B starts a prohibition timer after transmitting the UEIBR PUCCH, and restarts the prohibition timer after transmitting a CSI report via the PUSCH resource on the CG (Configured Grant). This not only provides a unified solution for Modes-A and B, but also serves as a method to prevent duplicate transmission of the UEIBR PUCCH that could be additionally triggered during the time between the terminal transmitting the UEIBR PUCCH and transmitting the CSI report via the CG's PUSCH. If the terminal operating in Mode-B does not receive a beam indication, TCI status update, or RS reconfiguration / update from the base station while the prohibition timer is operating, and all of the above conditions are satisfied, the terminal considers that the base station has not successfully received the CSI report and retransmits the pending UEIBR PUCCH.

[0155] The operation of the prohibition timer proposed in this invention is to start after the transmission of the UEIBR PUCCH using a single timer and restart the corresponding timer when the PUSCH is transmitted, but a first prohibition timer for the transmission of the UEIBR PUCCH and a second prohibition timer for the transmission of the CSI report may also be set. That is, the present invention may be operated using two such different timers. This means that if the prohibition timer operating for the PUSCH needs to be set to a time value shorter or longer than the prohibition timer set for the PUCCH, the base station can control the transmission of the UEIBR PUCCH by setting two different timers to the terminal.

[0156] The following describes the stop / reset conditions for the prohibition timer. If at least one of the following conditions is satisfied, the terminal stops / resets the prohibition timer, cancels all pending UEIBR PUCCHs, and resets BRI_COUNTER to 0.

[0157] - If RS reconfiguration / update for new beam is received,

[0158] - If the measured current beam based on the indicated TCI state is updated,

[0159] Stop / reset the prohibition timer.

[0160] Cancel all pending UEIBR PUCCH.

[0161] Stops / resets the timer for the time window for BRI.

[0162] Reset BRI_COUNTER

[0163] As previously described, if retransmissions of the UEIBR PUCCH continue to occur despite the UEIBR PUCCH being (re)transmitted, and the number of transmissions of the UEIBR PUCCH associated with any CSI report reaches the br_TrnasMax value, the terminal may determine that there is a problem with the quality of the uplink channel. In this case, the terminal may stop the relevant CSI report and perform at least one of the following actions.

[0164] - Trigger Beam Failure Report (on the PUCCH cell or the PUCCH group cell) and cancel all pending UEIBRs.

[0165] - Notify the RRC to release PUCCH for all Serving Cells.

[0166] - Notify the RRC to release SRS for all Serving Cells.

[0167] - Clears all configured downlink assignments and uplink grants.

[0168] - Clear all PUSCH resources for semi-persistent CSI reporting.

[0169] - Initiate a Random Access procedure on the SpCell and cancel all pending UEIBRs.

[0170] Figure 12 shows an example of the case where the UEIBR PUCCH described above reaches the maximum number of transmissions.

[0171] With reference to FIGS. 9 to 12, a method of operation of a terminal according to one embodiment of the present specification is described in detail below.

[0172] The terminal receives a CSI report configuration from the base station that includes at least one of the following information.

[0173] - Event information for UEIBR and information on the parameter(s) required to trigger the event

[0174] - UEIBR PUCCH resource information

[0175] _ prohibit timer

[0176] - Maximum number of transmissions for UEIBR PUCCH (ueibr_TransMax)

[0177] If UEIBR is triggered and there are no pending UEIBRs for the same configuration (e.g., event / beam / report), set UEIBR_COUNTER to 0.

[0178] When a UEIBR is triggered, it is considered pending until it is canceled.

[0179] If an RS reconfiguration / update for a new beam is received, or a TCI state update / beam indication is received, all pending UEIBRs are cancelled and the prohibition timer is stopped.

[0180] If the prohibition timer is not running,

[0181] If UEIBR_COUNTER is smaller than ueibr_TransMax

[0182] >> Instructs the lower layer to send UEIBR to a valid PUCCH resource for UEBIR.

[0183] >> Increase UEIBR_COUNTER by 1.

[0184] Start Prohibit timer.

[0185] Otherwise, (if UEIBR_COUNTER is equal to or greater than ueibr_TransMax) perform at least one of the following actions.

[0186] >> Trigger Beam Failure Report (on the PUCCH cell or the PUCCH group cell) and cancel all pending UEIBRs.

[0187] Notify the RRC to release PUCCH for all Serving Cells.

[0188] Notify the RRC to release SRS for all Serving Cells.

[0189] Clears all configured downlink assignments and uplink grants.

[0190] Clear all PUSCH resources for semi-persistent CSI reporting.

[0191] Initiate a Random Access procedure on the SpCell and cancel all pending UEIBRs.

[0192] If you are instructed to transmit a CSI report for a UEIBR PUCCH transmitted from a lower layer,

[0193] Restart the ban timer.

[0194] With reference to FIGS. 9 to 12, a method of operation of a base station according to one embodiment of the present specification is described in detail below.

[0195] The base station transmits a CSI report configuration containing at least one of the following information to the terminal.

[0196] - Event information for UEIBR and information on the parameter(s) required to trigger the event

[0197] - UEIBR PUCCH resource information

[0198] _ prohibit timer

[0199] - Maximum number of transmissions for UEIBR PUCCH (ueibr_TransMax)

[0200] The base station receives the UEIBR PUCCH from the terminal.

[0201] If there is no CG (Configured Grant) PUSCH configured on the terminal,

[0202] Transmits the DCI containing resource information for CSI reporting.

[0203] If there is a CG PUSCH set on the terminal,

[0204] Expect to receive CSI reports through the relevant CG PUSCH resource.

[0205] The base station receives a CSI report from the terminal.

[0206] The base station transmits a TCI state update / beam indication to the terminal instructing it to use a new beam.

[0207] The disclosures of this specification described above may be implemented through various means. For example, the disclosures of this specification may be implemented by hardware, firmware, software, or a combination thereof. Specifically, they will be described below with reference to the drawings.

[0208] FIG. 13 shows an apparatus according to one embodiment of the present specification.

[0209] Referring to FIG. 13, the wireless communication system may include a first device (100a) and a second device (100b).

[0210] The first device (100a) may be a base station, network node, transmission terminal, receiving terminal, wireless device, wireless communication device, vehicle, vehicle equipped with autonomous driving function, connected car, drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, fintech device (or financial device), security device, climate / environment device, device related to 5G service, or other device related to the field of the Fourth Industrial Revolution.

[0211] The second device (100b) may be a base station, network node, transmission terminal, receiving terminal, wireless device, wireless communication device, vehicle, vehicle equipped with autonomous driving function, connected car, drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, fintech device (or financial device), security device, climate / environment device, device related to 5G service, or other device related to the field of the Fourth Industrial Revolution.

[0212] The first device (100a) may include at least one processor, such as a processor (1020a), at least one memory, such as a memory (1010a), and at least one transceiver, such as a transceiver (1031a). The processor (1020a) may perform the aforementioned functions, procedures, and / or methods. The processor (1020a) may perform one or more protocols. For example, the processor (1020a) may perform one or more layers of a wireless interface protocol. The memory (1010a) is connected to the processor (1020a) and may store various forms of information and / or commands. The transceiver (1031a) is connected to the processor (1020a) and may be controlled to transmit and receive wireless signals.

[0213] The second device (100b) may include at least one processor, such as a processor (1020b), at least one memory device, such as a memory (1010b), and at least one transceiver, such as a transceiver (1031b). The processor (1020b) may perform the aforementioned functions, procedures, and / or methods. The processor (1020b) may implement one or more protocols. For example, the processor (1020b) may implement one or more layers of a wireless interface protocol. The memory (1010b) is connected to the processor (1020b) and may store various forms of information and / or commands. The transceiver (1031b) is connected to the processor (1020b) and may be controlled to transmit and receive wireless signals.

[0214] The memory (1010a) and / or the memory (1010b) may be connected to the processor (1020a) and / or the processor (1020b) respectively, either internally or externally, and may also be connected to other processors through various technologies such as wired or wireless connections.

[0215] The first device (100a) and / or the second device (100b) may have one or more antennas. For example, the antenna (1036a) and / or antenna (1036b) may be configured to transmit and receive wireless signals.

[0216] FIG. 14 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0217] In particular, FIG. 14 is a drawing illustrating the device of FIG. 13 in more detail.

[0218] The device includes a memory (1010), a processor (1020), a transceiver (1031), a power management module (1091), a battery (1092), a display (1041), an input unit (1053), a speaker (1042) and a microphone (1052), a SIM (subscriber identification module) card, and one or more antennas.

[0219] The processor (1020) may be configured to implement the proposed functions, procedures, and / or methods described herein. Layers of a radio interface protocol may be implemented in the processor (1020). The processor (1020) may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor (1020) may be an application processor (AP). The processor (1020) may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of processors (1020) may be SNAPDRAGON™ series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIO™ series processors manufactured by MediaTek®, ATOM™ series processors manufactured by INTEL®, KIRINTM series processors manufactured by HiSilicon®, or corresponding next-generation processors.

[0220] The power management module (1091) manages power for the processor (1020) and / or the transceiver (1031). The battery (1092) supplies power to the power management module (1091). The display (1041) outputs the results processed by the processor (1020). The input unit (1053) receives input to be used by the processor (1020). The input unit (1053) may be displayed on the display (1041). A SIM card is an integrated circuit used to securely store the International Mobile Subscriber Identity (IMSI) and associated keys used to identify and authenticate a subscriber in mobile devices such as mobile phones and computers. Contact information may also be stored on many SIM cards.

[0221] Memory (1010) is operably coupled with the processor (1020) and stores various information for operating the processor (610). Memory (1010) may include ROM (read-only memory), RAM (random access memory), flash memory, memory card, storage medium and / or other storage device. Where the embodiment is implemented in software, the techniques described herein may be implemented as modules (e.g., procedures, functions, etc.) that perform the functions described herein. Modules may be stored in memory (1010) and executed by the processor (1020). Memory (1010) may be implemented inside the processor (1020). Alternatively, memory (1010) may be implemented outside the processor (1020) and may be communically connected to the processor (1020) through various means known in the art.

[0222] The transceiver (1031) is operably coupled with the processor (1020) and transmits and / or receives a wireless signal. The transceiver (1031) includes a transmitter and a receiver. The transceiver (1031) may include a baseband circuit for processing a wireless frequency signal. The transceiver controls one or more antennas to transmit and / or receive a wireless signal. The processor (1020) transmits command information to the transceiver (1031) to transmit a wireless signal, for example, constituting voice communication data, in order to initiate communication. The antennas function to transmit and receive wireless signals. When receiving a wireless signal, the transceiver (1031) may transmit the signal to the processor (1020) for processing and convert the signal to baseband. The processed signal may be converted into audible or readable information output through a speaker (1042).

[0223] The speaker (1042) outputs sound-related results processed by the processor (1020). The microphone (1052) receives sound-related input to be used by the processor (1020).

[0224] The user inputs command information, such as a phone number, by, for example, pressing (or touching) a button on the input unit (1053) or by voice activation using the microphone (1052). The processor (1020) receives this command information and processes it to perform appropriate functions, such as making a call to the phone number. Operational data can be extracted from a SIM card or memory (1010). Additionally, the processor (1020) can display the command information or operation information on the display (1041) for the user's awareness and convenience.

[0225] FIG. 15 shows a block diagram of a processor in which the disclosure of the present specification is implemented.

[0226] As can be seen with reference to FIG. 15, a processor (1020) in which the disclosure of this specification is implemented may include a plurality of circuits to implement the proposed functions, procedures and / or methods described in this specification. For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3). Additionally, although not illustrated, the processor (1020) may include more circuits. Each circuit may include a plurality of transistors.

[0227] The above processor (1020) may be called an ASIC (application-specific integrated circuit) or an AP (application processor), and may include at least one of a DSP (digital signal processor), a CPU (central processing unit), and a GPU (graphics processing unit).

[0228] FIG. 16 is a block diagram showing in detail the transceiver of the first device shown in FIG. 13 or the transceiver of the device shown in FIG. 14.

[0229] Referring to FIG. 16, the transceiver unit (1031) includes a transmitter (1031-1) and a receiver (1031-2). The transmitter (1031-1) includes a Discrete Fourier Transform (DFT) unit (1031-11), a subcarrier mapper (1031-12), an IFFT unit (1031-13), a CP insertion unit (1031-14), and a wireless transmitter (1031-15). The transmitter (1031-1) may further include a modulator. Additionally, it may further include, for example, a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown), and a layer permutator (not shown), which may be positioned prior to the DFT unit (1031-11). That is, to prevent an increase in the PAPR (peak-to-average power ratio), the transmitter (1031-1) first passes the information through the DFT (1031-11) before mapping the signal to the subcarrier. After the signal spread (or precoded in the same sense) by the DFT section (1031-11) is mapped to the subcarrier through the subcarrier mapper (1031-12), it is then passed through the IFFT (Inverse Fast Fourier Transform) section (1031-13) to form a signal on the time axis.

[0230] The DFT unit (1031-11) performs a DFT on the input symbols to output complex-valued symbols. For example, if Ntx symbols are input (where Ntx is a natural number), the DFT size is Ntx. The DFT unit (1031-11) may be called a transform precoder. The subcarrier mapper (1031-12) maps the complex-valued symbols to each subcarrier in the frequency domain. The complex-valued symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper (1031-12) may be called a resource element mapper. The IFFT unit (1031-13) performs an IFFT on the input symbols to output a baseband signal for the data, which is a time-domain signal. The CP insertion section (1031-14) copies a portion of the latter part of the base band signal for data and inserts it into the front part of the base band signal for data. Through CP insertion, Inter-Symbol Interference (ISI) and Inter-Carrier Interference (ICI) are prevented, so that orthogonality can be maintained even in a multipath channel.

[0231] On the other hand, the receiver (1031-2) includes a wireless receiver (1031-21), a CP removal unit (1031-22), an FFT unit (1031-23), and an equalization unit (1031-24), etc. The wireless receiver (1031-21), CP removal unit (1031-22), and FFT unit (1031-23) of the receiver (1031-2) perform the inverse functions of the wireless transmitter (1031-15), CP insertion unit (1031-14), and IFF unit (1031-13) of the transmitter (1031-1). The receiver (1031-2) may further include a demodulator.

[0232] Although preferred embodiments have been described by way of example above, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0233] In the exemplary system described above, methods are described based on a flowchart as a series of steps or blocks, but are not limited to the order of the described steps, and some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, a person skilled in the art will understand that the steps shown in the flowchart are not exclusive, and that other steps may be included, or that one or more steps of the flowchart may be omitted without affecting the scope of rights.

[0234] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.

Claims

1. In a method of operation of a terminal in a wireless communication system, Step of receiving UEIBR (UE-Initiated Beam Reporting) configuration information; Based on the above UEIBR configuration information, a step of transmitting first uplink control information related to the UEIBR through a PUCCH (Physical Uplink Control Channel) resource; A step of starting a timer based on the transmission of the first uplink control information; A step of transmitting a report corresponding to the first uplink control information while the timer is operating; and A method comprising the step of restarting the timer based on the transmission of the above report.

2. In Paragraph 1, A method in which the above UEIBR configuration information includes information about the PUCCH resource and information about the timer.

3. In Paragraph 2, A method comprising at least one of the above-mentioned UEIBR configuration information, UEIBR event information, UEIBR event trigger information, and information on the maximum number of transmissions of uplink control information related to the UEIBR.

4. In Paragraph 3, A method in which, when the transmission of second uplink control information related to UEIBR is triggered, the transmission of said second uplink control information is suspended while said timer is operating.

5. In Paragraph 4, A method in which, when the transmission of the first uplink control information and the second uplink control information reaches the maximum number of transmissions indicated by the maximum number of transmissions information, at least one of triggering a beam failure report, initiating a random access procedure, and canceling all pending UEIBR transmissions is performed.

6. In Paragraph 1, A method further comprising the step of receiving beam indication information, RS (Reference Signal) reconfiguration information, or RS update information in response to the transmission of the above report.

7. In Paragraph 4, A method in which, if none of the beam indication information, RS (Reference Signal) reconfiguration information, or RS update information is received in response to the transmission of the above report, the withheld second uplink control information is transmitted.

8. As a terminal in a wireless communication system, At least one processor; and The operation performed based on the instruction being executed by the at least one processor includes at least one memory that stores instructions and is operablely electrically connected to the at least one processor: A step of receiving UEIBR (UE-Initiated Beam Reporting) configuration information, and Based on the above UEIBR configuration information, the step of transmitting first uplink control information related to the UEIBR through a PUCCH (Physical Uplink Control Channel) resource, and Based on the transmission of the first uplink control information above, the step of starting a timer, and The step of transmitting a report corresponding to the first uplink control information while the above timer is operating, and, A terminal comprising the step of restarting the timer based on the transmission of the above report.

9. In Paragraph 8, A terminal, wherein the above UEIBR configuration information includes information about the PUCCH resource and information about the timer.

10. In Paragraph 9, A terminal comprising at least one of the above UEIBR configuration information, UEIBR event information, UEIBR event trigger information, and information on the maximum number of transmissions of uplink control information related to UEIBR.

11. In Paragraph 10, A terminal in which, when the transmission of second uplink control information related to UEIBR is triggered, the transmission of said second uplink control information is suspended while said timer is operating.

12. In Paragraph 11, A terminal in which, when the transmission of the first uplink control information and the second uplink control information reaches the maximum number of transmissions indicated by the maximum number of transmissions information, at least one of triggering a beam failure report, initiating a random access procedure, and canceling all pending UEIBR transmissions is performed.

13. In Paragraph 8, A terminal further comprising the step of receiving beam indication information, RS (Reference Signal) reconfiguration information, or RS update information in response to the transmission of the above report.

14. In Paragraph 11, A terminal in which, in response to the transmission of the above report, none of the beam indication information, RS (Reference Signal) reconfiguration information, or RS update information is received, the above withheld second uplink control information is transmitted.

Images