JP7288953B2 - Connection failure recovery method and equipment - Google Patents

Description

(Cross reference to related applications)
This application claims priority from Chinese Patent Application No. 201810898696.2 filed on Aug. 8, 2018, the entire content of which is hereby incorporated by reference.
TECHNICAL FIELD Embodiments of the present disclosure relate to the technical field of communications, and in particular to a connection failure recovery method and apparatus.

In the prior art, when a secondary cell group (SCG) failure occurs in standardization, the operation of the terminal equipment becomes clear.

However, the cause of Master Cell Group (MCG) failure and SCG failure may be different. In the prior art, there is no clear definition on how terminal equipment recovers from connection failure when MCG failure occurs.

An object of the embodiments of the present disclosure is to provide a connection failure recovery method and device that can solve the problem of how to recover connection failure when MCG failure occurs.

In a first aspect, the connection failure recovery method applied to the terminal equipment includes:
determining the cause of the master cell group MCG failure;
performing corresponding connection failure recovery procedures and/or reporting MCG failure related information according to the cause of the MCG failure.

In a second aspect, the connection failure recovery method applied to the first network device comprises:
receiving MCG failure related information sent from the terminal device;
sending the MCG failure related information to a second network device or a third network device;
The first network equipment serves an SCG, the second network equipment serves a source MCG, the third network equipment serves a target MCG, or
The first network equipment serves an SCG, the second network equipment serves a target MCG, and the third network equipment serves a source MCG.

In a third aspect, the terminal device
a decision module for determining the cause of master cell group MCG failure;
a processing module for performing corresponding connection failure recovery processing and/or reporting MCG failure related information based on the cause of the MCG failure.

In a fourth aspect, the first network device comprises:
a receiving module for receiving MCG failure-related information transmitted from the terminal device;
a transmission module for transmitting the MCG failure related information to a second network device or a third network device;
The first network equipment serves an SCG, the second network equipment serves a source MCG, the third network equipment serves a target MCG, or
The first network equipment serves an SCG, the second network equipment serves a target MCG, and the third network equipment serves a source MCG.

In a fifth aspect, a terminal device comprises a processor, a memory, stored in said memory and executable on said processor, and when executed by said processor, the steps of the connection failure recovery method according to the first aspect. and a computer program for implementing

In a sixth aspect, a network device comprises a processor, a memory, stored in said memory and executable on said processor, and when executed by said processor, the steps of the connection failure recovery method according to the second aspect. and a computer program for implementing

In a seventh aspect, a computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the connection failure recovery method according to the first aspect or the second aspect.

In an embodiment of the present disclosure, when an MCG failure occurs, the terminal device can determine its behavior according to the cause of the MCG failure, and perform corresponding connection failure recovery operations.

Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of the preferred embodiments. The drawings are intended to depict preferred embodiments only and should not be construed as limiting the disclosure. Also, like reference numerals refer to like parts throughout the drawings.

1 is a schematic diagram of an architecture of a wireless communication system according to an embodiment of the present disclosure; FIG. 4 is a flowchart (part 1) of a connection failure recovery method according to an embodiment of the present disclosure; 2 is a flowchart (part 2) of a connection failure recovery method according to an embodiment of the present disclosure; 1 is a configuration diagram (part 1) of a terminal device according to an embodiment of the present disclosure; FIG. 1 is a configuration diagram of a first network device according to an embodiment of the present disclosure; FIG. FIG. 2 is a configuration diagram (part 2) of a terminal device according to an embodiment of the present disclosure; 1 is a configuration diagram of a network device according to an embodiment of the present disclosure; FIG.

Hereinafter, the technical means in the embodiments of the present disclosure will be clearly and completely described with reference to the drawings in the embodiments of the present disclosure. Apparently, the described embodiments are some but not all of the embodiments of the present disclosure. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work shall fall within the protection scope of the present disclosure.

