Method, apparatus and storage medium for transmitting physical random access channel (PRACH)

By configuring a Listen-Before-Speak (LBT) failure recovery mechanism on the terminal device, executing LBT and handling failures, the problem of PRACH link anomalies in the 5G NR base station system was solved, and the stability and success rate of the link were improved.

CN116471704BActive Publication Date: 2026-02-10DATANG MOBILE COMM EQUIP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210126392.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-01-10
Filing Date
2022-02-10
Publication Date
2026-02-10
Estimated Expiration
2042-02-10

AI Technical Summary

Technical Problem

In unlicensed spectrum operations of 5G NR base station systems, terminal devices fail to perform the Listen Before Talk (LBT) procedure when transmitting the Physical Random Access Channel (PRACH), resulting in link anomalies and unavailability, which affects link stability.

Method used

If the terminal device is configured to recover from a failed LBT (Listen-The-After) failure, LBT is executed, and a failure handling process is performed in case of failure to avoid link anomalies.

Benefits of technology

It effectively maintained the stability of the link, avoided link anomalies, and ensured the continuity and success rate of PRACH transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116471704B_ABST
    Figure CN116471704B_ABST
Patent Text Reader

Abstract

The present disclosure provides a method, device and storage medium for sending a physical random access channel (PRACH). The method comprises: in the case that a terminal device is configured with a listen before talk (LBT) failure recovery configuration, performing LBT when sending a random access preamble through the PRACH; and in the case that the LBT fails, performing a failure processing procedure of the LBT. Through the present disclosure, in the case that the terminal device is configured to be exempted from LBT when sending a random access preamble through the PRACH, the LBT failure processing can be effectively performed, the link exception can be effectively avoided, and the stability of the link can be effectively maintained.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus and storage medium for transmitting a Physical Random Access Channel (PRACH). Background Technology

[0002] In the unlicensed spectrum operation of the R16 standard of the 5th Generation Mobile Communication Technology (5G) New Radio (NR) base station system, the listen-before-talk (LBT) rule is followed, which means that if the base station / terminal equipment wants to transmit a signal, it can listen to the channel.

[0003] In related technologies, when the Physical Random Access Channel (PRACH) is transmitted without performing the LBT procedure, the LBT procedure is usually skipped and the PRACH transmission is performed directly.

[0004] This approach cannot effectively handle LBT failures, making terminal devices prone to entering a link abnormal and unavailable state, thus affecting link stability. Summary of the Invention

[0005] This disclosure aims to at least partially address one of the technical problems in the related art.

[0006] Therefore, the purpose of this disclosure is to propose a method, apparatus and storage medium for transmitting a Physical Random Access Channel (PRACH), which enables effective LBT failure handling when an exemption from Listen Before Talk (LBT) is configured during the transmission of the random access preamble in the PRACH, effectively avoiding link anomalies and thus effectively maintaining link stability.

[0007] The method for transmitting a Physical Random Access Channel (PRACH) according to the first aspect of this disclosure includes: when a terminal device is configured to recover from a failed Listen-Before-Talk (LBT) configuration, executing the LBT when the PRACH transmits a random access preamble; and executing a failure handling procedure for the LBT if the execution of the LBT fails.

[0008] The method for transmitting the Physical Random Access Channel (PRACH) proposed in the first aspect of this disclosure, by performing LBT when the PRACH transmits the random access preamble in the case of a terminal device being configured to wait for LBT failure and recover configuration, and performing LBT failure handling procedures in the case of LBT failure, effectively implements LBT failure handling when the terminal device is configured to waive waiver of LBT during the transmission of the random access preamble of PRACH, which can effectively avoid link anomalies and thus effectively maintain link stability.

[0009] The apparatus for transmitting a Physical Random Access Channel (PRACH) according to a second aspect embodiment of this disclosure includes: a first execution unit configured to execute the LBT when the PRACH transmits a random access preamble, in the case that the terminal device is configured to recover from a failed Listen-After-Talk (LBT) configuration failure; and a second execution unit configured to execute a failure handling procedure for the LBT in the case that the execution of the LBT fails.

[0010] The apparatus for transmitting the Physical Random Access Channel (PRACH) according to the second aspect of this disclosure, by performing LBT when the PRACH transmits the random access preamble in the case of a terminal device being configured to wait for LBT failure recovery, and performing LBT failure handling in the case of LBT failure, effectively performs LBT failure handling when the terminal device is configured to wait for LBT during the transmission of the random access preamble of the PRACH, thereby effectively avoiding link anomalies and effectively maintaining link stability.

[0011] The apparatus for transmitting a Physical Random Access Channel (PRACH) according to a third aspect embodiment of this disclosure includes: a memory, a transceiver, and a processor; the memory for storing a computer program; the transceiver for transmitting and receiving data under the control of the processor; and the processor for reading the computer program in the memory and performing the following operations: when a terminal device is configured to perform a Listen-After-Talk (LBT) failure recovery configuration, executing the LBT when the PRACH transmits a random access preamble; and executing a failure handling procedure for the LBT if the execution of the LBT fails.

[0012] The apparatus for transmitting the Physical Random Access Channel (PRACH) according to the third aspect of this disclosure, by performing LBT when the PRACH transmits the random access preamble in the case of a terminal device being configured to wait for LBT failure recovery, and performing LBT failure handling in the case of LBT failure, effectively performs LBT failure handling when the terminal device is configured to wait for LBT during the transmission of the random access preamble of the PRACH, thereby effectively avoiding link anomalies and effectively maintaining link stability.

[0013] A processor-readable storage medium is provided according to a fourth aspect embodiment of the present disclosure, the processor-readable storage medium storing a computer program for causing the processor to execute: a method for transmitting a Physical Random Access Channel (PRACH) according to a first aspect embodiment of the present disclosure.

[0014] The processor-readable storage medium proposed in the fourth aspect of this disclosure, by performing LBT when the PRACH transmits the random access preamble in the case of a terminal device being configured to waive LBT after a failure, and performing LBT failure handling in the case of LBT failure, effectively performs LBT failure handling when the terminal device is configured to waive LBT during the transmission of the random access preamble of the PRACH. This effectively avoids link anomalies and thus effectively maintains link stability.

[0015] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0016] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

[0017] Figure 1 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to an embodiment of this disclosure;

[0018] Figure 2 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0019] Figure 3 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0020] Figure 4 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0021] Figure 5 This is a schematic diagram of the LBT failure handling process in an embodiment of this disclosure;

[0022] Figure 6 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0023] Figure 7 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0024] Figure 8 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0025] Figure 9 This is a schematic diagram of the apparatus structure for transmitting the Physical Random Access Channel (PRACH) according to an embodiment of this disclosure;

[0026] Figure 10 This is a schematic diagram of an apparatus for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure;

[0027] Figure 11 This is a schematic diagram of an apparatus for transmitting the Physical Random Access Channel (PRACH) according to another embodiment of this disclosure. Detailed Implementation

[0028] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0029] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0030] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0031] This disclosure aims to address the technical problem in related technologies where LBT failure handling cannot be effectively executed, making terminal devices prone to link abnormalities and unavailability, thus affecting link stability. It provides a method for transmitting a Physical Random Access Channel (PRACH). By executing LBT when an exemption from the listen-before-tell LBT is configured during the transmission of the random access preamble in the PRACH, and by executing LBT failure handling procedures when LBT execution fails, this method effectively executes LBT failure handling when an exemption from the listen-before-tell LBT is configured during the transmission of the random access preamble in the PRACH, effectively avoiding link abnormalities and thus effectively maintaining link stability.

[0032] The technical solutions provided in this disclosure are applicable to a variety of systems, especially 5G systems. For example, applicable systems may include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) or 5G system (5GS).

[0033] Figure 1 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to an embodiment of this disclosure.

[0034] It should be noted that the execution entity of the method for transmitting the Physical Random Access Channel (PRACH) in this embodiment is a device for transmitting the PRACH. This device can be implemented in software and / or hardware and can be configured in a terminal device. The terminal device refers to a communication device capable of transmitting and receiving digital signals, and can transmit signals to network devices through the channel.

[0035] The terminal device involved in the embodiments of this disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem, etc. The name of the terminal device may also differ in different systems.

[0036] For example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). These wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices. They exchange voice and / or data with the RAN.

[0037] Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile device, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device; however, this disclosure does not limit the scope of the terminology used in this embodiment.

[0038] Network devices can be used to interchange received air frames with Internet Protocol (IP) packets, acting as routers between wireless terminal devices and the rest of the access network, which may include IP communication networks. Network devices can also coordinate attribute management of the air interface.

[0039] For example, the network equipment involved in this disclosure can be a base transceiver station (BTS) in a Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA) system, a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long-term evolution (LTE) system, a 5G base station (gNB) in a next-generation 5G network architecture, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in this disclosure. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0040] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0041] like Figure 1 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0042] S101: If the terminal device is configured to fail and recover from the LBT (Listen Before Talk) configuration failure, LBT shall be executed when the PRACH sends the random access preamble.

[0043] The Physical Random Access Channel (PRACH) is the access channel when a terminal device (such as a user equipment UE) initiates a call. It can be mapped to the Random Access Channel (RACH) and used to transmit RACH signals. In other words, it can be used to carry transmission signals from the RACH.

[0044] The random access preamble is the actual content sent by the UE in the Physical Random Access Channel (PRACH). It consists of a sequence of signals. The process of sending the random access preamble in the PRACH can be referred to as the process of sending the Physical Random Access Channel (PRACH).

[0045] The Listen Before Talk (LBT) rule means that if you want to send a signal on a channel, you can listen to the channel. If the channel is idle, you can send a signal on the channel. If the channel is busy, sending a signal may fail.

