Method for transmitting or receiving a physical uplink shared channel in a channel occupancy time and apparatus therefor

Abstract

A method for a terminal to transmit a physical uplink shared channel (PUSCH) in a wireless communication system is disclosed. Specifically, the disclosure includes receiving, from a higher layer, a first energy detection (ED) threshold for channel occupancy time (COT) sharing, obtaining one ED threshold among the first ED threshold and a second ED threshold determined by the terminal based on a maximum uplink (UL) power based on whether COT sharing can be used, and transmitting the PUSCH based on the one ED threshold, wherein the one ED threshold is the first ED threshold based on that COT sharing can be used, and the one ED threshold is the second ED threshold based on that COT sharing cannot be used.

Description

Technical Field

[0001] This disclosure relates to physical uplink sharing of a channel during channel occupancy time, and more specifically, to a method and apparatus for determining an energy detection threshold to be used by a user equipment for channel access procedures based on whether channel occupancy time sharing is permitted. Background Technology

[0002] As more and more communication devices require greater communication services in line with current trends, the next-generation fifth-generation (5G) system is needed to provide enhanced wireless broadband communication compared to traditional LTE systems. In the next-generation 5G system, communication scenarios are divided into enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC), among others.

[0003] In this paper, eMBB is a next-generation mobile communication scenario characterized by high spectral efficiency, high user experience data rate, and high peak data rate; URLLC is a next-generation mobile communication scenario characterized by ultra-high reliability, ultra-low latency, and ultra-high availability (e.g., vehicle-to-everything (V2X), emergency services, and remote control); and mMTC is a next-generation mobile communication scenario characterized by low cost, low energy, short packet size, and massive connectivity (e.g., Internet of Things (IoT)). Summary of the Invention

[0004] Technical issues

[0005] The purpose of this disclosure is to provide a method and apparatus for transmitting and receiving a physical uplink shared channel during channel occupancy time.

[0006] Those skilled in the art will recognize that the purposes achievable with this disclosure are not limited to those specifically described above, and that the above and other purposes achievable with this disclosure will become clearer from the following detailed description.

[0007] Technical solution

[0008] According to one aspect of this disclosure, a method is provided for a user equipment (UE) to transmit a Physical Uplink Shared Channel (PUSCH) in a wireless communication system, comprising: receiving a first energy detection (ED) threshold for channel occupancy time (COT) sharing via a higher layer; obtaining one of the first ED threshold and a second ED threshold determined by the UE based on maximum uplink (UL) power, depending on whether COT sharing is available; and transmitting the PUSCH based on an ED threshold, wherein the first ED threshold is based on the availability of COT sharing, and wherein the second ED threshold is based on the unavailability of COT sharing.

[0009] Information regarding the availability of COT sharing can be included in the configured permitted uplink control information (CG-UCI).

[0010] The method may further include: performing Listen-Before-Speak (LBT) based on an ED threshold, and sending a PUSCH based on the result of performing the LBT.

[0011] The UE can determine whether COT sharing is available, and the UE can select one ED threshold from the first ED threshold and the second ED threshold based on whether COT sharing is available as determined by the UE.

[0012] PUSCH can be a configured licensed PUSCH (CG-PUSCH).

[0013] In another aspect of this disclosure, an apparatus for transmitting a Physical Uplink Shared Channel (PUSCH) in a wireless communication system is provided, comprising at least one processor; and at least one memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform an operation. The operation may include: receiving a first Energy Detection (ED) threshold for Channel Occupancy Time (COT) sharing via a higher layer; acquiring one of the first ED threshold and a second ED threshold determined by a UE based on maximum uplink (UL) power, based on whether COT sharing is available; and transmitting the PUSCH based on the first ED threshold, wherein the first ED threshold is available based on COT sharing, and wherein the second ED threshold is available based on COT sharing unavailable.

[0014] Information regarding the availability of COT sharing can be included in the configured permitted uplink control information (CG-UCI).

[0015] The operation may further include: performing Listen-Before-Speak (LBT) based on an ED threshold, and sending a PUSCH based on the result of performing the LBT.

[0016] The UE can determine whether COT sharing is available, and the UE can select one ED threshold from the first ED threshold and the second ED threshold based on whether COT sharing is available as determined by the UE.

[0017] PUSCH can be a configured licensed PUSCH (CG-PUSCH).

[0018] In another aspect of this disclosure, a computer-readable storage medium is provided, including at least one computer program that causes at least one processor to perform operations. The operations may include: receiving from a higher layer a first energy detection (ED) threshold for channel occupancy time (COT) sharing; acquiring one of the first ED threshold and a second ED threshold determined by the UE based on maximum uplink (UL) power, based on whether COT sharing is available; and transmitting a PUSCH based on an ED threshold, wherein the ED threshold is the first ED threshold based on the availability of COT sharing, and wherein the ED threshold is the second ED threshold based on the unavailability of COT sharing.

[0019] In another aspect of this disclosure, a user equipment (UE) is provided for transmitting a Physical Uplink Shared Channel (PUSCH) in a wireless communication system, comprising at least one transceiver; at least one processor; and at least one memory operatively connected to and configured to store instructions that, when executed, cause the at least one processor to perform an operation. The operation may include: receiving, via the at least one transceiver, a first energy detection (ED) threshold for Channel Occupancy Time (COT) sharing via a higher layer; obtaining one of the first ED threshold and a second ED threshold determined by the UE based on maximum uplink (UL) power, based on whether COT sharing is available; and transmitting the PUSCH via the at least one transceiver based on the one ED threshold, wherein, based on the availability of COT sharing, the one ED threshold is the first ED threshold, and wherein, based on the unavailability of COT sharing, the one ED threshold is the second ED threshold.

[0020] In another aspect of this disclosure, a method is provided for a base station (BS) to receive a Physical Uplink Shared Channel (PUSCH) in a wireless communication system, comprising: transmitting information related to a maximum uplink (UL) power to a user equipment (UE) via a higher layer; transmitting a first energy detection (ED) threshold to the UE via a higher layer; and receiving the PUSCH and configured Granted Uplink Control Information (CG-UCI); wherein based on the CG-UCI including information notifying the COT that sharing is available, the BS identifies that the UE has transmitted the PUSCH based on the first ED threshold; and wherein based on the CG-UCI including information notifying the COT that sharing is unavailable, the BS identifies that the UE has transmitted the PUSCH based on a second ED threshold determined by the UE based on the maximum UL power.

[0021] In another aspect of this disclosure, a base station (BS) is provided for receiving a Physical Uplink Shared Channel (PUSCH) in a wireless communication system, comprising at least one transceiver; at least one processor; and at least one memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations. These operations may include: transmitting higher-layer signaling, including information relating to a maximum uplink (UL) power, to a user equipment (UE) via the at least one transceiver; transmitting higher-layer signaling, including a first energy detection (ED) threshold, to the UE via the at least one transceiver; and receiving the PUSCH and configured Granted Uplink Control Information (CG-UCI) via the at least one transceiver; wherein, based on the CG-UCI including information notifying the COT that sharing is available, the BS identifies that the UE has transmitted the PUSCH based on the first ED threshold; and wherein, based on the CG-UCI including information notifying the COT that sharing is unavailable, the BS identifies that the UE has transmitted the PUSCH based on a second ED threshold determined by the UE based on the maximum UL power.

[0022] Beneficial effects

[0023] According to the present invention, the UE can determine whether COT sharing is allowed, and select an appropriate energy detection threshold based on whether COT sharing is allowed, thereby appropriately increasing the UE's channel access opportunities.

[0024] Those skilled in the art will recognize that the effects that can be achieved using this disclosure are not limited to those specifically described above, and that other advantages of this disclosure will become clearer from the following detailed description taken in conjunction with the accompanying drawings. Attached Figure Description

[0025] Figure 1 The diagram illustrates an exemplary communication system applied to this disclosure;

[0026] Figure 2 The illustrations are applicable to exemplary wireless devices of this disclosure;

[0027] Figure 3 The illustration applies to another exemplary wireless device of this disclosure; and

[0028] Figure 4 The illustrations are applicable to exemplary vehicles or autonomous vehicles disclosed herein.

[0029] Figure 5 and 6 This is a diagram illustrating the composition of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block and the method of transmitting an SS / PBCH block.

[0030] Figure 7This is a diagram illustrating an example of a random access procedure.

[0031] Figure 8 An exemplary mapping of physical channels in a time slot is illustrated;

[0032] Figure 9 The illustration shows an exemplary uplink (UL) transmission operation of a user equipment (UE);

[0033] Figure 10 The illustration shows an example of repeated transmission based on configured permissions;

[0034] Figure 11 The diagram illustrates support for unlicensed wireless communication systems.

[0035] Figure 12 The illustration shows an exemplary method of consuming resources in an unauthorized band;

[0036] Figure 13 The illustration shows an exemplary channel access procedure for a UE used for UL signal transmission and / or DL ​​signal transmission in an unauthorized band applicable to this disclosure;

[0037] Figure 14 The diagram illustrates the structure of a radio frame;

[0038] Figure 15 The diagram illustrates the resource grid during the duration of a time slot;

[0039] Figure 16 The diagram illustrates a physical channel in a 3GPP (Third Generation Partnership Project) system, serving as an example of a wireless communication system, and a general signal transmission method using the physical channel; and

[0040] Figures 17 to 22 This is a diagram illustrating a UL channel transmission and reception method according to an embodiment of the present disclosure. Detailed Implementation

[0041] The various descriptions, functions, processes, proposals, methods and / or operation flowcharts of this disclosure described herein can be applied to, but are not limited to, various fields requiring wireless communication / connectivity between devices (e.g., 5G).

[0042] More specific examples will now be described with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise stated, similar reference numerals denote the same or corresponding hardware blocks, software blocks, or functional blocks.

[0043] Figure 1 The diagram illustrates a communication system 1 applied to this disclosure.

[0044] refer to Figure 1The communication system 1 applied to this disclosure includes wireless devices, a network (BS), and a network. Wireless devices are devices that perform communication using radio access technology (RAT) (e.g., 5G NR (or new RAT) or LTE), also referred to as communication / radio / 5G devices. Wireless devices may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, IoT devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle (V2V) communication. Here, vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and can be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions (TVs), smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices can include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances can include televisions, refrigerators, washing machines, and so on. IoT devices can include sensors, smart meters, and so on. For example, the BS and network can be implemented as wireless devices, and a specific wireless device 200a can be used as a BS / network node for other wireless devices.

[0045] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can be connected to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can perform direct communication with each other without the intervention of the BS / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., V2V / Vehicle-to-Everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0046] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f / BS 200 and between BS 200. These wireless communication / connections can be established via various RATs (e.g., 5G NR) such as UL / DL communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication 150c (e.g., relay or integrated access backhaul (IAB)). Wireless signals can be transmitted and received between wireless devices, between wireless devices and BSs, and between BSs via wireless communication / connections 150a, 150b, and 150c. For example, signals can be transmitted and received on various physical channels via wireless communication / connections 150a, 150b, and 150c. For this purpose, at least a portion of the various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for transmitting / receiving wireless signals can be performed based on various suggestions of this disclosure.

[0047] The following technologies can be used in various wireless access systems, such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and so on. CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate Evolution (EDGE) for GSM. OFDMA can be implemented as radio technologies such as IEEE 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Global Microwave Access Interoperability (WiMAX)), IEEE 802.20, Evolved UTRA (E-UTRA), and so on. UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS using E-UTRA (E-UMTS), and LTE Advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP New Radio or New Radio Access Technology (NR) is an evolution of 3GPP LTE / LTE-A.

[0048] With an increasing number of communication devices requiring greater communication capacity, there has been a demand for enhanced mobile broadband communications compared to traditional radio access technologies (RATs). Massive machine-type communications (MTC) that provides various services to multiple interconnected devices and things anytime, anywhere is one of the key challenges to be addressed in next-generation communications. Communication system designs that consider services sensitive to reliability and latency are also being discussed. Thus, the introduction of next-generation radio access technologies (RATs) for enhanced mobile broadband communications (eMBB), massive MTC (mMTC), and ultra-reliable and low-latency communications (URLLC) is being discussed. For convenience, this technology will be referred to as NR or New RAT in this disclosure.

[0049] Although the following description is given in the context of 3GPP communication systems (e.g., NR) for clarity, the technical spirit of this disclosure is not limited to 3GPP communication systems. For background techniques, terms and abbreviations used in this disclosure, please refer to the technical specifications published prior to this disclosure (e.g., 38.211, 38.212, 38.213, 38.214, 38.300, 38.331, etc.).

[0050] In a radio access system, a user equipment (UE) receives information from a base station (BS) on the DL (Local Level) and transmits information to the BS on the UL (Low- ...

[0051] Figure 2 The illustrations are applicable to wireless devices disclosed herein.

[0052] refer to Figure 2 The first wireless device 100 and the second wireless device 200 can transmit wireless signals via various RATs (e.g., LTE and NR). {First wireless device 100 and second wireless device 200} can correspond to... Figure 1 {Wireless Device 100x and BS 200} and / or {Wireless Device 100x and Wireless Device 100x}.

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

[0054] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or transceivers 206, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processors 202 may process information in the memories 204 to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers 206. The processors 202 may receive wireless signals including fourth information / signals via the transceivers 206, and then store the information obtained by processing the fourth information / signals in the memories 204. The memories 204 may be connected to the processors 202 and store various information related to the operation of the processors 202. For example, memory 204 may store software code including instructions for performing some or all of the processes controlled by processor 202 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive wireless signals via one or more antennas 208. Each of transceivers 206 may include a transmitter and / or a receiver. Transceivers 206 may be used interchangeably with RF units. In this disclosure, the wireless device may be a communication modem / circuit / chip.

[0055] The hardware components of wireless devices 100 and 200 will now be described in more detail. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as Physical (PHY), Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), RRC, and Service Data Adaptation Protocol (SDAP)). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information and provide such messages, control information, data, or information to one or more transceivers 106 and 206 according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

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

[0057] Specifically, when DG-PUSCH is continuously scheduled without gaps with the time axis resources of the CG configured for the UE, and when the LBT subband of DG-PUSCH is equal to the LBT subband of CG-PUSCH or a subset of the LBT subband of CG-PUSCH, while the UE is transmitting CG-PUSCH in NR-U based on Cat-4 LBT, the processor 102 according to an embodiment of the present disclosure can control the UE to continue transmitting DG-PUSCH after transmitting CG-PUSCH without LBT.

[0058] When there is a gap between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH on the time axis, or when the LBT subband resources of CG-PUSCH that have been transmitted on the frequency axis are different from the LBT subband resources of the scheduled DG-PUSCH (i.e., the LBT subband of DG-PUSCH is not included in the LBT subband of CG-PUSCH), the processor 102 can control the UE to immediately discard specific X symbols, Y CG-PUSCHs, or Z time slots before DG-PUSCH, so as to ensure the LBT gap before transmitting DG-PUSCH.

