COT sharing indicator in message 3 of random access procedure

By introducing COT sharing indicators and channel access optimization in RAR messages, the problems of channel sensing and LBT delay during random access in NR-U systems are solved, and more efficient Msg3 transmission and resource utilization are achieved, improving the System performance and battery life of user equipment.

CN113632580BActive Publication Date: 2024-12-03TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080023580.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-03-28
Filing Date
2020-03-24
Publication Date
2024-12-03
Estimated Expiration
2040-03-24

AI Technical Summary

Technical Problem

In wireless communication systems, especially in the non-permitted spectrum environment of NR-U, there are problems of unnecessary delays and resource waste in channel sensing and LBT operations during random access, especially during Msg3 transmission. The four-step RA process and LBT mechanism cause delay and battery life problems.

Method used

By introducing a COT sharing indicator in the RAR message, the user equipment allows the user equipment to skip the traditional fourth type of LBT operation during the COT period initiated by the base station, directly perform Msg3 transmission, and optimize channel access through the channel access type and priority fields , reduce unnecessary LBT attempts.

Benefits of technology

It reduces the transmission delay of Msg3, saves the battery life of user equipment, and avoids unnecessary waste of resources by optimizing the channel access mechanism, improving the efficiency and performance of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113632580B_ABST
    Figure CN113632580B_ABST
Patent Text Reader

Abstract

A method for operating a user equipment (UE) in a wireless communication system, comprising: receiving (802) a first random access procedure message from a base station, the first random access procedure message comprising a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and sending (804) a second random access procedure message to the base station within the shared COT period. A method for operating a base station, comprising: sending (902) a first random access procedure message to a user equipment (UE), the first random access procedure message comprising a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and receiving (904) a second random access procedure message from the UE within the shared COT period.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly, to a random access procedure of a wireless communication system. Background Art

[0002] The next generation of wireless communication systems is expected to support a wide range of use cases with different requirements, ranging from fully mobile devices to stationary IoT or fixed wireless broadband devices. The traffic patterns associated with many use cases are expected to include short or long bursts of data traffic with waiting periods of varying lengths between bursts (referred to herein as inactive states). In the New Radio (NR) specifications, both licensed assisted access and standalone unlicensed operation will be supported in 3GPP. Therefore, NR is studying the procedures for physical random access channel (PRACH) transmissions and / or scheduling request (SR) transmissions in unlicensed spectrum.

[0003] Introduction to NR-U

[0004] To cope with the growing demand for data, NR is considering the use of both licensed and unlicensed spectrum. 3GPP has defined a study project on NR-based access to unlicensed spectrum (NR-U). Compared with Licensed Assisted Access (LAA) in LTE, NR-U also needs to support dual connectivity (DC) and independent scenarios, where the MAC process including the random access channel (RACH) and the scheduling process on the unlicensed spectrum are susceptible to listen-before-talk (LBT) failures. There is no such limitation in LTE LAA, because there is licensed spectrum in the LAA scenario, so the RACH and scheduling-related signaling can be transmitted on the licensed spectrum instead of the unlicensed spectrum.

[0005] For discovery reference signal (DRS) transmission (e.g., PSS / SSS, PBCH, CSI-RS), control channel transmission (e.g., PUCCH / PDCCH), physical data channels (e.g., PUSCH / PDSCH), and uplink sounding reference signals (e.g., SRS transmission), channel sensing should be applied to determine channel availability before using the channel to transmit physical signals.

[0006] The radio resource management (RRM) procedures in NR-U are generally similar to those in LAA, as the goal of NR-U is to reuse LAA / eLAA / feLAA technologies as much as possible to handle coexistence issues between NR-U and other legacy radio access technologies (RATs).

[0007] Therefore, channel access / selection for LAA is one of the important aspects of coexistence with other RATs such as Wi-Fi. For example, LAA aims to use carriers that are crowded with Wi-Fi.

[0008] In the licensed spectrum, the UE measures the Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) of the downlink radio channels (e.g., SSB, CSI-RS) and provides measurement reports to its serving eNB / gNB. However, these measurements do not reflect the interference strength on the carrier. Another metric, the Received Signal Strength Indicator (RSSI), can be used for this purpose. On the eNB / gNB side, the RSSI can be derived based on the received RSRP and RSRQ reports. However, this requires that the RSRP and RSRQ reports are available. Due to LBT failure, some RSRP or RSRP reports may be blocked, due to the Discovery Reference Signal (DRS) transmission being blocked in the downlink, or due to the measurement reports being blocked in the uplink. The RSSI measurement, together with the time information about when and for how long the UE made the measurement, can assist the gNB / eNB in ​​detecting hidden nodes. In addition, the gNB / eNB can measure the load situation of the carrier, which is useful for the network to prioritize some channels for the purpose of load balancing and avoiding channel access failures.

[0009] LTE LAA has been defined to support the measurement of average RSSI and channel occupancy for measurement reports. Channel occupancy is defined as the percentage of time that the RSSI is measured above a configured threshold. To this end, the RSSI measurement timing configuration (RMTC) includes the measurement duration (e.g., 1-5ms) and the period between measurements (e.g., {40, 80, 160, 320, 640} ms).

[0010] COT Sharing in NR-U

[0011] For nodes (e.g., NR-U gNB / UE, LTE-LAA eNB / UE, or Wi-Fi AP / STA) that are allowed to transmit in unlicensed spectrum (e.g., the 5GHz band), it is typically necessary to perform a Clear Channel Assessment (CCA). This process typically involves listening to the medium to be idle for a number of time intervals. The medium can be listened to to be idle in different ways (e.g., using energy detection, preamble detection, or using virtual carrier sensing). The latter means that the node reads control information from other transmitting nodes that indicates when the transmission ends. After sensing that the medium is idle, the node is typically allowed to transmit for a period of time, sometimes called a Transmission Opportunity (TXOP). The length of the TXOP depends on the provisions and type of CCA that has been performed, but is typically in the range of 1ms to 10ms. This duration is typically referred to as the Channel Occupancy Time (COT).