The term "comprising" and any variation thereof in the specification and claims of this application is intended to cover non-exclusive inclusion, e.g., a process, method, system, article of manufacture comprising a series of steps or units Or, the devices are not limited to the explicitly indicated steps or units, and may include other steps or units not explicitly indicated or unique to those processes, methods, products or devices. Also, "and/or" as used in the specification and claims refers to at least one of the connected objects, e.g. Three cases are represented, where only A is present and where both A and B are present.

In the embodiments of the present disclosure, the term "exemplary" or "for example" or the like is intended to represent an example, instance or illustration. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this disclosure is not to be construed as preferred or advantageous over other embodiments or designs. In particular, use of the terms "exemplary" or "for example" are intended to present related concepts in a concrete fashion.

The techniques described herein are not limited to Long Time Evolution (LTE)/LTE-Advanced (LTE-A) systems, but also Code Division Multiple Access (CDMA) , Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OF DMA), single carrier frequency division multiple access (Single -carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" are always used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). OFDMA systems include Ultra-Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20 , Flash-OFDM, etc. can be implemented. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (eg LTE-A) are new UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used in the systems and radio technologies mentioned above or in other systems and radio technologies.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The connection failure recovery method and apparatus according to embodiments of the present disclosure can be applied to wireless communication systems. The wireless communication system may adopt a fifth-generation mobile communication technology (5G) system or an evolved long term evolution (eLTE) system or a subsequent evolution communication system.

FIG. 1 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the wireless communication system may include at least two network devices and a terminal device 12, the at least two network devices including a first network device 10 and a second network device 11. Often, the terminal equipment 12 can communicate (transmit signaling or data) with the first network equipment 10 and the second network equipment 11 . In actual application, the connections between the devices may be wireless connections, which are indicated by solid lines in FIG. 1 in order to simply and intuitively represent the connection relationships between the devices.

The communication system may include a plurality of terminal devices 12 , and the first network device 10 and the second network device 11 can communicate with the plurality of terminal devices 12 .

It should be noted that the first network device 10 and the second network device 11 in the above communication system may be base stations, and the base stations may be commonly used base stations. station (evolved node base station, eNB), and network equipment in the 5G system (e.g., next generation node base station (gNB) or transmission and reception point (TRP)), etc. equipment.

The terminal device 12 according to the embodiment of the present disclosure may be a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), etc. can be

FIG. 1 shows a dual connection (Dual Connectivity, DC) scene, dual connection is a technology introduced in Long Term Evolution (LTE), a new wireless technology (New Radio , NR). Dual connection means that a terminal device can connect to two base stations at the same time, and the two base stations can provide data transmission and reception services to the terminal device at the same time. Since the radio resources of two base stations can be used simultaneously, the service data transmission rate of the terminal equipment is doubled. It should be understood that there is a signaling interface between two base stations serving the same terminal equipment, e.g. the two base stations exchange configuration information for the associated terminal equipment.

The base stations serving the dual-access terminals belong to the same Radio Access Technology (RAT), or the base stations serving the dual-access terminals belong to different RATs. For example, in FIG. 1, both the first network device 10 and the second network device 11 are LTE eNBs, or the first network device 10 is an LTE eNB and the second network device 11 is an NR gNB. is. It should be appreciated that embodiments of the present disclosure can be applied to any type of combination of dual-connection base stations, and the types of first network equipment 10 and second network equipment 11 in FIG. 1 are not limited.

One of the base stations serving the dual access terminal equipment is a master base station (Master Node, MN) and the other is a secondary base station (Secondary Node, SN), for example, in FIG. The first network equipment 10 may be a master base station (Master Node, MN) and the second network equipment 11 may be a secondary base station (Secondary Node, SN), but of course not limited thereto. not. A master cell group is a group of serving cells associated with the master base station in a dual connection, and a secondary cell group is a group of serving cells associated with the secondary base station in a dual connection.

Each of the base stations serving the dual-access terminal equipment may support Carrier Aggregation (CA). The network sets two special cells in the dual-connection terminal equipment, namely one serving cell of the MN as the primary cell (PCell) of the terminal equipment, and one serving cell of the SN. is set as a primary secondary cell (PScell). The other cell serving the terminal equipment is the secondary cell (Scell) of the terminal equipment.

