Method and apparatus for channel access switching in a wireless communication system

Abstract

The present disclosure provides methods and apparatus for channel access switching in a wireless communication system with or without listen before talk and / or with different types of efficient operation of listen before talk. An apparatus including a user equipment or a base station can determine whether and / or how to perform listen before talk for a transmission based on a characteristic of the transmission. The characteristic can be a resource allocation for the transmission. The characteristic can be a manner in which resources are allocated for the transmission. The characteristic can be a length or size of resources allocated for the transmission. The characteristic can be an amount of resources allocated for the transmission. The resource allocation can be a time domain resource allocation and / or a frequency domain resource allocation.

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 139,522, filed January 20, 2021, and U.S. Provisional Patent Application No. 63 / 139,538, filed January 20, 2021, the entire disclosure of each of which is incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for channel access switching in wireless communication systems with or without Listen-Before-Talk (LBT) and / or with LBTs of different types and efficient operation. Background Technology

[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate with Internet Protocol (IP) packets. This type of IP packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) new radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate the evolution and completion of the 3GPP standards. Summary of the Invention

[0006] This disclosure provides a method and apparatus for channel access switching in a wireless communication system with or without Listen-Before-Talk (LBT) and / or with different types of efficient LBT operation. The apparatus can determine whether and / or how to perform LBT for a transmission based on the characteristics of the transmission. Characteristics may include resource allocation for the transmission. Characteristics may include the manner in which resources are allocated for the transmission. Characteristics may include the length or size of the resources allocated for the transmission. Characteristics may include the amount of resources allocated for the transmission. Resource allocation may be time-domain resource allocation and / or frequency-domain resource allocation.

[0007] In various embodiments, the apparatus determines whether to perform LBT for a transmission based on the resource allocation for the transmission. The apparatus may determine whether to perform LBT for a transmission based on the amount of resources allocated for the transmission. When / when the resources allocated for the transmission are greater than a threshold, the apparatus may perform LBT for the transmission. When / when the resources allocated for the transmission are less than a threshold, the apparatus may not perform LBT for the transmission. The apparatus may be a user equipment (UE) or a base station.

[0008] Various embodiments provide a method for a base station to operate in a shared spectrum, comprising transmitting a Channel State Information Reference Signal (CSI-RS) on a first resource on the channel after sensing the channel, wherein the first resource is indicated by Downlink Control Information (DCI); and transmitting the CSI-RS on a second resource on the channel without sensing the channel, wherein the second resource is indicated by Radio Resource Control (RRC) configuration.

[0009] Various embodiments provide a method for a base station to operate in a shared spectrum, comprising performing LBT on a first resource for CSI-RS transmission, wherein the first resource is indicated by DCI; and not performing LBT on a second resource for CSI-RS, wherein the second resource is indicated by RRC configuration. Attached Figure Description

[0010] Figure 1 A diagram illustrating a wireless communication system according to an embodiment of the present invention is shown.

[0011] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention.

[0012] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention.

[0013] Figure 4 This is according to an embodiment of the present invention. Figure 3 Functional block diagram of the program code.

[0014] Figure 5 shows the TS 38.211V15.7.0. Figure 4 Reproduction of .3.1-1: Uplink-downlink timing relationship.

[0015] Figure 6This is a flowchart of a method for a base station / UE to determine whether and / or how to perform LBT for a transmission based on whether a previous transmission was successfully received, according to an embodiment of the present invention.

[0016] Figure 7 This is a flowchart of a method for a UE / base station to determine whether and / or how to perform LBT for a transmission based on the number of previously successfully received transmissions, according to an embodiment of the present invention.

[0017] Figure 8 This is a flowchart of a method for a UE / base station to determine whether and / or how to perform LBT for a transmission based on the ratio of previously successfully received transmissions, according to an embodiment of the present invention.

[0018] Figure 9 This is a flowchart of a method for a UE / base station to determine whether and / or how to perform an LBT for a transmission based on whether a previous LBT associated with a previous transmission was successful, according to an embodiment of the present invention.

[0019] Figure 10 This is a flowchart of a method for a UE / base station to determine whether and / or how to perform an LBT for a transmission based on the number of previously successful LBTs, according to an embodiment of the present invention.

[0020] Figure 11 This is a flowchart of a method for a UE / base station to determine whether and / or how to perform an LBT for a transmission based on the ratio of previously successful LBTs, according to an embodiment of the present invention.

[0021] Figure 12 This is a flowchart of a method for a UE to determine whether and / or how to perform LBT for a transmission, according to an embodiment of the present invention.

[0022] Figure 13 This is a flowchart of a method for a base station to determine whether and / or how to perform LBT for a transmission, according to an embodiment of the present invention.

[0023] Figure 14 This is a flowchart of a method for a base station to operate in a shared spectrum to transmit CSI-RS on a first resource on a channel after sensing the channel, according to an embodiment of the present invention.

[0024] Figure 15 This is a flowchart of a method for a base station to perform LBT on a first resource for CSI-RS transmission in a shared spectrum, according to an embodiment of the present invention. Detailed Implementation

[0025] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that, based on the disclosed information, those skilled in the art can readily make adaptations for use and implementation of various aspects of the invention in 3GPP2 network architectures and other network architectures.

[0026] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation techniques.

[0027] Specifically, the exemplary wireless communication systems and apparatus described below may be designed to support one or more standards, such as those provided by the association known as the "3rd Generation Partnership Project" (referred to herein as 3GPP), including: [1] 3GPP TS 38.211 V15.7.0, "NR Physical Channels and Modulation"; [2] draft 3GPP TS 37.213 V16.4.0, "NR Physical Layer Procedures for Shared Spectrum Channel Access"; [3] RP-202925, "Revised WID: Extending Current NR Operation to 71 GHz"; and [4] 3GPP TS 38.214 V16.4.0, "NR Physical Layer Procedures for Data". The standards and documents listed above are hereby expressly and entirely incorporated herein by reference.

[0028] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one antenna group comprising 104 and 106, another antenna group comprising 108 and 110, and yet another antenna group comprising 112 and 114. Figure 1In this diagram, only two antennas are shown for each antenna group, but each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, forward link 120 can use a different frequency than the frequency used by reverse link 118.

[0029] Each antenna group and / or the area in which the antenna groups are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by the access network 100.

[0030] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, an access network using beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in neighboring cells.

[0031] AN can refer to a fixed station or base station used for communication with terminals, and may also be called an access point, Node B, base station, enhanced base station, eNodeB, or some other term. AT can also be called User Equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0032] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for several data streams is provided from the data source 212 to the transport (TX) data processor 214.

[0033] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data stream based on a specific decoding scheme selected for each data stream to provide decoded data.

[0034] OFDM technology can be used to multiplex the decoded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for said data stream are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. The data rate, decoding, and modulation for each data stream can be determined by instructions executed by processor 230.

[0035] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to symbols of the data stream and the antennas from which the symbols are transmitted.

[0036] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and up-converts) the analog signals to provide modulated signals suitable for transmission via a MIMO channel. Then, from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0037] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the received signal from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.

[0038] The RX data processor 260 then uses specific receiver processing technology from N R Each receiver receives and processes N data. ROne received symbol stream to provide N T Each detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data of the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0039] Processor 270 periodically determines which pre-decoding matrix to use (discussed below). Processor 270 formulates a reverse link message including a matrix index portion and a rank portion.

[0040] The reverse link message may include various types of information related to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0041] At transmitter system 210, the modulated signal from receiver system 250 is received via antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted through receiver system 250. Next, processor 230 determines which pre-decoding matrix to use to determine beamforming weights and then processes the extracted message.

[0042] Memory 232 can be used to temporarily store some buffered / calculated data from processor 240 or 242 via processor 230, some buffered data from 212, or some specific program code. Furthermore, memory 272 can be used to temporarily store some buffered / calculated data from processor 260 via processor 270, some buffered data from 236, or some specific program code.

[0043] Turn Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, this can be achieved using the communication device 300 in a wireless communication system. Figure 1The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals to pass the received signals to the control circuit 306 and wirelessly output signals generated by the control circuit 306.

[0044] Figure 4 This is according to an embodiment of the present invention. Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connections.

[0045] For LTE, LTE-A, or NR systems, Layer 2, Part 404 may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. Layer 3, Part 402 may include a Radio Resource Control (RRC) layer.

[0046] Any two or more of the following paragraphs, (sub)bullets, points, actions, or claims described in each invention may be logically, reasonably, and appropriately combined to form a particular method.

[0047] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following inventions may be implemented independently and separately to form a particular method. Dependencies in the following inventions (e.g., "based on," "more specifically," etc.) are merely possible embodiments that do not limit a particular method.

[0048] The frame structure is used in the new RAT (NR) for 5G to accommodate various types of time and frequency resource requirements (e.g., TS 38.211 V15.7.0, [1]), ranging from ultra-low latency (approximately 0.5ms) to latency-tolerant services for MTC, and from high peak rates for eMBB to extremely low data rates for MTC. A key focus of this study is low latency aspects, such as short TTI, while other aspects of mixing / adapting different TTIs may also be considered in the study. In addition to different services and requirements, forward compatibility is also an important consideration in the initial NR frame structure design, as not all NR features are included in the initial phase / version.

[0049] Reducing latency is a significant improvement across different generations / versions of the protocol, enhancing efficiency and meeting new application requirements, such as real-time services. A frequently used and effective method to reduce latency is to shorten the TTI (Time Interval) length, from 10ms in 3G to 1ms in LTE.

[0050] When NR is involved, the situation becomes somewhat different because backward compatibility is not always necessary. The underlying parameters can be adjusted so that reducing the number of symbols in the TTI is not the only tool for changing the TTI length. Using LTE underlying parameters as an example, which include 14 OFDM symbols in 1 ms and a subcarrier spacing of 15 kHz, when the subcarrier spacing is changed to 30 kHz, under the assumption of the same FFT size and the same CP structure, there will be 28 OFDM symbols in 1 ms. With the number of OFDM symbols in the TTI remaining the same, the TTI effectively becomes 0.5 ms. This means that designs with different TTI lengths can be maintained in conjunction with good scalability implemented on the subcarrier spacing. Of course, there will always be trade-offs for the choice of subcarrier spacing, such as FFT size, the definition / number of PRBs, CP design, and supported system bandwidth. When NR considers larger system bandwidth and larger coherence bandwidth, including a larger subcarrier spacing is a natural choice.

[0051] More details on the design of the NR frame structure, channels and basic parameters are given below based on [1] 3GPP TS 38.211 V15.7.0.

[0052] **********************Start of quotation********************************

[0053] 4-frame structure and physical resources

[0054] 4.1 Overview

[0055] Throughout this specification, unless otherwise specified, the magnitudes of the fields in the time domain are expressed in time units T. c =1 / (Δf) max ·N f ), where Δf max =480·10 3 Hz and N f =4096. Constant κ = T s / T c =64, where T s =1 / (Δf) ref ·N f,ref ), Δf ref =15·10 3 Hz and N f,ref =2048.

[0056] 4.2 Basic Parameters

[0057] As shown in Table 4.2-1, multiple OFDM basic parameters are supported, where μ and the cyclic prefix used for the bandwidth part are obtained from the higher-level parameters subcarrierSpacing and cyclicPrefix, respectively.

[0058] Table 4.2-1: Supported basic transmission parameters.

[0059] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 normal 1 30 normal 2 60 Normal, Extended 3 120 normal 4 240 normal

[0060] 4.3 Frame Structure

[0061] 4.3.1 Frames and Subframes

[0062] Downlink and uplink transmissions are organized into a T f =(Δf max N f / 100)·T c = A frame with a duration of 10ms, each frame consisting of T sf =(Δf max N f / 1000)·T c It consists of ten subframes with a duration of 1 ms. The number of consecutive OFDM symbols in each subframe is... Each frame is divided into two equal half-frames consisting of five subframes, each having half-frame 0 composed of subframes 0-4 and half-frame 1 composed of subframes 5-9.

[0063] On a carrier, there is one set of frames in the uplink and one set of frames in the downlink.

[0064] The uplink frame number i used to transmit from the UE will be T before the start of the corresponding downlink frame at the UE. TA =(NTA +N TA,offset )T c Beginning, where N TA,offset Given by [5, TS 38.213].

[0065] Figure 5 shows the TS 38.211V15.7.0. Figure 4 Reproduction of .3.1-1: Uplink-downlink timing relationship.

[0066] 4.3.2 Time Slot

[0067] For the subcarrier spacing configuration μ, the time slots are numbered in ascending order within the subframe. And numbered in ascending order within the frame as follows Existing in time slots 1 consecutive OFDM symbol, of which Depending on the cyclic prefix given in Tables 4.3.2-1 and 4.3.2-2. Time slots in subframes. The beginning is temporally related to the OFDM symbol in the same subframe. Align the beginnings.

[0068] OFDM symbols in a time slot can be classified as 'downlink', 'flexible', or 'uplink'. The signaling of the time slot format is described in section 11.1 of [5, TS38.213].

[0069] In the time slots of a downlink frame, the UE will assume that downlink transmissions only occur in the 'downlink' or 'flexible' symbols.

[0070] In the time slots of this uplink frame, the UE will only transmit in the 'uplink' or 'flexible' symbols.

[0071] Full-duplex communication is not possible in all cells within the cell group, and simultaneous transmission and reception as defined by parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306] are not supported. A UE expects to transmit in the uplink in one cell within the cell group no earlier than the end of the last received downlink symbol in the same or different cells within the cell group, where N... Rx-Tx As given in Table 4.3.2-3.

[0072] Full-duplex communication is not possible across all cells within the cell group, and simultaneous transmission and reception as defined by parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306] are not supported. The UE expects to receive downlink data in one cell within the cell group no earlier than the end of the last transmitted uplink symbol in the same or different cells within the cell group. Tx-Rx T c , where N Tx-Rx As given in Table 4.3.2-3.

[0073] UEs incapable of full-duplex communication are expected to transmit in the uplink no earlier than the end of the last received downlink symbol in the same cell. Rx-Tx T c , where N Rx-Tx As given in Table 4.3.2-3.

[0074] UEs incapable of full-duplex communication are expected to receive downlink signals no earlier than the end of the last transmitted uplink symbol in the same cell after N. Tx-Rx T c , where N Tx-Rx As given in Table 4.3.2-3.

[0075] Table 4.3.2-1: Number of OFDM symbols per slot, number of slots per frame, and number of slots per subframe used for normal cyclic prefix.

[0076]

[0077] Table 4.3.2-2: Number of OFDM symbols per slot, per frame slot, and per subframe slot used for extending the cyclic prefix.

