Method and apparatus for listen-before-talk mode for random access response in wireless communication system

Abstract

Methods, systems, and devices are provided for listen-before-talk mode of random access response in wireless communication systems, such that channel access type and cyclic prefix extended random access response indication can be more efficient. A method of a user equipment can include initiating a random access procedure, receiving a random access response, where the random access response includes a channel access type indication, and determining whether to perform listen-before-talk for a Msg3 based on the channel access type indication in the random access response.

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 227,748, filed July 30, 2021, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for a listen-before-talk (LBT) mode for random access response in wireless communication systems. 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 using Internet Protocol (IP) packets. This 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) 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] Methods, systems, and apparatus are provided for a listen-before-talk (LBT) mode for random access response (RAR) in wireless communication systems, enabling more efficient RAR indication of channel access type and cyclic prefix (CP) extensions.

[0007] In various embodiments, the method of the user equipment (UE) may include: initiating a random access procedure; receiving a RAR, wherein the RAR includes a channel access type indication; and determining whether to perform LBT for Msg3 based on the channel access type indication in the RAR.

[0008] In various embodiments, the UE's method may include: initiating a random access procedure; receiving a RAR, wherein the RAR includes a channel access type indication; and determining, based on the UE's LBT mode, whether to perform an LBT for Msg3 regardless of the channel access type indication in the RAR.

[0009] In various embodiments, the base station's method may include: receiving or detecting a preamble received from the UE; transmitting a RAR to the UE, wherein the RAR includes a channel access type field regardless of whether LBT is performed. 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 an embodiment of the present invention. Figure 3 Functional block diagram of the program code.

[0014] Figure 5 It comes from 3GPP TS 38.211 V15.7.0. Figure 4 3.1-1: Reproduction of the uplink-downlink timing relationship.

[0015] Figure 6 This is a reproduction of Table 4.2.1-1 from Draft 3GPP TS 37.213 V16.4.0: Channel Access Priority Class (CAPC) for UL.

[0016] Figure 7 This is a flowchart of a method for a UE according to an embodiment of the present invention, the method including triggering a RAR and determining, at least based on the UE's LBT mode, whether there is an indication in the RAR of channel access type and / or CP extension.

[0017] Figure 8 This is a flowchart of a method for a base station according to an embodiment of the present invention, the method including determining, at least based on the LBT mode of the UE, whether an indication of channel access type and / or CP extension exists in the RAR.

[0018] Figure 9 This is a flowchart of a UE method according to an embodiment of the present invention, the method including initiating a random access procedure and receiving a RAR, wherein the RAR includes a channel access type indication.

[0019] Figure 10 This is a flowchart of a UE method according to an embodiment of the present invention, the method including receiving a RAR, wherein the RAR includes a channel access type indication.

[0020] Figure 11 This is a flowchart of a base station method according to an embodiment of the present invention, the method including receiving or detecting a preamble and transmitting a RAR, wherein the RAR includes a channel access type field regardless of whether LBT is performed.

[0021] Figure 12 This is a flowchart of a UE method according to an embodiment of the present invention, the method including initiating a random access procedure and receiving a RAR, wherein the RAR includes a channel access type indication.

[0022] Figure 13 This is a flowchart of a UE method according to an embodiment of the present invention, the method including initiating a random access procedure and receiving a RAR, wherein the RAR includes a channel access type indication.

[0023] Figure 14 This is a flowchart of a base station method according to an embodiment of the present invention, the method including receiving or detecting a preamble received from a UE and transmitting a RAR to the UE. Detailed Implementation

[0024] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is described primarily in the context of the 3GPP architecture reference model. However, it should be understood that, with the aid of the disclosed information, those skilled in the art can readily adapt and implement aspects of the invention in 3GPP2 network architectures and other network architectures.

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

[0026] Specifically, the exemplary wireless communication systems described below can be designed to support one or more standards, such as those provided by the consortium referred to herein as 3GPP, which is named the “3rd Generation Partnership Project”, including: [1] 3GPP TS 38.211V15.7.0, “NR Physical Channels and Modulation”; [2] Draft 3GPP TS37.213V16.4.0, “NR Physical Layer Procedures for Shared Spectrum Channel Access”; [3] RP-202925, “Modified WID: Extending Current NR Operation to 71 GHz”; [4] 3GPP TS 38.213V16.6.0, “NR Physical Layer Procedures for Control”; and [5] 3GPP TS 38.212V16.6.0, “NR Multiplexing and Channel Decoding”. The standards and documents listed above are hereby explicitly and entirely incorporated herein by reference in their entirety.

[0027] 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 can utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, which 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, which 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 frequency different from that used by reverse link 118.

[0028] Each group of antennas and / or the area in which they 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 access network 100.

[0029] In communications via forward links 120 and 126, the transmit antennas of access network 100 utilize beamforming to improve the signal-to-noise ratio of the forward links used for different access terminals 116 and 122. Furthermore, compared to access networks that transmit to all their access terminals via a single antenna, access networks that use beamforming to transmit to access terminals randomly distributed within their coverage area cause less interference to access terminals in neighboring cells.

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

[0031] 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 multiple data streams is provided from the data source 212 to the transport (TX) data processor 214.

[0032] 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 streams based on a specific decoding scheme selected for each data stream to provide decoded data.

[0033] 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. Instructions executed by processor 230 determine the data rate, decoding, and modulation for each data stream. Memory 232 is coupled to processor 230.

[0034] 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 transmitting said symbols therefrom.

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

[0036] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received 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.

[0037] The RX data processor 260 then uses specific receiver processing technology from N R 254 receivers receive and process N R Each received symbol stream provides N TEach detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data used for 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.

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

[0039] The reverse link message may include various types of information about 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.

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

[0041] Memory 232 can be used to temporarily store some buffered / calculated data from 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 260 via processor 270, some buffered data from 236, or some specific program code.

[0042] Go to 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, the communication device 300 in the wireless communication system can be used to achieve... 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, pass received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.

[0043] Figure 4 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 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.

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

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

[0046] 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 or apparatus. The use of terms such as "based on," "more precisely," and "example" in the following disclosure is merely to suggest one possible embodiment of the particular method or apparatus and does not limit its application.

[0047] The new RAT (NR) for 5G uses frame structures to accommodate various types of requirements for time and frequency resources (e.g., [1] 3GPP TS 38.211 V15.7.0), ranging from ultra-low latency (~0.5ms) to latency-tolerant services for massive machine-type (MTC), and from high peak rates for enhanced mobile broadband (eMBB) to extremely low data rates for MTC. A key focus of this study is low latency aspects, such as short transmission time intervals (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 features of NR are included in the initial phase / version.

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

[0049] 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 Orthogonal Frequency Division Multiplexing (OFDM) symbols in 1 ms and a subcarrier spacing of 15 kHz, when the subcarrier spacing changes to 30 kHz, under the assumption of the same Fast Fourier Transform (FFT) size and the same CP structure, there will be 28 OFDM symbols in 1 ms. Equivalently, if the number of OFDM symbols in the TTI remains the same, the TTI 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 Physical Resource Blocks (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.

[0050] The following section provides more details on the design of the NR frame structure, channels, and basic parameters based on [1] 3GPP TS 38.211 V15.7.0:

[0051] ******************************** Beginning of quotation *************************************

[0052] ---------------------------------------------------------------------

[0053] 4-frame structure and physical resources

[0054] 4.1 General Provisions

[0055] Throughout this specification, unless otherwise specified, the sizes of the fields in the time domain are expressed in time units T. c =1 / (Δf) max ·N f ) express, 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] Table 4.2-1 provides support for multiple OFDM basic parameters, where μ and the cyclic prefix used for the bandwidth portion 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, expansion 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 =(N TA +N TA,offset )T c Beginning, where N TA,offset Given [5,TS 38.213].

[0065] Figure 5 It comes from 3GPP TS 38.211V15.7.0. Figure 4 3.1-1: Reproduction of the 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 Existing in time slots 1 consecutive OFDM symbol, of which This depends on the cyclic prefix given in Tables 4.3.2-1 and 4.3.2-2. Time slots in subframes The start of OFDM symbols in the same subframe The beginnings are aligned in time.

[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 sub-clause 11.1 of [5, TS38.213].

[0069] In the time slots of a downlink frame, the UE will assume that downlink transmissions occur only 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] In a group of cells, full-duplex communication is not possible and simultaneous transmission and reception are not supported, as defined by parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306]. UEs are not expected to be in the same or different cells within the same group of cells before the end of the last received downlink symbol, prior to N. Rx-Tx T c Transmission is performed on the uplink in one of the cells within the group of cells, where N Rx-Tx As given in Table 4.3.2-3.

[0072] UEs that cannot perform full-duplex communication in all cells within a group of cells and do not support simultaneous transmission and reception as defined by parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306] are not expected to be in the same or different cells within the same group of cells before the end of the last transmitted uplink symbol, prior to N. Tx-Rx T c Reception is performed in the downlink within one of the cells in the group of cells, where N Tx-Rx As given in Table 4.3.2-3.

[0073] UEs incapable of full-duplex communication are not expected to be in the same cell before N after the end of the last received downlink symbol. Rx-Tx T c Transmission occurs in the uplink, where N Rx-Tx As given in Table 4.3.2-3.

[0074] UEs incapable of full-duplex communication are not expected to be in the same cell before N, after the end of the last transmitted uplink symbol. Tx-Rx T c Reception occurs in the downlink, 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 the standard cyclic prefix.

[0076]

[0077] Table 4.3.2-2: Number of OFDM symbols per slot, number of slots per frame, and number of slots per subframe used to extend 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.3 Resource Elements

[0083] Each element in the resource grid used for antenna port p and subcarrier spacing configuration μ is called a resource element, and is defined by (k, l). p，μ A unique identifier, where k is the exponent in the frequency domain and l represents the sign position in the time domain relative to a reference point. Resource element (k, l) p，μ Corresponding to physical resources and complex values When there is no risk of confusion or a specific antenna port or subcarrier spacing is not specified, indices p and μ can be discarded, thus obtaining or a k，l .

[0084] 4.4.4 Resource Blocks

[0085] 4.4.4.1 General Provisions

[0086] Resource blocks are defined in the frequency domain A series of consecutive subcarriers.

[0087] 4.4.4.3 Common Resource Blocks

[0088] The common resource blocks are numbered from 0 upwards in the frequency domain for the subcarrier spacing configuration μ. The center of subcarrier 0 of the common resource block 0 used for the subcarrier spacing configuration μ coincides with 'point A'.

[0089] Number of common resource blocks in the frequency domain The relationship between the resource element (k, l) used for subcarrier spacing configuration μ is derived by the following formula:

[0090]

[0091] Here, k is defined relative to point A such that k = 0 corresponds to a subcarrier centered around point A.

[0092] 4.4.4.4 Physical Resource Blocks

[0093] The physical resource blocks used for subcarrier configuration μ are defined within the bandwidth portion and range from 0 to... Number, where i is the number of the bandwidth section. Physical resource blocks within bandwidth section i. With common resource blocks The relationship between them is given by the following formula:

[0094]

[0095] in It is a shared resource block, where the bandwidth portion starts relative to shared resource block 0. Index μ can be discarded when there is no risk of obfuscation.

[0096] 4.4.4.5 Virtual Resource Blocks

[0097] Virtual resource blocks are defined within the bandwidth portion and range from 0 to... Number, where i is the number of the bandwidth portion.

[0098] 4.4.5 Bandwidth Section

[0099] The bandwidth portion is the given fundamental parameter μ in the bandwidth portion i on a given carrier, as defined in sub-clause 4.4.4.3. i A subset of contiguous shared resource blocks. Start position. The number of resource blocks in the bandwidth portion They should be satisfied separately. and The bandwidth configuration is described in Clause 12 of [5, TS 38.213].

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

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

[0102] Unless otherwise stated, the descriptions in this specification apply to each of the bandwidth sections. When there is no risk of confusion, the exponent μ can be derived from... and throw away.

[0103] *********************************End of quotation*************************************

[0104] When accessing unlicensed spectrum, such as shared spectrum, a mechanism may be needed to determine whether a device (e.g., 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 may detect / receive signals on the spectrum / serving cell to determine whether the spectrum is available. When a device does not detect a signal or is silent for a period of time, for example, the device may consider the spectrum available and perform a transmission. On the other hand, when a device detects some signals on the spectrum, for example, with a specific strength from other devices, the device may consider the spectrum currently occupied and prevent its transmission. This mechanism is called Listen-Before-Speak (LBT). There may be some further details about how LBT is performed, such as the threshold at which a device determines whether the channel is currently occupied (e.g., the device may consider a weak signal as silent), the timing of the detection performed by the device when the LBT test is unsuccessful, and / or the timing and / or the timing and / or the execution of another test of the detection. Further details of the channel access scheme can be found in the following draft 3GPP TS37.213V16.4.0 [2]:

[0105] *******************************Quotation begins************************************

[0106] ---------------------------------------------------------------------

[0107] 4-channel access procedure

[0108] 4.0 General Principles

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

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

[0111] The channel access procedure is a sense-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. Sensing time slot duration T sl It is considered idle if the eNB / gNB or UE senses the channel during the sensing slot duration and determines that the detected power is less than the energy detection threshold X within at least 4µs of the sensing slot duration. Thresh Otherwise, the sensing time slot duration T sl They are considered busy.

[0112] - Channel occupancy refers to the transmission of an eNB / gNB / UE on a channel after the corresponding channel access procedure in this clause is executed.

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

[0114] - A DL transmission burst is defined as a set of transmissions from an eNB / gNB without 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 can transmit transmissions after gaps within a DL transmission burst without sensing the availability of the corresponding channel.

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

[0116] - 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:

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

[0118] 4.1 Downlink Channel Access Procedure

[0119] eNBs operating LAA Scells on the channel and gNBs performing transmissions on the channel shall perform the channel access procedures described in this clause for accessing the channel performing the transmission.

[0120] In this clause, X is used for sensing. Thresh Adjustments shall be made as described in Clause 4.1.5 where applicable.

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

[0122] 4.1.1 Type 1DL Channel Access Procedure

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

[0124] - 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

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

[0126] eNB / gNB can delay the duration T dA transmission is transmitted after the channel is first sensed to be idle during the sensing time slot duration and after counter N is 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:

[0127] 1) Set N = N init , where N init It is uniformly distributed between 0 and CW p A random number between these values ​​is generated, and then proceeds to step 4;