[0012] In Wi-Fi, feedback of data reception confirmation (ACK) is sent without performing clear channel assessment. Before the feedback transmission, a shorter duration (short interframe space, or SIFS) is introduced between the data transmission and the corresponding feedback (excluding the actual listening of the channel). In 802.11, the SIFS period (16μs for 5GHz OFDM PHY) is defined as:

[0013] aSIFSTime=aRxPHYDelay+aMACProcessingDelay+aRxTxTurnaroundTime

[0014] Where aRxPHYDelay defines the duration required for the PHY layer to deliver a packet to the MAC layer, aMACProcessingDelay defines the duration required for the MAC layer to trigger the PHY layer to send a response, and aRxTxTurnaroundTime defines the duration required to switch the radio from receive mode to transmit mode.

[0015] The SIFS duration is used to accommodate the hardware latency required to switch direction from receive to send.

[0016] It is expected that for NR in unlicensed bands (NR-U), similar gaps will be allowed to accommodate radio turnaround time. For example, this will enable the transmission of PUCCH carrying uplink control information (UCI) feedback and PUSCH carrying data and possibly UCI within the same transmission opportunity (TXOP) acquired by the initiating gNB, without requiring the UE to perform clear channel assessment prior to PUSCH / PUCCH transmission, as long as the gap between DL and UL transmissions is less than or equal to 16μs. Operation in this manner is generally referred to as "COT sharing". Figure 1 An example of COT sharing is shown. Specifically, Figure 1 Transmission opportunities (TXOPs) with and without COT sharing are shown, where CCA is performed by the initiating node (gNB). For the case of COT sharing, the gap between DL and UL transmissions is less than 16μs.

[0017] When the UE accesses the medium via Cat-4 LBT using a configured grant outside the gNB COT, the UE and gNB may also share the UE-acquired COT to schedule downlink (DL) data to the same UE. The UE COT information may be indicated in the UCI (e.g., CG-UCI) for configuring the granted PUSCH resources.

[0018] Figure 2An example of UE COT sharing with DL transmission is shown. For the case of COT sharing, the gap between UL and DL transmission is less than 16 μs.

[0019] Channel access process in NR-U

[0020] Listen before talk (LBT) is designed to coexist with unlicensed spectrum of other radio access technologies (RATs). In this mechanism, the radio device applies a clear channel assessment (CCA) check (i.e., channel sensing) before any transmission. The transmitter performs energy detection (ED) within a time period compared to a specific energy detection threshold in order to determine whether the channel is idle. If the channel is determined to be occupied, the transmitter performs a random back-off within the contention window before the next CCA attempt. To protect the ACK transmission, the transmitter must postpone for a period of time after each busy CCA slot before resuming the back-off. Once the transmitter seizes the opportunity to access the channel, the transmitter is only allowed to perform transmissions up to a maximum duration (i.e., maximum channel occupancy time (MCOT)). In order to differentiate QoS, channel access priorities based on service type have been defined. For example, four LBT priorities are defined for distinguishing channel access priorities between services using contention window size (CWS) and MCOT duration.

[0021] As described in 3GPP TR 38.889[1], channel access schemes for NR-based unlicensed spectrum access can be divided into the following categories:

[0022] Category 1: Transmit immediately after a short switching gap This is used for the transmitter to transmit immediately after a UL / DL switching gap inside the COT. The switching gap from reception to transmission is to accommodate the turnaround time of the transceiver and does not exceed 16 μs.

[0023] Category 2: LBT without random backoff. The duration that the channel is sensed to be idle before the transmitting entity transmits is deterministic.

[0024] Category 3: LBT with random backoff with fixed size contention window. The LBT procedure has the following procedure as one of its components: The transmitting entity draws a random number N within the contention window. The size of the contention window is specified by the minimum and maximum values ​​of N. The size of the contention window is fixed. The random number N is used in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel.

[0025] Category 4: LBT with random backoff with variable size contention window. The LBT procedure has the following procedure as one of its components: The transmitting entity draws a random number N within the contention window. The size of the contention window is specified by the minimum and maximum values ​​of N. The transmitting entity may vary the size of the contention window when drawing the random number N. The random number N is used in the LBT procedure to determine the duration of time that the channel is perceived to be idle before the transmitting entity transmits on the channel.

[0026] For different transmissions in COT and different channels / signals to be transmitted, different categories of channel access schemes may be used.

[0027] RACH procedure in NR unlicensed spectrum

[0028] The common four-step random access (RA) procedure has become the current standard for legacy systems such as LTE and NR Rel-15. It has been proposed to study a two-step procedure in which the UL message (PRACH+Msg3) is sent simultaneously and similarly two downlink (DL) messages (e.g., the timing advance command and contention resolution information in the random access response (RAR)) are sent in the DL as a synchronization response. In the conventional four-step procedure, one of the main uses of the first two messages is to obtain the UL time alignment of the UE. In many cases, such as in small cells or for fixed UEs, this may not be needed because TA=0 is sufficient (small cells) or the stored TA value from the last random access (RA) procedure can also be used for the current RA (stationary UE). In future radio networks, it can be expected that these situations are common due to the dense deployment of small cells and a large number of, for example, stationary IoT devices. The possibility of skipping the message exchange to obtain the TA value will lead to a reduction in RA latency and will be beneficial in several use cases (e.g., when sending infrequent small data packets). On the other hand, the two-step RA will consume more resources because it uses contention-based data transmission. This means that resources allocated for data may often go unused.

[0029] If both four-step and two-step RA are configured in one cell (and for that UE), the UE will select a preamble from one specific set if it wants to do four-step RA, and will select a preamble from another set if it wants to do two-step RA. Thus, preamble partitioning is done to distinguish between four-step and two-step RA.

[0030] Traditional four-step random access

[0031] The traditional four-step RA has been used in LTE and is also proposed as the baseline for NR. Figure 3 The principle of this process is shown in . The UE randomly selects the preamble to send.

[0032] When the eNB detects the preamble, it estimates the timing alignment (TA) that the UE should use in order to obtain UL synchronization at the eNB. The eNB responds with the TA in a grant to Msg3. In Msg3, the UE sends its identifier and the eNB responds by confirming the UE ID in Msg4. Msg 4 gives a contention resolution, i.e., even if several UEs use the same preamble (and Msg 3) at the same time, only one UE's identifier is sent. In LTE, it is not possible to complete a four-step RA in less than 14ms / TTI / SF.