[0078]

[0079] Table 4.3.2-3: Transition Time N Rx-Tx and N Tx-Rx

[0080] Transition Time FR1 FR2 <![CDATA[N Tx-Rx ]]> 25600 13792 <![CDATA[N Rx-Tx ]]> 25600 13792

[0081] 4.4 Physical Resources

[0082] 4.4.5 Bandwidth Section

[0083] The bandwidth portion is the given fundamental parameter μ in the bandwidth portion i on a given carrier, as defined in section 4.4.4.3. iA subset of contiguous common resource blocks. The start position in the bandwidth portion. and the number of resource blocks They should be satisfied respectively and The bandwidth configuration is described in section 12 of [5, TS 38.213].

[0084] The UE can be configured to use up to four bandwidth portions in the downlink, with a single downlink bandwidth portion being active at any given time. The UE does not expect to receive PDSCH, PDCCH, or CSI-RS (except RRM) outside of the active bandwidth portion.

[0085] The UE can be configured to use up to four bandwidth portions in the uplink, with a single uplink bandwidth portion active at any given time. When the UE is configured to use supplementary uplink, it can also be configured to use up to four additional bandwidth portions in the supplementary uplink, with a single supplementary uplink bandwidth portion active at any given time. The UE should not transmit PUSCH or PUCCH outside of the active bandwidth portion. For active cells, the UE should not transmit SRS outside of the active bandwidth portion.

[0086] Unless otherwise stated, the descriptions in this specification apply to each of the bandwidth sections. When there is no risk of confusion, the index μ can be obtained from... and Omitted in .

[0087] 4.5 Carrier Aggregation

[0088] It can aggregate transmissions from multiple cells. Unless otherwise specified, the description in this specification applies to each of the serving cells.

[0089] ***************************End of quotation*********************************

[0090] When access does not require a licensed spectrum (e.g., shared spectrum), mechanisms may be needed to determine whether a device (e.g., a UE or base station / access node) can access the spectrum (e.g., perform a transmission) to ensure fairness for all devices on the spectrum. For example, a device can detect / receive signals on the spectrum / serving cell to determine if the spectrum is available. When a device, for example, does not detect a signal or is silent for a period of time, it can consider the spectrum available and perform a transmission. On the other hand, when a device detects signals on the spectrum, for example, signals of a specific strength from other devices, it can consider the spectrum currently occupied and prevent its transmission. This mechanism can be called listen-before-talk (LBT). Further details regarding how LBT is performed may exist, such as the threshold at which the device determines if the channel is currently occupied (e.g., the device can consider a weak signal as silent), the timing of detection when the device fails to perform an LBT test, and / or the timing and / or the manner of performing another test of detection. Further details of the channel access scheme can be found in the following draft 3GPP TS 37.213 V16.4.0 [2]:

[0091] ***************************Start of quotation*******************************

[0092] 4-channel access procedure

[0093] 4.0 Overview

[0094] Unless otherwise specified, the definitions below may be applied to the terms used in this specification:

[0095] A channel is a carrier or a portion thereof, consisting of a continuous set of resource blocks (RBs) on which channel access procedures are performed in a shared spectrum.

[0096] The channel access procedure is a sensing-based procedure for evaluating the availability of a channel used to perform transmissions. The basic unit for sensing is a sensing time slot, which has a duration T. sl =9us. When the eNB / gNB or UE senses the channel during the sensing slot duration, the sensing slot duration T... sl It is considered idle, and it is determined that the power detected is less than the energy detection threshold X within at least 4 µs of the sensing time slot duration. Thresh In other cases, the sensing time slot duration T sl They are considered busy.

[0097] - Channel occupancy refers to the transmission of data on the channel by the eNB / gNB / UE after the corresponding channel access procedure in this chapter is executed.

[0098] - Channel occupancy time refers to the total time that the eNB / gNB / UE and any shared channel occupancy eNB / gNB / UE perform transmissions on the channel after the eNB / gNB / UE executes the corresponding channel access procedure described in this section. To determine channel occupancy time, the interval duration is counted within the channel occupancy time if the transmission interval is less than or equal to 25 µs. Shared channel occupancy time is available for transmissions between the eNB / gNB and the corresponding UE.

[0099] - A DL transmission burst is defined as a group of transmissions from an eNB / gNB that does not have any gaps greater than 16µs. Transmissions from an eNB / gNB separated by gaps greater than 16µs are considered separate DL transmission bursts. The eNB / gNB may transmit transmissions after gaps within a DL transmission burst without sensing the availability of the corresponding channel.

[0100] - A UL transmission burst is defined as a group of transmissions from a UE that do not have any gaps greater than 16µs. Transmissions from a UE separated by gaps greater than 16µs are considered separate UL transmission bursts. The UE can transmit transmissions after gaps within a UL transmission burst without sensing the availability of the corresponding channel.

[0101] - A discovery burst refers to a DL transmission burst that comprises a set of signals and / or channels confined within a window and associated with a duty cycle. A discovery burst can be any of the following:

[0102] - Transmissions initiated by the eNB include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS), and may include a non-zero power CSI reference signal (CSI-RS).

[0103] - A transmission initiated by a gNB includes at least an SS / PBCH block consisting of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH) with an associated demodulation reference signal (DM-RS). It may also include a CORESET for PDCCH that schedules PDSCH with SIB1, and a PDSCH carrying SIB1 and / or a non-zero power CSI reference signal (CSI-RS).

[0104] 4.1 Downlink Channel Access Procedure

[0105] eNBs operating LAA Scells on the channel and gNBs performing transmissions on the channel should execute the channel access procedures described in this section for accessing the channel performing the transmission.

[0106] In this section, where applicable, X is used for sensing. Thresh It has been adjusted to be as described in Section 4.1.5.

[0107] The gNB executes the channel access procedure in this section unless the higher-layer parameter ChannelAccessMode-r16 is provided and ChannelAccessMode-r16 = 'semi-static'.

[0108] 4.1.1 Type 1DL Channel Access Procedure

[0109] This section describes the channel access procedure to be performed by the eNB / gNB, where the duration spanned by the sensing slots sensed as idle prior to downlink transmission is random. This section applies to the following transmissions:

[0110] - Transmissions initiated by the eNB containing PDSCH / PDCCH / EPDCCH, or

[0111] - A transmission initiated by a gNB, which includes a unicast PDSCH with user plane data, or a unicast PDSCH with user plane data and a unicast PDCCH scheduling user plane data, or

[0112] - A transmission initiated by a gNB that has only a burst detection capability or a burst detection capability that has multiplexed non-unicast information, wherein the transmission duration is greater than 1 ms or the transmission causes the burst detection cycle to exceed 1 / 20.

[0113] eNB / gNB can delay the duration T d Transmission is transmitted after the channel is first sensed as idle during the sensing time slot duration and after counter N reaches zero in step 4. The counter N is adjusted by sensing the channel for an additional sensing time slot duration according to the following steps:

[0114] 1) Set N = N init , where N init For 0 and CW p A random number is uniformly distributed between them, and then proceed to step 4;

[0115] 2) If N>0 and eNB / gNB is selected to decrement the counter, then set N=N-1;

[0116] 3) Sensing the channel during the additional sensing time slot duration, and if the additional sensing time slot duration is idle, proceed to step 4; otherwise, proceed to step 5.

[0117] 4) If N = 0, stop; otherwise, go to step 2.

[0118] 5) Sensing channel until the additional delay duration T d The system detects either a busy sensing slot or an additional delay duration T. d All sensing time slots are idle;

[0119] 6) If the additional delay duration T d If the sensing channel is idle during all sensing time slot durations, proceed to step 4; otherwise, proceed to step 5.

[0120] If the eNB / gNB has not yet transmitted after step 4 of the above procedure, if when the eNB / gNB is ready to transmit, at least for the sensing time slot duration T... sl The middle channel is sensed to be idle and if the delay duration T immediately preceding this transmission... d If the channel has been sensed as idle during all sensing time slot durations, the eNB / gNB can transmit on the channel. If, after the eNB / gNB is ready to transmit, it senses the channel first during time slot duration T... sl The channel has not yet been sensed to be idle, or if a delay duration T immediately precedes this predetermined transmission. d If the channel is not idle during any sensing time slot duration, then during the delay duration T d After the sensing channel is idle during the duration of the sensing time slot, the eNB / gNB proceeds to step 1.

[0121] Delay duration T d From immediately following mp Continuous sensing time slot duration T sl The subsequent duration T f =16us, and T f Included in T f The duration T of the idle sensing slot at the beginning sl .

[0122] CW min,p ≤CW p ≤CW max,p For the competitive window. CW p The adjustment is described in Section 4.1.4.

[0123] Before step 1 of the above procedure, select CW. min,p and CW max,p .

[0124] m p CW min,p and CW max,p It is based on the channel access priority class p associated with eNB / gNB transmission, as shown in Table 4.1.1-1.

[0125] When the channel occupancy time exceeds T mcot,p In the case of eNB / gNB, the eNB / gNB will not transmit on the channel. In this case, the channel access procedure is performed based on the channel access priority class p associated with the eNB / gNB transmission, as shown in Table 4.1.1-1.

[0126] If the eNB / gNB transmits a discovery burst as described in Section 4.1.2 when N>0 in the above procedure, the eNB / gNB will not decrement N during the duration of the sensing time slot that overlaps with the discovery burst.

[0127] gNB can use any channel access priority class that meets the conditions described in this section for performing the above procedures to transmit transmissions that include burst detection.

[0128] The gNB should use the channel access priority class applicable to unicast user plane data multiplexed in the PDSCH to perform the above procedure for transmitting unicast PDSCH containing user plane data.

[0129] For p=3 and p=4, if any other technique can guarantee the absence of a shared channel on a long-term basis (e.g., by adjusting the level), then T mcot,p =10ms; otherwise, T mcot,p =8ms.

[0130] Table 4.1.1-1: Channel Access Priority Class (CAPC)

[0131]

[0132] 4.1.1.1 Regional limitations on channel occupancy time

[0133] In Japan, if the eNB / gNB has already transmitted after N=0 in step 4 of the above procedure, then the eNB / gNB can transmit up to T. j The next consecutive transmission is transmitted within a duration of 4ms, immediately following at least T. js After the sensing channel is idle within a 34µs sensing interval, and if the total sensing and transmission time does not exceed [a certain threshold], [the process continues]. Sensing interval T js The duration T immediately following the two sensing time slots f =16us, and T f Included in T f The idle sensing time slot at the beginning. The channel is sensed as during the sensing time slot duration T. js During the period of idle time, it is considered that the idle time reaches T. js .

[0134] 4.1.2 Type 2DL Channel Access Procedure

[0135] This section describes the channel access procedure to be performed by the eNB / gNB, where the duration of the sensing slots that are sensed as idle before downlink transmission is deterministic.

[0136] If the eNB performs a Type 2DL channel access procedure, it follows the procedure described in Section 4.1.2.1.

[0137] The Type 2A channel access procedure as described in Section 4.1.2.1 applies to the following transmissions performed by the eNB / gNB:

[0138] - Transmissions initiated by the eNB, which include burst detection but do not include PDSCH, wherein the transmission duration is at most 1ms, or

[0139] - A transmission initiated by a gNB that has either only a burst detection capability or a burst detection capability multiplexed with non-unicast information, wherein the transmission duration is at most 1 ms and the burst detection cycle is at most 1 / 20, or

[0140] - After the UE's transmission, the eNB / gNB transmission follows a 25µs gap in the shared channel occupancy as described in Section 4.1.3.

[0141] The Type 2B or Type 2C DL channel access procedures, as described in Sections 4.1.2.2 and 4.1.2.3 respectively, are applicable to transmissions performed by the gNB after a UE transmission, following a gap of 16 µs or at most 16 µs in shared channel occupancy as described in Section 4.1.3.

[0142] 4.1.2.1 Type 2A DL Channel Access Procedure

[0143] eNB / gNB can be immediately followed by a sensing channel that is idle for at least one sensing interval T. short_dl =25us later, DL transfer will begin. T short_dl The duration T immediately following a sensing time slot f =Composed of 16us, including the initial sensing time slot. If T short_dl If both sensing slots are detected as idle, then the channel is considered idle for T seconds. short_dl .

[0144] 4.1.2.2 Type 2B DL ​​Channel Access Procedure

[0145] gNB can be used in T f The DL transmission occurs immediately after the sensing channel becomes idle, within a duration of 16µs. f Included in T f The sensing time slot is performed within the last 9 µs. If the channel is sensed as idle for a total of at least 5 µs, and at least 4 µs of sensing is performed in the sensing time slot, then the channel is considered idle for a duration T. f The inside is considered free.

[0146] 4.1.2.3 Type 2C DL Channel Access Procedure

[0147] When the gNB follows the procedures in this section to transmit DL transmissions, the gNB does not sense the channel before transmitting the DL transmission. The duration of the corresponding DL transmission is at most 584 µs.

[0148] 4.1.4 Competition Window Adjustment Procedure

[0149] If the eNB / gNB transmits a PDSCH on the channel that is associated with the channel access priority class p, then the eNB / gNB maintains a contention window value CW for such transmissions as described in this section. p And adjust CW before step 1 of the procedure described in Section 4.1.1. p .

[0150] 4.1.4.2 Contention Window Adjustment Procedure for DL ​​Transmissions in gNB

[0151] If the gNB transmits a PDSCH on the channel that is associated with the channel access priority class p, then the gNB maintains a contention window value CW for those transmissions. p And adjust CW using the following steps before step 1 of the procedure described in Section 4.1.1. p :

[0152] 1) For each priority class p∈{1,2,3,4}, set CW p =CW min,p .

[0153] 2) If HARQ-ACK feedback is in CW p If the last update is available, proceed to step 3. Otherwise, if the gNB transfer following the procedure described in Section 4.1.1 does not include a retransmission or in CW... p The last update is the duration T from the end of the reference duration corresponding to the earliest DL channel occupancy. w If the data is transferred internally, proceed to step 5; otherwise, proceed to step 4.

[0154] 3) HARQ-ACK feedback is used for the reference duration of the latest available DL channel occupancy, corresponding to the PDSCH, as follows:

[0155] a. If at least one HARQ-ACK feedback is 'ACK' for a PDSCH with transport block-based feedback, or at least 10% of the HARQ-ACK feedback is 'ACK' for a PDSCH CBG transmitted at least partially on a channel with code block group-based feedback, then proceed to step 1; otherwise, proceed to step 4.

[0156] 4) For each priority class p∈{1,2,3,4}, CW p Increase to the next higher allowed value.

[0157] 5) For each priority class p∈{1,2,3,4}, CW p Leave it as is; proceed to step 2.