[0059] The processor 102 can control the UE to select one of a second ED threshold calculated based on the maximum UL power configured by the BS and a first ED threshold configured by the BS for UL to DL COT sharing, based on whether DL transmission other than PDCCH transmission of up to 2 symbols is allowed within the COT shared with the BS, and perform ULLBT and UL transmissions based on the selected ED threshold.

[0060] In this scenario, the processor 102 can control the UE to notify the BS whether DL transmissions other than PDCCH transmissions of up to 2 symbols are permitted within the COT shared with the BS during COT sharing by sending information in the CG-UCI regarding which ED threshold (or UL power based on the selected threshold) has been used to perform LBT and UL transmissions.

[0061] As another embodiment, the processor 202 according to embodiments of this disclosure can be controlled to receive CG-PUSCH transmitted from the UE based on Cat-4 LBT in NR-U, continuously schedule DG-PUSCH without gaps in the timeline resources for configuring CG for the UE, and configure LBT subbands for DG-PUSCH, which are equal to or a subset of the LBT subbands of CG-PUSCH. In this case, the processor 202 can control the UE to continue receiving DG-PUSCH after transmitting CG-PUSCH without LBT.

[0062] Processor 202 can configure CG-PUSCH and DG-PUSCH such that there is a gap between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH on the time axis, or that the LBT subband resources of CG-PUSCH that has been transmitted and the LBT subband resources of the scheduled DG-PUSCH are different on the frequency axis. In this case, in order to ensure the LBT gap before the UE transmits DG-PUSCH, processor 202 can control the reception of CG-PUSCH except for a specific X symbols, Y CG-PUSCH, or Z time slots immediately following DG-PUSCH.

[0063] Processor 202 can control the maximum UL power required to configure a first ED threshold for COT sharing for the UE and to calculate a second ED threshold for cases where the COT is not shared. When the UE selects one of the second ED threshold calculated based on the maximum UL power configured by the BS and the first ED threshold configured by the BS for UL-to-DL COT sharing and performs UL LBT and UL transmissions based on the selected ED threshold, processor 202 can control the reception of UL transmissions, depending on whether DL transmissions other than PDCCH transmissions of up to 2 symbols are allowed within the COT shared with the BS.

[0064] Processor 202 can control which ED threshold (or UL power based on the selected threshold) has been used to perform LBT and UL transmissions, receiving information via CG-UCI regarding the first ED threshold and the second ED threshold. Processor 202 can identify, based on CG-UCI, whether DL transmissions other than PDCCH transmissions of up to 2 symbols are permitted within the COT shared with the UE.

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

[0066] One or more transceivers 106 and 206 can transmit user data, control information, and / or wireless signals / channels as mentioned in the methods and / or operation flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information, and / or wireless signals / channels mentioned in the description, as well as the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document, from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and transmit and receive wireless signals. For example, one or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or wireless signals to one or more other devices. One or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or wireless signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, and suggestions disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102 and 202 of the received user data, control information, and radio signals / channels. One or more transceivers 106 and 206 may convert user data, control information, and radio signals / channels processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0067] Figure 3 The illustration shows another example of a wireless device applied to this disclosure. Wireless devices can be implemented in various forms depending on the use case / service (see reference). Figure 1 ).

[0068] refer to Figure 3 Wireless devices 100 and 200 can correspond to Figure 1The wireless devices 100 and 200 can be configured to include various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit 110 may include a communication circuit 112 and one or more transceivers 114. For example, the communication circuit 112 may include... Figure 2 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, one or more transceivers 114 may include Figure 2 One or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory unit 130, and add-on components 140, and provides overall control for the wireless device. For example, control unit 120 can control the electrical / mechanical operation of the wireless device based on programs / code / instructions / information stored in memory unit 130. Control unit 120 can transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface in memory unit 130.

[0069] The add-on component 140 can be configured in various ways depending on the type of wireless device. For example, the add-on component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device is capable of operating in, but is not limited to, robotic applications. Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR equipment ( Figure 1 100c), handheld devices ( Figure 1 100d), home appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcasting terminals, hologram devices, public safety equipment, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices ( Figure 1 400), BS ( Figure 1 It can be implemented in the form of 200, network nodes, etc.

[0070] exist Figure 3In wireless devices 100 and 200, all various elements, components, units / parts, and / or modules can be connected to each other via wired interfaces, or at least a portion thereof can be wirelessly connected to each other via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 can be wiredly connected, and control unit 120 and first units (e.g., 130 and 140) can be wirelessly connected via communication unit 110. Each element, component, unit / part, and / or module in wireless device 100 may further include one or more elements. For example, control unit 120 may be configured with a collection of one or more processors. For example, control unit 120 may be configured with a collection of one or more processors. For example, control unit 120 may be configured as a collection of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. In another example, storage unit 130 may be configured with RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0071] Figure 4 The illustrations apply to vehicles or autonomous vehicles as described in this disclosure. Vehicles or autonomous vehicles can be implemented as mobile robots, automobiles, trains, manned / unmanned aerial vehicles (AVs), ships, etc.

[0072] refer to Figure 4 The vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to... Figure 3 The frame size is 110 / 130 / 140.

[0073] Communication unit 110 can send signals (e.g., data and control signals) to and receive signals from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. Control unit 120 can perform various operations by controlling the components of the vehicle or autonomous vehicle 100. Control unit 120 may include an ECU. Drive unit 140a enables the vehicle or autonomous vehicle 100 to drive on a road. Drive unit 140a may include an engine, electric motor, powertrain, wheels, brakes, steering mechanism, etc. Power supply unit 140b can supply power to the vehicle or autonomous vehicle 100 and may include wired / wireless charging circuitry, battery, etc. Sensor unit 140c can acquire information about vehicle status, surrounding environment, user information, etc. Sensor unit 140c may include inertial measurement unit (IMU) sensors, collision sensors, wheel sensors, speed sensors, slope sensors, weight sensors, heading sensors, position modules, vehicle forward / reverse sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, humidity sensors, ultrasonic sensors, illuminance sensors, pedal position sensors, etc. Autonomous driving unit 140d may implement technologies for maintaining the vehicle within its lane, technologies for automatically adjusting speed such as adaptive cruise control, technologies for autonomous driving along a defined path, and technologies for automatically setting a route if a destination is set, etc.

[0074] For example, communication unit 110 can receive map data, traffic information data, etc., from an external server. Autonomous driving unit 140d can generate autonomous driving routes and driving plans from the acquired data. Control unit 120 can control drive unit 140a, enabling the vehicle or autonomous vehicle 100 to move along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, communication unit 110 can periodically / irregularly acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from nearby vehicles. During autonomous driving, sensor unit 140c can acquire information about vehicle status and / or surrounding environment. Autonomous driving unit 140d can update the autonomous driving route and driving plan based on newly acquired data / information. Communication unit 110 can transmit information about vehicle location, autonomous driving route, and / or driving plan to an external server. The external server can predict traffic information data using AI technology, etc., based on information collected from the vehicle or autonomous vehicle, and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0075] Meanwhile, the use of ultra-high frequency bands, i.e., millimeter-band frequencies of 6 GHz or higher, is being considered in NR systems to transmit data over a wide bandwidth while maintaining high transmission rates for multiple users. 3GPP refers to this system as NR. In this disclosure, the system will also be referred to as an NR system.

[0076] NR systems use OFDM or similar transmission schemes. NR systems may follow OFDM parameters different from those of LTE systems. Alternatively, NR systems may follow the parameter set of traditional LTE / LTE-A but support a wider system bandwidth (e.g., 100MHz). Alternatively, a single cell may support multiple parameter sets. That is, UEs operating with different parameter sets can coexist in a single cell.

[0077] Figure 5 The diagram illustrates the SSB structure. The UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurements, etc., based on the SSB. The term SSB is interchangeable with the Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block.

[0078] refer to Figure 5 The SSB consists of the PSS, SSS, and PBCH. The SSB comprises four consecutive OFDM symbols. The PSS, PBCH, SSS / PBCH, and PBCH are transmitted on their respective OFDM symbols. Each of the PSS and SSS comprises one OFDM symbol and 127 subcarriers, and the PBCH comprises three OFDM symbols and 576 subcarriers. Polar coding and Quadrature Phase Shift Keying (QPSK) are applied to the PBCH. The PBCH comprises data REs and demodulation reference signals (DMRS) REs in each OFDM symbol. There are three DMRS REs per RB, with three data REs between every two adjacent DMRS REs.

[0079] Cell search refers to the process by which a UE obtains time / frequency synchronization of a cell and detects the cell ID (e.g., Physical Layer Cell ID (PCID)). The PSS can be used within the cell ID detection group, and the SSS can be used within the cell ID detection group. The PBCH can be used in the detection of the SSB (Time) index and half-frame.

[0080] The UE's cell search process can be summarized in Table 1 below.

[0081] [Table 1]

[0082]

[0083] There are 336 cell ID groups. Each cell ID group contains three cell IDs. There are a total of 1008 cell IDs. Information about the cell ID group to which a cell ID belongs can be obtained / retrieved via the cell's SSS (Single Segment Service), and information about the cell IDs within the 336 cells can be obtained / retrieved via PSS (Personal Segment Service).

[0084] Figure 6 The diagram illustrates SSB transmission. (Reference) Figure 6 The SSB (Secondary Sub-Slot) is transmitted periodically according to the SSB periodicity. The basic SSB periodicity assumed by the UE during initial cell search is defined as 20ms. After cell access, the network (e.g., the BS) can set the SSB periodicity to one of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}. An SSB burst set can be configured at the beginning of the SSB period. The SSB burst set can be configured with a 5ms time window (i.e., half a frame), and the SSB can be repeated up to L times within the burst set. The maximum number of SSB transmissions L can be given according to the carrier's frequency band as follows. One time slot includes up to two SSBs.

[0085] -For the frequency range up to 3GHz, L = 4

[0086] -For the frequency range from 3GHz to 6GHz, L = 8

[0087] - For the frequency range from 6 GHz to 52.6 GHz, L = 64

[0088] The temporal position of an SSB candidate within an SS burst set can be defined according to the SCS as follows. The temporal position of an SSB candidate is indexed sequentially from 0 to L-1 within the SSB burst set (i.e., half-frame) (SSB index).

[0089] - Case A-15kHz SCS: The index of the first symbol of the candidate SSB is given as {2,8}+14*n, where n=0,1 for carrier frequencies equal to or below 3GHz, and n=0,1,2,3 for carrier frequencies from 3GHz to 6GHz.

[0090] -Case B-30kHz SCS: The index of the first symbol of the candidate SSB is given as {4,8,16,20}+28*n, where n=0 for carrier frequencies below or equal to 3GHz, and n=0,1 for carrier frequencies between 3GHz and 6GHz.

[0091] - Case C-30kHz SCS: The index of the first symbol of the candidate SSB is given as {2,8}+14*n, where n=0 for carrier frequencies equal to or below 3GHz, and n=0,1,2,3 for carrier frequencies from 3GHz to 6GHz.

[0092] - Case D-120kHz SCS: The index of the first symbol of the candidate SSB is given as {4,8,16,20}+28*n, where for carrier frequencies above 6GHz, n=0,1,2,3,5,6,7,8,10,11,12,13,15,16,17,18.

[0093] - Case E-240kHz SCS: The index of the first symbol of the candidate SSB is given as {8,12,16,20,32,36,40,44}+56*n, where n = 0,1,2,3,5,6,7,8 for carrier frequencies above 6GHz.

[0094] The UE's random access procedure can be summarized as shown in Table 2 and Figure 10 As shown in the image.

[0095] [Table 2]

[0096]

[0097]

[0098] Random access procedures are used for various purposes. For example, they can be used for initial network access, handover, and UE-triggered UL data transmission. UEs can use random access procedures to acquire UL synchronization and UL transmission resources. Random access procedures are classified into contention-based and contention-free random access procedures. Figure 7 This is a diagram illustrating an example of a random access procedure. Specifically, Figure 7 The diagram illustrates a contention-based random access process.

[0099] First, the UE can send the random access preamble as Msg1 of the random access procedure on the PRACH at the UL.

[0100] It supports random access preamble sequences with two different lengths. The long sequence length of 839 is used for subcarrier spacings of 1.25 kHz and 5 kHz, and the short sequence length of 139 is used for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz.

[0101] Multiple preamble formats are defined by one or more RACH OFDM symbols and different cyclic prefixes (and / or guard times). The RACH configuration for the cell is included in the cell's system information and provided to the UE. The RACH configuration includes information about the subcarrier spacing of the PRACH, available preambles, and preamble formats. The RACH configuration includes information about the association between SSBs and RACH (time-frequency) resources. The UE transmits the random access preamble on the RACH time-frequency resources associated with the detected or selected SSB.

[0102] The SSB threshold used for RACH resource association can be set by the network, and RACH preamble transmission and retransmission are performed based on the SSB, where the reference signal received power (RSRP) measured based on the SSB meets the threshold. For example, the UE can select one of the SSBs that meets the threshold and transmit or retransmit the RACH preamble based on the RACH resource associated with the selected SSB.

[0103] When the BS receives a random access preamble from the UE, the BS sends a random access response (RAR) message (Msg2) to the UE. The PDCCH used to schedule the PDSCH carrying the RAR is sent after CRC masking with the Random Access (RA) Radio Network Temporary Identifier (RNTI) (RA-RNTI). Upon detecting a PDCCH masked with RA-RNTI, the UE can receive the RAR from the DCI-scheduled PDSCH carried by the PDCCH. The UE checks whether the RAR information of the preamble sent by the UE, i.e., Msg1, is in the RAR. The presence of random access information for Msg1 sent by the UE can be determined based on the existence of the RA preamble ID of the preamble sent by the UE. When there is no response to Msg1, the UE can retransmit the RACH preamble within a predetermined number of times while performing power ramping. The UE calculates the PRACH transmission power used for retransmitting the preamble based on the most recent path loss and the power ramp counter.

[0104] When the UE receives the expected RAR information on the PDSCH, it can identify timing advance information for UL synchronization, initial UL authorization, and UE temporary cell RNTI (cell RNTI (C-RNTI)). The timing advance information is used to control uplink signal transmission timing. To better align the UE's PUSCH / PUCCH transmission with the subframe timing at the network side, the network (e.g., BS) can measure the time difference between PUSCH / PUCCH / SRS reception and the subframe and send timing advance information based on the measured difference. The UE can perform UL transmission as Msg3 on the uplink shared channel during random access based on the RAR information. Msg3 may include an RRC connection request and the UE identifier. In response to Msg3, the network can send Msg4, which can be considered a contention resolution message on the DL. By receiving Msg4, the UE can enter RRC connection mode.