[0128] 2) If N > 0 and eNB / gNB selects a decrementing counter, then set N = N - 1;

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

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

[0131] 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;

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

[0133] 4.1.2 Type 2DL Channel Access Procedure

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

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

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

[0137] - 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

[0138] - The transmission of the eNB / gNB after the UE's transmission, following a 25µs gap in the shared channel occupancy as described in Clause 4.1.3.

[0139] The Type 2B or Type 2C DL channel access procedures as described in Clauses 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 Clause 4.1.3.

[0140] 4.1.2.1 Type 2A DL Channel Access Procedure

[0141] eNB / gNB can sense at least a distance T short_dl =After sensing that the channel is idle within 25us, DL transmission is immediately transmitted. T short_dl Due to duration T f =16us followed by a sensing time slot, and T f Included in T f The sensing time slot at the beginning. If T short_dl If both sensing time slots are sensed as idle, then the channel is considered to be in T short_dl There is free time in the middle.

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

[0143] gNB can be used for duration T f = After sensing that the channel is idle within 16us, DL transmission is immediately sent. T f Included in T f The sensing time slots occurring within the last 9 µs. If the channel is sensed to be idle within a total of at least 5 µs, with at least 4 µs of sensing occurring within the sensing time slots, then the channel is considered to be in the duration T. f Internal free space.

[0144] 4.1.2.3 Type 2C DL Channel Access Procedure

[0145] When the gNB follows the procedures in this clause 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.

[0146] 4.2 Uplink Channel Access Procedure

[0147] 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 clause for the UE to access the channel performing the transmissions.

[0148] In this clause, transmissions from the UE are treated as separate UL transmissions, regardless of whether there are gaps between transmissions, and the X used for sensing Thresh Adjustments shall be made as described in Clause 4.2.3 where applicable.

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

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

[0151] 4.2.1 Channel access procedure for uplink transmission

[0152] The UE may perform UL transmission through one of the Type 1 or Type 2 UL channel access procedures. The Type 1 channel access procedure is described in Clause 4.2.1.1. The Type 2 channel access procedure is described in Clause 4.2.1.2.

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

[0154] The UE shall 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 clause.

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

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

[0157] If the SRS is triggered but the PUCCH transmission does not schedule a DL assignment instruction for a Type 2 channel access procedure, the UE should use the Type 2 channel access procedure.

[0158] 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, then the UE should attempt to transmit SRS according to the uplink channel access procedure specified for SRS transmission.

[0159] 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 assignment 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, then 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, then the UE can use a Type 1 channel access procedure to transmit other UL transmissions without applying CP extension.

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

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

[0162] 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 Clause 5.6.2 in [9].

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

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

[0165] 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 assumes that the gNB uses channel access priority class p=4 during the channel occupancy time.

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

[0167] As described in Clause 4.1.3, if the UE sets the 'COT sharing indication' in the AUL-UCI to '1' in a subframe within an autonomous uplink transmission, the total channel occupancy time (including subsequent DL transmissions) of the autonomous uplink transmission obtained through the channel access procedure in this clause shall not exceed T. ulmcot，p T ulmcot，p The information is given in Table 4.2.1-1.

[0168] Figure 6 This is a reproduction of Table 4.2.1-1 from Draft 3GPP TS 37.213 V16.4.0: Channel Access Priority Class (CAPC) for UL.

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

[0170] 4.2.1.0.0 Channel access procedure after detecting common DCI

[0171] If the UE detects the 'UL Duration and Offset' field in DCI Format 1C, as described in Clause 5.3.3.1.4 of [5], then the following applies:

[0172] - 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 a type 2 channel access procedure for transmission in subframe n+l+i, where i = 0, 1, ... d-1, regardless of the channel access type transmitted in the UL grant for those subframes, provided that the end of the UE transmission occurs in or before subframe n+l+d-1.

[0173] - If the 'UL Duration and Offset' field indicates the 'UL Offset' l and 'UL Duration' d for subframe n, and the 'COT Sharing Indication for AUL' field is set to '1', then assuming any priority class in subframe n+l+i, a UE configured with autonomous UL can use a Type 2 channel access procedure for autonomous UL transmission, 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 transmissions between n+l and n+l+d-1 should be contiguous.

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

[0175] 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 20, as described in clause 11.1.1 of [7], then the following may apply:

[0176] - The UE may switch from a Type 1 channel access procedure as described in Clause 4.2.1.1 to a Type 2A channel access procedure as described in Clause 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.

[0177] 4.2.1.0.1 Channel Access Procedure for Continuous UL Transmission

[0178] For continuous UL transmissions, the following applies:

[0179] If the UE is scheduled to use a UL-granted transmission set containing a PUSCH, and if the UE is unable to access a channel for a transmission in the set before the last transmission according to one of the Type 1, Type 2, or Type 2A UL channel access procedures, then the UE should attempt to transmit the next transmission according to the channel access type indicated in the UL grant. Otherwise, if the UE is unable to access a channel for a transmission in the set before the last transmission according to the Type 2B UL channel access procedure, then the UE should attempt to transmit the next transmission according to the Type 2A UL channel access procedure.

[0180] - If the UE is scheduled by the gNB to use a set of UL transmissions containing PUSCH or SRS symbols for UL permission transmission, then the UE should not apply CP extension to the remaining UL transmissions in the set after the first UL transmission following the access channel.

[0181] - If a UE is scheduled to transmit a set of seamless, continuous UL transmissions, including a PUSCH with one or more UL-granted permissions, a PUCCH with one or more DL-granted permissions, or an SRS with one or more DL-granted or UL-granted permissions, and the UE transmits one of the scheduled UL transmissions in the set after accessing a channel according to a UL channel access procedure of type 1, type 2, type 2A, type 2B, or type 2C, then the UE may continue transmitting the remaining UL transmissions in the set (if any).

[0182] - If the UE is configured to transmit a set of consecutive PUSCH or SRS transmissions on resources configured by the gNB, the time-domain resource configuration limits multiple transmission opportunities, and if the UE is unable to access the channel according to the Type 1 UL channel access procedure for transmission in a transmission opportunity prior to the last transmission opportunity, then the UE should attempt to transmit in the next transmission opportunity according to the Type 1 UL channel access procedure. If the UE transmits in one of the multiple transmission opportunities after accessing the channel according to the Type 1 UL channel access procedure, then the UE may continue transmitting in the remaining transmission opportunities in the set, wherein each transmission opportunity begins at the start symbol of the configured PUSCH granted during the duration of the COT.

[0183] - If the UE is configured by the gNB to transmit a set of seamless, continuous UL transmissions, including PUSCH, periodic PUCCH, or periodic SRS, and the UE transmits one of the configured UL transmissions in the set after accessing the channel according to the Type 1 UL channel access procedure, then the UE may continue transmitting the remaining UL transmissions in the set (if any).

[0184] - The UE is not expected to be indicated with respect to different channel access types in any consecutive UL transmissions without gaps between transmissions, except for the case where the first UL transmission in a consecutive UL transmission is identified as a Type 2B or Type 2C UL channel access procedure.

[0185] For UL deliveries with multiple start locations scheduled by the eNB, the following applies:

[0186] If the UE is scheduled by the eNB to transmit a PUSCH mode 1 transmission using the type 1 channel access procedure indicated in the DCI, and if the UE is unable to access the channel for transmission according to the PUSCH start position indicated in the DCI, then the UE should attempt to transmit at symbol 7 in the same subframe according to the type 1 channel access procedure. There is no limit to the number of attempts the UE can make using the type 1 channel access procedure.

[0187] If the UE is scheduled by the eNB to transmit a PUSCH mode 1 transmission using the type 2 channel access procedure indicated in the DCI, and if the UE cannot access the channel for transmission according to the PUSCH start position indicated in the DCI, then the UE may attempt to transmit in the same subframe according to the type 2 channel access procedure at symbol 7. The number of attempts the UE should make in consecutive scheduled subframes containing the transmission is limited to w+1, where w is the number of consecutive scheduled subframes using the type 2 channel access procedure.

[0188] For continuous UL transmissions that include transmission pauses, the following applies:

[0189] - If the UE is scheduled to transmit a set of consecutive UL transmissions without gaps using one or more ULs, and if the UE has stopped transmitting during or before one of these UL transmissions in the set and before the last UL transmission in the set, and if the UE senses that the channel is continuously idle after the UE has stopped transmitting, then the UE can transmit the later UL transmission in the set using a Type 2 channel access procedure or a Type 2A UL channel access procedure without applying CP extension.

[0190] - If the UE senses that the channel is discontinuously idle after the UE has stopped transmitting, the UE can transmit a later UL transmission from the set using a Type 1 channel access procedure, wherein the UL channel access priority class is indicated in the DCI corresponding to the UL transmission.

[0191] For UL transfers following autonomous UL transfers, the following applies:

[0192] -If the UE is scheduled by the eNB to pass through channel c j The UL received on channel c is allowed i Up transmission, i≠j, and if the UE is in channel c i If the UE uses autonomous UL for transmission, then the UE should terminate the in-process PUSCH transmission using autonomous UL at least one subframe before the UL transmission authorized by the received UL.

[0193] - If the UE is granted permission to use a Type 1 channel access procedure to transmit PUSCH on the same channel starting from subframe n by a UL received from the eNB on the channel, and if at least for the first scheduled subframe is occupied If a resource block is specified and the indicated PUSCH start position is OFDM symbol zero, and if the UE begins autonomous UL transmission before subframe n using a Type 1 channel access procedure on the same channel, then the UE can transmit UL transmission without gaps from subframe n according to the received UL grant, provided that the priority class value of the executed channel access procedure is greater than or equal to the priority class value indicated in the UL grant, and autonomous UL transmissions in subframes prior to subframe n, regardless of the higher-layer parameter endingSymbolAUL, should end at the last OFDM symbol of the subframe. The sum of the lengths of autonomous UL transmissions and scheduled UL transmissions will not exceed the maximum channel occupancy time corresponding to the priority level value used to execute the autonomous uplink channel access procedure. Otherwise, the UE will terminate the ongoing autonomous UL transmission at least one subframe before the start of the UL transmission according to the UL grant received on the same channel.

[0194] For UL transmissions that follow UL transmissions that have been configured to be authorized for UL transmission, the following applies:

[0195] - If the UE is scheduled to transmit a UL transmission starting from symbol i in time slot n using a Type 1 channel access procedure without a CP extension with a corresponding CAPC, and if the UE starts a configured-allowed UL transmission before symbol i in time slot n using a Type 1 channel access procedure with a corresponding CAPC, and the scheduled UL transmission occupies all RBs or all RBs of a subset of the same channel occupied by the configured-allowed UL transmission, then the UE can directly continue transmitting the scheduled UL transmission from symbol i in time slot n to the corresponding CAPC without gaps, provided that the CAPC value of the executed channel access procedure is greater than or equal to the CAPC value corresponding to the scheduled UL transmission. The sum of the transmission durations of the configured-allowed UL transmission and the scheduled UL transmission should not exceed the MCOT duration corresponding to the CAPC value used to transmit the configured-allowed UL transmission. Otherwise, the UE should terminate the configured-allowed UL transmission by discarding the transmission on at least the last configured-allowed UL transmission symbol before symbol i in time slot n, and attempt to transmit the scheduled UL transmission according to the corresponding CAPC. According to the mechanism in Clause 11.1 of [7, TS 38.213], there is a symbol with a configured-allowed PUSCH transmission in the last symbol drop slot of the scheduled DCI's CORESET. In this case, if the UE cannot terminate the configured-allowed UL transmission, then the UE ignores the scheduled DCI.

[0196] 4.2.1.0.2 Conditions for maintaining Type 1 UL channel access procedures

[0197] 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:

[0198] - 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 to access the channel.

[0199] - 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, then the UE will terminate the ongoing channel access procedure.

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

[0201] 4.2.1.0.3 Conditions used to indicate the access procedure for type 2 channels.

[0202] The eNB / gNB can respectively instruct the Type 2 channel access procedure in the DCI containing PUSCH or PUCCH UL grant or DL ​​assignment schedule transmission on the channel, as follows:

[0203] If the UL transmission starts at t0 and ends at t0+T CO It occurs within a time interval, of which

[0204] -T CO =T mcot，p +T g ,

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

[0206] -T mcot，p The value is determined by the eNB / gNB as described in Clause 4.1.1.

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

[0208] then,

[0209] - If the eNB / gNB has transmitted on the channel in accordance with the channel access procedure described in Clause 4.1.1, the eNB / gNB may indicate the Type 2 channel access procedure in the DCI, or