[0158] The reference duration and duration T in the above procedure w Defined as follows:

[0159] - The reference duration corresponding to a channel occupancy initiated by a gNB that includes PDSCH transmission is defined in this section as the duration from the start of the channel occupancy until the end of the first time slot in which at least one unicast PDSCH is transmitted on all resources allocated for the PDSCH, or until the end of the first transmission burst of the gNB containing unicast PDSCH transmitted on all resources allocated for the PDSCH (whichever occurs earlier). If the channel occupancy contains unicast PDSCH, but does not contain any unicast PDSCH transmitted on all resources allocated for said PDSCH, then the duration of the gNB's first transmission burst within the channel occupancy containing unicast PDSCH is the reference duration for CWS adjustment.

[0160] -T w =max(T) A ,T B +1ms), where T B T is the duration of the transmission burst starting from the reference duration in milliseconds, and if no other technique can guarantee the absence of a shared channel on a long-term basis, then T A =5ms; otherwise, T A =10ms.

[0161] If the gNB transmits a transmission on the channel using a Type 1 channel access procedure associated with channel access priority class p and the transmission is not associated with explicit HARQ-ACK feedback from the corresponding UE, then the gNB uses the latest CW for any DL transmission on the channel using a Type 1 channel access procedure associated with channel access priority class p. p Adjust CW before step 1 in the procedure described in section 4.1.1. p If the corresponding channel access priority class p has not yet been used for any DL transmission on the channel, then CW is used. p =CW min,p .

[0162] 4.1.4.3 Commonly Used Procedures for CWS Adjustment in DL Transmission

[0163] The following applies to the procedures described in Sections 4.1.4.1 and 4.1.4.2:

[0164] -If CW p =CW max,p This is used to adjust CW p The next higher allowed value is CW max,p .

[0165] -If CW p =CW max,p Used K times consecutively to generate N init Then CWp Reconfigured to CW only for priority class p min,p CW p =CW max,p p is used K times consecutively to generate N. init K is selected from a set of values ​​{1,2,…,8} for each priority class p∈{1,2,3,4} via eNB / gNB.

[0166] 4.1.5 Energy detection threshold adaptation program

[0167] eNBs / gNBs accessing the channels on which they perform transmissions should set the energy detection threshold (X). Thresh Set to less than or equal to the maximum energy detection threshold X Thresh_max .

[0168] X Thresh_max The following is determined:

[0169] -If a technology can guarantee, for example, that no other shared channels exist in the long term on a regulatory basis, then:

[0170] -

[0171] -X r It is the maximum energy detection threshold defined by the regulatory requirements in dBm when such requirements are defined; otherwise, X r =T max +10dB;

[0172] -otherwise,

[0173] -

[0174] in:

[0175] - For transmissions containing discovery bursts as described in Section 4.1.2, T A =5dB, and in other cases, T A =10dB;

[0176] -P H =23dBm;

[0177] -P TX It is the set maximum eNB / gNB output power in dBm for the channel;

[0178] - Regardless of whether single-channel or multi-channel transmission is used, eNB / gNB uses the set maximum transmission power on a single channel.

[0179] -T max(dBm)=10·log 10(3.16228·10 -8 (mW / MHz)·BWMHz(MHz));

[0180] -BWMHz is the bandwidth of a single channel in MHz.

[0181] 4.2 Uplink Channel Access Procedure

[0182] The UE performing transmissions on the LAA Scell, the eNB that schedules or configures UL transmissions for the UE performing transmissions on the LAA Scell, and the gNB that schedules or configures UL transmissions for the UE performing transmissions on the channel shall perform the procedures described in this section for the UE to access the channel performing the transmissions.

[0183] In this section, transmissions from the UE are treated as individual UL transmissions, regardless of whether there are gaps between transmissions, and the X-axis used for sensing is adjusted as described in Section 4.2.3 where applicable. Thresh .

[0184] The UE executes the channel access procedure in this section unless the higher-layer parameter ChannelAccessMode-r16 is provided and ChannelAccessMode-r16 = 'semi-static'.

[0185] If the UE fails to access the channel before the predetermined UL transmission to the gNB, Layer 1 notifies the higher layers of the channel access failure.

[0186] 4.2.1 Channel access procedure for uplink transmission

[0187] The UE may access the UL transmitted channel according to either the Type 1 or Type 2 UL channel access procedure. The Type 1 channel access procedure is described in Section 4.2.1.1. The Type 2 channel access procedure is described in Section 4.2.1.2.

[0188] If the UL that schedules the PUSCH transmission grants indication of a Type 1 channel access procedure, the UE shall use the Type 1 channel access procedure for transmitting transmissions that include the PUSCH transmission, unless otherwise stated in this section.

[0189] The UE should use a Type 1 channel access procedure for transmitting on configured UL resources that include autonomous or configured PUSCH transmissions, unless otherwise stated in this section.

[0190] If the UL that schedules the PUSCH transmission grants indication of a Type 2 channel access procedure, the UE should use the Type 2 channel access procedure for transmissions that include the PUSCH transmission, unless otherwise stated in this section.

[0191] The UE should use the Type 1 channel access procedure for transmitting SRS transmissions that do not include PUSCH transmissions. The UL channel access priority class p=1 in Table 4.2.1-1 is used for SRS transmissions that do not include PUSCH.

[0192] If SRS is triggered but the PUCCH transmission of the DL allocation indication type 2 channel access procedure is not scheduled, the UE should use the type 2 channel access procedure.

[0193] If the UE is scheduled by the eNB / gNB to transmit PUSCH and SRS in adjacent transmissions without any gap between them, and if the UE cannot access the channel used for PUSCH transmission, the UE should attempt to transmit SRS according to the uplink channel access procedure specified for SRS transmission.

[0194] If the UE is scheduled by the gNB to transmit a PUSCH and one or more SRSs via a single UL in a non-adjacent transmission, or if the UE is scheduled by the gNB to transmit a PUCCH and / or SRS via a single DL in a non-adjacent transmission, then the UE should use the channel access procedure indicated by the scheduling DCI for the first UL transmission scheduled by the scheduling DCI. If the UE senses that the channel is continuously idle after it has stopped transmitting the first transmission, the UE can use a Type 2 channel access procedure or a Type 2A UL channel access procedure to transmit other UL transmissions scheduled by the scheduling DCI without applying CP extension, provided that the other UL transmissions are within the gNB channel occupancy period. Otherwise, if the UE senses that the channel is not continuously idle or that the other UL transmissions are outside the gNB channel occupancy period after it has stopped transmitting the first UL transmission, the UE can use a Type 1 channel access procedure to transmit other UL transmissions without applying CP extension.

[0195] The UE shall use the Type 1 channel access procedure for PUCCH transmission unless otherwise stated in this section. If the DL grants or the random access response (RAR) message for the successRAR used to schedule PUCCH transmission, as determined in Section 9.2.3 of [7, TS38.213], indicates a Type 2 channel access procedure, the UE shall use the Type 2 channel access procedure.

[0196] When a UE uses a Type 1 channel access procedure for PUCCH transmission or only PUSCH transmission without UL-SCH, the UE should use the UL channel access priority class p=1 in Table 4.2.1-1.

[0197] The UE shall use a Type 1 channel access procedure for PRACH and PUSCH transmissions that are not associated with a random access procedure for initiating channel occupancy. In this case, the UL channel access priority class p=1 in Table 4.2.1-1 is used for PRACH transmissions, and the UL channel access priority class used for PUSCH transmissions is determined according to Section 5.6.2 of [9].

[0198] When the UE uses the Type 1 channel access procedure for PUSCH transmission on configured resources, the UE follows the procedure described in Section 5.6.2 of [9] to determine the corresponding UL channel access priority p in Table 4.2.1-1.

[0199] When a UE uses a Type 1 channel access procedure for PUSCH transmission of user plane data that is indicated by the UL or associated with a random access procedure in which the corresponding UL channel access priority p is not indicated, the UE follows the same procedure as for PUSCH transmission on configuration resources when using a Type 1 channel access procedure to determine p in Table 4.2.1-1.

[0200] When a UE uses a Type 2A, Type 2B, or Type 2C UL channel access procedure for PUSCH transmissions that are authorized by the UL or associated with a random access procedure that does not indicate the corresponding UL channel access priority p, the UE uses a gNB with channel access priority class p=4 during the channel occupancy time.

[0201] UE should not exceed T ulmcot,p During the channel occupancy time, the data is transmitted on the channel, where the channel access procedure is executed based on the channel access priority class p associated with the UE transmission, as shown in Table 4.2.1-1.

[0202] As described in Section 4.1.3, if the UE sets the 'COT sharing indication' in the AUL-UCI to '1' in the subframe within the autonomous uplink transmission, then the total channel occupancy time of the autonomous uplink transmission obtained through the channel access procedure in this section (which includes the following DL transmissions) should not exceed T. ulmcot,p T ulmcot,p The information is given in Table 4.2.1-1.

[0203] Table 4.2.1-1: Channel Access Priority Class (CAPC) for UL

[0204]

[0205] 4.2.1.0 Channel Access Procedures and UL-Related Signaling

[0206] 4.2.1.0.0 Channel access procedure after detecting common DCI

[0207] If the UE detects the 'UL Duration and Offset' field in DCI Format 1C, as described in Section 5.3.3.1.4 of [5], then the following may apply:

[0208] - If the 'UL Duration and Offset' field indicates the 'UL Offset' l and 'UL Duration' d for subframe n, then the scheduled UE can use Channel Access Procedure Type 2 for transmission in subframe n+l+i, where i = 0, 1, ... d-1, regardless of the Channel Access Type signaled in the UL grant for those subframes, provided that the UE transmission ends in or before subframe n+l+d-1.

[0209] - If the 'UL Duration and Offset' field indicates the 'UL Offset' l and 'UL Duration' d of subframe n, and the 'COT Sharing Indication for AUL' field is set to '1', then a UE configured to use autonomous UL can use Channel Access Procedure Type 2 for autonomous UL transmission with any priority class in subframe n+l+i, where i = 0, 1, ... d-1, provided that the end of the UE's autonomous UL transmission occurs in or before subframe n+l+d-1, and the autonomous UL transmission between n+l and n+l+d-1 should be continuous.

[0210] - If the 'UL Duration and Offset' field indicates the 'UL Offset' l and 'UL Duration' d of subframe n, and the 'COT Sharing Indicator of AUL Field' is set to '0', then a UE configured to use autonomous UL should not transmit autonomous UL in subframe n+l+i, where i = 0, 1, ... d-1.

[0211] If the UE determines the duration in the time domain and the position in the frequency domain of the remaining channel occupancy initiated by the gNB according to DCI format 2_0, as described in section 11.1.1 of [7], then the following may apply:

[0212] - The UE may switch from a Type 1 channel access procedure as described in Section 4.2.1.1 to a Type 2A channel access procedure as described in Section 4.2.1.2.1 for its corresponding UL transmission within the determined time domain duration and frequency domain location of the remaining channel occupancy. In this case, if the UL transmission is transmitted via PUSCH on the configured resources, the UE may adopt any priority class for the channel occupancy shared with the gNB.

[0213] 4.2.1.0.2 Conditions for Maintaining Type 1 UL Channel Access Procedures

[0214] If the UE receives a UL grant indicating that PUSCH transmissions should be scheduled using a Type 1 channel access procedure, or a DL-assigned DCI indicating that PUCCH transmissions should be scheduled using a Type 1 channel access procedure, and if the UE has an ongoing Type 1 channel access procedure prior to the PUSCH or PUCCH transmission start time:

[0215] - If the UL channel access priority class value p1 used for the ongoing Type 1 channel access procedure is equal to or greater than the UL channel access priority class value p2 indicated in the DCI, the UE can transmit PUSCH in response to UL permission by using the ongoing Type 1 channel access procedure and accessing the channel.

[0216] - If the UL channel access priority class value p1 used for the ongoing Type 1 channel access procedure is less than the UL channel access priority class value p2 indicated in the DCI, the UE will terminate the ongoing channel access procedure.

[0217] - The UE may transmit PUCCH transmissions in response to DL approval by using the ongoing Type 1 channel access procedure and by accessing the channel.

[0218] 4.2.1.0.3 Conditions used to indicate the access procedure for Type 2 channels.

[0219] The eNB / gNB can respectively instruct the Type 2 channel access procedure in the DCI containing UL permission or DL ​​allocation scheduling transmission of PUSCH or PUCCH on the channel, as follows:

[0220] If the UL transmission starts at t0 and ends at t0+T CO If it is carried out within a time interval, then among them

[0221] -T CO =T mcot,p +T g ,

[0222] -t0 is the time at which the eNB / gNB begins transmission on the carrier according to the channel access procedure described in Section 4.1.1.

[0223] - T is determined by the eNB / gNB as described in Section 4.1.1 mcot,p value,

[0224] -T g It is the total duration of all gaps with a duration greater than 25µs that occur between DL transmissions of the eNB / gNB and UL transmissions scheduled by the eNB / gNB, as well as between any two UL transmissions scheduled by the eNB / gNB starting from t0.

[0225] thus,

[0226] - If the eNB / gNB has been transmitted on the channel according to the channel access procedure described in Section 4.1.1, the eNB / gNB may indicate the Type 2 channel access procedure in the DCI, or

[0227] - When the eNB has transmitted on the channel according to the channel access procedure described in Section 4.1.1, the eNB may use the 'UL Duration and Offset' field to indicate that the UE may perform a Type 2 channel access procedure for transmission including PUSCH on the channel in subframe n, or

[0228] - When the eNB has acquired the channel using the maximum priority class value and has transmitted on the channel according to the channel access procedure described in Section 4.1.1, the eNB may use the 'UL Duration and Offset' field and the 'COT Sharing Indication for AUL' field to indicate that a UE configured to use autonomous UL can perform a Type 2 channel access procedure for autonomous UL transmission including PUSCH on the channel in subframe n, and the eNB transmission includes PDSCH, or

[0229] -eNB / gNB can schedule UL transmission on the channel after a duration of 25us, which follows the transmission of eNB / gNB on the channel having a Type 2A channel access procedure for UL transmission, as described in Section 4.2.1.2.1.

[0230] If UL transmission can be scheduled continuously, then the eNB / gNB should schedule t0 and t0+T. CO UL transmissions between consecutive UL transmissions without gaps between them. For UL transmissions on the channel following a transmission on the channel using the Type 2A channel access procedure as described in Section 4.2.1.2.1 in the eNB / gNB, the UE may use the Type 2A channel access procedure for UL transmissions.