[0105] When a UE performs a handover to another cell or BS, or when the procedure is requested by a command from the BS, a contention-free random access procedure can be used. The basic procedure of a contention-free random access procedure is similar to that of a contention-based random access procedure. However, unlike a contention-based random access procedure, in a contention-free random access procedure, the preamble (hereinafter referred to as the dedicated RA preamble) to be used by the UE is assigned to the UE by the BS, whereby the UE randomly selects the preamble to use from among several RA preambles. Information about the dedicated RA preamble can be included in an RRC message (e.g., a handover command) or provided to the UE via a PDCCH command. When initiating an RA procedure, the UE sends the dedicated RA preamble to the BS. The RA procedure is completed when the UE receives the RA procedure from the BS.

[0106] As mentioned above, the UL license in the RAR schedules PUSCH transmissions for the UE. The PUSCH carrying the initial UL transmission via the UL license in the RAR is also called the Msg3 PUSCH. The contents of the RAR UL license begin at the MSB and end at the LSB, and are given in Table 3.

[0107] [Table 3]

[0108] RAR UL License Field Number of bits Frequency hopping flag 1 Msg3 PUSCH Frequency Resource Allocation 12 Msg3 PUSCH Time Resource Allocation 4 Modulation and compilation scheme (MCS) 4 Transmit power control (TPC) for Msg3 PUSCH 3 CSI Request 1

[0109] The TPC command is used to determine the transmit power of Msg3 PUSCH and is interpreted according to, for example, Table 4.

[0110] [Table 4]

[0111] TPC command Value [dB] 0 -6 1 -4 2 -2 3 0 4 2 5 4 6 6 7 8

[0112] During contention-free random access, the CSI request field in the RAR UL license indicates whether the UE will include aperiodic CSI reports in PUSCH transmissions. The subcarrier spacing for Msg3 PUSCH transmissions is provided by the RRC parameters. The UE will transmit PRACH and Msg3 PUSCH on the same uplink carrier in the same serving cell. The ULBWP for Msg3 PUSCH transmissions is indicated by System Information Block 1 (SIB1). Figure 8 The diagram illustrates an exemplary mapping of physical channels within a time slot.

[0113] The DL control channel, DL or UL data, and UL control channel can all be included in a single timeslot. For example, the first N symbols in a timeslot (hereinafter referred to as the DL control area) can be used to transmit the DL control channel, and the last M symbols in the timeslot (hereinafter referred to as the UL control area) can be used to transmit the UL control channel. N and M are integers equal to or greater than 0. The resource area between the DL control area and the UL control area (hereinafter referred to as the data area) can be used for DL ​​data transmission or UL data transmission. Time slots for DL-to-UL or UL-to-DL handover can be defined between the control area and the data area. PDCCH can be transmitted in the DL control area, and PDSCH can be transmitted in the DL data area. Some symbols in a timeslot during the handover from DL to UL can be configured as time slots.

[0114] Now, a detailed description of the physical channel will be given.

[0115] The PDSCH delivers DL data (e.g., downlink shared channel (DL-SCH) transport blocks (TBs)) and employs modulation schemes such as Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, or 256-QAM. TBs are encoded as codewords. The PDSCH can deliver up to two codewords. Each codeword undergoes scrambling and modulation mapping individually, and modulation symbols from each codeword are mapped to one or more layers. OFDM signals are generated by mapping each layer along with DMRS to resources and are transmitted through the corresponding antenna ports.

[0116] The PDCCH delivers the DCI. For example, the PDCCH (i.e., the DCI) may carry information about the transmission format and resource allocation of the DL-SCH, resource allocation information for the Uplink Shared Channel (UL-SCH), paging information for the PCH, system information for the DL-SCH, resource allocation information for higher-layer control messages such as RARs transmitted on the PDCCH, transmit power control commands, information about the activation / release of configured schedules, etc. The DCI includes Cyclic Redundancy Check (CRC). Depending on the owner or purpose of the PDCCH, the CRC is masked using various identifiers (IDs) (e.g., Radio Network Temporary Identifier (RNTI)). For example, if the PDCCH is for a specific UE, the CRC is masked by the UE ID (e.g., Cell RNTI (C-RNTI)). If the PDCCH is used for paging messages, the CRC is masked by the Paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., System Information Block (SIB)), the CRC is masked by the System Information RNTI (SI-RNTI). When PDCCH is used for RAR, CRC is masked by Random Access RNTI (RA-RNTI).

[0117] PDCCH uses a fixed modulation scheme (e.g., QPSK). A PDCCH consists of 1, 2, 4, 8, or 16 control channel elements (CCEs) depending on its aggregation level (AL). A CCE consists of 6 resource element groups (REGs), each REG being defined by one OFDM symbol multiplied by one (P)RB.

[0118] The PDCCH is transmitted in a control resource set (CORESET). A CORESET corresponds to a set of physical resources / parameters used to deliver the PDCCH / DCI in the BWP. For example, a CORESET is defined as a set of REGs with a given set of parameters (e.g., SCS, CP length, etc.). A CORESET can be configured by system information (e.g., Master Information Block (MIB)) or UE-specific higher-layer signaling (e.g., RRC signaling). For example, the following parameters / information can be used to configure a CORESET, and multiple CORESETs may overlap with each other in the time / frequency domain.

[0119] -controlResourceSetId: Indicates the ID of CORESET.

[0120] -frequencyDomainResources: Indicates the frequency domain resources of CORESET. Frequency domain resources are indicated by a bitmap, and each bit of the bitmap corresponds to a group of RBs (i.e., six consecutive RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RB group of the BWP. The RB group corresponding to the bit set to 1 is allocated as the frequency domain resource of CORESET.

[0121] - Duration: Indicates the time zone resources of the CORESET. It indicates the number of consecutive OFDMA symbols in the CORESET. For example, the duration is set to one of 1 to 3.

[0122] -cce-REG-MappingType: Indicates the CCE to REG mapping type. Interleaved and non-interleaved types are supported.

[0123] -precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0124] -tci-StatesPDCCH: Provides information indicating the Transport Configuration Indication (TCI) status used for PDCCH (e.g., TCI-StateID). TCI states are used to provide quasi-co-address relationships between one or more DL RSs in the RS set (TCI states) and the PDCCHDMRS ports.

[0125] -tci-PresentInDCI: Indicates whether the TCI field is included in the DCI.

[0126] -pdcch-DMRS-ScramblingID: Provides information for initializing the PDCCH DMRS scrambling sequence.

[0127] To receive PDCCH, a UE can monitor (e.g., blindly decode) a set of PDCCH candidates in a CORESET. A PDCCH candidate is one or more CCEs monitored by the UE for PDCCH reception / detection. PDCCH monitoring can be performed in one or more CORESETs within an active DL BWP on each active cell configured with PDCCH monitoring. The set of PDCCH candidates monitored by the UE is defined as a PDCCH search space (SS) set. The SS set can be a common search space (CSS) set or a UE-specific search space (USS) set.

[0128] Table 5 lists exemplary PDCCH SS.

[0129] [Table 5]

[0130]

[0131] SS sets can be configured by system information (e.g., MIB) or UE-specific higher-layer (e.g., RRC) signaling. S or fewer SS sets can be configured in each DL BWP of the serving cell. For example, the following parameters / information can be provided for each SS set. Each SS set can be associated with one CORESET, and each CORESET configuration can be associated with one or more SS sets. -searchSpaceId: Indicates the ID of the SS set.

[0132] -controlResourceSetId: Indicates the CORESET associated with the SS collection.

[0133] -monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring periodicity (in slots) and PDCCH monitoring offset (in slots).

[0134] -monitoringSymbolsWithinSlot: Indicates one or more first OFDMA symbols used for PDCCH monitoring in a slot configured for PDCCH monitoring. OFDMA symbols are indicated by a bitmap, and each bit of the bitmap corresponds to one OFDMA symbol in the slot. The MSB of the bitmap corresponds to the first OFDMA symbol of the slot. One or more OFDMA symbols corresponding to one or more bits set to 1 correspond to one or more first symbols of the CORESET in that slot.

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

[0136] -searchSpaceType: Indicates whether the SS type is CSS or USS.

[0137] -DCI format: Indicates the DCI format of the PDCCH candidate.

[0138] The UE can monitor PDCCH candidates in one or more SS sets within a time slot based on the CORESET / SS set configuration. The timing when PDCCH candidates should be monitored (e.g., time / frequency resources) is defined as the PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings can be configured within a time slot.

[0139] Table 6 illustrates an exemplary DCI format transmitted on the PDCCH.

[0140] [Table 6]

[0141] DCI format use 0_0 PUSCH scheduling in a cell 0_1 PUSCH scheduling in a cell 1_0 PDSCH scheduling in a cell 1_1 PDSCH scheduling in a cell 2_0 Notify UE group of slot format 2_1 The UE group is notified of the PRB and OFDM symbols, whereby the UE can assume that no transmission is expected for the UE. 2_2 Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of a set of TPC commands via SRS of one or more UEs

[0142] DCI format 0_0 can be used to schedule PUSCH based on TB (or TB level), and DCI format 0_1 ​​can be used to schedule PUSCH based on TB (or TB level) or PUSCH based on Block Group (CBG) (or CBG level). DCI format 1_0 can be used to schedule PDSCH based on TB (or TB level), and DCI format 1_1 can be used to schedule PDSCH based on TB (or TB level) or PDSCH based on CBG (or CBG level) (DL-licensed DCI). DCI formats 0_0 / 0_1 can be referred to as UL-licensed DCI or UL scheduling information, and DCI formats 1_0 / 1_1 can be referred to as DL-licensed DCI or DL ​​scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., Dynamic Slot Format Indicator (SFI)) to the UE, and DCI format 2_1 is used to deliver DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be delivered to the corresponding UE group on the group common PDCCH, which is a PDCCH for the UE group. DCI format 0_0 and DCI format 1_0 can be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 can be referred to as non-fallback DCI formats. In fallback DCI formats, the DCI size / field configuration remains the same regardless of the UE configuration. Conversely, in non-fallback DCI formats, the DCI size / field configuration varies depending on the UE configuration.

[0143] PUCCH delivers uplink control information (UCI). UCI includes the following information.

[0144] -SR: Information used to request UL-SCH resources.

[0145] - HARQ-ACK: A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet has been successfully received. A 1-bit HARQ-ACK can be sent in response to a single codeword. A 2-bit HARQ-ACK can be sent in response to two codewords. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The terms HARQ-ACK, HARQ ACK / NACK, and ACK / NACK are used interchangeably.

[0146] -CSI: Feedback information used for the DL channel. Feedback information related to Multiple-Input Multiple-Output (MIMO) includes RI and PMI.

[0147] Table 7 illustrates exemplary PUCCH formats. Based on the PUCCH transmission duration, PUCCH formats can be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0148] [Table 7]

[0149]

[0150] PUCCH format 0 conveys a maximum of 2 bits of UCI and is mapped in a sequence-based manner for transmission. Specifically, the UE transmits a specific UCI to the BS by sending one of multiple sequences on the PUCCH of PUCCH format 0. The UE transmits the PUCCH of PUCCH format 0 in the PUCCH resources configured for the corresponding SR only when the UE sends an affirmative SR. PUCCH format 1 conveys a maximum of 2 bits of UCI and uses an orthogonal overlay code (OCC) in the time domain to extend the modulation symbols of the UCI (which are configured differently depending on whether frequency hopping is performed). DMRS is transmitted with symbols that do not transmit modulation symbols (i.e., in time division multiplexing (TDM)).

[0151] PUCCH format 2 transmits more than 2 bits of UCI, and the modulation symbols of DCI are transmitted in frequency division multiplexing (FDM) with DMRS. DMRS is located at a density of 1 / 3 in symbols #1, #4, #7, and #10 of a given RB. A pseudo-noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be activated for 2-symbol PUCCH format 2.

[0152] PUCCH format 3 does not support UE multiplexing within the same PRBS and transmits more than 2 bits of UCI. In other words, PUCCH resources for PUCCH format 3 do not include OCC. Modulation symbols are transmitted in TDM with DMRS.

[0153] PUCCH format 4 supports multiplexing of up to four UEs within the same PRBS and transmits more than two bits of UCI. In other words, PUCCH format 3's PUCCH resources include OCC. Modulation symbols are transmitted in TDM with DMRS.

[0154] PUSCH delivers UL data (e.g., UL Shared Channel Transport Block (UL-SCH TB)) and / or UCI based on CP-OFDM or DFT-s-OFDM waveforms. When PUSCH is transmitted in DFT-s-OFDM waveform, the UE transmits PUSCH via transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE can transmit PUSCH in CP-OFDM waveform, while when transform precoding is possible (e.g., enabled), the UE can transmit PUSCH in either CP-OFDM or DFT-s-OFDM waveform. PUSCH transmission can be dynamically scheduled by UL permission in DCI, or semi-statically scheduled by higher-layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling such as PDCCH) (configured scheduling or configured permission). PUSCH transmission can be performed in a codebook-based or non-codebook-based manner.

[0155] On the DL (Deep Allocation) layer, the BS can dynamically allocate resources for DL ​​transmission to the UE via one or more PDCCHs (including DCI format 1_0 or DCI format 1_1). Furthermore, the BS can indicate to a specific UE via one or more PDCCHs (including DCI format 2_1) that it has preempted some resources pre-scheduled for that UE for signal transmission to another UE. Additionally, in a semi-persistent scheduling (SPS) scheme, the BS can configure the DL assignment period via higher-layer signaling and signal the activation / deactivation of the DL assignment configured by the PDCCH to provide the UE with DL assignments for initial HARQ transmission. When retransmission is required for initial HARQ transmission, the BS explicitly schedules retransmission resources via the PDCCH. When DCI-based DL assignments conflict with SPS-based DL assignments, the UE can prioritize the DCI-based DL assignment.

[0156] Similar to DL, for UL, the BS can dynamically allocate resources for UL transmissions to the UE via one or more PDCCHs (including DCI format 0_0 or DCI format 0_1). Furthermore, the BS can allocate UL resources for initial HARQ transmissions to the UE based on a configuration grant (CG) method (similar to SPS). Although dynamic scheduling involves PDCCHs for PUSCH transmissions, configuration grant does not. However, UL resources for retransmissions are explicitly allocated by one or more PDCCHs. Thus, the operation of the BS pre-configuring UL resources without dynamic grant (DG) (e.g., UL grant via scheduling DCI) is called "CG". Two types of CG are defined.

[0157] - Type 1: UL licenses with a predetermined period are provided by higher-level signaling (without L1 signaling).

[0158] - Type 2: The UL licensing cycle is configured by higher-level signaling, and the activation / deactivation of the CG is signaled by the PDCCH to provide UL licensing.