It should be appreciated that embodiments of the present disclosure are applicable to multi-connection scenes as well as dual-connection scenes. Multi-connection means that more than two base stations serve the same terminal equipment. Embodiments of the present disclosure do not limit the type of multi-connection base station.

Similar to the dual-connection scene, one of the base stations serving the multi-connection terminal equipment is a master base station (Master Node), and the others are secondary base stations (Secondary Nodes). A master cell group is a group of serving cells associated with the master base station in a multi-connection, and a secondary cell group is a group of serving cells associated with the secondary base station in a multi-connection.

In a dual-connection or multi-connection scene, if the MCG downlink channel condition deteriorates and MCG failure occurs, according to the technical solution in the embodiments of the present disclosure, the terminal equipment can determine the terminal according to the cause of the MCG failure. It can determine the behavior of the equipment and perform corresponding connection failure recovery operations.

Referring to FIG. 2, an embodiment of the present disclosure provides a connection failure recovery method. An execution subject of the method is a terminal device. Specifically, it includes the following steps 201-202.

At step 201, determine the cause of the MCG failure;
In embodiments of the present disclosure, preferably the cause of MCG failure is
(1) Signaling Radio Bearers (SRB) integrity check failure (SRB Integrity check failure);
(2) Radio Resource Control (RRC) reconfiguration failure (RRC Reconfiguration failure);
(3) Handover failure (HOF) based on the first handover command containing the SCG configuration;
(4) the number of uplink transmissions exceeds a threshold, e.g., the maximum number of uplink transmissions is reached;
(5) Random Access Channel (RACH) transmission failure;
(6) radio link failure (RLF);
(7) handover failure based on a second handover command that does not include an SCG configuration.

In step 202, according to the cause of MCG failure, perform corresponding connection failure recovery procedures and/or report MCG failure related information.

In an embodiment of the present disclosure, preferably triggering the MCG reconfiguration process or the terminal device reconfiguration process when the cause of MCG failure is the first cause,
In the embodiment of the present disclosure, preferably when the cause of MCG failure is the first cause, trigger MCG re-establishment or the terminal equipment re-establishment procedure (RRC Connection Re-establishment procedure) death,
When the cause of the MCG failure is the second cause, the MCG reconfiguration process or the terminal equipment reconfiguration process is not triggered, and a suspend operation is performed on the MCG. The MCG suspend operation may include suspending uplink transmission and downlink reception of the MCG bearer part and/or splitting uplink transmission and downlink reception of the MCG bearer part.
The first cause is SRB integrity check failure, RRC reconfiguration failure, handover failure based on the first handover command including SCG configuration, the number of uplink transmissions exceeds a threshold, and/or failed transmission of the random access channel RACH.

In an embodiment of the present disclosure, preferably, when the cause of MCG failure is the second cause, do not trigger the reconfiguration process of MCG or the reconfiguration process of the terminal equipment; suspend to MCG; and transmitting MCG failure related information to network equipment serving the SCG, the second cause being a radio link failure and a second cause not including the SCG configuration. a handover failure based on a handover command, wherein performing a suspend operation on the MCG comprises stopping uplink transmission and downlink reception of the MCG bearer portion; and/or Alternatively, it may involve splitting uplink transmission and downlink reception of the MCG bearer part.

In embodiments of the present disclosure, the MCG failure related information may preferably include a Cause value of the MCG failure.

In embodiments of the present disclosure, the cause value may preferably include at least one of a first value, a second value, and a third value, the first value representing radio link failure; For example, the first value is RLF, and the second value represents handover failure, for example, the second value is HOF, and the third value is T304 timer timeout and T301 timer timeout. , the maximum number of uplink transmissions being reached, and a RACH transmission failure, e.g., when the third value represents the timeout of the T304 timer, the third value is T304 expiry. be.

It should be appreciated that the embodiments of the present disclosure are not limited to specific forms of the first value, the second value, and the third value.

In an embodiment of the present disclosure, when an MCG failure occurs, the terminal device can determine its behavior according to the cause of the MCG failure, and perform corresponding connection failure recovery operations.