[0231] If the eNB / gNB indicates a Type 2 channel access procedure for the UE in the DCI, then the eNB / gNB indicates the channel access priority class used to obtain access to the channel in the DCI.

[0232] To indicate a Type 2 channel access procedure, if the gap is at least 25µs or equal to 16µs or at most 16µs, the gNB may indicate a Type 2A or Type 2B, or Type 2C UL channel procedure, as described in Section 4.2.1.2.

[0233] 4.2.1.0.4 Channel Access Procedure for UL Multichannel Transmission

[0234] If UE

[0235] -Scheduled for transmission on channel set C, and if the type 1 channel access procedure is authorized by the UL scheduling of the UL transmission on channel set C, and if the UL transmission is scheduled to start transmission simultaneously on all channels in channel set C, or

[0236] -Uplink transmission is scheduled to be performed on configured resources on channel set C with type 1 channel access procedures, and if UL transmission is configured to start transmission simultaneously on all channels in channel set C, and

[0237] If the channel frequencies of the channel set C are a subset of the set of channel frequencies defined in Section 5.7.4 of [2].

[0238] - The UE can use the Type 2 channel access procedure as described in Section 4.2.1.2 on channel c i Transmitted on ∈C

[0239] -If immediately following channel c j Immediately before the UE transmits on channel c on channel c. i The above executes a type 2 channel access procedure, where i ≠ j, and

[0240] -If the UE has accessed channel c using the Type 1 channel access procedure as described in Section 4.2.1.1 j ,

[0241] - Before performing a Type 1 channel access procedure on any channel in the channel set C, the UE uniformly and randomly selects channel c from the channel set C. j .

[0242] - If the UE fails to access any of the channels within the carrier bandwidth, whether scheduled or configured by UL resources, the UE may not be on channel c within the carrier bandwidth. i Transmitted on ∈C.

[0243] 4.2.1.1 Type 1 UL Channel Access Procedure

[0244] This section describes the channel access procedure to be performed by the UE, where the duration spanned by sensing slots sensed as idle prior to UL transmission is random. This section applies to the following transmissions:

[0245] - Transmitted via eNB / gNB scheduling or configured PUSCH / SRS, or

[0246] - Transmitted via gNB scheduling or configured PUCCH, or

[0247] - Transmissions related to the random access procedure.

[0248] UE can delay duration Td After the channel is first sensed as idle during the sensing time slot duration and after counter N reaches zero in step 4, a type 1 channel access procedure is used to transmit the transmission. The counter N is adjusted by sensing the channel for the additional time slot duration, according to the steps described below.

[0249] 1) Set N = N init , where N init For 0 and CW p A random number is uniformly distributed between them, and then proceed to step 4;

[0250] 2) If N > 0, and the UE chooses to decrement the counter, then set N = N - 1;

[0251] 3) Sensing the channel during the additional time slot duration, and if the additional time slot duration is idle, proceed to step 4; otherwise, proceed to step 5;

[0252] 4) If N = 0, stop; otherwise, go to step 2.

[0253] 5) Sensing channel until the additional delay duration T d A busy time slot or an additional delay duration T was detected within the time slot. d All time slots are idle;

[0254] 6) If the additional delay duration T d If the sensing channel is idle during all time slot durations, proceed to step 4; otherwise, proceed to step 5.

[0255] 4.2.1.2 Type 2 UL Channel Access Procedure

[0256] This section describes the channel access procedure to be performed by the UE, where the duration of the sensing slots that are sensed as idle before UL transmission is deterministic.

[0257] If the UE is instructed by the eNB to perform a Type 2 UL channel access procedure, the UE follows the procedure described in Section 4.2.1.2.1.

[0258] 4.2.1.2.1 Type 2A UL Channel Access Procedure

[0259] If the UE is instructed to perform a Type 2A UL channel access procedure, the UE uses the Type 2A UL channel access procedure for UL transmission. The UE may then immediately follow the procedure if the sensing channel is idle for at least one sensing interval T. short_ul =Teleport immediately after 25us. T short_ul The duration T following a time slot in a time slot sensing context f =16us, and Tf Included in the sensing time slot at the beginning. If T short_ul If both sensing slots are detected as idle, then the channel is considered idle for T seconds. short_ul .

[0260] 4.2.1.2.2 Type 2B UL Channel Access Procedure

[0261] If the UE is instructed to perform a Type 2B UL channel access procedure, the UE uses the Type 2B UL channel access procedure for UL transmission. The UE can perform this procedure at T... f Transmission occurs immediately after the sensing channel becomes idle, within a duration of 16µs. f Included in T f The sensing time slot is performed within the last 9 µs. If the channel is sensed as idle for a total of at least 5 µs, and at least 4 µs of sensing is performed in the sensing time slot, then the channel is considered idle for a duration T. f The inside is considered free.

[0262] 4.2.1.2.3 Type 2C UL Channel Access Procedure

[0263] If the UE is instructed to perform a Type 2C UL channel access procedure for UL transmission, the UE does not sense the channel before transmission. The duration of the corresponding UL transmission is at most 584 µs.

[0264] 4.2.2 Competition Window Adjustment Procedure

[0265] If the UE uses a Type 1 channel access procedure associated with channel access priority class p on the channel to transmit, the UE maintains the contention window value CW. p Furthermore, for those transmissions described in this section, the CW is adjusted before step 1 of the procedure described in section 4.2.1.1. p .

[0266] 4.2.2.2 Contention window adjustment procedure for UL transmissions scheduled / configured by gNB

[0267] If the UE uses a Type 1 channel access procedure associated with channel access priority class p on the channel to transmit, the UE maintains the contention window value CW. p And adjust the CW before step 1 of the procedure described in Section 4.2.1.1 using the following steps. p :

[0268] 1) For each priority class p∈{1,2,3,4}, set CW p =CW min,p ;

[0269] 2) If HARQ-ACK feedback is in CW p If the last update is available, proceed to step 3. Otherwise, if the UE transmission following the procedure described in Section 4.2.1.1 does not involve a retransmission or in CW... p The last update is the duration T from the end of the reference duration corresponding to the earliest DL channel occupancy. w If the data is transferred internally, proceed to step 5; otherwise, proceed to step 4.

[0270] 3) HARQ-ACK feedback is used for the reference duration of the latest available UL channel occupancy, corresponding to the PUSCH, as follows:

[0271] a. If at least one HARQ-ACK feedback is 'ACK' for a PUSCH with transport block-based feedback, or if at least 10% of the HARQ-ACK feedback is 'ACK' for a PUSCH CBG transmitted at least partially on a channel with code block group (CBG)-based feedback, then proceed to step 1; otherwise, proceed to step 4.

[0272] 4) For each priority class p∈{1,2,3,4}, CW p Increase to the next higher allowed value;

[0273] 5) For each priority class p∈{1,2,3,4}, CW p Leave it as is; proceed to step 2.

[0274] 4.2.2.3 Common Procedures for CWS Adjustment in UL Transmission

[0275] The following applies to the procedures described in Sections 4.2.2.1 and 4.2.2.2:

[0276] -If CW p =CW max,p This is used to adjust CW p The next higher allowed value is CW max,p .

[0277] -If CW p =CW max,p Used K times consecutively to generate N init Then CW p Reconfigured to CW only for priority class p min,p CW p =CW max,p p is used K times consecutively to generate N. initThe UE selects K from a set of values ​​{1,2,…,8} for each priority class p∈{1,2,3,4}.

[0278] 4.2.3 Energy detection threshold adjustment procedure

[0279] UEs accessing the channel on which UL transmission is performed should set the energy detection threshold (X). Thresh Set to less than or equal to the maximum energy detection threshold X Thresh_max X Thresh_max The following is determined:

[0280] - If the UE is configured to use the higher-layer parameter maxEnergyDetectionThreshold-r14 or maxEnergyDetectionThreshold-r16, then

[0281] -X Thresh_max Set it to be equal to the value represented by the signal through higher-level parameters.

[0282] -otherwise

[0283] - The UE will determine X′ according to the procedure described in Section 4.2.3.1. Thresh_max ;

[0284] - If the UE is configured to use the higher-layer parameters EnergyDetectionThreshold-r14 or EnergyDetectionThreshold-r16, then

[0285] - Adjust X′ according to the offset value represented by a signal from higher-level parameters. Thresh_max To set X Thresh_max ;

[0286] -otherwise

[0287] -UE should be set to X Thresh_max =X′ Thresh_max .

[0288] …

[0289] 4.3 Channel Access Procedure for Semi-Static Channel Occupancy

[0290] The semi-static channel occupancy-based channel assessment procedure described in this chapter is intended for environments where, for example, regulatory levels and privacy policies ensure the absence of other technologies. If the gNB provides a UE with the higher-layer parameter ChannelAccessMode-r16='semi-static' via SIB1 or a dedicated configuration, it can transmit data through each T-frame within every two consecutive radio frames. xPeriodic channel occupation initiated by gNB, starting from the maximum channel occupation time T y =0.95T x i·T x The radio frame begins with an even-indexed location, where T is measured in milliseconds. x =period is a high-level parameter provided in SemiStaticChannelAccessConfig, and

[0291] In the following procedures in this section, when the gNB or UE performs sensing for channel availability assessment, at least for the sensing time slot duration T sl Sensing is performed during a period of 9µs. Corresponding adjustments for sensing performed by the gNB or UE are described in Sections 4.1.5 and 4.2.3, respectively.

[0292] Channel occupancy initiated by the gNB and shared with the UE should meet the following conditions:

[0293] - The gNB should begin transmitting a DL transmission burst immediately at the beginning of the channel occupancy time after sensing that the channel is idle for at least the duration of the sensing time slot. If the channel is sensed to be busy, the gNB should not perform any transmissions during the current period.

[0294] - If the gap between the DL transmission burst and any previous transmission burst is greater than 16µs, the gNB can sense the time slot duration T for at least... sl =9us After sensing that the channel is idle, immediately transmit the DL transmission burst during the channel occupancy time.

[0295] - If the gap between the DL and UL transmission bursts is at most 16µs, the gNB can transmit the DL transmission burst after the UL transmission burst within the channel occupancy time without sensing the channel.

[0296] - After detecting a DL transmission burst during the channel occupancy period, the UE can transmit a UL transmission burst as follows:

[0297] - If the gap between the DL and UL transmission bursts is at most 16µs, the UE can transmit the UL transmission burst after the DL transmission burst within the channel occupancy time without sensing the channel.

[0298] - If the gap between the UL and DL transmission bursts is greater than 16µs, the UE can sense channel idleness for at least one sensing time slot duration T immediately following the end of the 25µs interval after the transmission. sl =9us later, after the DL transmission burst during the channel occupancy time, the UL transmission burst is transmitted.

[0299] - Before the start of the next cycle, gNB and UE will be at least T z =max(0.05T) x No transmissions are transmitted within a set of consecutive symbols for a duration of 100us.

[0300] If the UE fails to access the channel before the predetermined UL transmission to the gNB, Layer 1 notifies the higher layers of the channel access failure.

[0301] ****************************End of quotation*********************************

[0302] There are studies on operation in frequency bands above 52.6 GHz. Some modifications are considered because there are several different characteristics compared to lower conventional frequency bands, such as wider available bandwidth / larger (phase) noise / ICI. Therefore, larger subcarrier spacing (e.g., up to 960 kHz) and cell bandwidth are expected to increase to the GHz level, for example, 1 or 2 GHz. And, since there is unlicensed spectrum in the frequency bands under consideration, it is also discussed whether any changes are needed to the channel access scheme. For example, in some cases, the device can access the channel / spectrum without LBT (e.g., without LBT). And, there are some adjustments to the LBTs under consideration, such as directional LBTs or receiver-assisted LBTs, as cited in the following [3] RP-202925:

[0303] ****************************Start of quotation*******************************

[0304] Based on the results of a research project supporting NR above 52.6 GHz and making the most of the FR2 design, this WI considers both licensed and unlicensed operations to extend NR operation to a maximum of 71 GHz, with the following objectives:

[0305] ■Physical layer aspects including [RAN1]:

[0306] In addition to the 120kHz SCS, new SCSs are specified for 480kHz and 960kHz, and a maximum bandwidth is defined for operation of data and control channels and reference signals in this frequency range, supporting only NCP.

[0307] Note: Except for timing-related aspects, a common design framework should be used for frequencies from 480kHz to 960kHz.

[0308] ○ Suitable for timeline-related aspects at 480kHz and 960kHz, such as BWP and beam switching timing, HARQ timing, UE processing, and preparation and calculation timelines for PDSCH, PUSCH / SRS and CSI, respectively.

[0309] ○ Support for up to 64 SSB beams for licensed and unlicensed operations in this frequency range.

[0310] ○ Supports 120kHz SCS for SSB and 120kHz SCS for initial access-related signals / channels in initial BWP.

[0311] ■ If necessary, study and specify additional SCS (240kHz, 480kHz, 960kHz) for SSB and additional SCS (480kHz, 960kHz) for initial access-related signals / channels in the initial BWP.

[0312] ■ If necessary, study and specify additional SCS (480kHz, 960kHz) for situations other than initial access.

[0313] ■Note: Coverage enhancement for SSB is not implemented.

[0314] ○ Specify the timing associated with beam-based operation as the new SCS (i.e., 480kHz and / or 960kHz), and investigate and specify potential enhancements for shared spectrum operation if necessary.

[0315] ■ Investigate which beam management will be used as the basis: R15 / 16 or R17 in RAN#91-e.

[0316] ○ Supports enhancements for PUCCH formats 0 / 1 / 4 to increase the number of RBs under PSD constraints in shared spectrum operations.

[0317] ○ Enhanced support for multi-PDSCH / PUSCH scheduling and HARQ support with a single DCI

[0318] Note: Coverage enhancement for multi-PDSCH / PUSCH scheduling is not implemented.

[0319] ○ Supports enhancements to PDCCH monitoring, including blind detection / CCE budget and multi-slot span monitoring, potential limitations on UEPDCCH configuration, and capabilities related to PDCCH monitoring.

[0320] ○ Specify support for PRACH sequence lengths (i.e., L=139, L=571, and L=1151), and if necessary, study and specify support for RO configurations for non-continuous RACH timings (ROs) in the time domain for operations in shared spectrum.

[0321] ○ Evaluate and, if necessary, specify PTRS enhancement for 120kHz SCS, 480kHz SCS, and / or 960kHz SCS, and DMRS enhancement for 480kHz SCS and / or 960kHz SCS.

[0322] ■Physical layer procedures containing [RAN1]:

[0323] The channel access mechanism assumes beam-based operation in order to comply with regulatory requirements for unlicensed spectrum applicable to frequencies between 52.6 GHz and 71 GHz.

