Patent Description:
Unlicensed Spectrum is an important technology in the <NUM> New Radio (NR) Access system. In general, the center frequency point of the working frequency band of NR-based access to unlicensed spectrum (NR-U) may be <NUM> and <NUM>. In unlicensed spectrum, NR-U should be designed to ensure fairness with other systems already operating on such unlicensed spectrum. The principle of fairness is the impact of NR-U on systems already deployed on unlicensed spectrum (e.g., WiFi) may not exceed the impact between these systems. To ensure fair coexistence among systems on unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. The general energy detection mechanism is the Listen Before Talk (LBT) mechanism, and the basic principle of this mechanism is that the base station or terminal (transmitter) needs to monitor for a specified period of time before transmitting data on the unlicensed spectrum. If the monitoring result indicates that the channel is idle, the transmitter may transmit data to the receiver. If the monitoring result indicates that the channel is in an occupied state, the transmitter needs to fall back for a period of time according to the regulations and continues to monitor the channel, and the transmitter transmits data to the receiver until the channel monitoring result is idle state.

In the random access procedure of the NR-U system, for a four-step random access procedure, the terminal and the base station need to send a total of four messages to complete the random access procedure. For a two-step random access procedure, the terminal and the base station need to send a total of two messages to complete the random access procedure. Among them, message A (MsgA) includes a random access preamble sent on a physical random access channel (PRACH) and payload information sent on a physical uplink shared channel (PUSCH). Whether it is the four-step random access or the two-step random access, before sending a message each time, the terminal and the base station need to perform LBT detection to determine whether the channel is occupied; if the LBT detection result is negative, it will cause the terminal to fail to complete random access and the terminal needs to resend Msg1/MsgA. In the existing random access technology, because the terminal device does not report to the network device whether LBT failure is detected, the network device cannot adjust the resource configuration of random access accordingly. <CIT>, discloses a method, a computer-readable medium, and an apparatus. The apparatus may be configured to determine to send a transmission to a first base station on a first unlicensed frequency channel of an unlicensed frequency spectrum. The apparatus may be configured to determine, for one or more attempts of a listen before talk (LBT) protocol, whether each attempt is a failed attempt or a successful attempt. The apparatus may be configured to determine that the first unlicensed frequency channel is one of: unavailable based on the LBT protocol failing due to at least one of a number of failed attempts exceeding a first threshold number of failed attempts or a duration of failed attempts exceeding a first threshold duration, or available based on at least one attempt of the LBT protocol being successful for the transmission. The apparatus may be configured to send a report to the first base station indicating whether the first unlicensed frequency channel is unavailable or available through a unicast radio resource control (RRC) message or a medium access control (MAC) control element (CE).

The present application provides a method for reporting a situation of random access, a method for receiving and applying a situation of a random access, a terminal device and a network device, which can realize reporting to the network the situation of the random access that has been performed by the terminal before.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be noted that the terms "first" and "second" and the like in the description of the embodiments of the present application, claims and the above drawings are used to distinguish similar objects, and not necessarily used to describe a specific order or sequence order. The objects described by "first" and "second" described at the same time may be the same or different.

The technical solutions of the embodiments of the present application may be applied to various communication systems, for example: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system, New Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation (5th-Generation, <NUM>) communications or other communication systems, etc..

Generally speaking, the number of connections supported by conventional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support conventional communication, but also support, for example, Device to Device (D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), and Vehicle to Vehicle (V2V) communication, etc. The embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiments of the present application may be applied to a Carrier Aggregation (CA) scenario, a Dual Connectivity (DC) scenario, and may also be applied to a Standalone (SA) network deployment scenario.

The embodiments of the present application do not limit the applied frequency spectrum. For example, the embodiments of the present application may be applied to the licensed spectrum, and may also be applied to the unlicensed spectrum.

