A method, apparatus, and communication device for handling wireless link failures.

Abstract

This application provides a method, apparatus, and communication device for handling wireless link failure. The method includes: a terminal device determining that an MCG wireless link failure has occurred while the SCG is in a deactivated state; the terminal device triggering an RRC connection reconstruction process or a fast recovery process for the MCG.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, specifically to a method, apparatus, and communication device for handling wireless link failures. Background Technology

[0002] In the event of a radio link failure in the Master Cell Group (MCG), the MCG can be quickly restored via the link on the Secondary Cell Group (SCG) side. However, the SCG can be in an active or deactivated state. If the SCG is in a deactivated state, the terminal device cannot quickly restore the MCG via the SCG-side link in the event of an MCG radio link failure. How to restore the MCG is a problem that needs to be solved. Summary of the Invention

[0003] This application provides a method, apparatus, and communication device for handling wireless link failures.

[0004] The method for handling wireless link failure provided in this application includes:

[0005] The terminal device determined that an MCG radio link failure occurred while the SCG was in a deactivated state.

[0006] The terminal device triggers the Radio Resource Control (RRC) connection reconstruction process of the MCG or the fast recovery process of the MCG.

[0007] The method for handling wireless link failure provided in this application includes:

[0008] The terminal device has determined that an MCG radio link failure has occurred;

[0009] The terminal device sends a first message to the SCG and starts a first timer. The first message is used to trigger the fast recovery process of the MCG.

[0010] If the terminal device receives an SCG deactivation command before the first timer expires, the terminal device triggers the RRC connection reconstruction process.

[0011] The apparatus for handling wireless link failures provided in this application embodiment is applied to a terminal device, and the apparatus includes:

[0012] A determination unit is used to determine that an MCG radio link failure has occurred while the SCG is in a deactivated state.

[0013] The communication unit is used to trigger the MCG's RRC connection reconstruction process or the MCG's fast recovery process.

[0014] The apparatus for handling wireless link failures provided in this application embodiment is applied to a terminal device, and the apparatus includes:

[0015] A determination unit, used to determine when an MCG radio link failure has occurred;

[0016] A communication unit is used to send a first message to the SCG, the first message being used to trigger the MCG's fast recovery process;

[0017] The control unit is configured to start a first timer after the communication unit sends a first message to the SCG;

[0018] The communication unit is further configured to trigger the RRC connection reconstruction process if an SCG deactivation command is received before the first timer expires.

[0019] The communication device provided in this application includes a processor and a memory. The memory stores computer programs, and the processor calls and runs the computer programs stored in the memory to perform the aforementioned method for handling wireless link failures.

[0020] The chip provided in this application embodiment is used to implement the above-described method for handling wireless link failures.

[0021] Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the aforementioned method for handling wireless link failures.

[0022] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to perform the above-described method for handling wireless link failure.

[0023] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described method for handling wireless link failure.

[0024] The computer program provided in this application embodiment, when run on a computer, causes the computer to perform the above-described method for handling wireless link failure.

[0025] Through the above technical solution, on the one hand, in the event of an MCG radio link failure, if the SCG is in a deactivated state, the terminal device directly initiates an RRC connection reconstruction process or initiates a random access procedure to the SCG and then performs rapid MCG recovery based on the SCG, thereby achieving either RRC connection reconstruction or rapid MCG recovery. On the other hand, in the event of an MCG radio link failure, if the terminal device receives an SCG deactivation command during the first timer period corresponding to rapid MCG recovery, the terminal device initiates an RRC connection reconstruction process, thereby achieving RRC connection reconstruction of the MCG. Attached Figure Description

[0026] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0027] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this application;

[0028] Figure 2 This is a flowchart illustrating the RRC connection reconstruction process provided in an embodiment of this application;

[0029] Figure 3 This is a schematic diagram illustrating the use of the Split SRB1 on the SCG side to trigger the fast MCG recovery process, as provided in an embodiment of this application.

[0030] Figure 4 This is a schematic diagram illustrating the use of SRB3 on the SCG side to trigger the fast MCG recovery process, as provided in an embodiment of this application.

[0031] Figure 5 This is a flowchart illustrating the method for handling wireless link failures provided in the embodiments of this application. Figure 1 ;

[0032] Figure 6 This is a flowchart illustrating the method for handling wireless link failures provided in the embodiments of this application. Figure 2 ;

[0033] Figure 7 This is a schematic diagram of the structural composition of the device for handling wireless link failures provided in the embodiments of this application. Figure 1 ;

[0034] Figure 8 This is a schematic diagram of the structural composition of the device for handling wireless link failures provided in the embodiments of this application. Figure 2 ;

[0035] Figure 9 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0036] Figure 10 This is a schematic structural diagram of the chip according to an embodiment of this application;

[0037] Figure 11 This is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0039] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5G communication systems, or future communication systems.

[0040] For example, the communication system 100 used in the embodiments of this application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminals located within that coverage area. Optionally, the network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or network equipment in a future communication system, etc.

[0041] The communication system 100 also includes at least one terminal 120 located within the coverage area of ​​network device 110. As used herein, "terminal" includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and / or another terminal. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. A terminal can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in future PLMNs, etc.

[0042] Optionally, the terminals 120 can communicate directly with each other via Device to Device (D2D).

[0043] Alternatively, 5G communication systems or 5G networks may also be referred to as New Radio (NR) systems or NR networks.

[0044] Figure 1 An exemplary network device and two terminals are shown. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area. This application embodiment does not limit this.

[0045] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0046] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities. This application embodiment does not limit this.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0048] To facilitate understanding of the technical solutions in the embodiments of this application, the technical solutions related to the embodiments of this application will be described below.

[0049] With people's pursuit of speed, latency, high-speed mobility, and energy efficiency, and the increasing diversity and complexity of business in future life, the third-generation partnership program (3GPP) is therefore being developed. rd The Generation Partnership Project (3GPP) international standards organization has begun developing 5G. The main application scenarios for 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0050] On the one hand, eMBB still aims to provide users with multimedia content, services, and data, and its demand is growing rapidly. On the other hand, because eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, its capabilities and needs vary considerably. Therefore, generalizations cannot be made; a detailed analysis based on the specific deployment scenario is necessary. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety assurance. Typical characteristics of mMTC include high connection density, small data volume, latency-insensitive services, low module cost, and long service life.

