CN114375070A

CN114375070A - Connection processing method and device

Info

Publication number: CN114375070A
Application number: CN202210135269.5A
Authority: CN
Inventors: 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-08-17
Filing date: 2018-08-17
Publication date: 2022-04-19
Also published as: CN110839300A; WO2020034868A1; CN110839300B

Abstract

The embodiment of the invention discloses a connection processing method and equipment, wherein the method comprises the following steps: receiving configuration information, wherein the configuration information comprises first connection configuration information used for simultaneously keeping the connection of a source node and a target node in a mobility process, and second connection configuration information used for reconfiguring the connection with the target node; executing connection operation based on the configuration information, and detecting whether the connection operation corresponding to the configuration information fails; and if the connection operation failure is detected, executing a processing procedure corresponding to the failed connection operation. In the invention, the failed connection operation can be timely found by detecting whether the corresponding connection operation fails, and the processing process corresponding to the connection operation is adopted for processing, thereby realizing the reasonable processing of different connection operation failures in the moving process, enabling the failed connection to be quickly recovered, and reducing the loss of data.

Description

Connection processing method and device

The application is a divisional application, and the application date of the original application is as follows: 08 month 17 in 2018; the application numbers are: 201810942854. X; the invention has the name: provided are a connection processing method and equipment.

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a connection processing method and device.

Background

In the Fifth Generation mobile communication technology (5G), during a mobility procedure, in order to meet a zero millisecond interruption delay of data transmission between a terminal device and a network side device, the terminal device needs to perform data transceiving with a source node and a target node at the same time. In order to achieve data connection with the source node and the target node, the terminal device may generally adopt a Dual Connectivity (DC) architecture.

The DC architecture generally includes a Master Cell Group (MCG) and a Secondary Cell Group (SCG), so that a terminal device using the DC architecture can perform data connection with a source node and a target node at the same time. In addition, the DC architecture also supports a Packet Data Convergence Protocol (PDCP) replication function, so that different bearer types may be generated, and correspondence between Protocol entities of bearer types of each type and a cell group of the DC architecture is as shown in fig. 1(a), fig. 1(b), and fig. 1 (c). In the case shown in fig. 1(a), the MCG bearer and the SCG bearer are respectively an MCG entity corresponding to the MCG bearer is a PDCP/Radio Link Control (RLC)/Medium Access Control (MAC) entity, and an SCG entity corresponding to the SCG bearer is a PDCP/RLC/MAC entity; the bearer type shown in fig. 1(b) is a split bearer, where the bearer corresponds to the PDCP entity in one cell group, but the corresponding two RLC entities and two MAC entities are in different cell groups; the bearer type shown in fig. 1(c) is a duplicate bearer, and the bearer corresponds to one PDCP entity, two RLC entities and one MAC entity in one cell group.

For a terminal device adopting a DC architecture, how to establish a connection and reasonably process problems encountered in the connection when performing mobility management such as node switching, SCG change, SCG addition, and the like become problems that need to be solved at present.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a connection processing method and device, so as to solve the problem of how to establish a connection and reasonably process the problems encountered in the connection during mobility management.

To solve the above technical problem, the embodiment of the present invention is implemented as follows:

in a first aspect, an embodiment of the present invention provides a connection processing method, which is applied to a terminal device, and the method includes:

receiving configuration information, wherein the configuration information comprises first connection configuration information used for simultaneously keeping connection between a source node and a target node in a mobility process, and second connection configuration information used for reconfiguring connection with the target node;

executing connection operation based on the configuration information, and detecting whether the connection operation corresponding to the configuration information fails;

and if the connection operation is detected to fail, executing a processing procedure corresponding to the failed connection operation.

In a second aspect, an embodiment of the present invention provides a connection processing method, which is applied to a network device, and the method includes:

sending configuration information, wherein the configuration information comprises first connection configuration information used for simultaneously keeping connection between a source node and a target node in a mobility process, and second connection configuration information used for reconfiguring connection with the target node;

the configuration information is used for the terminal equipment to execute connection operation according to the configuration information.

In a third aspect, an embodiment of the present invention provides a terminal device, where the terminal device includes:

a receiving module, configured to receive configuration information, where the configuration information includes first connection configuration information used for maintaining connection between a source node and a target node in a mobility procedure, and second connection configuration information used for reconfiguring connection with the target node;

a first execution module for executing a connection operation based on the configuration information;

the detection module is used for detecting whether the connection operation corresponding to the configuration information fails or not;

and the second execution module is used for executing the processing procedure corresponding to the failed connection operation if the connection operation failure is detected.

In a fourth aspect, an embodiment of the present invention provides a network-side device, where the device includes:

a first sending module, configured to send configuration information, where the configuration information includes first connection configuration information used for maintaining connection between a source node and a target node in a mobility procedure, and second connection configuration information used for reconfiguring connection with the target node;

In a fifth aspect, an embodiment of the present invention further provides a terminal device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the connection processing method according to the first aspect.

In a sixth aspect, an embodiment of the present invention further provides a network side device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the connection processing method according to the second aspect.

In a seventh aspect, the present invention provides a computer-readable storage medium, where a computer program is stored, and the computer program, when executed by a processor, implements the steps of the connection processing method according to the first aspect, or the computer program, when executed by the processor, implements the steps of the connection processing method according to the second aspect.

By the connection processing method and the device provided by the embodiment of the invention, the received configuration information comprises the first connection configuration information and the second connection configuration information in the mobility process, and corresponding connection operation is executed according to the configuration information; respectively executing the corresponding connection operation of the first connection configuration information and the second connection configuration information; whether the corresponding connection operation fails or not is detected, the failed connection operation can be timely found, and the processing process corresponding to the connection operation is adopted for processing, so that the reasonable processing of different connection operation failures in the moving process is realized, the failed connection can be quickly recovered, and the loss of data is reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:

FIG. 1(a) is one of the schematic diagrams of a DC architecture;

FIG. 1(b) is a second schematic diagram of the DC architecture;

FIG. 1(c) is a third schematic diagram of a DC architecture;

fig. 2 is one of method flow diagrams of a connection processing method provided by an embodiment of the present invention;

fig. 3 is a flowchart of a method for detecting whether a first connection operation fails in a connection processing method according to an embodiment of the present invention;

fig. 4 is a flowchart of a method for detecting whether a connection operation fails in a connection processing method according to an embodiment of the present invention;

fig. 5 is a second flowchart of a connection processing method according to another embodiment of the present invention;

FIG. 6 is an interaction flow diagram of a connection processing method according to an embodiment of the present invention;

FIG. 7 is a second interaction flow diagram of a connection processing method according to an embodiment of the present invention;

fig. 8 is a schematic block diagram of a terminal device according to an embodiment of the present invention;

fig. 9 is a schematic block diagram of a network-side device according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a network-side device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. As used in the specification and in the claims, "and/or" means at least one of the connected objects.

The technical scheme of the invention can be applied to various communication systems, such as: global System for Mobile communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE)/enhanced Long Term Evolution (LTE-a), New Radio, NR, and so on.

User Equipment (UE), also referred to as a User Terminal, a Mobile Terminal (Mobile Terminal), a Mobile User Equipment (ms), etc., may communicate with one or more core networks via a Radio Access Network (RAN, for example), and may be a Mobile Terminal, such as a Mobile phone (or referred to as a "cellular" phone) and a computer having a Mobile Terminal, such as a portable, pocket, hand-held, computer-included, or vehicle-mounted Mobile device, which exchange voice and/or data with the Radio Access Network.