[0210] - When the eNB has transmitted on the channel in accordance with the channel access procedure described in Clause 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 of PUSCH on the channel in subframe n, or

[0211] - When the eNB has acquired the channel on the channel according to the channel access procedure described in Clause 4.1.1 and using the maximum priority class value, the eNB may use the 'UL Duration and Offset' field and the 'COT Sharing Indication for AUL' field to indicate that a UE configured with 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

[0212] - The eNB / gNB may schedule UL transmissions on the channel after a duration of 25µs, which follow the transmissions of the eNB / gNB on the channel having a Type 2A channel access procedure for UL transmissions, as described in Clause 4.2.1.2.1.

[0213] eNB / gNB should be at t0 and t0+T CO UL transmissions can be scheduled between consecutive transmissions without gaps, provided they can be scheduled consecutively. For UL transmissions on the channel following a transmission on the channel using the Type 2A channel access procedure as described in Clause 4.2.1.2.1 in the eNB / gNB, the UE may use the Type 2A channel access procedure for UL transmissions.

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

[0215] 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 Clause 4.2.1.2.

[0216] 4.2.1.0.4 Channel Access Procedure for UL Multichannel Transmission

[0217] If UE

[0218] - Scheduled to transmit 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 simultaneously on all channels in channel set C, or

[0219] -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

[0220] If the channel frequencies of the channel set C are a subset of one of the set of channel frequencies defined in clause 5.7.4 of [2].

[0221] - The UE may use the Type 2 channel access procedure as described in Clause 4.2.1.2 on channel c i Transmitted on ∈C

[0222] -If in 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

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

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

[0225] - If the UE fails to access any of the channels with carrier bandwidth that the UE has been scheduled or configured with through UL resources, then the UE cannot access channel c within the carrier bandwidth. i Transmitted on ∈C.

[0226] 4.2.1.1 Type 1 UL Channel Access Procedure

[0227] This clause 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 clause applies to the following transmissions:

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

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

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

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

[0232] 1) Set N = N init Where N init It is uniformly distributed between 0 and CW p A random number between these values ​​is generated, and then proceeds to step 4;

[0233] 2) If N > 0 and the UE selects a decrementing counter, then set N = N - 1;

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

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

[0236] 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;

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

[0238] If the UE has not yet transmitted a UL transmission on the channel where the UL transmission is performed after step 4 in the above procedure, then the UE may transmit a transmission on the channel, provided that when the UE is ready to transmit the transmission, it is at least during the sensing time slot duration T. sl The channel is sensed to be idle, and there is a delay duration T immediately preceding the transmission. d The channel has been sensed to be idle for the entire duration of the time slot. If the channel has not been sensed to be idle during the time slot duration after the eNB / gNB is ready to transmit when the eNB / gNB first senses the channel, or if the channel is idle for the delay duration T immediately preceding this scheduled transmission. d Any sensing time slot duration T sl If the channel is not idle during the period, then during the delay duration T d After the channel is detected to be idle during the duration of the sensing time slot, the eNB / gNB proceeds to step 1.

[0239] Delay duration T d Due to duration T f=16us followed by mp consecutive time slot durations, where each time slot duration is T. sl =9us, and T f Included in T f The duration T of the idle time slot at the beginning sl .

[0240] CW min，p ≤CW p ≤CW max，p It's a competitive window. CW p The adjustment is described in Clause 4.2.2.

[0241] CW min，p and CW max，p Make the selection before step 1 of the above procedure.

[0242] m p CW min，p and CW max，p It is based on the channel access priority class p shown in Table 4.2.1-1 sent to the UE.

[0243] 4.2.1.2 Type 2 UL Channel Access Procedure

[0244] This clause describes the channel access procedure to be performed by the UE, where the duration spanned by the sensing slots that are sensed as idle prior to UL transmission is deterministic.

[0245] If the UE is instructed by the eNB to perform a Type 2 UL channel access procedure, the UE shall follow the procedure described in Clause 4.2.1.2.1.

[0246] 4.2.1.2.1 Type 2A UL Channel Access Procedure

[0247] If the UE is instructed to perform a Type 2AUL channel access procedure, then the UE uses the Type 2AUL channel access procedure for UL transmission. The UE can do so at least during the sensing interval T. short ul Transmit immediately after detecting an idle channel within 25µs. short_u1 Due to duration T f =16us followed by a sensing time slot, and T f Included in T f The sensing time slot at the beginning. If T short_ u l If both sensing time slots are sensed as idle, then the channel is considered to be in T short_ul There is free time in the middle.

[0248] 4.2.1.2.2 Type 2B UL Channel Access Procedure

[0249] If the UE is instructed to perform a Type 2B UL channel access procedure, then the UE uses the Type 2B UL channel access procedure for UL transmission. The UE can perform this procedure for a duration T. f = Transmit immediately after detecting channel idleness within 16us. T f Included in T f The sensing time slots occurring within the last 9 µs. If the channel is sensed to be idle within a total of at least 5 µs, with at least 4 µs of sensing occurring within the sensing time slots, then the channel is considered to be in the duration T. f Internal free space.

[0250] 4.2.1.2.3 Type 2C UL Channel Access Procedure

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

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

[0253] The semi-static channel occupancy-based channel assessment procedure described in this clause is intended for environments where, for example, regulatory levels and privacy policies ensure the absence of other technologies. If the gNB provides the UE with the higher-layer parameter ChannelAccessMode-r16='semi-static' via SIB1 or a dedicated configuration, then the gNB can allocate occupancy per T within every two consecutive radio frames. x Initiating periodic channel occupation, from i·T x Even-indexed radio frames start at the location and the maximum channel occupancy time T y =0.95T x T, in milliseconds x =period is a higher-level parameter provided in SemiStaticChannelAccessConfg, and

[0254] In the subsequent procedures of this clause, when the gNB or UE performs sensing for the purpose of assessing channel availability, at least for the sensing time slot duration T sl Sensing is performed during a period of 9µs. The corresponding X is used for performing sensing via gNB or UE. Thresh The adjustments are described in Clauses 4.1.5 and 4.2.3 respectively.

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

[0256] -gNB should be in the sensing time slot for at least T duration slUpon sensing that the channel is idle within 9µs, the gNB immediately initiates a DL transmission burst at the beginning of the channel occupancy period. If the channel is sensed to be busy, the gNB should not perform any transmissions during the current period.

[0257] - If the gap between the DL transmission burst and any previous transmission burst is greater than 16µs, then 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.

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

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

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

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

[0262] -gNB and UE must be at least T before the start of the next cycle. z =max(0.05T) x No transmission should be transmitted in a continuous set of symbols during a duration of 100us.

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

[0264] *********************************End of quotation*********************************

[0265] There are studies on operation in frequency bands above 52.6 GHz. Some amendments are under consideration 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 being 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 below in RP-202925 [3]:

[0266] **********************************Start of quotation*********************************

[0267] 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:

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

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

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

[0271] ○ 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.

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

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

[0274] ■ 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.

[0275] ■ If necessary, study and specify additional SCS (480kHz, 960kHz) for SSB in cases other than initial access.

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

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

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

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

[0280] ○ Enhancements supporting multi-PDSCH / PUSCH scheduling and HARQ support with a single DCI. Note: Coverage enhancements for multi-PDSCH / PUSCH scheduling are not implemented.

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

[0282] ○ 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.

[0283] ○ 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.

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

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

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

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

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

[0289] **********************************End of quotation*********************************

[0290] Random access procedures can be triggered for various purposes. For example, a random access procedure can be used to obtain UL transmission timing (e.g., for UL synchronization or to obtain UL timing advance), and / or to request UL permission, and / or for handover purposes and / or to establish a Radio Resource Control (RRC) connection and / or restore an RRC connection and / or re-establish an RRC connection and / or reclaim a beam. There can be 4-step random access procedures and 2-step random access procedures. Several messages can be exchanged between the UE and the base station, such as Msg1 (preamble), Msg2 (RAR), Msg3 and / or Msg4 for a 4-step random access procedure. Msg A and Msg B are involved. Further details of the random access procedure are quoted below from [4] 3GPP TS 38.213 V16.6.0 and [5] 3GPP TS 38.212 V16.6.0:

[0291] **********************************Start of quotation*********************************

[0292] --------------------------------------------------------------------

[0293] 8. Random Access Procedure

[0294] Before initiating the physical random access procedure, Layer 1 receives a set of SS / PBCH block indices from the higher layer and provides the corresponding set of RSRP measurements to the higher layer.

[0295] Prior to the initiation of a physical random access procedure, Layer 1 may receive instructions from a higher layer to perform a Type 1 random access procedure as described in Clauses 8.1 to 8.4 or a Type 2 random access procedure as described in Clauses 8.1 to 8.2A.

[0296] Before initiating the physical random access procedure, Layer 1 receives the following information from the higher layers:

[0297] - Configuration of physical random access channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources used for PRACH transmission).

[0298] - Parameters used to determine the root sequence and its cyclic shift in the PRACH preamble sequence set (index of the logical root sequence table, cyclic shift (N)). CS (and set types (unrestricted, restricted set A or restricted set B)).

[0299] From a physical layer perspective, the Type 1 L1 random access procedure includes the transmission of the random access preamble (Msg1) in the PRACH, the random access response (RAR) message (Msg2) with PDCCH / PDSCH, and, where applicable, the transmission of the PUSCH and PDSCH for contention resolution, which are scheduled by the RAR UL.

[0300] From the physical layer perspective, the Type 2L1 random access procedure includes the transmission of the random access preamble and PUSCH (MsgA) in PRACH and the reception of RAR messages (MsgB) with PDCCH / PDSCH, as well as, where applicable, the transmission of PUSCH and PDSCH for contention resolution, which are scheduled by backoff RARUL.

[0301] If the random access procedure is initiated by a PDCCH command to the UE, the PRACH transmission has the same SCS as the PRACH transmission initiated by a higher layer.

[0302] If the UE is configured with two UL carriers for the serving cell and the UE detects a PDCCH command, the UE uses the UL / SUL indicator field value from the detected PDCCH command to determine the UL carrier for the corresponding PRACH transmission.

[0303] 8.1 Random Access Preamble

[0304] The physical random access procedure is triggered after a request for PRACH transmission via a higher layer or PDCCH command. The configuration for PRACH transmission via a higher layer includes the following:

[0305] - Configuration for PRACH transmission [4, TS 38.211].

[0306] - Preamble Index, Preamble SCS, P PRACH，target This corresponds to RA-RNTI and PRACH resources.

[0307] Use the selected PRACH format on the indicated PRACH resource with the transmission power P as described in Clause 7.4. PRACH，b，f，c (i) Transmit PRACH.

[0308] For Type 1 random access procedures, ssb-perRACH-OccasionAndCB-PreamblesPerSSB provides the UE with N SS / PBCH block indices associated with a PRACH opportunity and R contention-based preambles per valid PRACH opportunity per SS / PBCH block index.

[0309] For a Type 2 random access procedure with a co-configuration of PRACH timings with a Type 1 random access procedure, the UE is provided with N SS / PBCH block indices associated with a PRACH timing via ssb-perRACH-OccasionAndCB-PreamblesPerSSB and Q contention-based preambles per valid PRACH timing per SS / PBCH block index via msgA-CB-PreamblesPerSSB-PerSharedRO. For a UE with a PRACH mask index provided via msgA-SSB-SharedRO-MaskIndex according to [11, TS38.321], PRACH delivery can be performed on a subset of PRACH timings associated with the same SS / PBCH block index within the SSB-RO mapping cycle.

[0310] For Type 2 random access procedures with separate configurations from Type 1 random access procedures that have PRACH timings, when provided, the UE is provided with N SS / PBCH block indices associated with a PRACH timing and R contention-based preambles per valid PRACH timing per SS / PBCH block index via msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB; otherwise, via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0311] For a Type 1 random access procedure, or for a Type 2 random access procedure with a configuration having separate PRACH timings from the Type 1 random access procedure, if N < 1, then one SS / PBCH block index maps to 1 / N consecutive valid PRACH timings, and R contention-based preambles with consecutive indices associated with the SS / PBCH block for each valid PRACH timing start from preamble index 0. If N ≥ 1, then R contention-based preambles with consecutive indices associated with the SS / PBCH block index n, 0 ≤ n ≤ N-1 for each valid PRACH timing start from preamble index 0. In the beginning, among them Provided by totalNumberOfRA-Preambles for Type 1 random access procedures, or by msgA-TotalNumberOfRA-Preambles for Type 2 random access procedures with PRACH timing separate from Type 1 random access procedures, and is an integer multiple of N.

[0312] For a Type 2 random access procedure with a configuration sharing PRACH timings with a Type 1 random access procedure, if N < 1, then one SS / PBCH block index maps to 1 / N consecutive valid PRACH timings, and Q contention-based preambles with consecutive indices associated with the SS / PBCH block for each valid PRACH timing start from preamble index R. If N ≥ 1, then Q contention-based preambles with consecutive indices associated with the SS / PBCH block index n, 0 ≤ n ≤ N-1 for each valid PRACH timing start from preamble index R. In the beginning, among them Provided by totalNumberOfRA-Preambles for Type 1 random access procedures.

[0313] For link recovery, the UE is provided with N SS / PBCH block indices associated with a PRACH timing via the Occasion in BeamFailureRecoveryConfig. For dedicated RACH configurations provided by RACH-ConfigDedicated, if cfra is provided, then the UE is provided with N SS / PBCH block indices associated with a PRACH timing via ssb-perRACH-Occasion in occasions. If N < 1, then one SS / PBCH block index maps to 1 / N consecutive valid PRACH timings. If N ≥ 1, then all N consecutive SS / PBCH block indices are associated with one PRACH timing.