[0051] In the early stages of NR deployment, complete NR coverage was difficult to achieve, so typical network coverage consisted of wide-area LTE coverage and isolated NR coverage. Furthermore, a large portion of LTE deployment was below 6 GHz, leaving very little spectrum available for 5G below 6 GHz. Therefore, NR had to explore spectrum applications above 6 GHz, but high-frequency band coverage was limited and signal fading was rapid. Simultaneously, to protect mobile operators' initial investments in LTE, a tight interworking working mode between LTE and NR was proposed.

[0052] To expedite 5G network deployment and commercial applications, 3GPP completed its first 5G release, E-UTRA-NR Dual Connectivity (EN-DC), by the end of December 2017. In EN-DC, the LTE base station (eNB) acts as the Master Node (MN), and the NR base station (gNB or en-gNB) acts as the Secondary Node (SN). The MN primarily handles RRC control functions and the control plane for communication with the core network; the SN can be configured with auxiliary signaling, such as SRB3, mainly providing data transmission functions.

[0053] Later in Release 15, other dual connectivity (DC) modes will be supported, namely NR-E-UTRA dual connectivity (NE-DC), 5GC-EN-DC, and NR DC. For EN-DC, the core network for access network connection is the Evolved Packet Core network (EPC), while the core network for other DC modes is the 5G Core Network (5GC).

[0054] In R15, when an MCG experiences a radio link failure (or simply an MCG failure), the RRC connection reconstruction process is triggered, as described above. Figure 2, Figure 2 A flowchart illustrating the RRC connection reconstruction process is provided, including the following steps:

[0055] Step 201: The terminal device sends an RRC connection reconstruction request message to the network.

[0056] Step 202: The network sends an RRC connection rebuild message to the terminal device.

[0057] Step 203: The terminal device sends an RRC connection reconstruction complete message to the network.

[0058] It should be noted that the "RRC Connection Re-establishment Request Message" can also be called the "RRC Re-establishment Request Message (RRCReestablishmentRequest)".

[0059] It should be noted that the "RRC connection reconstruction message" can also be called the "RRC Reestablishment message (RRCReestablishment)".

[0060] It should be noted that the "RRC connection reconstruction complete message" can also be called the "RRC reconstruction complete message (RRCReestablishmentComplete)".

[0061] Table 1 below lists the contents carried in the RRC connection re-establishment request message. The RRC connection re-establishment request message carries the re-establishment cause. In addition, the RRC connection re-establishment request message also carries the following: Cell-Radio Network Temporary Identifier (C-RNTI), Physical Cell Identity (PCI), and Short Message Authentication Code-Integrity (shortMAC-I). Furthermore,

[0062]

[0063] Table 1

[0064] To address scenarios where the MCG fails while the SCG signal remains strong, and to avoid RRC connection reconstruction in such cases and reduce service interruptions, Release 16 introduced the fast MCG recovery feature. Specifically, in the event of an MCG radio link failure, the terminal device sends an MCG failure information (MCGFailureInformation) through the SCG link, triggering the network side to quickly restore the MCG link.

[0065] It should be noted that MCG fast recovery can only be triggered if AS security is activated and at least one of SRB2 and split SRB1 is established. MCG failure information can be sent via Split SRB1 or SRB3 on the SCG side. MCGFailureInformation will only be reported using SRB3 if Split SRB1 is not configured and SRB3 is configured.

[0066] After sending the MCGFailureInformation, the terminal device starts a Guard timer (T316) and waits for a response from the network side. The network response message can be either a "reconfiguration with sync" or an "RRC Release" message. If the terminal device receives the response message, it stops the Guard timer. If the Guard timer times out, the terminal device triggers an RRC connection reconstruction process, in which case the reconstruction reason value in the RRC connection reconstruction request is set to "otherFailure".

[0067] The terminal device can only trigger the fast MCG recovery process after the network side has displayed the configuration. This is done by configuring the Guard timer (the network side configures the Guard timer through RRC dedicated signaling) to indicate to the terminal device that the fast MCG recovery process can be initiated.

[0068] When the fast MCG recovery process is triggered, the terminal device sends an MCGFailureInformation. At this time, the terminal device performs the following actions: 1. Suspends transmissions on MCG-side SRBs and DRBs, except for SRB0; 2. Resets the MCG MAC; 3. Saves the measurement configurations from the MCG and SCG sides, and if possible, continues measurements according to the MCG and SCG side measurement configurations. If the terminal device receives a response from the network side, it resumes transmissions on the MCG side.

[0069] Reference Figure 3 , Figure 3A schematic diagram is provided illustrating how a terminal device triggers a fast MCG recovery process using Split SRB1 on the SCG side. The uplink path of Split SRB1 is: Terminal device → MAC layer on the SCG side → RLC layer on the SCG side → PDCP layer on the MCG side → RRC layer on the MCG side. The downlink path is: RRC layer on the MCG side → PDCP layer on the MCG side → RLC layer on the SCG side → MAC layer on the SCG side → Terminal device. The terminal device uses Split SRB1 to send an MCG failure information (MCGFailureInformation) message to the network, and also uses Split SRB1 to receive network responses such as reconfiguration with sync or RRC release messages.

[0070] It should be noted that if the PDCP duplication function of split SRB1 is activated, there is no need to switch the primary path when the terminal device detects an MCG failure. If the PDCP duplication function of split SRB1 is not activated, the primary path is implicitly configured to the SCG side. During MCG recovery or RRC connection reconstruction, the terminal device expects the network side to explicitly configure the primary path to the MCG.

[0071] Reference Figure 4 , Figure 4 A schematic diagram is provided illustrating how a terminal device triggers a fast MCG recovery process using SRB3 on the SCG side. The uplink path of SRB3 is: Terminal device → SCG-side MAC layer → SCG-side RLC layer → SCG-side PDCP layer → SCG-side RRC layer → MCG. The downlink path of SRB3 is: MCG → SCG-side RRC layer → SCG-side PDCP layer → SCG-side RLC layer → SCG-side MAC layer → Terminal device. The terminal device uses SRB3 to send an MCG failure information (MCGFailureInformation) message to the network, and to enable SRB3 to receive a network response of either reconfiguration with sync or RRC release.

[0072] As an example, the content of an MCG failure information message includes at least one of the following: measurement results available on the MCG side; the reason for the MCG link failure; measurement results available on the SCG side; and measurement results available for the non-serving cell.

[0073] The aforementioned rapid MCG recovery process is performed under the default condition that the SCG is active. However, the SCG can be active or deactivated. If the SCG is deactivated, the terminal device cannot quickly recover the MCG via the SCG-side link in the event of a wireless link failure. How to perform MCG recovery is a problem that needs to be solved. To address this, the following technical solution is proposed according to embodiments of this application.

