Method and apparatus for dropping and / or multiplexing when ueibr uci and pusch are overlapped

Abstract

The present specification provides a method and apparatus for dropping and / or multiplexing when UEIBR UCI and PUSCH overlap in a wireless communication system. When a PUCCH (physical uplink control channel) resource for transmitting UEIBR (UE-Initiated Beam Reporting) UCI ​​(uplink control information) and a PUSCH (physical uplink shared channel) resource for transmitting PUSCH overlap, the terminal i) drops one of the UEIBR UCI transmission and the PUSCH transmission, or ii) multiplexes the UEIBR UCI transmission and the PUSCH transmission.

Description

Technology Field

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

[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). The problem to be solved

[0004] The present invention aims to provide a method and apparatus for efficiently performing operations during the overlap of UEIBR UCI and PUSCH in a wireless communication system. means of solving the problem

[0005] The present specification provides a method and apparatus for dropping and / or multiplexing when UEIBR UCI and PUSCH overlap in a wireless communication system. When a PUCCH (physical uplink control channel) resource for transmitting UEIBR (UE-Initiated Beam Reporting) UCI ​​(uplink control information) and a PUSCH (physical uplink shared channel) resource for transmitting PUSCH overlap, the terminal i) drops one of the UEIBR UCI transmission and the PUSCH transmission, or ii) multiplexes the UEIBR UCI transmission and the PUSCH transmission. Effects of the invention

[0006] According to the disclosure of this specification, the operation during the overlap of UEIBR UCI and PUSCH in a wireless communication system can be performed efficiently. Brief explanation of the drawing

[0007] Figure 1 illustrates the structure of a wireless frame used in NR. Figure 2 illustrates the slot structure of an NR frame. Figure 3 illustrates the structure of a self-contained slot. Figure 4 is a diagram illustrating the legacy reporting method and the UEIBR method. Figure 5 is a diagram illustrating the case where PUCCH resources and PUSCH resources overlap. FIG. 6 shows a configuration block diagram of a processor in which the disclosure of the present specification is implemented. FIG. 7 shows a wireless communication device according to one embodiment of the present specification. FIG. 8 illustrates a block diagram of a network node according to one embodiment of the present specification. FIG. 9 illustrates a block diagram of a communication device according to one embodiment of the present specification. Specific details for implementing the invention

[0008] 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.

[0009] In addition, the name of the base station may be used as a comprehensive term including RRH (remote radio head), eNB, TP (transmission point), RP (reception point), relay, etc.

[0010] 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 carrying information originating from upper layers, and uplink physical signals corresponding to resource elements used by the physical layer but not carrying 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.

[0011] 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.

[0012] Figure 1 illustrates the structure of a wireless frame used in NR.

[0013] 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).

[0014] Table 1 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS when a standard CP is used.

[0015] SCS(15*2 u ) N slot symb N frame,u slot N subframe,u slot 15 KHz(u =0) 14 10 1 30 KHz(u =1) 14 20 2 60 KHz(u =2) 14 40 4 120 KHz(u =3) 14 80 8 240 KHz(u =4) 14 160 16

[0016] N slot symb : Number of symbols in the slot

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

[0018] N subframe,u slot : Number of slots in the subframe

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

[0020] SCS (15*2 u ) N　 slot 　 symb N　 frame,u 　 slot N　 subframe,u 　 slot 60KHz (u=2) 12 40 4

[0021] ​​​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.

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

[0023] 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 (P)RBs 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., 4) BWPs. Data communication is performed through the active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is referred to as a Resource Element (RE) and can be mapped to a single complex symbol.

[0024] Figure 3 illustrates the structure of a self-contained slot.

[0025] 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.

[0026] 1. DL only configuration

[0027] 2. UL only configuration

[0028] 3. Mixed UL-DL Configuration

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

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

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

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

[0033] 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. Downlink Control Information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted in PDCCH. Uplink Control Information (UCI), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, Channel State Information (CSI), and Scheduling Request (SR), can be transmitted in PUCCH. GP provides a time gap during the process of the base station and the terminal switching 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.

[0034] <Disclosure of the present specification>

[0035] The present invention proposes a method for UEs to report new beams to the network more actively and resourcefully in a 3GPP NR system for UE-Initiated Beam Reporting (UEIBR).

