WO2022116938A1 - 由用户设备执行的方法以及用户设备 - Google Patents

由用户设备执行的方法以及用户设备 Download PDF

Info

Publication number
WO2022116938A1
WO2022116938A1 PCT/CN2021/133996 CN2021133996W WO2022116938A1 WO 2022116938 A1 WO2022116938 A1 WO 2022116938A1 CN 2021133996 W CN2021133996 W CN 2021133996W WO 2022116938 A1 WO2022116938 A1 WO 2022116938A1
Authority
WO
WIPO (PCT)
Prior art keywords
beam failure
serving cell
cell
bfd
timer
Prior art date
Application number
PCT/CN2021/133996
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 夏普株式会社
Publication of WO2022116938A1 publication Critical patent/WO2022116938A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • H04L5/0096Indication of changes in allocation
    • H04L5/0098Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24Cell structures
    • H04W16/28Cell structures using beam steering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment

Definitions

  • the present invention relates to the technical field of wireless communication, and more particularly, the present invention relates to a method for performing wireless link monitoring and beam failure detection by user equipment and corresponding user equipment.
  • Both radio link monitoring and beam failure detection are performed in the RRC connected state.
  • the quality of the radio link is generally relatively stable. If such a terminal is configured with a short DRX cycle at the same time, it may frequently monitor the radio link and detect beams, resulting in useless power consumption. In this case, after judging by certain criteria, the terminal can relax the wireless link monitoring, such as reducing the number of sampling times and lengthening the monitoring period. Similarly, after a certain accurate judgment, the beam failure detection can also be relaxed, so as to achieve the purpose of saving power consumption.
  • This disclosure discusses relaxed wireless link monitoring and relaxed beam failure detection, as well as the related issues of falling back from relaxed monitoring or detection to normal monitoring or detection.
  • the present invention provides a method performed by user equipment and user equipment, which can effectively trigger relaxed RLM and normalized RLM, and effectively trigger relaxed BFD and normalized BFD .
  • a method performed by a user equipment UE comprising: in the case of detecting a beam failure for a serving cell, a medium access control MAC entity indicates the beam failure information for the serving cell to a wireless a resource control RRC layer; and in the case that the beam failure recovery for the serving cell is successful, the MAC entity indicates the beam failure recovery information for the serving cell to the RRC layer.
  • the detection of beam failure for the serving cell includes at least one of the following situations: the number of beam failure case indications for the serving cell reported by the MAC entity and reported by the physical layer is greater than or equal to the number of beams Maximum count value of failure cases; the number of beam failure case indications reported by the MAC entity for the serving cell reported by the physical layer is greater than or equal to a first threshold, and the first threshold is less than the maximum count value of beam failure cases ; and the MAC entity receives the beam failure case indication reported by the physical layer.
  • the situation that the beam failure recovery for the serving cell is successful includes at least one of the following situations: the serving cell is a special cell, and the random access procedure initiated for the beam failure recovery of the special cell succeeds;
  • the serving cell is a secondary cell and is used to transmit a beam failure recovery MAC control element or a truncated beam failure recovery MAC control element containing beam failure recovery information for the serving cell.
  • the hybrid automatic request retransmission HARQ process is received by The cell wireless network temporarily identifies an uplink grant for new transmission indicated by the physical downlink control channel PDCCH scrambled by the C-RNTI; and the serving cell is a secondary cell and the secondary cell is deactivated.
  • the method further comprises: in the case that the RRC layer receives the beam failure information for the serving cell indicated by the MAC entity, triggering to start or restart the first a timer; and triggering to stop the first timer for the serving cell when the RRC layer receives the beam failure recovery information for the serving cell indicated by the MAC entity.
  • the method further includes: the RRC layer in the connected state receives the radio resource management RRM measurement value for the serving cell reported by the bottom layer, and performs layer 3 filtering to obtain the measurement result; In the case that the first timer is not running, it is judged whether the beam failure detection BFD relaxation criterion is satisfied according to the measurement result.
  • the method further includes: the RRC layer receives the beam failure detection BFD relaxation indication sent by the network; and in the case that the first timer is not running, configuring the bottom layer to use the relaxed BFD.
  • a method performed by a user equipment UE including: when the number of out-of-sync indications for special cells reported by the physical layer continuously received by the RRC layer is greater than or equal to a first threshold value, trigger the start of the second timer for the special cell; and when the RRC layer continuously receives the number of synchronization instructions for the special cell reported by the physical layer greater than or equal to the second threshold value, stop the timer for the special cell. the second timer of the special cell.
  • the method further includes: the RRC layer in the connected state receives the radio resource management RRM measurement value for the serving cell reported by the bottom layer, and performs layer 3 filtering to obtain the measurement result; In the case that the second timer is not running, it is determined whether the radio link monitoring RLM relaxation criterion is satisfied according to the measurement result.
  • the method further includes: the RRC layer receives a radio link monitoring RLM relaxation indication sent by the network; and in the case that the second timer is not running, configuring the bottom layer to use the relaxed RLM.
  • a user equipment comprising: a processor; and a memory storing instructions, wherein the instructions execute the above-mentioned method when executed by the processor.
  • the relaxed RLM and the restored normal RLM can be effectively triggered, and the relaxed BFD and the restored normal BFD can be effectively triggered.
  • FIG. 1 is a flowchart illustrating a method performed by a user equipment according to Embodiment 1 of the present invention.
  • FIG. 2 is a flowchart illustrating a method performed by a user equipment according to Embodiment 2 of the present invention.
  • FIG. 3 is a flowchart illustrating a method performed by a user equipment according to Embodiment 3 of the present invention.
  • FIG. 4 is a flowchart illustrating a method performed by a user equipment according to Embodiment 4 of the present invention.
  • FIG. 5 is a flowchart illustrating a method performed by a user equipment according to Embodiment 5 of the present invention.
  • FIG. 6 is a flowchart illustrating a method performed by a user equipment according to Embodiment 6 of the present invention.
  • FIG. 7 is a flowchart illustrating a method performed by a user equipment according to Embodiment 7 of the present invention.
  • FIG. 8 is a block diagram schematically showing a user equipment involved in the present invention.
  • UE User Equipment user equipment
  • RRC Radio Resource Control Radio Resource Control
  • MAC Medium Access Control, medium access control
  • RRC_IDLE RRC idle state
  • Radio Access Network Radio Access Layer
  • RSRP Reference Signal Receiving Power, reference signal receiving power
  • PDCCH Physical downlink control channel, physical downlink control channel
  • BWP Bandwidth Part, bandwidth fragment
  • DCI Downlink Control Information, downlink control information
  • MIB Master Information Block, the main information block
  • SIB System Information Block, system information block
  • RLM Radio Link Monitoring, wireless link monitoring
  • BFD Beam Failure Detection, beam failure detection
  • RRM Radio Resource Management, Radio Resource Management
  • a PCell, a PSCell, or an SCell, serving cell which can be PCell, PSCell or SCell
  • SpCell Special Cell, special cell, which can be PCell or PSCell.
  • PCell Primary Cell, the main cell
  • PSCell Primary SCG Cell, the primary SCG cell
  • SCell Secondary Cell, secondary cell
  • SCG Secondary Cell Group, secondary cell group
  • C-RNTI Cell RNTI, cell RNTI
  • Radio Network Temporary Identifier Radio Network Temporary Identifier, wireless network temporary identifier
  • HARQ Hybrid Automatic Repeat Request, hybrid automatic request retransmission
  • DAPS Dual Active Protocol Stack, dual active protocol stack
  • network, base station and RAN can be used interchangeably, and the network can be a long-term evolution LET network, a new radio access technology (New RAT, NR) network, an enhanced long-term evolution eLTE network, or a 3GPP subsequent evolution version other networks as defined in .
  • New RAT new radio access technology
  • eLTE enhanced long-term evolution eLTE network
  • 3GPP subsequent evolution version other networks as defined in .
  • the user equipment UE may refer to the NR device that supports the NR power consumption and energy saving enhancement function described in the background art, and may also refer to other types of NR devices or LTE devices.
  • RLM Radio Link Monitoring
  • the UE monitors the downlink radio link quality according to the reference signal configured by the network, in order to detect the downlink radio link quality of the cell.
  • the RLM flow is for SpCell (ie PCell, PSCell).
  • the configured reference signal for the RLM procedure may be SSB and/or CSI-RS.
  • the UE performs the RLM procedure on the activated downlink BWP.
  • the UE compares the BLER of the downlink radio link with the two thresholds Q out and Q in based on the configured reference signal.
  • the physical layer sends an out-of-sync (out-of-sync) indication to the upper layer; if the downlink radio link quality is higher than Q in , the physical layer sends an in-sync (synchronization) indication to the upper layer )instruct.
  • the RRC layer continuously receives N310 out-of-sync indications for the SpCell reported by the physical layer, it starts the T310 timer of the corresponding SpCell.
  • the RRC layer continuously receives N311 in-sync indications for the SpCell reported by the physical layer, it stops the T310 timer of the corresponding SpCell.
  • the UE may consider that a radio link failure has occurred, and thus trigger the RRC re-establishment procedure to restore the radio link.
  • the BFD is that the UE detects the beam according to the reference signal configured by the network, in order to detect the failure of the beam.
  • the BFD process can be for each Serving Cell, including SpCell and SCell.
  • the configured reference signal for the BFD procedure may be SSB and/or CSI-RS.
  • the UE performs the BFD procedure on the activated downlink BWP.
  • the UE compares the downlink radio link BLER and Q out_LR threshold based on the configured reference signal. If the downlink radio link quality is lower than Q out_LR , the physical layer sends a beam failure instance indication to the upper layer.
  • the configured parameters for the BFD process also include beamFailureDetectionTimer and beamFailureInstanceMaxCount.
  • beamFailureDetectionTimer is used to control a timer.
  • the timer is started or restarted after the MAC entity receives the beam failure instance indication sent by the physical layer. For BFD that occurs on the SpCell, the timer is stopped after the BFR is successful.
  • the BFI_COUNTER variable is used by the MAC layer to count the number of consecutively received beam failure instance indications. The initial value of this variable is 0, and it is incremented by 1 each time a beam failure instance indication is received. If beamFailureDetectionTimer times out, or beamFailureDetectionTimer, beamFailureInstanceMaxCount or any reference signal configured for beam failure detection by the upper layer of this Serving Cell changes, BFI_COUNTER is cleared.
  • BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount
  • the BFR of the Cell is triggered, that is, the BFR MAC CE or truncated BFR MAC CE containing the beam failure recovery information of the Serving Cell is sent; if the Serving Cell is not an SCell, it is initiated on the SpCell Random access procedure to recover from beam failure.
  • the criteria for judging the success of BFR can be:
  • the Serving Cell is an SCell, and the HARQ process used to transmit the BFR MAC CE or truncated BFR MAC CE containing the Serving Cell beam failure recovery information, receives the PDCCH scrambled by the C-RNTI for the new transmission the uplink authorization;
  • the RRM measurement relaxation in the RRC idle state and the RRC inactive state is that the base station broadcasts the RRM measurement relaxation configuration parameters in the RRC idle state and the inactive state through system messages, including low-speed mobility evaluation and non-cell edge evaluation.
  • the UE judges its mobility and whether it is at the edge of the cell by measuring and evaluating the RSRP of the cell, so as to determine whether to use the relaxed idle state or inactive state RRM measurement.
  • RLM and BFD can also employ similar RSRP-based measures and assessments to determine whether to trigger relaxation.
  • the monitoring and detection of RLM and BFD are based on downlink BLER as mentioned above. Considering that the changes of RSRP and BLER may be different in some cases, the relaxation criterion determined based on RSRP sometimes cannot fully reflect the wireless link situation. Therefore, after judging and executing the relaxed RLM based on RSRP, once the abnormality of the wireless link is detected, it should be able to recover to the normal RLM. Similarly, after judging and performing relaxed BFD based on RSRP, it should be able to recover to normal BFD once beam failure is detected.
  • the steps performed by the user equipment UE include: step 101 and step 103 .
  • the MAC entity indicates the Serving Cell beam failure information to the upper layer (ie, the RRC layer).
  • the beam failure information may include one or more of the following: a beam failure indication, a cell index value of the Serving Cell, and a cell ID of the Serving Cell.
  • the scenarios in which the MAC entity triggers a beam failure indication for each Serving Cell is one or more of the following:
  • the MAC entity indicates the beam failure information to the upper layer (that is, the RRC layer).
  • the threshold may be less than beamFailureInstanceMaxCount and greater than or equal to 1.
  • the MAC entity indicates the beam failure information to the upper layer (ie, the RRC layer).
  • the MAC entity if the MAC entity receives the beam failure instance indication reported by the physical layer, the MAC entity indicates the beam failure information to the upper layer (that is, the RRC layer).
  • the MAC entity indicates the Serving Cell beam failure recovery information to the upper layer (ie, the RRC layer).
  • the beam failure recovery information may include one or more of the following: a beam failure recovery indication, a cell index value of the Serving Cell, and a cell ID of the Serving Cell.
  • the scenarios in which the MAC entity triggers a beam failure recovery indication for each Serving Cell are one or more of the following:
  • the MAC entity indicates the beam failure recovery information to the upper layer (ie, the RRC layer).
  • the Serving Cell is an SCell
  • the HARQ process used to transmit the BFR MAC CE or the truncated BFR MAC CE containing the beam failure recovery information of the serving cell receives the PDCCH scrambled by the C-RNTI indicating the For the newly transmitted uplink grant, the MAC entity indicates beam failure recovery information to the upper layer (ie, the RRC layer).
  • the MAC entity indicates beam failure recovery information to the upper layer (ie RRC layer).
  • the conditions that can trigger the MAC entity to consider beam failure recovery success can be applied to trigger the MAC entity to indicate beam failure recovery related information to the upper layer (ie, the RRC layer).
  • the scenario where the MAC entity triggers the Serving Cell beam failure recovery indication may also be:
  • the beamFailureDetectionTimer timer expires, and the MAC entity indicates beam failure recovery information to the upper layer (ie, the RRC layer);
  • beamFailureDetectionTimer is reconfigured by the upper layer, and the MAC entity indicates the beam failure recovery information to the upper layer (ie RRC layer).
  • the steps performed by the user equipment UE include: step 201 and step 203 .
  • step 201 the RRC receives the beam failure information indicated by the MAC, and triggers to start or restart the timer T keep1 .
  • the timer T keep1 may be as follows:
  • each Serving Cell corresponds to a timer T keep1 ;
  • each SpCell corresponds to a timer T keep1 , and the rest of the SCells share a timer T keep1 ;
  • SpCell corresponds to a shared timer T keep1
  • SCells share a shared timer T keep1 .
  • triggering the start or restart of the timer T keep1 includes one or more of the following scenarios:
  • start or restart the timer T keep1 of the Serving Cell, and configure the bottom layer to use normal BFD for the Serving Cell;
  • start or restart the timer T keep1 , and configure the bottom layer to use normal BFD for all serving cells;
  • the Serving Cell is the beam failure information of the SpCell, start or restart the timer T keep1 of the SpCell, and configure the bottom layer to use normal BFD for the SpCell;
  • the Serving Cell is the beam failure information of the SCell, start or restart the timer T keep1 shared by the SCell, and configure the bottom layer to use normal BFD for all SCells;
  • the Serving Cell is the beam failure information of the SpCell
  • start or restart the timer T keep1 shared by the SpCell , and configure the bottom layer to use normal BFD for all SpCells.
  • step 203 when the RRC receives the beam failure recovery information of the Serving Cell indicated by the MAC, the stop timer T keep1 is triggered .
  • Triggering the stop timer T keep1 scenario includes one or more of the following:
  • the Serving Cell is the SpCell's beam failure recovery information
  • stop the SpCell's timer T keep1
  • the Serving Cell is the beam failure recovery information of the SCell, stop the timer T keep1 shared by the SCell;
  • the Serving Cell is the beam failure recovery information of the SpCell
  • stop the timer T keep1 shared by the SpCell .
  • the steps performed by the user equipment UE include: step 301 and step 303 .
  • the RRC layer receives the RRM measurement value of the serving Cell reported by the bottom layer in the connected state, and performs Layer 3 filtering to obtain the measurement result, which may include RSRP, RSRQ, SINR, etc.
  • step 303 if T keep1 is not running, the BFD relaxation criterion may be further determined, and if T keep1 is running, the BFD relaxation determination may not be further determined. Possible scenarios are one or more of the following:
  • the T keep1 of the serving cell determines the BFD relaxation criterion of the serving cell; if the BFD relaxation criterion of the serving cell is satisfied, configure the bottom layer to use the relaxed BFD for the serving cell, otherwise use the normal BFD;
  • T keep1 is not running, you can judge the BFD relaxation criteria of all serving cells; if the relaxation criteria are satisfied, configure the bottom layer to use relaxed BFD for all serving cells, otherwise use normal BFD;
  • the SpCell's T keep1 is not running, it can be judged that the SpCell's BFD relaxation criterion is satisfied; if the relaxation criterion is satisfied, configure the bottom layer to use relaxed BFD for the SpCell, otherwise use normal BFD;
  • the BFD relaxation criteria of all SpCells can be judged; if the relaxation criteria are satisfied, configure the bottom layer to use relaxed BFD for all SpCells, otherwise use normal BFD;
  • the BFD relaxation criterion of the SCell can be judged; if the relaxation criterion is satisfied, configure the bottom layer to use relaxed BFD for all SCells, otherwise use normal BFD.
  • the criteria for relaxing BFD include but are not limited to: judging whether the UE has low mobility, for example, the RSRP value change value of the Serving cell is less than a certain threshold; or judging whether the UE is at the edge of the cell, for example, according to whether the UE frequently switches.
  • the bottom layer adopts relaxed BFD or normal BFD
  • the BFD mode that is, relaxed BFD or normal BFD
  • the BFD mode changes perform the configuration again.
  • the relaxed BFD is still the normal BFD operation at the bottom layer. Otherwise, no configuration operation is required.
  • step 303 it is also possible to firstly judge the BFD sending criterion on the serving cell that obtained the measurement result, and then judge the operation of T keep1 after the relaxation criterion is judged to satisfy the condition. If T keep1 is not running, you can configure the bottom layer to use relaxed BFD; otherwise, use normal BFD. The specific optional conditions remain unchanged and will not be described again.
  • the steps performed by the user equipment UE include: step 401 and step 403 .
  • step 401 the RRC layer receives the relaxed BFD indication sent by the network.
  • step 403 if T keep1 is not running, configure the bottom layer to use relaxed BFD, and if T keep1 is running, do not configure the bottom layer to use relaxed BFD (ie, use normal BFD).
  • T keep1 is not running, configure the bottom layer to use relaxed BFD, and if T keep1 is running, do not configure the bottom layer to use relaxed BFD (ie, use normal BFD).
  • Possible scenarios are one or more of the following:
  • the T keep1 of the Serving Cell is not running and the network instructs the serving cell to use relaxed BFD, configure the bottom layer to use relaxed BFD for the serving cell, otherwise use normal BFD;
  • T keep1 is not running and the network instructs the serving cell to use relaxed BFD, configure the bottom layer to use relaxed BFD for all serving cells, otherwise use normal BFD;
  • the network instructs the SpCell to use relaxed BFD, configure the bottom layer to use relaxed BFD for the SpCell, otherwise use normal BFD;
  • the T keep1 of the SCell is not running and the network instructs to use relaxed BFD for the SCell, configure the bottom layer to use relaxed BFD for all SCells, otherwise use normal BFD.
  • the bottom layer before configuring the bottom layer to use relaxed BFD or normal BFD, you can determine whether the bottom layer is configured to use BFD (that is, relaxed BFD or normal BFD). When the BFD mode changes, configure the bottom layer again. Using relaxed BFD is still a normal BFD operation, otherwise, you do not need to configure the underlying operation.
  • BFD relaxed BFD or normal BFD
  • the steps performed by the user equipment UE include: step 501 and step 503 .
  • step 501 when the RRC layer continuously receives the number of out-of-sync indications of the SpCell reported by the physical layer is greater than or equal to a threshold value (for example, radioFailIndThreshold), a timer T keep2 is triggered to start.
  • Trigger scenarios include one or more of the following:
  • the threshold can be less than N310, greater than or equal to 1, then start or restart the T keep2 timer of the corresponding SpCell, and configure the bottom layer to use normal RLM for the corresponding SpCell;
  • T300 may be started when an RRCSetupRequest message is sent, and stopped when an RRCSetup or RRCReject is received.
  • T301 may be started when the RRCReestabilshmentRequest message is sent, and stopped when the RRCReestablishment or RRCSetup is received.
  • T311 may be started when an RRC reestablishment procedure is initiated, and stopped when an appropriate cell is selected.
  • T316 may be started when the MCGFailureInformation message is sent, and stopped when the RRCRelease, the RRCReconfiguration message with synchronous reconfiguration, the MobilityFromNRCommand message is received, or the re-establishment is initiated.
  • T319 may be started when an RRCResumeRequest or RRCResumeRequest1 message is initiated, and stopped when an RRCResume, RRCSetup, RRCRelease, RRCRelease with suspendConfig, RRCReject message or cell reselection is received.
  • the RRC layer continuously receives the number of "out-of-sync" indications of SpCells reported by the physical layer greater than or equal to a threshold (for example: radioFailIndThreshold); optionally, the threshold may be less than N310, greater than or equal to 1; then start or restart the T keep2 timer of the corresponding SpCell, and configure the bottom layer to use normal RLM for the corresponding SpCell;
  • a threshold for example: radioFailIndThreshold
  • the DAPS bearer when the RRC layer continuously receives the out-of-sync indications for the source measurement SpCell reported by the physical layer, the number is greater than or equal to a threshold value (for example, radioFailIndThreshold), And T304 is running, start or restart the T keep2 timer of the SpCell on the source side, and configure the bottom layer to use normal RLM for the SpCell on the source side.
  • a threshold value for example, radioFailIndThreshold
  • the DAPS bearer is a kind of bearer configured in the DAPS handover process.
  • the wireless protocol stack of this bearer exists on both sides of the source gNB and the target gNB, and can use both the source gNB resources and the target side gNB resources.
  • step 503 during the operation of T keep2 , when the RRC layer continuously receives the number of in-sync indications for SpCell reported by the physical layer is greater than or equal to a threshold (for example, but not limited to: radioFailRecoverThreshold), optionally, the threshold
  • a threshold for example, but not limited to: radioFailRecoverThreshold
  • the threshold can be less than N311 and greater than or equal to 1; then stop the T keep2 timer corresponding to the SpCell.
  • T keep2 can also be shared by all SpCells, that is, shared by PCell and PSCell. If so specified, starting, restarting, and stopping the T keep2 timer does not need to be specified as stopping the corresponding SpCell.
  • the steps performed by the user equipment UE include: step 601 and step 603 .
  • the RRC layer receives the RRM measurement value of the serving Cell reported by the bottom layer in the connected state, and performs layer 3 filtering to obtain the measurement result.
  • the measurement result may include RSRP, RSRQ, SINR, etc.
  • step 603 if the T keep2 of the SpCell is not running, the RLM relaxation criterion may be further judged, and if the T keep2 is running, the RLM relaxation judgment may not be further judged. Possible scenarios are one or more of the following:
  • the RLM relaxation criterion of all SpCells can be judged; if the relaxation criterion is satisfied, configure the bottom layer to use relaxed RLM for all SpCells, otherwise use normal RLM;
  • the T keep2 of the SpCell is not running, it can be judged that the RLM relaxation criterion of the SpCell is satisfied; if the relaxation criterion is satisfied, the bottom layer is configured to adopt the relaxed RLM for the SpCell, otherwise, the normal RLM is adopted;
  • the criteria for relaxing the RLM include but are not limited to: judging whether the UE has low mobility, for example, the RSRP value of the Serving cell changes less than a certain threshold; or judging whether the UE is at the edge of the cell, for example, according to whether the UE frequently switches.
  • the bottom layer adopts relaxed RLM or normal RLM
  • RLM mode that is, relaxed RLM or normal RLM
  • the RLM mode changes perform the configuration again
  • the bottom layer adopts the relaxed RLM operation or the normal RLM operation, otherwise the configuration operation is not required.
  • the RLM relaxation criterion may also be judged first on the SpCell from which the measurement result is obtained, and after the relaxation criterion is judged to satisfy the condition, the operation of T keep2 may be judged. If T keep2 is not running, the bottom layer can be configured to use relaxed RLM; otherwise, normal RLM is used. The specific optional situations are the same, and are not repeated here.
  • the steps performed by the user equipment UE include: step 701 and step 703 .
  • step 701 the RRC layer receives the relaxation RLM indication sent by the network.
  • step 703 if T keep2 is not running, configure the bottom layer to use relaxed RLM, and if T keep2 is running, do not configure the bottom layer to use relaxed RLM (ie, use normal RLM).
  • Possible scenarios are one or more of the following:
  • the network instructs the SpCell to use relaxed RLM, configure the bottom layer to use the relaxed RLM for the SpCell, otherwise use the normal RLM;
  • the bottom layer before configuring the bottom layer to use relaxed RLM or normal RLM, it can be determined that the bottom layer is configured to use the RLM mode (that is, the relaxed RLM or the normal RLM), and when the RLM mode changes, configure the bottom layer again.
  • the relaxed RLM is still the operation of the normal RLM, otherwise, no configuration operation is required.
  • FIG. 8 is used to illustrate a user equipment that can execute the method performed by the user equipment described in detail above in the present invention as a modification.
  • FIG. 8 is a block diagram showing a user equipment UE according to the present invention.
  • the user equipment UE80 includes a processor 801 and a memory 802 .
  • the processor 801 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
  • the memory 802 may include, for example, volatile memory (eg, random access memory RAM), a hard disk drive (HDD), non-volatile memory (eg, flash memory), or other memory, or the like.
  • Program instructions are stored on the memory 802 . When the instruction is executed by the processor 801, the above method described in detail in the present invention and executed by the user equipment can be executed.
  • a program running on a device 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 may be temporarily stored in volatile memory (eg, random access memory RAM), a hard disk drive (HDD), non-volatile memory (eg, flash memory), or other memory systems.
  • 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” as used herein may be a computer system embedded in the device, and may include an operating system or hardware (eg, peripheral devices).
  • the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that dynamically stores a program for a short period of time, or any other recording medium readable by a computer.
  • circuits eg, monolithic or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may 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. Where new integrated circuit technologies have emerged as a result of advances in semiconductor technology to replace existing integrated circuits, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the above-described embodiments. Although various examples of the described embodiments have been described, the invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