[0033] Two-step random access

[0034] The two-step RA process provides shorter latency than the normal four-step RA. In the two-step RA, the preamble and the message corresponding to the message 3 (Msg3) in the four-step RA are transmitted in the same subframe or in two subsequent subframes. Msg3 is sent on resources dedicated to the specific preamble. This means that both the preamble and Msg3 face contention, but in this case, contention resolution means that both the preamble and Msg3 are sent without conflict, or both are sent in the case of conflict. Figure 4 A two-step process is depicted.

[0035] After successfully receiving the preamble and Msg 3, the eNB will respond with the TA (assuming that no or only very minor updates should be needed) and Msg 4 for contention resolution.

[0036] If the UE timing alignment is poor (e.g. using TA=0 in a large cell or using an old TA even if the UE has moved), a problem may arise that the eNB can only detect the preamble. Transmissions with inaccurate TA values ​​may interfere with transmissions from other UEs in the same cell. In addition, due to its design pattern, the preamble signal has a higher detection probability than normal data. In this case, the network can reply with a normal RAR, giving the UE a chance to send a traditional Msg3 on the scheduled resources. This is a fallback to four-step RA.

[0037] Random Access Response (RAR)

[0038] A gNB that detects more than one Random Access Preamble at a time may choose to split its response into more than one MAC Protocol Data Units (PDUs), or it may choose to concatenate its responses into the same MAC PDU. Figure 5 Such a concatenated MAC PDU is shown.

[0039] If the gNB cannot process all detected preambles, it can send a back-off indicator (BI) to a specific preamble, such as Figure 5If the gNB detects a preamble for requesting system information (SI), it can only acknowledge the reception, as shown in the leftmost part of subPDU#1. Figure 5 As shown in subPDU#2 in.

[0040] The gNB may choose to use RAR for confirmation, which is where Msg3 occurs. Figure 6 As shown, the subheader corresponding to RAR consists of three header fields E / T / RAPID.

[0041] like Figure 7 As shown, in addition to the field that reserves the R bit, the payload corresponding to RAR consists of three fields: Figure 7 The formats of the Timing Advance Command, UL Grant and Temporary C-RNTI are shown. The fields R and UL Grant are specified as follows. R: Reserved bit, set to "0"; UL Grant: The Uplink Grant field indicates the resources to be used on the uplink. The size of the UL Grant field is 27 bits.

[0042] UL Approval in RAR

[0043] The UL grant in the RAR schedules the PUSCH transmission (Msg3 PUSCH) from the UE. The following Table 1 gives the content of the RAR UL grant, which starts with the MSB and ends with the LSB.

[0044] Table 1 (3GPP TS 38.213 / Table 8.2-1: Random Access Response Grant Content Field Size)

[0045] RAR Permission Field Number of bits Frequency Hopping Flag 1 PUSCH frequency resource allocation 14 PUSCH time resource allocation 4 MCS 4 TPC commands for PUSCH 3 CSI Request 1 Summary of the invention

[0046] Some embodiments provide a method of operating a user equipment (UE) in a wireless communication system. The method includes: receiving a first random access procedure message from a base station, the first random access procedure message including a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and sending a second random access procedure message to the base station within the shared COT period.

[0047] Some embodiments provide a method of operating a base station. The method includes: sending a first random access procedure message to a user equipment (UE), the first random access procedure message including a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and receiving a second random access procedure message from the UE within the shared COT period.

[0048] Some other embodiments provide a method for operating a user equipment (UE) in a wireless communication system. The method includes: receiving a first random access procedure message from a base station, the first random access procedure message including a channel access type field, the channel access type field indicating a channel access type that can be used to send a second random access procedure message during a shared channel occupation time (COT) period associated with the first random access procedure message; and sending a second random access procedure message to the base station within the shared COT period.

[0049] Some other embodiments provide a method of operating a base station. The method includes: sending a first random access procedure message to a user equipment UE, the first random access procedure message including a channel access type field, the channel access type field indicating a channel access type that can be used to send a second random access procedure message during a shared channel occupation time COT period associated with the first random access procedure message; and receiving the second random access procedure message from the UE within the shared COT period. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 Transmission opportunities (TXOPs) with and without COT sharing are shown, where CCA is performed by the initiating node (gNB).

[0051] Figure 2 An example of UE COT sharing with DL transmission is shown.

[0052] Figure 3 A four-step random access procedure is shown.

[0053] Figure 4 A two-step random access procedure is shown.

[0054] Figure 5 Concatenated MAC PDUs are shown.

[0055] Figure 6 A subheader corresponding to RAR is shown consisting of three header fields E / T / RAPID.

[0056] Figure 7 The formats of the Timing Advance Command, UL Grant and Temporary C-RNTI messages are shown.

[0057] Figure 8 is a flow chart illustrating the operation of a user equipment node according to some embodiments.

[0058] Fig. 9 is a flow chart illustrating the operation of a base station according to some embodiments.

[0059] Fig.10is a flow chart illustrating the operation of a user equipment node according to other embodiments.

[0060] Fig.11 is a flow chart illustrating the operation of a base station according to other embodiments.

[0061] Fig.12 A telecommunications network is schematically shown connected to a host computer via an intermediary network.

[0062] Fig.13 It is an overall block diagram of a host computer communicating with a user device via a base station over a partially wireless connection.

[0063] Figures 14 to 17 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment. DETAILED DESCRIPTION

[0064] In RAN2#105, there are several alternatives on how to provide additional opportunities to send Msg3.

[0065] In an alternative solution, Msg3 is repeated in the time domain. In this alternative solution, the UE may repeatedly send Msg3 with the same grant at multiple opportunities in the time domain. In this alternative solution, an indicator indicating Msg3 repetition is carried in the RAR.

[0066] In another alternative, multiple grants are carried in the RAR. In this alternative, the UE receives multiple grants from one RAR message. The UE performs LBT for each grant and uses the grant that has passed LBT for the transmission of Msg3.