[0046] In this context, performing LBT refers to listening to the channel. Successful LBT execution means that the channel is idle, which can trigger the transmission of a random access preamble on the PRACH. Failed LBT execution means that the channel is busy, which indicates that sending a random access preamble on the PRACH may result in transmission failure.

[0047] The "Listen First, Speak Later" LBT failure recovery configuration refers to the handling strategy set after multiple LBT failures. This LBT failure recovery configuration can be set to use the LBT execution result as a judgment condition, and based on the judgment condition, instruct the terminal device to switch the active uplink subset bandwidth (BWP). That is, switch the BWP for sending the random access preamble in PRACH, stop the ongoing RACH process, and re-initiate the random access channel RACH process. This re-initiation of RACH can be implemented by the higher layers in the terminal device to complete the parameter initialization and other processing operations for the RACH process.

[0048] In this embodiment of the disclosure, when the terminal device is configured to listen before speaking (LBT) and recover from the failure, LBT can be executed when the random access preamble is sent on the PRACH to listen to the channel and obtain the execution result of LBT. If LBT is executed successfully, it indicates that the channel is idle and can trigger the transmission of the random access preamble on the PRACH. If LBT fails, it indicates that the channel is busy. At this time, if the terminal is configured to exempt LBT during the transmission of the random access preamble on the PRACH, that is, if LBT is not executed during the transmission of the random access preamble on the PRACH, the terminal can still transmit the random access preamble on the PRACH, but it may cause the RACH process to fail.

[0049] In other embodiments, if the terminal device is configured to be exempt from the Listen Before Talk (LBT) during the PRACH transmission of the random access preamble, and the LBT failure recovery configuration is configured for the LBT, then for the PRACH transmission of the random access preamble, the LBT can be performed first, followed by the transmission of the random access preamble, or the transmission of the random access preamble can be performed first, followed by the LBT; there is no restriction on this.

[0050] S102: In the event that LBT execution fails, execute the LBT failure handling procedure.

[0051] LBT execution failure refers to a situation where the channel is busy, which may cause transmission failure when sending the random access preamble on PRACH.

[0052] The LBT failure handling process refers to the failure handling strategy for the process of transmitting the random access preamble in PRACH after the channel fails to execute LBT. The LBT failure handling process may include, for example, the execution of the random access resource selection process, or any other possible failure handling strategy, without limitation.

[0053] In this embodiment of the disclosure, when the terminal device is configured to recover from LBT failure, and after LBT is executed when the random access preamble is sent on the PRACH, the execution result of LBT can be obtained. The LBT execution result can be success or failure. Successful LBT execution means that the channel state is idle, which can trigger the transmission of the random access preamble on the PRACH. Failed LBT execution means that the channel state is busy, which indicates that if the random access preamble is sent on the PRACH, it may lead to transmission failure.

[0054] In this embodiment of the disclosure, if an indication of LBT execution failure is received, it indicates that LBT execution has failed, and the LBT failure handling process can be executed, including the random access resource selection process. The execution of the random access resource selection process can meet certain execution conditions, including receiving an LBT failure indication reported by the physical layer in the terminal device (the LBT failure indication is used to indicate LBT execution failure), not being configured to exempt the listen-before-tell LBT during the transmission of the random access preamble in PRACH, and having configured LBT failure recovery. If the execution conditions of the random access resource selection process are met, the random access resource selection process can be executed, and the random access preamble in PRACH can be sent again.

[0055] In this embodiment, by configuring the terminal device to recover from LBT failure, LBT is executed when the PRACH sends the random access preamble, and LBT failure handling is executed if LBT execution fails. This effectively executes LBT failure handling when the terminal device is configured to be exempt from LBT during the PRACH random access preamble transmission process, thus effectively avoiding link anomalies and maintaining link stability.

[0056] Figure 2 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0057] like Figure 2 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0058] S201: If the terminal device is configured to fail to recover from the LBT (Listen Before Talk) configuration failure, LBT shall be executed when the PRACH sends the random access preamble.

[0059] The Physical Random Access Channel (PRACH) is the access channel when a terminal device (such as a user equipment UE) initiates a call. It can be mapped to the Random Access Channel (RACH) and used to transmit RACH signals. In other words, it can be used to carry transmission signals from the RACH.

[0060] The random access preamble is the actual content sent by the UE in the Physical Random Access Channel (PRACH). It consists of a sequence of signals. The process of sending the random access preamble in the PRACH can be referred to as the process of sending the Physical Random Access Channel (PRACH).

[0061] The Listen Before Talk (LBT) rule means that if you want to send a signal on a channel, you can listen to the channel. If the channel is idle, you can send a signal on the channel. If the channel fails, that is, the channel is busy, it may cause the transmission to fail.

[0062] In this context, performing LBT refers to listening to the channel. Successful LBT execution means that the channel is idle, which can trigger the transmission of a random access preamble on the PRACH. Failed LBT execution means that the channel is busy, which indicates that sending a random access preamble on the PRACH may result in transmission failure.

[0063] The "Listen First, Speak Later" LBT failure recovery configuration refers to the handling strategy set after multiple LBT failures. This LBT failure recovery configuration can be set to use the LBT execution result as a judgment condition, and based on the judgment condition, instruct the terminal device to switch the active uplink subset bandwidth (BWP). That is, switch the BWP for sending the random access preamble in PRACH, stop the ongoing RACH process, and re-initiate the random access channel RACH process. This re-initiation of RACH can be implemented by the higher layers in the terminal device to complete the parameter initialization and other processing operations for the RACH process.

[0064] In this embodiment of the disclosure, when the terminal device is configured to listen before speaking (LBT) and recover from the failure, LBT can be executed when the random access preamble is sent on the PRACH to listen to the channel and obtain the execution result of LBT. If LBT is executed successfully, it indicates that the channel is idle and can trigger the transmission of the random access preamble on the PRACH. If LBT fails, it indicates that the channel is busy. At this time, if the process of sending the random access preamble on the PRACH is configured to exempt LBT from listening before speaking (i.e., LBT is not executed during the process of sending the random access preamble on the PRACH), the terminal can still send the random access preamble on the PRACH, but it may cause the RACH process to fail.

[0065] In other embodiments, if the terminal device is configured to be exempt from the Listen Before Talk (LBT) during the PRACH transmission of the random access preamble, and the LBT failure recovery configuration is configured for the LBT, then for the PRACH transmission of the random access preamble, the LBT can be performed first, followed by the transmission of the random access preamble, or the transmission of the random access preamble can be performed first, followed by the LBT; there is no restriction on this.

[0066] S202: In the event that LBT execution fails, execute the LBT failure handling procedure.

[0067] LBT execution failure refers to a situation where the channel is busy, which may cause transmission failure when sending the random access preamble on PRACH.

[0068] The LBT failure handling process refers to the failure handling strategy for the process of transmitting the random access preamble in PRACH after the channel fails to execute LBT. The LBT failure handling process may include, for example, the execution of the random access resource selection process, or any other possible failure handling strategy, without limitation.

[0069] In this embodiment of the disclosure, when the terminal device is configured to recover from LBT failure, and after LBT is executed when the random access preamble is sent on the PRACH, the execution result of LBT can be obtained. The LBT execution result can be success or failure. Successful LBT execution means that the channel state is idle, which can trigger the transmission of the random access preamble on the PRACH. Failed LBT execution means that the channel state is busy, which indicates that if the random access preamble is sent on the PRACH, it may lead to transmission failure.

[0070] In this embodiment of the disclosure, if an indication of LBT execution failure is received, it indicates that LBT execution has failed, and the LBT failure handling process can be executed, including the random access resource selection process. The execution of the random access resource selection process can meet certain execution conditions, including receiving an LBT failure indication reported by the physical layer in the terminal device (the LBT failure indication is used to indicate LBT execution failure), not being configured to exempt the listen-before-say LBT during the transmission of the random access preamble in PRACH, and having configured LBT failure recovery. If the execution conditions of the random access resource selection process are met, the random access resource selection process can be executed, and the random access preamble in PRACH can be sent again.

[0071] S203: If the random access preamble is not configured to be exempted from LBT during the PRACH transmission of the random access preamble, and the LBT is executed successfully, the random access preamble is transmitted in the PRACH.

[0072] Among them, LBT exemption means that when the terminal device sends a short control signaling, it can be sent directly without executing the LBT rule. The characteristics of the short control signaling are: the duty cycle is less than 10% within a certain transmission period (for example, the transmission period can be 100ms), that is, the transmission time is less than 10ms. During the PRACH transmission of the random access preamble, it is configured to be exempt from the listen-before-say LBT process, that is, during the PRACH transmission of the random access preamble, it is configured to not need to execute the LBT process, that is, during the PRACH transmission of the random access preamble, it is configured not to listen to the idle or busy state of the physical random access channel, and directly send the random access preamble in the PRACH.

[0073] In this embodiment of the disclosure, the fact that LBT exemption is not configured during the PRACH transmission of the random access preamble means that LBT needs to be performed to listen to the channel when the PRACH transmits the random access preamble.

[0074] In this embodiment of the disclosure, whether the terminal device is configured to be exempt from LBT (Listen Before Talk) during the transmission of the random access preamble in PRACH can be determined by the LBT exemption indication. The LBT exemption indication can be issued by the base station. When configuring RACH resources, the base station uses the LBT exemption indication to indicate whether the terminal device is exempt from LBT when transmitting PRACH by sending a broadcast message or a Radio Resource Control (RRC) message.

[0075] In this embodiment of the disclosure, if the terminal device does not receive an LBT exemption instruction from the base station, that is, if it is not configured to exempt the listen-before-speak (LBT) during the PRACH transmission of the random access preamble, then the LBT rule is executed to perform channel listening on the channel to be transmitted, in order to determine whether the channel to be transmitted is idle or busy, so as to obtain the execution result of LBT. If LBT is executed successfully, then the random access preamble is transmitted in the PRACH.

