WO2022057783A1 - 无线链路失败报告方法以及用户设备 - Google Patents

无线链路失败报告方法以及用户设备 Download PDF

Info

Publication number
WO2022057783A1
WO2022057783A1 PCT/CN2021/118175 CN2021118175W WO2022057783A1 WO 2022057783 A1 WO2022057783 A1 WO 2022057783A1 CN 2021118175 W CN2021118175 W CN 2021118175W WO 2022057783 A1 WO2022057783 A1 WO 2022057783A1
Authority
WO
WIPO (PCT)
Prior art keywords
handover
rlf
link failure
cell
information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/118175
Other languages
English (en)
French (fr)
Inventor
常宁娟
刘仁茂
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
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 Sharp Corp filed Critical Sharp Corp
Priority to EP21868606.1A priority Critical patent/EP4216597A4/en
Priority to US18/026,142 priority patent/US12526715B2/en
Publication of WO2022057783A1 publication Critical patent/WO2022057783A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00833—Handover statistics

Definitions

  • the present disclosure relates to the technical field of wireless communication, and more particularly, to a recovery method after a wireless link failure and a corresponding user equipment.
  • network optimization can be used to optimize network performance.
  • data collection and data analysis are carried out on the existing deployed and running network to find out the reasons affecting the network quality, and the network performance can be improved by modifying the configured network parameters, adjusting the network structure and deployed devices.
  • Self-configuration and Self-Optimization Network it refers to the process of automatically adjusting the network based on the measurement/performance measurement of user equipment and/or base station.
  • the network side may configure the UE to perform measurements for SON.
  • the SON function includes many aspects, such as the automatic neighbor relationship function (ANR, Automatic Neighbour Relation Function) for reducing the operator's neighbor management burden, and the mobility load balancing function (MLB, Mobility Load) for balancing the responsibility between different cells. Balancing), Mobility Robustness Optimization (MRO) to optimize mobility performance, Random Access Channel Optimization to optimize random access channel parameters, and Radio Link Failure to optimize coverage and MRO reporting functions, etc.
  • ANR Automatic Neighbour Relation Function
  • MLB Mobility Load
  • Balancing Mobility Robustness Optimization
  • Random Access Channel Optimization to optimize random access channel parameters
  • Radio Link Failure to optimize coverage and MRO reporting functions
  • the present disclosure aims to realize the SON function under the new mobility mechanism in the NR system of Release 16, and further, proposes a solution on how to set the content of the radio link failure report in the CHO or DAPS scenario.
  • the purpose of the embodiments of the present disclosure is to realize the radio link failure reporting problem of CHO or DAPS under the new mobility mechanism in the NR system of Release 16. More specifically, the present disclosure proposes a solution to the problem of how to set relevant link failure information in a radio link failure report when a radio link failure occurs in a handover scenario where the CHO mechanism or the DAPS mechanism is implemented.
  • the embodiments of the present disclosure provide a radio link failure reporting method performed in a user equipment and a corresponding user equipment.
  • a radio link failure reporting method including: a user equipment UE detects that a radio link failure RLF occurs; the UE stores radio link failure information in the RLF report; the If the UE has performed a handover procedure before the RLF, the radio link failure information includes: information used to indicate the type of the handover procedure; the global cell identifier and the tracking area code of the cell where the latest handover command is received ; and the elapsed time since the most recent handover command was received.
  • the radio link failure information may be stored in a variable VarRLF-Report corresponding to the RLF report.
  • the UE may set a field in the RLF report, the field contains information used to indicate the type of handover procedure, and the RLF report contains the previousPCellId information element , the previousPCellId information element is set to the global cell identity and tracking area code of the cell where the most recent handover command is received, and the RLF report contains the timeConnFailure information element, and the timeConnFailure information element is set to be received from the latest handover command. time experienced.
  • the UE may receive a time threshold Th from the network side through an RRC message, and the time identified by the timeConnFailure information element is less than or equal to the time threshold
  • Th the UE includes information used to indicate the type of the handover process in the RLF report
  • Th the UE is not in the The RLF report contains information indicating the type of the handover procedure.
  • the information used to indicate the type of the handover procedure indicates that the type of the handover procedure may be: conditional handover CHO, dual activation protocol stack DAPS handover or traditional handover.
  • the radio link failure reporting method of the first aspect above when the information indicating the type of the handover procedure does not exist, it may be indicated that the type of the handover procedure is conventional handover.
  • the RLF report may further include: setting the failure cell identifier as the cell identifier of the cell that monitors the RLF; setting the connection failure type connectionFailureType information element to rlf; and Set the UE identifier C-RNTI to the C-RNTI used by the UE in the primary cell.
  • the information for indicating the type of the handover process is set to correspond to each command The corresponding value, if the handover process performed by the UE before the RLF is a CHO handover, the information used to indicate the type of the handover process is set to CHO handover, if the handover performed by the UE before the RLF.
  • the process is a DAPS handover
  • the information used to indicate the type of the handover process is set to DAPS handover
  • the handover process performed by the UE before the RLF is a conditional handover CHO for link recovery
  • the The information used to indicate the type of handover procedure is set to CHO link recovery.
  • the RLF may be a primary cell group MCG RLF or a secondary cell group SCG RLF
  • the handover process may be a synchronization reconfiguration process of the primary cell PCell or the primary and secondary cell PSCell synchronous reconfiguration process.
  • a user equipment comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform the radio link failure reporting according to the context method.
  • FIG. 1 is a sequence diagram showing that a user equipment UE in a connected state changes a serving cell through a handover procedure.
  • FIG. 2 is a schematic diagram showing a flow of condition switching.
  • FIG. 3 is a schematic diagram showing that the UE simultaneously maintains the activation protocol stacks for the source base station and the target base station during the DAPS handover process.
  • FIG. 4 is a schematic diagram showing the processing flow of the radio link failure reporting method in Embodiment 1 of the present disclosure.
  • FIG. 5 shows a block diagram of a user equipment UE according to the present disclosure.
  • LTE Long Term Evolution
  • NR New Radio
  • LTE system is also used to refer to 5G and later LTE systems (such as eLTE systems, or LTE systems that can be connected to the 5G core network) ), while LTE can be replaced with Evolved Universal Terrestrial Radio Access (Evolved Universal Terrestrial Radio Access, E-UTRA) or Evolved Universal Terrestrial Radio Access Network E-UTRAN.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • handover refers to the change of the primary cell initiated by the network side, including the change of the primary cell between the cells and the change of the primary cell within the cell, that is, the primary cell of the UE is changed from the source cell to the target cell, where the source cell
  • the target cell and the target cell may be the same cell or different cells, and in this process, the secret key or security algorithm used for access layer security may also be updated accordingly.
  • the source cell is also called the source base station, and can also be the source beam (beam), the source transmission point (TRP), the source master cell group (Master Cell Group, MCG), and the target cell may also be called the target base station, or is the target beam, the target transmission point, or the target MCG.
  • the source cell refers to a connected cell serving the UE before the handover process is initiated, that is, a cell from which the UE receives an RRC message including a handover command.
  • the target cell refers to the cell that the UE is connected to serving the UE after the handover process is successfully completed, or the cell indicated by the target cell identifier included in the handover command, and the cell that the UE accesses when receiving the handover.
  • the present disclosure can also be applied to the change of the primary secondary cell (PSCell) under the dual connectivity (Dual Connectivity, DC) configuration.
  • the handover refers to the change of the PSCell
  • the source cell refers to the source PSCell.
  • the handover command described in the present disclosure is used to trigger the UE to perform handover, and in the NR system, it is an RRC reconfiguration message including a synchronous reconfiguration (Reconfigurationwithsync) information element. Further, for the handover of the master cell, it is an RRC reconfiguration message including a synchronization reconfiguration (Reconfigurationwithsync) information element for a master cell group (Master Cell Group, MCG). At this time, the handover may also be referred to as synchronous reconfiguration of the MCG.
  • the synchronization reconfiguration information element or the mobility control information element includes the configuration information of the target cell, such as the target cell identity, the frequency of the target cell, the public configuration of the target cell such as system information, and the random number used by the UE to access the target cell. Access configuration, security parameter configuration of the UE in the target cell, radio bearer configuration of the UE in the target cell, etc.
  • the RRC reconfiguration message and the RRC connection reconfiguration message are equivalent; similarly, the response message RRC reconfiguration complete message and the RRC connection reconfiguration complete message are equivalent.
  • the handover command is equivalent to the RRC message containing the handover command, and refers to the RRC message or the configuration in the RRC message that triggers the UE to perform handover.
  • Switch configuration refers to all or part of the configuration in the switch command. Cancel, Release, Delete, Empty, and Clear can be replaced. Execution, use and application are interchangeable. Configuration and reconfiguration can be replaced. Links and connections can be replaced. Monitor and detect can be replaced.
  • FIG. 1 is a sequence diagram showing that a user equipment UE in a connected state changes a serving cell through a handover procedure.
  • the handover process generally includes the following stages:
  • Phase 1 Measurement Phase.
  • the base station sends a measurement configuration to the user equipment (User Equipment, UE); the UE measures the radio link corresponding to the serving cell or the neighboring cell based on the measurement configuration, and when the configured measurement reporting conditions are met, the UE sends the measurement to the base station. Report.
  • the measurement phase is not necessary, and the base station can also blindly switch the UE when there is no valid measurement report.
  • Stage 2 Handover preparation stage.
  • the base station decides whether to trigger a handover for the UE according to the received measurement report and other factors such as the load of the base station. If it is determined that a handover is triggered for the UE, the source base station initiates a handover preparation process by sending a handover request message to the target base station.
  • the target base station decides whether to accept the handover request to the UE according to factors such as the context of the UE in the handover request message and the available resources of the target base station.
  • the inter-node RRC message is the handover command.
  • Phase 3 Switch execution phase.
  • the source base station sends the handover command to the UE, and starts to forward the data of the UE to the target base station.
  • the UE that receives the handover command immediately applies the configuration of the handover command to perform handover, accesses the target base station through a random access procedure, and sends an acknowledgement message to the target base station. Among them, the random access process is not necessary.
  • Stage 4 Handover completion stage. After confirming that the UE has successfully accessed, the target base station sends a handover complete message to the source base station. Accordingly, the source base station can release the UE context saved on it.
  • the UE detects the handover process through a timer T304.
  • the UE starts the T304 timer; when the handover process is completed, the UE stops the timer T304; when the T304 times out, the UE considers that the handover fails.
  • condition-based handover is briefly described. As mentioned above, in the technical requirements of Release 16, it is required to meet the "0ms" data interruption delay as much as possible in the process of mobile handover, and to improve the robustness of handover to meet the mobility requirements of seamless handover in NR. In the current handover process, one of the reasons that the handover fails and the data transmission is interrupted for a long time is that the handover command fails to be received due to the handover command not being issued in time. For this problem, a feasible method is condition-based handover (referred to as conditional handover).
  • FIG. 2 is a schematic diagram showing a flow of condition switching.
  • a relatively conservative measurement report threshold is set, so that the base station obtains the measurement result in advance, and performs handover preparation in advance according to the measurement result and the selected target base station, so that the base station can be under the real handover condition (relative to the conservative Before the measurement report threshold) is satisfied, the handover command including the handover candidate cell and the handover execution condition is delivered to the UE in advance, which carries the condition for the UE to execute the handover.
  • the UE After the UE receives the conditional handover command, it does not perform handover immediately, but saves the received handover command configuration, and starts monitoring the chain of the source cell according to the handover execution condition carried in the handover command message.
  • a conditional handover refers to a handover procedure that is performed only when one or more of the configured handover execution conditions are satisfied.
  • the handover execution condition is a measurement event, such as the condition is the conditional reconfiguration measurement event A3 (the signal quality of the neighbor cell is better than the serving cell by an offset for a continuous period of time).
  • the neighbor cell corresponds to the handover target cell.
  • conditional handover command can be included in the conditional handover command as handover execution conditions. Because the handover command is included in the RRC reconfiguration message, the conditional handover CHO is also called conditional reconfiguration.
  • the UE will generate and save a radio link failure report (RLF report) when a radio link failure (Radio Link Failure, RLF) or handover failure (Handover Failure, HOF) occurs. , and save the radio link failure information in the UE variable VarRLF-Report.
  • RLF report radio link failure report
  • the UE can inform the network side that there is an available radio link failure report (rlf-InfoAvailable information) through an RRC message. element to indicate).
  • the UE can complete the RRC connection establishment in the RRC connection re-establishment complete message (RRCConnectionReestablishmentComplete) in the RRC connection re-establishment process, in the RRC connection re-configuration complete message (RRCConnectionReconfigurationComplete) in the RRC connection re-configuration process, and in the RRC connection establishment process.
  • the message (RRCConnectionSetupComplete) or the RRC connection recovery complete message (RRCConnectionResumeComplete) in the RRC connection recovery process informs the network side that the UE has a saved available radio link failure report.
  • the network side may request the UE to report the saved radio link failure report through an RRC message (the rlf-ReportReq information element in the UEInformationRequest message indicates the request).
  • the UE will report the stored radio link failure report (the rlf-Report information element in the UEInformationResponse message) to the network side in the response RRC message.
  • the radio link failure report obtained by the network side is used for network optimization, such as network coverage and mobility robustness optimization.
  • the radio link failure report may include: measurement results of the source cell and neighbor cells available when the link fails, location information, ID of the primary cell where the link failure occurred, link failure type (RLF or HOF), RLF reason, slave
  • the time from connection failure to reporting the radio link failure the time from the last handover command received to the connection failure (denoted as timeConnFailure information element), the cell identity of the UE re-accessing the network, that is, the RRC re-establishment cell identity, etc.
  • Radio link recovery mechanism using saved conditional handover configuration
  • the UE After the conditional handover is configured, the UE does not perform the handover immediately, but performs the handover according to the received and saved conditional handover configuration after the corresponding condition is satisfied. During the period from the moment when the UE receives the conditional handover configuration to the period from when the handover is performed according to the received conditional handover configuration, the UE still maintains communication with the source base station. During this time, a radio link failure (Radio Link Failure, RLF) between the UE and the source base station may occur.
  • RLF Radio Link Failure
  • a link recovery enhancement mechanism is introduced in the NR or LTE system of Release 16: when RLF or HOF occurs, the UE selects a cell to perform the cell selection process (that is, when the T311 timer is running) during the RRC connection re-establishment process.
  • Link recovery if the UE is configured with an enable instruction that can execute CHO after link failure, and the cell selection process is due to monitoring MCG RLF or MCG handover failure (ie, synchronization reconfiguration failure in the NR system) And the selected cell is a conditional handover candidate cell (the synchronization reconfiguration information element reconfigurationWithSync corresponding to the cell is included in the MasterCellGroup information element in the saved conditional reconfiguration variable), then the UE switches according to the condition corresponding to the cell The configuration performs handover to this cell; otherwise, the UE attempts to restore the connection with the network side by sending an RRC connection establishment request to the selected cell.
  • This enhancement of the link recovery mechanism is referred to in the present disclosure as a link failure recovery mechanism based on a conditional switching configuration (for convenience of description, it is simply referred to as a conditional switching link recovery mechanism).
  • the network side enables this function of the UE by setting the CHO recovery information element (referred to as the attemptCondReconfig information element) in the CHO configuration to true, indicating that after the UE fails, if the selected cell is a target candidate cell and fails After the first cell selection, the UE needs to perform a conditional handover to restore the link.
  • the UE can perform CHO to the cell.
  • the conditional handover candidate cell refers to the (target) cell in the conditional handover configuration in the RRC message for configuring the conditional handover received by the UE, that is, in the synchronization reconfiguration information element (ReconfigurationWithSync) or the mobility control information element (MobilityControlInfo)
  • the cell identified by the cell ID The network side can simultaneously configure one or more candidate cells for handover execution conditions for the UE.
  • the UE after receiving the handover command, the UE does not cut off the link (data transmission) with the source base station during the handover process of accessing to the target base station, but can At the same time, the connection and data transmission with the target base station and the source base station are maintained, so as to avoid the delay caused by the interruption of the service caused by disconnecting the connection with the source base station before accessing the target base station during the handover process.
  • DAPS handover refers to such a handover process. After receiving the RRC message for handover, the UE still maintains the connection with the source base station until the source base station is released after successfully executing the random access procedure to the target.
  • the UE continues to receive downlink data from the source base station until the source base station is released, and the user continues to send uplink data to the source base station until the random access procedure to the target base station is successfully completed.
  • the MAC layer instructs the upper layer that the random access process is complete, and after receiving the instruction, the RRC layer instructs the lower layer (such as the PDCP layer) to perform uplink data change, and change the uplink path from the source base station. is the target base station.
  • the UE After receiving the handover command, the UE establishes a MAC entity for the target base station. If a DRB is configured as a DAPS bearer, it establishes an RLC entity and dedicated service information (Dedicated service information) associated with the target base station for the DRB. Traffic Channel, DTCH) logical channel, and the PDCP entity associated with the DAPS bearer is reconfigured as a DAPS PDCP entity, and the DAPS PDCP entity exists in the PDCP entity at the same time as the security and robustness associated with the source base station and the target base station.
  • a DRB is configured as a DAPS bearer, it establishes an RLC entity and dedicated service information (Dedicated service information) associated with the target base station for the DRB. Traffic Channel, DTCH) logical channel, and the PDCP entity associated with the DAPS bearer is reconfigured as a DAPS PDCP entity, and the DAPS PDCP entity exists in the PDCP entity at the same time as the security and robustness associated with the source
  • ROHC RObust Header Compression
  • the UE When the DAPS handover fails, that is, the T304 timer used to monitor the handover process expires, and if no radio link failure is detected on the source base station, the UE returns to the connection with the source base station, and reports the DAPS handover failure through the source base station instead of It will trigger the RRC connection re-establishment process. Otherwise, if a radio link failure is detected or has occurred on the source base station, the UE restores the link with the network by initiating an RRC connection re-establishment procedure.
  • too late handover generally because the handover command is issued too late, and the UE does not receive the handover command in time, which occurs in the RLF of the source cell; Too early handover is generally caused by too conservative handover-related parameter settings, so that the UE performs the handover before reaching the handover area, which may occur in the HOF during the handover process or shortly after the successful handover to the target cell.
  • RLF occurred in between; handover to the wrong cell is due to the unreasonable handover parameter settings of different cells, resulting in the wrong selection of the target cell of the UE, so that the UE may be successfully handed over to the target cell for a short time. After that, RLF occurs, and in a subsequent link recovery process such as an RRC re-establishment process, a cell different from the target cell is selected to perform RRC re-establishment.
  • new handover mechanisms such as CHO and DAPS are introduced.
  • the handover parameter configurations used in these new handover mechanisms can be configured differently from the corresponding parameters in the traditional handover mechanism, that is, it can be considered that different handover mechanisms ( scene) each has a set of switching related parameters. Therefore, when optimizing the mobility performance parameters on the network side, different handover mechanisms (scenarios) need to be distinguished, and the handover performance assistance information (such as RLF report) obtained from the UE under different handover mechanisms (scenarios) is separately counted. Different statistical data evaluates and adjusts the handover-related parameters corresponding to the corresponding handover mechanism (scenario), making network optimization more refined.
  • the UE performs a handover procedure from cell A to cell B.
  • an RLF in cell B occurs, and the UE sets and saves the relevant information of this RLF, that is, an RLF report.
  • the UE after the RLF restores the link connection with the network side through RRC connection re-establishment or RRC connection establishment or other methods.
  • the UE will indicate to the network side that there are RLF reports available on it.
  • the network side sends an RLF report request to the UE through an RRC message, so as to request the UE to report the saved RLF report.
  • the UE sends the saved RLF report to the network side based on the request.
  • the network side can determine that the RLF is actually the previous handover from cell A to cell B is unreasonable (such as premature handover or handover to the wrong cell), so the difference between cell A and cell B is affected.
  • the switching related parameters can be adjusted.
  • the network side decides when to obtain the saved RLF report from the UE. Therefore, in one case, when the network side (such as cell A or cell B) obtains the RLF report, the network side may have discarded the UE context information. According to the existing mechanism in the RLF According to the reported information, the network side cannot know what kind of handover process (such as traditional handover, CHO or DAPS) the previous handover associated with the RLF report is, which may lead to wrong handover parameter adjustment.
  • the network side cannot know what kind of handover process (such as traditional handover, CHO or DAPS) the previous handover associated with the RLF report is, which may lead to wrong handover parameter adjustment.
  • Example 1 of the present disclosure provides a method for the UE to report an RLF report to the network.
  • the UE detects that an RLF occurs, when the UE saves the RLF report in the RLF report (VarRLF-Rreport variable), it can set the RLF report in the following manner.
  • FIG. 4 is a schematic diagram showing the processing flow of the radio link failure reporting method in Embodiment 1 of the present disclosure.
  • the UE detects that RLF occurs. Preferably, it refers to the RLF of MCG.
  • the UE considers that the RLF is detected, including the following situations:
  • Case 1 The timer T310 used for wireless link failure monitoring times out;
  • Case 3 The random access problem indication from the MAC layer is received and the timers T300, T301, T304, T311 and T319 are not running; these timers are used to monitor the RRC connection establishment process, RRC connection re-establishment process, Handover process, cell reselection process in RRC re-establishment process and RRC connection recovery process.
  • the UE saves the radio link failure information in the RLF report.
  • the UE may store the radio link failure information in the variable VarRLF-Report corresponding to the RLF report.
  • the wireless link failure information can be set as follows, for example.
  • the UE has performed a handover procedure before this RLF, set a field containing information used to indicate the type (scenario) of the handover procedure; at the same time, include the previousPCellId information element and set it as the latest handover command
  • the global cell identity and tracking area code of the (primary) cell where the receiver is located; the timeConnFailure information element containing the timeConnFailure is set to the elapsed time since the most recent handover command was received.
  • the UE has performed a handover process before the RLF this time. It can also be further described as, if a handover command (such as an RRC reconfiguration message including a synchronization reconfiguration information element) is received before the connection failure (RLF) ), if the most recently received handover command was for an NR intra-NR handover.
  • a handover command such as an RRC reconfiguration message including a synchronization reconfiguration information element
  • RLF connection failure
  • the description of receiving (receiving) the handover command also includes executing the CHO command in the CHO scenario.
  • the information for indicating the type of the handover procedure may indicate that the type of the handover procedure is CHO, DAPS handover or traditional handover.
  • the information indicating the type of the handover procedure does not exist, it is considered that the corresponding handover procedure is a conventional handover, that is, not a CHO or DAPS handover.
  • the handover procedure performed by the UE before this RLF is a CHO
  • the information used to indicate the type of the handover procedure is set to CHO (conditional reconfiguration).
  • the received handover command is equivalent to the executed CHO command (conditional reconfiguration).
  • the handover procedure performed by the UE before this RLF is a DAPS handover
  • the information used to indicate the type of the handover procedure is set as DAPS handover.
  • the received handover command is equivalent to the received handover command, and any data radio bearer DRB configured as a DAPS bearer exists in the configuration in the handover command.
  • the handover procedure type may also be used to indicate that the handover procedure is a conditional handover for link recovery. That is, the handover process is a handover process performed when the cell selected in the cell selection process after a link failure is a conditional candidate cell, or the handover process is described as a conditional handover link recovery mechanism performed.
  • the UE does not always include the above-mentioned information indicating the handover procedure type in the RLF report, but only includes the above-mentioned handover indication handover procedure type information in the RLF report when a condition is satisfied.
  • the UE receives a time threshold configuration Th from the network side through an RRC message such as an RRC connection reconfiguration message, and the UE determines that the time indicated by the timeConnFailure information element is less than or equal to Th, the UE only includes the above indication in the RLF report Information on the type of switching process.
  • the UE determines that when the time identified by the timeConnFailure information element is greater than or greater than or equal to Th, the UE does not include the above-mentioned information indicating the type of the handover process in the RLF report. That is to say, the UE determines to include the handover procedure type information in the RLF report only when the RLF may be related to the handover procedure performed recently.
  • the threshold value Th is a predefined fixed value such as 1s.
  • the UE also includes the following contents in the RLFreport.
  • the cell identity is set to the global cell identity and tracking area code; otherwise, the cell identity is set to the cell Corresponding physical cell identity and carrier frequency.
  • connection failureType information element Set the connection failure type connectionFailureType information element to rlf.
  • the network side can obtain the handover type experienced by the UE before the RLF failure, thereby realizing more accurate adjustment and setting of mobility parameters.
  • the handover fails (T304 times out)
  • the handover is a DAPS handover, that is, the UE is configured with a DAPS bearer
  • the RRC re-establishment process is not immediately performed, but whether the source primary cell PCell detects
  • the UE will release the configuration related to the target cell and fall back to the source PCell.
  • the UE sends a failure information message to the source PCell by initiating a failure information process to report the current DAPS handover failure to the network side and falls back to the source cell.
  • the network side can only learn that a DAPS handover failure has occurred in the UE, but cannot obtain other failure information.
  • the network side can obtain more handover failure information by carrying the following failure information in the failure information message, so as to carry out More accurate network parameter optimization.
  • the failure information includes: the information of the random access process in the DAPS handover process: the measurement results of the handover source PCell and neighboring cells.
  • the setting of the information of the random access process includes:
  • the locationAndBandwidth information element and the subcarrierspacing information element are set to be associated with corresponding information of an uplink bandwidth part (BandWidth Part, BWP) of the random access resource.
  • BWP uplink bandwidth part
  • the msg1-FrequencyStart, msg1-FDM and msg1-sbcarrierSpacing information elements are set to indicate the frequency domain information where the preamble used by the contention-based random access resource is located.
  • the msg1-FrequencyStartCFRA, msg1-FDMCFRA, and msg1-sbcarrierSpacingCFRA information elements are set to indicate the frequency domain information where the preamble used by the contention free random access resource is located.
  • the information in the perRAinfoList information element of the random access attempt list is set according to the chronological order of each random access attempt:
  • the random access resource used is associated with a synchronous physical broadcast channel block (SS/PBCH), set the ssb-index information element to contain the index value of the synchronous physical broadcast channel block associated with the random access resource; set the numberOfPreambleSentOnSSB information element to indicate the number of consecutive random access attempts associated with the synchronous physical broadcast channel block; for each random access attempt, if it occurs on a contention-based random access resource and the random access procedure is not intended for Requests for other system information (that is, the raPurpose information element is not requestForOtherSI), if the contention resolution of the sent preamble is unsuccessful, set the contentionDetected information element to true, otherwise set it to false; if the random access attempt is based on For competing random access resources, if the reference signal received power RSRP of the synchronous physical broadcast information block is higher than a configured threshold rsrp-ThresholdSSB, the UE sets the dlRSRPAboveThreshold information element to be false, otherwise,
  • the random access resource used is associated with a channel state indication reference signal (CSI-RS)
  • CSI-RS channel state indication reference signal
  • set the csi-RS-index information element to include the index value of the CSI-RS associated with the random access resource
  • set numberOfPreambleSentOn CSI-RS RS information element to indicate the number of consecutive random access attempts associated with the CSI-RS.
  • the measurement results of the handover source PCell and neighboring cells include:
  • the measResultListNR information element in the measResultNeighCells information element to include the measured quantities of all available synchronized physical broadcast channel blocks SS-PBCH of the best measuring cell except the source PCell (reference signal received power RSRP or reference signal received quality RSRQ or signal interference noise ratio SINR).
  • the measResultListNR information element in the measResultNeighCells information element to include all available channel state indication reference signal CSI-RS measurements of the best measurement cell except the source PCell (reference signal received power RSRP or reference signal received quality RSRQ or signal interference noise ratio SINR).
  • FIG. 5 is a block diagram showing a user equipment UE according to the present invention.
  • the user equipment UE50 includes a processor 501 and a memory 502 .
  • the processor 501 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
  • the memory 502 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.
  • the memory 502 has program instructions stored thereon. When the instruction is executed by the processor 501, various methods such as the above-mentioned wireless link failure reporting method and wireless link failure setting method described in detail in the present invention can be executed.
  • base station refers to a mobile communication data and control switching center with larger transmit power and wider coverage area, including functions such as resource allocation and scheduling, data reception and transmission, and the like.
  • User equipment refers to a user's mobile terminal, for example, including a mobile phone, a notebook, and other terminal equipment that can wirelessly communicate with a base station or a micro base station.
  • the method and related apparatus of the present disclosure have been described above in conjunction with the preferred embodiments. Those skilled in the art will understand that the methods shown above are only exemplary. The methods of the present disclosure are not limited to the steps and sequences shown above.
  • the base station and user equipment shown above may include more modules, for example, may also include modules that can be developed or developed in the future and that can be used for the base station, MME, or UE, and so on.
  • the various identifiers shown above are only exemplary and not restrictive, and the present disclosure is not limited to the specific information elements exemplified by these identifiers. Numerous changes and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments.
  • the program running on the device may be a program that causes a computer to implement the functions of the embodiments of the present disclosure 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 disclosure 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.
  • Circuitry 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. In the event that new integrated circuit technologies emerge as a result of advances in semiconductor technology to replace existing integrated circuits, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