[0159] Figure 9 The illustration shows an exemplary UL transmission operation of the UE. The UE can be based on DG ( Figure 9 (a) or based on CG ( Figure 9 (b) to send the expected packets.

[0160] Resources for CG can be shared among multiple UEs. CG-based UL signal transmissions from each UE can be identified via time / frequency resources and RS parameters (e.g., different cyclic shifts, etc.). Therefore, when a UE fails to transmit a UL signal due to signal collisions, the BS can identify the UE and explicitly send a retransmission permission for the corresponding TB to the UE.

[0161] The CG supports K repeated transmissions for the same TB, including the initial transmission. Based on the resources used for the initial transmission, the same HARQ process ID is determined for the K repeated UL signals. The redundant version (RV) of the K repeated TB has one of the patterns {0,2,3,1}, {0,3,0,3}, and {0,0,0,0}.

[0162] Figure 10 The illustration shows an example of repeating transmission based on CG.

[0163] The UE will perform repeated transmissions until one of the following conditions is met:

[0164] - Successfully received UL license for the same TB;

[0165] - The number of repetitions of TB reaches K; and

[0166] - (In option 2) The end time of period P is reached.

[0167] Similar to Licensed Assisted Access (LAA) in traditional 3GPP LTE systems, the use of unlicensed bands for cellular communications is also being considered in 3GPP NR systems. Unlike LAA, NR cells in the unlicensed band (hereinafter referred to as NR unlicensed cells (Ucells)) aim for independent (SA) operation. For example, PUCCH, PUSCH, and PRACH transmissions can be supported in NR Ucells.

[0168] In the NR systems to which the various embodiments of this disclosure apply, each component carrier (CC) can be allocated / supported up to 400 MHz. When a UE operating in such a wideband CC always operates with its radio frequency (RF) module powered on throughout the entire CC, the UE's battery consumption may increase.

[0169] Alternatively, considering various use cases operating within a single broadband CC (e.g., eMBB, URLLC, mMTC, etc.), different parameter sets (e.g., SCS) can be supported for each frequency band within the CC.

[0170] Alternatively, each UE can have a different maximum bandwidth capability.

[0171] In this regard, the BS can instruct the UE to operate only within a portion of the bandwidth of the broadband CC, rather than the entire bandwidth. This portion of the bandwidth can be defined as the bandwidth portion (BWP).

[0172] A BWP can be a subset of consecutive RBs on the frequency axis. A BWP can correspond to a set of parameters (e.g., SCS, CP length, slot / microslot duration, etc.).

[0173] A BS can configure multiple BWPs within a single CC configured for a UE. For example, a BS can configure a BWP occupying a relatively small frequency area within a PDCCH monitoring slot and schedule PDSCHs indicated (or scheduled) by the PDCCH within a larger BWP. Alternatively, when UEs are concentrated on a particular BWP, the BS can configure another BWP for some UEs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, the BS can exclude some spectrum from the total bandwidth and configure BWPs on both sides of the cell within the same time slot.

[0174] The BS can configure at least one DL / UL BWP for a UE associated with a broadband CC, activate at least one of the DL / UL BWPs configured at a specific point in time (via L1 signaling (e.g., DCI), MAC signaling, or RRC signaling), and instruct a switch to another configured DL / UL BWP (via L1 signaling, MAC signaling, or RRC signaling). Furthermore, the UE can switch to a predetermined DL / UL BWP when a timer value (e.g., a BWP inactivity timer value) expires. The activated DL / UL BWP can be referred to as the active DL / UL BWP. During initial access or before the RRC connection is established, the UE may not receive configuration for the DL / UL BWP from the BS. In this case, the DL / UL BWP assumed by the UE is defined as the initially active DL / UL BWP.

[0175] Figure 11 The illustrations support exemplary wireless communication systems applicable to the unauthorized bands of this disclosure.

[0176] In the following description, a cell operating in the licensed band (L-band) is defined as an L-cell, and the carrier of the L-cell is defined as (DL / UL)LCC. A cell operating in the unlicensed band (U-band) is defined as a U-cell, and the carrier of the U-cell is defined as (DL / UL)UCC. The carrier / carrier frequency of a cell can refer to the cell's operating frequency (e.g., center frequency). The cell / carrier (e.g., CC) is commonly referred to as the cell.

[0177] When the BS and UE transmit and receive signals on the LCC and UCC of carrier aggregation, such as Figure 11 As shown in (a), the LCC and UCC can be configured as the primary CC (PCC) and secondary CC (SCC), respectively. The BS and UE can transmit and receive signals on a single UCC or on multiple carrier-aggregated UCCs, such as... Figure 11 As shown in (b). In other words, the BS and UE can transmit and receive signals only on (one or more) UCCs without using any LCCs. For SA operation, PRACH, PUCCH, PUSCH, and SRS transmissions can be supported on the UCell.

[0178] Signal transmission and reception operations in the unauthorized band as described in this disclosure can be applied to the above deployment scenarios (unless otherwise stated).

[0179] Unless otherwise stated, the following definitions apply to the following terms used in this disclosure.

[0180] - Channel: A carrier or part of a carrier consisting of a continuous set of RBs, wherein the channel access procedure (CAP) is performed in a shared spectrum.

[0181] - Channel Access Procedure (CAP): The process of assessing channel availability based on sensing before signal transmission to determine whether (one or more) other communication nodes are using the channel. The basic sensing unit is a sensing slot with a duration of Tsl = 9 μs. The BS or UE senses the slot during its duration. The sensing slot duration Tsl is considered idle when the power detected is less than the energy detection threshold Xthresh for at least 4 μs within the sensing slot duration. Otherwise, the sensing slot duration Tsl is considered busy. CAP can also be called Listen Before Talk (LBT).

[0182] - Channel occupancy: Transmissions on one or more channels from the BS / UE after CAP.

[0183] - Channel Occupancy Time (COT): The total time that the BS / UE and any one or more BS / UEs sharing the channel occupancy perform one or more transmissions on the channel after CAP. Regarding COT determination, if the transmission gap is less than or equal to 25µs, the gap duration can be counted in the COT. COT can be shared for transmission between the BS and the corresponding UE.

[0184] -DL transmission burst: A collection of transmissions from the BS without any gaps longer than 16μs. Transmissions from the BS separated by gaps longer than 16μs are considered separate DL transmission bursts. The BS may perform transmission(s) after the gaps without sensing channel availability within the DL transmission burst.

[0185] - UL Transmission Burst: A collection of transmissions from the UE without any gaps greater than 16 μs. Transmissions from the UE separated by gaps greater than 16 μs are considered separate UL transmission bursts. The UE can perform transmission(s) after the gaps without sensing channel availability within the UL transmission burst.

[0186] - Discovery Burst: A DL transmission burst comprising a set of one or more signals and / or one or more channels that are confined within a window and associated with a duty cycle. A discovery burst may include one or more transmissions initiated by the BS, including PSS, SSS, and cell-specific RS (CRS), and further including non-zero power CSI-RS. In NR systems, a discovery burst may include one or more transmissions initiated by the BS, comprising at least an SS / PBCH block and further including a CORESET for scheduling a PDCCH carrying SIB1, a PDSCH carrying SIB1, and / or a non-zero power CSI-RS.

[0187] Figure 12 An exemplary method for occupying resources in an unauthorized band is illustrated.

[0188] refer to Figure 12A communication node (e.g., a BS or UE) operating in the unlicensed band must determine whether one or more other communication nodes are using the channel before signal transmission. For this purpose, a communication node in the unlicensed band can perform a Capture on a Channel (CAP) to access the channel(s) on which it intends to perform transmissions. CAP can be performed based on sensing. For example, a communication node can determine whether one or more other communication nodes are transmitting on the channel(s) before signal transmission via carrier sensing (CS). Determining that one or more other communication nodes are not transmitting is defined as a Confirmed Clear Channel Assessment (CCA). Where a CCA threshold (e.g., Xthresh) predefined or configured by higher-layer (e.g., RRC) signaling exists, a communication node can determine that the channel is busy when energy above the CCA threshold is detected in the channel. Otherwise, the communication node can determine that the channel is idle. When the channel is determined to be idle, the communication node can begin transmitting signals in the unlicensed band. CAP can be replaced by a Level-Based Transmission (LBT).

[0189] Table 8 describes the exemplary CAPs supported in NR-U.

[0190] [Table 8]

[0191]

[0192] In wireless communication systems that support unlicensed bands, a cell (or carrier (e.g., CC)) or BWP configured for a UE can be wideband with a larger bandwidth (BW) than conventional LTE. However, the BW may be limited by regulations based on the requirement of CCA for independent LBT operation. A subband (SB) that performs LBT independently is defined as an LBT-SB. Multiple LBT-SBs can then be included in a wideband cell / BWP. The set of RBs included in an LBT-SB can be configured via higher-layer (e.g., RRC) signaling. Thus, based on (i) the BW of the cell / BWP and (ii) the RB set allocation information, one or more LBT-SBs can be included in a cell / BWP. Multiple LBT-SBs can be included in the BWP of a cell (or carrier). An LBT-SB can be, for example, a 20-MHz band. An LBT-SB can include multiple consecutive (P)RBs in the frequency domain and can therefore be referred to as a (P)RB set.

[0193] In Europe, two LBT operations are defined: Frame-Based Device (FBE) and Load-Based Device (LBE). In FBE, a fixed frame consists of a channel occupancy time (e.g., 1 to 10 ms) and an idle period corresponding to at least 5% of the channel occupancy time. The channel occupancy time is the period during which the communication node can continue transmitting while the communication node has successfully accessed the channel, and CCA is defined as the operation of observing the channel during the CCA time slot (at least 20 μs) at the end of the idle period. The communication node performs CCA periodically on a fixed frame basis. When the channel is not occupied, the communication node transmits during the channel occupancy time, while when the channel is occupied, the communication node postpones transmission and waits until the CCA time slot in the next period.

[0194] In LBE, a communication node can set q ∈ {4, 5, ..., 32} and then perform CCA within a CCA time slot. When the channel is unoccupied in the first CCA time slot, the communication node can guarantee a time period of up to (13 / 32)q ms and transmit data during that time period. When the channel is occupied in the first CCA time slot, the communication node randomly selects N ∈ {1, 2, ..., q}, stores the selected value as the initial value, and then senses the channel state based on the CCA time slot. Each time the channel is unoccupied in a CCA time slot, the communication node decrements the stored counter value by 1. When the counter value reaches 0, the communication node can guarantee a time period of up to (13 / 32)q ms and transmit data.

[0195] In LTE / NR systems, eNBs or UEs should also perform LBT (Local Band Breakdown) for signal transmissions in the unlicensed band (referred to as the U-band for convenience). Additionally, when an eNB or UE in an LTE / NR system transmits signals, other communication nodes, such as Wi-Fi nodes, should also perform LBT to prevent the eNB or UE from causing transmission interference. For example, in the Wi-Fi standard (801.11ac), the CCA (Corrective Calibration) threshold is defined as -62dBm for non-Wi-Fi signals and -82dBm for Wi-Fi signals. For instance, when a station (STA) or access point (AP) receives a signal other than a Wi-Fi signal at -62dBm or higher, the STA or AP should not transmit other signals to avoid interference.

[0196] The UE performs Type 1 or Type 2 CAP for UL signal transmissions in the unlicensed band. Typically, the UE can perform CAP (e.g., Type 1 or Type 2) configured by the BS for UL signal transmissions. For example, CAP type indication information can be included in the UL license (e.g., DCI format 0_0 or DCI format 0_1) for scheduling PUSCH transmissions.

[0197] In Type 1 UL CAP, the length of the time span by which a sensing slot is sensed as idle prior to transmission(s) is random. Type 1 UL CAP can be applied to the following transmissions.

[0198] - PUSCH / SRS transmissions scheduled and / or configured by the BS (one or more).

[0199] - PUCCH transmissions scheduled and / or configured by the BS (one or more).

[0200] - One or more transmissions related to the Random Access Procedure (RAP)

[0201] Figure 13 The illustration shows a type 1 CAP among the CAPs applicable to UEs for UL signal transmission in unlicensed bands in this disclosure.

[0202] First, refer to Figure 13 Describes the transmission of UL signals in an unauthorized band.

[0203] UE can delay duration T d During the duration of the sensing time slot, the UE senses whether the channel is idle. After the counter N decrements to 0, the UE can perform a transmission (S1334). The counter N is adjusted by sensing the channel during the duration of one or more additional time slots according to the following procedure.

[0204] Step 1) Set N = Ninit, where Ninit is uniformly distributed between 0 and CW. P A random number between the given values ​​is generated, and then proceed to step 4 (S1320).

[0205] Step 2) If N>0 and the UE selects a decrementing counter, then set N=N-1 (S1340).

[0206] Step 3) Sensing the channel during the additional time slot duration, and if the additional time slot duration is idle (Y), proceed to step 4. Otherwise (N), proceed to step 5 (S1350).

[0207] Step 4) If N = 0 (Y) (S1330), then stop CAP (S1332). Otherwise (N), go to step 2.

[0208] Step 5) Sensing the channel until a busy sensing slot is detected within the additional delay duration Td or all slots of the additional delay duration Td are sensed as idle (S1360).

[0209] Step 6) If the channel is sensed to be idle (Y) for all time slot durations of the additional delay duration Td, proceed to step 4. Otherwise (N), proceed to step 5 (S1370).

[0210] Table 9 illustrates how the mp, minimum CW, maximum CW, maximum channel occupancy time (MCOT), and allowed CW size applied to CAP vary according to the channel access priority level.

[0211] [Table 9]

[0212]

[0213] The delay duration Td includes a duration Tf (16 μs) immediately followed by mp consecutive time slot durations, where each time slot duration Tsl is 9 μs, and Tf includes the sensing time slot duration Tsl at the beginning of the 16-µs duration. CWmin,p <= CWp <= CWmax,p. CWp is set to CWmin,p and can be updated (CW size update) prior to step 1 based on the explicit / implicit reception response to a previous UL burst (e.g., PUSCH). For example, CWp can be initialized to CWmin,p based on the explicit / implicit reception response to a previous UL burst, can be increased to the next higher allowable value, or can be maintained at the existing value.

[0214] In Type 2 UL CAP, the length of the time span by the sensing slots sensed as idle before transmission(s) is deterministic. Type 2 UL CAP is classified into Type 2A UL CAP, Type 2B UL CAP, and Type 2C UL CAP. In Type 2A UL CAP, the UE can transmit a signal immediately after the channel is sensed as idle for at least the sensing duration Tshort_dl (=25μs). Tshort_dl includes a duration Tf (=16μs) and an immediately following sensing slot duration. In Type 2A UL CAP, Tf includes the sensing slot at the beginning of the duration. In Type 2B UL CAP, the UE can transmit a signal immediately after the channel is sensed as idle for at least the sensing slot duration Tf (=16μs). In Type 2B UL CAP, Tf includes the sensing slot within the last 9μs of the duration. In Type 2C UL CAP, the UE does not sense the channel before transmission.