[0314] The SS / PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon are mapped to valid PRACH timings in the following order, where the parameters are described in [4, TS 38.211].

[0315] - First, the ascending order of the preamble index within a single PRACH timeframe.

[0316] - Second, in ascending order of the frequency resource index used for frequency multiplexing PRACH timing.

[0317] - Third, in ascending order of the time resource index used for time-multiplexed PRACH timing within the PRACH slot.

[0318] Fourth, in ascending order of the index used for PRACH slots.

[0319] The associated period used for mapping the SS / PBCH block index to the PRACH timing, starting from frame 0, is the minimum value in the set determined by the PRACH configuration period according to Table 8.1-1, such that... Each SS / PBCH block index is mapped to the PRACH at least once within the associated period, wherein the UE obtains the value of ssb-PositionsInBurst from SIB1 or ServingCellConfigCommon. If an integer number of SS / PBCH blocks are indexed to PRACH timing mapping cycles within the associated period, and there are unmapped blocks... If a set of PRACH timings or PRACH preambles for an SS / PBCH block index is provided, then no SS / PBCH block index maps to said set of PRACH timings or PRACH preambles. An association pattern period comprises one or more association periods and is determined such that the pattern between the PRACH timing and the SS / PBCH block index repeats at most every 160 milliseconds. PRACH timings (if any) not associated with an SS / PBCH block index after an integer number of association periods are not used for PRACH transmission.

[0320] For a PRACH transmission triggered by a PDCCH command, if the value of the random access preamble index field is not zero, then the PRACH mask index field [5, TS 38.212] indicates the PRACH timing for the PRACH transmission, wherein the PRACH timing is associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH command.

[0321] For PRACH transmissions triggered by a higher layer, if an ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH timing used for the PRACH transmission, where the PRACH timing is associated with the selected SS / PBCH block index.

[0322] PRACH timings are mapped sequentially for each corresponding SS / PBCH block index. Each mapping cycle of consecutive PRACH timings for each SS / PBCH block index is reset by the index of the PRACH timing indicated by the mask index value. The UE selects the PRACH timing for PRACH transmission by the PRACH mask index value used for the indicated SS / PBCH block index in the first available mapping cycle.

[0323] For the indicated preamble index, the order of PRACH timing is:

[0324] - First, in ascending order of the frequency resource index used for frequency multiplexing PRACH timing.

[0325] - Second, in ascending order of the time resource index used for time-multiplexed PRACH timing within the PRACH slot.

[0326] - Third, in ascending order of the index used for PRACH slots.

[0327] For PRACH transmissions triggered after a request at a higher layer, if a csirs-ResourceList is provided, then the value of ra-OccasionList [12, TS 38.331] indicates a list of PRACH timings used for the PRACH transmission, where the PRACH timing is associated with a selected CSI-RS index indicated by csi-RS. The index of the PRACH timing indicated by ra-OccasionList is reset every associated mode cycle.

[0328] Table 8.1-1: Mapping between PRACH configuration cycle and SS / PBCH block to PRACH timing association cycle

[0329] PRACH configuration cycle (milliseconds) Associated cycles (number of PRACH configuration cycles) 10 {1，2，4，8，16} 20 {1，2，4，8} 40 {1，2，4} 80 {1，2} 160 {1}

[0330] All PRACH timings are valid for paired spectrum or supplemental uplink bands.

[0331] For unpaired spectrum

[0332] - If the UE is not provided with tdd-UL-DL-ConfgurationCommon, then the PRACH timing in the PRACH slot is valid, provided that it does not precede the SS / PBCH block in the PRACH slot and is received at least N times after the last SS / PBCH block reception symbol. gap It begins with a symbol, where N gap Provided in Table 8.1-2, and if channelAccessMode=semistatic is provided, it does not overlap with a set of consecutive symbols preceding the start of the next channel occupancy time in which the UE does not transmit [15, TS37.213].

[0333] The candidate SS / PBCH block indexes correspond to the SS / PBCH block indexes provided by ssb-PositionslnBurst in SIB1 or ServingCellConfigCommon, as described in Clause 4.1.

[0334] - If the UE is provided with tdd-UL-DL-ConfigurationCommon, then the PRACH timing in the PRACH slot is valid, provided that

[0335] -It is within the UL symbol, or

[0336] - It does not precede the SS / PBCH block in the PRACH slot, and is at least N after the last downlink symbol. gap The symbols and at least N after the last SS / PBCH block symbol gap It begins with a symbol, where N gap Provided in Table 8.1-2, and if channelAccessMode=semi-static is provided, it does not overlap with a set of consecutive symbols preceding the start of the next channel occupancy time in which no transmission will occur, as described in [15, TS 37.213].

[0337] The candidate SS / PBCH block index corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, as described in Clause 4.1.

[0338] For the preamble format B4[4, TS 38.211],

[0339] Table 8.1-2: N used for different preambles SCSμ gap value

[0340]

[0341] If a random access procedure is initiated via a PDCCH command, then if requested by a higher layer, the UE transmits the PRACH at the selected PRACH timing, as described in [11, TS 38.321], where the time between the last symbol received by the PDCCH command and the first symbol transmitted by the PRACH is greater than or equal to N. T，2 +Δ BWPSwitching +Δ Delay +T switch milliseconds, of which

[0342] -N T，2 It is the duration of N2 symbols corresponding to the PUSCH preparation time for UE processing capability 1 [6, TS 38.214], assuming μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH command and the SCS configuration of the corresponding PRACH transmission.

[0343] -If the UL BWP does not change during the action, then Δ BWPSwitching =0, and Δ BWPSwitching Additionally, it is defined in [10, TS38.133].

[0344] -For FR1, Δ Delay = 0.5 milliseconds, and for FR2, Δ Delay =0.25 milliseconds

[0345] -T switch The switching gap duration is as defined in [6, TS 38.214].

[0346] For PRACH transmission using 1.25kHz or 5kHz SCS, the UE determines N2, assuming SCS configuration μ = 0.

[0347] For single-cell operation or for operation with carrier aggregation in the same frequency band, the UE does not transmit PRACH and PUSCH / PUCCH / SRS in the same time slot, or does not transmit when the first or last symbol of the PRACH transmission in the first time slot is separated from the last or first symbol of the PUSCH / PUCCH / SRS transmission in the second time slot by less than N symbols, where N=2 for μ=0 or μ=1, N=4 for μ=2 or μ=3, and μ is the SCS configuration for the UL BWP in operation. For PUSCH transmission with repetition type B, this applies to every actual repetition of the PUSCH transmission [6, TS 38.214].

[0348] 8.1A PUSCH for Type 2 Random Access Procedures

[0349] For Type 2 random access procedures, where applicable, the UE transmits the PUSCH after transmitting the PRACH. The UE encodes the transport block provided for PUSCH transmission using a redundancy version number of 0. The PUSCH transmission is at least N symbols after the PRACH transmission, where N=2 for μ=0 or μ=1, and N=4 for μ=2 or μ=3, and μ is the SCS configuration used for the UL BWP in operation.

[0350] If the PUSCH timing associated with the DMRS resource is not mapped to a preamble for a valid PRACH timing, or if the associated PRACH preamble is not transmitted as described in Clause 7.5 or Clause 11.1, then the UE will not transmit the PUSCH during the PUSCH timing. If the PRACH preamble is not mapped to a valid PUSCH timing, then the UE may transmit the PRACH preamble during a valid PRACH timing.

[0351] The mapping between one or more PRACH preambles and PUSCH timings associated with DMRS resources is configured according to PUSCH.

[0352] The UE determines the time and frequency resources for the PUSCH timing in the valid UL BWP from the msgA-PUSCH-Config used for the valid UL BWP. If the valid UL BWP is not the initial UL BWP and no msgA-PUSCH-Config is provided for the valid UL BWP, then the UE uses the msgA-PUSCH-Config provided for the initial UL BWP.

[0353] The UE determines the first interlacing or first RB for the first PUSCH timing in the valid UL BWP from either interlaceIndexFirstPO-MsgA-PUSCH or frequencyStartMsgA-PUSCH, which provides an offset from the first RB of the valid UL BWP based on the number of RBs in the valid UL BWP. The PUSCH timing comprises the number of interlacings or RBs provided by nrofInterlacesPerMsgA-PO or nrofPRBs-perMsgA-PO, respectively. Consecutive PUSCH timings in the frequency domain of the UL BWP are separated by several RBs provided by guardBandMsgA-PUSCH. The number N of PUSCH timings in the frequency domain of the UL BWP... f Provided by nrofMsgA-PO-FDM.

[0354] For operations with shared spectrum channel access, if the PUSCH timing is provided by the higher-layer parameters frequencyStartMsgA-PUSCH and nrofPRBs-perMsgA-PO, then the UE expects the PUSCH timing to be limited to the same set of RBs as the corresponding PRACH transmission.

[0355] For operations with shared spectrum channel access, if the PUSCH timing is provided by the higher-layer parameters interlaceIndexFirstPO-MsgA-PUSCH and nrofInterlacesPerMsgA-PO, then the set of RBs used for the PUSCH timing in the valid ULBWP is the same set of RBs as the corresponding PRACH transmission. The UE assumes that the RB set is defined when the UE is not provided with intraCellGuardBandsPerSCS for the UL carrier, as described in Clause 7 of [6, TS38.214].

[0356] If the UE does not have a dedicated RRC configuration, or has an initial UL BWP as a valid UL BWP, or is not provided with startSymbolAndLengthMsgA-PO, then msgA-PUSCH-timeDomainAllocation provides the SLIV and the PUSCH mapping type for PUSCH transmission by indicating the following:

[0357] - First from PUSCH-TimeDomainResourceAllocationList

[0358] One of the maxNrofUL-Allocations values, provided it is provided in PUSCH-ConfigCommon.

[0359] PUSCH-TimeDomainResourceAllocationList

[0360] - From one of the entries in Table 6.1.2.1.1-2 or Table 6.1.2.1.1-3 of [6, TS 38.214], provided that PUSCH-TimeDomainResourceAllocationList is not provided in PUSCH-ConfigCommon.

[0361] Otherwise, the UE is provided with SLIV via startSymbolAndLengthMsgA-PO and with PUSCH mapping type via mappingTypeMsgA-PUSCH for PUSCH transmission.

[0362] To map one or more preambles of a PRACH slot to a PUSCH timing associated with a DMRS resource, the UE determines a first slot for a first PUSCH timing in a valid UL BWP from msgA-PUSCH-TimeDomainOffset, which provides an offset relative to the start of the PUSCH slot containing the start of each PRACH slot, in terms of the number of slots in the valid UL BWP. The UE does not anticipate PRACH preamble transmission and PUSCH transmission with msgA in a PRACH slot or PUSCH slot, or overlapping msgA PUSCH timings for MsgA PUSCH configuration. The UE anticipates that the first PUSCH timing in each slot has the same SLIV [6, TS 38.214] for PUSCH transmission provided by startSymbolAndLengthMsgA-PO or msgA-PUSCH-timeDomainAllocation.

[0363] Each consecutive PUSCH opportunity within a time slot is separated by guardPeriodMsgA-PUSCH symbols and has the same duration. The number N of time-domain PUSCH opportunities in each time slot is... t The number N of consecutive time slots containing PUSCH timings, provided by nrofMsgA-PO-perSlot. s Provided by nrofSlotsMsgA-PUSCH.

[0364] The msgA-DMRS-Config provides the UE with the DMRS configuration for PUSCH transmission during effective UL BWP PUSCH timing.

[0365] The msgA-MCS provides the UE with data information for PUSCH transmission during PUSCH timing via the msgA-MCS.

[0366] For PUSCH transmissions with frequency hopping in a time slot, when indicated by msgA-intraSlotFrequencyHopping for a valid UL BWP, msgA-HoppingBits are used instead of N as described in Table 8.3-1 of Clause 8.3. UL,hopThe frequency offset for the second hop is determined [6, TS 38.214]. If guardPeriodMsgA-PUSCH is provided, the first symbol of the second hop is separated from the end of the last symbol of the first hop by the guardPeriodMsgA-PUSCH symbols; otherwise, there is no time separation in the PUSCH transmission before and after the frequency hopping. If useInterlacePUCCH-PUSCH is provided for the UE in BWP-UplinkCommon, the UE will transmit the PUSCH without frequency hopping. The PUSCH transmission uses the same spatial filter as the associated PRACH transmission.

[0367] The UE determines whether to apply transform pre-decoding for PUSCH transmission, as described in [6, TS 38.214].

[0368] The timing of PUSCH transmissions is limited by frequency and time resources and is associated with DMRS resources. DMRS resources are provided by msgA-DMRS-Config.

[0369] For each consecutive number of N valid PRACH opportunities from a PRACH slot 前导码 Preamble Index

[0370] - First, the ascending order of the preamble index within a single PRACH timeframe.

[0371] - Second, in ascending order of the frequency resource index used for frequency multiplexing PRACH timing.

[0372] - Third, map the time resource indexes for time multiplexing PRACH opportunities within PRACH slots to valid PUSCH opportunities and associated DMRS resources in ascending order.

[0373] - First, the frequency resource index f used for frequency multiplexing PUSCH timing. id Increasing order

[0374] - Second, in ascending order of the DMRS resource index within the PUSCH timeframe, where the DMRS resource index is DMRS id The first is determined by ascending order of the DMRS port index, and the second by ascending order of the DMRS sequence index [4, TS 38.211].