Landscapes

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

Abstract

本公开提供了一种无线链路失败报告方法以及用户设备。所述无线链路失败报告方法，包括：用户设备UE监测到发生了无线链路失败RLF；所述UE在RLF报告中保存无线链路失败信息；所述UE在所述RLF之前执行过一个切换过程的情况下，所述无线链路失败信息包含：用于指示切换过程的类型的信息；最近的切换命令接收所在的小区的全球小区标识和跟踪区域码；以及从接收到最近的切换命令开始所经历的时间。

Description

无线链路失败报告方法以及用户设备 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及无线链路失败后的恢复方法以及对应的用户设备。
背景技术
无线网络中通过网络优化可以达到优化网络性能的目的。一般对现有已部署和运行的网络进行数据采集和数据分析等手段，找出影响网络质量的原因，并且通过修改所配置的网络参数、调整网络结构和部署的设备等手段来提升网络性能。对于自配置和自优化网络(Self-configuration and Self-Optimization Network，SON)，指的是基于用户设备和/或基站的测量/性能测量来自动调节网络的过程。网络侧可以配置UE执行用于SON的测量。SON功能包含很多方面，如用于降低运行商的邻区管理负担的自动邻区关系功能(ANR，Automatic Neighbour Relation Function)、用于均衡不同小区之间负责的移动负载均衡功能(MLB，Mobility Load Balancing)，用于优化移动性能的移动鲁棒性优化功能(MRO，Mobility Robustness Optimization)、用于优化随机接入信道参数的随机接入信道优化功能和用于优化覆盖以及MRO的无线链路失败报告功能等。
2019年4月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#86次全会上批准了一个5G技术标准的新的研究项目(参见非专利文献：RP-193255：New WID on enhancement of data collection for SON/MDT in NR)。其研究目的之一在版本16的NR系统在新的接入或移动机制如条件切换(Conditional Handover，CHO) 和双激活协议栈(Dual Active Protocol Stack，DAPS)切换下实现SON的功能。
本公开旨在实现在版本16的NR系统中新的移动机制下的SON功能，更进一步地，就如何设置在CHO或DAPS场景下的无线链路失败报告内容的提出解决方法。
发明内容
本公开实施例的目的在于在实现在版本16的NR系统中新的移动机制下CHO或DAPS的无线链路失败上报问题。更具体地，本公开针对在执行了CHO机制或DAPS机制的切换场景下发生无线链路失败时如何在无线链路失败报告中设置相关的链路失败信息的问题提出了解决方法。本公开实施例提供了在用户设备中执行的无线链路失败报告方法以及相应的用户设备。
根据本公开的第一方面，提出了一种无线链路失败报告方法，包括：用户设备UE监测到发生了无线链路失败RLF；所述UE在RLF报告中保存无线链路失败信息；所述UE在所述RLF之前执行过一个切换过程的情况下，所述无线链路失败信息包含：用于指示切换过程的类型的信息；最近的切换命令接收所在的小区的全球小区标识和跟踪区域码；以及从接收到最近的切换命令开始所经历的时间。
在上述第一方面的无线链路失败报告方法中，可以在所述RLF报告对应的变量VarRLF-Report中保存所述无线链路失败信息。
在上述第一方面的无线链路失败报告方法中，所述UE可以在所述RLF报告中设置一个域，所述域包含用于指示切换过程的类型的信息，所述RLF报告包含previousPCellId信息元素，所述previousPCellId信息元素设置为最近的切换命令接收所在的小区的全球小区标识和跟踪区域码，所述RLF报告包含timeConnFailure信息元素，所述timeConnFailure信息元素设置为从接收到最近的切换命令开始所经历的时间。
在上述第一方面的无线链路失败报告方法中，所述UE可以通过 RRC消息从网络侧接收时间门限值Th，在所述timeConnFailure信息元素所标识的时间小于或等于所述时间门限值Th时，所述UE在所述RLF报告中包含用于指示所述切换过程的类型的信息，在所述timeConnFailure信息元素所标识的时间大于所述时间门限值Th时，所述UE不在所述RLF报告中包含用于指示所述切换过程的类型的信息。
在上述第一方面的无线链路失败报告方法中，所述用于指示切换过程的类型的信息指示切换过程的类型可以为：条件切换CHO、双激活协议栈DAPS切换或者传统切换。
在上述第一方面的无线链路失败报告方法中，在所述指示切换过程的类型的信息不存在时，可以表示切换过程的类型是传统切换。
在上述第一方面的无线链路失败报告方法中，所述RLF报告中还可以包含：设置失败小区标识为监测到所述RLF的小区的小区标识；设置连接失败类型connectionFailureType信息元素为rlf；以及设置UE标识C-RNTI为UE在主小区所使用的C-RNTI。
在上述第一方面的无线链路失败报告方法中，在切换命令是CHO切换命令、DAPS切换命令或CHO链路恢复命令时，所述用于指示切换过程的类型的信息被设置为与各个命令对应的值，若所述UE在所述RLF之前执行的切换过程是一个CHO切换时，所述用于指示切换过程类型的信息设置为CHO切换，若所述UE在所述RLF之前执行的切换过程是一个DAPS切换时，所述用于指示切换过程类型的信息设置为DAPS切换，若所述UE在所述RLF之前执行的切换过程是一个用于链路恢复的条件切换CHO时，所述用于指示切换过程类型的信息设置为CHO链路恢复。
在上述第一方面的无线链路失败报告方法中，所述RLF可以是主小区组MCG RLF或辅小区组SCG RLF，所述切换过程可以是主小区PCell的同步重配置过程或主辅小区PSCell的同步重配置过程。
根据本公开的第二方面，提供一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行 根据上下文所述的无线链路失败报告方法。
附图说明
为了更完整地理解本公开及其优势，现在将参考结合附图的以下描述，其中：
图1是表示连接态的用户设备UE通过切换过程来变更服务小区的顺序图。
图2是表示条件切换的流程的示意图。
图3是表示UE在DAPS切换过程中同时维护对于源基站和目标基站的激活协议栈的示意图。
图4是表示本公开实施例1中的无线链路失败报告方法的处理流程的示意图。
图5表示本公开所涉及的用户设备UE的框图。
在附图中，相同或相似的结构均以相同或相似的附图标记进行标识。
具体实施方式
根据结合附图对本公开示例性实施例的以下详细描述，本公开的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。
在本公开中，术语“包括”和“含有”及其派生词意为包括而非限制；术语“或”是包含性的，意为和/或。
在本说明书中，下述用于描述本公开原理的各种实施例只是说明，不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本公开的示例性实施例。下述描述包括多种具体细节来帮助理解，但这些细节应认为仅仅是示例性的。因此，本领域普通技术人员应认识到，在不背离本公开的范围和精神的情况下，可以对本文中描述的实施例进行多种改变和修改。此外，为了清楚和简洁起见，省略了公知功能和结构的描述。此外，贯穿附图，相同参考数字用于相似功能和操作。
下文以长期演进系统(Long Term Evolution，LTE)/NR移动通信系统及其后续的演进版本作为示例应用环境，具体描述了根据本公开的多个实施方式。然而，需要指出的是，本公开不限于以下实施方式，而是可适用于更多其它的无线通信系统。若无特殊说明，在本公开中，小区和基站的概念可以互相替换；LTE系统也用于指代5G及其之后的LTE系统(如称为eLTE系统，或者可以连接到5G核心网的LTE系统)，同时LTE可以用演进的通用陆地无线接入(Evolved Universal Terrestrial Radio Access，E-UTRA)或演进的通用陆地无线接入网E-UTRAN来替换。在本公开中，切换指的是网络侧发起的主小区的变更，包含小区间的主小区变更也包含小区内的主小区变更，即UE的主小区从源小区变更为目标小区，其中源小区和目标小区可以是同一个小区也可以是不同的小区，在此过程中，用于接入层安全的秘钥或安全算法也可随之更新。源小区也称为源基站，也可以是源光束(beam)、源传输点(Transmission point，TRP)，源主小区组(Master Cell Group，MCG)，目标小区也可称为目标基站，也可以是目标光束、目标传输点或目标MCG。源小区指的是切换过程发起之前所连接的为UE服务的小区即UE从之接收包含切换命令的RRC消息的小区。目标小区指的是切换过程成功完成之后UE所连接的为UE服务的小区，或者说是切换命令中所包含的目标小区标识所指示的小区、UE收到执行切换时所接入的小区。但实际上，本公开也可以应用于双连接(Dual Connectivity，DC)配置下的主辅小区(Primary Secondary Cell，PSCell)变更，此时，切换指的是PSCell变更，源小区指的是源PSCell或源辅小区组(Secondary Cell Group，SCG)，目标小区指的是目标PSCell或目标SCG。本公开所述切换命令用于触发UE执行切换，在NR系统中是包含同步重配置(Reconfigurationwithsync)信息元素的RRC重配置消息。更进一步地，对于主小区的切换，是包含用于主小区组(Master Cell Group，MCG)的同步重配置(Reconfigurationwithsync)信息元素的RRC重配置消息。此时，切换也可称为MCG的同步重配置。在LTE系统中是包含移动控制信息(MobilityControlInformation) 信息元素的RRC连接重配置消息。其中，所述同步重配置信息元素或移动控制信息信息元素包含目标小区的配置信息，例如目标小区标识、目标小区频率、目标小区的公共配置如系统信息、UE接入到目标小区所使用的随机接入配置、UE在目标小区的安全参数配置、UE在目标小区的无线承载配置等。为便于描述，本公开中RRC重配置消息和RRC连接重配置消息等同；同理，其响应消息RRC重配置完成消息和RRC连接重配置完成消息等同。切换命令和包含切换命令的RRC消息等同，指触发UE执行切换的RRC消息或RRC消息中的配置。切换配置指切换命令中的全部或部分配置。取消、释放、删除、清空和清除等可以替换。执行、使用和应用可替换。配置和重配置可以替换。链路和连接可以替换。监测(monitor)和检测(detect)可替换。
下述先简要描述本公开实施例所涉及到的在先技术。
现有机制中的一般切换过程：
连接态的用户移动性主要通过切换过程来实现，所述切换即指的是处于无线资源控制(Radio Resource Control，RRC)连接态的UE变更服务小区的过程。图1是表示连接态的用户设备UE通过切换过程来变更服务小区的顺序图。如图1所示，切换过程一般包括如下阶段：
阶段1：测量阶段。基站向用户设备(User Equipment，UE)下发测量配置；UE基于该测量配置对服务小区或邻小区所对应的无线链路进行测量，当满足所配置的测量上报条件时，UE向基站发送测量报告。测量阶段不是必须的，在基站在没有有效测量报告的时候也可以盲切换UE。
阶段2：切换准备阶段。基站结合收到的测量报告以及其他因素如基站负载等决定是否为该UE触发切换。若确定对该UE触发切换，则源基站通过向目标基站发送切换请求消息来发起切换准备过程。目标基站根据切换请求消息中UE的上下文和目标基站的可用资源等因素决定是否接受对该UE的本次切换请求，如果可以，则向源基站回 复切换确认消息，其中切换确认消息中包含一条基站间(inter-node)的RRC消息即切换命令。
阶段3：切换执行阶段。源基站将切换命令下发给UE，并开始将该UE的数据转发给目标基站。收到切换命令的UE立即应用该切换命令的配置执行切换，通过随机接入过程接入到目标基站，向目标基站发送确认消息。其中，随机接入过程不是必须的。
阶段4：切换完成阶段。目标基站确认UE成功接入后，向源基站发送切换完成消息。源基站据此可以释放其上所保存的UE上下文。
UE通过一个定时器T304来检测切换过程，当切换过程发起时，UE开启T304定时器；当切换过程完成时，UE停止定时器T304；当T304超时，UE认为切换失败。
基于条件的切换：
其次简述基于条件的切换。如前所述在Release 16技术需求中，要求在移动切换过程中尽可能满足“0ms”的数据中断时延，并提高切换的鲁棒性以达到NR中的无缝切换的移动性需求。在当前的切换过程中，一种导致切换失败而造成较长时间数据传输中断的原因是切换命令下发的不及时导致的切换命令接收失败。对于该问题，一种可行的方法是基于条件的切换(简称之条件切换)。图2是表示条件切换的流程的示意图。在条件切换中，设置相对保守的测量报告门限，使得基站提前获取测量结果，并根据测量结果和选定的目标基站提前执行切换准备，这样基站可以在真正的切换条件(相对于所述保守的测量报告门限)满足之前，提前将包含切换候选小区和切换执行条件的切换命令下发给UE，其中携带UE执行切换的条件。不同于现有切换机制，UE收到条件切换命令后，并不会立即执行切换，而是保存所接收到的切换命令配置，并根据切换命令消息中携带的切换执行条件开始监测源小区的链路质量或目标小区的链路质量以评估切换执行条件是否满足。只有当监测到所配置的切换执行条件满足时，UE才开始执行所保存的切换命令，接入到目标小区。总言之，条件切换是指只有当所配置的一个或多个切换执行条件满足时才执行的切换过程。 对于切换执行条件，举例来说，切换执行条件是一个测量事件，比如所述条件是条件重配置测量事件A3(在持续一段时间内邻小区比服务小区信号质量好过一个偏移量)。所述邻小区对应切换的目标小区。一般来说，目前3GPP标准规范36.331和38.331(参见5.5.4章节)定义的所有测量事件，如A1～A5，都可作为切换执行条件包含在条件切换命令中。因为切换命令是包含在RRC重配置消息中的，所以条件切换CHO也称为条件重配置(conditional reconfiguration)。
现有机制中的链路失败上报机制：
当前的LTE系统和版本16的NR系统中，UE会在发生无线链路失败(Radio Link Failure，RLF)或切换失败(Handover Failure，HOF)时生成并保存一个无线链路失败报告(RLF report)，并将无线链路失败信息保存在UE变量VarRLF-Report。在恢复与网络侧的连接(如通过RRC重建立过程或用于建立新连接的RRC建立过程)后，UE可以通过RRC消息告知网络侧其上有可用的无线链路失败报告(rlf-InfoAvailable信息元素来指示)。如UE可以在RRC连接重建立过程中的RRC连接重建立完成消息(RRCConnectionReestablishmentComplete)中、RRC连接重配置过程中的RRC连接重配置完成消息(RRCConnectionReconfigurationComplete)中、RRC连接建立过程中的RRC连接建立完成消息(RRCConnectionSetupComplete)中或RRC连接恢复过程中的RRC连接恢复完成消息(RRCConnectionResumeComplete)中告知网络侧UE有保存的可用的无线链路失败报告。网络侧在收到所述指示后，可以通过RRC消息(UEInformationRequest消息中的rlf-ReportReq信息元素来指示所述请求)来请求UE上报其保存的无线链路失败报告。UE会在响应RRC消息中将所保存的无线链路失败报告(UEInformationResponse消息中的rlf-Report信息元素)上报给网络侧。网络侧获取的所述无线链路失败报告用于网络优化，如网络覆盖和移动鲁棒性优化。无线链路失败报告中可包含：链路失败时可用的源小区和邻居小区的测量结果、 位置信息、发生链路失败的主小区标识、链路失败类型(RLF还是HOF)、RLF理由、从连接失败到上报无线链路失败所经历的时间、上次收到切换命令到连接失败所经历的时间(记做timeConnFailure信息元素)，UE重新接入网络的小区标识即RRC重建立小区标识等。
利用保存的条件切换配置的无线链路恢复机制：
UE在配置了条件切换后，并不会立即执行切换，而是在所对应的条件满足之后才按照收到和保存的条件切换配置执行切换。在UE接收到条件切换配置的时刻到按照收到的条件切换配置执行切换的这段时间内，UE依然保持和源基站的通信。在这段时间内，可能会发生UE和源基站之间的无线链路失败(Radio Link Failure，RLF)。版本16的NR或LTE系统中引入了一个链路恢复增强机制：在发生RLF或HOF时，UE通过RRC连接重建立过程中的小区选择过程(即T311定时器运行时)来选择一个小区来执行链路恢复，若UE被配置了可以在链路失败后执行CHO的使能指示，且所述小区选择过程是由于监测到了MCG RLF或MCG的切换失败(即NR系统中的同步重配置失败)且所选择的小区是一个条件切换候选小区(所述小区对应的同步重配置信息元素reconfigurationWithSync包含在所保存的条件重配置变量中的MasterCellGroup信息元素中的)，则UE按照该小区对应的条件切换配置执行到该小区的切换；否则，UE通过向所选择的小区发送RRC连接建立请求来尝试恢复和网络侧的连接。这种链路恢复机制的增强在本公开中称为基于条件切换配置的链路失败恢复机制(为描述方便，简称为条件切换链路恢复机制)。网络侧通过将CHO配置中的CHO恢复信息元素(记做attemptCondReconfig信息元素)置为true来使能UE的这项功能，指示UE在失败后，若所选择的小区是一个目标候选小区且是失败后第一次小区选择时，UE要执行条件切换来恢复链路。使能了该功能的UE，若RLF/HOF后的第一次小区选择过程所选择的小区是一个目标候选小区，则UE可以执行到该小区的CHO。在版本16的系统中，UE在失败后仅允许执行一个CHO恢复。所述条件切换候选小区是指UE所接收到用于配置条件切换的 RRC消息中的条件切换配置中的(目标)小区，即同步重配置信息元素(ReconfigurationWithSync)或移动控制信息元素(MobilityControlInfo)中的小区标识所标识的小区。网络侧可以同时为UE配置一个或多个切换执行条件候选小区。
DAPS切换：
在版本16的NR或LTE系统中引入的DAPS机制中，UE在收到切换命令后，在执行接入到目标基站的切换过程中并不切断和源基站的链接(数据传输)，而是可以同时维护和目标基站以及源基站之间的连接和数据传输，从而避免切换过程中由于在接入目标基站之前就断开和源基站的连接而产生的对业务中断所带来的时延。DAPS切换，指的就是这样一种切换过程，UE在收到用于切换的RRC消息后仍维持和源基站之间的连接，直到成功执行到目标的随机接入过程后源基站被释放。在此过程中，UE继续从源基站接收下行数据直到源基站被释放，用户继续向源基站发送上行数据直到到目标基站的随机接入过程成功完成。向目标基站的随机接入过程完成后，MAC层向上层指示随机接入过程完成，RRC层在收到该指示后，指示下层(如PDCP层)执行上行数据变更，将上行路径从源基站变更为目标基站。
在DAPS切换情况下，UE在收到切换命令后，为目标基站建立一个MAC实体，若一个DRB被配置为DAPS承载，则为该DRB建立一个关联到目标基站的RLC实体和专用业务信息(Dedicated Traffic Channel，DTCH)逻辑信道，且对该DAPS承载所关联的PDCP实体重配为DAPS PDCP实体，所述DAPS PDCP实体即在PDCP实体中同时存在分别关联到源基站和目标基站的安全和鲁棒性头压缩(RObust Header Compression，ROHC)功能，且将所述安全和ROHC功能分别关联到源基站和目标基站所配置的对应的RLC实体上。通过上述方式，如图3所示，在DAPS切换过程中，UE同时维护对于源基站和目标基站的激活协议栈。
当DAPS切换失败，即用于监测切换过程的T304定时器超时，则如果源基站上未监测到无线链路失败，则UE返回到和源基站的连 接，通过源基站上报DAPS切换失败，而不会触发RRC连接重建立过程。否则，若源基站上监测到了或者已经发生无线链路失败，则UE通过发起RRC连接重建立过程来恢复和网络的链路。
在移动鲁棒性优化时，有几种典型类型：过晚切换(too late handover)，一般是由于切换命令下发太晚，而导致UE没有及时收到切换命令而发生在源小区的RLF；过早切换(too early handover)，一般是由于切换相关参数设置的过于保守，使得UE未到切换区域就执行了切换，从而可能发生在切换过程中的HOF或者在成功切换到目标小区之后很短之间内就发生了RLF；错误小区切换(handover to the wrong cell)，是由于不同小区的切换参数设置不合理，导致UE的目标小区选择错误，使得UE可能在成功切换到目标小区很短时间后就发生了RLF，而在后续的链路恢复过程如RRC重建立过程中选择了不同于目标小区的其他的小区执行RRC重建立。
由上可知，在版本16的NR或LTE系统中，区别于传统切换机制，引入了CHO和DAPS等新的切换机制。这些新的切换机制中所使用的切换参数配置如测量上报门限值，切换过程检测定时器T304的值等，可以和传统切换机制中的对应参数配置得不一样，即可以认为不同切换机制(场景)各有一套切换相关参数。因此，在网络侧进行移动性能参数优化时，对不同切换机制(场景)需要加以区分，将不同切换机制(场景)下从UE所获得的切换性能辅助信息(如RLF report)进行分开统计，基于不同的统计数据对相应的切换机制(场景)所对应的切换相关参数评估和调整，使得网络优化更加精细化。
考虑在一种场景下，UE执行了从小区A到小区B的切换过程。在成功切换到小区B的很短时间内，发生了在小区B的RLF，UE设置并保存此次RLF的相关信息即RLF报告。RLF后的UE通过RRC连接重建立或RRC连接建立或其他方式恢复和网络侧的链路连接。UE会向网络侧指示其上有保存可用的RLF报告。在随后的某个时间，网络侧通过RRC消息向UE发送RLF报告请求，来请求UE上报所保存的RLF报告。UE基于所述请求将所保存的RLF报告发送给网络侧。 网络侧基于所述RLF报告的内容可以判断此时RLF实际上是前一次从小区A到小区B的切换不合理(如过早切换或切换到错误小区)，从而对小区A和小区B之间的切换相关参数进行调整。另一方面，何时发送所述请求是由网络侧决定的，也就是说网络侧决定何时从UE上获取所保存的RLF报告。因此，在一种情况下，当网络侧(如小区A或小区B)获取到所述RLF报告时，网络侧可能已经丢弃了所述UE的上下文(UE context)信息，依据现有机制中RLF报告的信息，网络侧无法知道所述RLF报告所关联的前一次切换是何种切换过程(如传统切换、CHO或DAPS)，从而可能导致错误的切换参数调整。
以下，详细描述本公开中的若干实施例。以下的实施例仅仅是为了容易理解本发明而给出的示例，并不是为了限制本发明。
实施例1
以下，对本公开的实施例1进行详细说明。该实施例给出了一种UE向网络上报RLF报告的方法，UE在检测到发生RLF时，UE在RLF报告(VarRLF-Rreport变量)中保存RLF报告时，可以按照如下方式来设置RLF报告中的内容。作为一例，图4是表示本公开实施例1中的无线链路失败报告方法的处理流程的示意图。
如图1所示，在步骤1中，UE监测到发生了RLF。优选地，指的是MCG的RLF。UE认为监测到了RLF的情况包含下述几种情况：
情况1：用于无线链路失败监测的定时器T310超时；
情况2：用于无线链路失败监测的定时器T312超时；
情况3：收到MAC层的随机接入问题指示且此时定时器T300、T301、T304，T311和T319都不在运行状态；这些定时器分别用于监测RRC连接建立过程、RRC连接重建立过程、切换过程、RRC重建立过程中的小区重选过程和RRC连接恢复过程。
情况4：收到来自RLC层的最大重传次数已达到的指示。
在步骤2中，UE在RLF报告中保存无线链路失败信息。作为一 例，UE可以在RLF报告对应的变量VarRLF-Report中保存无线链路失败信息。
关于无线链路失败信息，例如可以按照下述方式进行设置。
若UE在此次RLF之前执行过一个切换过程，则设置一个域，其包含用于指示所述切换过程的类型(场景)的信息；同时，包含previousPCellId信息元素并将其设置为最近的切换命令接收所在的(主)小区的全球小区标识和跟踪区域码；包含timeConnFailure信息元素设置为从接收到最近的切换命令开始所经历的时间。
优选地，所述UE在此次RLF之前执行过一个切换过程也可进一步描述为，若在所述连接失败(RLF)之前收到过切换命令(如包含同步重配置信息元素的RRC重配置消息)，若最近收到的切换命令是对于一个NR系统内(intra-NR)切换。考虑到在CHO的场景下，接收CHO命令和执行CHO命令的时间点可以不同，所述收到(接收)切换命令的描述也包括CHO情况下的执行CHO命令。
所述用于指示切换过程类型的信息可以指示切换过程的类型为CHO、DAPS切换或传统切换。优选地，当所述指示切换过程类型的信息不存在时，认为所对应的切换过程是传统切换即不是CHO或DAPS切换。当UE在此次RLF之前执行的切换过程是一个CHO时，所述用于指示切换过程类型的信息设置为CHO(条件重配置)。此时所述收到的切换命令等同于执行了的CHO命令(条件重配置)。若UE在此次RLF之前执行的切换过程是一个DAPS切换时，所述用于指示切换过程类型的信息设置为DAPS切换。此时所述收到的切换命令等同于收到的切换命令且切换命令中的配置中存在任意被配置为DAPS承载的数据无线承载DRB。可选地，所述切换过程类型还可以是用于指示所述切换过程是一个用于链路恢复的条件切换。即所述切换过程是在链路失败后小区选择过程中所选择的小区是条件候选小区时执行的切换过程，或者描述为所述切换过程是因为执行了条件切换链路恢复机制。
可选地，UE不总是在RLF report中包含上述指示切换过程类型 的信息，而是在一种条件满足时，才在RLF report中包含上述切换指示切换过程类型的信息。例如，UE通过RRC消息如RRC连接重配置消息从网络侧接收一个时间门限值配置Th，UE判断当timeConnFailure信息元素所标识的时间小于或小于等于Th时，UE才在RLF report中包含上述指示切换过程类型的信息。反之，UE判断当timeConnFailure信息元素所标识的时间大于或大于等于Th时，UE不在RLF report中包含上述指示切换过程类型的信息。也就是说UE判断只有当所述RLF可能与最近执行的切换过程相关时，才将切换过程类型信息包含在RLF report中。可选地，所述门限值Th为预定义的固定值如1s钟。
除此之外，UE还在RLFreport中包含下述内容。
设置失败小区标识(如failedPCellId信息元素)为监测到RLF的(主)小区的小区标识。若所述小区对应的全球小区标识(global cell identity)和跟踪区域码(tracking area code)可用，则所述小区标识则设置为全球小区标识和跟踪区域码；否则，小区标识设置为所述小区对应的物理小区标识(physical cell identity)和载波频率(carrier frequency)。
设置连接失败类型connectionFailureType信息元素为rlf。
设置UE标识C-RNTI为UE在主小区所使用的C-RNTI。
通过该实施例所述方法，网络侧可以获取UE在RLF失败前所经历的切换类型，从而实现更精确的移动性参数调整和设置。
实施例2
如前所述，若发生切换失败(T304超时)，若切换是一个DAPS切换，即UE被配置了DAPS承载，则此时并不马上执行RRC重建立过程，而是判断源主小区PCell是否检测到了RLF，若源PCell未检测到RLF，则UE会释放目标小区相关的配置，并回退到源PCell。UE通过发起失败信息过程向源PCell发送失败信息消息来向网络侧上报本次DAPS切换失败并回退到源小区。
由此可知在上述DAPS切换失败情况下，不同于传统切换失败后UE需要保存RLF report，UE在DAPS切换失败后回退到源PCell的情况下，并不保存RLF report。通过失败信息消息(FailureInformation消息)，网络侧仅能获知该UE发生了DAPS切换失败，而无法获取其他失败信息。在该实施例中，UE在上述情况下即发生DAPS失败并回退到源PCell时，通过在失败信息消息中携带下述失败信息，使得网路侧可以获取更多的切换失败信息，从而进行更准确的网络参数优化。所述失败信息包括：所述DAPS切换过程中的随机接入过程的信息：切换源PCell和邻小区的测量结果。
所述随机接入过程的信息的设置包括：
设置absoluteFrequencyPointA信息元素用于指示随机接入资源所关联的参考资源块的绝对频率；
设置所述locationAndBandwidth信息元素和subcarrierspacing信息元素用于关联到随机接入资源的上行带宽部分(BandWidth Part，BWP)的对应信息。
设置msg1-FrequencyStart、msg1-FDM和msg1-sbcarrierSpacing信息元素用于指示基于竞争的随机接入资源所使用的preamble所在的频域信息。
设置msg1-FrequencyStartCFRA、msg1-FDMCFRA和msg1-sbcarrierSpacingCFRA信息元素用于指示无竞争(contention free)的随机接入资源所使用的preamble所在的频域信息。
按照每个随机接入尝试(attempt)时间先后顺序设置随机接入尝试列表perRAinfoList信息元素中的信息：
若所用的随机接入资源关联到一个同步物理广播信道块(SS/PBCH)，设置ssb-index信息元素来包含随机接入资源关联的所述同步物理广播信道块的索引值；设置numberOfPreambleSentOnSSB信息元素来指示关联到所述同步物理广播信道块的连续的随机接入尝试的次数；对每一个随机接入尝试，若发生在基于竞争的随机接入资源上且随机接入过程的目的不是用于其他系统信息的请求(即 raPurpose信息元素不是requestForOtherSI)，则若所发送的前导的竞争解决(contention resolution)不成功，设置contentionDetected信息元素是true，否则设置成false；若随机接入尝试是使用基于竞争的随机接入资源，若所述同步物理广播信息块的参考信号接收功率RSRP高于一个配置的门限值rsrp-ThresholdSSB，则UE设置dlRSRPAboveThreshold信息元素未true，否则，设置其为false。
若所用的随机接入资源关联到一个信道状态指示参考信号(CSI-RS)，设置csi-RS-index信息元素来包含随机接入资源关联的所述CSI-RS的索引值；设置numberOfPreambleSentOn CSI-RS信息元素来指示关联到所述CSI-RS的连续的随机接入尝试的次数。
切换源PCell和邻小区的测量结果包括：
设置measResultNeighCells信息元素中的measResultListNR信息元素以包括除源PCell外的最好测量小区的所有可用的同步物理广播信道块SS-PBCH的测量量(参考信号接收功率RSRP或参考信号接收质量RSRQ或信干噪比SINR)。
设置measResultNeighCells信息元素中的measResultListNR信息元素以包括除源PCell外的最好测量小区的所有可用的信道状态指示参考信号CSI-RS的测量量(参考信号接收功率RSRP或参考信号接收质量RSRQ或信干噪比SINR)。
实施例3
该实施例对本公开的用户设备UE进行说明。图5是表示本发明所涉及的用户设备UE的框图。如图5所示，该用户设备UE50包括处理器501和存储器502。处理器501例如可以包括微处理器、微控制器、嵌入式处理器等。存储器502例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器502上存储有程序指令。该指令在由处理器501运行时，可以执行本发明中详细描述的上述无线链路失败报告方法、无线链路失败设置方法等的各种方法。
本公开中，一些不同实施例之间可以协同工作，除非特别指出，实施例之间的概念或定义可以通用。
在本公开中，“基站”是指具有较大发射功率和较广覆盖面积的移动通信数据和控制交换中心，包括资源分配调度、数据接收发送等功能。“用户设备”是指用户移动终端，例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
上文已经结合优选实施例对本公开的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的。本公开的方法并不局限于上面示出的步骤和顺序。上面示出的基站和用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本公开并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、 分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种无线链路失败报告方法，包括：
    用户设备UE监测到发生了无线链路失败RLF；
    所述UE在RLF报告中保存无线链路失败信息；
    所述UE在所述RLF之前执行过一个切换过程的情况下，所述无线链路失败信息包含：用于指示切换过程的类型的信息；最近的切换命令接收所在的小区的全球小区标识和跟踪区域码；以及从接收到最近的切换命令开始所经历的时间。
  2. 根据权利要求1所述的无线链路失败报告方法，其中，
    在所述RLF报告对应的变量VarRLF-Report中保存所述无线链路失败信息。
  3. 根据权利要求1所述的无线链路失败报告方法，其中，
    所述UE在所述RLF报告中设置一个域，所述域包含用于指示切换过程的类型的信息，
    所述RLF报告包含previousPCellId信息元素，所述previousPCellId信息元素设置为最近的切换命令接收所在的小区的全球小区标识和跟踪区域码，
    所述RLF报告包含timeConnFailure信息元素，所述timeConnFailure信息元素设置为从接收到最近的切换命令开始所经历的时间。
  4. 根据权利要求3所述的无线链路失败报告方法，其中，
    所述UE通过RRC消息从网络侧接收时间门限值Th，
    在所述timeConnFailure信息元素所标识的时间小于或等于所述时间门限值Th时，所述UE在所述RLF报告中包含用于指示所述切换过程的类型的信息，
    在所述timeConnFailure信息元素所标识的时间大于所述时间门限值Th时，所述UE不在所述RLF报告中包含用于指示所述切换过程的类型的信息。
  5. 根据权利要求1所述的无线链路失败报告方法，其中，
    所述用于指示切换过程的类型的信息指示切换过程的类型为：条件切换CHO、双激活协议栈DAPS切换或者传统切换。
  6. 根据权利要求5所述的无线链路失败报告方法，其中，
    在所述指示切换过程的类型的信息不存在时，表示切换过程的类型是传统切换。
  7. 根据权利要求1所述的无线链路失败报告方法，其中，
    所述RLF报告中还包含：
    设置失败小区标识为监测到所述RLF的小区的小区标识；
    设置连接失败类型connectionFailureType信息元素为rlf；以及
    设置UE标识C-RNTI为UE在主小区所使用的C-RNTI。
  8. 根据权利要求1所述的无线链路失败报告方法，其中，
    在切换命令是CHO切换命令、DAPS切换命令或CHO链路恢复命令时，所述用于指示切换过程的类型的信息被设置为与各个命令对应的值，
    若所述UE在所述RLF之前执行的切换过程是一个CHO切换时，所述用于指示切换过程类型的信息设置为CHO切换，
    若所述UE在所述RLF之前执行的切换过程是一个DAPS切换时，所述用于指示切换过程类型的信息设置为DAPS切换，
    若所述UE在所述RLF之前执行的切换过程是一个用于链路恢复的条件切换CHO时，所述用于指示切换过程类型的信息设置为CHO链路恢复。
  9. 根据权利要求1所述的无线链路失败报告方法，其中，
    所述RLF是主小区组MCG RLF或辅小区组SCG RLF，
    所述切换过程是主小区PCell的同步重配置过程或主辅小区PSCell的同步重配置过程。
  10. 一种用户设备UE，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的无线链路失败报告方法。