[0076] In this embodiment of the disclosure, LBT is executed at the physical layer in the terminal device, and then the physical layer can report the execution result of LBT to the higher layer in the terminal device. The higher layer is the Medium Access Control (MAC) layer in the terminal device. After receiving the execution result of LBT, the higher layer can trigger subsequent processing logic.

[0077] In this embodiment of the disclosure, before the terminal device executes LBT, the execution parameters of LBT can be determined. The execution parameters of LBT can be the LBT type and the LBT beam direction (the LBT beam direction can be omnidirectional or directional).

[0078] In this embodiment of the disclosure, the LBT type can be either type-1 or type-2. Type-1 LBT is also called LBT CAT3. Type-1 LBT involves random backoff of the transmitting node within a fixed contention window. The contention window length is fixed, for example, the contention window (CW) can be an integer (e.g., CW can be 3). Before executing LBT, a random number N between 0 and CW can be generated, and then an idle channel listening for N time slots is performed. Type-2 LBT is also called LBT CAT2. Type-2 LBT involves the transmitting node performing an idle channel detection for a fixed duration. That is, before transmitting, an idle channel listening process of a fixed duration of 13μs can be performed. This fixed duration includes two energy detection time slots. When the detection results of both detection time slots are idle, the execution result of LBT CAT2 is considered to be idle.

[0079] In this embodiment of the disclosure, if LBT exemption is not configured during the PRACH transmission of the random access preamble, and if LBT is executed successfully, the random access preamble can be transmitted during PRACH. After LBT is executed at the physical layer in the terminal device, the higher layers in the terminal device can receive the execution result of LBT.

[0080] In this embodiment, by sending the random access preamble in PRACH without configuring an exemption from LBT and with successful LBT execution, the random access preamble can be sent in PRACH. This allows for LBT to be performed to listen to the channel even when no exemption from LBT is configured during the PRACH random access preamble transmission process. If the LBT execution is successful, the random access preamble can be sent in PRACH. This effectively ensures the execution continuity of the random access preamble transmission process in PRACH and effectively guarantees the success rate of random access preamble transmission in PRACH.

[0081] In this embodiment, by configuring an exemption from Listen-Before-Speak (LBT) during the PRACH random access preamble transmission process, LBT is executed. If LBT execution fails, a failure handling procedure for LBT is performed. This effectively prevents link anomalies and maintains link stability. Alternatively, by not configuring an exemption from LBT during PRACH random access preamble transmission and successfully executing LBT, LBT can be executed to listen to the channel even without an exemption. If LBT execution is successful, the random access preamble can be transmitted in PRACH. This effectively ensures the continuity of the random access preamble transmission process and guarantees a high transmission success rate.

[0082] Figure 3 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0083] like Figure 3 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0084] S301: If the random access preamble is not configured to be exempted from LBT during the PRACH transmission of the random access preamble, and the LBT is executed successfully, the random access preamble is transmitted in the PRACH.

[0085] Among them, LBT exemption means that when the terminal device sends a short control signaling, it can be sent directly without executing the LBT rule. The characteristics of the short control signaling are: the duty cycle is less than 10% within a certain transmission period (for example, the transmission period can be 100ms), that is, the transmission time is less than 10ms. During the PRACH transmission of the random access preamble, it is configured to be exempt from the listen-before-say LBT process, that is, during the PRACH transmission of the random access preamble, it is configured to not need to execute the LBT process, that is, during the PRACH transmission of the random access preamble, it is configured not to listen to the idle or busy state of the physical random access channel, and directly send the random access preamble in the PRACH.

[0086] In this embodiment of the disclosure, the fact that LBT exemption is not configured during the PRACH transmission of the random access preamble means that LBT needs to be performed to listen to the channel when the PRACH transmits the random access preamble.

[0087] In this embodiment of the disclosure, whether the terminal device is configured to be exempt from LBT (Listen Before Talk) during the transmission of the random access preamble in PRACH can be determined by the LBT exemption indication. The LBT exemption indication can be issued by the base station. When configuring RACH resources, the base station uses the LBT exemption indication to indicate whether the terminal device is exempt from LBT when transmitting PRACH by sending a broadcast message or a Radio Resource Control (RRC) message.

[0088] In this embodiment of the disclosure, if the terminal device does not receive an LBT exemption instruction from the base station, that is, if it is not configured to exempt the listen-before-speak (LBT) during the PRACH transmission of the random access preamble, then the LBT rule is executed to perform channel listening on the channel to be transmitted, in order to determine whether the channel to be transmitted is idle or busy, so as to obtain the execution result of LBT. If LBT is executed successfully, then the random access preamble is transmitted in the PRACH.

[0089] In this embodiment of the disclosure, LBT is executed at the physical layer in the terminal device, and then the physical layer can report the execution result of LBT to the higher layer in the terminal device. The higher layer is the Medium Access Control (MAC) layer in the terminal device. After receiving the execution result of LBT, the higher layer can trigger subsequent processing logic.

[0090] In this embodiment of the disclosure, before the terminal device executes LBT, the execution parameters of LBT can be determined. The execution parameters of LBT can be the LBT type and the LBT beam direction (the LBT beam direction can be omnidirectional or directional).

[0091] In this embodiment of the disclosure, the LBT type can be either type-1 or type-2. Type-1 LBT is also called LBT CAT3. Type-1 LBT involves random backoff of the transmitting node within a fixed contention window. The contention window length is fixed, for example, the contention window (CW) can be an integer (e.g., CW can be 3). Before executing LBT, a random number N between 0 and CW can be generated, and then an idle channel listening for N time slots is performed. Type-2 LBT is also called LBT CAT2. Type-2 LBT involves the transmitting node performing an idle channel detection for a fixed duration. That is, before transmitting, an idle channel listening process of a fixed duration of 13μs can be performed. This fixed duration includes two energy detection time slots. When the detection results of both detection time slots are idle, the execution result of LBT CAT2 is considered to be idle.

[0092] In this embodiment of the disclosure, if the random access preamble is not configured to be exempted from LBT during the PRACH transmission of the random access preamble and the LBT is executed successfully, the random access preamble can be transmitted through the PRACH. After the physical layer in the terminal device executes the LBT, the higher layer in the terminal device can receive the execution result of the LBT.

[0093] S302: Upon receiving an LBT failure indication, perform a random access resource selection procedure.

[0094] Among them, the LBT failure indication is a result indication used to characterize the failure of LBT execution. It is used to indicate that the LBT execution failed and can be received by the higher layer of the terminal device.

[0095] The random access resource selection process refers to switching to a new uplink channel to attempt to send a random access preamble on the PRACH.

[0096] In this embodiment of the disclosure, if the LBT exemption is not configured during the PRACH random access preamble transmission process, the LBT can be executed at the physical layer of the terminal device to obtain the LBT execution result. The LBT execution result is then converted into an LBT execution indication and reported to the higher layer of the terminal device. If the LBT execution fails, an LBT failure indication is reported to the higher layer of the terminal device. After receiving the LBT failure indication, if the terminal device is configured to recover from LBT failure, the higher layer of the terminal device executes the random access resource selection process to retry the RACH process.

[0097] In this embodiment of the disclosure, during the random access resource selection process, a random access channel (RACH) process can be performed. The user equipment (UE) sends a random access preamble to the base station on the physical random access channel (PRACH). After receiving the random access preamble, the base station sends a random access response (RAR) on the physical downlink shared channel (PDSCH). Then, the UE can send information such as the cell radio network temporary identifier on the physical uplink shared channel (PUSCH) according to the uplink scheduling information to perform radio resource control (RRC) connection. The base station sends a contention resolution message to the UE to determine whether the UE has successfully established a connection with the base station.

[0098] In this embodiment, by not configuring an exemption from LBT during the PRACH random access preamble transmission process and executing a random access resource selection process when an LBT failure indication is received, the random access resource selection process is used to switch the link to execute the PRACH random access preamble transmission process after receiving the LBT failure indication. This allows the PRACH transmission process to be retried when LBT execution fails.

[0099] In this embodiment, by not configuring an exemption from LBT during the PRACH random access preamble transmission process and successfully executing LBT, a random access preamble is transmitted in the PRACH. This allows for LBT to be executed to listen to the channel even when no exemption from LBT is configured during the PRACH random access preamble transmission process. Sending the random access preamble in the PRACH when LBT execution is successful effectively ensures the continuity of the random access preamble transmission process and the success rate of transmission. By not configuring an exemption from LBT during the PRACH random access preamble transmission process and executing a random access resource selection process upon receiving an LBT failure indication, the random access resource selection process switches the link to execute the random access preamble transmission process in the PRACH, enabling the PRACH transmission process to be retried when LBT execution fails.

[0100] Figure 4 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0101] like Figure 4 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0102] S401: In the case where the terminal device is configured to fail to recover from the LBT failure, the LBT configuration information is determined when the PRACH sends the random access preamble. The LBT configuration information is determined by the base station or by the terminal device.

[0103] LBT configuration information refers to parameter information that can be determined before LBT is executed. This LBT configuration information can be the type information of LBT and the beam direction information of LBT. The LBT configuration information can be determined by the base station or by the terminal equipment.

[0104] In this embodiment of the disclosure, when the base station determines the LBT configuration information, the base station can configure the LBT type information and beam direction information. The LBT type can be type-1 or type-2, and the LBT beam direction information can be omnidirectional or directional. When the base station determines the LBT configuration information, the base station can configure the LBT type information and beam direction information. The LBT type can be set to type-1 or type-2, and the LBT beam direction information can be set to omnidirectional or directional to obtain the LBT configuration information.

[0105] For example, a base station can be configured with LBT configuration information as follows:

[0106] RACH configuration information RACH-ConfigCommon

[0107] {

[0108] LBT_type_Msg1 ENUMERATED{type-1, type-2}

[0109] }