[0375] - Third, the time resource index t used for time-multiplexed PUSCH timing within the PUSCH slot. id Increasing order

[0376] - Fourth, for use with N sThe ascending order of the indexes of each PUSCH slot

[0377] Where N 前导码 =ceil(T 前导码 / T PUSCH ), T 前导码 It is the total number of valid PRACH opportunities per associated mode cycle multiplied by the number of preambles per valid PRACH opportunity provided by rach-ConfigCommonTwoStepRA, and T PUSCH It is the total number of valid PUSCH moments configured per PUSCH per association mode cycle multiplied by the number of DMRS resource indexes per valid PUSCH moment provided by msgA-DMRS-Config.

[0378] The PUSCH timing is valid if it does not overlap in time and frequency with any valid PRACH timing associated with a Type 1 or Type 2 random access procedure. Additionally, it is valid for unpaired spectrum and for SS / PBCH blocks with an index provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon.

[0379] - If the UE is not provided with tdd-UL-DL-ConfigurationCommon, then the PUSCH timing is valid, provided that the PUSCH timing is as described above.

[0380] - In the PUSCH time slot, it does not precede the SS / PBCH block, and

[0381] - At least N after the last SS / PBCH block symbol gap It begins with a symbol, where N gap Provided in Table 8.1-2, and if channelAccessMode=semistatic is provided, then it does not overlap with the set of consecutive symbols preceding the start of the next channel occupancy time in which the UE does not transmit [15, TS 37.213].

[0382] - If the UE is provided with tdd-UL-DL-ConfigurationCommon, then the PUSCH timing is valid, provided that the PUSCH timing is as described above.

[0383] -Inside the UL symbol, or

[0384] - In the PUSCH time slot, it does not precede the SS / PBCH block, and

[0385] - At least N after the last downlink symbol gapThe symbols and at least N after the last SS / PBCH block symbol gap It begins with a symbol, where N gap Provided in Table 8.1-2, and if channelAccessMode=semistatic is provided, then it does not overlap with the set of consecutive symbols preceding the start of the next channel occupancy time in which the UE does not transmit [15,TS37.213].

[0386] 8.2 Random Access Response - Type 1 Random Access Procedure

[0387] In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI during a window controlled by the higher layer [11, TS 38.321]. The window begins at the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH as defined in Clause 10.1 for the Type 1-PDCCHCSS set, i.e., at least one symbol after the last symbol of the PRACH timing corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS as defined in Clause 10.1 for the Type 1-PDCCHCSS set. The length of the window in multiple slots is provided by ra-ResponseWindow based on the SCS for the Type 1-PDCCHCSS set.

[0388] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI, and the LSB of the SFN field in the DCI format 1_0 (if included and applicable) is the same as the corresponding LSB of the SFN in the PRACH transmitted by the UE, and the UE receives a transport block in the corresponding PDSCH within the window, then the UE passes the transport block to the higher layer. The higher layer parses the transport block for the random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layer identifies the RAPID in the RAR message of the transport block, the higher layer indicates uplink permission for the physical layer. This is called random access response (RAR) UL permission in the physical layer.

[0389] If the UE does not detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, and the LSB of the SFN field in DCI format 1_0 (if included and applicable) is not the same as the corresponding LSB of the SFN in which the UE transmits PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the higher layer does not identify the RAPID associated with the PRACH transmission from the UE, then the higher layer may instruct the physical layer to transmit the PRACH. If requested by the higher layer, then the UE expects to transmit the PRACH no later than N symbols after the last symbol of the window or the last symbol of the received PDSCH. T,1 +0.75 milliseconds to transmit PRACH, where N T,1 This refers to the duration of N1 symbols corresponding to the PDSCH processing time for UE processing capability 1. It is assumed that μ corresponds to the minimum SCS configuration in the SCS configuration for carrying DCI format 1_0 PDCCH, the corresponding PDSCH when configuring additional PDSCH DM-RS, and the corresponding PRACH. For μ = 0, the UE assumes N... 1,0 =14[6,TS 38.214]. For PRACH transmission using 1.25kHz or 5kHz SCS, the UE assumes that the SCS configuration μ=0 to determine N1.

[0390] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI, and the LSB of the SFN field in the DCI format 1_0 (if included and applicable) is the same as the corresponding LSB of the SFN in which the UE transmits PRACH, and the UE receives a transport block in the corresponding PDSCH, then as described in [6, TS 38.214], the UE may assume the same DM-RS antenna port quasi-co-addressable nature for the SS / PBCH block or CSI-RS resource associated with the PRACH, as described in Clause 8.1, regardless of whether the UE is provided with a TCI-State of CORESET in which the UE receives a PDCCH with DCI format 1_0.

[0391] If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a non-contention-based random access procedure in SpCell [11, TS 38.321], the UE may assume that the PDCCH contains DCI format 1_0 and that the PDCCH command has the same DM-RS antenna port quasi-co-address characteristics. If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a non-contention-based random access procedure in a secondary cell, the UE may assume that the DM-RS antenna port quasi-co-address characteristics of the CORESET associated with the Type 1-PDCCHCSS set used for receiving the PDCCH contain DCI format 1_0.

[0392] RAR UL grants permission to schedule transmissions from the UE's PUSCH. Table 8.2-1 shows the contents of RAR UL grants that begin with the MSB and end with the LSB.

[0393] If the value of the frequency hopping flag is 0, then the UE transmits PUSCH without frequency hopping; otherwise, the UE transmits PUSCH with frequency hopping.

[0394] The UE determines the MCS for PUSCH transmission from the first sixteen indices of the applicable MCS index table for PUSCH as described in [6, TS 38.214].

[0395] TPC command value δ msg2,b,f,c The power used to set the PUSCH transmission is as described in Clause 7.1.1 and is explained according to Table 8.2-2.

[0396] The CSI request field is reserved.

[0397] The ChannelAccess-CPext field indicates the channel access type and CP extension for operations with shared spectrum channel access [15, TS 37.213], as defined in Table 7.3.1.1.1-4 or Table 7.3.1.1.1-4A of TS 38.212, provided that ChannelAccessMode-r16="semi-static" is provided as defined in Table 7.3.1.1.1-4 of TS 38.212.

[0398] Table 8.2-1: Size of the Granted Content Field in Random Access Response

[0399]

[0400] Table 8.2-2: TPC commands δ for PUSCH msg2,b,f,c

[0401] TPC command Value (in dB) 0 -6 1 -4 2 -2 3 0 4 2 5 4 6 6 7 8

[0402] Unless the UE is configured with an SCS, the UE receives subsequent PDSCHs using the same SCS as the PDSCH that provided the RAR message.

[0403] If the UE does not detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, and the LSB of the SFN field in DCI format 1_0 (if included and applicable) is not the same as the corresponding LSB of the SFN in which the UE transmits PRACH, or the UE does not correctly receive the corresponding transport block within the window, then the UE procedure is as described in [11, TS 38.321].

[0404] 8.2A Random Access Response - Type 2 Random Access Procedure

[0405] In response to the transmission of both PRACH and PUSCH, or in response to the transmission of only PRACH when the PRACH preamble is mapped to a valid PUSCH timing, the UE attempts to detect DCI format 1_0 [11, TS 38.321] with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by a higher layer. The window begins at the first symbol of the earliest CORESET, and the UE is configured to receive the PDCCH for the Type 1-PDCCH CSS set as defined in Clause 10.1, i.e., at least one symbol after the last symbol of the PUSCH timing corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type 1-PDCCH CSS set. The length of the window in multiple slots is provided by msgB-ResponseWindow based on the SCS for the Type 1-PDCCH CSS set.

[0406] In response to a PRACH transmission, if the PRACH preamble is not mapped to a valid PUSCH timing, the UE attempts to detect DCI format 1_0 [11, TS38.321] with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by a higher layer. The window begins at the first symbol of the earliest CORESET, and the UE is configured to receive the PDCCH for the Type 1-PDCCH CSS set as defined in Clause 10.1, i.e., at least one symbol after the last symbol of the PRACH timing corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type 1-PDCCH CSS set. The length of the window in multiple slots is provided by msgB-ResponseWindow based on the SCS for the Type 1-PDCCH CSS set.

[0407] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI, and the LSB (if applicable) of the SFN field in the DCI format 1_0 is the same as the corresponding LSB of the SFN in the PRACH transmitted by the UE, and the UE receives a transport block in the corresponding PDSCH within the window, then the UE passes the transport block to the higher layer. The higher layer indicates to the physical layer...

[0408] - Uplink permission is granted, provided that the RAR message is used for fallbackRAR and identifies the random access preamble identity (RAPID) associated with the PRACH transmission, and the UE procedure continues as described in clauses 8.2, 8.3, and 8.4 when the UE detects RAR UL permission, or

[0409] - Transmission of PUCCH with HARQ-ACK information having an ACK value, provided that the RAR message is for successRAR, where

[0410] - The PUCCH resource used for PUCCH transmission is derived from the 4-digit PUCCH resource indicator field in the successRAR file of the PUCCH resource set provided by pucch-ResourceCommon.

[0411] - The time slot used for PUCCH transmission is indicated by a 3-bit HARQ feedback timing indicator field in successRAR, which has a value k from {1,2,3,4,5,6,7,8} and references a duration T. 时隙 The timing for PUCCH transmission is determined as n+k+Δ, where n is the PDSCH reception time slot, and Δ is the PUSCH transmission constraint specified in Table 6.1.2.1.1-5 of [6, TS 38.214].

[0412] - The UE does not expect the first symbol transmitted by PUCCH to be less than N after the last symbol received by PDSCH. T,1 +0.5 milliseconds, where N T,1 This is the PDSCH processing time [6, TS 38.214] used for UE processing capability 1.

[0413] - For operations with shared spectrum channel access, the channel access type and CP extension [15, TS 37.213] used for PUCCH transmission are indicated by the ChannelAccess-CPext field in successRAR, as defined in Table 7.3.1.1.1-4 of TS 38.212, or Table 7.3.1.1.1-4A of TS 38.212, provided that ChannelAccessMode-r16="semi-static" is provided.

[0414] - The PUCCH transmission has the same spatial domain transmission filter as the last PUSCH transmission and is within the same effective ULBWP.

[0415] If the UE detects a DCI format 1_0 with a CRC scrambled by C-RNTI and a corresponding transport block in the PDSCH within the window, then the UE transmits a PUCCH [11, TS38.321] with HARQ-ACK information that has an ACK value if the UE correctly detects the transport block or a NACK value if the UE incorrectly detects the transport block and the time alignment timer is running.

[0416] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI and receives a transport block within a window in the corresponding PDSCH, then as described in [6, TS 38.214], the UE may assume the same DM-RS antenna port quasi-co-addressable nature for the SS / PBCH blocks associated with the PRACH, as described in Clause 8.1, regardless of whether the UE is provided with a CORESET TCI-State in a PDCCH with DCI format 1_0.

[0417] The UE does not expect to be instructed to transmit a PUCCH with HARQ-ACK information before the time when the UE applies the TA command provided by the transport block. If the UE does not detect a DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI within the window, and the LSB of the SFN field in the DCI format 1_0 (if applicable) is not the same as the corresponding LSB of the SFN in which the UE transmits the PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the higher layer does not identify the RAPID associated with the PRACH transmission from the UE, then the higher layer may instruct the physical layer to transmit only the PRACH according to a Type 1 random access procedure or to transmit both the PRACH and PUSCH according to a Type 2 random access procedure [11, TS 38.321]. If requested by the higher layer, the UE expects to transmit no later than N symbols after the last symbol of the window or the last symbol of the PDSCH reception. T,1 +0.75 milliseconds to transmit PRACH, where N T,1 This corresponds to the duration of N1 symbols used for PDSCH processing time in UE processing capability 1 when additional PDSCH DM-RS is configured. For μ = 0, the UE assumes N... 1,0 =14[6,TS 38.214].

[0418] Unless the UE is configured with an SCS, the UE receives subsequent PDSCHs using the same SCS as the PDSCH that provided the RAR message.

[0419] If the UE does not detect DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects 1_0 with a CRC scrambled by the corresponding MsgB-RNTI within the window, and the LSB of the SFN field in DCI format 1_0 (if applicable) is not the same as the corresponding LSB of the SFN in which the UE transmits PRACH, or the UE does not correctly receive the corresponding transport block within the window, then the UE procedure is as described in [11, TS 38.321].

[0420] 8.3 PUSCH scheduled by RAR UL

[0421] As described in Clause 12 and [4, TS 38.211], the UL BWP in the role of PUSCH transmission authorized by RAR UL is indicated by a higher layer.

[0422] If useInterlacePUCCH-PUSCH is not provided by BWP-UplinkCommon and BWP-UplinkDedicated, in order to determine the frequency domain resource allocation for PUSCH transmission within the UL BWP in operation.

[0423] - If the active UL BWP and the initial UL BWP have the same SCS and the same CP length, and the active UL BWP contains all the RBs of the initial UL BWP, or the active UL BWP is the initial UL BWP, then use the initial UL BWP.

[0424] Otherwise, the RB numbering starts from the first RB in the active UL BWP and the maximum number of RBs used for frequency domain resource allocation is equal to the number of RBs in the initial UL BWP.

[0425] Frequency domain resource allocation is based on uplink resource allocation type 1 [6, TS 38.214]. For The initial UL BWP size for each RB is determined by the UE processing the frequency domain resource allocation field as follows.

[0426] -if Or for operations with shared spectrum channel access, if