The network side device, configured to communicate with a user side device, may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, an evolved Node B (eNB or e-NodeB) in LTE, and a 5G Base Station (gNB), and the present invention is not limited thereto, but for convenience of description, the following embodiments use the gNB as an example for description.

The technical solutions provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

The English abbreviations related to the embodiments of the present invention are noted below.

Master Node (MN);

a Secondary Node (SN);

radio Resource Control (RRC);

service Data Adaptation Protocol (SDAP);

message Authentication Code for Integrity verification (MAC-I).

The embodiment of the invention provides a connection processing method, which is applied to terminal equipment and can be executed by the terminal equipment. Fig. 2 is a schematic flow chart of a connection processing method according to an embodiment of the present invention, and as shown in fig. 2, the method at least includes the following steps:

step 102, receiving configuration information, wherein the configuration information comprises first connection configuration information used for simultaneously keeping the connection between the source node and the target node in the mobility process, and second connection configuration information used for reconfiguring the connection between the source node and the target node.

In a specific implementation, the receiving of the configuration information in step 102 may be sent by the network side device. The configuration information may be configuration information of a command to connect a node switching command for a terminal device, an SCG to add a connection node, or a command to change a connection node of an SCG.

The source node may be understood as a node to which the terminal device is currently connected, and the target node may be understood as a node that needs to be added, handed over, or changed. Specifically, the source node may be a source cell, a source base station, a source MN, or a source SN of the terminal device in the mobility process; the target node may be a target cell, a target base station, a target MN or a target SN of the terminal device during mobility.

And 104, executing the connection operation based on the configuration information, and detecting whether the connection operation corresponding to the configuration information fails.

Specifically, in step 104, the performing the connection operation based on the configuration information includes: performing a first connection operation based on the first connection configuration information and performing a second connection operation based on the second connection configuration information in a mobility procedure.

Wherein, the performing the first connection operation may be establishing a connection with the target node on the basis of maintaining the connection with the source node; the performing of the second connection operation may be reconfiguring the connection with the target node while releasing the connection with the source node.

Correspondingly, the detecting whether the connection operation corresponding to the configuration information fails includes: detecting whether a first connection operation corresponding to the first connection configuration information fails and detecting whether a second connection operation corresponding to the second connection configuration information fails.

And step 106, if the connection operation is detected to fail, executing a processing procedure corresponding to the failed connection operation.

In the embodiment of the invention, if the first connection operation is detected to fail, a processing procedure corresponding to the first connection operation is executed; and if the second connection operation is detected to fail, executing a processing procedure corresponding to the second connection operation.

In the connection processing method provided in the embodiment of the present specification, in the mobility process, corresponding connection operations are executed based on the first connection configuration information and the second connection configuration information, and by detecting whether the corresponding connection operations fail, the failed connection operations can be found in time, and the processing procedure corresponding to the connection operations is adopted for processing, so that reasonable processing of different connection operation failures in the mobility process is achieved, the failed connection can be recovered quickly, and data loss is reduced.

In the embodiment of the present invention, different methods may be adopted to detect whether the connection operation fails, and accordingly, the types of the connection operation failures detected by the different methods may differ, and further, the connection operation failures need to be processed through different processing procedures. The specific detection process in step 104 and the corresponding specific processing process in step 106 are described in detail below.

Specifically, in step 104, it may be detected whether the connection operation fails through a timer disposed on the terminal device, and the type of the connection failure detected in this way is a connection failure caused by timeout of the timer. The detection of whether the connection operation fails through the timer can be implemented in at least the following two ways, which will be described below.

In the first way, the first step is to perform the following steps,

timing a first connection operation corresponding to the first connection configuration information through a first timer, and detecting whether the first connection operation fails or not based on a timing result of the first timer; and timing a second connection operation corresponding to the second connection configuration information through a second timer, and detecting whether the second connection operation fails or not based on a timing result of the second timer.

In the embodiment of the present invention, two timers, namely, a first timer and a second timer, are arranged on the terminal device, and whether the first connection operation fails or not is detected by the first timer, and whether the second connection operation fails or not is detected by the second timer.

The specific process of timing the first connection operation corresponding to the first connection configuration information by the first timer may be as follows:

starting a first timer when a first connection operation is executed based on the first connection configuration information; the first timer is stopped when the first connection is established.

In specific implementation, the duration of the first timer from the starting time to the stopping time can be determined as a timing result of the first timer; wherein, the duration of the first timer is used for representing the connection duration of the first connection operation. For example, a first timing time of the first timer at the time of starting and a second timing time of the first timer at the time of stopping may be recorded, and the time length of the first timer may be determined as the timing result of the first timer by subtracting the first timing time from the second timing time.

Of course, the foregoing describes only one specific implementation manner of determining the timing result of the first timer, and the specific implementation manner of determining the timing result of the timer in the art is not limited to the foregoing one, and may also be implemented by other manners, which are merely exemplary and do not limit the embodiments of the present invention.

In addition, in the embodiment of the present invention, when the first connection operation is started, the first timer is started; the first timer is stopped when the first connection is established (i.e., the first connection is established). Therefore, in order to be able to determine when to stop the first timer, it needs to be determined whether the first connection is established.

In the embodiment of the present invention, whether the first connection is established may be determined by at least one of the following manners:

(1) if receiving indication information which is sent by network side equipment and used for finishing the random access process to the target node, determining that a first connection is established;

(2) if the fact that the terminal equipment sends confirmation information of the completion of the establishment of the first connection to the network side equipment is detected, the establishment of the first connection is determined;

(3) and if receiving confirmation information of the first connection establishment completion sent by the network side equipment, determining that the first connection is established.

Specifically, whether the first connection is established may be determined by any one of the above manners, a combination of any two manners, or three manners.

Of course, the embodiment of the present invention only lists three specific implementation processes for determining whether the first connection is established, and the determination of whether the first connection is established may also be implemented in other manners, that is, the specific manner for determining whether the first connection is established is not limited thereto, and is not listed here.

The following describes the specific implementation of the above three modes in detail.

In the embodiment of the present invention, when the terminal device performs the first connection operation based on the first connection configuration information, the terminal device triggers the random access procedure to the target node, and therefore, whether the first connection is established can be detected by detecting whether the random access procedure is completed. Specifically, in the above (1), it may be detected in real time or according to a set time interval whether indication information that a random access procedure to a target node is completed, which is sent by a network side device, is received, and if it is detected that the indication information sent by the network side device is received, it is determined that the first connection is established.

After the terminal device establishes the first connection, it sends a message of completing RRC configuration to the network side device, so the confirmation information of completing the establishment of the first connection in (2) above may be the message of completing RRC configuration. Specifically, in the above (2), it may be detected in real time or at set time intervals whether the terminal device sends the confirmation information of the first connection establishment completion to the network-side device, and if it is detected that the terminal device sends the confirmation information to the network-side device, it is determined that the first connection is established.

In addition, in the embodiment of the present invention, if the terminal device establishes the first connection, the network side device may send a message that the RRC configuration is completed to the terminal device. Therefore, in the above (3), the confirmation information of the completion of the first connection establishment sent by the network side device may be a message of completion of RRC configuration. Specifically, in the above (3), it may be detected in real time or at set time intervals whether the terminal device receives the confirmation information that the first connection establishment is completed, where the confirmation information is sent by the network-side device, and if the confirmation information is detected, it is determined that the first connection is established.