PCT/CN2021/118175 2020-09-16 2021-09-14 无线链路失败报告方法以及用户设备 Ceased WO2022057783A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21868606.1A EP4216597A4 (en) 2020-09-16 2021-09-14 RADIO LINK FAILURE REPORTING METHOD AND USER EQUIPMENT
US18/026,142 US12526715B2 (en) 2020-09-16 2021-09-14 Radio link failure reporting method and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010976460.3A CN114268977A (zh) 2020-09-16 2020-09-16 无线链路失败报告方法以及用户设备
CN202010976460.3 2020-09-16

Publications (1)

Publication Number Publication Date
WO2022057783A1 true WO2022057783A1 (zh) 2022-03-24

Family

ID=80776477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/118175 Ceased WO2022057783A1 (zh) 2020-09-16 2021-09-14 无线链路失败报告方法以及用户设备

Country Status (4)

Country Link
US (1) US12526715B2 (zh)
EP (1) EP4216597A4 (zh)
CN (1) CN114268977A (zh)
WO (1) WO2022057783A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023245338A1 (en) * 2022-06-20 2023-12-28 Lenovo (Beijing) Limited Methods and apparatuses for son enhancements
WO2024168458A1 (en) * 2023-02-13 2024-08-22 Apple Inc. Radio link failure and handover failure in layer 1/layer 2 mobility

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12143836B2 (en) * 2022-05-10 2024-11-12 T-Mobile Innovations Llc Optimization of device configuration relating to wireless access technologies
WO2024000165A1 (en) * 2022-06-28 2024-01-04 Mediatek Singapore Pte. Ltd. Methods and apparatus to improve ue experience with a new type of radio bearer during inter-du inter-cell beam management
CN115209432B (zh) * 2022-07-06 2024-01-19 中电信数智科技有限公司 一种小区基站信号接入故障定位及自愈的方法
CN117459944A (zh) * 2022-07-19 2024-01-26 夏普株式会社 由用户设备执行的方法以及用户设备
CN117750447A (zh) * 2022-09-15 2024-03-22 夏普株式会社 由用户设备执行的方法以及用户设备
CN119300077A (zh) * 2023-07-12 2025-01-10 中国电信股份有限公司技术创新中心 链路失败报告方法及装置、计算机可读存储介质
CN119450567A (zh) * 2023-08-07 2025-02-14 夏普株式会社 链路失败报告方法和用户设备
CN119545452A (zh) * 2023-08-30 2025-02-28 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
WO2025074636A1 (ja) * 2023-10-06 2025-04-10 株式会社Ｎｔｔドコモ 端末
CN121510167A (zh) * 2024-08-09 2026-02-10 华为技术有限公司 通信方法及相关产品

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831079A (zh) * 2018-08-09 2020-02-21 惠州Tcl移动通信有限公司 通信切换方法及装置
WO2020156497A1 (en) * 2019-02-01 2020-08-06 Qualcomm Incorporated Techniques for communicating mobility information
WO2020163991A1 (en) * 2019-02-12 2020-08-20 Zte Corporation Method of performance information reporting

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379517B (zh) * 2012-04-13 2018-10-12 华为技术有限公司 无线链路失败报告处理方法、异常事件统计处理方法及设备和系统
CN108243469B (zh) * 2016-12-23 2021-07-16 夏普株式会社 用户移动性方法和设备
CN110868739B (zh) * 2018-08-27 2023-12-15 夏普株式会社 由用户设备执行的方法、用户设备以及切换命令生成方法
WO2020122797A1 (en) * 2018-12-14 2020-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Conditional mobility
US12396051B2 (en) * 2020-02-27 2025-08-19 Lg Electronics Inc. Method and apparatus for failure recovery in wireless communication system
US20230156539A1 (en) * 2020-04-09 2023-05-18 Lenovo (Beijing) Ltd. Method and apparatus for failure report
EP4136924A4 (en) * 2020-04-17 2023-12-27 Lenovo (Beijing) Limited Method and apparatus for fast mcg link recovery considering cho and lbt
WO2022006884A1 (en) * 2020-07-10 2022-01-13 Lenovo (Beijing) Limited Methods and apparatuses for processing a rlf during a daps handover procedure
JP2023547334A (ja) 2020-10-22 2023-11-10 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ハンドオーバ関連情報を提供するための方法および装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831079A (zh) * 2018-08-09 2020-02-21 惠州Tcl移动通信有限公司 通信切换方法及装置
WO2020156497A1 (en) * 2019-02-01 2020-08-06 Qualcomm Incorporated Techniques for communicating mobility information
WO2020163991A1 (en) * 2019-02-12 2020-08-20 Zte Corporation Method of performance information reporting

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP STANDARD SPECIFICATIONS 36.331
CATT: "Discussion on CHO and DAPS Mobility Enhancement", 3GPP DRAFT; R2-2008844, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941924 *
See also references of EP4216597A4
SESSION CHAIR (CMCC): "Report from SON/MDT session", 3GPP DRAFT; R2-2005736, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20200601 - 20200612, 15 June 2020 (2020-06-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051897890 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023245338A1 (en) * 2022-06-20 2023-12-28 Lenovo (Beijing) Limited Methods and apparatuses for son enhancements
WO2024168458A1 (en) * 2023-02-13 2024-08-22 Apple Inc. Radio link failure and handover failure in layer 1/layer 2 mobility

Also Published As

Publication number Publication date
EP4216597A1 (en) 2023-07-26
EP4216597A4 (en) 2024-08-07
CN114268977A (zh) 2022-04-01
US20230362774A1 (en) 2023-11-09
US12526715B2 (en) 2026-01-13

Similar Documents

Publication Publication Date Title
US12401561B2 (en) Radio link failure reporting method and user equipment
US12526715B2 (en) Radio link failure reporting method and user equipment
US20240224150A1 (en) Handover information reporting method and user equipment
US12457658B2 (en) Radio link failure recovery method and corresponding user equipment
US12526714B2 (en) Method performed by user equipment, and user equipment
EP4181568A1 (en) Handover information reporting method and user equipment
CN112584551B (zh) 无线链路失败恢复方法以及用户设备
WO2023179677A1 (zh) 无线链路失败信息报告方法以及用户设备
WO2023134763A1 (zh) 信息报告方法以及用户设备
US20240215099A1 (en) Handover information reporting method, user equipment, and communication system
WO2024017237A1 (zh) 由用户设备执行的方法以及用户设备
WO2023125649A1 (zh) 连接建立失败报告方法和用户设备
WO2024027704A1 (zh) 切换信息报告方法以及用户设备
WO2024094056A1 (zh) 信息报告方法以及用户设备
WO2023040955A1 (zh) 切换信息报告方法以及用户设备
WO2024008076A1 (zh) 切换信息报告方法以及用户设备
WO2024067624A1 (zh) 信息报告方法以及用户设备
WO2023241622A1 (zh) 由用户设备执行的方法、用户设备以及信息报告方法
CN119485520A (zh) 切换信息报告方法以及用户设备
WO2025237189A1 (zh) 信息报告方法以及用户设备
CN117750447A (zh) 由用户设备执行的方法以及用户设备
CN120186663A (zh) 信息报告方法以及用户设备
CN118338348A (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: 21868606

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

Country of ref document: EP

Effective date: 20230417

WWW Wipo information: withdrawn in national office

Ref document number: 2021868606

Country of ref document: EP

WWG Wipo information: grant in national office

Ref document number: 18026142

Country of ref document: US