[0427] - Truncate the frequency domain resource assignment field to its The least significant bit and the frequency resource assignment field in DCI format 0_0 as described in [5, TS 38.212] are interpreted as truncated frequency resource assignment fields.

[0428] -otherwise

[0429] -insert The most significant bit, or for operations with shared spectrum channel access, insert The most significant bit, of which N is in the frequency domain resource assignment field. UL,hop The value after the bit is set to '0', where if the frequency hopping flag is set to '0', then N UL,hop =0, and if the frequency hopping flag is set to '1', then N UL,hop The frequency resource assignment field, provided in Table 8.3-1 and interpreted as an extended frequency resource assignment field in DCI format 0_0 as described in [5, TS 38.212], is used for interpretation.

[0430] - Termination Condition

[0431] If useInterlacePUCCH-PUSCH is provided by BWP-UplinkCommon or BWP-UplinkDedicated, then frequency domain resource allocation is performed via uplink resource allocation type 2 [6, TS 38.214]. The UE processes the frequency domain resource assignment field as follows:

[0432] - Truncate the frequency domain resource assignment field to X = 6 LSBs when μ = 0, or to X = 5 LSBs when μ = 1.

[0433] - For interleaved allocation of PUSCH transmissions, the X MSB of the frequency domain resource allocation field in DCI format 0_0 [6, TS 38.214] is interpreted as X MSB of the truncated frequency domain resource allocation field in the UL BWP.

[0434] - For the allocation of the RB set for PUSCH transmission, the RB set of the active UL BWP is the RB set of the PRACH transmission associated with the RAR UL grant. The UE assumes that the RB set is defined when the UE is not provided with intraCellGuardBandsUL-List [6, TS 38.214].

[0435] The UE determines whether to apply transform pre-decoding, as described in [6,TS 38.214].

[0436] For PUSCH transmissions with frequency hopping scheduled by RAR UL or for Msg3 PUSCH retransmissions, the frequency offset [6, TS 38.214] for the second hop is given in Table 8.3-1.

[0437] Table 8.3-1: Frequency offset of the second hop for PUSCH transmissions with frequency hopping scheduled by RAR UL or Msg3 PUSCH retransmissions

[0438]

[0439] The subcarrierSpacing provided by BWP-UplinkCommon enables SCS UEs to transmit PRACH and PUSCH on the same uplink carrier in the same serving cell for PUSCH transmission.

[0440] The UE transmits transport blocks using redundancy version number 0 in the PUSCH scrambled by the RAR UL-approved scheduler in the corresponding RAR message. If a TC-RNTI is provided by a higher layer, the scrambling initialization for the RAR UL-approved PUSCH in Section 8.2 is via TC-RNTI. Otherwise, the scrambling initialization for the RAR UL-approved PUSCH in Section 8.2 is via C-RNTI. The Msg3 PUSCH retransmission of the transport block (if present) is scheduled by DCI format 0_0, which has a CRC scrambled by the TC-RNTI provided in the corresponding RAR message [11, TS 38.321]. The UE always transmits the RAR UL-approved PUSCH without duplication.

[0441] Referring to the time slot for PUSCH transmission authorized by RAR UL, if the UE receives a PDSCH with a RAR message that ends in time slot n for the corresponding PRACH transmission from the UE, then the UE transmits the PUSCH in time slot n+k2+Δ, where k2 and Δ are provided in [6, TS 38.214].

[0442] The UE may assume that the minimum time between the last symbol received by the PDSCH delivering the RAR message with RAR UL permission and the first symbol transmitted by the corresponding PUSCH scheduled by RAR UL permission is equal to N. T,1 +N T,2 +0.5 milliseconds, where N T,1 This corresponds to the duration of N1 symbols of PDSCH processing time used for UE processing capability 1 when additional PDSCH DM-RS is configured, where N... T,2 This corresponds to the duration of N2 symbols for the PUSCH preparation time used for UE processing capability 1 [6, TS 38.214], and to determine the minimum time, the UE assumes that N1 and N2 correspond to the smaller of the SCS configurations used for PDSCH and PUSCH. For μ = 0, the UE assumes N... 1,0 =14[6,TS 38.214].

[0443] 8.4 PDSCH with UE contention resolution identity

[0444] In response to a PUSCH transmission scheduled by RAR UL when the UE is not provided with a C-RNTI, the UE attempts to detect a DCI format 1_0 [11, TS38.321] with a CRC scrambled by the corresponding TC-RNTI of the PDSCH that is scheduled to include the UE contention-resolving identity. In response to a PDSCH reception with the UE contention-resolving identity, the UE transmits HARQ-ACK information in the PUCCH. The PUCCH transmission is within the same UL BWP as the PUSCH transmission. The minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission with HARQ-ACK information is equal to N. T,1 +0.5 milliseconds. N T,1 This corresponds to the duration of N1 symbols used for PDSCH processing time in UE processing capability 1 when additional PDSCH DM-RS is configured. For μ = 0, the UE assumes N... 1,0 =14[6,TS38.214].

[0445] When a PUSCH transmission scheduled by RAR UL, as described in [11,TS 38.321], or a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI provided in the corresponding RAR message [11,TS 38.321], is detected, as described in [6,TS 38.214], the UE may assume that the PDCCH carrying the DCI format has the same DM-RS antenna port quasi-co-addressable nature for the SS / PBCH block used by the UE for PRACH association, as described in Clause 8.1, regardless of whether the UE is provided with a CORESET TCI-State for a PDCCH with the DCI format.

[0446] **********************************End of quotation*********************************

[0447] **********************************Start of quotation*********************************

[0448] 7.3.1.1 DCI Format for PUSCH Scheduling

[0449] 7.3.1.1.1 Format 0_0

[0450] DCI format 0_0 is used to schedule PUSCH within a cell.

[0451] The following information is transmitted via DCI format 0_0, where the CRC is scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI:

[0452] …

[0453] - If ChannelAccessMode-r16="semi-static" is provided for operation in a cell with shared spectrum channel access, then the ChannelAccess-CPext-2 bit is used, indicating a combination of channel access type and CP extension as defined in Table 7.3.1.1.1-4 or Table 7.3.1.1.1.4A; otherwise, the bit is 0.

[0454] The following information is transmitted via DCI format 0_0 scrambled by TC-RNTI:

[0455] …

[0456] - If ChannelAccessMode-r16="semi-static" is provided for operation in a cell with shared spectrum channel access, then the ChannelAccess-CPext-2 bit is used, indicating a combination of channel access type and CP extension as defined in Table 7.3.1.1.1-4 or Table 7.3.1.1.1.4A; otherwise, the bit is 0.

[0457] Table 7.3.1.1.1-4: Channel Access Types and CP Extensions for DCI Format 0_0 and DCI Format 1_0

[0458]

[0459] Table 7.3.1.1.1-4A: Channel Access Types and CP Extensions when ChannelAccessMode-r16 = "Semi-static" is provided

[0460]

[0461] When operating in unlicensed / shared spectrum, channel access procedures, such as LBT, will be performed as mentioned above. However, there may be some special cases where channel access procedures may be skipped in unlicensed / shared spectrum. For example, the UE may be instructed to use a no-LBT mode, so that the UE does not need to perform LBT or skips LBT before transmission. In another instance, for some channels / signals, transmission can be performed directly without channel access procedures, for example, without listening / detecting whether the channel is busy / occupied. More details about special channels / signals can be found in the following quote from [5] 3GPP TS 38.212 V16.6.0:

[0462] **********************************Start of quotation*********************************

[0463] protocol:

[0464] For areas where LBT is not mandatory, the gNB should indicate to the UE whether this gNB-UE connection is operating in LBT mode or without LBT mode.

[0465] ●Supports cell-specific (as part of system information, dedicated RRC signaling, or both, common to all UEs in the cell) and UE-specific (as part of UE-specific RRC configuration, which may differ for different UEs in the cell) gNB indications.

[0466] protocol:

[0467] ●The contention exemption short control signaling rule applies to all supported SCSs for the transmission of msg1 for 4-step RACH and MsgA for 2-step RACH.

[0468] ○ Annotations for short control signaling transmissions are limited to 10% of any 100ms interval.

[0469] Alternative Option 1: The 10% limit on any 100ms interval applies to all available msg1 / msgA resources configured in the cell (not limited to resources actually used).

[0470] Alternative Option 2: A 10% limit on any 100ms interval applies from a UE's perspective to msg1 / msgA transmission.

[0471] ● Further research is needed: It could be possible to competitively exempt short control signaling rules from transmitting other UL signals / channels, such as msg3, SRS, PUCCH, PUSCH, etc., which are purely for user data.

[0472] **********************************End of quotation*********************************

[0473] Problems and Solutions

[0474] As detailed above, the Random Access Response (RAR) grant in unlicensed spectrum (e.g., shared spectrum) will contain indications of the channel access type and cyclic prefix (CP) extension. The User Equipment (UE) will apply the indicated channel access type and CP extension for its Msg3 Physical Uplink Shared Channel (PUSCH) transmission. This field will not exist for licensed spectrum. However, to maintain a constant bit width / size for the RAR grant, two bits are borrowed from the resource allocation (e.g., frequency domain) field. In other words, the interpretation of the RAR grant will differ depending on whether the channel access type and CP extension indication is present or not. The interpretation of the resource allocation for Msg3 will also differ depending on whether the channel access type and CP extension indication is present or not, due to the two-bit difference in the resource allocation field.

[0475] Different mechanisms / strategies exist for determining whether a channel access scheme, such as Listen-Before-Speak (LBT), is required for transmission. The first factor is the device's LBT mode. For example, if the device is in LBT-free mode, it can perform transmission without LBT. On the other hand, if the device is in LBT mode, it may need to perform transmission with LBT for most cases. Furthermore, even if the device is in LBT mode, some signals / channels / messages, such as preambles, may be exempt from LBT. In other words, for some channels / signals / messages, LBT is not required for all devices in unlicensed / shared spectrum, regardless of the device's LBT mode. For other channels / signals / messages, LBT may or may not be performed, for example, subject to the device's LBT mode. With the introduction of LBT mode, Msg3 PUSCH may or may not require LBT. The question of whether and / or how to handle indications of channel access type and CP extension arises.

[0476] The first concept of this invention is to interpret the RAR at least based on the UE's LBT mode. The UE determines, at least based on its LBT mode, whether an indication of channel access type and / or CP extension exists in the RAR. If the UE's LBT mode is "LBT mode," for example, a mode where the UE performs LBT under normal circumstances, then the UE determines that an indication of channel access type and / or CP extension exists in the RAR. If the UE's LBT mode is "no LBT mode," for example, a mode where the UE does not perform LBT under normal circumstances, then the UE determines that an indication of channel access type and / or CP extension does not exist in the RAR. The UE will determine, at least based on its LBT mode, the bit width / size of the resource allocation field in the RAR. If the UE's LBT mode is "LBT mode," then the UE will determine the first bit width / size of the resource allocation field in the RAR. If the UE's LBT mode is "no LBT mode," then the UE will determine the second bit width / size of the resource allocation field in the RAR. The second bit width / size is greater than the first bit width / size. The second bit width / size has two more bits than the first bit width / size. The UE operates in unlicensed / shared spectrum.

[0477] The second concept of this invention is to determine the channel access type and / or CP extension for Msg3 based on the UE's LBT mode. The channel access type and / or CP extension may differ from the access type and / or CP extension indicated by the RAR approval. The UE uses a first channel access type and / or a first CP extension for Msg3. The RAR approval indicates a second channel access type and / or a second CP extension. The RAR approval contains an indication of the channel access type and / or CP extension.

[0478] The third concept of this invention is to determine the channel access type and / or CP extension for Msg3 based on the indication in the RAR approval, regardless of the UE's LBT mode. The UE applies the first channel access type and / or the first CP extension for Msg3. The UE is in "no LBT mode". The UE performs LBT for the Msg3 PUSCH. The UE does not perform LBT for other PUSCHes. The RAR approval contains an indication of the channel access type and / or CP extension.

[0479] The fourth concept of this invention is to combine the second and third concepts to determine the channel access type and / or CP extension for Msg3, partly based on the UE's LBT mode and partly based on the indication in the RAR approval. For example, the channel access type is determined based on the UE's LBT mode, and the CP extension is determined based on the indication in the RAR approval. The UE is in a no-LBT mode. The UE does not perform LBT for Msg3, but applies the CP extension for Msg3. The RAR approval contains indications for the channel access type and / or CP extension.

[0480] In one embodiment, the UE determines, at least based on its LBT mode, whether an indication of channel access type and / or CP extension exists in the RAR. A random access procedure is triggered. If the UE's LBT mode is a first LBT mode, the UE determines that the indication of channel access type and / or CP extension does not exist. If the UE's LBT mode is a second LBT mode, the UE determines that the indication of channel access type and / or CP extension exists. If the channel access type indication does not exist, the UE does not perform LBT for Msg3. If the CP extension indication does not exist, the UE does not extend CP for Msg3. If the channel access type indication exists, the UE performs LBT for Msg3. If the CP extension indication exists, the UE extends CP for Msg3. The UE determines, at least based on its LBT mode, the bit width / size of the resource allocation field in the RAR. If the UE's LBT mode is a first LBT mode, the UE determines the first bit width / size of the resource allocation field in the RAR. If the UE's LBT mode is a second LBT mode, the UE determines the second bit width / size of the resource allocation field in the RAR. The UE operates in shared / unlicensed spectrum.