[0324] ■ Specify LBT and LBT-free related procedures, and do not specify additional sensing mechanisms for the LBT-free case.

[0325] ■Study and, if necessary, specify omnidirectional LBTs, directional LBTs, and receiver assistance in channel access.

[0326] ■ Research and, if necessary, specify an enhanced energy detection threshold.

[0327] **************************End of quotation**********************************

[0328] The duration or period of transmission can be indicated or predefined (e.g., time resources). Different signals or channels may use different methods to determine the duration or period. For example, duration / period can be configured, for example, via RRC configuration. Duration / period can be dynamically scheduled, for example, via DCI. Duration / period can be semi-statically scheduled, for example, configured via RRC configuration and activated / deactivated via DCI. Duration / period can be one or more (continuous) symbols or one or more (continuous) time slots. Frequency domain resource allocation can be performed in a similar manner, for example, via DCI or semi-static scheduling predefined, configured, and scheduled. Further details on how transmission time resources and / or frequency resources are determined are cited below.

[0329] ************************ Beginning of quotation ***************************************

[0330] 5.1.2 Resource Allocation

[0331] 5.1.2.1 Resource Allocation in the Time Domain

[0332] When a UE is scheduled to receive PDSCH via DCI, the time-domain resource allocation field value m of DCI provides a row index m+1 to the allocation table. The determination of the resource allocation table used is defined in Section 5.1.2.1.1. The index row specifies the slot offset K0, the start and length indicator SLIV or directly the start symbol S and the allocation length L, as well as the PDSCH mapping type to be used in PDSCH reception.

[0333] Given the parameter value for the index row:

[0334] - The time slot allocated for PDSCH is K s Where the UE is configured to use ca-SlotOffset for at least one of the scheduled and scheduled cells, then And in other cases, for And where n is the time slot with scheduled DCI, and K0 is the basic parameter based on PDSCH, and and are the subcarrier spacing configurations used for PDSCH and PDCCH, respectively.

[0335] - and μ offset,PDCCH These are determined by the higher-level configuration of ca-SlotOffset. and μ offset , and μ offset,PDSCH These are determined by the higher layer in the ca-SlotOffset configuration of the cell used to receive the PDCCH. and μ offset As defined in Section 4.5 of [4,TS 38.211].

[0336] - The reference point S0 used for the start symbol S is defined as:

[0337] - If configured to use referenceOfSLIVDCI-1-2, and when receiving a PDSCH scheduled by DCI format 1_2, where the CRC is scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI with K0=0 and PDSCH mapping type B, then the start symbol S is the start symbol S0 relative to the timing in which a PDCCH listening of DCI format 1_2 is detected.

[0338] - Otherwise, the start symbol S is relative to the start of the time slot using S0=0.

[0339] - Determine the number of consecutive symbols L counted from the start symbol S assigned for PDSCH based on the start and length indicators SLIV:

[0340] If (L-1)≤7, then

[0341] SLIV = 14·(L-1) + S

[0342] otherwise

[0343] SLIV = 14·(14-L+1)+(14-1-S)

[0344] Where 0 < L ≤ 14 - S, and

[0345] - The PDSCH mapping type is set to type A or type B, as defined in section 7.4.1.1.2 of [4,TS 38.211].

[0346] The UE will consider the S and L combinations that satisfy S0+S+L≤14 for the normal cyclic prefix and S0+S+L≤12 for the extended cyclic prefix as valid PDSCH allocations, as defined in Table 5.1.2.1-1:

[0347] Table 5.1.2.1-1: Effective S and L Combinations

[0348]

[0349] [...]

[0350] Two downlink resource allocation schemes are supported: Type 0 and Type 1. The UE will assume that downlink resource allocation type 1 will be used when a scheduling grant with DCI format 1_0 is received.

[0351] If the scheduling DCI is configured to indicate the downlink resource allocation type as part of the 'Frequency Domain Resource Allocation' field by setting the higher-layer parameter resourceAllocation in PDSCH-Config to 'dynamicSwitch' for DCI format 1_1 or setting the higher-layer parameter resourceAllocation-1-2 in PDSCH-Config to 'dynamicSwitch' for DCI format 1_2, then the UE will use downlink resource allocation type 0 or type 1, as defined by this DCI field. In other cases, the UE will use the downlink frequency resource allocation type, as defined by the higher-layer parameter resourceAllocation for DCI format 1_1 or the higher-layer parameter resourceAllocationDCI-1-2 for DCI format 1_2.

[0352] If the Bandwidth Part Indicator field is not configured in the scheduling DCI or the UE does not support active BWP changes via the DCI, then the RB index for downlink type 0 and type 1 resource allocation is determined within the UE's active bandwidth part. If the Bandwidth Part Indicator field is configured in the scheduling DCI and the UE supports active BWP changes via the DCI, then the RB index for downlink type 0 and type 1 resource allocation is determined within the UE's bandwidth part indicated by the value of the Bandwidth Part Indicator field in the DCI. When the UE detects a PDCCH designated for the UE, it first determines the downlink bandwidth part, and then determines the resource allocation within that bandwidth part.

[0353] For any type of PDSCH scheduled in DCI format 1_0 within the PDCCH common search space, regardless of which bandwidth portion is active, the RB numbering starts from the lowest RB of the CORESET in which DCI has been received; otherwise, the RB numbering starts from the lowest RB in the determined downlink bandwidth portion.

[0354] 5.1.2.2.1 Downlink resource allocation type 0

[0355] In type 0 downlink resource allocation, the resource block allocation information includes a bitmap indicating the resource block group (RBG) allocated to the scheduled UE, where the RBG is a contiguous set of virtual resource blocks defined by the higher-layer parameter rbg-Size configured by PDSCH-Config, and the size of the bandwidth portion is defined in Table 5.1.2.2.1-1.

[0356] Table 5.1.2.2.1-1: Nominal RBG size P

[0357] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0358] Size is The total number of RBGs (N) of the downlink bandwidth portion i of the PRB. RBG )pass Given, among which

[0359] -The size of the first RGB is

[0360] -if The final size of RBG is And in other cases it is P.

[0361] - The size of all other RBGs is P.

[0362] The bitmap has a size N RBGEach RBG has one bitmap bit, making each RBG addressable. RBGs should be indexed in ascending frequency order, starting from the lowest frequency in the bandwidth portion. The RBG bitmap order is such that RBG 0 to RBG N... RBG -1 is mapped from MSB to LSB. If the corresponding bit value in the bitmap is 1, then RBG is assigned to the UE; otherwise, RBG is not assigned to the UE.

[0363] 5.1.2.2.2 Downlink Resource Allocation Type 1

[0364] In type 1 downlink resource allocation, resource block allocation information indicates to the scheduled UE the size... A set of contiguously allocated non-interleaved or interleaved virtual resource blocks within the active bandwidth portion of the PRB, except in cases where DCI format 1_0 is being decoded in any common search space. In such cases, if CORESET 0 is configured for a cell, the size of CORESET 0 should be used, and if CORESET 0 is not configured for a cell, the size of the initial DL bandwidth portion should be used.

[0365] Downlink Type 1 resource allocation field is defined by the starting virtual resource block (RB). start The resource indicator value (RIV) and the length L of the contiguously allocated resource blocks. RBs Composition. The resource indicator value is defined by the following formula.

[0366] if but

[0367]

[0368] otherwise

[0369]

[0370] Where L RBs ≥1 and should not exceed

[0371] When the DCI format 1_0 size in USS is derived from the DCI format 1_0 size in CSS, but applied to a file with a size of... When a BWP is active, the downlink type 1 resource block allocation field is determined by the corresponding start resource block. The resource indication value (RIV) and the length of nearly contiguously allocated resource blocks. Composition, in which Given from the following:

[0372] - If CORESET 0 is configured for use with a cell, then the size of CORESET 0;

[0373] - If CORESET 0 is not configured for use with a cell, then it is the size of the initial DL bandwidth portion.

[0374] The resource indicator value is defined by the following formula:

[0375] if but

[0376]

[0377] otherwise

[0378]

[0379] Among them L' RBs =L RBs / K,RB' start =RB start / K, and should not exceed

[0380] if Then K comes from satisfying The maximum value of the set {1,2,4,8}; otherwise, K=1.

[0381] When a scheduling grant with DCI format 1_2 is received, the downlink type 1 resource allocation field is changed according to the starting resource block group RBG. start =0, 1...N RBG -1 resource indication value (RIV) and L for nearly contiguous allocation of resource block groups. RBGs =1, ..., N RBG The length composition is defined in 5.1.2.2.1, where the resource block group is defined as in 5.1.2.2.1. If the UE is configured to use the higher-layer parameter ResourceAllocationType1GranularityDCI-1-2, then P is defined by ResourceAllocationType1GranularityDCI-1-2; otherwise, P = 1. The resource indication value is defined by the following formula.

[0382] if but

[0383] RIV=N RBG (L RBGs -1)+RBG start

[0384] otherwise

[0385] RIV=NRBG (N RBG -L RBGs +1)+(N RBG -1-RBG start )

[0386] Where L RBGs ≥1 and should not exceed N RBG -RBG start .

[0387] [...]

[0388] 6.1.2 Resource Allocation

[0389] 6.1.2.1 Resource Allocation in the Time Domain

[0390] When a UE is scheduled to transmit a transport block without a CSI report, or when a UE is scheduled to transmit a transport block and a CSI report on the PUSCH via the DCI, the 'Time Domain Resource Allocation' field value m of the DCI provides the row index m+1 of the allocation table. The determination of the resource allocation table used is defined in Section 6.1.2.1.1. The index row specifies the slot offset K2 to be applied in the PUSCH transmission, the start and length indicator SLIV or the direct start symbol S and the allocation length L, the PUSCH mapping type and the number of repetitions (if numberOfRepetitions exists in the resource allocation table).

[0391] When a UE is scheduled to transmit a PUSCH without a transport block and with a CSI report via the 'CSI Request' field on the DCI, the 'Time Domain Resource Allocation' field value m of the DCI provides row index m+1 to the allocation table, as defined in Section 6.1.2.1.1. The index row specifies the start and length indicator SLIV or direct start symbol S and allocation length L to be applied in the PUSCH transmission, as well as the PUSCH mapping type, and determines the K2 value. Where Y j j = 0, ..., N Rep -1 is the corresponding list entry for higher-level parameters.

[0392] - If PUSCH is scheduled via DCI format 0_2, then it is reportSlotOffsetListDCI-0-2, and reportSlotOffsetListDCI-0-2 is configured.

[0393] - If PUSCH is scheduled via DCI format 0_1, then it is reportSlotOffsetListDCI-0-1, and reportSlotOffsetListDCI-0-1 is configured.

[0394] - In other cases, reportSlotOffsetList;

[0395] In use to trigger N Rep In the CSI-ReportConfig settings of the CSI report, and Y j (m+1) is Y j The (m+1)th entry.

[0396] - If the UE is configured to use ca-SlotOffset for at least one of the scheduled and scheduled cells, where the UE will transmit PUSCH in slot Ks determined by K2 as K s = Otherwise And where n is the time slot with scheduled DCI, K2 is the basic parameter based on PUSCH, and μ PUSCH and μ PDCCH For the subcarrier spacing configuration used for PUSCH and PDCCH respectively,

[0397] - and μ offset,PDCCH These are determined by the higher layer in the ca-SlotOffset configuration of the cell used to receive the PDCCH. and μ offset , and μ offset,PDSCH These are determined by the higher layer based on the ca-SlotOffset configuration of the cell used to transmit PUSCH. and μ offset As defined in Section 4.5 of [4,TS 38.211].

[0398] - For PUSCHs scheduled by DCI format 0_1, if pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB', the UE applies PUSCH repetition type B procedure when determining time-domain resource allocation. For PUSCHs scheduled by DCI format 0_2, if pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the UE applies PUSCH repetition type B procedure when determining time-domain resource allocation. In other cases, the UE applies PUSCH repetition type A procedure when determining time-domain resource allocation for PUSCHs scheduled by PDCCH.

[0399] - For PUSCH repetition type A, the start symbol S associated with the slot start and the number of consecutive symbols L counted from the symbols allocated for PUSCH are determined based on the start and length indicator SLIV of the index row:

[0400] If (L-1)≤7, then

[0401] SLIV = 14·(L-1) + S

[0402] otherwise

[0403] SLIV = 14·(14-L+1)+(14-1-S)

[0404] Where 0 < L ≤ 14 - S, and

[0405] - For PUSCH repetition type B, the start symbol S associated with the start of the slot and the number of consecutive symbols L counted from the symbols allocated for PUSCH are provided by the startSymbol and length of the index row of the resource allocation table, respectively.

[0406] - For PUSCH repeating type A, the PUSCH mapping type is set to type A or type B, as defined in section 6.4.1.1.3 of [4, TS 38.211], as given in the index row.

[0407] - For PUSCH repeating type B, the PUSCH mapping type is set to type B.

[0408] The UE should consider the S and L combinations defined in Table 6.1.2.1-1 as valid PUSCH assignments.

[0409] Table 6.1.2.1-1: Effective S and L Combinations

[0410]

[0411] [...]

[0412] 6.1.2.2 Resource Allocation in the Frequency Domain

[0413] The UE will use the resource allocation field in the detected PDCCH DCI to determine the resource block allocation in the frequency domain, except for PUSCH transmissions scheduled by RARUL or fallbackRARUL. In this case, the frequency domain resource allocation is determined according to Section 8.3 of [6,38.213], or according to Section 8.1A of [6,38.213] for MsgA PUSCH transmissions with frequency domain resource allocation. Three uplink resource allocation schemes, Type 0, Type 1, and Type 2, are supported. Uplink resource allocation scheme Type 0 is supported for PUSCHs only when transform pre-decoding is disabled. When transform pre-decoding is enabled or disabled, uplink resource allocation schemes Type 1 and Type 2 are supported for PUSCHs in both cases.

[0414] If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the 'Frequency Domain Resource Allocation' field by setting the higher-layer parameter resourceAllocation in push-Config to 'dynamicSwitch' for DCI format 0_1 ​​or setting the higher-layer parameter resourceAllocationDCI-0-2 in push-Config to 'dynamicSwitch' for DCI format 0_2, then the UE will use uplink resource allocation type 0 or type 1, as defined by this DCI field. In other cases, the UE will use the uplink frequency resource allocation type, as defined by the higher-layer parameter resourceAllocation for DCI format 0_1 ​​or the higher-layer parameter resourceAllocationDCI-0-2 for DCI format 0_2. The UE should assume that when it receives the scheduling PDCCH in DCI format 0_1 ​​and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, it will use uplink type 2 resource allocation.

