WO2024098433A1 - 一种通信方法、装置、设备及存储介质 - Google Patents

一种通信方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2024098433A1
WO2024098433A1 PCT/CN2022/131566 CN2022131566W WO2024098433A1 WO 2024098433 A1 WO2024098433 A1 WO 2024098433A1 CN 2022131566 W CN2022131566 W CN 2022131566W WO 2024098433 A1 WO2024098433 A1 WO 2024098433A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
information
lbt failure
terminal
lbt
Prior art date
Application number
PCT/CN2022/131566
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2022/131566 priority Critical patent/WO2024098433A1/zh
Priority to CN202280004970.1A priority patent/CN115997465A/zh
Publication of WO2024098433A1 publication Critical patent/WO2024098433A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a communication method, apparatus, device and storage medium.
  • LBT listen before talk
  • the network device can configure whether the terminal performs LBT before sending data, and the network device can also configure whether the terminal performs LBT failure detection and recovery.
  • the terminal establishes a connection with the network device through random access and sends data to the network device.
  • the terminal can be configured to perform LBT first.
  • LBT succeeds, the random access of the terminal can be performed.
  • the random access information sent by the terminal currently includes the LBT failure status of each beam, which makes the communication cost high. Therefore, how to ensure the sending of LBT failure status and reduce the communication cost has become an urgent problem to be solved.
  • the present disclosure provides a communication method, apparatus, device and storage medium.
  • a communication method is provided, which is applied to a terminal, comprising: in response to the terminal using a specific frequency band to access a service cell, sending random access information to a network device, the random access information including information for describing that the terminal first listens and then sends LBT failure information during the random access process.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal performs a random access attempt using random access resources associated with the downlink beam.
  • the LBT failure information includes first LBT failure count information, where the first LBT failure count information indicates the number of LBT failures for random access attempts using random access resources associated with a downlink beam.
  • the LBT failure information includes a beam identifier, which is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information in response to a specific frequency band being FR 1/FR 2-1, includes second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the random access information includes third LBT failure number information, and the third LBT failure number information indicates the number of LBT failures in random access attempts in the random access resources associated with the downlink sub-beam.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device
  • the method also includes: based on the configuration information, determining the beam identifier in a non-last random access process in the LBT failure recovery process.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or, the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • a communication device is provided, and the method is applied to a terminal, including: in response to the terminal accessing a service cell, sending random access information to a network device, the random access information being used to describe at least one random access process corresponding to the terminal in a listen-before-send LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of a synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device
  • the method also includes: based on the configuration information, determining the beam identifier in a non-last random access process in the LBT failure recovery process.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes a second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • a communication method is provided, which is applied to a network device, including: receiving random access information sent by a terminal, wherein the terminal uses a specific frequency band to access a service cell, and the random access information includes information for describing that the terminal first listens and then sends LBT failure information during the random access process.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal performs a random access attempt using random access resources associated with the downlink beam.
  • the LBT failure information includes first LBT failure count information, where the first LBT failure count information indicates the number of LBT failures for random access attempts using random access resources associated with a downlink beam.
  • the LBT failure information includes a beam identifier, which is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information in response to a specific frequency band being FR 1/FR 2-1, includes second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the random access information includes third LBT failure number information, and the third LBT failure number information indicates the number of LBT failures in random access attempts in the random access resources associated with the downlink sub-beam.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes a beam identifier determined by the terminal during a non-last random access process in the LBT failure recovery process.
  • the configuration information instructs the terminal to perform LBT before sending data to a network device;
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or, the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • a communication method is provided, which is applied to a network device, including: receiving random access information sent by a terminal to access a service cell, the random access information being used to describe at least one random access process corresponding to the terminal in a listen-before-send LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of a synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes a beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes a second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • a communication device which is configured in a terminal, and the device includes: a sending module, which is used to send random access information to a network device in response to the terminal using a specific frequency band to access a service cell, and the random access information includes information for describing that the terminal first listens and then sends LBT failure information during the random access process.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal performs a random access attempt using random access resources associated with the downlink beam.
  • the LBT failure information includes first LBT failure count information, where the first LBT failure count information indicates the number of LBT failures for random access attempts using random access resources associated with a downlink beam.
  • the LBT failure information includes a beam identifier, which is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information in response to a specific frequency band being FR 1/FR 2-1, includes second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the random access information includes third LBT failure number information, and the third LBT failure number information indicates the number of LBT failures in random access attempts in the random access resources associated with the downlink sub-beam.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device
  • the device also includes: a determination module for determining a beam identifier based on the configuration information during a non-last random access process in the LBT failure recovery process.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or, the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • a communication device which is configured in a terminal, and the device includes: a sending module, used to send random access information to a network device in response to the terminal accessing a service cell, and the random access information is used to describe at least one random access process corresponding to the terminal in the LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of a synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device
  • the device also includes: a determination module for determining the beam identifier based on the configuration information in a non-last random access process in the LBT failure recovery process.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes a second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • a communication device which is configured in a network device, and the device includes: a receiving module, used to receive random access information sent by a terminal, wherein the terminal uses a specific frequency band to access a service cell, and the random access information includes information for describing that the terminal first listens and then sends LBT failure information during the random access process.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal uses the random access resources associated with the downlink beam to make a random access attempt.
  • the LBT failure information includes first LBT failure count information, where the first LBT failure count information indicates the number of LBT failures for random access attempts using random access resources associated with a downlink beam.
  • the LBT failure information includes a beam identifier, which is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information in response to a specific frequency band being FR 1/FR 2-1, includes second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the random access information includes third LBT failure number information, where the third LBT failure number information indicates the number of LBT failures in random access attempts made on random access resources associated with a downlink sub-beam.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes a beam identifier determined by the terminal during a non-last random access process in the LBT failure recovery process.
  • the configuration information instructs the terminal to perform LBT before sending data to a network device;
  • the random access information includes a first LBT failure number information and/or a third LBT failure number information; or, the random access information includes a second LBT failure number information and/or a third LBT failure number information.
  • a communication device which is configured in a network device, and the device includes: a receiving module, used to receive random access information sent by a terminal to access a service cell, and the random access information is used to describe at least one random access process corresponding to the terminal in the LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of a synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes the beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes a second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • a communication device comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to: execute any one of the methods in the first aspect.
  • a communication device comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute any one of the methods in the second aspect.
  • a communication device comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute any one of the methods in the third aspect.
  • a communication device comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute any one of the methods in the fourth aspect.
  • a non-temporary computer-readable storage medium is provided, and when the instructions in the storage medium are executed by the processor of the terminal, the terminal is enabled to execute any one of the methods in the first aspect.
  • a non-temporary computer-readable storage medium is provided, and when the instructions in the storage medium are executed by the processor of the terminal, the terminal is enabled to execute any one of the methods in the second aspect.
  • a non-temporary computer-readable storage medium is provided.
  • the instructions in the storage medium are executed by the processor of the network device, the network device can execute any one of the methods in the third aspect.
  • a non-temporary computer-readable storage medium is provided.
  • the instructions in the storage medium are executed by the processor of the network device, the network device can execute any one of the methods in the fourth aspect.
  • the technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: by sending random access information including LBT failure status to the network device when accessing the serving cell in a specific frequency band, the terminal does not need to report the LBT failure status corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure status, thereby saving communication resources.
  • Fig. 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment.
  • Fig. 2 is a flow chart of a communication method according to an exemplary embodiment.
  • Fig. 3 is a flow chart showing another communication method according to an exemplary embodiment.
  • Fig. 4 is a flow chart showing yet another communication method according to an exemplary embodiment.
  • Fig. 5 is a flow chart of yet another communication method according to an exemplary embodiment.
  • Fig. 6 is a flow chart showing another communication method according to an exemplary embodiment.
  • Fig. 7 is a flow chart showing yet another communication method according to an exemplary embodiment.
  • Fig. 8 is a schematic diagram of a communication device according to an exemplary embodiment.
  • Fig. 9 is a schematic diagram showing another communication device according to an exemplary embodiment.
  • Fig. 10 is a schematic diagram showing yet another communication device according to an exemplary embodiment.
  • Fig. 11 is a schematic diagram of yet another communication device according to an exemplary embodiment.
  • Fig. 12 is a schematic diagram of a communication device according to an exemplary embodiment.
  • Fig. 13 is a schematic diagram of another communication device according to an exemplary embodiment.
  • the communication method involved in the present disclosure can be applied to the wireless communication system 100 shown in Figure 1.
  • the network system may include a network device 110 and a terminal 120.
  • the wireless communication system shown in Figure 1 is only for schematic illustration, and the wireless communication system may also include other network devices, for example, core network devices, wireless relay devices, and wireless backhaul devices, which are not shown in Figure 1.
  • the embodiment of the present disclosure does not limit the number of network devices and the number of terminals included in the wireless communication system.
  • the wireless communication system of the embodiment of the present disclosure is a network that provides wireless communication functions.
  • the wireless communication system can adopt different communication technologies, such as Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single Carrier FDMA (SC-FDMA), and Carrier Sense Multiple Access with Collision Avoidance.
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single Carrier FDMA
  • Carrier Sense Multiple Access with Collision Avoidance According to the capacity, rate, latency and other factors of different networks, networks can be divided into 2G (English: Generation) networks, 3G networks, 4G networks or future evolution networks, such as the 5th Generation Wireless Communication System (5G) network, which
  • the network device 110 involved in the present disclosure may also be referred to as a wireless access network device.
  • the wireless access network device may be: a base station, an evolved Node B (eNB), a home base station, an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and receiving point (TRP), etc. It may also be a gNB in an NR system, or it may also be a component or a part of a device constituting a base station, etc. When it is a vehicle-to-everything (V2X) communication system, the network device may also be a vehicle-mounted device.
  • V2X vehicle-to-everything
  • the terminal 120 involved in the present disclosure may also be referred to as a terminal device, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc., which is a device that provides voice and/or data connectivity to users.
  • the terminal may be a handheld device with a wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminals are: a smart phone (Mobile Phone), a pocket computer (Pocket Personal Computer, PPC), a handheld computer, a personal digital assistant (Personal Digital Assistant, PDA), a laptop computer, a tablet computer, a wearable device, or a vehicle-mounted device, etc.
  • V2X vehicle-to-everything
  • the terminal device may also be a vehicle-mounted device. It should be understood that the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal.
  • the network device 110 and the terminal 120 may use any feasible wireless communication technology to achieve mutual data transmission.
  • the transmission channel corresponding to the data sent by the network device 110 to the terminal 120 is called a downlink channel (DL)
  • the transmission channel corresponding to the data sent by the terminal 120 to the network device 110 is called an uplink channel (UL).
  • DL downlink channel
  • UL uplink channel
  • the network device involved in the embodiments of the present disclosure may be a base station.
  • the network device may also be any other possible network device
  • the terminal may be any possible terminal, which is not limited by the present disclosure.
  • LBT can be performed before sending data.
  • the network device can configure whether the terminal performs LBT before sending data, and the network device can also configure whether the terminal performs LBT failure detection and recovery.
  • the terminal detects continuous LBT failures based on the granularity of bandwidth part (BWP). For special cells (SpCells), if continuous LBT failures are detected on a BWP of a SpCell, the terminal will switch to another BWP of the SpCell that is configured with physical random access channel (PRACH) resources to initiate random access.
  • BWP bandwidth part
  • the SpCell can be a primary cell (PCell) or a primary secondary cell (PScell).
  • the terminal can generate an LBT failure medium access control element (MAC CE).
  • the MAC CE can indicate the identity document (ID) of all serving cells where the LBT failure occurred.
  • ID the identity document
  • the terminal will select another BWP with PRACH resources to initiate random access again. It can be understood that only when the random access is successful will the terminal cancel the consistent LBT failure triggered on all BWPs on the SpCell. It is worth noting that the reporting of the LBT failure MAC CE does not trigger the cancellation of the consistent LBT failure on each BWP of the SpCell. When the terminal tries all BWPs of the serving cell, a consistent LBT failure occurs.
  • the medium access control (MAC) layer of the terminal indicates the LBT failure to the radio resource control (RRC) layer, and the terminal declares a radio link failure (RLF) of the master cell group (MCG) or secondary cell group (SCG).
  • RRC radio resource control
  • the terminal can access the NR cell on the FR 1 band, FR 2-1 band and FR 2-2 band, and their respective frequency ranges can be shown in Table 1.
  • the LBT performed by the terminal on the FR 2-2 band is directional. That is, the signal detection (sensing) is performed in one direction.
  • the LBT performed by the terminal is omnidirectional, that is, the signal is sensed at 360 degrees.
  • the beam used by the terminal for sensing needs to be able to cover the beam used for terminal transmission in space.
  • the beam used for uplink transmission by the terminal also depends on the downlink beam sent by the network device selected by the terminal. That is, when the terminal receives the downlink beam sent by the network device, it will determine a terminal's receiving beam. When the terminal receives different beams sent by the network device, the receiving beams used can be the same or different.
  • the terminal determines the receiving beam, for terminals that support beam communication (correspondence) the corresponding transmitting beam of the receiving beam will be used to send data.
  • the terminal changes the received downlink beam of the network device the receiving beam of the terminal will change. Then the corresponding transmitting beam is likely to change as well.
  • the downlink beam sent by the network device can be identified by the index of the synchronization signal block (SSB) and/or the channel state information reference signal (CSI-RS). Therefore, when the terminal performs random access using random access resources associated with different downlink beams sent by the network device, the sensing beam may be different depending on the selected downlink beam. This will lead to different LBT results. Therefore, it is necessary to indicate the corresponding LBT failure for each (per) beam.
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • the terminal will indicate the corresponding LBT failure for each beam, and for omnidirectional LBT, regardless of whether the downlink beam selected by the terminal changes, the terminal's sensing beam is omnidirectional. The terminal's sensing result will not change. Obviously, the current method will make the communication cost higher. Therefore, how to ensure the sending of LBT failures and reduce communication costs has become an urgent problem to be solved.
  • the present disclosure provides a communication method, apparatus, device and storage medium, which sends random access information including LBT failure status to a network device when accessing a service cell in a specific frequency band, so that the terminal does not need to report the LBT failure status corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure status, thereby saving communication resources.
  • FIG. 2 is a flow chart of a communication method according to an exemplary embodiment. As shown in FIG. 2 , the method is applied to a terminal and may include the following steps:
  • step S11 in response to the terminal using a specific frequency band to access a serving cell, random access information is sent to a network device.
  • the terminal in response to the terminal using a specific frequency band to access a serving cell, may send random access information to the network device.
  • the random access information may include LBT failure information.
  • the LBT failure information is used to describe the situation where the terminal fails LBT during the random access process.
  • the random access information may also include any other information that may be involved in the random access process.
  • the terminal when a terminal needs to communicate with a network device, the terminal may initiate a connection establishment to the network device using a specific frequency band.
  • the terminal may establish a connection with the network device using a random access method.
  • the terminal may be configured to perform LBT before sending data. Therefore, the terminal performs an LBT detection before the random access begins.
  • the LBT is detected to be successful, random access is performed.
  • the random access is successful, it can be considered that the connection is successfully established.
  • the terminal may send random access information to the network device when the connection is successfully established or unsuccessful.
  • the random access information may include any information that may be involved in the random access process. For example, it includes LBT failure information for describing the failure of LBT of the terminal during the random access process.
  • the random access information can be recorded in a connection establishment failure report.
  • the connection establishment failure report is generated by the terminal when the connection establishment fails. It can be understood that reporting means that the terminal sends information, data, etc. to the network device.
  • the above random access information can be carried in the RLF report.
  • the RLF report can be generated by the terminal in the case of MCG RLF.
  • the random access information is carried in the SCG failure information, where the SCG failure information may be generated by the terminal in the case of SCG RLF.
  • the random access information when the terminal performs random access successfully, may be carried in a random access report used to describe the success of random access.
  • the random access report used to describe the success of random access may be generated by the terminal when the random access is successful.
  • the terminal when the terminal performs a serving cell handover and the handover is successful, the above random access information is carried in a handover success report.
  • the handover success report may be generated by the terminal when the serving cell handover is successful.
  • the PScell addition or change success report when a PScell is added or changed successfully, the PScell addition or change success report carries the above random access information.
  • the PScell addition or change success report may be generated by the terminal when a PScell is added or changed successfully.
  • the present disclosure sends random access information including LBT failure status to the network device when accessing the service cell in a specific frequency band, so that the terminal does not need to report the LBT failure status corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure status, thereby saving communication resources.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal uses the random access resources associated with the downlink beam to make a random access attempt.
  • the LBT failure information in the random access information is the LBT failure information corresponding to each downlink beam.
  • the downlink beam is the beam for which the terminal attempts random access using the random access resource associated with the beam.
  • the terminal when the terminal adopts FR 2-2 to access the service cell, the terminal performs LBT detection on different downlink beams when performing LBT detection during the random access process. That is to say, the terminal performs LBT detection on downlink beams in different directions respectively. It can also be understood that the terminal performs random access attempts on downlink beams in different directions using random access resources associated with dependent beams, and performs LBT detection in each random access attempt.
  • the terminal detects that LBT fails continuously for multiple times on a downlink beam, it can be considered that LBT has failed on the downlink beam.
  • the number of consecutive LBT failures can be pre-set or specified by the protocol, and is not limited in the present disclosure.
  • the LBT failure information corresponding to each downlink beam is sent to the network device. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the LBT failure information further includes first LBT failure count information.
  • the first LBT failure count information indicates the number of LBT failures of random access attempts using random access resources associated with a downlink beam.
  • the LBT failure information sent by the terminal may include first LBT failure number information.
  • the first LBT failure number information indicates the number of LBT failures of the terminal using the random access resource associated with the downlink beam to perform random access attempts. Among them, one first LBT failure number information may correspond to a random access process.
  • a random access process may include multiple random access attempts. When the number of random access attempt failures reaches a preset failure attempt threshold, the random access process may be considered to have failed. One or more LBT tests may be performed in a random access attempt. When the number of LBT failures reaches the LBT failure threshold, the random access attempt may be considered to have failed.
  • the number of LBT failures occurring during the random access attempt process may be recorded.
  • the number of LBT failures may be the total number of LBT failures corresponding to multiple random access attempts.
  • the number of LBT failures may be based on each random access attempt, and the number of LBT failures of the corresponding random access attempt is recorded respectively.
  • the present invention accesses the service cell in the FR 2-2 frequency band, the first LBT failure count information is sent to the network device. This makes it unnecessary for the terminal to report the LBT failure situation corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure situation, thereby saving communication resources.
  • the LBT failure information includes a beam identifier
  • the beam identifier is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information sent by the terminal may include a beam identifier.
  • the beam identifier may be an SSB identifier and/or a CSI-RS identifier.
  • the identifier may be an id or an index.
  • the SSB identifier is an SSB index
  • the CSI-RS identifier is a CSI-RS index. It can be understood that the beam indicated by the beam identifier is the downlink beam for the random access attempt mentioned above.
  • the terminal may record the SSB index and/or CSI-RS index corresponding to the random access resource of the SSB and/or CSI-RS associated with the random access attempt in chronological order. For example, multiple consecutive random access attempts may use the same SSB and/or CSI-RS associated with the random access resource.
  • the present disclosure When accessing a service cell on the FR 2-2 frequency band, the present disclosure sends a beam identifier to a network device, and the beam identifier indicates a downlink beam for random access attempts. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the LBT failure information in response to the specific frequency band being FR 1 or FR 2-1, includes the second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the LBT failure information in the random access information may include the second LBT failure number information corresponding to the downlink beam.
  • the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • LBT detection performed on the FR 1 band or the FR 2-1 band can be omnidirectional LBT. Therefore, the LBT failure information may not carry beam information, and there is no need to record the number of LBT failures corresponding to each beam.
  • the LBT failure information may carry the second LBT failure number information recording the total number of LBT failures during the random access process.
  • the second LBT failure number may correspond to the sum of the LBT failure numbers of all random access attempts during the random access process.
  • the present disclosure sends the second LBT failure count to the network device when accessing the service cell in the FR 1 band or the FR 2-1 band. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the downlink beam may include a downlink sub-beam, wherein the downlink sub-beam may represent a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • a terminal when a terminal has continuous LBT failures, it will perform LBT recovery by switching BWP and initiating a new random access attempt.
  • the terminal In response to the failure of a random access process of the terminal, the terminal can perform an LBT failure recovery process. For example, try to switch to another BWP and initiate a new random access process again until the random access is successful. Or if LBT fails continuously on all BWPs that can be tried, the terminal triggers RLF.
  • the random access processes involved above can all be considered to be related to the same LBT failure recovery process.
  • the random access process that triggers the LBT failure recovery process should also be considered to be related to the LBT failure recovery process.
  • the terminal may send random access information to the network device, and the LBT failure information in the random access information may be a beam for random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the terminal accesses the serving cell on FR 2-2, or the terminal accesses the serving cell on FR 1 band or FR 2-1 band.
  • the beam identifier is, for example, an SSB index and/or a CSI-RS index. It can be understood that the SSB index and/or the CSI-RS index in this embodiment is used to indicate the beam for random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • Each SSB index and/or CSI-RS index in this embodiment is used to indicate the beam for random access attempt in each random access process corresponding to the same LBT failure recovery process, that is, the downlink sub-beam.
  • the SSB and/or CSI-RS corresponding to the random access resource associated with the downlink sub-beam is indicated by the SSB index and/or CSI-RS index.
  • the present disclosure can send corresponding LBT failure conditions to the network device for beams belonging to the same LBT failure recovery process, so that the terminal does not need to report the LBT failure conditions corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure conditions, thereby saving communication resources.
  • each random access process in the random access information may include at least one of the following: information corresponding to each random access attempt; LBT failure information corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • the random access information may include information corresponding to each random access attempt.
  • the random access information records corresponding information of each random access attempt, such as a timestamp, corresponding communication parameters and other possible information.
  • the random access information may include LBT failure information corresponding to the random access attempt.
  • the random access information may include a DL reference signal receiving power (RSRP) of the SSB.
  • RSRP DL reference signal receiving power
  • the random access information may include frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message (message, Msg) 1 or Msg A.
  • Message 1 is the first step message of the four-step random access.
  • Message A is the first step message of the two-step random access.
  • the content of Msg A can include the content of Msg 1 and Msg 3 of the four-step random access.
  • the random access information may include subcarrier spacing (SCS) information of the BWP.
  • SCS subcarrier spacing
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information may not include at least one of the following: information corresponding to each random access attempt; LBT failure information corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • the random access information may not include information corresponding to each random access attempt.
  • the random access information may not include LBT failure information corresponding to the random access attempt.
  • the random access information may not include the DL RSRP of the SSB.
  • the random access information may not include the frequency domain resource configuration information or subcarrier spacing information used by Msg 1 or Msg A.
  • the random access information may not include the SCS information of the BWP.
  • the present disclosure provides a variety of different information that may not be included in the random access information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by the random access common information RA-InformationCommon or a newly added information field.
  • one or more of the information contained in each random access process corresponding to the random access information can be carried by random access common information (RA-InformationCommon).
  • the information contained in the random access information corresponding to each random access process such as information corresponding to each random access attempt; LBT failure information corresponding to the random access attempt; DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send Msg 1 or Msg A; one or more of the SCS information of BWP.
  • It can be carried through a newly added information domain. It can be understood that this embodiment means that it is not carried through RA-InformationCommon, but a new information domain is selected for carrying.
  • the new information domain can carry multiple information contained in the random access information corresponding to each random access process. It is also possible that each newly added information domain separately carries a piece of information contained in each random access process corresponding to the random access information.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB can be carried by the random access information list (perRAInfoList)
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt, and/or the DL RSRP of the SSB can be carried through a newly added information field. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • the new information field can carry multiple information including each random access attempt included in each random access process corresponding to the random access information, the beam information corresponding to the random access attempt, and the DL RSRP of the SSB.
  • Each newly added information field can also separately carry one of the random access attempts included in each random access process corresponding to the random access information, the beam information corresponding to the random access attempt, and the DL RSRP of the SSB.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • the random access information includes third LBT failure number information, and the third LBT failure number information indicates the number of LBT failures of random access attempts in the random access resources associated with the downlink sub-beam.
  • the random access information may include third LBT failure information, wherein the third LBT failure information indicates the number of LBT failures in random access attempts in the random access resources associated with the downlink sub-beam.
  • the number of LBT failures in this embodiment may be the total number of LBT failures corresponding to multiple random access attempts.
  • the number of LBT failures may be based on each random access attempt, and the number of LBT failures of the corresponding random access attempt is recorded respectively.
  • the present disclosure sends the third LBT failure number information based on the same LBT failure recovery process to the network device, so that the terminal does not need to report the LBT failure corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process, and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList.
  • the perRAInfoList of the last random access triggered by the continuous LBT failure is recorded.
  • the RA-InformationCommon of the last random access triggered by the continuous LBT failure is recorded.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process, and the LBT failure count information corresponding to each beam are carried through the newly added information domain, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam can be carried through a newly added information field, RA-InformationCommon or perRAInfoList. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • the new information field can carry multiple information including the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam.
  • Each newly added information field can also separately carry one of the beam identifiers corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • FIG3 is a flow chart of another communication method according to an exemplary embodiment.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device, and the method may further include the following steps:
  • step S21 based on the configuration information, the beam identifier is determined in a non-last random access process in the LBT failure recovery process.
  • the terminal may receive configuration information sent by the network device.
  • the configuration information is used to instruct the terminal to perform LBT before sending data to the network device.
  • the terminal may determine the beam identifier in a non-last random access process in the LBT failure recovery process, that is, the beam identifier of the downlink sub-beam.
  • the present disclosure can determine the beam identifier in the non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device.
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • the random access information in response to the terminal receiving configuration information sent by the network device, and the configuration information instructing the terminal to perform LBT before sending data to the network device, the random access information may include the first LBT failure number information and/or the third LBT failure number information.
  • the random access information in response to the terminal receiving configuration information sent by the network device, and the configuration information instructing the terminal to perform LBT before sending data to the network device, the random access information may include the second LBT failure number information and/or the third LBT failure number information.
  • the present disclosure includes LBT failure count information in the random access information only when the network device configures the terminal to perform LBT before sending data, so that the terminal does not need to report the LBT failure corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the present disclosure also provides a communication method, by sending random access information describing at least one random access process corresponding to the terminal in the LBT failure recovery process to a network device, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • FIG. 4 is a flow chart of another communication method according to an exemplary embodiment. As shown in FIG. 4 , the method is applied to a terminal and may include the following steps:
  • step S31 in response to the terminal accessing the serving cell, random access information is sent to the network device.
  • the terminal in response to the terminal accessing the serving cell, may send random access information to the network device.
  • the random access information is used to describe at least one random access process corresponding to the terminal in the LBT failure recovery process.
  • the random access information corresponds to at least one random access process corresponding to the same LBT failure recovery process. If the terminal starts the LBT failure recovery process based on the random access process, the random access process that triggers the LBT failure recovery process should also be considered to be related to the LBT failure recovery process.
  • the present disclosure sends random access information describing at least one random access process corresponding to a terminal in an LBT failure recovery process to a network device, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • each random access process in the random access information may include at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of the partial bandwidth BWP.
  • the random access information may include information corresponding to each random access attempt.
  • the random access information records corresponding information of each random access attempt, such as a timestamp, corresponding communication parameters and other possible information.
  • the random access information may include LBT failure information corresponding to the random access attempt.
  • the random access information may include the DL RSRP of the SSB.
  • the random access information may include frequency domain resource configuration information or subcarrier spacing information used by the random access process to send Msg 1 or Msg A.
  • Message 1 is the first step message of the four-step random access.
  • Message A is the first step message of the two-step random access.
  • the content of Msg A can include the content of Msg 1 and Msg 3 of the four-step random access.
  • the random access information may include SCS information of the BWP.
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information may not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • the random access information may not include information corresponding to each random access attempt.
  • the random access information may not include LBT failure information corresponding to the random access attempt.
  • the random access information may not include the DL RSRP of the SSB.
  • the random access information may not include the frequency domain resource configuration information or subcarrier spacing information used by Msg 1 or Msg A.
  • the random access information may not include the SCS information of the BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by the random access common information RA-InformationCommon or a newly added information field.
  • one or more of the information contained in each random access process corresponding to the random access information can be carried by RA-InformationCommon.
  • the information contained in the random access information corresponding to each random access process such as information corresponding to each random access attempt; LBT failure information corresponding to the random access attempt; DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send Msg 1 or Msg A; one or more of the SCS information of BWP.
  • It can be carried through a newly added information domain. It can be understood that this embodiment means that it is not carried through RA-InformationCommon, but a new information domain is selected for carrying.
  • the new information domain can carry multiple information contained in each random access process corresponding to the random access information. It is also possible that each newly added information domain separately carries one information contained in each random access process corresponding to the random access information.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB can be carried by perRAInfoList
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt, and/or the DL RSRP of the SSB can be carried through a newly added information field. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • the new information field can carry multiple information including each random access attempt included in each random access process corresponding to the random access information, the beam information corresponding to the random access attempt, and the DL RSRP of the SSB.
  • Each newly added information field can also separately carry one of the random access attempts included in each random access process corresponding to the random access information, the beam information corresponding to the random access attempt, and the DL RSRP of the SSB.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList.
  • the perRAInfoList of the last random access triggered by the continuous LBT failure is recorded.
  • the RA-InformationCommon of the last random access triggered by the continuous LBT failure is recorded.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the number of LBT failures corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the number of LBT failures corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through the newly added information domain, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam can be carried through a newly added information field, RA-InformationCommon or perRAInfoList. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • the new information field can carry multiple information including the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam.
  • Each newly added information field can also separately carry one of the beam identifiers corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • FIG5 is a flow chart of another communication method according to an exemplary embodiment.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device, and the method may further include the following steps:
  • step S41 based on the configuration information, the beam identifier is determined in a non-last random access process in the LBT failure recovery process.
  • the terminal may receive configuration information sent by the network device.
  • the configuration information is used to instruct the terminal to perform LBT before sending data to the network device.
  • the terminal may determine the beam identifier in a non-last random access process in the LBT failure recovery process, that is, the beam identifier of the downlink sub-beam.
  • the present disclosure can determine the beam identifier of a non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information sent by the terminal may include a beam identifier.
  • the beam identifier may be an SSB identifier and/or a CSI-RS identifier.
  • the identifier may be an id or an index.
  • the SSB identifier is an SSB index
  • the CSI-RS identifier is a CSI-RS index. It can be understood that the beam indicated by the beam identifier is the downlink beam for the random access attempt mentioned above.
  • the terminal may record the SSB index and/or CSI-RS index corresponding to the random access resource of the SSB and/or CSI-RS associated with the random access attempt in chronological order. For example, multiple consecutive random access attempts may use the same SSB and/or CSI-RS associated with the random access resource.
  • the present disclosure provides a variety of different beam identification information so that the network device can obtain random access information corresponding to at least one random access process in the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the random access information sent by the terminal may include first LBT failure number information.
  • the first LBT failure number information indicates the number of LBT failures of the terminal using the random access resource associated with the downlink beam to attempt random access.
  • One first LBT failure number information may correspond to one random access process.
  • a random access process may include multiple random access attempts. When the number of random access attempt failures reaches a preset failure attempt threshold, the random access process may be considered to have failed. One or more LBT tests may be performed in a random access attempt. When the number of LBT failures reaches the LBT failure threshold, the random access attempt may be considered to have failed.
  • the number of LBT failures occurring during the random access attempt process may be recorded.
  • the number of LBT failures may be the total number of LBT failures corresponding to multiple random access attempts.
  • the number of LBT failures may be based on each random access attempt, and the number of LBT failures of the corresponding random access attempt is recorded respectively.
  • the present invention sends the first LBT failure count information to the network device when accessing the service cell on the FR 2-2 frequency band, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • the random access information in response to the terminal accessing the serving cell in the FR 1 frequency band or the FR 2-1 frequency band, may include second LBT failure number information.
  • the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • the present invention sends a second LBT failure count to a network device when accessing a service cell in the FR 1 band or the FR 2-1 band, so that the network device can obtain random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the present disclosure also provides a communication method applied to a network device.
  • FIG. 6 is a flow chart of another communication method according to an exemplary embodiment. As shown in FIG. 6 , the method is applied to a network device and may include the following steps:
  • step S51 random access information sent by a terminal is received.
  • the network device may receive random access information sent by a terminal, wherein the terminal uses a specific frequency band to access a serving cell, and the random access information includes information describing LBT failure of the terminal during the random access process.
  • the random access information may also include any other information that may be involved in the random access process.
  • the present disclosure allows a network device to receive random access information including LBT failure status sent by a terminal when accessing a service cell in a specific frequency band, so that the terminal does not need to report the LBT failure status corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure status, thereby saving communication resources.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal uses the random access resources associated with the downlink beam to make a random access attempt.
  • the LBT failure information in the random access information is the LBT failure information corresponding to each downlink beam.
  • the downlink beam is the beam for which the terminal attempts random access using the random access resource associated with the beam.
  • the terminal when the terminal adopts FR 2-2 to access the service cell, the terminal performs LBT detection on different downlink beams when performing LBT detection during the random access process. That is to say, the terminal performs LBT detection on downlink beams in different directions respectively. It can also be understood that the terminal performs random access attempts on downlink beams in different directions using random access resources associated with dependent beams, and performs LBT detection in each random access attempt.
  • the terminal detects that LBT fails continuously for multiple times on a downlink beam, it can be considered that LBT has failed on the downlink beam.
  • the number of consecutive LBT failures can be pre-set or specified by the protocol, and is not limited in this disclosure.
  • the network device When the present invention accesses the service cell on the FR 2-2 frequency band, the network device receives the LBT failure information corresponding to each downlink beam sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the LBT failure information further includes first LBT failure count information.
  • the first LBT failure count information indicates the number of LBT failures of random access attempts using random access resources associated with a downlink beam.
  • the LBT failure information received by the network device may include first LBT failure number information.
  • the first LBT failure number information indicates the number of LBT failures of the terminal using the random access resource associated with the downlink beam to perform random access attempts. Among them, one first LBT failure number information may correspond to a random access process.
  • the network device When the present invention accesses the service cell on the FR 2-2 frequency band, the network device receives the first LBT failure number information sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the LBT failure information includes a beam identifier
  • the beam identifier is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information received by the network device may include a beam identifier.
  • the beam identifier may be an SSB identifier and/or a CSI-RS identifier.
  • the identifier may be an id or an index.
  • the SSB identifier is an SSB index
  • the CSI-RS identifier is a CSI-RS index. It can be understood that the beam indicated by the beam identifier is the downlink beam for the random access attempt mentioned above.
  • the network device When the present invention accesses a service cell on the FR 2-2 frequency band, the network device receives a beam identifier sent by the terminal, and the beam identifier indicates the downlink beam for random access attempt. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the LBT failure information in response to the specific frequency band being FR 1 or FR 2-1, includes the second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the LBT failure information in the random access information may include the second LBT failure number information corresponding to the downlink beam.
  • the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the network device When the present invention accesses the service cell in the FR 1 band or the FR 2-1 band, the network device receives the second LBT failure number sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the downlink beam may include a downlink sub-beam, wherein the downlink sub-beam may represent a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the LBT failure information in the random access information may be a beam for random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the terminal accesses the serving cell on FR 2-2, or the terminal accesses the serving cell on FR 1 band or FR 2-1 band.
  • the beam identifier is, for example, an SSB index and/or a CSI-RS index. It can be understood that the SSB index and/or the CSI-RS index in this embodiment is used to indicate the beam for which a random access attempt is made in at least one random access process corresponding to the same LBT failure recovery process.
  • the present disclosure can be directed to beams belonging to the same LBT failure recovery process, and the network device receives the corresponding LBT failure status sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure status corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure status, and thus saving communication resources.
  • each random access process in the random access information may include at least one of the following: information corresponding to each random access attempt; LBT failure information corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • the random access information may include information corresponding to each random access attempt.
  • the random access information records corresponding information of each random access attempt, such as a timestamp, corresponding communication parameters and other possible information.
  • the random access information may include LBT failure information corresponding to the random access attempt.
  • the random access information may include the DL RSRP of the SSB.
  • the random access information may include frequency domain resource configuration information or subcarrier spacing information used by the random access process to send Msg 1 or Msg A.
  • Message 1 is the first step message of the four-step random access.
  • Message A is the first step message of the two-step random access.
  • the content of Msg A can include the content of Msg 1 and Msg 3 of the four-step random access.
  • the random access information may include SCS information of the BWP.
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information may not include at least one of the following: information corresponding to each random access attempt; LBT failure information corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • the random access information may not include information corresponding to each random access attempt.
  • the random access information may not include LBT failure information corresponding to the random access attempt.
  • the random access information may not include the DL RSRP of the SSB.
  • the random access information may not include the frequency domain resource configuration information or subcarrier spacing information used by Msg 1 or Msg A.
  • the random access information may not include the SCS information of the BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by the random access common information RA-InformationCommon or a newly added information field.
  • one or more of the information contained in each random access process corresponding to the random access information can be carried by RA-InformationCommon.
  • one or more of the information contained in each random access process corresponding to the random access information can be carried through a newly added information field.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB can be carried by perRAInfoList
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB can be carried through a newly added information field. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • the random access information includes third LBT failure number information, and the third LBT failure number information indicates the number of LBT failures of random access attempts in the random access resources associated with the downlink sub-beam.
  • the random access information may include third LBT failure information, wherein the third LBT failure information indicates the number of LBT failures in random access attempts in the random access resources associated with the downlink sub-beam.
  • the disclosed network is provided with a receiving terminal for the third LBT failure number information based on the same LBT failure recovery process, so that the network device does not need to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process, and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process, and the LBT failure count information corresponding to each beam are carried through the newly added information domain, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam can be carried through a newly added information field, RA-InformationCommon or perRAInfoList. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes the beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process.
  • the network device may send configuration information to the terminal.
  • the configuration information is used to instruct the terminal to perform LBT before sending data to the network device.
  • the LBT failure information received by the network device may include a beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process, that is, a beam identifier of a downlink sub-beam.
  • the present disclosure can determine the beam identifier in the non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device.
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • the random access information in response to sending configuration information to the terminal, and the configuration information instructs the terminal to perform LBT before sending data to the network device, the random access information may include the first LBT failure number information and/or the third LBT failure number information.
  • the random access information in response to sending configuration information to the terminal, and the configuration information instructs the terminal to perform LBT before sending data to the network device, the random access information may include the second LBT failure number information and/or the third LBT failure number information.
  • the present disclosure includes LBT failure count information in the random access information only when the network device configures the terminal to perform LBT before sending data, so that the terminal does not need to report the LBT failure corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • FIG. 7 is a flow chart of another communication method according to an exemplary embodiment. As shown in FIG. 7 , the method is applied to a network device and may include the following steps:
  • step S61 random access information sent by a terminal accessing a serving cell is received.
  • the network device in response to the terminal accessing the serving cell, may receive random access information sent by the terminal.
  • the random access information is used to describe at least one random access process corresponding to the terminal in the LBT failure recovery process.
  • the network device of the present invention receives random access information sent by the terminal for describing at least one random access process corresponding to the LBT failure recovery process, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • each random access process in the random access information may include at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of the partial bandwidth BWP.
  • the random access information may include information corresponding to each random access attempt.
  • the random access information records corresponding information of each random access attempt, such as a timestamp, corresponding communication parameters and other possible information.
  • the random access information may include LBT failure information corresponding to the random access attempt.
  • the random access information may include the DL RSRP of the SSB.
  • the random access information may include frequency domain resource configuration information or subcarrier spacing information used by the random access process to send Msg 1 or Msg A.
  • Message 1 is the first step message of the four-step random access.
  • Message A is the first step message of the two-step random access.
  • the content of Msg A can include the content of Msg 1 and Msg 3 of the four-step random access.
  • the random access information may include subcarrier spacing and SCS information of the BWP.
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information may not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • the random access information may not include information corresponding to each random access attempt.
  • the random access information may not include LBT failure information corresponding to the random access attempt.
  • the random access information may not include the DL RSRP of the SSB.
  • the random access information may not include the frequency domain resource configuration information or subcarrier spacing information used by Msg 1 or Msg A.
  • the random access information may not include the SCS information of the BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by the random access common information RA-InformationCommon or a newly added information field.
  • one or more of the information contained in each random access process corresponding to the random access information can be carried by RA-InformationCommon.
  • one or more of the information contained in each random access process corresponding to the random access information can be carried through a newly added information field.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB can be carried by perRAInfoList
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB can be carried through a newly added information field. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through the newly added information domain, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam can be carried through a newly added information field, RA-InformationCommon or perRAInfoList. It can be understood that this embodiment means that it is not carried through perRAInfoList, but a new information field is selected for carrying.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes the beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process.
  • the network device may send configuration information to the terminal.
  • the configuration information is used to instruct the terminal to perform LBT before sending data to the network device.
  • the LBT failure information received by the network device may include a beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process, that is, a beam identifier of a downlink sub-beam.
  • the present disclosure can determine the beam identifier in the non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the LBT failure information sent by the terminal may include a beam identifier.
  • the beam identifier may be an SSB identifier and/or a CSI-RS identifier.
  • the identifier may be an id or an index.
  • the SSB identifier is an SSB index
  • the CSI-RS identifier is a CSI-RS index. It can be understood that the beam indicated by the beam identifier is the downlink beam for the random access attempt mentioned above.
  • the present disclosure provides a variety of different beam identification information so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the random access information sent by the terminal may include first LBT failure number information.
  • the first LBT failure number information indicates the number of LBT failures of the terminal using the random access resource associated with the downlink beam to attempt random access.
  • One first LBT failure number information may correspond to one random access process.
  • the network device When the present invention accesses a service cell on the FR 2-2 frequency band, the network device receives the first LBT failure number information sent by the terminal, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • the random access information in response to the terminal accessing the serving cell in the FR 1 frequency band or the FR 2-1 frequency band, may include second LBT failure number information.
  • the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • the network device When the present invention accesses the service cell in the FR 1 frequency band or the FR 2-1 frequency band, the network device receives the number of second LBT failures sent by the terminal, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the embodiments of the present disclosure also provide a communication device and equipment.
  • the communication device and equipment provided by the embodiments of the present disclosure include hardware structures and/or software modules corresponding to the execution of each function in order to realize the above functions.
  • the embodiments of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiments of the present disclosure.
  • Fig. 8 is a schematic diagram of a communication device according to an exemplary embodiment.
  • the device 200 is configured in a terminal, and the device 200 includes: a sending module 201, configured to send random access information to a network device in response to the terminal using a specific frequency band to access a serving cell, and the random access information includes information describing that the terminal first listens and then sends LBT failure information during the random access process.
  • a sending module 201 configured to send random access information to a network device in response to the terminal using a specific frequency band to access a serving cell, and the random access information includes information describing that the terminal first listens and then sends LBT failure information during the random access process.
  • the present disclosure sends random access information including LBT failure status to the network device when accessing the service cell in a specific frequency band, so that the terminal does not need to report the LBT failure status corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure status, thereby saving communication resources.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal uses the random access resources associated with the downlink beam to make a random access attempt.
  • the LBT failure information corresponding to each downlink beam is sent to the network device. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the LBT failure information includes first LBT failure count information, where the first LBT failure count information indicates the number of LBT failures for random access attempts using random access resources associated with a downlink beam.
  • the present invention accesses the service cell in the FR 2-2 frequency band, the first LBT failure count information is sent to the network device. This makes it unnecessary for the terminal to report the LBT failure situation corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure situation, thereby saving communication resources.
  • the LBT failure information includes a beam identifier, which is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the present disclosure When accessing a service cell on the FR 2-2 frequency band, the present disclosure sends a beam identifier to a network device, where the beam identifier indicates a downlink beam for a random access attempt. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the LBT failure information in response to a specific frequency band being FR 1/FR 2-1, includes second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the present disclosure sends the second LBT failure count to the network device when accessing the service cell in the FR 1 band or the FR 2-1 band. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the present disclosure can send corresponding LBT failure conditions to the network device for beams belonging to the same LBT failure recovery process, so that the terminal does not need to report the LBT failure conditions corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure conditions, thereby saving communication resources.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • the present disclosure provides a variety of different information that may be included in random access information so that a network device can better understand the process of a terminal performing random access.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • the random access information includes third LBT failure number information, where the third LBT failure number information indicates the number of LBT failures in random access attempts made on random access resources associated with a downlink sub-beam.
  • the present disclosure sends the third LBT failure number information based on the same LBT failure recovery process to the network device, so that the terminal does not need to report the LBT failure corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device
  • the device 200 also includes: a determination module 202, which is used to determine the beam identifier based on the configuration information in a non-last random access process in the LBT failure recovery process.
  • the present disclosure can determine the beam identifier in the non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data. This makes it unnecessary for the terminal to report the LBT failure corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or, the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • the present disclosure includes LBT failure count information in the random access information only when the network device configures the terminal to perform LBT before sending data, so that the terminal does not need to report the LBT failure corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • Fig. 9 is a schematic diagram of another communication device according to an exemplary embodiment.
  • the device 300 is configured in a terminal, and the device 300 includes: a sending module 301, configured to send random access information to a network device in response to the terminal accessing a serving cell, and the random access information is used to describe at least one random access process corresponding to the terminal in the LBT failure recovery process.
  • the present invention sends random access information describing at least one random access process corresponding to a terminal in an LBT failure recovery process to a network device, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of a synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the random access information including a variety of different information is sent to the network device, so that the network device can better understand the process of random access of the terminal.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • the device 300 in response to the terminal using FR 2-2 to access the service cell and receiving configuration information sent by the network device, the configuration information instructs the terminal to perform LBT before sending data to the network device, the device 300 also includes: a determination module 302, which is used to determine the beam identifier based on the configuration information in a non-last random access process in the LBT failure recovery process.
  • the present disclosure can determine the beam identifier of a non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the present disclosure provides a variety of different beam identification information so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the present invention sends the first LBT failure count information to the network device when accessing the service cell on the FR 2-2 frequency band, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes a second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • the present invention sends a second LBT failure count to a network device when accessing a service cell in the FR 1 band or the FR 2-1 band, so that the network device can obtain random access information of at least one random access process corresponding to the LBT failure recovery process.
  • Fig. 10 is a schematic diagram of another communication device according to an exemplary embodiment.
  • the device 400 is configured in a network device, and the device 400 includes: a receiving module 401, which is used to receive random access information sent by a terminal, wherein the terminal uses a specific frequency band to access a serving cell, and the random access information includes information describing that the terminal first listens and then sends LBT failure information during the random access process.
  • a receiving module 401 which is used to receive random access information sent by a terminal, wherein the terminal uses a specific frequency band to access a serving cell, and the random access information includes information describing that the terminal first listens and then sends LBT failure information during the random access process.
  • the present disclosure allows a network device to receive random access information including LBT failure status sent by a terminal when accessing a service cell in a specific frequency band, so that the terminal does not need to report the LBT failure status corresponding to each beam under any circumstances, thereby reducing the communication cost of the terminal reporting the LBT failure status, thereby saving communication resources.
  • the LBT failure information in response to the specific frequency band being the frequency range FR 2-2, is the LBT failure information corresponding to each downlink beam, and the terminal uses the random access resources associated with the downlink beam to make a random access attempt.
  • the network device When the present invention accesses the service cell on the FR 2-2 frequency band, the network device receives the LBT failure information corresponding to each downlink beam sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the LBT failure information includes first LBT failure count information, where the first LBT failure count information indicates the number of LBT failures for random access attempts using random access resources associated with a downlink beam.
  • the network device When the present invention accesses the service cell on the FR 2-2 frequency band, the network device receives the first LBT failure number information sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the LBT failure information includes a beam identifier, which is a synchronization signal block SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the network device When the present invention accesses a service cell on the FR 2-2 frequency band, the network device receives a beam identifier sent by the terminal, and the beam identifier indicates the downlink beam for random access attempt. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the LBT failure information in response to a specific frequency band being FR 1/FR 2-1, includes second LBT failure number information corresponding to the downlink beam, and the second LBT failure number information corresponding to the downlink beam indicates the total number of LBT failures during the random access process.
  • the network device when accessing a service cell in the FR 1 band or the FR 2-1 band, the network device receives the second LBT failure number sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the downlink beam includes a downlink sub-beam
  • the downlink sub-beam is a beam that performs a random access attempt in at least one random access process corresponding to the same LBT failure recovery process.
  • the present disclosure can be directed to beams belonging to the same LBT failure recovery process, and the network device receives the corresponding LBT failure status sent by the terminal. This makes it unnecessary for the network device to receive the LBT failure status corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure status, and thus saving communication resources.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of partial bandwidth BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • the random access information includes third LBT failure number information, where the third LBT failure number information indicates the number of LBT failures in random access attempts made on random access resources associated with a downlink sub-beam.
  • the disclosed network is provided with a receiving terminal for the third LBT failure number information based on the same LBT failure recovery process, so that the network device does not need to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the LBT failure count information corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes a beam identifier determined by the terminal during a non-last random access process in the LBT failure recovery process.
  • the present disclosure can determine the beam identifier in the non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the configuration information instructs the terminal to perform LBT before sending data to a network device;
  • the random access information includes the first LBT failure number information and/or the third LBT failure number information; or, the random access information includes the second LBT failure number information and/or the third LBT failure number information.
  • the present disclosure includes LBT failure count information in the random access information only when the network device configures the terminal to perform LBT before sending data, so that the terminal does not need to report the LBT failure corresponding to each beam under any circumstances, reducing the communication cost of the terminal reporting the LBT failure, thereby saving communication resources.
  • Fig. 11 is a schematic diagram of another communication device according to an exemplary embodiment.
  • the device 500 is configured in a network device, and the device 500 includes: a receiving module 501, configured to receive random access information sent by a terminal to access a serving cell, and the random access information is used to describe at least one random access process corresponding to the terminal in the LBT failure recovery process.
  • the network device of the present invention receives random access information sent by the terminal for describing at least one random access process corresponding to the LBT failure recovery process, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • each random access process in the random access information includes at least one of the following: information corresponding to each random access attempt; a beam identifier corresponding to the random access attempt; a downlink reference signal received power DL RSRP of a synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; and subcarrier spacing SCS information of a partial bandwidth BWP.
  • the present disclosure provides a variety of different information that may be included in random access information, so that network equipment can better understand the process of random access of a terminal.
  • each random access process in the random access information does not include at least one of the following: information corresponding to each random access attempt; beam identifier corresponding to the random access attempt; downlink reference signal received power DL RSRP of the synchronization signal block SSB; frequency domain resource configuration information or subcarrier spacing information used by the random access process to send message 1 or message A; subcarrier spacing SCS information of the partial bandwidth BWP.
  • random access information may not include a variety of different information, so that the network device can better understand the process of random access of the terminal.
  • each random access process in the random access information is carried by random access common information RA-InformationCommon or a newly added information field.
  • the random access information disclosed in the present invention may be carried by or not by RA-InformationCommon, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • each random access attempt in each random access process in the random access information, the beam information corresponding to the random access attempt and/or the DL RSRP of the SSB are carried through the random access information list perRAInfoList or a newly added information field.
  • Part of the information in the random access information disclosed in the present invention may be carried by or not by perRAInfoList, so that the network device can receive random access information of various different information, so that the network device can better understand the process of random access of the terminal.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure count information corresponding to each beam can be carried through RA-InformationCommon or perRAInfoList, providing multiple ways for network devices to obtain the beam identifier and the LBT failure count information corresponding to each beam.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process and the number of LBT failures corresponding to each beam are carried through a newly added information field, RA-InformationCommon or perRAInfoList.
  • the beam identifier corresponding to the non-last random access process in the LBT failure recovery process disclosed in the present invention, and the LBT failure number information corresponding to each beam can be carried through or not through RA-InformationCommon or perRAInfoList, providing a variety of acquisition methods for network devices to obtain the beam identifier and the LBT failure number information corresponding to each beam.
  • the configuration information instructs the terminal to perform LBT before sending data to the network device;
  • the LBT failure information includes the beam identifier determined by the terminal in a non-last random access process in the LBT failure recovery process.
  • the present disclosure can determine the beam identifier in the non-last random access process in the LBT failure recovery process when the network device configures the terminal to perform LBT before sending data. This makes it unnecessary for the network device to receive the LBT failure corresponding to each beam reported by the terminal under any circumstances, thereby reducing the communication cost of reporting the LBT failure and saving communication resources.
  • the beam identifier includes an SSB identifier and/or a channel state information reference signal CSI-RS identifier.
  • the present disclosure provides a variety of different beam identification information so that the network device can obtain random access information corresponding to at least one random access process in the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 2-2 to access the service cell, includes first LBT failure number information, and the first LBT failure number information indicates the number of LBT failures of random access attempts on the downlink beam.
  • the network device When the present invention accesses a service cell on the FR 2-2 frequency band, the network device receives the first LBT failure number information sent by the terminal, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the random access information in response to the terminal adopting FR 1 or FR 2-1 to access the service cell, includes a second LBT failure number information; the second LBT failure number information is the LBT failure number information corresponding to each random access process, indicating the total number of LBT failures in the random access process; or, the second LBT failure number information is the LBT failure number information corresponding to each LBT failure recovery process, indicating the total number of LBT failures in all random access processes associated with the LBT failure recovery process.
  • the network device When the present invention accesses the service cell in the FR 1 frequency band or the FR 2-1 frequency band, the network device receives the number of second LBT failures sent by the terminal, so that the network device can obtain the random access information of at least one random access process corresponding to the LBT failure recovery process.
  • the various modules/units involved in the apparatus 400 and the apparatus 500 involved in the embodiments of the present disclosure are only exemplary and are not intended to be limiting.
  • the apparatus 400 in the embodiments of the present disclosure may also include a sending module and/or a processing module, etc.
  • the apparatus 500 may also include a sending module and/or a processing module, etc.
  • the various modules included in the apparatus 200 and the apparatus 300 may interact with each other and may also interact with other network element devices.
  • Fig. 12 is a schematic diagram of a communication device according to an exemplary embodiment.
  • the device 600 may be any terminal such as a mobile phone, a computer, a digital broadcast terminal, a message transceiver device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • device 600 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input/output (I/O) interface 612 , a sensor component 614 , and a communication component 616 .
  • a processing component 602 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input/output (I/O) interface 612 , a sensor component 614 , and a communication component 616 .
  • a processing component 602 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input/output (I/O) interface 612 , a sensor component 614 , and a communication component
  • the processing component 602 generally controls the overall operation of the device 600, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 602 may include one or more processors 620 to execute instructions to complete all or part of the steps of the above-mentioned method.
  • the processing component 602 may include one or more modules to facilitate the interaction between the processing component 602 and other components.
  • the processing component 602 may include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.
  • the memory 604 is configured to store various types of data to support operations on the device 600. Examples of such data include instructions for any application or method operating on the device 600, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power component 606 provides power to the various components of the device 600.
  • the power component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 600.
  • the multimedia component 608 includes a screen that provides an output interface between the device 600 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
  • the multimedia component 608 includes a front camera and/or a rear camera. When the device 600 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and the rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
  • the audio component 610 is configured to output and/or input audio signals.
  • the audio component 610 includes a microphone (MIC), and when the device 600 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 604 or sent via the communication component 616.
  • the audio component 610 also includes a speaker for outputting audio signals.
  • I/O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.
  • the sensor assembly 614 includes one or more sensors for providing various aspects of status assessment for the device 600.
  • the sensor assembly 614 can detect the open/closed state of the device 600, the relative positioning of components, such as the display and keypad of the device 600, and the sensor assembly 614 can also detect the position change of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, the orientation or acceleration/deceleration of the device 600, and the temperature change of the device 600.
  • the sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • the sensor assembly 614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 616 is configured to facilitate wired or wireless communication between the device 600 and other devices.
  • the device 600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the device 600 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • controllers microcontrollers, microprocessors, or other electronic components to perform the above methods.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, and the instructions can be executed by a processor 620 of the device 600 to perform the above method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
  • Fig. 13 is a schematic diagram of another communication device according to an exemplary embodiment.
  • the device 700 may be provided as a base station, or as a server.
  • the device 700 includes a processing component 722, which further includes one or more processors, and a memory resource represented by a memory 732 for storing instructions executable by the processing component 722, such as an application.
  • the application stored in the memory 732 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 722 is configured to execute instructions to perform the above method.
  • the device 700 may also include a power supply component 726 configured to perform power management of the device 700, a wired or wireless network interface 750 configured to connect the device 700 to a network, and an input/output (I/O) interface 758.
  • the device 700 may operate based on an operating system stored in the memory 732, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • the present disclosure further provides a communication system, which includes a terminal and a network device.
  • the terminal is used to execute any one of the methods described in FIG2 and FIG3 ;
  • the network device is used to execute any one of the methods described in FIG4 and FIG5 .
  • the present disclosure further provides a communication system, which includes a terminal and a network device, wherein the terminal is used to execute any one of the methods described in FIG6 ; and the network device is used to execute any one of the methods described in FIG7 .
  • the UE does not need to indicate the number of LBT failures per beam, but only needs to indicate the corresponding number of LBT failures based on each random access process.
  • the present invention can decide whether to report the number of LBT failures per beam based on whether directional LBT is adopted.
  • the present disclosure can record random access information of multiple random access processes associated with the LBT failure recovery process.
  • plural refers to two or more than two, and other quantifiers are similar thereto.
  • “And/or” describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B may represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the singular forms “a”, “the” and “the” are also intended to include plural forms, unless the context clearly indicates other meanings.
  • first, second, etc. are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, the expressions “first”, “second”, etc. can be used interchangeably.
  • the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开是关于一种通信方法、装置、设备及存储介质，包括：响应于终端采用特定频段接入服务小区，向网络设备发送随机接入信息，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败的LBT失败信息。通过在特定频段接入服务小区时，向网络设发送包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。