[0481] If the UE's LBT mode is the first LBT mode, then the UE selects the first preamble. If the UE's LBT mode is the second LBT mode, then the UE selects the second preamble. If the UE's LBT mode is the first LBT mode, then the UE transmits the first preamble. If the UE's LBT mode is the second LBT mode, then the UE transmits the second preamble. The first preamble set is associated with the first LBT mode. The second preamble set is associated with the second LBT mode. The UE selects the preamble within the preamble set associated with its LBT mode. If the UE's LBT mode is the first LBT mode, then the UE selects the preamble within the first preamble set. If the UE's LBT mode is the second LBT mode, then the UE selects the preamble within the second preamble set. If the UE's LBT mode is the first LBT mode, then the UE transmits the preamble within the first preamble set. If the UE's LBT mode is the second LBT mode, then the UE transmits the preamble within the second preamble set.

[0482] The first Physical Random Access Channel (PRACH) resource is associated with the first LBT mode. The second PRACH resource is associated with the second LBT mode. The UE selects the PRACH resource associated with its LBT mode. If the UE's LBT mode is the first LBT mode, then the UE selects the first PRACH resource. If the UE's LBT mode is the second LBT mode, then the UE selects the second PRACH resource. If the UE's LBT mode is the first LBT mode, then the UE transmits the preamble within the first PRACH resource. If the UE's LBT mode is the second LBT mode, then the UE transmits the preamble within the second PRACH resource. The LBT mode can be either a "no LBT mode" or an "LBT mode" (e.g., the mode in which the UE performs LBT under normal circumstances).

[0483] The first LBT mode can be "no LBT mode". The second LBT mode can be "LBT mode" (e.g., the mode in which the UE performs LBT under normal circumstances). The first LBT mode can be an LBT mode associated with a first (set) of LBT-related parameters. The second LBT mode can be an LBT mode associated with a second (set) of LBT-related parameters. The UE's LBT mode can be indicated by another device. The UE's LBT mode can be indicated by the base station. The UE's LBT mode can be indicated by another UE. The UE's LBT mode can be determined by the UE itself. The UE's LBT mode can be determined by rules. The association between the preamble and the LBT mode can be indicated by the base station. The association between the preamble and the LBT mode can be indicated by RRC configuration. Therefore, the base station can identify the LBT mode of the UE transmitting the preamble. The base station can recognize whether LBT is required for Msg3. The base station can allocate resources for Msg3 accordingly, for example, allocating resources for Msg3 based on whether LBT is required for Msg3. The base station can transmit the RAR accordingly, for example, based on whether LBT is required for Msg3 (e.g., RAR grant).

[0484] In another embodiment, the base station determines, at least based on the UE's LBT mode, whether an indication of channel access type and / or CP extension exists in the RAR. A random access procedure is triggered. If the UE's LBT mode is a first LBT mode, the base station determines that the indication of channel access type and / or CP extension does not exist. If the UE's LBT mode is a second LBT mode, the base station determines that the indication of channel access type and / or CP extension exists. If the channel access type indication does not exist, the UE does not perform LBT for Msg3. If the CP extension indication does not exist, the UE does not extend CP for Msg3. If the channel access type indication exists, the UE performs LBT for Msg3. If the CP extension indication exists, the UE extends CP for Msg3. The base station determines, at least based on the UE's LBT mode, the bit width / size of the resource allocation field in the RAR. If the UE's LBT mode is a first LBT mode, the base station determines the first bit width / size of the resource allocation field in the RAR. If the UE's LBT mode is a second LBT mode, the base station determines the second bit width / size of the resource allocation field in the RAR. The UE operates in shared / unlicensed spectrum.

[0485] The base station determines the UE's LBT mode based at least on the detected preamble and / or PRACH resources. The preamble is transmitted by the UE. The UE triggers a random access procedure. The base station determines the UE's LBT mode based on the detected preamble. The base station determines the UE's LBT mode based on the PRACH resources containing the detected preamble. A first preamble is associated with a first LBT mode. A second preamble is associated with a second LBT mode. If the first preamble is detected, the base station determines the LBT mode is the first LBT mode. If the second preamble is detected, the base station determines the LBT mode is the second LBT mode. A first set of preambles is associated with the first LBT mode. A second set of preambles is associated with the second LBT mode. If a preamble within the first set of preambles is detected, the base station determines the LBT mode is the first LBT mode. If a preamble within the second set of preambles is detected, the base station determines the LBT mode is the second LBT mode.

[0486] The first PRACH resource is associated with the first LBT mode. The second PRACH resource is associated with the second LBT mode. If a preamble is detected in the first PRACH resource, the base station determines that the LBT mode is the first LBT mode. If a preamble is detected in the second PRACH resource, the base station determines that the LBT mode is the second LBT mode. The LBT mode can be either a "no LBT mode" or an "LBT mode" (e.g., the mode in which the UE performs LBT under normal circumstances).

[0487] The first LBT mode can be "no LBT mode". The second LBT mode can be "LBT mode" (e.g., the mode in which the UE performs LBT under normal circumstances). The first LBT mode can be an LBT mode associated with a first (set) of LBT-related parameters. The second LBT mode can be an LBT mode associated with a second (set) of LBT-related parameters. The UE's LBT mode can be indicated by another device. The UE's LBT mode can be indicated by the base station. The UE's LBT mode can be indicated by another UE. The UE's LBT mode can be determined by the UE itself. The UE's LBT mode can be determined by rules. The association between the preamble and the LBT mode can be indicated by the base station. The association between the preamble and the LBT mode can be indicated by RRC configuration. Therefore, the base station can identify the LBT mode of the UE transmitting the preamble. The base station can recognize whether LBT is required for Msg3. The base station can allocate resources for Msg3 accordingly, for example, allocating resources for Msg3 based on whether LBT is required for Msg3. The base station can transmit the RAR accordingly, for example, based on whether LBT is required for Msg3 (e.g., RAR grant).

[0488] In another embodiment, the UE determines the channel access type for Msg3 based at least on the UE's LBT mode. The UE determines the channel access type for Msg3 based at least on the indication in the RAR grant. The UE does not determine the channel access type for Msg3 based on the UE's LBT mode. The UE does not determine the channel access type for Msg3 based on the indication in the RAR grant. The UE determines the CP extension for Msg3 based at least on the UE's LBT mode. The UE determines the CP extension for Msg3 based at least on the indication in the RAR grant. The UE does not determine the CP extension for Msg3 based on the UE's LBT mode. The UE does not determine the channel access type for Msg3 based on the indication in the RAR grant. Indications for channel access type and / or CP extension exist in the RAR grant. The UE operates in shared / unlicensed spectrum. ChannelAccessMode-r16="semi-static" is not provided for operation within the cell. The UE performs LBT for Msg3 according to the indication for the channel access type for Msg3, regardless of the UE's LBT mode. The UE performs LBT for Msg3 according to its LBT mode, regardless of the indication of the channel access type for Msg3. The UE performs CP extension for Msg3 according to the indication of CP extension for Msg3, regardless of its LBT mode. The UE performs CP extension for Msg3 according to its LBT mode, regardless of the indication of CP extension for Msg3. The UE is in "No LBT Mode". The UE is in "LBT Mode". RAR instructs the UE to perform LBT. RAR instructs the UE not to perform LBT. The UE performs CP extension in "LBT Mode". The UE does not perform CP extension in "No LBT Mode". RAR instructs the UE to perform CP extension. RAR instructs the UE not to perform CP extension.

[0489] Initiate a random access procedure. The random access procedure is a contention-based random access procedure. The UE is in LBT-free mode. The UE performs LBT for Msg 3 PUSCH. The UE does not perform LBT for PUSCH that is not Msg3 PUSCH. The UE determines whether to perform LBT for a transmission based on the transmission type. The UE determines whether to perform LBT for a transmission based on the PUSCH type. The UE performs LBT for Msg3 PUSCH. The UE does not perform LBT for PUSCH transmitted that is not Msg3 PUSCH. The UE skips LBT for PUSCH transmitted that is not Msg3 PUSCH. The UE should perform LBT for Msg3 PUSCH. The UE is allowed not to perform LBT for other PUSCH. The UE can skip LBT for other PUSCH. The LBT mode can be one of "LBT-free mode" or "LBT mode" (e.g., the mode in which the UE performs LBT under normal circumstances). The first LBT mode can be "LBT-free mode". The second LBT mode can be "LBT mode". (For example, the LBT mode performed by the UE under normal circumstances). The UE's LBT mode can be indicated by another device. The UE's LBT mode can be indicated by the base station. The UE's LBT mode can be indicated by another UE. The UE's LBT mode can be determined by the UE itself. The UE's LBT mode can be determined by rules.

[0490] The LBT mode can be determined (at least) based on an indication. The indication can be received on the beam. The indication can be received on / through a downlink (DL) beam associated with the beam (e.g., a Transport Configuration Indicator (TCI) state). The indication can be received on / through a beam (beam direction) different from the beam (beam direction) of the beam. The indication can be received on / through a (DL) beam associated with the beam (e.g., a TCI state). The indication indicates the LBT mode. The LBT mode can include a mode in which the base station performs LBT. The LBT mode can include a mode in which the base station does not perform LBT. In a first LBT mode, the base station does not perform LBT. In a second LBT mode, the base station performs LBT. The base station does not determine the LBT mode based on an indication received on the second beam. The second beam is different from the beam of the beam. The beam direction of the second beam is different from the beam direction of the beam of the beam. The second beam is not associated with the beam of the beam. The base station determines the LBT mode individually for each beam. The base station determines a first LBT mode for the first beam. The base station determines the second LBT mode for the second beam.

[0491] The LBT mode can be omnidirectional LBT. The LBT mode can be directional LBT. The LBT mode can be receiver-assisted LBT. Different values ​​for the LBT parameters can be associated with different LBT modes. The LBT parameter can be the LBT's (energy detection) threshold. The LBT parameter can be the LBT's (contention) window size. The device can be a base station. The device can be a UE. The transmission can be PUSCH transmission. The transmission can be Physical Uplink Control Channel (PUCCH) transmission. The transmission can be PRACH transmission. The transmission can be Sounding Reference Signal (SRS) transmission.

[0492] LBT can be associated with DL channel access procedures. LBT can be associated with Type 1 DL channel access procedures. LBT can be associated with Type 2 DL channel access procedures. LBT can be associated with Type 2A DL channel access procedures. LBT can be associated with Type 2B DL ​​channel access procedures. LBT can be associated with Type 2C DL channel access procedures. LBT can be associated with Type A multi-channel access procedures. LBT can be associated with Type A1 multi-channel access procedures. LBT can be associated with Type A2 multi-channel access procedures. LBT can be associated with Type B multi-channel access procedures. LBT can be associated with Type B1 multi-channel access procedures. LBT can be associated with Type B2 multi-channel access procedures. LBT can be associated with UL channel access procedures. LBT can be associated with Type 1 UL channel access procedures. LBT can be associated with Type 2 UL channel access procedures. LBT can be associated with Type 2A UL channel access procedures. LBT can be associated with Type 2B UL channel access procedures. LBT can be associated with Type 2C UL channel access procedures.

[0493] For any of the embodiments of the present invention, LBT can be replaced by a channel access scheme or a channel access mechanism.

[0494] For any of the embodiments of the present invention, the present invention describes the behavior or operation of a single serving cell, unless otherwise indicated.

[0495] For any of the embodiments of the present invention, the present invention describes the behavior or operation of a plurality of serving cells, unless otherwise indicated.

[0496] For any of the embodiments of the present invention, the present invention describes the behavior or operation of a single bandwidth portion, unless otherwise indicated.

[0497] In any of the embodiments of the present invention, the base station configures multiple bandwidth portions for the UE, unless otherwise indicated.

[0498] In any of the embodiments of the present invention, the base station configures a single bandwidth portion for the UE, unless otherwise indicated.

[0499] See Figure 7 Regarding such and other concepts, systems, and methods of the present invention, method 1000 for a UE in a wireless communication system includes triggering a Receiving Arrival (RAR) (step 1002) and determining, at least based on the UE's LBT mode, whether an indication of channel access type and / or CP extension exists in the RAR (step 1004). See also Figure 8 Regarding such and other concepts, systems and methods of the present invention, method 1010 for a base station in a wireless communication system includes determining, at least based on the LBT mode of the UE, whether an indication of channel access type and / or CP extension exists in the RAR (step 1012).

[0500] In various embodiments, the UE operates in a shared spectrum.

[0501] In various embodiments, if the UE's LBT mode is the first LBT mode, then the UE does not have an indication to determine the channel access type and / or CP extension.

[0502] In various embodiments, if the UE's LBT mode is the second LBT mode, then the UE determines that an indication of channel access type and / or CP extension exists.

[0503] In various embodiments, if the channel access type indication is not present, the UE does not perform LBT for Msg3.

[0504] In various embodiments, if the indication for CP extension is not present, then the UE does not extend the CP for Msg3.

[0505] In various embodiments, if an indication of the channel access type is present, then the UE performs LBT for Msg3.

[0506] In various embodiments, if an indication for CP extension is present, then the UE extends the CP for Msg3.

[0507] In various embodiments, the UE determines the bit width / size of the resource allocation field in the RAR based at least on the UE's LBT mode.

[0508] In various embodiments, if the UE's LBT mode is the first LBT mode, then the UE determines the first width / size of the resource allocation field in the RAR.

[0509] In various embodiments, if the UE's LBT mode is the second LBT mode, then the UE determines the second bit width / size of the resource allocation field in the RAR.

