WO2019129139A1 - 一种在用户设备上运行的方法及用户设备 - Google Patents

一种在用户设备上运行的方法及用户设备 Download PDF

Info

Publication number
WO2019129139A1
WO2019129139A1 PCT/CN2018/124321 CN2018124321W WO2019129139A1 WO 2019129139 A1 WO2019129139 A1 WO 2019129139A1 CN 2018124321 W CN2018124321 W CN 2018124321W WO 2019129139 A1 WO2019129139 A1 WO 2019129139A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
beam transmission
access procedure
upper layer
counter
Prior art date
Application number
PCT/CN2018/124321
Other languages
English (en)
French (fr)
Inventor
张崇铭
山田升平
Original Assignee
夏普株式会社
张崇铭
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 张崇铭 filed Critical 夏普株式会社
Priority to US16/957,418 priority Critical patent/US20200367293A1/en
Priority to EP18896528.9A priority patent/EP3735088A4/en
Publication of WO2019129139A1 publication Critical patent/WO2019129139A1/zh

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
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • 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
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • 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

Definitions

  • the present invention relates to the field of wireless communication technologies.
  • the research topic of the new 5G wireless access technology was proposed at the 3rd Generation Partnership Project (3GPP) RAN#64 plenary meeting held in March 2016 (see Non-Patent Document: RP-160671New SID Proposal: Study On New Radio Access Technology).
  • 3GPP 3rd Generation Partnership Project
  • RP-160671New SID Proposal Study On New Radio Access Technology
  • the working frequency band of the new communication system can be extended to 100 GHz, and at the same time, it will meet at least the enhanced mobile broadband service requirements, the communication requirements of massive IoT UEs, and the business requirements of high reliability requirements.
  • the research work of the project will end in 2018.
  • the transmission of data/information is interrupted, and beam failure may occur as a beam failure.
  • the UE will send relevant request information (eg, beam failure recovery request) to the network, request reconfiguration, or restore a valid working beam.
  • relevant request information eg, beam failure recovery request
  • the prior art sets a timer (beamFailureRecoveryTimer, BFR timer) at the MAC layer.
  • the timer is started. If the beam transmission failure recovery request is successfully responded by the network side, the timer is stopped.
  • the MAC layer may indicate a link reset failure or a beam failure recovery request failure to the upper layer; after receiving the indication, the upper layer may determine that a radio link failure has occurred ( Radion link failure (RLF) can then trigger the RRC connection re-establishment process.
  • RLF Radion link failure
  • the UE sends relevant request information to the network side through a random access procedure, and the random access procedure has a preamble transmission COUNTER (hereinafter referred to as COUNTER) for counting the random access procedure.
  • COUNTER a preamble transmission
  • the value of COUNTER is incremented by one until the preset maximum number of transmissions is reached or exceeded.
  • the MAC needs an upper layer to indicate that a Random Access Problem has occurred. After receiving the indication, the upper layer may determine that a Radio Link Failure (RLF) has occurred, and then may trigger an RRC connection re-establishment procedure.
  • RLF Radio Link Failure
  • the BFR timer expires or the COUNTER reaches the maximum number of transmissions, which causes the upper layer to determine the RLF and trigger the RRC connection re-establishment.
  • the UE cannot judge whether the current link has actually failed according to the received indication. For example, when the situation occurs, the beam transmission failure recovery process has not ended yet, but the UE only has a problem in the random access process triggered by the beam transmission failure recovery, and there are various possible reasons for the random access problem. For example, the candidate beam measurement is inaccurate, or the transmitted preamble is in conflict, and the like. As mentioned above, the reason for the beam failure may be due to the rotation of the mobile phone and the occlusion of other objects. Once these obstacles are eliminated, the previously working beam can still work normally, and the UE is likely to be in the BFR after the random access problem occurs. The previous working beam is restored before the timer expires, resulting in misjudgment, resulting in unnecessary connection re-establishment, resource waste, and UE power consumption.
  • Embodiments of the present invention are directed to at least solving the above problems and/or disadvantages and at least the advantages described below.
  • a method for operating on a User Equipment comprising: initiating a preamble transmission counter in a random access procedure
  • the COUNTER counts the number of times the preamble is transmitted during the random access procedure; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, determines whether to indicate random to the upper layer of the UE according to the triggering reason of the random access procedure. Access problem.
  • the determining may include: if the random access procedure is triggered by a condition or condition related to link reconfiguration or beam transmission failure, not indicating a random access problem to an upper layer of the UE; And if the random access procedure is not triggered by a condition or condition associated with link reconfiguration or beam transmission failure, the random access problem is indicated to the upper layer of the UE.
  • a method for operating on a UE comprising: initiating a preamble transmission counter COUNTER in a random access procedure to count transmission of a preamble in a random access procedure The number of times; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, indicates a random access problem to the upper layer of the UE, and also indicates the type of the random access problem to the upper layer of the UE.
  • the random access problem type may include: a type 1 random access problem, indicating that the random access procedure is triggered by a condition or condition related to link reconfiguration or beam transmission failure; And a type 2 random access problem indicating that the random access procedure is not triggered by a condition or condition associated with link reconfiguration or beam transmission failure.
  • the method may further include: when the type 1 random access problem is indicated to the upper layer of the UE, if the beam transmission failure recovery failure is also indicated, determining that the radio link failure occurs .
  • the cause of the radio link failure may be set to a beam transmission failure recovery failure.
  • the method may further include: triggering an RRC connection re-establishment process after determining that a radio link failure occurs.
  • the indicating further may include: sequentially indicating the type 1 random access problem and the beam transmission failure recovery failure simultaneously or at a shorter interval.
  • the determining that the radio link failure occurs may include: starting the first timer after indicating the type 1 random access problem; if the beam is indicated during the first timer running If the transmission failure recovery fails, it is determined that the radio link failure occurs; and if the first timer expires, the indication of the type 1 random access problem is cancelled.
  • the determining that the radio link failure occurs may include: starting a second timer after indicating that the beam transmission failure recovery fails; if the type 1 random access problem is indicated during the second timer operation, Determining that a radio link failure has occurred; and if the second timer expires, canceling the indication that the beam transmission failure recovery failed.
  • the method may further include determining that a radio link failure occurs when the type 2 random access problem is indicated to an upper layer of the UE.
  • the method may further include: releasing the physical random access channel resource used for beam transmission failure recovery based on the indication of the type 1 random access problem.
  • the releasing may include: receiving a specific configuration or parameter indicating that the physical random access channel resource is unavailable for beam transmission failure recovery, or stopping the ongoing random access procedure.
  • a method for operating on a UE comprising: initiating a preamble transmission counter COUNTER in a random access procedure to count transmission of a preamble in a random access procedure The number of times; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, the random access problem or the beam transmission failure is indicated to the upper layer of the UE according to the timer set by the MAC layer or the triggering reason of the random access procedure. Recovery failed.
  • the indicating the random access problem or the beam transmission failure recovery failure to the upper layer of the UE according to the triggering reason of the timer set by the MAC layer or the random access procedure may include: if the random access procedure is If triggered by a condition or condition related to link reconfiguration or beam transmission failure, stop the timer and indicate to the upper layer of the UE that the beam transmission failure recovery fails; and if the random access procedure is not reconfigured with the link or If the condition or condition related to the beam transmission failure is triggered, the random access problem is indicated to the upper layer of the UE.
  • the method may further include determining that a radio link failure occurs after indicating a random access problem or a beam transmission failure recovery failure to an upper layer of the UE.
  • the indicating the random access problem or the beam transmission failure recovery failure to the upper layer of the UE according to the triggering reason of the timer set by the MAC layer or the random access procedure may include: if the timer is If it is running, the timer is stopped and the beam transmission failure recovery failure is indicated; and if the timer is not running, it indicates that a random access problem has occurred.
  • the indicating the random access problem or the beam transmission failure recovery failure to the upper layer of the UE according to the triggering reason of the timer or the random access procedure set by the MAC layer may include: when the timer is over At the same time, the upper layer of the UE indicates that the beam transmission failure recovery failure; and if the random access problem is also indicated after indicating the beam transmission failure recovery failure, it is determined that the radio link failure occurs.
  • the indicating further may include sequentially indicating beam transmission failure recovery failure and random access problem simultaneously or at a shorter interval.
  • the determining that the radio link failure occurs may include: starting a third timer after indicating that the beam transmission failure recovery fails; if the random access problem is indicated during the third timer running, Determining that a radio link failure has occurred; and if the third timer expires, canceling the indication that the beam transmission failure recovery failed.
  • the determining that the radio link failure occurs may include: starting the fourth timer after indicating the random access problem; determining that the wireless chain occurs if the beam transmission failure recovery failure is indicated during the fourth timer operation The path fails and the cause of the radio link failure is set to the beam transmission failure recovery failure; and if the fourth timer expires, it is determined that the radio link failure occurs and the cause of the radio link failure is set to the random access problem.
  • the method may further include: releasing the physical random access channel resource for beam transmission failure recovery after indicating that the beam transmission failure recovery failure.
  • a UE comprising a processor configured to: initiate a preamble transmission counter COUNTER in a random access procedure to count in a random access procedure The number of times the preamble is transmitted; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, it is determined whether to indicate a random access problem to the upper layer of the UE according to the triggering reason of the random access procedure.
  • a UE comprising a processor configured to: initiate a preamble transmission counter COUNTER in a random access procedure to count in a random access procedure The number of times the preamble is transmitted; and when the value of the counter COUNTER reaches or exceeds a preset maximum number of transmissions, indicates a random access problem to the upper layer of the UE, and also indicates the type of the random access problem to the upper layer of the UE.
  • a UE comprising a processor configured to: initiate a preamble transmission counter COUNTER in a random access procedure to count in a random access procedure The number of times the preamble is sent; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, the random access problem is indicated to the upper layer of the UE according to the timer set by the MAC layer or the triggering reason of the random access procedure. Or beam transmission failure recovery failed.
  • FIG. 1 shows a flow chart of a method of operating on a UE in accordance with an embodiment of the present invention
  • FIG. 2 shows another flow diagram of a method of operating on a UE in accordance with an embodiment of the present invention
  • FIG. 3 illustrates another flow diagram of a method of operating on a UE in accordance with an embodiment of the present invention
  • FIG. 4 shows a block diagram of a UE in accordance with an embodiment of the present invention.
  • the present invention is not limited to the following embodiments, but can be applied to more other wireless communication systems, such as an eLTE communication system, and can be applied to other base stations and UE devices, such as base stations and UEs supporting eLTE. device.
  • the present invention is not limited to the scenario of radio link interruption due to beam/beamforming, and can also be used in wireless link interruption scenarios due to other reasons.
  • the UE will send relevant request information (eg, beam failure recovery request) to the network, request reconfiguration, or restore a valid working beam.
  • relevant request information eg, beam failure recovery request
  • the prior art sets a timer (referred to herein as beamFailureRecoveryTimer, BFR timer) at the MAC layer.
  • the MAC layer receives the indication from the lower layer.
  • the indication of the lower layer may be a beam transmission failure or a link failure, or a link reconfiguration request, or a beam transmission. Failed recovery request.
  • the UE may initiate this timer; or the MAC layer may determine that a beam transmission recovery request or a link reconfiguration request is required to be transmitted, this timer may also be initiated.
  • the timer is stopped; if the UE has not received the network side before the timer expires
  • the MAC layer indicates to the upper layer that a link reconfiguration request failure or beam failure recovery request failure has occurred, or indicates a link reconfiguration request or beam to the upper layer.
  • the transmission failure recovery request fails, and the upper layer indicates that the link reconfiguration process or the beam transmission failure recovery has failed, because the link reconfiguration or the beam transmission failure recovery request is not responded, and a failure occurs, meaning that The link reconfiguration process or the beam transmission failure recovery process has failed.
  • an indication of the upper layer is collectively referred to as an upper layer indicating a request failure (request failure); after receiving the indication, the upper layer can determine that a radio link failure (RLF) has occurred, and then Trigger the RRC connection re-establishment process.
  • RLF radio link failure
  • the UE sends a link reconfiguration request or a beam transmission failure recovery request request to the network side through a random access procedure. It can be based on non-competitive RA or RA based on contention resolution.
  • COUNTER preamble transmission COUNTER
  • the specific process can include:
  • Step 1 Start COUNTER: When the random access procedure is initialized/triggered, set the value of COUNTER to one;
  • Step 2 Count the number of times the preamble is transmitted during the random access procedure: when the UE does not receive a response to the UE within a time window, and when the contention conflict resolution is not successful (for example, when the contention conflict resolution timer expires) , the value of COUNTER is increased by one;
  • Step 3 Determine whether the value of COUNTER is equal to the maximum number of times sent plus one
  • the UE may continue to send the preamble, and may continue to perform step two;
  • the MAC will indicate to the upper layer of the UE that a Random Access Problem has occurred or that a problem has occurred to the upper layer of the UE.
  • the problem is A random access problem, here and below, is collectively referred to as indicating a random access problem.
  • the upper layer may determine that a radio link failure has occurred, and then may trigger an RRC connection re-establishment procedure.
  • COUNTER it is judged whether the value of COUNTER is equal to the maximum number of transmissions plus one, which is equivalent to determining whether the value of COUNTER exceeds (greater than) the predetermined maximum number of transmissions. If the initial value of COUNTER is zero, then the determination here may be to determine whether the value of COUNTER is equal to the predetermined maximum number of transmissions.
  • Embodiment 1 will be described below with reference to FIG. 1.
  • the UE determines whether it is necessary to indicate to the upper layer that a random access problem has occurred according to the triggering reason of the RA.
  • it can be
  • the UE determines whether it is necessary to indicate to the upper layer that a random access problem has occurred according to the triggering reason of the RA.
  • the UE determines whether it is necessary to indicate to the upper layer that a random access problem has occurred according to the triggering reason of the RA.
  • the UE may be the MAC layer of the UE, considered Or determine that the random access procedure fails, or consider or determine that the random access procedure has not been successfully completed. In other words, the UE will not report or indicate a random access problem to the upper layer.
  • the upper layer here may be the RRC layer of the UE.
  • the UE may be the MAC layer of the UE, reporting or indicating a random access problem to the upper layer.
  • the upper layer here may be the RRC layer of the UE.
  • Case 1 The random access procedure is triggered by the indication from the lower layer.
  • the indication of the lower layer may be a beam transmission failure or a link failure, or a link reconfiguration request, or a beam transmission failure recovery request;
  • Case 2 The random access procedure is triggered by a beam transmission failure recovery request or a link reconfiguration request.
  • the random access procedure is not triggered by the indication from the lower layer.
  • the indication of the lower layer may be a beam transmission failure or a link failure, or a link reconfiguration request, or a beam transmission failure recovery request;
  • Case 3 The random access procedure is triggered by a PDCCH order (PDCCH order);
  • the random access procedure is triggered by the RRC layer, and may be, for example, a system information request.
  • Embodiment 2 and Embodiment 3 will be described below with reference to FIG.
  • the difference from the first embodiment is that when the UE reports a random access problem to the upper layer, it also indicates that the random access procedure is triggered by a condition or condition related to link reconfiguration or beam transmission failure.
  • a specific implementation may be:
  • the UE may be the MAC layer of the UE, report to the upper layer or indicate random Access problems, and indicate that this random access procedure or random access procedure problem is triggered by conditions or conditions related to link reconfiguration or beam transmission failure.
  • the upper layer here may be the RRC layer of the UE.
  • a further implementation manner of the solution is that the UE indicates the type 1 random access problem to the upper layer, and the type 1 random access problem refers to the random access procedure or the random access procedure problem being reconfigured with the link. Either the condition or condition triggered by the beam transmission failure.
  • the UE may be the MAC layer of the UE, reporting or indicating a random access problem to the upper layer.
  • the upper layer here may be the RRC layer of the UE.
  • the UE indicates the type 2 random access problem to the upper layer.
  • type 2 random access problem refers to the random access procedure or the random access procedure problem is not reconfigured with the link. Either the condition or condition triggered by the beam transmission failure is triggered by other reasons, such as PDCCH order or RRC layer.
  • the upper layer of the UE which may be the RRC layer, may adopt different behaviors, which may be:
  • the UE When receiving the indication of the type 1 random access problem, the UE determines that the radio link fails due to the indication, and optionally, the UE may set the RLF failure reason for the beam transmission failure recovery failure or the link reconfiguration failure. And, optionally, the UE may trigger an RRC connection re-establishment procedure.
  • the UE When receiving the indication of the type 1 random access problem, if the UE also receives the indication that the request failed, the UE determines that the radio link has failed, and optionally, the UE may set the RLF to fail because the beam transmission fails. Recovery failure or link reconfiguration failure, and optionally, the UE may trigger an RRC connection re-establishment procedure.
  • the specific one may be:
  • the UE receives the indication of the type 1 random access problem and the indication that the request fails, or the UE receives the indication of the type 1 random access problem and receives the indication that the request fails.
  • the UE first receives an indication of the type 1 random access problem, and then receives an indication that the request failed.
  • the UE starts a timer, or a time window.
  • the UE determines that the radio link has failed, and optionally, the UE may set the reason for the RLF failure to be a beam.
  • the transmission failure recovery fails or the link reconfiguration fails, and optionally, the UE may trigger an RRC connection re-establishment procedure, and optionally stop the timer or time window;
  • the UE discards the indication of the type 1 random access problem received before, or cancels the previously received type 1 random access. Indication of the problem.
  • the UE first receives an indication that the request has failed, and then receives an indication of the type 1 random access problem.
  • the UE starts a timer, or a time window:
  • the UE determines that the radio link has failed, and optionally, the UE The reason why the RLF failure may be set is that the beam transmission failure recovery failure or the link reconfiguration failure, and optionally, the UE may trigger the RRC connection re-establishment process, and optionally stop the timer or the time window;
  • the UE discards the indication that the previously received request failed, or cancels the previously received or generated request. Instructions.
  • the UE may determine that the radio link fails, and optionally, the UE may set the RLF failure reason to be a random access problem. Further, the UE may trigger the RRC. The connection re-establishment process.
  • the UE in particular the upper layer of the UE, for example, the RRC layer, may indicate the lower layer of the UE, such as the MAC layer or the physical layer, when the indication of the type 1 random access problem is received, or after clearing or Release or deactivate PRACH resources for beam transmission failure recovery or link reconfiguration. Thereby avoiding the UE repeatedly transmitting the preamble.
  • the UE in particular the upper layer of the UE, for example, the RRC layer
  • the UE may indicate the lower layer of the UE, such as the MAC layer or the physical layer, when the indication of the type 1 random access problem is received, or after clearing or Release or deactivate PRACH resources for beam transmission failure recovery or link reconfiguration.
  • a further implementation of this solution may be that the UE, in particular the upper layer of the UE, for example the RRC layer, arrives at the lower layer of the UE, such as the MAC layer or the physical layer, upon receiving an indication of the type 1 random access problem. Indicates a specific configuration or parameter; when the lower layer of the UE, such as the MAC layer or the physical layer, receives the configuration or parameters, it considers that the PRACH resource used for beam transmission failure recovery or link reconfiguration is unavailable or does not exist. Or deactivate it.
  • a further implementation of this solution may be that the UE, in particular the upper layer of the UE, for example the RRC layer, arrives at the lower layer of the UE, such as the MAC layer or the physical layer, upon receiving an indication of the type 1 random access problem. , stop the ongoing random access process, or reset the MAC layer.
  • Embodiments 4 to 6 will be described below with reference to FIG. 3.
  • the UE determines whether the upper layer indicates the random access problem or the beam transmission failure recovery failure or the link reconfiguration failure according to whether the BFR timer is running or the triggering reason of the RA.
  • the specific implementation can be:
  • the UE may be the MAC layer of the UE, and thinks that the BFR timer expires; preferably, if If the BFR timer is running, the UE stops the BFR timer and goes to the upper layer.
  • the upper layer may be the RRC layer of the UE, indicating that the request fails.
  • This process can also be expressed as: when the value of COUNTER exceeds or reaches the maximum number of transmissions, if the random access procedure is triggered by a condition or condition related to link reconfiguration or beam transmission failure, then UE, preferred It may be the MAC layer of the UE, stop the BFR timer, and go to the upper layer.
  • the upper layer may be the RRC layer of the UE, indicating that the request fails.
  • the UE When the UE, in particular the RRC layer of the UE, receives the indication or after, it can determine that the radio link fails, and optionally, the UE can set the RLF failure reason for the beam transmission failure recovery failure or link reconfiguration. Failure, and optionally, the UE may trigger an RRC connection re-establishment procedure.
  • the UE may be the MAC layer of the UE, up to the top, optionally, the upper layer may be the UE
  • the RRC layer indicates a random access problem.
  • the UE When the RRC layer of the UE, in particular the UE, receives the random access problem indication or after, it may determine that the radio link fails, and optionally, the UE may set the RLF failure reason for the random access problem, and Alternatively, the UE may trigger an RRC connection re-establishment procedure.
  • the UE stops the bfr timer and goes to the upper layer.
  • the upper layer may be the RRC layer of the UE, indicating that the request fails.
  • the UE When the UE, in particular the RRC layer of the UE, receives the indication that the request failed, or after, it may determine that the radio link fails, and optionally, the UE may set the RLF failure reason for the beam transmission failure recovery failure or chain.
  • the path reconfiguration fails, and optionally, the UE can trigger the RRC connection re-establishment process.
  • the UE is up to the upper layer.
  • the upper layer may be the RRC layer of the UE, indicating that a random access problem has occurred.
  • the UE When the RRC layer of the UE, in particular the UE, receives the random access problem indication or after, it may determine that the radio link fails, and optionally, the UE may set the RLF failure reason for the random access problem, and Alternatively, the UE may trigger an RRC connection re-establishment procedure.
  • the UE in particular the MAC layer of the UE, to the upper layer of the UE, preferably, may be the RRC layer, indicating that the request fails; the UE, in particular the upper layer of the UE, for example, the RRC layer, receives
  • the request fails, if the random access problem indication is received, the UE determines that the radio link fails, and optionally, the UE may set the RLF failure reason for the beam transmission failure recovery failure or link reconfiguration. Failure, and optionally, the UE may trigger an RRC connection re-establishment procedure.
  • the specific one may be:
  • the UE in particular the RRC layer of the UE, receives the indication of the failure of the request and the indication of the random access problem at the same time; or the UE receives both the indication that the request failed and the random access problem indication in a short interval. ;
  • the UE in particular the RRC layer of the UE, first receives an indication that the request has failed, and then receives an indication of the random access problem; preferably, the UE starts a timer, or a time window, when receiving the indication that the request failed. :
  • the UE determines that the radio link has failed, and optionally, the reason why the UE may set the RLF failure is Beam transmission failure recovery failure or link reconfiguration failure, and optionally, the UE may trigger an RRC connection re-establishment procedure, and optionally stop this timer or time window;
  • the UE discards the indication that the previously received request failed, or cancels the indication that the previous request failed.
  • the UE in particular the RRC layer of the UE, first receives an indication of the random access problem, and then receives an indication that the request has failed; preferably, the UE starts a timer when receiving the indication of the random access problem, or Time Window:
  • the UE determines that the radio link has failed, and optionally, the UE may set the reason for the RLF failure to be a beam.
  • the transmission failure recovery fails or the link reconfiguration fails, and optionally, the UE may trigger an RRC connection re-establishment procedure, and optionally stop the timer or time window;
  • the UE may determine that the radio link has failed, and optionally, the UE may set the cause of the RLF failure as a random access problem, and optionally, The UE may trigger an RRC connection re-establishment procedure.
  • the UE in particular the upper layer of the UE, for example, the RRC layer, may indicate the lower layer of the UE, such as the MAC layer or the physical layer, when the indication of the request failure occurs, or after clearing or Release or deactivate PRACH resources for beam transmission failure recovery or link reconfiguration. Thereby avoiding the UE repeatedly transmitting the preamble.
  • the UE in particular the upper layer of the UE, for example, the RRC layer
  • the UE may indicate the lower layer of the UE, such as the MAC layer or the physical layer, when the indication of the request failure occurs, or after clearing or Release or deactivate PRACH resources for beam transmission failure recovery or link reconfiguration.
  • a further implementation manner of this solution may be that the UE, in particular the upper layer of the UE, for example, the RRC layer, indicates the specific to the lower layer of the UE, such as the MAC layer or the physical layer, when the indication of the request failure occurs is received or after.
  • Configuration or parameter when the lower layer of the UE, for example, the MAC layer or the physical layer, receives the configuration or parameters, it is considered that the PRACH resource used for beam transmission failure recovery or link reconfiguration is unavailable, or does not exist, or is deactivated.
  • a further implementation manner of this solution may be that the UE, in particular the upper layer of the UE, for example, the RRC layer, stops receiving the downlink to the lower layer of the UE, such as the MAC layer or the physical layer, when the indication of the request failure occurs is received.
  • the random access process or reset the MAC layer.
  • Embodiment 7 will be described below with reference to FIG.
  • the UE 100 may include a memory 110 and a processor 120.
  • the memory 110 may store instructions or code for performing the operations described in any of the first to sixth embodiments.
  • Processor 120 can be configured to execute instructions or code stored in memory 110.
  • a UE comprising a processor (eg, 120) configured to: initiate a preamble transmission counter COUNTER in a random access procedure to count in a random connection And the number of times the preamble is sent in the process of entering; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, determining whether to indicate the random access problem to the upper layer of the UE according to the triggering reason of the random access procedure.
  • a processor eg, 120
  • initiate a preamble transmission counter COUNTER in a random access procedure to count in a random connection And the number of times the preamble is sent in the process of entering; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, determining whether to indicate the random access problem to the upper layer of the UE according to the triggering reason of the random access procedure.
  • the processor may be configured to not indicate a random connection to an upper layer of the UE if the random access procedure is triggered by a condition or condition related to link reconfiguration or beam transmission failure. The problem is entered; and if the random access procedure is not triggered by a condition or condition associated with link reconfiguration or beam transmission failure, the random access problem is indicated to the upper layer of the UE.
  • a UE comprising a processor (eg, 120) configured to: initiate a preamble transmission counter COUNTER in a random access procedure to count in a random connection The number of times the preamble is transmitted during the ingress; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, the random access problem is indicated to the upper layer of the UE, and the random access problem is also indicated to the upper layer of the UE.
  • a processor eg, 120
  • initiate a preamble transmission counter COUNTER in a random access procedure to count in a random connection The number of times the preamble is transmitted during the ingress.
  • the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions
  • the random access problem type may include: a type 1 random access problem, indicating that the random access procedure is triggered by a condition or condition related to link reconfiguration or beam transmission failure; And a type 2 random access problem indicating that the random access procedure is not triggered by a condition or condition associated with link reconfiguration or beam transmission failure.
  • the processor may be further configured to: when the type 1 random access problem is indicated to the upper layer of the UE, if the beam transmission failure recovery failure is also indicated, determining that the wireless occurs The link failed.
  • the cause of the radio link failure may be set to a beam transmission failure recovery failure.
  • the processor may be further configured to trigger an RRC connection re-establishment procedure after determining that a radio link failure has occurred.
  • the processor may be configured to sequentially indicate the type 1 random access problem and the beam transmission failure recovery failure simultaneously or at shorter intervals.
  • the processor may be configured to: after indicating the type 1 random access problem, start a first timer; if the beam transmission fails during the first timer operation If the recovery fails, it is determined that the radio link failure occurs; and if the first timer expires, the indication of the type 1 random access problem is cancelled.
  • the processor may be configured to: after indicating a beam transmission failure recovery failure, start a second timer; if the type 1 random access problem is indicated during the second timer operation, determine A radio link failure occurs; and if the second timer expires, the indication that the beam transmission failure recovery failed is cancelled.
  • the processor may be further configured to determine that a radio link failure occurs when the type 2 random access problem is indicated to an upper layer of the UE.
  • the processor may be further configured to: release the physical random access channel resource for beam transmission failure recovery based on the indication of the type 1 random access problem.
  • the processor may be configured to receive a specific configuration or parameter indicating that the physical random access channel resource is unavailable for beam transmission failure recovery, or to stop the ongoing random access procedure.
  • a UE comprising a processor (eg, 120) configured to: initiate a preamble transmission counter COUNTER in a random access procedure to count in a random connection The number of times the preamble is sent during the process; and when the value of the counter COUNTER reaches or exceeds the preset maximum number of transmissions, the upper layer of the UE is randomly indicated according to the timer set by the MAC layer or the triggering reason of the random access procedure. The access problem or beam transmission failure recovery failed.
  • a processor eg, 120
  • the processor may be configured to stop the timer and to the UE if the random access procedure is triggered by a condition or condition associated with link reconfiguration or beam transmission failure
  • the upper layer indicates beam transmission failure recovery failure; and if the random access procedure is not triggered by a condition or condition related to link reconfiguration or beam transmission failure, the random access problem is indicated to the upper layer of the UE.
  • the processor may be further configured to determine that a radio link failure occurs after indicating a random access problem or a beam transmission failure recovery failure to an upper layer of the UE.
  • the processor may be configured to: if the timer is running, stop the timer and indicate that a beam transmission failure recovery failure has occurred; and if the timer is not running, Then indicates that a random access problem has occurred.
  • the processor may be configured to: when the timer expires, indicate to the upper layer of the UE that the beam transmission failure recovery fails; and if the beam transmission failure recovery failure is indicated, further indicate With the random access problem, it is determined that a radio link failure has occurred.
  • the processor may be configured to sequentially indicate beam transmission failure recovery failures and random access problems simultaneously or at shorter intervals.
  • the processor may be configured to: after indicating a beam transmission failure recovery failure, start a third timer; if a random access problem is indicated during the third timer operation, determine A radio link failure occurs; and if the third timer expires, the indication that the beam transmission failure recovery failed is cancelled.
  • the processor may be configured to: initiate a fourth timer after indicating a random access problem; determine that a radio link failure occurs if a beam transmission failure recovery failure is indicated during the fourth timer operation And setting the cause of the radio link failure to beam transmission failure recovery failure; and if the fourth timer expires, determining that the radio link failure occurs and setting the cause of the radio link failure as a random access problem.
  • the processor may be further configured to release the physical random access channel resource for beam transmission failure recovery after indicating that the beam transmission failure recovery failure.
  • the program running on the device according to the present invention may be a program that causes a computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or information processed by the program can be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
  • a program for realizing the functions of the embodiments of the present invention can be recorded on a computer readable recording medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present invention may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that have replaced existing integrated circuits due to advances in semiconductor technology.
  • UE devices Fixed or non-mobile electronic devices installed indoors or outdoors can be used as UE devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

Landscapes

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

Abstract

本发明实施例提供了一种在用户设备UE上运行的方法，所述方法包括：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据随机接入过程的触发原因确定是否向UE的上层指示随机接入问题。

Description

一种在用户设备上运行的方法及用户设备 技术领域
本发明涉及无线通信技术领域。
背景技术
随着移动通信的快速增长和技术的巨大进步，世界将走向一个完全互联互通的网络社会，即任何人或任何东西在任何时间和任何地方都可以获得信息和共享数据。预计到2020年，互联设备的数量将达到500亿部，其中仅有100亿部左右可能是手机和平板电脑，其它的则不是与人对话的机器，而是彼此对话的机器。因此，如何设计系统以更好地支持万物互联是一项需要深入研究的课题。
为此，在2016年3月举行的第三代合作伙伴计划(3GPP)RAN#64次全会上，提出了新5G无线接入技术的研究课题(参见非专利文献：RP-160671New SID Proposal：Study on New Radio Access Technology)。在该工作项目的描述中，未来新的通信制式的工作频段可扩展至100GHz，同时将至少满足增强的移动宽带业务需求、海量物联网UE的通信需求，以及高可靠性要求的业务需求等，该项目研究工作将于2018年结束。
在该课题的研究中，计划使用波束(beam)/波束赋形(beam forming)来进行信息的传输，具体包括在使用高频进行通信的时候，为了应对高频信道衰落过快的特性，采用发射比较细的波束。但是，利用较细的波束来进行信息传输容易受到外界变化的影响，比如手机的旋转，其他物体的遮挡等等。
在采用波束赋形的传输场景下，一旦为UE数据/信息传输服务的有效波束信号变弱或者低于预配置的阈值，数据/信息的传输被中断，可以认为发生了波束传输失败(beam failure)。UE将向网络发送相关的请求信息(例如，波束传输失败恢复请求，beam failure recovery request)，请求重新配置，或者恢复有效的工作波束。为了管理和控制波束传输失败恢复(beam failure recovery)这个过程，现有技术在MAC层设定了一个定时器 (beamFailureRecoveryTimer，BFR timer)。当UE发生波束传输失败的时候，启动这个定时器，如果波束传输失败恢复请求被网络侧成功响应，那么停止运行这个定时器；如果在这个定时器超时之前，UE还没有收到网络侧的响应，那么当定时器超时之后，MAC层会向上层指示链路重置失败或者波束传输失败恢复请求失败(beam failure recovery request failure)；上层收到该指示后，可以判定发生了无线链路失败(Radion link failure，RLF)，然后可以触发RRC连接重建立过程。
值得注意的是，UE通过随机接入过程来向网络侧发送相关的请求信息，而随机接入过程有一个前导码发送计数器(preamble transmission COUNTER，以下简称COUNTER)，用来统计在随机接入过程中前导码(preamble)的发送次数，UE每发送一次前导码，COUNTER的值就加一，直到达到或者超过预设的最大发送次数。当COUNTER的值达到或者超过预设的最大发送次数时，MAC需要向上层(upper layer)指示发生了一个随机接入问题(RandomAccess Problem)。上层收到该指示后，可以判定发生了无线链路失败(Radion link failure，RLF)，然后可以触发RRC连接重建立过程。
由此可见，在链路重配置或者波束传输失败恢复(beam failure recovery)过程中BFR timer超时或者COUNTER达到最大发送次数，都会导致上层判定RLF，并触发RRC连接重建立。
由于COUNTER和BFRtimer是相互独立的，因此存在下述情况：
情况一：当COUNTER达到或者超过最大发送次数时，BFR timer还在运行；
情况二：当BRF timer超时时，COUNTER还未达到或者超过最大发送次数。
在这两种情况下，UE无法根据收到的指示来判断当前链路是否真正发生了失败。例如，当发生情况一时，波束传输失败恢复过程还没有结束，而是UE仅在进行由波束传输失败恢复触发的随机接入过程中发生了问题，而随机接入发生问题的可能原因有多种，例如候选的波束测量不准确，或者发送的前导码发生了冲突等等。如前所述，波束发生失败的原因可能是由于手机的旋转、其他物体的遮挡，一旦这些障碍消除，之前工作的波束 仍然可以正常工作，UE极有可能在发生随机接入问题之后但在BFR timer超时之前恢复之前的工作波束，从而导致发生误判，进而造成不必要的连接重建立，以及资源浪费和UE的功耗。
又例如，当发生情况二时，BFR timer已经超时，但是随机接入过程还在进行，并且极有可能成功。那么在这种时候判定RLF也可能是误判，从而导致了不必要的连接重建立，进而导致不必要的资源浪费以及UE的功耗。
可见，如何对在上述情况下UE收到的指示进行区分，以及采取相应的措施是需要解决的问题。
发明内容
本发明的各实施例是为了至少解决上述问题和/或缺点，并且至少提供以下描述的优点。
根据本发明的一个实施例，提供了一种在用户设备(UE)上运行的方法，所述方法可以包括：启动随机接入过程中的前导码发送计数器
COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据随机接入过程的触发原因确定是否向UE的上层指示随机接入问题。
在本发明的实施例中，所述确定可以包括：如果随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的，则不向UE的上层指示随机接入问题；以及如果随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的，则向UE的上层指示随机接入问题。
根据本发明的另一实施例，提供了一种在UE上运行的方法，所述方法可以包括：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，向UE的上层指示随机接入问题，并且还向UE的上层指示随机接入问题的类型。
在本发明的实施例中，所述随机接入问题类型可以包括：类型一的随机接入问题，指示随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的；以及类型二的随机接入问题，指示随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的。
在本发明的实施例中，所述方法还可以包括：当向UE的上层指示了所述类型一的随机接入问题时，如果还指示了波束传输失败恢复失败，则确定发生无线链路失败。可选地，无线链路失败的原因可以被设置为波束传输失败恢复失败。
在本发明的实施例中，所述方法还可以包括：在确定发生无线链路失败后，触发RRC连接重建立过程。
在本发明的实施例中，所述还指示可以包括：同时地或以较短间隔相继地指示所述类型一的随机接入问题和波束传输失败恢复失败。
在本发明的实施例中，所述确定发生无线链路失败可以包括：在指示了所述类型一的随机接入问题后，启动第一定时器；如果在第一定时器运行期间指示了波束传输失败恢复失败，则确定发生无线链路失败；以及如果第一定时器超时，则取消对所述类型一的随机接入问题的指示。
替代地，所述确定发生无线链路失败可以包括：在指示了波束传输失败恢复失败后，启动第二定时器；如果在第二定时器运行期间指示了所述类型一的随机接入问题，则确定发生无线链路失败；以及如果第二定时器超时，则取消对波束传输失败恢复失败的指示。
在本发明的实施例中，所述方法还可以包括：当向UE的上层指示了所述类型二的随机接入问题时，确定发生无线链路失败。
在本发明的实施例中，所述方法还可以包括：基于所述类型一的随机接入问题的指示，释放用于波束传输失败恢复的物理随机接入信道资源。可选地，所述释放可以包括：接收对用于波束传输失败恢复的物理随机接入信道资源不可用加以指示的特定配置或参数，或者停止正在进行的随机接入过程。
根据本发明的另一实施例，提供了一种在UE上运行的方法，所述方法可以包括：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败。
在本发明的实施例中，所述根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败可以 包括：如果随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的，则停止所述定时器并向UE的上层指示波束传输失败恢复失败；以及如果随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的，则向UE的上层指示随机接入问题。
在本发明的实施例中，所述方法还可以包括：在向UE的上层指示随机接入问题或波束传输失败恢复失败后，确定发生无线链路失败。
在本发明的实施例中，所述根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败可以包括：如果所述定时器正在运行，则停止所述定时器并指示发生了波束传输失败恢复失败；以及如果所述定时器没有运行，则指示发生了随机接入问题。
在本发明的实施例中，所述根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败可以包括：当所述定时器超时时，向UE的上层指示波束传输失败恢复失败；以及如果在指示了波束传输失败恢复失败后，还指示了随机接入问题，则确定发生无线链路失败。
在本发明的实施例中，所述还指示可以包括：同时地或以较短间隔相继地指示波束传输失败恢复失败和随机接入问题。
在本发明的实施例中，所述确定发生无线链路失败可以包括：在指示了波束传输失败恢复失败后，启动第三定时器；如果在第三定时器运行期间指示了随机接入问题，则确定发生无线链路失败；以及如果第三定时器超时，则取消对波束传输失败恢复失败的指示。
替代地，所述确定发生无线链路失败可以包括：在指示了随机接入问题后，启动第四定时器；如果在第四定时器运行期间指示了波束传输失败恢复失败，则确定发生无线链路失败并将无线链路失败的原因设置为波束传输失败恢复失败；以及如果第四定时器超时，则确定发生无线链路失败并将无线链路失败的原因设置为随机接入问题。
在本发明的实施例中，所述方法还可以包括：在指示波束传输失败恢复失败后，释放用于波束传输失败恢复的物理随机接入信道资源。
根据本发明的另一实施例，提供了一种UE，所述UE包括处理器，所述处理器被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据随机接入过程的触发原因确定是否向UE的上层指示随机接入问题。
根据本发明的另一实施例，提供了一种UE，所述UE包括处理器，所述处理器被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，向UE的上层指示随机接入问题，并且还向UE的上层指示随机接入问题的类型。
根据本发明的另一实施例，提供了一种UE，所述UE包括处理器，所述处理器被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败。
根据结合附图公开了本发明各种实施例的以下详细描述，本发明的其他方面、优点和突出特征对于本领域技术人员将变得清楚明白。
附图说明
根据结合附图的以下描述，本发明的某些实施例的上述和其他方面、特征和优点将更清楚，在附图中：
图1示出了根据本发明实施例的在UE上运行的方法的流程图；
图2示出了根据本发明实施例的在UE上运行的方法的另一流程图；
图3示出了根据本发明实施例的在UE上运行的方法的另一流程图；以及
图4示出了根据本发明实施例的UE的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本 发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
在具体描述之前，先对本发明中提到的若干术语做如下说明。除非另有指出，本发明中涉及的术语都具有下文的含义。
UE        User Equipment  用户设备
RLF       Radio Link Failure  无线链路失败
NR        New Radio  新一代无线技术
LTE       Long Term Evolution  长期演进技术
eLTE      Enhaced Long Term Evolution  增强的长期演进技术
RRC       Radio Resource Control  无线资源控制(层)
MAC       Medium Access Control  媒体接入控制(层)
PHY       physical layer  物理层
PDCCH     Physical Downlink Control Channel  物理下行控制信道
RA        Random Access  随机接入
PRACH     Physical Random Access Channel  物理随机接入信道
下文以NR移动通信系统及其后续的演进版本作为示例应用环境，以支持NR的基站和UE设备为例，具体描述了根据本发明的多个实施方式。然而，需要指出的是，本发明不限于以下实施方式，而是可适用于更多其它的无线通信系统，例如eLTE通信系统，而且可以适用于其他基站和UE设备，例如支持eLTE的基站和UE设备。同时本发明不限于由于波束/波束赋形导致的无线链路中断的场景，还可以用于由于其他原因导致的无线链路中断场景下。
在采用波束赋形的传输场景下，一旦为UE数据/信息传输服务的有效波束信号变弱或者低于预配置的阈值，数据/信息的传输被中断，可以认为发生了波束传输失败(beam failure)。UE将向网络发送相关的请求信息(例如，波束传输失败恢复请求，beam failure recovery request)，请求重新配置，或者恢复有效的工作波束。为了管理和控制波束传输失败恢复(beam failure recovery)这个过程，现有技术在MAC层设定了一个定时器(这里称为beamFailureRecoveryTimer，BFR timer)。
当UE发生波束传输失败的时候，例如，MAC层收到来自下层的指示，进一步的，下层的指示可以是波束传输失败或者链路失败，又或者是链路重配置请求，又或者是波束传输失败恢复请求。一旦收到此类指示，UE会启动这个定时器；又或者MAC层判定需要发送波束传输失败恢复请求beam failure recovery request或者链路重配置请求时，也可以启动这个定时器。
如果在定时器运行期间，UE发送的链路重配置请求或者波束传输失败恢复请求被网络侧成功响应，那么停止运行这个定时器；如果在这个定时器超时之前，UE还没有收到网络侧的响应，那么当定时器超时之后，MAC层会向上层指示发生了链路重配置请求失败或者波束传输失败恢复请求失败(beam failure recovery request failure)，或者是向上层指示链路重配置请求或者波束传输失败恢复请求发生了失败，还可以是向上层指示链路重配置过程或者波束传输失败恢复发生了失败，因为链路重配置或者波束传输失败恢复的请求没有被响应，发生了失败，意味着链路重配置过程或者波束传输失败恢复过程发生了失败。这里以及下文将这类向上层的指示统一称之为向上层指示请求发生失败(request failure)；上层收到该指示后，可以判定发生了无线链路失败(Radion link failure，RLF)，然后可以触发RRC连接重建立过程。
UE是通过随机接入过程来向网络侧发送链路重配置请求或者波束传输失败恢复请求请求的。可以基于非竞争的RA或者是基于竞争冲突解决的RA。在进行随机接入的过程中，有一个前导码发送计数器(preamble transmission COUNTER，以下简称COUNTER)，用来统计在随机接入过程中前导码的发送次数，在随机接入过程中与COUNTER相关的具体过程可以包括：
步骤一：启动COUNTER：当随机接入过程被初始化/触发时，设置COUNTER的值为一；
步骤二：统计在随机接入过程中前导码的发送次数：当UE在一个时间窗内没有收到给UE的响应时，以及当竞争冲突解决没有成功时(例如竞争冲突解决定时器超时时)，COUNTER的值加一；
步骤三：判断COUNTER的值是否等于最大发送次数值加一
-如果COUNTER的值不等于最大发送次数值加一，那么UE可以继续 发送前导码，以及还可以继续执行步骤二；
-如果COUNTER的值等于最大发送次数值加一，那么MAC会向UE的上层(upper layer)指示发生了随机接入问题(Random Access Problem)或者是向UE的上层指示发生了问题，该问题是一个随机接入问题，这里以及下文中统称为指示随机接入问题。上层收到该指示后，可以判定发生了无线链路失败，然后可以触发RRC连接重建立过程。
这里判断COUNTER的值是否等于最大发送次数加一，等价于判断COUNTER的值是否超过(大于)预定的最大发送次数。如果COUNTER的初始值为零，那么这里的判断可以是判断COUNTER的值是否等于预定的最大发送次数。
以下，详细描述本发明的若干实施例。
下面将参考图1对实施例一进行描述。
实施例一
当COUNTER的值超过或者达到最大发送次数时，UE根据RA的触发原因判断是否需要向上层指示发生了随机接入问题。优选的，可以是
-如果COUNTER的初始值为零，当COUNTER的值达到最大发送次数时，UE根据RA的触发原因判断是否需要向上层指示发生了随机接入问题。
-如果COUNTER的初始值为一，当COUNTER的值超过最大发送次数时(或者等于最大发送次数加一时)，UE根据RA的触发原因判断是否需要向上层指示发生了随机接入问题。
具体地：
当COUNTER的值超过或者达到最大发送次数时：
-如果当前的随机接入过程是被与链路重配置或者波束传输失败相关的情况或者条件触发的(triggered)或者引发的(initiated)，则UE，优选的，可以是UE的MAC层，认为或者判断随机接入过程失败，又或者认为或者判断随机接入过程没有成功完成。换句话说，UE将不向上层(upper layer)报告或者指示随机接入问题。这里的上层可以是UE的RRC层。
-如果当前的随机接入过程不是由于前述原因触发的，则UE，优选的，可以是UE的MAC层，向上层(upper layer)报告或者指示随机接入问题。这里的上层可以是UE的RRC层。
其中，前文以及下文所述的“随机接入过程是被与链路重配置或者波束传输失败相关的情况或者条件触发的”，具体可以是下面的一种或者多种情况：
情况一：随机接入过程是被来自下层的指示触发的，进一步的，下层的指示可以是波束传输失败或者链路失败，又或者是链路重配置请求，又或者是波束传输失败恢复请求；
情况二：随机接入过程是由波束传输失败恢复请求或者链路重配置请求触发的。
前文以及下文所述的“随机接入过程不是由于前述原因触发的，”具体可以是下面的一种或者多种情况：
情况一：随机接入过程不是被来自下层的指示触发的，进一步的，下层的指示可以是波束传输失败或者链路失败，又或者是链路重配置请求，又或者是波束传输失败恢复请求；
情况二：随机接入过程不是由波束传输失败恢复请求或者链路重配置请求触发的；
情况三：随机接入过程是由PDCCH命令(PDCCH order)触发的；
情况四：随机接入过程是由RRC层触发的，例如可以是系统信息请求。
下面将参考图2对实施例二和实施例三进行描述。
实施例二
与实施例一的区别在于，当UE向上层报告随机接入问题时，还指出随机接入过程是被与链路重配置或者波束传输失败相关的情况或者条件触发的。
具体的实施方式可以是：
当COUNTER值超过或者达到最大发送次数时：
-如果当前的随机接入过程是被与链路重配置或者波束传输失败相关的情况或者条件触发的，则UE，优选的，可以是UE的MAC层，向上层(upper layer)报告或者指示随机接入问题，并指出这个随机接入过程或者 随机接入过程问题是被与链路重配置或者波束传输失败相关的情况或者条件触发的。这里的上层可以是UE的RRC层。该方案的又一实施方式为，UE向上层指示了类型一的随机接入问题，所谓类型一的随机接入问题，是指随机接入过程或者随机接入过程问题是被与链路重配置或者波束传输失败相关的情况或者条件触发的。
-如果当前的随机接入过程不是由于前述原因触发的，则UE，优选的，可以是UE的MAC层，向上层(upper layer)报告或者指示随机接入问题。这里的上层可以是UE的RRC层。该方案的又一实施方式为，UE向上层指示了类型二的随机接入问题，所谓类型二的随机接入问题，是指随机接入过程或者随机接入过程问题不是被与链路重配置或者波束传输失败相关的情况或者条件触发的，而是由其他原因触发的，例如PDCCH order或者RRC层等。
基于UE向上层指示的随机接入问题，UE的上层，优选的，可以是RRC层，将采用不同的行为，具体可以是：
当收到类型一的随机接入问题的指示时，基于该指示，UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程。
又或者，
当收到类型一的随机接入问题的指示时，如果UE还收到了请求发生失败的指示，则UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程。
其中“当收到类型一的随机接入问题的指示时，如果UE还收到了请求发生失败的指示”具体可以是：
UE同时收到了类型一的随机接入问题的指示以及请求发生失败的指示，或者UE在间隔很短的时间内既收到了类型一的随机接入问题的指示又收到了请求发生失败的指示；
或者
UE首先收到了类型一的随机接入问题的指示，然后收到了请求发生失败的指示，优选的，UE在收到类型一的随机接入问题的指示时，启动了一 个定时器，或者时间窗：
如果在这个定时器还在运行期间，或者还处在时间窗内，UE收到了请求发生失败的指示，那么UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程，以及可选的停止这个定时器或者时间窗；
如果当这个定时器超时了，或者已经超出了这个时间窗，那么UE丢弃(discard)之前收到的类型一的随机接入问题的指示，或者取消(cancel)之前收到的类型一的随机接入问题的指示。
又或者
UE首先收到了请求发生失败的指示，然后收到了类型一的随机接入问题的指示，优选的，UE在收到请求发生失败的指示时，启动了一个定时器，或者时间窗：
如果在这个定时器还在运行期间，或者在时间窗包含的时间段内，UE收到了收到了类型一的随机接入问题的指示，那么UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程，以及可选的停止这个定时器或者时间窗；
如果当这个定时器超时了，或者当前时刻已经超出了这个时间窗，那么UE丢弃(discard)之前收到的请求发生失败的指示，或者取消(cancel)之前收到的或者生成的请求发生失败的指示。
此外，当收到类型二的随机接入问题的指示时，UE可以判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为随机接入问题，进一步的，UE可以触发RRC连接重建立过程。
实施例三
与实施例二的区别在于UE，特别是UE的上层，例如RRC层，收到了类型一的随机接入问题的指示之时或者之后，可以指示UE的下层，例如MAC层或者物理层，清除或者释放或者去激活用于波束传输失败恢复或者链路重配置的PRACH资源。从而避免UE重复发送前导码。
这一方案的又一种实施方式可以是UE，特别是UE的上层，例如RRC层，收到了类型一的随机接入问题的指示之时或者之后，向UE的下层，例如MAC层或者物理层，指示特定的配置或者参数；当UE的下层，例如MAC层或者物理层，收到该配置或者参数后，认为用于波束传输失败恢复或者链路重配置的PRACH资源不可用，或者不存在，或者去激活。
这一方案的又一种实施方式可以是UE，特别是UE的上层，例如RRC层，收到了类型一的随机接入问题的指示之时或者之后，向UE的下层，例如MAC层或者物理层，停止正在进行的随机接入过程，或者重置(reset)MAC层。
下面将参考图3对实施例四至实施例六进行描述。
实施例四
当COUNTER的值超过或者达到最大发送次数时，UE根据BFR timer是否运行或者RA的触发原因来判断向上层指示随机接入问题还是波束传输失败恢复失败或者链路重配置失败。
具体的实现方式可以是：
当COUNTER的值超过或者达到最大发送次数时，
-如果随机接入过程是被与链路重配置或者波束传输失败相关的情况或者条件触发的，那么UE，优选的，可以是UE的MAC层，认为(consider)BFR timer超时；优选的，如果BFR timer正在运行，则UE停止BFR timer，并向上层，可选的，上层可以是UE的RRC层，指示请求发生失败。
这一过程还可以被表述为：当COUNTER的值超过或者达到最大发送次数时，如果随机接入过程是被与链路重配置或者波束传输失败相关的情况或者条件触发的，那么UE，优选的，可以是UE的MAC层，停止BFR timer，并向上层，可选的，上层可以是UE的RRC层，指示请求发生失败。
当UE，特别是UE的RRC层，收到这个指示之时或者之后，可以判定无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程。
-如果随机接入过程不是被与链路重配置或者波束传输失败相关的情况或者条件触发的，那么UE，优选的，可以是UE的MAC层，向上层， 可选的，上层可以是UE的RRC层，指示随机接入问题。
当UE，特别是UE的RRC层，收到随机接入问题指示之时或者之后，可以判定无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为随机接入问题，以及可选的，UE可以触发RRC连接重建立过程。
本实施例的又一种实施方式可以是：
当COUNTER的值超过或者达到最大发送次数时，
-如果BFR timer正在运行，那么UE停止bfr timer，并向上层，可选的，上层可以是UE的RRC层，指示请求发生失败；
当UE，特别是UE的RRC层，收到请求发生失败的指示之时或者之后，可以判定无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程。
-如果BFR timer没有在运行，那么UE向上层，可选的，上层可以是UE的RRC层，指示发生了随机接入问题。
当UE，特别是UE的RRC层，收到随机接入问题指示之时或者之后，可以判定无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为随机接入问题，以及可选的，UE可以触发RRC连接重建立过程。
实施例五
当BFR timer超时时，UE，特别是UE的MAC层，向UE的上层(upper layer)，优选的，可以是RRC层，指示请求发生失败；UE，特别是UE的上层，例如RRC层，收到请求发生失败的指示时，如果还收到随机接入问题指示，那么UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程。
其中，“收到请求发生失败的指示时，如果还收到随机接入问题指示”，具体可以是：
UE，特别是UE的RRC层，同时收到了请求发生失败的指示和随机接入问题指示；或者UE在间隔很短的时间内既收到了请求发生失败的指示，又收到了随机接入问题指示；
或者
UE，特别是UE的RRC层，首先收到了请求发生失败的指示，然后收到了随机接入问题指示；优选的，UE在收到请求发生失败的指示时，启动了一个定时器，或者时间窗：
如果在这个定时器还在运行期间，或者还处在时间窗内，UE收到了随机接入问题的指示，那么UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程，以及可选的停止这个定时器或者时间窗；
如果当这个定时器超时了，或者已经超出了这个时间窗，那么UE丢弃(discard)之前收到的请求发生失败的指示，或者取消(cancel)之前的请求发生失败的指示；
又或者
UE，特别是UE的RRC层，首先收到了随机接入问题的指示，然后收到了请求发生失败的指示；优选的，UE在收到随机接入问题的指示时，启动了一个定时器，或者时间窗：
如果在这个定时器还在运行期间，或者还处在时间窗内，UE收到了请求发生失败的指示，那么UE判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因为波束传输失败恢复失败或者链路重配置失败，以及可选的，UE可以触发RRC连接重建立过程，以及可选的停止这个定时器或者时间窗；
如果当这个定时器超时了，或者已经超出了这个时间窗，那么UE可以判断无线链路发生失败，以及可选的，UE可以设置RLF失败的原因值为随机接入问题，以及可选的，UE可以触发RRC连接重建立过程。
实施例六
与实施例四和实施例五的区别在于UE，特别是UE的上层，例如RRC层，收到了请求发生失败的指示之时或者之后，可以指示UE的下层，例如MAC层或者物理层，清除或者释放或者去激活用于波束传输失败恢复或者链路重配置的PRACH资源。从而避免UE重复发送前导码。
这一方案的又一种实施方式可以是UE，特别是UE的上层，例如RRC 层，收到了请求发生失败的指示之时或者之后，向UE的下层，例如MAC层或者物理层，指示特定的配置或者参数；当UE的下层，例如MAC层或者物理层，收到该配置或者参数后，认为用于波束传输失败恢复或者链路重配置的PRACH资源不可用，或者不存在，或者去激活。
这一方案的又一种实施方式可以是UE，特别是UE的上层，例如RRC层，收到了请求发生失败的指示之时或者之后，向UE的下层，例如MAC层或者物理层，停止正在进行的随机接入过程，或者重置(reset)MAC层。
下面将参考图4对实施例七进行描述。
实施例七
如图4所示，根据本发明实施例的UE 100可以包括存储器110和处理器120。存储器110可以存储用于执行根据实施例一至实施例六中的任何一个所描述的操作的指令或代码。处理器120可以被配置为执行存储在存储器110中的指令或代码。
根据本发明的实施例，提供了一种UE，所述UE包括处理器(例如，120)，所述处理器被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据随机接入过程的触发原因确定是否向UE的上层指示随机接入问题。
在本发明的实施例中，所述处理器可以被配置为：如果随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的，则不向UE的上层指示随机接入问题；以及如果随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的，则向UE的上层指示随机接入问题。
根据本发明的实施例，提供了一种UE，所述UE包括处理器(例如，120)，所述处理器被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，向UE的上层指示随机接入问题，并且还向UE的上层指示随机接入问题的类型。
在本发明的实施例中，所述随机接入问题类型可以包括：类型一的随机接入问题，指示随机接入过程是被与链路重配置或波束传输失败相关的 情况或条件触发的；以及类型二的随机接入问题，指示随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的。
在本发明的实施例中，所述处理器还可以被配置为：当向UE的上层指示了所述类型一的随机接入问题时，如果还指示了波束传输失败恢复失败，则确定发生无线链路失败。可选地，无线链路失败的原因可以被设置为波束传输失败恢复失败。
在本发明的实施例中，所述处理器还可以被配置为：在确定发生无线链路失败后，触发RRC连接重建立过程。
在本发明的实施例中，所述处理器可以被配置为：同时地或以较短间隔相继地指示所述类型一的随机接入问题和波束传输失败恢复失败。
在本发明的实施例中，所述处理器可以被配置为：在指示了所述类型一的随机接入问题后，启动第一定时器；如果在第一定时器运行期间指示了波束传输失败恢复失败，则确定发生无线链路失败；以及如果第一定时器超时，则取消对所述类型一的随机接入问题的指示。
替代地，所述处理器可以被配置为：在指示了波束传输失败恢复失败后，启动第二定时器；如果在第二定时器运行期间指示了所述类型一的随机接入问题，则确定发生无线链路失败；以及如果第二定时器超时，则取消对波束传输失败恢复失败的指示。
在本发明的实施例中，所述处理器还可以被配置为：当向UE的上层指示了所述类型二的随机接入问题时，确定发生无线链路失败。
在本发明的实施例中，所述处理器还可以被配置为：基于所述类型一的随机接入问题的指示，释放用于波束传输失败恢复的物理随机接入信道资源。可选地，所述处理器可以被配置为：接收对用于波束传输失败恢复的物理随机接入信道资源不可用加以指示的特定配置或参数，或者停止正在进行的随机接入过程。
根据本发明的实施例，提供了一种UE，所述UE包括处理器(例如，120)，所述处理器被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波 束传输失败恢复失败。
在本发明的实施例中，所述处理器可以被配置为：如果随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的，则停止所述定时器并向UE的上层指示波束传输失败恢复失败；以及如果随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的，则向UE的上层指示随机接入问题。
在本发明的实施例中，所述处理器还可以被配置为：在向UE的上层指示随机接入问题或波束传输失败恢复失败后，确定发生无线链路失败。
在本发明的实施例中，所述处理器可以被配置为：如果所述定时器正在运行，则停止所述定时器并指示发生了波束传输失败恢复失败；以及如果所述定时器没有运行，则指示发生了随机接入问题。
在本发明的实施例中，所述处理器可以被配置为：当所述定时器超时时，向UE的上层指示波束传输失败恢复失败；以及如果在指示了波束传输失败恢复失败后，还指示了随机接入问题，则确定发生无线链路失败。
在本发明的实施例中，所述处理器可以被配置为：同时地或以较短间隔相继地指示波束传输失败恢复失败和随机接入问题。
在本发明的实施例中，所述处理器可以被配置为：在指示了波束传输失败恢复失败后，启动第三定时器；如果在第三定时器运行期间指示了随机接入问题，则确定发生无线链路失败；以及如果第三定时器超时，则取消对波束传输失败恢复失败的指示。
替代地，所述处理器可以被配置为：在指示了随机接入问题后，启动第四定时器；如果在第四定时器运行期间指示了波束传输失败恢复失败，则确定发生无线链路失败并将无线链路失败的原因设置为波束传输失败恢复失败；以及如果第四定时器超时，则确定发生无线链路失败并将无线链路失败的原因设置为随机接入问题。
在本发明的实施例中，所述处理器还可以被配置为：在指示波束传输失败恢复失败后，释放用于波束传输失败恢复的物理随机接入信道资源。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序 处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作UE设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种在用户设备UE上运行的方法，所述方法包括：
    启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及
    当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据随机接入过程的触发原因确定是否向UE的上层指示随机接入问题。
  2. 根据权利要求1所述的方法，其中，所述确定包括：
    如果随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的，则不向UE的上层指示随机接入问题；以及
    如果随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的，则向UE的上层指示随机接入问题。
  3. 一种在用户设备UE上运行的方法，所述方法包括：
    启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及
    当所述计数器COUNTER的值达到或超过预设的最大发送次数时，向UE的上层指示随机接入问题，并且还向UE的上层指示随机接入问题的类型。
  4. 根据权利要求3所述的方法，其中，所述随机接入问题的类型包括：类型一的随机接入问题，指示随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的；以及类型二的随机接入问题，指示随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的。
  5. 根据权利要求4所述的方法，还包括：基于所述类型一的随机接入问题的指示，释放用于波束传输失败恢复的物理随机接入信道资源。
  6. 一种在用户设备UE上运行的方法，所述方法包括：
    启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及
    当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败。
  7. 根据权利要求6所述的方法，其中，所述根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败包括：
    如果随机接入过程是被与链路重配置或波束传输失败相关的情况或条件触发的，则停止所述定时器并向UE的上层指示波束传输失败恢复失败；以及
    如果随机接入过程不是被与链路重配置或波束传输失败相关的情况或条件触发的，则向UE的上层指示随机接入问题。
  8. 根据权利要求6所述的方法，其中，所述根据MAC层设定的定时器或随机接入过程的触发原因向UE的上层指示随机接入问题或波束传输失败恢复失败包括：
    当所述定时器超时时，向UE的上层指示波束传输失败恢复失败；以及
    如果在指示了波束传输失败恢复失败后，还指示了随机接入问题，则确定发生无线链路失败。
  9. 根据权利要求6所述的方法，还包括：在指示波束传输失败恢复失败后，释放用于波束传输失败恢复的物理随机接入信道资源。
  10. 一种用户设备UE，包括：
    处理器，被配置为：启动随机接入过程中的前导码发送计数器COUNTER以统计在随机接入过程中前导码的发送次数；以及
    当所述计数器COUNTER的值达到或超过预设的最大发送次数时，根据随机接入过程的触发原因确定是否向UE的上层指示随机接入问题。
PCT/CN2018/124321 2017-12-27 2018-12-27 一种在用户设备上运行的方法及用户设备 WO2019129139A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/957,418 US20200367293A1 (en) 2017-12-27 2018-12-27 Method operating on user equipment and user equipment
EP18896528.9A EP3735088A4 (en) 2017-12-27 2018-12-27 OPERATING PROCESS ON A EU AND EU

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711455279.2A CN109982442A (zh) 2017-12-27 2017-12-27 一种在用户设备上运行的方法及用户设备
CN201711455279.2 2017-12-27

Publications (1)

Publication Number Publication Date
WO2019129139A1 true WO2019129139A1 (zh) 2019-07-04

Family

ID=67066622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/124321 WO2019129139A1 (zh) 2017-12-27 2018-12-27 一种在用户设备上运行的方法及用户设备

Country Status (4)

Country Link
US (1) US20200367293A1 (zh)
EP (1) EP3735088A4 (zh)
CN (1) CN109982442A (zh)
WO (1) WO2019129139A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111466128B (zh) * 2018-01-04 2023-08-08 富士通株式会社 波束失败恢复的配置方法、装置及通信系统
JP7026796B2 (ja) 2018-01-04 2022-02-28 サムスン エレクトロニクス カンパニー リミテッド 半永続的なチャネル状態情報レポート
WO2019141898A1 (en) * 2018-01-19 2019-07-25 Nokia Technologies Oy Beam failure recovery
CN110149179B (zh) * 2018-02-12 2021-01-15 维沃移动通信有限公司 一种波束失败恢复的方法和设备
CN110324914B (zh) * 2018-03-28 2021-03-23 维沃移动通信有限公司 波束失败的处理方法和终端
PL3780852T3 (pl) * 2018-03-28 2023-07-24 Beijing Xiaomi Mobile Software Co., Ltd. Sposób przesyłania informacji i urządzenie do przesyłania informacji
CN109076619B (zh) * 2018-07-16 2022-07-22 北京小米移动软件有限公司 随机接入控制方法和随机接入控制装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102067704A (zh) * 2008-06-18 2011-05-18 Lg电子株式会社 用于检测随机接入过程失败的方法
CN102946299A (zh) * 2012-11-23 2013-02-27 大唐移动通信设备有限公司 监测丢帧的方法、装置及基站
US20170079072A1 (en) * 2010-08-06 2017-03-16 Sharp Kabushiki Kaisha Base station apparatus, mobile station apparatus, and communication method
CN107006037A (zh) * 2014-10-03 2017-08-01 瑞典爱立信有限公司 在多载波场景中处理物理随机接入信道传输

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2854319B1 (en) * 2008-03-07 2018-07-25 NEC Corporation Radio communication system, communication apparatus, radio communication network system and method therefor
CN101547519A (zh) * 2008-03-28 2009-09-30 三星电子株式会社 一种无线资源控制连接建立的方法
CN108886808B (zh) * 2016-02-05 2022-11-29 瑞典爱立信有限公司 用于随机接入覆盖增强的方法和设备
CN111149306A (zh) * 2017-08-09 2020-05-12 Idac控股公司 用于波束恢复和管理的方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102067704A (zh) * 2008-06-18 2011-05-18 Lg电子株式会社 用于检测随机接入过程失败的方法
US20170079072A1 (en) * 2010-08-06 2017-03-16 Sharp Kabushiki Kaisha Base station apparatus, mobile station apparatus, and communication method
CN102946299A (zh) * 2012-11-23 2013-02-27 大唐移动通信设备有限公司 监测丢帧的方法、装置及基站
CN107006037A (zh) * 2014-10-03 2017-08-01 瑞典爱立信有限公司 在多载波场景中处理物理随机接入信道传输

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3735088A4 *

Also Published As

Publication number Publication date
CN109982442A (zh) 2019-07-05
EP3735088A4 (en) 2021-06-30
US20200367293A1 (en) 2020-11-19
EP3735088A1 (en) 2020-11-04

Similar Documents

Publication Publication Date Title
WO2019129139A1 (zh) 一种在用户设备上运行的方法及用户设备
JP7065177B2 (ja) ビーム障害回復に対するランダムアクセスのための方法およびデバイス
WO2019179514A1 (zh) 在用户设备上运行的方法及用户设备
WO2018171577A1 (zh) 基站、用户设备和相关方法
US11329711B2 (en) Apparatus, method and computer program
EP3644684B1 (en) User equipment and related method
CN108696884B (zh) 改进双卡双待设备的寻呼类型2性能的方法及装置
JP2018514097A5 (zh)
US11337255B2 (en) Wireless communication method and device
WO2021027456A1 (zh) 由用户设备执行的方法以及用户设备
WO2018196601A1 (zh) 数据传输方法和设备
AU2018311884B2 (en) Method and device for resetting media access control layer
US9532388B2 (en) Activating and deactivating transmission time interval bundling
WO2018201957A1 (zh) 用户设备和相关方法
WO2017118097A1 (zh) 故障报告方法及装置
EP3596974B1 (en) Monitoring and handling a radio link failure in an inactive state
WO2022127864A1 (zh) 用户设备的连接方法以及用户设备
TWI448175B (zh) A method and a device for activating a carrier component of a user equipment for handoff
JP2014183508A (ja) 基地局及び方法

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: 18896528

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018896528

Country of ref document: EP

Effective date: 20200727