In the embodiment of the present invention, in the above (1), (2), and (3), data transmission may be performed between the network-side device and the source node through connection therebetween.

Specifically, in this implementation manner, the timing, by the second timer, the second connection operation corresponding to the second connection configuration information specifically includes:

starting a second timer when a second connection operation is performed based on the second connection configuration information; when the second connection operation is established, the second timer is stopped.

In specific implementation, the duration of the second timer from the starting time to the stopping time can be determined as a timing result of the second timer; and the duration of the second timer is used for representing the connection duration corresponding to the second connection operation. For example, a first timing time of the second timer at the start and a second timing time of the second timer at the stop may be recorded, and the length of the second timer may be determined as the timing result of the second timer by subtracting the first timing time from the second timing time.

Of course, the foregoing describes only one specific implementation manner of determining the timing result of the second timer, and the specific implementation manner of determining the timing result of the timer in the art is not limited to the foregoing one, and may also be implemented by other manners, which are merely exemplary and do not limit the embodiments of the present invention.

In addition, in the embodiment of the present invention, when the second connection operation starts to be performed, the second timer is started; the second timer is stopped when the second connection is established (i.e., the second connection is established). Therefore, in order to be able to determine when to stop the second timer, it needs to be determined whether the second connection is established.

1) If receiving indication information which is sent by the network side equipment and indicates that the random access process of the target node is completed, determining that a second connection is established;

2) if the fact that the terminal equipment sends confirmation information of second connection establishment completion to the network side equipment is detected, the second connection is determined to be established;

3) and if receiving confirmation information of the second connection establishment completion sent by the network side equipment, determining that the second connection is established.

Specifically, whether the second connection is established may be determined by any one of the above manners; or, whether the second connection is established or not can be judged by combining any two of the above modes; or, the above three methods are combined to judge whether the second connection is established.

Of course, the embodiment of the present invention only lists three specific implementation processes for determining whether the second connection is established, and the determination of whether the second connection is established may also be implemented in other manners, that is, the specific manner for determining whether the second connection is established is not limited thereto, and is not listed here.

In the embodiment of the present invention, when the terminal device performs the second connection operation based on the second connection configuration information, the random access procedure to the target node is triggered to be performed, and therefore, whether the second connection is established or not can be detected by detecting whether the random access procedure of the target node is completed or not. Specifically, in 1) above, it may be detected in real time or according to a set time interval whether indication information that a random access procedure to a target node is completed, which is sent by a network side device, is received, and if it is detected that the indication information sent by the network side device is received, it is determined that a second connection is established.

After the terminal device establishes the second connection, it sends a message of completing RRC configuration to the network side device, so the confirmation information of completing the establishment of the second connection in 2) above may be the message of completing RRC configuration. Specifically, in 2), it may be detected in real time or at set time intervals whether the terminal device sends the confirmation information of the second connection establishment completion to the network-side device, and if it is detected that the terminal device sends the confirmation information to the network-side device, it is determined that the second connection is established.

In addition, in the embodiment of the present invention, if the terminal device establishes the second connection, the network side device may send a message that the RRC configuration is completed to the terminal device. Therefore, in the above 3), the confirmation information of the completion of the second connection establishment sent by the network side device may be a message of completion of RRC configuration. Specifically, in the above 3), it may be detected in real time or at set time intervals whether the terminal device receives the confirmation information that the network-side device has sent the second connection setup completion, and if the confirmation information that the network-side device has sent is detected, it is determined that the second connection is setup.

In addition, in order to implement detecting whether the connection operation fails through the first timer and the second timer, in the embodiment of the present invention, the configuration information further includes a first timing threshold of the first timer and a second timing threshold of the second timer;

accordingly, the detecting whether the first connection operation fails based on the timing result of the first timer includes: judging whether the first timer is overtime or not according to the first timing threshold; if so, determining that the first connection operation fails;

accordingly, the detecting whether the second connection operation fails based on the timing result of the second timer includes: judging whether the second timer is overtime or not according to a second timing threshold; if so, determining that the second connection operation fails.

In specific implementation, the timing result of the first timer may be compared with a first timing threshold, and if the timing result of the first timer is greater than or equal to the first timing threshold, the first timer is determined to be overtime; and comparing the timing result of the second timer with a second timing threshold, and if the timing result of the second timer is greater than or equal to the second timing threshold, determining that the second timer is overtime.

Of course, the above description only lists one specific implementation manner for determining whether the first timer and the second timer are overtime, and the specific implementation manner for determining whether the first timer and the second timer are overtime is not limited thereto, and may also be implemented by other manners, which is not described in detail herein.

For convenience of understanding, the following will describe in detail a specific procedure for detecting an operation failure in the method provided by the embodiment of the present invention by taking an example of detecting whether the first connection operation fails.

Fig. 3 shows a flowchart of a method for detecting whether a first connection operation fails in a mobility procedure in an embodiment of the present invention, where the method shown in fig. 3 at least includes the following steps:

step 202, when the mobile terminal is in the mobility process, when a first connection operation is executed based on the first connection configuration information, a first timer is started.

Step 204, judging whether a first connection operation is established; if yes, go to step 206;

step 206, stop the first timer.

Step 208, judging whether the first timer is overtime according to the first timing threshold; if yes, go to step 210.

Step 210, determining that the first connection operation fails.

The first timing threshold is configured by the network side device.

In the embodiment of the invention, the first connection operation is timed by the first timer, the second connection operation is timed by the second timer, and whether the first connection operation and the second connection operation fail or not is respectively detected according to the timing duration of the first timer and the second timer.

In the second way, the first way is,

timing a first connection operation corresponding to the first connection configuration information through a first timer, and detecting whether the first connection operation fails or not based on a timing result of the first timer; and timing a first connection operation corresponding to the first connection configuration information and a second connection operation corresponding to the second connection configuration information through a second timer, and detecting whether the second connection operation fails or not based on a timing result of the second timer.

Specifically, in this manner, the specific process of timing the first connection operation corresponding to the first connection configuration information by the first timer and detecting whether the first connection operation fails based on the timing result of the first timer is the same as that in the first case, and reference may be made to the detailed description of the first case, which is not repeated herein.

It should be noted that, in this manner, the time length counted by the second timer is the total connection time length of the first connection operation and the second connection operation.

Correspondingly, the timing the first connection operation corresponding to the first connection configuration information and the second connection operation corresponding to the second connection configuration information by the second timer specifically includes the following processes:

starting a first timer when a first connection operation is executed based on the first connection configuration information; the second timer is stopped when the second connection is established.

Determining the duration of the second timer from the starting time to the stopping time as a timing result of the second timer; and the duration of the second timer is used for representing the total connection duration corresponding to the first connection operation and the second connection operation.

In this way, the specific process of determining whether the second connection operation is established is the same as that in the first case, and details are not repeated here.

In addition, in this way, the timing duration of the second timer is the total connection duration corresponding to the first connection operation and the second connection operation. The specific size of the timing threshold corresponding to the second timer in the configuration information sent by the network side device is different from the second timing threshold in one of the above-described modes, and in this mode, the timing threshold corresponding to the second timer is recorded as the third timing threshold for distinction.