[0074] It should be noted that in the embodiments of this application, "fast MCG recovery" and "MCG fast recovery" have the same meaning and can be used interchangeably.

[0075] It should be noted that in the embodiments of this application, the description of "MCG side" can also be referred to as "MN side", and the description of "SCG side" can also be referred to as "SN side".

[0076] The technical solutions of this application can be applied to a DC architecture, where the primary node in the DC is MN, the secondary node in the DC is SN, the cell group on the MN side is called MCG, and the cell group on the SN side is called SCG. This application does not limit the type of DC; for example, it can be MR-DC, EN-DC, NE-DC, NR-DC, etc. Of course, the technical solutions of this application can also be applied to multi-connectivity architectures.

[0077] Figure 5 This is a flowchart illustrating the method for handling wireless link failures provided in the embodiments of this application. Figure 1 ,like Figure 5 As shown, the method for handling wireless link failures includes the following steps:

[0078] Step 501: The terminal device determines that an MCG radio link failure has occurred while the SCG is in a deactivated state.

[0079] Step 502: The terminal device triggers the Radio Resource Control (RRC) connection reconstruction process of the MCG or the fast recovery process of the MCG.

[0080] In this embodiment of the application, the terminal device is configured in DC mode, such as MR-DC mode.

[0081] In some optional implementations, if the SCG is in a deactivated state, the terminal device triggers an RRC connection reconstruction process in the event of a radio link failure in the MCG. Here, the terminal device may or may not be configured to trigger a fast MCG recovery process. Specifically, the terminal device is implicitly configured to trigger a fast MCG recovery process via a Guard timer (T316). That is, if the network side configures timer T316, the terminal device is considered capable of triggering a fast MCG recovery process; if the network device does not configure timer T316, the terminal device is considered incapable of triggering a fast MCG recovery process. Regardless of whether the network device configures timer T316, if the SCG is in a deactivated state, the terminal device triggers an RRC connection reconstruction process in the event of a radio link failure in the MCG.

[0082] In some alternative implementations, if the SCG is in a deactivated state, the terminal device triggers a fast recovery process for the MCG in the event of a wireless link failure in the MCG. Specifically, the terminal device initiates a random access procedure to the SCG and performs a fast recovery of the MCG based on the SCG, thereby ensuring the fast recovery of the MCG.

[0083] Here, the terminal device initiates a random access procedure to the SCG and performs a fast recovery of the MCG based on the SCG, including: the terminal device sending a first message to the SCG, the first message being carried in MSG3 during the random access procedure; the terminal device receiving an RRC reconfiguration message or an RRC release message sent by the SCG, the RRC reconfiguration message carrying synchronization reconfiguration (reconfiguration with sync), the RRC reconfiguration message or RRC release message being sent by the MCG to the SCG.

[0084] In some optional embodiments, the terminal device is configured with a first timer; after the terminal device sends the first message to the SCG, it starts the first timer; if the terminal device receives the RRC reconfiguration message or the RRC release message before the first timer expires, the terminal device stops the first timer.

[0085] Here, the first timer is configured by the network device; optionally, the first timer is configured by the network device via RRC signaling. The first timer can also be called a Guard timer or Timer T316, and the Guard timer or Timer T316 can be referred to in the description of the aforementioned related solutions.

[0086] Here, as an example, the content of the RRC reconfiguration message can be seen in Table 2 below.

[0087]

[0088] Table 2

[0089] The following describes how terminal devices can quickly access the MCG recovery process, categorized by scenario.

[0090] Scenario 1: The first message is an RRC connection reconstruction request message.

[0091] The terminal device sends an RRC connection reconstruction request message to the SCG, which is carried in the MSG3 during the random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, where the RRC reconfiguration message carries a synchronization reconfiguration (reconfiguration with sync), and the RRC reconfiguration message or RRC release message is sent to the SCG by the MCG.

[0092] In some alternative implementations, the RRC connection rebuild request message carries at least one of the following:

[0093] The first C-RNTI is the C-RNTI assigned by MCG to the terminal device;

[0094] The first PCI is the PCI of the primary cell PCell in the MCG;

[0095] The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm.

[0096] In some alternative implementations, the RRC connection rebuild request message carries a rebuild reason, which indicates at least one of the following:

[0097] The reason for the reconstruction was a wireless link failure in the MCG;

[0098] The purpose of reconstruction is to activate SCG;

[0099] The purpose of reconstruction is to rapidly restore the MCG based on the SCG.

[0100] In some optional implementations, after the terminal device sends an RRC connection reconstruction request message to the SCG, the terminal device receives an SCG activation confirmation message or an RRC connection reconstruction message sent by the SCG; wherein, the SCG activation confirmation message is prepared and sent by the SCG; or, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

[0101] Here, when the SCG activation confirmation message is prepared by the MCG, the SCG activation confirmation message is prepared by the MCG after the MCG failure message or RRC connection reconstruction message is sent by the SCG to the MCG.

[0102] Scenario 2: The first message is an MCG failure information (MCGFailureInformation) message.

[0103] The terminal device sends an MCG failure information message to the SCG, and the MCG failure information message is carried in MSG3 during the random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, the RRC reconfiguration message carries synchronization reconfiguration (reconfiguration with sync), and the RRC reconfiguration message or RRC release message is sent by the MCG to the SCG.

[0104] In some alternative implementations, the MCG failure message carries first information from the MCG side or second information from the SCG side.

[0105] When the MCG failure message carries first information from the MCG side, the first information is forwarded by the SCG to the MCG, and the MCG verifies the identity of the terminal device based on the first information. Alternatively, when the MCG failure message carries second information from the SCG side, the SCG verifies the identity of the terminal device based on the second information.

[0106] In some alternative implementations, the first information on the MCG side includes at least one of the following:

[0107] The first C-RNTI is the C-RNTI assigned by MCG to the terminal device;

[0108] The first PCI is the PCI of the PCell in the MCG;

[0109] The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm.

[0110] In some alternative implementations, the second information on the SCG side includes at least one of the following:

[0111] The second C-RNTI is the C-RNTI assigned by SCG to the terminal device;

[0112] The second PCI is the PCI of PSCell in SCG;

[0113] The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

[0114] In some optional implementations, after the terminal device sends an MCG failure information message to the SCG, the terminal device receives an SCG activation message sent by the SCG; wherein the SCG activation message is prepared and sent by the SCG; or, the SCG activation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

[0115] In some optional implementations, when the SCG activation message is prepared by the MCG, the SCG activation message is prepared by the MCG after the MCG failure message or the content of the MCG failure message is sent by the SCG to the MCG.