[0215] For a UE to transmit UL data in the unlicensed band, the BS must successfully send a UL grant in the unlicensed band during its LBT operation, and the UE must also successfully send UL data during its LBT operation. That is, the UE can only attempt UL data transmission if both the BS and the UE succeed in their LBT operations. Furthermore, because there is a delay of at least 4 milliseconds between the UL grant and the scheduled UL data in the LTE system, earlier access from another coexisting transport node in the unlicensed band during this period can delay the UE's scheduled UL data transmission. In this context, methods to improve the efficiency of UL data transmission in the unlicensed band are being discussed.

[0216] To support UL transmissions with relatively high reliability and relatively low latency, NR also supports CG Type 1 and CG Type 2, where the BS pre-configures time, frequency, and code resources for the UE via either higher-layer signaling (e.g., RRC signaling) or a combination of higher-layer signaling and L1 signaling (e.g., DCI). The UE can perform UL transmissions in resources configured with either Type 1 or Type 2 without receiving UL clearance from the BS. In Type 1, the periodicity of the CG, offset from SFN=0, time / frequency resource allocation, repetition count, DMRS parameters, MCS / TB size (TBS), power control parameters, etc., are configured solely by higher-layer signaling such as RRC signaling, without L1 signaling. Type 2 configures the periodicity and power control parameters of the CG via higher-layer signaling such as RRC signaling, and indicates a scheme for information regarding remaining resources (e.g., offset of initial transmission timing, time / frequency resource allocation, DMRS parameters, and MCS / TBS) by activating DCI as L1 signaling.

[0217] Now, refer to Figure 13 Describe the transmission of DL signals in the U-band.

[0218] BS can perform one of the following CAPs for DL ​​signal transmission in U-band.

[0219] (1) Type 1 DL CAP method

[0220] In Type 1DL CAP, the length of the duration spanned by the sensing slots that are sensed as idle prior to transmission(s) is random. Type 1DL CAP can be applied to the following transmissions.

[0221] - One or more transmissions initiated by the BS, including (i) a unicast PDSCH with user plane data, or (ii) a unicast PDSCH with user plane data and a unicast PDCCH scheduling user plane data; or

[0222] - One or more transmissions initiated by the BS, having (i) discovery bursts only, or (ii) discovery bursts multiplexed with non-unicast information.

[0223] refer to Figure 13 The BS can first sense whether the channel is idle during the sensing time slot duration of the delay duration Td. After the counter N is decremented to 0, transmission can be performed (S1334). The counter N is adjusted by sensing the channel during (one or more) additional time slot durations according to the following procedure.

[0224] Step 1) Set N = Ninit, where Ninit is a random number uniformly distributed between 0 and CWp, and proceed to step 4 (S1320).

[0225] Step 2) If N>0 and BS selects a decrementing counter, then set N=N-1 (S1340).

[0226] Step 3) Sensing the channel during the additional time slot duration, and if the additional time slot duration is idle (Y), proceed to step 4. Otherwise (N), proceed to step 5 (S1350).

[0227] Step 4) If N = 0 (Y) (S1330), then stop CAP (S1232). Otherwise (N), go to step 2.

[0228] Step 5) Sensing the channel until a busy sensing slot is detected within the additional delay duration Td or all slots of the additional delay duration Td are sensed as idle (S1360).

[0229] Step 6) If the channel is sensed to be idle (Y) for all time slot durations of the additional delay duration Td, proceed to step 4. Otherwise (N), proceed to step 5 (S1370).

[0230] Table 10 illustrates how the mp, minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW size applied to CAP vary according to the channel access priority level.

[0231] [Table 10]

[0232]

[0233] The delay duration Td includes the duration Tf (16 μs) which is followed by mp consecutive sensing time slot durations, where each sensing time slot duration Tsl is 9 μs, and Tf includes the sensing time slot duration Tsl at the beginning of the 16 μs duration.

[0234] CWmin,p <= CWp <= CWmax,p. CWp is set to CWmin,p and can be updated (CW size update) before step 1 based on the HARQ-ACK feedback (e.g., the ratio of ACK or NACK signals) used for the previous UL burst (e.g., PDSCH). For example, CWp can be initialized to CWmin,p based on the HARQ-ACK feedback used for the previous UL burst, CWp can be increased to the next maximum allowable value, or CWp can be maintained at its current value.

[0235] (2) Type 2DL CAP method

[0236] In Type 2 DL CAP, the length of the duration spanned by a time slot sensed as idle prior to transmission(s) is deterministic. Type 2 DL CAP is classified into Type 2A DL CAP, Type 2B DL ​​CAP, and Type 2C DL CAP.

[0237] Type 2A DL CAP can be applied to the following transmissions. In Type 2A DL CAP, the BS can transmit a signal immediately after sensing that the channel is idle for at least 25 μs of sensing duration Tshort_dl. Tshort_dl includes a duration Tf (=16 μs) and a subsequent sensing slot duration. Tf includes the sensing slot at the beginning of the duration.

[0238] -(i) One or more transmissions initiated by the BS, having (i) burst detection only, or (ii) burst detection multiplexed with non-unicast information, or

[0239] - Transmissions of one or more BSs after a 25μs interval between transmissions of the UE and one or more BSs within the shared channel occupancy period.

[0240] Type 2B DL ​​CAP applies to one or more transmissions performed by the BS after a 16μs interval through one or more transmission gaps via the UE within the shared channel occupancy period. In Type 2B DL ​​CAP, the BS can transmit a signal immediately after sensing that the channel is idle during Tf = 16μs. Tf includes the sensing time slot within the last 9μs of the duration. Type 2C DL CAP applies to one or more transmissions performed by the BS after a 16μs interval through one or more transmission gaps via the UE within the shared channel occupancy period. In Type 2C DL CAP, the BS does not sense the channel before performing the transmission.

[0241] Power Headroom Report (PHR)

[0242] The PHR procedure is used to inform the serving gNB how much transmission power is available for the UE, in addition to the power used by the current transmission. The power margin can be calculated using the following equation.

[0243] [Equation 1]

[0244] Power margin = UE maximum transmission power - PUSCH power = Pmax - P_pusch

[0245] If the power margin value is (+), it indicates "I still have some room at maximum power", implying "I can send more data".

[0246] If the power margin value is (-), it indicates that "I am already transmitting more power than I am allowed to transmit".

[0247] Specifically, the PHR process is used to provide the following types of power margin information to the serving gNB.

[0248] - Type 1 Power Margin: The difference between the UE's maximum transmission power and the estimated power transmitted via the UL Shared Channel (UL-SCH) for each active serving cell.

[0249] - Type 2 Power Margin: The difference between the UE's maximum transmission power and the estimated power of UL-SCH and PUCCH transmissions in a special cell (SpCell) of another MAC entity.

[0250] - Type 3 Power Margin: The difference between the UE's maximum transmission power and the estimated power of the probe reference signal (SRS) transmission for each active serving cell.

[0251] Figure 14 The diagram illustrates the structure of a radio frame.

[0252] In NR, UL and DL transmissions are configured within frames. Each radio frame is 10 ms long and is divided into two 5 ms half-frames. Each half-frame is further divided into five 1 ms subframes. Subframes are divided into one or more time slots, and the number of time slots within a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 OFDM(A) symbols. When using normal CP, each time slot includes 14 OFDM symbols. When using extended CP, each time slot includes 12 OFDM symbols. Symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-Extended OFDM (DFT-s-OFDM) symbols).

[0253] Table 11 illustrates, for example, how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS under normal CP conditions.

[0254] [Table 11]

[0255]

[0256]

[0257] *Nslotsymb: Number of symbols in a slot. *Nframe,uslot: Number of slots in a frame.

[0258] *Nsubframe,uslot: Number of time slots in a subframe

[0259] Table 12 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS under the extended CP case.

[0260] [Table 12]

[0261] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60kHz (u=2) 12 40 4

[0262] The frame structure is merely an example, and the number of subframes, slots, and symbols in a frame can be varied in various ways. In NR systems, different sets of OFDM(A) parameters (e.g., SCS, CP length, etc.) can be configured for multiple cells aggregated for a single UE. Therefore, the (absolute time) duration (referred to as the time unit (TU) for convenience) of time resources (e.g., subframes, slots, or transmission time intervals (TTI)) consisting of the same number of symbols can be configured differently across aggregated cells.

[0263] In NR, various parameter sets (or SCSs) can be supported to enable a wide range of fifth-generation (5G) services. For example, a 15kHz SCS can support wide areas in traditional cellular bands, while a 30kHz or 60kHz SCS can support dense urban areas, lower latency, and wide carrier bandwidth. With an SCS of 60kHz or higher, bandwidths greater than 24.25kHz can be supported to overcome phase noise.

[0264] The NR band can be defined by two types of frequency ranges, FR1 and FR2. FR1 and FR2 can be configured as shown in Table 3 below. FR2 can be millimeter wave (mmW).

[0265] [Table 13]

[0266]

[0267]

[0268] Figure 15The diagram illustrates the resource grid over the duration of a time slot.

[0269] A time slot comprises multiple symbols in the time domain. For example, a time slot comprises 14 symbols in normal CP and 12 symbols in extended CP. A carrier comprises multiple subcarriers in the frequency domain. A resource block (RB) can be defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth portion (BWP) can be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can take place in active BWPs, and only one BWP can be activated for a UE. Each element in the resource grid can be referred to as a resource element (RE) that a complex symbol can map to.

[0270] Figure 16 The diagram illustrates the physical channel in a 3GPP system and the general signal transmission method using the physical channel.

[0271] When the UE is powered on or enters a new cell, the UE performs an initial cell search (S11). The initial cell search involves acquiring synchronization with the BS. For this purpose, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH). The UE synchronizes its timing with the BS and obtains information such as the cell identifier (ID) based on the PSS / SSS. Furthermore, the UE can obtain information broadcast within the cell by receiving the PBCH from the BS. During the initial cell search, the UE can also monitor the DL channel status by receiving the downlink reference signal (DL RS).

[0272] After the initial cell search, the UE can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) corresponding to the PDCCH (S12).

[0273] Subsequently, to complete the connection to the BS, the UE can perform a random access procedure with the BS (S13 to S16). Specifically, the UE can transmit a preamble on the Physical Random Access Channel (PRACH) (S13), and can receive the PDCCH and the Random Access Response (RAR) for the preamble on the PDSCH corresponding to the PDCCH (S14). Then, the UE can transmit the Physical Uplink Shared Channel (PUSCH) using the scheduling information in the RAR (S15), and perform a contention resolution procedure including receiving the PDCCH and the PDSCH signal corresponding to the PDCCH (S16).

[0274] When the random access procedure is executed in two steps, steps S13 and S15 can be executed as one step (where message A is sent by the UE), and steps S14 and S16 can be executed as one step (where message B is sent by the BS).

[0275] Following the above process, during typical UL / DL signal transmission, the UE can receive PDCCH and / or PDSCH from the BS (S17) and send the Physical Uplink Shared Channel (PUSCH) and / or Physical Uplink Control Channel (PUCCH) to the BS (S18). The control information sent by the UE to the BS is typically referred to as Uplink Control Information (UCI). UCI includes Hybrid Automatic Repeat and HARQ-ACK / NACK, Scheduling Request (SR), Channel State Information (CSI), etc. CSI includes Channel Quality Indicator (CQI), Precoding Matrix Index (PMI), Rank Indicator (RI), etc. UCI is usually sent on the PUCCH. However, if control information and data should be sent simultaneously, they can be sent on the PUSCH. Additionally, the UE can periodically send UCI on the PUSCH when receiving requests / commands from the network.

[0276] Before describing the proposed method, the NR-based channel access schemes for unlicensed bands used in this disclosure are classified as follows.

[0277] - Category 1 (CAT-1): Within a COT, the next transmission immediately follows the previous transmission after the switching gap, and the switching gap is less than 16μs, even including transceiver turnaround time. Cat-1 LBT can correspond to the above-mentioned Type 2C CAP.

[0278] - Category 2 (Cat-2): LBT method without backoff. Transmission can be performed immediately once the channel is confirmed to be idle during a specific time period shortly before transmission. Cat-2 LBTs can be subdivided based on the length of the minimum sensing duration required for channel sensing immediately preceding transmission. For example, a Cat-2 LBT with a minimum sensing duration of 25 μs can correspond to Type 2A CAP described above, and a Cat-2 LBT with a minimum sensing duration of 16 μs can correspond to Type 2B CAP described above. The minimum sensing duration is merely exemplary, and minimum sensing durations less than 25 μs or 16 μs (e.g., a minimum sensing duration of 9 μs) are also available.

[0279] - Category 3 (Cat-3): LBT method with backoff based on a fixed contention window size (CWS)i. The transmitting entity selects a random number N within the range of 0 to a (fixed) maximum CWS value, and decrements a counter value each time the channel is determined to be idle. When the counter value reaches 0, the transmitting entity is allowed to perform transmission.

[0280] - Category 4 (Cat-4): LBT method with backoff based on variable CWS. The transmitting entity selects a random number N within the range of 0 to the (variable) maximum CWS value and decrements a counter value each time the channel is determined to be idle. When the counter value reaches 0, the transmitting entity is allowed to perform transmission. If the transmitting entity receives feedback indicating a reception failure, it will increase the maximum CWS value by one level, select another random number within the increased CWS value, and perform the LBT process. Cat-4 LBT can correspond to the above-described Type 1CAP.

[0281] The following description is given under the understanding that the term band can be used interchangeably with CC / cell, and that CC / cell (index) can be replaced by BWP (index) configured within CC / cell, or a combination of CC / cell (index) and BWP (index).

[0282] The terminology is defined as follows.

[0283] -UCI: Control information transmitted by the UE on the UL. UCI includes various types of control information (i.e., UCI types). For example, UCI can include HARQ-ACK (abbreviated as A / N or AN), SR, and CSI.

[0284] -PUCCH: Physical layer UL channel used for UCI transmission. For convenience, the PUCCH resources configured and / or indicated for A / N, SR, and CSI transmissions are referred to as A / N PUCCH resources, SR PUCCH resources, and CSI PUCCH resources, respectively.

[0285] - UL Licensed DCI: DCI used for UL licensing. For example, UL Licensed DCI means DCI format 0_0 and 0_1, and is sent on PDCCH.

[0286] -DL Assignment / License DCI: DCI used for DL ​​licensing. For example, DL Assignment / License DCI means DCI formats 1_0 and 1_1, and is sent on PDCCH.

[0287] -PUSCH: Physical layer UL channel used for UL data transmission.

[0288] - Time Slot: The basic time unit (TU) (or time interval) used for data scheduling. A time slot includes multiple symbols. Here, symbols include OFDM symbols (e.g., CP-OFDM symbols or DFT-s-OFDM symbols). In this specification, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbol are interchangeable.

[0289] - Perform LBT on / about channel X: This means performing LBT to confirm whether to transmit on channel X. For example, CAP can be performed before transmission on channel X begins.