Referring to FIG. 3, an embodiment of the present disclosure provides a connection failure recovery method. The execution subject of the method is the first network device. Specifically, it includes the following steps 301-302.

At step 301, the MCG failure related information transmitted from the terminal device is received.
In embodiments of the present disclosure, the MCG failure related information may preferably include a Cause value of the MCG failure.

In embodiments of the present disclosure, the cause value preferably includes at least one of a first value, a second value and a third value, the first value representing a radio link failure, e.g. The first value is RLF and the second value represents handover failure, for example the second value is HOF and the third value is T304 timer timeout and T301 timer timeout. and/or a maximum number of uplink transmissions is reached and RACH transmission failure, for example, the third value is T304 expiry when the third value represents the timeout of the T304 timer.

It should be appreciated that the embodiments of the present disclosure are not limited to specific forms of the first value, the second value, and the third value.

In step 302, send MCG failure related information to the second network device or the third network device.

A first network equipment serves an SCG, a second network equipment serves a source MCG, a third network equipment serves a target MCG, or Serving an SCG, said second network equipment serving a target MCG and said third network equipment serving a source MCG.

In an embodiment of the present disclosure, preferably, in step 302, the MCG failure related information is sent to the second network device or the third network device according to the MCG failure cause value in the MCG failure related information.

when the MCG failure cause value is the first value (e.g., RLF) or the third value (e.g., T304 expiry), sending the MCG failure-related information to a second network device;
When the MCG failure cause value is a second value (eg, HOF), sending the MCG failure related information to the third network device.

In an embodiment of the present disclosure, a first network equipment serving an SCG sends an MCG failure related message to a second network equipment serving a source MCG or a third network equipment serving a target MCG. By sending information, the behavior of the network side can be clarified.

Example 1
In step 1, when the terminal device determines that an MCG failure has occurred, it selects and triggers different actions according to the cause of the MCG failure, including the following two types of actions.

In a first type of operation, the terminal equipment triggers the MCG reconfiguration process or the terminal equipment reconfiguration process. The reason for MCG failure is
(1) SRB integrity check failure;
(2) RRC reconfiguration failure (RRC Reconfiguration failure);
(3) a handover failure (HOF) based on a handover command containing an SCG configuration;
(4) the number of uplink transmissions exceeds a threshold;
(5) RACH transmission failure.

The second type of action is that the terminal equipment does not trigger the reconfiguration process of the MCG or the reconfiguration process of the terminal equipment, performs a suspend operation on the MCG, and reports MCG failure related information to the SCG. including at least one of The cause of MCG failure is
(1) radio link failure (RLF);
(2) a handover failure (HOF) based on a handover command that does not contain an SCG configuration;

In step 2, based on the second type of operation of the terminal equipment in step 1, the terminal equipment may further cause the MCG failure related information reported to the SCG to carry a Cause value of the MCG failure. For example, the MCG failure cause value can be
(1) RLF representing radio link failure;
(2) HOF representing handover failure;
(3) T304 expiry, which indicates the timeout of timer T304;

In step 3, when the SCG receives the reported MCG failure related information, forward the MCG failure related information to the source MCG or the target MCG according to the cause value of the MCG failure, for example:
when the MCG failure cause value is equal to RLF or T304 expiry, forward MCG failure related information to the source MCG;
When the MCG failure cause value is equal to HOF, forward the MCG failure related information to the target MCG.

An embodiment of the present disclosure further provides a terminal device. Since the principle of the terminal device solving the problem is the same as the connection failure recovery method in the embodiments of the present disclosure, the implementation of the terminal device can refer to the implementation of the method, and redundant descriptions are omitted. do.

Referring to FIG. 4, an embodiment of the disclosure provides a terminal device. The terminal device 400 is
a decision module 401 for determining the cause of MCG failure;
a processing module 402 for performing corresponding connection failure recovery processing and/or reporting MCG failure related information based on the cause of MCG failure.