Description

一种通信方法、装置、设备及存储介质 技术领域
本公开涉及通信技术领域，尤其涉及一种通信方法、装置、设备及存储介质。
背景技术
目前在一些地区使用部分频段进行长期演进(long term evolution，LTE)或新无线网络(new radio，NR)的数据传输时，在发送数据前可以进行先听后发(listen before talk，LBT)。一般情况下，网络设备可以配置终端是否在发送数据前进行LBT，网络设备也可以配置终端是否要进行LBT失败检测与恢复。
终端通过随机接入的方式与网络设备建立连接，并向网络设备发送数据。在终端进行随机接入时可以被配置先进行LBT。当LBT成功后可以执行终端的随机接入。然而，目前终端发送的随机接入的信息会包含各个波束(beam)的LBT失败情况，使得通信成本较高。因此，如何保证发送LBT失败情况且降低通信成本，成为了亟需解决的问题。
发明内容
为克服相关技术中存在的问题，本公开提供一种通信方法、装置、设备及存储介质。
根据本公开实施例的第一方面，提供一种种通信方法，方法应用于终端，包括：响应于终端采用特定频段接入服务小区，向网络设备发送随机接入信息，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败信息。
在一个实施方式中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
在一个实施方式中，LBT失败信息包括第一LBT失败次数信息，第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一个实施方式中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一个实施方式中，响应于特定频段为FR 1/FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
在一个实施方式中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一个实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一个实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一个实施方式中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一个实施方式中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，方法还包括：基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
在一个实施方式中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
根据本公开实施例的第二方面，提供一种通信装置，方法应用于终端，包括：响应于终端接入服务小区，向网络设备发送随机接入信息，随机接入信息用于描述终端在先听后发LBT失败恢复流程中对应的至少一次随机接入过程。
在一个实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随 机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一个实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一个实施方式中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，方法还包括：基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
在一个实施方式中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一个实施方式中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
在一个实施方式中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
根据本公开实施例的第三方面，提供一种通信方法，方法应用于网络设备，包括：接 收终端发送的随机接入信息，其中，终端采用特定频段接入服务小区，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败信息。
在一个实施方式中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
在一个实施方式中，LBT失败信息包括第一LBT失败次数信息，第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一个实施方式中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一个实施方式中，响应于特定频段为FR 1/FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
在一个实施方式中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一个实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一个实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一个实施方式中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一个实施方式中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、 以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
在一个实施方式中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT；随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
根据本公开实施例的第四方面，提供一种通信方法，方法应用于网络设备，包括：接收终端接入服务小区所发送的随机接入信息，随机接入信息用于描述终端在先听后发LBT失败恢复流程中对应的至少一次随机接入过程。
在一个实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一个实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一个实施方式中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送 的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
在一个实施方式中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一个实施方式中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
在一个实施方式中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
根据本公开实施例的第五方面，提供一种通信装置，装置配置于终端，装置包括：发送模块，用于响应于终端采用特定频段接入服务小区，向网络设备发送随机接入信息，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败信息。
在一个实施方式中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
在一个实施方式中，LBT失败信息包括第一LBT失败次数信息，第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一个实施方式中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一个实施方式中，响应于特定频段为FR 1/FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
在一个实施方式中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一个实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率 DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一个实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一个实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一个实施方式中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一个实施方式中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一个实施方式中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，装置还包括：确定模块，用于基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
在一个实施方式中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
根据本公开实施例的第六方面，提供一种通信装置，装置配置于终端，装置包括：发送模块，用于响应于终端接入服务小区，向网络设备发送随机接入信息，随机接入信息用于描述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子 载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一种实施方式中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，装置还包括：确定模块，用于基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
在一种实施方式中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
在一种实施方式中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
根据本公开实施例的第七方面，提供一种通信装置，装置配置于网络设备，装置包括：接收模块，用于接收终端发送的随机接入信息，其中，终端采用特定频段接入服务小区，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败信息。
在一种实施方式中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
在一种实施方式中，LBT失败信息包括第一LBT失败次数信息，第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一种实施方式中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一种实施方式中，响应于特定频段为FR 1/FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
在一种实施方式中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一种实施方式中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一种实施方式中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一种实施方式中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一种实施方式中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
在一种实施方式中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送 数据前进行LBT；随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
根据本公开实施例的第八方面，提供一种通信装置，装置配置于网络设备，装置包括：接收模块，用于接收终端接入服务小区所发送的随机接入信息，随机接入信息用于描述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一种实施方式中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
在一种实施方式中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
在一种实施方式中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
根据本公开实施例的第九方面，提供一种通信设备，包括：处理器；用于存储处理器可执行指令的存储器；其中，处理器被配置为：执行第一方面中的任意一项方法。
根据本公开实施例的第十方面，提供一种通信设备，包括：处理器；用于存储处理器可执行指令的存储器；其中，处理器被配置为：执行第二方面中的任意一项方法。
根据本公开实施例的第十一方面，提供一种通信设备，包括：处理器；用于存储处理器可执行指令的存储器；其中，处理器被配置为：执行第三方面中的任意一项方法。
根据本公开实施例的第十二方面，提供一种通信设备，包括：处理器；用于存储处理器可执行指令的存储器；其中，处理器被配置为：执行第四方面中的任意一项方法。
根据本公开实施例的第十三方面，提供一种非临时性计算机可读存储介质，当存储介质中的指令由终端的处理器执行时，使得终端能够执行第一方面中的任意一项方法。
根据本公开实施例的第十四方面，提供一种非临时性计算机可读存储介质，当存储介质中的指令由终端的处理器执行时，使得终端能够执行第二方面中的任意一项方法。
根据本公开实施例的第十五方面，提供一种非临时性计算机可读存储介质，当存储介质中的指令由网络设备的处理器执行时，使得网络设备能够执行第三方面中的任意一项方法。
根据本公开实施例的第十六方面，提供一种非临时性计算机可读存储介质，当存储介质中的指令由网络设备的处理器执行时，使得网络设备能够执行第四方面中的任意一项方法。
本公开的实施例提供的技术方案可以包括以下有益效果：通过在特定频段接入服务小区时，向网络设发送包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种无线通信系统示意图。
图2是根据一示例性实施例示出的一种通信方法流程图。
图3是根据一示例性实施例示出的另一种通信方法流程图。
图4是根据一示例性实施例示出的又一种通信方法流程图。
图5是根据一示例性实施例示出的再一种通信方法流程图。
图6是根据一示例性实施例示出的另一种通信方法流程图。
图7是根据一示例性实施例示出的又一种通信方法流程图。
图8是根据一示例性实施例示出的一种通信装置示意图。
图9是根据一示例性实施例示出的另一种通信装置示意图。
图10是根据一示例性实施例示出的又一种通信装置示意图。
图11是根据一示例性实施例示出的再一种通信装置示意图。
图12是根据一示例性实施例示出的一种通信设备示意图。
图13是根据一示例性实施例示出的另一种通信设备示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。
本公开所涉及的通信方法可以应用于图1所示的无线通信系统100中。该网络系统可以包括网络设备110和终端120。可以理解的是，图1所示的无线通信系统仅是进行示意性说明，无线通信系统中还可包括其它网络设备，例如还可以包括核心网络设备、无线中继设备和无线回传设备等，在图1中未画出。本公开实施例对该无线通信系统中包括的网络设备数量和终端数量不做限定。
进一步可以理解的是，本公开实施例的无线通信系统，是一种提供无线通信功能的网络。无线通信系统可以采用不同的通信技术，例如码分多址(Code Division Multiple Access,CDMA)、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency-Division Multiple Access，OFDMA)、单载波频分多址(Single Carrier FDMA，SC-FDMA)、载波侦听多路访问/冲突避免(Carrier Sense  Multiple Access with Collision Avoidance)。根据不同网络的容量、速率、时延等因素可以将网络分为2G(英文：Generation)网络、3G网络、4G网络或者未来演进网络，如第五代无线通信系统(The 5th Generation Wireless Communication System，5G)网络，5G网络也可称为是NR。为了方便描述，本公开有时会将无线通信网络简称为网络。
进一步的，本公开中涉及的网络设备110也可以称为无线接入网络设备。该无线接入网络设备可以是：基站、演进型基站(evolved Node B，eNB)、家庭基站、无线保真(Wireless Fidelity，WIFI)系统中的接入点(Access Point，AP)、无线中继节点、无线回传节点、传输点(Transmission Point，TP)或者发送接收点(transmission and receiving point，TRP)等，还可以为NR系统中的gNB，或者，还可以是构成基站的组件或一部分设备等。当为车联网(V2X)通信系统时，网络设备还可以是车载设备。应理解，本公开的实施例中，对网络设备所采用的具体技术和具体设备形态不做限定。
进一步的，本公开中涉及的终端120，也可以称为终端设备、用户设备(User Equipment，UE)、移动台(Mobile Station，MS)、移动终端(Mobile Terminal，MT)等，是一种向用户提供语音和/或数据连通性的设备，例如，终端可以是具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：智能手机(Mobile Phone)、口袋计算机(Pocket Personal Computer，PPC)、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、笔记本电脑、平板电脑、可穿戴设备、或者车载设备等。此外，当为车联网(V2X)通信系统时，终端设备还可以是车载设备。应理解，本公开实施例对终端所采用的具体技术和具体设备形态不做限定。
本公开实施例中，网络设备110与终端120可以采用任意可行的无线通信技术以实现相互传输数据。其中，网络设备110向终端120发送数据所对应的传输通道称为下行信道(downlink，DL)，终端120向网络设备110发送数据所对应的传输通道称为上行信道(uplink，UL)。可以理解的是，本公开实施例中所涉及的网络设备可以是基站。当然网络设备还可以是其它任意可能的网络设备，终端可以是任意可能的终端，本公开不作限定。
目前，在一些地区使用部分频段进行LTE或NR的数据传输时，在发送数据前可以进行LBT。一般情况下，网络设备可以配置终端是否在发送数据前进行LBT，网络设备也可以配置终端是否要进行LBT失败检测与恢复。
如果网络设备为终端配置了进行LBT失败检测与恢复，终端在检测持续的LBT失败时，是以部分带宽(bandwidth part，BWP)为粒度进行检测的。对于特殊小区(special cell，SpCell)，如果在一个SpCell的一个BWP上检测到持续LBT失败(failure)，终端会切换到该SpCell的另外一个配置有物理随机接入信道(physical random access channel，PRACH) 资源的BWP上发起随机接入。其中，SpCell可以是主小区(primary cell，PCell)或主辅小区(primary secondary cell，PScell)。
同时，若持续(consistent)LBT failure没有取消，且如果终端有可用的(available)UL资源。终端可以生成一个LBT failure媒体接入控制元素(medium access control control element，MAC CE)。该MAC CE可以指示发生LBT failure的所有服务小区(serving cell)身份标识(identity document，id)。当然，如果随机接入失败，终端会再次选择另一个有PRACH资源的BWP发起随机接入。可以理解，只有随机接入成功的情况下，终端才会取消(cancel)SpCell上所有BWP上触发的consistent LBT failure。值得注意的是，LBT failure MAC CE的上报，并不会触发取消SpCell的各BWP上的consistent LBT failure。当终端尝试了serving cell的所有BWP后均发生consistent LBT failure，若serving cell为SpCell，终端的媒体接入控制(medium access control，MAC)层向无线资源控制(radio resource control，RRC)层指示LBT failure，以及终端声明(declare)主小区组(master cell group，MCG)或辅小区组(secondary cell group，SCG)无线链路失败(radio link failure，RLF)。
当前，终端可以在FR 1频段、FR 2-1频段和FR 2-2频段上接入NR小区，其各自的频率范围可以如表1所示出的。
Figure PCTCN2022131566-appb-000001
表1
其中，终端在FR 2-2频段上进行LBT与在FR 1频段和FR 2-1频段上进行LBT是存在一些区别的。因为FR 2-2频段相比于其它频段，其频率高很多。因此，终端在FR 2-2频段上进行的LBT是具有方向性的。即尽在一个方向上进行信号检测(sensing)。而在FR1频段和FR 2-1频段上，终端进行LBT是全向的，即360度对信号进行sensing。
对于方向性LBT，终端进行sensing的波束(beam)空间上需要能够覆盖终端传输所用的beam。终端上行发送所用的beam也取决于终端所选择的网络设备发送的下行beam。即终端在接收网络设备发送的下行beam时，会确定一个终端的接收beam。终端在接收网络设备下发的不同beam时，所使用的接收beam可以相同或者不同。当终端确定接收beam后，对支持beam通信(correspondence)的终端，则会使用该接收beam对应的发送beam 来发送数据。当终端更换所接收的网络设备下行beam时。终端的接收beam将发生变化。那么对应的发送beam就很有可能也发生变化。则终端sensing beam也将跟着变化。网络设备发送的下行beam可以通过同步信号块(synchronization signal block，SSB)和/或信道状态信息参考信号(channel state information-reference signal，CSI-RS)的索引(index)进行标识。因此，终端在使用网络设备发送的不同下行beam所关联的随机接入资源进行随机接入时，sensing beam可能会随选择的下行beam不同而不同。从而导致LBT的结果不同。因此有必要针对每个(per)beam指示对应的LBT失败情况。
但目前终端会针对各beam指示对应的LBT失败情况，而对于全向LBT，无论终端选择的下行beam是否变化，终端进行sensing beam都是全向的。终端的sensing结果不会变化。显然，当前的方式会使得通信成本较高。因此，如何保证发送LBT失败情况且降低通信成本，成为了亟需解决的问题。
因此，本公开提供了一种通信方法、装置、设备及存储介质，通过在特定频段接入服务小区时，向网络设发送包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
图2是根据一示例性实施例示出的一种通信方法流程图，如图2所示，该方法应用于终端，可以包括以下步骤：
在步骤S11中，响应于终端采用特定频段接入服务小区，向网络设备发送随机接入信息。
在一些实施例中，终端在响应于自身采用特定频段接入服务小区的情况下，可以向网络设备发送随机接入信息。该随机接入信息可以包括LBT失败信息。其中，LBT失败信息用于描述终端在随机接入过程中LBT失败的情况。
在一些实施例中，随机接入信息还可以包括其它任意在随机接入过程中可能涉及到的信息。
在一些实施例中，终端需要与网络设备进行通信时，终端可以采用特定频段向网络设备发起连接建立。在连接建立过程中，终端可以采用随机接入的方式与网络设备建立连接。而终端可能被配置在发送数据前先进行LBT。因此终端在随机接入开始前，先进行LBT检测。当检测LBT成功后进行随机接入，当随机接入成功后可以认为连接建立成功。终端可以在连接建立成功或者不成功的情况下，向网络设备发送随机接入信息。该随机接入信息可以包括任意在随机接入过程中可能涉及到的信息。如包括用于描述终端在随机接入过程中LBT失败的LBT失败信息。
例如，终端在向网络设备上报与随机接入相关的信息时，可以将随机接入信息记录在连接建立失败报告中。该连接建立失败报告为终端在连接建立失败时生成的。可以理解，上报即终端向网络设备发送信息、数据等。
又例如，在发生MCG RLF的情况下，如果RLF是因为随机接入失败导致，或者RLF因为终端切换服务小区失败导致，则可以在RLF报告中携带上述随机接入信息。RLF报告可以是发生MCG RLF的情况下终端生成的。
又例如，在发生SCG RLF的情况下，在SCG failure信息中携带上述随机接入信息。其中，SCG failure信息可以是发生SCG RLF的情况下终端生成的。
又例如，在终端随机接入成功的情况下，可以在用于描述随机接入成功的随机接入报告中携带上述随机接入信息。其中，用于描述随机接入成功的随机接入报告可以是在随机接入成功的情况下终端生成的。
又例如，在终端进行服务小区切换，并且切换成功的情况下，在切换成功报告中携带上述随机接入信息。其中，切换成功报告可以是在服务小区切换成功的情况下终端生成的。
又例如，当PScell添加或者改变成功的情况下，在PScell添加或者改变成功报告携带上述随机接入信息。其中，PScell添加或者改变成功报告可以是在PScell添加或者改变成功的情况下终端生成的。
本公开通过在特定频段接入服务小区时，向网络设备发送包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
在一些实施例中，响应于终端在FR 2-2接入服务小区的情况下，随机接入信息中的LBT失败信息为各下行波束对应的LBT失败信息。其中，下行波束为终端使用该波束关联的随机接入资源进行随机接入尝试的波束。
可以理解，当终端采用FR 2-2接入服务小区，终端在随机接入过程中进行LBT检测时是针对不同下行波束进行LBT检测。也就是说，终端是针对不同方向上的下行波束，分别进行LBT检测。也可以理解为，终端在不同方向上的下行波束上，利用相依波束关联的随机接入资源进行随机接入尝试，每次随机接入尝试中进行LBT检测。当终端检测到某个下行波束上LBT持续失败多次，则可以认为在该下行波束上LBT失败。其中，LBT连续失败的次数可以是预先设定，或者协议规定的，本公开不作限定。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送各下行波束对应的LBT失败信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，LBT失败信息还包括第一LBT失败次数信息。第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一些实施例中，终端发送的LBT失败信息可以包括第一LBT失败次数信息。该第一LBT失败次数信息表示终端使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。其中，一个第一LBT失败次数信息可以对应一个随机接入过程。
可以理解，一次随机接入过程中可以包括多次随机接入尝试，当随机接入尝试失败次数达到预设的失败尝试阈值时，可以认为本次随机接入过程失败。在一次随机接入尝试中可以进行一次或多次的LBT检测。当LBT失败次数达到LBT失败阈值时，可以认为本次随机接入尝试失败。
例如，在一次随机接入过程中，对于该随机接入过程中的各次随机接入尝试，可以记录随机接入尝试过程中发生LBT失败的次数。
如，LBT失败的次数可以是多个随机接入尝试对应LBT失败的总次数。又如，LBT失败的次数可以是基于各随机接入尝试，分别记录相应随机接入尝试的LBT失败次数。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送第一LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一些实施例中，终端发送的LBT失败信息可以包括波束标识。该波束标识可以是SSB标识和/或CSI-RS标识。其中，标识可以是id或者index。例如，SSB标识为SSB index；CSI-RS标识为CSI-RS index。可以理解，该波束标识所指示的波束，即上述提到的进行随机接入尝试的下行波束。
例如，在一次随机接入过程中，对于该随机接入过程中的各次随机接入尝试，可以按照时间先后顺序，终端记录随机接入尝试关联到的SSB和/或CSI-RS的随机接入资源对应的SSB index和/或CSI-RS index。如可以是连续多个随机接入尝试使用关联到的同一个SSB和/或CSI-RS的随机接入资源。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送波束标识，该波束标识指示 进行随机接入尝试的下行波束。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，响应于特定频段为FR 1或FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
在一些实施例中，响应于终端在FR 1频段或FR 2-1频段接入服务小区的情况下，随机接入信息中的LBT失败信息可以包括下行波束对应的第二LBT失败次数信息。该下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
可以理解，在FR 1频段或FR 2-1频段上进行LBT检测，可以是全向LBT。因此，LBT失败信息中可以不携带波束信息，并且无需记录各波束对应LBT失败次数。LBT失败信息中可以携带记录了随机接入过程中LBT失败的总次数第二LBT失败次数信息。其中，第二LBT失败次数可以对应该随机接入过程中所有随机接入尝试的LBT失败次数的总和。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，向网络设备发送第二LBT失败次数。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一些实施例中，下行波束中可以包括下行子波束。其中，下行子波束可以表示属于同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
例如，当终端发生连续LBT失败时，会通过切换BWP并发起新的随机接入尝试来进行LBT恢复。响应于终端在一次随机接入过程失败后，终端可以执行LBT失败恢复流程。如尝试切换另一BWP并再次发起新的随机接入过程，直至随机接入成功。或者所有可以尝试的BWP上均连续LBT失败，则终端触发RLF。显然，上述涉及到的随机接入过程均可以认为与同一个LBT失败恢复流程相关。
应当理解，若终端启动LBT失败恢复流程是基于随机接入过程触发的，则触发LBT失败恢复流程的随机接入过程也应当认为与该LBT失败恢复流程相关。
在一些实施例中，终端可以向网络设备发送随机接入信息，随机接入信息中LBT失败信息可以为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。例如，终端在FR 2-2上接入服务小区，或者终端在FR 1频段或FR 2-1频段上接入服务小区。
在一些实施例中，响应于随机接入信息中包括波束标识。该波束标识例如为SSB index 和/或CSI-RS index。可以理解，该实施例中的SSB index和/或CSI-RS index用于指示属于同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
例如。该实施例中的各个SSB index和/或CSI-RS index用于指示属于同一个LBT失败恢复流程对应的各次随机接入过程中进行随机接入尝试的波束，即下行子波束。相应的，下行子波束关联的随机接入资源对应的SSB和/或CSI-RS通过SSB index和/或CSI-RS index指示。
本公开可以针对属于同一个LBT失败恢复流程的波束，向网络设发送相应的LBT失败情况。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
其中，在一些实施例中，随机接入信息可以包括各次随机接入尝试对应的信息。
可以理解，随机接入信息中记录有各次随机接入尝试时相应的信息，例如时间戳、相应通信参数等等可能的信息。
在一些实施例中，随机接入信息可以包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以包括SSB的DL参考信号接收功率(reference signal receiving power，RSRP)。
在一些实施例中，随机接入信息可以包括随机接入过程发送消息(message，Msg)1或Msg A所使用的频域资源配置信息或子载波间隔信息。
可以理解，消息1为四步随机接入的第一步消息。消息A为两步随机接入的第一步消息。其中，Msg A的内容可以包含四步随机接入的Msg 1和Msg 3的内容。
在一些实施例中，随机接入信息可以包括BWP的子载波间隔(subcarrier spacing，SCS)信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一些实施例中，随机接入信息可以不包括各次随机接入尝试对应的信息。
在一些实施例中，随机接入信息可以不包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以不包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以不包括Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
在一些实施例中，随机接入信息可以不包括BWP的SCS信息。
本公开提供了随机接入信息可以不包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过随机接入公共信息(RA-InformationCommon)承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过新增的信息域承载。可以理解，该实施例即表示不通过RA-InformationCommon承载，而是选择新的信息域进行承载。例如该新的信息域可以承载随机接入信息中对应的各次随机接入过程所包含的多个信息。也可以每个新增的信息域单独承载随机接入信息中对应的各次随机接入过程所包含的一个信息。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过随机接入信息列表(perRAInfoList)承载
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机 接入尝试对应的波束信息和/或SSB的DL RSRP可以通过新增的信息域承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。例如该新的信息域可以承载随机接入信息中对应的各次随机接入过程所包含的各次随机接入尝试、随机接入尝试对应的波束信息、SSB的DL RSRP中的多个信息。也可以每个新增的信息域单独承载随机接入信息中对应的各次随机接入过程所包含的各次随机接入尝试、随机接入尝试对应的波束信息、SSB的DL RSRP中的一个信息。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一些实施例中，随机接入信息可以包括第三LBT失败信息。其中，第三LBT失败信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
例如，该实施例中的LBT失败次数，可以是多个随机接入尝试对应LBT失败的总次数。或者，LBT失败次数可以是基于各随机接入尝试，分别记录相应随机接入尝试的LBT失败次数。
本公开向网络设发送基于同一个LBT失败恢复流程的第三LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过RA-InformationCommon或perRAInfoList进行承载。
例如，在连接建立失败报告中，记录持续LBT失败触发的最后一个随机接入的perRAInfoList。
又例如，对RLF报告、切换成功报告、PSCell添加或改变报告中的一项或多项中，记录持续LBT失败触发的最后一个随机接入的RA-InformationCommon。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应 的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过新增的信息域、RA-InformationCommon或perRAInfoList承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。例如该新的信息域可以承载LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息中的多个信息。也可以每个新增的信息域单独承载LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息中的一个信息。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，图3是根据一示例性实施例示出的另一种通信方法流程图。响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，方法还可以包括以下步骤：
在步骤S21中，基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
在一些实施例中，终端可以接收到网络设备发送的配置信息。该配置信息用于指示终端向网络设备发送数据前进行LBT。终端可以基于该配置信息，在LBT失败恢复流程中非最后一次随机接入过程中确定波束标识。即下行子波束的波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT。随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
在一些实施例中，响应于终端接收到网络设备发送的配置信息，且配置信息指示终端向网络设备发送数据前进行LBT。随机接入信息可以包括第一LBT失败次数信息和/或第三LBT失败次数信息。
在一些实施例中，响应于终端接收到网络设备发送的配置信息，且配置信息指示终端向网络设备发送数据前进行LBT。随机接入信息可以包括第二LBT失败次数信息和/或第三LBT失败次数信息。
本公开仅当网络设备配置终端在发送数据前进行LBT的情况下，随机接入信息中包括LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
针对LBT失败恢复流程所管理的多个随机接入过程的随机接入信息，在相关技术中并没有一个很好的记录方式。因此，基于相同或相似的发明构思，本公开还提供了一种通信方法，通过向网络设备发送描述终端在LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
图4是根据一示例性实施例示出的又一种通信方法流程图，如图4所示，该方法应用于终端，可以包括以下步骤：
在步骤S31中，响应于终端接入服务小区，向网络设备发送随机接入信息。
在一些实施例中，响应于终端接入服务小区，终端可以向网络设备发送随机接入信息。该随机接入信息用于描述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
可以理解，该随机接入信息对应于同一个LBT失败恢复流程对应的至少一次随机接入过程。其中，若终端启动LBT失败恢复流程是基于随机接入过程触发的，则触发LBT失败恢复流程的随机接入过程也应当认为与该LBT失败恢复流程相关。
本公开通过向网络设备发送描述终端在LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
其中，在一些实施例中，随机接入信息可以包括各次随机接入尝试对应的信息。
可以理解，随机接入信息中记录有各次随机接入尝试时相应的信息，例如时间戳、相 应通信参数等等可能的信息。
在一些实施例中，随机接入信息可以包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以包括随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
可以理解，消息1为四步随机接入的第一步消息。消息A为两步随机接入的第一步消息。其中，Msg A的内容可以包含四步随机接入的Msg 1和Msg 3的内容。
在一些实施例中，随机接入信息可以包括BWP的SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一些实施例中，随机接入信息可以不包括各次随机接入尝试对应的信息。
在一些实施例中，随机接入信息可以不包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以不包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以不包括Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
在一些实施例中，随机接入信息可以不包括BWP的SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过RA-InformationCommon承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS 信息中的一项或多项。可以通过新增的信息域承载。可以理解，该实施例即表示不通过RA-InformationCommon承载，而是选择新的信息域进行承载。例如该新的信息域可以承载随机接入信息中对应的各次随机接入过程所包含的多个信息。也可以每个新增的信息域单独承载随机接入信息中对应的各次随机接入过程所包含的一个信息。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过perRAInfoList承载
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过新增的信息域承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。例如该新的信息域可以承载随机接入信息中对应的各次随机接入过程所包含的各次随机接入尝试、随机接入尝试对应的波束信息、SSB的DL RSRP中的多个信息。也可以每个新增的信息域单独承载随机接入信息中对应的各次随机接入过程所包含的各次随机接入尝试、随机接入尝试对应的波束信息、SSB的DL RSRP中的一个信息。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过RA-InformationCommon或perRAInfoList进行承载。
例如，在连接建立失败报告中，记录持续LBT失败触发的最后一个随机接入的perRAInfoList。
又例如，对RLF报告、切换成功报告、PSCell添加或改变报告中的一项或多项中，记 录持续LBT失败触发的最后一个随机接入的RA-InformationCommon。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过新增的信息域、RA-InformationCommon或perRAInfoList承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。例如该新的信息域可以承载LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息中的多个信息。也可以每个新增的信息域单独承载LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息中的一个信息。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，图5是根据一示例性实施例示出的再一种通信方法流程图。响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，方法还可以包括以下步骤：
在步骤S41中，基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
在一些实施例中，终端可以接收到网络设备发送的配置信息。该配置信息用于指示终端向网络设备发送数据前进行LBT。终端可以基于该配置信息，在LBT失败恢复流程中非最后一次随机接入过程中确定波束标识。即下行子波束的波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一些实施例中，终端发送的LBT失败信息可以包括波束标识。该波束标识可以是 SSB标识和/或CSI-RS标识。其中，标识可以是id或者index。例如，SSB标识为SSB index；CSI-RS标识为CSI-RS index。可以理解，该波束标识所指示的波束，即上述提到的进行随机接入尝试的下行波束。
例如，在一次随机接入过程中，对于该随机接入过程中的各次随机接入尝试，可以按照时间先后顺序，终端记录随机接入尝试关联到的SSB和/或CSI-RS的随机接入资源对应的SSB index和/或CSI-RS index。如可以是连续多个随机接入尝试使用关联到的同一个SSB和/或CSI-RS的随机接入资源。
本公开提供了多种不同的波束标识信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
在一些实施例中，响应于终端在FR 2-2频段接入服务小区的情况下，终端发送的随机接入信息可以包括第一LBT失败次数信息。该第一LBT失败次数信息表示终端使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。其中，一个第一LBT失败次数信息可以对应一个随机接入过程。
可以理解，一次随机接入过程中可以包括多次随机接入尝试，当随机接入尝试失败次数达到预设的失败尝试阈值时，可以认为本次随机接入过程失败。在一次随机接入尝试中可以进行一次或多次的LBT检测。当LBT失败次数达到LBT失败阈值时，可以认为本次随机接入尝试失败。
例如，在一次随机接入过程中，对于该随机接入过程中的各次随机接入尝试，可以记录随机接入尝试过程中发生LBT失败的次数。
如，LBT失败的次数可以是多个随机接入尝试对应LBT失败的总次数。又如，LBT失败的次数可以是基于各随机接入尝试，分别记录相应随机接入尝试的LBT失败次数。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送第一LBT失败次数信息。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关 联的所有随机接入流程中LBT失败的总次数。
在一些实施例中，响应于终端在FR 1频段或FR 2-1频段接入服务小区的情况下，随机接入信息可以包括第二LBT失败次数信息。第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，向网络设备发送第二LBT失败次数。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
基于相同构思，本公开还提供了应用于网络设备的通信方法。
图6是根据一示例性实施例示出的另一种通信方法流程图，如图6所示，该方法应用于网络设备，可以包括以下步骤：
在步骤S51中，接收终端发送的随机接入信息。
在一些实施例中，网络设备可以接收终端发送的随机接入信息。其中，终端采用特定频段接入服务小区，随机接入信息包括用于描述终端在随机接入过程中LBT失败信息。
在一些实施例中，随机接入信息还可以包括其它任意在随机接入过程中可能涉及到的信息。
本公开通过在特定频段接入服务小区时，网络设备接收终端发送的包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
在一些实施例中，响应于终端在FR 2-2接入服务小区的情况下，随机接入信息中的LBT失败信息为各下行波束对应的LBT失败信息。其中，下行波束为终端使用该波束关联的随机接入资源进行随机接入尝试的波束。
可以理解，当终端采用FR 2-2接入服务小区，终端在随机接入过程中进行LBT检测时是针对不同下行波束进行LBT检测。也就是说，终端是针对不同方向上的下行波束，分别进行LBT检测。也可以理解为，终端在不同方向上的下行波束上，利用相依波束关联的随机接入资源进行随机接入尝试，每次随机接入尝试中进行LBT检测。当终端检测到某个下行波束上LBT持续失败多次，则可以认为在该下行波束上LBT失败。其中，LBT连 续失败的次数可以是预先设定，或者协议规定的，本公开不作限定。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的各下行波束对应的LBT失败信息。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，LBT失败信息还包括第一LBT失败次数信息。第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一些实施例中，网络设备接收的LBT失败信息可以包括第一LBT失败次数信息。该第一LBT失败次数信息表示终端使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。其中，一个第一LBT失败次数信息可以对应一个随机接入过程。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的第一LBT失败次数信息。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一些实施例中，网络设备接收的LBT失败信息可以包括波束标识。该波束标识可以是SSB标识和/或CSI-RS标识。其中，标识可以是id或者index。例如，SSB标识为SSB index；CSI-RS标识为CSI-RS index。可以理解，该波束标识所指示的波束，即上述提到的进行随机接入尝试的下行波束。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的波束标识，该波束标识指示进行随机接入尝试的下行波束。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，响应于特定频段为FR 1或FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
在一些实施例中，响应于终端在FR 1频段或FR 2-1频段接入服务小区的情况下，随机接入信息中的LBT失败信息可以包括下行波束对应的第二LBT失败次数信息。该下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，网络设备接收终端发送的第二LBT失败次数。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT 失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一些实施例中，下行波束中可以包括下行子波束。其中，下行子波束可以表示属于同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
在一些实施例中，随机接入信息中LBT失败信息可以为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。例如，终端在FR 2-2上接入服务小区，或者终端在FR 1频段或FR 2-1频段上接入服务小区。
在一些实施例中，响应于随机接入信息中包括波束标识。该波束标识例如为SSB index和/或CSI-RS index。可以理解，该实施例中的SSB index和/或CSI-RS index用于指示属于同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
本公开可以针对属于同一个LBT失败恢复流程的波束，网络设备接收终端发送的相应的LBT失败情况。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
其中，在一些实施例中，随机接入信息可以包括各次随机接入尝试对应的信息。
可以理解，随机接入信息中记录有各次随机接入尝试时相应的信息，例如时间戳、相应通信参数等等可能的信息。
在一些实施例中，随机接入信息可以包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以包括随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
可以理解，消息1为四步随机接入的第一步消息。消息A为两步随机接入的第一步消息。其中，Msg A的内容可以包含四步随机接入的Msg 1和Msg 3的内容。
在一些实施例中，随机接入信息可以包括BWP的SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以不包括以 下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一些实施例中，随机接入信息可以不包括各次随机接入尝试对应的信息。
在一些实施例中，随机接入信息可以不包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以不包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以不包括Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
在一些实施例中，随机接入信息可以不包括BWP的SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过RA-InformationCommon承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过新增的信息域承载。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过perRAInfoList承载
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过新增的信息域承载。可以理解， 该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
在一些实施例中，随机接入信息可以包括第三LBT失败信息。其中，第三LBT失败信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
本公开网络设接收终端发送的基于同一个LBT失败恢复流程的第三LBT失败次数信息。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过RA-InformationCommon或perRAInfoList进行承载。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过新增的信息域、RA-InformationCommon或perRAInfoList承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
在一些实施例中，网络设备可以向终端发送配置信息。该配置信息用于指示终端向网络设备发送数据前进行LBT。网络设备接收的LBT失败信息可以包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识，即下行子波束的波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT。随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
在一些实施例中，响应于向终端发送配置信息，且配置信息指示终端向网络设备发送数据前进行LBT。随机接入信息可以包括第一LBT失败次数信息和/或第三LBT失败次数信息。
在一些实施例中，响应于向终端发送配置信息，且配置信息指示终端向网络设备发送数据前进行LBT。随机接入信息可以包括第二LBT失败次数信息和/或第三LBT失败次数信息。
本公开仅当网络设备配置终端在发送数据前进行LBT的情况下，随机接入信息中包括LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
图7是根据一示例性实施例示出的又一种通信方法流程图，如图7所示，该方法应用于网络设备，可以包括以下步骤：
在步骤S61中，接收终端接入服务小区所发送的随机接入信息。
在一些实施例中，响应于终端接入服务小区，网络设备可以接收终端发送的随机接入信息。该随机接入信息用于描述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
本公开网络设备接收终端发送的用于描述在LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少 一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
其中，在一些实施例中，随机接入信息可以包括各次随机接入尝试对应的信息。
可以理解，随机接入信息中记录有各次随机接入尝试时相应的信息，例如时间戳、相应通信参数等等可能的信息。
在一些实施例中，随机接入信息可以包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以包括随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
可以理解，消息1为四步随机接入的第一步消息。消息A为两步随机接入的第一步消息。其中，Msg A的内容可以包含四步随机接入的Msg 1和Msg 3的内容。
在一些实施例中，随机接入信息可以包括BWP的subcarrier spacing，SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程可以不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
在一些实施例中，随机接入信息可以不包括各次随机接入尝试对应的信息。
在一些实施例中，随机接入信息可以不包括随机接入尝试对应的LBT失败信息。
在一些实施例中，随机接入信息可以不包括SSB的DL RSRP。
在一些实施例中，随机接入信息可以不包括Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息。
在一些实施例中，随机接入信息可以不包括BWP的SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过RA-InformationCommon承载。
在一些实施例中，随机接入信息中对应的各次随机接入过程所包含的信息，例如各次随机接入尝试对应的信息；随机接入尝试对应的LBT失败信息；SSB的DL RSRP；随机接入过程发送Msg 1或Msg A所使用的频域资源配置信息或子载波间隔信息；BWP的SCS信息中的一项或多项。可以通过新增的信息域承载。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过perRAInfoList承载
在一些实施例中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP可以通过新增的信息域承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
本公开实施例提供的通信方法中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过RA-InformationCommon或perRAInfoList进行承载。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
在一些实施例中，针对LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，可以通过新增的信息域、RA-InformationCommon或perRAInfoList承载。可以理解，该实施例即表示不通过perRAInfoList承载，而是选择新的信息域进行承载。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
本公开实施例提供的通信方法中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
在一些实施例中，网络设备可以向终端发送配置信息。该配置信息用于指示终端向网络设备发送数据前进行LBT。网络设备接收的LBT失败信息可以包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识，即下行子波束的波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
本公开实施例提供的通信方法中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
在一些实施例中，终端发送的LBT失败信息可以包括波束标识。该波束标识可以是SSB标识和/或CSI-RS标识。其中，标识可以是id或者index。例如，SSB标识为SSB index；CSI-RS标识为CSI-RS index。可以理解，该波束标识所指示的波束，即上述提到的进行随机接入尝试的下行波束。
本公开提供了多种不同的波束标识信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
在一些实施例中，响应于终端在FR 2-2频段接入服务小区的情况下，终端发送的随机接入信息可以包括第一LBT失败次数信息。该第一LBT失败次数信息表示终端使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。其中，一个第一LBT失败次数信息可以对应一个随机接入过程。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的第一LBT失败次数信息。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
本公开实施例提供的通信方法中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
在一些实施例中，响应于终端在FR 1频段或FR 2-1频段接入服务小区的情况下，随机接入信息可以包括第二LBT失败次数信息。第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，网络设备接收终端发送发第二LBT失败次数。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
需要说明的是，本领域内技术人员可以理解，本公开实施例上述涉及的各种实施方式/实施例中可以配合前述的实施例使用，也可以是独立使用。无论是单独使用还是配合前述的实施例一起使用，其实现原理类似。本公开实施中，部分实施例中是以一起使用的实施方式进行说明的。当然，本领域内技术人员可以理解，这样的举例说明并非对本公开实施例的限定。
基于相同的构思，本公开实施例还提供一种通信装置、设备。
可以理解的是，本公开实施例提供的通信装置、设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本公开实施例中所公开的各示例的单元及算法步骤，本公开实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但 是这种实现不应认为超出本公开实施例的技术方案的范围。
图8是根据一示例性实施例示出的一种通信装置示意图。参照图8，该装置200配置于终端，装置200包括：发送模块201，用于响应于终端采用特定频段接入服务小区，向网络设备发送随机接入信息，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败信息。
本公开通过在特定频段接入服务小区时，向网络设备发送包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送各下行波束对应的LBT失败信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，LBT失败信息包括第一LBT失败次数信息，第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送第一LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送波束标识，该波束标识指示进行随机接入尝试的下行波束。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，响应于特定频段为FR 1/FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，向网络设备发送第二LBT失败次数。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
本公开可以针对属于同一个LBT失败恢复流程的波束，向网络设发送相应的LBT失败情况。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
本公开向网络设发送基于同一个LBT失败恢复流程的第三LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，装置200还包括：确定模块202，用于基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，响应于接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
本公开仅当网络设备配置终端在发送数据前进行LBT的情况下，随机接入信息中包括LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
图9是根据一示例性实施例示出的另一种通信装置示意图。参照图9，该装置300配置于终端，装置300包括：发送模块301，用于响应于终端接入服务小区，向网络设备发送随机接入信息，随机接入信息用于描述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
本公开通过向网络设备发送描述终端在LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次 随机接入过程的随机接入信息。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得向网络设备发送包括多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最 后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT，装置300还包括：确定模块302，用于基于配置信息，在LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
在一种实施方式中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
本公开提供了多种不同的波束标识信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
本公开在FR 2-2频段上接入服务小区时，向网络设备发送第一LBT失败次数信息。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
在一种实施方式中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，向网络设备发送第二LBT失败次数。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
图10是根据一示例性实施例示出的又一种通信装置示意图。参照图10，该装置400配置于网络设备，装置400包括：接收模块401，用于接收终端发送的随机接入信息，其 中，终端采用特定频段接入服务小区，随机接入信息包括用于描述终端在随机接入过程中先听后发LBT失败信息。
本公开通过在特定频段接入服务小区时，网络设备接收终端发送的包含LBT失败情况的随机接入信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，响应于特定频段为频率范围FR 2-2，LBT失败信息为各下行波束对应的LBT失败信息，终端利用下行波束关联的随机接入资源进行随机接入尝试。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的各下行波束对应的LBT失败信息。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，LBT失败信息包括第一LBT失败次数信息，第一LBT失败次数信息表示使用下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的第一LBT失败次数信息。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，LBT失败信息包括波束标识，波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的波束标识，该波束标识指示进行随机接入尝试的下行波束。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，响应于特定频段为FR 1/FR 2-1，LBT失败信息包括下行波束对应的第二LBT失败次数信息，下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，网络设备接收终端发送的第二LBT失败次数。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，下行波束包括下行子波束，下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
本公开可以针对属于同一个LBT失败恢复流程的波束，网络设备接收终端发送的相应的LBT失败情况。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT 失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息包括第三LBT失败次数信息，第三LBT失败次数信息表示在下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
本公开网络设接收终端发送的基于同一个LBT失败恢复流程的第三LBT失败次数信息。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，响应于向终端发送配置信息，配置信息指示终端向网络设备发送数据前进行LBT；随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
本公开仅当网络设备配置终端在发送数据前进行LBT的情况下，随机接入信息中包括LBT失败次数信息。使得终端无需在任何情况下均上报各个波束对应的LBT失败情况，降低了终端上报LBT失败情况的通信成本，进而节约了通信资源。
图11是根据一示例性实施例示出的再一种通信装置示意图。参照图11，该装置500配置于网络设备，装置500包括：接收模块501，用于接收终端接入服务小区所发送的随机接入信息，随机接入信息用于描述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
本公开网络设备接收终端发送的用于描述在LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
在一种实施方式中，随机接入信息中的各次随机接入过程包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号 接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以包括的多种不同信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程不包括以下至少一项：各次随机接入尝试对应的信息；随机接入尝试对应的波束标识；同步信号块SSB的下行参考信号接收功率DL RSRP；随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；部分带宽BWP的子载波间隔SCS信息。
本公开提供了随机接入信息可以不包括多种不同的信息，使得网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
本公开的随机接入信息可以通过或不通过RA-InformationCommon承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，随机接入信息中的各次随机接入过程中的各次随机接入尝试、随机接入尝试对应的波束信息和/或SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
本公开随机接入信息中的部分信息可以通过或不通过perRAInfoList承载，使得网络设备可以接收多种不同信息的随机接入信息，以便网络设备可以更了解终端进行随机接入的过程。
在一种实施方式中，响应于终端采用频率范围FR 2-2接入服务小区，LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息可以通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
本公开LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对 应的LBT失败次数信息可以通过或不通过RA-InformationCommon或perRAInfoList承载，为网络设备获取波束标识、以及各波束对应的LBT失败次数信息提供了多种获取方式。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，配置信息指示终端向网络设备发送数据前进行LBT；LBT失败信息包括终端在LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
本公开可以在网络设备配置终端在发送数据前进行LBT的情况下，确定LBT失败恢复流程中非最后一次随机接入过程中的波束标识。使得网络设备无需在任何情况下均接收终端上报的各个波束对应的LBT失败情况，降低了上报LBT失败情况的通信成本，进而节约了通信资源。
在一种实施方式中，波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
本公开提供了多种不同的波束标识信息，以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
在一种实施方式中，响应于终端采用FR 2-2接入服务小区，随机接入信息包括第一LBT失败次数信息，第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
本公开在FR 2-2频段上接入服务小区时，网络设备接收终端发送的第一LBT失败次数信息。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
在一种实施方式中，响应于终端采用FR 1或FR 2-1接入服务小区，随机接入信息包括第二LBT失败次数信息；第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
本公开在FR 1频段或FR 2-1频段上接入服务小区时，网络设备接收终端发送发第二LBT失败次数。以使得网络设备可以获取到LBT失败恢复流程中对应的至少一次随机接入过程的随机接入信息。
其中，需要说明的是，本公开实施例涉及的装置400和装置500中涉及的各个模块/单元，仅是进行示例性说明，并不引以为限。例如，本公开实施例中的装置400还可以包括发送模块和/或处理模块等。装置500还可以包括发送模块和/或处理模块等。其中，装置200和装置300中所包括的各模块之间可以进行交互，也可以与其它网元设备进行交互。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实 施例中进行了详细描述，此处将不做详细阐述说明。
图12是根据一示例性实施例示出的一种通信设备示意图。例如，设备600可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等任意终端。
参照图12，设备600可以包括以下一个或多个组件：处理组件602，存储器604，电力组件606，多媒体组件608，音频组件610，输入/输出(I/O)接口612，传感器组件614，以及通信组件616。
处理组件602通常控制设备600的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件602可以包括一个或多个处理器620来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件602可以包括一个或多个模块，便于处理组件602和其他组件之间的交互。例如，处理组件602可以包括多媒体模块，以方便多媒体组件608和处理组件602之间的交互。
存储器604被配置为存储各种类型的数据以支持在设备600的操作。这些数据的示例包括用于在设备600上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器604可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电力组件606为设备600的各种组件提供电力。电力组件606可以包括电源管理系统，一个或多个电源，及其他与为设备600生成、管理和分配电力相关联的组件。
多媒体组件608包括在所述设备600和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件608包括一个前置摄像头和/或后置摄像头。当设备600处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件610被配置为输出和/或输入音频信号。例如，音频组件610包括一个麦克风(MIC)，当设备600处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器604或经由通信 组件616发送。在一些实施例中，音频组件610还包括一个扬声器，用于输出音频信号。
I/O接口612为处理组件602和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件614包括一个或多个传感器，用于为设备600提供各个方面的状态评估。例如，传感器组件614可以检测到设备600的打开/关闭状态，组件的相对定位，例如所述组件为设备600的显示器和小键盘，传感器组件614还可以检测设备600或设备600一个组件的位置改变，用户与设备600接触的存在或不存在，设备600方位或加速/减速和设备600的温度变化。传感器组件614可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件614还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件614还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件616被配置为便于设备600和其他设备之间有线或无线方式的通信。设备600可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件616经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件616还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，设备600可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器604，上述指令可由设备600的处理器620执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
图13是根据一示例性实施例示出的另一种通信设备示意图。
例如，设备700可以被提供为一基站，或者是服务器。参照图13，设备700包括处理组件722，其进一步包括一个或多个处理器，以及由存储器732所代表的存储器资源，用于存储可由处理组件722执行的指令，例如应用程序。存储器732中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件722被配置为执行指令，以执行上述方法。
设备700还可以包括一个电源组件726被配置为执行设备700的电源管理，一个有线或无线网络接口750被配置为将设备700连接到网络，和一个输入输出(I/O)接口758。设备700可以操作基于存储在存储器732的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
在一个实施例中，例如图1示出的，本公开还提供了一种通信系统，该通信系统包括终端和网络设备。其中，终端用于执行图2、图3中描述的任意一种方法；网络设备用于执行图4、图5中描述的任意一种方法。
在一个实施例中，例如图1示出的，本公开还提供了一种通信系统，该通信系统包括终端和网络设备。其中，终端用于执行图6中描述的任意一种方法；网络设备用于执行图7中描述的任意一种方法。
本公开中UE无需per beam指示LBT失败次数，仅需基于各随机接入过程指示对应的LBT失败次数即可。
本公开可以依据是否采用方向性LBT来决定是否上报per beam的LBT失败次数。
本公开可以记录在LBT失败恢复流程所关联的多个随机接入过程的随机接入信息。
进一步可以理解的是，本公开中“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
进一步可以理解的是，术语“第一”、“第二”等用于描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开，并不表示特定的顺序或者重要程度。实际上，“第一”、“第二”等表述完全可以互换使用。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。
进一步可以理解的是，本公开中涉及到的“响应于”“如果”等词语的含义取决于语境以及实际使用的场景，如在此所使用的词语“响应于”可以被解释成为“在……时”或“当……时”或“如果”或“若”。
进一步可以理解的是，本公开实施例中尽管在附图中以特定的顺序描述操作，但是不应将其理解为要求按照所示的特定顺序或是串行顺序来执行这些操作，或是要求执行全部所示的操作以得到期望的结果。在特定环境中，多任务和并行处理可能是有利的。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实 施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利范围来限制。