[0110] LBT_type_Msg1 is used to instruct the terminal device to send PRACH. NUMERATED indicates enumeration. The LBT type is either type-1 or type-2. When NUMERATED indicates type-1, the terminal device executes type-1 LBT when sending PRACH. When NUMERATED indicates type-2, the terminal device executes type-2 LBT when sending PRACH.

[0111] In other embodiments, when configuring the LBT type information in the LBT configuration information, only one type can be indicated. When LBT_type_Msg1 is configured, the terminal device executes according to the type-1 type LBT, and when it is not configured, the terminal device executes according to the type-2 type LBT. Alternatively, when LBT_type_Msg2 is configured, the terminal device executes according to the type-2 type LBT, and when it is not configured, the terminal device executes according to the type-1 type LBT.

[0112] In other embodiments, the terminal device can also configure the LBT type information and LBT beam direction information. The terminal device can determine the LBT configuration information settings and use the configured information as the LBT configuration information.

[0113] S402: Execute LBT according to the LBT configuration information.

[0114] In this embodiment of the disclosure, after the LBT configuration information is determined by the base station or by the terminal device, LBT can be executed according to the LBT configuration information.

[0115] In this embodiment of the disclosure, when performing LBT according to LBT configuration information, the LBT of the corresponding type and beam direction can be performed according to the LBT type information and LBT beam direction information in the LBT configuration information.

[0116] Optionally, in some embodiments, the LBT configuration information includes: LBT type, and / or, LBT beam direction, so that the executed LBT can be configured according to the LBT type and LBT beam direction in the LBT configuration information, thereby realizing adaptive configuration of the LBT executed when listening to the channel and effectively improving the channel listening effect.

[0117] The LBT beam direction can be either an omnidirectional beam direction or a directional beam direction.

[0118] In this embodiment of the disclosure, the LBT type can be either type-1 or type-2. Type-1 LBT is also called LBT CAT3. Type-1 LBT involves random backoff of a fixed contention window by the transmitting node. The contention window length is fixed, for example, the contention window can be an integer (e.g., the contention window (CW) can be 3). Before executing LBT, a random number N between 0 and CW can be generated, and then an idle channel listening for N time slots is performed. Type-2 LBT is also called LBT CAT2. Type-2 LBT involves a fixed-duration idle channel detection by the transmitting node. That is, before transmitting, a fixed-duration idle channel listening process of 13μs can be performed. This fixed duration includes two energy detection time slots. When the detection results of both detection time slots are idle, the execution result of LBT CAT2 is considered to be idle.

[0119] In this embodiment of the disclosure, when executing an LBT according to the LBT configuration information, the LBT of the corresponding type and the corresponding beam direction can be called and executed according to the LBT type and LBT beam direction in the LBT configuration information.

[0120] In this embodiment, when the terminal device is configured to recover from a failed Listen-Before-Speak (LBT) configuration failure, the LBT configuration information is determined when the PRACH sends the random access preamble. The LBT configuration information is determined by either the base station or the terminal device. Based on the LBT configuration information, LBT is executed, thereby enabling the corresponding type of LBT to be executed to listen to the channel. Since the LBT configuration information can be determined by either the base station or the terminal device, adaptive configuration of the LBT configuration information can be achieved, improving the listening effect of channel listening processing.

[0121] S403: In the event that LBT execution fails, execute the LBT failure handling procedure.

[0122] In this case, LBT execution failure means that the channel is busy. This indicates that if a random access preamble is sent on PRACH, it may lead to transmission failure.

[0123] The LBT failure handling process refers to the failure handling strategy for the process of transmitting the random access preamble in PRACH after the channel fails to execute the LBT. The LBT failure handling process may include, for example, the execution of the random access resource selection process, or it may be other types of failure handling strategies, without any restrictions.

[0124] In this embodiment of the disclosure, when the terminal device is configured to recover from LBT failure, and after LBT is executed while the random access preamble is being sent on the PRACH, the execution result of LBT can be obtained. The LBT execution result can be either successful or unsuccessful. Successful LBT execution means that the channel state is idle and the random access preamble can be sent on the PRACH. Unsuccessful LBT execution means that the channel state is busy, which indicates that sending the random access preamble on the PRACH may result in transmission failure.

[0125] In this embodiment of the disclosure, if an indication of LBT execution failure is received, it indicates that LBT execution has failed, and the LBT failure handling process can be executed, including the random access resource selection process. The execution of the random access resource selection process can meet certain execution conditions, including receiving an LBT failure indication reported by the physical layer in the terminal device (the LBT failure indication is used to indicate LBT execution failure), not being configured to exempt the listen-before-tell LBT during the transmission of the random access preamble in PRACH, and having configured the LBT failure recovery configuration. If the execution conditions of the random access resource selection process are met, the random access resource selection process can be executed, switching to a new uplink channel to attempt to transmit the random access preamble in PRACH.

[0126] For example, such as Figure 5 As shown, Figure 5 This is a schematic diagram of the LBT failure handling process in this embodiment of the disclosure. If LBT exemption is configured during the PRACH random access preamble transmission process, LBT is executed at the physical layer in the terminal device, and the execution result of LBT is reported to the higher layer. If LBT execution fails, the LBT failure handling process is executed.

[0127] In this embodiment, by reverting to the Listen-Before-Speak (LBT) configuration when the terminal device is configured to recover from a LBT failure, LBT is executed when the PRACH transmits the random access preamble. If LBT execution fails, a failure handling process for LBT is implemented. This effectively handles LBT failures when the terminal device is configured to be exempt from LBT during the PRACH random access preamble transmission process, effectively preventing link anomalies and maintaining link stability. The LBT execution is configured according to the LBT type and LBT beam direction in the LBT configuration information, enabling LBT execution during channel snooping. Adaptive configuration ensures effective channel monitoring. In the event of a failed LBT (Listen-Before-Speak) configuration recovery for the terminal device, the LBT configuration information is determined when the PRACH sends the random access preamble. This LBT configuration information can be determined by the base station or the terminal device. Based on the LBT configuration information, LBT is executed, allowing for the appropriate type of LBT to monitor the channel. Since the LBT configuration information can be determined by either the base station or the terminal device, adaptive configuration of the LBT configuration information can be achieved, improving the effectiveness of channel monitoring.

[0128] Figure 6 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0129] like Figure 6 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0130] S601: Receive an indication message sent by the base station to configure the Random Access Channel (RACH) or via system broadcast.

[0131] The indication message for the random access channel RACH is used to determine whether an exemption from LBT is configured during the transmission of the random access preamble in the PRACH. This indication message for configuring the random access channel RACH can be configured and sent by the base station, or the base station can send other system broadcast indication messages. The terminal device receives the indication message for configuring the random access channel RACH or the system broadcast indication message sent by the base station.

[0132] In this embodiment of the present disclosure, when receiving a configuration random access channel (RACH) or system broadcast indication message sent by a base station, a data transmission interface can be pre-configured on the device that transmits the physical random access channel (PRACH). After the base station configures the RACH indication message, the base station can send the indication message through a broadcast message or an RRC message, or the base station can send other system broadcast indication messages. Then, the device that transmits the physical random access channel (PRACH) can receive the configuration random access channel (RACH) indication message sent by the base station through the data transmission interface.

[0133] S602: Based on the instruction message, determine whether an exemption from LBT is configured during the PRACH transmission of the random access preamble.

[0134] In this embodiment of the disclosure, after the terminal device receives an indication message sent by the base station to configure random access channel (RACH) resources or system broadcast, it can analyze and process the received indication message to detect whether the indication message contains a target field for determining whether LBT exemption is configured during the transmission of the random access preamble in the PRACH.

[0135] For example, a base station can configure indication messages as follows:

[0136] RACH configuration information RACH-ConfigCommon

[0137] {

[0138] LBT_exempt_Msg1 ENUMERATED{TRUE,FALSE}

[0139] }

[0140] In this context, LBT_exempt_Msg1 is the target field in the LBT exemption indication message, which indicates whether LBT exemption is configured during the transmission of the random access preamble in PRACH. ENUMERATED represents enumeration, which is either TRUE or FALSE. When ENUMERATED is TRUE, the terminal device can be considered as being configured to be exempt from LBT when sending PRACH, meaning that LBT execution is not triggered and the random access preamble can be sent directly in PRACH. When ENUMERATED is FALSE, the terminal device can be considered as not being configured to be exempt from LBT when sending PRACH, meaning that LBT execution can be triggered, and the random access preamble can only be sent in PRACH if LBT execution is successful.

[0141] In this embodiment of the present disclosure, when receiving an indication message from the base station to configure the Random Access Channel (RACH) or a system broadcast, and determining whether to configure the target field in the indication message, if the target field in the indication message is detected, it is determined that the LBT exemption is configured during the PRACH random access preamble transmission process, and then the LBT can be executed; if the target field in the indication message is not detected, it is determined that the LBT exemption is not configured during the PRACH random access preamble transmission process, and then the LBT can be executed.

[0142] In this embodiment, by receiving a configuration random access channel (RACH) or system broadcast indication message sent by the base station, it is determined whether LBT exemption is configured during the transmission of the random access preamble in the PRACH based on the indication message. This method effectively improves the accuracy and timeliness of determining whether LBT exemption is configured, and enables timely triggering of subsequent processing logic based on the indication message, thus effectively avoiding link anomalies.

[0143] Optionally, in some embodiments, it is determined whether the cell accessed by the terminal device is configured to be exempt from LBT based on the indication message, or, if no indication message is received, it is determined that the cell accessed by the terminal device is configured to be exempt from LBT. Thus, it is possible to determine whether the cell accessed by the terminal device is configured to be exempt from LBT based on the indication message, that is, to determine the mode of the cell accessed by the terminal device. This combines the LBT mode with the indication message for configuring LBT exemption by sending RACH information, thereby effectively reducing the overhead of the indication message.