In an embodiment of the present disclosure, preferably, the processing module 402 further triggers an MCG reconfiguration process or the terminal equipment reconfiguration process when the cause of MCG failure is the first cause;
The first cause is SRB integrity check failure, RRC reconfiguration failure, handover failure based on the first handover command including SCG configuration, the number of uplink transmissions exceeds a threshold, Random Access Channel RACH transmission failure.

In an embodiment of the present disclosure, preferably, the processing module 402 is further configured not to trigger an MCG reconfiguration process when the cause of MCG failure is a second cause; performing a suspend operation on the MCG if it is the cause; and sending MCG failure-related information to the network equipment serving the SCG when the above cause of MCG failure is the second cause. and at least one of
A second cause includes at least one of a radio link failure and a handover failure based on a second handover command that does not include an SCG configuration.

In embodiments of the present disclosure, the MCG failure related information preferably includes the MCG failure cause value.

In an embodiment of the present disclosure, preferably the cause value includes at least one of a first value, a second value and a third value, said first value representing a radio link failure, said The second value represents handover failure, and the third value is at least one of T304 timer timeout, T301 timer timeout, maximum number of uplink transmissions reached, and RACH transmission failure. represents one.

The terminal equipment according to the embodiments of the present disclosure can implement the above method embodiments, and the implementation principles and technical effects thereof are similar, so the description of the embodiments is omitted here.

Embodiments of the present disclosure further provide a first network device. Since the principle that the first network device solves the problem is similar to the connection failure recovery method in the embodiments of the present disclosure, the implementation of the first network device can refer to the implementation of the method, and the duplication We omit the description of the part where

Referring to FIG. 5, an embodiment of the present disclosure provides a first network device. The first network device 500 includes:
a receiving module 501 for receiving MCG failure-related information transmitted from the terminal device;
a sending module 502 for sending MCG failure related information to a second network device or a third network device;
A first network equipment serves an SCG, a second network equipment serves a source MCG, a third network equipment serves a target MCG, or Serving an SCG, said second network equipment serving a target MCG and said third network equipment serving a source MCG.

In an embodiment of the present disclosure, the MCG failure related information preferably includes an MCG failure cause value, and the transmitting module 502 further determines a second MCG failure cause value based on the MCG failure cause value in the MCG failure related information. the MCG failure related information to the first network device or the third network device.

In embodiments of the present disclosure, the cause value preferably includes at least one of a first value, a second value, and a third value, the first value representing radio link failure, the second A value of represents handover failure, and a third value represents at least one of T304 timer timeout, T301 timer timeout, maximum number of uplink transmissions reached, and RACH transmission failure. ,
The transmitting module 502 further transmits MCG failure related information to a second network device when the MCG failure cause value is the first value or the third value; value, send MCG failure related information to the third network device.

The first network device according to the embodiments of the present disclosure can implement the above method embodiments, and their implementation principles and technical effects are similar, so the embodiments are omitted here. .

As shown in FIG. 6, the terminal device 600 shown in FIG. 6 includes at least one processor 601 , memory 602 , at least one network interface 604 and user interface 603 . Each component in terminal equipment 600 is coupled by a bus system 605 . It should be appreciated that the bus system 605 provides connecting communication between these components. Bus system 605 further includes a power bus, a control bus and a status signal bus in addition to the data bus. However, for clarity of explanation, all of the various buses are referred to as bus system 605 in FIG.

User interface 603 may include a display, keyboard or pointing device (eg, mouse, trackball, touchpad or touchscreen), or the like.

It should be appreciated that memory 602 in embodiments of the present disclosure may be volatile memory or non-volatile memory, and may include both volatile and non-volatile memory. Non-volatile memory includes read-only memory (ROM), programmable read-only memory (ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory. It may be memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory can be Random Access Memory (RAM), which is used as an external cache. By way of example and not by way of limitation, static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate Synchronous dynamic random access memory (Double Data SDRAM, DDRSDRAM), Enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), Synchlink dynamic random access memory (Synchlink DRAM, SLDRAM) and Direct Rambus random access memory (Direct Rambus Many forms of RAM may be used, such as RAM, DRRAM). Memory 602 in systems and methods according to embodiments of the present disclosure is intended to include, but not be limited to, these memories and any other suitable types of memory.