[0415] The UE should assume that when the scheduled PDCCH is received in DCI format 0_0, uplink resource allocation type 1 is used, except when either the higher-layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkCommon or useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, in which case uplink resource allocation type 2 is used.

[0416] The UE expects to configure either or both of the useInterlacePUCCH-PUSCH in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated.

[0417] If the Bandwidth Part Indicator field is not configured in the scheduling DCI or the UE does not support changes to the active bandwidth part via the DCI, then the RB index for uplink type 0, type 1, and type 2 resource allocation is determined within the UE's active bandwidth part. If the Bandwidth Part Indicator field is configured in the scheduling DCI and the UE supports changes to the active bandwidth part via the DCI, then the RB index for uplink type 0, type 1, and type 2 resource allocation is determined within the UE's bandwidth part indicated by the value of the Bandwidth Part Indicator field in the DCI. When the UE detects a PDCCH designated for the UE, it first determines the uplink bandwidth part, and then determines the resource allocation within that bandwidth part. The RB numbering starts from the lowest RB in the determined uplink bandwidth part.

[0418] 6.1.2.2.1 Uplink resource allocation type 0

[0419] In type 0 uplink resource allocation, the resource block allocation information includes a bitmap indicating the resource block group (RBG) allocated to the scheduled UE, where the RBG is a group of contiguous virtual resource blocks defined by the higher-layer parameter rbg-Size configured by pusch-Config, and the size of the bandwidth portion is defined in Table 6.1.2.2.1-1.

[0420] Table 6.1.2.2.1-1: Nominal RBG size P

[0421] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0422] Size is The total number of RBGs (N) of the uplink bandwidth portion i of the PRB. RBG )pass Given, among which

[0423] -The size of the first RGB is

[0424] -if The final size of RBG is And in other cases it is P.

[0425] - The size of all other RBGs is P.

[0426] The bitmap has a size N RBG Each RBG has one bitmap, making each RBG addressable. RBGs should be indexed in ascending order of frequency for their bandwidth portions, starting with the lowest frequency. The bitmap order of the RBGs is such that RBG 0 through RBG N... RBG-1 is mapped from the MSB to the LSB of the bitmap. If the corresponding bit value in the bitmap is 1, then RBG is assigned to the UE; otherwise, RBG is not assigned to the UE.

[0427] In frequency range 1, only 'nearly contiguous allocation' as defined in [8,TS 38.101-1] is permitted as a non-contiguous allocation of per component carrier for UL RB allocation for CP-OFDM.

[0428] In frequency range 2, non-contiguous allocation of per-component carriers for UL RB allocation in CP-OFDM is not supported.

[0429] 6.1.2.2.2 Uplink Resource Allocation Type 1

[0430] In Type 1 uplink resource allocation, resource block allocation information indicates to the scheduled UE the size... A set of contiguously allocated, non-interleaved virtual resource blocks within the active bandwidth portion of the PRB, except in cases where DCI format 0_0 is being decoded in any common search space, in which case the initial UL bandwidth portion should be used. Size.

[0431] Uplink Type 1 resource allocation field is defined by the starting virtual resource block (RB). start The resource indicator value (RIV) and the length L of the contiguously allocated resource blocks. RBs Composition. The resource indicator value is defined by the following formula.

[0432] if but

[0433]

[0434] otherwise

[0435]

[0436] Where L RBs ≥1 and should not exceed

[0437] 6.1.2.2.3 Uplink Resource Allocation Type 2

[0438] In Type 2 uplink resource allocation, the resource block allocation information defined in [5, TS 38.212] indicates to the UE a set of at most M interleaved indices, and for DCI 0_0 listened to in the UE's specific search space and a set of at most M interleaved indices... DCI 0_1 of the continuous RB set, where M and the interleaving index are defined in Section 4.4.4.6 of [4, TS 38.211]. Within the active UL BWP, the allocated physical resource block n is mapped to the virtual resource block n. For DCI 0_0 and DCI 0_1 listened in the UE-specific search space, the UE shall determine the resource allocation in the frequency domain as the intersection of the indicated interleaved resource blocks, and as the union of the indicated set of RB sets, as well as the in-cell guard bands (if any) defined in Section 7 between the indicated RB sets.

[0439] …

[0440] For μ = 0, the X = 6 MSBs of the resource block allocation information indicate a set of allocated interleaving indices m0 + l to the UE, where the indication consists of the resource indication value (RIV). For 0 ≤ RIV < M(M + 1) / 2, l = 0, 1, … L - 1, the resource indication value corresponds to the starting interleaving index m0 and the number of consecutive interleaving indices L (L ≥ 1). The resource indication value is defined by the following formula:

[0441] If then

[0442] RIV = M(L - 1) + m0

[0443] Otherwise

[0444] RIV = M(M - L + 1) + (M - 1 - m0)

[0445] For RIV ≥ M(M + 1) / 2, the resource indication value corresponds to the starting interleaving index m0 and a set of values l according to Table 6.1.2.2.3-1.

[0446] …

[0447] 6.1.2.3 Resource Allocation for Uplink Transmissions with Configured Grants

[0448] When the PUSCH resource allocation is semi-statically configured by the higher-layer parameter configuredGrantConfig in the BWP-UplinkDedicated information element and the PUSCH transmission corresponds to a configured grant, the following higher-layer parameters are applied in the transmission:

[0449] - For type 1 PUSCH transmissions with configured grants, unless otherwise mentioned, the following parameters are given in configuredGrantConfig:

[0450] - To determine the PUSCH repetition type, if the high-level parameter pusch-RepTypeIndicator in rrc-ConfiguredUplinkGrant is configured and set to 'pusch-RepTypeB', then PUSCH repetition type B is applied; otherwise, PUSCH repetition type A is applied.

[0451] - For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rules of DCI format 0_0 regarding the UE-specific search space, as defined in Section 6.1.2.1.1.

[0452] -For PUSCH repetition type B, the time-domain resource allocation table is selected as follows:

[0453] - If pusch-RepTypeIndicatorDCI-0-1 in pusch-Config is configured and set to 'pusch-RepTypeB', then pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used;

[0454] - Otherwise, use pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Config.

[0455] - When neither push-RepTypeIndicatorDCI-0-1 nor push-RepTypeIndicatorDCI-0-2 in push-Config is set to 'pusch-RepTypeB', push-RepTypeIndicator in rrc-ConfiguredUplinkGrant should be configured to 'pusch-RepTypeB'.

[0456] - The high-level parameter timeDomainAllocation value m provides a row index m+1 pointing to the determined time-domain resource allocation table, where the starting symbol and length are determined according to the procedure defined in Section 6.1.2.1;

[0457] - According to the procedure in Section 6.1.2.2, the frequency domain resource allocation is determined by the N LSB bits in the higher-level parameter frequencyDomainAllocation, thus forming the bit sequence f. 17,…,f1,f0, where f0 is an LSB, and N is determined as the size of the frequency domain resource allocation field in DCI format 0_1 ​​for a given resource allocation type indicated by resourceAllocation, except where uplink type 2 resource allocation is used to configure useInterlacePUCCH-PUSCH in BWP-UplinkDedicated, where the UE interprets the LSB bits in the higher-layer parameter frequencyDomainAllocation with respect to the frequency domain resource allocation field of DCI 0_1 according to the procedure in Section 6.1.2.2.3;

[0458] -I MCS Provided by high-level parameters mcsAndTBS;

[0459] The number of DM-RS CDM groups, DM-RS ports, SRS resource indicators, and DM-RS sequence initializations are determined according to Section 7.3.1.1.2 of [5, TS38.212], and the antenna port value, the bit value of the DM-RS sequence initialization, the number of pre-decoding information and layers, and the SRS resource indicator are provided by antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator, respectively.

[0460] - When frequency hopping is enabled, the frequency offset between two frequency hops can be configured via the higher-level parameter FrequencyHoppingOffset.

[0461] ****************************End of quotation********************************

[0462] As detailed above, at least two channel access modes may exist, such as Listen-before-Talk (LBT) and no LBT for higher frequency bands (e.g., >52.6 GHz). Furthermore, LBT can be broken down into different types, such as fully directional LBT, directional LBT, and receiver-assisted LBT. Trade-offs may exist between these different modes / types. For example, the no-LBT mode can reduce transmission latency to benefit throughput, for example, when there is no conflict between the transmissions (e.g., from a receiver's perspective). On the other hand, LBT would be a better choice when transmissions conflict with each other, causing decoding failure (e.g., from a receiver's perspective). The apparatus may have some criteria to appropriately determine whether and / or how to perform LBT.

[0463] The method and concept of this invention are to determine whether and / or how to perform LBT for a transmission based on transmission characteristics. Characteristics may be resource allocation for the transmission. Characteristics may be the manner in which resources are allocated for the transmission. Characteristics may be the length or size of the resources allocated for the transmission. Characteristics may be the amount of resources allocated for the transmission. Resource allocation may be time-domain resource allocation and / or frequency-domain resource allocation.

[0464] In various embodiments, the apparatus determines whether to perform LBT for a transmission based on the resource allocation for the transmission. The apparatus may determine whether to perform LBT for a transmission based on the amount of resources allocated for the transmission. The apparatus may perform LBT for a transmission when / when the resources allocated for the transmission are greater than a threshold. The apparatus may not perform LBT for a transmission when / when the resources allocated for the transmission are less than a threshold. The threshold may be the number of Physical Resource Blocks (PRBs). The threshold may be the number of symbols. The threshold may be the number of time slots. The threshold may be one time slot. The threshold may be predefined, preconfigured, or indicated by the base station.

[0465] The apparatus may determine whether to perform LBT for a transmission based on the method of allocating resources for the transmission. When resources for the transmission are allocated using a first method, the apparatus may perform LBT for the transmission. When resources for the transmission are allocated using a second method, the apparatus may not perform LBT for the transmission.

[0466] The first method for allocating resources can be Downlink Control Information (DCI). This first method can be predefined / fixed. It can be configured, for example, via RRC configuration. It can also be a semi-static scheduling method. The second method for allocating resources can be DCI. This second method can be predefined / fixed. It can also be configured. It can also be a semi-static scheduling method.

[0467] When resources for transmission are configured, for example, via RRC configuration, the device may perform LBT for the transmission. When resources for transmission are indicated by DCI, the device may not perform LBT for the transmission. The device may determine whether to perform LBT for the transmission or not based on the characteristics of the transmission. Alternatively, when resources for transmission are indicated by DCI, the device may perform LBT for the transmission. When resources for transmission are configured, the device may not perform LBT for the transmission.

[0468] The device can determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the characteristics of the transmission. The device can determine how to perform an LBT for a transmission based on the resource allocation of the transmission. The device can determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the resource allocation of the transmission. The device can determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the amount of resources allocated for the transmission. When / when the resources allocated for the transmission are greater than a threshold, the device can perform a first type of LBT for the transmission. When / when the resources allocated for the transmission are less than a threshold, the device can perform a second type of LBT for the transmission. When / when resources for the transmission are allocated using a first method, the device can perform a first type of LBT for the transmission. When / when resources for the transmission are allocated using a second method, the device can perform a second type of LBT for the transmission. When / when resources for the transmission are configured, the device can perform a first type of LBT for the transmission. When / when resources for the transmission are indicated by a DCI, the device can perform a second type of LBT for the transmission. Resources can be time resources and / or frequency resources.

[0469] The exemplary methods and concepts of the present invention can determine whether and / or how to perform LBT for a transmission based on characteristics of previous transmissions. Characteristics may include: whether a previous transmission was successfully received; the number of previous transmissions successfully received; the ratio of previously received previous transmissions successfully received; whether previous LBTs associated with the previous transmission were successful; whether a channel is accessible for the previous transmission; the number of previously successful LBTs; and the ratio of previously successful LBTs.

[0470] In some embodiments, the apparatus may determine whether to perform LBT for a transmission based on whether a previous transmission was successfully received. When / when a previous transmission was not successfully received, the apparatus may perform LBT for the transmission. When / when a previous transmission was successfully received, the apparatus may not perform LBT for the transmission. The apparatus may determine whether to perform LBT for a transmission based on the number of previously received transmissions. When / when the number of previously received transmissions is less than a threshold, the apparatus may perform LBT for the transmission. When / when the number of previously received transmissions is greater than a threshold, the apparatus may not perform LBT for the transmission.

[0471] In some embodiments, the apparatus may determine whether to perform a Level Bypass (LBT) for a transmission based on the ratio of previously successfully received transmissions. When / when the ratio of previously successfully received transmissions is less than a threshold, the apparatus may perform an LBT for the transmission. When / when the ratio of previously successfully received transmissions is greater than a threshold, the apparatus may not perform an LBT for the transmission. The apparatus may determine whether to perform an LBT for a transmission based on whether previous LBTs associated with previous transmissions were successful. When / when previous LBTs associated with previous transmissions failed, the apparatus may perform an LBT for the transmission. When / when previous LBTs associated with previous transmissions were successful, the apparatus may not perform an LBT for the transmission. The apparatus may determine whether to perform an LBT for a transmission based on the number of previously successful LBTs. When / when the number of previously successful LBTs is less than a threshold, the apparatus may perform an LBT for the transmission. When / when the number of previously successful LBTs is greater than a threshold, the apparatus may not perform an LBT for the transmission. The apparatus may determine whether to perform an LBT for a transmission based on the ratio of previously successful LBTs. When / when the ratio of previously successful LBTs is less than a threshold, the apparatus may perform an LBT for the transmission. The device may not perform an LBT for a transmission if the ratio of previously successful LBTs is greater than a threshold. The threshold may be fixed, predefined, or indicated by the base station.

[0472] In some embodiments, the apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on whether a previous transmission was successfully received. The apparatus may determine how to perform an LBT for a transmission based on whether a previous transmission was successfully received. When / when a previous transmission was successfully received, the apparatus may perform a first type of LBT for the transmission. When / when a previous transmission was not successfully received, the apparatus may perform a second type of LBT for the transmission. The LBT associated with the previous transmission is a first type of LBT.

[0473] In some embodiments, if a previous transmission fails, the apparatus may switch from a first type of LBT to a second type of LBT. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the number of previously successfully received transmissions. The apparatus may determine how to perform an LBT for a transmission based on the number of previously successfully received transmissions. When / when the number of previously received transmissions is greater than a threshold, the apparatus may perform a first type of LBT for the transmission. When / when the number of previously received transmissions is greater than a threshold, the apparatus may perform a second type of LBT for the transmission. The LBT associated with the previous transmission is a first type of LBT.

