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

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

Info

Publication number
WO2021254197A1
WO2021254197A1 PCT/CN2021/098603 CN2021098603W WO2021254197A1 WO 2021254197 A1 WO2021254197 A1 WO 2021254197A1 CN 2021098603 W CN2021098603 W CN 2021098603W WO 2021254197 A1 WO2021254197 A1 WO 2021254197A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
source base
rlf
failure
daps
Prior art date
Application number
PCT/CN2021/098603
Other languages
English (en)
French (fr)
Inventor
常宁娟
刘仁茂
Original Assignee
夏普株式会社
常宁娟
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 常宁娟 filed Critical 夏普株式会社
Priority to EP21825252.6A priority Critical patent/EP4171115A1/en
Priority to US18/009,751 priority patent/US20230262565A1/en
Publication of WO2021254197A1 publication Critical patent/WO2021254197A1/zh

Links

Images

Classifications

    • 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/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H04W36/185—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection using make before break
    • 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • 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
    • 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/08—Reselecting an access point

Definitions

  • the present invention relates to the field of wireless communication technology, and more specifically, the present invention relates to a method executed by a user equipment and a corresponding user equipment.
  • seamless handover that is, the handover interruption time of zero milliseconds or close to zero milliseconds can be met during the handover process of changing the UE's serving cell .
  • Dual Active Protocol Stack Dual Active Protocol Stack
  • the UE after receiving the handover command, the UE does not cut off the link with the source base station (data transmission) during the handover process that accesses the target base station, but can maintain the connection with the target base station and the source base station at the same time.
  • the time delay caused by service interruption caused by disconnecting the connection with the source base station before accessing the target base station during the handover process In order to avoid the time delay caused by service interruption caused by disconnecting the connection with the source base station before accessing the target base station during the handover process.
  • the present invention provides a method executed by a user equipment and a user equipment, which can effectively execute the radio link failure report under the DAPS mechanism in the LTE/NR system.
  • a method executed by a user equipment UE includes: when the UE performs a DAPS handover failure during the DAPS handover of the dual activation protocol stack, if the source base station radio link failure is not detected If the source base station is RLF, the UE falls back to the source base station link, and does not generate and save handover failure information for the DAPS handover failure in the link failure report; and when falling back to the source base station link, if If the UE detects that the source base station RLF has occurred, the UE records and saves the link failure information for the source base station RLF in the link failure report.
  • the fallback to the source base station link includes: the source base station falls back to the used radio resource control RRC configuration and restores the suspended signaling radio bearer of the source cell.
  • the link failure report further includes: information indicating that the UE has just experienced the DAPS handover failure.
  • the link failure report further includes: the target cell identifier of the DAPS handover and/or information indicating the failure of the random access process performed during the DAPS handover.
  • a method executed by a user equipment UE includes: when the UE performs a DAPS handover failure during the DAPS handover of the dual activation protocol stack, if the source base station radio link is not detected Failure is the source base station RLF, then the UE falls back to the source base station link, and generates and saves the handover failure information for the DAPS handover failure in the link failure report; and when falling back to the source base station link, If the UE detects that the source base station RLF has occurred, the UE records and saves link failure information for the source base station RLF in the link failure report.
  • the fallback to the source base station link includes: the source base station falls back to the used radio resource control RRC configuration and restores the suspended signaling radio bearer of the source cell.
  • the link failure report further includes: information indicating that the source base station RLF occurred when the UE fell back to the source base station link after the DAPS handover failed.
  • a method executed by a user equipment UE includes: the UE detects that a source base station radio link failure occurs during the process of performing a dual activation protocol stack DAPS handover, that is, the source base station RLF; and If a DAPS handover failure occurs after the source base station RLF occurs, the UE generates and saves handover failure information for the DAPS handover failure in a link failure report, where the link failure report also includes Link failure information of the source base station RLF.
  • the link failure information for the source base station RLF includes one or more of the following: information representing the elapsed time from when the UE receives a DAPS handover command to the occurrence of the source base station RLF; Information indicating the reason for triggering the RLF of the source base station; and information indicating that the RLF of the source base station occurred during the execution of the DAPS handover.
  • a user equipment which includes: a processor; and a memory storing instructions; wherein the instructions execute the above-mentioned method when run by the processor.
  • the radio link failure report under the DAPS mechanism in the LTE/NR system can be effectively executed. Specifically, it can be effective when the source cell's radio link failure (Radio Link Failure, RLF) and/or the target cell's RLF or DAPS handover failure (HandOver Failure, HOF) occurs when the UE performs DAPS handover in the LTE/NR system Record or report the failure-related information locally.
  • RLF Radio Link Failure
  • HOF DAPS handover failure
  • Figure 1 is a schematic diagram of a general handover process.
  • Figure 2 is a schematic diagram showing a user plane protocol stack in a dual activation protocol stack configuration.
  • Fig. 3 is a flowchart showing a method executed by a user equipment according to Embodiment 1 of the present invention.
  • Fig. 4 is a flowchart showing a method executed by a user equipment according to Embodiment 2 of the present invention.
  • Fig. 5 is a flowchart showing a method executed by a user equipment according to scenario 3.1 of embodiment 3 of the present invention.
  • Fig. 6 is a flowchart showing a method executed by a user equipment according to scenario 3.2 of embodiment 3 of the present invention.
  • Fig. 7 is a flowchart showing a method executed by a user equipment according to Embodiment 4 of the present invention.
  • Fig. 8 is a flowchart showing a method executed by a user equipment according to Embodiment 5 of the present invention.
  • Fig. 9 is a flowchart showing a method executed by a user equipment according to Embodiment 6 of the present invention.
  • FIG. 10 is a flowchart showing a method executed by a user equipment according to Embodiment 7 of the present invention.
  • FIG. 11 is a flowchart showing a method executed by a user equipment according to Embodiment 8 of the present invention.
  • Fig. 12 is a flowchart showing a method executed by a user equipment according to Embodiment 9 of the present invention.
  • Fig. 13 is a block diagram schematically showing a user equipment involved in the present invention.
  • LTE Long Term Evolution
  • NR New Radio Access
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • handover refers to the change of the primary cell initiated by the network side, including the primary cell change between cells as well as the primary cell change 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 can be the same cell or a different cell.
  • the secret key or security algorithm used for access layer security can also be updated or not updated accordingly.
  • the security includes encryption and decryption and integrity protection.
  • the source cell can also be called the source base station, or the source beam (beam), the source transmission point (TRP), the source primary cell (Primary Cell, PCell), the source primary cell group MCG;
  • the target cell can also be called the target Base station, or target beam, target transmission point, target primary cell PCell, target cell group MCG.
  • the source cell refers to the cell that is connected to serve the UE before the handover process is initiated, that is, the cell that sends the RRC message containing the handover command to the UE.
  • the target cell refers to the cell that the UE connects to and serves the UE after the handover process is successfully completed, the cell indicated by the target cell identifier included in the handover command, or is described as the cell that performs downlink synchronization and random access during the handover process.
  • the handover command of the present invention is used to trigger the UE to perform handover.
  • it is an RRC reconfiguration message containing a synchronization reconfiguration (Reconfigurationwithsync) information element, and furthermore, it contains an RRC reconfiguration message for a master cell group (Master Cell Group, MCG).
  • the RRC reconfiguration message of the reconfiguration (Reconfigurationwithsync) information element is an RRC reconfiguration message containing a synchronization reconfiguration (Reconfigurationwithsync) information element.
  • the handover can also be referred to as the synchronous reconfiguration of the MCG.
  • the synchronization reconfiguration information element or the mobile control information information element may include the configuration information of the target cell, such as the target cell identity, the frequency of the target cell, the common configuration of the target cell, such as system information, and the information used by the UE to access the target cell. Random access configuration, security parameter configuration of the UE in the target cell, and radio bearer configuration of the UE in the target cell, etc.
  • the RRC reconfiguration message in the present invention is equivalent to the RRC connection reconfiguration message; in the same way, the response message RRC reconfiguration complete message is equivalent to the RRC connection reconfiguration complete message.
  • 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 the 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 can be replaced. Configuration and reconfiguration can be replaced. Monitor and detect can be replaced.
  • the RRC re-establishment message is equivalent to the RRC connection re-establishment message; in the same way, the response message RRC re-establishment complete message is equivalent to the RRC connection re-establishment complete message.
  • the RRC reconfiguration message used for the handover command carries the RRC configuration from the target base station, including but not limited to the following RRC configuration (for details, please refer to section 6.2.2 in the 3GPP technical standard protocol 38.331):
  • -Measurement configuration used to configure intra-frequency, inter-frequency and inter-radio access technology measurements performed by the UE. Such as measurement object configuration, measurement report configuration, measurement gap configuration, etc.
  • -Cell group configuration (cellGroupConfig information element), used to configure a primary cell group or a secondary cell group.
  • a primary cell group or a secondary cell group Including data radio bearer/signaling radio bearer corresponding radio link control (Radio Link Control, RLC) bearer configuration (rlc-bearerToAddModList information element and rlc-bearerToreleaselist information element), medium access control (Medium Access Control, MAC) configuration (MAC-cellgroupconfig information element), physical layer configuration, secondary cell addition/modification/release configuration, special cell (SpCell) configuration, etc.
  • the sPCell configuration includes cell index number, handover information (reconfigurationWithSync information element), radio link failure related timer and constant configuration, radio link detection (Radio Link Monitoring, RLM) configuration, special cell specific configuration, etc.
  • the reconfigurationwithsync information element is similar to the mobility control information in the LTE system. It contains handover-related information to achieve mobility. It includes the public information of the serving cell configuration, the C-RNTI of the UE in the target cell, the handover process monitoring timer T304 configuration, and Random access dedicated configuration for random access process to the target cell, etc.
  • RadiobearerConfig information element used to configure the service data application protocol layer (Service Data Application Protocol, SDAP) and PDCP of the radio bearer DRB and/or SRB.
  • the handover process refers to a process in which a UE in an RRC connected state changes a serving cell (primary cell).
  • the handover process generally includes the following stages:
  • Phase 1 Measurement phase.
  • the base station sends the measurement configuration to the user equipment (User Equipment, UE); the UE measures the radio link corresponding to the serving cell or 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 UE can be handed over blindly when the base station does not have a valid measurement report.
  • Phase 2 Handover preparation phase.
  • the base station determines whether to trigger a handover for the UE based on the received measurement report and other factors such as base station load. If it is determined to trigger a handover for the UE, the source base station initiates the handover preparation process by sending a handover request message to the target base station.
  • the target base station decides whether to accept this handover request for the UE according to the UE context in the handover request message and the available resources of the target base station. If accepted, it will reply to the source base station with a handover confirmation message, where the handover confirmation message contains a base station Inter-node RRC messages are handover commands.
  • Phase 3 Switch execution phase.
  • the source base station issues the handover command to the UE and starts to forward the UE's data 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 process, and sends a confirmation message to the target base station. Among them, the random access process is not necessary.
  • Phase 4 Switch completion phase. After the target base station confirms that the UE has successfully accessed, it sends a handover complete message to the source base station. According to this, the source base station can release the UE context stored on it.
  • DAPS Dual Active Protocol Stack
  • the DAPS handover introduced in version 16 refers to a handover process. After the UE receives the RRC message for handover, it still maintains the connection with the source base station until the source base station is released after the target random access process is successfully executed. . In this process, for a bearer configured with DAPS, 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 process to the target base station is successfully completed. After the random access process to the target base station is completed, the MAC layer instructs the upper layer to complete the random access process.
  • the RRC layer instructs the lower layer (such as the Packet Data Convergence Protocol, PDCP) layer to execute Uplink data change, which changes the uplink path from the source base station to the target base station.
  • the PDCP layer delivers the PDCP data protocol data unit (PDU) PDU to the RLC entity associated with the target base station, and delivers the PDCP control PDU associated with the source base station to the source base station
  • PDU Packet Data Convergence Protocol
  • the associated RLC entity delivers the PDCP control PDU associated with the target base station to the RLC entity associated with the target base station.
  • DAPS handover After the UE receives the handover command, it establishes a MAC entity for the target base station. If a DRB is configured as a DAPS bearer, it establishes an RLC entity associated with the target base station and dedicated service information (Dedicated Service Information) for the DRB. Traffic Channel, DTCH) logical channel, and the PDCP entity associated with the DAPS bearer is reconfigured as a DAPS PDCP entity.
  • the DAPS PDCP entity is a PDCP entity that is simultaneously associated with the source base station and the target base station for security and robustness.
  • ROHC RObust Header Compression
  • the UE In the DAPS process, if the source base station has a radio link failure, the UE will suspend the DRB transmission of all source base stations, reset the MAC entity, and release the source base station connection. After the DAPS handover is successful, the UE receives the RRC reconfiguration message sent from the target base station, which carries the indication information for instructing the release of the source base station (for example, identified by the daps-SourceRelease information element). After receiving the indication, the UE performs the release The configuration of the source base station and the operation of the protocol stack fall back to the single activation protocol stack state that only maintains the connection with the target base station.
  • the UE When the DAPS handover fails, that is, the T304 timer used to monitor the handover process expires, if the radio link failure is not detected on the source base station, the UE returns to the connection with the source base station, passes and informs the source base station that a DAPS handover failure has occurred , Without triggering the RRC connection re-establishment process. In the process of returning to the connection with the source base station, the UE falls back from the DAPS state to the single activation protocol stack state that only maintains communication with the source base station. If the DAPS handover fails, the source base station also detects RLF or is in the RLF state, the UE triggers the RRC connection re-establishment process to perform link recovery.
  • the DAPS handover can be replaced with a handover process in which any DRB is configured as a DAPS bearer.
  • Radio Link Failure Radio Link Failure
  • the UE considers that RLF has occurred when one of the following situations occurs: the timer T310 for RLF monitoring expires, the timer T312 for fast RLF monitoring expires, the random access problem indication from the MAC layer is received, and the random access problem indication from the MAC layer is received.
  • the UE In the case of single connection or dual connection, if the above timer, MAC entity, and RLC are associated with MCG, it is considered that MCG RLF is detected. In the case of dual connectivity (DC), the UE is configured with a secondary cell group (Secondary Cell Group, SCG). If the above timer, MAC entity, and RLC are associated with the SCG, it is considered that the SCG RLF is monitored.
  • SCG Secondary Cell Group
  • the judgment of the handover failure is realized by the running state of the timer T304.
  • the UE starts the timer T304 when it initiates the handover process and starts the handover to the target base station; when the handover process is successful, it stops the timer T304.
  • the handover process success refers to the RRC message used to respond to the handover command, such as RRC reconfiguration completed.
  • the message is successfully sent or the MAC layer of the UE successfully completes the random access process to the target base station; if T304 times out, the UE considers that the handover has failed, and HOF has occurred, and then the UE performs RRC re-establishment or rolls back to the source when there is DAPS configuration
  • the radio link failure reporting mechanism in the existing mechanisms is the radio link failure reporting mechanism in the existing mechanisms:
  • the UE In the current LTE system and version 16 NR system, the UE generates and saves a radio link failure report (RLF report) when a link failure occurs.
  • the UE variable used to save the radio link failure report is VarRLF-Report .
  • the UE can inform the network side that there is an available radio link failure report (as indicated by the rlf-InfoAvailable information element) through an RRC message.
  • the UE can use the RRC reestablishment complete message (RRCReestablishmentComplete) in the RRC connection re-establishment process, the RRC reconfiguration complete message (RRCReconfigurationComplete) in the RRC reconfiguration process, and the RRC setup complete message (RRCSetupComplete) in the RRC connection establishment process.
  • the RRC recovery complete message (RRCResumeComplete) in the middle or RRC connection recovery process informs the network-side UE that there is a saved available radio link failure report.
  • the network side may request the UE to report the stored radio link failure report through an RRC message (such as the rlf-ReportReq information element in the UEInformationRequest message to indicate 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 wireless link failure report obtained by the network side is used for network optimization, such as network coverage and mobile robustness optimization.
  • the radio link failure report can include: the measurement results of the source cell and neighboring cells available when the link fails, location information, the primary cell identification where the link fails, the type of link failure (such as RLF or HOF), the reason for the RLF, The elapsed time from link failure to the reporting of wireless link failure (timeSinceFailure information element), the time from the last handover command execution to the link failure (recorded as timeConnFailure information element), and random access process information Wait. In addition, it also includes the cell identity for reconnecting to the network after failure, such as the RRC re-establishment cell identity, the cell identity for the RRC connection establishment, and so on.
  • the random access process information is recorded in the link failure report when the cause of the link failure is random access failure or the link failure is a handover failure.
  • the random access process information includes: random access purpose or scenario, the frequency domain start information of message 1 (the lowest position of the physical random access channel PRACH transmission opportunity (occasion) in the frequency domain and the uplink bandwidth Part of the offset between the zero number physical resource blocks), the subcarrier spacing of the PRACH resource, and the detailed information about each random access attempt during the random access process.
  • the detailed information of each random access attempt also includes the used synchronization signal/physical broadcast channel block index value or the channel state information reference signal index value, and the number of random access preambles sent on the beam corresponding to the index value , And whether competition is monitored for each random access attempt and whether the measured signal quality (Reference Signal Received Power, RSRP) is higher than the configured threshold.
  • link failure report, radio link failure report, VarRLF-Report and connection failure information can be replaced.
  • the existing mechanism only supports the UE to save a link failure report, that is, when a link failure occurs again, the UE will clear the saved link failure information related to the previous link failure (such as the variable VarRLF-rpeort Information), and only record the link failure information related to the last link failure. The reason is that in the existing network, there are not many scenarios of multiple link failures that occur in connection, and between two link failures, the network side can always extract the information of the previous link failure from the UE side.
  • Scenario 1 After receiving the handover command containing the DAPS configuration, the UE executes the DAPS handover process.
  • the source base station RLF is monitored before DAPS is not successful (that is, T304 is running), and then the DAPS handover is successfully completed.
  • Scenario 2 After receiving the handover command containing the DAPS configuration, the UE executes the DAPS handover process. Then the DAPS handover failure occurs after T304 timeout. At this time, the source base station link does not detect the link failure, the UE releases the relevant configuration and protocol stack of the target cell, returns to the source base station, and sends an RRC message containing the DAPS failure indication to the source base station (Such as FailureInformation), but then a link failure of the source base station occurred. In short, in scenario 1, the DAPS handover failure of the UE occurs first, and then the link failure of the source cell occurs.
  • Scenario 3 After receiving the handover command containing the DAPS configuration, the UE executes the DAPS handover process.
  • the source base station RLF was monitored before DAPS was not successful (that is, the T304 was in the running state), and then the DAPS handover failure occurred after the T304 timed out. At this time, the UE initiates an RRC re-establishment process to perform link recovery.
  • scenario 3 the source base station link failure occurs in the UE first, and then the DAPS handover failure occurs.
  • Scenario 4 After the UE receives the handover command containing the DAPS configuration, it executes the DAPS handover process, and then the DAPS handover fails due to the timeout of T304. At this time, the source base station link does not detect a link failure, the UE releases the relevant configuration and protocol stack of the target cell, successfully rolls back to the source base station, and sends an RRC message (such as FailureInformation) containing a DAPS failure indication to the source base station.
  • RRC message such as FailureInformation
  • Scenario 5 After the UE receives the handover command containing the DAPS configuration, it executes the DAPS handover process.
  • the source base station RLF is monitored before DAPS is not successful (that is, T304 is running), and then the DAPS handover is successfully completed. But soon the RLF of the target base station occurred.
  • Scenario 6 After the UE receives the handover command including the DAPS configuration, it executes the DAPS handover process, and the DAPS handover is successful. Before receiving the source link release indication from the base station, the source base station RLF is monitored.
  • the UE does not record the corresponding link failure information for the source base station RLF that occurs during the DAPS handover process, that is, when the T304 timer is running, that is, when the source base station RLF occurs, the UE does not generate it in the VarRLF-report And save the corresponding information.
  • the failure information of the source base station RLF is also helpful for the network side to optimize the DAPS handover parameters. This is because the purpose of DAPS handover is to maintain data transmission to the source base station and the target base station at the same time during the handover process, thereby reducing data transmission delay, especially for services with relatively high delay requirements.
  • Fig. 3 is a flowchart showing a method executed by a user equipment according to Embodiment 1 of the present invention.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE when the source base station RLF in the DAPS handover process is monitored, the UE generates and saves link failure information related to the source base station RLF.
  • This embodiment is applicable to the above-mentioned scenarios where the source base station RLF occurs, such as scenarios 1, 6, and so on.
  • step 301 the UE monitors the RLF of the source base station.
  • the UE may consider that the RLF of the source base station has occurred when one or more of the following situations occur: the timer T310 or T312 associated with the source base station for judging radio link failure has expired, and the source
  • the random access problem indication of the MAC entity of the base station receives an indication from the RLF layer of the source base station to indicate that the maximum number of retransmissions has been reached.
  • step 303 the UE saves the RLF information in a link failure report variable (such as VarRLF-Report).
  • a link failure report variable such as VarRLF-Report
  • the storing of the source base station RLF information in the link failure report includes one or more of the following:
  • the failedPCellId field to the cell identity or cell frequency, tracking area code, etc. of the source primary cell where the RLF is monitored.
  • the DAPS handover process refers to the running state of T304 when the UE is configured with any DAPS bearer during the handover process, or after the DAPS handover is successful, T304 stops but the source base station configuration and protocol stack have not been released.
  • the successful handover means that the MAC layer successfully completes the random access process triggered by the handover.
  • the configuration and protocol stack of the source base station not yet released refers to before the UE receives the RRC message for releasing the source base station. In one mode, the field is set to "1" or "TRUE".
  • the target cell identity may be a global cell identity or a tracking area identity, a physical cell identity, a carrier frequency, and the like.
  • the field may also be used to indicate the source base station RLF that occurred during the DAPS handover of the link failure.
  • step 303 is executed.
  • step 301 it also includes that the UE receives the handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • Fig. 4 is a flowchart showing a method executed by a user equipment according to Embodiment 2 of the present invention.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE when the source base station RLF in the DAPS handover process is monitored, similar to the existing mechanism, the UE does not generate and save the link failure information related to the source base station RLF, but directly includes the related failure information in the RRC The message indicates to the target base station.
  • This embodiment is applicable to the above-mentioned scenarios where the source base station RLF occurs, such as scenarios 1, 6, and so on.
  • step 401 the UE monitors the RLF of the source base station.
  • the UE may consider that the RLF of the source base station has occurred when one or more of the following situations occur: the timer T310 or T312 associated with the source base station for judging radio link failure has expired, and the source
  • the random access problem indication of the MAC entity of the base station receives an indication from the RLF layer of the source base station to indicate that the maximum number of retransmissions has been reached.
  • step 403 the UE sends an RRC message containing failure information (RLF information) of the source base station to the target base station.
  • RLF information failure information
  • the RRC message may be an RRC reconfiguration complete message, such as an RRC reconfiguration complete message used to respond to a handover command or an RRC reconfiguration complete message used to respond to an RRC reconfiguration message containing a release instruction from the source base station, or other RRC messages .
  • RRC reconfiguration complete message such as an RRC reconfiguration complete message used to respond to a handover command or an RRC reconfiguration complete message used to respond to an RRC reconfiguration message containing a release instruction from the source base station, or other RRC messages .
  • the source base station failure information includes one or more of the following:
  • timeConnFailure field such as the timeConnFailure field to be the elapsed time from when the handover command is received to when the link failure occurs
  • the DAPS handover process refers to the running state of T304 when the UE is configured with any DAPS bearer during the handover process, or after the DAPS handover is successful, T304 stops but the source base station configuration and protocol stack have not been released.
  • the successful handover means that the MAC layer successfully completes the random access process triggered by the handover.
  • the configuration and protocol stack of the source base station not yet released refers to before the UE receives the RRC message for releasing the source base station.
  • the field is set to "TRUE" or "1", which means that the source base station RLF has occurred during the DAPS handover process.
  • step 403 is executed.
  • step 401 it also includes that the UE receives a handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE when the source base station RLF in the DAPS handover process is monitored, the UE generates and saves the link failure information related to the source base station RLF; when the DAPS handover fails, the UE also generates and saves the link failure related to the handover. Link failure information, but when the link failure information is generated and saved above, the link failure information related to the previous source base station RLF is not cleared. That is to say, the UE is allowed to save the failure reports corresponding to two consecutive link failures respectively.
  • This embodiment is applicable to the above-mentioned scenarios where the source base station RLF occurs, such as scenarios 2, 3, and so on.
  • Fig. 5 is a flowchart showing a method executed by a user equipment according to scenario 3.1 of embodiment 3 of the present invention.
  • the UE performs the following steps to record and save the link failure information.
  • the field settings in the UE recording and saving the link failure information are the same as the existing mechanism, and will not be repeated here.
  • step 501 when a DAPS handover fails, that is, T304 times out, the UE generates and saves the handover failure information (denoted as the first failure information) in the link failure report variable VarRLF-report.
  • the connection failure type field connectionFailureType in the link failure report is set to indicate that the type is DAPS handover failure.
  • the connection failure type field is set to handover failure hof.
  • step 503 if the source primary cell does not detect RLF, the UE falls back to the source base station link and releases the configuration and protocol stack of the target base station.
  • the fallback to the source base station link includes fallback to the RRC configuration used in the source base station, and restores the suspended signaling radio bearer of the source cell.
  • the UE initiates the transmission of a FailureInformation message to the source base station to fall back to the source base station link and inform the source base station that a DAPS handover failure has occurred.
  • step 505 the UE detects that the source base station RLF has occurred. For example, because the failure information message is not sent successfully, such as reaching the maximum number of RLF retransmissions, etc. At this time, the UE does not clear the previous link failure information stored in the link failure report variable VarRLF-report (here recorded as the first failure information), but adds a new item to additionally record and save the source base station RLF Corresponding link failure information (recorded as the second failure information here).
  • the UE determines that the DAPS handover failure of the UE has just occurred before the failure according to the stored first failure information.
  • the connection failure type is determined to be HOF or DAPS HOF
  • the failedPCellId field is the previous DAPS
  • the cell identity of the target primary cell during handover, the previousPCellId field is the cell identity of the current serving cell, or the value of the timeConnFailure field is less than a certain constant value, or the reestablishmentCellId is not included in the first failure information, etc.
  • the UE determines that a DAPS handover failure has occurred just before the failure.
  • the DAPS handover failure of the UE just before the failure may also be judged based on whether the UE has sent a failure information message FailureInformation. If the UE (the most recent period before the occurrence of the link failure) has sent a failure information message FailureInformation message, the UE considers that a DAPS handover failure has just occurred.
  • clearing the first failure information stored in the variable VarRLF-report of the link failure report occurs when the UE determines that no DAPS handover failure has occurred before this link failure.
  • Fig. 6 is a flowchart showing a method executed by a user equipment according to scenario 3.2 of embodiment 3 of the present invention.
  • the UE performs the following steps to record and save the link failure information.
  • the field settings in the UE recording and saving the link failure information are the same as the existing mechanism, and will not be repeated here.
  • step 601 when the UE detects that the source base station link RLF has occurred, the UE generates and saves the link failure information (recorded as the first failure information here) in the link failure report variable VarRLF-report.
  • the link failure information includes a field for indicating that the RLF is the source base station link RLF that occurs in the DAPS handover process.
  • the DAPS handover process refers to the T304 running state when the UE is configured with any DAPS bearer and the handover process is executed.
  • step 603 when the UE detects that the DAPS handover fails, that is, when T304 times out, the UE generates and saves the handover failure information in the link failure report variable VarRLF-report. At this time, the UE does not clear the first failure stored in the variable VarRLF-report of the link failure report, but adds a new item to additionally record and save the link failure information corresponding to the DAPS handover failure (here marked as the second failure) information).
  • the UE after a DAPS handover failure occurs, if the UE has a source base station link failure RLF just before the failure, the UE does not clear the first failure information stored in the link failure report variable VarRLF-report, but adds one New item to additionally record and save the second failure information corresponding to this DAPS switching failure.
  • the source base station RLF occurred just before the DAPS handover failure of the UE.
  • the UE determines that the source base station RLF occurred just before the DAPS handover failure according to the stored first failure information.
  • the UE determines that the source base station RLF occurred just before the failure.
  • the UE may directly determine that the source base station RLF has occurred by judging the current source base station link status, that is, if the source base station has detected the RLF, it determines that the source base station RLF has occurred just before the DAPS handover fails.
  • clearing the first failure information stored in the variable VarRLF-report of the link failure report occurs when the UE determines that the source base station RLF has not occurred before this link failure.
  • step 501 or step 601 it also includes that the UE receives the handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • the UE restores the connection with the network side by triggering the RRC connection re-establishment after a link failure occurs.
  • the UE includes a field for indicating the re-establishment of the cell identity in the first failure information or the second failure information.
  • the UE includes a field for indicating cell re-establishment in both the first failure information and the second failure information.
  • the UE only includes a field for indicating cell re-establishment in the failure information corresponding to the most recent link failure, that is, in the second failure information.
  • Fig. 7 is a flowchart showing a method executed by a user equipment according to Embodiment 4 of the present invention.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE following the rules of the existing mechanism, the UE is not allowed to save the two failure reports corresponding to two consecutive link failures. However, if the consecutive link failure occurs during the DAPS handover, the UE will In addition to recording the failure information corresponding to this RLF according to the existing mechanism, the RLF report also contains some failure information of the previous DAPS handover failure. This embodiment is applicable to scenario 2.
  • the UE performs the following steps to record and save the link failure information.
  • the field settings in the UE recording and saving the link failure information are the same as the existing mechanism, and will not be repeated here.
  • step 701 when a DAPS handover fails, that is, T304 times out. If the source primary cell does not detect RLF, the UE falls back to the source base station link. Optionally, the UE does not generate and save the handover failure information (recorded as the first failure information) in the link failure report variable VarRLF-report at this time.
  • the UE falls back to the source base station link and releases the configuration and protocol stack of the target base station.
  • the fallback to the source base station link includes fallback to the RRC configuration used in the source base station, and restores the suspended signaling radio bearer of the source cell.
  • the UE initiates the transmission of a FailureInformation message to the source base station to fall back to the source base station link and inform the source base station that a DAPS handover failure has occurred.
  • the UE detects that the source base station RLF has occurred. For example, because the failure information message is not sent successfully, such as reaching the maximum number of RLF retransmissions, etc.
  • the UE records and saves the link failure information corresponding to the source base station RLF in a link failure report variable such as VarRLF-Report.
  • the UE clears the stored first failure information.
  • the UE includes a field in the link failure information variable to indicate that the UE has just experienced a DAPS handover failure.
  • the UE includes the target cell identifier of the DAPS handover in the link failure information variable.
  • it also includes random access process information performed in the DAPS handover process.
  • the "source base station” in this step is only used to better describe the method.
  • the UE has released the configuration and protocol stack of the DAPS handover target base station, and ended the handover state, so in step 703
  • the "source base station” may also be referred to as the serving base station, the current base station, or the current MCG, etc.
  • the operation including the DAPS handover failure information in step 703 is performed.
  • the DAPS handover failure of the UE just before the RLF may be judged based on whether the UE has sent a FailureInformation message. If the UE (a short period of time before the occurrence of the link failure) has sent a failure information message FailureInformation, the UE considers that a DAPS handover failure has just occurred. Alternatively, if the UE (a short time before the link failure RLF occurs) has performed the DAPS handover and the DAPS handover failure has occurred, the UE considers that the DAPS handover failure has just occurred.
  • the UE determines based on the first failure information saved in step 701, for example, if the UE has saved first failure information or if the UE saved the first failure information in step 701 and if the first failure information indicates the UE After a DAPS handover failure has been experienced, and the previous PCellId field in the failure information shown in the failure information indicates the identifier related to the cell where the RLF is currently occurring, the UE considers that the DAPS handover failure has just occurred.
  • the link failure report variable includes a field to indicate that the RLF is an RLF that occurred after the DAPS handover fails, or the RLF is a fallback to the source base station link failure after the DAPS handover fails.
  • the field is a connectionFailureType field.
  • step 701 it also includes that the UE receives the handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • Fig. 8 is a flowchart showing a method executed by a user equipment according to Embodiment 5 of the present invention.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE following the rules of the existing mechanism, the UE is not allowed to save the two failure reports corresponding to two consecutive link failures. However, if the consecutive link failure occurs during the DAPS handover, the UE will not check the latest one.
  • the link failure RLF generates a new RLF report (VarRLF-Report), but adds the related failure information of the link failure RLF to the RLF report corresponding to the previous DAPS handover failure.
  • This embodiment is applicable to scenario 2.
  • the UE performs the following steps to record and save the link failure information.
  • the field settings in the UE recording and saving the link failure information when the DAPS handover fails are the same as the existing mechanism, and will not be repeated here.
  • step 801 when a DAPS handover fails, T304 times out. If the source primary cell does not detect RLF, the UE falls back to the source base station link. At this time, the UE reports the variable VarRLF- in the link failure. Generate and save the switching failure information in the report (denoted as the first switching failure information).
  • the UE falls back to the source base station link and releases the configuration and protocol stack of the target base station.
  • the fallback to the source base station link includes fallback to the RRC configuration used in the source base station, and restores the suspended signaling radio bearer of the source cell.
  • the UE initiates the transmission of a FailureInformation message to the source base station to fall back to the source base station link and inform the source base station that a DAPS handover failure has occurred.
  • the UE detects that the source base station RLF has occurred. For example, because the failure information message is not sent successfully, such as reaching the maximum number of RLF retransmissions, etc.
  • the UE records the link failure information corresponding to the source base station RLF in the link failure report variable such as VarRLF-Report as follows: contains a field to indicate that the RLF occurred when the UE fell back to the source base station link after the DAPS handover failed. Or the fallback to the source base station link fails. Optionally, it contains a field indicating the measurement results of the primary cell and neighboring cells that are available when the RLF occurs.
  • it also includes a time field, which is used to indicate the elapsed time between the failure of the DAPS handover in step 801 in the UE and the RLF in step 803.
  • a time field which is used to indicate the elapsed time between the failure of the DAPS handover in step 801 in the UE and the RLF in step 803.
  • it also includes a field to indicate the reason for the RLF.
  • the UE when RLF occurs, the UE does not clear the first failure information stored in the radio link failure report variable in step 801, but in addition to the first failure information stored in the radio link failure report, Contains the above fields.
  • the term "source base station" in this step is just to better describe the method.
  • step 801 the UE has released the configuration and protocol stack of the DAPS handover target base station and ended the handover state, so in step 803
  • the "source base station” may also be referred to as the serving base station, the current base station, or the current MCG, etc.
  • the link failure report variable is generated when the DAPS handover failure in step 801 occurs, and includes related information about the DAPS handover failure; it is not a new link failure report item created in step 803.
  • step 801 it also includes that the UE receives the handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • Fig. 9 is a flowchart showing a method executed by a user equipment according to Embodiment 6 of the present invention.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE following the rules of the existing mechanism, the UE is not allowed to separately save the two failure reports corresponding to two consecutive link failures. However, if the consecutive link failures during the DAPS handover occur, the UE will not report the latest link failure. If the link fails, RLF generates a new RLF report (VarRLF-Report). This embodiment is applicable to scenario 2.
  • the UE performs the following steps to record and save the link failure information.
  • the field settings in the UE recording and saving the link failure information when the DAPS handover fails are the same as the existing mechanism, and will not be repeated here.
  • step 901 when a DAPS handover fails, T304 times out. If the source primary cell does not detect RLF, the UE falls back to the source base station link. At this time, the UE reports the variable VarRLF- in the link failure. Generate and save the switch failure information in the report.
  • the UE falls back to the source base station link and releases the configuration and protocol stack of the target base station.
  • the fallback to the source base station link includes fallback to the RRC configuration used in the source base station, and restores the suspended signaling radio bearer of the source cell.
  • the UE initiates the transmission of a FailureInformation message to the source base station to fall back to the source base station link and inform the source base station that a DAPS handover failure has occurred.
  • the UE detects that the source base station RLF has occurred. For example, because the failure information message is not sent successfully, such as reaching the maximum number of RLF retransmissions, etc. In this case (the RLF occurs when the UE falls back to the source base station link after the DAPS handover fails, or the fallback to the source base station link fails), the UE does not generate a new link for this RLF Failure report, and also do not modify or add information/fields in the saved link failure report variables such as VarRLF-Report.
  • step 901 it also includes that the UE receives the handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • FIG. 10 is a flowchart showing a method executed by a user equipment according to Embodiment 7 of the present invention.
  • This embodiment provides a way for UE to report link failure information during DAPS handover.
  • the UE following the rules of the existing mechanism, the UE is not allowed to separately save the two failure reports corresponding to two consecutive link failures. However, if the consecutive link failure occurs during the DAPS handover, the UE will In addition to recording the failure information corresponding to this DAPS handover failure according to the existing mechanism, the RLF report also contains some failure information of the previous source base station RLF. This embodiment is applicable to scenario 3.
  • the UE performs the following steps to record and save the link failure information.
  • the field settings in the UE recording and saving the link failure information are the same as the existing mechanism, and will not be repeated here.
  • step 1001 the UE monitors the RLF of the source base station.
  • the UE may consider that the RLF of the source base station has occurred when one or more of the following situations occur: the timer T310 or T312 associated with the source base station for judging the radio link failure has expired, and it has received the RLF from the source.
  • the random access problem indication of the MAC entity of the base station receives an indication from the RLF layer of the source base station to indicate that the maximum number of retransmissions has been reached.
  • step 1003 when a DAPS handover fails, that is, T304 times out, the UE generates and saves the handover failure information in the link failure report variable VarRLF-report.
  • the UE also includes the failure information of the source base station RLF in step 1001 in the variable.
  • the source base station failure information includes one or more of the following:
  • step 1001 it also includes that the UE receives the handover command including the DAPS configuration and executes the handover process.
  • the UE performs the above operations when DAPS is configured.
  • the DAPS configured for the UE can also be described as the UE configured with any one or more DAPS bearers; or any one or more DRBs of the UE are configured with DAPS (such as (Identified by the daps-Config information element).
  • the DAPS bearer refers to that the bearer DRB is configured with an information element for indicating daps configuration, such as a daps-config information element.
  • the daps-config information element is configured separately for each DRB.
  • step 1003 when the UE initiates the RRC connection re-establishment process, the source base station failure information is included in the link failure report as in its initialization phase.
  • FIG. 11 is a flowchart showing a method executed by a user equipment according to Embodiment 8 of the present invention.
  • This embodiment is applicable to scenario 4.
  • a DAPS handover fails, if the source base station link of the UE does not detect RLF, the UE falls back to the source base station link. At this time, the UE does not generate a corresponding radio link for the DAPS handover failure event. Link failure report.
  • step 1101 when a DAPS handover fails, that is, T304 times out. If the source primary cell does not detect RLF, the UE does not generate and save the link failure report variable VarRLF-report corresponding to the handover failure. In other words, only when the source cell also monitors the RLF, the UE generates and saves the link failure report variable VarRLF-report corresponding to the handover failure.
  • step 1103 if the source primary cell does not detect the RLF, the UE falls back to the source base station link and releases the configuration and protocol stack of the target base station.
  • the fallback to the source base station link includes fallback to the RRC configuration used in the source base station, and restores the suspended signaling radio bearer of the source cell.
  • the UE initiates the transmission of a FailureInformation message to the source base station to fall back to the source base station link and inform the source base station that a DAPS handover failure has occurred.
  • the failure information message FailureInformation message contains one or more of the following indication information: used to indicate that the failure is a DAPS handover failure; the random access process information in the DAPS handover process; the best quality is measured All available measurement results of one or more cells, the measurement does not include the measurement of the source primary cell.
  • the one or more cells refer to the cells associated with the configured measurement object (such as the measojectNR information element configuration).
  • Fig. 12 is a flowchart showing a method executed by a user equipment according to Embodiment 9 of the present invention.
  • This embodiment proposes a method for the UE to report to the base station that there is more than one radio link failure report available.
  • the UE may include an indication through the RRC message Information, the indication information is used to indicate to the network side that there is more than one available RLF or HOF failure information stored on the UE.
  • the RRC message may be an RRC establishment complete message, an RRC recovery complete message, an RRC re-establishment complete message, an RRC reconfiguration complete message, and the like.
  • the UE performs the above operation.
  • the UE receives a request indication included in an RRC message from the base station, and the request indication is used to request the UE to report one or more stored RLF/HOF information.
  • the request indication information may instruct the UE to report only one RLF/HOF related information; or may instruct the UE to report all stored RLF/HOF related information.
  • the RRC message is a UE Information Request message UEInformationRequest.
  • step 1205 the UE reports one or more stored RLF/HOF related information to the base station through an RRC message.
  • the request indication information in step 1203 instructs the UE to report only one RLF/HOF associated information; then in this step 1205, the UE only reports the failure information associated with the most recent link failure; or if the information in step 1203 is The request instructs the UE to report all stored RLF/HOF related information, and the UE reports all stored RLF/HOF related information to the base station. Alternatively, the UE always reports all stored RLF/HOF related information to the base station.
  • the aforementioned one RLF/HOF associated information refers to failure information associated with an RLF or HOF event.
  • FIG. 13 is used to describe a user equipment that can execute the method executed by the user equipment described in detail above in the present invention as a modified example.
  • Fig. 13 is a block diagram showing a user equipment UE related to the present invention.
  • the user equipment UE130 includes a processor 1301 and a memory 1302.
  • the processor 1301 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 1302 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memories.
  • the memory 1302 stores program instructions. When the instruction is run by the processor 1301, it can execute the above-mentioned method executed by the user equipment described in detail in the present invention.
  • the method and related equipment of the present invention have been described above in conjunction with preferred embodiments. Those skilled in the art can understand that the method shown above is only exemplary. The method of the present invention is not limited to the steps and sequence 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 that can be used for base stations, MMEs, or UEs, and so on.
  • the various identifiers shown above are only exemplary rather than restrictive, and the present invention is not limited to specific information elements as examples of these identifiers. Those skilled in the art can make many changes and modifications based on the teaching of the illustrated embodiment.
  • the program running on the device according to the present invention may be a program that enables the computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or the information processed by the program can be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • the program for realizing the functions of the various embodiments of the present invention can be recorded on a computer-readable recording medium.
  • Corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute these programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically for a short period of time, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • the general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, 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-mentioned embodiment. Although various examples of the embodiment have been described, the present 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提出了一种由用户设备UE执行的方法，包括：当所述UE在执行双激活协议栈DAPS切换的过程中发生DAPS切换失败时，若未监测到源基站无线链路失败即源基站RLF，则所述UE回退到源基站链路，并且不在链路失败报告中生成和保存针对所述DAPS切换失败的切换失败信息；以及在回退到源基站链路时，若所述UE监测到发生了源基站RLF，则所述UE在链路失败报告中记录和保存针对所述源基站RLF的链路失败信息。图3

Description

由用户设备执行的方法以及用户设备 技术领域
本发明涉及无线通信技术领域，更具体地，本发明涉及由用户设备执行的方法以及相应的用户设备。
背景技术
2018年6月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#80次全会上批准了一个5G技术标准的新的研究项目(参见非专利文献：RP-181433：New WID on NR(New Radio)mobility enhancements)以及一个长期演进系统(Long Term Evolution，LTE)Release 16的新研究项目(参见非专利文献：RP-181544)。这两个项目的研究目的之一是找到用于满足移动性需求之一的解决方案：无缝切换，即在更换UE的服务小区的切换过程中能够满足零毫秒或接近零毫秒的切换中断时间。在正在研究的降低切换中断时间的解决方案中，有一种解决方法是双激活协议栈(Dual Active Protocol Stack)机制。在DAPS机制中，UE在收到切换命令后，在执行接入到目标基站的切换过程中并不切断和源基站的链接(数据传输)，而是可以同时维护和目标基站以及源基站之间的连接和数据传输，从而避免切换过程中由于在接入目标基站之前就断开和源基站的连接而产生的对业务中断所带来的时延。
发明内容
为了解决上述问题中的至少一部分，本发明提供了一种由用户设备执行的方法以及用户设备，能够有效执行在LTE/NR系统中DAPS机制下的无线链路失败报告。
根据本发明，提出了一种由用户设备UE执行的方法，包括：当所述UE在执行双激活协议栈DAPS切换的过程中发生DAPS切换失败时，若未监测到源基站无线链路失败即源基站RLF，则所述UE回退到源基站链路，并且不在链路失败报告中生成和保存针对所述DAPS切换失败的切换失败信息；以及在回退到源基站链路时，若所述UE监测到发生了源基站RLF，则所述UE在链路失败报告中记录和保存针对所述源基站RLF的链路失败信息。
优选地，所述回退到源基站链路包括：源基站回退到所使用的无线资源控制RRC配置并恢复源小区的挂起的信令无线承载。
优选地，所述链路失败报告还包括：表示所述UE刚刚经历了所述DAPS切换失败的信息。
优选地，所述链路失败报告还包括：所述DAPS切换的目标小区标识、以及/或者表示所述DAPS切换的过程中执行的随机接入过程的失败的信息。
此外，根据本发明，提出了一种由用户设备UE执行的方法，包括：当所述UE在执行双激活协议栈DAPS切换的过程中发生DAPS切换失败时，若未监测到源基站无线链路失败即源基站RLF，则所述UE回退到源基站链路，并且在链路失败报告中生成和保存针对所述DAPS切换失败的切换失败信息；以及在回退到源基站链路时，若所述UE监测到发生了源基站RLF，则所述UE在所述链路失败报告中记录和保存针对所述源基站RLF的链路失败信息。
优选地，所述回退到源基站链路包括：源基站回退到所使用的无线资源控制RRC配置并恢复源小区的挂起的信令无线承载。
优选地，所述链路失败报告还包含：表示所述UE在所述DAPS切换失败后回退到源基站链路时发生了所述源基站RLF的信息。
另外，根据本发明，提出了一种由用户设备UE执行的方法，包括：所述UE在执行双激活协议栈DAPS切换的过程中监测到发生了源基站无线链路失败即源基站RLF；以及若在发生了所述源基站RLF之后发生了DAPS切换失败，所述UE在链路失败报告中生成和保存 针对所述DAPS切换失败的切换失败信息，其中，所述链路失败报告还包括针对所述源基站RLF的链路失败信息。
优选地，针对所述源基站RLF的所述链路失败信息包含下述的一种或多种：表示从所述UE收到DAPS切换命令到发生所述源基站RLF所经历的时间的信息；表示触发所述源基站RLF的原因的信息；以及表示在执行所述DAPS切换的过程中的发生了所述源基站RLF的信息。
此外，根据本发明，提出了一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据上述的方法。
根据本发明，能够有效执行在LTE/NR系统中DAPS机制下的无线链路失败报告。具体地，能够在LTE/NR系统中由UE执行DAPS切换时发生源小区的无线链路失败(Radio Link Failure，RLF)和/或目标小区的RLF或DAPS切换失败(HandOver Failure，HOF)时有效地记录或上报所述失败相关信息。
附图说明
为了更完整地理解本发明及其优势，现在将参考结合附图的以下描述，其中：
图1是标识一般切换过程示意图。
图2是表示双激活协议栈配置下的用户面协议栈示意图。
图3是示出了根据本发明的实施例1的由用户设备执行的方法的流程图。
图4是示出了根据本发明的实施例2的由用户设备执行的方法的流程图。
图5是示出了根据本发明的实施例3的情形3.1的由用户设备执行的方法的流程图。
图6是示出了根据本发明的实施例3的情形3.2的由用户设备执行的方法的流程图。
图7是示出了根据本发明的实施例4的由用户设备执行的方法的流程图。
图8是示出了根据本发明的实施例5的由用户设备执行的方法的流程图。
图9是示出了根据本发明的实施例6的由用户设备执行的方法的流程图。
图10是示出了根据本发明的实施例7的由用户设备执行的方法的流程图。
图11是示出了根据本发明的实施例8的由用户设备执行的方法的流程图。
图12是示出了根据本发明的实施例9的由用户设备执行的方法的流程图。
图13是示意性示出本发明所涉及的用户设备的框图。
具体实施方式
根据结合附图对本发明示例性实施例的以下详细描述，本发明的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。在附图中，相同或相似的结构均以相同或相似的附图标记进行标识。
在本发明中，术语“包括”和“含有”及其派生词意为包括而非限制；术语“或”是包含性的，意为和/或。
在本说明书中，下述用于描述本发明原理的各种实施例只是说明，不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本发明的示例性实施例。下述描述包括多种具体细节来帮助理解，但这些细节应认为仅仅是示例性的。因此，本领域普通技术人员应认识到，在不背离本发明的范围和精神的情况下，可以对本文中描述的实施例进行多种改变和修改。此外，为了清楚和简洁起见，省略了公知功能和结构的描述。此外，贯穿附图，相同参考数字用于相似功能和操作。
下文以长期演进系统(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)，源主小区(Primary Cell，PCell)，源主小区组MCG；目标小区也可称为目标基站，或目标光束、目标传输点，目标主小区PCell，目标小区组MCG。源小区指的是切换过程发起之前所连接的为UE服务的小区即向UE发送包含切换命令的RRC消息的小区。目标小区指的是切换过程成功完成之后UE所连接的为UE服务的小区，切换命令中所包含的目标小区标识所指示的小区，或描述为切换过程中执行下行同步和随机接入的小区。本发明所述切换命令用于触发UE执行切换，在NR系统中是包含同步重配置(Reconfigurationwithsync)信息元素的RRC重配置消息，更进一步地，是包含用于主小区组(Master Cell Group，MCG)的同步重配置(Reconfigurationwithsync)信息元素的RRC重配置消息。此时，切换也可称为MCG的同步重配置。在LTE系统中是包含移动控制信息(MobilityControlInfo)信息元素的RRC连接重配置消息。其中，所述同步重配置信息元素或移动控制信息信息元素可以包含目标小区的配置信息，例如目标小区标识、目标小区频率、目标小区的公共配置 如系统信息、UE接入到目标小区所使用的随机接入配置、UE在目标小区的安全参数配置、UE在目标小区的无线承载配置等。为便于描述，本发明中RRC重配置消息和RRC连接重配置消息等同；同理，其响应消息RRC重配置完成消息和RRC连接重配置完成消息等同。切换命令和包含切换命令的RRC消息等同，指触发UE执行切换的RRC消息或RRC消息中的配置。切换配置指切换命令中的全部或部分配置。取消、释放、删除、清空和清除等可以替换。执行、使用和应用可替换。配置和重配置可以替换。监测(monitor)和检测(detect)可替换。RRC重建立消息和RRC连接重建立消息等同；同理，其响应消息RRC重建立完成消息和RRC连接重建立完成消息等同。
下列描述了本发明涉及的现有技术中的过程或概念。
NR系统中的切换配置：
在NR系统中，用于切换命令的RRC重配置消息承载着来自目标基站的RRC配置，包含但不限于下述RRC配置(具体请参见3GPP技术标准协议38.331中的6.2.2章节)：
-测量配置(measconfig信息元素)：用于配置UE所执行的频率内、频率间和无线接入技术间的测量。如测量对象配置、测量上报配置、测量空隙(gap)配置等。
-小区组配置(cellGroupConfig信息元素)，用于配置主小区组或辅小区组。包括数据无线承载/信令无线承载对应的无线链路控制(Radio Link Control，RLC)承载配置(rlc-bearerToAddModList信息元素和rlc-bearerToreleaselist信息元素)、媒介接入控制(Medium Access Control，MAC)配置(MAC-cellgroupconfig信息元素)、物理层配置、辅小区添加/修改/释放配置、特殊小区(Special cell，SpCell)配置等。其中，sPCell配置中包含小区索引号、切换信息(reconfigurationWithSync信息元素)、无线链路失败相关定时器及常数配置、无线链路检测(Radio Link Monitoring，RLM)配置、特殊小区专用配置等。其中reconfigurationwithsync信息元素和LTE系统中的移动控制信息类似，包含切换相关信息来实现移动性，其包含服 务小区配置公共信息、UE在目标小区的C-RNTI、切换过程监控定时器T304配置、用于向目标小区随机接入过程的随机接入专用配置等。
-非接入层专用信息(dedicatedInfoNASList信息元素)。
-无线承载配置(radiobearerConfig信息元素)，用于配置无线承载DRB和/或SRB的服务数据应用协议层(Service Data Application Protocol，SDAP)和PDCP。
-主密钥更新配置(masterKeyupdate信息元素)。
下面描述LTE/NR系统中的一般切换过程，具体可参见图1。
连接态的用户移动性主要通过切换过程来实现，所述切换即指的是处于RRC连接态的UE变更服务小区(主小区)的过程。切换过程一般包括如下阶段：
阶段1：测量阶段。基站向用户设备(User Equipment，UE)下发测量配置；UE基于该测量配置对服务小区或邻小区所对应的无线链路进行测量，当满足所配置的测量上报条件时，UE向基站发送测量报告。测量阶段不是必须的，在基站在没有有效测量报告的时候也可以盲切换UE。
阶段2：切换准备阶段。基站结合收到的测量报告以及其他因素如基站负载等决定是否为该UE触发切换。若确定对该UE触发切换，则源基站通过向目标基站发送切换请求消息来发起切换准备过程。目标基站根据切换请求消息中UE的上下文和目标基站的可用资源等因素决定是否接受对该UE的本次切换请求，如果接受，则向源基站回复切换确认消息，其中切换确认消息中包含一条基站间(inter-node)的RRC消息即切换命令。
阶段3：切换执行阶段。源基站将切换命令下发给UE，并开始将该UE的数据转发给目标基站。收到切换命令的UE立即应用该切换命令的配置执行切换，通过随机接入过程接入到目标基站，向目标基站发送确认消息。其中，随机接入过程不是必须的。
阶段4：切换完成阶段。目标基站确认UE成功接入后，向源基站发送切换完成消息。源基站据此可以释放其上所保存的UE上下文。
双激活协议栈(Dual Active Protocol Stack，DAPS)切换：
版本16引入的DAPS切换，指的一种切换过程，UE在收到用于切换的RRC消息后仍维持和源基站之间的连接，直到成功执行到目标的随机接入过程后源基站被释放。在此过程中，对于配置了DAPS的承载，UE继续从源基站接收下行数据直到源基站被释放，用户继续向源基站发送上行数据直到到目标基站的随机接入过程成功完成。向目标基站的随机接入过程完成后，MAC层向上层指示随机接入过程完成，RRC层在收到该指示后，指示下层(如包数据聚合协议(Packet Data Convergence Protocol，PDCP)层)执行上行数据变更，将上行路径从源基站变更为目标基站。当PDCP层被请求了上行数据变更时，PDCP层将PDCP数据协议数据单元(Protocol Data Unit，PDU)PDU递交给目标基站所关联的RLC实体，将关联到源基站的PDCP控制PDU递交给源基站关联的RLC实体，将关联到目标基站的PDCP控制PDU递交给目标基站关联的RLC实体。
在DAPS切换情况下，UE在收到切换命令后，为目标基站建立一个MAC实体，若一个DRB被配置为DAPS承载，则为该DRB建立一个关联到目标基站的RLC实体和专用业务信息(Dedicated Traffic Channel，DTCH)逻辑信道，且对该DAPS承载所关联的PDCP实体重配为DAPS PDCP实体，所述DAPS PDCP实体即在PDCP实体中同时存在分别关联到源基站和目标基站的安全和鲁棒性头压缩(RObust Header Compression，ROHC)功能，且将所述安全和ROHC功能分别关联到源基站和目标基站所配置的对应的RLC实体上。通过上述方式，在DAPS切换过程中，UE同时维护对于源基站和目标基站的激活协议栈，见图2。
在DAPS的过程中，如果源基站发生无线链路失败，则UE会挂起所有源基站的DRB的传输，重置MAC实体，释放源基站的连接。当DAPS切换成功后，UE接收从目标基站发送的RRC重配置消息， 其中携带了用于指示释放源基站的指示信息(如以daps-SourceRelease信息元素标识)，当收到该指示后UE执行释放源基站配置和协议栈的操作，回退到仅和目标基站维持连接的单激活协议栈状态。
当DAPS切换失败，即用于监测切换过程的T304定时器超时，则如果源基站上未监测到无线链路失败，则UE返回到和源基站的连接，通过并告知源基站发生了DAPS切换失败，而不会触发RRC连接重建立过程。在返回和源基站的连接过程中，UE从DAPS状态回退到仅和源基站保持通信的单激活协议栈状态。如果DAPS切换失败时，源基站也监测到了RLF或者处于RLF状态，则UE触发RRC连接重建立过程来进行链路恢复。
下述实施例中，所述DAPS切换可以替换成任意一个DRB被配置为DAPS承载的切换过程。
无线链路失败(Radio Link Failure，RLF)：
UE在下述情况之一发生时，认为发生了RLF：用于RLF监测的定时器T310超时、用于快速RLF监测的定时器T312超时、收到来自MAC层的随机接入问题指示和收到来自RLC实体的用于指示重传次数达到最大数的指示。在DAPS切换时，若上述定时器、MAC实体和RLC是与源基站MCG关联的，则认为监测到了源基站MCG RLF(简称源基站RLF)；若上述定时器、MAC实体和RLC是与目标基站MCG关联的，则认为监测到了目标基站MCG RLF。在单连接或双连接的情况下，若上述定时器、MAC实体和RLC是与MCG关联的，则认为监测到了MCG RLF。在双连接(Dual Connectivity，DC)的时候，UE被配置了辅小区组(Secondary Cell Group，SCG)，若上述定时器、MAC实体和RLC是与SCG关联的，则认为监测到了SCG RLF。
切换失败(HandOver Failure)：
切换失败的判断通过定时器T304的运行状态来实现。UE在发起切换过程，开始执行到目标基站的切换时，开启定时器T304；当切换过程成功时，停止定时器T304，所述切换过程成功指用于响应切换命令的RRC消息如RRC重配置完成消息成功发送或者UE MAC层成功 完成了到目标基站的随机接入过程；若T304超时，则UE认为切换失败，发生了HOF，随后UE通过执行RRC重建立或在有DAPS配置时回退到源基站连接等方式来恢复RRC连接。后续如无特殊说明，所述链路失败可指RLF或HOF，也称连接失败。
现有机制中的无线链路失败报告机制：
当前的LTE系统和版本16的NR系统中，UE会在发生链路失败时生成并保存一个无线链路失败报告(RLF report)，如用于保存无线链路失败报告的UE变量是VarRLF-Report。在恢复与网络侧的连接(如通过RRC重建立过程或RRC建立过程)后，UE可以通过RRC消息告知网络侧其上有可用的无线链路失败报告(如rlf-InfoAvailable信息元素来指示)。如UE可以在RRC连接重建立过程中的RRC重建立完成消息(RRCReestablishmentComplete)中、RRC重配置过程中的RRC重配置完成消息(RRCReconfigurationComplete)中、RRC连接建立过程中的RRC建立完成消息(RRCSetupComplete)中或RRC连接恢复过程中的RRC恢复完成消息(RRCResumeComplete)中告知网络侧UE有保存的可用的无线链路失败报告。网络侧在收到所述指示后，可以通过RRC消息(如UEInformationRequest消息中的rlf-ReportReq信息元素来指示所述请求)来请求UE上报其保存的无线链路失败报告。UE会在响应RRC消息中将所保存的无线链路失败报告(UEInformationResponse消息中的rlf-Report信息元素)上报给网络侧。网络侧获取的所述无线链路失败报告用于网络优化，如网络覆盖和移动鲁棒性优化。无线链路失败报告中可包含：链路失败时可用的源小区和邻居小区的测量结果、位置信息、发生链路失败的主小区标识、链路失败类型(如RLF还是HOF)、RLF理由、从链路失败到上报无线链路失败所经历的时间(timeSinceFailure信息元素)、上次收到切换命令执行切换过程到链路失败所经历的时间(记做timeConnFailure信息元素)、随机接入过程信息等。除此之外，还包括失败后重新连接到网络的小区标识如RRC重建立小区标识、RRC连接建立的小区标识等。所述随机接入过程信息在所述链路失败的原 因是随机接入失败或所述链路失败是切换失败时，被记录在链路失败报告中。一般来说，所述随机接入过程信息中包含：随机接入目的或场景、消息1的频域起始信息(物理随机接入信道PRACH发送时机(occasion)在频域的最低位置与上行带宽部分的零号物理资源块之间的偏移)、PRACH资源的子载波间隔、随机接入过程中关于每次随机接入尝试的的详细信息。每次随机接入尝试的的详细信息又包括所使用的同步信号/物理广播信道块索引值或信道状态信息参考信号索引值、所述索引值对应的波束上所发送的随机接入前导的次数、以及每次随机接入尝试是否监测到了竞争和所述测量的信号质量(Reference Signal Received Power，RSRP)是否高于所配置的门限值。本发明中，链路失败报告、无线链路失败报告、VarRLF-Report和连接失败信息之间可以替换。现有机制中仅支持UE保存一例链路失败报告，也就是说当再一次发生链路失败时，UE会清除所保存的与前一次链路失败相关的链路失败信息(如变量VarRLF-rpeort中的信息)，而仅记录最近一次链路失败所相关的链路失败信息。原因在于，在现有网络中，接续发生的多次链路失败场景并不多，且在两次链路失败之间，网络侧总是能够从UE侧提取到前一次链路失败的信息。
本发明中考虑下述几种链路失败场景：
场景1：UE收到包含DAPS配置的切换命令后，执行DAPS切换过程。在DAPS尚未成功前(即T304处于运行状态)监测到了源基站RLF，随后DAPS切换成功完成。
场景2：UE收到包含DAPS配置的切换命令后，执行DAPS切换过程。随后T304超时发生了DAPS切换失败，此时源基站链路未监测到链路失败，则UE释放目标小区相关配置和协议栈，回退到源基站，向源基站发送包含DAPS失败指示的RRC消息(如FailureInformation)，但随后发生了源基站的链路失败。简言之，在场景1中，UE先发生DAPS切换失败，随后发生源小区链路失败。
场景3：UE收到包含DAPS配置的切换命令后，执行DAPS切 换过程。在DAPS尚未成功前(即T304处于运行状态)监测到了源基站RLF，随后T304超时发生了DAPS切换失败。此时UE发起RRC重建立过程来进行链路恢复。简言之，在场景3中，UE先发生源基站链路失败，随后发生DAPS切换失败。
场景4：UE收到包含DAPS配置的切换命令后，执行DAPS切换过程，随后T304超时发生了DAPS切换失败。此时源基站链路未监测到链路失败，则UE释放目标小区相关配置和协议栈，成功回退到源基站，向源基站发送包含DAPS失败指示的RRC消息(如FailureInformation)。
场景5：UE收到包含DAPS配置的切换命令后，执行DAPS切换过程。在DAPS尚未成功前(即T304处于运行状态)监测到了源基站RLF，随后DAPS切换成功完成。但很快发生了目标基站的RLF。
场景6：UE收到包含DAPS配置的切换命令后，执行DAPS切换过程，且DAPS切换成功。在尚未接收到来自基站的源链路释放指示前，监测到了源基站RLF。
当前机制中，在DAPS切换过程中即T304定时器运行状态下发生的源基站RLF，UE是不予记录其对应的链路失败信息的，即发生源基站RLF时，UE不在VarRLF-report中生成并保存相应的信息。但在DAPS切换过程中，源基站RLF的失败信息对于网络侧优化DAPS的切换参数也是有帮助的。这是因为DAPS切换的目的就是在切换过程中能够同时维持到源基站和目标基站的数据传输，从而降低数据传输延迟，尤其是对时延要求比较高的业务来说。所以在DAPS切换过程中保持源基站链路的正常运行也是很重要的。因此，如何记录DAPS切换过程中的源基站RLF信息是本发明关注的问题。此外，在上述几种场景中如场景2和场景3，UE接连发生两次链路失败，而现有机制仅支持UE记录最近一次链路失败，这使得前一次链路失败的失败信息无法被网络侧获取，从而对DAPS切换的参数优化不利，这也是本发明所关注的问题。本发明对于上述问题通过下述实施例给出了解决方案。
实施例1：
图3是示出了根据本发明的实施例1的由用户设备执行的方法的流程图。
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，当监测到DAPS切换过程中的源基站RLF时，UE生成并保存源基站RLF相关的链路失败信息。该实施例适用于上述发生源基站RLF的场景如场景1、6等。
如图3所示，在步骤301，UE监测到源基站的RLF。
如前所述，UE可以在下述情况中的一种或多种发生时认为发生了源基站的RLF：源基站关联的用于判断无线链路失败的定时器T310或T312超时，收到了来自源基站MAC实体的随机接入问题指示，收到了来自源基站RLF层的用于指示重传的最大数已达到的指示。
在步骤303，UE在链路失败报告变量(如VarRLF-Report)中保存RLF信息。步骤303中，还可包括UE挂起源基站中的所有数据无线承载，释放源基站连接等。
所述在链路失败报告中保存源基站RLF信息，包括下述的一种或多种：
-清空链路失败报告变量中包含的信息；
-设置failedPCellId域为监测到RLF的源主小区的小区标识或小区频率、跟踪区域码等。
-设置previousPCellId域为收到切换命令的源主小区的小区标识和跟踪区域码；
-设置timeConnFailure域为从收到切换命令到发生链路失败所经历的时间；
-设置连接失败类型connectionFailureType域为无线链路失败；
-设置c-RNTI域为在源主小区所使用的小区无线网络临时标识C-RNTI；
-设置链路失败原因字段rlf-cause为触发无线链路失败的原因；
-包含用于指示所述RLF为发生在DAPS切换过程中的源基站链路RLF的字段。所述DAPS切换过程中指的是UE被配置了任何的DAPS承载时执行切换过程时T304正在运行状态，或者在DAPS切换成功T304停止后但尚未释放源基站配置和协议栈。所述切换成功指MAC层成功完成了切换所触发的随机接入过程。所述尚未释放源基站配置和协议栈指在UE收到用于释放源基站的RRC消息之前。在一种方式中，所述字段设置为“1”或“TRUE”。
-包含一个字段用于指示所述DAPS切换的目标小区的标识。所述目标小区标识可以是全球小区标识或跟踪区域标识、物理小区标识和载波频率等。优选地，所述字段还可以用于指示本次链路失败是发生在DAPS切换时的源基站RLF。
-包含一次字段用于指示所述链路失败是否发生在尚未成功接入目标基站的DAPS切换过程中(即T304正在运行)，还是发生在已成功接入目标基站但尚未接收到源基站链路释放指示的DAPS切换过程中。或者可描述为，该字段用于指示所述链路失败是否发生在T304运行过程中。
优选地，当步骤301中T304正在运行时，即UE正处在DAPS切换过程中且尚未成功接入目标基站时，执行步骤303。
显然地，在步骤301之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
实施例2：
图4是示出了根据本发明的实施例2的由用户设备执行的方法的 流程图。
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，当监测到DAPS切换过程中的源基站RLF时，类似现有机制，UE并不生成并保存源基站RLF相关的链路失败信息，而是将相关失败信息直接包含在RRC消息中指示给目标基站。该实施例适用于上述发生源基站RLF的场景如场景1、6等。
如图4所示，在步骤401，UE监测到源基站的RLF。
如前所述，UE可以在下述情况中的一种或多种发生时认为发生了源基站的RLF：源基站关联的用于判断无线链路失败的定时器T310或T312超时，收到了来自源基站MAC实体的随机接入问题指示，收到了来自源基站RLF层的用于指示重传的最大数已达到的指示。
在步骤403，UE向目标基站发送包含源基站失败信息(RLF信息)的RRC消息。
所述RRC消息可以是RRC重配置完成消息，如用于响应切换命令的RRC重配置完成消息或者用于响应包含源基站释放指示的RRC重配置消息的RRC重配置完成消息，也可是其他RRC消息。
所述源基站失败信息包含下述的一种或多种：：
-设置字段如timeConnFailure字段为从收到切换命令到发生链路失败所经历的时间；
-设置链路失败原因字段rlf-cause为触发无线链路失败的原因；
-包含用于指示所述RLF为发生在DAPS切换过程中的源基站链路RLF的字段。所述DAPS切换过程中指的是UE被配置了任何的DAPS承载时执行切换过程时T304正在运行状态，或者在DAPS切换成功T304停止后但尚未释放源基站配置和协议栈。所述切换成功指MAC层成功完成了切换所触发的随机接入过程。所述尚未释放源基站配置和协议栈指在UE收到用于释放源基站的RRC消息之前。在一种方式中，所所述字段设置为“TRUE”或“1”，则表示在DAPS切换过程中发生了源基站RLF。
优选地，当步骤401中T304正在运行时，即UE正处在DAPS切换过程中且尚未成功接入目标基站时，执行步骤403。
显然地，在步骤401之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
实施例3：
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，当监测到DAPS切换过程中的源基站RLF时，UE生成并保存源基站RLF相关的链路失败信息；当发生DAPS切换失败时，UE也生成并保存切换失败相关的链路失败信息，但在上述生成并保存链路失败信息时，并不清除此前的源基站RLF相关的链路失败信息。也就是说允许UE分别保存连续两次链路失败各自对应的失败报告。该实施例适用于上述发生源基站RLF的场景如场景2、3等。
情形3.1
图5是示出了根据本发明的实施例3的情形3.1的由用户设备执行的方法的流程图。
对于先发生DAPS切换失败，然后发生源基站RLF的场景，UE执行下述步骤来记录和保存链路失败信息。所述UE记录和保存链路失败信息中的字段设置和现有机制相同，此处不赘述。
在步骤501，当发生DAPS切换失败时即T304超时，UE在链路失败报告变量VarRLF-report中生成和保存此次切换失败信息(记做第一失败信息)。优选地，所述链路失败报告中的连接失败类型字段connectionFailureType设置为用于指示所述类型为DAPS切换失败。 备选地，所述连接失败类型字段设置为切换失败hof。
在步骤503，源主小区未监测到RLF，则UE回退到源基站链路，释放目标基站的配置和协议栈。所述回退到源基站链路包括回退到在源基站所使用的RRC配置，恢复源小区的挂起的信令无线承载。UE向源基站发起失败信息消息FailureInformation消息的发送，以回退到源基站链路并告知源基站发生了DAPS切换失败。
在步骤505，UE监测到发生了源基站RLF。比如由于Failureinformation消息发送不成功，如达到RLF最大重传次数等。UE此时并不清空链路失败报告变量VarRLF-report中所保存的前一个链路失败的信息(此处记做第一失败信息)，而是增加一个新项来另外记录和保存源基站RLF对应的链路失败信息(此处记做第二失败信息)。也就是说，发生RLF后，若UE在失败之前刚刚发生了DAPS切换失败，则UE并不清空链路失败报告变量VarRLF-report中所保存第一失败信息，而是增加一个新项来另外记录和保存此次RLF对应的第二失败信息。所述UE在失败之前刚刚发生了DAPS切换失败，在一种实现方式中是为UE根据已保存的第一失败信息来确定UE在失败之前刚刚发生了DAPS切换失败。比如，UE上有保存的记录所述DAPS切换失败的第一失败信息，或若所保存的第一链路失败信息中，连接失败类型确定为HOF或DAPS HOF，所述failedPCellId字段是前一次DAPS切换时的目标主小区的小区标识，所述previousPCellId字段是当前服务小区的小区标识，或者所述timeConnFailure字段的值小于某个常数值等，或所述reestablishmentCellId没有包含在所述第一失败信息中等，UE确定在失败之前刚刚发生了DAPS切换失败。备选地，所述UE在失败之前刚刚发生了DAPS切换失败，也可以是UE基于是否发送过失败信息消息FailureInformation消息来判断的。若UE(在发生链路失败之前的最近一段时间)发送过失败信息消息FailureInformation消息，则UE认为刚刚发生了DAPS切换失败。
也就是说，清空链路失败报告变量VarRLF-report中所保存第一失败信息发生在UE确定在本次链路失败之前没有发生DAPS切换失败 的情况下。
情形3.2
图6是示出了根据本发明的实施例3的情形3.2的由用户设备执行的方法的流程图。
对于先发生源基站RLF，然后发生DAPS切换失败的场景，UE执行下述步骤来记录和保存链路失败信息。所述UE记录和保存链路失败信息中的字段设置和现有机制相同，此处不赘述。
在步骤601，当UE监测到发生了源基站链路RLF，UE在链路失败报告变量VarRLF-report中生成和保存此次链路失败信息(此处记做第一失败信息)。优选地，在所述链路失败信息中包含用于指示所述RLF为发生在DAPS切换过程中的源基站链路RLF的字段。优选地，所述DAPS切换过程中指的是UE被配置了任何的DAPS承载时执行切换过程时T304正在运行状态。
在步骤603，UE监测到发生DAPS切换失败时即T304超时，UE在链路失败报告变量VarRLF-report中生成和保存此次切换失败信息。UE此时并不清空链路失败报告变量VarRLF-report中所保存的第一失败，而是增加一个新项来另外记录和保存DAPS切换失败对应的链路失败信息(此处记做第二失败信息)。也就是说，发生DAPS切换失败后，若UE在失败之前刚刚发生了源基站链路失败RLF，则UE并不清空链路失败报告变量VarRLF-report中所保存第一失败信息，而是增加一个新项来另外记录和保存此次DAPS切换失败对应的第二失败信息。所述UE在DAPS切换失败之前刚刚发生了源基站RLF，在一种实现方式中UE根据已保存的第一失败信息来确定在DAPS切换失败之前刚刚发生了源基站RLF。比如，若所保存的第一链路失败信息中相关字段指示了所述failedPCellId字段是本次DAPS切换时的源主小区的小区标识，或所述previousPCellId字段是源主小区的小区标识，或所述reestablishmentCellId没有包含在所述第一失败信息中等，UE确定在失败之前刚刚发生了源基站RLF。备选地，UE可以直接通过判断当前的源基站链路状态来确定发生了源基站RLF，即若源基站已 检测到了RLF，则确定在DAPS切换失败之前刚刚发生了源基站RLF。
也就是说，清空链路失败报告变量VarRLF-report中所保存第一失败信息发生在UE确定在本次链路失败之前没有发生源基站RLF的情况下。
显然地，在步骤501或步骤601之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
可选地，在上述两种情形中，UE在发生链路失败后通过触发RRC连接重建立来恢复和网络侧的链接，在RRC重建立过程中，若选择了一个用于重建立的小区，则UE在第一失败信息或第二失败信息中包含用于指示重建立小区标识的字段。或者UE在第一失败信息和第二失败信息中都包含用于指示重建立小区的字段。可选地，UE仅在最近一次链路失败所对应的失败信息中包含用于指示重建立小区的字段即在第二失败信息中。
实施例4
图7是示出了根据本发明的实施例4的由用户设备执行的方法的流程图。
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，遵循现有机制的准则，不允许UE分别保存连续两次链路失败对应的两项失败报告，但若发生DAPS切换时的连续的链路失败，则UE在最近一次的RLF报告中除了依照现有机制记录本次RLF对应的失败信息外，还包含前一次DAPS切换失败的一些失败信息。该实施例适用于场景2。
在先发生DAPS切换失败，然后发生源基站RLF的场景下，UE 执行下述步骤来记录和保存链路失败信息。所述UE记录和保存链路失败信息中的字段设置和现有机制相同，此处不赘述。
如图7所示，在步骤701，当发生DAPS切换失败时即T304超时，若源主小区未监测到RLF，则UE回退到源基站链路。可选的，此时UE不在链路失败报告变量VarRLF-report中生成和保存此次切换失败信息(记做第一失败信息)。
具体地，源主小区未监测到RLF，则UE回退到源基站链路，释放目标基站的配置和协议栈。所述回退到源基站链路包括回退到在源基站所使用的RRC配置，恢复源小区的挂起的信令无线承载。UE向源基站发起失败信息消息FailureInformation消息的发送，以回退到源基站链路并告知源基站发生了DAPS切换失败。
在步骤703，UE监测到发生了源基站RLF。比如由于Failureinformation消息发送不成功，如达到RLF最大重传次数等。UE在链路失败报告变量如VarRLF-Report中记录和保存源基站RLF对应的链路失败信息。可选的，若步骤701中UE记录了第一失败信息，则UE清除所保存的第一失败信息。此外，UE在链路失败信息变量中包含一个字段用来指示UE刚刚经历了一个DAPS切换失败。优选地，UE在链路失败信息变量中包含所述DAPS切换的目标小区标识。可选地，还包括所述DAPS切换过程中执行的随机接入过程信息。该步骤中称“源基站”只是为了更好地描述所述方法，实际上在步骤701中UE已经释放了DAPS切换目标基站的配置和协议栈，结束了所述切换状态，所以在步骤703中“源基站”也可称为服务基站、当前基站或当前MCG等。
当UE在RLF之前刚刚发生了DAPS切换失败时，执行上述步骤703中包含DAPS切换失败信息的操作。所述UE在RLF之前刚刚发生了DAPS切换失败，可以是UE基于是否发送过失败信息消息FailureInformation消息来判断的。若UE(在发生链路失败之前的一段短时间)发送过失败信息消息FailureInformation消息，则UE认为刚刚发生了DAPS切换失败。或者，也可以是若UE(在发生链路失败 RLF之前的一段短时间)执行过DAPS切换且发生了DAPS切换失败，则UE认为刚刚发生了DAPS切换失败。又或者，UE基于步骤701中保存的第一失败信息来判断，比如若UE有保存的第一失败信息或者若UE在步骤701时保存了第一失败信息且若所述第一失败信息指示UE经历了DAPS切换失败，且所示失败信息中的前序主小区标识previousPCellId字段指示为当前发生RLF的小区相关的标识，则UE认为刚刚发生了DAPS切换失败。
可选地，所述链路失败报告变量中包含一个字段用来指示所述RLF是发生在DAPS切换失败后的RLF，或者所述RLF是DAPS切换失败后回退到源基站链路失败。优选地，所述字段为连接失败类型字段connectionFailureType。
显然地，在步骤701之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
实施例5
图8是示出了根据本发明的实施例5的由用户设备执行的方法的流程图。
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，遵循现有机制的准则，不允许UE分别保存连续两次链路失败对应的两项失败报告，但若发生DAPS切换时的连续的链路失败，则UE并不对最近一次的链路失败RLF生成新的RLF报告(VarRLF-Report)，而是在前一次DAPS切换失败对应的RLF报告中添加此次链路失败RLF的相关失败信息。该实施例适用于场景2。
在先发生DAPS切换失败，然后发生源基站RLF的场景下，UE 执行下述步骤来记录和保存链路失败信息。所述在DAPS切换失败时UE记录和保存链路失败信息中的字段设置和现有机制相同，此处不赘述。
如图8所示，在步骤801，当发生DAPS切换失败时即T304超时，若源主小区未监测到RLF，则UE回退到源基站链路，此时UE在链路失败报告变量VarRLF-report中生成和保存此次切换失败信息(记作第一切换失败信息)。
具体地，源主小区未监测到RLF，则UE回退到源基站链路，释放目标基站的配置和协议栈。所述回退到源基站链路包括回退到在源基站所使用的RRC配置，恢复源小区的挂起的信令无线承载。UE向源基站发起失败信息消息FailureInformation消息的发送，以回退到源基站链路并告知源基站发生了DAPS切换失败。
在步骤803，UE监测到发生了源基站RLF。比如由于Failureinformation消息发送不成功，如达到RLF最大重传次数等。UE在链路失败报告变量如VarRLF-Report中按如下来记录源基站RLF对应的链路失败信息：包含一个字段用来指示UE在DAPS切换失败后回退到源基站链路时发生了RLF，或者所述回退到源基站链路失败。可选地，包含表示发生RLF发生时可用的主小区和邻小区测量结果的字段。可选地，还包括一个时间字段，用于表示UE发生步骤801中DAPS切换失败到步骤803中的RLF之间经历的时间，可选地，还包含一个字段用于表示RLF的原因。该步骤中，UE在发生RLF时，并不清除步骤801中无线链路失败报告变量中所保存的第一失败信息，而是在所述无线链路失败报告所保存的第一失败信息以外，包含上述字段。该步骤中称“源基站”只是为了更好地描述所述方法，实际上在步骤801中UE已经释放了DAPS切换目标基站的配置和协议栈，结束了所述切换状态，所以在步骤803中“源基站”也可称为服务基站、当前基站或当前MCG等。
所述链路失败报告变量是在步骤801中的DAPS切换失败发生时生成的，其中包括所述DAPS切换失败的相关信息；并不是步骤803 中创建的新的链路失败报告项。
显然地，在步骤801之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
实施例6
图9是示出了根据本发明的实施例6的由用户设备执行的方法的流程图。
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，遵循现有机制的准则，不允许UE单独保存连续两次链路失败对应的两项失败报告，但若发生DAPS切换时的连续的链路失败，则UE并不对最近一次的链路失败RLF生成新的RLF报告(VarRLF-Report)。该实施例适用于场景2。
在先发生DAPS切换失败，然后发生源基站RLF的场景下，UE执行下述步骤来记录和保存链路失败信息。所述在DAPS切换失败时UE记录和保存链路失败信息中的字段设置和现有机制相同，此处不赘述。
如图9所示，在步骤901，当发生DAPS切换失败时即T304超时，若源主小区未监测到RLF，则UE回退到源基站链路，此时UE在链路失败报告变量VarRLF-report中生成和保存此次切换失败信息。
具体地，源主小区未监测到RLF，则UE回退到源基站链路，释放目标基站的配置和协议栈。所述回退到源基站链路包括回退到在源基站所使用的RRC配置，恢复源小区的挂起的信令无线承载。UE向源基站发起失败信息消息FailureInformation消息的发送，以回退到源基站链路并告知源基站发生了DAPS切换失败。
在步骤903，UE监测到发生了源基站RLF。比如由于Failureinformation消息发送不成功，如达到RLF最大重传次数等。在这种情况下(UE在DAPS切换失败后回退到源基站链路时发生了RLF，或者所述回退到源基站链路失败)，UE并不生成新的对于本次RLF的链路失败报告，也不对已保存的链路失败报告变量如VarRLF-Report中的信息/字段进行改动或增加。
显然地，在步骤901之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
实施例7
图10是示出了根据本发明的实施例7的由用户设备执行的方法的流程图。
该实施例给出了一种UE在DAPS切换时的链路失败信息上报方式。在该实施例中，遵循现有机制的准则，不允许UE单独保存连续两次链路失败对应的两项失败报告，但若发生DAPS切换时的连续的链路失败，则UE在最近一次的RLF报告中除了依照现有机制记录本次DAPS切换失败对应的失败信息外，还包含前一次源基站RLF的一些失败信息。该实施例适用于场景3。
在先发生源基站RLF，然后发生DAPS切换失败的场景下，UE执行下述步骤来记录和保存链路失败信息。所述UE记录和保存链路失败信息中的字段设置和现有机制相同，此处不赘述。
如图10所示，在步骤1001，UE监测到源基站的RLF。
如前所述，UE可以在下述情况中的一种或多种发生时认为发生了源基站的RLF：源基站关联的用于判断无线链路失败的定时器T310 或T312超时，收到了来自源基站MAC实体的随机接入问题指示，收到了来自源基站RLF层的用于指示重传的最大数已达到的指示。
在步骤1003，当发生DAPS切换失败时即T304超时，UE在链路失败报告变量VarRLF-report中生成和保存此次切换失败信息。除此之外，UE在所述变量中还包括步骤1001中所述源基站RLF的失败信息。所述源基站失败信息包含下述的一种或多种：
-设置一个字段为从收到切换命令到发生源基站RLF链路失败所经历的时间；
-设置另一字段为触发源基站RLF的原因；
-包含用于指示在DAPS切换过程中的发生了源基站链路RLF的字段。所述DAPS切换过程中指的是UE被配置了任何的DAPS承载时执行切换过程时T304正在运行状态。在一种方式中，所述字段设置为“TRUE”或“1”，则表示在DAPS切换过程中发生了源基站RLF。
显然地，在步骤1001之前还包括UE接收包含DAPS配置的切换命令，并执行切换过程。UE在配置了DAPS的情况下执行上述操作，所述UE被配置的DAPS也可以描述为UE被配置了任何一个或多个DAPS承载；或者UE的任何一个或多个DRB被配置了DAPS(如以daps-Config信息元素来标识)。所述DAPS承载指的是所述承载DRB被配置了用于指示daps配置的信息元素如daps-config信息元素。优选地，所述daps-config信息元素是对每一个DRB分别配置的。
在另一种实施方式下，步骤1003中UE在发起RRC连接重建立过程时如其初始化阶段将所述源基站失败信息包含在链路失败报告中。
实施例8
图11是示出了根据本发明的实施例8的由用户设备执行的方法的流程图。
该实施例适用于场景4。在该实施例中，在发生DAPS切换失败时，若UE的源基站链路未监测到RLF，则UE回退到源基站链路， 此时UE并不对此次DAPS切换失败事件生成对应的无线链路失败报告。
如图11所示，在步骤1101，当发生DAPS切换失败时即T304超时，若源主小区未监测到RLF，则UE不生成和保存此次切换失败对应的链路失败报告变量VarRLF-report。换句话说，只有当源小区也监测到了RLF时，UE才生成和保存此次切换失败对应的链路失败报告变量VarRLF-report。
在步骤1103，若源主小区未监测到RLF，则UE回退到源基站链路，释放目标基站的配置和协议栈。所述回退到源基站链路包括回退到在源基站所使用的RRC配置，恢复源小区的挂起的信令无线承载。UE向源基站发起失败信息消息FailureInformation消息的发送，以回退到源基站链路并告知源基站发生了DAPS切换失败。
所述失败信息消息FailureInformation消息中包含如下指示信息的一种或多种：用于指示所述失败为DAPS切换失败；所述DAPS切换过程中的随机接入过程信息；与所测量的质量最好的一个或多个小区的所有可用的测量结果，所述测量不包含对源主小区的测量。优选的，所述一个或多个小区指的是与所配置的测量对象(如measojectNR信息元素配置)所关联的小区。
实施例9
图12是示出了根据本发明的实施例9的由用户设备执行的方法的流程图。
该实施例提出了一种UE向基站上报其上有可用的多于一个无线链路失败报告的方法。
如图12所示，在步骤1201，若UE上的链路失败报告变量(如VarRLF-Report)有保存的多于一个的可用的RLF或HOF的失败信息，UE可以通过RRC消息中包含一个指示信息，所述指示信息用于向网络侧指示UE上有保存的多于一个的可用的RLF或HOF失败信息。所述RRC消息中可以是RRC建立完成消息、RRC恢复完成消息、RRC 重建立完成消息、RRC重配置完成消息等。优选的，当UE的注册公共陆地移动网络(Registered Public Land Mobile Network，RPLMN)被包含在链路失败报告变量中所保存的PLMN标识列表中时，UE执行上述操作。
在步骤1203，UE收到来自基站的包含在RRC消息中的请求指示，所述请求指示用于请求UE上报所保存的一个或多个RLF/HOF信息。优选地，所述请求指示信息可以指示UE仅上报一个RLF/HOF关联的信息；或者可以指示UE上报所有所保存的RLF/HOF关联的信息。优选地，所述RRC消息为UE信息请求消息UEInformationRequest。
在步骤1205，UE通过RRC消息向基站上报所保存的一个或多个RLF/HOF关联的信息。优选地，若步骤1203中所述请求指示信息指示UE仅上报一个RLF/HOF关联的信息；则该步骤1205中，UE仅上报关联到最近一次链路失败的失败信息；或者若步骤1203中所述请求指示UE上报所有所保存的RLF/HOF关联的信息，则UE向基站上报所保存的所有RLF/HOF关联的信息。备选地，UE总是向基站上报所保存的所有RLF/HOF关联的信息。
上述一个RLF/HOF关联的信息指的是一次RLF或HOF事件所关联的失败信息。
[变形例]
下面，利用图13来说明作为一种变形例的可执行本发明上面所详细描述的用户设备执行的方法的用户设备。
图13是表示本发明所涉及的用户设备UE的框图。
如图13所示，该用户设备UE130包括处理器1301和存储器1302。处理器1301例如可以包括微处理器、微控制器、嵌入式处理器等。存储器1302例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器1302上存储有程序指令。该指令在由处理器1301运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
值得说明的是，不同实施例之间并不是互相排斥的方案，也就是说，不同实施例是对于本发明所述问题的不同方面给出的方法，其在一个系统中是可以协同工作的。
上文已经结合优选实施例对本发明的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的。本发明的方法并不局限于上面示出的步骤和顺序。上面示出的基站和用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本发明并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控 制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备UE执行的方法，包括：
    当所述UE在执行双激活协议栈DAPS切换的过程中发生DAPS切换失败时，若未监测到源基站无线链路失败即源基站RLF，则所述UE回退到源基站链路，并且不在链路失败报告中生成和保存针对所述DAPS切换失败的切换失败信息；以及
    在回退到源基站链路时，若所述UE监测到发生了源基站RLF，则所述UE在链路失败报告中记录和保存针对所述源基站RLF的链路失败信息。
  2. 根据权利要求1所述的方法，其中，
    所述回退到源基站链路包括：源基站回退到所使用的无线资源控制RRC配置并恢复源小区的挂起的信令无线承载。
  3. 根据权利要求1所述的方法，其中，
    所述链路失败报告还包括：表示所述UE刚刚经历了所述DAPS切换失败的信息。
  4. 根据权利要求3所述的方法，其中，
    所述链路失败报告还包括：所述DAPS切换的目标小区标识、以及/或者表示所述DAPS切换的过程中执行的随机接入过程的失败的信息。
  5. 一种由用户设备UE执行的方法，包括：
    当所述UE在执行双激活协议栈DAPS切换的过程中发生DAPS切换失败时，若未监测到源基站无线链路失败即源基站RLF，则所述UE回退到源基站链路，并且在链路失败报告中生成和保存针对所述DAPS切换失败的切换失败信息；以及
    在回退到源基站链路时，若所述UE监测到发生了源基站RLF，则所述UE在所述链路失败报告中记录和保存针对所述源基站RLF的链路失败信息。
  6. 根据权利要求5所述的方法，其中，
    所述回退到源基站链路包括：源基站回退到所使用的无线资源控制RRC配置并恢复源小区的挂起的信令无线承载。
  7. 根据权利要求5所述的方法，其中，
    所述链路失败报告还包含：表示所述UE在所述DAPS切换失败后回退到源基站链路时发生了所述源基站RLF的信息。
  8. 一种由用户设备UE执行的方法，包括：
    所述UE在执行双激活协议栈DAPS切换的过程中监测到发生了源基站无线链路失败即源基站RLF；以及
    若在发生了所述源基站RLF之后发生了DAPS切换失败，所述UE在链路失败报告中生成和保存针对所述DAPS切换失败的切换失败信息，
    其中，所述链路失败报告还包括针对所述源基站RLF的链路失败信息。
  9. 根据权利要求8所述的方法，其中，
    针对所述源基站RLF的所述链路失败信息包含下述的一种或多种：
    表示从所述UE收到DAPS切换命令到发生所述源基站RLF所经历的时间的信息；
    表示触发所述源基站RLF的原因的信息；以及
    表示在执行所述DAPS切换的过程中的发生了所述源基站RLF的信息。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中的任一项所述的方法。
PCT/CN2021/098603 2020-06-18 2021-06-07 由用户设备执行的方法以及用户设备 WO2021254197A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21825252.6A EP4171115A1 (en) 2020-06-18 2021-06-07 Method executed by user equipment and user equipment
US18/009,751 US20230262565A1 (en) 2020-06-18 2021-06-07 Method performed by user equipment, and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010562707.7A CN113825182A (zh) 2020-06-18 2020-06-18 由用户设备执行的方法以及用户设备
CN202010562707.7 2020-06-18

Publications (1)

Publication Number Publication Date
WO2021254197A1 true WO2021254197A1 (zh) 2021-12-23

Family

ID=78924622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/098603 WO2021254197A1 (zh) 2020-06-18 2021-06-07 由用户设备执行的方法以及用户设备

Country Status (4)

Country Link
US (1) US20230262565A1 (zh)
EP (1) EP4171115A1 (zh)
CN (1) CN113825182A (zh)
WO (1) WO2021254197A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116847390A (zh) * 2022-03-25 2023-10-03 夏普株式会社 无线链路失败信息报告方法以及用户设备
CN117750447A (zh) * 2022-09-15 2024-03-22 夏普株式会社 由用户设备执行的方法以及用户设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103298004A (zh) * 2012-02-28 2013-09-11 北京三星通信技术研究有限公司 汇报无线链路失败信息的方法
WO2020088592A1 (en) * 2018-10-31 2020-05-07 Mediatek Singapore Pte. Ltd. Reordering with dual protocol to reduce mobility interruption in wireless network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103298004A (zh) * 2012-02-28 2013-09-11 北京三星通信技术研究有限公司 汇报无线链路失败信息的方法
WO2020088592A1 (en) * 2018-10-31 2020-05-07 Mediatek Singapore Pte. Ltd. Reordering with dual protocol to reduce mobility interruption in wireless network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TECHNICAL STANDARD PROTOCOL 38.331
ERICSSON: "Summary of AI 8.13.2.1 - Handover related SON aspects", 3GPP TSG-RAN WG2 #112-E R2-2010995, vol. RAN WG2, no. 2020-11-02 to 2020-11-13, 16 November 2020 (2020-11-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 40, XP009533180 *
VIVO: "Discussion on the RLF and HOF for DAPS", 3GPP DRAFT; R2-1909775 DISCUSSION ON THE RLF AND HOF FOR DAPS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 8, XP051767570 *

Also Published As

Publication number Publication date
EP4171115A1 (en) 2023-04-26
CN113825182A (zh) 2021-12-21
US20230262565A1 (en) 2023-08-17

Similar Documents

Publication Publication Date Title
EP3562208B1 (en) User mobility method and device
WO2021190608A1 (zh) 无线链路失败报告方法以及用户设备
US11665599B2 (en) Light-weight RRC connection setup in multi-rat network
WO2021115370A1 (zh) 无线链路失败恢复方法以及用户设备
WO2020249081A1 (zh) 无线链路失败恢复方法以及用户设备
WO2021227881A1 (zh) 无线链路失败恢复方法及对应的用户设备
WO2020221193A1 (zh) 条件切换方法及对应的用户设备
WO2021057702A1 (zh) 无线链路失败恢复方法以及用户设备
WO2021013170A1 (zh) 无线链路失败恢复方法以及用户设备
WO2011000280A1 (zh) 检测过早切换方法、基站及系统
WO2022012363A1 (zh) 切换信息报告方法及用户设备
WO2022057783A1 (zh) 无线链路失败报告方法以及用户设备
WO2021254197A1 (zh) 由用户设备执行的方法以及用户设备
WO2023134763A1 (zh) 信息报告方法以及用户设备
WO2023040955A1 (zh) 切换信息报告方法以及用户设备
WO2022257974A1 (zh) 切换信息报告方法、用户设备以及通信系统
WO2024017237A1 (zh) 由用户设备执行的方法以及用户设备
WO2024008076A1 (zh) 切换信息报告方法以及用户设备
WO2023005967A1 (zh) 切换信息报告方法以及用户设备
WO2024094056A1 (zh) 信息报告方法以及用户设备
WO2024067624A1 (zh) 信息报告方法以及用户设备
WO2023246770A1 (zh) 由用户设备执行的方法以及用户设备
WO2023241622A1 (zh) 由用户设备执行的方法、用户设备以及信息报告方法
WO2023179677A1 (zh) 无线链路失败信息报告方法以及用户设备
WO2024027704A1 (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: 21825252

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

Country of ref document: EP

Effective date: 20230118