[0116] Here, the content of the MCG failure message includes at least one of the following: measurement results available on the MCG side; the reason for the MCG link failure; measurement results available on the SCG side; and measurement results available for the non-serving cell.

[0117] In some alternative implementations, the SCG activation message carries a reason for activating the SCG, the reason for activating the SCG indicating at least one of the following:

[0118] The reason for activation is that the MCG experienced a wireless link failure;

[0119] The purpose of activation is to activate SCG;

[0120] The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

[0121] Scenario 3: The first message is an SCG activation request message.

[0122] The terminal device sends an SCG activation request message to the SCG, which is carried in the MSG3 during the random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, the RRC reconfiguration message carrying synchronization reconfiguration, and the RRC reconfiguration message or RRC release message being sent to the SCG by the MCG.

[0123] In some alternative implementations, the SCG activation request message carries first information from the MCG side or second information from the SCG side.

[0124] When the SCG activation request message carries first information from the MCG side, the first information is forwarded by the SCG to the MCG, and the MCG verifies the identity of the terminal device based on the first information. Alternatively, when the SCG activation request message carries second information from the SCG side, the SCG verifies the identity of the terminal device based on the second information.

[0125] In some alternative implementations, the first information on the MCG side includes at least one of the following:

[0126] The first C-RNTI is the C-RNTI assigned by MCG to the terminal device;

[0127] The first PCI is the PCI of the PCell in the MCG;

[0128] The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm.

[0129] In some alternative implementations, the second information on the SCG side includes at least one of the following:

[0130] The second C-RNTI is the C-RNTI assigned by SCG to the terminal device;

[0131] The second PCI is the PCI of PSCell in SCG;

[0132] The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

[0133] In some alternative implementations, the SCG activation request message carries an activation reason, which indicates at least one of the following:

[0134] The reason for activation is that the MCG experienced a wireless link failure;

[0135] The purpose of activation is to activate SCG;

[0136] The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

[0137] In some optional implementations, after the terminal device sends an SCG activation request message to the SCG, the terminal device receives an SCG activation message sent by the SCG; wherein the SCG activation message is prepared and sent by the SCG; or, the SCG activation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

[0138] In some alternative implementations, if the SCG activation message is prepared by the MCG, the SCG activation request message is sent by the SCG to the MCG, and then the SCG activation message is prepared by the MCG.

[0139] In some alternative implementations, the SCG activation message carries a reason for activating the SCG, the reason for activating the SCG indicating at least one of the following:

[0140] The reason for activation is that the MCG experienced a wireless link failure;

[0141] The purpose of activation is to activate SCG;

[0142] The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

[0143] The above technical solutions in the embodiments of this application clarify how to achieve rapid MCG recovery in the event of a wireless link failure in the MCG, thereby ensuring normal communication on the MCG side.

[0144] The technical solutions of the embodiments of this application are illustrated below with specific application examples.

[0145] Application Example 1

[0146] The terminal device is configured in DC mode, such as MR-DC mode.

[0147] 1. If the SCG is in a deactivated state, the terminal device will initiate a random access procedure to the SCG when the MCG experiences a wireless link failure.

[0148] 2. During the random access process, the terminal device sends an RRC connection reconstruction request message to the SCG via message 3 (MSG3).

[0149] Optionally, after the terminal device sends the RRC connection reconstruction request message, it starts timer T316.

[0150] The RRC connection reconstruction request message carries at least one of the following information: C-RNTI, PCI, and shortMAC-I. C-RNTI is the C-RNTI assigned by the MCG to the terminal device; PCI is the PCI of the PCell on the MCG side; and shortMAC-I is a shortMAC-I generated using KgNB or KeNB, i.e., the key and integrity protection algorithm on the MCG side.

[0151] The RRC connection re-establishment request message also carries a re-establishment cause, which is "MCG failure" and indicates at least one of the following: the re-establishment is due to a radio link failure of the MCG; the purpose of the re-establishment is to activate the SCG; or the purpose of the re-establishment is to quickly restore the MCG based on the SCG. Table 3 below shows the contents of the re-establishment cause.

[0152]

[0153] Table 3

[0154] 3. After SCG receives the RRC connection reconstruction request message,

[0155] Option 1: The SCG sends an SCG activation confirmation message or an RRC connection reconstruction message to the terminal device. Alternatively,

[0156] Option 2: The SCG sends an MCG failure message or an RRC connection reconstruction request message to the MCG. The MCG prepares an SCG activation confirmation message and sends the SCG activation confirmation message to the terminal device through the link on the SCG side.

[0157] 4. After receiving the MCG failure notification message or RRC connection reconstruction request message sent by the SCG, the MCG sends an RRC reconfiguration message carrying synchronization reconfiguration to the terminal device or sends an RRC release message to the SCG through the link on the SCG side.

[0158] Application Example 2

[0159] The terminal device is configured in DC mode, such as MR-DC mode.

[0160] 1. If the SCG is in a deactivated state, when the MCG experiences a wireless link failure, the terminal device will initiate a random access procedure to the SCG side.

[0161] 2. During the random access process, the terminal device sends an MCG failure information (MCGFailureInformation) message to the SCG via message 3 (MSG3).

[0162] Optionally, after the terminal device sends the MCGFailureInformation message, it starts timer T316.

[0163] The MCGFailureInformation message carries at least one of the following information from either the MCG or SCG side: C-RNTI, PCI, or shortMAC-I.

[0164] If the MCGFailureInformation message carries information from the MCG side, then the C-RNTI is the C-RNTI assigned by the MCG to the terminal device, the PCI is the PCI of the PCell on the MCG side, and the shortMAC-I is the shortMAC-I generated using KgNB or KeNB, i.e., the key and integrity protection algorithm on the MCG side.

[0165] If the MCGFailureInformation message carries information from the SCG side, then the C-RNTI is the C-RNTI assigned by the SCG to the terminal device, the PCI is the PCI of the PSCell on the SCG side, and the shortMAC-I is the shortMAC-I generated using S-KgNB or S-KeNB, which are the key and integrity protection algorithms on the SCG side.

[0166] 3. After receiving the MCGFailureInformation message, if the SCG carries information from the SCG side, the SCG needs to verify the identity and legitimacy of the terminal device based on that information. If the message carries information from the MCG side, the SCG forwards that information to the MCG for verification of the terminal device's identity and legitimacy. Furthermore,

[0167] Option 1: SCG sends an SCG activation message to the terminal device. Alternatively,