Accordingly, the detecting whether the second connection operation fails based on the timing result of the second timer includes:

judging whether the second timer is overtime or not according to a third timing threshold; if so, determining that the second connection operation fails.

In order to facilitate understanding of a specific implementation procedure for detecting whether the first connection operation and the second connection operation fail in this manner, the following description will be made by using specific embodiments.

Fig. 4 is a flowchart of a method for detecting whether a connection operation fails in an embodiment of the present invention, where the method shown in fig. 4 at least includes the following steps:

step 302, when in a mobility process, executing a first connection operation based on first connection configuration information and starting a first timer and a second timer;

step 304, judging whether a first connection operation is established; if yes, go to step 306;

step 306, stop the first timer.

Step 308, judging whether the first timer is overtime according to the first timing threshold; if yes, go to step 310.

At step 310, it is determined that the first connection operation failed.

In step 312, a second connection operation is performed based on the second connection configuration information.

Step 314, judging whether a second connection operation is established; if yes, go to step 316.

Step 316, stop the second timer.

Step 318, judging whether the second timer is overtime according to the third timing threshold; if yes, go to step 320.

Step 320, determining that the second connection operation fails.

The first timing threshold and the third timing threshold are configured by the network side device.

In the embodiment of the present invention, when detecting whether a connection operation fails through a first timer and a second timer, when establishing the first connection operation based on first connection configuration information, the first timer and the second timer are started, when establishing the first connection operation, the first timer is stopped, and when establishing the second connection operation, the second timer is stopped; the method avoids that when the second connection operation is established based on the second connection configuration information, the second timer is restarted, and the two timers are simultaneously started at one trigger moment, so that the detection process is more convenient, and whether the connection operation fails due to the overtime of the timers can be simply and conveniently detected.

In the above description, whether a connection operation failure occurs due to timeout of the timer is detected by the timer, and accordingly, if the first connection operation failure is detected, the processing procedure corresponding to the failed connection operation is executed in step 106, and the processing procedure corresponding to the first connection operation failure may specifically include at least one of the following processing procedures a1 to a 6:

a1, reporting failure information to network side equipment; wherein the failure information at least comprises the following information: a type of first connection operation failure; measurement information of at least one cell among a source node cell, a target node cell and a neighbor cell;

a2, executing a second connection operation according to the second connection configuration information;

a3, reestablishing RRC connection between the terminal equipment and the network side equipment;

a4, restoring the connection state of the terminal equipment to the connection state before the connection operation is executed;

a5, stopping or suspending the connection of the terminal device and the source node;

and A6, resetting or rebuilding the connection entity of the terminal equipment and the source node.

Specifically, in the above-mentioned a1, the type of the first connection operation failure is a connection failure caused by a timeout of the first timer. In this case, the failure information may be reported to the network-side device through the connection with the source node. And after receiving the failure information of the first connection operation failure reported by the terminal equipment, the network side equipment sends connection reconfiguration information to the terminal equipment so as to enable the terminal equipment to establish connection with the node which can establish the connection currently.

In the above-described a4, the connection state of the terminal device is restored to the connection state before the connection operation is performed, which can be understood as restoring the connection state of the terminal device to the connection state before the first connection operation is performed. That is, before the first connection operation is performed, the terminal device establishes a connection with which node, and the terminal device still maintains the connection with the node.

In a5, stopping or suspending the connection of the terminal device to the source node is to stop the reception and transmission of data through the connection to the source node.

In the above a6, the entity resetting or reestablishing the connection between the terminal device and the source node may be a MAC/RLC/PDCP/SDAP entity to which the terminal device is connected to the source node.

If it is detected that the second connection operation fails, the processing procedure corresponding to the failed connection operation is executed in step 106, and the processing procedure corresponding to the failed second connection operation is executed, which may specifically include at least one of the following processing procedures B1 to B3:

b1, reestablishing RRC connection between the terminal equipment and the network side equipment;

b2, restoring the connection state of the terminal equipment to the connection state before the connection operation is executed;

b3, reporting failure information to network side equipment; wherein the failure information at least comprises the following information: a type of second connection operation failure; measurement information of at least one of the source node cell, the target node cell and the neighbor cell.

In the above B2, the connection state of the terminal device is restored to the connection state before the connection operation is performed, and it is understood that the connection state of the terminal device is restored to the connection state before the first connection operation is performed. That is, before the first connection operation is performed, the terminal device establishes a connection with which node, and the terminal device still maintains the connection with the node.

In the above B3, the type of the failure of the second connection operation is a failure caused by the timeout of the second timer. In a specific implementation manner, after the processing procedure of B1 is completed, failure information may be reported to the network side device. Specifically, after receiving the failure information of the first connection operation failure reported by the terminal device, the network side device sends the connection reconfiguration information to the terminal device, so that the terminal device establishes a connection with a node which can currently establish a connection.

Of course, in the embodiment of the present invention, in addition to detecting whether a connection failure occurs due to the timeout of the timer through the timer, in the step 104, detecting whether the connection operation corresponding to the configuration information fails may further include at least one of the following detection manners S1-S7:

s1, if detecting the physical layer of the connection is out of step, determining that the connection operation corresponding to the configuration information is failed;

s2, if detecting that the random access of the connected MAC layer reaches the maximum sending times, determining that the connection operation corresponding to the configuration information fails;

s3, determining that the connection operation corresponding to the configuration information fails if it is detected that the data transmission frequency of the terminal device reaches the maximum retransmission frequency of the connected RLC entity;

s4, if detecting the RRC message reconfiguration failure of the connection, determining that the connection operation corresponding to the configuration information fails;

s5, if it is detected that the beam recovery process of the terminal device fails, determining that the connection operation corresponding to the configuration information fails;

s6, if the MAC-I error of the PDCP entity is detected, determining that the connection operation corresponding to the configuration information fails;

s7, if the difference value of the uplink transmission subframe boundary between the main cell group and the auxiliary cell group of the terminal equipment exceeds the maximum uplink transmission timing difference, determining that the connection operation corresponding to the configuration information fails.

Specifically, if the first connection operation is failed by using one or more combinations of the above-mentioned S1-S7, the connection mentioned in S1-S7 is the first connection, and if the second connection operation is failed by using one or more combinations of the above-mentioned S1-S7, the connection mentioned in S1-S7 is the second connection.

The following will describe in detail the specific implementation of the methods in S1-S7, taking the detection of whether the first connection operation fails as an example.

In S1, it is detected whether the physical layer of the first connection is out-of-sync, and if so, it is determined that the operation of the first connection fails. Specifically, in the embodiment of the present invention, it may be detected whether the physical layer of the first connection is out of synchronization by detecting whether the timer T310 is overtime, and if the timer T310 is overtime, it is determined that the physical layer of the first connection is out of synchronization.

In the manner shown in S2, during the first connection operation, the number of times of random access of the MAC layer of the first connection is detected, and it is determined whether the number of times of random access reaches the maximum number of times of transmission (the maximum number of times of transmission may be understood as the maximum number of attempts), and if so, it is determined that the first connection operation fails.

In the manner shown in S3, during the first connection operation, the number of data transmissions of the terminal device is detected, and it is determined whether the number of data transmissions reaches the number of large-mouth retransmissions of the RLC entity of the first connection, and if so, it is determined that the first connection operation fails.