Claims (59)

  1. 一种通信方法，其特征在于，所述方法应用于终端，包括：
    响应于所述终端采用特定频段接入服务小区，向网络设备发送随机接入信息，所述随机接入信息包括用于描述所述终端在随机接入过程中先听后发LBT失败信息。
  2. 根据权利要求1所述的方法，其特征在于，响应于所述特定频段为频率范围FR 2-2，所述LBT失败信息为各下行波束对应的LBT失败信息，所述终端利用所述下行波束关联的随机接入资源进行随机接入尝试。
  3. 根据权利要求2所述的方法，其特征在于，所述LBT失败信息包括第一LBT失败次数信息，所述第一LBT失败次数信息表示使用所述下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
  4. 根据权利要求2或3所述的方法，其特征在于，所述LBT失败信息包括波束标识，所述波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
  5. 根据权利要求1所述的方法，其特征在于，响应于所述特定频段为FR 1/FR 2-1，所述LBT失败信息包括下行波束对应的第二LBT失败次数信息，所述下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
  6. 根据权利要求2-5中任意一项所述的方法，其特征在于，所述下行波束包括下行子波束，所述下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
  7. 根据权利要求6所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  8. 根据权利要求6所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程不包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  9. 根据权利要求7或8所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
  10. 根据权利要求7或8所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程中的所述各次随机接入尝试、所述随机接入尝试对应的波束信息和/或所述SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
  11. 根据权利要求6-10中任意一项所述的方法，其特征在于，所述随机接入信息包括第三LBT失败次数信息，所述第三LBT失败次数信息表示在所述下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
  12. 根据权利要求6-11中任意一项所述的方法，其特征在于，所述LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
  13. 根据权利要求6-12中任意一项所述的方法，其特征在于，所述LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
  14. 根据权利要求6-13中任意一项所述的方法，其特征在于，响应于接收到网络设备发送的配置信息，所述配置信息指示所述终端向所述网络设备发送数据前进行LBT，所述方法还包括：
    基于所述配置信息，在所述LBT失败恢复流程中非最后一次随机接入过程中，确定波束标识。
  15. 根据权利要求1-14中任意一项所述的方法，其特征在于，响应于接收到网络设备发送的配置信息，所述配置信息指示所述终端向所述网络设备发送数据前进行LBT；
    所述随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，
    所述随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
  16. 一种通信方法，其特征在于，所述方法应用于终端，包括：
    响应于所述终端接入服务小区，向网络设备发送随机接入信息，所述随机接入信息用于描述所述终端在先听后发LBT失败恢复流程中对应的至少一次随机接入过程。
  17. 根据权利要求16所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    同步信号块SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  18. 根据权利要求16所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程不包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    同步信号块SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  19. 根据权利要求17或18所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
  20. 根据权利要求17或18所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程中的所述各次随机接入尝试、所述随机接入尝试对应的波束信息和/或所述SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
  21. 根据权利要求17-20中任意一项所述的方法，其特征在于，响应于所述终端采用频率范围FR 2-2接入服务小区，所述LBT失败恢复流程中最后一次随机接入过程对应的所述波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
  22. 根据权利要求17-21中任意一项所述的方法，其特征在于，响应于所述终端采用FR 2-2接入服务小区，所述LBT失败恢复流程中非最后一次随机接入过程对应的所述波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
  23. 根据权利要求17-22中任意一项所述的方法，其特征在于，响应于所述终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，所述配置信息指示所述终端向所述网络设备发送数据前进行LBT，所述方法还包括：
    基于所述配置信息，在所述LBT失败恢复流程中非最后一次随机接入过程中，确定所述波束标识。
  24. 根据权利要求17-23中任意一项所述的方法，其特征在于，所述波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
  25. 根据权利要求16-24中任意一项所述的方法，其特征在于，响应于所述终端采用FR 2-2接入服务小区，所述随机接入信息包括第一LBT失败次数信息，所述第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
  26. 根据权利要求16-25中任意一项所述的方法，其特征在于，响应于所述终端采用FR 1或FR 2-1接入服务小区，所述随机接入信息包括第二LBT失败次数信息；
    所述第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，
    所述第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与所述LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
  27. 一种通信方法，其特征在于，所述方法应用于网络设备，包括：
    接收终端发送的随机接入信息，其中，所述终端采用特定频段接入服务小区，所述随机接入信息包括用于描述所述终端在随机接入过程中先听后发LBT失败信息。
  28. 根据权利要求27所述的方法，其特征在于，响应于所述特定频段为频率范围FR2-2，所述LBT失败信息为各下行波束对应的LBT失败信息，所述终端利用所述下行波束关联的随机接入资源进行随机接入尝试。
  29. 根据权利要求28所述的方法，其特征在于，所述LBT失败信息包括第一LBT失败次数信息，所述第一LBT失败次数信息表示使用所述下行波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
  30. 根据权利要求28或29所述的方法，其特征在于，所述LBT失败信息包括波束标识，所述波束标识为同步信号块SSB标识和/或信道状态信息参考信号CSI-RS标识。
  31. 根据权利要求27所述的方法，其特征在于，响应于所述特定频段为FR 1/FR 2-1，所述LBT失败信息包括下行波束对应的第二LBT失败次数信息，所述下行波束对应的第二LBT失败次数信息表示在随机接入过程中LBT失败的总次数。
  32. 根据权利要求28-31中任意一项所述的方法，其特征在于，所述下行波束包括下行子波束，所述下行子波束为同一个LBT失败恢复流程对应的至少一次随机接入过程中进行随机接入尝试的波束。
  33. 根据权利要求32所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  34. 根据权利要求32所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程不包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  35. 根据权利要求33或34所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
  36. 根据权利要求33或34所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程中的所述各次随机接入尝试、所述随机接入尝试对应的波束信息和/或所述SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
  37. 根据权利要求32-36中任意一项所述的方法，其特征在于，所述随机接入信息包括第三LBT失败次数信息，所述第三LBT失败次数信息表示在所述下行子波束关联的随机接入资源进行随机接入尝试的LBT失败次数。
  38. 根据权利要求32-37中任意一项所述的方法，其特征在于，所述LBT失败恢复流程中最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
  39. 根据权利要求32-38中任意一项所述的方法，其特征在于，所述LBT失败恢复流程中非最后一次随机接入过程对应的波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon或perRAInfoList承载。
  40. 根据权利要求32-39中任意一项所述的方法，其特征在于，响应于向所述终端发送配置信息，所述配置信息指示所述终端向所述网络设备发送数据前进行LBT；
    所述LBT失败信息包括所述终端在所述LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
  41. 根据权利要求27-40中任意一项所述的方法，其特征在于，响应于向所述终端发送配置信息，所述配置信息指示所述终端向所述网络设备发送数据前进行LBT；
    所述随机接入信息包括第一LBT失败次数信息和/或第三LBT失败次数信息；或者，
    所述随机接入信息包括第二LBT失败次数信息和/或第三LBT失败次数信息。
  42. 一种通信方法，其特征在于，所述方法应用于网络设备，包括：
    接收终端接入服务小区所发送的随机接入信息，所述随机接入信息用于描述所述终端在先听后发LBT失败恢复流程中对应的至少一次随机接入过程。
  43. 根据权利要求42所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    同步信号块SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  44. 根据权利要求42所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程不包括以下至少一项：
    各次随机接入尝试对应的信息；
    随机接入尝试对应的波束标识；
    同步信号块SSB的下行参考信号接收功率DL RSRP；
    随机接入过程发送消息1或消息A所使用的频域资源配置信息或子载波间隔信息；
    部分带宽BWP的子载波间隔SCS信息。
  45. 根据权利要求43或44所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程通过随机接入公共信息RA-InformationCommon或新增的信息域承载。
  46. 根据权利要求43或44所述的方法，其特征在于，所述随机接入信息中的各次随机接入过程中的所述各次随机接入尝试、所述随机接入尝试对应的波束信息和/或所述SSB的DL RSRP，通过随机接入信息列表perRAInfoList或新增的信息域承载。
  47. 根据权利要求43-46中任意一项所述的方法，其特征在于，响应于所述终端采用频率范围FR 2-2接入服务小区，所述LBT失败恢复流程中最后一次随机接入过程对应的所述波束标识、以及各波束对应的LBT失败次数信息，通过RA-InformationCommon或perRAInfoList承载。
  48. 根据权利要求43-47中任意一项所述的方法，其特征在于，响应于所述终端采用FR 2-2接入服务小区，所述LBT失败恢复流程中非最后一次随机接入过程对应的所述波束标识、以及各波束对应的LBT失败次数信息，通过新增的信息域、RA-InformationCommon 或perRAInfoList承载。
  49. 根据权利要求43-48中任意一项所述的方法，其特征在于，响应于所述终端采用FR 2-2接入服务小区，以及接收到网络设备发送的配置信息，所述配置信息指示所述终端向所述网络设备发送数据前进行LBT；
    所述LBT失败信息包括所述终端在所述LBT失败恢复流程中非最后一次随机接入过程中确定的波束标识。
  50. 根据权利要求43-49中任意一项所述的方法，其特征在于，所述波束标识包括SSB标识和/或信道状态信息参考信号CSI-RS标识。
  51. 根据权利要求42-50中任意一项所述的方法，其特征在于，响应于所述终端采用FR 2-2接入服务小区，所述随机接入信息包括第一LBT失败次数信息，所述第一LBT失败次数信息表示在下行波束上进行随机接入尝试的LBT失败次数。
  52. 根据权利要求42-51中任意一项所述的方法，其特征在于，响应于所述终端采用FR 1或FR 2-1接入服务小区，所述随机接入信息包括第二LBT失败次数信息；
    所述第二LBT失败次数信息为各随机接入过程对应的LBT失败次数信息，表示在随机接入过程中LBT失败的总次数；或，
    所述第二LBT失败次数信息为各LBT失败恢复流程对应的LBT失败次数信息，表示在与所述LBT失败恢复流程关联的所有随机接入流程中LBT失败的总次数。
  53. 一种通信装置，其特征在于，所述装置配置于终端，所述装置包括：
    发送模块，用于响应于所述终端采用特定频段接入服务小区，向网络设备发送随机接入信息，所述随机接入信息包括用于描述所述终端在随机接入过程中先听后发LBT失败信息。
  54. 一种通信装置，其特征在于，所述装置配置于终端，所述装置包括：
    发送模块，用于响应于所述终端接入服务小区，向网络设备发送随机接入信息，所述随机接入信息用于描述所述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
  55. 一种通信装置，其特征在于，所述装置配置于网络设备，所述装置包括：
    接收模块，用于接收终端发送的随机接入信息，其中，所述终端采用特定频段接入服务小区，所述随机接入信息包括用于描述所述终端在随机接入过程中先听后发LBT失败信息。
  56. 一种通信装置，其特征在于，所述装置配置于网络设备，所述装置包括：
    接收模块，用于接收终端接入服务小区所发送的随机接入信息，所述随机接入信息用于描述所述终端在LBT失败恢复流程中对应的至少一次随机接入过程。
  57. 一种通信设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：执行权利要求1至52中任意一项所述的方法。
  58. 一种非临时性计算机可读存储介质，当所述存储介质中的指令由终端的处理器执行时，使得所述终端能够执行权利要求1至26中任意一项所述的方法。
  59. 一种非临时性计算机可读存储介质，当所述存储介质中的指令由网络设备的处理器执行时，使得所述网络设备能够执行权利要求27至52中任意一项所述的方法。