[0067] In another alternative, multiple RARs may be received within the same RAR window. In this alternative, the UE is allowed to receive multiple RAR messages within the same RAR window. Each RAR may carry different permissions.

[0068] In addition, RAN1 has reached agreement on the channel access mechanism for the RA procedure. Specifically, it is agreed that UL transmissions as part of the RACH procedure to initiate channel occupation do not consider LBT other than Cat 4. If it is allowed to transmit on multiple LBT bandwidths, it does not exclude the use of Cat 2 to transmit on the LBT bandwidth.

[0069] According to the protocol, this is interpreted as: the RA message of the RA procedure will apply Cat4 LBT in case the corresponding transmission is not performed within the shared COT initiated by the gNB.

[0070] RAN1 has also discussed COT sharing for NR-U. The goal is to avoid unnecessary LBT operations for subsequent transmission bursts within the COT period, which can be initiated by the gNB. The following agreement on shared DLCOT with UL bursts has been captured in TR.

[0071] Within the gNB-initiated COT, the UE's UL bursts consisting of one or more of PUSCH, PUCCH, PRACH and SRS follow the channel access scheme in Table 2 below, which is reproduced from 3GPP TR38.889 Table 7.2.1.3.1-3.

[0072] Table 2 (3GPP TR 38.889 / Table 7.2.1.3.1-3): Channel access scheme for UL bursts within COT initiated by gNB as LBE device

[0073]

[0074] A UL burst is defined as a collection of transmissions from a given UE with no gaps or gaps no greater than 16 μs. Transmissions from a UE with gaps greater than 16 μs are considered separate UL bursts. The number of LBT attempts within the COT should be determined when developing the specification.

[0075] It would be beneficial to allow the UE to send Msg3 over the transmission of Msg2 within the COT initiated by the gNB. To do this, several issues with the existing NR specification in NR Rel-15 must be addressed.

[0076] The first problem is how to send the COT sharing indicator to the UE for its Msg3 transmission.

[0077] One option to signal the indicator is via RAR message, however, the existing RAR format does not contain any indicator about COT sharing of Msg3. The second problem is how to update the existing RAR format to carry the COT sharing indicator of Msg3.

[0078] According to some embodiments, COT sharing of Msg3 is indicated to the UE during the RA process so that the UE can skip the traditional Type 4 LBT for Msg3 transmission within the shared COT period.

[0079] The COT sharing indicator may include, for example, at least one of the following fields:

[0080] 1) COT sharing indicator bit, indicating that the transmission of Msg3 together with DL transmission (Msg2 or any other DL transmission intended for other UEs) can be initiated within the current COT, and the current COT is initiated by the gNB

[0081] 2) Channel access type, indicating the channel access type configured by the gNB for Msg3 transmission.

[0082] 3) Channel access priority, indicating the channel access priority associated with the configured channel access type (e.g., Class 4 LBT).

[0083] The COT sharing indicator for Msg3 may be sent in the RAR message as part of the UL grant field, or as a new field added to the RAR message.

[0084] Through the proposed mechanism, unnecessary LBT operations for Msg3 can be avoided. Therefore, the UP delay of new data is reduced. In addition, UE battery life can be saved by avoiding unnecessary LBT operations.

[0085] Some embodiments are described herein in the context of NR unlicensed spectrum (NR-U). However, the scope of the inventive concept is not limited to NR-U scenarios. The inventive concept is also applicable to other unlicensed operation scenarios, such as LTE LAA / eLAA / feLAA.

[0086] In some embodiments, the COT sharing indicator for Msg3 may be indicated in the RAR message. The COT sharing indicator may include, for example, at least one of the above fields (ie, COT sharing indicator bit, channel access type and / or channel access priority).

[0087] There are several options for including the COT sharing indicator in the RAR message.

[0088] Option 1: The COT sharing indicator for Msg3 may be included in the UL Grant field in the RAR message.

[0089] In one example, 3GPP TS 38.213 / Table 8.2-1 may be updated as shown in Table 3 below. In this example, the highlighted fields in the table are new fields. The size of the UL grant may be increased from 27 bits to a higher value within the range (between 28 bits and 33 bits, depending on which fields are defined and the actual size of each new field).

[0090] Table 3 (3GPP TS38.213 / Table 8.2-1: Updated random access response permission content field size)

[0091]

[0092]

[0093] In another example, the COT sharing indicator may reuse some bits in any existing field in the UL grant field if they can be saved in some scenarios. In one case, it may be sufficient to use only 12 bits for PUSCH frequency resource allocation, as in LTE. Therefore, two bits may be reused to carry the COT sharing indicator. In another case, if the MCS or PUSCH frequency resource allocation can be pre-configured for the UE for Msg3 transmission, the MCS field or the PUSCH frequency resource allocation field may be saved. In another case, if the associated RA is a contention-based random access procedure, the CSI request field is not used, in which case the CSI request field may be reused for the purpose of carrying the COT sharing indicator. In yet another case, if a fixed TPC command value is pre-configured for the UE for the transmission of Msg3, the TPC command field is reused to carry the COT sharing indicator.

[0094] Option 2: The COT sharing indicator of Msg3 may be included as a new field in the RAR message. In one example, the RAR message size may be increased by 1 octet for the COT sharing indicator.

[0095] The R bits in the MAC payload of the RAR and / or the R bits in the MAC subheader with the backoff indicator may be reused for the COT sharing indicator. For the latter case, the COT sharing indicator is signaled to UEs that have sent the preamble, however, they have not yet received the RA message. In this case, the UE applies the received COT sharing indicator to subsequent Msg3 transmissions within the detected COT.

[0096] In another example, the COT sharing indicator may reuse other fields in the RAR message. In one case, if the UE is already UL aligned, or the UE is located in a small cell that does not strictly require UEs in the cell to be UL aligned for UL transmission, or the UE remains stationary, the timing advance command field may be reused for the COT sharing indicator so that its uplink timing alignment remains unchanged.

