WO2020087369A1 - 一种计数方法、终端设备及装置 - Google Patents

一种计数方法、终端设备及装置 Download PDF

Info

Publication number
WO2020087369A1
WO2020087369A1 PCT/CN2018/113118 CN2018113118W WO2020087369A1 WO 2020087369 A1 WO2020087369 A1 WO 2020087369A1 CN 2018113118 W CN2018113118 W CN 2018113118W WO 2020087369 A1 WO2020087369 A1 WO 2020087369A1
Authority
WO
WIPO (PCT)
Prior art keywords
counter
indication information
lbt
global
terminal device
Prior art date
Application number
PCT/CN2018/113118
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 EP18938371.4A priority Critical patent/EP3863359B1/en
Priority to CN202110572029.7A priority patent/CN113316172B/zh
Priority to KR1020217014876A priority patent/KR20210084506A/ko
Priority to JP2021523625A priority patent/JP7353365B2/ja
Priority to CN201880097125.7A priority patent/CN112673701A/zh
Priority to PCT/CN2018/113118 priority patent/WO2020087369A1/zh
Priority to AU2018448175A priority patent/AU2018448175A1/en
Publication of WO2020087369A1 publication Critical patent/WO2020087369A1/zh
Priority to US17/243,495 priority patent/US11785487B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
    • H04L1/201—Frame classification, e.g. bad, good or erased
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • the present invention relates to the field of information processing technology, and in particular, to a counting method, terminal device, chip, computer-readable storage medium, computer program product, and computer program.
  • embodiments of the present invention provide a counting method, terminal device, chip, computer-readable storage medium, computer program product, and computer program.
  • an embodiment of the present invention provides a counting method, which is applied to a terminal device and includes:
  • an embodiment of the present invention provides a terminal device, including:
  • the processing unit maintains at least one counter, wherein the counter is used to record the number of times the first indication information is received; based on the received first indication information, it is determined to increase the count value of the counter corresponding to the first indication information.
  • 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 first aspect or the various implementations thereof.
  • a chip is provided for implementing the method in the above first aspect or each implementation manner thereof.
  • the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip executes any one of the first aspect to the second aspect described above or its respective implementations method.
  • a computer-readable storage medium for storing a computer program that causes a computer to execute the method in the first aspect or its various implementations.
  • a computer program product which includes computer program instructions, which cause the computer to execute the method in the first aspect or its various implementations.
  • a computer program which when run on a computer, causes the computer to execute the method in the first aspect or its various implementations.
  • the counter value is determined based on the corresponding first indication information by maintaining the counter. In this way, when the counter passing the counter reaches a certain number, corresponding control processing can be performed, so that the uplink transmission can grab the channel, thereby ensuring the performance of the uplink transmission.
  • 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 a counting method provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a terminal device provided by an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a composition of a communication device according to 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
  • CDMA Code Division Multiple Access
  • WCDMA Broadband Code Division Multiple Access
  • GPRS general packet radio service
  • LTE Long-term evolution
  • FDD Freq terminal equipment ncy Division Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Global Interoperability for Microwave Access
  • the communication system 100 applied in the embodiments 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 referred to as a communication terminal, terminal).
  • the network device 110 can provide communication coverage for a specific geographic area, and can communicate with terminal devices located within the coverage area.
  • the network device 110 may be a network device (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a network device (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 a cloud radio access network (Cloud Radio Access Network, CRAN), or the network equipment may be a mobile switching center, a relay station, an access point, Vehicle-mounted devices, wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks or network devices in future public land mobile networks (Public Land Mobile Network, PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB network device
  • Evolutional Node B, eNB or eNodeB Evolutional Node B, eNB or eNodeB
  • a wireless controller in a cloud radio access network Cloud Radio Access Network, CRAN
  • the network equipment may
  • the communication system 100 also includes at least one terminal device 120 within the coverage of the network device 110.
  • terminal equipment includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Lines (DSL), digital cables, and direct cable connections ; And / or another data connection / network; and / or via wireless interfaces, such as for cellular networks, wireless local area networks (Wireless Local Area Network, WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) equipment.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Lines
  • WLAN wireless local area networks
  • digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter
  • IoT Internet of Things
  • a terminal device configured to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal”, or “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communication Systems (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; can include radiotelephones, pagers, Internet / internal PDA with network access, web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palm-type receivers or others including radiotelephone transceivers Electronic device.
  • PCS Personal Communication Systems
  • GPS Global Positioning System
  • Terminal equipment can refer to access terminal, user equipment (User Equipment), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent Or user device.
  • Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital processing (Personal Digital Assistant (PDA), wireless communication Functional handheld devices, computing devices, or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in a 5G network, or terminal devices in a future-evolving PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • terminal equipment 120 may perform terminal direct connection (Device to Device, D2D) communication.
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within the coverage area. This application The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
  • network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
  • the devices with communication functions in the network / system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiments of the present application.
  • An embodiment of the present invention provides a counting method, which is applied to a terminal device, as shown in FIG. 2, and includes:
  • Step 201 Maintain at least one counter, where the counter is used to record the number of times the first indication information is received;
  • Step 202 Based on the received first indication information, determine to increase the count value of the counter corresponding to the first indication information.
  • the first indication information is used to indicate one of the following: LBT failure, LBT success, SR transmission failure, preamble transmission failure, and uplink data transmission failure.
  • the first indication information sent by the physical layer may be received, and the first indication information is used to indicate LBT failure; or, when LBT succeeds, it may also be received by The received first indication information determines that the LBT failed; or, the first indication information may be used to determine that the SR transmission failure occurred in the uplink transmission; or, the first indication information may be used to determine the preamble transmission failure or the uplink data transmission failure.
  • the first indication information sent by the physical layer may also be information received from the network side, which is transmitted to the MAC layer or the RRC layer through the physical layer, and then the RRC layer or the MAC layer maintains the global counter and / or at least At least one counter for upstream transmission.
  • step 202 based on the received first indication information, it is determined to increase the count value of the counter corresponding to the first indication information; it may include: regardless of the content contained in the received first indication information, Increase the count value of the counter corresponding to the first indication information;
  • the first indication information when it is determined that the first indication information is used to indicate at least one of LBT failure, SR transmission failure, preamble transmission failure, and uplink data transmission failure, it may be determined to increase the count value of the counter.
  • the triggering method of LBT may include one of the following: uplink PUCCH transmission scheduling request SR or HARQ feedback; uplink PUSCH transmission data; RACH process initiation. That is to say, through the uplink transmission of PUCCH, PUSCH or random access channel, the LBT process can be triggered.
  • the at least one counter includes: a global counter, and / or at least one counter for at least one uplink transmission.
  • At least one counter is a global counter.
  • the determining to increase the count value of the counter corresponding to the first indication information based on the received first indication information includes determining to increase the count value of the global counter based on the received first indication information .
  • the information that can be included in the first instruction information indicates that the count value of the global counter will be increased regardless of the failure of any kind of upstream transmission.
  • a global timer corresponding to the global counter may be configured for the terminal device through the network side.
  • the method further includes: when receiving the first indication information, starting or restarting the global timer.
  • the condition for starting or restarting the global timer is that the first indication information is received.
  • the count value of the global counter is increased by 1, and the global timer is started or restarted; that is, when the global timer is not running ,
  • the global timer may be started based on the first indication information, and when the global timer has started counting, the global timer may be restarted based on the first indication information.
  • the global timer can be used to control the situation where the count value of the global counter has not changed for a long time. For example, if the count value of the global counter has not been increased for a long time, that is, when there is no operation such as upstream channel preemption for a long time, if the next time When the uplink transmission is performed again and a failure occurs, the count is accumulated based on the count value of the originally recorded global counter, but this will cause performance problems in the uplink transmission.
  • the global counter can be reset when the global timer times out. In this way, it is possible to restart counting of the global counter when the count value of the global counter has not been changed for a long period of time.
  • the method further includes: when the global counter reaches a preset threshold, the radio resource control (RRC, Radio Resource Control) layer triggers one of the following processes: RRC connection re-establishment; secondary cell group (SCG, Secondary) Cell)-Radio link failure (RLF, Radio Link Failure) processing; RRC reconfiguration.
  • RRC Radio Resource Control
  • the RRC reconfiguration may be at least one of the following: reconfiguration of uplink BWP, or reconfiguration of PRACH resources, reconfiguration of PUCCH resources, reconfiguration of PUSCH resources, and reconfiguration of uplink carriers, etc.
  • the SCG-RLF process is to suspend all SCG's SRB (Signalling radio bearers, signaling radio bearers) and DRB (Data Radio Radio Bearers, data radio bearers), reset the SCG MAC (Media Access Control Address, media access control) entity, and Use MCG to report the number of LBT failures online.
  • the preset threshold value may be a threshold value set according to actual conditions, for example, it may be set to 10, and of course, it may also be set to other values, which is not exhaustive here.
  • connection re-establishment request when RRC connection re-establishment is initiated, a connection re-establishment request is initiated to the network side; the connection re-establishment request includes: the number of LBT failures, and / or, the event that triggers the LBT.
  • the terminal can further report to the network in the re-establishment request message: the number of LBT failures, and / or: the event of initiating the LBT, such as the PUCCH sending SR triggering LBT, and the uplink data sending trigger LBT or RACH triggers LBT, etc.
  • the global counter may be maintained at the MAC layer of the terminal device.
  • the physical layer indicates LBT failure to the MAC, and the MAC layer triggers the execution of the foregoing behavior.
  • it can also be maintained at the RRC layer.
  • the physical layer indicates LBT failure to RRC, and the RRC triggers the execution of the foregoing behavior.
  • At least one counter is at least one counter for at least one uplink transmission.
  • this scenario can maintain one or more counters, and can maintain the same or different counters for different uplink transmissions, that is, a corresponding counter can be maintained for each uplink transmission, or it can be One counter is maintained for the first part of the uplink transmission, and another counter is maintained for the remaining part of the uplink transmission.
  • the determining to increase the count value of the counter corresponding to the first indication information based on the received first indication information includes: determining to increase the counter in the at least one counter based on the received first indication information The count value of at least part of the counter.
  • the at least one counter for at least one uplink transmission includes at least one of the following: a first counter for SR; a second counter for PUSCH; and a third counter for RACH.
  • At least one of the above three counters is included in this scenario.
  • the above three counters are only examples. In actual processing, if there are more upstream transmissions, more counters can be maintained. , Just no longer exhaustive. It should also be noted that in actual processing, there may be one or more upstream transmissions corresponding to one counter. For example, two counters may be set, a fourth counter may be configured for SR and PUCCH, and a fifth counter may be configured for RACH. More counters may be the sixth counter corresponding to the preamble sequence, which is used to record how many times the preamble sequence is retransmitted in the RACH process. When the RACH process is triggered, the corresponding sixth counter is initialized to 1. When the RAR is not received in the RAR window or the contention conflict is not resolved, the preamble counter is incremented. It may also include a seventh counter that records the beam instance failure indicated by the physical layer to the MAC layer, and its initial value is 0.
  • the description is based on the above three counters, and the determining to increase the count value of at least part of the at least one counter based on the received first indication information includes: including at least one of the following:
  • the count value of the third counter is increased.
  • the information included in the first indication information indicates which upstream transmission fails, and the count value of the corresponding counter is increased.
  • the first indication information can be used to indicate SR
  • the transmission LBT fails or the PUSCH transmission LBT fails the count value of the fourth counter is increased
  • the first indication information is that the LBT corresponding to the RACH fails, the count value of the fifth counter is increased.
  • the first counter for SR; the second counter for PUSCH; and the third counter for RACH are configured with corresponding first timer, second timer, and third timer respectively .
  • Different timers can be configured for the network side. It should be noted that different timers are configured for different counters, that is, different timers are configured for at least one counter of at least one uplink transmission. Of course, the timing of different timers can be the same or different.
  • the method further includes: when the uplink transmission corresponding to the first indication information fails, the corresponding timer may be restarted or started.
  • the method further includes one of the following:
  • the global timer can be used to control the situation where a counter has not changed its count value for a long time. For example, if the count value of a certain counter has not been increased for a long time, it means that the uplink channel has not been preempted for a long time. At this time, if the next uplink transmission is to be performed again and a failure occurs, the count will be accumulated based on the count value of a counter previously recorded, but this will cause performance problems in the uplink transmission. By adding a certain timer, a certain counter can be reset when the certain timer times out. In this way, it is possible to restart counting of a certain counter when the count value of a certain counter has not been changed for a long time.
  • the method further includes: configuring at least one threshold value for the at least one counter for at least one uplink transmission.
  • the RRC reconfiguration may be at least one of the following: reconfiguration of uplink BWP, or reconfiguration of PRACH resources, reconfiguration of PUCCH resources, reconfiguration of PUSCH resources, and reconfiguration of uplink carriers, etc.
  • the SCG-RLF process is to suspend all SCG's SRB (Signaling radio bearers, signaling radio bearers) and DRB (Data Radio Radio Bearers, data radio bearers), reset the SCG MAC (Media Access Control Address, media access control) entity, and Use MCG to report the number of LBT failures online.
  • the threshold value may be a threshold value set according to actual conditions, for example, it may be set to 10, and of course, it may be set to other numerical values, which is not exhaustive here.
  • connection re-establishment request when RRC connection re-establishment is initiated, a connection re-establishment request is initiated to the network side; the connection re-establishment request includes: the number of LBT failures, and / or, the event that triggers the LBT.
  • different processing can be set for different counters.
  • the RRC layer when the count value exceeds the threshold value, the RRC layer is notified to trigger RRC reconfiguration: the RRC layer is notified to release all And configure PUCCH resources: notify the RRC layer to release all SRS: clear all configured downlink allocated resources and uplink authorized resources.
  • the second counter when the count value exceeds the threshold value, a process of notifying the RRC layer to trigger RRC reconfiguration may be performed.
  • a process of notifying the RRC layer to release all SRSs and clearing all configured downlink allocated resources and uplink authorized resources may be performed.
  • the global counter may be maintained at the MAC layer of the terminal device.
  • the physical layer indicates LBT failure to the MAC, and the MAC layer triggers the execution of the foregoing behavior.
  • it can also be maintained at the RRC layer.
  • the physical layer indicates LBT failure to RRC, and the RRC triggers the execution of the foregoing behavior.
  • the global counter and at least one counter for at least one upstream transmission can be maintained at the same time; for example, there can be a case where the global counter for global upstream transmission can be maintained at
  • the counter value can be determined based on the corresponding first indication information by maintaining the counter. In this way, when the counter passing the counter reaches a certain number, corresponding control processing can be performed, so that the uplink transmission can grab the channel, thereby ensuring the performance of the uplink transmission.
  • An embodiment of the present invention provides a terminal device, as shown in FIG. 3, including:
  • the processing unit 31 maintains at least one counter, wherein the counter is used to record the number of times the first indication information is received; based on the received first indication information, it is determined to increase the count value of the counter corresponding to the first indication information.
  • the first indication information is used to indicate one of the following: LBT failure, LBT success, SR transmission failure, preamble transmission failure, and uplink data transmission failure.
  • the first indication information sent by the physical layer may be received, and the first indication information is used to indicate LBT failure; or, when LBT succeeds, it may also be received by The received first indication information determines that the LBT failed; or, the first indication information may be used to determine that the SR transmission failure occurred in the uplink transmission; or, the first indication information may be used to determine the preamble transmission failure or the uplink data transmission failure.
  • the first indication information sent by the physical layer may also be information received from the network side, which is transmitted to the MAC layer or the RRC layer through the physical layer, and then the RRC layer or the MAC layer maintains the global counter and / or at least At least one counter for upstream transmission.
  • the processing unit 31 determines to increase the count value of the counter corresponding to the first indication information based on the received first indication information; it may include: regardless of the content contained in the received first indication information, Increase the count value of the counter corresponding to the first indication information;
  • the first indication information when it is determined that the first indication information is used to indicate at least one of LBT failure, SR transmission failure, preamble transmission failure, and uplink data transmission failure, it may be determined to increase the count value of the counter.
  • the triggering method of LBT may include one of the following: uplink PUCCH transmission scheduling request SR or HARQ feedback; uplink PUSCH transmission data; RACH process initiation. That is to say, through the uplink transmission of PUCCH, PUSCH or random access channel, the LBT process can be triggered.
  • the at least one counter includes: a global counter, and / or at least one counter for at least one uplink transmission.
  • At least one counter is a global counter.
  • the processing unit 31 determines to increase the count value of the global counter based on the received first instruction information.
  • the information that can be included in the first instruction information indicates that the count value of the global counter will be increased regardless of the failure of any kind of upstream transmission.
  • the terminal device further includes a communication unit 32, and also obtains the configured global timer corresponding to the global counter.
  • a global timer corresponding to the global counter may be configured for the terminal device through the network side.
  • the processing unit 31 After acquiring the configured global timer corresponding to the global counter, the processing unit 31 starts or restarts the global timer when receiving the first indication information.
  • the condition for starting or restarting the global timer is that the first indication information is received.
  • the count value of the global counter is increased by 1, and the global timer is started or restarted; that is, when the global timer is not running ,
  • the global timer may be started based on the first indication information, and when the global timer has started counting, the global timer may be restarted based on the first indication information.
  • the global timer can be used to control the situation where the count value of the global counter has not changed for a long time. For example, if the count value of the global counter has not been increased for a long time, that is, when there is no operation such as upstream channel preemption for a long time, if the next time When the uplink transmission is performed again and a failure occurs, the count is accumulated based on the count value of the originally recorded global counter, but this will cause performance problems in the uplink transmission.
  • the global counter can be reset when the global timer times out. In this way, it is possible to restart counting of the global counter when the count value of the global counter has not been changed for a long period of time.
  • the processing unit 31 when the global counter reaches a preset threshold, the radio resource control (RRC, Radio Resource Control) layer triggers one of the following processes: RRC connection re-establishment; secondary cell group (SCG, Secondary) Cell)-Radio link failure (RLF, Radio Link Failure) processing; RRC reconfiguration.
  • RRC Radio Resource Control
  • the RRC reconfiguration may be at least one of the following: reconfiguration of uplink BWP, or reconfiguration of PRACH resources, reconfiguration of PUCCH resources, reconfiguration of PUSCH resources, and reconfiguration of uplink carriers, etc.
  • the SCG-RLF process is to suspend all SCG's SRB (Signalling radio bearers, signaling radio bearers) and DRB (Data Radio Radio Bearers, data radio bearers), reset the SCG MAC (Media Access Control Address, media access control) entity, and Use MCG to report the number of LBT failures online.
  • the preset threshold value may be a threshold value set according to actual conditions, for example, it may be set to 10, and of course, it may also be set to other values, which is not exhaustive here.
  • the processing unit 31 initiates a connection re-establishment request to the network side through the communication unit 32;
  • the connection re-establishment request includes: the number of LBT failures, and / or, an event that triggers LBT.
  • the terminal can further report to the network in the re-establishment request message: the number of LBT failures, and / or: the event of initiating the LBT, such as the PUCCH sending SR triggering LBT and the uplink data sending trigger LBT or RACH triggers LBT, etc.
  • the global counter may be maintained at the MAC layer of the terminal device.
  • the physical layer indicates LBT failure to the MAC, and the MAC layer triggers the execution of the foregoing behavior.
  • it can also be maintained at the RRC layer.
  • the physical layer indicates LBT failure to RRC, and the RRC triggers the execution of the foregoing behavior.
  • At least one counter is at least one counter for at least one uplink transmission.
  • this scenario can maintain one or more counters, and can maintain the same or different counters for different uplink transmissions, that is, a corresponding counter can be maintained for each uplink transmission, or it can be One counter is maintained for the first part of the uplink transmission, and another counter is maintained for the remaining part of the uplink transmission.
  • the processing unit 31 determines to increase the count value of at least a part of the at least one counter based on the received first indication information.
  • the at least one counter for at least one uplink transmission includes at least one of the following: a first counter for SR; a second counter for PUSCH; and a third counter for RACH.
  • At least one of the above three counters is included in this scenario.
  • the above three counters are only examples. In actual processing, if there are more upstream transmissions, more counters can be maintained. , Just no longer exhaustive. It should also be noted that in actual processing, there may be one or more upstream transmissions corresponding to one counter. For example, two counters may be set, a fourth counter may be configured for SR and PUCCH, and a fifth counter may be configured for RACH. More counters may be the sixth counter corresponding to the preamble sequence, which is used to record how many times the preamble sequence is retransmitted in the RACH process. When the RACH process is triggered, the corresponding sixth counter is initialized to 1. When the RAR is not received in the RAR window or the contention conflict is not resolved, the preamble counter is incremented. It may also include a seventh counter that records the beam instance failure indicated by the physical layer to the MAC layer, and its initial value is 0.
  • the processing unit 31 executes at least one of the following:
  • the count value of the third counter is increased.
  • the information included in the first indication information indicates which upstream transmission fails, and the count value of the corresponding counter is increased.
  • the first indication information can be used to indicate SR
  • the transmission LBT fails or the PUSCH transmission LBT fails the count value of the fourth counter is increased
  • the first indication information is that the LBT corresponding to the RACH fails, the count value of the fifth counter is increased.
  • the first counter for SR; the second counter for PUSCH; and the third counter for RACH are configured with corresponding first timer, second timer, and third timer respectively .
  • Different timers can be configured for the network side. It should be noted that different timers are configured for different counters, that is, different timers are configured for at least one counter of at least one uplink transmission. Of course, the timing of different timers can be the same or different.
  • the processing unit 31 may restart or start the corresponding timer when the uplink transmission corresponding to the first indication information fails.
  • processing unit 31 also performs one of the following:
  • the global timer can be used to control the situation where a counter has not changed its count value for a long time. For example, if the count value of a certain counter has not been increased for a long time, it means that the uplink channel has not been preempted for a long time At this time, if the next uplink transmission is to be performed again and a failure occurs, the count will be accumulated based on the count value of a counter previously recorded, but this will cause performance problems in the uplink transmission.
  • a certain counter can be reset when the certain timer times out. In this way, it is possible to restart counting of a certain counter when the count value of a certain counter has not been changed for a long time.
  • the processing unit 31 configures at least one threshold value for at least one counter for at least one uplink transmission.
  • the processing unit 31 executes at least part of the following processing when the count value of the counter in the at least one counter exceeds a corresponding threshold value:
  • the RRC reconfiguration may be at least one of the following: reconfiguration of uplink BWP, or reconfiguration of PRACH resources, reconfiguration of PUCCH resources, reconfiguration of PUSCH resources, and reconfiguration of uplink carriers, etc.
  • the SCG-RLF process is to suspend all SCG's SRB (Signaling radio bearers) and DRB (Data Radio Radio Bearers), reset SCG MAC (Media Access Control Address) media entities, and Use MCG to report the number of LBT failures online.
  • the threshold value may be a threshold value set according to actual conditions, for example, it may be set to 10, and of course, it may be set to other numerical values, which is not exhaustive here.
  • connection re-establishment request when RRC connection re-establishment is initiated, a connection re-establishment request is initiated to the network side; the connection re-establishment request includes: the number of LBT failures, and / or, the event that triggers the LBT.
  • different processing can be set for different counters.
  • the RRC layer when the count value exceeds the threshold value, the RRC layer is notified to trigger RRC reconfiguration: the RRC layer is notified to release all And configure PUCCH resources: notify the RRC layer to release all SRS: clear all configured downlink allocated resources and uplink authorized resources.
  • the second counter when the count value exceeds the threshold value, a process of notifying the RRC layer to trigger RRC reconfiguration may be performed.
  • a process of notifying the RRC layer to release all SRSs and clearing all configured downlink allocated resources and uplink authorized resources may be performed.
  • the global counter may be maintained at the MAC layer of the terminal device.
  • the physical layer indicates LBT failure to the MAC, and the MAC layer triggers the execution of the foregoing behavior.
  • it can also be maintained at the RRC layer.
  • the physical layer indicates LBT failure to RRC, and the RRC triggers the execution of the foregoing behavior.
  • the global counter and at least one counter for at least one upstream transmission can be maintained at the same time; for example, there can be a case where the global counter for global upstream transmission can be maintained at
  • the counter value can be determined based on the corresponding first indication information by maintaining the counter. In this way, when the counter passing the counter reaches a certain number, corresponding control processing can be performed, so that the uplink transmission can grab the channel, thereby ensuring the performance of the uplink transmission.
  • FIG. 4 is a schematic structural diagram of a communication device 400 provided by an embodiment of the present application.
  • the communication device may be the foregoing terminal device or network device of this embodiment.
  • the communication device 400 shown in FIG. 4 includes a processor 410, and the processor 410 can call and run a computer program from the memory to implement the method in the embodiments of the present application.
  • the communication device 400 may further include a memory 420.
  • the processor 410 can call and run a computer program from the memory 420 to implement the method in the embodiments of the present application.
  • the memory 420 may be a separate device independent of the processor 410, or may be integrated in the processor 410.
  • the communication device 400 may further include a transceiver 430, and the processor 410 may control the transceiver 430 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 430 may include a transmitter and a receiver.
  • the transceiver 430 may further include antennas, and the number of antennas may be one or more.
  • the communication device 400 may specifically be a network device according to an embodiment of the present application, and the communication device 400 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. .
  • the communication device 400 may specifically be a terminal device or a network device according to an embodiment of the present application, and the communication device 400 may implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. It is concise and will not be repeated here.
  • FIG. 5 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 500 shown in FIG. 5 includes a processor 510, and the processor 510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 500 may further include a memory 520.
  • the processor 510 can call and run a computer program from the memory 520 to implement the method in the embodiments of the present application.
  • the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.
  • the chip 500 may further include an input interface 530.
  • the processor 510 can control the input interface 530 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.
  • the chip 500 may further include an output interface 540.
  • the processor 510 can control the output interface 540 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • chips mentioned in the embodiments of the present application may also be referred to as system-on-chips, system chips, chip systems, or system-on-chip chips.
  • FIG. 6 is a schematic block diagram of a communication system 600 provided by an embodiment of the present application. As shown in FIG. 6, the communication system 600 includes a terminal device 610 and a network device 620.
  • the terminal device 610 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 620 can be used to implement the corresponding functions implemented by the network device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a 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 (Application Specific Integrated Circuit, ASIC), an existing programmable gate array (Field Programmable Gate Array, FPGA), or other available 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 application may be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and 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 embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically Erasable programmable read only memory (Electrically, EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiments of the present application 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) 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. That is to say, the memories in the embodiments of the present application are intended to include but are not limited to these and any other suitable types of memories.
  • Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiments of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application, for simplicity , Will not repeat them here.
  • An embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, 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 application. Repeat again.
  • the computer program product may be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application, For brevity, I will not repeat them here.
  • An embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program runs on the computer, the computer is allowed to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. , Will not repeat them here.
  • the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application.
  • the computer program runs on the computer, the computer is implemented by the mobile terminal / terminal device in performing various methods of the embodiments of the present application For the sake of brevity, I will not repeat them here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a division of logical functions.
  • there may be other divisions for example, multiple units or components may be combined or 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 may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application 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 functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product
  • the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • 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 disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本发明公开了一种计数方法、终端设备、芯片、计算机可读存储介质、计算机程序产品以及计算机程序，其中方法包括：维护至少一个计数器，其中，所述计数器用于记录接收到第一指示信息的次数；基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值。

Description

一种计数方法、终端设备及装置 技术领域
本发明涉及信息处理技术领域，尤其涉及一种计数方法、终端设备、芯片、计算机可读存储介质、计算机程序产品以及计算机程序。
背景技术
当先听后发(LBT，Listen Before Talk)失败时，即随机接入信道(RACH，Random Access Channel)流程中功率攀升计数器不会累加，但是需要继续讨论是否PREAMBLE前导序列传输计数器是否需要累加。在NR-U中，由于终端设备工作在非授权频带，就有可能由于信道的不确定性会抢占不到信道，即发生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频分双工(Freq终端设备ncy 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)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment，终端设备)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可选地，终端设备120之间可以进行终端直连(Device to Device，D2D)通信。
可选地，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备 120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
实施例一、
本发明实施例提供了一种计数方法，应用于终端设备，如图2所示，包括：
步骤201：维护至少一个计数器，其中，所述计数器用于记录接收到第一指示信息的次数；
步骤202：基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值。
这里，所述第一指示信息用于指示以下之一：LBT失败、LBT成功、SR传输失败、前导序列传输失败、上行数据传输失败。
也就是说，可以在发生LBT失败的时候，可以接收物理层(PHY)发来的第一指示信息，该第一指示信息用于指示LBT失败；或者，当LBT成功的时候，也可以通过接收到的第一指示信息确定LBT失败；或者，可以通过第一指示信息来确定上行传输中发生SR传输失败；或者，可以通过第一指示信息确定前导序列传输失败或上行数据传输失败。需要理解的是，物理层发来第一指示信息还可以为从网络侧接收到的信息，通过物理层传输给MAC层或RRC层，然后由RRC层或MAC层来维护全局计数器和/或至少一个针对上行传输的至少一个计数器。
需要指出的是，前述步骤202中，基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值；可以包括有：不论接收到的第一指示信息包含的内容，均增加第一指示信息所对应的计数器的计数值；
或者，可以当确定第一指示信息用于指示LBT失败、SR传输失败、前导序列传输失败、上行数据传输失败中的至少之一时，确定增加计数器的计数值。
另外，关于LBT的触发方式，可以包括以下之一：上行PUCCH传输调度请求SR或HARQ的反馈；上行PUSCH传输数据；RACH过程的发起。也就是说，通过PUCCH、PUSCH或者随机接入信道这些上行传输，可以触发LBT过程。
关于前述步骤201以及步骤202中，所述至少一个计数器，包含：全局计数器，和/或，针对至少一种上行传输的至少一个计数器。
具体的，可以分为以下几种场景进行说明：
场景1、本场景中至少一种计数器为一个全局计数器。
这种场景中，所述基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值，包括：基于接收的第一指示信息，确定增加所述全局计数器的计数值。
也就是上述第一指示信息中能够包含的信息中指示了不论哪种上行传输发生失败都会增加全局计数器的计数值。
进一步地，本场景中，还会获取配置的对应全局计数器的全局定时器。具体来说，可以为通过网络侧为终端设备配置与全局计数器对应的全局定时器。
所述获取配置的对应全局计数器的全局定时器之后，所述方法还包括：当接收到第一指示信息时，启动或重启所述全局定时器。
也就是说，全局定时器的启动或者重启的条件为，接收到第一指示信息。进一步解释来说，当接收到网络侧为终端设备指示某一个上行传输发生失败的时候，全局计数器的计数值加1，同时将全局定时器开启或者重启；即，当全局定时器没有运行的时候，可以基于第一指示信息开启全局定时器，当全局定时器已经开始计时的时候，可以基于第一指示信息重启全局定时器。
该全局定时器能够用于控制全局计数器长期没有发生计数值改变的情况，比如，若当前长期没有增加全局计数器的计数值，也就是说长期没有进行上行信道抢占等操作的时候，若下一次要再次进行上行传输且发生失败的时候，就会在原来记录的全局计数器的计数值的基础之上累积进行计数，但是，这样就会导致上行传输发生性能有问题。通过添加全局定时器，就可以当所述全局定时器超时时，重置全局计数器。这样，就能够在很长一段时间内没有改变全局计数器的计数值的时候，能够重新开始对全局计数器进行计数。
所述方法还包括：当所述全局计数器达到预设门限值时，由无线资源控制(RRC，Radio Resource Control)层触发以下处理之一：RRC连接重建立；辅小区群组(SCG，Secondary Cell Group)-无线链路失败(RLF，Radio Link Failure)处理；RRC重配置。
其中，所述RRC重配置可以为以下至少之一：重配置上行BWP，或者重配置PRACH资源，重配置PUCCH资源，重配置PUSCH资源，重配置上行载波等。SCG-RLF流程，即暂停所有SCG的SRB(Signalling radio bearers，信令无线承载)和DRB(Data Radio Bearer，数据无线承载)，重置SCG MAC(Media Access Control Address，媒体访问控制)实体，并通过MCG想网络上报LBT失败次数。
所述预设门限值可以为根据实际情况设置的门限值，比如，可以设置为10，当然还可以设置为其他数值，这里不进行穷举。
其中，当发起RRC连接重建立时，向网络侧发起连接重建立请求；所述连接重建立请求包括：LBT失败次数，和/或，触发LBT的事件。
也就是说，如果发起了RRC重建立流程，终端进一步可以在重建立请求消息中向网络上报：LBT失败次数，和/或：发起LBT的事件，比如由于PUCCH发送SR触发 LBT，上行数据发送触发LBT或者RACH触发LBT等。
本场景中，所述全局计数器可以在终端设备的MAC层维护，比如，物理层将LBT失败指示给MAC，由MAC层触发执行前述行为行为。或者，还可以在RRC层维护，比如，物理层将LBT失败指示给RRC，由RRC触发执行前述行为。
场景2、本场景中至少一种计数器为针对至少一种上行传输的至少一个计数器。
与场景1不同在于，本场景能够维护一个或更多个计数器，并且针对不同的上行传输可以维护相同或不同的计数器，也就是说，可以针对每一个上行传输维护一个对应的计数器，也可以为针对上行传输中的第一部分上行传输维护一个计数器，针对上行传输的剩余部分维护另一个计数器。
这种场景中，所述基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值，包括：基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值。
具体来说，所述针对至少一种上行传输的至少一种计数器，至少包括以下至少之一：针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器。
也就是，本场景中至少包括有上述三个计数器中的至少一个，当然需要理解的是，上述三个计数器仅为示例，实际处理中，若存在更多的上行传输还可以维护更多的计数器，只是不再穷举。还需要指出的是，实际处理中，可能存在某一个或多个上行传输对应一个计数器，比如，可以设置两个计数器，可以为针对SR、PUCCH配置第四计数器，针对RACH配置第五计数器。更多的计数器，可以为前导序列对应的第六计数器，用于在RACH流程中，记录前导序列重传了多少次的。当RACH流程触发时，对应的第六计数器被初始化为1。当在RAR窗口中没有收到RAR或者竞争冲突没有解决时，preamble计数器加1。还可以包括记录物理层指示给MAC层的beam failure instance的第七计数器，其初始值为0。
相应的，基于上述三种计数器来进行说明，所述基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值，包括：包括以下至少之一：
当所述第一指示信息为对应SR传输的LBT失败时，增加所述第一计数器的计数值；
当所述第一指示信息为对应PUSCH传输的LBT失败时，增加所述第二计数器的计数值；
当所述第一指示信息为对应RACH的LBT失败时，增加所述第三计数器的计数值。
也就是上述第一指示信息中包含的信息中指示哪种上行传输发生失败都会增加相应计数器的计数值。当然，还需要理解的是，当某几个上行传输对应同一个计数器的时候，比如，针对SR、PUCCH配置第四计数器，针对RACH配置第五计数器的时候，可以当第一指示信息为指示SR传输的LBT失败或PUSCH传输的LBT失败的时候，增加第四计数器的计数值；以及当第一指示信息为对应RACH的LBT失败时，增加第五计数器的计数值。前述仅为示例，实际处理中可以存在其他的上行传输对应一个计数器 的情况，这里不穷举。
进一步地，本场景中，还会所述针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器，分别配置对应的第一定时器、第二定时器以及第三定时器。可以为由网络侧为其配置的不同的定时器，需要指出的是，针对不同的计数器会配置不同的定时器，也就是说，针对至少一种上行传输的至少一个计数器分别配置不同的定时器，当然，不同的定时器的定时时长可以相同也可以不同。
所述获取配置的定时器之后，所述方法还包括：当接收到第一指示信息所对应的上行传输失败时，可以重启或启动对应的定时器。
具体的，所述方法还包括以下之一：
当接收到第一指示信息为对应SR传输的LBT失败时，启动或重启所述第一定时器；
当接收到所述第一指示信息为对应PUSCH传输的LBT失败时，启动或重启所述第二定时器；
当接收到所述第一指示信息为对应RACH的LBT失败时，启动或重启所述第三定时器。
也就是说，该全局定时器能够用于控制某一个计数器长期没有发生计数值改变的情况，比如，若当前长期没有增加某一个计数器的计数值，也就是说长期没有进行上行信道抢占等操作的时候，若下一次要再次进行上行传输且发生失败的时候，就会在原来记录的某一个计数器的计数值的基础之上累积进行计数，但是，这样就会导致上行传输发生性能有问题。通过添加某一个定时器，就可以当所述某一个定时器超时时，重置某一个计数器。这样，就能够在很长一段时间内没有改变某一个计数器的计数值的时候，能够重新开始对某一个计数器进行计数。
所述方法还包括：所述针对至少一种上行传输的至少一个计数器，配置至少一个门限值。
当所述至少一个计数器中存在计数器的计数值超过对应的门限值时，执行以下处理中的至少部分：
通知RRC层触发RRC重建立：
通知RRC层触发RRC重配置：
通知RRC层释放所有与配置PUCCH资源：
通知RRC层释放所有SRS：
清除所有配置的下行分配资源和上行授权资源：
发起RACH流程：
通知网络侧LBT失败次数；
通知网络侧触发LBT的事件。
其中，所述RRC重配置可以为以下至少之一：重配置上行BWP，或者重配置PRACH资源，重配置PUCCH资源，重配置PUSCH资源，重配置上行载波等。SCG-RLF流程， 即暂停所有SCG的SRB(Signaling radio bearers，信令无线承载)和DRB(Data Radio Bearer，数据无线承载)，重置SCG MAC(Media Access Control Address，媒体访问控制)实体，并通过MCG想网络上报LBT失败次数。
所述门限值可以为根据实际情况设置的门限值，比如，可以设置为10，当然还可以设置为其他数值，这里不进行穷举。
其中，当发起RRC连接重建立时，向网络侧发起连接重建立请求；所述连接重建立请求包括：LBT失败次数，和/或，触发LBT的事件。
需要指出的是，本场景中，可以针对不同的计数器设置不同的处理，比如，针对第一计数器，可以设置计数值超过门限值时候，执行通知RRC层触发RRC重配置：通知RRC层释放所有与配置PUCCH资源：通知RRC层释放所有SRS：清除所有配置的下行分配资源和上行授权资源。针对第二计数器，可以设置当计数值超过门限值时候，执行通知RRC层触发RRC重配置的处理。针对第三计数器，可以设置计数值超过门限值的时候，执行通知RRC层释放所有SRS，以及清除所有配置的下行分配资源和上行授权资源的处理。需要理解的是，针对不同的计数器设置不同的处理，当然也可以设置相同的处理，只是这里不再穷举。
本场景中，所述全局计数器可以在终端设备的MAC层维护，比如，物理层将LBT失败指示给MAC，由MAC层触发执行前述行为行为。或者，还可以在RRC层维护，比如，物理层将LBT失败指示给RRC，由RRC触发执行前述行为。
最后，结合前述场景1、2，还需要说明的是，可以同时维护全局计数器、以及针对至少一个上行传输的至少一个计数器；比如，可以有一种情况，当前可以维护针对全局上行传输的全局计数器，当然，还可以维护针对其中某一个或某几个上行传输的一个计数器，或者，还可以维护针对某一个或某几个上行传输中每一个上行传输的计数器。也就是说，前述场景1、2可以同时存在，同时存在的时候，分别基于前述场景中的方式处理，不再赘述。
可见，通过采用上述方案，就能够通过维护计数器，基于对应的第一指示信息来确定计数器的计数值。如此，就能够在通过计数器的计数器达到一定的数量的时候，进行相应的控制处理，从而使得上行传输能够抢到信道，进而保证了上行传输的性能。
实施例二、
本发明实施例提供了一种终端设备，如图3所示，包括：
处理单元31，维护至少一个计数器，其中，所述计数器用于记录接收到第一指示信息的次数；基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值。
这里，所述第一指示信息用于指示以下之一：LBT失败、LBT成功、SR传输失败、前导序列传输失败、上行数据传输失败。
也就是说，可以在发生LBT失败的时候，可以接收物理层(PHY)发来的第一指 示信息，该第一指示信息用于指示LBT失败；或者，当LBT成功的时候，也可以通过接收到的第一指示信息确定LBT失败；或者，可以通过第一指示信息来确定上行传输中发生SR传输失败；或者，可以通过第一指示信息确定前导序列传输失败或上行数据传输失败。需要理解的是，物理层发来第一指示信息还可以为从网络侧接收到的信息，通过物理层传输给MAC层或RRC层，然后由RRC层或MAC层来维护全局计数器和/或至少一个针对上行传输的至少一个计数器。
需要指出的是，处理单元31，基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值；可以包括有：不论接收到的第一指示信息包含的内容，均增加第一指示信息所对应的计数器的计数值；
或者，可以当确定第一指示信息用于指示LBT失败、SR传输失败、前导序列传输失败、上行数据传输失败中的至少之一时，确定增加计数器的计数值。
另外，关于LBT的触发方式，可以包括以下之一：上行PUCCH传输调度请求SR或HARQ的反馈；上行PUSCH传输数据；RACH过程的发起。也就是说，通过PUCCH、PUSCH或者随机接入信道这些上行传输，可以触发LBT过程。
所述至少一个计数器，包含：全局计数器，和/或，针对至少一种上行传输的至少一个计数器。
具体的，可以分为以下几种场景进行说明：
场景1、本场景中至少一种计数器为一个全局计数器。
这种场景中，所述处理单元31，基于接收的第一指示信息，确定增加所述全局计数器的计数值。
也就是上述第一指示信息中能够包含的信息中指示了不论哪种上行传输发生失败都会增加全局计数器的计数值。
进一步地，本场景中，所述终端设备还包括通信单元32，还会获取配置的对应全局计数器的全局定时器。具体来说，可以为通过网络侧为终端设备配置与全局计数器对应的全局定时器。
所述获取配置的对应全局计数器的全局定时器之后，所述处理单元31，当接收到第一指示信息时，启动或重启所述全局定时器。
也就是说，全局定时器的启动或者重启的条件为，接收到第一指示信息。进一步解释来说，当接收到网络侧为终端设备指示某一个上行传输发生失败的时候，全局计数器的计数值加1，同时将全局定时器开启或者重启；即，当全局定时器没有运行的时候，可以基于第一指示信息开启全局定时器，当全局定时器已经开始计时的时候，可以基于第一指示信息重启全局定时器。
该全局定时器能够用于控制全局计数器长期没有发生计数值改变的情况，比如，若当前长期没有增加全局计数器的计数值，也就是说长期没有进行上行信道抢占等操作的时候，若下一次要再次进行上行传输且发生失败的时候，就会在原来记录的全局计数器 的计数值的基础之上累积进行计数，但是，这样就会导致上行传输发生性能有问题。通过添加全局定时器，就可以当所述全局定时器超时时，重置全局计数器。这样，就能够在很长一段时间内没有改变全局计数器的计数值的时候，能够重新开始对全局计数器进行计数。
所述处理单元31，当所述全局计数器达到预设门限值时，由无线资源控制(RRC，Radio Resource Control)层触发以下处理之一：RRC连接重建立；辅小区群组(SCG，Secondary Cell Group)-无线链路失败(RLF，Radio Link Failure)处理；RRC重配置。
其中，所述RRC重配置可以为以下至少之一：重配置上行BWP，或者重配置PRACH资源，重配置PUCCH资源，重配置PUSCH资源，重配置上行载波等。SCG-RLF流程，即暂停所有SCG的SRB(Signalling radio bearers，信令无线承载)和DRB(Data Radio Bearer，数据无线承载)，重置SCG MAC(Media Access Control Address，媒体访问控制)实体，并通过MCG想网络上报LBT失败次数。
所述预设门限值可以为根据实际情况设置的门限值，比如，可以设置为10，当然还可以设置为其他数值，这里不进行穷举。
其中，处理单元31，当发起RRC连接重建立时，通过通信单元32向网络侧发起连接重建立请求；所述连接重建立请求包括：LBT失败次数，和/或，触发LBT的事件。
也就是说，如果发起了RRC重建立流程，终端进一步可以在重建立请求消息中向网络上报：LBT失败次数，和/或：发起LBT的事件，比如由于PUCCH发送SR触发LBT，上行数据发送触发LBT或者RACH触发LBT等。
本场景中，所述全局计数器可以在终端设备的MAC层维护，比如，物理层将LBT失败指示给MAC，由MAC层触发执行前述行为行为。或者，还可以在RRC层维护，比如，物理层将LBT失败指示给RRC，由RRC触发执行前述行为。
场景2、本场景中至少一种计数器为针对至少一种上行传输的至少一个计数器。
与场景1不同在于，本场景能够维护一个或更多个计数器，并且针对不同的上行传输可以维护相同或不同的计数器，也就是说，可以针对每一个上行传输维护一个对应的计数器，也可以为针对上行传输中的第一部分上行传输维护一个计数器，针对上行传输的剩余部分维护另一个计数器。
这种场景中，所述处理单元31，基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值。
具体来说，所述针对至少一种上行传输的至少一种计数器，至少包括以下至少之一：针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器。
也就是，本场景中至少包括有上述三个计数器中的至少一个，当然需要理解的是，上述三个计数器仅为示例，实际处理中，若存在更多的上行传输还可以维护更多的计数器，只是不再穷举。还需要指出的是，实际处理中，可能存在某一个或多个上行传输对应一个计数器，比如，可以设置两个计数器，可以为针对SR、PUCCH配置第四计数器， 针对RACH配置第五计数器。更多的计数器，可以为前导序列对应的第六计数器，用于在RACH流程中，记录前导序列重传了多少次的。当RACH流程触发时，对应的第六计数器被初始化为1。当在RAR窗口中没有收到RAR或者竞争冲突没有解决时，preamble计数器加1。还可以包括记录物理层指示给MAC层的beam failure instance的第七计数器，其初始值为0。
相应的，基于上述三种计数器来进行说明，所述基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值，处理单元31，执行以下至少之一：
当所述第一指示信息为对应SR传输的LBT失败时，增加所述第一计数器的计数值；
当所述第一指示信息为对应PUSCH传输的LBT失败时，增加所述第二计数器的计数值；
当所述第一指示信息为对应RACH的LBT失败时，增加所述第三计数器的计数值。
也就是上述第一指示信息中包含的信息中指示哪种上行传输发生失败都会增加相应计数器的计数值。当然，还需要理解的是，当某几个上行传输对应同一个计数器的时候，比如，针对SR、PUCCH配置第四计数器，针对RACH配置第五计数器的时候，可以当第一指示信息为指示SR传输的LBT失败或PUSCH传输的LBT失败的时候，增加第四计数器的计数值；以及当第一指示信息为对应RACH的LBT失败时，增加第五计数器的计数值。前述仅为示例，实际处理中可以存在其他的上行传输对应一个计数器的情况，这里不穷举。
进一步地，本场景中，还会所述针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器，分别配置对应的第一定时器、第二定时器以及第三定时器。可以为由网络侧为其配置的不同的定时器，需要指出的是，针对不同的计数器会配置不同的定时器，也就是说，针对至少一种上行传输的至少一个计数器分别配置不同的定时器，当然，不同的定时器的定时时长可以相同也可以不同。
所述获取配置的定时器之后，所述处理单元31，当接收到第一指示信息所对应的上行传输失败时，可以重启或启动对应的定时器。
具体的，所述处理单元31，还执行以下之一：
当接收到第一指示信息为对应SR传输的LBT失败时，启动或重启所述第一定时器；
当接收到所述第一指示信息为对应PUSCH传输的LBT失败时，启动或重启所述第二定时器；
当接收到所述第一指示信息为对应RACH的LBT失败时，启动或重启所述第三定时器。
也就是说，该全局定时器能够用于控制某一个计数器长期没有发生计数值改变的情况，比如，若当前长期没有增加某一个计数器的计数值，也就是说长期没有进行上行信道抢占等操作的时候，若下一次要再次进行上行传输且发生失败的时候，就会在原来记录的某一个计数器的计数值的基础之上累积进行计数，但是，这样就会导致上行传输发 生性能有问题。通过添加某一个定时器，就可以当所述某一个定时器超时时，重置某一个计数器。这样，就能够在很长一段时间内没有改变某一个计数器的计数值的时候，能够重新开始对某一个计数器进行计数。
所述处理单元31，所述针对至少一种上行传输的至少一个计数器，配置至少一个门限值。
处理单元31，当所述至少一个计数器中存在计数器的计数值超过对应的门限值时，执行以下处理中的至少部分：
通知RRC层触发RRC重建立：
通知RRC层触发RRC重配置：
通知RRC层释放所有与配置PUCCH资源：
通知RRC层释放所有SRS：
清除所有配置的下行分配资源和上行授权资源：
发起RACH流程：
通知网络侧LBT失败次数；
通知网络侧触发LBT的事件。
其中，所述RRC重配置可以为以下至少之一：重配置上行BWP，或者重配置PRACH资源，重配置PUCCH资源，重配置PUSCH资源，重配置上行载波等。SCG-RLF流程，即暂停所有SCG的SRB(Signaling radio bearers，信令无线承载)和DRB(Data Radio Bearer，数据无线承载)，重置SCG MAC(Media Access Control Address，媒体访问控制)实体，并通过MCG想网络上报LBT失败次数。
所述门限值可以为根据实际情况设置的门限值，比如，可以设置为10，当然还可以设置为其他数值，这里不进行穷举。
其中，当发起RRC连接重建立时，向网络侧发起连接重建立请求；所述连接重建立请求包括：LBT失败次数，和/或，触发LBT的事件。
需要指出的是，本场景中，可以针对不同的计数器设置不同的处理，比如，针对第一计数器，可以设置计数值超过门限值时候，执行通知RRC层触发RRC重配置：通知RRC层释放所有与配置PUCCH资源：通知RRC层释放所有SRS：清除所有配置的下行分配资源和上行授权资源。针对第二计数器，可以设置当计数值超过门限值时候，执行通知RRC层触发RRC重配置的处理。针对第三计数器，可以设置计数值超过门限值的时候，执行通知RRC层释放所有SRS，以及清除所有配置的下行分配资源和上行授权资源的处理。需要理解的是，针对不同的计数器设置不同的处理，当然也可以设置相同的处理，只是这里不再穷举。
本场景中，所述全局计数器可以在终端设备的MAC层维护，比如，物理层将LBT失败指示给MAC，由MAC层触发执行前述行为行为。或者，还可以在RRC层维护，比如，物理层将LBT失败指示给RRC，由RRC触发执行前述行为。
最后，结合前述场景1、2，还需要说明的是，可以同时维护全局计数器、以及针对至少一个上行传输的至少一个计数器；比如，可以有一种情况，当前可以维护针对全局上行传输的全局计数器，当然，还可以维护针对其中某一个或某几个上行传输的一个计数器，或者，还可以维护针对某一个或某几个上行传输中每一个上行传输的计数器。也就是说，前述场景1、2可以同时存在，同时存在的时候，分别基于前述场景中的方式处理，不再赘述。
可见，通过采用上述方案，就能够通过维护计数器，基于对应的第一指示信息来确定计数器的计数值。如此，就能够在通过计数器的计数器达到一定的数量的时候，进行相应的控制处理，从而使得上行传输能够抢到信道，进而保证了上行传输的性能。
图4是本申请实施例提供的一种通信设备400示意性结构图，通信设备可以为本实施例前述的终端设备或者网络设备。图4所示的通信设备400包括处理器410，处理器410可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图4所示，通信设备400还可以包括存储器420。其中，处理器410可以从存储器420中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器420可以是独立于处理器410的一个单独的器件，也可以集成在处理器410中。
可选地，如图4所示，通信设备400还可以包括收发器430，处理器410可以控制该收发器430与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器430可以包括发射机和接收机。收发器430还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备400具体可为本申请实施例的网络设备，并且该通信设备400可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备400具体可为本申请实施例的终端设备、或者网络设备，并且该通信设备400可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图5是本申请实施例的芯片的示意性结构图。图5所示的芯片500包括处理器510，处理器510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图5所示，芯片500还可以包括存储器520。其中，处理器510可以从存储器520中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器520可以是独立于处理器510的一个单独的器件，也可以集成在处理器510中。
可选地，该芯片500还可以包括输入接口530。其中，处理器510可以控制该输入接口530与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或 数据。
可选地，该芯片500还可以包括输出接口540。其中，处理器510可以控制该输出接口540与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的终端设备，并且该芯片可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图6是本申请实施例提供的一种通信系统600的示意性框图。如图6所示，该通信系统600包括终端设备610和网络设备620。
其中，该终端设备610可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备620可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究 竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (37)

  1. 一种计数方法，应用于终端设备，包括：
    维护至少一个计数器，其中，所述计数器用于记录接收到第一指示信息的次数；
    基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值。
  2. 根据权利要求1所述的方法，其中，所述第一指示信息用于指示以下之一：
    LBT失败、LBT成功、SR传输失败、前导序列传输失败、上行数据传输失败。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    基于以下之一，触发执行LBT：
    上行PUCCH传输调度请求SR或HARQ的反馈；
    上行PUSCH传输数据；
    RACH过程的发起。
  4. 根据权利要求1-3任一项所述的方法，其中，所述至少一个计数器，包含：全局计数器，和/或，针对至少一种上行传输的至少一个计数器。
  5. 根据权利要求4所述的方法，其中，所述基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值，包括：
    基于接收的第一指示信息，确定增加所述全局计数器的计数值；
    和/或，基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值。
  6. 根据权利要求4或5所述的方法，其中，所述方法还包括：
    获取配置的对应全局计数器的全局定时器；
    和/或，获取配置的与所述针对至少一种上行传输的至少一个计数器对应的至少一个定时器。
  7. 根据权利要求6所述的方法，其中，所述获取配置的对应全局计数器的全局定时器之后，所述方法还包括：
    当接收到第一指示信息时，启动或重启所述全局定时器。
  8. 根据权利要求7所述的方法，所述启动或重启所述全局定时器之后，所述方法还包括：
    当所述全局定时器超时时，重置全局计数器。
  9. 根据权利要求4-8任一项所述的方法，其中，所述方法还包括：
    当所述全局计数器达到预设门限值时，由无线资源控制RRC层触发以下处理之一：
    RRC连接重建立；辅小区群SCG-无线链路失败RLF处理；RRC重配置。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    当发起RRC连接重建立时，向网络侧发起连接重建立请求；
    其中，所述连接重建立请求包括：LBT失败次数，和/或，触发LBT的事件。
  11. 根据权利要求4所述的方法，其中，所述针对至少一种上行传输的至少一种计数器，至少包括以下至少之一：针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器。
  12. 根据权利要求11所述的方法，其中，所述基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值，包括以下至少之一：
    当所述第一指示信息为对应SR传输的LBT失败时，增加所述第一计数器的计数值；
    当所述第一指示信息为对应PUSCH传输的LBT失败时，增加所述第二计数器的计数值；
    当所述第一指示信息为对应RACH的LBT失败时，增加所述第三计数器的计数值。
  13. 根据权利要求11所述的方法，其中，
    所述针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器，分别配置对应的第一定时器、第二定时器以及第三定时器。
  14. 根据权利要求13所述的方法，其中，所述方法还包括以下之一：
    当接收到第一指示信息为对应SR传输的LBT失败时，启动或重启所述第一定时器；
    当接收到所述第一指示信息为对应PUSCH传输的LBT失败时，启动或重启所述第二定时器；
    当接收到所述第一指示信息为对应RACH的LBT失败时，启动或重启所述第三定时器。
  15. 根据权利要求11-14任一项所述的方法，其中，所述方法还包括：
    所述针对至少一种上行传输的至少一个计数器，配置至少一个门限值。
  16. 根据权利要求15所述的方法，其中，所述方法还包括：
    当所述至少一个计数器中存在计数器的计数值超过对应的门限值时，执行以下处理中的至少部分：
    通知RRC层触发RRC重建立：
    通知RRC层触发RRC重配置：
    通知RRC层释放所有与配置PUCCH资源：
    通知RRC层释放所有SRS：
    清除所有配置的下行分配资源和上行授权资源：
    发起RACH流程：
    通知网络侧LBT失败次数；
    通知网络侧触发LBT的事件。
  17. 一种终端设备，包括：
    处理单元，维护至少一个计数器，其中，所述计数器用于记录接收到第一指示信息的次数；基于接收的第一指示信息，确定增加所述第一指示信息所对应的计数器的计数值。
  18. 根据权利要求17所述的终端设备，其中，所述第一指示信息用于指示以下之一：
    LBT失败、LBT成功、SR传输失败、前导序列传输失败、上行数据传输失败。
  19. 根据权利要求18所述的终端设备，其中，所述处理单元，基于以下之一，触发执行LBT：
    上行PUCCH传输调度请求SR或HARQ的反馈；
    上行PUSCH传输数据；
    RACH过程的发起。
  20. 根据权利要求17-19任一项所述的终端设备，其中，所述至少一个计数器，包含：全局计数器，和/或，针对至少一种上行传输的至少一个计数器。
  21. 根据权利要求20所述的终端设备，其中，所述处理单元，基于接收的第一指示信息，确定增加所述全局计数器的计数值；
    和/或，基于接收的第一指示信息，确定增加所述至少一个计数器中的至少部分计数器的计数值。
  22. 根据权利要求20或21所述的终端设备，其中，所述终端设备还包括：
    通信单元，获取配置的对应全局计数器的全局定时器；
    和/或，获取配置的与所述针对至少一种上行传输的至少一个计数器对应的至少一个 定时器。
  23. 根据权利要求22所述的终端设备，其中，所述处理单元，当接收到第一指示信息时，启动或重启所述全局定时器。
  24. 根据权利要求23所述的终端设备，其中，所述处理单元，当所述全局定时器超时时，重置全局计数器。
  25. 根据权利要求20-24任一项所述的终端设备，其中，所述处理单元，当所述全局计数器达到预设门限值时，控制由RRC层触发以下处理之一：
    RRC连接重建立；辅小区群SCG-无线链路失败RLF处理；RRC重配置。
  26. 根据权利要求25所述的终端设备，其中，所述处理单元，当发起RRC连接重建立时，控制通过通信单元向网络侧发起连接重建立请求；
    其中，所述连接重建立请求包括：LBT失败次数，和/或，触发LBT的事件。
  27. 根据权利要求20所述的终端设备，其中，所述针对至少一种上行传输的至少一种计数器，至少包括以下至少之一：针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器。
  28. 根据权利要求27所述的终端设备，其中，所述处理单元，包括以下至少之一：
    当所述第一指示信息为对应SR传输的LBT失败时，增加所述第一计数器的计数值；
    当所述第一指示信息为对应PUSCH传输的LBT失败时，增加所述第二计数器的计数值；
    当所述第一指示信息为对应RACH的LBT失败时，增加所述第三计数器的计数值。
  29. 根据权利要求27所述的终端设备，其中，
    所述处理单元，针对SR的第一计数器；针对PUSCH的第二计数器；针对RACH的第三计数器，分别配置对应的第一定时器、第二定时器以及第三定时器。
  30. 根据权利要求29所述的终端设备，其中，所述处理单元，执行以下之一：
    当接收到第一指示信息为对应SR传输的LBT失败时，启动或重启所述第一定时器；
    当接收到所述第一指示信息为对应PUSCH传输的LBT失败时，启动或重启所述第二定时器；
    当接收到所述第一指示信息为对应RACH的LBT失败时，启动或重启所述第三定时器。
  31. 根据权利要求27-30任一项所述的终端设备，其中，所述处理单元，所述针对至少一种上行传输的至少一个计数器，配置至少一个门限值。
  32. 根据权利要求31所述的终端设备，其中，所述处理单元，当所述至少一个计数器中存在计数器的计数值超过对应的门限值时，执行以下处理中的至少部分：
    通知RRC层触发RRC重建立：
    通知RRC层触发RRC重配置：
    通知RRC层释放所有与配置PUCCH资源：
    通知RRC层释放所有SRS：
    清除所有配置的下行分配资源和上行授权资源：
    发起RACH流程：
    通知网络侧LBT失败次数；
    通知网络侧触发LBT的事件。
  33. 一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1-16任一项所述方法的步骤。
  34. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1-16中任一项所述的方法。
  35. 一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1-16任一项所述方法的步骤。
  36. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1-16中任一项所述的方法。
  37. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1-16中任一项所述的方法。
PCT/CN2018/113118 2018-10-31 2018-10-31 一种计数方法、终端设备及装置 WO2020087369A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
EP18938371.4A EP3863359B1 (en) 2018-10-31 2018-10-31 Counting method, terminal device, and apparatus
CN202110572029.7A CN113316172B (zh) 2018-10-31 2018-10-31 一种计数方法、终端设备及装置
KR1020217014876A KR20210084506A (ko) 2018-10-31 2018-10-31 카운팅 방법, 단말기 디바이스 및 장치
JP2021523625A JP7353365B2 (ja) 2018-10-31 2018-10-31 カウント方法、端末デバイス及び装置
CN201880097125.7A CN112673701A (zh) 2018-10-31 2018-10-31 一种计数方法、终端设备及装置
PCT/CN2018/113118 WO2020087369A1 (zh) 2018-10-31 2018-10-31 一种计数方法、终端设备及装置
AU2018448175A AU2018448175A1 (en) 2018-10-31 2018-10-31 Counting method, terminal device, and apparatus
US17/243,495 US11785487B2 (en) 2018-10-31 2021-04-28 Counting method, terminal device, and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/113118 WO2020087369A1 (zh) 2018-10-31 2018-10-31 一种计数方法、终端设备及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/243,495 Continuation US11785487B2 (en) 2018-10-31 2021-04-28 Counting method, terminal device, and apparatus

Publications (1)

Publication Number Publication Date
WO2020087369A1 true WO2020087369A1 (zh) 2020-05-07

Family

ID=70462494

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/113118 WO2020087369A1 (zh) 2018-10-31 2018-10-31 一种计数方法、终端设备及装置

Country Status (7)

Country Link
US (1) US11785487B2 (zh)
EP (1) EP3863359B1 (zh)
JP (1) JP7353365B2 (zh)
KR (1) KR20210084506A (zh)
CN (2) CN113316172B (zh)
AU (1) AU2018448175A1 (zh)
WO (1) WO2020087369A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115669203A (zh) * 2020-05-18 2023-01-31 日本电气株式会社 用于通信的方法、设备和计算机可读介质
US11805544B2 (en) 2019-01-09 2023-10-31 Hannibal Ip Llc Method and apparatus for LBT failure detection

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112021010650A2 (pt) * 2018-12-28 2021-08-17 Zte Corporation métodos, aparelho e sistemas para indicar falhas de transmissão em uma comunicação sem uso de fios
US11627624B2 (en) * 2019-07-25 2023-04-11 FG Innovation Company Limited Method and apparatus for handling LBT failure
EP4033849A1 (en) * 2021-01-20 2022-07-27 ASUSTek Computer Inc. Method and apparatus for determining channel access in a wireless communication system
US11700046B2 (en) * 2021-06-04 2023-07-11 Qualcomm Incorporated Beam failure avoidance based on detected interference

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101848495A (zh) * 2009-03-27 2010-09-29 中兴通讯股份有限公司 随机接入处理方法和处理系统
CN102067704A (zh) * 2008-06-18 2011-05-18 Lg电子株式会社 用于检测随机接入过程失败的方法
CN102396288A (zh) * 2009-03-12 2012-03-28 交互数字专利控股公司 无线电链路失败的监控方法和设备
CN102595603A (zh) * 2012-01-17 2012-07-18 大唐移动通信设备有限公司 一种bsr的传输控制方法及装置
US20160345362A1 (en) * 2015-05-21 2016-11-24 Newracom, Inc. Channel access for multi-user communication

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6891819B1 (en) * 1997-09-05 2005-05-10 Kabushiki Kaisha Toshiba Mobile IP communications scheme incorporating individual user authentication
US7512086B2 (en) * 2000-06-12 2009-03-31 Samsung Electronics Co., Ltd Method of assigning an uplink random access channel in a CDMA mobile communication system
US6862703B2 (en) * 2001-08-13 2005-03-01 Credence Systems Corporation Apparatus for testing memories with redundant storage elements
JP4346996B2 (ja) * 2003-08-29 2009-10-21 株式会社日立コミュニケーションテクノロジー 移動通信システム
JP2006012253A (ja) * 2004-06-23 2006-01-12 Advantest Corp 試験装置及び試験方法
GB2461780B (en) * 2008-06-18 2011-01-05 Lg Electronics Inc Method for detecting failures of random access procedures
KR100949972B1 (ko) * 2009-01-02 2010-03-29 엘지전자 주식회사 단말의 임의접속 수행 기법
KR101582196B1 (ko) * 2009-04-29 2016-01-04 삼성전자 주식회사 이동통신 시스템에서 네트워크의 랜덤 액세스 프리엠블 및 자원 최적화 장치 및 방법
US8804632B2 (en) * 2009-10-30 2014-08-12 Lg Electronics Inc. Method of performing random access procedure in multiple component carrier system
US8411588B2 (en) * 2009-11-09 2013-04-02 Research In Motion Limited Methods and apparatus to manage wireless device power consumption
US20140133656A1 (en) * 2012-02-22 2014-05-15 Qualcomm Incorporated Preserving Security by Synchronizing a Nonce or Counter Between Systems
US10027359B2 (en) * 2014-08-13 2018-07-17 Qualcomm Incorporated Managing transmitter collisions
US10841931B2 (en) 2015-06-26 2020-11-17 Wilus Institute Of Standards And Technology Inc. Wireless communication method for uplink multiple-user transmission schedule and wireless communication terminal using the method
US10420147B2 (en) * 2015-07-05 2019-09-17 Ofinno, Llc Random access process in carrier aggregation
US10187907B2 (en) * 2015-07-05 2019-01-22 Ofinno Technologies, Llc Preamble transmission in a wireless device
GB2542172A (en) * 2015-09-10 2017-03-15 Nec Corp Communication system
US20180124831A1 (en) 2016-10-29 2018-05-03 Ofinno Technologies, Llc Dual connectivity scheduling request for wireless network and wireless device
JP2020010075A (ja) * 2016-11-11 2020-01-16 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路
US10681738B2 (en) 2016-12-16 2020-06-09 Ofinno, Llc Random access in a wireless device and wireless network
CN109547167B (zh) * 2017-08-02 2022-03-29 华为技术有限公司 一种计数方法及通信装置
TWI800554B (zh) * 2017-11-14 2023-05-01 美商內數位專利控股公司 無線系統中輔助上鏈
WO2019096394A1 (en) * 2017-11-16 2019-05-23 Huawei Technologies Co., Ltd. Processing device and method for beam failure recovery
US10602549B2 (en) * 2018-03-05 2020-03-24 Asustek Computer Inc. Method and apparatus of handling beam failure recovery in a wireless communication system
CN112154706B (zh) * 2018-04-03 2024-04-16 交互数字专利控股公司 用于信道接入管理的方法
US11277302B2 (en) * 2018-06-21 2022-03-15 Ofinno, Llc PUCCH based beam failure recovery procedure
EP3609285B1 (en) * 2018-08-09 2021-10-06 Comcast Cable Communications, LLC Resource management for beam failure recovery procedures
CA3056217A1 (en) * 2018-09-21 2020-03-21 Comcast Cable Communications, Llc Activation and deactivation of power saving operation
EP3627721A1 (en) * 2018-09-24 2020-03-25 Comcast Cable Communications LLC Beam failure recovery procedures
US11343735B2 (en) * 2018-09-25 2022-05-24 Comcast Cable Communications, Llc Beam configuration for secondary cells

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102067704A (zh) * 2008-06-18 2011-05-18 Lg电子株式会社 用于检测随机接入过程失败的方法
CN102396288A (zh) * 2009-03-12 2012-03-28 交互数字专利控股公司 无线电链路失败的监控方法和设备
CN101848495A (zh) * 2009-03-27 2010-09-29 中兴通讯股份有限公司 随机接入处理方法和处理系统
CN102595603A (zh) * 2012-01-17 2012-07-18 大唐移动通信设备有限公司 一种bsr的传输控制方法及装置
US20160345362A1 (en) * 2015-05-21 2016-11-24 Newracom, Inc. Channel access for multi-user communication

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11805544B2 (en) 2019-01-09 2023-10-31 Hannibal Ip Llc Method and apparatus for LBT failure detection
CN115669203A (zh) * 2020-05-18 2023-01-31 日本电气株式会社 用于通信的方法、设备和计算机可读介质

Also Published As

Publication number Publication date
US20210250793A1 (en) 2021-08-12
CN113316172B (zh) 2023-01-06
EP3863359B1 (en) 2024-05-08
KR20210084506A (ko) 2021-07-07
JP7353365B2 (ja) 2023-09-29
EP3863359A1 (en) 2021-08-11
JP2022509744A (ja) 2022-01-24
CN113316172A (zh) 2021-08-27
CN112673701A (zh) 2021-04-16
US11785487B2 (en) 2023-10-10
AU2018448175A1 (en) 2021-06-03
EP3863359A4 (en) 2021-12-01

Similar Documents

Publication Publication Date Title
WO2020087369A1 (zh) 一种计数方法、终端设备及装置
US11825519B2 (en) Random access method, terminal device, network device, and storage medium
US20210289560A1 (en) Method for selecting random access procedure, terminal device and network device
WO2020020332A1 (zh) 一种随机接入方法、终端设备及存储介质
WO2019237805A1 (zh) 一种随机接入方法及装置、通信设备
WO2020186466A1 (zh) 无线通信的方法、终端设备和网络设备
AU2019291439A1 (en) Channel access method and apparatus for physical random access channel transmission, and program
TW202025838A (zh) 通訊方法、終端設備和網路設備
WO2020191599A1 (zh) 通信方法、终端设备和网络设备
WO2020024616A1 (zh) 一种随机接入方法及相关设备
WO2020087476A1 (zh) 传输系统信息的方法和设备
CN112789939B (zh) 一种功率控制方法及装置、终端、网络设备
WO2020227907A1 (zh) 一种资源确定方法及装置、终端
WO2021026841A1 (zh) 调度请求传输的方法和设备
WO2020215330A1 (zh) 随机接入过程中传输信息的方法、终端设备和网络设备
WO2020206643A1 (zh) 一种随机接入方法、设备及存储介质
WO2020191592A1 (zh) 一种寻呼时机配置方法及装置、终端、网络设备
WO2020051919A1 (zh) 一种资源确定及配置方法、装置、终端、网络设备
WO2020056606A1 (zh) 确定上行控制信息传输资源个数的方法、装置及程序
WO2020077600A1 (zh) 一种触发波束失败恢复的方法及装置、终端
WO2020010612A1 (zh) 波束失败恢复实现方法、装置、芯片及计算机程序
WO2022267069A1 (zh) 通信方法及装置
WO2019242382A1 (zh) 一种指示信道接入类型的方法、终端设备及网络设备
WO2020061869A1 (zh) 一种链路恢复方法及装置、通信设备
WO2020198988A1 (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: 18938371

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021523625

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217014876

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018938371

Country of ref document: EP

Effective date: 20210504

ENP Entry into the national phase

Ref document number: 2018448175

Country of ref document: AU

Date of ref document: 20181031

Kind code of ref document: A