[0474] In some embodiments, if (too many) previous transmissions fail, the apparatus may switch from a first type of LBT to a second type of LBT. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the ratio of successfully received previous transmissions. The apparatus may determine how to perform an LBT for a transmission based on the ratio of successfully received previous transmissions. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the ratio of successfully received previous transmissions. When / when the ratio of received previous transmissions is greater than a threshold, the apparatus may perform a first type of LBT for the transmission. When / when the ratio of received previous transmissions is greater than a threshold, the apparatus may perform a second type of LBT for the transmission. The LBT associated with the previous transmission is a first type of LBT.

[0475] In some embodiments, if (too many) previous transmissions fail, the apparatus may switch from a first type of LBT to a second type of LBT. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on whether a previous LBT associated with a previous transmission was successful. The apparatus may determine how to perform an LBT for a transmission based on whether a previous LBT associated with a previous transmission was successful. When / when a previous LBT associated with a previous transmission is successful, the apparatus may perform a first type of LBT for the transmission. When / when a previous LBT associated with a previous transmission fails, the apparatus may perform a second type of LBT for the transmission. The previous LBT was a first type of LBT.

[0476] In some embodiments, if an LBT fails, the apparatus may switch from a first type of LBT to a second type of LBT. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the number of previously successful LBTs. The apparatus may determine how to perform an LBT for a transmission based on the number of previously successful LBTs. When / when the number of previously successful LBTs is greater than a threshold, the apparatus may perform a first type of LBT for the transmission. When / when the number of previously successful LBTs is less than a threshold, the apparatus may perform a second type of LBT for the transmission. The previous LBT was a first type of LBT.

[0477] In some embodiments, if (too many) LBT failures occur, the apparatus may switch from a first type of LBT to a second type of LBT. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the ratio of previously successful LBTs. The apparatus may determine how to perform LBTs for a transmission based on the ratio of previously successful LBTs. The apparatus may determine whether to perform a first type of LBT or a second type of LBT for a transmission based on the ratio of previously successful LBTs. When / when the ratio of previously successful LBTs is greater than a threshold, the apparatus may perform a first type of LBT for the transmission. When / when the ratio of previously successful LBTs is less than a threshold, the apparatus may perform a second type of LBT for the transmission.

[0478] In some embodiments, the first type of LBT can be an omnidirectional LBT. The first type of LBT can be a directional LBT. The first type of LBT can be a receiver-assisted LBT. The second type of LBT can be an omnidirectional LBT. The second type of LBT can be a directional LBT. The second type of LBT can be a receiver-assisted LBT. Different values ​​of the LBT parameter can be associated with different types of LBTs. The first type of LBT can be associated with a first value of the LBT parameter. The second type of LBT can be associated with a second value of the LBT parameter. The LBT parameter can be the LBT's (energy detection) threshold. The LBT parameter can be the LBT's (contention) window size.

[0479] The devices mentioned in this article may be base stations or user equipment (UE).

[0480] In various embodiments, the transmission can be carried out via the Physical Downlink Shared Channel (PDSCH). The transmission can be carried out via the Physical Downlink Control Channel (PDCCH). The transmission can be carried out via the SS-Block / Physical Broadcast Channel (SS / PBCH). The transmission can be carried out via the CSI Reference Signal (CSI-RS). The CSI-RS can be used in the discovery of burst transmissions. The transmission can be carried out via the Demodulation Reference Signal (DM-RS). The transmission can be used in the discovery of burst transmissions. The transmission can be carried out via the Physical Uplink Shared Channel (PUSCH). The transmission can be carried out via the Physical Uplink Control Channel (PUCCH). The transmission can be carried out via the Physical Random Access Channel (PRACH). The transmission can be carried out via the Sounding Reference Signal (SRS).

[0481] In various embodiments, the first type of LBT can be a downlink (DL) channel access procedure. The first type of LBT can be a type 1 DL channel access procedure. The first type of LBT can be a type 2 DL channel access procedure. The first type of LBT can be a type 2A DL channel access procedure. The first type of LBT can be a type 2B DL ​​channel access procedure. The first type of LBT can be a type 2C DL channel access procedure. The first type of LBT can be a type A multi-channel access procedure. The first type of LBT can be a type A1 multi-channel access procedure. The first type of LBT can be a type A2 multi-channel access procedure. The first type of LBT can be a type B multi-channel access procedure. The first type of LBT can be a type B1 multi-channel access procedure. The first type of LBT can be a type B2 multi-channel access procedure.

[0482] In various embodiments, the first type of LBT can be an uplink (UL) channel access procedure. The first type of LBT can be a type 1 UL channel access procedure. The first type of LBT can be a type 2 UL channel access procedure. The first type of LBT can be a type 2A UL channel access procedure. The first type of LBT can be a type 2B UL channel access procedure. The first type of LBT can be a type 2C UL channel access procedure.

[0483] In various embodiments, the second type of LBT can be a DL channel access procedure. The second type of LBT can be a type 1 DL channel access procedure. The second type of LBT can be a type 2 DL channel access procedure. The second type of LBT can be a type 2A DL channel access procedure. The second type of LBT can be a type 2B DL ​​channel access procedure. The second type of LBT can be a type 2C DL channel access procedure.

[0484] In various embodiments, the second type of LBT can be a type A multichannel access procedure. The second type of LBT can be a type A1 multichannel access procedure. The second type of LBT can be a type A2 multichannel access procedure. The second type of LBT can be a type B multichannel access procedure. The second type of LBT can be a type B1 multichannel access procedure. The second type of LBT can be a type B2 multichannel access procedure. The second type of LBT can be a UL channel access procedure. The second type of LBT can be a type 1 UL channel access procedure. The second type of LBT can be a type 2 UL channel access procedure. The second type of LBT can be a type 2A UL channel access procedure. The second type of LBT can be a type 2B UL channel access procedure. The second type of LBT can be a type 2C UL channel access procedure.

[0485] In some embodiments, the device / UE determines whether and / or how to perform LBT for a transmission based on the characteristics of the transmission. Characteristics may be resource allocation for the transmission. Characteristics may be the length or size of the resources allocated for the transmission. Characteristics may be the amount of resources allocated for the transmission. The UE may perform LBT for the transmission when / when the resources allocated for the transmission are greater than a threshold. The UE may not perform LBT for the transmission when / when the resources allocated for the transmission are less than a threshold (e.g., perform the transmission directly without LBT). Resources may be time resources. Resources may be frequency resources. Resources may be both time and frequency resources. The threshold may be the number of Physical Resource Blocks (PRBs). The threshold may be the number of symbols. The threshold may be the number of time slots. The threshold may be one time slot. The threshold may be predefined, preconfigured, or indicated by the base station.

[0486] When a transmission spans more than one time slot, the UE may perform LBT for the transmission. When a transmission is within one time slot, the UE may not perform LBT for the transmission. When the resources allocated for the transmission are greater than a threshold, the UE may perform a first type of LBT for the transmission. When the resources allocated for the transmission are less than a threshold, the UE may perform a second type of LBT for the transmission. When a transmission spans more than one time slot, the UE may perform a first type of LBT for the transmission. When a transmission is within one time slot, the UE may perform a second type of LBT for the transmission. When the resources allocated for the transmission are greater than a threshold, the UE may perform LBT for the transmission with a first value for the LBT parameter. When the resources allocated for the transmission are less than a threshold, the UE may perform LBT for the transmission with a second value for the LBT parameter. When a transmission spans more than one time slot, the UE may perform LBT for the transmission with a first value for the LBT parameter. When a transmission is within one time slot, the UE may perform LBT for the transmission with a second value for the LBT parameter.

[0487] In some other embodiments, the apparatus / base station determines whether and / or how to perform LBT for a transmission based on the characteristics of the transmission. Characteristics may be resource allocation for the transmission. Characteristics may be the length or size of the resources allocated for the transmission. Characteristics may be the amount of resources allocated for the transmission. The base station may perform LBT for the transmission when / when the resources allocated for the transmission are greater than a threshold. The base station may not perform LBT for the transmission when / when the resources allocated for the transmission are less than a threshold (e.g., perform the transmission directly without LBT). Resources may be time resources. Resources may be frequency resources. Resources may be both time and frequency resources. The threshold may be the number of PRBs. The threshold may be the number of symbols. The threshold may be the number of time slots. The threshold may be one time slot. The threshold may be predefined, preconfigured, or indicated by the base station.

[0488] When a transmission spans more than one time slot, the base station may perform LBT for the transmission. When a transmission is within one time slot, the base station may not perform LBT for the transmission. When the resources allocated for the transmission are greater than a threshold, the base station may perform a first type of LBT for the transmission. When the resources allocated for the transmission are less than a threshold, the base station may perform a second type of LBT for the transmission. When a transmission spans more than one time slot, the base station may perform a first type of LBT for the transmission. When a transmission is within one time slot, the base station may perform a second type of LBT for the transmission. When the resources allocated for the transmission are greater than a threshold, the base station may perform LBT for the transmission with a first value of the LBT parameter. When the resources allocated for the transmission are less than a threshold, the base station may perform LBT for the transmission with a second value of the LBT parameter. When a transmission spans more than one time slot, the base station may perform LBT for the transmission with a first value of the LBT parameter. When a transmission is within one time slot, the base station may perform LBT for the transmission with a second value of the LBT parameter.

[0489] In other embodiments, the device / UE determines whether and / or how to perform LBT for a transmission based on the characteristics of the transmission. The characteristics may be the manner in which resources are allocated for the transmission. The UE may determine whether and / or how to perform LBT for a transmission based on the manner in which resources are allocated for the transmission. When / when resources for the transmission are allocated using a first manner, the UE may perform LBT for the transmission. When / when resources for the transmission are allocated using a second manner, the UE may not perform LBT for the transmission. When / when resources for the transmission are configured, the UE may perform LBT for the transmission. When / when resources for the transmission are indicated by a DCI, the UE may not perform LBT for the transmission. When / when resources for the transmission are indicated by a DCI, the UE may perform LBT for the transmission. When / when resources for the transmission are configured, the UE may not perform LBT for the transmission. When / when resources for the transmission are allocated using a first manner, the UE may perform a first type of LBT for the transmission. When / when resources for the transmission are allocated using a second manner, the UE may perform a second type of LBT for the transmission. When resources for transmission are configured, the UE may perform a first type of LBT for the transmission. When resources for transmission are indicated by the DCI, the UE may perform a second type of LBT for the transmission. When resources for transmission are allocated using a first method, the UE may perform LBT for the transmission with a first value for the LBT parameter. When resources for transmission are allocated using a second method, the UE may perform LBT for the transmission with a second value for the LBT parameter. When resources for transmission are configured, the UE may perform LBT for the transmission with a first value for the LBT parameter. When resources for transmission are indicated by the DCI, the UE may perform LBT for the transmission with a second value for the LBT parameter.

[0490] In other embodiments, the apparatus / base station determines whether and / or how to perform LBT for a transmission based on the characteristics of the transmission. The characteristics may be the manner in which resources are allocated for the transmission. The base station may determine whether and / or how to perform LBT for a transmission based on the manner in which resources are allocated for the transmission. When / when resources for the transmission are allocated using a first manner, the base station may perform LBT for the transmission. When / when resources for the transmission are allocated using a second manner, the base station may not perform LBT for the transmission. When / when resources for the transmission are configured, the base station may perform LBT for the transmission. When / when resources for the transmission are indicated by a DCI, the base station may not perform LBT for the transmission. When / when resources for the transmission are indicated by a DCI, the base station may perform LBT for the transmission. When / when resources for the transmission are configured, the base station may not perform LBT for the transmission. When / when resources for the transmission are allocated using a first manner, the base station may perform a first type of LBT for the transmission. When / when resources for the transmission are allocated using a second manner, the base station may perform a second type of LBT for the transmission. When resources for transmission are configured, the base station may perform a first type of LBT for the transmission. When resources for transmission are indicated by the DCI, the base station may perform a second type of LBT for the transmission. When resources for transmission are allocated using a first method, the UE may perform LBT for the transmission with a first value of the LBT parameter. When resources for transmission are allocated using a second method, the base station may perform LBT for the transmission with a second value of the LBT parameter. When resources for transmission are configured, the base station may perform LBT for the transmission with a first value of the LBT parameter. When resources for transmission are indicated by the DCI, the base station may perform LBT for the transmission with a second value of the LBT parameter.

[0491] refer to Figure 6 In various embodiments / methods 1000, the base station / UE determines whether and / or how to perform LBT for a transmission based on the characteristics of the transmission (step 1004) (step 1002), where the characteristics may be whether a previous transmission was successfully received (step 1006). When / when a previous transmission was not successfully received, the base station / UE may perform LBT for the transmission. When / when a previous transmission was successfully received, the base station / UE may not perform LBT for the transmission (e.g., directly perform the transmission without LBT). When / when a previous transmission was not successfully received, the base station may perform a first type of LBT for the transmission. When / when a previous transmission was successfully received, the base station / UE may perform a second type of LBT for the transmission. When / when a previous transmission was not successfully received, the base station / UE may perform LBT for a transmission having a first value of the LBT parameter. When / when a previous transmission was not successfully received, the base station / UE may perform LBT for a transmission having a second value of the LBT parameter.

[0492] refer to Figure 7 In various embodiments / methods 1010, the UE / base station determines whether and / or how to perform LBT for a transmission based on transmission characteristics (step 1014) (step 1012), where the characteristic may be the number of previously successfully received transmissions (step 1016). When the number of previously successfully received transmissions is less than a threshold, the UE / base station may perform LBT for the transmission. When the number of previously successfully received transmissions is greater than the threshold, the UE / base station may not perform LBT for the transmission (e.g., directly perform the transmission without LBT). When the number of previously successfully received transmissions is greater than the threshold, the UE / base station may perform a first type of LBT for the transmission. When the number of previously successfully received transmissions is less than the threshold, the UE / base station may perform a second type of LBT for the transmission. When the number of previously successfully received transmissions is greater than the threshold, the UE / base station may perform LBT for a transmission with a first value of the LBT parameter. When the number of previously successful LBTs is less than the threshold, the UE / base station may perform LBT for a transmission with a second value of the LBT parameter. The LBT associated with a previous transmission can be a first type of LBT. The LBT associated with a previous transmission can use a first value.