[0097] In another embodiment, the COT sharing indicator for Msg3 may be carried by other signaling means, such as downlink control information (DCI), MAC control element (CE), or RRC signaling message. In one example, the COT sharing indicator may be carried in the COT information in the GC-PDCCH signaling. In this example, the UE performs transmission of Msg3 according to the specified channel access type and / or the specified channel access priority within the detected COT period. In this example, the UE may first send a preamble. Thereafter, the UE may detect a DL signal indicating an upcoming COT period within the RAR window. Therefore, the UE may be required to monitor several PDCCHs (in different search spaces and / or different CORESETs) simultaneously.

[0098] In another embodiment, COT sharing for Msg3 and DL transmission may be configured by UE / RA event / service / channel access priority. UE capabilities may be defined accordingly.

[0099] Figure 8 Operation of a UE according to some embodiments is shown. As shown therein, a method of operating a UE in a wireless communication system includes: receiving (802) a first random access procedure message from a base station, the first random access procedure message including a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and sending (804) a second random access procedure message to the base station within the shared COT period.

[0100] Fig. 9 Operation of a base station according to some embodiments is shown. As shown therein, a method of operating a base station in a wireless communication system includes: sending (902) a first random access procedure message to a user equipment UE, the first random access procedure message including a channel occupancy time COT sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and receiving (904) a second random access procedure message from the UE within the shared COT period.

[0101] Fig.10 Operations of a UE according to other embodiments are shown. As shown therein, a method of operating a UE in a wireless communication system includes: receiving (1002) a first random access procedure message from a base station, the first random access procedure message including a channel access type field indicating a channel access type that can be used during a shared channel occupation time (COT) period; and sending (804) a second random access procedure message to the base station within the shared COT period.

[0102] Fig.11Operation of a base station according to some embodiments is shown. As shown therein, a method of operating a base station in a wireless communication system includes: sending (1102) a first random access procedure message to a user equipment UE, the first random access procedure message including a channel access type field indicating a channel access type that can be used during a shared channel occupation time (COT) period, and receiving (904) a second random access procedure message from the UE during the shared COT period.

[0103] In some embodiments, the second random access procedure message comprises a Msg3 transmission, and the first random access procedure message comprises a random access response message.

[0104] In some embodiments, the COT sharing indicator is included in the random access response message as part of the uplink grant field.

[0105] In some embodiments, the COT sharing indicator includes a COT sharing indicator bit, and the COT sharing indicator bit indicates that the second random access procedure message can be sent within the current COT period.

[0106] In some embodiments, the COT sharing indicator includes a channel access type field indicating a channel access type that may be used to send the second random access procedure message.

[0107] In some embodiments, the COT sharing indicator includes a channel access priority field indicating a channel access priority associated with a channel access type that may be used to send the second random access procedure message.

[0108] In some embodiments, the COT sharing indicator includes bits reused from an existing uplink grant field. In some embodiments, the existing uplink grant field includes an MCS field, a channel state information CSI request field, or a physical uplink shared channel PUSCH frequency resource allocation field. In some embodiments, the COT sharing indicator includes two bits in a physical uplink shared channel PUSCH uplink grant field.

[0109] In some embodiments, the COT sharing indicator comprises a new field in the uplink grant message.

[0110] In some embodiments, the COT sharing indicator comprises bits reused from a medium access control MAC payload or a MAC subheader.

[0111] In some embodiments, the COT sharing indicator comprises bits reused from the timing advance command field.

[0112] In some embodiments, the COT sharing indicator is sent in a downlink control information DCI, a MAC control element CE, or a radio resource control RRC signaling message.

[0113] COT sharing can be configured per UE, RA event, service and / or channel access priority.

[0114] Therefore, some embodiments described herein provide for Msg3 transmission in the COT period initiated by the gNB. Compared to previous approaches, some embodiments can reduce / minimize the impact of LBT on Msg3 and limit potential changes to the specification.

[0115] Specifically, compared to other alternatives, such as providing multiple grants to the UE in the RAR message, allowing the UE to send Msg3 within the DL COT with the Msg2 transmission initiated by the gNB is beneficial to reduce / minimize the impact of LBT on Msg3 and limit potential changes to the specification. In this case, if the switching gap between DL and UL is short enough, the UE can avoid the traditional Category 4 LBT for Msg3 transmission. In this way, the latency of Msg3 can be reduced by avoiding the traditional LBT operation. The gNB is responsible for scheduling the DL allocation and UL grants to the UE. Therefore, the gNB can control the gap between the end of DL transmission and the start of Msg3 transmission to be short enough.

[0116] If there is a risk that the gap between the end of DL transmission and the start of Msg3 transmission is not short enough for the intended UE, the gNB may also schedule other transmissions to other UEs to occupy the channel. Similar to the COT sharing scenario for UL bursts, if the gap is equal to or shorter than 16 microseconds, the UE may apply the immediate transmission Msg3 skipping LBT operation. If the gap is not greater than 25 microseconds, the UE may apply Cat2 LBT to the Msg3 transmission. In other cases, the UE may perform Category 4 LBT for the Msg3 transmission.

[0117] To increase the transmission opportunities of Msg3, the UE is configured to send Msg3 within the COT with Msg2 transmission initiated by the gNB.

[0118] The detailed channel access mechanism of Msg3 can be signaled in the RAR message. In LTE LAA, for dynamic scheduling, the channel access type and channel access priority are sent via an uplink grant in DCI (e.g., format 0A and format 0B), where the channel access type occupies 1 bit and the CAPC occupies 2 bits. In LTE LAA, the channel access type and channel access priority are signaled via an uplink grant in DCI.

[0119] In NR-U, it would be beneficial to apply a similar signaling mechanism to Msg3 transmission. Both the channel access type and CAPC for Msg3 transmission can be carried via the uplink grant in the RAR message.

[0120] The channel access mechanism (channel access type and / or CAPC) of Msg3 may be sent via the uplink grant in the RAR message.

[0121] Other definitions and examples:

[0122] Reference Fig.12 According to an embodiment, a communication system includes a telecommunication network 3210 (e.g., a cellular network of the 3GPP type), the telecommunication network 3210 including an access network 3211 (e.g., a radio access network) and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c (e.g., NB, eNB, gNB or other types of wireless access points), each of which defines a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE) 3291 located in the coverage area 3213c is configured to be wirelessly connected to the corresponding base station 3212c or to be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to the corresponding base station 3212.