根据本发明,提出了一种由用户设备UE执行的方法,包括:在检测到针对服务小区的波束失败的情况下,媒质接入控制MAC实体将针对所述服务小区的波束失败信息指示给无线资源控制RRC层;以及在针对服务小区的波束失败恢复成功的情况下,所述MAC实体将针对所述服务小区的波束失败恢复信息指示给所述RRC层。

Description

由用户设备执行的方法以及用户设备 技术领域
本发明涉及无线通信技术领域,更具体地,本发明涉及由用户设备执行无线链路监测和波束失败检测的方法以及相应的用户设备。
背景技术
2019年12月,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#86次全会上,针对版本17的节省功率消耗增强的工作项目(参见非专利文献:RP-193239New WID:UE Power Saving Enhancements),并获批准。该工作项目的最新版本参见非专利文献:RP-200938 Revised WID_UE Power Saving Enhancements for NR_Change。该工作项目主要研究RRC空闲态和RRC非激活态下终端如何节省功率。该工作项目的目标之一是研究和评估低移动性场景下放松终端的无线链路监测和放松终端的波束失败检测。
无线链路监测和波束失败检测都是在RRC连接态进行的。对于低移动性终端,无线链路质量一般相对稳定,如果此类终端同时配置了较短的DRX周期,可能频繁监测无线链路和检测波束而产生无用的功率消耗。在这种情况下,经过一定的准则判断后,终端可以放松无线链路监测,比如减少采样次数、加长监测周期等。同样,经过一定的准确判断后,也可以放松波束失败检测,从而达到节省功耗的目的。当监测到无线链路异常时,需要从放松的无线链路监测恢复到正常的无线链路监测,以便及时监测到无线链路的变化,在无线链路失败时及时发起链路恢复等流程,避免放松的无线链路监测对无线链路恢复产生影响,进而避免对用户业务产生影响。同理,对于波束失败检测也需要有类似的从放松的波束失败检测恢复到正常的波束失败检测的方法。
本发明讨论放松的无线链路监测和放松的波束失败检测,以及从放松的监测或检测回退为正常的监测或检测的相关问题。
发明内容
为了解决上述问题中的至少一部分,本发明提供了一种由用户设备执行的方法以及用户设备,能够有效地触发放松的RLM和恢复正常的RLM,以及有效地触发放松的BFD和恢复正常的BFD。
根据本发明,提出了一种由用户设备UE执行的方法,包括:在检测到针对服务小区的波束失败的情况下,媒质接入控制MAC实体将针对所述服务小区的波束失败信息指示给无线资源控制RRC层;以及在针对服务小区的波束失败恢复成功的情况下,所述MAC实体将针对所述服务小区的波束失败恢复信息指示给所述RRC层。
优选地,所述检测到针对服务小区的波束失败的情况包括以下情况的至少一种:所述MAC实体接收的物理层上报的针对所述服务小区的波束失败例指示的个数大于或等于波束失败例最大计数值;所述MAC实体接收的物理层上报的针对所述服务小区的波束失败例指示的个数大于或等于第一门限,所述第一门限小于所述波束失败例最大计数值;以及所述MAC实体接收到物理层上报的波束失败例指示。
优选地,所述针对服务小区的波束失败恢复成功的情况包括以下情况的至少一种:所述服务小区是特殊小区,并且针对所述特殊小区的波束失败恢复发起的随机接入过程成功;所述服务小区是辅小区,并且用于传输包含针对所述服务小区的波束失败恢复信息的波束失败恢复MAC控制元素或者截断的波束失败恢复MAC控制元素的混合自动请求重传HARQ进程,收到由小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH指示的用于新传的上行授权;以及所述服务小区是辅小区且所述辅小区被去激活。
优选地,所述方法还包括:在所述RRC层收到由所述MAC实体指示的针对所述服务小区的所述波束失败信息的情况下,触发启动或重启针对所述服务小区的第一定时器;以及在所述RRC层收到由所述MAC实体指示的针对所述服务小区的所述波束失败恢复信息的情况下,触发停止针对所述服务小区的所述第一定时器。
优选地,所述方法还包括:所述RRC层在连接态下收到底层上报的针对所述服务小区的无线资源管理RRM测量值,进行层三滤波得到测量结果; 以及在针对所述服务小区的所述第一定时器并未运行的情况下,根据所述测量结果来判断是否满足波束失败检测BFD放松准则。
优选地,所述方法还包括:所述RRC层接收网络发送的波束失败检测BFD放松指示;以及在所述第一定时器并未运行的情况下,则配置底层采用放松的BFD。
另外,根据本发明,提出了一种由用户设备UE执行的方法,包括:当无线资源控制RRC层连续收到物理层上报的针对特殊小区的失步指示的个数大于或等于第一门限值时,触发启动针对所述特殊小区的第二定时器;以及当RRC层连续收到物理层上报的针对所述特殊小区的同步指示的个数大于或等于第二门限值时,停止针对所述特殊小区的所述第二定时器。
优选地,所述方法还包括:所述RRC层在连接态下收到底层上报的针对服务小区的无线资源管理RRM测量值,进行层三滤波得到测量结果;以及在针对所述特殊小区的所述第二定时器并未运行的情况下,根据所述测量结果来判断是否满足无线链路监测RLM放松准则。
优选地,所述方法还包括:所述RRC层接收网络发送的无线链路监测RLM放松指示;以及在所述第二定时器并未运行的情况下,则配置底层采用放松的RLM。
此外,根据本发明,提出了一种用户设备,包括:处理器;以及存储器,存储有指令,其中,所述指令在由所述处理器运行时执行上述的方法。
根据本发明,能够有效地触发放松的RLM和恢复正常的RLM,以及有效地触发放松的BFD和恢复正常的BFD。
附图说明
图1是示出了根据本发明的实施例1的由用户设备执行的方法的流程图。
图2是示出了根据本发明的实施例2的由用户设备执行的方法的流程图。
图3是示出了根据本发明的实施例3的由用户设备执行的方法的流程图。
图4是示出了根据本发明的实施例4的由用户设备执行的方法的流程图。
图5是示出了根据本发明的实施例5的由用户设备执行的方法的流程图。
图6是示出了根据本发明的实施例6的由用户设备执行的方法的流程图。
图7是示出了根据本发明的实施例7的由用户设备执行的方法的流程图。
图8是示意性示出本发明所涉及的用户设备的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意,本发明不应局限于下文所述的具体实施方式。另外,为了简便起见,省略了对与本发明没有直接关联的公知技术的详细描述,以防止对本发明的理解造成混淆。
下面描述本发明涉及的部分术语,术语的具体含义见3GPP最新标准规范,例如TS38.300、TS38.331、TS38.133、TS38.321等。除非另有指出,本发明中涉及的术语都具有下文的含义。
UE:User Equipment用户设备
NR:New Radio新一代无线技术
RRC:Radio Resource Control无线资源控制
MAC:Medium Access Control,媒质接入控制
RRC_CONNECTED:RRC连接态
RRC_INACTIVE:RRC非激活态
RRC_IDLE:RRC空闲态
RAN:Radio Access Network,无线接入层
RSRP:Reference Signal Receiving Power,参考信号接收功率
AS:Access Stratum,接入层
PDCCH:Physical downlink control channel,物理下行控制信道
BWP:Bandwidth Part,带宽片段
DCI:Downlink Control Information,下行控制信息
DL:Downlink,下行
IE:Information Element,信息元素
CE:Control Element,控制元素
MIB:Master Information Block,主信息块
SIB:System Information Block,系统信息块
RLM:Radio Link Monitoring,无线链路监测
BFD:Beam Failure Detection,波束失败检测
RLF:Radio Link Failure,无线链路失败
BFR:Beam Failure Recovery,波束失败恢复
BLER:Block Error Rate,误块率
RRM:Radio Resource Management,无线资源管理
Serving Cell:A PCell,a PSCell,or an SCell,服务小区,可以是PCell,PSCell或者SCell
SpCell:Special Cell,特殊小区,可以是PCell或PSCell。
PCell:Primary Cell,主小区
PSCell:Primary SCG Cell,主SCG小区
SCell:Secondary Cell,辅小区
SCG:Secondary Cell Group,辅小区组
C-RNTI:Cell RNTI,小区RNTI
RNTI:Radio Network Temporary Identifier,无线网络临时标识
HARQ:Hybrid Automatic Repeat Request,混合自动请求重传
DAPS:Dual Active Protocol Stack,双激活协议栈
本发明中,网络、基站和RAN可互换使用,所述网络可以是长期演进LET网络、新无线访问技术(New RAT,NR)网络、增强的长期演进eLTE网络,也可以是3GPP后续演进版本中定义的其他网络。
本发明中,用户设备UE可以指背景技术中所述的支持NR功耗节能增强功能的NR设备,也可以指其他类型的NR设备或者LTE设备。
在现有技术中,RLM(无线链路监测)是UE根据网络配置的参考信号监测下行无线链路质量,目的是为了检测到小区的下行无线链路质量的情况。RLM流程针对SpCell(即PCell,PSCell)。配置的用于RLM流程的参考信号可以是SSB和/或CSI-RS。UE在激活的下行BWP上执行RLM流程。为了判断下行链路的质量,UE基于配置的参考信号对下行无线链路的BLER和Q out、Q in这两个门限进行比较。如果下行无线链路质量低于Q out,则物理层向上层发送out-of-sync(失步)指示;如果下行无线链路质量高于 Q in,则物理层向上层发送in-sync(同步)指示。当RRC层连续收到N310个物理层上报的对于SpCell的out-of-sync指示,则启动对应的SpCell的T310定时器。在T310运行期间,当RRC层连续收到了N311个物理层上报的对于SpCell的in-sync指示,则停止对应的SpCell的T310定时器。当T310定时器超时,UE可以认为无线链路失败发生了,从而触发RRC重建流程来恢复无线链路。
BFD是UE根据网络配置的参考信号检测波束,目的是为了检测到波束失败的情况。BFD流程可以针对每个Serving Cell,包括SpCell和SCell。配置的用于BFD流程的参考信号可以是SSB和/或CSI-RS。UE在激活的下行BWP上执行BFD流程。UE基于配置的参考信号对下行无线链路的BLER和Q out_LR这个门限进行比较。如果下行无线链路质量低于Q out_LR,则物理层向上层发送beam failure instance indication(波束失败例指示)。配置的用于BFD流程的参数还包括:beamFailureDetectionTimer和beamFailureInstanceMaxCount。beamFailureDetectionTimer用于控制一个定时器,该定时器在MAC实体收到物理层发送的beam failure instance indication后启动或者重启,对于SpCell上发生的BFD该定时器在BFR成功后停止。BFI_COUNTER变量用于MAC层计数连续收到beam failure instance indication的个数,该变量初始值为0,每收到一次beam failure instance indication加1。如果beamFailureDetectionTimer超时,或者beamFailureDetectionTimer,beamFailureInstanceMaxCount或者对于本Serving Cell上层配置的用于波束失败检测的任何参考信号发生改变,则BFI_COUNTER清零。当BFI_COUNTER大于等于beamFailureInstanceMaxCount,如果Serving Cell是SCell,触发该Cell的BFR,即发送包含Serving Cell波束失败恢复信息的BFR MAC CE或者截断的BFR MAC CE;如果该Serving Cell不是SCell,则在SpCell上发起随机接入过程来对波束失败进行恢复。
其中,BFR成功的判断标准可以是:
-如果Serving Cell是SpCell,并且为SpCell波束失败恢复发起的随机接入过程成功;
-或者,如果Serving Cell是SCell,并且用于传输包含Serving Cell波束失败恢复信息的BFR MAC CE或者截断的BFR MAC CE的 HARQ进程,收到由C-RNTI加扰的PDCCH指示的用于新传的上行授权;
-或者,如果SCell被去激活。
同时,在现有技术中,在RRC空闲态和RRC非激活态RRM测量放松是基站通过系统消息广播RRC空闲态和非激活态下的RRM测量放松配置参数,包括低速移动评估和非小区边缘评估的开关、低速移动和非小区边缘的判决门限和判决时间参数等。UE通过对小区RSRP的测量和评估,判断自己的移动性和是否处于小区边缘,从而确定是否采用放松的空闲态或非激活态RRM测量。
RLM和BFD也可以采用类似的基于RSRP的测量和评估来确定是否触发放松。如前所述RLM和BFD的监测和检测都是基于下行链路的BLER。考虑到RSRP和BLER的变化在一些情况下可能不同,因此基于RSRP判断出的放松准则有时不能够完全体现出无线链路情况。所以,基于RSRP判断并执行放松的RLM后,一旦检测到无线链路异常应该能够恢复为正常的RLM。类似的,如果基于RSRP判断并执行放松的BFD后,一旦检测到波束失败应该能够恢复为正常的BFD。由于无线链路异常而回退到正常的RLM后,再次收到RSRP测量结果并通过判断准则发现满足放松RLM条件时,仍然保持正常的RLM,以便UE能够及时恢复链路。同理,由于波束失败而回退到正常的BFD后,再次收到RSRP测量结果并通过判断准则发现满足放松BFD条件时,仍然保持正常的BFD,以便UE能够及时恢复波束。从而,达到既节省了UE的功耗又不影响业务体验的效果。
以下,详细描述本发明对触发放松的RLM和恢复正常的RLM,以及触发放松的BFD和恢复正常的BFD相关流程的若干实施例。
实施例1
在本发明的实施例1中,如图1所示,用户设备UE执行的步骤包括:步骤101和步骤103。
在步骤101,MAC实体将Serving Cell波束失败信息指示给上层(即RRC层)。其中,波束失败信息可以包含如下一种或者多种:波束失败指示,Serving Cell的小区索引值,Serving Cell的小区ID。
MAC实体对每个Serving Cell触发波束失败指示的场景为如下的一种 或多种:
-可选地,如果MAC实体接收物理层上报的Serving Cell的beam failure instance indication个数(BFI_COUNTER)大于等于beamFailureInstanceMaxCount,MAC实体将波束失败信息指示给上层(即RRC层)。
-可选地,如果MAC实体接收物理层上报的beam failure instance indication个数(BFI_COUNTER)大于等于一个门限值(例如但不限于:beamFailIndThreshold),可选地,该门限值可以小于beamFailureInstanceMaxCount大于等于1,MAC实体将波束失败信息指示给上层(即RRC层)。
-可选地,如果MAC实体接收到物理层上报的beam failure instance indication,则MAC实体将波束失败信息指示给上层(即RRC层)。
在步骤103,MAC实体将Serving Cell波束失败恢复信息指示给上层(即RRC层)。其中,波束失败恢复信息可以包含如下一种或者多种:波束失败恢复指示,Serving Cell的小区索引值,Serving Cell的小区ID。
MAC实体对每个Serving Cell触发波束失败恢复指示的场景为如下的一种或多种:
-可选地,如果Serving Cell是SpCell,并且为SpCell波束失败恢复发起的随机接入过程成功,MAC实体将波束失败恢复信息指示给上层(即RRC层)。
-可选地,如果Serving Cell是SCell,并且用于传输包含服务小区波束失败恢复信息的BFR MAC CE或者截断的BFR MAC CE的HARQ进程,收到由C-RNTI加扰的PDCCH指示的用于新传的上行授权,MAC实体将波束失败恢复信息指示给上层(即RRC层)。
-可选地,如果SCell被去激活,MAC实体将波束失败恢复信息指示给上层(即RRC层)。
换言之,等价地,能够触发MAC实体认为波束失败恢复成功的条件,均可以适用于触发MAC实体将波束失败恢复的相关信息指示给上层(即RRC层)。
或者,MAC实体触发Serving Cell波束失败恢复指示的场景,还可能为:
-可选地,beamFailureDetectionTimer定时器超时,MAC实体将波束失败恢复信息指示给上层(即RRC层);
-可选地,beamFailureDetectionTimer,beamFailureInstanceMaxCount,步骤101中提到的门限值(beamFailIndThreshold),或者是任何用于波束失败检测的参考信号被上层重新配置,MAC实体将波束失败恢复信息指示给上层(即RRC层)。
实施例2
在本发明的实施例2中,如图2所示,用户设备UE执行的步骤包括:步骤201和步骤203。
在步骤201中,RRC收到MAC指示的波束失败信息,触发启动或重启定时器T keep1
其中,定时器T keep1可能是如下情况:
-可选地,每个Serving Cell对应一个定时器T keep1
-可选地,所有Serving Cell共用一个定时器T keep1
-可选地,每个SpCell对应一个定时器T keep1,其余的SCell共用一个定时器T keep1
-可选地,SpCell对应一个共用定时器T keep1,SCell共用一个定时器T keep1
当RRC收到MAC指示的Serving Cell的波束失败信息,触发启动或重启定时器T keep1场景包括如下一种或多种:
-可选地,启动或者重启该Serving Cell的定时器T keep1,配置底层对该Serving Cell采用正常的BFD;
-可选地,启动或者重启定时器T keep1,配置底层对所有serving Cell采用正常的BFD;
-可选地,如果Serving Cell为SpCell的波束失败信息,启动或重启该SpCell的定时器T keep1,配置底层对该SpCell采用正常的BFD;
-可选的,如果Serving Cell为SCell的波束失败信息,启动或重启SCell 共用的定时器T keep1,配置底层对所有SCell采用正常的BFD;
-可选地,如果Serving Cell为SpCell的波束失败信息,启动或重启该SpCell共用的定时器T keep1,配置底层对所有SpCell采用正常的BFD。
其中,可选地,在配置底层采用正常的BFD之前,还可以检查是否之前配置过底层采用放松的BFD,如果没有配置过放松的BFD,则不用执行配置正常BFD动作,即原有即为正常BFD。
在步骤203中,当RRC收到MAC指示的Serving Cell的波束失败恢复信息,触发停止定时器T keep1
触发停止定时器T keep1场景包括如下一种或多种:
-可选地,停止该Serving Cell的定时器T keep1
-可选地,停止定时器T keep1
-可选地,如果Serving Cell为SpCell的波束失败恢复信息,停止该SpCell的定时器T keep1
-可选的,如果Serving Cell为SCell的波束失败恢复信息,停止SCell共用的定时器T keep1
-可选地,如果Serving Cell为SpCell的波束失败恢复信息,停止SpCell共用的定时器T keep1
实施例3
在本发明的实施例3中,如图3所示,用户设备UE执行的步骤包括:步骤301和步骤303。
在步骤301中,RRC层在连接态下收到底层上报的serving Cell的RRM测量值,进行层三滤波得到测量结果,测量结果可能包含RSRP,RSRQ,SINR等。
在步骤303中,如果T keep1不在运行,则可能进一步判断BFD放松准则,如果T keep1在运行,则可以不用进一步判断BFD放松判断。可能的场景为如下一种或多种:
-可选地,如果Serving Cell的T keep1没有在运行,则判断该serving cell 的BFD放松准则;如果该serving cell的BFD放松准则满足,则配置底层对该serving cell采用放松的BFD,否则采用正常BFD;
-可选地,如果T keep1没有在运行,则可以判断所有serving cell的BFD放松准则;如果放松准则满足,则配置底层对所有serving cell采用放松的BFD,否则采用正常BFD;
-可选地,如SpCell的T keep1没有在运行,则可以判断该SpCell的BFD放松准则;如果放松准则满足,则配置底层对该SpCell采用放松的BFD,否则采用正常BFD;
-可选地,如SpCell共用的T keep1没有在运行,则可以判断所有SpCell的BFD放松准则;如果放松准则满足,则配置底层对所有SpCell采用放松的BFD,否则采用正常BFD;
-可选地,如SCell的T keep1没有在运行,则可以判断SCell的BFD放松准则;如果放松准则满足,则配置底层对所有SCell采用放松的BFD,否则采用正常BFD。
其中,放松BFD的准则包括但不限于:判断UE是否为低移动性,例如Serving cell的RSRP值变化值小于一定门限;或者判断UE是否在小区边缘,例如根据UE是否频繁发生切换。
其中,可选地,在配置底层采用放松的BFD还是正常的BFD之前,可以判断之前配置了底层采用BFD的方式(即放松的BFD还是正常的BFD),当BFD方式发生变化时候,再执行配置底层采用放松的BFD还是正常的BFD的操作,否则不用执行配置操作。
在步骤303中,还可以先对得到测量结果的serving cell进行BFD发送准则判断,当放松准则判断满足条件后,再判断T keep1的运行情况。如果T keep1不在运行,则可以配置底层采用放松的BFD;否则,采用正常的BFD。具体的可选情况不变,不再赘述。
实施例4
在本发明的实施例4中,如图4所示,用户设备UE执行的步骤包括:步骤401和步骤403。
在步骤401,RRC层收到网络发送的放松BFD指示。
在步骤403,如果T keep1不在运行,则配置底层采用放松的BFD,如果 T keep1在运行,则不用配置底层采用放松的BFD(即采用正常BFD)。可能的场景为如下一种或多种:
-可选地,如果Serving Cell的T keep1没有在运行,网络指示对该servingcell采用放松BFD,则配置底层对该serving cell采用放松的BFD,否则采用正常BFD;
-可选地,如果T keep1没有在运行,网络指示对serving cell采用放松BFD,则配置底层对所有serving cell采用放松的BFD,否则采用正常BFD;
-可选地,如SpCell的T keep1没有在运行,网络指示对SpCell采用放松BFD,则配置底层对该SpCell采用放松的BFD,否则采用正常BFD;
-可选地,如SpCell共用的T keep1没有在运行,网络指示对SpCell采用放松BFD,则配置底层对所有SpCell采用放松的BFD,否则采用正常BFD;
-可选地,如SCell的T keep1没有在运行,网络指示对SCell采用放松BFD,则配置底层对所有SCell采用放松的BFD,否则采用正常BFD。
其中,可选地,在配置底层采用放松的BFD还是正常的BFD之前,可以判断之前配置底层采用BFD的方式(即放松的BFD还是正常的BFD),当BFD方式发生变化时候,再执行配置底层采用放松的BFD还是正常的BFD的操作,否则不用执行配置底层的操作。
实施例5
在本发明的实施例5中,如图5所示,用户设备UE执行的步骤包括:步骤501和步骤503。
在步骤501中,当RRC层连续收到物理层上报的SpCell的out-of-sync指示个数大于等于一个门限值(例如radioFailIndThreshold),触发启动定时器T keep2。触发场景包含如下一种或多种:
-可选地,在T300,T301,T311,T316以及T319这些定时器都没有运行时,当RRC层连续接收到物理层上报的SpCell的“out-of-sync”指示的个数大于等于一个门限值(例如但不限于:radioFailIndThreshold),该门限值可以小于N310,大于等于1,则 启动或重启对应SpCell的T keep2定时器,配置底层对对应SpCell采用正常的RLM;
T300可以是RRCSetupRequest消息发送时候启动,收到RRCSetup或者RRCReject时停止。
T301可以是RRCReestabilshmentRequest消息发送时启动,收到RRCReestablishment或者RRCSetup时停止。
T311可以是发起RRC重建流程时启动,选择到合适的小区时停止。
T316可以是MCGFailureInformation消息发送时启动,收到RRCRelease、带同步重配的RRCReconfiguration消息、MobilityFromNRCommand消息或者发起重建的时候停止。
T319可以是发起RRCResumeRequest或RRCResumeRequestl消息时启动,收到RRCResume、RRCSetup、RRCRelease、带suspendConfig的RRCRelease、RRCReject消息或者小区重选时停止。
-可选地,当RRC层连续接收到物理层上报的SpCell的“out-of-sync”指示的个数大于等于一个门限值(例如:radioFailIndThreshold);可选地,该门限值可以小于N310,大于等于1;则启动或重启对应SpCell的T keep2定时器,配置底层对对应SpCell采用正常的RLM;
-可选地,在DAPS切换中,如果配置了DAPS bearer,当RRC层连续收到物理层上报的对于源测SpCell的out-of-sync指示个数大于等于一个门限值(例如radioFailIndThreshold),并且T304正在运行,则启动或重启源侧SpCell的T keep2定时器,配置底层对源侧SpCell采用正常的RLM。
其中,可选地,在配置底层采用正常的RLM之前,还可以检查是否之前配置过底层采用放松的RLM,如果没有配置过放松的RLM,则不用执行配置正常RLM动作,即原有即为正常RLM。
其中,DAPS bearer为在DAPS切换流程中配置的一种bearer,这种bearer的无线协议栈存在于源gNB和目标gNB两侧,既能利用源gNB资源也能利用目标侧gNB资源。
在步骤503中,T keep2运行期间,当RRC层连续收到了物理层上报的对 于SpCell的in-sync指示个数大于等于一个门限值(例如但不限于:radioFailRecoverThreshold),可选地,该门限值可以小于N311,大于等于1;则停止对应SpCell的T keep2定时器。
可选地,T keep2也可以是所有SpCell共用一个,即PCell和PSCell共用一个。如果这样规定,则启动、重启、停止T keep2定时器不需要特别说明为对应的SpCell停止。
实施例6
在本发明的实施例6中,如图6所示,用户设备UE执行的步骤包括:步骤601和步骤603。
在步骤601中,RRC层在连接态下收到底层上报的serving Cell的RRM测量值,进行层三滤波得到测量结果,测量结果可能包含RSRP,RSRQ,SINR等。
在步骤603中,如果SpCell的T keep2不在运行,则可能进一步判断RLM放松准则,如果T keep2在运行,则可以不用进一步判断RLM放松判断。可能的场景为如下一种或多种:
-可选地,如果T keep2没有在运行,则可以判断所有SpCell的RLM放松准则;如果放松准则满足,则配置底层对所有SpCell采用放松的RLM,否则采用正常RLM;
-可选地,如SpCell的T keep2没有在运行,则可以判断该SpCell的RLM放松准则;如果放松准则满足,则配置底层对该SpCell采用放松的RLM,否则采用正常RLM;
其中,放松RLM的准则包括但不限于:判断UE是否为低移动性,例如Serving cell的RSRP值变化值小于一定门限;或者判断UE是否在小区边缘,例如根据UE是否频繁发生切换。
其中,可选地,在配置底层采用放松的RLM还是正常的RLM之前,可以判断之前配置了底层采用RLM的方式(即放松的RLM还是正常的RLM),当RLM方式发生变化时候,再执行配置底层采用放松的RLM还是正常的RLM的操作,否则不用执行配置操作。
在步骤603中,还可以先对得到测量结果的SpCell进行RLM放松准则判断,当放松准则判断满足条件后,再判断T keep2的运行情况。如果T keep2 不在运行,则可以配置底层采用放松的RLM;否则,采用正常的RLM。具体的可选情况相同,不再赘述。
实施例7
在本发明的实施例7中,如图7所示,用户设备UE执行的步骤包括:步骤701和步骤703。
在步骤701,RRC层收到网络发送的放松RLM指示。
在步骤703,如果T keep2不在运行,则配置底层采用放松的RLM,如果T keep2在运行,则不用配置底层采用放松的RLM(即采用正常RLM)。可能的场景为如下一种或多种:
-可选地,如果SpCell的T keep2没有在运行,网络指示对该SpCell采用放松RLM,则配置底层对该SpCell采用放松的RLM,否则采用正常RLM;
-可选地,如果T keep2没有在运行,网络指示对SpCell采用放松RLM,则配置底层对所有SpCell采用放松的RLM,否则采用正常RLM;
其中,可选地,在配置底层采用放松的RLM还是正常的RLM之前,可以判断之前配置底层采用RLM的方式(即放松的RLM还是正常的RLM),当RLM方式发生变化时候,再执行配置底层采用放松的RLM还是正常的RLM的操作,否则不用执行配置操作。
[变形例]
下面,利用图8来说明作为一种变形例的可执行本发明上面所详细描述的用户设备执行的方法的用户设备。
图8是表示本发明所涉及的用户设备UE的框图。
如图8所示,该用户设备UE80包括处理器801和存储器802。处理器801例如可以包括微处理器、微控制器、嵌入式处理器等。存储器802例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器802上存储有程序指令。该指令在由处理器801运行时,可以执行本发明详细描述的由用户设备执行的上述方法。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统,可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如,单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器,也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路,也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下,本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外,本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例,但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备,如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上,已经参考附图对本发明的实施例进行了详细描述。但是,具体的结构并不局限于上述实施例,本发明也包括不偏离本发明主旨的任何设计改动。另外,可以在权利要求的范围内对本发明进行多种改动,通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外,上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备UE执行的方法,包括:
    在检测到针对服务小区的波束失败的情况下,媒质接入控制MAC实体将针对所述服务小区的波束失败信息指示给无线资源控制RRC层;以及
    在针对服务小区的波束失败恢复成功的情况下,所述MAC实体将针对所述服务小区的波束失败恢复信息指示给所述RRC层。
  2. 根据权利要求1所述的方法,其中,
    所述检测到针对服务小区的波束失败的情况包括以下情况的至少一种:
    所述MAC实体接收的物理层上报的针对所述服务小区的波束失败例指示的个数大于或等于波束失败例最大计数值;
    所述MAC实体接收的物理层上报的针对所述服务小区的波束失败例指示的个数大于或等于第一门限,所述第一门限小于所述波束失败例最大计数值;以及
    所述MAC实体接收到物理层上报的波束失败例指示。
  3. 根据权利要求1所述的方法,其中,
    所述针对服务小区的波束失败恢复成功的情况包括以下情况的至少一种:
    所述服务小区是特殊小区,并且针对所述特殊小区的波束失败恢复发起的随机接入过程成功;
    所述服务小区是辅小区,并且用于传输包含针对所述服务小区的波束失败恢复信息的波束失败恢复MAC控制元素或者截断的波束失败恢复MAC控制元素的混合自动请求重传HARQ进程,收到由小区无线网络临时标识C-RNTI加扰的物理下行控制信道PDCCH指示的用于新传的上行授权;以及
    所述服务小区是辅小区且所述辅小区被去激活。
  4. 根据权利要求1所述的方法,还包括:
    在所述RRC层收到由所述MAC实体指示的针对所述服务小区的所述波束失败信息的情况下,触发启动或重启针对所述服务小区的第一定时器;以及
    在所述RRC层收到由所述MAC实体指示的针对所述服务小区的所述 波束失败恢复信息的情况下,触发停止针对所述服务小区的所述第一定时器。
  5. 根据权利要求4所述的方法,还包括:
    所述RRC层在连接态下收到底层上报的针对所述服务小区的无线资源管理RRM测量值,进行层三滤波得到测量结果;以及
    在针对所述服务小区的所述第一定时器并未运行的情况下,根据所述测量结果来判断是否满足波束失败检测BFD放松准则。
  6. 根据权利要求4所述的方法,还包括:
    所述RRC层接收网络发送的波束失败检测BFD放松指示;以及
    在所述第一定时器并未运行的情况下,则配置底层采用放松的BFD。
  7. 一种由用户设备UE执行的方法,包括:
    当无线资源控制RRC层连续收到物理层上报的针对特殊小区的失步指示的个数大于或等于第一门限值时,触发启动针对所述特殊小区的第二定时器;以及
    当RRC层连续收到物理层上报的针对所述特殊小区的同步指示的个数大于或等于第二门限值时,停止针对所述特殊小区的所述第二定时器。
  8. 根据权利要求7所述的方法,还包括:
    所述RRC层在连接态下收到底层上报的针对服务小区的无线资源管理RRM测量值,进行层三滤波得到测量结果;以及
    在针对所述特殊小区的所述第二定时器并未运行的情况下,根据所述测量结果来判断是否满足无线链路监测RLM放松准则。
  9. 根据权利要求7所述的方法,还包括:
    所述RRC层接收网络发送的无线链路监测RLM放松指示;以及
    在所述第二定时器并未运行的情况下,则配置底层采用放松的RLM。
  10. 一种用户设备,包括:
    处理器;以及
    存储器,存储有指令,
    其中,所述指令在由所述处理器运行时执行根据权利要求1至9中的任一项所述的方法。