[0144] In this embodiment of the disclosure, when the base station sends an indication message for configuring the Random Access Channel (RACH) or system broadcast, it can indicate whether the cell to which the terminal device is accessed is configured to be exempt from LBT. That is, it can indicate the mode of the cell to which the terminal device is accessed. The mode of the cell to which the terminal device is accessed is divided into LBT mode and NO-LBT mode. In LBT mode, the LBT process is performed when data or signals are transmitted on the channel (the channel includes PRACH and any other channel / signal information). In NO-LBT mode, the LBT process is not performed when data or signals are transmitted on the channel.

[0145] In this embodiment of the disclosure, when the base station configures the indication message of the random access channel RACH to indicate the mode of the cell accessed by the terminal device, 1 bit of indication information can be used to indicate the LBT mode or the NO-LBT mode.

[0146] For example, a base station can configure indication messages as follows:

[0147] LBT-modeAndMsg1_exempt ENUMERATED{TRUE, FALSE};

[0148] Here, ENUMERATED represents enumeration, which is divided into TRUE and FALSE. When LBT-modeAndMsg1_exempt is TRUE, the terminal device can be regarded as being configured to be exempt from LBT when sending PRACH, and the cell accessed by the terminal device is in LBT mode. When LBT-modeAndMsg1_exempt is FALSE, the terminal device can be regarded as not being configured to be exempt from LBT when sending PRACH, and the cell accessed by the terminal device is in LBT mode. When LBT-modeAndMsg1_exempt is not configured or indicated by the base station, that is, when the terminal device does not receive an indication message, it is determined that the cell accessed by the terminal device is in NO-LBT mode, and the cell accessed by the terminal device is configured to be exempt from LBT.

[0149] In other embodiments, the base station may send other system broadcast messages to determine whether the cell accessed by the terminal device is configured to be exempt from LBT. The indication message in the other system broadcast may indicate whether the cell accessed by the terminal device is configured to be exempt from LBT. After receiving the configuration random access channel RACH or the system broadcast indication message sent by the base station, the terminal device may determine whether it is configured to be exempt from LBT during the transmission of the random access preamble in the PRACH according to the indication message.

[0150] Optionally, in some embodiments, when determining whether an LBT exemption is configured during the PRACH random access preamble transmission process, the geographical location of the terminal device is determined. If the geographical location belongs to a target location area, it is determined that an LBT exemption is configured during the PRACH random access preamble transmission process. Here, the target location area is the location area where an LBT exemption is configured during the PRACH random access preamble transmission process. If the geographical location does not belong to the target location area, it is determined that an LBT exemption is not configured during the PRACH random access preamble transmission process. This allows the terminal device to determine whether an LBT exemption is configured during the PRACH random access preamble transmission process by combining its own geographical location, thus enabling flexible determination of whether an LBT exemption is configured during the PRACH random access preamble transmission process.

[0151] The target location area refers to the location area where the terminal device configured to be exempt from LBT is located during the PRACH transmission of the random access preamble.

[0152] In this embodiment of the disclosure, when determining whether an exemption from LBT is configured during the PRACH transmission of the random access preamble, the geographical location of the terminal device can first be obtained through location processing. Then, the geographical location of the terminal device can be searched within the target location area. If the geographical location of the terminal device belongs to the target location area, it is determined that an exemption from LBT is configured during the PRACH transmission of the random access preamble. If the geographical location of the terminal device does not belong to the target location area, it is determined that an exemption from LBT is not configured during the PRACH transmission of the random access preamble.

[0153] S603: Execute LBT.

[0154] In this embodiment of the disclosure, after determining whether an exemption from LBT is configured during the PRACH transmission of the random access preamble according to the indication message, LBT can be executed to listen to the channel.

[0155] S604: If the random access preamble is not configured to be exempted from LBT during the PRACH transmission of the random access preamble, and the LBT is executed successfully, the random access preamble is transmitted in the PRACH.

[0156] Among them, LBT exemption means that when the terminal device sends a short control signaling, it can be sent directly without executing the LBT rule. The characteristics of the short control signaling are: the duty cycle is less than 10% within a certain transmission period (for example, the transmission period can be 100ms), that is, the transmission time is less than 10ms. During the PRACH transmission of the random access preamble, it is configured to be exempt from the listen-before-say LBT process, that is, during the PRACH transmission of the random access preamble, it is configured to not need to execute the LBT process, that is, during the PRACH transmission of the random access preamble, it is configured not to listen to the idle or busy state of the physical random access channel, and directly send the random access preamble in the PRACH.

[0157] In this embodiment of the disclosure, the fact that LBT exemption is not configured during the PRACH transmission of the random access preamble means that LBT needs to be performed to listen to the channel when the PRACH transmits the random access preamble.

[0158] In this embodiment of the disclosure, whether the terminal device is configured to be exempt from LBT (Listen Before Talk) during the transmission of the random access preamble in PRACH can be determined by the LBT exemption indication. The LBT exemption indication can be issued by the base station. When configuring RACH resources, the base station uses the LBT exemption indication to indicate whether the terminal device is exempt from LBT when transmitting PRACH by sending a broadcast message or a Radio Resource Control (RRC) message.

[0159] In this embodiment of the disclosure, if the terminal device does not receive an LBT exemption instruction from the base station, that is, if it is not configured to exempt the listen-before-speak (LBT) during the transmission of the random access preamble in PRACH, then the LBT rule is executed to perform channel listening on the channel to be transmitted, in order to determine whether the channel to be transmitted is idle or busy, so as to obtain the execution result of LBT. If LBT is executed successfully, then the random access preamble is transmitted in PRACH.

[0160] In this embodiment of the disclosure, LBT is executed at the physical layer in the terminal device, and then the physical layer can report the execution result of LBT to the higher layer in the terminal device. The higher layer is the Medium Access Control (MAC) layer in the terminal device. After receiving the execution result of LBT, the higher layer can trigger subsequent processing logic.

[0161] In this embodiment of the disclosure, before the terminal device executes LBT, the execution parameters of LBT can be determined. The execution parameters of LBT can be the LBT type and the LBT beam direction (the LBT beam direction can be omnidirectional or directional).

[0162] In this embodiment of the disclosure, the LBT type can be either type-1 or type-2. Type-1 LBT is also called LBT CAT3. Type-1 LBT involves random backoff of the transmitting node within a fixed contention window. The contention window length is fixed, for example, the contention window (CW) can be an integer (e.g., CW can be 3). Before executing LBT, a random number N between 0 and CW can be generated, and then an idle channel listening for N time slots is performed. Type-2 LBT is also called LBT CAT2. Type-2 LBT involves the transmitting node performing an idle channel detection for a fixed duration. That is, before transmitting, an idle channel listening process of a fixed duration of 13μs can be performed. This fixed duration includes two energy detection time slots. When the detection results of both detection time slots are idle, the execution result of LBT CAT2 is considered to be idle.

[0163] In this embodiment of the disclosure, if LBT exemption is not configured during the PRACH transmission of the random access preamble, and if LBT is executed successfully, the random access preamble can be transmitted during PRACH. After LBT is executed at the physical layer in the terminal device, the higher layers in the terminal device can receive the execution result of LBT.

[0164] S605: In the event that LBT execution fails, execute the LBT failure handling procedure.

[0165] LBT execution failure refers to a situation where the channel is busy, which may cause transmission failure when sending the random access preamble on PRACH.

[0166] The LBT failure handling process refers to the failure handling strategy for the process of transmitting the random access preamble in PRACH after the channel fails to execute LBT. The LBT failure handling process may include, for example, the execution of the random access resource selection process, or any other possible failure handling strategy, without limitation.

[0167] In this embodiment of the disclosure, when the terminal device is configured to recover from LBT failure, and after LBT is executed when the random access preamble is sent on the PRACH, the execution result of LBT can be obtained. The LBT execution result can be success or failure. Successful LBT execution means that the channel state is idle, which can trigger the transmission of the random access preamble on the PRACH. Failed LBT execution means that the channel state is busy, which indicates that if the random access preamble is sent on the PRACH, it may lead to transmission failure.

[0168] In this embodiment of the disclosure, if an indication of LBT execution failure is received, it indicates that LBT execution has failed, and the LBT failure handling process can be executed, including the random access resource selection process. The execution of the random access resource selection process can meet certain execution conditions, including receiving an LBT failure indication reported by the physical layer in the terminal device (the LBT failure indication is used to indicate LBT execution failure), not being configured to exempt the listen-before-tell LBT during the transmission of the random access preamble in PRACH, and having configured LBT failure recovery. If the execution conditions of the random access resource selection process are met, the random access resource selection process can be executed, and the random access preamble in PRACH can be sent again.

[0169] In this embodiment, by receiving an indication message from the base station to configure the Random Access Channel (RACH), it is determined whether an exemption from LBT is configured during the transmission of the random access preamble in the PRACH. This method effectively improves the accuracy and timeliness of determining whether an LBT exemption is configured, allowing for timely triggering of subsequent processing logic based on the indication message. This effectively avoids link anomalies. Furthermore, in the case of a failed LBT configuration recovery after the terminal device is configured to listen before speaking, LBT is executed during the transmission of the random access preamble in the PRACH. If LBT execution fails, a failure handling process is implemented. This method ensures that an exemption from listening before speaking is configured during the transmission of the random access preamble in the PRACH. When discussing LBT (Local Bit-Based Access) failure handling, effectively implementing LBT failure processing can effectively avoid link anomalies, thereby effectively maintaining link stability. By determining the geographical location of the terminal device, if the geographical location belongs to the target location area, it is determined whether LBT exemption is configured during the PRACH random access preamble transmission process. Here, the target location area is the location area where LBT exemption is configured during the PRACH random access preamble transmission process. If the geographical location does not belong to the target location area, it is determined that LBT exemption is not configured during the PRACH random access preamble transmission process. Thus, it is possible for the terminal device to determine whether LBT exemption is configured during the PRACH random access preamble transmission process by combining its own geographical location, enabling flexible determination of whether LBT exemption is configured during the PRACH random access preamble transmission process.