[0168] Option 2: The SCG sends an MCGFailureInformation message or the content of an MCGFailureInformation message to the MCG. The MCG then prepares an SCG activation message and sends it to the terminal device via the link on the SCG side.

[0169] 4. After receiving the MCGFailureInformation message or the MCG failure notification message sent by the SCG, the MCG sends an RRC reconfiguration message carrying synchronization reconfiguration to the terminal device or an RRC release message to the SCG through the link on the SCG side.

[0170] Application Example 3

[0171] The terminal device is configured in DC mode, such as MR-DC mode.

[0172] 1. If the SCG is in a deactivated state, the terminal device will initiate a random access procedure to the SCG when the MCG experiences a wireless link failure.

[0173] 2. During the random access process, the terminal device sends an SCG activation request message to the SCG via message 3 (MSG3).

[0174] Optionally, after the terminal device sends the SCG activation request message, it starts timer T316.

[0175] The SCG activation request message carries at least one of the following information from the MCG side or the SCG side: C-RNTI, PCI, or shortMAC-I.

[0176] in,

[0177] If the SCG activation request message carries information from the MCG side, then the C-RNTI is the C-RNTI assigned by the MCG to the terminal device, the PCI is the PCI of the PCell on the MCG side, and the shortMAC-I is the shortMAC-I generated using KgNB or KeNB, i.e., the key and integrity protection algorithm on the MCG side.

[0178] If the SCG activation request message carries information from the SCG side, then the C-RNTI is the C-RNTI assigned by the SCG to the terminal device, the PCI is the PCI of the PSCell on the SCG side, and the shortMAC-I is the shortMAC-I generated using S-KgNB or S-KeNB, which are the key and integrity protection algorithms on the SCG side.

[0179] Furthermore, the SCG activation request message may also carry the reason for requesting SCG activation (hereinafter referred to as the activation reason). Here, the activation reason is, for example, "MCG failure", indicating at least one of the following: the reason for activation is that the MCG has experienced a radio link failure; the purpose of activation is to activate the SCG; the purpose of activation is to perform rapid recovery of the MCG based on the SCG.

[0180] 3. After receiving the SCG activation request message, if it carries information from the SCG side, the SCG needs to verify the identity and legitimacy of the terminal device based on that information. If it carries information from the MCG side, the SCG forwards that information to the MCG for verification of the terminal device's identity and legitimacy. Furthermore,

[0181] Option 1: SCG sends an SCG activation message to the terminal device, optionally including the activation reason, such as "MCGfailure". Alternatively,

[0182] Option 2: The SCG sends an SCG activation request message to the MCG. The MCG prepares the SCG activation message and sends it to the terminal device through the link on the SCG side.

[0183] 4. After receiving the SCG activation request message from the SCG, the MCG sends an RRC reconfiguration message carrying synchronization reconfiguration to the terminal device or an RRC release message to the SCG via the link on the SCG side.

[0184] Figure 6 This is a flowchart illustrating the method for handling wireless link failures provided in the embodiments of this application. Figure 2 ,like Figure 6 As shown, the method for handling wireless link failures includes the following steps:

[0185] Step 601: The terminal device determines that an MCG wireless link failure has occurred.

[0186] Step 602: The terminal device sends a first message to the SCG and starts a first timer. The first message is used to trigger the fast recovery process of the MCG. If the terminal device receives an SCG deactivation command before the first timer expires, the terminal device triggers the RRC connection reconstruction process.

[0187] In this embodiment of the application, the terminal device is configured in DC mode, such as MR-DC mode.

[0188] In this embodiment of the application, if the terminal device detects a wireless link failure in the MCG and the first timer is configured, the terminal device performs fast SCG recovery through the link on the SCG side.

[0189] Here, the first timer is configured by the network device; optionally, the first timer is configured by the network device via RRC signaling. The first timer can also be called a Guard timer or Timer T316, and the Guard timer or Timer T316 can be referred to in the description of the aforementioned related solutions.

[0190] In this embodiment, during the rapid SCG recovery process via the SCG-side link, the terminal device sends a first message to the MCG via the SCG-side link and starts a first timer after sending the first message. Optionally, the first message is an RRC connection reconstruction request message, an MCG failure information message, or an SCG activation request message.