[0036] In particular, a multiplexing method is provided when UEIBR Uplink Channel Information (UCI) is PUCCH Format 0 and another UCI is PUCCH Format 1, or when UEIBR UCI is PUCCH Format 1 and another UCI is PUCCH Format 2.

[0037] Figure 4 is a diagram illustrating the legacy reporting method and the UEIBR method.

[0038] In existing beam management procedures, the network can configure or enable frequent periodic or semi-persistent beam reporting, or frequently trigger non-periodic beam reporting to ensure optimal / preferred beams for data and control transmissions are secured in a timely manner. However, this approach clearly leads to the problem of increased uplink reporting and control signal overhead. On the other hand, if the beam reporting frequency is reduced, the beam information reported by the UE becomes outdated, preventing the network from always servicing the UE with the optimal beam, which can lead to performance degradation. Conversely, since the UE can identify changes in beam quality more quickly and accurately, applying UEIBR allows for the provision of beam information more timely while reducing reporting overhead. Figure 4 is a schematic diagram comparing the legacy reporting method and the UEIBR method.

[0039] Referring to Figure 4, the terminal measures the quality of Beam 1 and Beam 2 at every moment, and the optimal beam changes from Beam 1 to Beam 2 around time ①. Therefore, it is optimal to be served by Beam 2 after time ①. However, in the case of the legacy reporting method, the terminal must report the beam at a fixed interval, so it cannot report at time ① and can only report to replace the beam at time ②, which is the earliest reporting time after time ①. However, this results in performance degradation because the terminal is served by a beam that is no longer the optimal beam from time ① to time ②. On the other hand, in the case of UEIBR, the terminal can report at time ①, immediately upon measuring that the optimal beam is Beam 2. Therefore, performance degradation can be prevented.

[0040] The Work Item Description (WID) of UEIBR defined in the NR MIMO Phase 5 item of 3GPP Release 19 is as follows.

[0041] 1. Specify enhancement to facilitate UE-initiated / event-driven beam management for reducing overhead and / or latency, assuming the unified TCI while leveraging (as much as possible) legacy CSI measurement and reporting configuration frameworks, targeting FR2 and sTRP with intra- and inter-cell beam management

[0042] a. UL signaling content(s) (and procedure(s) as required) for UE-initiated / event-driven beam reporting facilitating fast beam switching

[0043] b. UL signaling medium / container considering the UE-initiated / event-driven nature of the UL transmission, designed primarily for the purpose of beam reporting

[0044] WG1 #119 회의에서 아래와 같은 내용들이 합의되었다.

[0045] Agreement

[0046] Confirm the following working assumption in RAN1#117:

[0047] On beam report transmission procedure for UE-initiated / event-driven beam reporting

[0048] - For mode-A, at least support one-bit indication in the first PUCCH channel to request a resource for a second UL channel to carry beam report.

[0049] o In such case, a periodic PUCCH resource (with PUCCH format 0 / 1) is configured by dedicated RRC signaling.

[0050] - For mode-B, at least support one-bit indication in the first PUCCH channel to notify a second UL channel to carry beam report.

[0051] o In such case, a periodic PUCCH resource (with PUCCH format 0 / 1) is configured by dedicated RRC signaling.

[0052] - FFS: Whether / how to support multi-bit indication in the first PUCCH for mode-A and mode-B, e.g., when multi-event(s) are approved.

[0053] - FFS: details on the dedicated RRC signaling

[0054] Agreement

[0055] On beam report transmission procedure for UE-initiated / event-driven beam reporting, regarding first PUCCH channel configuration, Alt-2 is supported for both mode-A and mode-B: the first PUCCH channel is a new UCI type

[0056] - Alt-2 (new UCI type): Introduce RRC parameter, e.g., firstPUCCHResourceConfig- UEIBR, for the periodic PUCCH resource configuration.

[0057] * It is RAN1's understanding that the RRC parameter is NOT associated with SchedulingRequestId.

[0058] * 1-bit to PUCCH resource is encoded by reusing the encoding mechanism of positive / negative SR.

[0059] * The dedicated RRC parameter at least comprises the following:

[0060] periodicityAndOffset

