WO2021056296A1 - 一种信息处理方法、终端设备 - Google Patents

一种信息处理方法、终端设备 Download PDF

Info

Publication number
WO2021056296A1
WO2021056296A1 PCT/CN2019/107973 CN2019107973W WO2021056296A1 WO 2021056296 A1 WO2021056296 A1 WO 2021056296A1 CN 2019107973 W CN2019107973 W CN 2019107973W WO 2021056296 A1 WO2021056296 A1 WO 2021056296A1
Authority
WO
WIPO (PCT)
Prior art keywords
lbt failure
lbt
terminal device
time period
counter
Prior art date
Application number
PCT/CN2019/107973
Other languages
English (en)
French (fr)
Inventor
石聪
田文强
吴作敏
付喆
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2019/107973 priority Critical patent/WO2021056296A1/zh
Priority to CN201980095356.9A priority patent/CN113678559A/zh
Publication of WO2021056296A1 publication Critical patent/WO2021056296A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • the present invention relates to the field of information processing technology, and in particular to an information processing method, terminal equipment, chip, computer readable storage medium, computer program product, and computer program.
  • uplink transmission if the network is configured for repeated transmission of authorized resources, or when the transmission resource cycle of the scheduling request configured by the network is relatively small, or the cycle of channel state information reporting resources is relatively small, a large number of upstream upstream may be reported in a short time. Failed event of transmission after listening (LBT, Listen before talk). In this way, due to the intensive uplink transmission of New Radio (NR), it is easy to cause the terminal device to fail to trigger the LBT, thereby reducing system performance.
  • LBT Long Term Evolution
  • NR New Radio
  • embodiments of the present invention provide an information processing method, terminal equipment, chip, computer-readable storage medium, computer program product, and computer program.
  • an information processing method includes:
  • the terminal device obtains the LBT failure indication for the BWP of the uplink bandwidth part
  • the terminal device controls the LBT failure counter to perform counting processing based on a first time period; wherein, the first time period is used to control the number of counts of the LBT failure counter;
  • the terminal device Based on the count value of the LBT failure counter, it is determined whether the terminal device has sustained LBT failure in the uplink BWP.
  • a terminal device including:
  • the processing unit obtains the LBT failure indication for the uplink bandwidth part BWP; controls the LBT failure counter to perform counting processing based on the first time period; wherein the first time period is used to control the number of counts of the LBT failure counter; Based on the count value of the LBT failure counter, it is determined whether a continuous LBT failure occurs in the uplink BWP.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation manners.
  • a chip is provided to implement the methods in the foregoing implementation manners.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the method in the above-mentioned first aspect or its various implementation manners.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute the method in the above-mentioned first aspect or each of its implementation manners.
  • a computer program product including computer program instructions that cause a computer to execute the method in the first aspect or its implementation manners.
  • a computer program which when running on a computer, causes the computer to execute the method in the first aspect or its implementation manners.
  • the counting process of the LBT failure indication is controlled according to the first time period, so as to determine whether a continuous LBT failure occurs according to the count value of the failure counter of the final LBT failure indication.
  • the increase of the count value of the LBT failure counter it is possible to avoid triggering LBT failures too frequently, thereby improving system performance.
  • FIG. 1 is a schematic diagram 1 of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of an information processing method provided by an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of the structure of a terminal device provided by an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of the composition structure of a communication device provided by an embodiment of the present invention.
  • FIG. 5 is a schematic block diagram of a chip provided by an embodiment of the present application.
  • FIG. 6 is a second schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 applied in the embodiment of the present application may be as shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.
  • the network equipment 110 may be a network equipment (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a network equipment (NodeB, NB) in a WCDMA system, or an evolution in an LTE system Type network equipment (Evolutional Node B, eNB or eNodeB), or a wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment may be a mobile switching center, a relay station, an access point, In-vehicle devices, wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • NB network equipment
  • Evolutional Node B eNodeB
  • eNodeB LTE system Type network equipment
  • CRAN Cloud Radio Access Network
  • the network equipment may be a mobile switching center, a relay station, an access point, In-
  • the communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110.
  • the "terminal equipment” used here includes but is not limited to connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, and direct cable connection ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal” or a "mobile terminal”.
  • direct terminal connection (Device to Device, D2D) communication may be performed between the terminal devices 120.
  • NR is in the unlicensed frequency band, including the following working scenarios:
  • Scenario A Carrier aggregation scenario, the primary cell (PCell) is a licensed spectrum, and secondary cells (SCell) working on unlicensed spectrum are aggregated through carrier aggregation;
  • PCell primary cell
  • SCell secondary cells
  • Scenario B dual-connection working scenario
  • PCell is LTE licensed spectrum
  • PScell is New Radio (NR, New Radio) unlicensed spectrum
  • Scenario C Independent work scenario, NR works as an independent cell in an unlicensed spectrum
  • Scenario D NR single cell scenario, the uplink (UL) works in the licensed spectrum, and the downlink (DL) works in the unlicensed spectrum;
  • Scenario E Dual-connection working scenario, PCell is NR licensed spectrum, and PScell is NR unlicensed spectrum.
  • the working frequency band (Band) of NR-U is 5GHz unlicensed spectrum and 6GHz unlicensed spectrum.
  • the design of NR-U should ensure fairness with other systems that are already working on these unlicensed spectrums, such as WiFi.
  • the principle of fairness is that the impact of NR-U on systems that have been deployed on unlicensed spectrum (such as WiFi) cannot exceed the impact between these systems.
  • the general energy detection mechanism is the LBT mechanism, and the basic principle of the mechanism is that the base station or terminal (transmitting end) needs to listen for a period of time according to regulations before transmitting data on the unlicensed spectrum. If the listening result indicates that the channel is idle, the transmitting end can transmit data to the receiving end. If the listening result indicates that the channel is in an occupied state, the transmitting end needs to back off for a period of time according to regulations before continuing to listen to the channel, knowing that the channel listening result is in an idle state, before transmitting data to the receiving end.
  • Scheduling request used to request uplink resources
  • PRACH Physical Random Access Channel, physical random access channel
  • RACH random access channel
  • Physical Uplink Shared Channel (PUSCH, Physical Uplink Shared Channel) transmission including uplink data transmission based on configured grant and uplink data transmission based on dynamic grant;
  • PUSCH Physical Uplink Shared Channel
  • Physical layer signaling transmission including acknowledgement (ACK)/non-acknowledgement (NACK) feedback, channel state information (CSI, Channel State Information) reporting, etc.;
  • ACK acknowledgement
  • NACK non-acknowledgement
  • CSI Channel State Information
  • MAC Media Access Control
  • the MAC layer also maintains a counter to count the number of PRACH failures, PREAMBLE_TRANSMISSION_COUNTER. When the counter reaches the configured threshold, the terminal device will trigger the radio link failure and initiate the RRC re-establishment process;
  • the terminal device For the uplink transmission based on the configured authorized resource (configured grant), the terminal device does not maintain a counter. If the data transmission fails, the network will schedule a retransmission. For RLC (Radio Link Control, radio link layer control) AM mode, there will be a counter at the RLC layer. When the retransmission counter reaches the maximum number of times, RLF will also be triggered. For the RLC UM mode, it relies on the retransmission mechanism of the MAC and physical layer.
  • RLC Radio Link Control, radio link layer control
  • the terminal device On the unlicensed frequency band, the terminal device needs to use LBT to monitor whether the channel is available before transmitting SR, PRACH or PUSCH. If it is not available, that is, LBT fails, the terminal device needs to wait until the next transmission opportunity to perform LBT again.
  • a mechanism will be designed at the MAC layer to deal with the problem of UL LBT failure.
  • Uplink continuous LBT problem detection will consider LBT failures caused by all types of uplink transmissions; at the same time, the recovery mechanism triggered by LBT failures caused by any type of uplink transmission is the same;
  • the network configures a threshold, and the MAC layer of the terminal device records the number of LBT failures. When this threshold is reached, the terminal device triggers a continuous LBT failure event;
  • the terminal device resets the counter, and starts or restarts when the LBT fails.
  • the mechanism is basically the same as the beam failure recovery (BFR, beam failure recovery) mechanism.
  • BFR beam failure recovery
  • uplink transmission there is burst transmission.
  • the network is configured with authorized resources configured grant/dynamic grant repetition transmission, or when the network configured SR transmission resource period is relatively small, or the CSI report resource If the cycle is relatively small, the terminal device may report a large number of dense upstream LBT failure events in a short period of time. In this way, when the network configuration threshold is relatively small, the terminal device will trigger the continuous LBT failure prematurely.
  • the problem with prematurely triggering continuous LBT failure is that it is possible that the current unlicensed channel is only occupied by the different system for a short period of time, but due to its own NR uplink intensive transmission, the terminal device triggers the LBT failure, thereby reducing system performance.
  • this embodiment provides a solution to control the counting of LBT failure indications in the first time period by increasing the first time period, so as to reduce the triggering of LBT failure.
  • an embodiment of the present invention provides an information processing method, as shown in FIG. 2, including:
  • Step 21 The terminal device obtains a listen before transmission (LBT, Listen before talk) failure indication for the uplink bandwidth part (BWP, BandWidth Part);
  • LBT listen before transmission
  • BWP BandWidth Part
  • Step 22 The terminal device controls the LBT failure counter to perform counting processing based on the first time period; wherein the first time period is used to control the number of counts of the LBT failure counter;
  • Step 23 Based on the count value of the LBT failure counter, determine whether the terminal device has sustained LBT failure in the uplink BWP.
  • the terminal device may be a mobile terminal in a communication system.
  • the foregoing terminal device obtaining the LBT failure indication for the uplink bandwidth part may be the terminal device obtaining the LBT failure indication for the uplink BWP sent by the lower layer.
  • the lower layer may be the physical layer.
  • the terminal device may obtain the LBT failure indication for the uplink BWP from the physical layer through the MAC entity.
  • the terminal device first needs to obtain the configuration information related to the LBT failure configured by the higher layer. Specifically, the terminal device obtains the configuration information related to the LBT failure of the RRC layer.
  • the failure-related configuration information includes:
  • the threshold of the number of LBT failures is used to control that when the number of LBT failures received by the MAC layer reaches the threshold, a continuous LBT failure event can be triggered;
  • the length of the first time period may be realized by setting a filter window, or may be realized by the timing duration of the first timer. For example, you can set the duration of the filter window.
  • the MAC layer of the terminal device does not count the number of LBT failures during the first time period, that is, the time period when the filtering window/first timer is running.
  • LBT_Failure_Counter an LBT failure counter
  • the behavior of the MAC layer of the terminal device may include:
  • the LBT failure counter is not counted if the time when the terminal device obtains the LBT failure indication for the uplink BWP is within the first time period
  • the MAC layer of the terminal device judges whether it is in the first time period, that is, whether it is in the filtering window, or whether the first timer is running, if the received LBT failure indication is within the filtering window/or the first If a timer is running, the terminal device ignores the LBT failure indication, that is, LBT_Failure_Counter is not updated;
  • the terminal device determines whether the time when the terminal device obtains the LBT failure indication for the uplink BWP is within the first time period. If the time when the terminal device obtains the LBT failure indication for the uplink BWP is not within the first time period, it controls the count value of the LBT failure counter to increase by 1, and at the same time turns on all The first time period.
  • the processing for the terminal device to start the first time period may include: controlling the MAC layer of the terminal device to start a filtering window/or controlling to start a first timer.
  • the terminal device can be controlled based on the first time period before entering the first time period and within the duration of the first time period, only based on the received LBT failure indication on the LBT failure counter.
  • the count value is increased by 1, and the LBT failure event will not be triggered prematurely due to more LBT failure indications.
  • the terminal device After controlling the LBT failure counter to increase by 1, the terminal device determines whether the count value of the LBT failure counter is greater than or equal to a preset LBT failure count threshold;
  • the terminal device determines that a continuous LBT failure occurs in the corresponding uplink BWP.
  • the LBT failure counter can also be reconfigured. Specifically, reconfiguration can occur in the following situations:
  • the LBT failure counter is reset.
  • the LBT failure counter may be reset when the LBT success indication is received
  • the LBT failure counter may be reset when the uplink transmission is successful.
  • the uplink transmission is successful without an LBT success indication, but when the uplink transmission is actually performed, the LBT failure indication is not received, then the uplink transmission can be considered as successful.
  • the terminal device when the terminal device performs uplink transmission, it can perform any of PRACH transmission, PUSCH transmission, and SR transmission. If after completing the uplink transmission, the corresponding LBT failure indication is not received, then it can be considered as uplink transmission. If the transmission is successful, the LBT failure counter can be cleared to 0 at this time.
  • the LBT failure counter can be reset when the relevant configuration information is reconfigured for the upper layer.
  • the high-level LBT failure-related configuration information when the high-level LBT failure-related configuration information is reconfigured, it may include at least one of the following reconfigurations: the threshold of the number of LBT failures, and the length of the first time period.
  • the length of the first time period may be: the length of the filtering window, or the timing duration of the first timer.
  • the LBT failure counter can be reset, that is, cleared to 0; or, if the corresponding parameter reconfiguration occurs, then the LBT also needs to fail When the counter is reset, it is cleared to 0.
  • the LBT success indication may be obtained from the physical layer by the MAC layer of the terminal device.
  • the filter window or the first timer can also be stopped, that is, if the LBT failure counter is cleared to 0, then the next step can be entered.
  • the filter window or the first timer can also be stopped, that is, if the LBT failure counter is cleared to 0, then the next step can be entered.
  • the implementation in the related protocol can be as follows:
  • the MAC entity shall (the processing performed by the MAC entity):
  • LBT_COUNTER> lbtFailureInstanceMaxCount (if LBT-COUNTER is greater than the preset number of LBT failure thresholds (i.e. lbtFailureInstanceMaxCount)):
  • Window/Timer or lbtFailureInstanceMaxCount is reconfigured by upper layers (if the upper layer reconfigures the filter window or the first timer or the threshold of the number of LBT failures); or
  • this example adds an LBT failure indication timer.
  • the LBT failure indication timer is used to control the recording of the number of LBT failures within this duration. If this duration is exceeded, then It can be considered that the number of LBT failures does not need to be recorded jointly with this LBT failure, or the LBT failure indication received after the task exceeds this duration is not related to the LBT failure indication within this duration, and the recording can be restarted. In this way, it is possible to reduce the problem of frequent LBT failure triggers due to the LBT failure that occurs after a period of time is also recorded.
  • the failure-related configuration information includes:
  • the threshold of the number of LBT failures, the length of the first time period, and the LBT failure indication timer is the threshold of the number of LBT failures, the length of the first time period, and the LBT failure indication timer.
  • the LBT failure indication timer can be implemented by a preset window or a second timer duration.
  • the LBT failure indication timer within this time period, the terminal device can consider that the LBT failure indication is continuous/related. That is, the time interval between LBT failure indications controlled by the LBT failure indication timer cannot be too long, if it is too long, it can be considered that it is not a continuous or related LBT failure indication.
  • the behavior of the terminal device MAC layer is as follows:
  • the LBT failure counter is not counted
  • the count value of the LBT failure counter is controlled to increase by 1, and the terminal device starts the first time period at the same time.
  • the terminal device when the terminal device is turned on for the first time period, the terminal device starts or restarts the LBT failure indication timer.
  • the MAC layer of the terminal device starts/restarts LBT_Detection_Timer (LBT failure indication timer);
  • the MAC layer of the terminal device determines whether the filtering window/timer is running. If the received LBT failure indication is within the filtering window/Timer is running, the terminal device ignores the LBT failure indication, that is, LBT_Failure_Counter is not updated; if it is received The LBT failure indication is not within the filter window/Timer is not running, then:
  • the terminal device can trigger a continuous LBT failure event, that is, the terminal device can perform the LBT failure recovery process;
  • the MAC layer of the terminal device starts the filtering window/Timer
  • the relevant configuration information is reconfigured, such as the network reconfiguration LBT failure threshold, and/or reconfiguration filter window/timer length, and/or reconfiguration LBT_Detection_Timer; or LBT_Detection_Timer timeout, or when the terminal MAC
  • the MAC layer of the terminal device resets the LBT_Failure_Counter and stops the filtering window/Timer.
  • the LBT failure indication timer when the LBT failure indication is received, if it does not enter the first time period, the first time period is turned on, and the LBT failure indication timer is turned on; in this way, it is realized that there will be no increase in the first time period
  • the count value of the LBT failure counter even if the first time period is over, the LBT failure indication is received, and the count value of the LBT failure counter is increased, and the count value of the LBT failure counter will be reset with the LBT failure indication timer. In this way, it is possible to further avoid the situation of relatively intensive uplink transmission, which may easily lead to the triggering of the LBT failure event.
  • the MAC entity shall (the processing performed by the MAC entity):
  • LBT_COUNTER> lbtFailureInstanceMaxCount (if LBT-COUNTER is greater than the preset number of LBT failure thresholds (i.e. lbtFailureInstanceMaxCount)):
  • lbtFailureDetectionTimer or lbtFailureInstanceMaxCount is reconfigured by upper layers (or if the upper layer reconfigures the LBT failure indication timer or the threshold of the number of LBT failures); or
  • the counting process of the LBT failure indication is controlled according to the first time period, so as to determine whether a continuous LBT failure occurs according to the count value of the failure counter of the final LBT failure indication.
  • the increase of the count value of the LBT failure counter it is possible to avoid triggering LBT failures too frequently, thereby improving system performance.
  • the embodiment of the present invention provides a terminal device, as shown in FIG. 3, including:
  • the processing unit 31 obtains the listen before transmission (LBT, Listen before talk) failure indication for the uplink bandwidth part (BWP, BandWidth Part), and controls the LBT failure counter to perform counting processing based on the first time period; wherein, the first time period A period of time is used to control the number of counts of the LBT failure counter; based on the count value of the LBT failure counter, it is determined whether a continuous LBT failure occurs in the uplink BWP.
  • LBT listen before transmission
  • BWP BandWidth Part
  • the terminal device may be a mobile terminal in a communication system.
  • the processing unit 31 obtains the LBT failure indication for the uplink BWP from the lower layer.
  • the lower layer may be the physical layer.
  • the terminal device may obtain the LBT failure indication for the uplink BWP from the physical layer through the MAC entity.
  • the processing unit 31 first needs to obtain the configuration information related to the LBT failure configured by the higher layer. Specifically, the terminal device obtains the configuration information related to the LBT failure of the RRC layer.
  • the failure-related configuration information includes:
  • the threshold of the number of LBT failures and the length of the first time period is the threshold of the number of LBT failures and the length of the first time period
  • the threshold of the number of LBT failures is used to control when the number of LBT failures received by the MAC layer reaches the threshold, the continuous LBT failure event can be triggered;
  • the length of the first time period can be implemented by setting a filter window, or can be implemented by the timing duration of the first timer. For example, you can set the duration of the filter window.
  • the MAC layer of the terminal device does not count the number of LBT failures during the first time period, that is, the time period when the filtering window/first timer is running.
  • the behavior of the MAC layer of the terminal device may include:
  • the processing unit 31 obtains the LBT failure indication for the uplink BWP within the first time period, it does not count the LBT failure counter;
  • the MAC layer of the terminal device judges whether it is in the first time period, that is, whether it is in the filtering window, or whether the first timer is running, if the received LBT failure indication is within the filtering window/or the first If a timer is running, the terminal device ignores the LBT failure indication, that is, LBT_Failure_Counter is not updated;
  • the processing unit 31 if the time when the LBT failure indication for the uplink BWP is acquired is not within the first time period, it controls the count value of the LBT failure counter to increase by 1, and at the same time turns on the first time period. segment.
  • the processing unit 31 determines whether the count value of the LBT failure counter is greater than or equal to a preset LBT failure count threshold; if it is greater than or equal to the preset LBT failure count threshold, it is determined that a continuous BWP occurs in the corresponding bandwidth portion LBT failed.
  • the LBT failure counter can also be reconfigured. Specifically, reconfiguration can occur in the following situations:
  • the high-level LBT failure-related configuration information when it is reconfigured, it may include at least one of the following reconfigurations: the threshold of the number of LBT failures, and the length of the first time period.
  • the length of the first time period may be: the length of the filtering window, or the timing duration of the first timer.
  • this example adds an LBT failure indication timer.
  • the LBT failure indication timer is used to control the recording of the number of LBT failures within this duration. If this duration is exceeded, then It can be considered that the number of LBT failures does not need to be recorded jointly with this LBT failure, or the LBT failure indication received after the task exceeds this duration is not related to the LBT failure indication within this duration, and the recording can be restarted. In this way, it is possible to reduce the problem of frequent LBT failure triggers due to the LBT failure that occurs after a period of time is also recorded.
  • the failure-related configuration information includes:
  • the threshold of the number of LBT failures, the length of the first time period, and the LBT failure indication timer is the threshold of the number of LBT failures, the length of the first time period, and the LBT failure indication timer.
  • the LBT failure indication timer can be implemented by a preset window or a second timer duration.
  • the LBT failure indication timer within this time period, the terminal device can consider that the LBT failure indication is continuous/related. That is, the time interval between LBT failure indications controlled by the LBT failure indication timer cannot be too long, if it is too long, it can be considered that it is not the LBT failure indication corresponding to the same event.
  • the behavior of the terminal device MAC layer is as follows:
  • the processing unit 31 when obtaining the LBT failure indication for the uplink BWP, does not count the LBT failure counter within the first time period;
  • the processing unit 31 when obtaining the LBT failure indication for the uplink BWP, is not within the first time period, controls the count value of the LBT failure counter to increase by 1, and at the same time the terminal device starts the first time period.
  • the difference from the foregoing example is that the processing unit 31 of this example starts or restarts the LBT failure indication timer when the first time period is started.
  • the counting process of the LBT failure indication is controlled according to the first time period, so as to determine whether a continuous LBT failure occurs according to the count value of the failure counter of the final LBT failure indication.
  • the increase of the count value of the LBT failure counter it is possible to avoid triggering LBT failures too frequently, thereby improving system performance.
  • FIG. 4 is a schematic structural diagram of a communication device 900 provided by an embodiment of the present invention.
  • the communication device in this embodiment may be specifically the terminal device in the foregoing embodiment.
  • the communication device 900 shown in FIG. 4 includes a processor 910, and the processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present invention.
  • the communication device 900 may further include a memory 920.
  • the processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiment of the present invention.
  • the memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.
  • the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 930 may include a transmitter and a receiver.
  • the transceiver 930 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 900 may specifically be a network device in an embodiment of the present invention, and the communication device 900 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present invention. For brevity, details are not repeated here. .
  • the communication device 900 may specifically be a satellite or a network device according to the embodiment of the present invention, and the communication device 900 may implement the corresponding procedures implemented by the mobile terminal/satellite in each method of the embodiment of the present invention. For the sake of brevity, I won't repeat them here.
  • Fig. 5 is a schematic structural diagram of a chip according to an embodiment of the present invention.
  • the chip 1000 shown in FIG. 5 includes a processor 1010, and the processor 1010 can call and run a computer program from the memory to implement the method in the embodiment of the present invention.
  • the chip 1000 may further include a memory 1020.
  • the processor 1010 can call and run a computer program from the memory 1020 to implement the method in the embodiment of the present invention.
  • the memory 1020 may be a separate device independent of the processor 1010, or may be integrated in the processor 1010.
  • the chip 1000 may further include an input interface 1030.
  • the processor 1010 can control the input interface 1030 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1000 may further include an output interface 1040.
  • the processor 1010 can control the output interface 1040 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present invention, and the chip can implement the corresponding process implemented by the satellite in each method of the embodiment of the present invention.
  • the chip can implement the corresponding process implemented by the satellite in each method of the embodiment of the present invention.
  • the chip mentioned in the embodiment of the present invention may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • the processor in the embodiment of the present invention may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present invention may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present invention may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on.
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • SDRAM Synchronous dynamic random access memory
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • synchronous connection Dynamic random access memory switch link DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • FIG. 6 is a schematic block diagram of a communication system 800 provided by an embodiment of the present application. As shown in FIG. 6, the communication system 800 includes a satellite 810 and a network device 820.
  • the satellite 810 can be used to implement the corresponding function implemented by the UE in the above method
  • the network device 820 can be used to implement the corresponding function implemented by the network device in the above method.
  • the embodiment of the present invention also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the terminal device in the embodiment of the present invention, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention.
  • the embodiment of the present invention also provides a computer program product, including computer program instructions.
  • the computer program product may be applied to the terminal device in the embodiment of the present invention, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention.
  • the embodiment of the present invention also provides a computer program.
  • the computer program can be applied to the terminal device in the embodiment of the present invention.
  • the computer program is run on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention.
  • I won’t repeat it here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present invention essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present invention.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

一种信息处理方法、终端设备、芯片、计算机可读存储介质、计算机程序产品以及计算机程序，所述方法包括：终端设备获取到针对上行带宽部分(BWP)的先侦听后传输(LBT)失败指示(21)；所述终端设备基于第一时间段控制LBT失败计数器进行计数处理(22)；其中，所述第一时间段用于对所述LBT失败计数器的计数次数进行控制；基于所述LBT失败计数器的计数值，确定所述终端设备是否在所述上行BWP发生持续的LBT失败(23)。

Description

一种信息处理方法、终端设备 技术领域
本发明涉及信息处理技术领域，尤其涉及一种信息处理方法、终端设备、芯片、计算机可读存储介质、计算机程序产品以及计算机程序。
背景技术
在上行传输中，网络如果配置授权资源的重复传输，或者当网络配置的调度请求的传输资源周期比较小，或者信道状态信息上报资源的周期比较小时，可能会在短时间内上报大量的上行先侦听后传输(LBT，Listen before talk)失败事件。这样，由于新无线(NR，New Radio)上行密集传输，就会容易导致终端设备触发LBT失败，从而降低系统性能。
发明内容
为解决上述技术问题，本发明实施例提供了一种信息处理方法、终端设备、芯片、计算机可读存储介质、计算机程序产品以及计算机程序。
第一方面，提供了一种信息处理方法，所述方法包括：
终端设备获取到针对上行带宽部分BWP的LBT失败指示；
所述终端设备基于第一时间段控制LBT失败计数器进行计数处理；其中，所述第一时间段用于对所述LBT失败计数器的计数次数进行控制；
基于所述LBT失败计数器的计数值，确定所述终端设备是否在所述上行BWP发生持续的LBT失败。
第二方面，提供了一种终端设备，包括：
处理单元，获取到针对上行带宽部分BWP的LBT失败指示；基于第一时间段控制LBT失败计数器进行计数处理；其中，所述第一时间段用于对所述LBT失败计数器的计数次数进行控制；基于所述LBT失败计数器的计数值，确定是否在所述上行BWP发生持续的LBT失败。
第三方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第四方面，提供了一种芯片，用于实现上述各实现方式中的方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一方面或其各实现方式中的方法。
第五方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面或其各实现方式中的方法。
第七方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面或其各实现方式中的方法。
通过采用上述方案，根据第一时间段，控制对LBT失败指示的计数处理，从而根据最终的LBT失败指示的失败计数器的计数值确定是否发生持续的LBT失败。如此，就能够通过控制LBT失败计数器的计数值的增加，来避免过于频繁的触发LBT失败，从而提升系统性能。
附图说明
图1是本申请实施例提供的一种通信系统架构的示意性图一；
图2为本发明实施例提供的一种信息处理方法流程示意图；
图3为本发明实施例提供的终端设备组成结构示意图；
图4为本发明实施例提供的一种通信设备组成结构示意图；
图5是本申请实施例提供的一种芯片的示意性框图；
图6是本申请实施例提供的一种通信系统架构的示意性图二。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide  Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统100可以如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的网络设备(Base Transceiver Station，BTS)，也可以是WCDMA系统中的网络设备(NodeB，NB)，还可以是LTE系统中的演进型网络设备(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。作为在此使用的“终端设备”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。
可选地，终端设备120之间可以进行终端直连(Device to Device，D2D)通信。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
相关技术中，NR在非授权频段，包括如下几种工作场景：
场景A：载波聚合场景，主小区(PCell)为授权频谱，通过载波聚合方式聚合工作在非授权频谱上的辅小区(SCell)；
场景B：双连接工作场景，PCell为LTE授权频谱，PScell为新无线(NR， New Radio)非授权频谱；
场景C：独立工作场景，NR作为一个独立小区工作在非授权频谱；
场景D：NR单小区场景，上行链路(UL)工作在授权频谱，下行链路(DL)工作在非授权频谱；
场景E：双连接工作场景，PCell为NR授权频谱，PScell为NR非授权频谱。
一般来说，NR-U的工作频带(Band)为5GHz非授权频谱和6GHz非授权频谱。在非授权频谱上，NR-U的设计应该保证与其他已经工作在这些非授权频谱上的系统之间的公平性，比如WiFi等。公平性的原则是，NR-U对于已经部署在非授权频谱上的系统(比如WiFi)的影响不能超过这些系统之间的影响。
为了保证在非授权频谱上各系统之间的公平性共存，能量检测已经被同意作为一个基本的共存机制。一般的能量检测机制为LBT机制，该机制的基本原理为：基站或者终端(传输端)在非授权频谱上传输数据之前，需要先按照规定侦听一段时间。如果侦听的结果表示该信道为空闲状态，则传输端可以给接收端传输数据。如果侦听的结果表示该信道为占用状态，则传输端需要根据规定回退一段时间再继续侦听信道，知道信道侦听结果为空闲状态，才能向接收端传输数据。
对于终端设备发起的上行传输，主要有包括如下几类：
调取请求(SR，scheduling request)：用于请求上行资源；
PRACH(Physical Random Access Channel，物理随机接入信道)传输：由于随机接入信道(RACH)触发，终端设备需要发送msg1；
物理上行共享信道(PUSCH，Physical Uplink Shared Channel)传输：包括基于configured grant的上行数据传输以及基于dynamic grant的上行数据传输；
物理层信令传输：包括确认(ACK)/非确认(NACK)反馈，信道状态信息(CSI，Channel State Information)上报等；
在授权频段上，对于SR传输，介质接入控制(MAC，Media Access Control)会维护一个计数器来统计SR失败次数，即SR_COUNTER，当SR_COUNTER达到与配置的门限时，终端设备会触发RACH流程；
对于PRACH传输，MAC层也会维护一个计数器来统计PRACH失败次数，PREAMBLE_TRANSMISSION_COUNTER,当该计数器达到与配置的门限是，终端设备会触发无线链路失败，发起RRC重建流程；
对于基于配置的授权资源(configured grant)的上行传输，终端设备不会维护计数器。如果数据传输失败，网络会调度重传。对于RLC(Radio Link Control，无线链路层控制)AM模式，在RLC层会有一个计数器，当重传计数器达到最大次数，也会触发RLF。而对于RLC UM模式，则依赖于MAC和物理层的重传机制。
在非授权频带上，终端设备传输SR，PRACH或者PUSCH之前都需要先用LBT来侦听信道是否可用，如果不可以用，即LBT失败，则终端设备需要等到下一个传输机会再次执行LBT。
在RAN2#105次会议中，同意了如下结论：持续的上行传输导致的LBT失败会引起RLF。
进一步在RAN2#105bis会议中：在MAC层会设计一个机制来处理UL LBT失败的问题。
更进一步，在RAN2#107Prague会议上，同意了如下结论：
上行持续LBT问题检测会考虑所有类型的上行传输导致的LBT失败；同时，任何上行传输类型引起的LBT失败触发的恢复机制一样；
网络配置一个门限，终端设备的MAC层记录LBT失败的次数，当达到这个门限时,终端设备触发持续LBT失败事件；
同时也同意引入一个定时器(timer)，当timer超时的时候终端设备重置计数器，并且在收到LBT失败的时候启动或重启。
对于目前同意的结论，其机制基本跟波束失败恢复(BFR，beam failure recovery)机制一致。在上行传输中，存在突发(burst)传输，比如网络如果配置授权资源configured grant/动态授权dynamic grant的重复(repetition)传输，或者当网络配置的SR传输资源周期比较小，或者CSI上报资源的周期比较小时，终端设备有可能会在短时间内上报大量(dense)的上行LBT失败事件。这样，当网络配置的门限比较小时，终端设备会过早的触发持续LBT失败。
过早的触发持续LBT失败所在的问题在于，有可能当前所在的unlicensed信道只是被异系统占用一小段时间，但是由于本身NR上行密集传输，导致终端设备触发了LBT失败，从而降低系统性能。
因此，本实施例提供了一种方案，通过增加第一时间段，以对在第一时间段中控制对LBT失败指示的计数处理，从而能够减少触发LBT失败的情况。具体的，本发明实施例提供了一种信息处理方法，如图2所示，包括：
步骤21：终端设备获取到针对上行带宽部分(BWP，BandWidth Part)的先侦听后传输(LBT，Listen before talk)失败指示；
步骤22：所述终端设备基于第一时间段控制LBT失败计数器进行计数处理；其中，所述第一时间段用于对所述LBT失败计数器的计数次数进行控制；
步骤23：基于所述LBT失败计数器的计数值，确定所述终端设备是否在所述上行BWP发生持续的LBT失败。
本实施例中，所述终端设备可以为通信系统中的移动终端。
前述终端设备获取到针对上行带宽部分(BWP，Bandwidth Part)的LBT失败指示，可以为终端设备获取到下层发来的针对上行BWP的LBT失败 指示。
其中，下层可以为物理层。并且终端设备可以为通过MAC实体获取到物理层发来的针对上行BWP的LBT失败指示。
在一种示例中，
终端设备首先需要获取高层配置的LBT失败相关配置信息，具体来说，终端设备获取RRC层的LBT失败相关配置信息。
其中，所述失败相关配置信息包括：
LBT失败次数门限值，和第一时间段的长度；
所述LBT失败次数门限值，用于控制当MAC层接收的LBT失败次数达到该门限时，可以触发持续LBT失败事件；
所述第一时间段的长度可以通过设置过滤窗口实现，或者可以通过第一定时器的定时时长来实现。比如，可以设置过滤窗口的时长。终端设备的MAC层在该第一时间段也就是过滤窗口/第一定时器运行时其定时时长内，不统计LBT失败次数。
另外，终端设备可以在MAC层维护一个LBT失败计数器(LBT_Failure_Counter)，并且初始化LBT_Failure_Counter＝0。
在前述配置基础上，如果终端设备的MAC层从下层(比如物理层)收到LBT失败指示，则终端设备的MAC层的行为可以包括：
一种情况中，若所述终端设备获取到所述针对上行BWP的所述LBT失败指示的时刻处于所述第一时间段内，则不对所述LBT失败计数器进行计数；
也就是说，终端设备MAC层判断是否处于第一时间段内，也就是否处于过滤窗口内，或者第一定时器是否正在运行，如果收到的该LBT失败指示在过滤窗口之内/或者第一定时器(Timer)正在运行，则终端设备忽视该LBT失败指示，即LBT_Failure_Counter不更新；
另一种情况中，若所述终端设备获取到针对上行BWP的所述LBT失败指示的时刻不处于所述第一时间段内，则控制所述LBT失败计数器的计数值加1，同时开启所述第一时间段。
也就是说，如果收到的该针对上行BWP的LBT失败指示不在过滤窗口之内或者第一定时器没有运行，则：
终端设备的MAC层将LBT_Failure_Counter加1，即LBT_Failure_Counter＝LBT_Failure_Counter+1；并且，开启第一时间段。
其中，终端设备开启所述第一时间段的处理可以包括：终端设备MAC层控制启动过滤窗口/或者控制开启第一定时器。
可以看出，通过上述处理，可以基于第一时间段控制终端设备在进入该第一时间段之前以及在第一时间段的持续时长之内，仅基于接收到的LBT失败指示对LBT失败计数器的计数值加1，不会由于出现较多的LBT失败指示导致过早的触发LBT失败事件。
并且，还可以包括：
控制所述LBT失败计数器加1后，终端设备判断所述LBT失败计数器的计数值是否大于等于预设的LBT失败次数门限值；
若大于等于所述预设的LBT失败次数门限值，则所述终端设备确定在对应的所述上行BWP发生持续的LBT失败。
也就是说，如果终端设备判断LBT_Failure_Counter>＝配置的LBT失败次数门限，则所述终端设备确定在对应的带宽部分BWP发生持续的LBT失败，也就是终端设备可以触发一个持续LBT失败事件，即终端设备可以执行LBT失败恢复过程。
进一步地，针对LBT失败计数器还可以进行重配置，具体的可以在以下几种情况下发生重配置的情况：
当所述终端设备获取到LBT成功指示、或者所述终端设备上行传输成功时，重置所述LBT失败计数器；
或者，当高层配置的LBT失败相关配置信息发生重配时，重置所述LBT失败计数器。
具体来说，一种情况中，可以在收到LBT成功指示的时候，重置所述LBT失败计数器；
第二种情况中，可以在上行传输成功的时候，重置所述LBT失败计数器。
这种情况中，所述上行传输成功可以没有LBT成功指示，而是在实际进行上行传输的时候，没有接收到LBT失败指示，那么就可以认为该上行传输成功。举例来说，终端设备进行上行传输，可以为上行进行PRACH传输、PUSCH传输、SR传输中的任意一种，如果在完成上行传输后，没有在接收到对应的LBT失败指示，那么就可以认为上行传输成功，此时可以对LBT失败计数器进行清0。
第三种情况中，可以为高层重配相关配置信息的时候，重置LBT失败计数器。
其中，高层的LBT失败相关配置信息发生重配时，可以包括重配以下至少之一：LBT失败次数门限值，第一时间段的长度。
其中，第一时间段的长度可以为：过滤窗口的长度，或者第一定时器的定时时长。
也就是说，若LBT成功了，那么可以不再进行LBT计数，因此可以将LBT失败计数器进行重置，也就是清0；又或者，如果发生对应的参数的重配置，那么也需要对LBT失败计数器进行重置也就是清0。
其中，所述LBT成功指示可以由终端设备的MAC层从物理层获取。
进一步地，在终端设备MAC层重置LBT失败计数器(也就是清0)的时候，还可以将过滤窗口或第一定时器停止，也就是说，如果LBT失败计数器清0了，那么可以进入下一次重新统计LBT失败次数的处理中，也 就不需要维持本次用于进行LBT失败统计的第一时间段。需要理解的是，这种情况下，无论当前时刻处于第一时间段的哪种相对时刻，都可以直接停止第一时间段的计时；即无论当前时刻处于过滤窗口的哪个相对时刻，都可以控制关闭过滤窗口，或者，控制将第一定时器停止。
相关的协议中实现方式可以如下：
The MAC entity shall(MAC实体会执行的处理):
if LBT failure indication has been received from lower layers(如果从下层接收到LBT失败指示):
if the configured window/timer is not running(如果配置的过滤窗口或者第一定时器没有运行):
2>increment LBT_COUNTER by 1(LBT-COUNTER，即LBT失败计数器加1)；
2>if LBT_COUNTER>＝lbtFailureInstanceMaxCount(如果LBT-COUNTER大于预设的LBT失败次数门限值(即lbtFailureInstanceMaxCount)):
3>trigger consistent LBT failure event(则触发持续LBT失败事件)；
2>start the configured window/timer(并且开启配置的过滤窗口或第一定时器)；
if configured Window/Timer or lbtFailureInstanceMaxCount is reconfigured by upper layers(如果上层对过滤窗口或第一定时器或LBT失败次数门限值进行重配置)；or
if LBT success indication has been received from lower layer(或者，如果接收到下层的LBT失败成功指示):
2>set LBT_COUNTER to 0(则重置LBT计数器为0).
2>stop the configured window/timer,if running(如果过滤窗口开启或者第一定时器运行，则停止配置的过滤窗口或停止第一定时器).
再另一种示例中，
与前述示例不同在于，在前述示例的基础上，本示例增加了LBT失败指示定时器，该LBT失败指示定时器，用于控制在该时长内对LBT失败次数进行记录，如果超过该时长，则可以认为对LBT失败次数不需要与本次LBT失败进行共同记录，或者，可以任务超过该时长之后接收到的LBT失败指示与在该时长之内的LBT失败指示不相关，可以重新开始进行记录。这样，可以减少由于在一段时间之后发生的LBT失败也进行记录，从而带来的LBT失败触发较为频繁的问题。
具体来说，本示例中，所述失败相关配置信息包括：
LBT失败次数门限值，第一时间段的长度，以及LBT失败指示定时器。
其中，所述LBT失败指示定时器可以由预设的窗口或第二定时器时长来实现。
LBT失败指示定时器，在该时长内，终端设备可以认为LBT失败指示是连续的/相关的。即通过该LBT失败指示定时器控制LBT失败指示之间的时间间隔不能过长，如果过长就可以认为不是连续的或者相关的LBT失败指示。
与前一示例相同在于，同样在终端设备的MAC实体维护一个LBT失败计数器(LBT_Failure_Counter)，并且初始化LBT_Failure_Counter(LBT失败计数器)＝0；
如果终端MAC实体从下层(比如物理层)收到LBT失败指示，则终端设备MAC层的行为如下：
若所述终端设备获取到针对上行BWP的LBT失败指示的时刻处于所述第一时间段内，则不对LBT失败计数器进行计数；
或者，
若所述终端设备获取到针对上行BWP的LBT失败指示的时刻不处于所述第一时间段内，则控制LBT失败计数器的计数值加1，同时所述终端设备开启所述第一时间段。
与前述示例不同在于，本示例在所述终端设备开启所述第一时间段时，所述终端设备启动或重启LBT失败指示定时器。
举例来说，终端设备MAC层启动/重启LBT_Detection_Timer(LBT失败指示定时器)；
终端设备MAC层判断过滤窗口/定时器是否正在运行，如果收到的该LBT失败指示在过滤窗口之内/Timer正在运行，则终端设备忽视该LBT失败指示，即LBT_Failure_Counter不更新；如果收到的该LBT失败指示不在过滤窗口之内/Timer没有运行，则：
终端设备MAC层将LBT_Failure_Counter加1，即LBT_Failure_Counter＝LBT_Failure_Counter+1；
如果终端设备判断LBT_Failure_Counter>＝配置的LBT失败次数门限，则终端设备可以触发一个持续LBT失败事件，也就是终端设备可以执行LBT失败恢复过程；
终端设备MAC层启动过滤窗口/Timer；
终端设备MAC层启动/重启LBT_Detection_Timer；
当高层配置的LBT失败相关配置信息发生重配，比如网络重配LBT失败次数门限，和/或重配过滤窗口/定时器长度，和/或重配置LBT_Detection_Timer；或者LBT_Detection_Timer超时，或者，当终端MAC层从物理层收到LBT成功指示的情况下，终端设备MAC层重置LBT_Failure_Counter，并停止过滤窗口/Timer。
以上处理中，通过在接收到LBT失败指示的时候，如果没有进入第一时间段内，就开启第一时间段，并且开启LBT失败指示定时器；如此，实现在第一时间段内不会增加LBT失败计数器的计数值，即便第一时间段结 束，接收到LBT失败指示，增加LBT失败计数器的计数值，也会对随着LBT失败指示定时器来对LBT失败计数器的计数值进行重置，从而进一步的避免较为密集的上行传输，容易导致LBT失败事件的触发的情况。
本示例的相关的协议实现方式：
The MAC entity shall(MAC实体会执行的处理):
if LBT failure indication has been received from lower layers(如果从下层接收到LBT失败指示):
if the configured window/timer is not running(如果配置的过滤窗口或者第一定时器没有运行):
2>increment LBT_COUNTER by 1(LBT-COUNTER，即LBT失败计数器加1)；
2>if LBT_COUNTER>＝lbtFailureInstanceMaxCount(如果LBT-COUNTER大于预设的LBT失败次数门限值(即lbtFailureInstanceMaxCount)):
3>trigger consistent LBT failure event(则触发持续LBT失败事件)；
2>start the configured window/timer(并且开启配置的过滤窗口或第一定时器)；
2>start/restart the lbtFailureDetectionTimer(启动或重启LBT失败指示定时器)；
1>if the lbtFailureDetectionTimer expires(如果LBT失败指示定时器超时)；or
if lbtFailureDetectionTimer or lbtFailureInstanceMaxCount is reconfigured by upper layers(或者，如果上层对LBT失败指示定时器或者LBT失败次数门限值进行重配)；or
if LBT success indication has been received from lower layer(或者，如果接收到下层的LBT失败成功指示):
2>set LBT_COUNTER to 0(则重置LBT计数器为0).
2>stop the configured window/timer,if running(如果过滤窗口开启或者第一定时器运行，则停止配置的过滤窗口或停止第一定时器)。
可见，通过采用上述方案，根据第一时间段，控制对LBT失败指示的计数处理，从而根据最终的LBT失败指示的失败计数器的计数值确定是否发生持续的LBT失败。如此，就能够通过控制LBT失败计数器的计数值的增加，来避免过于频繁的触发LBT失败，从而提升系统性能。
本发明实施例提供了一种终端设备，如图3所示，包括：
处理单元31，获取到针对上行带宽部分(BWP，BandWidth Part)的先侦听后传输(LBT，Listen before talk)失败指示,基于第一时间段控制LBT失败计数器进行计数处理；其中，所述第一时间段用于对所述LBT失败计 数器的计数次数进行控制；基于所述LBT失败计数器的计数值，确定是否在所述上行BWP发生持续的LBT失败。
本实施例中，所述终端设备可以为通信系统中的移动终端。
处理单元31，获取到下层发来的针对上行BWP的LBT失败指示。
其中，下层可以为物理层。并且终端设备可以为通过MAC实体获取到物理层发来的针对上行BWP的LBT失败指示。
在一种示例中，
处理单元31，首先需要获取高层配置的LBT失败相关配置信息，具体来说，终端设备获取RRC层的LBT失败相关配置信息。
其中，所述失败相关配置信息包括：
LBT失败次数门限值和第一时间段的长度；
LBT失败次数门限值，用于控制当MAC层接收的LBT失败次数达到该门限时，可以触发持续LBT失败事件；
第一时间段的长度可以通过设置过滤窗口实现，或者可以通过第一定时器的定时时长来实现。比如，可以设置过滤窗口的时长。终端设备的MAC层在该第一时间段也就是过滤窗口/第一定时器运行时其定时时长内，不统计LBT失败次数。
在前述配置基础上，如果终端设备的MAC层从下层(比如物理层)收到LBT失败指示，则终端设备的MAC层的行为可以包括：
一种情况中，处理单元31，若获取到针对上行BWP的LBT失败指示的时刻处于所述第一时间段内，则不对LBT失败计数器进行计数；
也就是说，终端设备MAC层判断是否处于第一时间段内，也就是否处于过滤窗口内，或者第一定时器是否正在运行，如果收到的该LBT失败指示在过滤窗口之内/或者第一定时器(Timer)正在运行，则终端设备忽视该LBT失败指示，即LBT_Failure_Counter不更新；
另一种情况中，处理单元31，若获取到针对上行BWP的LBT失败指示的时刻不处于所述第一时间段内，则控制LBT失败计数器的计数值加1，同时开启所述第一时间段。
并且，还可以包括：
处理单元31，判断所述LBT失败计数器的计数值是否大于等于预设的LBT失败次数门限值；若大于等于预设的LBT失败次数门限值，则确定在对应的带宽部分BWP发生持续的LBT失败。
进一步地，针对LBT失败计数器还可以进行重配置，具体的可以在以下几种情况下发生重配置的情况：
当处理单元31，获取到LBT成功指示时，重置所述LBT失败计数器；
或者，当高层配置的LBT失败相关配置信息发生重配的情况。
具体来说，本示例中，高层的LBT失败相关配置信息发生重配时，可以包括重配以下至少之一：LBT失败次数门限值，第一时间段的长度。
其中，第一时间段的长度可以为：过滤窗口的长度，或者第一定时器的定时时长。
再另一种示例中，
与前述示例不同在于，在前述示例的基础上，本示例增加了LBT失败指示定时器，该LBT失败指示定时器，用于控制在该时长内对LBT失败次数进行记录，如果超过该时长，则可以认为对LBT失败次数不需要与本次LBT失败进行共同记录，或者，可以任务超过该时长之后接收到的LBT失败指示与在该时长之内的LBT失败指示不相关，可以重新开始进行记录。这样，可以减少由于在一段时间之后发生的LBT失败也进行记录，从而带来的LBT失败触发较为频繁的问题。
具体来说，本示例中，所述失败相关配置信息包括：
LBT失败次数门限值，第一时间段的长度，以及LBT失败指示定时器。
其中，所述LBT失败指示定时器可以由预设的窗口或第二定时器时长来实现。
LBT失败指示定时器，在该时长内，终端设备可以认为LBT失败指示是连续的/相关的。即通过该LBT失败指示定时器控制LBT失败指示之间的时间间隔不能过长，如果过长就可以认为不是同一个事件对应的LBT失败指示。
与前一示例相同在于，同样在终端设备的MAC实体维护一个LBT失败计数器(LBT_Failure_Counter)，并且初始化LBT_Failure_Counter＝0；
如果终端MAC实体从下层(比如物理层)收到LBT失败指示，则终端设备MAC层的行为如下：
处理单元31，获取到针对上行BWP的LBT失败指示时，处于所述第一时间段内，则不对LBT失败计数器进行计数；
或者，
处理单元31，获取到针对上行BWP的LBT失败指示时，不处于所述第一时间段内，则控制LBT失败计数器的计数值加1，同时所述终端设备开启所述第一时间段。
与前述示例不同在于，本示例处理单元31，在开启所述第一时间段时，启动或重启LBT失败指示定时器。
可见，通过采用上述方案，根据第一时间段，控制对LBT失败指示的计数处理，从而根据最终的LBT失败指示的失败计数器的计数值确定是否发生持续的LBT失败。如此，就能够通过控制LBT失败计数器的计数值的增加，来避免过于频繁的触发LBT失败，从而提升系统性能。
图4是本发明实施例提供的一种通信设备900示意性结构图，本实施例中的通信设备可以具体为前述实施例中的终端设备。图4所示的通信设备900包括处理器910，处理器910可以从存储器中调用并运行计算机程序， 以实现本发明实施例中的方法。
可选地，图4所示，通信设备900还可以包括存储器920。其中，处理器910可以从存储器920中调用并运行计算机程序，以实现本发明实施例中的方法。
其中，存储器920可以是独立于处理器910的一个单独的器件，也可以集成在处理器910中。
可选地，如图4所示，通信设备900还可以包括收发器930，处理器910可以控制该收发器930与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器930可以包括发射机和接收机。收发器930还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备900具体可为本发明实施例的网络设备，并且该通信设备900可以实现本发明实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备900具体可为本发明实施例的卫星、或者网络设备，并且该通信设备900可以实现本发明实施例的各个方法中由移动终端/卫星实现的相应流程，为了简洁，在此不再赘述。
图5是本发明实施例的芯片的示意性结构图。图5所示的芯片1000包括处理器1010，处理器1010可以从存储器中调用并运行计算机程序，以实现本发明实施例中的方法。
可选地，如图5所示，芯片1000还可以包括存储器1020。其中，处理器1010可以从存储器1020中调用并运行计算机程序，以实现本发明实施例中的方法。
其中，存储器1020可以是独立于处理器1010的一个单独的器件，也可以集成在处理器1010中。
可选地，该芯片1000还可以包括输入接口1030。其中，处理器1010可以控制该输入接口1030与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1000还可以包括输出接口1040。其中，处理器1010可以控制该输出接口1040与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本发明实施例中的网络设备，并且该芯片可以实现本发明实施例的各个方法中由卫星实现的相应流程，为了简洁，在此不再赘述。
应理解，本发明实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
应理解，本发明实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中 的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本发明实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本发明实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本发明实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图6是本申请实施例提供的一种通信系统800的示意性框图。如图6所示，该通信系统800包括卫星810和网络设备820。
其中，该卫星810可以用于实现上述方法中由UE实现的相应的功能，以及该网络设备820可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
本发明实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本发明实施例中的终端设备，并且该计算机程序使得计算机执行本发明实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本发明实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本发明实施例中的终端设备，并且该计算机程序指令使得计算机执行本发明实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本发明实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本发明实施例中的终端设备，当该计算机程序在计算机上运行时，使得计算机执行本发明实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本发明所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在 一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (19)

  1. 一种信息处理方法，所述方法包括：
    终端设备获取到针对上行带宽部分BWP的先侦听后传输LBT失败指示；
    所述终端设备基于第一时间段控制LBT失败计数器进行计数处理；其中，所述第一时间段用于对所述LBT失败计数器的计数次数进行控制；
    基于所述LBT失败计数器的计数值，确定所述终端设备是否在所述上行BWP发生持续的LBT失败。
  2. 根据权利要求1所述的方法，其中，所述终端设备基于第一时间段控制LBT失败计数器进行计数处理，包括：
    若所述终端设备获取到所述针对上行BWP的所述LBT失败指示的时刻处于所述第一时间段内，则不对所述LBT失败计数器进行计数；
    或者，
    若所述终端设备获取到所述针对上行BWP的所述LBT失败指示的时刻不处于所述第一时间段内，则控制所述LBT失败计数器的计数值加1，同时所述终端设备开启所述第一时间段。
  3. 根据权利要求2所述的方法，其中，所述基于所述LBT失败计数器的计数值，确定所述终端设备是否在所述上行BWP发生持续的LBT失败，包括：
    终端设备判断所述LBT失败计数器的计数值是否大于等于预设的LBT失败次数门限值；
    若大于等于所述预设的LBT失败次数门限值，则所述终端设备确定在对应的所述上行BWP发生持续的LBT失败。
  4. 根据权利要求1-3任一项所述的方法，其中，所述终端设备开启所述第一时间段时，所述方法还包括：
    所述终端设备启动或重启LBT失败指示定时器。
  5. 根据权利要求4所述的方法，其中，所述方法还包括：
    当所述LBT失败指示定时器超时时，所述终端设备重置所述LBT失败计数器。
  6. 根据权利要求1-5任一项所述的方法，其中，所述方法还包括：
    当所述终端设备获取到LBT成功指示、或者所述终端设备上行传输成功时，所述终端设备重置所述LBT失败计数器。
  7. 根据权利要求1-6任一项所述的方法，其中，所述方法还包括：
    所述终端设备获取高层配置的LBT失败相关配置信息；
    其中，所述失败相关配置信息包括：
    所述LBT失败次数门限值和所述第一时间段的长度；
    或者，所述LBT失败次数门限值，所述第一时间段的长度，以及所述 LBT失败指示定时器。
  8. 一种终端设备，包括：
    处理单元，获取到针对上行BWP的LBT失败指示；基于第一时间段控制LBT失败计数器进行计数处理；其中，所述第一时间段用于对所述LBT失败计数器的计数次数进行控制；基于所述LBT失败计数器的计数值，确定是否在所述上行BWP发生持续的LBT失败。
  9. 根据权利要求8所述的终端设备，其中，所述处理单元，
    若获取到所述针对上行BWP的所述LBT失败指示的时刻处于所述第一时间段内，则不对所述LBT失败计数器进行计数；
    或者，
    若获取到所述针对上行BWP的所述LBT失败指示的时刻不处于所述第一时间段内，则控制所述LBT失败计数器的计数值加1，同时开启所述第一时间段。
  10. 根据权利要求9所述的终端设备，其中，所述处理单元，判断所述LBT失败计数器的计数值是否大于等于预设的LBT失败次数门限值；
    若大于等于所述预设的LBT失败次数门限值，则确定在对应的所述上行BWP发生持续的LBT失败。
  11. 根据权利要求8-10任一项所述的终端设备，其中，所述处理单元，启动或重启LBT失败指示定时器。
  12. 根据权利要求11所述的终端设备，其中，所述处理单元，当所述LBT失败指示定时器超时时，重置所述LBT失败计数器。
  13. 根据权利要求8-12所述的终端设备，其中，所述处理单元，获取到LBT成功指示、或者上行传输成功时，重置所述LBT失败计数器。
  14. 根据权利要求8-13任一项所述的终端设备，其中，所述处理单元，获取到高层配置的LBT失败相关配置信息；
    其中，所述失败相关配置信息包括：
    所述LBT失败次数门限值和所述第一时间段的长度；
    或者，所述LBT失败次数门限值，所述第一时间段的长度，以及所述LBT失败指示定时器。
  15. 一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1-7任一项所述方法的步骤。
  16. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1-7中任一项所述的方法。
  17. 一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1-7任一项所述方法的步骤。
  18. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1-7中任一项所述的方法。
  19. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1-7中任一项所述的方法。
PCT/CN2019/107973 2019-09-25 2019-09-25 一种信息处理方法、终端设备 WO2021056296A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/107973 WO2021056296A1 (zh) 2019-09-25 2019-09-25 一种信息处理方法、终端设备
CN201980095356.9A CN113678559A (zh) 2019-09-25 2019-09-25 一种信息处理方法、终端设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/107973 WO2021056296A1 (zh) 2019-09-25 2019-09-25 一种信息处理方法、终端设备

Publications (1)

Publication Number Publication Date
WO2021056296A1 true WO2021056296A1 (zh) 2021-04-01

Family

ID=75166262

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/107973 WO2021056296A1 (zh) 2019-09-25 2019-09-25 一种信息处理方法、终端设备

Country Status (2)

Country Link
CN (1) CN113678559A (zh)
WO (1) WO2021056296A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023010257A1 (zh) * 2021-08-02 2023-02-09 Oppo广东移动通信有限公司 侧行通信方法、装置、设备及存储介质
WO2023050148A1 (en) * 2021-09-29 2023-04-06 Nec Corporation Methods, devices, and computer readable medium for communication
WO2023133736A1 (zh) * 2022-01-12 2023-07-20 北京小米移动软件有限公司 一种确定先听后说失败的方法及装置
WO2024092824A1 (zh) * 2022-11-04 2024-05-10 北京小米移动软件有限公司 一种失败报告的上报方法及其装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108476532A (zh) * 2016-02-02 2018-08-31 英特尔Ip公司 随机接入过程期间的先听后说(lbt)失败
US20180279386A1 (en) * 2015-09-25 2018-09-27 Alcatel Lucent Method and apparatus for listening before talk
WO2019031796A1 (en) * 2017-08-11 2019-02-14 Lg Electronics Inc. METHOD FOR MANAGING PRE-CONFIGURED UPLINK RESOURCES BASED ON LBT PROCEDURE IN A WIRELESS COMMUNICATION SYSTEM AND DEVICE THEREOF
CN109565877A (zh) * 2016-08-18 2019-04-02 Lg 电子株式会社 在支持未授权频带的无线通信系统中通过多个未授权分量载波发送上行链路信号的方法和支持该方法的设备
CN110166182A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种竞争窗管理的方法及发送设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105611637B (zh) * 2016-02-06 2019-05-24 北京佰才邦技术有限公司 信道发送状态的指示方法和终端
CN107371273B (zh) * 2016-05-13 2023-05-30 中兴通讯股份有限公司 随机接入方法、装置及用户设备
CN109151833B (zh) * 2017-06-16 2020-07-21 华为技术有限公司 传输控制信息的方法和装置
EP3840516A4 (en) * 2018-08-15 2022-03-30 Beijing Xiaomi Mobile Software Co., Ltd. METHOD AND DEVICE FOR BACKOFF IN A TRANSMISSION METHOD, DEVICE, SYSTEM AND STORAGE MEDIUM
WO2020147042A1 (zh) * 2019-01-16 2020-07-23 北京小米移动软件有限公司 Lbt失败的处理方法和lbt失败的处理装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279386A1 (en) * 2015-09-25 2018-09-27 Alcatel Lucent Method and apparatus for listening before talk
CN108476532A (zh) * 2016-02-02 2018-08-31 英特尔Ip公司 随机接入过程期间的先听后说(lbt)失败
CN109565877A (zh) * 2016-08-18 2019-04-02 Lg 电子株式会社 在支持未授权频带的无线通信系统中通过多个未授权分量载波发送上行链路信号的方法和支持该方法的设备
WO2019031796A1 (en) * 2017-08-11 2019-02-14 Lg Electronics Inc. METHOD FOR MANAGING PRE-CONFIGURED UPLINK RESOURCES BASED ON LBT PROCEDURE IN A WIRELESS COMMUNICATION SYSTEM AND DEVICE THEREOF
CN110166182A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种竞争窗管理的方法及发送设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023010257A1 (zh) * 2021-08-02 2023-02-09 Oppo广东移动通信有限公司 侧行通信方法、装置、设备及存储介质
WO2023050148A1 (en) * 2021-09-29 2023-04-06 Nec Corporation Methods, devices, and computer readable medium for communication
WO2023133736A1 (zh) * 2022-01-12 2023-07-20 北京小米移动软件有限公司 一种确定先听后说失败的方法及装置
WO2024092824A1 (zh) * 2022-11-04 2024-05-10 北京小米移动软件有限公司 一种失败报告的上报方法及其装置

Also Published As

Publication number Publication date
CN113678559A (zh) 2021-11-19

Similar Documents

Publication Publication Date Title
WO2021056296A1 (zh) 一种信息处理方法、终端设备
KR102306823B1 (ko) 무선 통신 시스템에서 면허 도움 접속 기술 활용 시 기지국의 데이터 스케쥴링을 위한 장치 및 방법
US11564255B2 (en) Method and apparatus for processing LBT monitoring failures and system
EP3096564A1 (en) Data processing method after release of unauthorized spectrum, and user equipment
EP3925401B1 (en) User equipment, radio network node and methods for managing recovery procedures therein
JP7353365B2 (ja) カウント方法、端末デバイス及び装置
EP3941150A1 (en) Random access method, terminal device and network device
WO2020107416A1 (zh) 随机接入过程选择方法、装置、芯片及计算机程序
US20220052796A1 (en) Harq information feedback method and device
WO2021087929A1 (zh) 一种随机接入的方法和装置
CN113196851B (zh) 信息上报方法及相关设备
WO2020227944A1 (zh) 侧行链路监测的方法和设备
US20210314923A1 (en) Methods and Devices for Data Transmission
WO2021217363A1 (zh) 无线通信方法、终端设备和网络设备
WO2020215330A1 (zh) 随机接入过程中传输信息的方法、终端设备和网络设备
WO2021026841A1 (zh) 调度请求传输的方法和设备
WO2020191632A1 (zh) 一种功率控制方法及装置、终端、网络设备
WO2021163858A1 (zh) 一种进程选择方法及终端设备
US11800546B2 (en) Method and apparatus for determining number of uplink control information transmission resources, and program
WO2020051735A1 (zh) 通信方法、终端设备和网络设备
US20220053395A1 (en) Event processing method and user equipment
US20220046710A1 (en) System and method for multiple parallel messaging indication
WO2022027249A1 (zh) 信息传输方法、装置、设备及存储介质
WO2021022570A1 (zh) 数据传输方法、终端设备及存储介质
WO2019242378A1 (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: 19946712

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19946712

Country of ref document: EP

Kind code of ref document: A1