PCT/CN2021/133996 2020-12-01 2021-11-29 由用户设备执行的方法以及用户设备 WO2022116938A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011384607.6 2020-12-01
CN202011384607.6A CN114585008A (zh) 2020-12-01 2020-12-01 由用户设备执行的方法以及用户设备

Publications (1)

Publication Number Publication Date
WO2022116938A1 true WO2022116938A1 (zh) 2022-06-09

Family

ID=81768159

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/133996 WO2022116938A1 (zh) 2020-12-01 2021-11-29 由用户设备执行的方法以及用户设备

Country Status (2)

Country Link
CN (1) CN114585008A (zh)
WO (1) WO2022116938A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110062462A (zh) * 2018-01-19 2019-07-26 维沃移动通信有限公司 一种波束失败恢复方法及终端
CN110149179A (zh) * 2018-02-12 2019-08-20 维沃移动通信有限公司 一种波束失败恢复的方法和设备
CN111107593A (zh) * 2019-01-23 2020-05-05 维沃移动通信有限公司 一种用于链路失败恢复的方法、用户侧设备和网络侧设备
CN111436069A (zh) * 2019-01-11 2020-07-21 华硕电脑股份有限公司 无线通信中用于改进侧链路通信的调度模式的方法和设备
WO2020173915A1 (en) * 2019-02-25 2020-09-03 Nokia Technologies Oy Method for beam failure detection

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110062462A (zh) * 2018-01-19 2019-07-26 维沃移动通信有限公司 一种波束失败恢复方法及终端
CN110149179A (zh) * 2018-02-12 2019-08-20 维沃移动通信有限公司 一种波束失败恢复的方法和设备
CN111436069A (zh) * 2019-01-11 2020-07-21 华硕电脑股份有限公司 无线通信中用于改进侧链路通信的调度模式的方法和设备
CN111107593A (zh) * 2019-01-23 2020-05-05 维沃移动通信有限公司 一种用于链路失败恢复的方法、用户侧设备和网络侧设备
WO2020173915A1 (en) * 2019-02-25 2020-09-03 Nokia Technologies Oy Method for beam failure detection

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Discussions on UE power saving for RLM and BM", 3GPP DRAFT; R4-2016150, vol. RAN WG4, 23 October 2020 (2020-10-23), pages 1 - 4, XP051945037 *