In some embodiments, memory 602 stores the following elements: executable modules or data structures, or subsets or extended sets thereof, such as operating system 6021 and application programs 6022 .

The operating system 6021 includes various system programs such as a framework layer, a core library layer, a driver layer, etc. for implementing various basic services and processing hardware-based services. Application programs 6022 include various application programs such as a media player and a browser that implement various application services. Programs implementing methods according to embodiments of the present disclosure may be included in application programs 6022 .

In one embodiment of the present disclosure, the cause of MCG failure is determined during execution by invoking programs or instructions stored in memory 602, and more specifically, programs or instructions stored in application program 6022. and performing corresponding connection failure recovery procedures and/or reporting MCG failure related information according to the cause of the MCG failure.

The terminal equipment according to the embodiments of the present disclosure can implement the above method embodiments, and the implementation principles and technical effects thereof are similar, so the description of the embodiments is omitted here.

Referring to FIG. 7, FIG. 7 is a configuration diagram of a network device applied to an embodiment of the present disclosure. As shown in FIG. 7, network device 700 includes processor 701, transceiver 702, memory 703 and bus contains an interface,
In one embodiment of the present disclosure, the network device 700 further includes a computer program stored in the memory 703 and executable on the processor 701 which, when executed by the processor 701, transmits from the terminal device and transmitting the MCG failure-related information to a second network device or a third network device. The network appliance 700 serves the SCG, the second network appliance serves the source MCG, and the third network appliance serves the target MCG.

In FIG. 7, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors, represented by processor 701, and memory, represented by memory 703. connected together by various circuits. The bus architecture may also connect together various other circuits such as peripherals, stabilizers and power management circuits, all of which are known in the art and thus further described herein. omitted. A bus interface provides an interface. Transceiver 702 may be multi-part, ie, includes a transmitter and a receiver, to provide a unit that communicates with various other devices over a transmission medium.

Processor 701 is responsible for managing the bus architecture and general processing, and memory 703 can store data that processor 701 uses when performing operations.

The network equipment according to the embodiments of the present disclosure can implement the above method embodiments, and the implementation principles and technical effects thereof are similar, so the description of the embodiments is omitted here.

The steps of a method or algorithm described with reference to the content disclosed in this disclosure may be implemented in the form of hardware or may be implemented in the form of a processor executing software instructions. The software instructions may be comprised of corresponding software modules, which may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable hard disk, read-only disk, or any other form known in the art. may be stored in a storage medium of An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and storage medium may be located in an ASIC. Further, the ASIC may be located in core network interface equipment. Of course, the processor and storage medium may reside in the core network interface equipment as separate components.

Those skilled in the art should appreciate that, in one or more of the examples above, the functions described in the present disclosure may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on the computer-readable medium. Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Although the above specific embodiments describe the purpose, technical means and beneficial effects of the present disclosure in more detail, the above are only specific embodiments of the present disclosure and limit the protection scope of the present disclosure. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical means of the present disclosure should all fall within the protection scope of the present disclosure.

A person skilled in the art should understand that the embodiments of the present disclosure may be provided as a method, system or computer program product. Accordingly, embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Further, embodiments of the present disclosure may be implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable computer program code. can take the form of a computer program product embodied in

Embodiments of the present disclosure are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It should be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processing unit or other programmable data processing apparatus to produce a machine and executed by the processor of the computer or other programmable data processing apparatus. The instructions provided may produce an apparatus that implements the functionality specified in one or more of the flows in the flowcharts and/or one or more blocks in the block diagrams.

These computer program instructions can also be stored in a computer readable memory capable of directing a computer or other programmable data processing apparatus to function in a specified manner. The stored instructions may produce an article of manufacture that includes an instruction device that implements the functionality defined in one or more flows in the flowcharts and/or one or more blocks in the block diagrams.

These computer program instructions can also be loaded into a computer or other programmable data processing apparatus and cause the computer or other programmable device to perform a series of operational steps to produce a computer-implemented process of: Instructions executed by a computer or other programmable device implement the functional steps defined in one or more of the flows in the flowcharts and/or one or more blocks in the block diagrams.