In the method shown in S4, it is detected whether the RRC message of the first connection fails to be reconfigured, and if the RRC message fails to be reconfigured, it is determined that the first connection operation fails.

In the manner shown in S5, it is determined that the first connection operation has failed if the failure of the beam recovery process is detected by detecting whether the beam recovery process of the terminal device has failed.

In the manner shown in S6, it may be detected whether the MAC-I of the PDCP entity of the first connection is wrong, and if the MAC-I is detected as wrong, it is determined that the first connection operation fails.

In the manner shown in S7, it may be detected whether a difference between subframe boundaries of uplink transmission between the primary cell group and the secondary cell group of the terminal device exceeds the maximum uplink transmission timing difference, and if the difference exceeds the maximum uplink transmission timing difference, it is determined that the first connection operation fails.

In the embodiment of the present invention, the first connection operation failure includes a connection operation failure of the terminal device with the source node and/or the target node; the connection operation between the terminal device and the source node may fail, the connection operation between the terminal device and the target node may fail, or the connection operations between the terminal device and both the source node and the target node may fail.

Accordingly, in the embodiment of the present invention, if the failure of the first connection operation is detected through at least one of the above-mentioned methods S1-S7; in step 106, if the processing procedure corresponding to the failed connection operation is executed, the processing procedure corresponding to the first connection operation is executed, and specifically, the processing procedure includes at least one of the following C1-C9 processes:

c1, reporting failure information to the network side equipment; wherein the failure information at least includes: a type of first connection operation failure; measurement information of at least one of the source node cell, the target node cell and the neighbor cell.

C2, executing the connection operation again based on the configuration information;

c3, executing a second connection operation based on the second connection configuration information;

c4, reestablishing RRC connection between the terminal equipment and the network side equipment;

c5, restoring the connection state of the terminal equipment to the connection state before the connection operation is executed;

c6, stopping or suspending the connection of the terminal equipment and the source node;

c7, resetting or rebuilding the connection entity of the terminal device and the source node;

c8, stopping or suspending the connection of the terminal device and the target node;

c9, resetting or rebuilding the connection entity of the terminal device and the target node.

Here, in C1, the type of the first connection operation failure is determined based on the determination manner of the first connection operation failure, that is, the type of the first connection operation failure corresponds to the determination manner of the first connection operation failure. The failure information reported to the network side device may be failure information of connection failure between the terminal device and the source node and/or the target node. And after receiving the failure information of the first connection operation failure reported by the terminal equipment, the network side equipment sends connection reconfiguration information to the terminal equipment so as to enable the terminal equipment to establish connection with the node which can establish the connection currently.

In C2, the switching is continued or the SCG is added or changed, and the operation can be resumed from the first connection operation based on the first connection configuration information.

In C5, the restoring the connection state of the terminal device to the connection state before the connection operation is performed may be to rollback the connection configuration of the terminal device to the configuration of the terminal device before the first connection operation is performed. That is, before the first connection operation is performed, the terminal device establishes a connection with which node, and the terminal device still maintains the connection with the node.

In C6, stopping or suspending the connection of the terminal device with the source node is to stop the reception and transmission of data through the connection with the source node.

In C7, the resetting or reestablishing of the connection entity between the terminal device and the source node may be a MAC/RLC/PDCP/SDAP entity that resets or reestablishes the connection entity between the terminal device and the source node.

In C8, stopping or suspending the connection of the terminal device with the target node is to stop the reception and transmission of data through the connection with the target node.

In C9, the resetting or reestablishing of the connection entity between the terminal device and the target node may be a MAC/RLC/PDCP/SDAP entity that resets or reestablishes the connection entity between the terminal device and the target node.

And the second connection operation failure comprises the connection operation failure of the terminal equipment and the target node.

Accordingly, in the embodiment of the present invention, if the failure of the first connection operation is detected through at least one of the above-mentioned methods S1-S7; in step 106, if the processing procedure corresponding to the failed connection operation is executed, the processing procedure corresponding to the second connection operation is executed, specifically, the processing procedure includes at least one of the following processes D1-D4:

d1, executing the connection operation again based on the configuration information;

d2, reestablishing RRC connection between the terminal equipment and the network side equipment;

d3, restoring the connection state of the terminal equipment to the connection state before the connection operation is executed;

d4, reporting failure information to the network side equipment; wherein the failure information at least includes: a type of second connection operation failure; measurement information of at least one of the source node cell, the target node cell, and a neighboring cell.

Specifically, the detailed descriptions of D1-D4 are omitted herein, and the processing procedure corresponding to the first connection operation is executed when the first connection operation fails.

In a specific implementation manner, after the RRC connection between the terminal device and the network side device is reestablished, the terminal device reports the failure information to the network side device.

In the connection processing method provided by the embodiment of the present invention, the received configuration information includes first connection configuration information and second connection configuration information, and connection operations corresponding to the first connection configuration information and the second connection configuration information are respectively executed; whether the corresponding connection operation fails or not is detected, the failed connection operation can be timely found, and the processing process corresponding to the connection operation is adopted for processing, so that the reasonable processing of different connection operation failures in the moving process is realized, the failed connection can be quickly recovered, and the loss of data is reduced.

Corresponding to the foregoing embodiment, an embodiment of the present invention further provides a connection processing method applied to a network side device, and in the embodiment of the present invention, details of parts that are the same as those in the foregoing connection processing method embodiment may refer to the contents of the foregoing embodiment, and this embodiment is not repeated. Fig. 5 is a second flowchart of a method of a connection processing method according to an embodiment of the present invention, where the method shown in fig. 5 at least includes the following steps:

step 402, sending configuration information, wherein the configuration information comprises first connection configuration information used for simultaneously keeping the connection between the source node and the target node in the mobility process, and second connection configuration information used for reconfiguring the connection between the source node and the target node;

and the configuration information is used for the terminal equipment to execute connection operation according to the configuration information.

Specifically, when performing the connection operation according to the configuration information, the terminal device performs a first connection operation according to the first connection configuration information, and performs a second connection operation according to the second connection configuration information.

When the terminal device executes the connection operation according to the configuration information, the first timer is used for timing the first connection operation, and whether the first connection operation fails or not is detected according to a timing result of the first timer; and timing the second connection operation through the second timer, or timing the first connection operation and the second connection operation through the second timer, and detecting whether the second connection operation fails according to a timing result of the second timer.

In order to enable the terminal device to detect whether the first connection operation fails according to a timing result of the first timer, and detect whether the second connection operation fails according to a timing result of the second timer, in an embodiment of the present specification, the second configuration information includes a first timing threshold and a second timing threshold;

a first timing threshold, configured to detect, by the terminal device, whether the first connection operation based on the first connection configuration information fails according to the first timing threshold;

and the second timing threshold value is used for detecting whether the second connection operation based on the second connection configuration information fails or not by the terminal equipment according to the second timing threshold value.

In the embodiment of the invention, the terminal equipment judges whether the first timer is overtime or not according to the first timing threshold; if so, determining that the first connection operation fails; judging whether the second timer is overtime according to a second timing threshold; if so, determining that the second connection operation fails.

Fig. 6 shows one of interaction flowcharts of a connection processing method according to an embodiment of the present invention, where the method shown in fig. 6 at least includes the following steps:

step 502, the network side device sends configuration information to the terminal device.