[0170] Figure 7 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0171] like Figure 7 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0172] S701: When LBT exemption is configured during the transmission of the random access preamble in PRACH and the reference configuration information is the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the last transmission of the random access preamble in PRACH on the terminal device.

[0173] The first power ramp count value refers to the power count value when the terminal device sends PRACH. Under the same conditions, the larger the value of the first power ramp count value, the greater the power of the terminal device when sending PRACH, and the smaller the value of the first power ramp count value, the smaller the power of the transmission.

[0174] The power ramp count value related to the last time the terminal device sent a random access preamble in PRACH refers to the power ramp count value related to the last time the random access preamble was sent in PRACH, corresponding to the current process of sending a random access preamble in PRACH.

[0175] The second power ramp count value refers to the power ramp count value related to the last time the terminal device sends the random access preamble in PRACH.

[0176] The reference configuration information refers to the terminal equipment configuration information used to determine the first power ramp-up count value.

[0177] The target configuration information refers to the judgment condition used to determine whether to increment the second power ramp count value. When the reference configuration information is the target configuration information, the second power ramp count value can be incremented to obtain the first power ramp count value.

[0178] In this embodiment of the disclosure, if an exemption from LBT is configured during the PRACH transmission of the random access preamble, a comparison process can be performed in the target configuration information based on the reference configuration information. If the reference configuration information is the target configuration information, an increment step size can be set, and the second power ramp-up count value can be incremented according to the increment step size. The incremented second power ramp-up count value is then used as the first power ramp-up count value. The increment step size can be set to 1, or any other reasonable value can be set as the increment step size, without any limitation.

[0179] Optionally, in some embodiments, the target configuration information includes any one of the following: being configured to be exempt from LBT during the last transmission of the random access preamble in PRACH, or not receiving an LBT failure indication during the last transmission of the random access preamble in PRACH. This allows the reference configuration information to be verified based on the target configuration information, thereby determining the first power ramp-up count value based on the target configuration information and the reference configuration information. This enables adaptive configuration of the power count value of the terminal device when transmitting the random access preamble in PRACH.

[0180] In this embodiment of the disclosure, a judgment condition can be preset as target configuration information. The target configuration information may include: being configured to be exempt from LBT during the last PRACH random access preamble transmission process, or not receiving an LBT failure indication during the last PRACH random access preamble transmission process. If the reference configuration information is any of the target configuration information, the second power ramp count value is incremented, and the incremented second power ramp count value is used as the first power ramp count value.

[0181] In this embodiment of the disclosure, the target configuration information can be used to compare the reference configuration information. If the target configuration information does not include any of the following: being configured to exempt LBT during the PRACH random access preamble transmission process, being configured to exempt LBT during the previous PRACH random access preamble transmission process, or not receiving an LBT failure indication during the previous PRACH random access preamble transmission process, then there is no need to increment the second power ramp count value, and the second power ramp count value without increment processing is used as the first power ramp count value.

[0182] S702: If LBT exemption is configured during the transmission of the random access preamble in PRACH, and the reference configuration information is not the target configuration information, then the second power ramp count value is used as the first power ramp count value.

[0183] In this embodiment of the disclosure, if an exemption from LBT is configured during the PRACH transmission of the random access preamble, a comparison process can be performed between the reference configuration information and the target configuration information. If the reference configuration information is not the target configuration information, the second power ramp-up count value is not incremented, and the second power ramp-up count value is used as the first power ramp-up count value.

[0184] S703: Determine the indication parameters based on the first power ramp-up count value.

[0185] Among them, the indication parameter refers to the relevant power parameters when the terminal device sends PRACH, which is used to characterize the power level when the terminal device sends PRACH.

[0186] In this embodiment of the disclosure, if an exemption from LBT is configured during the transmission of the random access preamble in PRACH, an indication parameter is determined based on the first power ramp-up count value. A judgment condition can be preset. When the judgment condition is met, the power ramp-up count value of the last PRACH transmission on the terminal device is incremented to obtain the incremented power ramp-up count value as the first power ramp-up count value. Then, the relevant power parameters of the terminal device when transmitting PRACH can be determined based on the first power ramp-up count value, and the obtained relevant power parameters of the terminal device when transmitting PRACH are used as the indication parameter. The increment step size during the increment processing can be 1, or it can be set to an increment step size of other values ​​for increment processing, without limitation.

[0187] In this embodiment of the disclosure, after determining the first power ramp-up count value as described above, the indication parameter can be determined based on the first power ramp-up count value.

[0188] In this embodiment, by configuring an exemption from LBT during the PRACH transmission of the random access preamble, and the reference configuration information being the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the last PRACH transmission of the random access preamble on the terminal device. Based on the first power ramp count value, an indication parameter is determined. Thus, the indication parameter can be determined based on the reference configuration information and the target configuration information. Since the indication parameter is used to indicate the relevant power when transmitting the random access preamble in the PRACH, adaptive configuration of the relevant power can be achieved, effectively ensuring the execution effect of the PRACH transmission of the random access preamble.

[0189] S704: Send a random access preamble on PRACH according to the indicated parameters.

[0190] In this embodiment of the disclosure, after determining the indication parameters based on the first power ramp-up count value, a random access preamble can be sent on the PRACH according to the indication parameters.

[0191] In this embodiment of the disclosure, when sending a random access preamble on PRACH according to the indication parameters, the random access preamble can be sent on PRACH according to the power of the terminal device when sending PRACH as indicated by the indication parameters.

[0192] In this embodiment of the disclosure, if LBT exemption is configured during the PRACH transmission of the random access preamble, the transmission of the random access preamble is completed with reference to the indication parameters, and the execution result of LBT can be disregarded.

[0193] S705: Execute LBT.

[0194] In this embodiment of the disclosure, if LBT exemption is configured during the PRACH transmission of the random access preamble, LBT can be performed by the physical layer in the terminal device. In this case, the transmission of the random access preamble is completed with reference to the indication parameters when the PRACH transmits the random access preamble, and the execution result of LBT can be ignored. The execution result of LBT is used to trigger the failure handling process of LBT. If LBT exemption is configured during the PRACH transmission of the random access preamble, and the reference configuration information is not the target configuration information, then the second power ramp-up count value is used as the first power ramp-up count value.

[0195] S706: In the event that LBT execution fails, execute the LBT failure handling procedure.

[0196] In this embodiment of the present disclosure, after the physical layer in the terminal device performs LBT as described above, the execution result of LBT can be obtained and reported to the higher layer of the terminal device. If LBT execution fails, the failure execution result of LBT is uploaded to the higher layer of the terminal device, and the higher layer in the terminal device performs the failure handling process of LBT.

[0197] In this embodiment of the disclosure, since LBT is exempted during the PRACH transmission of the random access preamble, the execution result of LBT is only used to trigger the failure handling process of LBT, and the execution result of LBT may not be used as a reference during the PRACH transmission of the random access preamble.

[0198] In this embodiment, when the terminal device is configured to recover from a LBT failure, LBT is executed when the PRACH sends the random access preamble. If LBT execution fails, LBT failure handling is performed. This effectively prevents link anomalies and maintains link stability when the terminal device is configured to be exempt from LBT during the PRACH random access preamble transmission process. The reference configuration information is verified based on the target configuration information to determine the first power ramp-up count value, enabling adaptive configuration of the power count value of the terminal device when sending the random access preamble in the PRACH.

[0199] Figure 8 This is a flowchart illustrating a method for transmitting a Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0200] like Figure 8 As shown, the method for transmitting the Physical Random Access Channel (PRACH) includes:

[0201] S801: When the PRACH is configured to be exempt from LBT during the transmission of the random access preamble, the power parameters for transmitting the PRACH are determined based on the first power ramp-up count value.

[0202] In this embodiment of the disclosure, after incrementing the second power ramp count value to obtain the first power ramp count value, or after using the second power ramp count value as the first power ramp count value, the power parameters for transmitting PRACH can be determined based on the first power ramp count value.

[0203] S802: Use the power parameters for transmitting PRACH as indication parameters.

[0204] In this embodiment of the present disclosure, after determining the power parameters for transmitting PRACH based on the first power ramp-up count value, the power parameters for transmitting PRACH can be used as indication parameters.

[0205] In this embodiment of the disclosure, after using the power parameters for transmitting PRACH as indication parameters, a random access preamble can be transmitted in PRACH according to the indication parameters.

[0206] In this embodiment, when LBT exemption is configured during the PRACH transmission of the random access preamble, the power parameters for transmitting the PRACH are determined based on the first power ramp-up count value. The power parameters for transmitting the PRACH are used as indication parameters. Thus, the power parameters for transmitting the PRACH can be determined based on the first power ramp-up count value, thereby enabling the acquisition of the transmission power when transmitting the random access preamble in the PRACH and ensuring the effective execution of the PRACH transmission of the random access preamble process.

[0207] S803: If an exemption from LBT is configured during the transmission of the random access preamble in PRACH, the random access preamble is transmitted in PRACH according to the indication parameters.

[0208] In this embodiment of the disclosure, after using the power parameter for transmitting PRACH as an indication parameter, if LBT exemption is configured during the transmission of the random access preamble in PRACH, the random access preamble can be transmitted in PRACH according to the indication parameter. This enables the transmission of the random access preamble in PRACH based on the power parameter corresponding to the indication parameter. In this case, the process of transmitting the random access preamble in PRACH can refer to the indication parameter instead of the execution result of LBT, thereby effectively ensuring that when LBT exemption is configured during the transmission of the random access preamble in PRACH, the process can be executed effectively and in a timely manner, and has a more reliable execution effect.