Embodiments of the present application describe various embodiments in conjunction with a network device and a terminal device, where the terminal device may also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus, etc. The terminal device may be a station (ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in next generation communication systems, such as a terminal device in NR networks or a terminal device in future evolved Public Land Mobile Network (PLMN), etc..

As an example but not a limitation, in the embodiments of the present application, the terminal device may also be a wearable device. The wearable device may also be referred to as a wearable smart device, which is a general term for wearable devices which are intelligently designed and developed for daily wear applying wearable technology, such as glasses, gloves, watches, clothing and shoes. The wearable device is a portable device that is worn directly on the body, or integrated into the user's clothing or accessories. The wearable device is not only a hardware device, but also achieves powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured and large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and devices that need to be used in conjunction with other devices (e.g., smartphones) and focus only on a certain type of application function, such as various types of smart bracelets and smart jewelry for physical sign monitoring.

The network device may be a device used to communicate with mobile devices, and the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, or a base station (NodeB, NB) in WCDMA, and may be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an access point, or a vehicle-mounted device, a wearable device, and may be a network device (gNB) in the NR network or a network device in the future evolved PLMN network, etc..

In the embodiments of the present application, the network device provides services for the cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to the network device (such as a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell, where the small cell may include: a Metro cell, a Micro cell, a Pico cell, a Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

<FIG> exemplarily illustrates one network device <NUM> and two terminal devices <NUM>. Optionally, the wireless communication system <NUM> may include a plurality of network devices <NUM>, and other numbers of terminal devices <NUM> may be included within the coverage area of each network device <NUM>, which is not limited in the embodiments of the present application. The embodiments of the present application may be applied to one terminal device <NUM> and one network device <NUM>, and may also be applied to one terminal device <NUM> and another terminal device <NUM>.

Optionally, the wireless communication system <NUM> may also include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), which is not limited by the embodiments of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this disclosure is just an association relationship describing associated objects, which means that there can be three relationships. For example, A and/or B may indicate that A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this disclosure generally indicates that the contextual objects are in an "or" relationship.

The embodiments of the present application provide a method for reporting a situation of a random access, and <FIG> is a flow chart of implementing a method <NUM> for reporting the situation of the random access according to the embodiments of the present application. The method may optionally be applied to the system shown in <FIG>, but is not limited thereto. The method includes at least some of the following contents.

In S210: a situation of a random access that has been performed by the terminal device is sent to a network device, where the situation of the random access includes information related to a result of a listen before talk (LBT) detection of the terminal device in a random access attempt.

Optionally, the terminal device sends the situation of the random access in a random access report.

The random access report (RACH report) is a message sent by the terminal device to the network device proposed by the <NUM> NR R16 Self-Organizing Network (SON) technology. In response to the request of the network device, the terminal device sends the random access report to the network device, and the network device may optimize the parameters set by the network itself according to the report reported by the terminal device. In the embodiments of the present application, the terminal device may carry the situation of the random access that needs to be reported in the random access report, and report it to the network device.

For the four-step random access procedure and the two-step random access procedure, the manners for the terminal device to report the situation of the random access are different, which are described respectively below.

For the first category, reporting the situation of the random access (such as LBT detection results) in the four-step random access procedure:.

The four-step random access procedure is shown in <FIG>, including: the terminal device sending Msg1 to the network device, where a random access preamble is carried in the Msg <NUM>; the network device replying a random access response, i.e., Msg2, to the terminal device, where the Msg2 contains an uplink grant (UL grant) for a sending opportunity of Msg3; and the terminal device sending an RRC signaling carrying UE ID, i.e., Msg3, to the network device, where the Msg <NUM> is sent in the UL grant allocated by the network device. After the terminal device sends the Msg3, the contention resolution timer is started, and the random access process is completed if the terminal receives a Msg4 from the network device before the timer expires.

In the embodiments of the present application, for the four-step random access procedure, the terminal device reports to the network device whether an LBT failure is detected during the sending procedure of Msg1 and/or Msg3. The network device adjusts the resource configuration according to the detection result reported by the terminal device. The specific scheme is as follows:.

The terminal device sends at least one of the following to the network device:.

Optionally, the terminal device further sends at least one of the following to the network device:.

For example, the terminal device reports at least one of the following:.

In addition, the terminal device may also report in the random access report a measurement result of the terminal device related to a channel occupancy of a cell where the random access is located, measResultForRSSI.

Optionally, the measResultForRSSI is included in a random access report.

Optionally, the measResultForRSSI is included in a random access report under each Synchronization Signal Block (SSB).

Optionally, the measResultForRSSI is included in a random access report under each Channel Status Indicator Reference Signal (CSI-RS).

Optionally, the measResultForRSSI is included in a random access report of each attempt.

Taking the measResultForRSSI being included in the random access report under each SSB/CSI-RS as an example, the method for the terminal to report the situation of the LBT detection during the four-step random access procedure is as follows:
measResultForRSSI including the measurement result of Received Signal Strength Indication (RSSI) in dBm and channel occupancy, where the channel occupancy is the percentage of samples whose RSSI is higher than a preset channel occupancy threshold.

If measRSSI-ReportConfig is configured in the corresponding report configuration (reportConfig), the RSSI result (rssi-Result) is set to the average of the samples provided by the lower layer during the report interval, and the channel occupancy is set to the percentage of samples with RSSI values above the preset channel occupancy threshold during the report interval to all samples.

Examples of reporting measResultForRSSI in the random access report (PerRASSBInfo-r16) under each SSB and reporting measResultForRSSI in the random access report (PerRACSI-RSInfo-r16) under each CSI-RS are as follows:
<IMG>.

The network device may receive a situation of a random access that has been performed by a terminal device, where the situation of the random access includes information related to a result of an LBT detection of the terminal device in a random access attempt.

Optionally, the network device may further adjust the random access resource according to the situation of the random access, for example, change a time-frequency location of the random access resource when a plurality pieces of information related to LBT failure are received.

Optionally, the network device determines whether the PerRAAttemptInfoList-r16 in the received random access report of the terminal contains too many PerRAAttemptInfo indicating information related to LBT failure. If the answer is yes, it is considered to change the time-frequency location of the random access resource. For example, the frequency location of a bandwidth part (BWP) where the random access resource is located is changed, specifically, locationAndBandwidth may be changed to avoid a frequency position with a lot of interference. Alternatively, when the BWP is wide enough (greater than <NUM>), a frequency position of the random access resource inside the BWP, msg1-FrequencyStart-r16, is changed. The above manner may be applied to Msg3.

<FIG> is a schematic diagram of a manner in which a network device adjusts a frequency domain position of a random access resource in a method for adjusting the random access resource according to the embodiments of the present application. As shown in <FIG>, when the random access report received by the network device contains a plurality pieces of information related to LBT failure, the time-frequency location of the random access resource may be changed. Two changing manners are shown in <FIG>. The first option is to change the frequency position of the BWP where the random access is located. For example, if the LBT frequently fails during the random access of the terminal device, the BWP where the random access is located is then changed from BWP1 to BWP2. The second option is to change the frequency position of the random access resource inside the BWP. For example, if the LBT frequently fails during the random access of the terminal device, the frequency band where the random access is located in the BWP1 is changed. The premise of adopting the second option may be that the BWP is wide enough, e.g., the BMP is greater than a preset threshold. For example, the preset threshold is set to <NUM>.

In addition, the manner in which the network device adjusts the random access resource according to the LBT detection result reported by the terminal device may also include: changing a frequency domain position of an uplink grant (UL grant) allocated to a Msg3 in a Random Access Response (RAR) when receiving a plurality pieces of information related to LBT failure of the Msg3 of the random access procedure.

Optionally, the network device may determine whether LBT failure frequently occurs at the sending position of the received Msg3 of the terminal, and if yes, it considers to change the frequency domain location of the uplink grant allocated to Msg3 in the RAR.

For the second category, reporting the situation of the random access (such as LBT detection results) in the two-step random access procedure:.

The two-step random access procedure is shown in <FIG>, where the terminal and the base station need to send a total of two messages to complete the random access procedure. MsgA contains the random access preamble sent on PRACH and payload information sent on PUSCH. The detection situations of LBT during the two-step random access procedure are as follows:.

In the embodiments of the present application, for the two-step random access procedure, the terminal device reports to the network device whether an LBT failure is detected during the sending procedure of MsgA preamble, MsgA payload and/or Msg3. The network device adjusts the resource configuration according to the detection result reported by the terminal device. The specific schemes are as follows:.

In some implementation manners, the information related to the time-frequency location where the MsgA preamble of the random access procedure is located includes at least one of the following:.

Correspondingly, the network device may determine a spectrum bandwidth occupied by a sending resource of the MsgA preamble based on at least one of the lowest frequency position used to transmit message A msgA-RO-FrequencyStart, the information about the number of frequency multiplexing msgA-FDM, the number of Physical Resource Blocks (PRBs) occupied by each Random Access Channel Occasion (RACH Occasion, RO) unit, and a subcarrier bandwidth of BWP.

For example, msgA-RO-FrequencyStart is <NUM>, msgA-FDM = <NUM>, the number of RBs occupied by each RO unit = <NUM>, and the subcarrier bandwidth of BWP is <NUM>. Then the network device determines that the RB indexes occupied by the MsgA preamble is from <NUM> to <NUM>+<NUM>*<NUM> = <NUM>, and the bandwidth range is <NUM>*<NUM>*<NUM> = <NUM> (one PRB=a frequency range occupied by <NUM> subcarriers). The starting position is given by the starting frequency point of the BWP + msgA-RO-FrequencyStart*<NUM>.

In some implementation manners, the information related to the time-frequency location where the MsgA payload of the random access procedure is located includes at least one of the following:.

Correspondingly, the network device may determine a spectrum bandwidth occupied by a sending resource of the MsgA payload based on at least one of the lowest frequency position where the payload is located frequencyStartMsgA-PUSCH, the information about the number of frequency domain multiplexing nrofMsgA-PO-FDM, the number of PRBs occupied by each PUSCH unit nrofPRBs-PerMsgA-PO, and a subcarrier bandwidth of the BWP.

In addition, the terminal device may also report in the random access report a measurement result of the terminal device related to a channel occupancy of a cell where the random access is located, measResultForRSSI,.

Optionally, the measResultForRSSI is included in a random access report under each SSB.

Optionally, the measResultForRSSI is included in a random access report under each CSI-RS.

Optionally, the measResultForRSSI is included in a random access report of each random access attempt.

Taking the measResultForRSSI being included in the random access report under each SSB as an example, the method for the terminal to report the situation of the LBT detection during the two-step random access procedure is as follows:
<IMG>.

Optionally, the network device determines whether PerRAAttemptInfoList-r16 in the received random access report of the terminal contains too many PerRAAttemptInfo indicating information related to LBT failure. If the answer is yes, it is considered to change the time-frequency location of the random access resource. For example, the frequency location of a bandwidth part (BWP) where the random access is located is changed, specifically, locationAndBandwidth may be changed to avoid a frequency position with a lot of interference. Alternatively, when the BWP is wide enough (greater than <NUM>), a frequency position of the random access resource inside the BWP, msg1-FrequencyStart-r16, is changed.

To sum up, in the embodiments of the present application, the terminal device can report to the network device the situation of the random access that has been performed before, and the situation of the random access may include information related to a result of an LBT detection of the terminal device in a random access attempt, so that the network device can obtain the LBT situation during the random access procedure of the terminal device, and know whether its own random access resource (the time-frequency resource position of the preamble) is placed in a position that is often subject to external interference, so as to timely adjust the frequency location of the random access, thereby reducing the probability of LBT failure during the random access procedure.

The embodiments of the present application also provide a method for receiving and applying a situation of a random access, which may be applied to a network device. <FIG> is a flow chart of implementing a method <NUM> for receiving and applying a situation of a random access according to the embodiments of the present application, and the method includes the following steps.

In S610: a situation of a random access that has been performed by a terminal device is received from the terminal device, where the situation of the random access includes information related to a result of an LBT detection of the terminal device in a random access attempt.

Optionally, the network device may further adjust a random access resource according to the situation of the random access.

Optionally, the situation of the random access is received by the network device through a random access report.

Optionally, the adjusting random access resource according to the situation of the random access includes: changing a time-frequency location of the random access resource when a plurality pieces of information related to LBT failure are received.

Optionally, the changing the time-frequency location of the random access resource includes at least one of the following:.

Optionally, in a case that a BWP width is greater than a preset threshold, the frequency position of the random access resource inside the BWP is changed.

Optionally, the adjusting the random access resource according to the situation of the random access includes: changing a frequency domain position of an uplink grant allocated to a message <NUM> in a random access response (RAR) when receiving a plurality pieces of information related to LBT failure of the message <NUM> of the random access procedure.

Optionally, the receiving a plurality pieces of information related to LBT failure includes: a plurality of each random access attempt information indicating information related to LBT failure being included in a list of each random access attempt information in the received random access report.

Optionally, the network device receives at least one of the following from the terminal device:.

Optionally, the network device further receives at least one of the following from the terminal device:.

Optionally, the information related to the time-frequency location where the preamble of the message A of the random access procedure is located includes at least one of the following:.

Optionally, the method further includes: determining, by the network device, a spectrum bandwidth occupied by a sending resource of the preamble of the message A based on at least one of the lowest frequency position used to transmit message A msgA-RO-FrequencyStart, the information about the number of frequency multiplexing msgA-FDM, the number of PRBs occupied by each Random Access Channel Occasion (RO) unit, and a subcarrier bandwidth of the BWP.

The information related to the time-frequency location where the payload of the message A of the random access procedure is located provided by the embodiments of the present application includes at least one of the following:.

Optionally, the method further includes: determining, by the network device, a spectrum bandwidth occupied by a sending resource of the payload of the message A based on at least one of the lowest frequency position where the payload is located frequencyStartMsgA-PUSCH, the information about the number of frequency domain multiplexing nrofMsgA-PO-FDM, the number of PRBs occupied by each PUSCH unit nrofPRBs-PerMsgA-PO, and a subcarrier bandwidth of the BWP.

Optionally, the network device receives a measurement result of the terminal device related to a channel occupancy of a cell where the random access is located from the terminal device.

Optionally, the measurement result of the terminal device related to the channel occupancy of the cell where the random access is located is included in a random access report; and/or.

The embodiments of the present application further provide a terminal device, and <FIG> is a schematic structural diagram of a terminal device <NUM> according to the embodiments of the present application, where the terminal device includes:
a sending module <NUM>, configured to send a situation of a random access that has been performed by the terminal device to a network device, where the situation of the random access includes information related to a result of an LBT detection of the terminal device in a random access attempt.

Optionally, the sending module <NUM> sends the situation of the random access in a random access report.

Optionally, the sending module <NUM> sends at least one of the following to the network device:.

Optionally, the sending module <NUM> further sends at least one of the following to the network device:.

Optionally, the information related to the time-frequency location where the payload of the message A of the random access procedure is located includes at least one of the following:.

Optionally, the sending module <NUM> sends a measurement result of the terminal device related to a channel occupancy of a cell where the random access is located to the network device.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the terminal device according to the embodiments of the present application are respectively intended to implement the corresponding processes of the terminal device in the method <NUM> of <FIG>, and will not be repeated herein for the sake of brevity.

The embodiments of the present application further provides a network device, <FIG> is a schematic structural diagram of a network device <NUM> according to embodiments of the present application, and the network device <NUM> includes:
a receiving module <NUM>, configured to receive a situation of a random access that has been performed by a terminal device from the terminal device, where the situation of the random access includes information related to a result of a listen before talk (LBT) detection of the terminal device in a random access attempt.

As shown in <FIG>, optionally, the above mentioned network device may further includes:
an adjusting module <NUM>, configured to adjust a random access resource according to the situation of the random access.

Optionally, the situation of the random access is received by the receiving module <NUM> through a random access report.

Optionally, the adjusting module <NUM> is configured to: change a time-frequency location of the random access resource when a plurality pieces of information related to LBT failure is received.

Optionally, the adjusting module <NUM> is configured to: change a frequency domain position of an uplink grant allocated to a message <NUM> in a random access response (RAR) when receiving a plurality pieces of information related to LBT failure of the message <NUM> of the random access procedure.

Optionally, the receiving a plurality pieces of information related to LBT failure includes:
a plurality of each random access attempt information indicating information related to LBT failure being included in a list of the each random access attempt information in the received random access report.

Optionally, the receiving module <NUM> receives at least one of the following from the terminal device:.

Optionally, the receiving module <NUM> further receives at least one of the following from the terminal device:.

Optionally, the adjusting module <NUM> is further configured to:
determine a spectrum bandwidth occupied by a sending resource of the preamble of the message A based on at least one of the lowest frequency position used to transmit message A msgA-RO-FrequencyStart, the information about the number of frequency multiplexing msgA-FDM, the number of PRBs occupied by each Random Access Channel Occasion (RO) unit, and a subcarrier bandwidth of the BWP.

Optionally, the adjusting module <NUM> is further configured to:.

Optionally, the receiving module <NUM> receives a measurement result of the terminal device related to a channel occupancy of a cell where the random access is located from the terminal device.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the network device according to the embodiments of the present application are respectively intended to implement the corresponding processes of the network device in the method <NUM> of <FIG>, and will not be repeated herein for the sake of brevity.

<FIG> is a schematic structural diagram of a communication device <NUM> according to the embodiments of the present application. The communication device <NUM> shown in <FIG> includes a processor <NUM>, and the processor <NUM> may call and run a computer program from a memory, so as to implement the method in the embodiments of the present application.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a memory <NUM>. The processor <NUM> may call and run a computer program from the memory <NUM>, so as to implement the method in the embodiments of the present application.

The memory <NUM> may be a separate device independent of the processor <NUM>, or it may be integrated into the processor <NUM>.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a transceiver <NUM>, and the processor <NUM> may control the transceiver <NUM> to communicate with other device(s). Specifically, the transceiver <NUM> may send information or data to other device(s), or receive information or data from other device(s).

The transceiver <NUM> may further include an antenna, and there may be one or more antennas.

Optionally, the communication device <NUM> may be the terminal device of the embodiments of the present application, and the communication device <NUM> may implement the corresponding processes implemented by the terminal device in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

Optionally, the communication device <NUM> may be the network device of the embodiments of the present application, and the communication device <NUM> may implement the corresponding processes implemented by the network device in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

<FIG> is a schematic structural diagram of a chip <NUM> according to the embodiments of the present application. The chip <NUM> shown in <FIG> includes a processor <NUM>, and the processor <NUM> may call and run a computer program from a memory, so as to implement the methods in the embodiments of the present application.

Optionally, as shown in <FIG>, the chip <NUM> may further include a memory <NUM>. The processor <NUM> may invoke and run a computer program from the memory <NUM>, so as to implement the methods in the embodiments of the present application.

Optionally, the chip <NUM> may further include an input interface <NUM> The processor <NUM> may control the input interface <NUM> to communicate with other devices or chips, specifically, to acquire information or data sent by other devices or chips.

Optionally, the chip <NUM> may further include an output interface <NUM> The processor <NUM> may control the output interface <NUM> to communicate with other devices or chips, specifically, to output information or data sent by other devices or chips.

Optionally, the chip may be applied to the terminal device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the terminal device in the methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

Optionally, the chip may be applied to the network device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the network device in the methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system on chip, a system chip, a chip system, or a System-on-Chip.

The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc..

The aforementioned memories may be volatile memories or nonvolatile memories, or may include both the volatile and nonvolatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).

It should be understood that the above-mentioned memories are illustrative but not restrictive. For example, the memory in the embodiments of the present application may also be a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), and a Direct Rambus RAM (DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.

All or part of the above embodiments may be implemented by software, hardware, firmware or any combination thereof. When being implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that may be accessed by a computer, or a data storage device such as a server or a data center containing one or more available media integration. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) and the like.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and shall not constitute any limitation to the processes implemented in the embodiments of the present application.

Claim 1:
A method for reporting a situation of a random access, applied to a terminal device, the method comprising:
sending (S610) a situation of a random access that has been performed by the terminal device to a network device, wherein the situation of the random access comprises information related to a result of a listen before talk, LBT, detection of the terminal device in a random access attempt,
wherein at least one of the following is sent by the terminal device to the network device:
indication information indicating whether an LBT failure is detected before a preamble of a random access message A is sent;
indication information indicating whether an LBT failure is detected before a payload of the random access message A is sent; and
indication information indicating whether an LBT failure is detected before a random access message <NUM> is sent,
wherein at least one of the following is further sent by the terminal device to the network device:
information related to a time-frequency location where the preamble of the random access message A is located;
information related to a time-frequency location where the payload of the random access message A is located;
information related to a time-frequency location where the random access message <NUM> is located.