Obviously, those skilled in the art can make various modifications and variations to the examples of this disclosure without departing from the spirit and scope of this disclosure. Thus, the present disclosure includes such modifications and variations of the embodiments of the present disclosure provided that they fall within the scope of protection defined by the claims of this disclosure and their equivalents. It is intended that

Claims (10)

A connection failure recovery method applied to terminal equipment, comprising:
determining the cause of master cell group MCG failure in an EN-DC scene or an NGEN-DC scene ;
performing corresponding connection failure recovery procedures and/or reporting MCG failure related information based on the cause of the MCG failure;
performing a corresponding connection failure recovery procedure and/or reporting MCG failure related information based on the cause of the MCG failure;
In the EN-DC scene or NGEN-DC scene,
not triggering the MCG reconfiguration process or the terminal device reconfiguration process when the cause of the MCG failure is the second cause;
performing a suspend operation on the MCG when the cause of the MCG failure is a second cause;
sending MCG failure related information to a network device serving an SCG when the cause of the MCG failure is a second cause;
The connection failure recovery method, wherein the second cause includes at least one of a radio link failure and a handover failure based on a second handover command that does not include an SCG configuration. Based on the cause of the MCG failure, performing a corresponding connection failure recovery process,
triggering an MCG reconfiguration process or a terminal device reconfiguration process when the cause of the MCG failure is the first cause;
The first cause is
a signaling radio bearer SRB integrity check failure;
Radio Resource Control RRC reconfiguration failure; and
handover failure based on a first handover command including a secondary cell group SCG configuration;
the number of uplink transmissions exceeding a threshold;
Random Access Channel RACH transmission failure. The connection failure recovery method of claim 1, wherein the MCG failure related information includes a cause value of MCG failure. the cause value includes at least one of a first value, a second value, and a third value;
The first value represents a radio link failure, the second value represents a handover failure, and the third value represents a T304 timer timeout, a T301 timer timeout, and a maximum uplink transmission. 4. The connection failure recovery method of claim 3, representing at least one of reaching a number of times and RACH transmission failure. a terminal device,
a decision module for determining the cause of a master cell group MCG failure in an EN-DC scene or an NGEN-DC scene ;
a processing module for performing corresponding connection failure recovery processing and/or reporting MCG failure related information based on the cause of the MCG failure;
In an EN-DC scene or an NGEN-DC scene, the processing module comprises:
not triggering the MCG reconfiguration process or the terminal device reconfiguration process when the cause of the MCG failure is the second cause;
performing a suspend operation on the MCG when the cause of the MCG failure is a second cause;
and sending MCG failure-related information to a network device serving an SCG when the cause of the MCG failure is a second cause;
The terminal equipment, wherein the second cause includes at least one of a radio link failure and a handover failure based on a second handover command that does not include an SCG configuration. The processing module is
is further used to trigger an MCG reconfiguration process or a terminal device reconfiguration process when the cause of the MCG failure is the first cause;
The first cause is
a signaling radio bearer SRB integrity check failure;
Radio Resource Control RRC reconfiguration failure; and
handover failure based on a first handover command including a secondary cell group SCG configuration;
the number of uplink transmissions exceeding a threshold;
and failure to transmit a random access channel RACH. The terminal device according to claim 5, wherein the MCG failure related information includes an MCG failure cause value. the cause value includes at least one of a first value, a second value, and a third value;
The first value represents a radio link failure, the second value represents a handover failure, and the third value represents a T304 timer timeout, a T301 timer timeout, and a maximum uplink transmission. 8. The terminal device according to claim 7, representing at least one of reaching a number of times and failing to transmit a RACH. A computer program according to any one of claims 1 to 4, comprising a processor, a memory, and a computer program stored in said memory and executable on said processor, said computer program being executed by said processor. A terminal device that implements the steps of the connection failure recovery method. A computer readable storage medium storing a computer program that, when executed by a processor, implements the steps of the connection failure recovery method of any one of claims 1-4.

Images