[0510] Return to reference Figure 3 and 4 In one or more embodiments from the UE's perspective, apparatus 300 includes program code 312 stored in the transmitter's memory 310. CPU 308 can execute program code 312 to: (i) trigger RAR, and (ii) determine, at least based on the UE's LBT mode, whether an indication of channel access type and / or CP extension exists in the RAR. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0511] Back to Figure 3 and 4 In one or more embodiments from the perspective of a base station, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) determine, at least based on the LBT mode of the UE, whether an indication of channel access type and / or CP extension exists in the RAR. Furthermore, CPU 308 may execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0512] See Figure 9 Regarding such and other concepts, systems and methods of the present invention, method 1020 for a UE in a wireless communication system includes: initiating a random access procedure (step 1022); receiving a RAR, wherein the RAR includes a channel access type indication (step 1024); and determining whether to perform LBT for Msg3 based on the channel access type indication in the RAR (step 1026).

[0513] In various embodiments, if / when the Channel Access Type Indicator in the RAR indicates that the UE should not perform LBT, the UE will not perform LBT for Msg3. If / when the Channel Access Type Indicator in the RAR indicates that the UE should perform LBT, the UE will perform LBT for Msg3.

[0514] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE determines whether to perform LBT for Msg3 based on the channel access type indication in the RAR.

[0515] In various embodiments, when the UE is in a no-LBT mode and / or when the UE is configured not to perform LBT, the UE determines whether to perform LBT for Msg3 based on the UE's LBT mode, regardless of the channel access type indication in the random access response.

[0516] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE does not perform LBT for Msg3.

[0517] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE ignores the channel access type indication in the RAR.

[0518] In various embodiments, the UE determines how to interpret the Channel Access Type Indication based on the UE's LBT mode.

[0519] In various embodiments, the UE operates in a shared spectrum.

[0520] In various embodiments, ChannelAccessMode-r16="semi-static" is not provided.

[0521] In various embodiments, LBT refers to the channel access scheme and / or sensing of the channel used to perform transmission.

[0522] Return to reference Figure 3 and 4 In one or more embodiments from the UE's perspective, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) initiate a random access procedure, (ii) receive a RAR, wherein the RAR includes a channel access type indication, and (iii) determine whether to perform LBT for Msg3 based on the channel access type indication in the RAR. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0523] See Figure 10 Regarding such and other concepts, systems, and methods of the present invention, method 1030 for a UE in a wireless communication system includes: receiving a RAR, wherein the RAR includes a channel access type indication (step 1032); receiving another RAR, wherein the RAR includes a channel access type indication (step 1034); and determining, based on the UE's LBT mode, whether to perform LBT for Msg3 regardless of the channel access type indication in the RAR (step 1036).

[0524] In various embodiments, when the UE is in a no-LBT mode and / or when the UE is configured not to perform LBT, the UE determines whether to perform LBT for Msg3 based on the UE's LBT mode, regardless of the channel access type indication in the RAR.

[0525] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE does not perform LBT for Msg3.

[0526] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE ignores the channel access type indication in the RAR.

[0527] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE does not ignore the channel access type indication in the RAR.

[0528] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE determines whether to perform LBT for Msg3 based on the channel access type indication in the RAR.

[0529] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE does not perform LBT for Msg3 if / when the channel access type indication in the RAR indicates that the UE does not perform LBT.

[0530] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE performs LBT for Msg3 if / when the Channel Access Type Indicator in the RAR instructs the UE to perform LBT.

[0531] In various embodiments, the UE operates in a shared spectrum.

[0532] In various embodiments, LBT refers to the channel access scheme and / or sensing of the channel used to perform transmission.

[0533] Return to reference Figure 3 and 4 In one or more embodiments from the UE's perspective, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a RAR, wherein the RAR includes a channel access type indication; (ii) receive another RAR, wherein the RAR includes a channel access type indication; and (iii) determine whether to perform LBT for Msg3 based on the UE's LBT mode, regardless of the channel access type indication in the RAR. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0534] See Figure 11Regarding such and other concepts, systems, and methods of the present invention, method 1040 for a base station in a wireless communication system includes: receiving or detecting a preamble (step 1042); transmitting a RAR, wherein the RAR includes a channel access type field regardless of whether LBT is performed (step 1044); and determining whether to perform LBT for Msg3 based on the LBT mode of the UE regardless of the channel access type indication in the RAR (step 1036).

[0535] In various embodiments, the Channel Access Type field indicates whether the UE performs LBT for Msg 3.

[0536] In various embodiments, the base station operates in the shared spectrum and / or does not provide ChannelAccessMode-r16="semi-static".

[0537] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a base station, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) receive or detect a preamble, (ii) transmit a RAR, wherein the RAR includes a channel access type field regardless of whether LBT is performed, and (iii) determine whether to perform LBT for Msg3 based on the UE's LBT mode regardless of the channel access type indication in the RAR. Furthermore, CPU 308 may execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0538] See Figure 12 Regarding such and other concepts, systems and methods of the present invention, method 1050 for a UE in a wireless communication system includes: initiating a random access procedure (step 1052); receiving a RAR, wherein the RAR includes a channel access type indication (step 1054); and determining whether to perform LBT for Msg3 based on the channel access type indication in the RAR (step 1056).

[0539] In various embodiments, if / when the Channel Access Type Indicator in the RAR indicates that the UE should not perform LBT, the UE will not perform LBT for Msg3. If / when the Channel Access Type Indicator in the RAR indicates that the UE should perform LBT, the UE will perform LBT for Msg3.

[0540] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE determines whether to perform LBT for Msg3 based on the channel access type indication in the RAR.

[0541] In various embodiments, when the UE is in a no-LBT mode and / or when the UE is configured not to perform LBT, the UE determines whether to perform LBT for Msg3 based on the UE's LBT mode, regardless of the channel access type indication in the RAR.

[0542] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE does not perform LBT for Msg3.

[0543] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE ignores the channel access type indication in the RAR.

[0544] In various embodiments, the UE determines how to interpret the Channel Access Type Indication based on the UE's LBT mode.

[0545] In various embodiments, the UE operates in a shared spectrum.

[0546] In various embodiments, ChannelAccessMode-r16="semi-static" is not provided.

[0547] In various embodiments, LBT refers to the channel access scheme and / or sensing of the channel used to perform transmission.

[0548] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a base station, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) initiate a random access procedure, (ii) receive a RAR, wherein the RAR includes a channel access type indication, and (iii) determine whether to perform LBT for Msg3 based on the channel access type indication in the RAR. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0549] See Figure 13 Regarding such and other concepts, systems and methods of the present invention, method 1060 for a UE in a wireless communication system includes: initiating a random access procedure (step 1062); receiving a RAR, wherein the RAR includes a channel access type indication (step 1064); and determining, based on the UE's LBT mode, whether to perform an LBT for Msg3 regardless of the channel access type indication in the RAR (step 1066).

[0550] In various embodiments, when the UE is in a no-LBT mode and / or when the UE is configured not to perform LBT, the UE determines whether to perform LBT for Msg3 based on the UE's LBT mode, regardless of the channel access type indication in the RAR.

[0551] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE does not perform LBT for Msg3.

[0552] In various embodiments, when the UE is in LBT-free mode and / or when the UE is configured not to perform LBT, the UE ignores the channel access type indication in the RAR.

[0553] In various embodiments, when the UE is in LBT mode and / or when the UE is configured to perform LBT, the UE does not ignore the channel access type indication in the RAR.

[0554] In various embodiments, the UE operates in a shared spectrum.

[0555] In various embodiments, LBT refers to the channel access scheme and / or sensing of the channel used to perform transmission.

[0556] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a base station, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) initiate a random access procedure, (ii) receive a RAR, wherein the RAR includes a channel access type indication, and (iii) determine whether to perform an LBT for Msg3 based on the LBT mode of the UE, regardless of the channel access type indication in the RAR. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0557] See Figure 14 Regarding such and other concepts, systems and methods of the present invention, method 1070 for a base station in a wireless communication system includes: receiving or detecting a preamble received from a UE (step 1072); transmitting a RAR to the UE, wherein the RAR includes a channel access type field regardless of whether LBT is performed (step 1074).

[0558] In various embodiments, the Channel Access Type field indicates whether the UE performs LBT for Msg 3.

[0559] In various embodiments, the UE operates in the shared spectrum and / or does not provide ChannelAccessMode-r16="semi-static".

[0560] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a base station, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive or detect a preamble received from a UE, and (ii) transmit a RAR to the UE, wherein the RAR includes a channel access type field regardless of whether LBT is performed. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

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

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

[0563] 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 different ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented or practiced by using other structures, functions, or structures and functions other than or different from one or more 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.

[0564] 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, voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof, can be used to represent data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the foregoing description.

[0565] 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., a digital implementation, an analog implementation, or a combination of both, which may be designed using source decoding or some other technique) and have instructions in various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination thereof. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.

[0566] 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 may 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.

[0567] 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 the specific order or hierarchy of steps in a process can be rearranged based on design preferences, while remaining within the scope of this disclosure. The appended method claims give the elements of each step in an exemplary order and are not intended to limit one to the given specific order or hierarchy.

[0568] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in 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 medium known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, this machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. Example storage media can be integrated with a processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside as discrete components in a user equipment. 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.

[0569] 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 user equipment, characterized in that, include: Initiate a random access procedure; Receive a random access response from the base station, wherein the random access response includes an indication of the channel access type and the cyclic prefix extension; as well as The system determines whether to perform a listen-before-speak (LBS) operation for Msg3 based on the indications of the channel access type and the cyclic prefix extension in the random access response. Specifically, if the LBS indications of the channel access type and the cyclic prefix extension in the random access response indicate that the user equipment should not perform a LBS operation, then the user equipment will not perform a LBS operation for Msg3. The random access response also includes a random access response grant. The channel access type and cyclic prefix extension indicated by the indication of the channel access type and cyclic prefix extension are different from those of the channel access type and cyclic prefix extension indicated by the random access response grant indication.

2. The method according to claim 1, characterized in that, When the user equipment is in listen-before-speak mode and / or when the user equipment is configured to perform listen-before-speak, the user equipment determines whether to perform listen-before-speak for Msg3 based on the channel access type indication in the random access response.

3. The method according to claim 2, characterized in that, When the user equipment is in a no-listen-before-speak mode and / or when the user equipment is configured not to perform a listen-before-speak, the user equipment determines whether to perform a listen-before-speak for Msg3 based on the user equipment's listen-before-speak mode, regardless of the channel access type indication in the random access response.

4. The method according to claim 2, characterized in that, When the user equipment is in a no-listen-before-speak mode and / or when the user equipment is configured not to perform a listen-before-speak, the user equipment does not perform a listen-before-speak for Msg3.

5. The method according to claim 2, characterized in that, When the user equipment is in a no-listen-before-speak mode and / or when the user equipment is configured not to perform a listen-before-speak, the user equipment ignores the channel access type indication in the random access response.

6. The method according to claim 2, characterized in that, The user equipment determines how to interpret the channel access type indication based on the user equipment's listen-before-speak mode.

7. The method according to claim 1, characterized in that, The user equipment operates in a shared spectrum.

8. The method according to claim 1, characterized in that, The user equipment does not provide ChannelAccessMode-r16="semi-static".

9. The method according to claim 1, characterized in that, "Listen first, then speak" refers to channel access schemes and / or sensing the channels used to perform transmissions.

10. A method for a user equipment, characterized in that, include: Initiate a random access procedure; Receive a random access response from the base station, wherein the random access response includes an indication of the channel access type and the cyclic prefix extension; as well as Whether to perform a listen-before-speak mode for Msg3 is determined based on the listen-before-speak mode of the user equipment configured by the radio resource control configuration, regardless of the indication of the channel access type and the indication of the cyclic prefix extension in the random access response. The random access response also includes a random access response grant. The channel access type and cyclic prefix extension indicated by the indication of the channel access type and cyclic prefix extension are different from those of the channel access type and cyclic prefix extension indicated by the random access response grant indication.

11. The method according to claim 10, characterized in that, When the user equipment is in a no-listen-before-speak mode and / or when the user equipment is configured not to perform a listen-before-speak, the user equipment does not perform a listen-before-speak for Msg3.

12. The method according to claim 10, characterized in that, When the user equipment is in a no-listen-before-speak mode and / or when the user equipment is configured not to perform a listen-before-speak, the user equipment ignores the channel access type indication in the random access response.

13. The method according to claim 10, characterized in that, When the user equipment is in listen-before-speak mode and / or when the user equipment is configured to perform listen-before-speak, the user equipment does not ignore the channel access type indication in the random access response.

14. The method according to claim 10, characterized in that, The user equipment operates in a shared spectrum.

15. The method according to claim 10, characterized in that, "Listen first, then speak" refers to channel access schemes and / or sensing the channels used to perform transmissions.

16. A method for a base station, characterized in that, include: Receive or detect preambles received from user equipment; as well as A random access response is transmitted to the user equipment to determine whether to perform a listen-before-tell for Msg3, wherein the random access response includes indications of the channel access type and cyclic prefix extension, regardless of whether a listen-before-tell is performed. The random access response also includes a random access response grant. The channel access type and cyclic prefix extension indicated by the indication of the channel access type and cyclic prefix extension are different from those of the channel access type and cyclic prefix extension indicated by the random access response grant indication.

17. The method according to claim 16, characterized in that, The channel access type indicates whether the user equipment performs a listen-before-speak operation for Msg3.

18. The method according to claim 16, characterized in that, The user equipment operates in the shared spectrum and / or does not provide ChannelAccessMode-r16="semi-static".

Images