[0191] Here, the link on the SCG side is, for example, split SRB1 (see reference). Figure 3 ) or SRB3 (refer to Figure 4 It should be noted that when the terminal device sends the first message, the SCG is still active. Therefore, the terminal device can use the split SRB1 or SRB3 on the SCG side to send the first message.

[0192] In this embodiment of the application, if the terminal device receives an SCG deactivation command before the first timer expires (or during the operation of the first timer), the terminal device triggers the RRC connection reconstruction process. Here, the timing at which the terminal device triggers the RRC connection reconstruction process can have the following two options:

[0193] Option 1: After receiving the SCG deactivation command, the terminal device stops the first timer and triggers the RRC connection reconstruction process; or,

[0194] Option 2: After receiving the SCG deactivation command, the terminal device maintains the operation of the first timer and triggers the RRC connection reconstruction process after the first timer expires.

[0195] In the above scheme, the SCG remains in an active state during the operation of the first timer; after the first timer stops or times out, the SCG enters a deactivated state.

[0196] For example: If the terminal device receives an SCG deactivation command during the execution of timer T316, then: the terminal device stops timer T316 and triggers the RRC connection reconstruction process; or, the terminal device maintains the execution of timer T316 and triggers the RRC connection reconstruction process after timer T316 expires. Here, during the execution of timer T316, the SCG is in an active state, and the terminal device maintains PDCCH listening on the SCG side. After timer T316 stops or expires, the SCG is in a deactivated state, and the terminal device no longer transmits and / or receives on the SCG side.

[0197] Figure 7 This is a schematic diagram of the structural composition of the device for handling wireless link failures provided in the embodiments of this application. Figure 1 ,like Figure 7 As shown, the apparatus for handling wireless link failures includes:

[0198] Determination unit 701 is used to determine that an MCG radio link failure has occurred when the SCG is in a deactivated state;

[0199] The communication unit 702 is used to trigger the MCG's RRC connection reconstruction process or the MCG's fast recovery process.

[0200] In some alternative implementations, the communication unit 702 is used to initiate a random access procedure to the SCG and perform rapid recovery of the MCG based on the SCG.

[0201] In some optional embodiments, the communication unit 702 is configured to send a first message to the SCG, the first message being carried in the MSG3 during the random access process; and to receive an RRC reconfiguration message or an RRC release message sent by the SCG, the RRC reconfiguration message carrying synchronization reconfiguration, the RRC reconfiguration message or RRC release message being sent by the MCG to the SCG.

[0202] In some alternative embodiments, the terminal device is configured with a first timer; the apparatus further includes:

[0203] The control unit is configured to start the first timer after sending the first message to the SCG; and to stop the first timer if the RRC reconfiguration message or the RRC release message is received before the first timer expires.

[0204] In some alternative implementations, the first message is an RRC connection reconstruction request message.

[0205] In some alternative implementations, the RRC connection rebuild request message carries at least one of the following:

[0206] The first C-RNTI is the C-RNTI assigned by MCG to the terminal device;

[0207] The first PCI is the PCI of the PCell in the MCG;

[0208] The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm.

[0209] In some alternative implementations, the RRC connection rebuild request message carries a rebuild reason, which indicates at least one of the following:

[0210] The reason for the reconstruction was a wireless link failure in the MCG;

[0211] The purpose of reconstruction is to activate SCG;

[0212] The purpose of reconstruction is to rapidly restore the MCG based on the SCG.

[0213] In some optional embodiments, the communication unit 702 is further configured to receive an SCG activation confirmation message or an RRC connection reconstruction message sent by the SCG after sending the first message to the SCG.

[0214] The SCG activation confirmation message is prepared and sent by the SCG; or, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

[0215] In some alternative implementations, the SCG activation confirmation message is prepared by the MCG.

[0216] After the SCG sends an MCG failure message or an RRC connection reconstruction message to the MCG, the SCG activation confirmation message is prepared by the MCG.

[0217] In some alternative implementations, the first message is an MCG failure information message or an SCG activation request message.

[0218] In some alternative implementations, the MCG failure message or SCG activation request message carries first information from the MCG side or second information from the SCG side.

[0219] In some alternative implementations, the first information on the MCG side includes at least one of the following:

[0220] The first C-RNTI is the C-RNTI assigned by MCG to the terminal device;

[0221] The first PCI is the PCI of the PCell in the MCG;

[0222] The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm.

[0223] In some alternative implementations, the second information on the SCG side includes at least one of the following:

[0224] The second C-RNTI is the C-RNTI assigned by SCG to the terminal device;

[0225] The second PCI is the PCI of PSCell in SCG;

[0226] The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

[0227] In some optional implementations, if the MCG failure message or SCG activation request message carries first information from the MCG side, the first information is forwarded by the SCG to the MCG, and the MCG verifies the identity of the terminal device based on the first information.

[0228] In some optional implementations, if the MCG failure message or SCG activation request message carries second information from the SCG side, the SCG uses the second information to verify the identity of the terminal device.

[0229] In some alternative implementations, when the first message is an SCG activation request message, the SCG activation request message carries an activation reason, the activation reason being used to indicate at least one of the following:

[0230] The reason for activation is that the MCG experienced a wireless link failure;

[0231] The purpose of activation is to activate SCG;

[0232] The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

[0233] In some optional embodiments, the communication unit 702 is further configured to receive an SCG activation message sent by the SCG after sending the first message to the SCG;

[0234] The SCG activation message is prepared and sent by the SCG; or the SCG activation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

[0235] In some alternative implementations, if the first message is an SCG activation request message,

[0236] After the SCG sends the SCG activation request message to the MCG, the SCG activation message is prepared by the MCG.

[0237] In some alternative implementations, if the first message is an MCG failure message,

[0238] After the SCG sends the MCG failure message or the content of the MCG failure message to the MCG, the SCG activation message is prepared by the MCG.

[0239] In some alternative implementations, the SCG activation message carries a reason for activating the SCG, the reason for activating the SCG indicating at least one of the following:

[0240] The reason for activation is that the MCG experienced a wireless link failure;

[0241] The purpose of activation is to activate SCG;

[0242] The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

[0243] Those skilled in the art should understand that the description of the apparatus for handling wireless link failure in the embodiments of this application can be understood with reference to the description of the method for handling wireless link failure in the embodiments of this application.

[0244] Figure 8 This is a schematic diagram of the structural composition of the device for handling wireless link failures provided in the embodiments of this application. Figure 2 ,like Figure 8 As shown, the apparatus for handling wireless link failures includes:

[0245] Determination unit 801 is used to determine that an MCG radio link failure has occurred;

[0246] The communication unit 802 is used to send a first message to the SCG, the first message being used to trigger the fast recovery process of the MCG;

[0247] The control unit 803 is used to start a first timer after the communication unit sends a first message to the SCG;

[0248] The communication unit 802 is further configured to trigger the RRC connection reconstruction process if an SCG deactivation command is received before the first timer expires.

[0249] In some optional embodiments, the control unit 803 is configured to stop the first timer after the communication unit 802 receives the SCG deactivation command; or, after the communication unit 802 receives the SCG deactivation command, maintain the operation of the first timer until timeout.

[0250] The communication unit 802 is used to trigger the RRC connection reconstruction process after the first timer stops or times out.

[0251] In some alternative implementations, the SCG remains active during the operation of the first timer;

[0252] After the first timer stops or times out, the SCG enters a deactivation state.

[0253] In some alternative implementations, the first message is an RRC connection reconstruction request message, an MCG failure information message, or an SCG activation request message.

[0254] Those skilled in the art should understand that the description of the apparatus for handling wireless link failure in the embodiments of this application can be understood with reference to the description of the method for handling wireless link failure in the embodiments of this application.

[0255] Figure 9 This is a schematic structural diagram of a communication device 900 provided in an embodiment of this application. This communication device can be a terminal device or a network device. Figure 9 The communication device 900 shown includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0256] Optionally, such as Figure 9 As shown, the communication device 900 may further include a memory 920. The processor 910 can retrieve and run computer programs from the memory 920 to implement the methods described in this embodiment.

[0257] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0258] Optionally, such as Figure 9 As shown, the communication device 900 may also include a transceiver 930, which the processor 910 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0259] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas may be one or more.

[0260] Optionally, the communication device 900 may specifically be a network device in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0261] Optionally, the communication device 900 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0262] Figure 10 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 10 The chip 1000 shown includes a processor 1010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0263] Optionally, such as Figure 10 As shown, chip 1000 may further include memory 1020. Processor 1010 can retrieve and run computer programs from memory 1020 to implement the methods described in this embodiment.

[0264] The memory 1020 can be a separate device independent of the processor 1010, or it can be integrated into the processor 1010.

[0265] Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 can control the input interface 1030 to communicate with other devices or chips, specifically, to acquire information or data sent by other devices or chips.