[0061] PUCCH-ResourceID

[0062] - Above applies at least for the single CC case.

[0063] - Reuse multiplexing / dropping rule(s) of SR as baseline

[0064] * FFS: overlapping with SR / LRR or PUSCH

[0065] Note: Further details on first PUCCH retransmission (if supported) for mode A and mode B will be continued to be separately discussed in RAN1.

[0066] According to the agreement reached at the RAN1 #119 meeting, RRC parameters related to a PUCCH resource for transmitting a UEIBR UCI named firstPUCCHResourceConfig-UEIBR will be defined. Additionally, it was agreed to set the PUCCH resource ID and period for the said PUCCH resource. At the RAN1 #117 meeting, it was agreed to set the format of firstPUCCHResourceConfig-UEIBR to 0 or 1.

[0067] Figure 5 is a diagram illustrating the case where PUCCH resources and PUSCH resources overlap.

[0068] When PUCCH resources for transmitting UEIBR Uplink Channel Information (UCI) are allocated periodically, said PUCCH resources may overlap with the Physical Uplink Shared Channel (PUSCH) in the time domain.

[0069] Figure 5 illustrates a case where PUCCH resources and PUSCH resources for UEIBR UCI transmission overlap in the time domain. The present invention provides a method for dropping and multiplexing when PUCCH resources allocated for UEIBR UCI transmission overlap with PUSCH resources.

[0070] Dropping method

[0071] 1. UEIBR UCI drop:

[0072] The terminal always drops the UEIBR UCI transmission if the PUCCH and PUSCH resources for the UEIBR UCI transmission overlap.

[0073] 2. PUSCH Priority-based drop:

[0074] The terminal determines whether to drop the UEIBR UCI by distinguishing the priority of the PUSCH.

[0075] [Example] Dropping rule: It can be set as Priority 1 PUSCH > Priority 2 PUSCH > UEIBR UCI > Priority 3 PUSCH. In this case, the terminal decides whether to drop UEIBR based on the PUSCH priority.

[0076] PUSCH Priority can be set by the base station.

[0077] In the present invention, the PUSCH priority may vary depending on the type of information included in the PUSCH (e.g., channel status information, scheduling requests, HARQ responses, etc.) or the importance of the information that the terminal intends to transmit, and the present invention does not specify the factors determining the priority.

[0078] 3. Count-based drop:

[0079] If the PUCCH resource and PUSCH resource for UEIBR UCI transmission overlap, the terminal increases the count value. If the count value is less than or equal to the set count threshold value, the UEIBR UCI transmission is dropped.

[0080] Count threshold value(s) can be set from the base station.

[0081] If the Count value exceeds the threshold, PUSCH can be dropped.

[0082] The dropable count value can be set differently depending on the PUSCH priority.

[0083] [Example]. Table 3

[0084] Count value Dropable PUSCH Priority 1 PUSCH Priority 2 PUSCH Priority 3 PUSCH

[0085] The terminal resets the count after dropping the PUSCH.

[0086] In the present invention, if the count threshold value is not separately set, the terminal assumes the count threshold value to be 0.

[0087] Multiplexing method

[0088] 1. Resource Element (RE) Puncturing:

[0089] The base station can reserve an RE for 1-bit UEIBR UCI transmission, and if the PUCCH resource and PUSCH resource for UEIBR UCI transmission overlap, the terminal punctures a 1-bit into the reserved RE of PUSCH for UEIBR UCI transmission.

[0090] The terminal can receive the following information from the base station.

[0091] The following information is information required by the terminal for UEIBR UCI transmission and includes RE location information for UEIBR UCI transmission, a channel coding method for modulating 1-bit, and a symbol modulation scheme.

[0092] i. First OFDM symbol in time domain: reserved RE position start time position information

[0093] ii. First subcarrier in frequency domain: reserved. Starting frequency location information of the RE position.

[0094] iii. Periodic spacing in time domain: Periodic interval information in the time domain

[0095] iv. Periodic spacing in frequency domain: Periodic spacing information in the frequency domain

[0096] v. Total number of OFDM symbols: Total length information in the time domain

[0097] vi. Total number of subcarriers: Total length information in the frequency domain

[0098] vii. Coding scheme and modulation: Information for encoding 1-bits and symbol modulation