PCT/CN2022/131566 2022-11-11 2022-11-11 一种通信方法、装置、设备及存储介质 WO2024098433A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/131566 WO2024098433A1 (zh) 2022-11-11 2022-11-11 一种通信方法、装置、设备及存储介质
CN202280004970.1A CN115997465A (zh) 2022-11-11 2022-11-11 一种通信方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/131566 WO2024098433A1 (zh) 2022-11-11 2022-11-11 一种通信方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024098433A1 true WO2024098433A1 (zh) 2024-05-16

Family

ID=85990625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/131566 WO2024098433A1 (zh) 2022-11-11 2022-11-11 一种通信方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN115997465A (zh)
WO (1) WO2024098433A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113196851A (zh) * 2019-07-18 2021-07-30 Oppo广东移动通信有限公司 信息上报方法及相关设备
CN114503775A (zh) * 2022-01-12 2022-05-13 北京小米移动软件有限公司 一种确定先听后说失败的方法及装置
US20220322452A1 (en) * 2019-12-26 2022-10-06 Huawei Technologies Co., Ltd. Communication method and system, and device
US20220353914A1 (en) * 2020-08-27 2022-11-03 Zte Corporation Method and apparatus related to direction-based listen before talk

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113196851A (zh) * 2019-07-18 2021-07-30 Oppo广东移动通信有限公司 信息上报方法及相关设备
US20220322452A1 (en) * 2019-12-26 2022-10-06 Huawei Technologies Co., Ltd. Communication method and system, and device
US20220353914A1 (en) * 2020-08-27 2022-11-03 Zte Corporation Method and apparatus related to direction-based listen before talk
CN114503775A (zh) * 2022-01-12 2022-05-13 北京小米移动软件有限公司 一种确定先听后说失败的方法及装置