[0123] The telecommunications network 3210 itself is connected to a host computer 3230, which may be implemented in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 3221 and 3222 between the telecommunications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may be made via an optional intermediate network 3220. The intermediate network 3220 may be a combination of one or more of a public, private, or carrier network; the intermediate network 3220 (if present) may be a backbone network or the Internet; specifically, the intermediate network 3220 may include two or more subnetworks (not shown).

[0124] Fig.12The communication system as a whole implements a connection between one of the connected UEs 3291, 3292 and the host computer 3230. The connection can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to use the access network 3211, the core network 3214, any intermediate networks 3220 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 3250. The OTT connection 3250 can be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are not aware of the routing of uplink and downlink communications. For example, the base station 3212 may not be informed or may not need to be informed of the past routing of the incoming downlink communication with data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of outgoing uplink communications originating from the UE 3291 to the host computer 3230.

[0125] Now refer to Fig.13 To describe an example implementation of the UE, base station, and host computer discussed in the previous paragraph according to the embodiment. In the communication system 3300, the host computer 3310 includes hardware 3315, and the hardware 3315 includes a communication interface 3316, and the communication interface 3316 is configured to establish and maintain a wired or wireless connection of an interface with different communication devices of the communication system 3300. The host computer 3310 also includes a processing circuit 3318, which may have storage and / or processing capabilities. Specifically, the processing circuit 3318 may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The host computer 3310 also includes software 3311, which is stored in the host computer 3310 or can be accessed by the host computer 3310 and can be executed by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 is operable to provide services to a remote user (e.g., UE 3330), which is connected via an OTT connection 3350 terminated at the UE 3330 and the host computer 3310. In providing services to the remote user, the host application 3312 may provide user data sent using the OTT connection 3350.

[0126] The communication system 3300 also includes a base station 3320 provided in the telecommunication system, the base station 3320 including hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include: a communication interface 3326 for establishing and maintaining a wired or wireless connection with an interface of different communication devices of the communication system 3300; and a radio interface 3327 for establishing and maintaining at least a connection with a network located in a coverage area ( Fig.13 The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct, or it may pass through a core network (eg, a wireless network) of the telecommunications system. Fig.13 3320) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0127] The communication system 3300 also includes the UE 3330 already mentioned. Its hardware 3335 may include a radio interface 3337, which is configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 also includes a processing circuit 3338, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The UE 3330 also includes software 3331, which is stored in the UE 3330 or can be accessed by the UE 3330 and can be executed by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 is operable to provide services to human or non-human users via the UE 3330 with the support of the host computer 3310. In the host computer 3310, the executing host application 3312 can communicate with the executing client application 3332 via the OTT connection 3350 terminated at the UE 3330 and the host computer 3310. When providing services to users, the client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 can transmit both the request data and the user data. The client application 3332 can interact with the user to generate the user data it provides.

[0128] Notice, Fig.13The host computer 3310, base station 3320 and UE 3330 shown can be respectively Fig.12 The host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 are the same. That is, the internal workings of these entities can be as follows Fig.13 As shown, and independently, the surrounding network topology can be Fig.12 network topology.

[0129] exist Fig.13 , an OTT connection 3350 has been abstractly drawn to illustrate communications between a host computer 3310 and a user device 3330 via a base station 3320, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the route, which can be configured to be hidden from the UE 3330 or from the service provider operating the host computer 3310, or from both. While the OTT connection 3350 is active, the network infrastructure can also make decisions that dynamically change the route (e.g., based on load balancing considerations or reconfiguration of the network).

[0130] The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE 3330 using the OTT connection 3350, wherein the wireless connection 3370 forms the last leg in the OTT connection 3350. More specifically, the teachings of these embodiments can improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user waiting time, better responsiveness, and extended battery life.

[0131] For the purpose of monitoring the data rate, latency and other factors improved by one or more embodiments, a measurement process may be provided. There may also be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 3350 may be implemented in software 3311 of the host computer 3310 or in software 3331 of the UE 3330 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 3350 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above or providing the value of other physical quantities that the software 3311, 3331 can use to calculate or estimate the monitoring quantity. Reconfiguration of the OTT connection 3350 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration does not need to affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such processes and functions may be known and practiced in the art. In a particular embodiment, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 to measure throughput, propagation time, latency, etc. The measurements may be implemented as follows: Software 3311 and 3331 enables the use of OTT connection 3350 to send messages (specifically, empty messages or "fake" messages) while it monitors propagation time, errors, etc.

[0132] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Fig.12 and Fig.13 To simplify the present disclosure, only reference is made to the host computer, base station and UE described herein. Fig.14 In a first step 3410 of the method, a host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission to the UE carrying the user data. In an optional third step 3430, in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0133] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Fig.12 and Fig.13For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig.15 In a first step 3510 of the method, a host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be via a base station. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0134] Fig.16 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Fig.12 and Fig.13 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig.16 Reference to the figure. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional sub-step 3621 of the second step 3620, the UE provides user data by executing a client application. In another optional sub-step 3611 of the first step 3610, the UE executes a client application, which provides user data in response to input data received from the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates transmission of user data to the host computer in an optional third sub-step 3630. In a fourth step 3640 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0135] Fig.17 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Fig.12 and Fig.13 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig.17 In an optional first step 3710 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional second step 3720, the base station initiates a transmission of the received user data to a host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0136] References

[0137] [1]3GPP TR 38.889 "Study on NR-based access to unlicensed spectrum, Release16", v16.0.0

[0138] [2] 3GPP TS38.321, V15.4.0.

[0139] [3] 3GPP TS 38.213, V15.4.0.

[0140] Example

[0141] Embodiment 1. A method for operating a user equipment UE in a wireless communication system, the method comprising:

[0142] receiving a first random access procedure message from a base station, the first random access procedure message comprising a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message; and

[0143] Sending a second random access procedure message to the base station within the shared COT period.

[0144] Embodiment 2. According to the method described in any one of the preceding embodiments, the second random access procedure message includes a Msg3 transmission.