[0493] refer to Figure 8 In various embodiments / methods 1020, the UE / base station determines whether and / or how to perform LBT for a transmission based on transmission characteristics (step 1024) (step 1022), where the characteristic may be the ratio of previously successfully received transmissions (1026). When / when the ratio of previously successfully received transmissions is less than a threshold, the UE / base station may perform LBT for the transmission. When / when the ratio of previously successfully received transmissions is greater than the threshold, the UE / base station may not perform LBT for the transmission (e.g., directly perform the transmission without LBT). When / when the ratio of previously successfully received transmissions is greater than the threshold, the UE / base station may perform a first type of LBT for the transmission. When / when the ratio of previously successfully received transmissions is less than the threshold, the UE / base station may perform a second type of LBT for the transmission. When / when the ratio of previously successfully received transmissions is greater than the threshold, the UE / base station may perform LBT for a transmission having a first value of the LBT parameter. When / when the ratio of previously successfully received transmissions is less than the threshold, the UE / base station may perform LBT for a transmission having a second value of the LBT parameter. The LBT associated with the previous transmission is a first-type LBT. The LBT associated with the previous transmission can use a first value.

[0494] refer to Figure 9In various embodiments / methods 1030, the UE / base station determines whether and / or how to perform LBT for a transmission based on the characteristics of the transmission (step 1034) (step 1032), where the characteristics may be whether a previous LBT associated with a previous transmission was successful (step 1036). When / when a previous LBT associated with a previous transmission is successful, the UE / base station may perform LBT for the transmission. When / when a previous LBT associated with a previous transmission fails, the UE / base station may not perform LBT for the transmission (e.g., directly perform the transmission without LBT). When / when a previous LBT associated with a previous transmission is successful, the UE / base station may perform a first type of LBT for the transmission. When / when a previous LBT associated with a previous transmission fails, the UE / base station may perform a second type of LBT for the transmission. When / when a previous LBT associated with a previous transmission is successful, the UE / base station may perform LBT for a transmission having a first value for the LBT parameter. When / when a previous LBT associated with a previous transmission fails, the UE / base station may perform LBT for a transmission having a second value for the LBT parameter. The LBT associated with the previous transmission is a first-type LBT. The LBT associated with the previous transmission can use a first value.

[0495] refer to Figure 10 In various embodiments / methods 1040, the UE / base station determines whether and / or how to perform LBT for the transmission based on the characteristics of the transmission (step 1044) (step 1042), where the characteristics may be the number of previously successful LBTs (step 1046). When / when the number of previously successful LBTs (e.g., within a window) is less than a threshold, the UE / base station may perform LBT for the transmission. When / when the number of previously successful LBTs is greater than the threshold, the UE / base station may not perform LBT for the transmission (e.g., directly perform the transmission without LBT). When / when the number of previously successful LBTs (e.g., within a window) is greater than the threshold, the UE / base station may perform a first type of LBT for the transmission. When / when the number of previously successful LBTs (e.g., within a window) is less than the threshold, the UE / base station may perform a second type of LBT for the transmission. When / when the number of previously successful LBTs (e.g., within a window) is greater than the threshold, the UE / base station may perform LBT for the transmission having a first value for the LBT parameter. When the number of previously successful LBTs (e.g., within a window) is less than a threshold, the UE / base station may perform an LBT for a transmission with a second value for the LBT parameter. The LBT associated with the previous transmission is a first type of LBT. The first value can be used for the LBT associated with the previous transmission.

[0496] refer to Figure 11In various embodiments / methods 1050, the UE / base station determines whether and / or how to perform LBT for a transmission based on transmission characteristics (step 1054) (1052), where the characteristic may be the ratio of previously successful LBTs (1056). When / when the ratio of previously successful LBTs (e.g., within a window) is less than a threshold, the UE / base station may perform LBT for the transmission. When / when the ratio of previously successful LBTs is greater than a threshold, the UE / base station may not perform LBT for the transmission (e.g., directly perform the transmission without LBT). When / when the ratio of previously successful LBTs (e.g., within a window) is greater than a threshold, the UE may perform a first type of LBT for the transmission. When / when the ratio of previously successful LBTs (e.g., within a window) is less than a threshold, the UE / base station may perform a second type of LBT for the transmission. When / when the ratio of previously successful LBTs (e.g., within a window) is greater than a threshold, the UE / base station may perform LBT for a transmission having a first value for the LBT parameter. When the rate of previously successful LBTs (e.g., within a window) is less than a threshold, the UE / base station may perform an LBT for a transmission with a second value for the LBT parameter. The LBT associated with the previous transmission is a first type of LBT. The first value can be used for the LBT associated with the previous transmission.

[0497] Previously, the transfer could be done within the window. Previously, the LBT could be done within the window.

[0498] Through various embodiments of the present invention, LBT can be replaced by a channel access scheme or channel access mechanism.

[0499] Through various embodiments of the invention, unless otherwise indicated, the invention describes the behavior or operation of a single serving cell.

[0500] Through various embodiments of the present invention, unless otherwise indicated, the present invention describes the behavior or operation of multiple serving cells.

[0501] Through various embodiments of the invention, unless otherwise indicated, the invention describes the behavior or operation of a single bandwidth portion.

[0502] Through various embodiments of the present invention, unless otherwise indicated, the base station configures multiple bandwidth portions for the UE.

[0503] Through various embodiments of the present invention, unless otherwise indicated, the base station configures a single bandwidth portion for the UE.

[0504] refer to Figure 12 Embodiments of the present invention may include a method 1060 for a device / UE, which includes determining whether and / or how to perform LBT for a transmission based on the characteristics of the transmission (step 1064) (step 1062).

[0505] In some embodiments, the characteristics of the transmission include resource allocation for the transmission.

[0506] In some embodiments, the characteristics of the transmission include the manner in which resources are allocated for the transmission.

[0507] In some embodiments, the characteristics of the transmission include the length or size of the resources allocated for the transmission.

[0508] In some embodiments, the characteristics of the transmission include the amount of resources allocated for the transmission.

[0509] In some embodiments, if the resources allocated for transmission are greater than a threshold, LBT is performed for the transmission.

[0510] In some embodiments, LBT is not performed for a transmission if the resources allocated for transmission are less than a threshold.

[0511] In some embodiments, the threshold is indicated by the base station.

[0512] In some embodiments, the threshold is predefined or fixed.

[0513] In some embodiments, the threshold is the number of PRBs.

[0514] In some embodiments, the threshold is the number of symbols.

[0515] In some embodiments, the threshold is the number of time slots.

[0516] In some embodiments, the threshold is a time slot.

[0517] In some embodiments, if the first method is used to allocate resources for transmission, then LBT is performed for the transmission.

[0518] In some embodiments, if the second method is used to allocate resources for transmission, LBT is not performed for the transmission.

[0519] In some embodiments, if the resources used for transmission are configured, LBT is performed for the transmission.

[0520] In some embodiments, if the resources used for transmission are indicated by DCI, LBT is not performed for the transmission.

[0521] Return to reference Figure 3 and Figure 4In one or more embodiments of the device / UE 300, the device / UE 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to: (i) determine whether and / or how to perform LBT for a transmission; and (ii) wherein the determination is based on one or more characteristics of the transmission. Furthermore, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[0522] refer to Figure 13 Embodiments of the present invention may include a method 1070 for a device / base station, which includes determining whether and / or how to perform LBT for a transmission based on the characteristics of the transmission (step 1074) (step 1072).

[0523] In some embodiments, the characteristics of the transmission include resource allocation for the transmission.

[0524] In some embodiments, the characteristics of the transmission include the manner in which resources are allocated for the transmission.

[0525] In some embodiments, the characteristics of the transmission include the length or size of the resources allocated for the transmission.

[0526] In some embodiments, the characteristics of the transmission include the amount of resources allocated for the transmission.

[0527] In some embodiments, if the resources allocated for transmission are greater than a threshold, LBT is performed for the transmission.

[0528] In some embodiments, LBT is not performed for a transmission if the resources allocated for transmission are less than a threshold.

[0529] In some embodiments, the threshold is indicated by the base station.

[0530] In some embodiments, the threshold is predefined or fixed.

[0531] In some embodiments, the threshold is the number of PRBs.

[0532] In some embodiments, the threshold is the number of symbols.

[0533] In some embodiments, the threshold is the number of time slots.

[0534] In some embodiments, the threshold is a time slot.

[0535] In some embodiments, if the first method is used to allocate resources for transmission, then LBT is performed for the transmission.

[0536] In some embodiments, if the second method is used to allocate resources for transmission, LBT is not performed for the transmission.

[0537] In some embodiments, if the resources used for transmission are configured, LBT is performed for the transmission.

[0538] In some embodiments, if the resources used for transmission are indicated by DCI, LBT is not performed for the transmission.

[0539] Return to reference Figure 3 and Figure 4 In one or more embodiments of the device / base station 300, the device / base station 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to: (i) determine whether and / or how to perform LBT for a transmission; and (ii) wherein the determination is based on transmission characteristics. Furthermore, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[0540] refer to Figure 14 Embodiments of the present invention may include a method 1080 for a device / base station, comprising, at step 1082, operating in a shared spectrum. The base station transmits CSI-RS on a first resource on the channel after sensing the channel (step 1084), wherein the first resource is indicated by DCI (step 1086). The base station further transmits CSI-RS on a second resource on the channel without sensing the channel (step 1088), wherein the second resource is indicated by RRC configuration (step 1090).

[0541] In some embodiments, CSI-RS on a second resource is used to detect bursts.

[0542] In some embodiments, if CSI-RS is transmitted on the first resource, the base station transmits CSI-RS on the channel after sensing the channel.

[0543] In some embodiments, the base station transmits CSI-RS on a second resource for burst detection, or transmits CSI-RS on a channel without sensing the channel.

[0544] In some embodiments, the base station does not perform LBT for CSI-RS transmissions on the second resource.

[0545] In some embodiments, the base station performs LBT for CSI-RS transmissions on the first resource.

[0546] In some embodiments, the first resource and the second resource are on the serving cell.

[0547] Return to reference Figure 3 and Figure 4 In one or more embodiments of the device / base station 300, the device / base station 300 includes program code 312 stored in memory 310. CPU 308 is executable of program code 312 to: (i) operate in a shared spectrum; (ii) transmit CSI-RS on a first resource on the channel after sensing the channel; (iii) wherein the first resource is indicated by DCI; (iv) transmit CSI-RS on a second resource on the channel without sensing the channel; and (v) wherein the second resource is indicated by RRC configuration. Furthermore, CPU 308 is executable of program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[0548] refer to Figure 15 Embodiments of the present invention include a method 1100 for an apparatus / base station, comprising, at step 1102, operating in a shared spectrum. The base station performs LBT for CSI-RS transmissions on a first resource (step 1104), wherein the first resource is indicated by a DCI (step 1106). The base station does not perform LBT for CSI-RS transmissions on a second resource (step 1108), wherein the second resource is indicated by an RRC configuration (step 1110).

[0549] In some embodiments, CSI-RS on a second resource is used to detect bursts.

[0550] In some embodiments, if CSI-RS is transmitted on the first resource, the base station performs LBT for CSI-RS.

[0551] In some embodiments, when CSI-RS is transmitted on a second resource for burst detection, the base station does not perform LBT for CSI-RS.

[0552] In some embodiments, the first resource and the second resource are on the serving cell.

[0553] Return to reference Figure 3 and Figure 4 In one or more embodiments of the device / base station 300, the device / base station 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to: (i) operate in a shared spectrum; (ii) perform LBT for CSI-RS transmissions on a first resource; (iii) wherein the first resource is indicated by DCI; (iv) not perform LBT for CSI-RS transmissions on a second resource; and (v) wherein the second resource is indicated by RRC configuration. Furthermore, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[0554] Any combination of the concepts or teachings above may be combined or formed into new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.

[0555] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein may be used independently, alone, and / or in combination with multiple methods, alternatives, steps, examples, and embodiments.

[0556] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, an apparatus or method can be implemented using any number of aspects set forth herein. Furthermore, this apparatus or method can be implemented or practiced using other structures, functions, or structures and functions other than or different from one or more of the aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time-hopping sequence.

[0557] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0558] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or combinations thereof, designed using source decoding or some other technique) and various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software modules"), or combinations thereof, with instructions. To clearly illustrate this interchangeability between hardware and software, the functionality of the various illustrative components, blocks, modules, circuits, and steps has been described above in general terms. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as causing a deviation from the scope of this disclosure.

[0559] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein and to execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0560] It should be understood that any particular order or hierarchy of steps in any disclosed process is an instance of an example method. It should be understood that a particular order or hierarchy of steps in a process may be rearranged based on design preferences while remaining within the scope of this disclosure. The appended method claims present the elements of the various steps in an exemplary order, but are not intended to limit us to the particular order or hierarchy presented.

[0561] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with a software module executed by a processor, or a combination of both. The software module (e.g., containing executable instructions and associated data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage media known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage media and write information to the storage media. Example storage media can be integrated with the processor. The processor and storage media can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage media can reside in a user equipment as discrete components. Furthermore, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some aspects, the computer program product may include packaging material.

[0562] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications are possible. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which this invention pertains.

Claims

1. A method for a base station to operate in a shared spectrum, characterized in that, include: In the case where the channel state information reference signal, which is not used to detect bursts, is transmitted on the first resource of the channel after the channel is sensed, as indicated by the downlink control information; as well as In the event that the channel state information reference signal for detecting bursts is transmitted on the second resource as instructed by the radio resource control configuration, the channel state information reference signal is transmitted on the second resource on the channel without sensing the channel.

2. The method according to claim 1, characterized in that, This further includes not performing a listen-before-speak procedure for the transmission of channel state information reference signals on the second resource.

3. The method according to claim 1, characterized in that, It further includes performing a listen-before-speak operation for the transmission of channel state information reference signals on the first resource.

4. The method according to claim 1, characterized in that, The first resource and the second resource are on the serving cell.

5. A base station configured to operate in a shared spectrum, characterized in that, include: Memory; as well as A processor operatively coupled to the memory, wherein the processor is configured to execute program code to: In the case where the channel state information reference signal, which is not used to detect bursts, is transmitted on the first resource as indicated by downlink control information, the channel state information reference signal is transmitted on the first resource on the channel after the channel is sensed. as well as In the event that the channel state information reference signal for detecting bursts is transmitted on the second resource as instructed by the radio resource control configuration, the channel state information reference signal is transmitted on the second resource on the channel without sensing the channel.

6. The base station according to claim 5, characterized in that, The processor is further configured to execute the program code to perform a listen-before-speak operation without regard to the transmission of channel state information reference signals on the second resource.

7. The base station according to claim 5, characterized in that, The processor is further configured to execute the program code to perform a listen-before-speak for the transmission of channel state information reference signals on the first resource.

8. The base station according to claim 5, characterized in that, The first resource or the second resource is on the serving cell.

9. The base station according to claim 5, characterized in that, The channel is a carrier or part of a carrier consisting of a continuous set of resource blocks.

Images