The configuration information comprises first connection configuration information used for simultaneously keeping the connection of the source node and the target node in the mobility process, and second connection configuration information used for reconfiguring the connection of the source node and the target node; the configuration information also includes a first timing threshold and a second timing threshold.

Step 504, in the mobility process, the terminal device executes a first connection operation based on the first connection configuration information, and starts a first timer.

Step 506, if the terminal device determines that the first connection is established, the first timer is stopped.

And step 508, the terminal device judges whether the first timer is overtime according to the first timing threshold, and if yes, the terminal device determines that the first connection operation fails.

Step 510, the terminal device executes a failure handling procedure corresponding to the first connection operation.

In step 512, the terminal device performs a second connection operation based on the second connection configuration information, and starts a second timer.

And step 514, if the terminal equipment determines that the second connection is established, stopping the second timer.

In step 516, the terminal device determines whether the second timer is overtime according to the second timing threshold, and if yes, determines that the second connection operation fails.

Step 518, the terminal device executes a failure handling procedure corresponding to the second connection operation.

Fig. 7 shows a second interaction flowchart of the connection processing method according to the embodiment of the present invention, where the method shown in fig. 7 at least includes the following steps:

step 602, the network side device sends configuration information to the terminal device.

The configuration information comprises first connection configuration information used for simultaneously keeping the connection of the source node and the target node in the mobility process, and second connection configuration information used for reconfiguring the connection of the source node and the target node; the configuration information also includes a first timing threshold and a third timing threshold.

Step 604, in the mobility process, the terminal device executes a first connection operation based on the first connection configuration information, and starts a first timer and a second timer.

Step 606, if the terminal device determines that the first connection is established, the first timer is stopped.

Step 608, the terminal device determines whether the first timer is overtime according to the first timing threshold, and if yes, determines that the first connection operation fails.

Step 610, the terminal device executes a failure handling process corresponding to the first connection operation.

In step 612, the terminal device performs a second connection operation based on the second connection configuration information.

And step 614, if the terminal equipment determines that the second connection is established, stopping the second timer.

In step 616, the terminal device determines whether the second timer is overtime according to the third timing threshold, and if yes, determines that the second connection operation fails.

Step 618, the terminal device executes a failure handling procedure corresponding to the second connection operation.

In addition, in the embodiment of the present invention, when the terminal device determines that the first connection operation fails or the second connection operation fails, failure information of the connection operation failure is reported to the network side device. Specifically, the failure information at least includes the following information:

a type of connection operation failure; measurement information of at least one of the source node cell, the target node cell and the neighbor cell.

After receiving the failure information reported by the terminal equipment, the network side equipment sends connection reconfiguration information to the terminal equipment; and the connection reconfiguration information is used for reestablishing the connection according to the connection reconfiguration information when the terminal equipment fails in connection operation.

Specifically, when the connection operation fails, the terminal device may establish a connection with any node that can currently establish a connection.

In the connection processing method provided by the embodiment of the present invention, the configuration information sent to the terminal device includes the first connection configuration information and the second connection configuration information, so that the terminal device executes different connection operations according to the first connection configuration information and the second connection configuration information, which is convenient for mobility management, and maintains simultaneous connection with the source node and the target node during a moving process, and can also reduce interruption delay of data transmission during a mobility process.

Corresponding to the connection processing method provided by the foregoing embodiment, the present invention provides a terminal device, and the terminal device provided by the embodiment of the present invention can implement each process implemented by the terminal device in the foregoing embodiment.

Fig. 8 is a schematic diagram of a module composition of a terminal device according to an embodiment of the present invention, where the device shown in fig. 8 includes:

a receiving module 702, configured to receive configuration information, where the configuration information includes first connection configuration information used for maintaining a connection between a source node and a target node during a mobility procedure, and second connection configuration information used for reconfiguring a connection with the target node;

a first executing module 704, configured to execute a connection operation based on the configuration information;

a detecting module 706, configured to detect whether a connection operation corresponding to the configuration information fails;

the second executing module 708 is configured to, if it is detected that the connection operation fails, execute a processing procedure corresponding to the failed connection operation.

Optionally, the detecting module 706 includes:

a first timing unit, configured to time, by using a first timer, a first connection operation corresponding to the first connection configuration information;

a first detecting unit configured to detect whether the first connection operation has failed based on a timing result of the first timer;

a second timing unit, configured to time, by using a second timer, a second connection operation corresponding to the second connection configuration information;

a second detection unit configured to detect whether the second connection operation has failed based on a timing result of the second timer;

alternatively, the first and second electrodes may be,

the detecting module 706 includes:

a first detection unit configured to detect whether the first connection operation has failed based on a timing result of the first timer;

a third timing unit, configured to time, by using a second timer, a first connection operation corresponding to the first connection configuration information and a second connection operation corresponding to the second connection configuration information;

a third detecting unit, configured to detect whether the second connection operation fails based on a timing result of the second timer.

Optionally, the configuration information further includes a first timing threshold of the first timer and a second timing threshold of the second timer;

correspondingly, the first detecting unit is specifically configured to:

judging whether the first timer is overtime or not according to the first timing threshold; if so, determining that the first connection operation fails;

the second detection unit is specifically configured to:

judging whether the second timer is overtime or not according to a second timing threshold; and if so, determining that the second connection operation fails.

Optionally, the first timing unit is specifically configured to:

starting the first timer when executing a first connection operation based on the first connection configuration information; and stopping the first timer when the first connection is established.

Optionally, the first timing unit is further specifically configured to perform at least one of the following operations:

if receiving indication information sent by network side equipment and indicating that the random access process to the target node is completed, determining that the first connection is established;

if the confirmation information of the first connection establishment completion is sent to the network side equipment, the first connection is determined to be established;

and if receiving confirmation information of the first connection establishment completion sent by the network side equipment, determining that the first connection is established.

Optionally, the second timing unit is specifically configured to:

starting the second timer when executing a second connection operation based on the second connection configuration information;

and stopping the second timer when the second connection is established.

Optionally, the third timing unit is specifically configured to:

starting the second timer when executing a first connection operation based on the first connection configuration information;

and stopping the second timer when the second connection is established.

Optionally, the second timing unit is further configured to perform at least one of the following operations:

if receiving indication information sent by the network side equipment and indicating that the random access process to the target node is completed, determining that the second connection is established;

if the confirmation information of the second connection establishment completion is sent to the network side equipment, the second connection is determined to be established;

and if receiving the confirmation information of the second connection establishment completion sent by the network side equipment, determining that the second connection is established.

Optionally, the third timing unit is further configured to perform at least one of the following operations:

Optionally, if the connection operation failure is detected as the first connection operation failure;

the second executing module 708 is specifically configured to execute at least one of the following processes:

reporting failure information to network side equipment; wherein the failure information at least comprises the following information: a type of first connection operation failure; measurement information of at least one of the source node cell, the target node cell, and a neighboring cell;

executing a second connection operation according to the second connection configuration information;

reestablishing Radio Resource Control (RRC) connection between the terminal equipment and network side equipment;

restoring the connection state of the terminal equipment to the connection state before the connection operation is executed;

stopping or suspending the connection of the terminal equipment and the source node;

and resetting or rebuilding the connection entity of the terminal equipment and the source node.

Optionally, if the connection operation failure is detected as the second connection operation failure;

reestablishing RRC connection between the terminal equipment and network side equipment;