Also Published As

Publication number Publication date
CN114585008A (zh) 2022-06-03

Similar Documents

Publication Publication Date Title
WO2021190608A1 (zh) 无线链路失败报告方法以及用户设备
CN110798867B (zh) 用户设备的控制方法以及用户设备
US9661510B2 (en) Failure event report extension for inter-RAT radio link failure
US20230022967A1 (en) Method for radio link failure recovery and user equipment
WO2020221193A1 (zh) 条件切换方法及对应的用户设备
WO2021057702A1 (zh) 无线链路失败恢复方法以及用户设备
WO2021227881A1 (zh) 无线链路失败恢复方法及对应的用户设备
WO2022012363A1 (zh) 切换信息报告方法及用户设备
WO2020192277A1 (zh) 一种多载波直通链路管理方法及终端
WO2021254197A1 (zh) 由用户设备执行的方法以及用户设备
WO2023125649A1 (zh) 连接建立失败报告方法和用户设备
WO2023134763A1 (zh) 信息报告方法以及用户设备
WO2023040955A1 (zh) 切换信息报告方法以及用户设备
WO2022116938A1 (zh) 由用户设备执行的方法以及用户设备
WO2022127730A1 (zh) 由用户设备执行的方法以及用户设备
WO2023284831A1 (zh) 执行无线链路监测的方法及用户设备
JP2023522738A (ja) 無線通信システムおよびユーザのための装置
WO2023246770A1 (zh) 由用户设备执行的方法以及用户设备
WO2024067624A1 (zh) 信息报告方法以及用户设备
WO2024094056A1 (zh) 信息报告方法以及用户设备
WO2023005967A1 (zh) 切换信息报告方法以及用户设备
WO2024017237A1 (zh) 由用户设备执行的方法以及用户设备
WO2024008076A1 (zh) 切换信息报告方法以及用户设备
WO2024027704A1 (zh) 切换信息报告方法以及用户设备
WO2023198145A1 (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: 21899970

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21899970

Country of ref document: EP

Kind code of ref document: A1