Also Published As

Publication number Publication date
CN115997465A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
US11711131B2 (en) Information transmission method and information transmission device
US20220232637A1 (en) Random access method and device
CN108496385B (zh) 信息上报方法及装置和基于带宽部分的操作方法及装置
CN110785958B (zh) 传输配置状态激活方法、装置及存储介质
CN109314875B (zh) 辅服务小区波束失败的上报方法，装置和存储介质
CN112543485B (zh) 语音通话控制方法、装置及存储介质
WO2022141405A1 (zh) 资源集合配置方法、装置及存储介质
CN113994765B (zh) 一种bwp切换方法、装置及存储介质
CN108702689B (zh) 小区接入方法、装置及存储介质
WO2024098433A1 (zh) 一种通信方法、装置、设备及存储介质
CN114902730A (zh) 信息传输方法、装置、通信设备和存储介质
CN114503648A (zh) 提早识别的方法、装置、通信设备及存储介质
WO2024087258A1 (zh) 波束失败检测参考信号资源的确定方法、装置及存储介质
WO2024092584A1 (zh) 一种通信方法、装置、设备及存储介质
RU2793334C1 (ru) Способ и устройство для активирования состояния индикатора конфигурации передачи и носитель информации
US20240172006A1 (en) Method and apparatus for beam recovery, communication device and storage medium
WO2024130590A1 (zh) 一种传输配置指示状态的确定方法、装置及存储介质
WO2024082314A1 (zh) 传输配置指示状态的确定方法、装置及存储介质
WO2024113189A1 (zh) 小数据传输sdt方法、装置、通信设备及存储介质
WO2024082312A1 (zh) 传输配置指示状态的确定方法、装置及存储介质
US12035354B2 (en) Method for processing data, communication device and storage medium
CN112673702B (zh) 随机接入方法、装置及存储介质
WO2024065467A1 (zh) 测量间隔配置方法以及装置、通信设备及存储介质
WO2023206036A1 (zh) 一种随机接入的方法、装置、设备及存储介质
WO2022077234A1 (zh) 下行控制信息调度方法、装置及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22964901

Country of ref document: EP

Kind code of ref document: A1