reporting failure information to network side equipment; wherein the failure information at least comprises the following information: a type of second connection operation failure; measurement information of at least one of the source node cell, the target node cell, and a neighboring cell.

Optionally, the detecting module 706 is further specifically configured to perform at least one of the following operations:

if the physical layer of the connection is detected to be out of step, determining that the connection operation corresponding to the configuration information fails;

if the random access of the connected media access control MAC layer is detected to reach the maximum sending times, determining that the connection operation corresponding to the configuration information fails;

if the data transmission times of the terminal equipment reach the maximum retransmission times of the connected Radio Link Control (RLC) entity, determining that the connection operation corresponding to the configuration information fails;

if detecting that the RRC message reconfiguration of the connection fails, determining that the connection operation corresponding to the configuration information fails;

if the beam recovery process of the terminal equipment is detected to be failed, determining that the connection operation corresponding to the configuration information is failed;

if the MAC-I error of the message authentication code for integrity verification of the PDCP entity of the packet data is detected, determining that the connection operation corresponding to the configuration information fails;

and if the difference value of the subframe boundaries of the uplink transmission between the main cell group and the auxiliary cell group of the terminal equipment exceeds the maximum uplink transmission timing difference, determining that the connection operation corresponding to the configuration information fails.

Optionally, if the connection operation failure is detected as a first connection operation failure corresponding to the first connection configuration information; the first connection operation failure includes: the connection operation between the terminal equipment and the source node and/or the target node is failed;

the second executing module 708 is further specifically configured to execute at least one of the following processes:

reporting failure information to network side equipment; wherein the failure information at least includes: a type of the first connection operation failure; measurement information of at least one of the source node cell, the target node cell, and a neighboring cell.

Executing connection operation based on the configuration information again;

resetting or rebuilding a connection entity of the terminal device and the source node;

stopping or suspending the connection of the terminal equipment and the target node;

and resetting or rebuilding the connection entity of the terminal equipment and the target node.

Optionally, if the connection operation failure is detected, detecting a second connection operation failure corresponding to the second connection configuration information; the second connection operation failure includes: the connection operation between the terminal equipment and the target node fails;

executing connection operation based on the configuration information again;

reporting failure information to network side equipment; wherein the failure information at least includes: a type of the second connection operation failure; measurement information of at least one of the source node cell, the target node cell, and a neighboring cell.

In the terminal device provided by the embodiment of the present invention, the received configuration information includes first connection configuration information and second connection configuration information, and the first connection configuration information and the second connection configuration information are respectively executed with corresponding connection operations; whether the corresponding connection operation fails or not is detected, the failed connection operation can be timely found, and the processing process corresponding to the connection operation is adopted for processing, so that the reasonable processing of different connection operation failures in the moving process is realized, the failed connection can be quickly recovered, and the loss of data is reduced.

Corresponding to the connection processing method provided in the foregoing embodiment, an embodiment of the present invention provides a network side device, and the network side device provided in the embodiment of the present invention can implement each process implemented by the network side device in the foregoing embodiment.

Fig. 9 is a schematic diagram of a module composition of a network-side device according to an embodiment of the present invention, where the network-side device shown in fig. 9 includes:

a first sending module 802, configured to send configuration information, where the configuration information includes first connection configuration information used for maintaining a connection between a source node and a target node in a mobility procedure, and second connection configuration information used for reconfiguring a connection with the target node;

Optionally, the configuration information includes a first timing threshold and a second timing threshold;

the first timing threshold is used for the terminal device to detect whether the first connection operation based on the first connection configuration information fails according to the first timing threshold;

the second timing threshold is used for the terminal device to detect whether the second connection operation based on the second connection configuration information fails according to the second timing threshold.

Optionally, the apparatus further includes:

a second sending module, configured to send connection reconfiguration information; and the connection reconfiguration information is used for reestablishing the connection according to the connection reconfiguration information when the terminal equipment fails in connection operation.

In the network-side device provided in the embodiment of the present invention, the configuration information sent to the terminal device includes the first connection configuration information and the second connection configuration information, so that the terminal device executes different connection operations according to the first connection configuration information and the second connection configuration information, which is convenient for mobility management, and maintains simultaneous connection with the source node and the target node during a mobility procedure, and can also reduce interruption delay of data transmission during the mobility procedure.

Corresponding to the connection processing method provided in the foregoing embodiment, this embodiment provides a terminal device, and the terminal device provided in the embodiment of the present invention can implement each process implemented by the terminal device in the foregoing embodiment.

Fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present invention, and as shown in fig. 10, the terminal device 900 includes: at least one processor 901, memory 902, at least one network interface 904, and a user interface 903. The various components in the terminal device 900 are coupled together by a bus system 905. It is understood that the bus system 905 is used to enable communications among the components. The bus system 905 includes a power bus, a control bus, and a status signal bus, in addition to a data bus. For clarity of illustration, however, the various buses are labeled in fig. 9 as bus system 905.

The user interface 903 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, among others.

It is to be understood that the memory 902 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration, and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDRS DRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 902 of the systems and methods described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, memory 902 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof: an operating system 9021 and application programs 9022.

The operating system 9021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is configured to implement various basic services and process hardware-based tasks. The application 9022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. A program implementing the method of an embodiment of the present invention may be included in application 9022.

In this embodiment of the present invention, the terminal device 900 further includes: memory 902, processor 901, a computer program stored on the memory 902 and executable on the processor 901, the computer program realizing the following steps when executed by the processor 901:

When executed by the processor 901, the computer program may also implement each step in the connection processing method in the embodiments of the present invention, and can achieve the same effect, and in order to avoid repetition, details are not described here again.

The method disclosed in the above embodiments of the present invention may be applied to the processor 901, or implemented by the processor 901. The processor 901 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 901. The Processor 901 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may reside in ram, flash memory, rom, prom, or eprom, registers, among other computer-readable storage media known in the art. The computer readable storage medium is located in the memory 902, and the processor 901 reads the information in the memory 902, and combines the hardware to complete the steps of the above method. Specifically, the computer-readable storage medium has stored thereon a computer program, which when executed by the processor 901 implements the steps in the above-described embodiments.

It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described in this disclosure may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in this disclosure. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

Corresponding to the connection processing method provided in the foregoing embodiment, this embodiment provides a network side device, and the network side device provided in the embodiment of the present invention can implement each process implemented by the network side device in the foregoing embodiment.

Fig. 11 is a schematic structural diagram of a network-side device according to an embodiment of the present invention, and as shown in fig. 11, the network-side device 1000 includes: a processor 1001, a transceiver 1002, a memory 1003, a user interface 1004, and a bus interface.

In this embodiment of the present invention, the network side device 1000 further includes: a computer program stored on the memory 1003 and executable on the processor 1001, the computer program, when executed by the processor 1001, implementing the steps of:

In fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1001 and various circuits of memory represented by memory 1003 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1002 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user-side devices, the user interface 1004 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1001 is responsible for managing a bus architecture and general processes, and the memory 1003 may store data used by the processor 1001 in performing operations.

The computer program can realize the respective steps of the connection processing method in the above-described embodiments when executed by the processor 1001.

The network side device 1000 can implement each process implemented by the network side device in the foregoing embodiments, and achieve the same technical effect, and for avoiding repetition, details are not described here.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the connection processing method in the foregoing embodiments and can achieve the same technical effect, or when the computer program is executed by a processor, the computer program implements each process of the connection processing method in the foregoing embodiments and can achieve the same technical effect, and details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only an example of the present invention, and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. A connection processing method is applied to a terminal device, and comprises the following steps:

if the connection operation failure is detected to be the first connection operation failure, executing a processing process corresponding to the failed connection operation;

the processing procedure corresponding to the connection operation with the execution failure comprises the following steps: reporting failure information to a network side; wherein the failure information comprises: a type of first connection operation failure;

the reporting of the failure information to the network side includes: and reporting the failure information to a network side through the connection with the source node.

2. The method according to claim 1, wherein the detecting whether the connection operation corresponding to the configuration information fails comprises:

timing a first connection operation corresponding to the first connection configuration information through a first timer, and detecting whether the first connection operation fails or not based on a timing result of the first timer;

alternatively, the first and second electrodes may be,

and timing a first connection operation corresponding to the first connection configuration information through a first timer, and detecting whether the first connection operation fails or not based on a timing result of the first timer.

3. The method of claim 2, wherein the configuration information further comprises a first timing threshold of the first timer;

the detecting whether the first connection operation fails based on a timing result of the first timer includes: judging whether the first timer is overtime or not according to the first timing threshold; and if so, determining that the first connection operation fails.

4. The method according to claim 2 or 3, wherein the timing, by the first timer, the first connection operation corresponding to the first connection configuration information includes:

starting the first timer when a first connection operation is performed based on the first connection configuration information;

stopping the first timer when the first connection is established.

5. The method of claim 4, wherein determining whether to establish the first connection is performed by at least one of:

if receiving indication information which is sent by network side equipment and used for finishing the random access process to the target node, determining that the first connection is established;

6. The method of claim 1, wherein the detecting whether the connection operation corresponding to the configuration fails comprises:

timing a second connection operation corresponding to the second connection configuration information through a second timer, and detecting whether the second connection operation fails or not based on a timing result of the second timer; alternatively, the first and second electrodes may be,

and timing a first connection operation corresponding to the first connection configuration information and a second connection operation corresponding to the second connection configuration information through a second timer, and detecting whether the second connection operation fails or not based on a timing result of the second timer.

7. The method of claim 6, wherein the configuration information further comprises a second timing threshold of the second timer;

the detecting whether the second connection operation fails based on the timing result of the second timer includes: judging whether the second timer is overtime or not according to the second timing threshold; and if so, determining that the second connection operation fails.

8. The method according to claim 6, wherein the timing, by the second timer, the second connection operation corresponding to the second connection configuration information includes:

starting the second timer when a second connection operation is performed based on the second connection configuration information;

stopping the second timer when the second connection is established.

9. The method according to claim 6, wherein the timing, by the second timer, the first connection operation corresponding to the first connection configuration information and the second connection operation corresponding to the second connection configuration information includes:

starting the second timer when a first connection operation is performed based on the first connection configuration information;

stopping the second timer when the second connection is established.

10. The method according to claim 8 or 9, wherein determining whether to establish the second connection is performed by at least one of:

if receiving indication information which is sent by network side equipment and used for finishing the random access process to the target node, determining that the second connection is established;

and if receiving confirmation information of the second connection establishment completion sent by the network side equipment, determining that the second connection is established.

11. The method according to any of claims 1 to 3, wherein detecting the failure of the connection operation is detecting the failure of the first connection operation;

the processing procedure corresponding to the connection operation with the execution failure further includes at least one of the following processing:

re-performing a connection operation based on the configuration information;

resetting or rebuilding a connection entity of the terminal equipment and the source node;

and resetting or rebuilding a connection entity of the terminal equipment and the target node.

12. The method according to any one of claims 1 to 3, further comprising: if the connection operation failure is detected, detecting the second connection operation failure;

the processing procedure corresponding to the connection operation with the failed execution comprises at least one of the following processing:

re-performing a connection operation to the configuration information

reporting failure information to network side equipment; wherein the failure information at least comprises the following information: a type of second connection operation failure; measurement information of at least one of the source node cell, the target node cell and the neighbor cell.

13. The method according to any one of claims 1 to 3, wherein the detecting whether the connection operation corresponding to the configuration information fails comprises at least one of the following manners:

if the random access of the connected Media Access Control (MAC) layer is detected to reach the maximum sending times, determining that the connection operation corresponding to the configuration information fails;

if detecting that the reconfiguration of the connected RRC message fails, determining that the connection operation corresponding to the configuration information fails;

and if the difference value of the subframe boundary of the uplink transmission between the main cell group and the auxiliary cell group of the terminal equipment exceeds the maximum uplink transmission timing difference, determining that the connection operation corresponding to the configuration information fails.

14. The method of claim 1, wherein the failure of the first connection operation comprises: the connection operation between the terminal equipment and the source node and/or the target node is failed; or, the second connection operation failure comprises: and the connection operation between the terminal equipment and the target node fails.

15. The method according to claim 1 or 2, wherein the failure information further comprises: measurement information of at least one of the source node cell, the target node cell and the neighbor cell.

16. The method according to claim 1 or 2, wherein the failure of the first connection operation refers to a failure of establishing a connection with a target node while maintaining the connection with a source node.

17. A connection processing method is applied to a network side device, and the method comprises the following steps:

the configuration information is used for the terminal equipment to execute connection operation according to the configuration information;

the method further comprises the following steps:

receiving failure information reported by the terminal, wherein the failure information comprises: a type of first connection operation failure;

the receiving the failure information reported by the terminal comprises: and receiving failure information reported by the terminal through the connection with the source node.

18. The method of claim 17, wherein the configuration information comprises a first timing threshold;

the first timing threshold is used for the terminal device to detect whether the first connection operation based on the first connection configuration information fails according to the first timing threshold.

19. The method of claim 17, wherein the configuration information comprises a second timing threshold;

the second timing threshold is used for the terminal device to detect whether a second connection operation based on the second connection configuration information fails according to the second timing threshold.

20. A terminal device, characterized in that the device comprises:

the second execution module is used for executing a processing procedure corresponding to the failed connection operation if the connection operation failure is detected to be the first connection operation failure;

21. The apparatus of claim 20, wherein the detection module comprises:

alternatively, the detection module includes:

a first detection unit configured to detect whether the first connection operation has failed based on a timing result of the first timer.

22. The apparatus of claim 21, wherein the configuration information further comprises a first timing threshold of the first timer;

the first detection unit is specifically configured to:

judging whether the first timer is overtime or not according to the first timing threshold; and if so, determining that the first connection operation fails.

23. The device according to claim 21 or 22, wherein the first timing unit is specifically configured to:

starting the first timer when a first connection operation is performed based on the first connection configuration information; stopping the first timer when the first connection is established.

24. A network-side device, the device comprising:

the apparatus further comprises:

a receiving module, configured to receive failure information reported by the terminal, where the failure information includes: a type of first connection operation failure;

the receiving module is specifically configured to receive failure information reported by the terminal through connection with a source node.

25. The apparatus of claim 24, wherein the configuration information comprises a first timing threshold;

26. A terminal device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the connection processing method according to any one of claims 1 to 16.

27. A network-side device, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the connection processing method according to any one of claims 17 to 19.

28. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the connection process according to any one of claims 1-16; alternatively, the computer program realizes the steps of the connection processing method according to any one of claims 17 to 19 when executed by a processor.