[0099] The terminal identifies the location to insert the UEIBR UCI using the following information, applies the configured channel coding and symbol modulation scheme, and transmits it via the PUCCH resource.

[0100] After transmission, the terminal expects to receive DCI containing the CSI report request.

[0101] <General devices to which this specification may apply>

[0102] Hereinafter, devices to which the present specification may be applied are described.

[0103] FIG. 6 shows a configuration block diagram of a processor in which the disclosure of the present specification is implemented.

[0104] As can be seen with reference to FIG. 6, a processor (1020) in which the disclosure of the present specification is implemented may include a plurality of circuits to implement the proposed functions, procedures and / or methods described in the present specification. For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3).

[0105] Additionally, although not illustrated, the processor (1020) may include more circuits. Each circuit may include multiple transistors.

[0106] 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).

[0107] FIG. 7 shows a wireless communication device according to one embodiment of the present specification.

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

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] FIG. 8 illustrates a block diagram of a network node according to one embodiment of the present specification.

[0116] In particular, Figure 8 is a diagram illustrating the network node of Figure 7 in more detail when the base station is divided into a central unit (CU) and a distributed unit (DU).

[0117] Referring to FIG. 9, base stations (W20, W30) may be connected to a core network (W10), and base station (W30) may be connected to a neighboring base station (W20). For example, the interface between base stations (W20, W30) and the core network (W10) may be referred to as NG, and the interface between base station (W30) and neighboring base station (W20) may be referred to as Xn.

[0118] The base station (W30) can be divided into a CU (W32) and a DU (W34, W36). That is, the base station (W30) can be operated in a hierarchically separated manner. The CU (W32) may be connected to one or more DUs (W34, W36), and, for example, the interface between the CU (W32) and the DU (W34, W36) can be referred to as F1.

[0119] The CU (W32) can perform the functions of the upper layers of the base station, and the DU (W34, W36) can perform the functions of the lower layers of the base station. For example, the CU (W32) may be a logical node hosting the RRC (radio resource control), SDAP (service data adaptation protocol), and PDCP (packet data convergence protocol) layers of the base station (e.g., gNB), and the DU (W34, W36) may be a logical node hosting the RLC (radio link control), MAC (media access control), and PHY (physical) layers of the base station. Alternatively, the CU (W32) may be a logical node hosting the RRC and PDCP layers of the base station (e.g., en-gNB).

[0120] The operation of the DU (W34, W36) can be partially controlled by the CU (W32). A single DU (W34, W36) can support one or more cells. A single cell can be supported by only one DU (W34, W36). A single DU (W34, W36) can be connected to one CU (W32), and with appropriate implementation, a single DU (W34, W36) can be connected to multiple CUs.

[0121] FIG. 9 illustrates a block diagram of a communication device according to one embodiment of the present specification.

[0122] In particular, Fig. 9 is a drawing that illustrates the terminal of Fig. 7 in more detail.

[0123] The terminal 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.

[0124] The processor (1020) may be configured to implement the proposed functions, procedures, and / or methods described herein. Layers of a wireless 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 the processor (1020) may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or a corresponding next-generation processor.

[0125] 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.

[0126] 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.

[0127] 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).

[0128] 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).

[0129] 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).

[0130] The processor (1020) receives this command information and processes it to perform appropriate functions, such as making a call to a phone number. Operational data can be extracted from a SIM card or memory (1010).

[0131] Additionally, the processor (1020) can display command information or driving information on the display (1041) for the user to recognize and for convenience.

[0132] The examples of the present disclosure disclosed in this specification and drawings are provided merely to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present name. It is obvious to those skilled in the art that other variations based on the technical concept of the invention are possible in addition to the examples disclosed herein.

Claims

Claim 1 A method of operation of a terminal in a wireless communication system, wherein when a PUCCH (physical uplink control channel) resource for transmitting UEIBR (UE-Initiated Beam Reporting) UCI ​​(uplink control information) and a PUSCH (physical uplink shared channel) resource for transmitting PUSCH overlap, the method comprises the steps of: i) dropping one of the UEIBR UCI transmission and the PUSCH transmission, or ii) multiplexing the UEIBR UCI transmission and the PUSCH transmission.

Images