[0145] Embodiment 3. According to the method of any one of the preceding embodiments, the first random access procedure message comprises a random access response message.

[0146] Embodiment 4. The method according to embodiment 3, wherein the COT sharing indicator is included in the random access response message as part of an uplink grant field.

[0147] Embodiment 5. According to the method of any one of the preceding embodiments, the COT sharing indicator comprises a COT sharing indicator bit, and the COT sharing indicator bit indicates that the second random access procedure message can be sent within a current COT period.

[0148] Embodiment 6. According to the method of any one of the preceding embodiments, the COT sharing indicator comprises a channel access type field, and the channel access type field indicates a channel access type that can be used to send the second random access procedure message.

[0149] Embodiment 7. The method according to any one of the preceding embodiments, wherein the COT sharing indicator comprises a channel access priority field, the channel access priority field indicating a channel access priority associated with a channel access type that can be used to send the second random access procedure message.

[0150] Embodiment 8. The method of embodiment 4, wherein the COT sharing indicator comprises bits reused from an existing uplink grant field.

[0151] Embodiment 9. The method according to embodiment 8, wherein the existing uplink grant field includes an MCS field, a channel state information CSI request field, or a physical uplink shared channel PUSCH frequency resource allocation field.

[0152] Embodiment 10. The method of embodiment 4, wherein the COT sharing indicator comprises a new field in an uplink grant message.

[0153] Embodiment 11. The method of embodiment 4, wherein the COT sharing indicator comprises bits reused from a medium access control MAC payload or a MAC subheader.

[0154] Embodiment 12. The method of embodiment 4, wherein the COT sharing indicator comprises bits reused from a timing advance command field.

[0155] Embodiment 13. The method according to embodiment 1, wherein the COT sharing indicator is sent in a downlink control information DCI, a MAC control element CE, or a radio resource control RRC signaling message.

[0156] Embodiment 14: The method according to any one of the preceding embodiments, wherein COT sharing is configured by UE, RA event, service and / or channel access priority.

[0157] Embodiment 15 A user equipment (UE) is configured to communicate with a base station, the UE comprising a radio interface and a processing circuit, the processing circuit being configured to perform the operations according to any one of Embodiments 1 to 14.

[0158] Embodiment 16. A method implemented in a base station includes:

[0159] Sending a first random access procedure message to a user equipment UE, wherein the first random access procedure message includes a channel occupancy time COT sharing indicator, wherein the COT sharing indicator indicates a shared COT period associated with the first random access procedure message; and

[0160] A second random access procedure message is received from the UE within the shared COT period.

[0161] Embodiment 17. The method according to embodiment 16, wherein the second random access procedure message comprises a Msg3 transmission.

[0162] Embodiment 18. The method according to embodiment 16 or 17, wherein the first random access procedure message comprises a random access response message.

[0163] Embodiment 19. The method according to any one of embodiments 16 to 18, wherein the COT sharing indicator is included in the random access response message as part of an uplink grant field.

[0164] Embodiment 20. The method according to any one of embodiments 16 to 19, wherein the COT sharing indicator comprises a COT sharing indicator bit, and the COT sharing indicator bit indicates that the second random access procedure message can be sent within a current COT period.

[0165] Embodiment 21. The method according to any one of embodiments 16 to 20, wherein the COT sharing indicator includes a channel access type field, and the channel access type field indicates a channel access type that can be used to send the second random access procedure message.

[0166] Embodiment 22. The method according to any one of Embodiments 16 to 21, wherein the COT sharing indicator includes a channel access priority field, the channel access priority field indicating a channel access priority associated with a channel access type that can be used to send the second random access procedure message.

[0167] Embodiment 23. The method of Embodiment 19, wherein the COT sharing indicator comprises bits reused from an existing uplink grant field.

[0168] Embodiment 24: The method according to embodiment 23, wherein the existing uplink grant field includes an MCS field, a channel state information CSI request field, or a physical uplink shared channel PUSCH frequency resource allocation field.

[0169] Embodiment 25. The method of Embodiment 19, wherein the COT sharing indicator comprises a new field in an uplink grant message.

[0170] Embodiment 26. The method of Embodiment 19, wherein the COT sharing indicator comprises bits reused from a medium access control MAC payload or a MAC subheader.

[0171] Embodiment 27. The method of embodiment 19, wherein the COT sharing indicator comprises bits reused from a timing advance command field.

[0172] Embodiment 28. The method of embodiment 16, wherein the COT sharing indicator is sent in a downlink control information (DCI), a MAC control element (CE), or a radio resource control (RRC) signaling message.

[0173] Embodiment 29. The method according to any one of embodiments 16 to 28, wherein COT sharing is configured by UE, RA event, service and / or channel access priority.

[0174] Embodiment 30. A base station is configured to communicate with a user equipment (UE), the base station comprising a radio interface and a processing circuit, the processing circuit being configured to perform the operations according to any one of embodiments 16 to 29.

[0175] Explanation of abbreviations

[0176] 3GPP Third Generation Partnership Project

[0177] BI rollback indicator

[0178] CCA Clear Channel Assessment

[0179] COT Channel Occupancy Time

[0180] CSI-RS Channel State Information-Reference Signal

[0181] CWS contention window size

[0182] DC Dual Connection

[0183] DCI Downlink Control Information

[0184] DL Downlink

[0185] DRS Discovery Reference Signal

[0186] ED Energy Detection

[0187] gNB gNodeB

[0188] LAA License Assisted Access

[0189] LBT Listen before you speak

[0190] LTE Long Term Evolution

[0191] MAC Media Access Control

[0192] MCOT Maximum Channel Occupancy Time

[0193] MCS Modulation and Coding Scheme

[0194] NR New Radio

[0195] PBCH Physical Broadcast Channel

[0196] PDCCH Physical Downlink Control Channel

[0197] PDSCH Physical Downlink Shared Channel

[0198] PDU Protocol Data Unit

[0199] PRACH Physical Random Access Channel

[0200] PSS Primary Synchronization Signal

[0201] PUCCH Physical Uplink Control Channel

[0202] PUSCH Physical Uplink Shared Channel

[0203] QoS Quality of Service

[0204] RA Random Access

[0205] RACH Random Access Channel