[0209] S804: Execute LBT.

[0210] In this embodiment of the disclosure, if LBT exemption is configured during the PRACH transmission of the random access preamble, then LBT is performed in the physical layer of the terminal device.

[0211] S805: In the event that LBT execution fails, execute the LBT failure handling procedure.

[0212] In this embodiment of the present disclosure, after the physical layer in the terminal device performs LBT as described above, the execution result of LBT can be obtained and reported to the higher layer of the terminal device. If LBT execution fails, the failure execution result of LBT is uploaded to the higher layer of the terminal device, and the higher layer in the terminal device performs the failure handling process of LBT.

[0213] In this embodiment, by configuring the terminal device to recover from LBT failure (Listen-After-Speak) failure, LBT is executed when the PRACH transmits the random access preamble. If LBT execution fails, the LBT failure handling process is executed. This effectively prevents link anomalies and maintains link stability when LBT exemption is configured during PRACH transmission of the random access preamble. Furthermore, by determining the PRACH transmission power parameters based on the first power ramp-up count value when LBT exemption is configured during PRACH transmission of the random access preamble, the PRACH transmission power parameters are used as indication parameters. This allows for the acquisition of transmission power during PRACH transmission of the random access preamble, ensuring the effective execution of the PRACH transmission process. It can also send a random access preamble on PRACH according to the power parameters corresponding to the indication parameters. In this case, the process of sending the random access preamble on PRACH can refer to the indication parameters instead of the execution result of LBT. This effectively ensures that when LBT exemption is configured during the process of sending the random access preamble on PRACH, the process can be executed effectively and in a timely manner, and has a more reliable execution effect.

[0214] Figure 9 This is a schematic diagram of the apparatus structure for transmitting the Physical Random Access Channel (PRACH) according to an embodiment of this disclosure.

[0215] like Figure 9 As shown, the apparatus 80 for transmitting the Physical Random Access Channel (PRACH) includes:

[0216] The first execution unit 901 is used to execute LBT when PRACH sends a random access preamble if the terminal device fails to recover its configuration after being configured to listen before speaking (LBT).

[0217] The second execution unit 902 is used to execute the failure handling process of LBT in the event that LBT execution fails.

[0218] In some embodiments of this disclosure, such as Figure 10 As shown, Figure 10 This is a schematic diagram of an apparatus for transmitting the Physical Random Access Channel (PRACH) according to another embodiment of this disclosure, which also includes:

[0219] The first transmitting unit 903 is configured to transmit a random access preamble in the PRACH according to an indication parameter when it is configured to be exempt from LBT during the transmission of the random access preamble in the PRACH process.

[0220] In some embodiments of this disclosure, it also includes:

[0221] The second transmitting unit 904 is used to transmit the random access preamble in the PRACH if it is not configured to be exempt from LBT during the transmission of the random access preamble in the PRACH process and the LBT is successfully executed.

[0222] In some embodiments of this disclosure, it also includes:

[0223] The first determining unit 905 is used to determine the indication parameters based on the first power ramp-up count value when the LBT exemption is configured during the PRACH transmission of the random access preamble.

[0224] If the reference configuration information is the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the last time the terminal device sends the random access preamble in PRACH.

[0225] In some embodiments of this disclosure, it also includes:

[0226] The processing unit 906 is used to use the second power ramp count value as the first power ramp count value when the reference configuration information is not the target configuration information.

[0227] In some embodiments of this disclosure, the target configuration information includes any of the following:

[0228] The last time the random access preamble was sent during PRACH, an exemption from LBT was configured.

[0229] During the last transmission of the random access preamble in PRACH, no LBT failure indication was received.

[0230] In some embodiments of this disclosure, the first determining unit 905 is specifically used for:

[0231] Based on the first power ramp-up count value, determine the power parameters for transmitting PRACH;

[0232] The power parameters for sending PRACH are used as indication parameters.

[0233] In some embodiments of this disclosure, it also includes:

[0234] The third execution unit 907 is used to execute the random access resource selection process upon receiving an LBT failure indication.

[0235] In some embodiments of this disclosure, it also includes:

[0236] The receiving unit 908 is used to receive an indication message sent by the base station to configure the random access channel RACH or a system broadcast;

[0237] The second determining unit 909 is used to determine, based on the indication message, whether an exemption from LBT is configured during the PRACH transmission of the random access preamble.

[0238] In some embodiments of this disclosure, it also includes:

[0239] The third determining unit 910 is used to determine, based on the indication message, whether the cell accessed by the terminal device is configured to be exempt from LBT; or,

[0240] The fourth determining unit 911 is used to determine, in the absence of receiving an indication message, that the cell accessed by the terminal device is configured to be exempt from LBT.

[0241] In some embodiments of this disclosure, it also includes:

[0242] The fifth determining unit 912 is used to determine the geographical location of the terminal device;

[0243] The sixth determining unit 913 is used to determine, when the geographical location belongs to the target location area, the location area that is configured to be exempt from LBT during the PRACH transmission of the random access preamble, wherein the target location area is the location area that is exempt from LBT during the PRACH transmission of the random access preamble.

[0244] The seventh determining unit 914 is used to determine that no exemption LBT was configured during the PRACH transmission of the random access preamble when the geographical location is not within the target location area.

[0245] In some embodiments of this disclosure, the first execution unit 901 is specifically used for:

[0246] Determine the LBT configuration information, wherein the LBT configuration information is determined by the base station or by the terminal device;

[0247] Execute LBT according to the LBT configuration information.

[0248] In some embodiments of this disclosure, the LBT configuration information includes: LBT type, and / or, LBT beam direction.

[0249] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0250] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium.

[0251] Based on this understanding, the technical solutions disclosed herein, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0252] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0253] In this embodiment, by performing LBT when the terminal device is configured to be exempt from LBT during PRACH transmission of the random access preamble, and performing LBT failure handling when LBT execution fails, the LBT failure handling is effectively executed when the terminal device is configured to be exempt from LBT during PRACH transmission of the random access preamble. This effectively avoids link anomalies and thus effectively maintains link stability.

[0254] Figure 11 This is a schematic diagram of the structure of an apparatus for transmitting the Physical Random Access Channel (PRACH) according to another embodiment of this disclosure.

[0255] See Figure 11The apparatus 110 for transmitting the Physical Random Access Channel (PRACH) includes a memory 1101, a transceiver 1102, a processor 1103, and a user interface 1104: the memory 1101 is used to store computer programs; the transceiver 1102 is used to transmit and receive data under the control of the processor 1103; the processor 1103 is used to read the computer program in the memory 1101 and perform the following operations:

[0256] If the terminal device is configured to listen before speaking (LBT) and the configuration fails to recover, LBT will be executed when the PRACH sends the random access preamble.

[0257] In the event that LBT execution fails, the LBT failure handling procedure is executed.

[0258] Among them, Figure 11 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1103 and memory represented by memory 1101 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1102 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1104 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0259] The processor 1103 is responsible for managing the bus architecture and general processing, while the memory 1101 can store the data used by the processor 1103 when performing operations.

[0260] Optionally, the processor 1103 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0261] The processor executes any of the methods provided in the embodiments of this disclosure by invoking a computer program stored in memory, according to the obtained executable instructions. The processor and memory may also be physically separated.

[0262] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0263] If an exemption from LBT is configured during the transmission of the random access preamble in PRACH, the random access preamble is transmitted in PRACH according to the indication parameters.

[0264] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0265] If the random access preamble is not configured to be exempt from LBT during the PRACH transmission process, and the LBT is executed successfully, the random access preamble is transmitted in the PRACH.

[0266] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0267] In the case where LBT exemption is configured during the transmission of the random access preamble in PRACH, the indication parameters are determined based on the first power ramp-up count value;

[0268] If the reference configuration information is the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the last time the terminal device sends the random access preamble in PRACH.

[0269] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0270] If the reference configuration information is not the target configuration information, the second power ramp count value will be used as the first power ramp count value.

[0271] In some embodiments of this disclosure, the target configuration information includes any of the following:

[0272] The last time the random access preamble was sent during PRACH, an exemption from LBT was configured.

[0273] During the last transmission of the random access preamble in PRACH, no LBT failure indication was received.

[0274] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0275] Based on the first power ramp-up count value, determine the power parameters for transmitting PRACH;

[0276] The power parameters for sending PRACH are used as indication parameters.

[0277] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0278] Upon receiving an LBT failure indication, a random access resource selection procedure is executed.

[0279] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0280] Receive indication messages sent by the base station to configure the Random Access Channel (RACH) or broadcast by the system;

[0281] Based on the instruction message, determine whether an exemption from LBT is configured during the PRACH transmission of the random access preamble.

[0282] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0283] Based on the instruction message, determine whether the cell accessed by the terminal device is configured to be exempt from LBT; or,

[0284] If no instruction message is received, it is determined that the cell accessed by the terminal device is configured to be exempt from LBT.

[0285] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0286] Determine the geographical location of the terminal device;

[0287] If the geographical location falls within the target location area, it is determined that an LBT exemption is configured during the PRACH random access preamble transmission process, where the target location area is the location area exempt from LBT during the PRACH random access preamble transmission process; or...

[0288] If the geographical location is not within the target location area, it is determined that the exemption LBT was not configured during the PRACH transmission of the random access preamble.

[0289] In some embodiments of this disclosure, processor 1103 is specifically used for:

[0290] Determine the LBT configuration information, wherein the LBT configuration information is determined by the base station or by the terminal device;

[0291] Execute LBT according to the LBT configuration information.

[0292] In some embodiments of this disclosure, the LBT configuration information includes: LBT type, and / or, LBT beam direction.

[0293] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0294] To implement the above embodiments, this disclosure provides a processor-readable storage medium storing a computer program for causing the processor to execute a method for transmitting a Physical Random Access Channel (PRACH).