[0266] Optionally, the chip 1000 may also include an output interface 1040. The processor 1010 can control the output interface 1040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0267] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0268] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0269] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0270] Figure 11 This is a schematic block diagram of a communication system 1100 provided in an embodiment of this application. Figure 11 As shown, the communication system 1100 includes a terminal device 1110 and a network device 1120.

[0271] The terminal device 1110 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, these will not be elaborated here.

[0272] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0273] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0274] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0275] This application also provides a computer-readable storage medium for storing computer programs.

[0276] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0277] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0278] This application also provides a computer program product, including computer program instructions.

[0279] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0280] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0281] This application also provides a computer program.

[0282] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0283] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0284] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0285] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0286] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0287] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0288] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0289] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0290] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for handling wireless link failure, the method comprising: The terminal device determined that a radio link failure occurred in the primary cell group (MCG) while the secondary cell group (SCG) was in a deactivated state. The terminal device triggers the Radio Resource Control (RRC) connection reconstruction process of the MCG or the fast recovery process of the MCG; The terminal device triggers a rapid recovery process for the MCG, including: The terminal device sends a first message to the SCG, and the first message is carried in the MSG3 during the random access process; The terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG. The RRC reconfiguration message carries synchronization reconfiguration. The RRC reconfiguration message or RRC release message is sent by the MCG to the SCG. Wherein, when the first message is an RRC connection reconstruction request message, the RRC connection reconstruction request message carries at least one of the following: The first cell wireless network temporary identifier (C-RNTI) is a C-RNTI assigned by the MCG to the terminal device. The first physical cell identifier (PCI) is the PCI of the primary cell PCell in the MCG. The first short complete message authentication code (shortMAC-I) is a shortMAC-I generated based on the MCG key and integrity protection algorithm. Alternatively, when the first message is an MCG failure information message or an SCG activation request message, the MCG failure information message or SCG activation request message carries first information from the MCG side or second information from the SCG side. The first information on the MCG side includes at least one of the following: The first C-RNTI is the C-RNTI assigned by MCG to the terminal device; The first PCI is the PCI of the PCell in the MCG; The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm; The second information on the SCG side includes at least one of the following: The second C-RNTI is the C-RNTI assigned by SCG to the terminal device; The second PCI is the PCI of PSCell in SCG; The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

2. The method according to claim 1, wherein, The terminal device is configured with a first timer; the method further includes: After the terminal device sends the first message to the SCG, it starts the first timer; If the terminal device receives the RRC reconfiguration message or the RRC release message before the first timer expires, the terminal device stops the first timer.

3. The method according to claim 1, wherein, The RRC connection rebuild request message carries a rebuild reason, which indicates at least one of the following: The reason for the reconstruction was a wireless link failure in the MCG; The purpose of reconstruction is to activate SCG; The purpose of reconstruction is to rapidly restore the MCG based on the SCG.

4. The method according to any one of claims 1, wherein, After the terminal device sends the first message to the SCG, the method further includes: The terminal device receives an SCG activation confirmation message or an RRC connection reconstruction message sent by the SCG. The SCG activation confirmation message is prepared and sent by the SCG; or, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

5. The method according to claim 4, wherein, When the SCG activation confirmation message is prepared by the MCG. After the SCG sends an MCG failure message or an RRC connection reconstruction message to the MCG, the SCG activation confirmation message is prepared by the MCG.

6. The method according to claim 1, wherein, When the MCG failure message or SCG activation request message carries the first information from the MCG side, the first information is forwarded by the SCG to the MCG, and the MCG verifies the identity of the terminal device based on the first information.

7. The method according to claim 1, wherein, When the MCG failure message or SCG activation request message carries second information from the SCG side, the SCG uses the second information to verify the identity of the terminal device.

8. The method according to claim 1, wherein, In the case that the first message is an SCG activation request message, the SCG activation request message carries an activation reason, the activation reason being used to indicate at least one of the following: The reason for activation is that the MCG experienced a wireless link failure; The purpose of activation is to activate SCG; The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

9. The method according to claim 1, wherein, After the terminal device sends the first message to the SCG, the method further includes: The terminal device receives the SCG activation message sent by the SCG; The SCG activation message is prepared and sent by the SCG; or the SCG activation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

10. The method according to claim 9, wherein, In the case that the first message is an SCG activation request message, After the SCG sends the SCG activation request message to the MCG, the SCG activation message is prepared by the MCG.

11. The method according to claim 9, wherein, In the case that the first message is an MCG failure message, After the SCG sends the MCG failure message or the content of the MCG failure message to the MCG, the SCG activation message is prepared by the MCG.

12. The method according to any one of claims 9 to 11, wherein, The SCG activation message carries a reason for SCG activation, which indicates at least one of the following: The reason for activation is that the MCG experienced a wireless link failure; The purpose of activation is to activate SCG; The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

13. A method for handling wireless link failure, the method comprising: The terminal device has determined that an MCG radio link failure has occurred; The terminal device sends a first message to the SCG and starts a first timer. The first message is used to trigger the fast recovery process of the MCG. If the terminal device receives an SCG deactivation command before the first timer expires, the terminal device triggers the RRC connection reconstruction process. The first message is either an RRC connection reconstruction request message, an MCG failure information message, or an SCG activation request message. Wherein, when the first message is an RRC connection reconstruction request message, the RRC connection reconstruction request message carries at least one of the following: The first cell wireless network temporary identifier (C-RNTI) is a C-RNTI assigned by the MCG to the terminal device. The first physical cell identifier (PCI) is the PCI of the primary cell PCell in the MCG. The first short complete message authentication code (shortMAC-I) is a shortMAC-I generated based on the MCG key and integrity protection algorithm. Alternatively, when the first message is an MCG failure information message or an SCG activation request message, the MCG failure information message or SCG activation request message carries first information from the MCG side or second information from the SCG side. The first information on the MCG side includes at least one of the following: The first C-RNTI is the C-RNTI assigned by MCG to the terminal device; The first PCI is the PCI of the PCell in the MCG; The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm; The second information on the SCG side includes at least one of the following: The second C-RNTI is the C-RNTI assigned by SCG to the terminal device; The second PCI is the PCI of PSCell in SCG; The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

14. The method according to claim 13, wherein, The terminal device triggers the RRC connection reconstruction process, including: After receiving the SCG deactivation command, the terminal device stops the first timer and triggers the RRC connection reconstruction process; or, After receiving the SCG deactivation command, the terminal device maintains the operation of the first timer and triggers the RRC connection reconstruction process after the first timer expires.