[0290] In LAA UL, with the introduction of asynchronous HARQ procedures, there are no additional channels, such as the Physical HARQ Indicator Channel (PHICH), for indicating HARQ-ACK information for PUSCH to the UE. Therefore, accurate HARQ-ACK information is not required to adjust the CW size during the UL LBT procedure. During the UL LBT procedure, when a UL clearance is received in the nth subframe, the first subframe of the most recent UL transmission (TX) burst preceding the (n-3)th subframe has been configured as the reference subframe, and the CW size has been adjusted based on the New Data Indicator (NDI) of the HARQ procedure ID corresponding to the reference subframe. That is, when the BS switches NDI or indicates retransmission of one or more TBs for each or more Transport Blocks (TBs), a mechanism has been introduced that, if the transmission of the PUSCH fails in the reference subframe due to a collision with other signals, the corresponding CW size is increased to the next maximum CW size of the currently applied CW size in a pre-agreed set of CW sizes; or, if the PUSCH in the reference subframe has been successfully transmitted without any collisions with other signals, the CW size is initialized to a minimum (e.g., CW...). min The method.

[0291] In NR systems, each CC can support up to 400MHz. When a UE operating in such a wideband CC always operates through an RF module that is enabled for the entire CC, the UE's battery consumption may increase.

[0292] Alternatively, considering the various communication use cases such as eMBB, URLLC, and / or mMTC operating in a single broadband CC, different sets of parameters (e.g., SCS) can be supported for each band within the CC.

[0293] Each UE can have a different maximum bandwidth capability. In this respect, the BS can instruct the UE to operate only within a portion of the bandwidth, rather than the total bandwidth of the wideband CC. For convenience, the portion of the bandwidth can be defined as the BWP. The BWP can include consecutive RBs on the frequency axis and correspond to a set of parameters such as SCS, CP length, and / or slot / microslot duration.

[0294] The BS can even configure multiple BWPs within a single CC configured for the UE. For example, the BS can configure a BWP occupying a relatively small frequency region in the PDCCH monitoring slot and schedule the PDSCH scheduled by the PDCCH in a BWP allocated to a larger frequency region than the BWP used for the PDCCH.

[0295] Alternatively, when UEs are concentrated on a particular BWP, the BS can configure another BWP, some of which UEs can send and receive signaling notifications for load balancing.

[0296] Alternatively, considering the elimination of frequency-domain inter-cell interference between neighboring cells, the BS can exclude some intermediate spectrum of the total bandwidth and configure two BWPs in the same time slot. That is, the BS can configure at least one DL / UL BWP for a UE associated with a broadband CC and activate at least one of the DL / UL BWPs configured at a specific time point via L1 signaling, MAC control element (CE) signaling, or radio resource control (RRC) signaling.

[0297] In addition, the currently active BWP can be switched to another DL / UL BWP via L1 signaling, MAC CE signaling or RRC signaling, or the active BWP can be switched to a predetermined DL / UL BWP when the timer value based on the timer expires.

[0298] An active DL / UL BWP is defined as the active DL / UL BWP. During initial access or before RRC connection establishment, the UE may not receive the configuration for the DL / UL BWP. In this case, the UE assumes the DL / UL BWP is the initially active DL / UL BWP.

[0299] In NR Unlicensed (NR-U), when the bandwidth allocated to the BWP by the BS and / or UE is greater than 20MHz, in order to coexist fairly with Wi-Fi, the BWP can be divided into units that are integer multiples of 20MHz, and LBT can be executed in 20MHz units. The 20MHz units that can be distinguished from the aforementioned LBTs are called subbands.

[0300] For UE UL data transmission in the U-band, the BS should successfully perform LBT (Local Level-By) for UL-licensed transmission in the U-band, and the UE should also successfully perform LBT for UL data transmission. That is, the UE can only attempt to transmit UL data if both the LBT performed by the base station and the LBT performed by the UE are successful. In LTE systems, because a minimum 4-millisecond delay occurs between UL licensing and the UL data scheduled by UL licensing, earlier access from another coexisting transmission node in the U-band during the corresponding time period may delay UL data propagation. In this case, a method to increase the efficiency of UL data transmission in the U-band needs to be discussed.

[0301] In LTE LAA, the BS can notify the UE of the Autonomous Uplink (AUL) subframes or time slots for autonomous UL transmission via an X-bit bitmap (e.g., a 4-bit bitmap), allowing the UE to transmit UL data without receiving UL clearance. When the UE is indicated to autonomous transmission activation, it can transmit UL data in the subframe or time slot indicated by the X-bit bitmap, even without receiving UL clearance. When sending the PDSCH to the UE, the BS also sends the PDCCH, which is the scheduling information required for decoding. Similarly, when sending the PUSCH to the BS on the AUL, the UE also sends the AUL UCI, which is the information required by the BS to decode the PUSCH. The AUL UCI includes information required to receive the AUL PUSCH, such as the HARQ identifier (ID), NDI, Redundancy Version (RV), AUL subframe start position and AUL subframe end position, and information about the UE-initiated COT shared with the BS.

[0302] Specifically, “COT initiated by UE and shared with BS” can indicate the following procedure.

[0303] A portion of the channel occupied by the UE can be assigned to the BS via Category 4 LBT or Type 1 CAP based on random backoff, and the BS can perform a 25μsec one-shot LBT based on a timing gap generated by the UE without using an end symbol. In this case, when the channel becomes idle due to the performance of the one-shot LBT, the BS can transmit PDCCH and / or PDSCH. This process is called COT sharing between the UE and the BS.

[0304] To support UL transmissions with relatively high reliability and relatively low time latency, NR also supports CG Type 1 and CG Type 2, where the BS configures time, frequency and code domain resources for the UE through a combination of higher-layer signaling (e.g., RRC signaling) or higher-layer signaling and L1 signaling (e.g., DCI).

[0305] In other words, even without receiving UL authorization from the BS, the UE can perform UL transmissions in resources configured with Type 1 or Type 2. In Type 1, the periodicity of the CG, the offset from SFN=0, time / frequency resource allocation, number of repetitions, demodulation reference signal (DMRS) parameters, modulation and compilation scheme (MCS) / TBS, power control parameters, etc., can only be configured by higher-level signaling such as RRC signaling.

[0306] Type 2 is a scheme that configures the periodicity and power control parameters of the CG through higher-level signaling such as RRC signaling and indicates information such as the offset of the initial transmission timing, time / frequency resource allocation, DMRS parameters and the remaining resources of the MCS / TBS by activating DCI as L1 signaling.

[0307] The AUL of LTE LAA and CG of NR show significant differences in the method of sending HARQ-ACK feedback for PUSCH that the UE has sent without receiving UL clearance, and in the presence or absence of UCI sent with the PUSCH. Explicit HARQ-ACK feedback is sent in the AUL Downlink Feedback Information (AUL-DFI) of LTE LAA when the HARQ procedure is determined by an equation in the NR CG for the symbol index, symbol period, and number of HARQ procedures.

[0308] Furthermore, in LTE LAA, whenever an AUL PUSCH transmission is performed, a UCI including information such as HARQ ID, NDI, and RV is also transmitted in the AUL UCI. In the case of NR CG, the BS identifies the UE through the time / frequency resources and DMRS resources used by the UE for PUSCH transmission, while in the case of LTE LAA, the BS identifies the UE through the UE ID explicitly included in the AUL UCI transmitted along with the PUSCH and DMRS resources.

[0309] The BS can configure CG resources for the UE as type 1 or type 2, and the UE can perform UL transmissions by performing LBTs on the configured time / frequency resources. The BS can share the COT obtained through Cat-4 LBTs with the UE, allowing the UE to perform only Cat-2 LBTs within the BS's COT to increase channel access probability. Similarly, the UE can share the COT obtained by performing Cat-4 LBTs for CG PUSCH or DG PUSCH transmissions outside the BS's COT, allowing the BS to perform DL transmissions by performing Cat-2 LBTs within the remaining COT after the UE performs UL transmissions.

[0310] When performing this UL to DL COT sharing, the transmission power of the UE and BS may differ. If the BS transmits a signal with relatively high DL power in the COT obtained by the UE based on an Energy Detection (ED) threshold calculated based on the maximum UL power configured for the UE, this could lead to severe interference or transmission conflicts with other neighboring nodes. Therefore, the BS can configure the ED threshold for UL to DL COT sharing for the UE via higher-layer signaling such as RRC signaling.

[0311] Therefore, the UE can have a first ED threshold calculated based on the maximum UL power configured by the BS according to the energy detection threshold adaptation procedure defined in Clause 4.1.5 of 3GPP TS 37.213, and a second ED threshold configured by the BS for UL to DL COT sharing, and selectively use one ED threshold depending on whether COT is shared during UL transmission. Alternatively, the second ED threshold configured by the BS can always be used as the default value.

[0312] In this scenario, the UE can notify the BS whether COT sharing is permitted by including information in the CG-UCI regarding which ED threshold or UL power has been used to perform LBT and UL transmissions. Here, "UE notifies BS whether COT sharing is permitted" can mean that the UE notifies the BS whether other DL transmissions besides PDCCH transmissions of up to 2 symbols are possible within the shared COT.

[0313] In the case of DL to UL COT sharing, the UE can receive signals such as GC-PDCCH from the BS, which includes information about whether CG-PUSCH can be sent within the COT, and perform Cat-2 LBT. Then, if the channel is idle, the UE can perform UL transmission.

[0314] In this case, the ED threshold for Cat-2 LBT can be either the ED threshold configured by the BS or the ED threshold configured by the UE based on the UE's UL power, as described above.

[0315] Unlike LTE AUL, if the frequency axis resources used for CG are configured with a bandwidth of 20MHz or greater, the frequency axis resources can include multiple LBT subbands in units of 20MHz. For the UE to perform UL transmission on the corresponding CG-PUSCH resources, transmission is only allowed if the UE successfully performs LBT in all LBT subbands as a result of performing LBT in each LBT subband. Furthermore, even when the remaining COT is shared and used for DL ​​transmission, DL transmission can be allowed only in subbands equal to or smaller than the LBT subbands in which the UE successfully performed LBT.

[0316] As described in Clause 4.2.1 of 3GPP TS 37.213, UE transmission operations without LBT are supported when scheduling DG-PUSCH on LTE AUL in consecutive subframes with no gap to AUL-PUSCH if the conditions described in Table 14 below are met.

[0317] [Table 14]

[0318]

[0319]

[0320] Even in NR-U, if DG-PUSCH is scheduled consecutively without gaps in the time axis resources used to configure CG for the UE (i.e., in the case of CG-DG back-to-back scheduling), the UE can only transmit DG-PUSCH without LBT if the frequency band of DG-PUSCH has the same LBT subband as the frequency band of CG-PUSCH. In this case, there should be no gap between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH. If gaps exist or the LBT subbands are not equal, an LBT gap corresponding to a specific X symbols immediately preceding DG-PUSCH may be required for the UE to perform LBT.

[0321] In NR, regarding multiple CCs / cells configured for a UE, the BS can simultaneously receive PHRs for all CCs / cells via a DG-PUSCH or CG-PUSCH transmitted in one CC / cell. Each CC / cell can be a U-cell operating in the U-band, a cell operating in the L-band, or a CC / cell with an additional Supplemental UL (SUL) configured therein.

[0322] There are two types of PHR information, which can be included in either DG-PUSCH or CG-PUSCH: the actual PHR based on the power of the PUSCH used by the UE for actual transmission, and the virtual PHR based on the reference transport format defined in Clause 7.7 of 3GPP TS 38.213. The reference transport format is a transport format used to virtually calculate the PHR in the absence of PUSCH transmission. For example, such a transport format can be defined based on an RB and a minimum MCS level.

[0323] In the case of CG-PUSCH or DG-PUSCH transmitted via L-band carriers, there is no possibility of confusion between the actual PHR and the virtual PHR because transmission is always guaranteed. However, CG-PUSCH transmitted via U-band carriers can be transmitted or discarded depending on the success of the UL LBT. Therefore, if the CG-PUSCH of the NR-U cell, including the PHR report, cannot be transmitted due to LBT failure, or if the LBT of the PUSCH of another CC / cell fails, the BS may be confused about whether the PHR transmitted at the retransmission time point is the actual PHR or the virtual PHR. To solve this problem, a method could be considered whereby, when transmitting PHR via CG-PUSCH of the NR-U cell, only the virtual PHR is always transmitted, or the UE can signal to the BS which of the actual and virtual PHRs has been transmitted via CG-UCI.