[0295] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0296] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0297] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0298] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0299] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

[0300] It should be noted that in the description of this disclosure, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this disclosure, unless otherwise stated, "a plurality of" means two or more.

[0301] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of preferred embodiments of this disclosure includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the function involved, as will be understood by those skilled in the art to which embodiments of this disclosure pertain.

[0302] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0303] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0304] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0305] The storage media mentioned above can be read-only memory, disk, or optical disk, etc.

[0306] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0307] Although embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A method for transmitting a Physical Random Access Channel (PRACH), characterized in that, The method includes: If the terminal device is configured to fail and recover from the LBT failure, the LBT is executed when the PRACH sends the random access preamble. If the execution of the LBT fails, the failure handling procedure of the LBT shall be executed. If the LBT is configured to be waived during the transmission of the random access preamble in the PRACH, the random access preamble is transmitted in the PRACH according to the indication parameter; or, if the LBT is not configured to be waived during the transmission of the random access preamble in the PRACH, and the LBT is executed successfully, the random access preamble is transmitted in the PRACH. Determine the geographical location of the terminal device; If the geographical location belongs to the target location area, it is determined that the LBT is configured to be exempted during the PRACH transmission of the random access preamble, wherein the target location area is the location area where the LBT is exempted during the PRACH transmission of the random access preamble; or, if the geographical location does not belong to the target location area, it is determined that the LBT is not configured to be exempted during the PRACH transmission of the random access preamble.

2. The method as described in claim 1, characterized in that, include: If the LBT is configured to be exempted during the transmission of the random access preamble by the PRACH, the indication parameter is determined based on the first power ramp-up count value; If the reference configuration information is the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the random access preamble sent by the terminal device in the PRACH last time.

3. The method as described in claim 2, characterized in that, include: If the reference configuration information is not the target configuration information, then the second power ramp count value is used as the first power ramp count value.

4. The method as described in claim 3, characterized in that, The target configuration information includes any one of the following: The LBT was previously configured to be exempted during the transmission of the random access preamble in the PRACH; During the previous transmission of the random access preamble in the PRACH, no LBT failure indication was received.

5. The method as described in claim 2, characterized in that, Determining the indication parameter based on the first power ramp count value includes: Based on the first power ramp count value, determine the power parameters for transmitting the PRACH; The power parameters for transmitting the PRACH are used as the indication parameters.

6. The method as described in claim 1, characterized in that, include: Upon receiving an LBT failure indication, a random access resource selection procedure is executed.

7. The method as described in claim 1, characterized in that, include: Receive indication messages sent by the base station to configure the Random Access Channel (RACH) or broadcast by the system; Based on the instruction message, determine whether the LBT is configured to be exempted during the PRACH transmission of the random access preamble.

8. The method as described in claim 7, characterized in that, include: Based on the instruction message, determine whether the cell accessed by the terminal device is configured to exempt the LBT; or, If the instruction message is not received, it is determined that the cell accessed by the terminal device is configured to exempt the LBT.

9. The method as described in claim 1, characterized in that, The execution of the LBT includes: Determine LBT configuration information, wherein the LBT configuration information is determined by the base station or by the terminal device; The LBT is executed according to the LBT configuration information.

10. The method as described in claim 9, characterized in that, The LBT configuration information includes: LBT type, and / or, LBT beam direction.

11. An apparatus for transmitting a Physical Random Access Channel (PRACH), comprising: The first execution unit is configured to execute the LBT when the PRACH sends the random access preamble if the terminal device is configured to fail to recover from the LBT failure. The second execution unit is used to execute the failure handling process of the LBT in the event that the LBT fails to execute; The device further includes: A first transmitting unit is configured to transmit the random access preamble in the PRACH according to an indication parameter if the LBT is exempted during the transmission of the random access preamble in the PRACH process; or, a second transmitting unit is configured to transmit the random access preamble in the PRACH if the LBT is not exempted during the transmission of the random access preamble in the PRACH process and the LBT is successfully executed. The fifth determining unit is used to determine the geographical location of the terminal device; The sixth determining unit is configured to determine, if the geographical location belongs to the target location area, that the LBT is configured to be exempted during the PRACH transmission of the random access preamble, wherein the target location area is the location area where the LBT is exempted during the PRACH transmission of the random access preamble; or, the seventh determining unit is configured to determine, if the geographical location does not belong to the target location area, that the LBT is not configured to be exempted during the PRACH transmission of the random access preamble.

12. The apparatus as claimed in claim 11, characterized in that, Also includes: The first determining unit is configured to determine the indication parameter based on the first power ramp-up count value when the LBT is exempted during the PRACH transmission of the random access preamble. If the reference configuration information is the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the last time the terminal device sends the random access preamble on the PRACH.

13. The apparatus as claimed in claim 12, characterized in that, Also includes: The processing unit is configured to use the second power ramp count value as the first power ramp count value when the reference configuration information is not the target configuration information.

14. The apparatus as claimed in claim 13, characterized in that, The target configuration information includes any one of the following: The LBT was previously configured to be exempted during the transmission of the random access preamble in the PRACH; During the previous transmission of the random access preamble in the PRACH, no LBT failure indication was received.

15. The apparatus as claimed in claim 12, characterized in that, The first determining unit is specifically used for: Based on the first power ramp count value, determine the power parameters for transmitting the PRACH; The power parameters for transmitting the PRACH are used as the indication parameters.

16. The apparatus as claimed in claim 11, characterized in that, Also includes: The third execution unit is used to perform the random access resource selection process upon receiving an LBT failure indication.

17. The apparatus as claimed in claim 11, characterized in that, Also includes: The receiving unit is used to receive indication messages sent by the base station for configuring the random access channel (RACH) or system broadcasts; The second determining unit is configured to determine, based on the indication message, whether the LBT is exempted during the PRACH transmission of the random access preamble.

18. The apparatus as claimed in claim 17, characterized in that, Also includes: The third determining unit is used to determine, based on the indication message, whether the cell accessed by the terminal device is configured to exempt the LBT; or, The fourth determining unit is configured to determine, in the absence of receiving the indication message, that the cell accessed by the terminal device is configured to exempt the LBT.

19. The apparatus as claimed in claim 11, characterized in that, The first execution unit is specifically used for: Determine LBT configuration information, wherein the LBT configuration information is determined by the base station or by the terminal device; The LBT is executed according to the LBT configuration information.

20. The apparatus as claimed in claim 19, characterized in that, The LBT configuration information includes: LBT type, and / or, LBT beam direction.

21. An apparatus for transmitting a Physical Random Access Channel (PRACH), characterized in that, Includes a memory, a transceiver, and a processor: the memory stores computer programs; the transceiver sends and receives data under the control of the processor; the processor reads the computer programs from the memory and performs the following operations: If the terminal device is configured to fail and recover from the LBT failure, the LBT is executed when the PRACH sends the random access preamble. If the execution of the LBT fails, the failure handling procedure of the LBT shall be executed. The processor is specifically used for: If the LBT is configured to be waived during the transmission of the random access preamble in the PRACH, the random access preamble is transmitted in the PRACH according to the indication parameter; or, if the LBT is not configured to be waived during the transmission of the random access preamble in the PRACH, and the LBT is executed successfully, the random access preamble is transmitted in the PRACH. Determine the geographical location of the terminal device; If the geographical location belongs to the target location area, it is determined that the LBT is configured to be exempted during the PRACH transmission of the random access preamble, wherein the target location area is the location area exempted from the LBT during the PRACH transmission of the random access preamble; Alternatively, if the geographical location does not belong to the target location area, it is determined that the exemption of the LBT was not configured during the transmission of the random access preamble by the PRACH.

22. The apparatus as claimed in claim 21, characterized in that, The processor is specifically used for: If the LBT is configured to be exempted during the transmission of the random access preamble by the PRACH, the indication parameter is determined based on the first power ramp-up count value; If the reference configuration information is the target configuration information, the second power ramp count value is incremented to obtain the first power ramp count value. The second power ramp count value is the power ramp count value related to the random access preamble sent by the terminal device in the PRACH last time.

23. The apparatus as claimed in claim 22, characterized in that, The processor is specifically used for: If the reference configuration information is not the target configuration information, then the second power ramp count value is used as the first power ramp count value.

24. The apparatus as claimed in claim 23, characterized in that, The target configuration information includes any one of the following: The LBT was previously configured to be exempted during the transmission of the random access preamble in the PRACH; During the previous transmission of the random access preamble in the PRACH, no LBT failure indication was received.

25. The apparatus as claimed in claim 22, characterized in that, The processor is specifically used for: Based on the first power ramp count value, determine the power parameters for transmitting the PRACH; The power parameters for transmitting the PRACH are used as the indication parameters.

26. The apparatus as claimed in claim 21, characterized in that, The processor is specifically used for: Upon receiving an LBT failure indication, a random access resource selection procedure is executed.

27. The apparatus as claimed in claim 21, characterized in that, The processor is specifically used for: Receive indication messages sent by the base station to configure the Random Access Channel (RACH) or broadcast by the system; Based on the instruction message, determine whether the LBT is configured to be exempted during the PRACH transmission of the random access preamble.

28. The apparatus as claimed in claim 27, characterized in that, The processor is specifically used for: Based on the instruction message, determine whether the cell accessed by the terminal device is configured to exempt the LBT; or, If the instruction message is not received, it is determined that the cell accessed by the terminal device is configured to exempt the LBT.

29. The apparatus as claimed in claim 21, characterized in that, The processor is specifically used for: Determine LBT configuration information, wherein the LBT configuration information is determined by the base station or by the terminal device; The LBT is executed according to the LBT configuration information.

30. The apparatus as claimed in claim 29, characterized in that, The LBT configuration information includes: LBT type, and / or, LBT beam direction.

31. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to perform the method according to any one of claims 1 to 10.