[0206] RAR Random Access Response

[0207] RAT Radio Access Technology

[0208] RRC Radio Resource Control

[0209] RRM Radio Resource Management

[0210] RSRP Reference Signal Received Power

[0211] RSRQ Reference Signal Received Quality

[0212] RSSI Received Signal Strength Indicator

[0213] SI System Information

[0214] SR Scheduling Request

[0215] SSB Synchronous Signal Block

[0216] SSS Secondary synchronization signal

[0217] TA Timing Alignment

[0218] TPC Transmit Power Control

[0219] UCI Uplink Control Information

[0220] UE User Equipment

[0221] UL Uplink.

Claims

1. A method for operating a user equipment (UE) in a wireless communication system, the method comprising: receiving (802) a first random access procedure message from a base station, the first random access procedure message comprising a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message, so that the UE can skip a listen-before-talk (LBT) for transmission of a second random access procedure message within the shared COT period; as well as A second random access procedure message is sent (804) to the base station within the shared COT period.

2. The method according to claim 1, wherein: The second random access process message includes Msg3 transmission.

3. The method according to claim 1 or 2, wherein: The first random access procedure message includes a random access response message.

4. The method according to claim 3, wherein: The COT sharing indicator is included in the random access response message as part of an uplink grant field.

5. The method according to claim 1, wherein: The COT sharing indicator includes a COT sharing indicator bit, and the COT sharing indicator bit indicates that the second random access procedure message can be sent within a current COT period.

6. The method according to claim 1, wherein: The COT sharing indicator includes a channel access type field, and the channel access type field indicates a channel access type that can be used to send the second random access procedure message.

7. The method according to claim 6, wherein: The channel access type field includes two bits in the physical uplink shared channel PUSCH frequency resource allocation in the uplink grant field.

8. The method according to claim 1, wherein: The COT sharing indicator includes a channel access priority field indicating a channel access priority associated with a channel access type that can be used to send the second random access procedure message.

9. The method according to claim 4, wherein: The COT sharing indicator includes bits reused from an existing uplink grant field.

10. The method according to claim 9, wherein: The existing uplink grant field includes an MCS field, a channel state information CSI request field or a physical uplink shared channel PUSCH frequency resource allocation field.

11. The method according to claim 4, wherein: The COT sharing indicator comprises a new field in the uplink grant message.

12. The method according to claim 4, wherein: The COT sharing indicator includes bits reused from a medium access control MAC payload or a MAC subheader.

13. The method according to claim 4, wherein: The COT sharing indicator includes bits reused from the timing advance command field.

14. The method according to claim 4, wherein: The COT sharing indicator comprises two bits in a physical uplink shared channel (PUSCH) resource allocation in an uplink grant field.

15. The method according to claim 1, wherein: The COT sharing indicator is sent in a downlink control information DCI, a MAC control element CE or a radio resource control RRC signaling message.

16. The method according to claim 1, wherein: COT sharing is configured per UE, RA event, service and / or channel access priority.

17. A user equipment UE, configured to communicate with a base station, the UE comprising a radio interface and a processing circuit, the processing circuit being configured to perform operations, the operations comprising: receiving (802) a first random access procedure message from a base station, the first random access procedure message comprising a channel occupancy time (COT) sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message, so that the UE can skip a listen-before-talk (LBT) for transmission of a second random access procedure message within the shared COT period; as well as A second random access procedure message is sent (804) to the base station within the shared COT period.

18. A method of operating a base station, comprising: Sending (902) a first random access procedure message to a user equipment UE, the first random access procedure message comprising a channel occupancy time COT sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message, so that the UE can skip a listen-before-talk LBT for transmission of a second random access procedure message within the shared COT period; as well as A second random access procedure message is received (904) from the UE within the shared COT period.

19. The method according to claim 18, wherein: The second random access process message includes Msg3 transmission.

20. The method according to claim 18 or 19, wherein: The first random access procedure message includes a random access response message.

21. The method according to claim 20, wherein: The COT sharing indicator is included in the random access response message as part of an uplink grant field.

22. The method according to claim 18, wherein: The COT sharing indicator includes a COT sharing indicator bit, and the COT sharing indicator bit indicates that the second random access procedure message can be sent within a current COT period.

23. The method according to claim 18, wherein: The COT sharing indicator includes a channel access type field, and the channel access type field indicates a channel access type that can be used to send the second random access procedure message.

24. The method according to claim 23, wherein: The channel access type field includes two bits in the physical uplink shared channel PUSCH frequency resource allocation in the uplink grant field.

25. The method of claim 18, wherein: The COT sharing indicator includes a channel access priority field indicating a channel access priority associated with a channel access type that can be used to send the second random access procedure message.

26. The method according to claim 21, wherein: The COT sharing indicator includes bits reused from an existing uplink grant field.

27. The method according to claim 26, wherein: The existing uplink grant field includes an MCS field, a channel state information CSI request field or a physical uplink shared channel PUSCH frequency resource allocation field.

28. The method of claim 21, wherein: The COT sharing indicator comprises a new field in the uplink grant message.

29. The method according to claim 21, wherein: The COT sharing indicator includes bits reused from a medium access control MAC payload or a MAC subheader.

30. The method of claim 21, wherein: The COT sharing indicator includes bits reused from the timing advance command field.

31. The method of claim 21, wherein: The COT sharing indicator comprises two bits in a physical uplink shared channel (PUSCH) resource allocation in an uplink grant field.

32. The method of claim 18, wherein: The COT sharing indicator is sent in a downlink control information DCI, a MAC control element CE or a radio resource control RRC signaling message.

33. The method of claim 18, wherein: COT sharing is configured per UE, RA event, service and / or channel access priority.

34. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and a processing circuit, the processing circuit being configured to perform operations, the operations comprising: Sending (902) a first random access procedure message to a user equipment UE, the first random access procedure message comprising a channel occupancy time COT sharing indicator, the COT sharing indicator indicating a shared COT period associated with the first random access procedure message, so that the UE can skip a listen-before-talk LBT for transmission of a second random access procedure message within the shared COT period; as well as A second random access procedure message is received (904) from the UE within the shared COT period.