[0324] The following describes proposed methods for addressing the aforementioned problems. Specifically, [Proposed Methods #1] through [Proposed Methods #3] describe methods for using an ED threshold by the UE based on whether COT is shared, and for performing LBT and / or sending PUSCH based on the ED threshold.

[0325] [Proposed Method #4] describes the conditions under which a UE transmits DG-PUSCH without an LBT for back-to-back CG-DG PUSCH transmission, and the UE's operation when the conditions are not met.

[0326] [Proposed Method #5] and [Proposed Method #6] describe methods for UE to transmit PHR.

[0327] [Proposed Method #1] through [Proposed Method #6] are not always executed independently. In other words, [Proposed Method #1] through [Proposed Method #6] can be operated on / executed individually, but two or more proposed methods can be operated on / executed in combination.

[0328] For example, [Proposed Method #1], [Proposed Method #4], and [Proposed Method #5] can be combined to perform the operation of the UE and / or BS, and [Proposed Method #1], [Proposed Method #2], and [Proposed Method #3] can be combined to perform the operation of the UE and / or BS. That is, [Proposed Method #1] through [Proposed Method #6] are not optional and are classified for ease of explanation.

[0329] Furthermore, the embodiments of [Proposed Method #1] to [Proposed Method #6] described below according to this disclosure are not limited to the U-band, but can be applied to operations between the UE and the BS, which transmit and receive UL / DL signals through a frequency band that can perform LBT-based CAP.

[0330] For example, the proposed methods #1 to #6 described below can also be applied to operations between UEs and BSs that transmit and receive UL / DL signals via the Citizens Broadband Radio Service (CBRS).

[0331] Furthermore, "performing LBT" may have the same meaning as "performing CCA". The series of processes involving LBT and / or CCA transmitting and receiving UL / DL signals via a frequency band in an idle state is defined as CAP. Therefore, performing LBT and / or CCA may have the same meaning as performing CAP.

[0332] [Proposed Method #1] Wherein, when the UE receives a first ED threshold to be used for performing UL LBT for UL to DL COT sharing from the BS via higher-layer signaling such as RRC signaling, the UE selects the ED threshold to be used for the LBT to be performed before sending CG-PUSCH as follows and indicates the selected ED threshold via CG-UCI.

[0333] (1) A method of performing UL LBT based on a first ED threshold configured via higher-layer signaling and sending a CG-UCI including information about the first ED threshold, so that the UE and BS share the remaining COT after sending CG-PUSCH.

[0334] (2) Perform UL LBT based on a second ED threshold calculated based on the maximum UL power configured by the BS instead of a first ED threshold configured by higher-layer signaling, and send a CG-UCI including information about the second ED threshold so that the UE does not allow DL transmissions other than the BS’s PDCCH transmission for up to 2 symbols in the remaining COT after sending the CG-PUSCH.

[0335] Reference Figure 17 The above-mentioned [Proposed Method #1] is described in detail. The UE can share the COT obtained by performing Cat-4 LBT for CG PUSCH transmission or DG PUSCH transmission with the BS, so that the BS can transmit DL signals and / or DL ​​channels within the remaining COT after the UE performs UL transmission and after performing Cat-2 LBT.

[0336] However, when the UE and BS have different transmission powers and the BS transmits DL signals and / or DL ​​channels at a relatively high DL power in the COT obtained by the UE based on a second ED threshold calculated based on the maximum UL power configured for the UE, this may lead to severe interference or transmission conflicts with other neighboring nodes. Therefore, the BS can configure a first ED threshold for UL-DL COT sharing for the UE via higher-layer signaling such as RRC signaling (S1701).

[0337] In addition, the UE can select one of a second ED threshold calculated based on the maximum UL power configured by the BS and a first ED threshold configured by the BS for UL to DLCOT sharing, depending on whether DL transmissions other than PDCCH transmissions of up to 2 symbols are allowed within the COT shared with the BS, and perform UL LBT and UL transmissions based on the selected ED threshold.

[0338] In this scenario, when the UE shares a COT with the BS, it notifies the BS whether DL transmissions, in addition to PDCCH transmissions of up to two symbols, are permitted within the shared COT by sending information in the CG-UCI regarding which ED threshold (or UL power based on the selected threshold) has been used to perform LBT and UL transmissions.

[0339] Here, "up to 2 symbols" can refer to a duration corresponding to a length of up to 2 symbols based on a 15-kHz SCS. For example, a length of up to 2 symbols based on a 15-kHz SCS can be a duration corresponding to a length of up to 4 symbols based on a 30-kHz SCS and a duration corresponding to a length of up to 8 symbols based on a 60-kHz SCS.

[0340] Alternatively, when the UE shares the COT with the BS, by transmitting information about the length of the remaining COT in the CG-UCI based on two symbols for the 15-kHz SCS, the UE can inform the BS whether other DL transmissions including up to two symbols of PDCCH transmission are permitted within the shared COT. As mentioned above, the information about the length of the remaining COT can be based on four symbols for the 30-kHz SCS being included in the CG-UCI, or based on eight symbols for the 60-kHz SCS being included in the CG-UCI.

[0341] Alternatively, when COT is shared, if only up to 2 symbols of PDCCH transmission are always allowed, i.e., if DL transmission other than up to 2 symbols of PDCCH transmission is not allowed, the UE can indicate that DL transmission other than 2 symbols of PDCCH transmission is not allowed by sending a message in CG-UCI indicating that there is no remaining length of COT to the BS (S1703). That is, when the BS receives the message indicating no remaining COT length from the UE via CG-UCI, it can interpret this message as meaning that DL transmission (based on 15-kHz SCS) other than up to 2 symbols of PDCCH transmission is not allowed. Alternatively, when the BS receives the message indicating no remaining COT length from the UE via CG-UCI, it can interpret this message as meaning that the UE has sent CG-PUSCH using the second ED threshold instead of the first ED threshold.

[0342] In other words, if the UE notifies the BS via CG-UCI that UL LBT and UL transmissions are performed based on a first ED threshold configured by the BS, the BS can perform DL transmissions, such as PDSCH transmissions with more symbols including 2-symbol PDCCH transmissions, within the shared COT of the UE. In this case, the BS can perform DL transmissions based on Cat-2 LBTs within the shared COT. Conversely, if the UE notifies the BS via CG-UCI that UL LBT and UL transmissions are performed based on a second ED threshold calculated based on the maximum UL power, the BS can identify that DL transmissions using the shared COT, other than 2-symbol PDCCH transmissions, may not be possible. In this case, the BS can perform DL transmissions based on Cat-4 LBTs (S1705).

[0343] In other words, when it is possible for the BS to configure COT sharing for the UE and the BS transmits DL signals within the shared COT, if the BS transmits the DL signals based on relatively high power, the DL signals transmitted by the BS may interfere with or conflict with the signals of other nodes. Therefore, the BS can configure a first ED threshold for COT sharing, and the UE can perform UL LBT based on the first ED threshold when the COT is shared. For example, if the UE performs UL LBT based on a relatively low first ED threshold and transmits UL signals by determining that the corresponding channel is idle, this means that other nodes will not transmit signals in the corresponding channel at power exceeding the first ED threshold, which may also mean that the BS's DL signals will interfere with the signals of relatively few other nodes. Accordingly, the BS can configure a relatively low first ED threshold so that the UE can perform UL LBT based on the first ED threshold while sharing the COT.

[0344] However, even if the BS configures the UE to share the COT, the UE does not always have to share the COT. That is, when the UE should use all the COTs to transmit the CG-PUSCH or use only a very short COT to receive another DL signal, the UE may not share the COTs and use all the COTs to transmit the CG-PUSCH.

[0345] However, even in this case, if the UE should perform UL LBT using the first ED threshold, the probability of UL LBT success is reduced, which may result in only a decrease in the UE's channel access opportunities. Therefore, if COT is not shared, it is advantageous for the UE to perform UL LBT using the second ED threshold calculated based on the maximum UL power.

[0346] Here, not sharing the COT may mean that no other DL signal transmissions are allowed within the COT except for the two symbols of the BS PDCCH transmission.

[0347] Therefore, the UE can selectively use the ED threshold based on whether the COT is shared. For example, if the COT is shared, the UE can use the first ED threshold to perform UL LBT, and if the COT is not shared, the UE can use the second ED threshold to perform UL LBT.

[0348] In this scenario, the BS can only perform appropriate operations, such as DL transmission and / or UL reception, once it identifies whether the UE shares the COT and / or which ED threshold is used. Therefore, the UE can send relevant information from the CG-UCI multiplexed with the CG-PUSCH to the BS.

[0349] For example, the UE includes and sends information in the CG-UCI regarding whether COT sharing is possible (i.e., information about whether COT sharing is possible). When the BS receives the CG-UCI, the BS can determine whether COT sharing is possible and which ED threshold the UE has already used based on the information included in the CG-UCI. For example, if the CG-UCI received by the BS includes information indicating that COT sharing is possible, the BS can use a first ED threshold to identify that the UE has performed UL LBT. Conversely, if the CG-UCI includes information indicating that COT sharing is impossible, the BS can identify that the UE will perform UL LBT using a second ED threshold.

[0350] As another example, the UE can include information about the ED threshold used for UL LBT in the CG-UCI. For instance, if information about a first ED threshold is included in the CG-UCI received by the BS, the BS recognizes that the UE has performed UL LBT using the first ED threshold and that COT sharing is possible. Conversely, if information about a second threshold is included in the CG-UCI received by the BS, the BS can recognize that the UE has performed UL LBT using the second ED threshold and that COT sharing is not possible. That is, the UE can explicitly send one of the information about which ED threshold to use and the information about whether COT sharing is possible, and implicitly send the other to the BS in association with the explicit information.

[0351] However, the UE can explicitly include all information about which ED threshold to use and whether COT sharing is possible in the CG-UCI and send the CG-UCI to the BS.

[0352] [Proposed Method #2] When a first ED threshold for a UL LBT to be used for UL-to-DLCOT sharing is received from the BS via higher-level signaling such as RRC signaling, one of (i) the first ED threshold configured via higher-level signaling and (ii) the second ED threshold calculated by the UE based on the maximum UL power configured by the BS is used as the ED threshold to be used for the LBT performed before the UE sends DG-PUSCH.

[0353] Specifically, will refer to Figure 18 [Proposed Method #2] is described in detail. In the case of DG-PUSCH, since there is no method as in [Proposed Method #1] for informing the BS which ED threshold has been used via a UL signal such as CG-UCI, the UE can use the ED threshold of the UL-permitted scheduling indication sent by the BS to perform UL LBT and send PUSCH (S1805). In other words, upon receiving DG-PUSCH from the UE based on the first ED threshold scheduled for UL to DL COT sharing, the BS can send other DL (e.g., PDSCH) signals, including a 2-symbol PDCCH, in the remaining COT after the DG-PUSCH transmission ends.

[0354] Upon receiving a DG-PUSCH instruction to perform UL LBT and UL transmissions using a second ED threshold calculated by the UE based on the maximum UL power, the BS may send a PDCCH of up to two symbols after the DG-PUSCH transmission ends (S1803). For this purpose, the BS can configure a first ED threshold for UL-DL COT sharing for the UE via higher-layer signaling such as RRC signaling (S1801).

[0355] In other words, when the BS instructs the UE to use the first ED threshold for COT sharing via UL authorization, the BS can share the UE's COT to transmit additional DL signals and / or DL ​​channels, including up to two symbols of PDCCH. That is, the BS can perform DL transmission based on Cat-2 LBT within the shared COT. Conversely, when the BS instructs the UE to use the second ED threshold calculated based on the maximum UL power via UL authorization, the BS can transmit only up to two symbols of PDCCH within the UE's COT. In this case, the BS can perform DL transmission based on Cat-4 LBT (S1807).

[0356] [Proposed Method #3] When the first ED threshold for the UL LBT to be used for UL-to-DLCOT sharing is received from the BS via higher-level signaling such as RRC signaling, the remaining COT after the DL transmission shared within the BS's COT is used to select the ED threshold for Cat-2 LBT-based DG-PUSCH or CG-PUSCH transmissions.

[0357] (1) Method using the first ED threshold configured by BS

[0358] (2) Using a method that calculates a second ED threshold based on the maximum UL power configured by the BS using the UE.

[0359] (3) Using the Max(first ED threshold, second ED threshold) method

[0360] (4) Using the Min(first ED threshold, second ED threshold) method

[0361] Reference Figure 19The above-mentioned [Proposed Method #3] is described in detail. The BS can configure a first ED threshold for UL to DL COT sharing for the UE via higher-layer signaling such as RRC signaling (S1901). The BS can perform DL transmission to the UE (e.g., PDSCH) using the COT obtained based on Cat-4 LBT (S1903). In the case of DL to UL COT sharing, the UE performs Cat-2 LBT by receiving an indication / configuration from the BS whether to send CG-PUSCH within the COT via physical layer signaling such as GC-PDCCH or via higher-layer signaling. If the channel is idle, the UE can perform UL transmission (S1905). In this case, the ED threshold used by the UE for Cat-2 LBT can be the first ED threshold configured by the BS as in (1) or the second ED threshold of the UE based on the power configured by the UE using the maximum UL power as in (2). Alternatively, the UE can use the larger or smaller value of the first ED threshold in (1) and the second ED threshold in (2) as the ED threshold (S1905).

[0362] [Proposed Method #4] After performing Cat-4 LBT on the CG resource configured by the BS, during the transmission of CG-PUSCH, a method of performing back-to-back CG-DG PUSCH transmission relative to the DG-PUSCH scheduled based on UL license is performed according to the following conditions. Here, the CG-UL resource may include multiple LBT subbands.

[0363] (1) When there is no gap between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH on the time axis, and the LBT subband resources of the CG-PUSCH that have been transmitted on the frequency axis are the same as the LBT subband resources of the scheduled DG-PUSCH, or the LBT subbands allocated to DG-PUSCH are a subset of the LBT subbands of CG-PUSCH, the method of continuously transmitting DG-PUSCH immediately after CG-PUSCH without LBT is provided.

[0364] (2) When there is a gap between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH, the LBT subband resources of CG-PUSCH already transmitted on the frequency axis are different from the LBT subband resources of scheduled CG-PUSCH, or the LBT subband of DG-PUSCH allocated to it is not included in the LBT subband of CG-PUSCH (i.e., the LBT subband of DG-PUSCH is not a subset of the LBT subband of CG-PUSCH), a method is used to discard specific X symbols, Y CG-PUSCH, or Z time slots immediately before DG-PUSCH to ensure LBT before transmitting DG-PUSCH.

[0365] In this case, the X, Y, and Z values ​​for how many symbols, CG-PUSCHs, and time slots will be dropped for the LBT gap can use the values ​​specified in the standard. Alternatively, the X, Y, and Z values ​​can use values ​​configured / indicated by the BS via higher-layer signaling such as RRC signaling, physical-layer signaling such as DCI, or a combination of higher-layer and physical-layer signaling. In the proposed method above, back-to-back transmission from DG-PUSCH to CG-PUSCH can be performed by rearranging the order of CG-PUSCH to DG-PUSCH and DG-PUSCH to CG-PUSCH.

[0366] In (2), when the priority of DG-PUSCH is higher than that of CG-PUSCH, there is a gap between DG-PUSCH and CG-PUSCH, or the LBT subband resources of DG-PUSCH and CG-PUSCH are different, the UE may discard the transmission of CG-PUSCH after DG-PUSCH.

[0367] In LTE LAA, when DG-PUSCH is scheduled in consecutive subframes without a gap from AUL-PUSCH, the UE can send DG-PUSCH without LBT (Article 4.2.1 of 3GPP TS 37.213).

[0368] Similarly, reference Figure 20 The above-mentioned [Proposed Method #4] is described in detail. Even when CG-PUSCH is transmitted based on Cat-4 LBT in NR-U (S2003), if DG-PUSCH is continuously scheduled with UL permission and there is no gap with the time axis resources of the CG configured for the UE (S2001), i.e., in the case of CG-DG back-to-back scheduling, the UE can transmit DG-PUSCH without LBT. In this case, unlike LTE, in NR-U, because the bandwidth of the CG resources configured for the UE is greater than 20MHz, the CG resources can include multiple LBT subbands. Therefore, in order to continuously transmit DG-PUSCH without LBT using the COT obtained for CG-PUSCH, the frequency band of the scheduled DG-PUSCH should be included in the frequency band of the CG-PUSCH. That is, the LBT subband of DG-PUSCH should be the same as the LBT subband of CG-PUSCH, or the LBT subband of DG-PUSCH should be a subset of the LBT subband of CG-PUSCH. Similar to the case of LTE LAA, there should be no time gap between CG-PUSCH and DG-PUSCH (S2005).

[0369] For example, refer to Figure 21If LBT subband #1 and LBT subband #2 are allocated as CG resources, and DG-PUSCH is scheduled while CG-PUSCH is being sent by performing LBT on CG-PUSCH, LBT subband #1 and LBT subband #2 can be allocated as LBT subbands of DG-PUSCH such that the LBT subbands of DG-PUSCH are the same as the LBT subbands of CG resources, or LBT subband #1 or LBT subband #2 can be allocated as LBT subbands of DG-PUSCH such that the LBT subbands of DG-PUSCH are a subset of the LBT subbands of CG resources.

[0370] However, subset relations do not necessarily have to be satisfied on a unit basis using LBT subbands. For example, suppose... Figure 21 Each LBT subband illustrated in the figure includes 10 RBs with indices #0 to #9 respectively. Since the UE has already performed LBT on a total of 20 RBs included in subband #1 and LBT subband #2 for CG-PUSCH transmission, the UE can transmit DG-PUSCH without LBT even if RBs with indices #5 to #9 in LBT subband #1 and RBs with indices #0 to #4 in LBT subband #2 are allocated as frequency resources for DG-PUSCH, and if RBs with indices #0 to #9 in LBT subband #1 and RBs with indices #0 to #9 in LBT subband #2 are allocated as LBT subbands for DG-PUSCH.

[0371] In other words, the frequency resources (or frequency domain) used for DG-PUSCH transmission should be included in or identical to the frequency resources (or frequency domain) used for CG-PUSCH transmission. This inclusion relationship does not need to satisfy a subset relationship on a per-LBT subband basis. Even if LBT subbands for DG-PUSCH are configured on the LBT subbands of two CG-PUSCH transmissions, it can be said that the frequency resources of DG-PUSCH are included in the frequency resources of CG-PUSCH. In other words, the frequency resources used for DG-PUSCH transmission need to have a subset relationship with respect to all frequency resources used for CG-PUSCH transmission.

[0372] In other words, when there is no gap on the time axis between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH, and the LBT subband resources of the CG-PUSCH that have been transmitted on the frequency axis are the same as those of the DG-PUSCH scheduled for the UE, or the LBT subband / LBT frequency resources of DG-PUSCH are included in the LBT subband / LBT frequency resources of CG-PUSCH, the UE can immediately continue to transmit DG-PUSCH after CG-PUSCH without LBT.

[0373] However, if there is a gap between the end symbol of CG-PUSCH and the start symbol of DG-PUSCH on the time axis, or if the LBT subband resources of CG-PUSCH that have been transmitted on the frequency axis are different from the LBT subband resources of DG-PUSCH that have been scheduled, that is, if the LBT subband of DG-PUSCH is not included in the LBT subband of CG-PUSCH, then the UE may not transmit DG-PUSCH without LBT.

[0374] In this scenario, the UE should discard a specific set of X symbols, Y CG-PUSCHs, or Z time slots immediately before sending the DG-PUSCH to ensure an LBT gap before transmitting the DG-PUSCH. The X, Y, or Z values ​​specifying how many symbols, CG-PUSCHs, or time slots will be discarded to ensure an LBT gap can be used. Alternatively, the X, Y, or Z values ​​can be configured / indicated to the UE by the BS via higher-layer signaling, physical-layer signaling, or a combination of both, and the UE can discard symbols, CG-PUSCHs, or time slots using the configured / indicated values.

[0375] Furthermore, the same method can be applied even when the order of CG-PUSCH and DG-PUSCH is reversed, i.e., in the case of back-to-back transmission of DG-CG. In other words, if there is no time gap between DG-PUSCH and CG-PUSCH on CG resources immediately following DG-PUSCH, and if CG-PUSCH and DG-PUSCH are transmitted via the same LBT or if the LBT subband of CG-PUSCH is a subset of the subband of DG-PUSCH, then the UE can immediately continue transmitting CG-PUSCH without LBT after the DG-PUSCH transmission ends. However, because DG-PUSCH has a higher priority than CG-PUSCH, if there is a time gap between DG-PUSCH and CG-PUSCH or if the LBT subband of DG-PUSCH is different from the LBT subband of CG-PUSCH, the UE can skip CG-PUSCH transmission without discarding specific X symbols or Y DG-PUSCH, as in (2).

[0376] [Proposed Method #5] When the UE is configured with multiple L cells or multiple U cells such as NR-U cells, and transmits a PHR for each CC in the CG-PUSCH transmitted in the NR-U cell, it should always transmit a virtual PHR or indicate via CG-UCI whether the PHR included in the CG-PUSCH is a virtual PHR or an actual PHR.

[0377] refer to Figure 22In NR, regarding multiple CCs / cells configured for a UE, the BS can simultaneously receive PHRs (S2201) for all CCs / cells by transmitting a DG-PUSCH or CG-PUSCH in one CC / cell. In this case, each CC / cell can be a U cell operating in the U band, a cell operating in the L band, or a CC / cell in which SUL is also configured.

[0378] Two types of PHR information can be included in DG-PUSCH or CG-PUSCH: actual PHR based on the power of the PUSCH used by the UE for actual transmission and virtual PHR based on the reference format defined in Clause 7.7 of 3GPP TS 38.213.

[0379] Because CG-PUSCH or DG-PUSCH transmission is always guaranteed on licensed carriers, there is no probability that the BS will generate confusion about whether the PHR included in the PUSCH is an actual PHR or a virtual PHR. However, depending on whether the UL LBT is successful, CG-PUSCH transmitted on unlicensed carriers may be sent or discarded. In this case, if the CG-PUSCH of the NR-U cell including the PHR report is not sent due to LBT failure, the BS may still generate confusion about whether the PHR included in the CG-PUSCH is an actual PHR or a virtual PHR even when the CG-PUSCH including the PHR is retransmitted through the next CG resource, because the BS cannot distinguish whether the CG-PUSCH was initially sent or retransmitted.

[0380] To address this issue, when a UE is configured with multiple L-cells or multiple U-cells, such as NR-U cells, and sends a PHR for each CC in the CG-PUSCH transmitted in the NR-U cell, the UE can either always send a virtual PHR, or inform the BS whether the PHR included in the CG-PUSCH is a virtual PHR or an actual PHR through a bitmap for each CC / cell in the CG-UCI. For example, when the number of CCs / cells configured for the UE is 8, the CG-UCI can include an 8-bit bitmap. When the bit value is "0" (or "1"), this indicates that the PHR for the corresponding CC / cell is an actual PHR, and when the bit value is "1" (or "0"), this indicates that the PHR for the corresponding CC / cell is a virtual PHR. The size of the bitmap included in the CG-UCI can be changed or fixed depending on the number of CCs / cells configured for the UE. If the number of CCs / cells configured for the UE is smaller than the bitmap size when the bitmap size is fixed, the remaining bits can be padded with zeros. For example, if the bitmap size is 8 bits and the number of CCs / cells configured for the UE is 4, the UE can use the first 4 bits to inform the BS of the PHR information for each CC / cell, and the remaining 4 bits can be padded with zeros. If the number of CCs / cells configured for the UE is greater than the bitmap size, the BS can obtain the PHR information through modulo operations. For example, if the bitmap size is 8 bits and 10 CCs / cells #0 to #9 are configured for the UE, the first bit of the bitmap can indicate whether the PHRs for CCs / cells #0 and #8 are virtual PHRs or actual PHRs.

[0381] Furthermore, for cells configured with SUL, the UE can simultaneously transmit PHRs not only for the SUL carrier but also for the Normal Uplink (NUL) carrier. In this case, the UE can configure and transmit PHR reports for both carriers as a virtual PHR and a Type 1 PHR.

[0382] In addition, when the UE simultaneously sends the PHR of the NUL carrier and the PHR of the SUL carrier for a cell configured with SUL, the UE can configure and send a PHR report for both carriers as a virtual PHR, and configure and send a PHR report as a type 1 PHR for a carrier in which PUSCH is configured, and a PHR report as a type 3 PHR for a carrier in which PUSCH and / or PUCCH are not configured, or a carrier in which PUSCH and / or PUCCH are not configured but SRS handover is configured.

[0383] [Proposed Method #6] When configuring multiple L-cells or multiple U-cells such as NR-U cells for a UE, both SUL carriers and NUL carriers are configured in a specific cell, and PUSCH or PUCCH transmission can be configured in each carrier, (1) configure and transmit PHR only for carriers in which PUSCH / PUCCH is configured in SUL carriers and NUL carriers, (2) transmit information about PHRs for carriers used for predefined / configured / indicated, or (3) indicate information about carriers corresponding to PHRs included in CG-PUSCH via CG-UCI or MAC CE.

[0384] The carrier for reporting the PHR can be either a SUL carrier or a NUL carrier configured with either PUCCH or PUSCH. The PHR type can be fixed to a specific PHR type (e.g., Type 1), or it can be configured to / instruct the UE to use a specific type between Type 1 and Type 3. Furthermore, the UE can be configured / instructed to always send the PHR as a virtual PHR or to send both a virtual PHR and a real PHR.

[0385] Multiple L-cells or U-cells can be configured for the UE. Additionally, both NUL and SUL carriers can be configured in a specific cell, and PUSCH or PUCCH transmission can be configured in at least one of these two carriers. In this case, PHR reports for all cells / CCs configured for the UE can be sent via CG-PUSCH transmitted in the U cell. If PUSCH or PUCCH transmission is configured only in one of the NUL or SUL carriers, the UE can send only the PHR for the carrier used to configure PUSCH or PUCCH transmission.

[0386] Alternatively, even if the PUSCH transmission is configured for both SUL and NUL carriers, a PHR may be sent only for the previously configured / indicated / defined carrier. Alternatively, a PHR may be sent only for a specific carrier among the two carriers used to configure the PUSCH or PUCCH transmission, and information about the carrier corresponding to the sent PHR may be communicated to the BS via CG-UCI or MAC CE.

[0387] The embodiments of this disclosure described herein are combinations of the elements and features of this disclosure. Unless otherwise stated, these elements or features may be considered optional. Each element or feature may be practiced without combination with other elements or features. Additionally, embodiments of this disclosure may be constructed by combining portions of elements and / or features. The order of operations described in the embodiments of this disclosure may be rearranged. Some constructions of any embodiment may be included in another embodiment and may be replaced by corresponding constructions of another embodiment. It will be apparent to those skilled in the art that claims not expressly referenced in the appended claims may be presented in combination as embodiments of this disclosure, or may be included as new claims by subsequent amendments made after filing the application.

[0388] In this disclosure, in some cases, specific operations described as being performed by the BS can also be performed by upper-layer nodes of the BS. That is, it is obvious that in a network consisting of multiple network nodes including the BS, various operations performed for communication with the MS can be performed by the BS or network nodes other than the BS. The term "BS" can be replaced by the terms "fixed station," "node B," "enhanced node B (eNodeB or eNB)," "access point," etc.

[0389] Those skilled in the art will understand that this disclosure can be performed in other specific ways than those described herein without departing from the spirit and essential characteristics of this disclosure. Therefore, the above embodiments are to be interpreted in all respects as illustrative and not restrictive. The scope of this disclosure should be determined by the appended claims and their legal equivalents, not by the foregoing description, and all variations falling within the meaning and equivalence of the appended claims should be included therein.

[0390] Industrial applicability

[0391] Although the above-described method and apparatus for transmitting and receiving PUSCH within a COT have been described based on an example applied to a 5G NR system, the method and apparatus can be applied to various wireless communication systems in addition to 5G NR systems.

Claims

1. A method comprising: The User Equipment (UE) transmits a configured Granted Physical Uplink Shared Channel (CG-PUSCH) based on a first energy detection threshold, wherein the CG-PUSCH includes configured Granted Uplink Control Information (CG-UCI) related to the configuration of the first energy detection threshold, and the channel occupancy initiated by the UE is shared with the Base Station (BS); and The UE transmits the CG-PUSCH based on a second energy detection threshold, wherein the CG-PUSCH includes a CG-UCI associated with the absence of a first energy detection threshold, and for a transmission duration of no more than two symbols for a subcarrier spacing of 15 kHz, the channel occupancy initiated by the UE is shared with the BS. The first energy detection threshold is received through higher-level parameters, and the second energy detection threshold is received from the BS.

2. The method according to claim 1, further comprising: The UE performs Listen-Before-Speak (LBT) based on either the first or the second energy detection threshold. The PUSCH is sent based on the result of executing the LBT.

3. A user equipment (UE), comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform operations including: The UE transmits a configured Granted Physical Uplink Shared Channel (CG-PUSCH) based on a first energy detection threshold, wherein the CG-PUSCH includes configured Granted Uplink Control Information (CG-UCI) related to the configured first energy detection threshold, and the channel occupancy initiated by the UE is shared with the base station (BS); and The UE transmits the CG-PUSCH based on a second energy detection threshold, wherein the CG-PUSCH includes a CG-UCI associated with the absence of a first energy detection threshold, and for a transmission duration of no more than two symbols for a subcarrier spacing of 15 kHz, the channel occupancy initiated by the UE is shared with the BS. The first energy detection threshold is received through higher-level parameters, and the second energy detection threshold is received from the BS.

4. The UE according to claim 3, in, The operation further includes: the UE performing Listen-Before-Speak (LBT) based on the first energy detection threshold or the second energy detection threshold, and The PUSCH is sent based on the result of executing the LBT.

5. A computer-readable storage medium comprising at least one computer program that causes at least one processor to perform operations, the operations including: The User Equipment (UE) transmits a configured Granted Physical Uplink Shared Channel (CG-PUSCH) based on a first energy detection threshold, wherein the CG-PUSCH includes configured Granted Uplink Control Information (CG-UCI) related to the configuration of the first energy detection threshold, and the channel occupancy initiated by the UE is shared with the Base Station (BS); and The UE transmits the CG-PUSCH based on a second energy detection threshold, wherein the CG-PUSCH includes a CG-UCI associated with the absence of a first energy detection threshold, and for a transmission duration of no more than two symbols for a subcarrier spacing of 15 kHz, the channel occupancy initiated by the UE is shared with the BS. The first energy detection threshold is received through higher-level parameters, and the second energy detection threshold is received from the BS.

6. A method comprising: The base station (BS) receives a configured permitted physical uplink shared channel (CG-PUSCH) based on a first energy detection threshold, wherein the CG-PUSCH includes configured permitted uplink control information (CG-UCI) related to the configuration of the first energy detection threshold, and the channel occupancy initiated by the user equipment (UE) is shared with the BS. The BS receives the CG-PUSCH based on a second energy detection threshold, wherein the CG-PUSCH includes a CG-UCI associated with the absence of a first energy detection threshold, and for transmission durations of no more than 2, 4, and 8 symbols for subcarrier spacings of 15 kHz, 30 kHz, and 60 kHz, the channel occupancy initiated by the UE is shared with the BS. The first energy detection threshold is received through higher-level parameters, and the second energy detection threshold is received from the BS.

7. A base station (BS), comprising: At least one transceiver; At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform operations including: The BS receives a configured permitted physical uplink shared channel (CG-PUSCH) based on a first energy detection threshold, wherein the CG-PUSCH includes configured permitted uplink control information (CG-UCI) related to the configuration of the first energy detection threshold, and the channel occupancy initiated by the user equipment (UE) is shared with the BS. The BS receives the CG-PUSCH based on a second energy detection threshold, wherein the CG-PUSCH includes a CG-UCI associated with the absence of a first energy detection threshold, and for transmission durations of no more than 2, 4, and 8 symbols for subcarrier spacings of 15 kHz, 30 kHz, and 60 kHz, the channel occupancy initiated by the UE is shared with the BS. The first energy detection threshold is received through higher-level parameters, and the second energy detection threshold is received from the BS.

Images