15. The method according to claim 14, wherein, During the operation of the first timer, the SCG remains in an active state; After the first timer stops or times out, the SCG enters a deactivation state.

16. An apparatus for handling wireless link failures, applied to a terminal device, the apparatus comprising: A determination unit is used to determine that an MCG radio link failure has occurred while the SCG is in a deactivated state. The communication unit is used to trigger the MCG's RRC connection reconstruction process or the MCG's fast recovery process; The communication unit is used to send a first message to the SCG, the first message being carried in the MSG3 during the random access process; and to receive an RRC reconfiguration message or an RRC release message sent by the SCG, the RRC reconfiguration message carrying synchronization reconfiguration, the RRC reconfiguration message or the RRC release message being sent to the SCG by the MCG. Wherein, when the first message is an RRC connection reconstruction request message, the RRC connection reconstruction request message carries at least one of the following: The first C-RNTI is the C-RNTI assigned by MCG to the terminal device; The first PCI is the PCI of the PCell in the MCG; The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm; When the first message is an MCG failure information message or an SCG activation request message, the MCG failure information message or SCG activation request message carries first information from the MCG side or second information from the SCG side. The first information on the MCG side includes at least one of the following: The first C-RNTI is the C-RNTI assigned by MCG to the terminal device; The first PCI is the PCI of the PCell in the MCG; The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm; The second information on the SCG side includes at least one of the following: The second C-RNTI is the C-RNTI assigned by SCG to the terminal device; The second PCI is the PCI of PSCell in SCG; The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

17. The apparatus according to claim 16, wherein, The terminal device is configured with a first timer; the device further includes: The control unit is configured to start the first timer after sending the first message to the SCG; and to stop the first timer if the RRC reconfiguration message or the RRC release message is received before the first timer expires.

18. The apparatus according to claim 16, wherein, The RRC connection rebuild request message carries a rebuild reason, which indicates at least one of the following: The reason for the reconstruction was a wireless link failure in the MCG; The purpose of reconstruction is to activate SCG; The purpose of reconstruction is to rapidly restore the MCG based on the SCG.

19. The apparatus according to claim 16, wherein, The communication unit is also configured to receive an SCG activation confirmation message or an RRC connection reconstruction message sent by the SCG after sending the first message to the SCG. The SCG activation confirmation message is prepared and sent by the SCG; or, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

20. The apparatus according to claim 19, wherein, When the SCG activation confirmation message is prepared by the MCG. After the SCG sends an MCG failure message or an RRC connection reconstruction message to the MCG, the SCG activation confirmation message is prepared by the MCG.

21. The apparatus according to claim 16, wherein, When the MCG failure message or SCG activation request message carries the first information from the MCG side, the first information is forwarded by the SCG to the MCG, and the MCG verifies the identity of the terminal device based on the first information.

22. The apparatus according to claim 16, wherein, When the MCG failure message or SCG activation request message carries second information from the SCG side, the SCG uses the second information to verify the identity of the terminal device.

23. The apparatus according to claim 16, wherein, In the case that the first message is an SCG activation request message, the SCG activation request message carries an activation reason, the activation reason being used to indicate at least one of the following: The reason for activation is that the MCG experienced a wireless link failure; The purpose of activation is to activate SCG; The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

24. The apparatus according to claim 16, wherein, The communication unit is also configured to receive an SCG activation message sent by the SCG after sending the first message to the SCG. The SCG activation message is prepared and sent by the SCG; or the SCG activation message is prepared by the MCG and forwarded to the SCG for sending by the SCG.

25. The apparatus according to claim 24, wherein, In the case that the first message is an SCG activation request message, After the SCG sends the SCG activation request message to the MCG, the SCG activation message is prepared by the MCG.

26. The apparatus according to claim 24, wherein, In the case that the first message is an MCG failure message, After the SCG sends the MCG failure message or the content of the MCG failure message to the MCG, the SCG activation message is prepared by the MCG.

27. The apparatus according to any one of claims 24 to 26, wherein, The SCG activation message carries a reason for SCG activation, which indicates at least one of the following: The reason for activation is that the MCG experienced a wireless link failure; The purpose of activation is to activate SCG; The purpose of activation is to enable rapid recovery of the MCG based on the SCG.

28. An apparatus for handling wireless link failures, applied to a terminal device, the apparatus comprising: A determination unit, used to determine when an MCG radio link failure has occurred; A communication unit is used to send a first message to the SCG, the first message being used to trigger the MCG's fast recovery process; The control unit is configured to start a first timer after the communication unit sends a first message to the SCG; The communication unit is further configured to trigger the RRC connection reconstruction process if an SCG deactivation command is received before the first timer expires. The first message is either an RRC connection reconstruction request message, an MCG failure information message, or an SCG activation request message. Wherein, when the first message is an RRC connection reconstruction request message, the RRC connection reconstruction request message carries at least one of the following: The first cell wireless network temporary identifier (C-RNTI) is a C-RNTI assigned by the MCG to the terminal device. The first physical cell identifier (PCI) is the PCI of the primary cell PCell in the MCG. The first short complete message authentication code (shortMAC-I) is a shortMAC-I generated based on the MCG key and integrity protection algorithm. Alternatively, when the first message is an MCG failure information message or an SCG activation request message, the MCG failure information message or SCG activation request message carries first information from the MCG side or second information from the SCG side. The first information on the MCG side includes at least one of the following: The first C-RNTI is the C-RNTI assigned by MCG to the terminal device; The first PCI is the PCI of the PCell in the MCG; The first shortMAC-I is a shortMAC-I generated based on the MCG key and integrity protection algorithm; The second information on the SCG side includes at least one of the following: The second C-RNTI is the C-RNTI assigned by SCG to the terminal device; The second PCI is the PCI of PSCell in SCG; The second shortMAC-I is a shortMAC-I generated based on the SCG key and integrity protection algorithm.

29. The apparatus according to claim 28, wherein, The control unit is configured to stop the first timer after the communication unit receives the SCG deactivation command; or, after the communication unit receives the SCG deactivation command, maintain the operation of the first timer until it times out. The communication unit is used to trigger the RRC connection reconstruction process after the first timer stops or times out.

30. The apparatus according to claim 29, wherein, During the operation of the first timer, the SCG remains in an active state; After the first timer stops or times out, the SCG enters a deactivation state.

31. A communication device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as claimed in any one of claims 1 to 12, or the method as claimed in any one of claims 13 to 15.

32. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 12, or the method as claimed in any one of claims 13 to 15.

33. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as claimed in any one of claims 1 to 12, or the method as claimed in any one of claims 13 to 15.

Images